Scope of Application for Formulas 

Use

You use the scope of application to define:

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

●     Which active direct usage a particular status is valid for, for objects with their own 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, independently of Customizing for objects with and without direct usage, you can use the status to:

●     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 SAP 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 Scope of Application for Recipes).

When generating formula data without direct usage, the system uses the scope of application to check whether data of a formula can be output. 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

In Customizing for Scopes of Application:

●     The ratings and validity areas for which you want to use your formulas 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 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 always edit the status of independent formulas in the scope of application (see Statuses for the Scope of Application of 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 valid-to date of the preceding scope of application entry is also adjusted.

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. This inconsistency is not checked 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 graphic below 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.

Scopes of Application for a Sample Formula

The formula is introduced in the United States on January 5. First, change state C1 of the formula header and material item is used. 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. These change states are used to introduce the formula in the EU on April 25. Due to high demand, the production capacity in the EU is increased between June 13 and October 7 by a production partnership. The formula is released for the partner, too. This makes further changes to the material items necessary. Change state C3 is used for the formula header and material item 1 as of June 13 and change state C4 is used for the formula header and material item 2 as of July 9. As of October 7, the demand is covered purely internally again. The release for the partner is withdrawn.