# SAP PP Tables: Production Order, Routing, Resource and PIR Table List > Source: https://netray.co/tools/sap-pp-production-order-routing-pir-resource-tables-map > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A table list for SAP PP grouped by production order, routing, work center, PIR and BOM, with the key fields to join on. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP PP consultant - Production planner - ABAP developer ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Area **Key:** area **Type:** text #### What it stores **Key:** stores **Type:** text #### Key fields and joins **Key:** keys **Type:** text **Rows:** **Table:** AUFK **Area:** Production order **Stored:** Order master data shared by all order types **Keys:** AUFNR; OBJNR links to status tables **Table:** AFKO **Area:** Production order **Stored:** Order header data PP (dates, scheduling, plan number AUFPL) **Keys:** AUFNR; AUFPL leads to operations **Table:** AFPO **Area:** Production order **Stored:** Order item (material, planned quantity, delivered quantity) **Keys:** AUFNR, POSNR **Table:** AFVC **Area:** Production order **Stored:** Operations of the order **Keys:** AUFPL, APLZL **Table:** AFVV **Area:** Production order **Stored:** Operation quantities, dates and values **Keys:** AUFPL, APLZL **Table:** AFRU **Area:** Production order **Stored:** Order confirmations **Keys:** RUECK, RMZHL; AUFNR for the order **Table:** RESB **Area:** Production order **Stored:** Reservations and dependent requirements (components) **Keys:** RSNUM, RSPOS, RSART; AUFNR for order components **Table:** JEST **Area:** Status **Stored:** Individual object status (released, confirmed, technically complete) **Keys:** OBJNR, STAT **Table:** MKAL **Area:** Production version **Stored:** Production versions of a material **Keys:** MATNR, WERKS, VERID **Table:** PLKO **Area:** Routing **Stored:** Routing header (task list type N) **Keys:** PLNTY, PLNNR, PLNAL **Table:** PLPO **Area:** Routing **Stored:** Routing operations **Keys:** PLNTY, PLNNR, PLNKN **Table:** PLAS **Area:** Routing **Stored:** Allocation of operations to sequences in the task list **Keys:** PLNTY, PLNNR, PLNAL, PLNKN **Table:** MAPL **Area:** Routing **Stored:** Assignment of routings to materials **Keys:** MATNR, WERKS, PLNTY, PLNNR, PLNAL **Table:** PLFL **Area:** Routing **Stored:** Task list sequences **Keys:** PLNTY, PLNNR, PLNAL, PLNFL **Table:** CRHD **Area:** Resource **Stored:** Work center header (work center, plant, category) **Keys:** OBJTY, OBJID; ARBPL and WERKS for the readable key **Table:** CRTX **Area:** Resource **Stored:** Work center texts **Keys:** OBJTY, OBJID, SPRAS **Table:** CRCO **Area:** Resource **Stored:** Assignment of work center to cost center and activity types **Keys:** OBJTY, OBJID **Table:** CRCA **Area:** Resource **Stored:** Assignment of capacity to work center **Keys:** OBJTY, OBJID, capacity category **Table:** KAKO **Area:** Resource **Stored:** Capacity header (available capacity, shifts, calendar) **Keys:** KAPID **Table:** PBIM **Area:** PIR **Stored:** Independent requirements header per material, plant and version **Keys:** MATNR, WERKS, BEDAE, VERSB, PBDNR **Table:** PBED **Area:** PIR **Stored:** Independent requirements schedule lines (dates and quantities) **Keys:** BDZEI links to PBIM **Table:** PLAF **Area:** Planning **Stored:** Planned orders **Keys:** PLNUM **Table:** MDKP **Area:** Planning **Stored:** MRP document header **Keys:** DTNUM **Table:** MDTB **Area:** Planning **Stored:** MRP table (stock/requirements list elements) **Keys:** DTNUM, DTPOS **Table:** STKO **Area:** BOM **Stored:** BOM header **Keys:** STLTY, STLNR, STLAL **Table:** STPO **Area:** BOM **Stored:** BOM item (components) **Keys:** STLTY, STLNR, STLKN **Table:** MAST **Area:** BOM **Stored:** Material to BOM link **Keys:** MATNR, WERKS, STLAN, STLNR, STLAL **Table:** STAS **Area:** BOM **Stored:** BOM item selection (links STKO to STPO) **Keys:** STLTY, STLNR, STLAL, STLKN **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the table list **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### Which table stores the SAP routing? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap pp tables, sap pp routing table, resource table in sap pp, pir table in sap pp, all table in sap pp, table sap production, sap afko afpo tables, sap pbim pbed, sap work center table crhd --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json