Dependencies (SAP Library - Master Recipes (PP-PI-MD))

Dependencies

Before master recipes are archived and deleted, the system checks for the following usages:

Usage in a production version

The master recipe is stored in the material master record as part of a production version.

Usage in an inspection lot

This criterion is only relevant if you have installed the application component Quality Management System (QM). You can only archive a master recipe if it is no longer used in an inspection lot.

Usage in a run schedule header

A run schedule header always requires information from its master recipe, for example for confirmation. You can only archive this type of master recipes if the run schedule header is complete and archived.

Therefore, the archiving functionality for master recipes is dependent on the following objects:

Material master records with production versions

Run schedule headers

Inspection lots (archiving object QM_CONTROL)

Before archiving a master recipe, the system does not check whether you have defined relationships to other master recipes. Relationships across recipes are deleted when the master recipe containing the predecessor phase of the relationship is deleted. They are also deleted if the recipe with the successor phase is not deleted in the same archiving run.

What Happens If a Master Recipe Is Still Used?

If in the usage check, the system finds a master recipe that is still being used, the system responds in one of the following ways:

The archiving run is terminated. You receive an information message with the master recipe that is still being used. Do not set the Log indicator in variant editing for this result

The archiving run is completed. You receive a log with a list of all master recipes that could not be archived or deleted because of the usage check.
Set the Log indicator in variant editing for this result.