PLAS table — PLAS Task List Selection Table

One row in PLAS represents the selection criteria for a single task list group and group counter, valid from a given key date, independent of which task list category it belongs to - routing, reference operation set, inspection plan, standard network, or equipment task list. The row carries the status of that counter, the usage indicator that says which order types or applications are allowed to pull it, and the lot size range within which it is valid. SAP built PLAS as a shared selection layer so that order creation, matchcode searches, and mass task list evaluation reports do not have to query five different type-specific header tables. It is populated automatically whenever a task list header is created or changed in the relevant maintenance transactions; it is not maintained directly.

PLAS is small relative to the order and confirmation tables, but it is still cross-category, so PLNTY must always be part of the selection or a routing and an inspection plan sharing the same group number will collide in the result set. MANDT is implicit in most tools but explicit in raw SQL. STTAG is a date and there can be several rows per PLNNR-PLNAL pair as validity changes over time, so date logic (select the latest STTAG less than or equal to the reference date) is required, not a plain equality match. STATU and VERWE are coded values, not free text, and their meaning is client-configuration-dependent, so check the underlying domain values before assuming a status code means what it meant on the last project.

Symptom: an order was created against an unexpected routing alternative. Take the material and plant, find the task list group and counters via MAPL, then select PLAS for that PLNTY-PLNNR-PLNAL combination restricted to STTAG less than or equal to the order's basic start date, ordered descending by STTAG. The topmost row with a usable STATU and a lot size range covering the order quantity is the counter SAP would have picked; if a different counter has a later STTAG or a narrower lot size window that excludes the order quantity, that explains the mismatch.

PLAS is unchanged in S/4HANA and continues to carry the same role in task list selection logic. It has not been replaced by a CDS-based compatibility view in the way some order and material master tables have been repointed, and the surrounding transactions for maintaining routings, reference operation sets, and inspection plans still write to it exactly as in ECC. No structural changes specific to S/4HANA are documented for this table.

Most confusion around PLAS comes from treating it as if it held task list content, when it only holds selection metadata.

Routing and task list selection questions sit with the PP master data or process planning team, not with the shop floor or MES team, since PLAS content is driven entirely by how task lists were configured and maintained. Cross-category confusion between routings and inspection plans usually needs input from whoever owns quality task lists as well.

PLKO carries the full header for the selected counter, PLPO carries the operations, and PLFL links sequences to operations within that header. MAPL is the bridge from material and plant to the task list group and counter that PLAS then filters. Task list maintenance transactions for routings, reference operation sets, and inspection plans all write to PLAS as a side effect of saving the header; it is never the primary maintenance object itself.