Recipe Development - Doc 1

3/31/2019
Recipe Development (PLM-WUI-RCP)

Generated on: 2019-03-31
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
3/31/2019
Recipe Development (PLM-WUI-RCP)

Use
Recipe Development (PLM-WUI-RCP) contains the following functions:
Status Management
In status management, you de ne status pro les in Customizing that contain all available statuses and status
transitions.
Note
This function is object-speci c, so depending on the object type (speci cation, recipe, label set, and so on) you have
to set different Customizing activities.
Web-based user interface with fast entry for speci cation management in Environment, Health and Safety (EH&S) (see
Speci cation Management (EHS-BD-SPE))
In speci cation management you create speci cations, for example, for the input and output substances used in the
recipe.
Web-Based Recipe Development
Here you manage the recipes that comprise of all the information about the production process for a product, as well as
the input and output substances and packaging used in that process. You can also edit formula data for multiple recipes
simultaneously.
Web-Based Labeling
Here you create and manage label sets that you can use, for example, to create print templates for labels.
Creation of reports for recipes, label sets, and speci cations using Windows Wordprocessor Integration (WWI)
Creation of building blocks as prede ned, independent, and reusable objects that can act as templates for recipes, or
parts of recipes, see Building Blocks
Compliance check for speci cations and recipes
Mass changes for recipes and speci cations
Grouping of objects into object sets, see Object Sets
Caution
If you have used non-Web-based Recipe Management (PLM-RM) up to now, you can no longer use the recipes managed
there in Web-based Recipe Development (PLM-WUI-RCP), because the underlying databases are different.
To migrate the formulas and recipes from Recipe Management (PLM-RM) to Recipe Development (PLM-WUI-RCP), you can
use the transaction/PLMI/RCP_MIGRATION Recipe Development - Migrate Formula and Recipe. For more information, see
the documentation for report /PLMI/RCP_MIGRATION and SAP Note 1511580 .
Integration
Recipe Development is integrated in the following applications:
Web User Interface of SAP Product Lifecycle Management (PLM-WUI) (PLM Web UI)
3/31/2019
This contains the following general functions that you can also use for Recipe Development:
Search (see Search)
Work center and control center (see Control Center and Work Center: Overview)
Authorization concept (see Authorizations and Access Control Context (PLM-WUI-APP-ACC) )
Guided Structure Synchronization (see Guided Structure Synchronization (PLM-WUI-GSS) )
The PLM Web UI contains Web-based interfaces for managing the following objects, which you also require for Recipe
Development:
Material master (see Material Master (LO-MD-MM) and Material on the Web UI)
Material BOM (see BOMs (PP-BD-BOM) and Material BOM on the Web UI)
Documents (see Document Management and Document on the Web UI)
Change number, engineering record, and process route (see Engineering Change Management (LO-ECH) and
Engineering Change Management on the Web User Interface (UI))
Classes and characteristics from classi cation (see Classi cation (CA-CL) and Classi cation on the Web UI)
Embedded search
Object Navigator
The object navigator displays information about recipes, speci cations, and labels as well as all linked objects, for
example ones from Portfolio and Project Management.
You can also navigate to any linked object from here.
Authorizations
Use
You can de ne authorizations for individual applications within the Recipe Development (PLM-WUI-RCP) component, by means
of authorization roles (PFCG roles), authorization objects, and authorization groups.
Caution
You are only allowed to use authorization roles as a demo role with demo users in the test system. If a demo role contains
the wildcard "*" (asterisk) for parameters, you must not use the demo role in the productive system, because this grants too
many authorizations to users there. After copying this role to a productive system, you must thoroughly check each
authorization parameter containing an asterisk before you use it. For productive use, we strongly recommend that you build
new roles using the authorization default values from the transaction Maintain the Assignments of Authorization Objects
(SU22), rather than using the demo roles as a starting point.
Integration
In Recipe Development, you can use access control management (ACM) on the PLM Web User Interface for recipes, label sets,
and speci cations (see Authorizations and Access Control Context (PLM-WUI-APP-AC) ).
Using ACM, you can assign objects to access control contexts. For every context, you use context roles and access control lists
to de ne access rights for users or user groups.
3/31/2019
For using ACM, the PLM Web User Interface (PLM Web UI) comes delivered with sample composite roles that contain a central
context role de nition, and the necessary additional single roles that were de ned with the Role Maintenance (PFCG)
transaction. The following sample composite roles for ACM have been de ned for Recipe Development:
SAP_PLMWUI_DEMO_RCP_DEVEL4_RM (see Recipe Developer (for Pilot Implementation))
SAP_PLMWUI_DEMO_RCP_REVIEW4_RM (see Recipe Reviewer (for Pilot Implementation))
These roles contain all necessary authorization roles and authorization objects.
Caution
You can only use these roles as copy template for your own roles; you cannot use them directly in the productive system,
since the sample composite roles contain very general authorizations.
Features
Authorization Roles and Authorization Objects
The following table lists the single authorization roles required for each of the applications in Recipe Development, which you
can use as template for your own roles. If no authorization role is available, the required authorization object is speci ed.
Note
Sample roles are likewise available for further master data objects in Recipe Development, such as materials, material
BOMs, or documents.
Application Associated Authorization Roles or Authorization Object
Status Management Authorization object PLM_SAM PLM Authorizations for Status Management
Speci cation Management on the Web UI Authorization Roles:
SAP_PLMWUI_SPEC_ADD_AUTH Auxiliary Role for Speci cation Management
SAP_PLMWUI_SPEC_DISPLAY Display Speci cation
SAP_PLMWUI_SPEC_FES_SAMPLE Access to Speci cation Fast Entry Screen

Variant
SAP_PLMWUI_SPEC_MAINTAIN Maintain Speci cation
Recipe Development (Display Authorization Roles:

Authorization)
SAP_PLMWUI_RECIPE_DISPLAY Recipe Reviewer
SAP_PLMWUI_SPEC_DISPLAY Display Speci cation
3/31/2019
Application Associated Authorization Roles or Authorization Object
Recipe Development (Change Authorization Roles:

Authorization)
SAP_PLMWUI_RECIPE_MAINTAIN Recipe Developer
If you want to assign different authorizations for formula developers and process
developers, you can copy this role and change it accordingly (see Different
Authorizations for Formula Developers and Process Developers).
SAP_PLMWUI_SPEC_MAINTAIN Maintain Speci cation
SAP_PLMWUI_BB_MAINTAIN Recipe Developer (Building Blocks)
Synchronization Recipe to Manufacturing Authorization Role SAP_PLMWUI_RECIPE_H2M Recipe Synchronization Planner

BOM
Synchronization Recipe to Master Recipe Authorization Object PLM_GSSR2M PLM Authorization Object for Recipe to Master Recipe
Synch. — This object is added to the SAP_PLMWUI_RECIPE_H2M Recipe Synchronization
Planner role
Simulation Authorization Object PLM_RCPMDL Authorization Object for Recipe Simulation
Migration of Recipes from Recipe Authorization Roles:

Management (PLM-RM)
SAP_PLMWUI_RECIPE_MIGR_DISPLAY Display Migration of Recipe
SAP_PLMWUI_RECIPE_MIGRATION Recipe Migration
Mass Change of Recipes Authorization Role SAP_PLMWUI_MASS_CHANGE Role for Mass Change
Labeling Authorization Roles:
SAP_PLMWUI_LABEL_DISPLAY Label Reviewer
SAP_PLMWUI_LABEL_MAINTAIN Label Developer
Compliance Check Authorization Object C_EHSB_REG Authorization Check for Compliance Check
Download Data Authorization Role SAP_PLMWUI_DOWNLOAD_DATA Download Data Administrator
Recipe Archiving There is no separate authorization object for recipe archiving, authorization object
S_ARCHIVE controls if transaction SARA can be run.
Object Sets Authorization Roles:
SAP_PLMWUI_OBJECT_SET Object Set User
SAP_PLMWUI_OBJECT_SET_ADMIN Object Set Administrator
Authorization Groups
Using authorization groups, you can de ne user groups that are authorized to work with these objects. To be able to use an
authorization group for objects, a speci cation type must be assigned to the authorization group, even if the object itself is not
a speci cation. In Recipe Development, you use the following speci cation types for this purpose:
For recipes, RECIPE_WUI
For labels, LABEL_WUI
For speci cations, the associated speci cation type, for example SUBSTANCE
3/31/2019
You de ne authorization groups in Customizing for Recipe Development under Recipe Specify Authorization Groups . You can
also select the speci cation category there.
You can use authorization groups in combination with Access Control Management (ACM). For example, you can use
authorization groups for statistical calculations that re ect the general organizational structure of your company, and you can
use the access control management to assign authorizations dynamically.
You can use the same or different authorization groups for speci cations and recipes. If you use the same authorization groups,
you only have to create one authorization group in Customizing and then assign it to both speci cation categories.
Authorizations for Recipe-Dependent Master Data
Even if you have sufficient authorization for a recipe, it may be the case that you do not have the necessary authorization for its
master data objects. You can display and work on such a recipe in a restricted manner, but you cannot delete it.
The system behaves as follows, depending on which object you do not have authorization for:
If you do not have authorization for the primary output speci cation, you cannot call up the recipe.
If you do not have authorization for the change number assigned to the recipe, you can display the recipe but not
process it.
If you do not have authorization for the objects used in the formula (speci cations, materials, or recipes), the system
does not display any data in the Formula, Process Calculation Results views, and you cannot execute any of the
associated functions.
If you do not have authorization for the property speci cation, the corresponding eld in the General Data view is empty,
and you cannot execute any of the associated functions (see Property Speci cation).
If you do not have authorization for a recipe determined during explosion, the system stops the explosion on this level
and uses the data of the speci cation (see Explosion).
Different Authorizations for Formula

Developers and Process Developers
You can use the authorization object PLM_RCPTAB ( eld ID for Recipe View /PLMB/RCPT) to control whether a user receives
authorization to display and change only formula data ( eld value Formula FORMULA) or process data ( eld value Process
PROCESS).
Generally, the following rules apply:
The process developer can never access the Formula view and he or she cannot assign process elements to formula
items and cannot create streams.
Similarly, a formula developer cannot access the Process view and he or she cannot change process data.
However, there are exceptions to this rule, if the recipe type allows the use of streams in the recipe (see Streams). In this case,
the formula developer must also be able to process the process stages in which these streams are created or consumed.
Therefore, in a recipe with such a recipe type, the formula developer can also access the Process view and he or she can create
process stages in this view to which he or she can then assign streams. However, he or she cannot create or change operations
or actions.
The Process view is always visible for recipes with streams, even if the recipe type does not even allow processes. In this case,
however, only process stages can be used, and not operations or actions.
3/31/2019
The following table provides an overview of the different options:
Recipe Type Allows Process Recipe Type Allows Streams Formula Developer Process Developer
Yes No
Formula view visible Formula view not
visible
Process view not
visible Process view visible
No No
Formula view not
visible
Process view not

visible
Yes Yes
Formula view visible Formula view not
visible
Process view visible
Process view visible
Process stages can be
created and changed in
No Yes the Process view (no
Formula view not
other process elements)
visible
Assignment of process
Process view is visible
stages to formula items
is possible Process stages can be
created and changed in
the Process view (no
other process elements)
Recipe Developer (for Pilot Implementation)

SAP_PLMWUI_DEMO_RCP_DEVEL4_RM
Use
Recipe Reviewer (for Pilot Implementation)

SAP_PLMWUI_DEMO_RCP_REVIEW4_RM
Use
The purpose of this role is to enable a user to display objects in Recipe Development in the PLM Web UI.
The role is suited especially for use in pilot implementations.
Caution
This role should be used as a demo role with demo users only. A demo role must not be used in a production system in case it
contains wildcards “*” (asterisks) for parameters, which might grant too many authorizations to users. After copying this
role to a production system, each authorization parameter containing an asterisk must be thoroughly checked before use.
3/31/2019
For production use, we strongly recommend that you build brand new roles using the authorization default values from
transaction SU22, rather than using the demo roles as a starting point.
Recipe Developer (Building Blocks)

SAP_PLMWUI_BB_MAINTAIN
Use
Caution
Auxiliary Role for Speci cation Management

SAP_PLMWUI_SPEC_ADD_AUTH
Use
This role grants additional authorizations for Speci cation Management in the PLM Web User Interface (PLM Web UI). Since it
is a supplement to the role Speci cation Management (SAP_EHS_SAF_SUBSTANCEDATA), they both need to be assigned to all
users of Recipe Development in PLM Web UI.
Caution
Display Speci cation

SAP_PLMWUI_SPEC_DISPLAY
Use
The purpose of this role is to provide all authorizations needed to display speci cations in the PLM Web UI.
Caution
3/31/2019
Activities
Typical activities for this role include displaying speci cations, change documents, reports, and so on.
Access to Speci cation Fast Entry Screen

Variant
SAP_PLMWUI_SPEC_FES_SAMPLE
Use
The purpose of this sample role is to allow users to de ne access to WebDynpro con guration variants on the Fast Entry Screen
(FES) of Speci cations in the PLM Web UI. You can specify the elements, the content and the appearance of the FES using these
con guration variants.
Through roles created according to this sample, you can assign con guration variants that are available to speci c users on the
FES initial screen.
Caution
Activities
To de ne such authorizations, note the following:
Maintain authorization object PLM_SPCFES.
Fill the authorization eld (WebDynpro variant) with single values.
You can maintain this authorization object twice or more with single values.
Maintain Speci cation

SAP_PLMWUI_SPEC_MAINTAIN
Use
3/31/2019
The purpose of this role is to provide all authorizations needed to maintain speci cations in the PLM Web UI.
Caution
Activities
Typical activities for this role include:
displaying change documents
changing and displaying reports
changing and displaying value assignment usage for speci cations and speci cation types
displaying phrase libraries and phrase groups
Recipe Reviewer
SAP_PLMWUI_RECIPE_DISPLAY
Use
Recipe reviewers have the authorization to display recipes in Recipe Development.
Note
The authorizations for this role are only complete if both of the following roles are also assigned to the user:
Speci cation Management (SAP_EHS_SAF_SUBSTANCEDATA)
Auxiliary Role for Speci cation Management (WUIAUTH_ROLES_SPEC_ADD_AUTH)
Caution
Recipe Developer
SAP_PLMWUI_RECIPE_MAINTAIN
3/31/2019
Use
Recipe developers have the authorization to perform all recipe-related activities (create, change, display, delete, print, and copy
recipes).
Note
The authorizations for this role are only complete if both of the following roles are also assigned to the user:
Speci cation Management (SAP_EHS_SAF_SUBSTANCEDATA)
Auxiliary Role for Speci cation Management (SAP_PLMWUI_SPEC_ADD_AUTH )
This role also controls authorization differences between formula developers, process developers and recipe developers using
authorization parameters.
For more information about how the system displays information for formula and process developers, see Different
Authorizations for Formula Developers and Process Developers.
Caution
Recipe Synchronization Planner

SAP_PLMWUI_RECIPE_H2M
Use
This sample role grants the user the authorization to plan the synchronization of recipes to bills of material (BOM) and recipes
to PP-PI master recipe. Recipe Synchronization Planners can create, change, display, and delete recipe to BOM and recipe to
master recipe synchronizations.
Note
The authorizations for this role are only complete if the user also has the role Recipe Reviewer
(SAP_PLMWUI_RECIPE_DISPLAY) assigned.
To execute synchronizations to create and change BOMs, the role Maintain BOM (SAP_PLMWUI_BOM_MAINTAIN) is also
needed.
Caution
3/31/2019
Role for Mass Change

SAP_PLMWUI_MASS_CHANGE
Use
Caution
Label Reviewer
SAP_PLMWUI_LABEL_DISPLAY
Use
The purpose of this sample role is to allow label reviewers to display product labels in Labeling in PLM Web User Interface.
Caution
Label Developer
SAP_PLMWUI_LABEL_MAINTAIN
Use
The task of a label developer is to create, change, display or delete product labels. This role grants the relevant authorizations
in Labeling in PLM Web UI.
Caution
3/31/2019
Download Data Administrator

SAP_PLMWUI_DOWNLOAD_DATA
Use
The purpose of this role is to enable users in Recipe Development to perform the following actions in the Download Data
function:
Delete the selection layouts of other users
Create, update, or delete standard selection layouts
Without this authorization, users can only create, update and delete their own custom selection layouts.
Caution
Object Set User

SAP_PLMWUI_OBJECT_SET
Use
The purpose of this role is to enable users to create and maintain their own object sets, and share object sets with other users.
For more information, see Object Sets.
Caution
Object Set Administrator

3/31/2019
SAP_PLMWUI_OBJECT_SET_ADMIN
Use
The purpose of this role is to enable users to maintain object sets even if they are not the owners of that object set. For more
information, see Object Sets.
Caution
Status Management
Use
In status management, you de ne status schemes that contain all available statuses and status transitions. As a result, you can
de ne a release process, for example.
Status management contains the following data:
All statuses available in the system
For each object type and status, the activities that are allowed for an object with this status, and the properties that the
object must have so that this status can be set
For each object type and status, whether the setting of the status affects other elds of the object (for example,
whether an input eld is locked)
Status schemes that de ne the initial status of an object type, all possible transitions between different statuses, as well
as the preconditions for these transitions
Note
This function is object-speci c so depending on the object type (speci cation, recipe, label, and so on) you have to perform
different Customizing activities.
Prerequisites
You de ne status schemes in Customizing for Recipe Development for the different object types as follows:
Recipes and building blocks: Recipe Development Recipe Status and Action Management
Speci cations: Recipe Development Speci cation Management Speci cation Speci cation Master Status
Management for Header Status
Labels: Recipe Development Labeling Status and Action Management
Example
3/31/2019
For more information, see:
Status Schemes for Recipes
Status Scheme for Building Blocks
Status Scheme for Label Sets
Header Status for Speci cations

Use
Status schemes support you during a release process. The following status schemes are de ned for recipes in the standard
system:
Simple status scheme
You use this status scheme if you only use the recipe in the development department, for example.
Status scheme with transfer from the development department to the production department
You use this status scheme if you transfer the recipe via the Guided Structure Synchronization to the production
department and want to create a manufacturing BOM from it.
Prerequisites
If you want to use your own status scheme, you have to edit the activities in Customizing for Recipe Development, under
Recipe Status and Action Management .
You enter this status scheme under Recipe De ne Recipe Types for the recipe types used by you.
Features
The following status attributes are available for recipes:
DELETION_ALLOWED: Recipe can be marked for deletion
LOCKED_FOR_CHANGE: Recipe is locked for all changes
CONSIST_EXPLOSION: Explosion-relevant recipe data is consistent and the recipe is locked for changes (see
Consistency Check)
REL_EXPLOSION: Recipe is relevant for explosion (see Explosion)
CONSIST_SYNC_BOM: Recipe data that is relevant for synchronization of the recipe with a manufacturing BOM is
consistent and the recipe is locked for changes (see Consistency Check)
REL_SYNC_BOM: Recipe is locked for all changes and relevant for synchronization with a manufacturing BOM. The recipe
data that is relevant for the synchronization of a recipe with a manufacturing BOM is consistent (see Synchronizing a
Recipe with a Manufacturing BOM).
DESC_CHANGE_ALLOWED: Description change is allowed
DOC_CHANGE_ALLOWED: Document change is allowed (see Documents)
3/31/2019
REL_SYNC_MRCP: Attribute for synchronization of recipe to master recipe (see Synchronizing a Recipe with a Master
Recipe)
REUSE_RESTRICTED: Reuse is restricted
Simple Status Scheme
This status scheme contains the following statuses:
In Process
In this status, you can change recipe data and mark a recipe for deletion. From here, you can switch to the For Release
status.
For Release
If you want to set this status, the consistency check checks whether the recipe is consistent for the explosion. Only then
can you set this status. The recipe is locked for changes as of this status.
You use this status to initiate the release process; the responsible recipe developer checks the recipe and changes the
status.
From this status, you can either switch back to the In Process status or switch to the Released status.
Caution
In the standard delivery, the following procedure is possible in one of the statuses For Release:
1. You open the recipe or label and set the status In Process.
2. You change data.
3. You set the status back to For Release.
4. Now you save the data.
With this procedure, you have changed the data in the status For Release, without causing the status change to be
documented anywhere, for example in a change document.
To prevent this, you have the following options:
You assign the authorizations in such a way that no user has authorization for both status changes, from For Release
to In Process and back.
You implement the Business Add-In (BAdI) BAdI: Additional Checks Before Status Change in such a way that the
status change from In Process to For Release is only possible if the data has been changed beforehand.
Released
The explosion-relevant recipe data is consistent and the recipe is locked for changes.
By setting this status, you transfer the recipe to production. In this status, a recipe is considered in the explosion. You
cannot change released recipes, you can only set them to status Obsolete.
Obsolete
By setting this status, you lock a recipe temporarily against usage, for example because it is only executed in a particular
season due to the availability of raw materials (such as the processing of fresh fruits). You can mark a recipe with this
3/31/2019
status for deletion, but you cannot change it, or create a recipe using an obsolete speci cation as the primary output.
From here, you can switch back to the For Release status.
The status attributes, displayed in the following table, are assigned to the status:
Status Status Attributes
In Process
Can be marked for deletion
For Release
Is locked for changes
Explosion-relevant data is consistent and can no longer be

changed
Released

changed
Is relevant for the explosion
Obsolete
Recipes with Status ʻReleased’
In case you have to change descriptions and long texts in a released recipe for translation reasons, you can still do that even
after an official work ow process has been performed.
When a recipe is released, meaning it has the status attribute LOCKED_FOR_CHANGE assigned, you cannot insert or modify its
document links in Document Management (transaction CV02N). This is also true for inserting or modifying multiple document
links; the action does not take place unless all entries are in a status that allows change.
Status Scheme with Transfer from the Development Department to the Production Department
In Process
In this status, you can change recipe data and mark a recipe for deletion.
3/31/2019
For Release (Development)
If you want to set this status, the consistency check checks whether the recipe is consistent for the explosion and for the
synchronization. Only then can you set this status. The recipe is locked for changes as of this status.
With this status, you can trigger the release process; the responsible recipe developer checks the recipe and transfers
the recipe to the production department by setting the status For Release (Production).
For Release (Production)
The production department checks the recipe before releasing it. In this status, a recipe is considered in the explosion.
With this status switch, you automatically change the recipe purpose from development to production (see Recipe
Purpose).
Caution
2. You change data.
Released for Production
By setting this status, you transfer the recipe to production. You cannot change released recipes, you can only set them
to status Obsolete.
Obsolete
season due to the availability of raw materials (such as the processing of fresh fruits). In this status, you can switch from
the status Released for Production. You can mark a recipe with this status for deletion, but you cannot change it.
In Process
3/31/2019


changed
Data that is relevant for synchronization of the recipe with a

manufacturing BOM is consistent and can no longer be
changed


changed

changed


changed
Is relevant for the synchronization of a recipe with a

manufacturing BOM
Obsolete
3/31/2019

Use
Status schemes support you during a release process.
Prerequisites
If you want to use your own status scheme, you have edit the activities in Customizing for Recipe Development, under
You enter this status scheme under Recipe Building Block De ne Building Block Types for the building block types used by
you.
Features
The following status attributes are available for building blocks:
DELETION_ALLOWED: Building block can be marked for deletion
LOCKED_FOR_CHANGE: Building block is locked for all changes
CONSIST_EXPLOSION: Explosion-relevant building block data is consistent and the building block is locked for changes
(see Consistency Check)
REL_EXPLOSION: Building block is relevant for explosion (see Explosion)
CONSIST_SYNC_BOM: Building block data that is relevant for synchronization of the building block with a manufacturing
BOM is consistent and the building block is locked for changes (see Consistency Check)
REL_SYNC_BOM: Building block is locked for all changes and relevant for synchronization with a manufacturing BOM. The
building block data that is relevant for the synchronization of a building block with a manufacturing BOM is consistent
(see Synchronizing a building block with a Manufacturing BOM).
SKIP_FORMULA_CHECK: Do not perform formula check
REUSE_RESTRICTED: Building block is restricted from being used further
Status Scheme
The status scheme for building blocks contains the following statuses:
In Process
In this status, you can change building block data and mark a building block for deletion. From here, you can switch to the
For Release status.
For Release
If you want to set this status, the consistency check checks whether the building block is consistent for the explosion.
Only then can you set this status. The building block is locked for changes as of this status.
3/31/2019
You use this status to initiate the release process; the responsible building block developer checks the building block and
changes the status.
Caution
2. You change data.
Released
The explosion-relevant building block data is consistent and the building block is locked for changes.
By setting this status, you transfer the building block to production. In this status, a building block is considered in the
explosion. You cannot change released building blocks, you can only set them to status Obsolete.
Obsolete
By setting this status, you lock a building block temporarily against usage, for example because it is only executed in a
particular season due to the availability of raw materials (such as the processing of fresh fruits). You can mark a building
block with this status for deletion, but you cannot change it. From here, you can switch back to the For Release status.
In Process
For Release

changed
3/31/2019
Released

changed
Obsolete
Note
You can set the building block's status to Released even without a valid formula.
Building Blocks with Status ʻReleased’
When a building block is released, meaning it has the status attribute LOCKED_FOR_CHANGE assigned, you cannot insert or
modify its document links in Document Management (transaction CV02N). This is also true for inserting or modifying multiple
document links; the action does not take place unless all entries are in a status that allows change.

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 .
3/31/2019
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
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:
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.
3/31/2019
In Process Can be marked for deletion
For Release Is locked for changes
Released Is locked for changes
Obsolete

Use
This function de nes the header status of a speci cation, handles status change with manual and automatic precondition
checks, and can lock a speci cation to prevent further editing.
You can check the current status of a speci cation in the following places:
The Personal Objects Worklist in the Speci cation Work Center
In the Identi cation Region (IDR) at the top of the speci cation main view
On the Header Status tab
You can search speci cations according to this parameter.
When you create a new speci cation, the system assigns an initial status to it automatically. For more information about the
initial status, see the Activities section.
Note
The header status for speci cations is also integrated into the CG02 (Substance Workbench) transaction but is intended for
use on the Web User Interface with full functionality.
The header status of speci cations uses the authorization object PLM_SAM and requires the authorization role
SAP_PLMWUI_STATUS_CHANGER. Only users with this authorization can change the header status of a speci cation.
The standard delivery contains two status schemes, which you can modify in Customizing, see the Activities section:
3/31/2019
Simple Header Status Scheme for Speci cation (PLM_RDSHS)
This scheme is set as default for all standard speci cation types. It contains only two statuses: Active and Obsolete.
Active
This is the initial status of this scheme. In this status, you can change speci cation data. You can switch to
Obsolete from here.
Obsolete
In this status, the speci cation becomes locked and cannot be edited, used in, or referred to from recipes,
speci cations, or building blocks.
When you set your speci cation to Obsolete, the system informs you about the number of objects affected by this
status change.
Caution
Use this status carefully, as you can switch to other statuses from here only with speci c authorization
controlled by the authorization object PLM_SAM.
Alternative Header Status Scheme for Speci cation (PLM_RDSH)
This scheme contains the following statuses:
In Process
This is the initial status of this scheme. In this status, you can change speci cation data. From here, you can
switch to For Release or Obsolete.
For Release
From here, you can either switch back to In Process or switch to Released.
Released
In this status, the speci cation becomes locked and cannot be edited. From here, you can switch to any other
status.
Obsolete
In this status, the speci cation becomes locked and cannot be edited or used in or referred to from recipes,
Caution
Use this status carefully, as you cannot switch to other statuses from here.
3/31/2019
Features
Speci cation statuses can have the following attributes:
LOCKED_FOR_CHANGE: A speci cation with this status cannot be edited. By default, this attribute is added to the
Released and Obsolete statuses.
OBSOLETE: A speci cation with this status cannot be used in or referred to from any recipes, speci cations, or building
blocks. By default, this attribute is added to the Obsolete status.
The header status scheme depends on the speci cation type. For example, you can set different status schemes for real
substances and nutrients. By default, all speci cations use the simple header status scheme.
You can also assign precondition checks to all status transitions. The following table summarizes the precondition checks for the
default statuses:
Status Precondition Description
For Release – –
Released CONSISTENT Object is consistent
NO_ACTIVE_RATING_STS All rating and validity areas are in released status
Obsolete NO_ACTIVE_INHERIT_TO There is no active inherit to relation
NO_ACTIVE_RCP_USG_AL Not used in active recipe
NO_ACTIVE_RCP_USG_IN Not used as input speci cation in active recipe
NO_ACTIVE_RCP_USG_PO Not used as primary output spec. in active recipe
NO_ACTIVE_RCP_USG_PS Not used as property speci cation in active recipe
NO_ACTIVE_RCP_USG_SO Not used as secondary output in active recipe
NO_ACTIVE_SPC_CMP_US Not used as composition in active speci cation
The NO_ACTIVE_RCP_USG_AL precondition check can be used instead of the following checks:
NO_ACTIVE_RCP_USG_IN
NO_ACTIVE_RCP_USG_PO
NO_ACTIVE_RCP_USG_PS
3/31/2019
NO_ACTIVE_RCP_USG_SO
NO_ACTIVE_SPC_CMP_US
The consistency check calls the Business Add-In BAdI: Check Consistency of Speci cation (/PLMI/SPC_CHCK_CONSIST). If the
checks in this BAdI fail then the status change is not possible. For more details, see Customizing for Recipe Development under
Logistics — General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Speci cation
Management Speci cation Business Add-Ins (BAdIs) BAdI: Consistency Check .
Activities
See Customizing for Speci cation Management under Logistics — General Product Lifecycle Management (PLM) PLM Web
User Interface Recipe Development Speci cation Management Speci cation Speci cation Master Status Management for
Header Status .
You can do the following in this Customizing node:
De ne Status Scheme — Create a new status scheme or modify the existing ones, create or modify statuses, add or
remove attributes.
BAdI: Settings for the Header Status View of Speci cations — Change the layout of the Header Status tab for
speci cations.
Change Header Status for Multiple Speci cations — De ne a set of existing speci cations and change their header
statuses based on a prede ned ruleset.
BAdI: Change of Header Status for Multiple Speci cations — This BAdI is used with the report Change Header Status
for Multiple Speci cations.
To activate the initial header status for newly created speci cations, see the documentation under Logistics —
General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Speci cation
Management Speci cation Business Add-Ins (BAdIs) Extended Checks for Speci cations Implementation: Initial Header
Status for Speci cations .
Speci cation Management

Use
On the PLM Web User Interface (Web UI) for speci cation management, you can create, change, and display the business object
speci cation for the substance, packaging and recipe properties speci cation categories. Speci cations are data objects that
use value assignments for physical and chemical data to de ne certain properties. For each speci cation structured data is
stored in property trees.
This business object is used by Recipe Development (PLM-WUI-RCP) and Environment, Health and Safety (EH&S).
Note
Speci cations belonging to the category recipe properties are created in Recipe Development, and they contain a property
tree to store recipe properties. These property speci cations are only available in combination with a recipe version. For
more information, see Property Speci cation.
With the help of object sets you can group any number and type of objects (for example recipes, speci cations, building blocks)
and organize them according to your needs. For more information, see Object Sets.
3/31/2019
Features
The Web UI for speci cation management displays the same data as the Substance Workbench (transaction CG02) in
Environment, Health and Safety (EH&S). However, the data may be grouped differently than in the Substance Workbench.
In speci cation management on the PLM Web UI, the following value assignment types are available for the diet suitability value
assignment category, which is speci c to Recipe Development:
Allergens
Compliance with religious certi cates
Genetically modi ed ingredients
You can now lter and sort table columns for properties. To do so, place the cursor on the column heading, click the small
triangle that appears in the bottom-right corner of the cell, and select the sort or lter options from the menu.
Status management for speci cations
There are two different status types for speci cations, as follows:
Header status, which is valid for the whole speci cation.
This is visible on the Header Status subtab of General Data, and the relevant statuses can be set in Customizing for
Recipe Development, under Speci cation Management Speci cation Speci cation Master Status Management for
Header Status .
For more information, see Header Status for Speci cations.
Status, where you can specify for which usages a speci cation’s identi ers and value assignment instances should be
protected.
This is visible on the Status subtab of General Data. You can set the relevant statuses in Customizing for Recipe
Development, under Speci cation Management Speci cation Speci cation Master Status Management for Validity
Areas .
For more information, see Speci cation Status.
Speci cations not used in Recipe Development
To search for speci cations that are not used in recipes within Recipe Development, run the Find Unused Speci cations
(/PLMI/RSP_FIND_UNUSED_SPECS) report.
Features supported by the Substance Workbench only
Creating and changing phrases, inheritance templates, and regulatory lists
Advanced management of hit lists (see Hit Lists)
Formatting of long texts
Displaying change documents
Creating and managing reports
Note
You can display released reports and create ad-hoc reports from templates. For more information, see WWI Reports.
Searching for characteristic values in characteristics

3/31/2019
Triggering of data exchange activities, such as Application Link Enabling (ALE)
Starting EH&S Expert activities
Process Route
You can use change management to de ne a process route, which you use to model a process and assign a processor to every
step. You can change this de ned process at any time (see Process Route).
More Information
Speci cation Management (EHS-BD-SPE)
Additional Features for Speci cations
To set up context-dependent value help for value assignments, see SAP Note 1607953 .
To trigger a SAP Business Work ow when saving speci cations, see SAP Note 1622635 .
To allow users to access change documents directly from the PLM Web UI for speci cations, see SAP Note 1963483 .
To enable document assignments to speci cations on header level, see SAP Note 1959682 .
General Data
Use
In the General Data view, you can see data related to the entire speci cation.
Prerequisites
You can specify whether subviews like Basic Data, Restrictions, and so on are displayed according to the speci cation type in
the Customizing activity De ne Subviews for General Data under Logistics - General Product Lifecycle Management
(PLM) PLM Web User Interface Recipe Development Speci cation Management Speci cation Speci cation Master .
If you want to use change numbers, you can set the change number usage according to the speci cation type in the
Customizing activity Set Change Number Usage for Creating Speci cations under Logistics - General Product Lifecycle
Management (PLM) PLM Web User Interface Recipe Development Speci cation Management Speci cation Speci cation
Master .
Features
In the standard system, the following subviews are available in the General Data view:
Basic Data
In this subview, you can see the speci cation's header data, validity, and administration information.
This subview also displays the owning context of the speci cation. For more information on Access Control Context, see
Impact of ACM on the Work with PLM Web UI.
Identi ers
In this subview, you can maintain identi ers and identi er usage information.
3/31/2019
You can also add a long text to an identi er with the following criteria:
If the text you entered is shorter than 132 characters, the text is stored as an identi er, and the identi er itself
remains editable.
If the text is longer than 132 characters, the identi er is read-only.
Identi ers from inherited speci cations and identi ers with a released usage are also read-only.
You can add default identi er types that you de ne according to the speci cation type in the Customizing activity De ne
Default Identi ers under Logistics - General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
Development Speci cation Management Speci cation Speci cation Master .
Restrictions
In this subview, you can display combinations of ratings and validity areas that control access to the speci cation, and
are assigned to the header data of a speci cation in EH&S.
SAP recommends using Access Control Management (ACM) instead of restrictions for Recipe Development.
For more information, see Restrictions.
Status
You can use this subview to edit the status of usages (rating and validity area). You cannot edit identi ers and value
assignments that have released usages. You can also view comprehensive administrative information that includes
change numbers for the displayed usages, as well as display their status history.
For more information, see Speci cation Status.
Material Assignments
In this subview, you can establish object links between speci cations and materials relevant for Recipe Development in
the SAP component Material Master (LO-MD-MM). This allows you to create a link to other logistics processes.
For more information, see Assignment of Speci cations and Materials.
Relationships
This subview displays information about inheritance. You can create inheritance relationships using inheritance
templates, which you can manage in the Substance Workbench (CG02). However, if you have previously speci ed
references for a speci cation, the system replaces the Speci cation inherits from table with read-only reference data.
For more information, see Inheritance.
Authorizations (only if Access Control Management is active)
WWI Reports (for more information, see WWI Reports).
Header Status (for more information, see Header Status for Speci cations).

Use
This function de nes the header status of a speci cation, handles status change with manual and automatic precondition
checks, and can lock a speci cation to prevent further editing.
You can check the current status of a speci cation in the following places:
The Personal Objects Worklist in the Speci cation Work Center

3/31/2019
In the Identi cation Region (IDR) at the top of the speci cation main view
On the Header Status tab
You can search speci cations according to this parameter.
When you create a new speci cation, the system assigns an initial status to it automatically. For more information about the
initial status, see the Activities section.
Note
The header status for speci cations is also integrated into the CG02 (Substance Workbench) transaction but is intended for
use on the Web User Interface with full functionality.
The header status of speci cations uses the authorization object PLM_SAM and requires the authorization role
SAP_PLMWUI_STATUS_CHANGER. Only users with this authorization can change the header status of a speci cation.
The standard delivery contains two status schemes, which you can modify in Customizing, see the Activities section:
Simple Header Status Scheme for Speci cation (PLM_RDSHS)
This scheme is set as default for all standard speci cation types. It contains only two statuses: Active and Obsolete.
Active
This is the initial status of this scheme. In this status, you can change speci cation data. You can switch to
Obsolete from here.
Obsolete
In this status, the speci cation becomes locked and cannot be edited, used in, or referred to from recipes,
When you set your speci cation to Obsolete, the system informs you about the number of objects affected by this
status change.
Caution
Use this status carefully, as you can switch to other statuses from here only with speci c authorization
controlled by the authorization object PLM_SAM.
Alternative Header Status Scheme for Speci cation (PLM_RDSH)
This scheme contains the following statuses:
In Process
This is the initial status of this scheme. In this status, you can change speci cation data. From here, you can
switch to For Release or Obsolete.
3/31/2019
For Release
From here, you can either switch back to In Process or switch to Released.
Released
In this status, the speci cation becomes locked and cannot be edited. From here, you can switch to any other
status.
Obsolete
In this status, the speci cation becomes locked and cannot be edited or used in or referred to from recipes,
Caution
Use this status carefully, as you cannot switch to other statuses from here.
Features
Speci cation statuses can have the following attributes:
LOCKED_FOR_CHANGE: A speci cation with this status cannot be edited. By default, this attribute is added to the
Released and Obsolete statuses.
OBSOLETE: A speci cation with this status cannot be used in or referred to from any recipes, speci cations, or building
blocks. By default, this attribute is added to the Obsolete status.
The header status scheme depends on the speci cation type. For example, you can set different status schemes for real
substances and nutrients. By default, all speci cations use the simple header status scheme.
You can also assign precondition checks to all status transitions. The following table summarizes the precondition checks for the
default statuses:
For Release – –
Released CONSISTENT Object is consistent
NO_ACTIVE_RATING_STS All rating and validity areas are in released status
Obsolete NO_ACTIVE_INHERIT_TO There is no active inherit to relation
3/31/2019
NO_ACTIVE_RCP_USG_AL Not used in active recipe
NO_ACTIVE_RCP_USG_IN Not used as input speci cation in active recipe
NO_ACTIVE_RCP_USG_PO Not used as primary output spec. in active recipe
NO_ACTIVE_RCP_USG_PS Not used as property speci cation in active recipe
NO_ACTIVE_RCP_USG_SO Not used as secondary output in active recipe
NO_ACTIVE_SPC_CMP_US Not used as composition in active speci cation
The NO_ACTIVE_RCP_USG_AL precondition check can be used instead of the following checks:
NO_ACTIVE_RCP_USG_IN
NO_ACTIVE_RCP_USG_PO
NO_ACTIVE_RCP_USG_PS
NO_ACTIVE_RCP_USG_SO
NO_ACTIVE_SPC_CMP_US
The consistency check calls the Business Add-In BAdI: Check Consistency of Speci cation (/PLMI/SPC_CHCK_CONSIST). If the
checks in this BAdI fail then the status change is not possible. For more details, see Customizing for Recipe Development under
Logistics — General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Speci cation
Management Speci cation Business Add-Ins (BAdIs) BAdI: Consistency Check .
Activities
See Customizing for Speci cation Management under Logistics — General Product Lifecycle Management (PLM) PLM Web
User Interface Recipe Development Speci cation Management Speci cation Speci cation Master Status Management for
Header Status .
You can do the following in this Customizing node:
De ne Status Scheme — Create a new status scheme or modify the existing ones, create or modify statuses, add or
remove attributes.
BAdI: Settings for the Header Status View of Speci cations — Change the layout of the Header Status tab for
speci cations.
Change Header Status for Multiple Speci cations — De ne a set of existing speci cations and change their header
statuses based on a prede ned ruleset.
BAdI: Change of Header Status for Multiple Speci cations — This BAdI is used with the report Change Header Status
for Multiple Speci cations.
To activate the initial header status for newly created speci cations, see the documentation under Logistics —
Management Speci cation Business Add-Ins (BAdIs) Extended Checks for Speci cations Implementation: Initial Header
Status for Speci cations .
Speci cation Properties

3/31/2019
Use
In the Properties view, you can see structured information about the properties of a selected property tree. When you select a
value assignment type, the Instances table displays the value assignment instances assigned to it.
Prerequisites
You can select which subviews are available in the Properties view according to value assignment category in the Customizing
activity De ne Subviews for Value Assignment Categories under Logistics - General Product Lifecycle Management
(PLM) PLM Web User Interface Recipe Development Speci cation Management Speci cation Speci cation Database
Structure Settings for Value Assignment .
Features
In the collapsible Instances table, you can perform the following actions:
Enter characteristics and sort the entries
Change data in existing value assignment instances
Delete existing value assignment instances
Overwrite the data of an inherited value assignment instance permanently or temporarily
Invert the valuation table for a better overview
Display and hide the details of the selected value assignment instance
Change the unit of measurement of a characteristic with automatic conversion of the value.
Depending on the value assignment type and category of the selected property, the Details area allows you to de ne values for
the following:
Speci cation listing for value assignment category B (listing with class)
Composition for value assignment category C (listing with class)
Nutrient composition or quantitative composition for value assignment category RMS_N (nutritional composition)
Diet suitability for value assignment category RMS_D (diet suitability)
Allergen listing for value assignment category RMS_D (diet suitability)
Compliance with religious certi cates for value assignment category RMS_D (diet suitability)
Genetically modi ed ingredients for value assignment category RMS_D (diet suitability)
Usage
Sources
User-de ned texts
Document links
Fast Entry Screen

Use
3/31/2019
The Fast Entry Screen displays user interface variants for speci cation management in PLM Web User Interface (Web UI).
These variants allow occasional users to create, display, and edit speci cations on a user interface that contains only a de ned
selection of data.
When you, as a system administrator, create a FES variant, you de ne those speci cation properties (for example, density) that
are relevant for a speci c user group, and the layout in which they appear.
Integration
The Fast Entry Screen (FES) is an application within speci cation management in the PLM Web UI. It has a separate component
con guration /PLMU/WDC_SPC_FES_OIF_CFG, which may have several variants.
Features
Creating FES Variants
You, as a system administrator, can con gure the FES in the component con gurator of the Floorplan Manager (FPM) for Web
Dynpro ABAP. To do this, the FPM_CONFIG_EXPERT (FPM Con guration Expert) user parameter has to be assigned to you. If
this user parameter value is set to “x”, the Con gure Page icon appears on the toolbar of the FES.
You can create new user interface variants in the Navigation panel of the component con gurator. For each new variant, you can
select properties to be displayed on the FES in prede ned lists or tables.
Working with Speci cations Using FES Variants
Users can perform the following actions through the Fast Entry Screen:
Create new speci cations
Create new speci cations by copying existing ones
In this case, copied values can be used as default values that can be overwritten by the user.
If the source speci cation contains an inheritance relationship and you have selected the checkbox Copy Inheritance
Relationships (Inherits From), you can create a speci cation with defaults that users cannot change.
Note
It is not possible to overwrite inherited values on the FES, independent from the inheritance template settings.
Display or edit speci cations
To do this, users can select the speci cation and the con guration variant they want to work with on the initial screen.
Their access rights are controlled by the authorization object PLM_SPCFES (PLM Authorizations for Speci cation Fast
Entry Screen). It is also possible to access a speci cation and con guration variant directly by a prede ned URL.
More Information
For detailed information about the Floorplan Manager, see the SAP NetWeaver application help for WebDynpro ABAP.
For a step-by-step guide on con guring the FES, see SAP Note 1607027 .
WWI Reports
3/31/2019
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
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.
Uploading MSDS Documents

Use
3/31/2019
You can attach material safety data sheets (MSDS) to a speci cation on the WWI Reports tab. The status of these uploaded
les will always be Released.
Note
Only .pdf and .doc type les are allowed.
Prerequisites
You have de ned which tabs should be visible for each speci cation type in Customizing for Recipe Development under Logistics
— General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Speci cation
Management Speci cation Speci cation Master De ne Subviews for General Data .
Procedure
1. Navigate to the WWI Reports tab of the speci cation.
2. Choose the MSDS Upload button.
3. Browse for the le you want to upload, ll in all the required parameters and choose OK. For easy vendor management,
the F4 help of vendors contains all strings previously typed in by any user.
Note
On the F4 help of the generation variant, you only see variants with type IBD_MSDS.
The upload started in the background. To see the result, open the speci cation again.
Copying Speci cations

Use
You use this process to copy the data of one speci cation into another speci cation in speci cation management in the PLM
Web User Interface (Web UI).
Prerequisites
You can use an inheritance template to de ne which data objects of the speci cation should be copied (see Inheritance
Template), The inheritance template used for copying can be de ned as default by making the appropriate entries in
Customizing (see section Default Values).
Activities
Note
You can copy a source speci cation into a new one only if they belong to the same speci cation category, for example, both
are of category substance.
You can copy speci cation data according to the following:
3/31/2019
Copy a speci cation together with its inheritance relationships. These relationships are also valid in the target
speci cation, which means that if the source speci cation's data is changed in the future due to an inheritance, the
relevant inherited data is updated accordingly.
Depending on inheritance template settings, copied inheritance relationships may allow the following:
Overwriting of inherited values
Temporary overwriting of inherited values
No overwriting of inherited values
If the Copy inheritance relationships checkbox is selected and the source speci cation itself contains inheritance
relationships, more than one inheritance template is actually used:
The inheritance template that determines which data (usages, identi er, value assignment) is inherited from the
source speci cation
The inheritance templates that determined which data was inherited to the present source speci cation from
another source speci cation.
Note
Inherited data is available only after the target speci cation is saved.
Copy a speci cation without copying inheritance relationships. By doing so, you copy the data without creating a
connection between the source and target speci cations.
Choose whether to copy material assignments
Default Values
You can set default values for the following data on the initial screen in the Customizing activity De ne Default Values for
Copying Speci cations under Logistics General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
Development Speci cation Management Speci cation Speci cation Master :
(Inheritance) template
Template group
Material assignments
Copying inheritance relationships of the source speci cation
If you have made no entries in this activity, you can enter these values manually when copying speci cations.
Engineering Change Management for

Speci cations
Use
You can manage changed speci cation using change numbers in speci cation management in the PLM Web User Interface (Web
UI).
Engineering Change Management (ECM) has the same features in the PLM Web UI as in the Substance Workbench in
Environment, Health and Safety (EH&S).
3/31/2019
Prerequisites
The environment parameter SP_EXT_ECM_STATUS controls the usage of ECM for speci cations. It is deactivated by default,
therefore you have to activate it in the Customizing activity Specify Environment Parameters under Logistics -
Management Basic Settings .
Features
The following features are speci c to ECM for speci cations in the Web UI:
You can only enter a change number on the initial screen.
You cannot edit change number data on the Status subview.
You can only switch from one change number to another in display mode.
If you open a speci cation with a change number and another active change number is already assigned to the
speci cation, you get a warning message.
Status history information is read-only.
You cannot change or delete a rating with the status Released, but you can change its status from Released to In
Process on the Status subview.
If you do so, and change number usage is active for the speci cation, the system makes a record split and assigns the
change number automatically. The system automatically adjusts the date elds to the Valid From/Valid To date de ned
by the change number.
You can delete a rating with In Process status and no change number in one of the following ways:
Without a change number
With a change number
For the latter, do the following:
1. Access the same speci cation in change mode using a change number valid for speci cations.
2. Mark the status screen entry rating previously created, and delete it. You will only delete the status line beginning
with the key date of the change number.
Further Enhancement Possibilities for ECM
To ensure the following, implement the Business Add-In BAdI: Extended Checks for Speci cations under Logistics -
Management Speci cation :
Prevent changing speci cations without a change number if they were created/changed with an active change
number
Prevent changing speci cation with a certain status with change number
Prevent deleting status screen entries that are results of a record split and are not released, if the change
number used to create the record split is also used to change other data in the speci cation
To ensure that you can set a status to Obsolete by changing its Valid To date, implement the Business Add-In BAdI:
Extended Checks for Engineering Change Management under Logistics - General Product Lifecycle Management
(PLM) PLM Web User Interface Recipe Development Speci cation Management Speci cation .
3/31/2019
Download of Speci cation Data

Use
You can download a freely de nable set of data of one or more speci cations.
Prerequisites
You have made the required settings in Customizing for Recipe Development, see Variants in Download Data.
You have at least read rights for the speci cations of which you want to download the data.
Features
On the Download Data main view for speci cations, you can nd the following areas:
Variant and format selection — here you can choose which variant and output format you want to apply.
Download Data Parameters — here you can set the format, and also select the relevant object data.
Included Properties — here you can select the properties for download. You can select properties from several property
trees; the data will be displayed as a list and not grouped by property trees.
There are properties that appear in more groups — for example Possible Hazards (Summary) — but you can select them
separately to avoid confusion. This does not affect the output since properties are downloaded only once (not arranged
by property trees).
Note
If more than one speci cation is selected, the Included Properties area displays the properties of the speci cation
that is the rst in the object list. You can modify the order of object by clicking the Object List button.
Additional Information — here you can select the relevant data groups that lter the output data:
Nutrient Group
Diet Group
Allergen Group
Religious Certi cate Group
Genetically Modi ed Ingredient Group
You can access the Download Data or the Download Data with Quick Selection functions for speci cations in the following
places:
For downloading the data of one speci cation:
On the Speci cation UI when changing or displaying a speci cation, select Additional Functions Download Data
or Additional Functions Download Data with Quick Selection .
When displaying a speci cation in Object Navigator, select Additional Functions Download Data or Additional
Functions Download Data with Quick Selection .
For downloading the data of one or more speci cations:
3/31/2019
In the Speci cation Work Center, select the required speci cations in the search result list, then choose Additional
Functions Download Data or Additional Functions Download Data with Quick Selection .
In the Speci cation Work Center, under My Objects (Personal Objects Worklist), select the required speci cations
and click the Download Data button.
More Information
Downloading Data
Mass Change for Speci cation

Use
Mass change allows you to select several speci cations and change certain data at the same time, without having to access the
speci cations one by one.
For the areas of a speci cation that you can change using this function, see section Features.
Prerequisites
You have authorization to maintain standard selections for the given objects.
Features
The following data can be edited with the mass change functions:
Header data
Authorization Group
Note
Identi er
Identi cation Type
Identi er
Language
Status
Material Assignment
Material
Plant
Note
You can edit objects only if their status allows editing.
You can access the Mass Change main view from the following places:
3/31/2019
My Objects in the Speci cation Work Center: Select the speci cations you want to change, then choose Edit Mass
Change .
Object Sets in the Speci cation Work Center: Select the speci cations you want to change, then choose Additional
Functions Mass Change .
Advanced Search: Select the speci cations you want to change from the search results, then choose Additional
Functions Mass Change .
Activities
To change several values at a time, select the corresponding speci cations on the main view, then choose Change Values.
You also have the option to edit the data manually and search in the previously selected speci cations using the Re ne
Selection option.
Recipe Development
Use
You use this function to develop the recipes that comprise the information about the production process for a product, as well
as the input and output substances and packaging used in that process.
Based on the ingredients used, Recipe Development can carry out different calculations, for example to determine a product's
nutritional value or costs.
Caution
If you have used non-Web-based Recipe Management (PLM-RM) up to now, you can no longer use the recipes managed
there in Web-based Recipe Development (PLM-WUI-RCP), because the underlying databases are different.
To migrate the formulas and recipes from Recipe Management (PLM-RM) to Recipe Development (PLM-WUI-RCP), you can
use the transaction/PLMI/RCP_MIGRATION Recipe Development - Migrate Formula and Recipe. For more information, see
the documentation for report /PLMI/RCP_MIGRATION and SAP Note 1511580 .
Integration
To be able to use all features of Recipe Development, you need the following additional components:
Business Context Viewer (BCV)
In the side panel, you can call the Business Context Viewer when editing recipes. The standard system provides you with
prede ned query views for recipes and the materials used in the recipes. You can enhance this standard content and
con gure it for your own business needs. For more information, see Recipe Data Analysis.
Guided structure synchronization (see Guided Structure Synchronization (PLM-WUI-GSS) ).
Portfolio and Project Management
In Portfolio and Project Management, you can link recipes with objects (project, phase, task, element, and initiative) (see
Portfolio and Project Management).
Features
3/31/2019
Recipe Development contains the following functions:
Web-based interface for creating, displaying, and changing recipes
A tabular view of the formulas, for creating, displaying, and changing a formula's input and output substances and
alternatives
Display and change of formula data of multiple recipes simultaneously
Formula optimization
Overview of the process in which the primary output is produced, for creating, displaying, and changing the sequence of
process elements such as process stages, operations, and actions
Process parameters and process parameter masters that you can use to de ne a process run in more detail. Process
parameters, for example, are boiler pressure or oven temperature.
Equipment requirements
Calculations that the system performs based on the ingredients contained in the recipe
For example, you can de ne calculations that determine the nutrient values or costs produced when a recipe is made.
You can display the calculation results at any time in Recipe Development.
Transfer of calculation results to the primary output speci cation or output stream speci cation.
Explosion simulation based on simulation models
Explosion log that contains the steps the system carried out during the recipe explosion
Consistency check
PDF-based print forms
Download of recipe data for single or multiple recipes
Synchronization of recipes and manufacturing BOMs
Synchronization of recipes to master recipe (PP-PI)
Note
With the help of object sets, you can group any number and type of objects (for example recipes, speci cations, building
blocks) and organize them according to your needs. For more information, see Object Sets.
Recipe
De nition
A recipe comprises all the information about all input and output substances produced or required the production process for a
substance, as well as information regarding that process.
The primary output of a recipe is the substance that is to be produced with this recipe. Other substances can be left over during
the production process: these are the secondary outputs.
The recipe is uniquely identi ed by a combination of the following:
Speci cation of the primary output
3/31/2019
Alternative recipe
Recipe version if you have speci ed in Customizing that the relevant recipe type supports versions
You can also use one single eld to identify recipes during assignment, search, or display, if you enable single- eld recipe input in
Customizing (Recipe General Settings ).
Note
You cannot delete a recipe that has been created and saved. However, you can mark a recipe for deletion or for archiving if
the recipe status allows this (see Status Schemes for Recipes).
Structure
A recipe is made up of the following parts:
Identi cation Region
The Identi cation Region is the area at the top of the screen in Recipe Development and is not dependent on the view you are
in. You cannot change the data here.
The Identi cation Region contains the following general information:
Speci cation of the primary output with description
Description of the recipe
Recipe type
Recipe status (see Status Schemes for Recipes)
Recipe purpose
Plant
Validity period (see Recipe Validity)
General Data
Note
This area contains partly the same data as the Identi cation Region.
This view contains the following subviews:
Basic data
Recipe description with long text
Recipe status and recipe purpose
Plant
This eld is only displayed if the recipe type is marked in Customizing as plant-dependent (see Plant Dependency
of Recipes).
WBS element (see WBS Element Assignment for Recipes)
Authorization group
3/31/2019
You use authorization groups to assign to recipes groups of users who are authorized to work with these recipes
(see Authorizations).
Property speci cation
This eld is only displayed if the recipe type requires or allows a property speci cation (see Property
Speci cation).
Validity data for the recipe
Archiving ag
If you no longer use a recipe, you can archive it. For more information, see Recipe Archiving.
Owning context
Administrative information
Descriptions
You can create language-speci c description texts in all languages available in the system. However, the system always
displays the description in the logon language only in the Identi cation Region, search result, or explosion log.
Documents (see Documents)
Classes and characteristics (see Classi cation in Recipe Development)
Reports (see Reports)
This view is only displayed if the recipe type requires or allows a property speci cation.
Formula
The Input and Output view contains all input and output substances and their alternatives with quantities and all other relevant
data, for example, the component type and the assigned substances or materials (see Formula).
In the Optimization view, you can optimize a formula according to various criteria (see Formula Optimization).
Process
This view contains the process with which the primary output is produced with all associated process elements (see Process).
Calculation Results
This view shows the data that the system determines by prede ned calculations based on the ingredients contained in the
formula (see Calculations). These are the following calculations in the standard system:
Ingredients
Composition
Nutrients (per ingredient and composition)
Diets (per ingredient and composition)
Allergens (per ingredient and composition)
Religious certi cates (per ingredient and composition)
Genetically-modi ed ingredients (per ingredient and composition)
Costs
3/31/2019
Nutrient Loss Calculation (item-level process and storage loss calculation)
Authorizations
This view contains the authorizations assigned to the recipe (see Authorizations and Access Control Context (PLM-WUI-APP-
ACC).
Process Route
You can use change management to de ne a process route, which you use to model a process and assign a processor to every
step. You can change this de ned process at any time (see Process Route).
More Information
The following features are also available in Recipe Development:
Change Documents for Recipes (SAP Note 1963483 )
Speci cation in Recipe Development

De nition
In Recipe Development you use speci cations to describe substances or packaging and their properties.
Use
In the standard system you use the following speci cation categories for Recipe Development:
SUBSTANCE Substance, with the following speci cation types, for example:
REAL_SUB Real substance
LIST_SUB Listed substance
DIET Diet and DIET_GROUP Diet group
NUTRIENT Nutrient and NUTR_GROUP Nutrient group
ALLERGEN Allergen and ALLERG_GRP Allergen group
GENMOD Genetically modi ed ingredient and GENMOD_GRP Genetically modi ed ingredients (group)
RELIGIOUS Religious certi cate and RELIG_GRP Religious certi cates (group)
PACKAGE Packaging
RECIPE_WUI Recipe Properties (see Property Speci cation)
Note
Recipes are not de ned as speci cations, unlike in the non-Web-based Recipe Management (PLM-RM) (see Recipe
Management (PLM-RM)).
Integration
3/31/2019
You can use speci cations in the Speci cation Workbench for Environment, Health and Safety (EH&S) as well as on the Web
user interface for speci cations within Recipe Development.
If you want to use a speci cation that does not yet exist, you can create it from Recipe Development.
More Information
Speci cation Management (EHS-BD-SPE)
Speci cation Management
Alternative Recipe and Recipe Version

De nition
If you want to de ne different recipes for a primary output, you use different alternative recipes.
The information in the various alternative recipes can be different apart from the primary output.
Note
When you create a new recipe, the system considers this to be the rst alternative recipe.
If versions are permitted for the recipe type you are using, you can create multiple recipe versions for each alternative recipe,
for example, if you want to change recipe data during the recipe development process.
Use
You create alternative recipes when you need multiple recipes for the same primary output with the following different
properties:
Different recipe types
Different input substances
Different processes
Different validity periods
Different recipe purposes
Different plants, if the recipe type allows the use of plants
If you merely want to allow different input substances or different material assignments for an input substance, you can create
alternative items in the formula of a recipe (see Formula Editing).
Note
If a formula contains alternative items, the system only considers the item marked as Used Alternative into account during
calculation or during explosion. When synchronizing a recipe with a material BOM, however, you have the option of choosing
between the existing alternatives (see Synchronizing a Recipe with a Manufacturing BOM).
In the following cases, you should not change an existing recipe version; instead, you should always create a new recipe version:
3/31/2019
You have transferred the calculation results for the version to the primary output speci cation (see Transfer of
Calculation Results).
You have created a material BOM from the version (see Synchronizing a Recipe with a Manufacturing BOM).
You have created a label from the version.
Recipe Type
You use the recipe type to differentiate recipes in terms of how detailed they are and how they are used in different areas of an
enterprise.
You can create alternative recipes with different recipe types for a recipe but all recipe versions of the same alternative recipe
must have the same recipe type.
The recipe type determines the following properties of the recipe:
Which status scheme is valid for the recipe type (see Status Schemes for Recipes)
Whether you can use change numbers to specify the validity (see Recipe Validity)
How the identi ers are assigned to alternative recipes (see Alternative Recipe and Recipe Version)
Whether you can create recipe versions for an alternative recipe
Whether the system writes change documents for the recipe
Whether the recipe is allowed to contain a process (see Process)
Whether the recipe is allowed to contain streams (see Streams)
Note
If a recipe allows streams, process stages can always be created for associated recipes, even if the recipe type
generally does not allow processes. For more information, see Material Flow and Different Authorizations for Formula
Developers and Process Developers.
Whether a plant is allowed to be assigned (see Plant Dependency)
Whether a property speci cation can or must be created for the recipe (see Property Speci cation) and which settings
apply for this property speci cation
Whether the automatic creation of primary output speci cations mandatory, optional, or not allowed
Whether alternative items for the primary output are allowed to be created in the formula (see Formula Editing)
Whether it is allowed to manually adjust the composition of output streams and the primary output of the recipe (see
Manual Composition)
In which sequence recipes of different recipe types are considered during explosion (see Explosion)
To make these settings, see Customizing activity De ne Recipe Types, under Logistics - General Product Lifecycle
Management (PLM) PLM Web User Interface Recipe Development Recipe .
Caution
Do not create building block types and recipe types with the same identi er.
3/31/2019

Use
Status schemes support you during a release process. The following status schemes are de ned for recipes in the standard
system:
Simple status scheme
You use this status scheme if you only use the recipe in the development department, for example.
Status scheme with transfer from the development department to the production department
You use this status scheme if you transfer the recipe via the Guided Structure Synchronization to the production
department and want to create a manufacturing BOM from it.
Prerequisites
If you want to use your own status scheme, you have to edit the activities in Customizing for Recipe Development, under
You enter this status scheme under Recipe De ne Recipe Types for the recipe types used by you.
Features
The following status attributes are available for recipes:
DELETION_ALLOWED: Recipe can be marked for deletion
LOCKED_FOR_CHANGE: Recipe is locked for all changes
CONSIST_EXPLOSION: Explosion-relevant recipe data is consistent and the recipe is locked for changes (see
Consistency Check)
REL_EXPLOSION: Recipe is relevant for explosion (see Explosion)
CONSIST_SYNC_BOM: Recipe data that is relevant for synchronization of the recipe with a manufacturing BOM is
consistent and the recipe is locked for changes (see Consistency Check)
REL_SYNC_BOM: Recipe is locked for all changes and relevant for synchronization with a manufacturing BOM. The recipe
data that is relevant for the synchronization of a recipe with a manufacturing BOM is consistent (see Synchronizing a
Recipe with a Manufacturing BOM).
REL_SYNC_MRCP: Attribute for synchronization of recipe to master recipe (see Synchronizing a Recipe with a Master
Recipe)
REUSE_RESTRICTED: Reuse is restricted
3/31/2019
In Process
In this status, you can change recipe data and mark a recipe for deletion. From here, you can switch to the For Release
status.
For Release
If you want to set this status, the consistency check checks whether the recipe is consistent for the explosion. Only then
can you set this status. The recipe is locked for changes as of this status.
You use this status to initiate the release process; the responsible recipe developer checks the recipe and changes the
status.
Caution
2. You change data.
Released
The explosion-relevant recipe data is consistent and the recipe is locked for changes.
By setting this status, you transfer the recipe to production. In this status, a recipe is considered in the explosion. You
cannot change released recipes, you can only set them to status Obsolete.
Obsolete
season due to the availability of raw materials (such as the processing of fresh fruits). You can mark a recipe with this
status for deletion, but you cannot change it, or create a recipe using an obsolete speci cation as the primary output.
From here, you can switch back to the For Release status.
In Process
3/31/2019
For Release

changed
Released

changed
Obsolete
Recipes with Status ʻReleased’
In case you have to change descriptions and long texts in a released recipe for translation reasons, you can still do that even
after an official work ow process has been performed.
When a recipe is released, meaning it has the status attribute LOCKED_FOR_CHANGE assigned, you cannot insert or modify its
document links in Document Management (transaction CV02N). This is also true for inserting or modifying multiple document
links; the action does not take place unless all entries are in a status that allows change.
In Process
In this status, you can change recipe data and mark a recipe for deletion.
If you want to set this status, the consistency check checks whether the recipe is consistent for the explosion and for the
synchronization. Only then can you set this status. The recipe is locked for changes as of this status.
With this status, you can trigger the release process; the responsible recipe developer checks the recipe and transfers
the recipe to the production department by setting the status For Release (Production).
3/31/2019
The production department checks the recipe before releasing it. In this status, a recipe is considered in the explosion.
With this status switch, you automatically change the recipe purpose from development to production (see Recipe
Purpose).
Caution
2. You change data.
By setting this status, you transfer the recipe to production. You cannot change released recipes, you can only set them
to status Obsolete.
Obsolete
season due to the availability of raw materials (such as the processing of fresh fruits). In this status, you can switch from
the status Released for Production. You can mark a recipe with this status for deletion, but you cannot change it.
In Process


changed

changed
3/31/2019


changed

changed


changed
Is relevant for the synchronization of a recipe with a

manufacturing BOM
Obsolete
Recipe Purpose
Use
The recipe purpose speci es in which area of an enterprise a recipe is used, for example, in development or for production.
You can de ne a sequence of recipe purposes for every recipe purpose in Customizing; the system then takes the associated
recipes into account during explosion.
3/31/2019
The recipe purposes DEV Development and PROD Production are delivered with the standard system.
Integration
In the standard system, the recipe purpose is set automatically according to the status of the recipe (see Status Schemes for
Recipes).
Example
Im Customizing, the recipe purpose Development has the following sequence:
1. Development
2. Production
If the recipe that is exploded has the recipe purpose Development, the system rst takes recipes into account that have the
recipe purpose Development. If no recipes with this recipe purpose exist, the system also takes recipes with the recipe purpose
Production into account.
Development Recipe
Use
To assist product development, you can create development recipes for experimental purposes.
A development recipe is usually one with a simple structure, for which the nal product is not yet known. However, you might
already have an interim product or information on physical or chemical properties ready. These recipes can also be simpler by
content (for example, by containing only the formula and not requiring process information), and they can have different
approval scenarios compared to a general or site recipe.
Procedure
To de ne recipe types for experimental purposes, you have to make the relevant settings in Customizing under Logistics —
General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development .
1. De ne a new external or internal number range under Speci cation Management Speci cation Master Specify
Number Ranges for Speci cations .
2. Create a speci cation type for the primary output of the development recipe under Speci cation
Management Speci cation Master Specify Speci cation Types , and set the number ranges that you de ned in the
previous step.
3. Create a recipe type that will represent your development recipes. Select the status scheme you want to use for your
recipe type and set the Auto-Create PO Spec. option to mandatory under Recipe De ne Recipe Types .
You also have to set up the Defaults for Primary Output Speci cation for this new recipe type, because these values will
be used when the system creates speci cations automatically. Here you can use the speci cation type created in step 2.
For more information, see Recipe Type.
Note
You can de ne a status scheme under Recipe Status and Action Management De ne Status Scheme . For more
information, see Status Management.
3/31/2019
4. Allow your speci cation type to be used as primary output under Recipe De ne Allowed Speci cation Types per
Formula Item Type .
Plant Dependency
If the recipe type allows it, you must specify in a recipe the plant in which the recipe is to be used (see Recipe Type).
Note
In the standard system, the recipe type PLANT Plant Recipe ist de ned for plant-dependent recipes.
If a plant is speci ed in a recipe, this has the following effects:
Every version of the alternative recipe is assigned to the same plant.
The system enters the plant in the calculation parameter (see Calculations).
If you assign to a formula item a speci cation that is assigned a material that does not exist in this plant, the system
does not assign the material automatically. However, you can assign such a material manually (see Formula Editing).
If a formula item is assigned a material that does not exist in the plant assigned to the recipe, the recipe is not
consistent (see Consistency Check).
The system uses the plant as default value when synchronizing the recipe with a manufacturing bill of material (see
Synchronizing a Recipe with a Manufacturing BOM).
WBS Element Assignment of Recipes

Use
This function enables work breakdown structure elements (WBS elements) to be assigned to recipes in PLM Web UI. For more
information about work breakdown structures, see What is a Work Breakdown Structure?.
Integration
This function creates an (optional) binary relationship between the Project System (PS) element (WBS element) and a PLM
object (recipe). For more information about Project System, see Project System (PS).
Prerequisites
In order to use this function, transaction SOBL_MODEL has to be set up in Customizing to handle the roles for WBS elements
and recipes, and to handle the relationship type (link) between the two.
Features
This function enables a relationship (link) to be established between recipes and WBS elements in the Web UI of recipes. The
traceability of the relationship is supported by Generic Object Services and Enterprise Search.
Activities
3/31/2019
The user establishes a link to a WBS element in the Web UI of the recipe. The system stores the link in Generic Object Services
as a binary relationship between the two objects.
Example
A speci c recipe is being developed at a customer for a special order, which will be replenished using Project System (PS). The
establishment of a link between the recipe and the relevant WBS element provides better visibility, accountability, and
traceability.
Property Speci cation

De nition
Speci cation uniquely belonging to a recipe, containing a property tree in which relevant properties for a recipe are stored.
These properties can differ from the properties de ned in the speci cation of the primary output.
Use
The recipe type determines whether a property speci cation is mandatory, optional, or not permitted (see Recipe Type).
If a property speci cation is mandatory, the system automatically creates a property speci cation when you create a recipe.
The system uses the default values de ned for this purpose in the recipe type.
If the property speci cation is optional, you can create it in the Basic Data General Data view.
In the property speci cation, you can save the calculation results for the recipe and store additional data such as
measurements.
The property speci cation is only valid in connection with the recipe. Therefore, the following conditions apply:
If you remove a property speci cation from a recipe, the system automatically deletes the property speci cation.
You can only edit a property speci cation if the associated recipe can be edited, that is, if the status of the recipe allows
such editing and the recipe is not marked for archiving.
Each recipe version can have only one property speci cation. When you copy a recipe version, you can copy the property
speci cation for the new recipe version at the same time.
It is possible to mark a component type so that it is not exploded during calculation, if, for example, you do not want to show
detailed composition information. In this case, the system can use the values from the property speci cation instead of the
primary output speci cation. You can set this attribute for component types in Customizing activity De ne Explosion Scopes
and Assign Component Types under Logistics — General Product Lifecycle Management (PLM) PLM Web User
Interface Recipe Development Recipe Calculations .
Integration
The system also uses property speci cations internally for the versioning of reports (see WWI Reports). If you have already
created reports for the recipe, the speci cation cannot be deleted, that is, the recipe cannot be marked for deletion.
Recipe Validity
3/31/2019
When a recipe is developed, the validity is mostly not very important at the beginning. Therefore, you can create and edit
recipes without a restricted validity. However, if a recipe is relevant to production, the production department mostly needs
concrete information about the validity.
You can restrict the validity of a recipe according to time and quantity.
Validity Period
You have the following options for restricting the validity period:
You enter a valid-from and a valid-to date.
The validity can overlap. This is useful, for example, if a material is to be replaced. The preceding recipe is valid until the
material currently being used is depleted. After that, the next recipe should be used.
You enter a change number from which the system determines the valid-from date. The valid-to date is the date
12.31.9999 if no subsequent recipe version with a valid-from date exists.
Note
You can only assign a change number directly while creating the recipe.
If a recipe version with a later valid-from date exists, the system automatically sets the valid-to date of the previous
recipe to one day before the valid-from date of the version that follows.
If you want to use different change numbers, you can create different recipe versions and assign a change number to
each one.
If you use change numbers, it is not possible to have overlapping validities or gaps in which there are no valid recipe
versions.
Validity According to Quantities

You can de ne the validity based on quantities in the Basic Data view under General Data.
In the standard system, no checks are implemented for the quantity-based validity; this data only serves to describe the recipe
in more detail.
When you create a material BOM from the recipe, the system copies the quantity-based validity as lot size of the material BOM
(see Synchronizing a Recipe with a Manufacturing BOM).
Formula
De nition
The formula contains the input and output items of a recipe.
Note
Depending on the authorizations you have been granted, it may be the case that you can only edit process data. In this case,
you do not see this view.
For more information, see Different Authorizations for Formula Developers and Process Developers.
3/31/2019
Structure
The formula contains the following data for every item:
Associated process element
Process stage, operation, and activity to which this item belongs, with description
Item type
Item types are input, input or output stream, primary or secondary output.
Item description
If a material is assigned to the item, the system uses the short text of the material as the item description. If no material
is assigned to the item, the system uses the rst or second identi er de ned in the speci cation. If the item is a stream,
you can change the description.
Component type
Component types are, for example, component, ingredient, packaging.
If several alternatives exist for an item, information as to whether the item is the alternative used.
Speci cation with two description texts, which the system determines from the rst two identi ers of the speci cation
You can use speci cations for substances or packaging, for example.
If a material is assigned, the material with short text
Note
If you want to create a material BOM from the recipe, every item must be assigned a speci cation with material.
If the item is an input stream, the process stage in which the stream is produced.
Information as to whether the speci cation is used in a different recipe:
For input items, this is a recipe that produces the assigned substance.
For output items, this is a recipe that uses the assigned substance as input.
Note
If you want to display these linked recipes, you can jump to the object navigator via the speci cation context menu.
Information as to whether the quantity for this item is to be calculated from other items
The upper and lower limit, between which the speci ed or calculated quantity of the item must be.
Scrap
Exception value with description if relevant
Quantity with unit of measure
Mass, volume, density, if relevant
An explosion recipe, if the system is to always use a speci c recipe for this formula item during explosion
Calculation mode
For output streams and primary outputs, you can choose between the following modes:
3/31/2019
Normal
Total solids calculation
Evaporation and absorption calculation
Evaporation and absorption calculation with total solids
For more information, see Calculation Modes.
Total solids [KG] and total solids percent, if relevant
In the standard system, the following values are calculated automatically from this data, for each formula item (based on the
item, the primary input, or the stream), when you call the Input and Output formula view:
Mass in percent
Mass in the unit speci ed in Customizing
Volume in percent
Volume in the unit speci ed in Customizing
Calculated quantity, if the quantity for the item is to be calculated from other items
Mass, volume, density, if relevant
If a density is de ned in the material or in the speci cation for a formula item, the system always calculates the volume
based on the density according to the priority de ned in Customizing.
If no density is de ned, and you have speci ed that the quantity is to be calculated from other items, the system
calculates an approximate value for the density based on the data of the input substances.
Loss quantity
Logistic quantity
Note
You can display or change formula data for multiple recipes simultaneously (see Display and Change of Multiple Recipes).
More Information
You can create new layouts for the formula view and select the columns you need in Customizing for Recipe Development, under
Recipe De ne Layouts for Formula Views .
Streams
Use
Streams are intermediate products of a recipe that arise and are used up again during the process. A stream is produced on a
process stage (output stream) and is used up again on at least one other process stage (input stream).
Streams are only available within the recipe version in which they are created.
Prerequisites
3/31/2019
In Customizing for the recipe, you have speci ed that recipes of this recipe type can contain streams (see Recipe Type).
Features
If you assign a recipe input item to a process stage, the system automatically creates an output stream and assigns the item
number and the description text of the stage to it. You can then process this stream and use it on a different stage as input
stream.
You can assign a speci cation, such as the primary output, to an output stream that can only be used for exactly this output
stream. In other words, the speci cation can only be used once within each recipe version for an alternative recipe, and not
outside of the alternative recipe.
Note
When you copy a recipe that contains speci cations for output streams, the system automatically creates new
speci cations.
If the component type of the output stream causes an explosion stop, you must assign a speci cation so that the system
considers this formula item in the calculation.
You cannot assign a material or speci cation to an input stream, the system uses the corresponding data from the associated
output stream.
For a recipe with streams, the system always displays the Process view, even if the recipe type does not allow a process. You can
process the process stages there.
Depending on your authorizations, you can only use certain functions. For more information, see Different Authorizations for
Formula Developers and Process Developers.
You can calculate the nutrient losses that arise during the recipe process for output streams. See Process Loss and Storage
Loss.
Material Flow
Use
Depending on whether the recipe type allows a process or the use of streams, you have different options for displaying a
material ow.
Recipe Type Allows Process Recipe Type Allows Streams Material Flow
Yes No Material ow cannot be displayed
No Yes Material ow on stage level
Yes Yes Material ow for all process elements
No No Material ow cannot be displayed
Process Is Allowed, Streams Are Allowed
For this recipe type, every stage that is assigned an input item must also have an output item. This can be either the primary
output, a secondary output, or an output stream.
3/31/2019
Therefore, the system automatically creates an output stream for every stage having an input item, that is not assigned an
output.
You then assign this output stream to one or more stages as input stream.
Only Streams Are Allowed
In this case, you can nevertheless use process stages within the recipe to be able to work with streams. In the formula, you can
then assign stage numbers to the formula items and create and process streams.
Only Process Is Allowed
In this case, you can assign formula items to the process stages. However, the recipe does not display a material ow.
Neither Process Nor Stream Are Allowed
In this case, you cannot display a material ow.
More Information
Recipe Type
Streams
Different Authorizations for Formula Developers and Process Developers
Process
De nition
A sequence of chemical, physical, or biological activities for converting, storing, or transporting material or energy (see process
as per ISA standard S88).
A recipe can contain a maximum of one process, if the recipe type allows this (see Recipe Type).
The process contains all the activities that are required to produce a product or different intermediate products.
Note
If the recipe type allows streams, you also see this view even if the recipe type does not allow processes (see
Streams).
Depending on the authorizations you have been granted, it may be the case that you can only edit formula data. In
this case, you do not see this view or you can only see it in a limited manner.
Structure
In the standard system, the recipe process is a combination of the following process elements:
Stage
3/31/2019
Operation
Action
Note
If you want to use different process elements, you can replace the names in Customizing (see Adapting the Standard
System).
The left screen area in the Process view contains a tree structure of all process elements contained in the process and of the
input items or output items associated with those process elements. If a stream is assigned to a process element, you receive
additional information regarding in which process element an input stream is created or an output stream is consumed.
The process is the top element and is identi ed by the recipe label in the tree structure. The process can be broken down into
several stages. The stages can contain different operations, which themselves can be broken down further into actions.
For every process element, further views are available for the following data:
If the process type is a stage or an operation, all subordinate process elements
Formula items that are assigned to the process element
Assigned process parameters
Language-dependent description texts
Documents
Operations additionally contain a Sequence view, in which you can de ne which operations precede the selected operation, and
which operations follow it.
Importing a recipe is possible by inserting a source's reusable items into the target recipe. These items can be selected on their
own, such as process elements and their formula items, process parameters and equipment requirements, that is, the whole
recipe does not need to be imported. See section Origin and Reusing Building Blocks and Recipes.
Origin
The Origin column links to the recipe or building block the particular process item was loaded or imported from. The link is active
if the user has the appropriate authorization to open the linked object.
If the loaded content is updated, the item's reference to the original object is lost. However the system keeps the reference in
the following cases:
Copying recipes on the initial screen
Creating new alternatives or versions of recipes
Copying building blocks on the initial screen
By default, the system clears the origin reference if you make changes in the following areas:
Formula Items Process Parameters/EQR Parameters Equipment Requirements
Item Type Unit of Measure Header class
Speci cation eld changes Target
3/31/2019
Material eld changes Min Value
Component Type Max Value
Process Parameter
Process Parameter Master

De nition
In a process parameter master, you de ne process parameters that you specify as default values or want to reuse. You can then
use these in the Process Parameters view of a process or process element (see Value Assignment of Process Elements by
Means of Process Parameters).
To create or change a process parameter master, in recipe editing choose Related Links Change Process Parameter Master .
Structure
De ne the following data for every process parameter master:
Identi er and description
Unit of measure and data type
The data type and the unit of quantity together determine whether characters are allowed as values, and exactly how
many decimal places the values for digits are allowed to have.
Possible value assignments
You have the following options for limiting value assignments:
You de ne the target value, minimum value, and maximum value.
You assign a class.
To do this, you use classes of the class type 105 with corresponding characteristics.
When you assign a class, you can valuate the associated characteristics in the details for the process parameters,
in the Process Parameters view.
Process parameter group
You de ne process parameter groups in Customizing for Recipe Development under Recipe Process De ne Process
Parameter Groups .
If you no longer want to use a process parameter master, you can mark this entry as obsolete.
Note
If a process parameter master is assigned to a process element, the system marks the corresponding entry as used. You
cannot change the data anymore after that.
Equipment Requirement
De nition
3/31/2019
Contains information about the required production resources in the production process as well as technical data that is
described by texts, documents, and valuated characteristics.
Use
You can assign equipment requirements (EQRs) on the following levels:
Recipes:
Recipe header (EQR is not considered when synchronizing a recipe with a manufacturing BOM)
Stage
Operation
Action
Building blocks of the following type:
Process
Stage
Operation
Action
EQR
Note
If the relevant column is not displayed in the table, you have to re ne your table settings to enable the display (see User-
Speci c Settings).
Depending on which process element you selected, the system displays all relevant equipment requirements sorted according
to stage.
For every stage, you can mark an equipment requirement as primary resource.
You can describe equipment requirements by using the following further properties:
Language-dependent description texts with long text
Classes and characteristics
Documents
Displaying Equipment Requirements
You can display equipment requirements and equipment requirement process parameters (EQR PPs) in the process structure
tree on the Process tab by selecting the corresponding checkboxes after choosing Content Settings. You can specify whether
they are displayed by default in Customizing activity De ne Process Structure, under Recipe Development Recipe Process .
Reusing Building Blocks and Recipes

Use
3/31/2019
To make use of already existing processes, you can load building blocks or import recipes into a recipe that you are working on.
Activities
Loading Building Blocks
You can load building blocks into a recipe in the Load Building Block panel on the Process main view, according to the building
block''s identi er. They can also be loaded into other building blocks. When you load a building block that can have a formula, the
system also loads all the existing formula items into the recipe.
The hierarchy to consider for this is the following:
1. Process
2. Stage
3. Operation
4. Action
Note
Equipment requirement building blocks can be loaded at any process level.
Process Building Blocks
You can only load one process building block into another when the top process item is selected in the process structure
tree. The system loads all assigned process elements, but does not load header documents and classi cations.
In case the building block's category is process and it is loaded to a selected recipe in the process structure tree, the
system appends it to the end using the next biggest 10 as starting ID, and applies the stage ID pacing between the
stages.
By choosing the Refresh button on the Process main view, you can display the contents of the building block to be loaded.
However, this function only shows the contents that you are authorized to see. Even if there is more content than what is
visible, the system loads only the displayed items.
Stage Building Blocks
In stage building blocks, the stage column is hidden from the formula- and process elements tabs, as well as the process
structure tree.
The copy, paste, insert, delete options for the top level element are disabled.
You can load building blocks into the recipe once you have started creating or editing a recipe.
Stage building blocks can be loaded the following ways:
When you select a parent, that is, a higher level element in the process structure tree for process elements, the
system loads the building block with all content assigned to its process elements. This means that a new process
element is created and appended as the last new entry with this type below the parent. This way new elements
receive their descriptions from the building block's descriptions, including the long text.
In case the process element you have selected is on the same level as the current building block, it loads its
content into the current one. This means that the header description and long text are loaded, and the assigned
content is loaded with a numbering that is continuous compared to the last number. For example, if stage 15 has 3
formula items as input (10, 20, 30), the next input items are loaded from 40 onwards.
The system checks for over ow before items are actually loaded.
3/31/2019
When you select these items for loading in case of stage building blocks, the system behaves according to the following
Recipe: The system appends items to the end using the next biggest 10 as a starting ID, and applies the stage ID
pacing between the stages.
Stage: The system loads items into the selected process element.
Operation: Building blocks with stage category cannot be loaded to an operation process element.
Action: Building blocks with category stage cannot be loaded to an action process element.
EQR: Building blocks with category stage cannot be loaded to an EQR process element.
Operation Building Blocks
In operation building blocks, the stage and operation columns are hidden from the formula- and process elements tabs,
as well as the process structure tree.
Operation building blocks can be loaded the following ways:
Equipment Requirement Building Blocks
You can load an equipment requirement (EQR) building block into an existing recipe to any process element, including
the recipe object itself.
Importing Recipes
You can import a full recipe, or part of a process structure that you nd useful and want to reuse for the current recipe. You can
select certain parts of a recipe for import if, for example, your recipe has stages with operations and actions, but you only want
to reuse one of the operations in an existing stage of the current recipe. In this case you do not have to create a new stage,
since that stage would be removed anyway because you would move the operation to the required position and would delete
the rest of the stage.
When you select an element during import, if the element is already a child node of a hierarchy, its parents indicate that not all
of their subordinate elements are selected by displaying a 3rd state checkbox. When an element is selected, it automatically
sets the selectable elements below.
You can select the following elements of a recipe for import:
Recipe structure
Process elements and their dependent data
The selected elements can have the following kinds of subordinates:
Lower level process element, for example, an operation for a stage
Dependent data for the actual process element, for example the formula and process parameter of a stage
3/31/2019
These elements cannot be selected individually but you can specify whether a process element is taken over along with its
dependent data. Whenever a checkbox has 3rd state, it is taken over and shown in the overview during the recipe's import.
You can see the difference between loading building blocks and importing recipes in the following table:
Loading Building Blocks Importing Recipes
Any building block can be loaded into any recipe or another building Imported recipe has to be the same type as the target recipe
block
Loaded as a whole unit You can select what parts of a recipe you want to import
Can be loaded to various parts of a recipe Appended to the end of the target recipe''s process
Origin
Process Parameter
More Information
Authorization in Building Blocks
Creating Building Blocks
Calculation Results
De nition
The system determines calculation results based on the calculations speci ed in Customizing (see Calculations). When you call
a view that contains calculation results, the system explodes the recipe and recalculates the values (see Explosion).
3/31/2019
Since you cannot change calculated data, you have to change the calculation parameters or the formula data to get other
results. Then the system explodes the recipe again and recalculates the data.
Structure
The following views are de ned for calculation results in the standard system.
Note
If you want to use other calculations, follow the steps under Adapting the Standard System.
Ingredients
This view contains the ingredients used in the recipe that are necessary to produce the primary output.
Composition
This view contains the analytical composition of the primary output and describes its properties.
Note
In the Ingredients and Composition views, the Group Items function is available. When you execute this function, the system
groups all formula items that have the same assigned speci cation into one item. You can undo this grouping by choosing
the Show All Items function.
If the items that are grouped have different component types, the system does not show any component type for the
grouped item.
In case reaction happens in your recipe, you can use manual composition to adjust the values accordingly. See Manual
Composition.
Nutrients
This view shows calculation results for all the nutrient groups that exist in the system. You can display the values as follows:
In relation to the ingredients for a selected nutrient group
This display contains all the information about the nutrients in the ingredients.
In relation to the composition of all the nutrients in the selected nutrient group
This display contains information about the nutrients that are in the recipe and from which the system determines the
nutrient composition of the primary output.
You can change the information that is displayed as follows:
Change the quantity for which the values are calculated
Change the rating and the validity area. In doing so, you determine which data records the system uses from
speci cation management for the calculations.
Change the process loss or storage loss
Select which nutrient information is displayed from all the nutrient groups that exist in the system
Diets
3/31/2019
This view shows calculation results for all diet groups de ned in the system. You can display the values as follows:
In relation to the ingredients for a selected diet group
This display contains all information about the diet suitability of the ingredients.
In relation to the composition of all diets in the selected diet group.
This display contains diet-relevant information about all the substances that are in the recipe and from which the system
determines the diet suitability of the primary output.
You can change the information that is displayed as follows:
Change the rating and the validity area. In doing so, you determine which data records the system uses from
speci cation management for the calculations.
You can select which dietary information is displayed from all the diet groups that exist in the system.
Allergens, Genetically Modi ed Ingredients, Religious Certi cates
The same information applies for these views as for the Diets view.
Costs
Here you can see the costs for a certain output quantity.
The system determines the costs according to the priority speci ed in Customizing. In the view, you can retroactively choose
one of the following price types for each item:
Estimated price from the property tree of the speci cation
Prices available in the material master
To calculate the material price, the system also takes into account the plant speci ed in the calculation parameters.
Manually entered price if the data is not lled or you want to calculate with other values
Note
This manual editing is not saved in the database.
To use this feature, you have to enable manual price calculation by adding price ID MAN_PRICE to Customizing activity
Logistics — General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
Development Recipe Calculation-Relevant Views Make Settings for Costs View .
You can use the Reset Calculation button to cancel this selection and return to the cost calculation that uses the price types
speci ed in Customizing.
If you want to use very small values for unit price (for example, 0,00005 EUR/g), then the system warns you that it may not
calculate the estimated price properly with the standard cost calculation. In this case, we recommend that you use the oating
price calculation described in the documentation for Customizing activity Logistics — General Product Lifecycle Management
(PLM) PLM Web User Interface Recipe Development Recipe Calculation-Relevant Views Make Settings for Costs View .
Nutrient Loss Calculation
This view behaves similarly to the Nutrients tab, however process loss and storage loss are calculated on the item level. You can
save separate process loss pro les for each output stream, as well as the primary output. Storage loss pro les can only be
3/31/2019
saved for the primary output. Process loss and storage loss pro les are speci cations with their own speci cation type. The
calculation considers the loss pro les on lower levels of the recipe explosion hierarchy.
The Nutrient Loss Calculation tab of a formula item's details area displays loss information for the selected item. The Nutrient
Loss Calculation subtab under Calculation Results shows the values calculated for the primary output.
For more information on this hierarchical nutrient loss calculation, see SAP Note 1829406 .
Integration
You can transfer the data of the individual views to the primary output speci cation or an output stream’s speci cation (see
Transfer of Calculation Results).
Process Loss and Storage Loss

Use
In the Nutrients and Nutrient Loss Calculation views, you can calculate the nutrient losses that arise during the recipe process
or during storage.
Prerequisites
You have created speci cations of the type process loss pro le and storage loss pro le that contain the process loss or storage
loss percentage for the relevant nutrients.
You have entered the speci cation type and the value assignment type of these pro les in Customizing for the recipe
calculation that you use for nutrient calculations.
Features
You can choose from all speci cations available for process loss and storage loss that belong to the speci cation types
set in Customizing in the following places:
In the Nutrients view on the Calculation Results tab
In the detailed view of the formula item (this view calculates on the recipe level)
When you have chosen a value for process loss or storage loss, the system automatically calculates the values of the
nutrients displayed (if a loss has been de ned for them), and enters these into the corresponding elds.
You can set process loss and storage loss pro les on item level in the Nutrient Loss Calculation area of the formula
item’s detailed view. Process loss is valid for output streams and primary outputs, while storage loss is de ned only for
primary outputs.
You cannot set a process loss pro le to an output stream with a component type that has an explosion stop set. See
Customizing for Recipe Development under Logistics — General Product Lifecycle Management (PLM) PLM Web User
Interface Recipe Development Recipe Calculations De ne Explosion Scopes and Assign Component Types .
In the Nutrient Loss Calculation view on the Calculation Results tab only the primary output’s loss calculation appears.
For more information about the difference between the two nutrient loss calculations, see SAP Note 1829406 .
Documents
3/31/2019
Use
Depending on the requirements of your enterprise’s processes, you may want to add extra information or explanation to your
recipes or building blocks. For example, you could add a con rmation document from authorities when you release a recipe. This
information is often in different formats, such as text, graphic, video, or others. The document can be object-speci c, however
you can choose to apply it to more than one object, such as several building blocks.
To store the information centrally, use Document Management and the document type RMS (recipe document). These
documents can then be linked to the recipe or building block objects, and have all the data formats handled by Document
Management.
Note
If you want to allow further document types to be used with your recipes or building blocks, you can do this in Customizing
activity Cross-Application Components Document Management Control Data De ne Document Types .
Once you have assigned a document to a recipe or building block (or vice versa), you can display and print the assigned
document and its original application les from the object itself, if a viewer program is available.
Integration
The system can assign documents to recipes or building blocks by having an object link between the object type and the
document type. Between building blocks and the document type RMS you can de ne the object link with the object /PLMB/RBB
(building blocks). For recipes, the object link is created through the object /PLMB/RCP. You can make settings for this link
assignment in Customizing for Document Management in the activity De ne Document Types.
The transaction CV02N - Change Document displays a document's assignments to recipes and building blocks separately
because they exist through different object links.
Features
Status
If a recipe or building block is in status Released (that is, the attribute LOCKED_FOR_CHANGE is assigned to this status), then
you cannot modify its document assignment. For example, if a building block is in status Released, you cannot remove the linked
document from it. This is also true for the recipe object.
However, you can still enable the editing of the document assignment if the DOC_CHANGE_ALLOWED attribute is assigned to a
speci c status of the object. This attribute has to be de ned together with the attribute LOCKED_FOR_CHANGE.
Note
You can only assign the DOC_CHANGE_ALLOWED attribute to a speci c status if you run the report in Customizing for Status
and Action Management, under Logistics - General Product Lifecycle Management (PLM) PLM Web User
Interface Recipe Development Recipe Status and Action Management Collect Object Types and Assigned Attributes .
The status of individual recipes or building blocks is visible in the CV02N - Change Document transaction and on the DMS Web
User Interface.
Activities
To add new document links to building blocks, make sure that you have checked Customizing activity Maintain Key Fields under
Cross-Application Components Document Management Control Data .
3/31/2019
You can also assign documents to building blocks from the context-sensitive help of the application.
More Information
Document Management
Document on the Web UI
Status and Action Management on the Web UI
Classi cation in Recipe Development

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)
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
Recipe Editing
Use
3/31/2019
This process describes how recipes are typically worked on in Recipe Development. The process covers the steps from creating
a recipe to its release by the decision-maker responsible.
Note
Depending on the authorizations you have been granted, it may be the case that you can edit only formula data or only
process data. For more information, see Different Authorizations for Formula Developers and Process Developers. This
process assumes that you have all authorizations as recipe developer.
Prerequisites
You have created the primary output and substances used as speci cations with the relevant properties.
You have made the relevant settings in Customizing under Logistics General Product Lifecycle Management (PLM) PLM Web
User Interface Recipe Development Recipe .
Process
1. You create a recipe for a primary output and specify the recipe type.
If a recipe already exists for the primary output, you create a new alternative recipe or a new version of the existing
alternative recipe.
You can also copy an existing recipe, as well as and make use of existing processes by loading building blocks or importing
full or partial recipes (see Reusing Building Blocks and Recipes).
2. If you want to restrict the validity, you can enter validity data (see Recipe Validity).
3. You create language-dependent description texts and assign documents (see Documents).
4. You create the formula with all required input and output substances.
Note
Depending on your authorizations, it may be the case that you can only change formula data or process data.
5. You (or a recipe developer) edit the formula (see Formula Editing) and optimize it (see Formula Optimization).
6. The system determines the input substances relevant to the calculation. To do this, it explodes the recipe and all recipes
that were found for the input substances over multiple levels (see Explosion).
7. The system determines the calculation results for the calculations de ned in Customizing (see Calculations).
8. You check the calculation results (see Calculation Results).
9. If the calculation result does not meet the requirements, edit the formula again until the results are optimal.
10. If you want to determine how different explosions impact the recipe data, perform a simulation (see Simulation).
11. If the recipe type allows a process, create the process (see Process).
12. You (or a process developer) edit the process (see Process Editing).
13. You (or a formula developer) assign the formula items (see Formula Editing).
If a recipe type allows streams but not processes, you can assign process stages to the formula items, but not activities
or actions (see Streams).
14. You check if the recipe is consistent (see Consistency Check).
3/31/2019
15. You transfer the calculated recipe data to the speci cation of the primary output or, if it exists, of an output stream (see
Transfer of Calculation Results).
16. You save recipe properties in a property speci cation (see Property Speci cation)
17. You nish editing by changing the status (see Status Schemes for Recipes).
18. If you want to create a material BOM for production from the recipe, create a material BOM using Guided Structure
Synchronization (see Synchronizing a Recipe with a Manufacturing BOM).
19. If you want to synchronize a PLM recipe with a PP-PI master recipe, see Synchronizing a Recipe with a Master Recipe.
Formula Editing
Use
The system determines the calculation results automatically from the formula data using the calculations speci ed in
Customizing and the calculation parameters.
You can change the formula data in the Input and Output subview of the Formula view; the system then adapts the calculation
results automatically straight away.
Note
Depending on the authorizations you have been granted, it may be the case that you can only edit formula data or only
process data.
You can use different calculation modes for intraformula calculations, for example total solids or evaporation/absorption. See
Calculation Modes.
Features
Inserting or Deleting a Formula Item
You have the following options for inserting a formula item:
You enter the data of the new item in an empty row at the end. You have to enter at least the speci cation and the
quantity. The system uses the data speci ed as the default in Customizing for the unit of measure and component type.
If you assign a speci cation that is assigned a material, the system transfers the material for plant-independent recipes
automatically. In the case of plant-dependent recipes, the system only transfers the material if the material is likewise
assigned to this plant. If it is not assigned to the plant, you can enter this manually, but the recipe is no longer consistent
then (see Consistency Check).
To insert a new item at a certain position, select the row below the row you want to use and choose the Insert
pushbutton.
Note
You can only insert an item between two items between which at least one empty item number exists. If there is not
an empty item number, execute the Renumber Items function rst.
3/31/2019
You copy one or more rows and change the data. To copy rows, select them and choose Copy. You then select the row
above the row in which the copied rows are to be inserted and choose the Insert pushbutton.
To delete one or more process elements, select them and choose the corresponding pushbutton.
Renumbering Formula Items
When you choose this function, the system renumbers the formula items as follows:
The item that contains the primary output always has the item number 1; you cannot change this number.
All other numbers are renumbered in the speci ed order in steps of 10.
You use this function, for example, if you have inserted formula items between other items or you want to insert an item at a
position at which no empty item numbers exist.
Using Alternative Items
You can create alternatives for items and assign other speci cations and other materials to them. You cannot change other
alternative data.
You can show and hide alternative items in the Formula view.
You can create alternatives for the following items:
Inputs
If you want to allow substances as alternatives for an input substance, you can create alternative formula items with the
same item number. You have to select an alternative as Alternative Used for every item number.
Note
If a formula contains alternative items, the system only considers the item marked as Used Alternative into account during
calculation or during explosion. When synchronizing a recipe with a material BOM, however, you have the option of choosing
between the existing alternatives (see Synchronizing a Recipe with a Manufacturing BOM).
Primary outputs
If the recipe type allows it, you can also specify alternative items for the primary output formula item, for documentation
purposes. To do this, choose More Add Alternative for Primary Output .
You cannot mark this alternative as Alternative Used, since the primary output is always de ned by the recipe.
Scaling Formula Quantities
You can adapt the quantities of all items to a particular quantity of a selected input or output item that is not a stream. To do
this, select the item and choose Scale Quantities and enter the target quantity for this item. The system then scales the
quantities of all other items accordingly.
Calculating Quantities from Other Items
If you select the Calculate Quantity checkbox for an item, the system calculates the quantity of this item according to the
quantities of the other items.
Creating Speci cation
3/31/2019
If no speci cation exists yet for a formula item, you can create one from the formula editing and use it immediately in other
formula items. The system will save the speci cation as soon as you save the recipe.
To do this, choose More Create Speci cation .
Transferring Calculated Values to Output Item
You can transfer the calculated values to the speci cation of the primary output or of an output stream (see Transfer of
Calculation Results). To do this, choose Transfer to Primary Output or More Transfer to Output .
De ning Explosion Path for Item
If a speci cation is assigned to an item that is the primary output of other recipes, you can de ne which recipe the system uses
during explosion. To do this, enter the recipe in the Explosion Recipe column. If a recipe is entered here, the system considers
only this recipe during the explosion of the formula item (see Explosion).
Reloading Master Data
If master data (such as a speci cation or a material that the system uses to calculate the recipe data) was changed in the
database while you had the recipe open for processing, the recipe data is no longer current. This can be the case, for example, if
you navigated via the context menu from the recipe to a speci cation and changed data there.
For the system to recalculate the recipe data based on the changed master data, choose Reload Master Data.
Displaying and Changing Formula Data for Multiple Recipes
You can display and change formula data for multiple recipes simultaneously (see Display and Change of Multiple Recipes).
Linking Formula Items with Process Elements
If the recipe type allows a process, you can assign the process elements de ned in the process to the formula items in the
Formula view.
If the recipe type does not allow a process but does allow streams, you can create level numbers on the Process view and then
assign these to the formula items on the Formula view. You can only change further process data if you also have the
authorization to change these and if the recipe type allows a process.
If the formula contains streams, the Source column in the formula for the input stream indicates on which stage the associated
output stream is produced.
Assigning Formula Items to a Different Stage
You can change the stage assignment for input items and secondary outputs, by entering the new stage in the corresponding
column. If alternatives exist for this item, the system likewise transfers these to the new stage. The system reassigns the item
number according to the new assignment.
For other output items (primary outputs and output streams), choose More Move Output . In the resulting dialog box, specify
the stage to which the output is to be assigned. You can also choose whether further existing items are also to be moved to the
source stage, or if they are to stay in the original stage. The system checks whether an output stream already exists on the
target stage. If this is the case, the system automatically deletes this stream and all associated input streams.
Showing and Hiding Item Details
You can display the exact data for each formula item below the formula in Formula view.
You can see the calculation results for the relevant formula item here in addition to the general data (see Calculation Results).
3/31/2019
Selecting and Changing the Layout
You can de ne different layouts for the table display of the formula in Customizing. For example, you can use a layout for logistic
data. You can then switch from one layout to another in the Formula view. If you change the layout, the user-speci c changes
and table display are lost and the system only displays the columns of the layout you selected in the order de ned there.
Displaying Formula Items in the Process Structure Tree
The system displays formula items in the process structure tree if you select the corresponding checkbox after choosing
Content Settings on the Process tab. You can specify whether formula items are displayed by default in Customizing activity
De ne Process Structure, under Recipe Development Recipe Process .
Additional Features for Formula Editing
Automatic Formula Item Update (SAP Note 1987071 )
Material F4 help on the Formula (SAP Note 1962103 )
Calculation Modes
Use
You can select the calculation mode you want to use on the Formula tab of a recipe in the Calculation Mode column. This setting
determines which cells are read-only and which cells are editable, as well as the position of the Calculate Quantity checkbox.
The standard delivery contains the following calculation modes:
Normal
Total Solids
Evap./Abs. with Total Solids
Evaporation/Absorption
See the relevant sections in this chapter for a description of each calculation mode.
Prerequisites
You can only use total solids calculation if you do the following:
Set the Total Solids or Evap./Abs. with Total Solids calculation mode for each formula item that takes part in the
calculation
Give the total solids percentage property value in the input items' speci cations
Output stream speci cations are not considered during these special scenarios.
To use the evaporation/absorption calculation mode with or without total solids, you have to de ne the balancing item by
performing the following steps:
1. Create a speci cation or a material for the balancing item. Enter a value for Density.
If you use a material as balancing item, provide the unit of measure conversion values.
2. In the SAP Menu, go to Logistics Production — Process Recipe Development Balancing Item Maintenance .
3. Create a new entry for each recipe type and calculation mode that you want to use.
3/31/2019
Note
You can use the <*> symbol to make settings for all recipe types.
4. Enter the name of the speci cation, and add the material if needed. If the Unit of Measure eld remains empty,
then the default value is used. This default value is set in Customizing activity Logistics — General Product
Lifecycle Management (PLM) PLM Web User Interface Recipe Development Recipe De ne Allowed Units of
Measure .
5. Save your entry.
6. Set which calculation mode should be available for which recipe type in Customizing activity Logistics —
General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
Development Recipe Calculations De ne Allowed Calculation Modes .
We recommend if you use one of these calculation modes that you create a new layout for the formula view in
Customizing for Recipe Development under Recipe De ne Layouts for Formula Views and select the following columns:
ICON, POSNR, ITEM_TYPE, SUBID, SUBST_IDENT1, COMP_TYPE, QUANT, UOM, TOTAL_SOLID,
TOTAL_SOLID_PCT, CALC_TYPE, IS_BALANCING_ITEM.
Features
Normal Calculation
This is the basic calculation mode that calculates quantity without any special scenarios.
Note
The normal calculation mode is the minimum scenario, therefore it appears in dropdown lists as a blank line.
Total Solids Calculation
If you choose the Total Solids calculation mode to formulate the recipe, you can calculate the total solids mass from bottom to
top in the whole recipe.
You have two directions for the calculation:
Give the input quantity of an item: the system calculates the total solids mass from the total solids percentage value of
that item.
Give the required total solids mass of an input item: the system calculates the required input quantity from the total
solids percentage value of that item.
The system calculates total solids mass and percentage for all output streams and the primary output as well if you have
provided values for all their items.
Evaporation and Absorption with Total Solids
It can occur in a process that water or another substance in a formula is evaporated or absorbed, and thus the quantity of the
input does not exactly match the quantity of the output. This is represented with the balancing item which shows how much of a
substance is evaporated (negative value) or absorbed (positive value). Using the Evap./Abs. with Total Solids calculation mode
you can calculate this balancing item besides total solids. In this case the Calculate Quantity checkbox is automatically set for
the balancing item.
You have the following options:
3/31/2019
Give the input and output quantity of a stage or the whole recipe: the system calculates the evaporation/absorption
quantity.
Give the target total solids percentage of a stage or the primary output: the system calculates the output quantity and
the evaporation/absorption quantity.
Total Solids-Independent Evaporation/Absorption
This calculation mode is the same as described in section Evaporation and Absorption with Total Solids, except that total solids
are not calculated. Therefore you only have the option to give the input and output quantity of a stage or the whole recipe, and
the system calculates the evaporation/absorption quantity.
More Information
To create more calculation modes, see the Customizing activities for Recipe Development under Logistics — General Product
Lifecycle Management (PLM) PLM Web User Interface Recipe Development Recipe Calculations Business Add-Ins (BAdIs) .
Display and Change of Multiple Recipes

Use
You can use this function to display and change recipe data for multiple recipes simultaneously.
Note
If you change data, you can only save these changes for all loaded recipes simultaneously.
The following recipe views are available:
Formula (see Formula)
This view contains all input and output substances available in the selected recipes.
It does not display streams or alternative input substances; it only displays the alternative formula items that are
marked as used.
Calculation Results (see Calculation Results).
This view contains the calculation results for the calculations de ned in Customizing for all selected recipes. You can
display and compare the data.
Features
Recipe Selection
You can call and change the selection of the recipes at any time by using the corresponding pushbutton. You can add or delete
recipes from the selection.
Sorting of Input and Output Substances
The recipe that was selected during the call of the function, for example in the object navigator, determines the sorting of the
input and output substances. If several recipes were selected during the call, the system uses the rst one in the list for the
sorting. Even if you load or delete recipes later on.
3/31/2019
Changeability Overview
During selection of the recipes, the system checks to what degree you can change them.
You cannot change a recipe in the following cases:
The recipe contains streams.
The system does not display output streams in this application.
The status of the recipe does not allow changes.
The recipe is marked for archiving.
The recipe is currently locked.
If the recipe type of the recipe allows streams but no streams existed until now in the recipe, you can change all data except for
the stage number.
Formula
The Formula view contains a list of the following ingredients:
All ingredients that exist in the rst recipe
All additional ingredients that exist in the remaining recipes
Each ingredient has the following data:
Sort number
Assigned speci cation with description
Item type
Component type
Assigned material with description
For each recipe, the quantity with unit and stage number
Note
The system does not display speci cation data or material data in the row for the primary output; it only displays the
quantity, because not all selected recipes have to have the same primary output. The primary output is contained in the
respective column header as part of the recipe identi cation.
If the recipes are changeable, the following further functions for formula processing are available:
For every formula item, you can display the details and calculation results for that item, as on Input and Output view for
individual recipes.
You can add or delete rows.
You can move rows and renumber the formula items.
If you save the changed sequence, the system copies the sequence to the item numbers in the recipe formula.
You can create speci cations.
3/31/2019
You can remove single items from individual recipes by setting that item’s quantity to zero and removing its unit of
measure. If you remove all the item’s assignments from all recipes, the system does not show the ingredient itself.
Calculation Results
All calculations de ned in the system have their own view, on which you can compare the calculation results for all loaded
recipes. You can only change the data if you change the formula data or the calculation parameters.
For the calculation results for ingredients and for standard composition, you can switch between a hierarchical display and a
tabular display.
The hierarchical display depicts the ingredients in the hierarchy levels determined through explosion (see Explosion). You can
expand or collapse the different levels.
Note
If reuse occurs, you cannot use the hierarchical display.
Copying of Recipes
You can copy new recipe alternatives to recipe versions. You can also create multiple versions at the same time. Following the
copying, the system displays new recipes at the bottom of the table.
Activities
You have the following options for calling multiple recipes simultaneously:
You select the function from the control center or from the work center for recipes.
First, the entry screen is displayed, where you can select recipes.
In a personal worklist, you select one or more recipes and choose Display Display Multiple Recipes or Edit Change
Multiple Recipes .
In the search results, you select one or more recipes and choose Additional Functions Display Multiple Recipes
In the object navigator, you select a recipe and choose Additional Functions Display Multiple Recipes .
In recipe processing, under You Can Also, you choose Display Multiple Recipes or Change Multiple Recipes.
Formula Optimization
Use
You can use formula optimization to optimize the quantities of formula items that are assigned to a process stage on which the
primary input or an output stream is produced.
For each output, you can choose whether you want to optimize a particular ingredient or a property.
If the recipe does not have a process and thus contains only one stage, the optimization considers all formula items.
Caution
If reuse occurs within a stage, you cannot use optimization.
3/31/2019
Features
Choosing an Output Substance
You can run optimization for either the primary output or an output stream. You can change the quantity of this output
substance in the optimization. The system then automatically adjusts the quantities of the dependent input items within the
optimization. You can then transfer the quantities to the formula.
De ning Target Function and Constraints
In the target function, you determine which values the system runs optimization for. You can choose either a formula item or a
property that is relevant for calculating the nutrients or costs.
You can maximize or minimize this variable through the optimization.
In addition, you can de ne the following further constraints that optimization is to consider:
For properties, you can choose the following constraints:
Minimum value or maximum value
Minimum value and maximum value
Fixed target value
For every property, you can also choose whether it is to be optimized for all formula items or just for those formula items
selected for optimization.
For ingredients that are used as formula items, you can de ne relationships.
For formula items, you can choose the following constraints:
Minimum or maximum value for the quantity
Minimum and maximum value for the quantity
Fixed target value
Choosing Items for Optimization
You can choose which items you want to run the optimization for. The system displays the formula items of the stage that
produces the selected output. You can choose one or several assigned items. You then press the pushbutton Optimize Marked
Items to start the optimization.
Transferring Optimized Values
After the optimization run, the system displays the optimized values. If you want to copy the optimized quantities or the upper
and lower limits used in the optimization, choose Transfer Results to Formula.
Recommendation
The formula optimization might possibly change data relevant for consistency. You should therefore run a consistency check
after you have transferred the optimized values.
Explosion
Use
3/31/2019
When it calculates the recipe data, the system checks whether more recipes exist for an input component that produce this
substance. If the system nds recipes, it explodes the corresponding formulas over multiple levels.
In the explosion, the system takes into account all recipes that meet the following requirements:
The user has the necessary authorizations for the recipe.
The recipe is valid on the key date.
The recipe has either the same recipe purpose or a recipe purpose that is contained in the related sequence (see Recipe
Purpose).
The recipe is not marked for deletion or archiving.
The recipe has a status that is relevant for the explosion (see Status Schemes for Recipes).
Caution
The system does not take recipes from Recipe Management (PLM-RM) into account.
Prerequisites
In Customizing for Environment, Health and Safety, you have carried out the activity Basic Data and Tools Speci cation
Database Structure Specify Component Types for Compositions .
You have carried out the following activities in Customizing for Recipe Development:
Recipe Calculations De ne Explosion Scopes and Assign Component Types
Recipe Calculations De ne Recipe Calculations
Features
Explosion Scope
The following explosion scopes are de ned in the standard system:
Logistic explosion
The logistic explosion includes scrap that occurs in production in the calculation.
Scienti c explosion
The scienti c explosion includes all chemical and physical properties of the substances used.
Explosion for synchronization recipe to material BOM
Explosion Recipe
If you have entered an explosion recipe in the formula for an item, the system uses this recipe for the explosion of the
associated substance.
Note
If you want to manage development recipes, see Development Recipe.
Explosion Stop
3/31/2019
The explosion stops in the following cases:
The system can no longer nd any producing recipes for a component in an explosion-relevant status for which the user
has authorization.
The Customizing settings for the corresponding component type specify that the component is not exploded any further.
This makes sense for some components that are created by a reaction, for example. The system cannot calculate the
corresponding values for these components mathematically from the input substances. In the case of a substance whose
component type is not explosion-relevant, the system uses the substance composition that is speci ed in the property
tree.
Reuse occurs.
Reuse occurs if an output component is used as an input component in the current recipe or in a recipe that is obtained
through explosion of the current recipe.
Explosion Logs
When the system performs a calculation for which the recipe is exploded, it writes all the steps it carried out to the explosion
log. You can display different views for each calculation type. Views for which no calculation has been performed yet, are empty.
The explosion log contains a table of all input substances the system determined during the explosion. You can show and hide
the ingredients that were determined for input substances produced by another recipe.
If the system determines multiple recipes for an input substance, it displays all recipes. You can also display the non-used
recipes, by choosing the Display Non-Used pushbutton.
The system displays at most the following data for each speci cation found in the explosion and for each recipe:
Description
Recipe type
Whether the recipe is used
Stage number
Formula item number
Description of the item type
Whether reuse occurs
Description of the component type
Whether the explosion was stopped
Material with description
Quantity and unit
When you select a row in the explosion log, the system shows all messages issued for this item in the lower screen area.
More Information
Explosion Process
Explosion Process
3/31/2019
Use
This process describes how the system proceeds in a multilevel explosion of a recipe.
The recipe with which the system starts the explosion is called the "start recipe" in the explanations that follow.
The system executes this process whenever you choose a view that contains calculation results in a recipe. This can be a view
under Calculation Results or a detail view for a formula item in the Formula view.
Note
If the recipe type of the recipe allows streams, the system then also explodes the recipe when you call the Input and Output
formula view.
If the input substance cannot be exploded any further, the system uses the data speci ed in the speci cation for this substance
for the calculations.
Prerequisites
In Customizing for Environment, Health and Safety (EH&S), you have processed the activity Basic Data and Tools Speci cation
Management Speci cation Database Structure Component Settings Specify Component Types for Compositions .
You have carried out the following activities in Customizing for Recipe Development in PLM Web UI:
Recipe Calculations De ne Explosion Scopes and Assign Component Types
Recipe Calculations De ne Recipe Calculations
Process
1. The system determines the calculation de ned for the selected view and the relevant explosion scope.
The explosion scope speci es which component types are relevant to the explosion and at which component types the
explosion stops.
2. The system determines the recipe's input substances, whose component type is relevant for the explosion scope.
The system carries out the following checks for each input substance:
a. Has the setting been made that the explosion stops at this component type?
If so, the input substance is not exploded any further.
b. Is the input substance produced by a single or multiple recipes?
If the system does not nd a recipe, the input substance is not exploded any further.
If the input substance cannot be exploded any further, the system ends the explosion for this substance and carries on
with the next input substance.
If the system determines one or more recipes for a substance, it starts checking these recipes.
3. The system checks the recipes that were determined as follows:
a. Is an explosion recipe speci ed for the formula item?
If yes, the system uses this recipe for the associated substance and explodes the recipe further.
b. Do recipes exist for which the user who is logged on does not have the necessary authorizations?
3/31/2019
If yes, the explosion stops.
c. Do valid recipes exist for the key date of the start recipe?
If not, the explosion stops.
d. Do recipes exist that have the same recipe purpose as the start recipe or that have a recipe purpose that is
assigned to this start recipe in sequence in Customizing?
If yes, the system continues checking these recipes in the speci ed sequence of recipe purposes.
If no recipe is found with one of these recipe purposes, the explosion stops.
e. Do recipes exist that have the same recipe type as the start recipe or that have a recipe type that is assigned to
this start recipe in sequence in Customizing?
If so, the system continues checking these recipes in the speci ed sequence of recipe types.
If no recipe is found with one of these recipe types, the explosion stops.
f. Do recipes exist that have an explosion-relevant status?
If not, the explosion stops.
g. The system continues the explosion of the recipe determined here for the input substance in the same way as for
the start recipe.
3/31/2019
Explosion Process
3/31/2019
Result
In a multilevel explosion of the start recipe, the system has determined all input substances at the lowest level.
In recipe calculations, the system considers all input substances at the lowest level that have a component type that is relevant
to the calculation.
Calculations
Use
The system automatically performs all the calculations you have de ned in Customizing, based on the data entered in the Input
and Output view under Formula when you call one of the following views:
Calculation results for formula items
In the Input and Output view, you can display details of formula items. In the details area, views for the de ned
calculations display the corresponding calculation results for the selected item.
Calculation results for one or multiple recipes
In the Calculation Results view, you see views for the de ned calculations that display the corresponding calculation
results for the whole recipe.
The system uses the following calculation parameters for the calculations:
Calculation Parameter Meaning Default Value
Quantity Base quantity for the calculation of De ned in Customizing for calculations
nutrients and costs with unit of measure under De ne Default Calculation
Parameters
Unit of Measure De ned in Customizing for calculations

under De ne Default Calculation
Parameters
Key Date Key date for the explosion and the If the validity is restricted in the recipe, the
determination of attributes from the valid-from date; otherwise the current date
speci cation or material master
Material Price Type Price type for the cost calculation with De ned in Customizing for calculations
currency determined from the material under Make Settings for Costs View
master
Currency De ned in Customizing for calculations
under De ne Default Calculation
Parameters
Plant Plant for which the material price is De ned in Customizing for calculations
calculated under De ne Default Calculation
Parameters
Validity Area Speci es the validity area for which De ned in Customizing for calculations
speci cations are taken into account under De ne Default Calculation
Parameters
Rating Speci es the rating for which speci cations De ned in Customizing for calculations
are taken into account under De ne Default Calculation
Parameters
3/31/2019
If you want to change the calculation parameters for the displayed recipe, choose Calculation Parameters. If you change the
calculation parameters, the system saves the new settings in the recipe the next time you save it. When you exit the recipe, the
system uses the changed parameters the next time the recipe is called.
Prerequisites
You have made the Customizing settings for Recipe Development under Recipe Development Calculations and Recipe
Development Calculation-Relevant Views .
For all speci cations used, the corresponding data exists in the Recipe Development property tree RM Default Property Tree
for Recipe Management in Web UI.
Features
This section lists the calculations de ned in the standard system.
Note
If you want to use different calculations, follow the instructions under Adapting the Standard System.
Ingredients
The system uses this calculation to determine the ingredients used in the recipe that are necessary to produce the primary
output.
Composition
The system uses this calculation to determine the analytical composition of the primary output and thus describe its properties.
The composition of an output substance is process-speci c. It describes the substance as it is created in the recipe, that is, as
the result of a speci c process. You can de ne the process-independent composition of a substance in the property tree of the
associated speci cation in speci cation management.
The system determines the associated quantities as a proportion in which an ingredient is contained in the current output
substance. To do this, it uses the quantities speci ed in the recipes and compositions. However, the quantity of an ingredient is
only taken into account if it is relevant for the calculation.
If several output substances are assigned to a recipe, the system assumes that the relative proportions of the input substances
are the same for all output substances.
If the system cannot calculate the quantity for a substance, for example, because it cannot convert the units used into one
another, it terminates the calculation.
In case reaction happens, you can use manual composition to adjust the values accordingly. See Manual Composition.
Nutrients
The system uses this calculation to determine the nutrient composition. To do this, it rst determines all the nutrient groups
that exist in the system and then calculates the respective information for the associated nutrients with respect to input
substances and primary output composition.
If you have speci ed corresponding pro les in Customizing, the system also takes into account process losses and storage
losses with respect to nutrients (see Process Loss and Storage Loss).
3/31/2019
Diets
The system uses this calculation to determine the diet suitability.
For every ingredient found, the system rst determines the diet suitability speci ed in the ingredient property tree. This means
that for every ingredient, it determines the speci ed diet substances, and for every diet substance it determines the exception
value that describes the diet suitability in the property tree. If the system cannot determine a diet suitability for an ingredient, it
uses the exception value for this ingredient, which is de ned in Customizing under Assign Exception Values to Speci cation
Types or De ne Default Exception Value.
Based on the exception values speci ed for a diet substance in all relevant substances, the system determines the exception
value that has the highest sequential number in Customizing. This exception value is then the diet suitability of the diet
substance in the primary output.
In addition to the calculated diet suitability, the system also displays the diet suitability that is saved in the property tree for the
primary output, in the diet composition. In addition, the system shows the limit value that you have de ned for a given diet
substance.
Allergens, Genetically Modi ed Ingredients, Religious Certi cates
As in the Diets view, the system determines the exception values from the corresponding property tree of the substance
speci cations.
Costs
The system uses this calculation to determine the costs of the primary output in relation to an output quantity. The system
calculates the costs from the prices of materials or speci cations that are assigned to the input components and output
components. You de ne the associated priorities in Customizing. You can also enter the price data manually, but manual price
values are not saved in the database.
If you want to use very small values for unit price (for example, 0,00005 EUR/g), then the system warns you that it may not
calculate the estimated price properly with the standard cost calculation. In this case, we recommend that you use the oating
price calculation described in the documentation of Customizing activity Logistics — General Product Lifecycle Management
(PLM) PLM Web User Interface Recipe Development Recipe Calculation-Relevant Views Make Settings for Costs View .
In the Costs view, you can choose which price type you want to use for each item. The following price types can be selected:
Speci cation price
This price data is taken from the speci cation of the item.
Material price
This price data is taken from the material assignment of the item. When calculating the material price, the system also
takes into account the plant speci ed in the calculation parameters.
Manual price
If neither the speci cation nor the material contains price data but you still want to calculate an estimated price, you can
enter price data manually and the system calculates with the provided values.
Note
This manual input is not saved in the database.
To use this functionality, you have to enable manual price calculation by adding a new price ID MAN_PRICE to
Customizing activity Logistics — General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
3/31/2019
Development Recipe Calculation-Relevant Views Make Settings for Costs View .
The system calculates the costs of that individual item in the details view for the formula item.
Nutrient Loss Calculation
This view behaves similarly to the Nutrients tab, however process loss and storage loss are calculated on the item level. You can
save separate process loss pro les for each output stream, as well as the primary output. Storage loss pro les can only be
saved for the primary output. Process loss and storage loss pro les are speci cations with their own speci cation type. The
calculation considers the loss pro les on lower levels of the recipe explosion hierarchy.
The Nutrient Loss Calculation tab of a formula item's details area displays loss information for the selected item. The Nutrient
Loss Calculation subtab under Calculation Results shows the values calculated for the primary output.
For more information on this hierarchical nutrient loss calculation, see SAP Note 1829406 .
Manual Composition
Use
During a process components can enter into reaction with each other; for example, some or all of a material disappears, new
materials are created, and so on. Manual composition helps users follow these changes, because quantities can be adjusted
manually. You can make this adjustment in the following places:
On the Composition tab of the Formula details view
In case of primary output, also the Calculation Results tab
Prerequisites
To see the corresponding buttons and columns, you have to use a recipe type that allows manual composition. See
Interface Recipe Development Recipe De ne Recipe Types .
To edit the Adjusted Quantity [%] column, you have to use a component type that allows manual composition. See
Interface Recipe Development Recipe Calculations De ne Explosion Scopes and Assign Component Types .
Note
To edit the primary output's composition manually, you have to select both the Man. Comp and the Prop. Spec
checkboxes in this Customizing activity. For editing an output stream's composition, only the Man. Comp checkbox is
required.
Activities
The manually entered values are not saved with the recipe; you have to transfer the values to speci cations. You can choose
between the following options:
Manually transfer the values to the output stream, primary output, or property speci cation. For more information, see
Transfer of Calculation Results.
Set the auto-transfer (see section Automatic Transfer of Composition Values).
3/31/2019
Note
You cannot transfer values to the primary output speci cation automatically.
Automatic Transfer of Composition Values
Automatic transfer (auto-transfer) can be set in Customizing activity De ne Recipe Calculations; see Customizing for Recipe
Development under Logistics — General Product Lifecycle Management (PLM) PLM Web User Interface Recipe
Development Recipe Calculations . In this activity, select the COMPOSITION calculation ID and navigate to the Standard
Composition folder.
If auto-transfer is set, then the manually entered values are buffered. Thus, when you save the recipe the system transfers
values automatically to the appropriate speci cation. The following options are possible:
Output stream values are transferred to the output stream’s speci cation
Primary output values are transferred to the property speci cation
Note
If no property speci cation exists for the recipe, the primary output's modi ed values cannot be transferred
automatically.
Simulation
Use
When the system calculates recipes, it automatically explodes the corresponding input items over multiple stages (see
Explosion).
You can use simulation to check how the calculation results change if you select alternative explosions for input items.
To do so, you de ne explosion simulation rules in a simulation model for any number of speci cations. You can then apply this
model to a recipe.
Features
Simulation Rule
In a simulation rule, you de ne either an explosion stop for a speci cation, or you select one of the recipes that produces this
speci cation as the explosion recipe. In the simulation, you can also use recipes that do not have an explosion-relevant status
and thus cannot be used in the standard explosion (see Status Schemes for Recipes).
You can de ne simulation rules either for selected speci cations directly, or via a simulated explosion of a particular recipe.
Note
If the system does not determine any recipe for a speci cation that can be exploded, the explosion always stops (see
Explosion Process). However, you can create a rule for this speci cation that de nes an explosion stop. In this way, you can
prevent newly-created recipes from being exploded when the model is used again at a later point in time.
De ning Simulation Rules for Any Number of Speci cations Directly
3/31/2019
You can de ne simulation rules for selected speci cations directly in the simulation model in the Simulation Rules view, on the
Explosion Simulation tab page.
You have the following options for adding rules:
You enter a speci cation in an empty row directly and de ne the associated rule.
You copy all speci cations that are used in a recipe for input items, and then de ne the associated rules.
If a rule has already been de ned for a speci cation from this recipe in this simulation model, the system does not copy
this speci cation again.
You copy rules from an existing simulation model.
If a different simulation model contains rules for speci cations, for which rules have likewise been de ned in the model
currently being edited, you must decide if the system keeps the current rule or replaces it with the copied rule.
De ning Simulation Models Through Explosion Path Simulation
In the Simulation for Explosion Path view, on the Explosion Simulation tab page, you can perform a multilevel explosion of the
recipe for every recipe calculation de ned in the system. The system then determines all of the speci cations used in the recipe
and displays these hierarchically.
If a rule was already created for a speci cation in the Simulation Rules view, this is applied directly and the row of the associated
speci cation is marked accordingly.
For every speci cation, you can likewise in this view create a new rule or change or delete an existing rule. If the simulated
explosion path changes as a result, the system adjusts the display.
The system copies every rule that you de ne in this view to the Simulation Rules view. You can edit or delete rules in this view as
well.
Applying Simulation Model to a Recipe
In recipe processing in display mode, you can activate the simulation and load a simulation model. The system then applies the
rules automatically to the speci cations that exist in the recipe and redetermines the calculation results.
Note
If the simulation model contains rules for speci cations that are not used in the recipe, the system ignores these rules. As in
the standard explosion, the system explodes items with speci cations for which no rules are de ned.
In the explosion log, you can identify where the modeled explosion deviates from the standard explosion.
Activities
To create a simulation model, in recipe processing choose Related Links Create Simulation Model , to change or display the
corresponding option.
To activate the simulation, in display mode choose Activate Simulation and select a simulation model in the resulting dialog
window.
If you have changed the simulation model and want to reload it, or if you want to use a different simulation model, choose Load
Simulation Model during active simulation.
To end the simulation, choose Deactivate Simulation.
3/31/2019
Example
You have developed a new recipe for an icing in your company. Before you release the recipe, you want to check the effects of
the icing in cake recipes that use it.
To do this, you as recipe developer proceed as follows:
1. You create a simulation model with a rule that says that the new recipe is to be used when exploding the speci cation of
the icing.
2. In the display of the cake recipe, you activate the simulation and load the simulation model you created previously.
3. You check the recipe data of the cake recipe.
4. In the object navigator or using the search function, you determine further cake recipes that use the icing.
5. You call the recipes individually in display mode, and check the recipe data during active simulation with the same
simulation model as above.
6. Once you have checked all cake recipes and have decided that the new icing recipe is to be used, you set the status of
the icing recipe that was used previously to Obsolete. You then release the new recipe and transfer the calculated values
of the recipe to the speci cation of the primary output.
Process Editing
The process contains all the activities that are required to produce a product or different products.
You can edit the process data in the Process view of the recipe.
Note
Depending on the authorizations you have been granted, it may be the case that you can only edit formula data or only
process data.
Inserting or Deleting a Process Element

To insert a new process element, select the header element of the process (the primary output) in the structure and choose the
associated Process Elements view.
You have the following options:
In an empty line, based on the process element type, enter the stage number, operation number, action number, and a
description text. The system automatically sorts the new line accordingly and updates the tree structure.
To insert a new item at a certain position, select the row below the row you want to use and choose the Insert
pushbutton.
Note
You can only insert a process element between two elements, between which at least one empty number exists. If
there is not an empty number, execute the Renumber Elements function rst.
You copy a row and change the data.
3/31/2019
To copy a row, select it and choose Copy. You then select the row above the row in which the copied row is to be inserted
and choose the Insert pushbutton. You then change the data in the new row.
To make use of existing processes, load building blocks or import full or partial recipes (see Reusing Building Blocks and
Recipes).
To delete a process element, select the row and choose the corresponding pushbutton.
Note
If the recipe does not allow a process but does allow streams, you can edit stages.
Renumbering Elements
If you select this function, the system reassigns the stage numbers, operation numbers, and action numbers in steps of 10
respectively.
You use this function, for example, if you have inserted process elements between others or you want to insert a process
element at a position at which no empty numbers exist.
Creating Process Elements Automatically

You can create new process elements (that is, stages, operations, and actions) directly in the Formula view as well as the
Formula Items subtab of the Process view. To do this, enter a new combination of stage, operation and action, and the system
automatically creates the missing items. For example, if stage 10 exists and you enter stage/operation/action 10/5/1
combination, operation 10/5 and action 10/5/1 are created automatically after con rmation.
Assigning and Displaying Process Parameters

In the respective Process Parameters view, you can assign process parameters (PPs) to the entire process or to individual
process elements, to valuate the process run (see Value Assignment of Process Elements by Means of Process Parameters).
The system displays process parameters in the process structure tree if you select the corresponding checkbox after choosing
Content Settings. You can specify whether process parameters are displayed by default in Customizing activity De ne Process
Structure, under Recipe Development Recipe Process .
Checking Assigned Formula Items

In the respective Formula Items view, you can check the existing formula items for the entire process or for individual process
elements.
If you have selected a process, you can also change the assignment. If you have selected a process element, you can assign a
formula item to a subordinate process element.
Assigning Description Texts or Documents

In the respective Descriptions and Documents views, you can assign language-dependent description texts and documents to
the entire process or to individual process elements.
Assigning Equipment Requirements
3/31/2019
In the Equipment Requirement view, you can assign equipment requirements to the entire process or to individual process
elements, to document speci c requirements for further recipe development and later production (see Equipment
Requirement).
Drag and Drop

You can reorganize stages, operations, and actions by dragging and dropping process elements in the process structure tree.
The assignment of operations and actions can also be changed by using drag and drop, however the dependent data (such as
formula, process parameter, EQR and EQR PP) remains with the process elements after reassignment.
Reassigning a Primary Output Speci cation

If a stage has input items, the system can replace the stage’s output stream with the primary output speci cation. If the stage
has no input items, a corresponding output stream is created without input items. In case an input item is taken away, the
output stream is created for a stage that has formula items; otherwise it is completely removed.
Value Assignment of Process Elements by

Means of Process Parameters
Use
To de ne a more detailed process run, you can valuate the entire process or individual process elements by using process
parameters. Process parameters, for example, are boiler pressure or oven temperature.
Prerequisites
If you want to use a process parameter master for the value assignment, you have created this process parameter master
previously (see Process Parameter Master).
Features
In the Process Parameters view of a process or process element, you can valuate with or without reference to process
parameter master data.
Value Assignment with Reference to Process Parameter Master Data
You can valuate one or more process parameter masters to the process or process element.
The system copies the value assignments saved in the process parameter master as default values, which you can then
change.
If a class is assigned to the process parameter master, you can valuate the associated characteristics in the detail view
of the process parameter.
You can assign and valuate every process parameter master more than once.
If a process parameter master is assigned to a process element, the system marks the corresponding entry in the
master data as used. You cannot change the data anymore after that.
Value Assignment Without Reference to Process Parameter Master Data
You can also enter the process parameters directly in the Process Parameters view. In this case, you cannot use any
classes.
3/31/2019
Consistency Check
Use
You use the consistency check to check the recipe data for the whole recipe according to selected criteria, for example if you
have changed data or if you want to change the recipe status.
If the recipe is not consistent, the system issues messages that describe which data caused the inconsistency.
If you change data relevant to the consistency or optimize the formula, you should carry out the consistency check again.
Note
Data in the standard system that is not relevant to the consistency is for example:
Description of the recipe
Linked documents
Recipe purpose
Prerequisites
If you want to use additional individual checks, you can implement the corresponding BAdIs accordingly. You can nd these BAdIs
in Customizing for the PLM Web UI under Recipe Development Recipe Business Add-Ins (BAdIs) BAdIs for Checks .
If you want the system to consider additional checks at status change, implement the BAdI Additional Checks Before Status
Change accordingly. You will nd the BAdI in Customizing under Recipe Development Status Management Business Add-Ins
(BAdIs) BAdI: Additional Checks Before Status Change
Features
The system carries out the consistency check in the following cases:
You start the consistency check manually, by choosing the corresponding pushbutton in recipe processing.
You change the status of a recipe to a status with a status attribute that requires a consistency check (see Status
Schemes for Recipes).
The following status attributes for recipes require a consistency check:
CONSIST_EXPLOSION: Explosion-relevant recipe data is consistent and the recipe is locked for changes.
CONSIST_SYNC_BOM: Recipe data that is relevant for synchronization of the recipe with a material BOM is
consistent and the recipe is locked for changes.
REL_SYNC_BOM: Recipe is relevant for synchronization with a material BOM and is locked for changes, recipe
data that is relevant for synchronization of the recipe with a material BOM is consistent (see Synchronizing a
Recipe with a Manufacturing BOM)
The following check criteria exist in the system:
General Criteria
3/31/2019
If a material and a speci cation have been assigned to the formula item:
Is the material assigned to the speci cation?
Are the total quantities of all input items equal to the total quantities of all output items?
Are the calculated values, in particular the absolute mass, still correct?
Calculated values can no longer be correct, for example, if the relevant data of a speci cation used in a recipe has been
changed.
If a plant is speci ed for the recipe:
Does the assigned material exist in the corresponding plant?
Explosion-Relevant Criteria:
Has the component type been speci ed for every formula item that is not a stream?
Has a speci cation been speci ed for every formula item that is not a stream?
If a stream has a component type that causes an explosion stop: Is a speci cation assigned to the formula item?
Can the quantities speci ed in all explosion-relevant formula items be converted into units of mass?
Synchronization-Relevant Criteria
Has a quantity or an exception value been assigned to every formula item?
Has a material been assigned to every formula item that is not a stream?
If a material has been assigned to the formula item in addition: Do the units of measure used match the assigned
material?
Has at least one input item been speci ed?
The following table indicates which criteria the consistency check uses in which situation:
Criteria Manually-Triggered Check Check at Status Change
General Criteria Always When the status to be set has one of the
following status attributes:
Explosion-Relevant Criteria When the assigned status scheme contains
a status with one of the following status CONSIST_EXPLOSION
attributes:
CONSIST_SYNC_BOM
CONSIST_EXPLOSION
REL_SYNC_BOM
CONSIST_SYNC_BOM
REL_SYNC_BOM
Synchronization-Relevant Criteria When the assigned status scheme contains When the status to be set has one of the
a status with one of the following status following status attributes:
attributes:
CONSIST_SYNC_BOM
CONSIST_SYNC_BOM
REL_SYNC_BOM
REL_SYNC_BOM
Transfer of Calculation Results

3/31/2019
Use
You can transfer the results of the recipe calculations de ned in Customizing to certain speci cations, such as:
Speci cation of the primary output
Speci cation of an output stream, if one exists (see Streams)
Property speci cation, if one exists (see Property Speci cation)
Note
A recipe can only contain output streams and a property speci cation if the recipe type allows this (see Recipe Type).
The system transfers the results to the relevant property of the speci cation in the Recipe Development property tree (see
Property Tree).
You can transfer the calculation results to the primary output speci cation for the following calculation types:
Ingredient listing
Standard composition
Qualitative composition (group-based)
Quantitative composition (group-based)
Quantitative hierarchical composition (group-based)
Costs (logistic calculation)
Intraformula calculations
Prerequisites
You have de ned calculations in Customizing for Recipe Development under Recipe Calculations De ne Recipe Calculations .
The key date of the recipe matches the valid-from date of the recipe.
The speci cation of the primary output to which you want to transfer the data meets the following requirements:
It has the status In Process
You have the relevant authorizations for this speci cation
Features
In the standard system, the calculation results of the default calculations are copied to the properties of the speci cation as
follows:
Calculation ID Calculation Type Description Property
INGREDIENT Ingredient listing Ingredients Composition List of Ingredients
COMPOSITION Standard composition Composition Composition Standard

Composition
3/31/2019
Calculation ID Calculation Type Description Property
DIETS Qualitative composition (group- Diets Composition Diet Suitability

based)
ALLERGENS Qualitative composition (group- Allergens Composition Allergens

based)
GENMODIFICATION Qualitative composition (group- Genetically modi ed ingredients Composition Genetically

based) Modi ed Ingredients
RELIGIOUS Qualitative composition (group- Religious certi cates Composition Religious

based) Certi cates
NUTRIENTS Quantitative composition (group- Nutrients Composition Nutrient

based) Composition
 Note
The system saves the nutrient
data without losses (process
loss or storage loss).
NUTRIENTS-HIER Quantitative hierarchical Nutrient Loss Calculation The loss calculations are
composition (group-based) transferred to different properties,
as follows:
Original quantity and

quantity after process loss
goes to
Composition Nutrient
Composition
Quantity after storage loss

goes to Composition Hier.
Nutrient Comp. after
Storage Loss
COSTS Costs (logistic calculation) Costs Administration Estimated Price
INTRACALCULATION Calculations in formula Calculation in the formula Physical-Chemical Data Density
Activities
To execute the transfers, do the following:
For the primary output, choose the pushbutton Transfer to Primary Output or the pushbutton More Transfer to Output
in the Formula view
For an output stream, choose the pushbutton More Transfer to Output in the Formula view
For a property speci cation, choose the pushbutton Transfer to Property Speci cation in the Basic Data view
The Transfer Calculation Results to Speci cation dialog box displays the data of the target speci cation, which cannot be
changed. You can then select the calculations for which the results should be transferred.
Synchronizing a Recipe with a

Manufacturing BOM
3/31/2019
Use
You can transfer data from an alternative recipe to a manufacturing bill of material (MBOM) with Guided Structure
Synchronization (GSS) (see Guided Structure Synchronization (PLM-WUI-GSS) ).
The MBOM contains the material assigned to the primary output of the recipe as BOM header, and the materials assigned to
the recipe items as items.
The system creates a change state for the MBOM for every recipe version during synchronization.
You can create a new MBOM or, if you have already executed synchronization, update the existing MBOM with the changed
recipe data.
You can also enable the following features:
Initiate synchronization using an already existing and not yet synchronized MBOM
Manage an MBOM in a remote logical system
De ne split points and assign them to the output streams of a recipe that you can synchronize into subordinate BOMs
Assign an already synchronized MBOM to a new synchronization unit
For more information, see Advanced Features for Synchronization.
Prerequisites
To be able to use GSS for recipes, the following prerequisites must be met:
You have edited the general Customizing for GSS under Logistics — General Product Lifecycle Management
(PLM) PLM Web User Interface PLM Web Applications Guided Structure Synchronization and the section Settings for
Synchronization Recipe to BOM.
In particular, you have determined here which explosion scope GSS is to use when exploding recipes (see Explosion).
At least one recipe version with a status that is ready for manufacturing (see Status Schemes for Recipes) exists and
has not yet been synchronized.
Additional features have their own prerequisites in Customizing (see Advanced Features for Synchronization).
Caution
Depending on the materials or on the MBOM, further prerequisites may be necessary. If the prerequisites are not met, the
Reconciliation Workbench issues corresponding error messages and con icts after the synchronization.
Features
Synchronization Unit
The alternative recipe, together with the assigned MBOM, forms a synchronization unit. The synchronization unit can have the
following status:
New, in other words, the alternative recipe was not yet synchronized
Not aligned, in other words, there are new or changed recipe versions that were not yet synchronized
Aligned, in other words, no changes were made since the last synchronization
3/31/2019
Note
You can also display and search for synchronization units in the object navigator or in the work center and control center of
the PLM Web UI. Note that the system in each case only shows the last recipe version that was synchronized or is pending
synchronization, even if further recipe versions may have already been synchronized with this synchronization unit.
Planning Synchronization
When you call the synchronization, the planning screen appears. In the top screen area, you see a table that contains all existing
synchronization units for the alternative recipe.
Every synchronization unit contains the following data from the target BOM:
As BOM header material, the material assigned to the primary output of the recipe
Plant
BOM usage
Alternative BOM
In the lower screen area, you see the detail data for the synchronization unit selected in the table.
The detail area contains the following data:
On the General view, you see administrative data for the synchronization unit and the following parameters of the target
MBOM:
The quantity of the material that used as base quantity to scale the BOM, in the base unit of measure for the
material (changeable)
The system uses the base quantity of the primary output as the default value.
The owning context (ACC) to which the MBOM is to be assigned (optional and changeable)
The destination of the remote system, where the target MBOM is created after the synchronization, in case you
have enabled cross-system synchronization (see Advanced Features for Synchronizing).
On the Mapping view, you see which recipe version the system determined as relevant for manufacturing and thus for
synchronization.
You assign change numbers to these recipe versions (see Change Number on the Web UI). The system then creates a
change state for the changed MBOM components (header or item) for the changed change number when synchronizing.
The system marks the assignment of a change number to the recipe version that was last released and not yet
synchronized, as the next assignment to be synchronized.
To determine the structure of the target BOM; the system explodes the recipe after synchronization (see Explosion). On
the Synchronization Options view, you determine how the system is to behave during recipe explosion.
You can control the explosion as follows:
Explosion scope
In Customizing, specify an explosion scope that de nes which component types the system considers during the
explosion.
Explosion strategy
De ne the way the ingredients are listed in the source structure of the reconciliation workbench during the
explosion of the source recipe. You can assign the default explosion strategy to a speci c plant in Customizing
3/31/2019
under Guided Structure Synchronization Settings for Synchronization Recipe to BOM Assign Additional Plant-
Speci c Data .
Alternative items
If the recipe version to be synchronized contains alternative items, you have the following options:
You determine that the system automatically uses the alternative item that is de ned as Alternative Used
in the formula.
You can then specify further recipes that produce the input items for the recipe. The system then explodes
these recipes as well and creates an MBOM, including their input items.
Note
The system only considers the recipes that are speci ed here. If the system determines an input item
during the explosion that exists for a further recipe that is not speci ed here, the system does not
explode this recipe.
The explosion stops at the corresponding item and the MBOM is only created up to this level.
If you specify an alternative recipe whose primary output is either not an input substance for the recipe
or for which the system did not nd a valid recipe version, the Reconciliation Workbench issues a
corresponding message.
You determine that you select, in the Reconciliation Workbench during synchronization, which alternative
item the system is to use.
If you select a different alternative item, the system calculates the associated quantity in such a way that
the item has the same mass per primary output as the alternative item speci ed in the recipe as the
alternative used.
You determine that the system copies all alternative items to the MBOM.
Reconciliation Workbench
After you have started the synchronization from the planning, the Reconciliation Workbench appears. Here, the system displays
the target structure that is to be created or updated through synchronization.
Note
You have the possibility to switch to an advanced, more customizable version of the Reconciliation Workbench. To do this, you
have to set the RWB Features option to Advanced in Customizing under Guided Structure Synchronization Settings for
Synchronization Recipe to BOM General Settings for Synchronization Recipe to BOM .
If the system determines con icts, it displays these and you can solve them directly by using prede ned actions. The following
con icts can occur here:
Rounding con ict between source quantity and target quantity (information)
Because the recipe can contain values with up to six decimal places, but the MBOM only allows three, deviations caused
by rounding may occur during synchronization. In Customizing, you specify as of which deviation the Reconciliation
Workbench is to issue a con ict.
New alternative elements exist (information)
The system has determined alternative items. In the Proposal column of the con ict, you can choose which alternative
the system is to use for the MBOM.
3/31/2019
New elements exist in target (information)
A new change state was created for the MBOM component (header or item) described in the associated con ict
description.
Element removed in source (error)
An item existing in the target structure no longer exists in the recipe. You must choose here whether you want to
restrict, delete, or keep the item in the MBOM as well. If you keep the item, you must then check the MBOM and adjust
the quantities.
Element removed in target (error)
An item existing in the recipe no longer exists in the BOM. Check the recipe.
Zero value in the target quantity (error)
The quantity of the target MBOM item is zero due to its value allowing only three decimal places. You must switch to a
unit of measure with a higher precision to avoid a zero quantity result.
No target is determined for source (error)
By synchronizing with an existing BOM, the formula items in the recipe are not mapped automatically. For each formula
item, a con ict is issued whether you want to create a new target item, map to an existing BOM item, or do not map the
selected source item at all.
No valid target to update (error)
If a formula item in the previous synchronization has been mapped to a BOM item that does not exist with the change
number used for the current synchronization, then the system cannot update the target structure, unless this con ict is
resolved (SAP Note 1970407 ).
If there are no more errors, save the target structure. Only then does GSS save the MBOM to the database. If you exit
Reconciliation Workbench without saving, the data is lost and you must restart the synchronization.
When you open the Reconciliation Workbench for con ict resolution, the system displays the content of the recipe you
are using as the source.
This view of the recipe structure contains only formula items relevant for BOM synchronization, and can be hidden if
necessary.
Activities
To call the synchronization planning, choose the Synchronization Recipe to BOM option in Recipe Editing under You Can Also.
To synchronize a recipe version for the rst time, create a new synchronization unit and start the synchronization.
To update an existing MBOM that was created through synchronization, select an existing synchronization unit and start the
synchronization.
For additional features, see Advanced Features for Synchronization.
Advanced Features for Synchronization

Use
You can set the following advanced features for a recipe to BOM synchronization:
3/31/2019
Synchronization with an Existing BOM
Cross-System Synchronization
Splitting of Recipes with Stream
Synchronization Unit Lifecycle Management
Prerequisites
You have enabled the relevant functions in Customizing under Logistics — General Product Lifecycle Management
(PLM) PLM Web User Interface Recipe Development Recipe Settings for Synchronization Recipe to BOM General
Settings for Synchronization Recipe to BOM .
For the full functionality of these features, you have to set the Advanced version of the Reconciliation Workbench in the
above Customizing activity.
Features
Synchronization with an Existing BOM
You can start a synchronization using an already existing and not yet synchronized BOM.
When enabled, you are able to select from a list of the available BOMs that you can assign as an Alternative BOM when creating
a new synchronization unit. You can only proceed with the synchronization, if the selected BOM's valid-from date is equal or
earlier than the valid from-date of the change number in the mapping for the selected recipe version.
During synchronization, a new con ict is issued, because the formula items in the recipe are not mapped automatically. For each
of these items, you can decide whether you want to create a new target item, map to an existing BOM item, or do not map the
formula item at all.
Note
You are only able to select a BOM that is not assigned to any other synchronization unit.
Cross-System Synchronization
You can create the target MBOM not only in your local system, but in a remote logistic, non-PLM system as well. To do this, set
the destination of the target system and assign it to a speci c plant in Customizing under Recipe
Development Recipe Settings for Synchronization Recipe to BOM Assign Additional Plant-Speci c Data .
When enabled, the synchronization unit table shows information on whether a destination exists for the speci ed plant, and
displays the destination based on this information. Each data that is evaluated during a synchronization (materials, plant and
change number) comes from the remote system, otherwise the scenario is the same as with a local synchronization.
Note
BOMs in synchronization units without plant assignment are always handled as group BOMs in the local PLM system,
therefore you cannot use them for cross-system synchronization.
Splitting of Recipes with Stream
This feature allows you to synchronize the formula of a recipe into multiple BOMs in one step without de ning intermediate
products on the recipe side.
3/31/2019
When enabled, you can de ne split points as a new option on the Synchronization Options view and assign subordinate BOMs to
the streams of a recipe. The BOM header and the subordinate BOMs are then synchronized together with a single
synchronization unit. After a successful synchronization, the setting is locked and you cannot change it.
You can only use this feature if the recipe type allows streams. You can edit recipe types in Customizing under Recipe
Development Recipe De ne Recipe Types .
Note
De ning split points for your recipe disables the selection of the explosion strategy, which is set to Uncondensed. This
overrides the plant-dependent setting in Customizing under Recipe Development Recipe Settings for Synchronization
Recipe to BOM Assign Additional Plant-Speci c Data .
Synchronization Unit Lifecycle Management
This feature introduces the following new statuses for synchronization units:
Pending: The BOM is already assigned to another synchronization unit which is not yet synchronized
Obsolete: You can no longer use the synchronization unit
When enabled, you can choose an already used and synchronized BOM when creating a new synchronization unit.
If you create a new synchronization unit for a BOM that already has a synchronization unit, then the existing one is set to
Pending status. Once the synchronization occurs, this status changes to Obsolete. If you delete the new synchronization unit
without synchronization, the BOM’s previous synchronization unit becomes active again and returns to its original status
(Aligned/Not Aligned). If you create the new synchronization unit for the same alternative of the recipe, then the Mapping view
shows information about the BOM’s previous synchronization unit. In any other case, this information is only available in the
synchronization unit table, where there is a reference to the previous synchronization unit. You can also set a synchronization
unit with status Aligned/Not Aligned to Obsolete directly and irreversibly.
Note
If you create a synchronization unit for an already synchronized BOM, then you can use the existing subordinate BOMs as
BOMs for the de nition of split points. For a detailed explanation on which entries are valid for the Alternative BOM eld, see
SAP Note 2025916 .
Synchronizing a Recipe with a Master Recipe

Use
After a recipe is nal and released, you send it to production with transferring data to a master recipe (PP-PI) with Guided
Structure Synchronization (PLM-WUI-GSS) . The master recipe is used in Production Planning - Process Industries (PP-PI). You
can create a new master recipe or, if you have already executed synchronization, update the existing master recipe with a
change number, depending on Customizing.
This function is to plan the synchronization and execute it by solving the con icts between the recipe and the master recipe. The
synchronization works one way, that is, a development recipe's updated data can be transferred to the master recipe. The
synchronization includes all process elements (stage, operation, action, equipment requirements, process parameters, and
BOM), the mapping rules for process parameters can be de ned in Customizing. For more information, see the Activities
section.
Prerequisites
3/31/2019
To be able to use GSS for recipes, the following prerequisites must be met:
You have the proper authorization to perform synchronization. This is handled by authorization object PLM_R2MR, see
Authorizations.
You have set the required Customizing activities, see SAP note 1851685 for detailed information.
At least one recipe version with a status that is ready for manufacturing exists (has a status with attribute
REL_SYNC_MRCP — by default, this is the “Released” status) and has not yet been synchronized. For more information
about recipe statuses, see Status Schemes for Recipes.
Features
Synchronization Unit
The alternative recipe, together with the assigned master recipe, forms a synchronization unit (PLM-WUI-APP). The
synchronization unit can have the following status:
New — the alternative recipe was not yet synchronized
Not aligned — there are newer, not synchronized recipe versions compared to the last synchronized one
Aligned — there are no newer recipe versions compared to the last synchronized one
Planning Synchronization
When you call the synchronization, the planning screen appears. In the top screen area, you see a table that contains all existing
synchronization units for the alternative recipe.
Every synchronization unit contains the following data:
From the source recipe:
The material assigned to the primary output of the recipe
BOM usage
Alternative BOM
Plant
From the target recipe:
Master recipe group
Master recipe group counter
In the lower screen area, you see the detail data for the synchronization unit selected in the table.
The detail area contains the following data:
On the General view, you see administrative data for the synchronization unit.
On the Mapping view, you see which recipe version the system determined as relevant for manufacturing and thus for
synchronization.
You can assign change numbers to these recipe versions (see Change Number on the Web UI) if the use of change
numbers is set in the appropriate Customizing activity (for more information, see the Activities chapter). The system
3/31/2019
then creates a change state for the changed master recipe components for the changed change number when
synchronizing.
The system automatically marks the assignment of a change number to the recipe version that is considered as released
and not yet synchronized (but newer than the last synchronized one), as the next assignment to be synchronized. A
recipe version is considered released if it has the status attribute REL_SYNC_MRCP for the object type PLM_RCP. For
more information, see Customizing activity De ne Status Scheme under Logistics — General Product Lifecycle
Management (PLM) PLM Web User Interface Recipe Development Recipe Status and Action Management .
Reconciliation Workbench
After you have started the synchronization from the planning, the Reconciliation Workbench appears. Here, the system displays
the source (PLM recipe) and the target (PP-PI master recipe) structure. The target structure shows how the master recipe will
be updated when the synchronization starts.
If the system determines con icts, it displays these and you can solve them directly by using prede ned actions. By default, the
following con icts can occur here:
Con ict Severity Actions
Element Removed in Source Error Keep the target unchanged or remove the
element from the target.
Element Removed in Target Error The target will remain unchanged. (The
synchronization works one way; removing
the element from the source is not
possible.)
New Elements Exist in Target Error Keep the target unchanged or remove the
new items from the master recipe.
Complex Attribute Aspect Modi ed Warning This con ict occurs when something is
changed in the process parameters (source
side) or in the process instructions (target
side). Choose to accept or adjust the
con icting complex attributes.
Multiple Resources Found Error Select the resource you want to use.
Process Item Reordering Error Keep the target unchanged or adjust target.
Process Item Reassignment Error Keep the target unchanged or adjust target.
Equipment Requirement Changed Error Keep the target unchanged or adjust target.
from/to Primary Resource
Equipment Requirement has been moved Error Keep the target unchanged or remove the
to Process Level equipment requirement from the target.
Class Does Not Exist for Primary Warning –

Characteristic Does Not Exist for Primary Warning –

Resource Does Not Exist for Primary Warning –

Class Does Not Exist for Equipment Information –

Requirement
3/31/2019
Con ict Severity Actions
Resource Does Not Exist for Primary Information –

Note
The actual list of possible actions may differ, depending on Customizing.
If there are no more errors, save the target structure. Only then does GSS save the master recipe to the database. If you exit
Reconciliation Workbench without saving, the data is lost and you must restart the synchronization.
Activities
To call the synchronization planning, choose the Synchronization Recipe to Master Recipe option in Recipe Editing or in Object
Navigator under You Can Also.
To synchronize a recipe version for the rst time, create a new synchronization unit and start the synchronization.
To update an existing master recipe that was created through synchronization, select an existing synchronization unit and start
the synchronization.
You can nd the relevant Customizing activities under Logistics — General Product Lifecycle Management (PLM) PLM Web
User Interface Recipe Development Recipe Settings for Synchronization Recipe to Master Recipe .
Building Blocks
De nition
A building block is a prede ned, independent, and reusable object created in the PLM Web User Interface (Web UI) that can act
as a template for recipes, or parts of recipes.
Use
To save you having to enter identical data from scratch when creating new recipes, you can create and use building blocks as
often as required. To make up a complex process, you can load different categories of building blocks into a recipe and nalize
the process afterwards.
Building Block Categories
Building blocks can be created in the following categories:
Process
Process building blocks can contain multiple stages, or even a whole process when there is no need for a separate recipe
or intermediate product.
For example, the preparation of pizza dough that is used as a basis for different frozen pizza products.
Stage
Stage building blocks represent a process step that is always performed in the same way, that is, with the same
equipment requirements, process parameters, operations, and actions.
3/31/2019
For example, the baking of the pizza dough.
Operation
Operation building blocks represent a xed set of speci ed actions.
For example, the standard process for the cooling of an oven.
Action
Action building blocks represent the most granular element of a process that can bring equipment requirements into the
process.
For example, when opening the oven door, protective gloves are required.
Equipment requirement
Equipment requirement building blocks de ne often-required equipment with a speci c set of parameters.
For example, a forklift that can lift ve tons that you might need individually or part of an operation as well.
Building Block Types
Building block types can exist within each building block category to distinguish between different areas and ways of use. For
example, one type of action building block can be plant-dependent, but you may also need plant-independent ones.
You can distinguish building blocks according to type within a category according to the following attributes:
The status scheme used
Whether the system writes change documents for building blocks of this type
Whether the process building block can contain streams
Whether the building block is plant-dependent
You can create building block types in Customizing activity De ne Building Block Types, under Logistics - General Product
Lifecycle Management (PLM) PLM Web User Interface Recipe Development Recipe Building Block .
Caution
Do not create building block types and recipe types with the same identi er.
Structure
A building block can consist of the following units:
Process elements (stages, operations, actions)
Process parameters
Inside a building block, you can specify the following data:
Process elements that are below that building block in the hierarchy. For example, within a process building block you can
specify stages, operations, actions, and equipment requirements.
Classes and characteristics assigned to the building block, and data for the characteristics
3/31/2019
Note
You can only assign one class to one equipment requirement.
Process parameters assigned to the process elements of the building blocks, to describe the process ow in more detail
Centrally managed documents assigned to the building block, stored in SAP Document Management. For example,
standard operating procedures or plant diagrams.
Formula items, with similar capabilities as in recipes. Formula items are transferred when a building block with formula is
loaded into a recipe. These formula items have an output speci cation ( nal output); however its contents are not
transferred when a building block is loaded, as they are not referenced within the recipe that the building block is used in.
Language-dependent short and long texts
When a building block is created, the system creates a speci cation automatically. You can de ne the attributes for this
speci cation in Customizing activity De ne Default Settings for Building Block Categories, under Recipe Development.

Prerequisites
You have created building block types in Customizing activity De ne Building Block Types, under Logistics -
General Product Lifecycle Management (PLM) PLM Web User Interface Recipe Development Recipe Building Block .
You have created the required classes in Classi cation.
You have de ned the attributes for the speci cation the system creates for building blocks in Customizing activity
Building Block De ne Default Settings for Building Block Categories .
Procedure
You can create, display, and edit building blocks in the SAP NetWeaver Business Client. To create a building block, do the
following:
1. Choose Building Blocks
2. Choose the building block category.
You can create building blocks in the following categories
Process
Stage
Operation
Action
3. Choose the building block type.
4. Enter a building block name (if your Customizing settings allow it for the current building block category).
Copying Building Blocks
3/31/2019
You can also create a new building block by copying an existing one. The copied building block displays what its original was in
the Basic Data view; however, the alternatives and the versions are not shown.
The system behaves according to the following during the copy process:
Status: When the status schemes of the original and the copied building blocks are different, the copied one adopts the
new status scheme's initial status.
Change documents: If the copied building block handles change documents and the original one does not, the system
makes entries in the new building block's change document.
Streams: In case of process building blocks, if streams are allowed in the original but not in the new one, the system
removes both the streams and their primary output (PO) assignments. If streams are allowed in both the original and
the copied one, an output stream is automatically created for each stream (except the empty one representing the PO).
Plant dependency: If both building blocks are plant-dependent, the system copies the value from the source. If the copied
building block is plant-dependent but the original is not, then the system adds the default plant if one is set in the SAP
NetWeaver Business Client's Work Center. If the new building block is not plant-dependent but the source is, then no
plant values are copied.
Note
When creating a new building block by copying another one, the new building block can only belong to the same category as
the original one.
Reusing Building Blocks and Recipes

Use
To make use of already existing processes, you can load building blocks or import recipes into a recipe that you are working on.
Activities
Loading Building Blocks
You can load building blocks into a recipe in the Load Building Block panel on the Process main view, according to the building
block''s identi er. They can also be loaded into other building blocks. When you load a building block that can have a formula, the
system also loads all the existing formula items into the recipe.
The hierarchy to consider for this is the following:
1. Process
2. Stage
3. Operation
4. Action
Note
Equipment requirement building blocks can be loaded at any process level.
Process Building Blocks
3/31/2019
You can only load one process building block into another when the top process item is selected in the process structure
tree. The system loads all assigned process elements, but does not load header documents and classi cations.
In case the building block's category is process and it is loaded to a selected recipe in the process structure tree, the
system appends it to the end using the next biggest 10 as starting ID, and applies the stage ID pacing between the
stages.
By choosing the Refresh button on the Process main view, you can display the contents of the building block to be loaded.
However, this function only shows the contents that you are authorized to see. Even if there is more content than what is
visible, the system loads only the displayed items.
Stage Building Blocks
In stage building blocks, the stage column is hidden from the formula- and process elements tabs, as well as the process
structure tree.
You can load building blocks into the recipe once you have started creating or editing a recipe.
Stage building blocks can be loaded the following ways:
The system checks for over ow before items are actually loaded.
When you select these items for loading in case of stage building blocks, the system behaves according to the following
Recipe: The system appends items to the end using the next biggest 10 as a starting ID, and applies the stage ID
pacing between the stages.
Stage: The system loads items into the selected process element.
Operation: Building blocks with stage category cannot be loaded to an operation process element.
Action: Building blocks with category stage cannot be loaded to an action process element.
EQR: Building blocks with category stage cannot be loaded to an EQR process element.
Operation Building Blocks
In operation building blocks, the stage and operation columns are hidden from the formula- and process elements tabs,
as well as the process structure tree.
Operation building blocks can be loaded the following ways:
3/31/2019
Equipment Requirement Building Blocks
You can load an equipment requirement (EQR) building block into an existing recipe to any process element, including
the recipe object itself.
Importing Recipes
You can import a full recipe, or part of a process structure that you nd useful and want to reuse for the current recipe. You can
select certain parts of a recipe for import if, for example, your recipe has stages with operations and actions, but you only want
to reuse one of the operations in an existing stage of the current recipe. In this case you do not have to create a new stage,
since that stage would be removed anyway because you would move the operation to the required position and would delete
the rest of the stage.
When you select an element during import, if the element is already a child node of a hierarchy, its parents indicate that not all
of their subordinate elements are selected by displaying a 3rd state checkbox. When an element is selected, it automatically
sets the selectable elements below.
You can select the following elements of a recipe for import:
Recipe structure
Process elements and their dependent data
The selected elements can have the following kinds of subordinates:
Lower level process element, for example, an operation for a stage
Dependent data for the actual process element, for example the formula and process parameter of a stage
These elements cannot be selected individually but you can specify whether a process element is taken over along with its
dependent data. Whenever a checkbox has 3rd state, it is taken over and shown in the overview during the recipe's import.
You can see the difference between loading building blocks and importing recipes in the following table:
Loading Building Blocks Importing Recipes
Any building block can be loaded into any recipe or another building Imported recipe has to be the same type as the target recipe
block
Loaded as a whole unit You can select what parts of a recipe you want to import
Can be loaded to various parts of a recipe Appended to the end of the target recipe''s process
Origin
3/31/2019
Process Parameter
More Information
Documents
Use
Depending on the requirements of your enterprise’s processes, you may want to add extra information or explanation to your
recipes or building blocks. For example, you could add a con rmation document from authorities when you release a recipe. This
information is often in different formats, such as text, graphic, video, or others. The document can be object-speci c, however
you can choose to apply it to more than one object, such as several building blocks.
To store the information centrally, use Document Management and the document type RMS (recipe document). These
documents can then be linked to the recipe or building block objects, and have all the data formats handled by Document
Management.
Note
If you want to allow further document types to be used with your recipes or building blocks, you can do this in Customizing
activity Cross-Application Components Document Management Control Data De ne Document Types .
Once you have assigned a document to a recipe or building block (or vice versa), you can display and print the assigned
document and its original application les from the object itself, if a viewer program is available.
Integration
The system can assign documents to recipes or building blocks by having an object link between the object type and the
document type. Between building blocks and the document type RMS you can de ne the object link with the object /PLMB/RBB
(building blocks). For recipes, the object link is created through the object /PLMB/RCP. You can make settings for this link
assignment in Customizing for Document Management in the activity De ne Document Types.
The transaction CV02N - Change Document displays a document's assignments to recipes and building blocks separately
because they exist through different object links.
3/31/2019
Features
Status
If a recipe or building block is in status Released (that is, the attribute LOCKED_FOR_CHANGE is assigned to this status), then
you cannot modify its document assignment. For example, if a building block is in status Released, you cannot remove the linked
document from it. This is also true for the recipe object.
However, you can still enable the editing of the document assignment if the DOC_CHANGE_ALLOWED attribute is assigned to a
speci c status of the object. This attribute has to be de ned together with the attribute LOCKED_FOR_CHANGE.
Note
You can only assign the DOC_CHANGE_ALLOWED attribute to a speci c status if you run the report in Customizing for Status
and Action Management, under Logistics - General Product Lifecycle Management (PLM) PLM Web User
Interface Recipe Development Recipe Status and Action Management Collect Object Types and Assigned Attributes .
The status of individual recipes or building blocks is visible in the CV02N - Change Document transaction and on the DMS Web
User Interface.
Activities
To add new document links to building blocks, make sure that you have checked Customizing activity Maintain Key Fields under
Cross-Application Components Document Management Control Data .
You can also assign documents to building blocks from the context-sensitive help of the application.
More Information
Document Management
Status and Action Management on the Web UI

Use
Building blocks use the authorization object of the recipe, PLM_RCPCVS.
Using an authorization group for building blocks is mandatory, as opposed to recipes where this is optional. The authorization
group of speci cations is synchronized with the authorization group of building blocks, which means that when the authorization
group is changed for building blocks, then it also changes for speci cations.
Apart from this default behavior, you can also con gure a building block category with optional authorization group by selecting
the corresponding checkbox in Customizing activity De ne Default Settings for Building Block Categories, under Recipe
Development Building Block . In this case the building block can be saved without authorization group and the speci cation is
not synchronized (but created with the authorization group which is set in the customizing).
Building blocks have their own context authorization based on their GOS object type, PLM_RCP_BB.
3/31/2019
More Information
Authorizations

Use
Status schemes support you during a release process.
Prerequisites
If you want to use your own status scheme, you have edit the activities in Customizing for Recipe Development, under
You enter this status scheme under Recipe Building Block De ne Building Block Types for the building block types used by
you.
Features
The following status attributes are available for building blocks:
DELETION_ALLOWED: Building block can be marked for deletion
LOCKED_FOR_CHANGE: Building block is locked for all changes
CONSIST_EXPLOSION: Explosion-relevant building block data is consistent and the building block is locked for changes
(see Consistency Check)
REL_EXPLOSION: Building block is relevant for explosion (see Explosion)
CONSIST_SYNC_BOM: Building block data that is relevant for synchronization of the building block with a manufacturing
BOM is consistent and the building block is locked for changes (see Consistency Check)
REL_SYNC_BOM: Building block is locked for all changes and relevant for synchronization with a manufacturing BOM. The
building block data that is relevant for the synchronization of a building block with a manufacturing BOM is consistent
(see Synchronizing a building block with a Manufacturing BOM).
SKIP_FORMULA_CHECK: Do not perform formula check
REUSE_RESTRICTED: Building block is restricted from being used further
Status Scheme
The status scheme for building blocks contains the following statuses:
In Process
In this status, you can change building block data and mark a building block for deletion. From here, you can switch to the
For Release status.
For Release
3/31/2019
If you want to set this status, the consistency check checks whether the building block is consistent for the explosion.
Only then can you set this status. The building block is locked for changes as of this status.
You use this status to initiate the release process; the responsible building block developer checks the building block and
changes the status.
Caution
2. You change data.
Released
The explosion-relevant building block data is consistent and the building block is locked for changes.
By setting this status, you transfer the building block to production. In this status, a building block is considered in the
explosion. You cannot change released building blocks, you can only set them to status Obsolete.
Obsolete
By setting this status, you lock a building block temporarily against usage, for example because it is only executed in a
particular season due to the availability of raw materials (such as the processing of fresh fruits). You can mark a building
block with this status for deletion, but you cannot change it. From here, you can switch back to the For Release status.
In Process
For Release

changed
3/31/2019
Released

changed
Obsolete
Note
You can set the building block's status to Released even without a valid formula.
Building Blocks with Status ʻReleased’
When a building block is released, meaning it has the status attribute LOCKED_FOR_CHANGE assigned, you cannot insert or
modify its document links in Document Management (transaction CV02N). This is also true for inserting or modifying multiple
document links; the action does not take place unless all entries are in a status that allows change.
Adapting the Standard System

In the standard system, Recipe Development offers functions that are especially geared to the food industry. If you want to use
Recipe Development in a different industrial area, for example, you can change the process element types used and the
available calculations.
Note
For more options for the settings, see Customizing.
Changing the Names for Process Elements

In the standard system, the process model is based on the breakdown of the process into the following process element types:
Stage
3/31/2019
Operation
Activity
If you want to use other process element types, you can, in Customizing, replace the names that are used on the user interface.
In Customizing, choose Recipe Development Recipe Process Replace Names for Process Element Types .
Changing Calculations
In the standard system, the system makes the following calculations:
Ingredients
Composition
Nutrients
Nutrient Loss
Diets
Costs
Allergens
Religious Certi cation
In the standard system in the Calculation Results view, you can see one view for each of these calculations that contains the
corresponding calculation results.
If you want to de ne other calculations and make the calculation results available on the user interface, you have to make the
following settings in Customizing under Recipe Development:
Under Calculations De ne Recipe Calculations , you create the desired recipe calculations.
Under Calculation-Relevant Views De ne Calculation Result Views , you create views for these calculations and de ne
in which sequence these views are to be displayed.
Under Calculation-Relevant Views De ne Labels for Calculation Result Views , you create the labels that are used on
the respective views.
Under Calculation-Relevant Views De ne Columns for Calculation Result Views , you determine which columns are
available.
Changing Search
Single-Field Recipe Input
You can allow the usage of one single eld to identify recipes during assignment, display, or search-as-you-type. By enabling
single- eld recipe input, you modify the initial screens to display one input eld instead of the Primary Output Speci cation,
Alternative Recipe, and Recipe Version elds in create, display, and change mode of the application.
Enabling the single input eld also changes the user interface in the following places:
Import popup on the Process tab and the process structure tree's import button
Initial screens for changing and displaying multiple recipes
3/31/2019
When looking for recipes, the system considers the separator that you have de ned in Customizing activity General Settings,
under Recipe Development Recipe in the recipe input key.
When allowing single- eld recipe input, you need to run report /PLMB/RCP_SEARCH_TERM_GENERATE - Generate Search
Term in transaction SE38. This report creates the single recipe keys that the system uses for searching, and overwrites the keys
generated with earlier separator settings.
Case-Insensitive Description Search
You can allow the system to search for and assign recipes based on their descriptions in a case-insensitive manner if you enable
it in Customizing, under Recipe Development Recipe General Settings . If you make this setting, every description-based
search inside the recipe object changes its behavior.
If you have data in your system before you activate case-insensitive search, you have to run report /PLMB/RCP_CONV_DESCR -
Generate Recipe Descriptions for Case-Insensitive Search in transaction SE38. This report aligns case-sensitive descriptions
with case-insensitive ones.
User-Speci c Settings
In addition to the general personalization options available in the application environment, for example, in the SAP Enterprise
Portal, you can use the following user-speci c settings in Recipe Development:
Work Environment
You can prede ne user-speci c parameters in the work environment on the Generic tab page (see Control Center).
You can use the following parameters especially for recipe development:
Unit of measure for recipes
If you de ne a unit of measure here, the system uses it instead of the unit of measure that is de ned in
Customizing for Recipe Development under Recipe De ne Allowed Units of Measure .
Default Group for Calculations
If a corresponding parameter is de ned in Customizing in the de nition of a group-based recipe calculation, you
can specify a default group for this calculation, which is entered automatically as default value in the calculation
results view.
Settings for Tables
You can also change the current display by changing the order of the columns or inserting additional columns. Choose
Settings above the table. The system saves the changed display with your user. The next time you call a recipe, the
system displays the table in this form.
In the formula, this does not change the layout de ned in Customizing. If you choose a different layout, the changes are
lost and the system only displays the columns of the layout you selected in the order de ned there.
Recipe Data Analysis

You can use the Business Context Viewer (BCV) side panel in Recipe Development to display additional information about
recipes for further analysis.
For more information about BCV, see Business Context Viewer (BCV).
3/31/2019
BCV is delivered with four default contents for Recipe Development: three for the whole Recipe Management application, and
one especially for the formula item.
Note
You can only use the BCV side panel if your user has the role SAP_BCV_USER (user) or SAP_BCV_ADMIN (administrator)
assigned to it.
The side panel can display the following tables:
Recipe Development:
Where-Used List of Recipe
If the output speci cation of this recipe is used in any other recipe as an input, this query shows all these recipes. You can
then query further into the recipes using the drill-down functionality. If it is not being used in any other recipe as an input,
an empty table is displayed.
Recipes of a Change Number
If a recipe has a change number, the recipes related to the same change number are displayed in BCV along with their
current status. You can then query further into the recipes using the drill-down functionality. If no change number is used,
an empty table is displayed.
Materials Assigned to Output Substance of a Recipe
You can choose a speci c material that can then become the object for further BCV material queries. For example, you
are working with a recipe for a primary output (PO) speci cation for chocolate cake, and this recipe is for the PO
speci cation 12345. Materials 123, 345 and 456 are assigned to speci cation 12345. In this case, this BCV query shows all
materials (123, 345 and 456) linked to speci cation 12345. You can then decide that you want to know more about
material 345, so you select that material from the list. This is then in the input for other BCV queries related to material
345.
Formula:
Materials Assigned to Substance
You can select different rows in the formula view of Recipe Development. If you choose a row within the formula that is
an input speci cation, BCV displays all the materials linked to that input speci cation. If the selected row in an output
speci cation, all BCV content relevant for the whole recipe is displayed.
Minimum, Maximum or Current Quantity for Formula Items
This report shows the quantity of each formula item in a stacked column chart. It displays each stacked column with the
maximum quantity, current quantity, and minimum quantity of the speci c item.
Calculated Costs of Each Ingredient
This report shows the costs of a recipe split into ingredients in a pie chart.
Ingredient Quantities
This report shows the quantity of each ingredient of a recipe.
Composition Quantities
This report shows the quantity of each composition item of a recipe.
Formula Items Quantities
This report shows the quantity of each formula item of a recipe.

3/31/2019
Validity of Recipe Versions
This report shows the validity of each recipe version in a Gantt chart. The versions are labeled with their current status
and usage.
Costs of Recipe Versions
This report shows the costs of each recipe version in a stacked chart.
For an overview of all prede ned business content for Recipe Development, see SAP Business Content for Business Context
Viewer in Recipe Development.
SAP Business Content for Business Context

Viewer in Recipe Development
Use
Business Content Viewer (BCV) comes delivered with prede ned business content for the analysis of recipes in Recipe
Development. You can enhance this standard content and con gure BCV for your own business needs.
Prerequisites
The business content for Recipe Development is a part of the following BC set:
PLM Content for Recipe Development (/PLMI/BCV_BC_PLM_RCP)
To use the business contents for Material and Change Number, you must also activate BC set PLM BCV Content General
(/PLMI/BCV_BC_PLM_GENERAL).
Features
Prede ned Search Connectors
Business Object Search Connector ID Data Provision Technology Description
Formula 1PLMRCP_MAT2INSUB Classic InfoSet Materials Assigned to Input

Substance
Recipe 1PLMRCP_MAT2OUTSUB Classic InfoSet Materials Assigned to Output

Substance
Recipe 1PLMRCP_RCPBYCHANGNR Classic InfoSet Recipes Related to Change

Number
Recipe 1PLMRCP_WUL Classic InfoSet Where-used List of Recipe
For more information about search connectors, see Search Connector.
Prede ned Queries
Business Object Query ID Search Connector ID Description
Formula 1PLMRCP_MAT2INSUB 1PLMRCP_MAT2INSUB Materials Assigned to Input

Substance
3/31/2019
Recipe 1PLMRCP_MAT2OUTSUB 1PLMRCP_MAT2OUTSUB Materials Assigned to Output

Substance
Recipe 1PLMRCP_RCPBYCHANGNR 1PLMRCP_RCPBYCHANGNR Recipes Related to Change

Number
Recipe 1PLMRCP_WUL 1PLMRCP_WUL Where-used List of Recipe
For more information about BCV queries, see BCV Query.
Prede ned Query Views
In the Query Views accordion item of the side panel, you can nd the following prede ned query views:
Business Object Query View ID Query View Description
Formula 1PLMRCP_MAT2INSUB Materials Assigned to Input Substance
Recipe 1PLMRCP_MAT2OUTSUB Materials Assigned to Output Substance
Recipe 1PLMRCP_RCPBYCHANGNR Recipes Related to Change Number
Recipe 1PLMRCP_WUL Where-Used List of Recipe
Prede ned Dashboards
In the Dashboards accordion item of the side panel, you can nd the following prede ned dashboards:
Context Key Dashboard ID Description
/PLMU/FORMULA 1PLMRCP_RFO_STD PLM Recipe Development — Formula

Dashboard
/PLMU/RECIPE 1PLMRCP_RCP_STD PLM Recipe Development — Recipe

Dashboard
Prede ned Overviews
In the Overview accordion item of the side panel, you can nd the following prede ned overviews:
Context Key Overview ID Description
/PLMU/FORMULA 1PLMRCP_RFO_TAB PLM Recipe Development — Formula

Overview
/PLMU/RECIPE 1PLMRCP_RCP_TAB PLM Recipe Development — Recipe

Overview
SAP Business Content for Business Context

Viewer in Recipe Development (Enhanced)
Use
3/31/2019
Business Content Viewer (BCV) comes delivered with prede ned business content for the analysis of recipes in Recipe
Development. You can enhance this standard content and con gure BCV for your own business needs.
Prerequisites
The business content for Recipe Development is a part of the following BC set:
PLM RD Business Content for BCV – Enhanced (/PLMI/BCV_BC_PLM_RCP_2)
Features
Prede ned Search Connectors
Business Object Search Connector ID Data Provision Technology Description
Formula Item 1PLMRCP_MINMAX_ITEM Classic InfoSet Min. - Max. - Current Quantity

for Items
Recipe 1PLMRCP_COSTS_INGR Classic InfoSet Calculated Costs of Each

Ingredient
Formula Item 1PLMRCP_QUAN_ITEM Classic InfoSet Formula Item Quantities
Recipe 1PLMRCP_QUAN_COMP Classic InfoSet Composition Quantities
Recipe Version 1PLMRCP_VALIDITY Classic InfoSet Validity of Recipe Versions
Recipe Version 1PLMRCP_VERS_COSTS Classic InfoSet Costs of Recipe Version
For more information about search connectors, see Search Connector.
Prede ned Queries
Formula Item 1PLMRCP_MINMAX_ITEM 1PLMRCP_MINMAX_ITEM Minimum - Maximum - Current

Quantity for Formula Items
Recipe 1PLMRCP_COSTS_INGR 1PLMRCP_COSTS_INGR Calculated Costs of Each

Ingredient
Formula Item 1PLMRCP_QUAN_ITEM 1PLMRCP_QUAN_ITEM Formula Items Quantities
Ingredient 1PLMRCP_QUAN_OF_INGR 1PLMRCP_QUAN_OF_INGR Ingredient Quantities
Composition 1PLMRCP_QUAN_COMP 1PLMRCP_QUAN_COMP Composition Quantities
Recipe Version 1PLMRCP_VALIDITY 1PLMRCP_VALIDITY Validity of Recipe Versions
Recipe Version 1PLMRCP_VERS_COSTS 1PLMRCP_VERS_COSTS Costs of Recipe Versions
For more information about BCV queries, see BCV Query.
Prede ned Query Views
In the Query Views accordion item of the side panel, you can nd the following prede ned query views:
3/31/2019
Formula 1PLMRCP_MINMAX_ITEM Min. - Max. - Current Quantity for Items
Recipe 1PLMRCP_COSTS_INGR Calculated Costs of Each Ingredient
Formula Item 1PLMRCP_QUAN_OF_ITEM Formula Item Quantities
Ingredient 1PLMRCP_QUAN_OF_INGR Ingredient Quantities
Composition 1PLMRCP_QUAN_OF_COMP Composition Quantities
Recipe Version 1PLMRCP_VALIDITY Status and Validity of Recipe Versions
Recipe Version 1PLMRCP_VERS_COSTS Costs of Recipe Versions
Prede ned Overviews
In the Overview accordion item of the side panel, you can nd the following prede ned overviews:
Context Key Overview ID Description
1PLMRCP_MINMAX_ITEM 1PLMRCP_MINMAX Min. - Max. - Current Quantity for Items
/PLMU/RECIPE 1PLMRCP_COSTS Calculated Costs of Each Ingredient
/PLMU/RECIPE 1PLMRCP_QUANTITY Quantity of Formula Items, Ingredients, and

Compositions
/PLMU/RECIPE 1PLMRCP_VALIDITY Status and Validity of Recipe Versions
/PLMU/RECIPE 1PLMRCP_VERCOSTS Costs of Recipe Version
Mass Changes to Recipes

You can use mass change to change speci c data for a multitude of recipes simultaneously. In the standard system, the
following mass change functions are available:
General Data
Formula Items
In addition, you can use mass change to start the creation of new versions (see Mass Creation for Recipe Versions).
For more information about mass changes, see Mass Changes.
Mass Creation for Recipe Versions

Use
You can create new versions for multiple recipes simultaneously.
To start the creation of new recipe versions, you use the mass change application. There you can call the creation of new
versions in mass change as a function (see Mass Changes to Recipes).
3/31/2019
Features
The creation of new versions involves three steps:
Determining the data
Checking the data and saving the new versions
Con rming the versions created
You can skip the step Check and Save and jump directly to the step Con rm. The system then creates new versions
automatically and saves them. In the step Con rm, the system displays the new versions and lists in the application log possible
messages that occured during creation.
In the step Check and Save, you can check the new versions and cancel their creation, if necessary.
Activities
1. Select the recipes for which you want to create new versions, and choose More Functions Start Mass Changes .
The entry screen for mass changes appears.
2. Choose Creation of New Versions as function for the mass changes.
The entry screen for creating new versions appears. The system displays a list of all selected recipes. You can add further
recipes to the list or delete recipes from the list.
3. If required, specify a change number.
Note
The use of change numbers depends on your settings in Customizing. If the use of change numbers is not permitted
for the recipe type, the eld is not ready for input. If Customizing was con gured to require the use of a change
number, you must enter a change number during mass creation.
To create a new version, you must use a separate change number.
You can specify one change number centrally for all recipes, or you can enter the change number for each recipe. You can
also create a new change number from the mass change, as follows:
a. Choose Create Change Number.
b. In a second mode, you can process change numbers.
c. After you have saved the new change number, you can specify it in the mass processing.
4. Choose Continue.
You have reached the step Check Data and Save. In this step, the recipes are displayed with the new versions. For
example, if you had previously selected a recipe CHOCO_CAKE with the alternative 001 and version 000, the new version
CHOCO_CAKE /001/ 001 is displayed.
You can change the description for the new version. You can specify a change number for individual objects, or change
the change number.
Note
If you select Close, the creation of new versions is canceled.
5. Choose Continue.
3/31/2019
You have reached the step Con rm. The new recipe version has now been created and saved. In the step Con rm, you
can check data once more. The system outputs an application log with the status of the process and possible messages.
From this screen, you can navigate back to the entry screen for mass change directly, to make changes to the newly
created versions.
Choose More Functions to navigate to further applications.
Download of Recipe Data

Use
You can download a freely de nable set of data of one or more recipes.
Prerequisites
You have made the required settings in Customizing for Recipe Development, see Variants in Download Data.
You have at least display authorization for the recipes of which you want to download the data.
Features
The Download Data main view of consists of the following areas:
Display of the loaded selection layout and the number of objects selected for download
Download Data Parameters: here you can set the variant that you want to use and de ne the format of the output le.
This area is the same with each object type.
Additional Information: here you can select calculation-relevant parameters that lter the output data.
You can lter the calculation data according to composition:
Nutrient Group
Diet Group
Allergen Group
Religious Certi cate Group
Genetically Modi ed Ingredient Group
And according to pricing:
Rating
Validity Area
Material Price Type
Currency
Plant
You can access the Download Data or the Download Data with Quick Selection functions for recipes in the following points:
For downloading the data of one recipe:
3/31/2019
When changing or displaying a recipe, select Additional Functions Download Data or Additional
When displaying a recipe in the Object Navigator, select Additional Functions Download Data or Additional
For downloading the data of one or several recipes:
In the Recipe Work Center of the SAP NetWeaver Business Client, select the required recipes from the search
results, then choose Additional Functions Download Data or Additional Functions Download Data with Quick
Selection .
In the Recipe Work Center, under My Objects in the Personal Objects Worklist (POWL), select the required recipes
and click the Download Data button. Here you can select both the Download Data and Download Data with Quick
Selection options.
More Information
Downloading Data
Recipe Archiving
Use
Unused or obsolete recipes can be stored in an archive database. Archived recipes do not appear in the search help or search
result lists and cannot be opened on the PLM Web UI.
The archiving is performed with the transaction SARA. The archiving object responsible for archiving recipes is /PLMB/RCP.
Archiving recipes requires the following steps:
1. Mark the recipes for archiving on the Web UI
A recipe developer who has authorization to edit a recipe can mark a recipe for archiving on the General Data Basic
Data tab of the Change Recipe view. This serves as an indicator for the administrator responsible for archiving, and the
recipes can still be edited.
2. Preprocess the recipes
This locks the recipes for editing.
Caution
This is an irreversible process.
3. Write the recipes in the archive database
The Write job creates the archive les. The maximum size of one archive le is limited, so several archive les may be
created with one job.
4. Delete the recipes from the productive database
The recipes are deleted from the productive database.
The archived recipe data can only be read with the Read report of the SARA transaction.
3/31/2019
Even if a recipe is archived, you cannot create a new recipe with the same recipe ID (that is, the same primary output
speci cation, alternate, and version). You can still create an alternative recipe.
Archived Tables
Here you can see the tables from which data is archived during the archiving process.
Table ID Table Description
/PLMB/RCA_C_PAR Calculation Parameter Names
/PLMB/RCA_C_PART Calculation Parameter Set Descriptions
/PLMB/RCA_COMP Value Assignment Type of Composition
/PLMB/RCA_COSTMP Material Prices Selectable in Cost Screen
/PLMB/RCA_COSTMT Descriptions of Material Prices
/PLMB/RCA_COSTPR Priority of Prices
/PLMB/RCA_COSTS Parameter for Costs
/PLMB/RCA_CPARA Calculation Parameter Set
/PLMB/RCA_INGR Value Assignment Type of Composition
/PLMB/RCA_PARHDR Calculation Parameter Header
/PLMB/RCA_PARITM Recipe Calculation Parameter Items
/PLMB/RCA_PRICID Price ID
/PLMB/RCA_PRICT Price ID
/PLMB/RCA_QUAL Value Assignment Type of Qualitative Data
/PLMB/RCA_QUANT Value Assignment Type of Quantitative Data
/PLMB/RCA_RFO Parameter for Intraformula Calculation
/PLMB/RCA_TAB Floorplan Tabs with Calculation ID
/PLMB/RCA_TABM Main Tabs
/PLMB/RCA_TABS View Sequence per Main View
/PLMB/RCA_TABSC View Sequence per Main View (Calculation Results)
/PLMB/RCA_TABSF View Sequence per Main View
/PLMB/RCA_UI Recipe Calculation - UI Set Up
/PLMB/RCP_ALLUOM Units of Measure Allowed in Recipe Development
/PLMB/RCP_ASSIGN Assignment of Recipe Items
/PLMB/RCP_BB_SPE Default Speci cations for Building Block Creation
/PLMB/RCP_DESCR Descriptions
/PLMB/RCP_MDL_HD Recipe Model Header
/PLMB/RCP_MDL_RL Recipe Model Table for Rules
/PLMB/RCP_MDL_S Customizing Settings for Recipe Modeling
3/31/2019
/PLMB/RCP_PLNT Plant Assignment for Recipe
/PLMB/RCP_RBB Recipe Building Blocks
/PLMB/RCP_RECIPE Recipes
/PLMB/RCP_RECREL Default Table for Object Relationship Service
/PLMB/RCP_SET General Settings
/PLMB/RCP_SINGLE Recipes
/PLMB/RCP_SPEC Defaults for Property Speci cation
/PLMB/RCP_STSP Defaults for Stream Speci cation
/PLMB/RCP_SUBTYP Additional Recipe Type
/PLMB/RCP_SUBUSG Recipe Customizing: Subordinated Recipe Purpose
/PLMB/RCP_T_LOGD Created Testdata Directory
/PLMB/RCP_TY_DES Recipe Customizing: Recipe Type Description
/PLMB/RCP_TY_GEN Recipe Customizing: Recipe Type General Set
/PLMB/RCP_USG Recipe Customizing: Recipe Purpose
/PLMB/RCP_USGDES Recipe Customizing: Recipe Purpose Description
/PLMB/RCP_WBSREL Default Table for Object Relationship Service
/PLMB/RFO_COLPRP Formula I/O Table Column Properties (Unit of Measure)
/PLMB/RFO_FRM Formula
/PLMB/RFO_FRMITM Formula items
/PLMB/RFO_LYOT Formula: Layout De nition
/PLMB/RFO_LYOT_E Excluded Fields from Formula Layout Customizing
/PLMB/RFO_LYOT_F Formula: Field Assignment to Layouts
/PLMB/RFO_LYOT_T Formula: Texts for Layout De nition
/PLMB/RPR_EQR Equipment Requirements
/PLMB/RPR_HDR Process
/PLMB/RPR_OTR_T Recipe Process Element Description
/PLMB/RPR_PE Process Element
/PLMB/RPR_PP_M Recipe Process Parameter Master Data
/PLMB/RPR_PP_VAL Process Parameter Values
/PLMB/RPR_PPGRDS Process Parameter Group Descriptions
/PLMB/RPR_PPGRID Process Parameter Group IDs
/PLMB/RPR_QUEUE Sequence of Process Operations
/PLMB/RSP_VATC Assignment Value Assignment Type - Calculation ID
3/31/2019
/PLMI/GSS_R2B_SU Sync Units for Recipe to BOM
/PLMI/GSS_R2B_KM GSS Recipe -> mBOM: Key Mapping table
/PLMI/GSS_R2B_AR Additional sources for recipe to BOM
/PLMI/GSS_R2BAOP GSS Recipe ->mBOM: Attribute Operations Table
/PLMB/GSS_SUNITT Synchronization Unit Description
/PLMB/GSS_SU_PAR Synchronization Unit Parameters
/PLMB/GSS_SU_STA Synchronization Unit Status
/PLMB/GSS_SU_STR Assignment of Structures to Synchronization Units
INOB Link between Internal Number and Object
KSSK Allocation Table: Object to Class
AUSP Characteristic Values
Activities
All the functions in recipe archiving (preprocessing, write, delete, and read) can be enhanced by implementing the
corresponding Business Add-Ins (BAdIs) in Customizing for Recipe Development under Logistics — General Product Lifecycle
Management PLM Web User Interface Recipe Development Recipe Business Add-Ins (BAdIs) BAdIs for Recipe Archiving .
Note
BAdI: Check Recipe Before Marking for Deletion (/PLMI/RCP_BO_DELETE_ENH) does not run during the actual
preprocessing of recipe archiving, so implement preprocessing checks in BAdI: Enhancement of the Preprocessing Function
in Recipe Archiving, which can be found in the same Customizing area.
If you are using Information Lifecycle Management and would like to use Data Retention for recipe archiving, you have to create
an audit area with appropriate policies. For more information, see Using ILM Retention Management in the Application System.
More Information
Data Archiving (CA-ARC)
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
3/31/2019
All formula item data as available on the Formula view
The following process data:
Process elements
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.
3/31/2019
More Information
Report De nition (EHS-BD-RDF)
Windows Wordprocessor Integration (WWI)
Symbol
Repeating Groups
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
3/31/2019
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).
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
Additional features for Labeling
Change Document Application for Label Sets (SAP Note 1987190 )
Ad-Hoc WWI Reports for Label Sets (SAP Note 1968394 )
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
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
3/31/2019
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.
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.
3/31/2019
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

Recipe Development - Doc 1

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Recipe Development - Doc 1

Enviado por

Direitos autorais:

Formatos disponíveis

3/31/2019

Recipe Development (PLM-WUI-RCP)

SAP ERP | 6.18.11

For more information, please visit the SAP Help Portal.

Recipe Development (PLM-WUI-RCP)

Web-Based Recipe Development

Compliance check for speci cations and recipes

Mass changes for recipes and speci cations

Grouping of objects into object sets, see Object Sets

Search (see Search)

Authorization concept (see Authorizations and Access Control Context (PLM-WUI-APP-ACC) )

Guided Structure Synchronization (see Guided Structure Synchronization (PLM-WUI-GSS) )

Documents (see Document Management and Document on the Web UI)

You can also navigate to any linked object from here.

SAP_PLMWUI_DEMO_RCP_DEVEL4_RM (see Recipe Developer (for Pilot Implementation))

SAP_PLMWUI_DEMO_RCP_REVIEW4_RM (see Recipe Reviewer (for Pilot Implementation))

Application Associated Authorization Roles or Authorization Object

Speci cation Management on the Web UI Authorization Roles:

SAP_PLMWUI_SPEC_ADD_AUTH Auxiliary Role for Speci cation Management

SAP_PLMWUI_SPEC_DISPLAY Display Speci cation

SAP_PLMWUI_SPEC_FES_SAMPLE Access to Speci cation Fast Entry Screen

SAP_PLMWUI_SPEC_MAINTAIN Maintain Speci cation

Recipe Development (Display Authorization Roles:

SAP_PLMWUI_SPEC_ADD_AUTH Auxiliary Role for Speci cation Management

SAP_PLMWUI_SPEC_DISPLAY Display Speci cation

Application Associated Authorization Roles or Authorization Object

Recipe Development (Change Authorization Roles:

SAP_PLMWUI_SPEC_ADD_AUTH Auxiliary Role for Speci cation Management

SAP_PLMWUI_SPEC_MAINTAIN Maintain Speci cation

SAP_PLMWUI_BB_MAINTAIN Recipe Developer (Building Blocks)

Synchronization Recipe to Manufacturing Authorization Role SAP_PLMWUI_RECIPE_H2M Recipe Synchronization Planner

Simulation Authorization Object PLM_RCPMDL Authorization Object for Recipe Simulation

Migration of Recipes from Recipe Authorization Roles:

SAP_PLMWUI_RECIPE_MIGRATION Recipe Migration

Labeling Authorization Roles:

SAP_PLMWUI_LABEL_DISPLAY Label Reviewer

SAP_PLMWUI_LABEL_MAINTAIN Label Developer

Download Data Authorization Role SAP_PLMWUI_DOWNLOAD_DATA Download Data Administrator

Object Sets Authorization Roles:

SAP_PLMWUI_OBJECT_SET Object Set User

SAP_PLMWUI_OBJECT_SET_ADMIN Object Set Administrator

For recipes, RECIPE_WUI

For labels, LABEL_WUI

Authorizations for Recipe-Dependent Master Data

Diﬀerent Authorizations for Formula

Generally, the following rules apply:

Process view not

Recipe Developer (for Pilot Implementation)

Recipe Reviewer (for Pilot Implementation)

The role is suited especially for use in pilot implementations.

Recipe Developer (Building Blocks)

Auxiliary Role for Speci cation Management

Display Speci cation

Access to Speci cation Fast Entry Screen

To de ne such authorizations, note the following:

Maintain authorization object PLM_SPCFES.

Fill the authorization eld (WebDynpro variant) with single values.

Maintain Speci cation

Typical activities for this role include:

displaying change documents

changing and displaying reports

displaying phrase libraries and phrase groups

Speci cation Management (SAP_EHS_SAF_SUBSTANCEDATA)

Auxiliary Role for Speci cation Management (WUIAUTH_ROLES_SPEC_ADD_AUTH)