PBTDT SAP (Work table: maintaining independent requirements) Structure details
Description: Work table: maintaining independent requirements
Structure field list including key, data, relationships and ABAP select examples
PBTDT 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 "Work table: maintaining 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_PBTDT TYPE PBTDT.
The PBTDT table consists of various fields, each holding specific information or linking keys about Work table: maintaining independent requirements data available in SAP. These include MATNR (Material Number), BEDPL (Activating requirements planning), BEDPP (Requirements plan item), DAT01 (Delivery/order finish date).. 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 PBTDT 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 |
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| BEDPL | Activating requirements planning | BEDPL | CHAR | 1 | XFELD | ||||
| BEDPP | Requirements plan item | BEDPP | NUMC | 6 | NUM06 | BDP | |||
| DAT01 | Delivery/order finish date | DAT01 | DATS | 8 | DATUM | ||||
| PLNMG | Planned quantity | PLNMG | QUAN | 13(3) | MENG13 | ||||
| ENTMG | Withdrawal quantity | ENTMG | QUAN | 13(3) | MENG13 | ||||
| UPLMG | Originally planned quantity | UPLMG | QUAN | 13(3) | MENG13 | ||||
| ZUMNG | Dynamically allocated quantity | DZUMNG | QUAN | 13(3) | MENG13 | ||||
| WDATU | Reqstd date | WDATU | DATS | 8 | DATUM | ||||
| PERKZ | Period Indicator | PERKZ | CHAR | 1 | PERKZ | PKZ | |||
| PERXX | Planning period | PERXX | CHAR | 6 | PERIOD | ||||
| DBVKZ | Indicator: reqmts date already exists in database | DBVKZ | CHAR | 1 | X | ||||
| SERNR | BOM explosion number | SERNR | CHAR | 8 | Assigned to domain | SERNR | |||
| ZUOKR | Criterion for allocation | DZUOKR | CHAR | 16 | ZUOKR |
| Key field | Non-key field |
How do I retrieve data from SAP structure PBTDT using ABAP code?
As PBTDT 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 PBTDT as there is no data to select.How to access SAP table PBTDT
Within an ECC or HANA version of SAP you can also view further information about PBTDT 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