PKKUM SAP (Structure of Container Data) Structure details
Description: Structure of Container Data
Structure field list including key, data, relationships and ABAP select examples
PKKUM 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 "Structure of Container Data" 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_PKKUM TYPE PKKUM.
The PKKUM table consists of various fields, each holding specific information or linking keys about Structure of Container Data data available in SAP. These include DAT00 (Receipt/Requirements date), PKBST (Kanban status), PLNUM (Planned order number), AUFNR (Order Number).. 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 PKKUM 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 |
MNG01 | Quantity received or quantity required | MNG01 | QUAN | 13(3) | MENGV13 | ||||
DAT00 | Receipt/Requirements date | DAT00 | DATS | 8 | DATUM | ||||
PKBST | Kanban status | PKBST | CHAR | 1 | PKBST | ||||
PLNUM | Planned order number | PLNUM | CHAR | 10 | Assigned to domain | ALPHA | PLNUM | PAF | |
AUFNR | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
POSNR | Order Item Number | CO_POSNR | NUMC | 4 | CO_POSNR | ||||
EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
ETENR | Delivery Schedule Line Number | ETENR | NUMC | 4 | Assigned to domain | ETENR | |||
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 | |||
TBNUM | Transfer Requirement Number | TBNUM | NUMC | 10 | Assigned to domain | TBNUM | TBN | ||
XCODE | Function code | XCODE | CHAR | 20 | FCODE | ||||
KONNR | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
KONTP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
BSART | Order Type (Purchasing) | BSART | CHAR | 4 | Assigned to domain | BSART | BSA | ||
UMWRK | Receiving/Issuing Plant | UMWRK | CHAR | 4 | Assigned to domain | WERKS | |||
PEDTR | Order finish date in the planned order | PEDTR | DATS | 8 | DATUM | ||||
LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
PSTYP | Item Category in Purchasing Document | PSTYP | CHAR | 1 | Assigned to domain | PSTYP | |||
PKBMG | Quantity requested | PKBMG | QUAN | 13(3) | MENG13 | ||||
PKLKZ | Deletion Indicator for a Kanban | PKLKZ | CHAR | 1 | XFELD | ||||
PABNUM | JIT Call Number | PABNUM | CHAR | 10 | Assigned to domain | ALPHA | PABNUM | PABNUM | |
PABPOS | JIT call item | PABPOS | NUMC | 4 | PABPOS | ||||
ETENS | Sequential Number of Vendor Confirmation | ETENS | NUMC | 4 | NUM04 | ||||
ZPUNKT | Reporting Point | SA_ZPUNKT | CHAR | 4 | NUMCV | VORNR | |||
VBELN | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
VBELP | Item number of the SD document | POSNR | NUMC | 6 | Assigned to domain | POSNR |
Key field | Non-key field |
How do I retrieve data from SAP structure PKKUM using ABAP code?
As PKKUM 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 PKKUM as there is no data to select.How to access SAP table PKKUM
Within an ECC or HANA version of SAP you can also view further information about PKKUM 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