JinJin48
JinJin48
SAP Consultant | BTP · S/4HANA · US Global Rollout
· 6 min read

Cover: SAP PP Routing — master data defining the manufacturing process sequence linking Material, Work Centers, and Operations

SAP PP Routing

The Routing (作業手順) is the master data object that defines the manufacturing process for a finished or semi-finished material. It specifies the sequence of operations, the work centers responsible for each operation, and the standard times (setup, machine, labor) required to complete production. Together with the BOM, the Routing forms the technical backbone of production planning, scheduling, capacity planning, and cost calculation. This article covers Routing and its child object Routing Operation — their types, organizational scope, integration with other PP master data, and the field-level detail PP consultants configure and maintain.


Part 1: Routing — Core Concepts (All Modules)

1.1 What Is the Routing?

Hub-and-spoke diagram showing the Routing at center, connected to Material Master, Work Center, BOM, Production Version, and Production Order

A Routing is a time-sequenced list of manufacturing operations that describes how a product is made. Each operation is assigned to a Work Center and carries standard time values used for scheduling, capacity planning, and cost roll-up. Without a Routing, SAP PP cannot schedule production orders, plan capacity, or calculate standard costs for manufactured materials.

AspectDetails
RoleDefines manufacturing process sequence: operations, work centers, standard times, and control keys
Modules using itPP (production orders, capacity planning, MRP scheduling — primary owner), CO (standard cost calculation via activity types at work centers), PM (maintenance task lists share the same task list infrastructure)
TransactionsCA01 (Create) / CA02 (Change) / CA03 (Display) / CA60 (Where-used list) / CAOR (Operation overview)
Key TablesPLKO (Routing header — task list group), PLPO (Routing operations), PLAS (Allocation: Material to Routing), PLFL (Sequences), PLMZ (Component assignment to operations)
S/4HANA noteRouting data model is unchanged from ECC. In S/4HANA, the Fiori app “Manage Routings” (F3082) provides a modern interface. Recipe management (Process Industries) uses a separate object (Master Recipe) but shares the same foundational structure.

1.2 Routing Types and Variants

Comparison grid showing the four SAP PP task list types: Routing, Reference Operation Set, Rate Routing, and Reference Rate Routing

SAP PP uses the concept of “task lists” to cover multiple manufacturing scenarios. Selecting the wrong task list type causes mismatches in production order creation, capacity planning, and costing.

Routing TypeTask List TypeUse CaseKey Behavior
RoutingN (Normal)Standard discrete manufacturing — most commonMaterial-specific. Assigned to one or more materials. Used in production orders and MRP scheduling.
Reference Operation SetRReusable operation library — operations shared across multiple routingsNot material-specific. Referenced by other routings to reduce maintenance. Changes to the Reference Operation Set propagate to all referencing routings.
Rate RoutingR (Rate)Repetitive manufacturing (high-volume, line-based production)Used with planned orders in repetitive manufacturing. Operation quantities are rates per period rather than per order.
Reference Rate RoutingSReusable operation library for repetitive manufacturingShared operations for Rate Routings — same reuse concept as Reference Operation Set but for the repetitive manufacturing context.

Design principle: For standard discrete manufacturing projects, only Routing (type N) and Reference Operation Sets are relevant. Commit to the Reference Operation Set strategy early — retrofitting shared operations into existing routings is high-effort.


1.3 Organizational Levels and Data Hierarchy

Hierarchy tree showing Routing structure: Plant, Routing Header, Operation, with Material and BOM Item references

Data hierarchy with a concrete example

Plant 1000
   │
   ├── Material FG-1000
   │      Finished Good — Widget Assembly X
   │      │
   │      └── BOM Header (Usage 1, Alt 01)
   │             ├── BOM Item 0010 — RM-2001, Qty 2 EA
   │             └── BOM Item 0020 — SFG-3001, Qty 1 EA
   │
   ├── Production Version 0001
   │      ── links ──> Material FG-1000
   │      ── links ──> Routing "RTG-1000" + BOM Header (Usage 1)
   │
   └── Routing "RTG-1000", Counter 1
          Usage: Production, Lot Size 1–9999
          ── assigned to ──> Material FG-1000
          │
          ├── Operation 0010 — Cutting
          │      Work Center WC-CUT-01
          │      Setup 30 min, Machine 45 min, Labor 30 min
          │      ── consumes ──> BOM Item 0010 (RM-2001)
          │
          ├── Operation 0020 — Machining
          │      Work Center WC-MACH-02
          │      Setup 60 min, Machine 120 min, Labor 60 min
          │      ── inspected by ──> Quality Inspection (In-Process)
          │
          ├── Operation 0030 — Assembly
          │      Work Center WC-ASSY-03
          │      Setup 45 min, Machine 90 min, Labor 90 min
          │      ── consumes ──> BOM Item 0020 (SFG-3001)
          │
          └── Operation 0040 — Final Inspection & Packing
                 Work Center WC-PACK-04
                 Setup 15 min, Machine 30 min, Labor 30 min

1.4 Integration with Other Master Data Objects

Hub-and-spoke showing Routing at center connected to Material Master, Work Center, BOM / BOM Item, Production Version, and Production Order

The Routing does not stand alone. It is the bridge between the product structure (BOM) and the manufacturing resources (Work Centers), and is activated for execution via the Production Version.

ObjectRelationshipPractical Notes
Material MasterRouting is assigned to a material via PLASThe material’s Work Scheduling view (production scheduler profile, scheduling margin key, in-house production time) must be consistent with the routing’s standard times. In-house production time in MM03 is used as a fallback when no routing exists.
Work CenterEach operation references exactly one Work CenterWork Center must exist in the same plant. Capacity category and standard value key defined at the Work Center must match the capacity and time fields used in the routing operation. Misalignment causes scheduling and costing errors.
BOM / BOM ItemBOM components are assigned to operations via PLMZComponent assignment (CA01, “Components” tab on operation) controls the goods issue timing — components are issued when the operation is confirmed. Without explicit assignment, all components are issued at order release.
Production VersionProduction Version links one BOM alternative and one Routing counterThe Production Version (C223 / MM02 Work Scheduling view) activates a specific BOM + Routing combination for a material-plant-lot-size. MRP uses Production Version to select the correct routing for scheduling.
Production OrderRouting is copied into the production order at order creationOperations from the routing become order operations. Changes to the routing after order creation do NOT automatically update existing orders — orders must be re-scheduled or manually adjusted.
Costing (CO)Standard cost uses routing operations × work center activity ratesCO uses the standard values from routing operations and the activity type rates from work center cost center assignments to calculate the manufacturing cost component in the material standard cost. Routing and cost center must be aligned before cost roll-up.

Part 2: PP-Specific Field Details

2.0 Scope of PP Ownership

Checklist showing PP consultant ownership across Routing data sections: Header, Sequences, Operations, Component Assignment

Data SectionPP InvolvementNotes
Routing Header◎ OwnerGroup, Status, Usage, Lot Size Range, Valid From/To
Sequences◎ OwnerStandard sequence (mandatory), parallel/alternative sequences (optional)
Operations◎ OwnerOperation number, Work Center, Control Key, Standard Values
Component Assignment◎ OwnerBOM item-to-operation assignment for goods issue timing
Suboperations◎ OwnerSub-steps within an operation (optional)
Production Resources/Tools (PRT)○ Shared with Plant MaintenanceJigs, fixtures, and tools assigned to operations

Legend: ◎ = Owner / Critical, ○ = Direct involvement


2.1 Routing Header

Checklist of key Routing header fields: Task List Type, Group, Group Counter, Plant, Usage, Status, Lot Size Range, Valid From/To

The Routing Header (PLKO) defines the identity, validity scope, and administrative classification of the routing. Getting these fields right at creation time avoids the need for mass updates later.

FieldDescriptionPractical Usage
Task List TypeIdentifies the category of task list (N = Routing, R = Reference Op Set, etc.)Determines behavior in production order creation and MRP. For standard discrete manufacturing, always use type N. Once created, the type cannot be changed — deletion and re-creation is required.
GroupInternal key identifying the routing groupSystem-assigned or manually entered. A Group can hold multiple counters (alternative routings). Use a consistent numbering convention (e.g., aligned with material number) to simplify where-used list maintenance.
Group CounterDifferentiates alternative routings within one GroupCounter 1 = primary routing. Additional counters represent alternative methods. The Production Version controls which counter applies to a given order. Keep the number of active counters minimal — each counter must be maintained independently.
PlantPlant for which the routing is validRoutings are plant-specific. For multi-plant rollouts, routings must be created separately per plant or copied using PLAS/CA01 with plant change. Reference Operation Sets allow operation-level reuse across plants.
UsageDefines which type of order the routing can be used inUsage 1 = Production (standard for PP). Other usages (e.g., 3 = Universal, 4 = Plant Maintenance) restrict or broaden the routing’s applicability. Confirm usage during blueprint — it affects whether the routing appears in production order creation and in MRP scheduling.
StatusControls whether the routing is released for useStatus 4 = Released (General) — the standard active status for production. Status 1 = Created (under development). A routing in status 1 cannot be used in production orders. Release status must be set before the Production Version referencing the routing can be made active.
Lot Size Range (From / To)Minimum and maximum production quantity for this routingAllows different routings (counters) for different lot sizes — e.g., small lots use a manual process, large lots use an automated line. If the production order quantity falls outside all defined ranges, order creation fails. Always cover the full expected quantity spectrum.
Valid From / ToDate validity of the routingA routing with an expired Valid To date cannot be selected for new production orders. Manage validity carefully when implementing engineering changes — create a new counter with a future Valid From rather than modifying the active counter in-place.
Base QuantityReference quantity for standard time valuesAll standard times (setup, machine, labor) in the routing operations are expressed per this base quantity. Example: Base Qty = 1 EA means setup time is per 1 piece produced. Misalignment between base quantity and production order quantities causes incorrect scheduling and costing.

2.2 Sequences

Comparison of Standard Sequence vs. Parallel and Alternative Sequences in SAP PP Routing

Every routing must contain exactly one Standard Sequence (Sequence 0). Parallel and Alternative sequences are optional and serve specific scheduling strategies.

Sequence TypeCodeUse CaseKey Behavior
Standard Sequence0Normal linear process flow — all operations executed in numbered orderMandatory. Operations are scheduled end-to-end. The production order always begins with the standard sequence.
Parallel Sequence1–99 (branch type P)Operations that can run simultaneously with the standard sequenceEnables overlapping scheduling of independent operations (e.g., sub-assembly prepared in parallel with main assembly). Requires a branch and return operation in the standard sequence.
Alternative Sequence1–99 (branch type A)Alternative process route — either/or, not simultaneousUsed when the product can be manufactured via different process paths. The scheduler selects one sequence per order. Rarely used outside process industry projects.

Design principle: For most discrete manufacturing implementations, only the Standard Sequence is required. Parallel sequences add scheduling complexity — model them only if the physical process genuinely requires concurrent operations that must be tracked and confirmed separately.


2.3 Operations

Checklist of key Routing operation fields: Operation Number, Work Center, Control Key, Standard Values (Setup/Machine/Labor), Description

Operations (PLPO) are the core planning unit within a routing. Each operation represents one manufacturing step, performed at one Work Center, consuming capacity and activity types for scheduling and costing.

FieldDescriptionPractical Usage
Operation NumberSequential step number (0010, 0020, …)Determines execution sequence. Gaps (10, 20, 30 rather than 1, 2, 3) allow future insertion of steps without renumbering. Renumbering existing operations in a live system invalidates confirmation history — avoid.
Work CenterWork center assigned to this operationMust exist in the same plant. Determines which cost center and activity types are used for costing. Also defines the default scheduling formula. Assigning the wrong work center is the most common routing setup error.
Control KeyDefines how the operation is processed and confirmedPP01 = Internal processing (standard in-house operation, confirmation required). PP02 = External processing (subcontracting — triggers a purchase requisition for the operation). PP03 = Milestone confirmation (confirming this operation auto-confirms all preceding operations). Select the correct key during blueprint — changing it after production orders exist causes confirmation inconsistencies.
Operation Short TextDescription of the manufacturing stepAppears on the shop floor paper and in production order operation lists. Keep concise and action-oriented (e.g., “Weld frame assembly,” “Final inspection”). Avoid using material numbers or internal codes — operators on the shop floor need plain-language descriptions.
Base QuantityReference quantity for this operation’s standard timesNormally inherited from the routing header. Can be overridden at operation level for operations with a different per-unit effort profile. Overriding at operation level increases maintenance complexity.
Setup TimeTime to prepare the work center before production startsScheduled once per production order regardless of order quantity. High setup times relative to operation time indicate a candidate for SMED or lot-size optimization. Setup time is a key input to capacity planning bottleneck analysis.
Machine TimeTime the machine runs per base quantity unitThe primary capacity-consumption field. Used in conjunction with the work center’s capacity category to calculate available capacity utilization. For labor-intensive operations, Machine Time may be zero — use Labor Time instead.
Labor TimeTime a person is required per base quantity unitRelevant when human resource capacity is planned separately from machine capacity. Assign to a labor activity type on the Work Center for correct cost allocation.
Activity Type (from Work Center)CO activity type charged per operation timeDefined on the Work Center, not directly on the operation. The cost roll-up uses: Activity Qty × Activity Rate = Manufacturing Cost Component. Confirm activity type alignment with CO before running standard cost estimates.
Subcontracting (External Processing)Triggers PR for outsourced operation when Control Key = PP02When PP02 is set, the system creates a purchase requisition for external processing when the production order is created. The vendor performs the operation and sends back the processed material. Requires a purchasing info record (or outline agreement) for the service.

2.4 Component Assignment

Hierarchy tree showing BOM Item to Operation assignment — components linked to the operation where they are issued during confirmation

Component assignment links BOM items to specific routing operations, controlling exactly when (at which operation confirmation) components are issued from stock. Without explicit assignment, SAP issues all components at order release — which is operationally impractical for multi-stage manufacturing.

FieldDescriptionPractical Usage
Material (BOM Item)The component material assigned to this operationPulled from the BOM associated via Production Version. Only components included in the BOM can be assigned. If a component does not appear in the assignment list, check that the BOM and routing are linked via the correct Production Version.
Operation NumberThe operation at which the component is consumedGoods issue is triggered when this operation is confirmed (movement type 261). Assigning components to the correct operation is especially important in multi-stage routings where sub-assemblies are consumed at intermediate steps rather than at the start of production.
Relevant to CostingFlag indicating whether the component is included in cost calculationShould be set for all BOM components in standard implementations. Deactivating excludes the component from standard cost roll-up — use only for informational components (e.g., engineering drawings referenced in the BOM).
Bulk MaterialIndicates the component is a bulk/backflush materialBulk materials (consumables like lubricants, small fasteners) are typically not individually issued — they are settled via a periodic posting rather than at operation confirmation. Confirm bulk material treatment during blueprint to avoid goods issue anomalies.

L1) Big Picture

IDCategoryTitle
pp-001OverviewWhat is SAP PP?

L2-A) Master Data

IDCategoryTitle
pp-a01OverviewSAP PP Master Data: Overview, Hierarchy & Relationships
pp-a02-01Master DataSAP PP Material Master
pp-a02-02Master DataSAP PP MRP Controller
pp-a03-01Master DataSAP PP Work Center
pp-a04-01Master DataSAP PP Bill of Materials (BOM)
pp-a04-02Master DataSAP PP Routing 📍
pp-a05-01Master DataSAP PP Production Version
pp-a06-01Master DataSAP PP Class
pp-a06-02Master DataSAP PP Characteristic

L2-B) Transaction

IDCategoryTitle
pp-b01OverviewSAP PP Transactions: Process Flow, Hierarchy & Relationships