Checking of Dependent Change States

Use

The recipe status network guarantees the correct sequence of processing stages within a change state. In addition to this, this function checks the preceding and succeeding change state when a status is changed. This check applies to all status changes that influence the changeability of recipe data. The check ensures that the processing sequence is observed across all change states of a recipe (see System Statuses for Recipes ).

Prerequisites

You have activated the following functions for your recipe types in Customizing for Recipe Management under Start of the navigation path Recipe Next navigation step Recipe Settings End of the navigation path :

  • Status management

  • Checking dependent change states when the status changes ( Depend.chg states indicator)

    Recommendation Recommendation

    If you have to comply with the requirements of Good Manufacturing Practices (GMP) for the pharmaceutical industry or a similar standard, we recommend that you activate these functions.

    End of the recommendation.

Features

This function regulates status changes in the recipe as follows:

  • You can only assign the status Processing closed (that is, changes are no longer permitted) to a change state if none of the preceding change states has the status In process or Rejected , which means that changes are allowed.

  • You can only assign the status Rejected to a change state with status Processing closed if all of the succeeding change states have the status In process or Rejected .

  • You can only create a new change state (initial status In process ) if all succeeding change states have the status In process or Rejected .

  • You can only release a change state if none of the preceding change states has the status In process or Rejected .

  • You can only assign the status Application scope restricted to a change state if none of the preceding change states has the status In process or Rejected .