Status Management and Scope of Application
Use
The change states of recipes go through different stages during their processing and each stage permits different processing steps and business transactions. Change states of recipes are, for example, created, used, and then replaced by a new change state. Their application area can be unrestricted or limited to a certain regional or organizational unit.
With status management and the scope of application, the SAP system provides functions that you can use to ensure that the sequence of processing stages laid down for the recipe is observed and document this.
Prerequisites
You have activated status management and the check for dependent change states depending on the recipe type in Customizing for
Recipe Management
under
Recipe Settings
. You can also deactivate both of these functions here.
Recommendation
If you have to comply with the requirements of Good Manufacturing Practices (GMP) for the pharmaceutical industry or a similar standard, we recommend that you activate these functions.
For information about other requirements, see the documentation of the individual functions (see below).
Features
Function |
Description |
|---|---|
System statuses document and guarantee the sequence of processing steps defined in the standard system for the change state of a recipe. |
|
In addition to system statuses, this function guarantees that the processing sequence is observed across all change states of a recipe. |
|
User statuses are part of a status profile that you define. You add user statuses to the system statuses of a recipe defined in the standard system. You use them to map enterprise-specific processes in the SAP system. |
|
You use scopes 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. |