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

The following functions have been activated for your recipe types (see Customizing for Recipes, IMG activity Recipe Settings):

●     Status management

●     The check of dependent change states at status changes (Depend.chg statuses indicator)

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

Features

This function regulates status changes in the recipe as follows:

●     You can only assign the status Processing closed (that is, changes are prohibited) to a change state if none of the preceding change states has In process or Rejected status, 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.