KDPBO SAP (Open allocations from customer reqmt/reservation/dep.reqmt) Structure details
Description: Open allocations from customer reqmt/reservation/dep.reqmt
Structure field list including key, data, relationships and ABAP select examples
KDPBO 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 "Open allocations from customer reqmt/reservation/dep.reqmt" 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_KDPBO TYPE KDPBO.
The KDPBO table consists of various fields, each holding specific information or linking keys about Open allocations from customer reqmt/reservation/dep.reqmt data available in SAP. These include DAT00 (Receipt/Requirements date), SORT2 (Sort indicator 02), VRMNG (Quantity), BDART (Requirement type).. 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 KDPBO 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 |
| PLAKZ | Indicator for planning segment | PLAKZ | CHAR | 1 | PLAKZ | ||||
| DAT00 | Receipt/Requirements date | DAT00 | DATS | 8 | DATUM | ||||
| SORT2 | Sort indicator 02 | SORT2 | CHAR | 2 | SORT2 | ||||
| VRMNG | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
| BDART | Requirement type | BDART | CHAR | 2 | BDART | BDA |
| Key field | Non-key field |
How do I retrieve data from SAP structure KDPBO using ABAP code?
As KDPBO 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 KDPBO as there is no data to select.How to access SAP table KDPBO
Within an ECC or HANA version of SAP you can also view further information about KDPBO 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