Scope of Application

Definition

A combination of regional and organizational assignment, validity period, and the status of an object.

Use

A scope of application entry defines a usage (combination of rating and regional and organizational assignment) that has a particular status within a status network and within a particular validity period.

You can assign scopes of application to the following objects in Recipe Management:

The following distinction is true for the individual objects whose data records a scope of application entry refers to:

  • Objects without direct usage (for example, recipe data, formula header data, and input and output of materials and substances of the formula)

    Recipe data does not normally have a direct usage. However, a formula contains objects with direct usage and objects without.

    You can only assign objects a usage that do not have their own direct usage using the scope of application. A scope of application entry specifies for these objects for which usage the data records that belong to it are intended, in a particular time period. Each scope of application entry is joined to a status. In the recipe, the status is used to document the processing stages that are to be carried out. In addition, you can use the status to achieve the following in the formula for objects without direct usage:

    • Protect data from changes

    • Prevent data from being output in reports

      You can only output formula data of objects without direct usage in a report if a scope of application entry exists whose usage matches the report generation variant in question. If no scope of application entry exists, no data is output.

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

  • Objects with direct usage (formula identifiers, formula value assignments)

    Unlike a recipe, a formula contains objects with direct usage.

    A scope of application entry is relevant for objects with direct usage if the usage of the scope of application entry applies to the active direct usage. The Active indicator must be set for the direct usage of each of the data records in question. The scope of application entry defines the status of the data record only if the entry is relevant. You can use the status to achieve the following in the formula for objects with direct usage:

    • Protect data from changes

    • Prevent data from being output in reports

      You can only output formula data of objects with direct usage in a report if they have their own active, direct usage that matches the report generation variant in question.

      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 .

Structure

A scope of application comprises the following information:

  • A usage for which the data is defined, or for which the data with the appropriate usage should be protected from changes or being output in a report.

    It is made up of the following elements:

    • A rating to characterize the target group for which the data is defined or for which the data should be protected.

      In a business relationship in which you manufacture products together with partners, for example, the ratings For internal use only or For partner would make sense.

    • A validity area for characterizing the regional or organizational unit for which the data is defined or for which the data should be protected.

      Possible validity areas could be, for example, a specific plant, country, or region.

  • Validity period for which the usage is intended

    Validity periods of scopes of application that are assigned to the same object and have the same usage may not overlap each other.

  • Status of the object referring to its current usage and its validity area

    The status network that applies depends on the object type (see Use ).

  • User or area responsible for the relevant object

Integration

You can link a scope of application to a change master record. It is identified by a change master number. In the change master record, you can plan, manage, and document related changes to different objects (for example, recipe, formula, and scope of application) centrally. You specify the valid-from date of the changes in the change master record. It applies to all objects that have been edited with the change master record and can be changed later on.

See also:

Recipe Editing with Change Master Records

Formula Editing with Change Master Records