# How to Create a Master Recipe in SAP PP-PI (C201)

> Source: https://netray.co/erp-help/sap-pp-pi-create-master-recipe-c201-how-to
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## 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.

## Kind

how-to

## System

sap

## Erp

SAP S/4HANA and ECC

## Module

Production Planning for Process Industries (PP-PI)

## Query

how to create master recipe in sap pp

## Alternate Queries

- sap master recipe c201
- sap pp-pi master recipe creation
- master recipe control recipe destination sap

## Applies To

SAP ECC 6.0 and SAP S/4HANA on-premise with PP-PI (process manufacturing)

## Steps

### Create a master recipe

**Items:**

- Run C201 (Create Master Recipe). Enter the plant, a recipe group name (or let the system number it) and the group counter.
- On 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.
- Open the operations overview and create the operations and phases. Phases are the lowest level that is controlled in the process; operations group phases.
- Assign 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.
- Assign the material components (BOM items) to the phases that consume them, in the Materials assignment.
- Maintain the control recipe destination on the operation or phase if the process instructions are to be sent to a PI sheet or control system.
- Add the production version (C223) linking the BOM alternative and the master recipe, then test with a process order (COR1).

## Sections

### Header data and usage

**Body:**

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

**Body:**

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

**Body:**

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.

**Code:**

- C201   Create master recipe
- C202   Change master recipe
- C203   Display master recipe
- CRC1   Create resource
- C223   Maintain production version
- COR1   Create process order

## 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.

## Ai Angle

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.

## Faq

### What is the tcode to create a master recipe in SAP?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

how to create master recipe in sap pp, sap c201 master recipe, sap pp-pi master recipe, master recipe vs routing sap, sap process order master recipe, control recipe destination sap, sap resource network master recipe, sap production version master recipe

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
