MDZU SAP (Pegging: receipts table) Structure details
Description: Pegging: receipts table
Structure field list including key, data, relationships and ABAP select examples
MDZU 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 "Pegging: receipts table" 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_MDZU TYPE MDZU.
The MDZU table consists of various fields, each holding specific information or linking keys about Pegging: receipts table data available in SAP. These include DELPS (MRP element item), DELET (Schedule Line Number MRP Element), DELKZ (MRP element), MATNR (Material Number).. 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 MDZU 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 |
DELNR | MRP element number | DEL12 | CHAR | 12 | DEL12 | ||||
DELPS | MRP element item | DELPS | NUMC | 6 | DELPS | ||||
DELET | Schedule Line Number MRP Element | DELET | NUMC | 4 | DELET | ||||
DELKZ | MRP element | DELKZ | CHAR | 2 | DELKZ | ||||
MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
BERID | MRP Area | BERID | CHAR | 10 | Assigned to domain | BERID | BERID | ||
PLAAB | Material requirements planning segment | PLAAB | NUMC | 2 | PLAAB | ||||
PLANR | Planning segment number | PLANR | CHAR | 20 | PLANR | ||||
DAT00 | Receipt/Requirements date | DAT00 | DATS | 8 | DATUM | ||||
BAART | P.O./Order type | BAART | CHAR | 4 | BAART | ||||
VERSB | Version number for independent requirements | VERSB | CHAR | 2 | Assigned to domain | VERSB | VES | ||
MNG01 | Quantity received or quantity required | MNG01 | QUAN | 13(3) | MENGV13 | ||||
MNG02 | Quantity received or quantity required | MNG01 | QUAN | 13(3) | MENGV13 | ||||
INDEX | Field defined as in SY-TABIX | TABIX_D | INT4 | 10 | TABIX | ||||
ALLOC | Pegging: flag: receipt is allocated to requirement | ALLOC | CHAR | 1 | XFELD | ||||
EXTRA | MRP element data | EXTRA | CHAR | 40 | CHAR40 |
Key field | Non-key field |
How do I retrieve data from SAP structure MDZU using ABAP code?
As MDZU 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 MDZU as there is no data to select.How to access SAP table MDZU
Within an ECC or HANA version of SAP you can also view further information about MDZU 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