Scope of Application for Recipes 

Use

You use the scope of application to restrict the usage of change statuses 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. You need to do so, for example:

·        If you want to release a change status for a restricted usage only

·        If you want to release a change status 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

In Customizing for Scopes of Application:

·        The ratings and validity areas for which you want to use your recipes have been defined.

·        The settings for the status of the scope of application have been made.

Features

For general information about the structure and use of scopes of application, see Scope of Application. In addition, bear in mind the following when using scopes of application in recipes:

·        Recipes have a status network that you can use to release change statuses 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 status instead (see System Statuses for Recipes).

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

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

·        If you use scopes of application, the validity period of a recipe is no longer determined by the data of the relevant change status but by the validity period of the scope of application entries. This may deviate from the validity period of the relevant change status, for example, if you want to implement a recipe in a certain region later than in others.

Activities

·        Editing Scopes of Application

·        Shifting the Valid-From Date (Engineering Change Management documentation)

By shifting the valid-from date of a change master record, you change the validity of the objects edited with this change master record. Beside the valid-from date of the scope of application entry in question, the valid-to date of the preceding scope of application entry is adjusted, too.

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. This inconsistency is not checked in engineering change management at present.

·        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 graphic below illustrates in a sample recipe how scope of application entries can be used. It shows the change statuses 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 status, and that the validity period of the scope of application entry can be different from that of the change status.

Scopes of Application for a Sample Recipe

The recipe is introduced in the USA on 02/01. After a successful pilot phase, it is also used in the EU as of 03/15. In its first phase, production was only carried out internally. On 07/01, change status C1 is replaced by change status C2 in US, which is used to manufacture an improved version of the product. In 10/15, this change status is also introduced in the EU, where it is not very successful though. For this reason, it is replaced by an even further improved version on 03/20 of the following year. Change status C3 is used to manufacture this version. Since this version sells extremely well, the production capacity in the EU is increased by a production partnership as of 07/10. The recipe is released for the partner, too. At the same time, change status C3 is also introduced in the US.