Consistency Check 
You use the consistency check to check the recipe data for the whole recipe according to selected criteria, for example if you have changed data or if you want to change the recipe status.
If the recipe is not consistent, the system issues messages that describe which data caused the inconsistency.
If you change data relevant to the consistency or optimize the formula, you should carry out the consistency check again.
Note
Data in the standard system that is not relevant to the consistency is for example:
Description of the recipe
Linked documents
Recipe purpose
Prerequisites
If you want to use additional individual checks, you can implement the corresponding BAdIs accordingly. You can find these BAdIs in Customizing for the PLM Web UI under 
Recipe Development 
Recipe Business Add-Ins (BAdIs) BAdIs for Checks 
.
If you want the system to consider additional checks at status change, implement the BAdI Additional Checks Before Status Change accordingly. You will find the BAdI in Customizing under Recipe Development Status Management Business Add-Ins (BAdIs) BAdI: Additional Checks Before Status Change
Features
The system carries out the consistency check in the following cases:
You start the consistency check manually, by choosing the corresponding pushbutton in recipe processing.
You change the status of a recipe to a status with a status attribute that requires a consistency check (see Status Schemes for Recipes).
The following status attributes for recipes require a consistency check:
CONSIST_EXPLOSION: Explosion-relevant recipe data is consistent and the recipe is locked for changes.
CONSIST_SYNC_BOM: Recipe data that is relevant for synchronization of the recipe with a material BOM is consistent and the recipe is locked for changes.
REL_SYNC_BOM: Recipe is relevant for synchronization with a material BOM and is locked for changes, recipe data that is relevant for synchronization of the recipe with a material BOM is consistent (see Synchronizing a Recipe with a Manufacturing BOM)
The following check criteria exist in the system:
General Criteria
If a material and a specification have been assigned to the formula item:
Is the material assigned to the specification?
Are the total quantities of all input items equal to the total quantities of all output items?
Are the calculated values, in particular the absolute mass, still correct?
Calculated values can no longer be correct, for example, if the relevant data of a specification used in a recipe has been changed.
If a plant is specified for the recipe:
Does the assigned material exist in the corresponding plant?
Explosion-Relevant Criteria:
Has the component type been specified for every formula item that is not a stream?
Has a specification been specified for every formula item that is not a stream?
If a stream has a component type that causes an explosion stop: Is a specification assigned to the formula item?
Can the quantities specified in all explosion-relevant formula items be converted into units of mass?
Synchronization-Relevant Criteria
Has a quantity or an exception value been assigned to every formula item?
Has a material been assigned to every formula item that is not a stream?
If a material has been assigned to the formula item in addition: Do the units of measure used match the assigned material?
Has at least one input item been specified?
The following table indicates which criteria the consistency check uses in which situation:
Criteria |
Manually-Triggered Check |
Check at Status Change |
|---|---|---|
General Criteria |
Always |
When the status to be set has one of the following status attributes:
|
Explosion-Relevant Criteria |
When the assigned status scheme contains a status with one of the following status attributes:
|
|
Synchronization-Relevant Criteria |
When the assigned status scheme contains a status with one of the following status attributes:
|
When the status to be set has one of the following status attributes:
|