PBKD SAP (Allocation index: customer reqmts to ind. requirements) Structure details
Description: Allocation index: customer reqmts to ind. requirements
Structure field list including key, data, relationships and ABAP select examples
PBKD 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 "Allocation index: customer reqmts to ind. 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_PBKD TYPE PBKD.
The PBKD table consists of various fields, each holding specific information or linking keys about Allocation index: customer reqmts to ind. requirements data available in SAP. These include PDATU (Delivery/order finish date), ZAEHL (Log counter), SORT2 (Sort indicator 02), RSNUM (Number of Reservation/Dependent Requirement).. 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 PBKD 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 | ||||
| ZAEHL | Log counter | DZAEHR | NUMC | 4 | NUM4 | ||||
| SORT2 | Sort indicator 02 | SORT2 | CHAR | 2 | SORT2 | ||||
| RSNUM | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | Assigned to domain | RSNUM | RES | ||
| RSPOS | Item Number of Reservation/Dependent Requirement | RSPOS | NUMC | 4 | RSPOS | RPO | |||
| KDAUF | Sales Order Number | KDAUF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
| DAT00 | Receipt/Requirements date | DAT00 | DATS | 8 | DATUM | ||||
| VRMNG | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
| VPMAT | Planning material | VPMAT | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
| VPWRK | Planning plant | VPWRK | CHAR | 4 | Assigned to domain | WERKS | |||
| UMREF | Conversion factor: quantities | UMREFF | FLTP | 16(16) | FLTP | ||||
| KDURP | Sales order source | KDURP | CHAR | 1 | CHAR1 | ||||
| BDART | Requirement type | BDART | CHAR | 2 | BDART | BDA | |||
| POSNR | Requirements plan item | BEDPP | NUMC | 6 | NUM06 | BDP | |||
| DELKZ | MRP element | DELKZ | CHAR | 2 | DELKZ | ||||
| KDEIN | Delivery Schedule for Sales Order | KDEIN | NUMC | 4 | NUM04 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PBKD using ABAP code?
As PBKD 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 PBKD as there is no data to select.How to access SAP table PBKD
Within an ECC or HANA version of SAP you can also view further information about PBKD 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