MAPL table — Material Assignment to Task Lists
MAPL links materials and plants to task lists such as routings, providing the assignment that lets production planning find the correct routing or other material-relevant task list. It stores material, plant, task-list type, group, group counter, and assignment validity or selection context. The routing header and operations themselves are stored in PLKO, PLAS, PLFL, and PLPO.
Verified practitioner reference for MAPL — Material Assignment to Task Lists, covering its real SAP role, keys and joins, diagnostic proof, S/4HANA context, common pitfalls, ownership, and related objects.
Published 20 Sept 2026· 651 words
Purpose
MAPL is the material-to-task-list assignment table used by production planning and related applications. A routing can exist independently as a task list, but a material/plant must be assigned to the appropriate task-list group and group counter before standard selection logic can use it for the material. MAPL provides that bridge; it does not contain operation standard values or BOM component allocations.
Key fields
Interpret an assignment using the material, plant, task-list identity, and effective/change context.
- MATNR — material number.
- WERKS — plant.
- PLNTY — task-list type.
- PLNNR — task-list group.
- PLNAL — group counter or alternative task-list identification.
- Validity/change-number and deletion context — determine whether an assignment is effective.
- Selection/assignment counters — distinguish multiple assignment records where applicable.
How it joins the data model
MAPL links to PLKO for the task-list header by task-list type/group/group counter context. PLAS and PLPO identify selected operations; PLFL stores sequences. MAST performs the analogous material-to-BOM assignment on the BOM side, while PLMZ maps BOM components to operations. Production versions can further control which BOM and routing combination is selected.
How to read it safely
Do not stop at a MAPL row when diagnosing routing selection. Confirm plant, task-list usage/status, validity date, deletion flags, production version, and lot-size/selection rules in the surrounding task-list model. Multiple routing assignments can be valid for one material, and standard selection can still choose only one based on configuration and production version.
How to prove it in the data
When a production order or costing run selects the wrong routing, start with the material and plant and list valid MAPL assignments for the key date. Resolve each assignment to PLKO and its operations in PLAS/PLPO, then compare status, usage, validity, group counter, and production version. This proves whether the problem is missing assignment, task-list validity, or higher-level selection logic.
Reproduce using the order material, plant, task-list type, production quantity and relevant key date. Inspect the valid MAPL assignments and follow the chosen task-list group/counter into PLKO and routing operations. Compare the result with the standard routing display and any production version or selection logic for the release. Do not overwrite MAPL directly; correct the approved routing/master-data setup through business transactions.
ECC vs S/4HANA
MAPL remains part of the classic task-list data model used in S/4HANA manufacturing. Fiori and released CDS views may provide newer read interfaces, and production-version use is more central in S/4HANA planning, but the material-to-task-list assignment concept remains relevant. New custom analytics should prefer released task-list CDS content where available.
Common pitfalls
Production incident: a production order picks a different routing from the one an engineer expects. A valid task-list definition alone is not enough: material/plant assignment, group counter, validity date, usage, status and selection criteria all affect the outcome. MAPL can point to alternative task lists, and a report that selects the first assignment without considering key date may display an obsolete routing.
- Assuming one material can have only one routing assignment.
- Ignoring plant, key date, usage, status, or group counter.
- Confusing MAPL material-to-routing assignment with MAST material-to-BOM assignment.
- Using MAPL alone to explain production-version selection.
- Editing task-list tables directly instead of using routing maintenance or supported APIs.
Whose problem this is
Primary ownership is PP master data or manufacturing engineering. Product Costing joins when routing selection affects cost estimates; QM can use related task-list concepts for inspection plans; ABAP joins only for proven custom selection logic or migration interfaces.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/maplERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.