SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP PP Tables: Production Order, Routing, Resource and PIR Table List

SAP Production Planning data is spread over order, routing, work center, PIR and BOM tables. This list groups them by object so you can find the routing table, the resource table or the PIR table fast, and see which fields connect them.

Download:
TableAreaWhat it storesKey fields and joins
AUFK
Production order
AUFNR; OBJNR links to status tables
AFKO
Production order
AUFNR; AUFPL leads to operations
AFPO
Production order
AUFNR, POSNR
AFVC
Production order
AUFPL, APLZL
AFVV
Production order
AUFPL, APLZL
AFRU
Production order
RUECK, RMZHL; AUFNR for the order
RESB
Production order
RSNUM, RSPOS, RSART; AUFNR for order components
JEST
Status
OBJNR, STAT
MKAL
Production version
MATNR, WERKS, VERID
PLKO
Routing
PLNTY, PLNNR, PLNAL
PLPO
Routing
PLNTY, PLNNR, PLNKN
PLAS
Routing
PLNTY, PLNNR, PLNAL, PLNKN
MAPL
Routing
MATNR, WERKS, PLNTY, PLNNR, PLNAL
PLFL
Routing
PLNTY, PLNNR, PLNAL, PLNFL
CRHD
Resource
OBJTY, OBJID; ARBPL and WERKS for the readable key
CRTX
Resource
OBJTY, OBJID, SPRAS
CRCO
Resource
OBJTY, OBJID
CRCA
Resource
OBJTY, OBJID, capacity category
KAKO
Resource
KAPID
PBIM
PIR
MATNR, WERKS, BEDAE, VERSB, PBDNR
PBED
PIR
BDZEI links to PBIM
PLAF
Planning
PLNUM
MDKP
Planning
DTNUM
MDTB
Planning
DTNUM, DTPOS
STKO
BOM
STLTY, STLNR, STLAL
STPO
BOM
STLTY, STLNR, STLKN
MAST
BOM
MATNR, WERKS, STLAN, STLNR, STLAL
STAS
BOM
STLTY, STLNR, STLAL, STLKN

In ECC PIR requirements are read from PBIM and PBED. In S/4HANA the PIR tables still exist, but requirements for MRP are also handled through MRP live and may differ by release. Key field lists show join fields, not the whole primary key. Confirm in SE11.

Want load and PIR answers without exports?

We can sketch a read-only assistant over your PP data. Optional, the table list works without us.

Optional. The tool and every export work without this. No spam.

How to use the table list

Pick the object you need and read across: the key fields tell you how to join. A report of order operations starts at AFKO, takes AUFPL, and joins AFVC. A routing report starts at MAPL for a material and goes to PLKO and PLPO. Work center names come from CRHD, because operations store an internal object ID rather than the readable work center.

  • Order to operations: AFKO-AUFPL to AFVC-AUFPL.
  • Operation to work center: AFVC-ARBID to CRHD-OBJID.
  • Material to routing: MAPL to PLKO to PLPO.

Routing and resource tables

Routings are task lists of type N. PLKO is the header, PLPO the operations, and MAPL ties the routing to a material and plant. The resource, which SAP calls a work center, is CRHD with a numeric object ID. Capacity data sits behind it in CRCA and KAKO, and cost center and activity assignments in CRCO. These are the tables to read when you want load and available capacity.

PIR tables

Planned independent requirements, the forecast or sales plan that feeds MRP, live in PBIM at material and plant level with a requirements type and version. The dated quantities are in PBED, linked by the requirement number. A planner who asks what is planned for a material next quarter queries these two tables for the active version. Consumption against PIR shows up in MDTB.

Common mistakes

Common mistakes include joining operations to work centers on the readable name instead of the object ID, ignoring the version field on PIR so inactive versions inflate demand, and reading BOM item tables without the validity and change number. Also remember the order status lives in JEST, not in AUFK, so a released filter needs a status join.

Frequently Asked Questions

Which table stores the SAP routing?

Routing headers are in PLKO and operations in PLPO, both with task list type N. MAPL assigns the routing to a material and plant. To find the routing of a material start at MAPL, then read PLKO for the header and PLPO for the steps.

What is the resource table in SAP PP?

Resources are work centers, stored in CRHD. It has an internal object ID that operation tables use, and the readable work center name and plant. Texts are in CRTX, capacity in CRCA and KAKO, and cost center assignment in CRCO.

Which tables hold PIR in SAP PP?

PBIM holds the planned independent requirement header per material, plant and version. PBED holds the dated quantities. You can see the same data in MD62 and MD63. Filter on the active version or inactive PIR will inflate the demand figure.

Which tables hold production orders?

AUFK has the order master, AFKO the PP header with scheduling data, AFPO the order item with quantities, AFVC the operations and RESB the components. Order status is in JEST via the object number OBJNR from AUFK.

If planners keep exporting these tables to spreadsheets, we can add a private assistant over your SAP PP data that answers load, PIR and routing questions and shows the query.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations