Use

You use the scope of application to specify the following:

You use the scope of application to specify which usage (combination of rating and regional or organizational unit) the data records are specified for, for objects without direct usage. You specify a validity period with the appropriate status for each scope of application entry. In this way you can guarantee that the data records are released separately for each usage.

You use the scope of application to specify which active direct usage a particular status is valid for, for objects with direct usage. The scope of application entry is useful if the usage of the scope of application entry applies to the active direct usage of the data record. Only then does the scope of application entry define the status of the data record.

In the formula, depending on the Customizing settings you made, you can use the status to achieve following for objects with and without direct usage:

Protect data from changes

Prevent data from being output in reports

The system response for objects with direct usage corresponds to the standard response of the Environment, Health and Safety (EH&S) component (see Generation Variant ).

For more information see Statuses for the Scope of Application for Formulas .

Integration

How and whether you assign scopes of application to a formula depends on the type of formula assignment specified in the recipe (see Formula Assignment ):

Independent formulas have their own scopes of application that you create during formula editing.

In dependent formulas, the status and scope of application for the recipe to which they belong, apply (see Scopes of Application for Recipes ).

When the system generates formula data without direct usage, it uses the scope of application to check whether it is allowed to output the data of a formula. The active direct usage is critical for formula data with active direct usage. For more information see Statuses for the Scope of Application for Formulas .

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 formulas.

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 formulas:

Independent formulas do not have a general status network that you could use to release a formula without restricting the scope of application. For this reason, you edit the status of an independent formula in the scope of application (see Statuses for the Scope of Application for Formulas ).

Unlike recipes, formulas consist of several change objects (for example, formula header, material item, or substance item) whose change states may deviate from each other. For this reason, you do not edit the scope of application entries for a particular change state but for the formula as a whole. A scope of application entry applies to all change states of the formula objects that are valid in its validity period.

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. 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 shift the valid-from date of a scope of application entry to 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.

We recommend that when working with change numbers, you change the formula data for the change state with the last valid-from date only.

Example

The following graphic illustrates in a sample formula how scope of application entries can be used. It shows the change states of some of the formula objects along with their validity periods and the scope of application entries in which the formula has been released. Note that the scope of application entries apply to all change states contained in their validity period.

You introduce the formula in the USA on January 5. You first use the change state C1 of the formula header and material item. In the course of improvements, material item 2 (change state C2) is added on March 10 and change state C1 is replaced by C2 in the formula header. You use these change states to introduce the formula in the EU on April 25. Due to high demand, you increase the production capacity in the EU between June 13 and July 10 by means of a production partnership: You release the formula for the partner, too. This makes further changes to the material items necessary. You use change state C3 for the formula header and material item 1 as of June 13 and change state C4 for the formula header and material item 2 as of July 9. As of July 10, the demand can be covered internally again. Therefore, you withdraw the released formula for the partner.