Recipe Dev

6/17/2019
Recipe Development (PLM-WUI-RCP)

Generated on: 2019-06-17
SAP ERP | 6.18.11
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the SAP Help Portal.
This is custom documentation. For more information, please visit the SAP Help Portal 1
6/17/2019
Labeling
Use
You use Labeling to create and manage label sets. Label sets are used as input for nal product label creation and label artwork
design.
Integration
Labeling is connected to the recipe object as well as to speci cations in the PLM Web User Interface (PLM Web UI), and to
phrase management in the Environment, Health and Safety component by means of Business Add-Ins (BAdIs) in the
enhancement spots RMSL_LABEL and RMSL_LABEL_WEBUI.
With speci cation management and Recipe Development in the PLM Web UI, you manage the speci cations and recipes from
which the system determines the data for a label set. In phrase management, you de ne phrases that you can assign to a label
set as footnotes and statements.
Note
Labeling in PLM Web UI can only create label sets for recipes created in Recipe Development in PLM Web UI.
Features
Labeling uses speci cations and recipes as the basis for creating a label set.
The content of the label set is nalized on the Label De nition view, which includes lists of data for the following labels:
Ingredient label (see Creating an Ingredient Label)
Qualitative label (see Creating a Qualitative Label)
Component label (see Creating a Component Label)
The package label provides additional functions (see Creating a Package Label).
You can perform the following activities using label sets:
Edit label data in Labeling, preview it as a PDF form, or export it as an XML le
Generate WWI reports (see WWI Reports)
Display the ingredient and qualitative data lists with different visual settings for different countries or geographical
areas de ned as target locations (see Target Location)
Classify label sets and restrict their usage, that is, their rating and validity area
De ne different label sets identi ed by primary output speci cations, alternative labels, and label versions. You can
choose to manage your changes with change numbers, but once you have started using change numbers, this decision
cannot be reversed (see Engineering Change Management in Labeling in PLM Web UI).
Apply the same status changes to labels as to recipes, but you can also specify your own status scheme in Customizing.
For more information about status management, see Status Scheme for Label Sets.
Control authorizations using access control management (ACM), see Authorizations and Access Control Context (PLM-
WUI-APP-ACC).
6/17/2019
The content of a label set is de ned as qualitative label, component label, and ingredient label. You can change these names in
the Web Dynpro component con guration and in Customizing activity De ne List Titles, under Logistics - General Product
Lifecycle Management (PLM) PLM Web User Interface Recipe Development Labeling .
Documents
You can assign documents to label sets and manage these document links from Labeling, Document in the Web UI, and
Document Management (DMS) applications.
You can access and edit document assignments in Labeling on the Documents tab of the General Data view, and modify these
assignments even when the rest of the label set is locked for change.
When you copy a label set, the system copies these documents links as well.
More Information
Document Management
Document on the Web UI
Additional features for Labeling
Change Document Application for Label Sets (SAP Note 1987190 )
Ad-Hoc WWI Reports for Label Sets (SAP Note 1968394 )
Target Location
Use
You can differentiate label content for different countries or geographical areas with target locations, since target locations
allow you to display ingredient or qualitative data in different ways.
A target location consists of a rating and validity area combination, and one or more languages.
Features
 Example
The following data may be entered as the label set's target location in the case of Switzerland:
Target location pro le: TLP_CH
Language: German, French, Italian
Rating: Public
Validity area: REG_CH
When you create a new label set, you must provide a target location and a language.
You can create target location pro les in Customizing activity De ne Target Location Pro les under Logistics - General
Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Labeling , where you can also assign a
default pro le for creating a label set.
6/17/2019
You can also de ne whether a target location is added to newly created label sets automatically, by prompt, or not at all, in this
Customizing activity. If you have chosen not to add any target locations automatically when creating new label sets, you can add
them later manually.
For label sets, the target location can have an in uence on the following data:
Display of the ingredient, qualitative data, and component list elements
Generated drafts of the given ingredient or qualitative data list
Statements and footnotes
Whenever you create a new target location, it must contain at least one language.
Labels that were created with no target location receive a default target location when you display or edit them in Recipe
Development in PLM Web UI. This default target location consists of an “empty” usage (no values for rating and validity area),
and the language of the label as speci ed on the Basic Data subview.
Activities
Creating new ingredient and qualitative data lists
The following data stays the same for one label set regardless of the target location:
Ingredient items
Ingredient list values
Position of ingredient items
The following can change according to target location:
Ingredient description and text for draft
Visibility of item for draft
Statements and footnotes
If there are already one or more target locations in the label set with corresponding ingredient and qualitative data, ingredient
and qualitative data content is created automatically when you add a new target location.
If there are several target locations in the label set, but no ingredient or qualitative data has been created yet, the content is
created for all existing target locations when you assign a data origin to the ingredient or qualitative label.
Statements
The following statement types exist on the label set:
Statements independent from target location
Statements for the whole label set (Label De nition Global De nition )
Statements for component label
Footnotes for data origin value declarations on the component list
Statements dependent on target location
6/17/2019
Statements for the ingredient or qualitative label
Footnotes for ingredient or qualitative list items
Where statements depend on the target location, you can de ne values for the target location itself and for the languages
assigned to the target location.
For statements independent from target location, you can de ne values for languages (in some cases indicating the target
location where they belong, for information purposes).
You can copy statements from one target location to another.
You can specify a purpose for statements, which indicates a special reason. For example, if the statement is Store in a cool, dry
place, then the statement purpose can be set as storage.
You de ne a statement purpose in Customizing activity Specify Statement Purpose under Logistics - General Product
Drafts
Label drafts can be generated from ingredient and qualitative data. The draft content depends on the target location of the
label set.
You can in uence the content of the generated draft by:
Assigning footnotes to list items by setting an item to be displayed in the draft
Specifying whether the proportion of an item is to be displayed for the ingredient label
De ning qualitative value declarations for the qualitative label
On the ingredient label, you can preview the draft name of an item in the Text for Draft column.
Further target location-dependent label features
XML export
PDF print preview
Component structure descriptions
Data origin description
Label set title
Ingredient list description
Features not dependent on target location
Label set description
Package list description
Package list long text
Authorization for Label Sets

Use
6/17/2019
In labeling in the PLM Web User Interface (Web UI), you can assign user authorizations to determine object access.
Prerequisites
You have made the necessary entries in Customizing activity Specify Authorization Groups under Logistics - General Product
Features
You can assign the following user roles relevant for labeling:
Label developer
Label reviewer
You can also control authorizations to label sets using access control management (ACM).
More Information
For more information about authorizations in labeling, see Authorizations.
For more information on ACM, see Authorizations and Access Control Context (PLM-WUI-APP-ACC) .
Product Labeling Process

Use
You use this process to create label sets based on speci cations in the PLM Web User Interface (Web UI). You can preview the
package label as a PDF-based print form, and export the print form or the label set as an XML le to an external system, where
you can, for example, create a print layout.
Prerequisites
You have made the necessary entries in the Customizing activities under Logistics - General Product Lifecycle
Management (PLM) PLM Web User Interface Recipe Development Labeling .
You have created the primary output speci cation in Speci cation Management (either in Environment, Health and
Safety, or in the PLM Web UI).
For more information, see Speci cation Management in EH&S, or Speci cation Management in the PLM Web UI.
You have created a recipe for this speci cation as primary output in Recipe Development (PLM-WUI-RCP). You cannot
create label sets for recipes created in Recipe Management (PLM-RM).
If you use nutrients as components and you want to calculate proportions of their recommended daily allowances (RDA),
you have to use an RDA pro le — containing data for nutrients only. You create this as a speci cation with speci cation
category substance and speci cation type RMSL_RDA.
You can make the following additional settings:
If you want to use a speci cation as the data origin for the ingredient label, you must have speci ed a value assignment
type for ingredient composition in Customizing activity Set Up Connection to Recipe Management in PLM-RM under
Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Labeling .
6/17/2019
If you are using nutrients and you want their quantities and recommended daily allowances to be rounded automatically
by the system, you can de ne rounding rules. The system calculates declared values according to these rules. For more
information, see Rounding Rules for Nutrients.
If you want to transfer calculated values as default values for values that are declared on the label, you can integrate the
Business Add-Ins (BAdIs) for rules accordingly. You can choose whether the system transfers the calculated values
automatically or use the pushbutton to transfer the values manually.
For more information, see Customizing for Labeling under Include BAdI Implementation for Rules.
Process
1. Create or open a label set.
You can edit the general data as follows:
Enter default values for the rating, validity, and data origin. The system offers these values as default when
it creates the label lists.
Create language-dependent label set descriptions.
Specify the usage (the rating with which the label set is valid and the area to which this rating applies).
Specify the classes and the characteristic values.
Assign footnotes and marketing statements to the label set that apply to the product as a whole on the
Global De nition subview. You can de ne these statements in Phrase Management.
You de ne the label content:
De ne the target locations on the Global De nition subview (see Customizing activity De ne Target
Location Pro les, under Logistics - General Product Lifecycle Management (PLM) PLM Web User
Interface Recipe Development Labeling ).
Create the different labels of the label set.
For more information, see:
Creating an Ingredient Label
Creating a Qualitative Label
Creating a Component Label
Assemble the nal label content on the package label.
For more information, see Creating a Package Label
2. You can preview the data in a PDF print layout on the package label (for settings, see Customizing activity De ne PDF
Forms, under Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
Development Labeling ).
Note
SAP delivers the PDF print form PLMU/UI_LBL_ADOBE_WUI. You can specify pre-de ned text modules to be
displayed on the print form by using phrases. You can do this in Customizing activity De ne PDF Forms, under
Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
Development Labeling .
3. Once you have completed processing, set the status For Release. (See Status Management.)
6/17/2019
Note
You can also set your own status scheme in the Customizing activity De ne Status Scheme, under Logistics - General
Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Status Management .
4. Release the label set.
Caution
You cannot change the data of a label set that has the status Released.
5. Export the data of the label set as an XML le.
You can export the complete label set or the content of a package size that you have speci ed. To do this, choose the
Export to XML link on either the Basic Data subview, or on the package label for a selected package size.
The structure of the XML le is de ned by the structure RMSLS_XML_LABEL.
Note
You can display or export the data at any time during processing.
6. If you do not want to use the label set any longer, set the status Obsolete.
Note
You cannot undo this status, and you can no longer edit the label set.
Creating an Ingredient Label

Use
You use this procedure to create an ingredient label as part of a label set.
Procedure
1. Create a label set (see Product Labeling Process).
2. Choose the Ingredient Label subview on the Label De nition main view, and choose Assign Data.
3. Select a data origin. You can use the following as the data origin:
The speci cation you entered when creating the label set.
All recipes created in the PLM Web UI that use this speci cation as primary output.
Note
Labeling in PLM Web UI can only create label sets for recipes created in Recipe Development (PLM-WUI-RCP).
After selecting a data origin, the content of the ingredient list is displayed with the corresponding calculated values for
each ingredient.
The following steps are optional for the ingredient label:
1. Generate language-dependent drafts for the label, and edit the data if needed.
6/17/2019
2. Add footnotes to the ingredient label. You can create footnotes in phrase management.
For more information, see Phrase Management (EHS-BD-PHR).
3. Edit the items in the list. You can choose from the following options:
Edit declared values
Create and delete declaration groups
Hide an item or its declared value from the draft
Sort the list
Explode ingredients to their components
De ne a hierarchy by using declaration groups
Copy target location-relevant settings from one target location to another
Undo and reset your list-related actions
Aggregate ingredients
To aggregate ingredients, select the relevant rows in the ingredient list and choose Aggregate.
Aggregation is possible if at least one of the following criteria is met:
The ingredients have the same speci cation
The ingredients have different speci cation descriptions, but the phrase assigned to them is the same
 Example
Different kinds of salt can exist in an ingredient list. Salt may be the same declared name for salt (coarse) and
salt ( ne). You can select both of these items and aggregate them below the item Salt. The system then adds
their quantities automatically.
Combine the quantity of ingredients fully or partially
To combine ingredients, select the items and choose Combine. A dialog box appears, where you set the name of
the newly created combined item and the percentages of the original items that are to be combined. The system
then creates the new item, calculates its quantity, and adjusts the quantities of the original items.
 Example
An ingredient list contains the items water and apple juice concentrate. You can combine these two items to
appear as apple juice.
Note
Since ingredient and qualitative data information is package-size-independent, it is only possible to create those types of
lists once. Since a label set contains multiple package sizes, and on one package you can have several sets of size-dependent
component information, these items are de ned more than once.
Creating a Qualitative Label

Use
6/17/2019
You use this procedure to create a qualitative label as part of a label set.
The qualitative data list on the qualitative label consists of the properties that are not measurable by numbers and units.
 Example
The qualitative label of a food industry label set can contain declared information on diet suitability (vegetarian), allergens
(nuts), religious certi cate compliance (kosher), and gene modi cations.
Procedure
1. Create a label set or open an existing one (see Product Labeling Process).
2. Choose the Qualitative Label subview on the Label De nition main view, and choose Assign Data.
3. Select a data origin and a group. You can use the following as the data origin:
The speci cation you entered when creating the label set
All recipes created in the PLM Web UI that use this speci cation as primary output
Note
Labeling in PLM Web UI can only create label sets for recipes created in Recipe Development (PLM-WUI-RCP).
The following steps are optional for the qualitative label:
Edit the values that are to be declared on the label
Insert additional items
Generate language-dependent drafts for the label, and edit the data if needed
Add statements and footnotes to the label. You can create them in Phrase Management.
Delete items from the list
Note
Creating a Component Label

Use
You use this procedure to create a component label as part of a label set.
The component list contains a structure that describes how many key constituents there are, and a list where they can be
de ned multiple times based on the quantity of the output. A de ned quantity can have multiple comparisons to standard value
sets, as a proportional value.
You can de ne a component structure template in the Customizing activity De ne Template for Component Structure under
Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Labeling (see
6/17/2019
De ning a Component Structure).
 Example
In the food industry, vitamins are usually shown as a xed set of elements. Vitamin C, for example, can be present in multiple
ingredients even within a single product like mixed fruit yoghurt, in strawberries, cranberries, and so on. In this case, Vitamin
C must be displayed independently from the ingredient, showing the product’s total quantity.
Prerequisites
There must be one component structure per label. The description can appear in different languages, or differently in the
same language, depending on the target location.
Procedure
1. Create a label set or open an existing one (see Product Labeling Process).
2. Choose the component label.
3. Choose component structure template and the items.
4. Choose Assign Data.
5. Select a data origin, a base quantity, and a group.
You can use the following data as the data origin:
The speci cation you entered when creating the label set
All recipes created in the PLM Web UI that use this speci cation as an input or an output
The system then transfers the data and calculates the corresponding values.
Note
If you choose a recipe as the data origin and you want to use the values calculated on the Nutrient Loss Calculation
tab, see the Customizing activity Set Up Connection to Recipe Development (PLM-WUI-RCP) under Labeling.
6. Assign RDA pro les to data origins if you are using nutrients as components. The RDA pro le contains the recommended
daily allowances (RDA) of nutrients expressed as a percentage.
The following steps are optional for the component label:
Edit the component structure
Edit the declared value and unit of measure
Assign statements to the items of the component list and footnotes to the declared values of the data origins. You can
create these in phrase management (see Phrase Management (EHS-BD-PHR)).
Add a descriptions for the component list items
Note
lists once. A label set contains multiple package sizes and on one package you can have multiple size-dependent component
information; therefore these items are de ned more than once.
6/17/2019
De ning a Component Structure

Use
The component structure describes the key constituents in the component list.
Prerequisites
You have de ned a component structure template in the Customizing activity De ne Template for Component Structure under
Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Labeling .
Procedure
By de ning a component structure, which is a list of speci cations with type Nutrient, there is no difference between the
structures of data origins and RDAs.
You have the following options when editing a component structure:
Adding single items (speci cations with type Nutrient)
Adding items from a group with type Nutrient
Adding items de ned as component structure template in Customizing
Changing the indentations and moving items up and down the component structure
You cannot add a single speci cation to a data origin, but if you want to add a new item, you can add it on the component
structure level. This also changes all data origins and RDAs.
If you specify a Statement, the Description column displays the phrase description of the speci cation in the selected language.
If you have not speci ed a Statement, the identi er of the entered speci cation is displayed, according to the selected language
and usage.
You can control whether or not the declared value of an item is shown in the nal output by selecting the Display checkbox. If
you have chosen not to display the item, you cannot edit it when a declared component value exists.
Creating a Package Label

Use
You use this procedure to create a package label as part of a label set.
Procedure
1. Create a label set or open an existing one.
2. Choose the package label and then choose Add.
3. Select a package size and a base quantity.
The following steps are optional for the package label:
6/17/2019
Edit language-dependent long texts
Add descriptions for each package size
Select the content to be displayed for each package size from the ingredient, qualitative and component items,
according to target location
Choose a PDF layout for print preview. (You can de ne PDF forms in the Customizing activity De ne PDF Forms under
Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Labeling .)
Generate a print preview
Note
Rounding Rules for Nutrients

If you use nutrients as components, you can de ne rounding rules for quantities or recommended daily allowances (RDA) of
nutrients in speci cation management in the PLM Web UI.
The system uses rounding rules when it determines the declared values for the component list from the calculated values.
The system uses the base unit of measure of the nutrient when rounding quantities, and rounds recommended daily allowances
as percentages.
If the system cannot determine any rounding rules or any valid rounding rules for a nutrient, it rounds the values as speci ed in
the Business Add-In (BAdI) BAdI: Data for Nutrition Label/Quantitative Component Label: Execute Rules; in the standard
system, this is to two decimal places. You also use this BAdI to specify how the rounding rules are de ned.
In the standard system, you de ne rounding rules by specifying the settings and the beginning of the intervals in which the
rounding rules are applied:
Intervals
You specify intervals that build on each other. The interval with the smallest value is the starting point from where
rounding is applied. Subsequent intervals specify sections in which the rounding rule might be de ned differently.
The last interval with the highest number is used for all numbers above the interval limit. The interval limit is de ned as
exact as four decimal places.
 Example
You have de ned three rounding rules. You have speci ed the lower limit as Limit1 and Limit2. The system evaluates
any calculated value to be rounded based on the following limits:
If the value is smaller than Limit1, no rounding is applied.
If the value is equal to or bigger than Limit1 and smaller than Limit2, the rounding de ned for Limit1 is applied.
If the value is equal to or bigger than Limit2, the rounding de ned for Limit2 is applied.
Settings for rounding rules
Round to the Nearest:
6/17/2019
The value of this eld de nes a stepping in which results are calculated.
 Example
Round to the nearest is 5.
If the calculated value is 4, it is rounded up to 5. If the value is 7, it is rounded down to 5.
Round to the nearest is 0.2.
If the calculated value is 8.15, it is rounded up to 8.2. If the value is 7.91, it is rounded down to 8.0.
Declared Value and Declared Value Statement:
You can enter a xed numerical value, a phrase, or a combination of both, that is used for values of this interval.
 Example
You have set up a rounding rule as follows:
Interval From: 100.0001
Declared Value: 100.00
Declared Value Statement: More than
If the calculated value is 112.2456, then the returning value is 100.00 and the value statement is More than.
Do Not Display Item:
If this eld is selected, the result will be that the Display checkbox is not selected.
Engineering Change Management in

Labeling in PLM Web UI
Use
You can manage changes by assigning change numbers to label sets in labeling in the PLM Web UI.
Prerequisites
You have set the use of change numbers to mandatory in Customizing activity General Settings, under Logistics - General
Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Labeling .
Note
You can set change numbers to either mandatory or not allowed in Customizing. This setting is not reversible once you have
started creating label sets.
Features
Each label version within an alternative label can have one change number assigned.
6/17/2019
If you enable change numbering, the valid-from date of the change number becomes the key date of the label set. The valid-to
date then cannot be changed in the rst label version, since it is set to in nite. If you create another version, the valid-to date
becomes the valid-from date of the next version, minus one day.
Label sets are identi ed by a key made up of their product speci cation ID, alternative number, and version number. If you are
not using versions, the version number is automatically set to 000.
You can create several alternative label sets for a speci cation. For an alternative label set you have the option to create
several label versions. If you have selected not to use label versions in Customizing, each label set you create becomes a new
alternative label.
Each label version can have a status. For more information, see Status Scheme for Label Sets.
Status Scheme for Label Sets

Use
In the standard system, a simple status scheme is de ned for label sets that supports you in the release process.
Prerequisites
If you want to use your own status scheme, you can create it, as well as the corresponding activities in Customizing activity
De ne Status Scheme, under Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
Development Labeling Status and Action Management .
You then assign this scheme in Customizing activity General Settings under Logistics - General Product Lifecycle Management
(PLM) PLM Web User Interface Recipe Development Labeling .
Features
For the label set object, the following status attributes are available:
DELETION_ALLOWED: Label set can be marked for deletion
LOCKED_FOR_CHANGE: Label set is locked for changes
DOC_CHANGE_ALLOWED: Document change is allowed (see Documents)
The assignment of these attributes to a status in uences the kind of activities you can perform when a label set has that
particular status.
The status scheme contains the following statuses:
In Process
In this status, you can change label data and mark the label set for deletion.
For Release
You use this status to initiate the release process; the person responsible can check the label and change the status.
Caution
In the standard delivery, if the label set status is set to For Release, the following procedure is still possible in order to
change data:
6/17/2019
1. Open the label set and change the status to In Process.
2. Edit the label set.
3. Set the status back to For Release.
4. Save the label set.
With this procedure, you have changed the label set in the status For Release, without causing the status change to
be documented anywhere, for example in a change document.
To prevent this procedure, you have the following options:
Assign the authorizations in a way that no user has authorization for both status changes, from For Release to
In Process and back.
Implement the Business Add-In (BAdI) BAdI: Additional Checks Before Status Change in a way that the status
change from In Process to For Release is only possible if the data has been changed beforehand.
Released
You use this status to release the label set for further external processing. You cannot change released labels, you can
only set them to status Obsolete.
Obsolete
You use this status to lock a label temporarily, and switch from the status Released. You can mark a label with this status
for deletion or change it.
The following table displays the standard attribute assignments to standard statuses.
Status Status Attributes
In Process Can be marked for deletion
For Release Is locked for changes
Released Is locked for changes
Obsolete
Can be marked for deletion
Is locked for changes
Status Scheme for Label Sets
Classi cation in Recipe Development

6/17/2019
Use
You can use classi cation to group objects according to your selected criteria, by assigning similar objects to the same class and
by assigning speci c values to the class characteristics. Based on the classes and their characteristics, you can then search for
recipes, for example.
You can classify the following objects in Recipe Development:
Recipe
Process parameters (characteristics only)
Equipment requirements
Label
Prerequisites
You have created the required classes in the classi cation, with the following class types and associated characteristics:
Object Type Class Type
Recipe 104 Recipe
Process Parameters 105 Process Parameters
Equipment Requirement 019 Work Center Class
Label 103 Label Valuation
You can also use a class hierarchy.
More Information
Classi cation (CA-CL)
Classi cation on the Web UI
WWI Reports
Use
You can use Windows Wordprocessor Integration (WWI) reports to output data and graphic symbols from speci cations, label
sets, and recipes in Recipe Development in PLM Web User Interface (Web UI).
Prerequisites
You have made the necessary entries in the Customizing activities under Logistics - General Product Lifecycle Management
(PLM) PLM Web User Interface Recipe Development Reporting .
Features
Displaying Reports
6/17/2019
For speci cations and recipes, you can use the PLM Web UI to display released reports that you create, manage and release in
Environment, Health and Safety (EH&S). You can nd the relevant EH&S transactions in the SAP Easy Access menu under
Environment, Health and Safety Basic Data and Tools Report De nition .
To display a selected report in the PLM Web UI, you rst need to maintain the object keys, that is, the parameter values
assigned to the report. You can then open the report in Microsoft Word, or save it to a selected location.
Reports are listed according to the generation variants used to create them, however, only released reports are included. For
more information, see Generation Variant Editing.
Creating New Reports
To create new reports for recipes and display them in the PLM Web UI, rst you need to request report creation in EH&S. After
veri cation, an entitled EH&S user can release the newly created reports.
You can also create ad-hoc reports for speci cations and recipes, for information purposes. These reports are not designed for
official processes, that is, they cannot be veri ed and released. Ad-hoc reports are based on templates (generation variants),
and are generated regardless of the mode you are working in (such as edit, create, or display).
To create an ad-hoc report, choose Ad-Hoc Report from the Additional Functions menu. The system then displays the ad-hoc
report in Microsoft Word, according to the generation variant you have selected.
Displaying Report Information
You can display administrative data about the selected report for both recipes and speci cations, including:
Header data
Status log
Report body storage
More Information
For more information about creating and releasing reports in EH&S, see Report Creation: Process.
Windows Wordprocessor Integration in

Recipes
Use
You can use the Windows Wordprocessor Integration (WWI) from Environment, Health and Safety (EH&S) to create and view
reports in Recipe Development in PLM Web User Interface (Web UI).
Based on your selection, the system can show reports in Windows Word for the following data:
Basic data of a recipe
All formula item data as available on the Formula view
The following process data:
Process elements
6/17/2019
Assigned formula items
Process parameters
Process parameters assigned to equipment requirements
Recipe descriptions (language independent)
Documents assigned to the recipe
Classi cation data (classes and characteristic values), assigned to the following items:
Recipe
Process parameters
Calculation parameters
Calculation results for the following items:
Listed compositions (scienti c ingredients, composition)
Grouped compositions (allergens, diets, genetically modi ed ingredients, nutrients, religious certi cate
compliance)
Costs
Explosion by scienti c ingredients
Features
The delivered report symbols and repeating groups for WWI Reporting in Recipe Development also support following scenarios:
Use customized report templates. To de ne these templates, make the relevant entries in the separate Customizing
activities for speci cations and recipes under Logistics - General Product Lifecycle Management (PLM) PLM Web User
Interface Recipe Development Reporting .
Do nested reporting of process elements of the following types:
stage
operation
action
Do nested reporting of the assigned process parameters, equipment requirements, and formula items per process
element, using repeating groups.
Do nested reporting of formula items and the related recipe, where the item’s speci cation is the primary output
speci cation.
Navigate from an item's speci cation into a related recipe.
Print WWI reports.
More Information
Report De nition (EHS-BD-RDF)
6/17/2019
Windows Wordprocessor Integration (WWI)
Symbol
Repeating Groups
Compliance Check in Recipe Development

Use
You can use compliance check in Recipe Development to check whether a product complies with certain constraints. These can
be, for example, legal constraints or constraints laid down by an enterprise. You can use compliance check for all substances for
which a speci cation or recipe has been created.
In the standard Recipe Development system, you can de ne different types of constraints in substances, such as nutrients
(quantitative), or diets, allergens, genetically modi ed ingredients, and religious certi cate compliance (qualitative). Then you
can check whether the substance, speci cation, or recipe complies with these constraints.
Compliance check can be run in two operating modes, as follows:
With EH&S Expert Server
If you choose this option, the compliance check uses the EH&S Expert (see EH&S Expert), for which you need speci c
settings, see Speci c Settings for Compliance Check with EH&S Expert Server.
Choose this operating mode if you want to de ne your own compliance rules.
Without EH&S Expert Server
If you choose this option, the compliance check does not need an external server; it runs within PLM and on the same
system. For more information, see Speci c Settings for Compliance Check without EH&S Expert Server.
The advantage of this operating mode is that it may improve the performance of the compliance check.
Features
In Recipe Development, you can access compliance check from your personal object worklist within the Recipe Work Center and
the Speci cation Work Center, as well as from the Object Navigator.
With compliance check, you have the following options:
Mass check
You can select one or more substances or recipes. When you perform the check for recipes, the system can check the
corresponding primary outputs or recipe composition.
Individual check
You can call an individual check from the speci cation or from recipe application. If you start the individual check from
recipe, the system checks the primary output speci cation of the recipe, or the recipe composition (there is a selection
for data origin).
More Information
Running the Compliance Check in Recipe Development
6/17/2019
Constraints
De nition
Constraints are properties of a speci cation for a substance or substance group, which specify what the substance or substance
group must be composed of to comply with certain regulations.
The two operating modes differ slightly in connection with constraints, as follows:
Compliance Check with EH&S Expert Server
You de ne constraints or value assignment types as classes in the system. For more information, see Customizing for
Recipe Development under Compliance Check Compliance Check with EH&S Expert Server Set Up Compliance Check
for Recipe Development .
Compliance Check without EH&S Expert Server
In standard delivery, there are seven constraints de ned. See Customizing for Recipe Development under Compliance
Check Compliance Check without EH&S Expert Server Assign Value Assignment Types to Constraints .
If you want to use additional constraints, see Customizing for Recipe Development under Compliance
Check Compliance Check without EH&S Expert Server Business Add-Ins (BAdIs) Example: Create New Constraint .
Structure
The following constraint types are available for the compliance check in the standard Recipe Development system:
Substance excluded: A product is not allowed to contain this substance
Restricted: The concentration of a substance in a product is not allowed to exceed a certain limit value. The system
calculates the total concentration of all instances of the substance in the composition.
Required: A certain concentration of the substance must be present in the product. If the concentration exceeds a
certain level, this may be stated on the label, for example, “Contains aspartame”.
Depending on the constraint type, you can de ne properties of the constraints as characteristics for the relevant value
assignment type. These properties include:
The legislation from which the regulation originates
A limit or value for constraint types with a minimum or maximum quantity
A statement that is to be issued if the constraint is complied with as a result of the check, such as “Kosher”, or if it is not
complied with, for example, “Not suitable for consumption”.
Other lter criteria, such as the application area, for example, “Oral Hygiene Products”
More Information
Substance with Constraints
Maintaining Constraints

6/17/2019
De nition
In the compliance check in Recipe Development, you can assign individual substances with constraints or a substance group
with constraints (speci cation type CCK_GRP).
Substance groups with constraints comprise multiple substances of the same substance type. Constraints that are assigned to
the substance group refer to the group as a whole, even though the individual substances in the group can have different
weightings.
 Example
You can de ne a substance group with constraints that contains certain substances and assign an appropriate constraint to
that group. For example, if more than 10% of a product is made up of a combination of the substances sorbitol (E420),
mannitol (E421), isomalt (E953), maltitol (E965), lactitol (E966), and xylitol (E967), the packaging must display the
information “Excessive consumption may have a laxative effect” as the result of the check.
Structure
You can assign constraints to the following substance types in the compliance check in Recipe Development:
Allergens (speci cation type ALLERGEN)
Diet (speci cation type DIET)
Genetically modi ed ingredients (speci cation type GENMOD)
Listed substance (speci cation type LIST_SUB)
Nutrient (speci cation type NUTRIENT)
Religious certi cate compliance (speci cation type RELIGIOUS)
To assign a constraint to a substance, call the substance in the speci cation and switch to the property tree de ned for the
compliance check. Select the required constraint type and specify the properties.
Caution
Technically, it is possible to de ne constraints in real substances but we do not recommend this because the system only
checks real substances at the lowest explosion level. If a real substance with constraints is used at a level in between, the
system cannot take it into account. The compliance check can then produce incorrect results.
Substance Group with Constraints
You use a substance group with constraints to group multiple substances together and assign a constraint to them. You can
group together multiple substances of the same speci cation type and give them weightings.
You can create substance groups with constraints for the following substance types in the compliance check in Recipe
Development:
Listed substance (speci cation type LIST_SUB)
Nutrient (speci cation type NUTRIENT)
In the compliance check, the system takes every substance in the substance group into account according to its weighting.
6/17/2019
Create a speci cation of the speci cation type substance group with constraints (CCK_GRP). Specify the substances in the
substance group with constraints property in the property tree de ned for the compliance check, and give the substances
weightings. Then specify the constraints for them.
Note
You cannot use substance groups with the speci cation types listed substance group (LIST_GRP), nutrient group
(NUTR_GROUP), or diet group (DIET_GROUP) from Recipe Development for the compliance check.
If you use compliance check without EH&S Expert server and do not use substance groups, you can choose not to check them in
Customizing for Recipe Development under Compliance Check Compliance Check without EH&S Expert Server Additional
Settings . This may result in a performance increase.
In speci cation management, you can display and maintain constraints in two ways.
Fast Constraint Maintenance (FCM) allows you to display and maintain the details of all types of constraints
simultaneously. You can do this for constraints assigned to all speci cations in relation to one application area and one
regulation.
 Example
You can use FCM to display or change the maximum amount of fat that various dairy substances may contain
according to the German Food Regulation.
The RM Compliance Check Property Tree in the Properties view of speci cation management allows you to display and
maintain the details of one type of constraint assigned to one speci cation in relation to any application area and
regulation selected.
 Example
You can use RM Compliance Check Property Tree to display or change the maximum amount of fat that milk may
contain according to various regulations.
Fast Constraint Maintenance

Use
This function enables you to display and maintain all constraints de ned for a selected application area and regulation.
Features
After selecting the application area and the regulation on the initial screen, you can use the following views to display or
maintain constraints in Fast Constraint Maintenance:
Substances
Constraints assigned to real and listed substances that belong to the standard composition of speci cations with the
selected regulation and application area. Possible types: restrictive, mandatory, or prohibitive.
Note
6/17/2019
Substance groups are not supported in Fast Constraint Maintenance.
Quantitative data
Constraints related to nutrient composition. Possible types: mandatory, restrictive, or prohibitive.
Qualitative data
Constraints related to diets, allergens, genetically modi ed ingredients and compliance with religious certi cates.
Possible types: qualitatively positive/negative declaration.
You can use these views to display the following characteristics:
Names and descriptions of speci cations
Types of the constraints
Limits for required or restrictive constraints assigned to substances or qualitative data
Exception values for constraints assigned to qualitative data
Positive and negative statements expressing the constraints (you can assign more than one statements to each
constraint)
Usages for the constraints (you can assign more than one usages to each constraint)
Status of change (an icon showing whether a constraint was updated successfully or if the update failed; as well as an
icon showing if an object is locked or not modi ed)
More Information
Compliance Check in Recipe Development
Constraints
Running the Compliance Check in Recipe

Development
Use
You use this process to check whether a substance complies with certain constraints. You can perform the compliance check on
individual or multiple speci cations and recipes.
Prerequisites
You have made all the required settings in the Customizing for Compliance Check in Recipe Development Compliance
Check
The recipe or speci cation, for which you want to run the compliance check, must exist
6/17/2019
You have the correct authorization to run the compliance check, that is, you have the authorization to display and change
a recipe or speci cation (see Authorizations)
Process
You can access the compliance check from your personal object worklist in the recipe work center or the speci cation work
center.
Note
You can perform individual compliance checks from the recipe and speci cation work centers, while you can perform both
individual or mass compliance checks from your personal object worklist as well as from the Enterprise Search results.
Individual Compliance Checks:
1. From either the main Change Recipe / Display Recipe screen or the main Change Speci cation / Display Speci cation
screen, choose Additional Functions Start Compliance Check
2. A separate window opens, which contains the input parameters for the compliance check.
The header for a recipe contains the following information:
Recipe
Recipe description
Recipe type
Recipe status
Recipe purpose
The header for a speci cation contains the following information:
Speci cation
Category
Type
Authorization group
The General Settings contain the following information:
Data Origin, the setting selected here indicates whether the compliance check is run for a recipe or a
speci cation
Note
In the case of a recipe, the data origin can either be recipe or the primary output of a speci cation.
Rating, the setting selected here together with the validity area make up the usage of the standard composition
Validity Area, the setting selected here together with the rating makes up the usage of the standard composition
The Constraint Selection comprises the following:
Composition Types
Parameters for Constraint Validity
6/17/2019
Usage of Constraint
Note
The selection of settings here are de ne in the Customizing for Compliance Check in Recipe Development.
For more information about the input parameters, see Save As Default and Variants.
3. Once you have made your desired settings, you can run the compliance check either by choosing Next or Run in the
Background.
Note
If you chose Next, the Check Results screen is displayed. You must then choose Save Result in order to save the
compliance check results to the database. If you chose Run in the Background, the results are automatically saved to
the database. In either case, the compliance check is given a unique ID, such as
Compliance check 000000000000101, which is displayed at the top of the screen.
4. To view the compliance check results, navigate to the Display Compliance Check Results screen. Enter the unique ID for
the compliance check, and choose Continue. If you are not sure of the ID, choose F4 and search for the compliance check
results using the following criteria:
Compliance Check ID
Results Status
Created By
Speci cation
Date and Time From
Date and Time To
Data Origin
Note
For detailed information about the compliance check results, see Displaying the Compliance Check Results
5. You can export and preview the details of the compliance check results and input parameters in Adobe PDF format.
Choose Print to display the print preview.
Note
You have to save the compliance check before you can use the Print function.
Mass Compliance Checks
You can perform mass compliance checks from your personal object worklist as well as from the Enterprise Search:
From your personal object worklist, select multiple objects and choose Compliance Check. The Mass Compliance Check
screen is displayed. Proceed as mentioned above.
From the Enterprise Search search results, select multiple objects and choose Additional Functions Start Compliance
Check . The Mass Compliance check screen is displayed. Proceed as mentioned above.
More Information
6/17/2019
Save As Default
Variants
Displaying the Compliance Check Results
Speci c Settings for Compliance Check with EH&S Expert Server
Speci c Settings for Compliance Check without EH&S Expert Server
Save As Default
Use
When you are on the Compliance Check (Input Parameters) screen, you can save the input parameters that you have selected
as the default entries for that speci c recipe or speci cation.
These default parameters are attached to the recipe or the speci cation itself. They are not user-speci c entries. That is, the
parameters that were saved as default will be preselected regardless of who runs a compliance check next on that same recipe
or speci cation.
If desired, you can change the parameter entries before you run the check. The default selection is not affected; — unless you
save them as default again.
Integration
When you are running a mass compliance check on a recipe or speci cation, and you save the input parameters as default,
these default parameters will be displayed for each individual recipe or speci cation. However, the default parameters will not
be saved for the next mass compliance check.
 Example
You run a mass compliance check on Recipe A, Recipe B, and Recipe C, and save your input parameters as default. The next
time Recipe A is called up (individually) for a compliance check, the input parameters will be preselected. However, if you run
a mass compliance check on Recipe A, Recipe B, and Recipe C again, the input parameters will not be preselected.
Activities
From the Compliance Check (Input Parameters) screen, select from the following input parameters:
Rating
Validity Area
Constraint Selection
Usage of Constraint
Then choose Save as Default. Con rm your selection in the dialog box displayed.
Note
6/17/2019
The only parameter that you cannot save as default is the Data Origin.
More Information
Variants
Variants
Use
When you are on the Compliance Check (Input Parameters) screen, you can save your selection of input parameters as a
variant. Unlike the function Save as Default, the variant you save is not attached to the recipe or speci cation itself. Instead,
you are de ning a speci c selection of constraints, which can be reused by anyone with any recipe or speci cation.
Integration
Once you have saved a variant, you can directly run the compliance check using a variant for any recipe or speci cation.
If you are displaying or changing a recipe or speci cation, choose Additional Functions Start Compliance Check with Variants .
Select one or more variants, and choose OK. The compliance check will be run for the recipe or speci cation with those speci c
input parameters that were de ned for the variant.
A dialog box will be displayed with the overall compliance check results. Choose the unique ID of the compliance check results to
view the Display Compliance Check Results screen.
Note
If you are running the compliance check with variants for a recipe, the data origin will be always Recipe. Where as, if you run
a standard compliance check (without variants) for a recipe, you have the option of setting the data origin to either Recipe
or Speci cation.
You can access the Compliance Check with Variants function from the Object Navigator for either recipe or speci cation by
choosing
Additional Functions Start Compliance Check with Variants
You can also access the Compliance Check with Variants function from the Enterprise Search Hitlist by choosing Additional
Functions Start Compliance Check with Variants .
Note
If you are using the Enterprise Search for either recipe or speci cation, you can select multiple recipes or speci cations as
well as multiple variants.
Activities
To save your variants, from the Compliance Check (Input Parameters) screen, select from the following input parameters:
Rating
Validity Area
6/17/2019
Constraint Selection
Usage of Constraint
Then choose Variants Save In the dialog box displayed, de ne the variant name as well as a short description. Now the variant
is saved, and can be reused at any time. Con rm your selection in the dialog box displayed.
Note
The only parameter that you cannot save is the Data Origin.
To delete a variant, from the Compliance Check (Input Parameters) screen, choose Variants Delete . This will delete the
variant completely from the list of Variant Parameters.
If you are already in the Compliance Check (Input Parameters) screen, you can also load an existing variant, by choosing
Variants Load .
More Information
Save As Default
Compliance Check for Quantitative

Composition Types
Use
If you have selected the Use indicator for the composition types Composition or Nutrients on the Compliance Check (Input
Parameters) screen, the system checks whether the recipes comply with the constraints de ned for the selected composition
type.
Features
If you select one or more of the quantitatively-relevant composition types, the compliance check checks all the substances in
the composition to determine the suitability of the recipe. It only takes values without storage loss into account.
The following constraint types are de ned for the quantitatively-relevant composition types in the standard system:
Substance excluded
The compliance check checks whether the proportion of the substance with constraints in the substance composition is
greater than zero. If this is the case for one substance, the result of the check for the relevant constraint is "
Result Not OK".
 Example
According to the "German Cosmetic Ordinance", a nished product is not allowed to contain benzene.
However, benzene can be used as an auxiliary substance during production, provided that it can be completely
removed afterwards.
Products that contain boric acid must carry the label "Do not use on children under the age of three".
6/17/2019
For substance groups with constraints, the system checks whether the weighted total of the substance group in the
composition of the product is greater than zero.
Restricted
The compliance check checks whether the proportion of the substance with constraints in the substance composition
exceeds the limit value speci ed in the constraint. If this is the case for one substance, the result of the check for the
relevant constraint is "Result Not OK".
 Example
Nail strengthener is only allowed to contain 5% formaldehyde.
composition of the product exceeds the limit value.
Required
The compliance check checks whether the proportion of the substance with constraints in the substance composition
falls below the limit value speci ed in the constraint. If this is the case for one substance, the result of the check for the
relevant constraint is "Result Not OK".
 Example
A product must contain a minimum quantity of preservatives to guarantee a minimum shelf life.
Orange juice must consist of at least 55% fruit.
If a product contains more than 2% ammonia, this must be stated on the label.
composition of the product falls below the limit value.
Compliance Check for Qualitative

Composition Types
Use
If you select the Use indicator for the composition types Allergens, Diets, Genetically Modi ed Ingredients, or Religious
Certi cate Compliance on the Compliance Check (Input Parameters) screen, the system checks whether the selected
qualitatively relevant compositions of the product comply with the de ned constraints.
Features
The source of the compliance check is the qualitative calculation of the recipe or the qualitative composition properties from
the speci cation of the product.
For qualitative components, the suitability is maintained as an exception value, such as

“Yes”, “No”, “Suited for”, “Not assessed”, or “Unknown”. A qualitative constraint is de ned by specifying the
set of suitable exception values that are allowed for the corresponding qualitative declaration in the product.
The following constraint types are de ned for the qualitatively-relevant composition types in the standard system:
Positive Constraint for Qualitative Component Declaration (Qualitatively Positive Check)

6/17/2019
The compliance check checks whether the qualitative components contained in the product have the exception values
speci ed in the constraint. If this is the case, the result of the check is “Result is OK”.
 Example
A qualitatively positive constraint with the exception value “ Vegetarian, Suited for Vegetarian” is de ned
in the speci cation of the qualitative substance (Diet) Vegetarian. The result of a check on the product Tofu Burger is
“ Result is OK” since its qualitative component Vegetarian contains the exception value “
Suited for Vegetarian”.
Negative Constraint for Qualitative Component Declaration (Qualitatively Negative Check)
The compliance check checks whether the qualitative component contained in the product do not have the exception
value speci ed in the constraint. If this is the case, the result of the check for the relevant constraint is
"Result Not OK".
 Example
A constraint with the qualitative exception values ” Yes” and “ Unknown” is de ned in the speci cation of the
qualitative component (Allergen) Nut. The result of the check for product Cheesecake is “ Result OK” because it
has “ No” as exception value for its allergenic component Nut.
Displaying the Compliance Check Results

Use
The Display Compliance Check Results screen allows you to view the detailed information about the compliance check, such as
the components and constraint types of the speci cation or recipe for which the compliance check was executed.
From the Display Compliance Check Results screen, you can display the application log, the input parameters that were used,
as well as the technical parameters that were de ned for running the check. You can also print the results of the compliance
check.
From the Compliance Check Results table, you can navigate directly back to the recipe or speci cation in question.
Features
The compliance check results are displayed in a table, or hierarchical tree, consisting of three levels:
The rst level, or root, contains the name of the speci cation or recipe. If there are multiple objects (in case of mass
compliance check), the tree list contains multiple root entries.
The second level contains the components of the speci cation or recipe.
The third level contains the detailed results of the constraint types (such as restricted or mandatory) and the application
area/regulation/usage combinations, with the overrun factors if there are any, for the listed constraint.
You can navigate through the result tree using the Previous and Next buttons.
Note
The Previous and Next buttons function at the third level. That is, you navigate from one constraint type to the next
constraint type.
6/17/2019
The result list shows three possible statuses:
OK (green)
Not OK (red)
Warning (yellow) — only in compliance check without EH&S Expert server
This status shows the components without maintained constraints.
You can use the Show/Hide Details buttons to control the visibility of the details area. The name of the selected object is also
displayed in this area of the screen.
You can see the following details:
The status and the compliance statement for the selected row in the tree.
The usages assigned to the selected constraint (level three) in the tree, such as the rating description, the description of
the validity area category, and the validity area description.
Note
If there is no constraint selected, this tab is inactive.
The parameters for constraint validity assigned to the selected constraint (level three) in the tree.
Note
If there is no constraint selected, this tab is inactive.
The application log contains the following information about each compliance check run:
Error messages
Warning messages
Information messages
Status messages
The input parameters are the parameters that were selected for the compliance check, such as the following:
Data origin
Rating
Validity area
Composition types
Usage of the constraints
The technical parameters are de ned in Customizing for Compliance Check, under Recipe Development Compliance Check .
Activities
To view the compliance check results, navigate to the Display Compliance Check Results screen. Enter the unique ID for the
compliance check, and choose Continue, or choose F4 and search for the compliance check results using the following criteria:
6/17/2019
Compliance Check ID
Results Status
Created By
Speci cation
Date and Time From
Date and Time To
Data Origin
Once you are displaying the results of a compliance check, you can choose the following functions:
Print
Application Log
Input Parameters
Technical Parameters
More Information
If you are using compliance check with EH&S Expert server, see Technical Parameters.
If you are using compliance check without EH&S Expert server, see Speci c Settings for Compliance Check without EH&S Expert
Server.
Speci c Settings for Compliance Check with

EH&S Expert Server
Use
This compliance check operating mode uses the EH&S Expert, for which you have to create a set of rules with the corresponding
mapping tables.
You can set this operating mode in Customizing for Recipe Development under Recipe Development Compliance
Check Compliance Check Operating Mode Selection .
More Information
See the Customizing activities for Compliance Check under Recipe Development Compliance Check Compliance Check with
EH&S Expert Server .
EH&S Expert
Set of Rules
Mapping Tables
6/17/2019
Set of Rules for the Compliance Check in

Recipe Development
De nition
The EH&S Expert requires a set of rules to perform the compliance check in Recipe Development. (For more information, see
the documentation for EH&S Expert under Set of Rules.)
Note
To be able to use the set of rules supplied by SAP for the compliance check in Recipe Development, proceed as described in
the Customizing for Recipe Development under Recipe Development Compliance Check Set Up Set of Rules .
The sections that follow here describe the properties of the set of rules.
Structure
System Prerequisites for Using the Set of Rules
The diet composition of a product always contains all diet substances that exist in the system.
The nutrient composition of a product always contains all nutrients that exist in the system.
All speci cations of a substance group with constraints have the same speci cation type.
The parameter table I_TABPARAMS of EH&S Expert contains the following data:
Parameter values for selecting constraints with the pre x FI_
Parameter values of the composition with the pre x AD_
Composition types stored in the result of the check with the pre x CT_
Key date stored in the result of the check with the parameter ID KEY_DATE_EXT
The compliance check can only take active usages into account. Therefore, when values are assigned to the constraints,
the Active indicator must be selected for the usages that are speci ed in the parameters for the compliance check, for
all substances with constraints to be checked.
Basic Settings in the Set of Rules
The following composition types are de ned in the phrase mapping table:
ALL (Allergen composition)
CMD (Composition)
DIET (Diet composition)
GMOD (Genetically modi ed ingredients)
NUTR (Nutrient composition)
REL (Religious certi cate compliance)
The following constraint types are de ned in the phrase mapping table:
6/17/2019
PROH (Prohibited)
REST (Restricted)
COMP (Required)
QPOS (Qualitatively positive)
QNEG (Qualitatively negative)
In the record mapping table, constraints are de ned by the following value assignment types:
SAP_RMS_CC_C_PROH (Constraint type "Prohibited" for listed substances and nutrients)
SAP_RMS_CC_C_RST_L (Constraint type "Restricted" for listed substances)
SAP_RMS_CC_C_RST_N (Constraint type "Restricted" for quantitative components)
SAP_RMS_CC_C_CMP_L (Constraint type "Required" for listed substances)
SAP_RMS_CC_C_CMP_N (Constraint type "Required" for quantitative components)
SAP_RMS_CC_C_QPOS (Constraint type "Qualitatively positive" for qualitative components)
SAP_RMS_CC_C_QNEG (Constraint type "Qualitatively negative" for qualitative components)
The result of the check is de ned by the value assignment type SAP_RMS_CC_RESULT in the record mapping table.
The following statuses of the result of the compliance check are de ned in the phrase mapping table:
01 (Result OK)
02 (Result not OK)
03 (Error in check)
The following parameters for constraint validity and selection are de ned as facts in the set of rules:
APPLICATION_AREA
REGULATION
The following data in the composition mapping table is provided by the relevant remote-enabled function modules:
Composition of the product (function module EHSB_RC02_EXPL_LIST_GET)
List of the substances with constraints that are relevant to the compliance check (function module
EHSB_RC02_REG_SUBST_GET)
List of the substance groups with constraints that are relevant to the compliance check including the
corresponding compositions of substances with constraints (function module
EHSB_RC02_GROUP_REG_SUBST_GET)
List of the units of measurement with conversion factors that are relevant to the compliance check (function
module EHSB_RC02_UNIT_CONV_GET)
List of the exception values that trigger an error (function module RMSC200_EXCEPTION_VALUES)
List of the exception values that trigger a warning (function module RMSC200_EXCEPTION_VALUES)
Recipe-Development-speci c information about the speci cation to be checked, for example, the ID of the recipe
(function module RMSC200_GET_RMIDS).
Determining the Composition
6/17/2019
The set of rules determines the composition of the product from a table in the EHSBS_RC_EXPLBUF structure. The system
takes only the following table elds into account:
RECN (Internal substance ID)
COMPTYPE (Composition type)
UNIT (Unit of measure)
ECVAL (Exception value)
COMPTGT_FLT (Proportion of substance in composition)
Taking Exception Values into Account
In Recipe Development, exception values are de ned for the items of a composition, for example, where the quantity cannot be
clearly determined.
In composition mapping, the tables g_excvals_warning and g_excvals_error contain the exception values for which the
compliance check writes a warning or error message to the application log.
Adjustments to the Set of Rules for

Enhancements
De ning Additional Composition Types
The composition types allergens (ALL), substance composition (CMD), diet composition (DIET), genetically modi ed
ingredients (GMOD), nutrient composition (NUTR), and religious certi cate compliance (REL) are de ned in the standard
system and con gured in the set of rules. If you want to use additional composition types in a similar way to CMD, you have to
make the following adjustments to the set of rules:
In the phrase mapping table (table ExpPhraseMap), create two new rows with the new composition type as the
external ID. Enter [#COMPTYPE_COMP#] in the rst row as the internal ID and enter the external ID again in the second
row. In the rst row, enter /READTHIS in the Options column. (For more information, see Phrase Mapping.)
The system assigns substances with constraints that are not contained in the explosion result to the composition type which
has the option /WRITETHIS assigned to it in fact mapping. It does this in the detailed result. If you want the newly-de ned
composition type to be assigned to these substances with constraints in the detailed result instead of the composition type
CMD that is used in the standard system, make the following changes in the Options column:
Change the entry in the row with the internal ID [#COMPTYPE_COMP#] and the external ID CMD to /READTHIS.
Change the entry in the row with the internal ID [#COMPTYPE_COMP#] and the external ID of the new composition type
to /READTHIS/WRITETHIS.
Additional Parameters for the Constraint Validity of Constraint Types

This set of rules allows you to use up to three additional parameters for the constraint validity of constraint types.
The entries with the following external IDs (table ExpFactMap) are supplied in fact mapping for this purpose:
N:FILTER3
6/17/2019
N:FILTER4
N:FILTER5
Enter the relevant characteristic in the form M:<characteristic key > (for example, M:SAP_RMS_CC_FILTER3) instead.
Technical Parameters
Use
When you are on the Compliance Check (Input Parameters) screen, you can display the technical parameters used by the
EH&S Expert, which de ne how the compliance check is run. These settings are made in Customizing for Compliance Check in
Recipe Development Compliance Check .
Activities
From the Compliance Check (Input Parameters) screen, choose Technical Parameters. A dialog box is displayed showing the
following parameters:
Data Origin
Data Provider
RFC Destination
Set of Rules
Note
If you have sufficient authorization, you can change the parameters in the Technical Parameters dialog box. The system will
use this selection for the individual compliance check run; this will not changes the settings made Customizing.
Mapping Tables for Compliance Check in

Recipe Development
In the standard system, the set of rules for the compliance check in Recipe Development contains the following mapping tables:
Phrase mapping
The phrase mapping table contains the regulations for mapping phrase codes used in the set of rules to phrase keys in
EH&S. Phrase mapping is also used in the set of rules for the compliance check to de ne constant values, for example,
the values for the status of the result of the check.
Composition mapping
The composition mapping table contains the regulations for mapping compositions in the set of rules to value
assignment types of the category composition in EH&S. Composition mapping is also used in the set of rules for the
compliance check to transfer multiple data records of the same type to the set of rules, for example, the list of exception
values which trigger an error.
Fact mapping
6/17/2019
The fact mapping table contains the regulations for mapping facts in the set of rules to characteristics or other elements
in the EH&S data model.
Record mapping
The record mapping table contains the regulations for mapping records in the set of rules to value assignment types in
EH&S.
The sections that follow contain the most important information about the structure and content of these tables.
Note
For more information, see Mapping Table in the EH&S Expert documentation.
Phrase Mapping
EH&S Expert uses the entries de ned in the phrase mapping table (table ExpPhraseMap) to convert the external values into
internal keys that are used in the code of the set of rules. The system converts these keys back to external values when it
returns the results to the compliance check.
The following table provides a list of the composition and constraint types used in the compliance check for Recipe
Development:
Internal ID External ID Options Description
[#COMPTYPE_QUAL_POSNEG#] ALL /READTHIS Composition type ALL
[#COMPTYPE_COMP#] CMD /READTHIS/WRITETHIS Composition type CMD
[#COMPTYPE_DIET#] DIET /READTHIS Composition type DIET
[#COMPTYPE_QUAL_POSNEG#] GMOD /READTHIS Composition type GMOD
[#COMPTYPE_NUTRIENT#] NUTR /READTHIS Composition type NUTRIENT
[#COMPTYPE_QUAL_POSNEG#] REL /READTHIS Composition type REL
[#CONSTR_TYPE_COMPULS#] COMP Constraint type Required
[#CONSTR_TYPE_PROH#] PROH Constraint type Prohibited
[#CONSTR_TYPE_QUAL_NEG#] QNEG Constraint type

Qualitatively negative
[#CONSTR_TYPE_QUAL_POS#] QPOS Constraint type

Qualitatively positive
[#CONSTR_TYPE_RESTR#] REST Constraint type Restricted
[#STATUS_COMPLIANT#] 01 Result of check Result OK
[#STATUS_ERROR#] 02 Result of check

Error in Check
[#STATUS_NOT_COMPLIANT#] 03 Result of check

Result Not OK
ALL Composition type ALL

(additional entry, technical
requirement)
6/17/2019
Internal ID External ID Options Description
CMD Composition type CMD

requirement)
DIET Composition type DIET

requirement)
GMOD Composition type GMOD

requirement)
NUTR Composition type NUTRIENT

requirement)
REL Composition type REL

requirement)
Note
For more information, see Phrase Mapping in the EH&S Expert documentation.
Composition Mapping
Composition mapping (table ExpGroupMap) contains the following tables that are lled by the speci ed remote-enabled
function modules when they are called:
Internal ID (Table) External ID (Function Module and Table) Options Descriptio
g_excvals_error FCT:RMSC200_EXCEPTION_VALUES; List of

TAB:ET_EXCEPTION_VALUES_ERROR exception
values tha
trigger err
messages
g_excvals_warning FCT:RMSC200_EXCEPTION_VALUES; List of

TAB:ET_EXCEPTION_VALUES_WARNING exception
values tha
trigger
warning
messages
g_explosion_result FCT:EHSB_RC02_EXPL_LIST_GET; /RECNCMP=RECN Explosion

TAB:ET_EXPLOSION result
g_recipe_information FCT:RMSC200_GET_RMIDS;TAB:ET_RECIPE Additional

informatio
about reci
from Recip
Developm
6/17/2019
Internal ID (Table) External ID (Function Module and Table) Options Descriptio
g_subst_group_members FCT:EHSB_RC02_GROUP_REG_SUBST_GET; /RECNCMP=RECNSUB Substance

TAB:ET_GROUP_SUB with
constraint
the
substance
groups wit
constraint
g_subst_groups_with_constr FCT:EHSB_RC02_GROUP_REG_SUBST_GET; Substance

TAB:ET_GROUP_SUB groups wit
constraint
g_subst_with_constr FCT:EHSB_RC02_REG_SUBST_GET;TAB:ET_SUBSTANCE /RECNCMP=RECN All

substance
with
constraint
g_units_of_measurement FCT:EHSB_RC02_UNIT_CONV_GET;TAB:ET_UNITS /RECNCMP=RECN Conversio

table for
units of
measurem
Note
For more information, see Composition Mapping in the EH&S Expert documentation.
Parameters in Fact Mapping

The following tables contain the parameters used in fact mapping (table ExpFactMap):
Table of exception values (table g_excvals_error) that trigger an error message along with the speci cation type for
which the exception values are de ned:
External ID (Table Field) Internal ID (Input Fact) Description
C:COMPEXCVAL i_message_excval Exception value
C:SUBCAT i_message_subcat Speci cation type for which the

exception value triggers an error
Table of exception values (table g_excvals_warning) that trigger a warning message along with the speci cation
type for which the exception values are de ned:
C:COMPEXCVAL i_message_excval Exception value
C:SUBCAT i_message_subcat Speci cation type for which the

exception value triggers a warning
message
Table of additional information (table g_recipe_information) from Recipe Development:

6/17/2019
C:RECIPE i_recipe_id Recipe ID
C:STAGE i_stage_number Stage
C:INDEP_STAGE i_indep_stage Independent stage
C:PROCESS i_process Process
Table of units of measurement (table g_units_of_measurement) that contains the dimension and conversion factor
for the standard unit of measurement of the dimension for each unit of measurement used:
C:MSEHI i_unit Unit of measurement
C:DIMD i_dimension Dimension that belongs to unit of

measurement
C:CONVERSION_FACTOR i_conv_fact Conversion factor of the unit of

measurement in relation to the standard
unit of measurement
Note
For more information, see Fact Mapping in the EH&S Expert documentation.
Input Data in Fact and Record Mapping

The following tables contain the input data for the speci cation to be checked and the components in fact mapping (see Fact
Mapping) and record mapping (see Record Mapping):
Input Data for Speci cation to Be Checked
General Information
External ID Internal ID Description
P:I_TAB_PARAMS i_params Parameter from table I_TAB_PARAMS
H:SUBID s_customer_key Speci cation key of the speci cation to be

checked (only used for messages and log
les)
Explosion result
The system takes the explosion result from the corresponding function module with the table elds named below. The
system determines the nutrient base unit from the speci cation database for the substances with constraints contained
in the explosion result.
Table g_explosion_result
External ID Internal ID (Input Fact) Description
H:SUBID i_comp_subid Speci cation key
6/17/2019
C:COMPTYPE i_comp_comptype Composition type (as technical key)
C:COMPTYPE i_comp_comptype_phrase Composition type (converted to

corresponding internal key by phrase
mapping)
H:SUBCAT i_comp_subcat Speci cation type
C:COMPTGT_FLT i_comp_value Value
C:UNIT i_comp_unit Unit of measurement for value
C:EXCVAL i_comp_excval Exception value
M:SAP_RMS_1011_001_VALUE; i_comp_base_unit_nutr Base unit of measure of nutrient

SAP_RMS_1011_001
Substances with constraints
The system writes the substances with constraints that it determines based on the parameters that were speci ed for
selecting constraints to the table g_subst_with_constr using the function module.
Table g_subst_with_constr
H:SUBID i_subst_subid Speci cation key of substance with

constraints
Substance groups with constraints
The table g_subst_groups_with_constr contains all substances with constraints with the corresponding
substance group. To improve performance and reduce the number of times tables are accessed, the system reads
substance groups with constraints in denormalized form, that is, it summarizes the data from all relevant tables in this
one table.
Table g_subst_groups_with_constr
H:SUBID i_group_subid Speci cation key of substance group with

constraints
C:SUBIDSUB i_subst_subid Speci cation key of substance with

constraints
C:WEIGHTING_FACTOR i_subst_weight_fact Weighting factor of substance with

constraints in substance group
M:SAP_RMS_1011_001_VALUE; i_comp_base_unit_nutr Base unit of measure of nutrient

SAP_RMS_1011_001
Substances with constraints in substance groups with constraints
If you want to use the data for the substances with constraints in the substance groups with constraints, you have to call
the function module a second time. The system reads the speci cation types for these components to ensure that all
substances in a substance group have the same speci cation type.
6/17/2019
Table g_subst_group_members
C:SUBIDCMP i_group_subid Speci cation key of substance group with

constraints
H:SUBID i_subst_subid Speci cation key of substance with

H:SUBCAT i_subst_subcat Speci cation type of substance with

Input Data for Components

Constraints of the constraint type "Prohibited" (value assignment type SAP_RMS_CC_C_PROH; internal compositions
g_explosion_result, g_subst_with_constr, g_subst_groups_with_constr)
Record r_constr_proh
External ID (Characteristics and Usage) Internal ID (Input Fact) Description
M:SAP_RMS_CC_FILTER_REG i_constr_filter_1 Parameter for constraint validity no. 1
M:SAP_RMS_CC_FILTER_APPL i_constr_filter_2 Parameter for constraint validity no. 2
N:FILTER3 i_constr_filter_3 Parameter for constraint validity no. 3
M:SAP_RMS_CC_STATEMENT_POS i_pos_statement Positive statement of constraint
M:SAP_RMS_CC_STATEMENT_NEG i_neg_statement Negative statement of constraint (not for

g_subst_with_constr)
U:VACLID,RVLID i_constr_usage Usage of constraint
Constraints of the constraint type "Restricted" for listed substances (value assignment type SAP_RMS_CC_C_RST_L;
internal compositions g_explosion_result, g_subst_with_constr, g_subst_groups_with_constr)
Record r_constr_restr_subst
M_ SAP_RMS_CC_REGLIMIT_NO_UNIT i_constr_limit_subst Limit value de ned in the constraint (not for

6/17/2019
M:SAP_RMS_CC_STATEMENT_NEG i_neg_statement Negative statement of constraint (not for

Constraints of the constraint type "Restricted" for quantitative components (value assignment type
SAP_RMS_CC_C_RST_N; internal compositions g_explosion_result, g_subst_with_constr,
g_subst_groups_with_constr)
Record r_constr_restr_nutr
M_ SAP_RMS_CC_REGLIMIT_NO_UNIT i_constr_limit_nutr Limit value de ned in the constraint
M:SAP_RMS_CC_STATEMENT_NEG i_neg_statement Negative statement of constraint
Constraints of the constraint type "Required" for listed substances (value assignment type SAP_RMS_CC_C_CMP_L;
internal compositions g_explosion_result, g_subst_with_constr, g_subst_groups_with_constr)
Record r_constr_compuls_subst
M_ SAP_RMS_CC_REGLIMIT_UNIT_PORP i_constr_limit_subst Limit value de ned in the constraint (not for

M:SAP_RMS_CC_STATEMENT_POS i_pos_statement Positive statement of constraint (not for

Constraints of the constraint type "Required" for quantitative components (value assignment type
SAP_RMS_CC_C_CMP_N; internal compositions g_explosion_result, g_subst_groups_with_constr)
6/17/2019
Record r_constr_compuls_nutr
M_ SAP_RMS_CC_REGLIMIT_NO_UNIT i_constr_limit_nutr Limit value de ned in the constraint
Constraints of the constraint type "Qualitatively positive" for qualitative components (value assignment type
SAP_RMS_CC_C_QPOS; internal composition g_explosion_result)
Record r_constr_qual_pos
External ID (Characteristics and Usage) Internal ID Description
(Input Fact)
M_ SAP_RMS_CC_EXCVAL i_constr_excval Exception value of constraint
Constraints of the constraint type "Qualitatively negative" for qualitative components (value assignment type
SAP_RMS_CC_C_QNEG; internal composition g_explosion_result)
Record r_constr_qual_neg
6/17/2019
M_ SAP_RMS_CC_EXCVAL i_constr_excval Exception value of constraint
Speci c Settings for Compliance Check

without EH&S Expert Server
Use
This compliance check operating mode does not need an external server, however, it has some restrictions:
You can only de ne new rules by implementing Business Add-Ins (BAdIs)
Inherited characteristic values cannot be checked
You can select this operating mode in Customizing for Recipe Development under Recipe Development Compliance
Check Compliance Check Operating Mode Selection .
Activities
The following features are only available in compliance check without EH&S Expert server after the relevant Customizing is set:
Turn off the green light for result OK completely or partially
Show yellow light for not maintained constraints
Exclude substance groups from the check
Exclude non-grouped diets and nutrients from the check
Show added columns on the result list view: Limit for Constraint % and Component Quantity %
You can nd the settings for these features in Customizing for Compliance Check, under Recipe Development Compliance
Check Compliance Check without EH&S Expert Server Additional Settings or you can directly change the settings on the
result view with the Technical Parameters button.
More Information
See Customizing activities for Compliance Check under Recipe Development Compliance Check Compliance Check without
EH&S Expert Server .

Recipe Dev

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Recipe Dev

Caricato da

Copyright:

Formati disponibili

6/17/2019

Recipe Development (PLM-WUI-RCP)

SAP ERP | 6.18.11

For more information, please visit the SAP Help Portal.

Ingredient label (see Creating an Ingredient Label)

Qualitative label (see Creating a Qualitative Label)

Component label (see Creating a Component Label)

You can perform the following activities using label sets:

Edit label data in Labeling, preview it as a PDF form, or export it as an XML le

Generate WWI reports (see WWI Reports)

Document on the Web UI

Additional features for Labeling

Change Document Application for Label Sets (SAP Note 1987190 )

Ad-Hoc WWI Reports for Label Sets (SAP Note 1968394 )

Target location pro le: TLP_CH

Language: German, French, Italian

Validity area: REG_CH

Display of the ingredient, qualitative data, and component list elements

Generated drafts of the given ingredient or qualitative data list

Statements and footnotes

Ingredient list values

Position of ingredient items

The following can change according to target location:

Ingredient description and text for draft

Visibility of item for draft

Statements and footnotes

The following statement types exist on the label set:

Statements independent from target location

Statements for component label

Footnotes for data origin value declarations on the component list

Statements dependent on target location

Footnotes for ingredient or qualitative list items

You can copy statements from one target location to another.

You can in uence the content of the generated draft by:

Assigning footnotes to list items by setting an item to be displayed in the draft

De ning qualitative value declarations for the qualitative label

Further target location-dependent label features

PDF print preview

Component structure descriptions

Data origin description

Label set title

Ingredient list description

Features not dependent on target location

Label set description

Package list description

Package list long text

Authorization for Label Sets

Product Labeling Process

You can make the following additional settings:

You can edit the general data as follows:

Create language-dependent label set descriptions.

Specify the classes and the characteristic values.

You de ne the label content:

Create the diﬀerent labels of the label set.

For more information, see:

Creating an Ingredient Label

Creating a Qualitative Label

Creating a Component Label

Assemble the nal label content on the package label.

For more information, see Creating a Package Label

4. Release the label set.

5. Export the data of the label set as an XML le.