PLPO table — PLPO - Routing Operations and Standard Values

One row in PLPO represents a single operation or sub-operation belonging to a task list - a routing, a rate routing, or a reference operation set. The row carries the operation short text, the control key that governs scheduling and confirmation behaviour, the work center reference, the base quantity the standard values are calculated against, and up to six pairs of standard value fields (planned value plus unit) used for costing and scheduling, typically labelled for setup, machine and labour time depending on the work center's formula. PLPO does not belong to a production order. It belongs to the task list itself, and its content is copied into an order's operation data (AFVC/AFVU) only at the moment the order is created from that routing. Multiple rows exist per task list, one per operation and sub-operation, distinguished by the internal node counter.

Always restrict by MANDT first, then by the full task list key: PLNTY plus PLNNR plus PLNAL, and ideally PLNKN if it is already known from PLAS. Selecting on VORNR alone is not selective because operation numbers repeat across every routing in the system. Do not scan PLPO by work center (ARBID) or by plant without also restricting the task list type, the table is large in any system with a mature master data set and an unrestricted scan on ARBID will be slow. If a change number or validity date matters, check whether the row is time-sliced before assuming a single row is the only version.

Symptom: a production order shows a standard time for an operation that does not match what planning expects. First find the routing group and alternative used, PLNTY/PLNNR/PLNAL, from the order's operation record. Then select PLPO on that exact key plus PLNKN for the operation in question and read VGW01 to VGW06 with LAR01 to LAR06. If those values match the order but not expectation, the order is correct and the discrepancy is in the routing itself, not in order execution.

PLPO continues to exist as a standard transparent table in S/4HANA and is still populated by the same routing and reference operation set maintenance transactions as in ECC. Its structure and key fields are unchanged for the fields listed here. Analytical and Fiori-based routing reporting in S/4HANA is generally built on CDS views layered on top of the classic task list tables rather than reading PLPO directly, but PLPO itself remains the underlying source table.

Routing content in PLPO belongs to the PP master data or process engineering team that owns work center and routing maintenance. Standard value definitions and activity type assignments are usually a joint decision with the costing team, since LAR01-06 feed activity price valuation. Discrepancies between planned standard values and order results are a scheduling or execution question, not a PLPO data question, once the routing content itself has been confirmed correct.

PLKO holds the task list header above PLPO. PLAS is the operation assignment table that carries the internal node counter linking header to operations. PLFL, where used, carries sequence and flow information for the same task list. MAPL assigns materials to a task list group and alternative. CRHD is the work center master resolved from PLPO-ARBID. AFVC and AFVU are the order-level operation tables populated from PLPO at order creation, and are the correct place to look for what actually happened rather than what was planned.