# SAP Table for Routing and Work Center, Work Orders and Capacity > Source: https://netray.co/erp-help/sap-table-for-routing-work-center-and-production-order > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Routings live in PLKO (header) and PLPO (operations), linked to materials by MAPL and to operations by PLAS. Work centers are in CRHD, with capacity in KAKO. Production (work) orders are split across AUFK, AFKO and AFPO, with operations in AFVC. For reports, use COOIS for orders, CA03 for routings, CR03 for work centers and CM01 for capacity. ## Kind how-to ## System sap ## Erp SAP ERP / S/4HANA ## Module PP / Production Orders, Routings, Work Centers, Capacity ## Query sap table for routing and work center ## Alternate Queries - work order sap table - sap work order table - work center and routing table in sap - capacity planning table in sap - work order report in sap ## Applies To SAP ECC 6.0 and S/4HANA PP; some objects are moved or extended in newer S/4 releases but these tables remain valid ## Steps ### How to find the data you need **Items:** - Use SE16N (or SE16) to read a table, and always filter by plant (WERKS) to keep results manageable. - For a routing, find the material in MAPL to get the task list type PLNTY, group PLNNR and group counter PLNAL. - Read the header from PLKO with those three keys, then the operations from PLPO through the allocation in PLAS. - For the work center on an operation, take ARBID from PLPO and match it to OBJID in CRHD, then read the name and plant from CRHD and the text table CRTX. - For a work order, read AUFK by AUFNR, then AFKO (header data, dates) and AFPO (item, material, quantity) on the same order number. - For order operations, join AFKO-AUFPL to AFVC-AUFPL, and AFVC-ARBID to CRHD-OBJID for the work center. - For capacity, read KAKO (capacity header) using the capacity ID on the work center, and KBED for capacity requirements. ## Sections ### Routing and work center tables **Body:** The task list tables are PLKO (task list header), PLPO (task list operation), PLAS (allocation of operations to the sequence), and MAPL (assignment of task lists to materials and plants). Routings use task list type N, and reference operation sets, rate routings and master recipes use other types. Work centers sit in CRHD (header, with OBJTY and OBJID as the key and ARBPL as the work center name), with CRCO linking cost centers, CRTX for text and CRCA for the assignment of capacities. A routing operation holds the internal work center ID, not the name, so you must join to CRHD to display it. ### Production (work) order tables **Body:** AUFK is the order master common to all order types (production, internal, maintenance). AFKO holds the production order header: scheduled dates, routing number AUFPL and BOM link. AFPO holds the order item: material, planned quantity and delivered quantity. Operations are in AFVC with times in AFVV, and components are in RESB. Always filter AUFK by order category (AUART and AUTYP) because it also holds non-production orders. AUFNR is the common key across them. **Code:** -- Sample join for orders, material and work center (SQL view / CDS idea) SELECT k.AUFNR, p.MATNR, p.PSMNG, v.VORNR, c.ARBPL FROM AFKO k JOIN AFPO p ON p.AUFNR = k.AUFNR JOIN AFVC v ON v.AUFPL = k.AUFPL JOIN CRHD c ON c.OBJID = v.ARBID AND c.OBJTY = 'A' WHERE p.WERKS = '1000' ### Capacity and the standard reports **Body:** Capacity header data sits in KAKO, linked from CRHD through the capacity assignment. Capacity requirements generated by orders are held in KBED and its related tables. For available versus required capacity, use the planning tables rather than summing raw rows, because shifts, efficiency and calendars are involved. Standard reports save table work: COOIS is the order information system for lists of production orders, CO03 displays one order, CA03 displays a routing, CR03 a work center, CM01 and CM02 evaluate capacity, and CM21 gives a work center load. Use SQL joins when you need data these reports cannot export. ## Pitfalls - Joining on work center name instead of internal OBJID. - Reading AUFK for production data without filtering the order category. - Forgetting the group counter PLNAL, which returns duplicate routing alternatives. - Ignoring client (MANDT) and plant in custom queries. - Treating validity dates as irrelevant. Routings and work centers are time-dependent in key places. - Using direct SQL on S/4HANA custom code when a released CDS view or API exists. ## Ai Angle On an on-prem SAP system, a private AI layer can translate a question like which work centers are over capacity next week into the right joins across CRHD, KAKO and AFVC, show the query, and return the result using read-only access. It saves SE16N trial and error, but the join logic still comes from SAP's own tables. ## Faq ### What is the SAP table for routing? **Answer:** PLKO holds the task list header and PLPO holds the operations. MAPL assigns a routing to a material and plant, and PLAS links operations to the sequence. Routings use task list type N. ### What is the SAP table for work order data? **Answer:** AUFK is the order master, AFKO the production order header, AFPO the order item, AFVC the operations and RESB the components. They join on AUFNR and on the routing number AUFPL. ### Which table holds work centers? **Answer:** CRHD is the work center header. Its key is object type and ID, while ARBPL is the readable name. Related tables are CRCO for cost centers, CRTX for text and CRCA for capacity assignments. ### Which report shows work orders without writing queries? **Answer:** COOIS lists production orders by selection, CO03 displays one order, and CO02 changes it. For routings use CA03 and for work centers CR03, with CM01 for capacity. ## Search terms sap table for routing and work center, work order sap table, sap work order table, plko plpo tables, crhd table sap, afko afpo aufk, capacity planning table in sap, work order report in sap, sap routing table --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json