Consistency Check (SAP Library - Master Recipes (PP-PI-MD))

Consistency Check

When you create a master recipe, you can easily get data inconsistencies, for example:

You create a phase and enter a number for it that has already been created for a later date.

You determine in the control key for an operation or phase that inspection characteristics are required for it. However, you do not create the inspection characteristics immediately.

Some inconsistencies can only be removed at a later date when you know what the production process will be like in detail. For some consistency checks, you can therefore determine the point in time at which they are carried out yourself.

These check whether:

Operation and phase numbers are unique

Secondary resource numbers are unique within an operation or phase

Process instruction numbers are unique within a phase

Characteristic numbers are unique within a process instruction

Inspection characteristics required by the control key are defined

If you do not carry out the consistency check in the master recipe, it will automatically be carried out when you create an order.

The consistency check is always carried out for the entire recipe group.
It is not only carried out on the key date but for the entire validity period of the change status you called. Therefore, a recipe is also inconsistent, for example, if the key date you used when creating inspection characteristics is later than that of its phase.

Consistency Check in the Master Recipe

The consistency check in master recipes can be started as follows:

Automatically for a specific recipe status

You determine the status for which the consistency check is carried out automatically when you define recipe statuses in Customizing for Master Recipes.

The automatic consistency check is carried out before saving a master recipe. In addition, the system checks for inspection characteristic consistency when you exit the characteristic overview.

Manually during recipe editing

You can manually start the consistency check at any time irrespective of the recipe status.

During the check, the system creates a consistency log where system messages on errors are collected. You can use these system messages to decide whether you want to save the recipe or correct the errors.

Consistency Check at Order Creation

Once a recipe is checked and saved without inconsistencies, the system sets an internal indicator in the recipe header so that no further check is carried out when you create an order . In the following cases, the indicator is reset:

If you change the recipe again without repeating the consistency check

If you change the valid-from date of a change number used in the recipe (see Engineering Change Management and Recipe Approval)

When the order is released, a consistency check is carried out if:

The transferred recipe is internally marked as inconsistent

The recipe is consistent but a configurable material has been assigned to it at header level