MDALV_MD73_PBET SAP (Table for Splitting Data for Independent Requirements) Structure details
Description: Table for Splitting Data for Independent Requirements
Related tables to MDALV_MD73_PBET
Access table MDALV_MD73_PBET
Structure field list including key, data, relationships and ABAP select examples
MDALV_MD73_PBET 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 "Table for Splitting Data for Independent 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_MDALV_MD73_PBET TYPE MDALV_MD73_PBET.
The MDALV_MD73_PBET table consists of various fields, each holding specific information or linking keys about Table for Splitting Data for Independent Requirements data available in SAP. These include PDATU (Delivery/order finish date), ENTLU (Period indicator (day, week, month, posting period)), EDATU (Requirements date), PLNMG (Planned 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 MDALV_MD73_PBET 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 |
| BDZEI | Independent requirements pointer | BDZEI | NUMC | 12 | Assigned to domain | BDZEI | |||
| PDATU | Delivery/order finish date | DAT01 | DATS | 8 | DATUM | ||||
| ENTLU | Period indicator (day, week, month, posting period) | ENTLU | CHAR | 1 | Assigned to domain | PRGBZ | |||
| EDATU | Requirements date | EDATV | CHAR | 10 | CHAR10 | ||||
| PLNMG | Planned quantity | PLNMG | QUAN | 13(3) | MENG13 | ||||
| ENTMG | Withdrawal quantity | ENTMG | QUAN | 13(3) | MENG13 | ||||
| MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| TXTET | Indicator: long text exists | TXTKZ | CHAR | 1 | FLAG | ||||
| LAEDA | Date of Last Change | LAEDA | DATS | 8 | DATUM | ||||
| AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| SERNR | BOM explosion number | SERNR | CHAR | 8 | Assigned to domain | SERNR | |||
| VERID | Production Version | VERID | CHAR | 4 | Assigned to domain | VERID | VER | ||
| TECHS | Parameter Variant/Standard Variant | TECHS | CHAR | 12 | TECHS | ||||
| STPKT | Supporting point for independent requirements | STPKT | CHAR | 1 | CHAR1 | ||||
| CUOBJ | Configuration (internal object number) | CUOBJ | NUMC | 18 | CUOBJ | CUX |
| Key field | Non-key field |
How do I retrieve data from SAP structure MDALV_MD73_PBET using ABAP code?
As MDALV_MD73_PBET 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 MDALV_MD73_PBET as there is no data to select.How to access SAP table MDALV_MD73_PBET
Within an ECC or HANA version of SAP you can also view further information about MDALV_MD73_PBET 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