MDNB SAP (Net requirements) Structure details
Description: Net requirements
Structure field list including key, data, relationships and ABAP select examples
MDNB 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 "Net requirements" 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_MDNB TYPE MDNB.
The MDNB table consists of various fields, each holding specific information or linking keys about Net requirements data available in SAP. These include PLANR (Planning segment number), DAT00 (Receipt/Requirements date), MNG01 (Quantity received or quantity required), MNG03 (Shortage Quantity).. 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 MDNB 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 | ||||
| DAT00 | Receipt/Requirements date | DAT00 | DATS | 8 | DATUM | ||||
| MNG01 | Quantity received or quantity required | MNG01 | QUAN | 13(3) | MENGV13 | ||||
| MNG03 | Shortage Quantity | MNG03 | QUAN | 13(3) | MENG13 | ||||
| SERNR | BOM explosion number | SERNR | CHAR | 8 | Assigned to domain | SERNR | |||
| VERID | Production Version | VERID | CHAR | 4 | Assigned to domain | VERID | VER | ||
| CUOBJ | Configuration (internal object number) | CUOBJ | NUMC | 18 | CUOBJ | CUX | |||
| KNTTP | Account Assignment Category | KNTTP | CHAR | 1 | Assigned to domain | KNTTP | KNT | ||
| SOBKZ | Special Stock Indicator | SOBKZ | CHAR | 1 | Assigned to domain | SOBKZ | |||
| KZVBR | Consumption Posting | KZVBR | CHAR | 1 | KZVBR | ||||
| KZBWS | Valuation of Special Stock | KZBWS | CHAR | 1 | KZBWS | ||||
| KDAUF | Sales Order Number | KDAUF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
| PSPEL | WBS Element | PS_POSNR | NUMC | 8 | Assigned to domain | ABPSP | PS_POSNR | ||
| ARSNR | Settlement reservation number | ARSNR | NUMC | 10 | MDNUM | ||||
| ARSPS | Item number of the settlement reservation | ARSPS | NUMC | 4 | RSPOS | ||||
| MONKZ | Indicator: for assembly order procedures | MONKZ | CHAR | 1 | XFELD | ||||
| VRPLA | Indicator: planning without final assembly | VRPLA | CHAR | 1 | XFELD | ||||
| PBDNR | Requirements Plan Number | PBDNR | CHAR | 10 | CHAR10 | PBN | |||
| TECHS | Parameter Variant/Standard Variant | TECHS | CHAR | 12 | TECHS | ||||
| EDGNO | Internal number for edge of object dependencies tree | EDGNO | NUMC | 17 | Assigned to domain | EDGNO | |||
| UMREZ | Numerator for Conversion to Base Units of Measure | UMREZ | DEC | 5 | UMBSZ | ||||
| UMREN | Denominator for conversion to base units of measure | UMREN | DEC | 5 | UMBSN | ||||
| ERFME | Unit of Entry | ERFME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| DBSKZ | Direct procurement indicator | DBSKZ | CHAR | 1 | DBSKZ | ||||
| WRK02 | Planning/production plant | WRK02 | CHAR | 4 | Assigned to domain | WERKS | |||
| STLTY | BOM category | STLTY | CHAR | 1 | STLTY | ||||
| STLNR | Bill of material | STNUM | CHAR | 8 | NUMCV | STNUM | STLNR | ||
| STLKN | BOM item node number | STLKN | NUMC | 8 | KNTNR | ||||
| STPOZ | Internal counter | CIM_COUNT | NUMC | 8 | CIM_COUNT | ||||
| .INCLU--AP | 0 | ||||||||
| KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
| Key field | Non-key field |
How do I retrieve data from SAP structure MDNB using ABAP code?
As MDNB 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 MDNB as there is no data to select.How to access SAP table MDNB
Within an ECC or HANA version of SAP you can also view further information about MDNB 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