Use

You use the scope of application to restrict the use of change states for a recipe to certain regional or organizational units. You enter a separate validity period along with a status for each scope of application entry. This is necessary, for example, in the following cases:

If you want to release a change state for a restricted usage only

If you want to release a change state for different usages with different validity periods

Integration

You can also assign scopes of application to independent formulas (see Scope of Application for Formulas ). In dependent formulas, the status and scope of application of the recipe to which they belong apply.

Prerequisites

You have made the following settings in Customizing for Recipe Management under Scope of Application

You have defined the ratings and validity areas for which you want to use your recipes.

You have made the settings for the scope of application status.

Features

For general information about the structure and use of scopes of application, see Scope of Application . Also note the following when using scopes of application in recipes:

Recipes have a status network that you can use to release change states generally, that is without restricting the usage. You activate the use of scope of application entries by assigning the status Application scope restricted to a change state instead (see System Statuses for Recipes ).

In recipes, you edit the scope of application for a change state. You can define several scope of application entries per change state.

Separate status networks are valid within each scope of application (see Statuses for the Scope of Application for Recipes ).

When you use scopes of application, the data of the relevant change state no longer determines the validity period of a recipe; this is done by the validity period of the scope of application entries. This may deviate from the validity period of the relevant change state, for example, if you want to implement a recipe in a certain region later than in others.

You can change the validity area for released general recipes on the Basic Data tab page later on. Choose with the quick info text Change Date.

Activities

Editing Scopes of Application

Shifting the Valid-From Date in Engineering Change Management

By shifting the valid-from date of a change master record, you change the validity of the objects edited with this change master record. In addition to the valid-from date of the relevant scope of application entry, the system adjusts the valid-to date of the preceding scope of application entry.

To prevent inconsistencies, you should not make the valid-from date of a scope of application entry a date before the valid-from date of the preceding or a date after the valid-from date of the succeeding scope of application entry. The system does not check this inconsistency in engineering change management.

Evaluating the Use of Change Master Records

You use this procedure to evaluate the use of change master records in scopes of application, recipes, and formulas.

Example

The following graphic illustrates in a sample recipe how scope of application entries can be used. It shows the change states of the recipe along with their validity periods and scope of application entries for which they have been released.

Note that separate scope of application entries can be defined for each change state and that the validity period of the scope of application entry can be different from that of the change state.

You introduce the recipe in the USA on January 2. After a successful pilot phase, you introduce it in the EU too from March 15. In its first phase, production is only carried out internally. On July 1, you replace change state C1 by change state C2 in the United States, which is used to manufacture an improved version of the product. On October 15, you introduce this change state in the EU but it does not have much success there. For this reason, you replace it by an even further improved version on March 20 of the following year. Change state C3 is used to manufacture this version. Since this version sells extremely well, you increase production capacity in the EU by means of a production partnership from July 10. You release the recipe for the partner, too. At the same time, you introduce change state C3 in the USA.