Use

You use the status of a scope of application to document which processing status the recipe has with regard to the usage defined in the scope of application. In this way, you decide separately for each scope of application entry whether and when you want to release the relevant change state of the recipe. You use the following types of status for this:

System status

System statuses are defined in the standard system. You use them to document the processing stages defined for a change state in the standard system.

User status

They are part of a status profile that you defined and can use to add to the system statuses if necessary. You use user statuses to map enterprise-specific processes in the SAP system.

Prerequisites

For the scope of application for recipes, you have specified in Customizing for Recipe Management under Determine Status Attributes for Recipes which system or user status you want to use as the initial status. This is the status Processing closed in the standard system.

If you want to use your own statuses, you have defined a suitable user status profile in addition and activated it for the scope of application for recipes in Customizing for Recipe Management under Set Up User Status Profile

Features

Only one system status or user status is active at any processing stage for a scope of application entry of a recipe. The following status network applies:

Each scope of application entry is automatically assigned the initial status you defined in your system settings when it is created (see "Prerequisites"). You make all subsequent status changes on the Scope of Application tab page.

The user statuses of the active user status profile are inserted in the status network as a complete chain. They apply to all recipes in Recipe Management. If no user status profile has been activated in your system, you can release scope of application entries with status Processing Closed straight away.

You can assign the authorization for carrying out the status switch separately for each system status and user status in the authorization object of the scope of application. In this way, the authorization can be restricted to certain users. For more information, see the Recipe Management Implementation Guide (IMG) under Set Authorizations .

Example

You specify the plants for which your recipes are valid in the scope of application for your recipes. You want production and quality assurance of the relevant plant and finally the head of quality control to check the recipes before they are released. To ensure this process is carried out, you have activated a user status profile with the following user statuses in Customizing for the scope of application for recipes:

Therefore, the following status network applies:

An employee from production sets the status Checked prod. as the first user status. An employee from quality assurance can then set the next status Checked QM, which in turn permits the next status Checked head of QM. The recipe cannot be released for the scope of application until the head of quality control has set this status.