Show TOC

Function documentationStatus Schemes for Recipes Locate this document in the navigation structure

 

Status schemes support you during a release process. The following status schemes are defined for recipes in the standard system:

  • Simple status scheme

    You use this status scheme if you only use the recipe in the development department, for example.

  • Status scheme with transfer from the development department to the production department

    You use this status scheme if you transfer the recipe via the Guided Structure Synchronization to the production department and want to create a manufacturing BOM from it.

Prerequisites

If you want to use your own status scheme, you have edit the activities in Customizing for Recipe Development, under   Status Management  .

You enter this status scheme under   Recipe   Define Recipe Types   for the recipe types used by you.

Features

The following status attributes are available for recipes:

  • DELETION_ALLOWED: Recipe can be marked for deletion

  • LOCKED_FOR_CHANGE: Recipe is locked for all changes

  • CONSIST_EXPLOSION: Explosion-relevant recipe data is consistent and the recipe is locked for changes (see Consistency Check)

  • REL_EXPLOSION: Recipe is relevant for explosion (see Explosion)

  • CONSIST_SYNC_BOM: Recipe data that is relevant for synchronization of the recipe with a manufacturing BOM is consistent and the recipe is locked for changes (see Consistency Check)

  • REL_SYNC_BOM: Recipe is locked for all changes and relevant for synchronization with a manufacturing BOM. The recipe data that is relevant for the synchronization of a recipe with a manufacturing BOM is consistent (see Synchronizing a Recipe with a Manufacturing BOM).

Simple Status Scheme

This status scheme contains the following statuses:

  • In Process

    In this status, you can change recipe data and mark a recipe for deletion. From here, you can switch to the For Release status.

  • For Release

    If you want to set this status, the consistency check checks whether the recipe is consistent for the explosion. Only then can you set this status. The recipe is locked for changes as of this status.

    You use this status to initiate the release process; the responsible recipe developer checks the recipe and changes the status.

    From this status, you can either switch back to the In Process status or switch to the Released status.

Caution Caution

In the standard delivery, the following procedure is possible in one of the statuses For Release:

  1. You open the recipe or label and set the status In Process.

  2. You change data.

  3. You set the status back to For Release.

  4. Now you save the data.

With this procedure, you have changed the data in the status For Release, without causing the status change to be documented anywhere, for example in a change document.

To prevent this, you have the following options:

  • You assign the authorizations in such a way that no user has authorization for both status changes, from For Release to In Process and back.

  • You implement the Business Add-In (BAdI) BAdI: Additional Checks Before Status Change in such a way that the status change from In Process to For Release is only possible if the data has been changed beforehand.

End of the caution.
  • Released

    The explosion-relevant recipe data is consistent and the recipe is locked for changes.

    By setting this status, you transfer the recipe to production. In this status, a recipe is considered in the explosion. You cannot change released recipes, you can only set them to status Obsolete.

  • Obsolete

    By setting this status, you lock a recipe temporarily against usage, for example because it is only executed in a particular season due to the availability of raw materials (such as the processing of fresh fruits). You can mark a recipe with this status for deletion, but you cannot change it. From here, you can switch back to the For Release status.

The status attributes, displayed in the following table, are assigned to the status:

Status

Status Attributes

In Process

  • Can be marked for deletion

For Release

  • Is locked for changes

  • Explosion-relevant data is consistent and can no longer be changed

Released

  • Is locked for changes

  • Explosion-relevant data is consistent and can no longer be changed

  • Is relevant for the explosion

Obsolete

  • Can be marked for deletion

  • Is locked for changes

This graphic is explained in the accompanying text.

Simple Status Scheme

Status Scheme with Transfer from the Development Department to the Production Department

This status scheme contains the following statuses:

  • In Process

    In this status, you can change recipe data and mark a recipe for deletion.

  • For Release (Development)

    If you want to set this status, the consistency check checks whether the recipe is consistent for the explosion and for the synchronization. Only then can you set this status. The recipe is locked for changes as of this status.

    With this status, you can trigger the release process; the responsible recipe developer checks the recipe and transfers the recipe to the production department by setting the status For Release (Production).

  • For Release (Production)

    The production department checks the recipe prior to releasing it. In this status, a recipe is considered in the explosion.

    With this status switch, you automatically change the recipe purpose from development to production (see Recipe Purpose).

Caution Caution

In the standard delivery, the following procedure is possible in one of the statuses For Release:

  1. You open the recipe or label and set the status In Process.

  2. You change data.

  3. You set the status back to For Release.

  4. Now you save the data.

With this procedure, you have changed the data in the status For Release, without causing the status change to be documented anywhere, for example in a change document.

To prevent this, you have the following options:

  • You assign the authorizations in such a way that no user has authorization for both status changes, from For Release to In Process and back.

  • You implement the Business Add-In (BAdI) BAdI: Additional Checks Before Status Change in such a way that the status change from In Process to For Release is only possible if the data has been changed beforehand.

End of the caution.
  • Released for Production

    By setting this status, you transfer the recipe to production. You cannot change released recipes, you can only set them to status Obsolete.

  • Obsolete

    By setting this status, you lock a recipe temporarily against usage, for example because it is only executed in a particular season due to the availability of raw materials (such as the processing of fresh fruits). In this status, you can switch from the status Released for Production. You can mark a recipe with this status for deletion, but you cannot change it.

The status attributes, displayed in the following table, are assigned to the status:

Status

Status Attributes

In Process

  • Can be marked for deletion

For Release (Development)

  • Is locked for changes

  • Explosion-relevant data is consistent and can no longer be changed

  • Data that is relevant for synchronization of the recipe with a manufacturing BOM is consistent and can no longer be changed

For Release (Production)

  • Is locked for changes

  • Explosion-relevant data is consistent and can no longer be changed

  • Data that is relevant for synchronization of the recipe with a manufacturing BOM is consistent and can no longer be changed

  • Is relevant for the explosion

Released for Production

  • Is locked for changes

  • Explosion-relevant data is consistent and can no longer be changed

  • Is relevant for the explosion

  • Is relevant for the synchronization of a recipe with a manufacturing BOM

Obsolete

  • Can be marked for deletion

  • Is locked for changes

This graphic is explained in the accompanying text.

Status Scheme with Transfer from the Development Department to the Production Department