User Statuses for Recipes 

Use

User statuses belong to one of the status profiles that you defined and add to the recipe system statuses defined in the standard system (see System Statuses for Recipes). Which status profile applies to the change states of a recipe, depends on the recipe type.

User statuses map enterprise-specific processes onto the SAP system. They document transactions that are not logged in the standard system and ensure that certain transactions not defined in the standard system are executed.

Prerequisites

●     You have defined the necessary user profiles along with their user statuses, transaction control, and authorizations for the recipe types (see Customizing for Recipes, activity Set Up User Status Profile).

●     You have assigned the required status profile to your recipe types (see Customizing for Recipes, activity Recipe Settings).

Features

Like system statuses, user statuses can be set or deleted by business transactions and, in turn, influence which transactions are permitted. In addition, you can set and delete user statuses manually in the recipe workbench. You can define the authorization required for the status change separately for each user status in the status profile and thus restrict it to certain users.

The SAP system distinguishes the following types of user status:

●     User statuses with a status number

They represent a status sequence. Only one status with a status number can be set in a recipe change state at any given time. Once the next status with a status number is set, the preceding status is deleted.

●     User statuses without a status number

Several of these statuses can be active at any one time. They can be set in addition to the statuses with a status number.

You can restrict the usage of user statuses.

For more information, see Restriction of User Statuses.

Activities

To edit the user statuses of a change state, go to the  Basic Data tab page and choose  with the quick info text Choose Detail next to the status field. You set or delete a user status by selecting or deselecting it.

Example

You want the change states of your recipes to be subject to the following checks:

●     At the end of the processing phase, the change states are first to be checked by production and then by someone from quality assurance.

●     Before releasing them, the change states are first to be checked by the production director and then by the head of quality control.

To make sure that this process is observed, you assigned a user status profile with the following user statuses to your recipe types in Customizing:

Status	Initial	Transaction Control
In Process: Production	Yes	The status prohibits transaction Release Recipe.
To Be Checked: Prod.Director	No	The status is set by transaction Close Recipe Processing. It prohibits transactions Release Recipe and Restrict Scope of Application.

Therefore, the following status network applies:

An employee in production deletes the initial user status In Process: Production once recipe creation has been completed. An employee in quality assurance can then check the recipe and close recipe processing.

When recipe processing is closed, the system automatically sets the user status To Be Checked: Prod.Director. The production director deletes this status once he or she has checked the recipe. The head of quality control can then release the recipe or set status Application Scope Restricted.