SAP ECC MRP Tables and MRP Element (DELKZ) Codes
This reference lists the SAP ECC 6.0 tables behind MRP and the most used MRP element codes (DELKZ) with the table each element comes from. It is for PP consultants and developers who need to report on MRP results or trace what MD04 is showing.
| Section | Table / DELKZ | Description / meaning | Key or main fields / source table | Use |
|---|---|---|---|---|
A: Table | MDKP | Header of the stored MRP list per material, plant and MRP area | DTNUM; MATNR, PLWRK, BERID, DISPO | Find the MRP list number for a material, then read MDTB |
A: Table | MDTB | MRP list items with MRP element (DELKZ), dates and quantities | DTNUM, DTPOS; DELKZ, DELNR, DAT00, MNG01, PLUMI, AUSSL | Stored result of the last MRP run as shown in MD05 |
A: Table | MDVM | Planning file entries at plant level | MAFID, MDKEY (material and plant); GSAEN, AKKEN, RESAL | Which materials will the next net change run plan (plant level planning) |
A: Table | DBVM | Planning file entries including MRP area | MAFID, DISST, MATNR, BERID; GSAEN, AKKEN, RESAL | Planning file when MRP areas are active; check with MD21 |
A: Table | MDLV | MRP area definitions | BERID; BERTY, WERKS | List MRP areas and their type (plant, storage location, subcontractor) |
A: Table | MDLG | Storage locations assigned to an MRP area | BERID, WERKS, LGORT | Which storage locations belong to a storage location MRP area |
A: Table | MDMA | MRP area data for a material | MATNR, BERID; WERKS, DISMM, DISPO, DISLS, MINBE | MRP parameters that override MARC for one MRP area |
A: Table | T024D | MRP controllers | WERKS, DISPO; DSNAM | Name of MRP controller and mail settings |
A: Table | T438A | MRP types | DISMM; DISVF procedure | Meaning of PD, VB, V1, ND and custom MRP types |
A: Table | T438M | MRP groups (group stored in field MTART) | WERKS, MTART | Planning horizon, strategy group and other MRP group settings |
A: Table | T439A | Lot-sizing procedures | DISLS | Meaning of EX, FX, WB, HB and custom lot sizes |
A: Table | T399D | MRP control parameters per plant | WERKS; PLAHZ, UMTHZ, NKPAF, NKBAN | Plant parameters: planning horizon, number ranges, firming |
A: Table | PLAF | Planned orders | PLNUM; MATNR, PLWRK, GSMNG, PSTTR, PEDTR | Open planned orders from MRP |
A: Table | EBAN | Purchase requisitions | BANFN, BNFPO; MATNR, WERKS, MENGE, LFDAT | Requisitions created by MRP (ESTKZ shows the creation indicator) |
A: Table | RESB | Reservations and dependent requirements | RSNUM, RSPOS, RSART; MATNR, BDMNG, BDTER | Dependent requirements of planned and production orders |
A: Table | PBIM | Planned independent requirements, header per material | MATNR, WERKS, BEDAE, VERSB, PBDNR; BDZEI | PIR versions and requirement types |
A: Table | PBED | Planned independent requirements, schedule lines | BDZEI, PDATU; PLNMG | PIR quantities per period (join to PBIM on BDZEI) |
A: Table | MARC (MRP fields) | Plant data for material, MRP views | MATNR, WERKS; DISMM, DISPO, DISLS, BESKZ, SOBSL, DISGR, EISBE, PLIFZ | Main MRP settings per plant |
B: DELKZ code | AR | Dependent reservation | RESB | Requirement |
B: DELKZ code | BA | Purchase requisition | EBAN | Receipt |
B: DELKZ code | BB | Subcontractor requirements of material provided | RESB (subcontract PO components) | Requirement |
B: DELKZ code | BE | Purchase order item schedule line | EKET | Receipt |
B: DELKZ code | BR | Process order | AFKO / AFPO | Receipt |
B: DELKZ code | FE | Production order | AFKO / AFPO | Receipt |
B: DELKZ code | IH | Maintenance order | AUFK / AFIH | Order element |
B: DELKZ code | KB | Individual customer stock | MSKA | Stock |
B: DELKZ code | LA | Shipping notification | EKES | Receipt |
B: DELKZ code | LE | Scheduling agreement schedule line | EKET | Receipt |
B: DELKZ code | LK | Stock with subcontractor | MSLB | Stock |
B: DELKZ code | MR | Reservation | RESB | Requirement |
B: DELKZ code | NE | Network order | AUFK / AFKO | Order element |
B: DELKZ code | PA | Planned order | PLAF | Receipt |
B: DELKZ code | PB | Project stock | MSPR | Stock |
B: DELKZ code | PP | Planned independent requirement | PBIM / PBED | Requirement |
B: DELKZ code | QM | Inspection lot for quality management | QALS | Receipt |
B: DELKZ code | SB | Dependent requirement | RESB | Requirement |
B: DELKZ code | SH | Safety stock | MARC-EISBE / MDMA | Requirement |
B: DELKZ code | U1 | Release order for a stock transfer order | EKET / EKPO in issuing plant | Requirement |
B: DELKZ code | U2 | Release order for a stock transfer requisition | EBAN in issuing plant | Requirement |
B: DELKZ code | U4 | Release order for stock transport scheduling agreement | EKET in issuing plant | Requirement |
B: DELKZ code | UR | Stock transfer reservation | RESB | Requirement or receipt |
B: DELKZ code | VC | Sales order | VBAP / VBEP | Requirement |
B: DELKZ code | VE | SD scheduling agreement | VBEP | Requirement |
B: DELKZ code | VJ | Delivery | LIPS | Requirement |
B: DELKZ code | WB | Plant stock | MARD | Stock |
B: DELKZ code | CH | Batch stock | MCHB | Stock |
B: DELKZ code | JI | JIT call | JIT call tables | Requirement |
DELKZ meanings are the fixed values of the MRP element domain in SAP ECC 6.0 (field MDTB-DELKZ). Source tables show where the underlying document lives; MD04 reads them live rather than from MDTB. Check SE11 in your release for industry-specific values.
Get an MRP exception report built from your tables
Tell us your plants and MRP controllers and we will outline a read-only report over MDKP, MDTB and the source documents.
Optional. The tool and every export work without this. No spam.
Where MRP data lives in SAP ECC
The planning file (MDVM, or DBVM when MRP areas are active) tells the next run which materials changed; MD20 and MD21 maintain and display it, and MDAB or MDRE rebuild it. MRP itself runs with MD01 (total planning online), MDBT (total planning in background), MD02 (single item, multi-level) and MD03 (single item, single level). The run creates planned orders (PLAF), purchase requisitions (EBAN) and schedule lines, and dependent requirements in RESB. If you save MRP lists, MDKP and MDTB store the result per material as shown in MD05. MD04, the stock/requirements list, is built live from the source documents every time you open it, so it is always current while MD05 reflects the last run. MRP Live (MD01N) is S/4HANA only.
- MD04: live stock/requirements list
- MD05: stored MRP list (MDKP / MDTB)
- MD21: display planning file entries
- MD06: collective MRP list display
Worked example: exceptions for one MRP controller
To list exception messages for MRP controller 001 in plant 1000, read MDKP where PLWRK = 1000 and DISPO = 001 to get the DTNUM values, then read MDTB for those DTNUM where AUSSL is not blank. AUSSL holds the exception key (for example 10 reschedule in, 15 reschedule out, 20 cancel). DELKZ on each row tells you whether the line is a planned order (PA), purchase requisition (BA), PO schedule line (BE) or sales order (VC), and DELNR gives the document number. MD06 shows the same collective list on screen; MDKP and MDTB are only filled when the MRP run creates MRP lists (creation indicator in MD01 or the MRP group).
Gotchas
MDTB is empty if MRP lists are not created, which is common after switching to MD04-only work. The MRP group is in T438M under field MTART, not DISGR, which confuses many SE16 queries. MRP areas move material parameters from MARC to MDMA; if a material has an MRP area, check MDMA before trusting MARC-DISPO. DBVM replaces MDVM as the planning file once MRP areas are activated in Customizing. Safety stock (SH) and plant stock (WB) are not documents, so they have no DELNR.
How to check the result in the system
Open MD04 for the same material and plant and compare each line's element label with the DELKZ codes in this table. For a stored list, MD05 shows exactly what MDTB holds. If counts differ, the MRP list is older than the documents; rerun MD03 for that material and compare again.
Frequently Asked Questions
Which table stores the MRP controller in SAP?
MRP controllers are defined in T024D (key plant and DISPO, with the name in DSNAM). The controller assigned to a material is MARC-DISPO, or MDMA-DISPO when the material is planned in an MRP area. Maintain them in Customizing under MRP controllers.
Which table stores MRP areas?
MDLV holds the MRP area definitions with type and plant, MDLG the storage locations assigned to a storage location MRP area, and MDMA the material data per MRP area. With MRP areas active, the planning file moves to DBVM, which includes the MRP area field BERID.
What is the MRP element table in SAP?
MDTB stores MRP list items with the MRP element code in DELKZ, such as PA planned order, BA purchase requisition, BE PO schedule line, VC sales order and SB dependent requirement. MDKP is its header. The documents themselves stay in PLAF, EBAN, EKET, VBEP and RESB.
Where is the MRP group stored?
The MRP group assigned to a material is MARC-DISGR. The MRP group definitions are in T438M, keyed by plant and the MRP group, which is stored in a field named MTART in that table. Maintain them in OPPR.
If your planners want to ask SAP ECC in plain English which orders are late against MRP and why, we can add a private AI layer over your MRP tables on your own servers.
Related Tools
SAP MRP Types and MD01 Run Parameters Reference
Reference of the MRP types on the material master and the parameters you set when starting the MRP run in MD01.
SAPSAP MRP Type Reference
Searchable list of SAP MRP types, lot sizing procedures, procurement types and special procurement keys used in the material master MRP views.
SAPSAP ECC Movement Type to OBYC Transaction Key and GBB Account Modifier Reference
Look up which OBYC transaction key and GBB account modifier a SAP ECC movement type uses, so you know which G/L account a goods movement will hit.
Developer ToolsSAP ECC Data Dictionary and Repository Tables Reference (DD02L, DD03L, T100, E070, TSTC)
Which SAP table holds table names, field lists, domain values, messages, transports and transaction codes, with key fields and join paths.
More SAP tools
See all- SAP ECC Private AI Layer Blueprint Generator
- SAP ECC AI Assistant Sizing and Value Calculator
- SAP ECC SD User Exit Forms Reference (MV45AFZZ, RV60AFZZ, MV50AFZ1)
- SAP ECC Customer Exits (SMOD Enhancements) by Module Reference
- SAP ECC Classic BAdI Definitions Reference (MIGO, ME21N, MIRO, Deliveries, PM Orders)
- SAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)
- SAP ECC Output Determination Tables and Codes Reference (NAST, TNAPR, NACE)
- SAP ECC Movement Type Configuration Tables Reference (T156, T156T, T157D)
- SAP ECC Stock Type and Location Transfer Movement Type Matrix
Keep exploring
Free tools
- SAP Cost Element Categories ReferenceA searchable list of SAP CO cost element categories, S/4HANA account types and the master data objects around them.
- SAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)Reference of the tables behind SM37 on SAP ECC 6.0: job header, steps, schedules, events, spool and variants, with joins, plus the TBTCO-STATUS values.
- SAP ECC Output Determination Tables and Codes Reference (NAST, TNAPR, NACE)Reference of NAST-based output control on SAP ECC 6.0: tables, application codes, transmission media, processing status values and standard output types with driver programs.
ERP fixes and how-tos
- How to Read MD04 Exception Messages in SAPMD04 exception icons tell a planner why a procurement element no longer matches demand. Read the element detail and act on it, not just rerun MRP.
- SAP KI 235: G/L Account Requires an Assignment to a CO ObjectSAP KI 235 fires when a P&L G/L account has no cost element or the posting carries no valid CO account assignment. Fix it with KA01/KA02 or a default assignment.
- How to add AI to SAP ECC 6.0 on-prem without moving data to a cloudReference architecture for a private on-prem AI assistant on SAP ECC 6.0: RFC and BAPI reads, SLT replica, retrieval index, local LLM, permission mirroring.
AI on your ERP
- AI Agents for SAP Production Planning, MRP, and Exception TriageAI agents that triage SAP MD04 exceptions, explain predictive MRP shortages, and draft planned-order actions, grounded on your own SAP data, deployed on-prem.
- AI for SAP Plant Maintenance: Notifications, Work Orders, and Predictive SignalsAI grounded on SAP PM data that triages notifications, drafts work orders, standardizes failure codes, and flags predictive maintenance signals, on-prem.
Integrations
- How to add AI agents to SAP ECC 6.0How to add AI agents to SAP ECC 6.0: a tool layer over BAPIs, RFC and IDocs, human approval before any posting, and an on-prem model that never leaves your network.
- How to connect Power BI to SAP ECC 6.0Connect Power BI to SAP ECC 6.0: SAP ERP connector, BW and warehouse options, on-prem data gateway, key manufacturing dashboards, and adding natural-language Q&A.