Consistency Checks for Production VersionsYou use this function to check whether the data of a production version is consistent with the data of the assigned task lists/master recipes and the assigned alternative BOM. In this way, you make sure that a valid task list or valid BOM really exists for the entire validity period of the production version.
The consistency check determines a check status for the objects assigned (task list/recipe or BOM). All change statuses within the validity period of the production version are taken into account. Warning and error messages about inconsistencies are displayed in the check result. The check status for each object is displayed as an icon in the production version. The following icons may be displayed:
Check Status |
Meaning |
Possible Reasons |
|
|
|
|
|
|
|
|
|
At the production version level, the check status is summarized as follows:
If no task list/master recipe or alternative BOM is assigned to the production version, the yellow traffic-light is displayed.
Otherwise, the check status of the object with the worst check result is displayed. A red traffic-light is, for example, displayed whenever a red traffic-light exists at the object level.
You can check the data consistency of the production version as follows:
For individual production versions of a recipe or material (see Maintaining Production Versions ) The check status is saved together with the production version, recipe, or material.
For all production versions of a material, alternative BOM, or recipe (see Checking Production Versions (Mass Function) ) You decide on the initial screen whether you only want to display the check result or also transfer the check status to the production version.
Note
The system does not automatically lock a production version for all usages if the check result is negative. However, you can set the lock indicator manually if you want to (see Editing Production Versions ).