Recipe Editing 

Purpose

This process describes how recipes or recipe change states are typically created. The process covers the steps from creating a recipe to its release by the decision-maker responsible. The process applies to general recipes and site recipes.

Use the transformation function to create a master recipe. For more information, see Transformation Process.

Prerequisites

●     You have defined the required recipe types in Customizing for Environment, Health and Safety (EH&S). For more information, see the Implementation Guide (IMG) for Recipe Management under Set Up EH&S Customizing.

●     For these recipe types, you have activated status management and all recipe views (tab pages) available in the SAP standard system in Customizing for Recipe Management in the IMG activity Recipe Settings. If this is not the case, the process steps concerning the recipe status or missing tab pages cease to apply.

Process Flow

...

       1.      You start recipe editing and enter the basic data for the relevant change state. Depending on the initial situation, you proceed as follows:

○     You create a new recipe. You can copy the data of an existing recipe if required. You specify the type and key of the recipe along with the valid-from date as of the current date.

○     You load an existing recipe and create a new change state for it. You specify a valid-from date for the change state that is after the valid-from date of the recipe. The validity period of the existing change state is shortened accordingly.

○     You create a version or draft of an existing recipe.

○     You load and edit a change state whose processing has not yet been closed.

For more information, see Information Systems and Loading of Specifications.

       2.      You enter the recipe data that applies to all change states. This includes:

○     Recipe structure

You link all recipes of the type general recipe, site recipe, or your own copies of these recipe types to a formula. If the settings made for the recipe type specify that recipe-dependent formulas are used, the formula and the link to the recipe are created automatically when you create the recipe.

○     Recipe hierarchy

Depending on the recipe type, you link a recipe to higher- and/or lower-level recipes. In this way, you assign, for example, the site recipes derived from a general recipe to this recipe and the master recipes created from a site recipe to this site recipe.

○     Recipe classification

If you want to group your recipes according to your own criteria, you classify the recipe.

○     Recipe identifiers

You use identifiers to assign different descriptions to your recipes, depending on the context.

       3.      You enter the following data for each change state:

○     The basic data Person Responsible for Recipe and Reference Quantity

You already entered this data when you created the recipe. This data is transferred to all change states you create afterwards, where you can change it if necessary.

○     Documents

You link centrally managed documents such as standard operating procedures (SOPs) and plant graphics stored in SAP Document Management to the relevant recipes. The document links are copied when a new change state is created.

○     Texts

To describe change states, you can enter language-dependent short texts and long texts. You can also translate some texts in recipe editing.

○     Scope of application

You can specify scopes of application that combine a spatial or organizational assignment, the validity period, and a change state.

○     Formula data

In recipes with dependent formulas, you edit the relevant change state of the formula from within the recipe.

○     Process data

You can edit the process and its elements from the recipe, or create them as independent building blocks and copy them to the recipe.

○     Equipment requirement data

You can edit the equipment requirements from the recipe, or create them as independent building blocks and copy them to the recipe.

       4.      You close editing of a change state by setting the appropriate status on the  Basic Data tab page for the recipe.

       5.      The decision-maker responsible (for example, the production director or head of quality control) checks the change state. Depending on the results of this check, he or she sets one of the following statuses on the  Basic Data tab page:

○     Rejected:

The change state contains errors. You can restart the editing of the change state and correct the data.

○     Released:

The change state can be used immediately and without any restrictions.

○     Application scope restricted:

The change state is not generally released.
You define different scopes of application with limited regional or organizational validity, a separate validity period, and status for it. The recipe is released separately for each scope of application.

Result

You can only use the change state until one of the following actions is performed:

●     You deactivate the change state for a certain period of time. You may want to do this, for example, if a process is carried out only in a certain season due to the raw material availability (for example, the processing of fresh fruit).

●     You mark the change state as obsolete. It can then be deleted.