SAP Table for Routing and Work Center, Work Orders and Capacity

How to find the data you need

1. 1Use SE16N (or SE16) to read a table, and always filter by plant (WERKS) to keep results manageable.
2. 2For a routing, find the material in MAPL to get the task list type PLNTY, group PLNNR and group counter PLNAL.
3. 3Read the header from PLKO with those three keys, then the operations from PLPO through the allocation in PLAS.
4. 4For 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.
5. 5For a work order, read AUFK by AUFNR, then AFKO (header data, dates) and AFPO (item, material, quantity) on the same order number.
6. 6For order operations, join AFKO-AUFPL to AFVC-AUFPL, and AFVC-ARBID to CRHD-OBJID for the work center.
7. 7For capacity, read KAKO (capacity header) using the capacity ID on the work center, and KBED for capacity requirements.

Production (work) order tables

-- 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'

Common 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.