SAP PLM Recipe Development – Recipe Consistency Check vs. Recipe Compliance Check
This blog belongs to a series of blogs regrouped on the SCN page “SAP PLM Recipe Development for Beginners”.
In SAP PLM Recipe Development there are two kinds for checks available:
The question is, are those two checks actually the same thing? If not, what is the difference? Do they address different use cases?
Recipe Consistency Check
Let’s take a look a recipe and click on the button “Check Consistency”.
When we click it, a message appears – in this case “Recipe is consistent” – so all is fine with this recipe.
What about the cases where the recipe is not consistent? Here are some examples:
In this case, when clicking on “Check Consistency” we the message: “Enter a material for formula item 1”. And indeed, the specification of item 1 is not linked with a material and the material field is empty. Creating a BOM (Bill of Material) without materials is not possible, so this check function also makes sense.
In this case, when we click on the button “Check Consistency” an error message appears, stating “Unit of formula item 30 does not match with base unit in material master”.
As we can see in the screen-shot above, all other input items are in grams (G), only this item is in liters (L). To solve the issue, we can either change the unit of measure here in the recipe formula. Or, if this is on purpose to be maintained in liters, then we need to maintain a conversion factor in the material master for this material (SAP GUI – MM02 – Alternative Data).
Consistency checks are not only triggered with the button “Check Consistency”. Status Changes also trigger consistency checks in the background. Here, I tried to change the status from “In Work” to “For Release” for the same recipe as above. But the system does not allow this status change, as the Unit of Measure “Liters” does not match with the Unit of Measure in the material master.
For status change triggered the consistency checks, please take a look at:
IMG: Logistics General – Product Lifecycle Management (PLM) – PLM Web User Interface – Recipe Development – Recipe – Status and Action Management
If you want to build your own customer specific consistency checks, please look at:
IMG: Logistics General – Product Lifecycle Management (PLM) – PLM Web User Interface – Recipe Development – Recipe – Business Add-Ins (BAdIs):
Recipe Compliance Check
Now, let’s take a look at the Compliance Check.
In a recipe, if you click “Additional Functions” – “Start Compliance Check” a new window appears. Here you maintain items to be checked (e.g. Nutrients, Ingredients, …) and you select an Application Area (e.g. Food & Beverage) and a Regulation (e.g. EU regulation).
If you then click “Next”, the compliance check is executed. The traffic lights (green and red) show you the substances and ingredients which are compliant or not compliant with the selected regulation and application area.
The Recipe Consistency Check is integral part of the Recipe Development System. Build in checks (such as specification has to be linked with material before BOM creation can take place) help you to avoid data-inconsistencies which could lead to system errors.
The Recipe Compliance Check is an optional function. This function can be configured and set-up according to the companies specific needs. Application and regulation help you to maintain certain constraints that reflect the legal requirements governments impose on products.