MDEZ SAP (Individual lines of the MRP elements) Structure details
Description: Individual lines of the MRP elements
Structure field list including key, data, relationships and ABAP select examples
MDEZ is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Individual lines of the MRP elements" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_MDEZ TYPE MDEZ.
The MDEZ table consists of various fields, each holding specific information or linking keys about Individual lines of the MRP elements data available in SAP. These include PLANR (Planning segment number), SORT0 (Numeric field length 8), TAG00 (Daily shift (sort indicator 0)), SORT1 (Sort indicator 01).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP MDEZ structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
PLAAB | Material requirements planning segment | PLAAB | NUMC | 2 | PLAAB | ||||
PLANR | Planning segment number | PLANR | CHAR | 20 | PLANR | ||||
SORT0 | Numeric field length 8 | NUM08 | NUMC | 8 | NUM08 | ||||
TAG00 | Daily shift (sort indicator 0) | TAG00 | NUMC | 2 | TAG00 | ||||
SORT1 | Sort indicator 01 | SORT1 | CHAR | 1 | SORT1 | ||||
SORT2 | Sort indicator 02 | SORT2 | CHAR | 2 | SORT2 | ||||
DELKZ | MRP element | DELKZ | CHAR | 2 | DELKZ | ||||
PLUMI | Receipt/issue indicator | PLUMI | CHAR | 1 | CHAR1 | ||||
VRFKZ | Availability indicator | VRFKZ | CHAR | 1 | VRFKZ | ||||
DAT00 | Receipt/Requirements date | DAT00 | DATS | 8 | DATUM | ||||
DAT01 | Delivery/order finish date | DAT01 | DATS | 8 | DATUM | ||||
DELB0 | Abbreviation for MRP element | DELB0 | CHAR | 6 | DELB0 | ||||
EXTRA | MRP element data | EXTRA | CHAR | 40 | CHAR40 | ||||
AUSSL | Exception message key | AUSSL | CHAR | 2 | Assigned to domain | AUSSL | |||
AUSKT | Exception message number | AUSKT | CHAR | 2 | AUSKT | ||||
MNG01 | Quantity received or quantity required | MNG01 | QUAN | 13(3) | MENGV13 | ||||
MNG02 | Available quantity | VRFMG | QUAN | 13(3) | MENGV13 | ||||
MNG03 | Available quantity | VRFMG | QUAN | 13(3) | MENGV13 | ||||
MNG04 | ATP quantity | MNG04 | QUAN | 13(3) | MENGV13 | ||||
FBYTE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
ALINE | Line index for internal table processing | XLINE | INT4 | 10 | XLINE | ||||
ZLINE | Line index for internal table processing | XLINE | INT4 | 10 | XLINE | ||||
SELKZ | Selection flag | SELKZ | CHAR | 1 | SELKZ | ||||
ABEKZ | Exception indicator | ABEKZ | CHAR | 1 | CHAR1 | ||||
VERID | Production Version | VERID | CHAR | 4 | Assigned to domain | VERID | VER | ||
SERNR | BOM explosion number | SERNR | CHAR | 8 | Assigned to domain | SERNR | |||
REVLV | Revision Level | REVLV | CHAR | 2 | NUMCV | REVLV | RVS | ||
MNAUS | Variable scrap quantity | MNG02 | QUAN | 13(3) | MENG13 | ||||
DAT02 | Start/release date | DAT02 | DATS | 8 | DATUM | ||||
DAT03 | Opening date | DAT03 | DATS | 8 | DATUM | ||||
SOBES | Special procurement type | SOBES | CHAR | 1 | SOBES | ||||
ESOBS | Special procurement - external display | ESOBS | CHAR | 1 | Assigned to domain | ESOBS | |||
WRK01 | Planning Plant | PLWRK | CHAR | 4 | Assigned to domain | WERKS | WRK | ||
WRK02 | Planning Plant | PLWRK | CHAR | 4 | Assigned to domain | WERKS | WRK | ||
SLOC2 | Issuing/Receiving Storage Location | SLOC2 | CHAR | 4 | Assigned to domain | LGORT | |||
LGORT | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
UMDAT | Rescheduling date | UMDAT | DATS | 8 | DATUM | ||||
LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
MD4KD | Customer name | MD4KD | CHAR | 35 | NAME | ||||
MD4LI | Vendor name | MD4LI | CHAR | 35 | NAME | ||||
LLMSG | Exception at a lower BOM level | LLMESSAGE | CHAR | 2 | Assigned to domain | AUSSL | |||
LLDLY | Delay for lower BOM levels | MDDELAY | INT4 | 10 | INT4 | ||||
TRAMG | MRP: stock in transit | TRAMG | QUAN | 13(3) | MENGV13 | ||||
USEX1 | Field to be filled by user exit | USEEX | CHAR | 30 | CHAR30 | ||||
USEX2 | Field to be filled by user exit | USEEX | CHAR | 30 | CHAR30 | ||||
USEX3 | Field to be filled by user exit | USEEX | CHAR | 30 | CHAR30 | ||||
SORT3 | Sort indicator for individual customer segments | SRTKD | NUMC | 8 | NUM8 | ||||
UNIV1 | Quantity received or quantity required | MNG01 | QUAN | 13(3) | MENGV13 | ||||
UNIV2 | Available quantity | VRFMG | QUAN | 13(3) | MENGV13 | ||||
UNIV3 | Text field | TEXT | CHAR | 29 | FL_TEXT | ||||
DETAIL_ICON | Carrier field for icons | ICON_TEXT | CHAR | 132 | SYCHAR132 | ||||
PRIO_URG | Requirement Urgency | PRIO_URG | NUMC | 2 | PURG | PRIO_URG | |||
PRIO_REQ | Requirement Priority | PRIO_REQ | NUMC | 3 | PREQ | PRIO_REQ | |||
MDMAT | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
MDLOC | Location of MRP Element | MDLOC | CHAR | 20 | |||||
MDWRK | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
MDBER | MRP Area | BERID | CHAR | 10 | Assigned to domain | BERID | BERID | ||
.INCLU--AP | 0 | ||||||||
MPNMT | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
Key field | Non-key field |
How do I retrieve data from SAP structure MDEZ using ABAP code?
As MDEZ is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on MDEZ as there is no data to select.How to access SAP table MDEZ
Within an ECC or HANA version of SAP you can also view further information about MDEZ and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects