Use

System statuses document the processing stages of a change state in a recipe that are defined in the standard system. The system sets or deletes the system status according to a fixed status network when you carry out certain processing steps in the recipe. At the same time, the status set determines which recipe data may be changed and which processes may be carried out. System statuses, therefore, ensure that the sequence of processes defined in the standard system is observed.

Prerequisites

You have activated status management for your recipe types in Customizing for Recipe Management under Recipe Settings

If you have to comply with the requirements of Good Manufacturing Practices (GMP) for the pharmaceutical industry or a similar standard, we recommend activating the check for dependent change states (see Checking of Dependent Change States ).

Features

Only one system status is active at any processing stage of a recipe change state. Below you will find an overview of the different statuses, their sequence, and meaning.

In process

This status is assigned automatically to every change state of a recipe when it is created. You can change the recipe data only if this status is set.

Processing closed

You assign this status to a change state whose release procedure you want to initiate. The change state is frozen. It can now be checked by the persons responsible who can release or reject it.

Released

You use this status to generally release a change state, that is, without any restrictions by the scope of application.

You can only change released recipes if you create a new change state and set the existing change state to obsolete. This ensures that a change state is kept unchanged once it has been released.

You can also assign documents to released change states, provided that the relevant Customizing settings have been made. Documents assigned in this way are, however, specially highlighted (see Documents ).

Application scope restricted

You set this status if you want to limit the usage of a change state to certain regional or organizational units. You can assign different scopes of application to change states with this status. Each of these scopes of application has its own validity period and status (see Scope of Application for Recipes ). The same restrictions as described for released recipes apply to the editing of all other recipe data.

Inactive

You use this status to lock a recipe temporarily, for example, because it is only executed in a certain season due to the raw material availability (such as the processing of fresh fruit).

In process, rejected , or obsolete

You can only delete recipes with these statuses.

Activities

You change the system status of a change state by performing the relevant business transaction. Choose the corresponding function on the Basic Data tab page to do so.