LIKPUKWA SAP (Header and Status Data for Goods Issue and Reversal of GI) Structure details
Description: Header and Status Data for Goods Issue and Reversal of GI
Structure field list including key, data, relationships and ABAP select examples
LIKPUKWA 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 "Header and Status Data for Goods Issue and Reversal of GI" 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_LIKPUKWA TYPE LIKPUKWA.
The LIKPUKWA table consists of various fields, each holding specific information or linking keys about Header and Status Data for Goods Issue and Reversal of GI data available in SAP. These include VBELN (Delivery), STATUS (Carrier field for icons), ERNAM (Name of Person who Created the Object), ERZET (Entry time).. 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 LIKPUKWA 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 |
SELKZ | Selection flag | SELKZ | CHAR | 1 | SELKZ | ||||
VBELN | Delivery | VBELN_VL | CHAR | 10 | Assigned to domain | ALPHA | VBELN | VL | |
STATUS | Carrier field for icons | ICON_TEXT | CHAR | 132 | SYCHAR132 | ||||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
ERZET | Entry time | ERZET | TIMS | 6 | UZEIT | ||||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
BZIRK | Sales district | BZIRK | CHAR | 6 | Assigned to domain | BZIRK | BZI | ||
VSTEL | Shipping Point/Receiving Point | VSTEL | CHAR | 4 | Assigned to domain | VSTEL | VST | ||
VKORG | Sales Organization | VKORG | CHAR | 4 | Assigned to domain | VKORG | VKO | C_VKORG | |
LFART | Delivery Type | LFART | CHAR | 4 | Assigned to domain | LFART | ALT | ||
AUTLF | Complete delivery defined for each sales order? | AUTLF | CHAR | 1 | XFELD | ||||
KZAZU | Order Combination Indicator | KZAZU_D | CHAR | 1 | XFELD | ||||
WADAT | Goods Issue Date | WADAT | DATS | 8 | DATUM | ||||
LDDAT | Loading Date | LDDAT | DATS | 8 | DATUM | ||||
TDDAT | Transportation Planning Date | TDDAT_D | DATS | 8 | DATUM | ||||
LFDAT | Delivery Date | LFDAT_V | DATS | 8 | DATUM | ||||
KODAT | Picking Date | KODAT | DATS | 8 | DATUM | ||||
ROUTE | Route | ROUTE | CHAR | 6 | Assigned to domain | ROUTE | |||
VBTYP | SD document category | VBTYP | CHAR | 1 | VBTYP | ||||
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | KUN | C_KUNNR |
KUNAG | Sold-to party | KUNAG | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | VAG | |
ANZPK | Total number of packages in delivery | ANZPK | NUMC | 5 | ANZPK | ||||
LSTEL | Loading Point | LSTEL | CHAR | 2 | Assigned to domain | LSTEL | |||
TRAGR | Transportation Group | TRAGR | CHAR | 4 | Assigned to domain | TRAGR | |||
FKDAT | Billing date for billing index and printout | FKDAT | DATS | 8 | DATUM | ||||
LFSTK | Delivery status | LFSTK | CHAR | 1 | STATV | ||||
WBSTK | Total goods movement status | WBSTK | CHAR | 1 | STATV | ||||
FKSTK | Billing status | FKSTK | CHAR | 1 | STATV | ||||
GBSTK | Overall processing status of document | GBSTK | CHAR | 1 | STATV | ||||
KOSTK | Overall picking / putaway status | KOSTK | CHAR | 1 | STATV | ||||
KOQUK | Status of pick confirmation | KOQUK | CHAR | 1 | STATV | ||||
LVSTK | Overall status of warehouse management activities | LVSTK | CHAR | 1 | STATV | ||||
PKSTK | Overall packing status of all items | PKSTK | CHAR | 1 | STATV_PKST | ||||
TRSTA | Transportation planning status | TRSTA | CHAR | 1 | TRSTA | ||||
TKNUM | Shipment Number | TKNUM | CHAR | 10 | Assigned to domain | ALPHA | TKNUM | TNR | SD_F4_SHP_ID |
MBLNR | Number of Material Document | MBLNR | CHAR | 10 | ALPHA | BELNR | MBN | ||
STDAT | Local Date | SYSTDATLO | DATS | 8 | SYDATS | ||||
WADAT_IST | Actual Goods Movement Date | WADAT_IST | DATS | 8 | DATUM | WDTI | |||
PDSTK | POD status on header level | PDSTK | CHAR | 1 | STATV | ||||
STATUS_BEW | Optical status of a movement (icon) | STATUS_BEW | CHAR | 4 | ICON_4 | ||||
PODAT | Date (proof of delivery) | PODAT | DATS | 8 | DATUM | DAT | |||
POTIM | Confirmation time | POTIM | TIMS | 6 | TIME_PLANT | TIM | |||
KNFAK | Customer factory calendar | KNFAK | CHAR | 2 | Assigned to domain | WFCID | |||
LFUHR | Time of delivery | LFUHR | TIMS | 6 | LFUHR | ||||
MSR_ACTIVE | Advanced Returns Management Active | MSR_ACTIVE | CHAR | 1 | MSR_ACTIVE |
Key field | Non-key field |
How do I retrieve data from SAP structure LIKPUKWA using ABAP code?
As LIKPUKWA 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 LIKPUKWA as there is no data to select.How to access SAP table LIKPUKWA
Within an ECC or HANA version of SAP you can also view further information about LIKPUKWA 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