How to Create a Master Recipe in SAP PP-PI (C201)
how to create master recipe in sap pp
Also searched as
- sap master recipe c201
- sap pp-pi master recipe creation
- master recipe control recipe destination sap
Short answer
A master recipe is the PP-PI equivalent of a routing: it holds the operations and phases, the resources they run on, material assignments and the control recipe destination. Create it with C201, assign the material at header level, build the resource network, and then add a production version (C223) so process orders can use it.
Applies to: SAP ECC 6.0 and SAP S/4HANA on-premise with PP-PI (process manufacturing)
Create a master recipe
- 1Run C201 (Create Master Recipe). Enter the plant, a recipe group name (or let the system number it) and the group counter.
- 2On the header, assign the material the recipe produces, set the usage (for example 1 for production), status (for example 4 released), the planner group and the lot size range.
- 3Open the operations overview and create the operations and phases. Phases are the lowest level that is controlled in the process; operations group phases.
- 4Assign the resource (CRC1 resource, a work center type in PP-PI) and a control key to each operation or phase. Use a PI control key.
- 5Assign the material components (BOM items) to the phases that consume them, in the Materials assignment.
- 6Maintain the control recipe destination on the operation or phase if the process instructions are to be sent to a PI sheet or control system.
- 7Add the production version (C223) linking the BOM alternative and the master recipe, then test with a process order (COR1).
Header data and usage
The header identifies the recipe by group and counter, the plant, and the material. Usage and status determine where the recipe may be used and whether it is released. Only a released recipe can be used in a process order, so a status of 'created' will produce a missing-recipe error later.
Lot size range defines the minimum and maximum quantity the recipe is valid for. Production versions pick the recipe by lot size, which allows different recipes for pilot and full-scale batches.
You can maintain the validity of the recipe as a change number (engineering change management) for controlled changes.
Operations, phases and the resource network
Operations contain phases, and phases are the executable steps: charge, heat, hold, discharge. Each phase has a resource, a control key, and standard values for duration and activity. You can also use sub-operations as an alternative to phases in some designs.
The resource network is the graphical sequence of operations and phases. It defines relationships, such as start to start with a lag, which feed scheduling. It is also where you see parallel branches, so spend time here to get the logic correct.
Phases can carry process instructions (set a setpoint, record a value) that become part of the control recipe. A destination decides whether they are sent to a PI sheet or to a process control system through the PI-PCS interface.
Control recipe destination and production version
A control recipe destination is the target for the process instructions generated from a phase. It can be a PI sheet (a structured electronic work instruction) or an external control system defined through the process control interface. Without a destination, no control recipe or PI sheet is created for the phase.
The production version ties the material, BOM and master recipe together. Process orders created with COR1 read the production version. If the lot size lies outside the range or the validity dates do not match, the order cannot find a recipe.
After creating the recipe, run a check in the recipe (Check function) to catch missing resources, inconsistent relationships and unassigned components.
C201 Create master recipe
C202 Change master recipe
C203 Display master recipe
CRC1 Create resource
C223 Maintain production version
COR1 Create process order
Try it here, free
SAP Equipment Master Data Template
Collect the data needed to create an equipment master record in SAP PM and export it as a clean data sheet.
Common pitfalls
- !Leaving the recipe status as 'created' and wondering why the process order cannot find it.
- !Choosing a control key without the PI indicators, so the phases are not recognized in the order.
- !Forgetting to assign components to phases, so material staging happens at the wrong point.
- !Not creating the production version, which is the link the process order actually reads.
- !Using a resource without capacity, so scheduling produces no capacity picture.
How an ERP-grounded AI assistant handles this
Master recipe problems are usually discoverable in the data: lot size ranges that do not overlap, missing phase assignments, or no released version. A grounded assistant can read recipes and production versions and answer 'why can the order not find a recipe for 5,000 kg' in seconds. Netray can host the model privately next to your SAP system so recipe data, which often is intellectual property, stays on-premise.
Frequently asked questions
What is the tcode to create a master recipe in SAP?
C201 creates the master recipe, C202 changes it and C203 displays it. These are for PP-PI. In discrete manufacturing, the equivalent object is a routing, created with CA01.
What is the difference between a master recipe and a routing?
A routing is used in discrete manufacturing with production orders. A master recipe is used in process manufacturing with process orders, adds phases, a resource network and control recipe handling. The idea is the same, a sequence of operations on resources.
What is a control recipe destination?
It is the target that receives the process instructions of a phase when a process order is released: a PI sheet for operators or a process control system. Without it, no control recipe is generated for that phase.
Why can the process order not find my master recipe?
Typical causes are an unreleased status, a lot size outside the range in the production version, validity dates that do not match, or no production version at all. Check C223 first.
Related
SAP PP End to End Configuration: Steps, IMG Paths and Process Flow
SAP PP configuration runs in a fixed order: enterprise structure (plant, storage location, planning plant), master data (material, BOM, work center, routing, production version), MRP and planning, production order types and scheduling, confirmation, then costing and settlement. Get the order right because each layer depends on the one before it. The IMG node is Production in SPRO, plus Materials Management for plant and MRP basics.
How-toHow to Create a Control Key in SAP PP (OPJ8)
A control key tells SAP what an operation is allowed to do: be scheduled, costed, confirmed, printed, sent for external processing. Create one with transaction OPJ8 (or SPRO > Production > Basic Data > Routing > Operation Data > Define Control Key), copy a standard key such as PP01, change the indicators, and assign it in the routing or work center.
Error fixSAP CO01 Error: No Production Version Found for Material
SAP cannot pick a production version for the order quantity and date, so it cannot determine the BOM and routing. Fix it in C223 or on the MRP 4 view of the material: create a version for the plant, make its validity dates and lot size range cover the order, link a valid BOM alternative and routing, and remove the lock indicator.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI Agents for SAP Production Planning, MRP, and Exception Triage
AI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
Stuck on SAP S/4HANA and ECC?
Talk to engineers who work inside SAP S/4HANA and ECC every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP Equipment Master Data TemplateCollect the data needed to create an equipment master record in SAP PM and export it as a clean data sheet.
- SAP PP Go-Live Master Data and Cutover ChecklistA tick-box readiness check for production planning go-live, covering master data, configuration, cutover and support.
- SAP PP Master Data Change Request TemplateA controlled change form for BOMs, routings, work centers and MRP data with impact assessment, approvals and rollback.
ERP fixes and how-tos
- SAP PP-PI and the PI Sheet ExplainedWhat SAP PP-PI is, how a PI sheet carries process instructions to the shop floor via control recipes, and how process orders differ from discrete PP orders.
- How to create a routing, work center and production supervisor in SAP PPSet up SAP PP master data: create a work center with CR01, a routing with CA01, and a production supervisor with OPJ2, plus the production version link.
- How to Create a Control Key in SAP PP (OPJ8)Create and configure a routing control key in SAP PP with OPJ8: what each indicator does, which ones matter for confirmation and costing, and how to test it.