SAP PP Routing

You are an SAP PP (Production Planning) specialist. The user wants to create routings with operations, work centers, and standard values using SAP transaction CA01 or the API layer.

What to check first

• Run transaction SPRO and navigate to Production Planning > Routings > Master Data > Define Work Centers to confirm work centers exist
• Verify user has authorization object C_RTNG_CRT (routing create) and C_RTNG_CHK (routing check)
• Check table CRHD (work center master) contains at least one active work center with capacity data

Steps

1. Access transaction CA01 (Create Routing) or use module LSMW for batch routing uploads
2. Enter routing Header Data: Plant, Routing Number, Routing Type (01 for standard routing), Version, and Description
3. Add Operations by clicking "Operation" in the detail section — assign sequential operation counter (0010, 0020, 0030) and work center code
4. For each operation, maintain Standard Values tab: Setup Time, Machine Time, Labor Time, and quantity per unit (base quantity)
5. Define Sequence by setting operation dependencies and parallel execution flags if multiple work centers operate simultaneously
6. Assign Work Center field (CWORK in PLKO table) — system validates capacity and cost center linkage automatically
7. Link BOM if required via the Routing-to-BOM relationship in header (field PLNFL)
8. Save routing with Status flag (field PLNST) set to "02" (Active) — inactive routings cannot be used in production orders
9. Run consistency check CTRL+F8 (Check Routing) before releasing to catch missing work centers or circular dependencies

Code

" SAP PP Routing Creation via BAPI
REPORT z_create_routing.

DATA: gs_routing_header TYPE bapiplnghdr,
      gs_routing_item   TYPE bapiplngops,
      gs_header_text    TYPE bapiplnghtxt,
      gt_operations     TYPE TABLE OF bapiplngops,
      gv_routing_group  TYPE bapiplnghdr-plngrp,
      gv_routing_count  TYPE bapiplnghdr-plnnr,
      gs_return         TYPE bapiret2,
      gt_return         TYPE TABLE OF bapiret2.

PARAMETERS: p_plant   TYPE bapiplnghdr-plnty VALUE 'P001',
            p_routing TYPE bapiplnghdr-plnnr VALUE 'ROU001',
            p_version TYPE bapiplnghdr-plnkn VALUE '01'.

START-OF-SELECTION.

  " Header data
  gs_routing_header-plnty = p_plant.
  gs_routing_header-plnnr = p_routing.
  gs_routing_header-plnkn =

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change