Statuses for the Scope of Application for Recipes 

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 statuses

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

●     User statuses

These are part of a status profile that you defined and can use to add to the system statuses if necessary. User statuses enable you to map enterprise-specific processes onto the SAP system.

Prerequisites

●     You have specified which system status or user status is to be used as the initial status for the scope of application for recipes. In the standard system, this is the status Processing Closed (see Customizing for Scopes of Application, IMG activity Determine Status Attributes for Recipes).

●     If you want to use your own statuses, you must also have defined a suitable user status profile and activated it for the scope of application for recipes (see Customizing for Scopes of Application, IMG activity 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:

Status Network for the Scope of Application for Recipes

Each scope of application entry is automatically assigned the initial status 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 directly release scope of application entries with status Processing Closed.

You can assign the authorization for carrying out the status switch separately for each system status and user status in the authorization object for the scope of application. In this way, the authorization can be restricted to certain users (see Customizing for Recipe Management, IMG activity 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 that this process is carried out, a user status profile with the following user statuses has been activated in Customizing for Scopes of Application for recipes:

No.	Status	Next Statuses Allowed
1	Checked prod.	Checked QM
2	Checked QM	Checked head of QM
3	Checked head of QM	Checked prod. and Checked QM

Therefore, the following status network applies:

The status Checked prod. is set by an employee in production as the first user status. An employee of 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 unless the head of quality control has set this status.