PKWAITING_KANBAN SAP (Waiting Kanban in Trigger Group) Structure details
Description: Waiting Kanban in Trigger Group
Related tables to PKWAITING_KANBAN
Access table PKWAITING_KANBAN
Structure field list including key, data, relationships and ABAP select examples
PKWAITING_KANBAN 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 "Waiting Kanban in Trigger Group" 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_PKWAITING_KANBAN TYPE PKWAITING_KANBAN.
The PKWAITING_KANBAN table consists of various fields, each holding specific information or linking keys about Waiting Kanban in Trigger Group data available in SAP. These include TRIGAZ (Trigger Point for Waiting Kanbans), MANDT (Client), PKKEY (Identification Number), PKNUM (Control cycle 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 PKWAITING_KANBAN 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 |
| TRIGGR | Trigger Group | TRIGGR | CHAR | 10 | TRIGGR | ||||
| TRIGAZ | Trigger Point for Waiting Kanbans | TRIGAZ | NUMC | 3 | BEHAZ | ||||
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| PKKEY | Identification Number | PKKEY | NUMC | 10 | Assigned to domain | PKKEY | |||
| PKNUM | Control cycle number | PKNUM | CHAR | 7 | PKHD | ALPHA | PKNUM | PKNUM | |
| PKPOS | Kanban item number / control cycle item | PKPOS | NUMC | 3 | PKPOS | ||||
| PKBST | Kanban status | PKBST | CHAR | 1 | PKBST | ||||
| PKIMG | Actual quantity | PKIMG | QUAN | 13(3) | MENG13 | ||||
| SAEDT | Date of last change | SAEDT | DATS | 8 | DATUM | ||||
| SAEUZ | Time of the last status change | SAEUZ | TIMS | 6 | UZEIT | ||||
| SADT2 | Date of last change | SAEDT | DATS | 8 | DATUM | ||||
| SAUZ2 | Time of the last status change | SAEUZ | TIMS | 6 | UZEIT | ||||
| PLNUM | Planned order number | PLNUM | CHAR | 10 | PLAF | ALPHA | PLNUM | PAF | |
| AUFNR | Order Number | AUFNR | CHAR | 12 | AUFK | ALPHA | AUFNR | ANR | |
| POSNR | Order Item Number | CO_POSNR | NUMC | 4 | CO_POSNR | ||||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | EKKO | ALPHA | EBELN | BES | MEKK_C |
| EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | EKPO | EBELP | BSP | ||
| ETENR | Delivery Schedule Line Counter | EETEN | NUMC | 4 | Assigned to domain | EETEN | |||
| RSNUM | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | RESB | 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 | ||
| TBPOS | Transfer Requirement Item | TBPOS | NUMC | 4 | TBPOS | TBP | |||
| SPKKZ | Blocking indicator for kanban container | SPKKZ | CHAR | 1 | XFELD | ||||
| MBLNR | Number of Material Document | MBLNR | CHAR | 10 | ALPHA | BELNR | MBN | ||
| MBLPO | Item in Material Document | MBLPO | NUMC | 4 | MBLPO | POS | |||
| PKLKZ | Deletion Indicator for a Kanban | PKLKZ | CHAR | 1 | XFELD | ||||
| PKBMG | Quantity requested | PKBMG | QUAN | 13(3) | MENG13 | ||||
| PKBSA | Previous kanban status | PKBSA | CHAR | 1 | PKBST | ||||
| PABNUM | JIT Call Number | PABNUM | CHAR | 10 | Assigned to domain | ALPHA | PABNUM | PABNUM | |
| PABPOS | JIT call item | PABPOS | NUMC | 4 | PABPOS | ||||
| PKGPZG | Planned Receipt | PKGPZG | DEC | 15 | TZNTSTMPS | ||||
| HDFLG | Indicator: Changed Control Cycle Data Available for Kanban | HDFLG | CHAR | 1 | XFELD | ||||
| ETENS | Sequential Number of Vendor Confirmation | ETENS | NUMC | 4 | EKES | NUM04 | |||
| ZPUNKT | Reporting Point | SA_ZPUNKT | CHAR | 4 | NUMCV | VORNR | |||
| PRTNR | Confirmation number | PRTNR | NUMC | 10 | Assigned to domain | PRTNR | CONFNUMBER | ||
| 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 | |||
| TIMESTAMP | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
| MARKED | New Input Values | XFLAG | CHAR | 1 | XFLAG |
| Key field | Non-key field |
How do I retrieve data from SAP structure PKWAITING_KANBAN using ABAP code?
As PKWAITING_KANBAN 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 PKWAITING_KANBAN as there is no data to select.How to access SAP table PKWAITING_KANBAN
Within an ECC or HANA version of SAP you can also view further information about PKWAITING_KANBAN 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