Status Management and Scope of Application 

Use

The change statuses of recipes go through different stages during their processing and each stage permits different processing steps and business transactions. Change statuses of recipes are, for example, created, used, and then replaced by a new change status. 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 can activate or deactivate status management and the check for dependent change statuses depending on the recipe type (see Customizing for Recipes, IMG activity Recipe Settings). If you have to comply with the requirements of Good Manufacturing Practices (GMP) for the pharmaceutical industry or a similar standard, we strongly recommend activating these functions.

For information about other requirements, see the documentation of the individual functions (see below).

Features

Function	Description
System Statuses for Recipes	System statuses document and guarantee the sequence of processing steps defined in the standard system for the change status of a recipe.
Checking of Dependent Change Statuses	In addition to system statuses, this function guarantees that the processing sequence is observed across all change statuses of a recipe.
User Statuses for Recipes	User statuses are part of a status profile that you defined. They add to the system statuses defined for recipes in the standard system and serve to map enterprise-specific processes onto the SAP System.
Scope of Application	You use scopes 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.