PEKPO SAP (Auxiliary Fields, Purchasing Document Item Printout) Structure details
Dictionary Type: Structure
Description: Auxiliary Fields, Purchasing Document Item Printout
Description: Auxiliary Fields, Purchasing Document Item Printout
Structure field list including key, data, relationships and ABAP select examples
PEKPO 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 "Auxiliary Fields, Purchasing Document Item Printout" 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_PEKPO TYPE PEKPO.
The PEKPO table consists of various fields, each holding specific information or linking keys about Auxiliary Fields, Purchasing Document Item Printout data available in SAP. These include LPEIN (Category of Delivery Date), EINDT (Item Delivery Date), UZEIT (Delivery Date Time-Spot), WEMNG (Quantity of Goods Received).. 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 PEKPO 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 |
| EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | EKPO | EBELP | BSP | ||
| LPEIN | Category of Delivery Date | LPEIN | CHAR | 1 | TPRG | PRGBZ | |||
| EINDT | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
| UZEIT | Delivery Date Time-Spot | LZEIT | TIMS | 6 | UZEIT | ||||
| WEMNG | Quantity of Goods Received | WEEMG | QUAN | 13(3) | MENG13 | ||||
| MAHNZ | Number of Reminders/Expediters | MAHNZ | DEC | 3 | PACK2 | ||||
| LICHA | Vendor Batch Number | LICHN | CHAR | 15 | LICHN | ||||
| XBLNR | Delivery note number | BLNRX | CHAR | 35 | CHAR35 | ||||
| LWEMG | Quantity of Goods Received | WEEMG | QUAN | 13(3) | MENG13 | ||||
| BUDAT | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| LFDAT | Delivery Date | LFDAT_V | DATS | 8 | DATUM | ||||
| TPRIN | Time (print format) | TPRIN | CHAR | 5 | CHAR5 | ||||
| RLDAT | Date of return delivery | RDATU | DATS | 8 | DATS | ||||
| RLBNR | Document number of return delivery | RLBNR | CHAR | 10 | ALPHA | BELNR | |||
| RLMNG | Quantity of return delivery | RLFMG | QUAN | 13(3) | MENG13 | ||||
| WEMPF | Goods Recipient/Ship-To Party | WEMPF | CHAR | 12 | WEMPF | ||||
| ABLAD | Unloading Point | ABLAD | CHAR | 25 | TEXT25 | ||||
| BSMNG | Quantity as Per Vendor Confirmation | BBMNG | QUAN | 13(3) | MENGE | ||||
| MSR_ID | Process Identification Number | MSR_PROCESS_ID | CHAR | 10 | ALPHA | MSR_PROCESS_ID | |||
| MSR_ITEM | Item Number | MSR_PROCESS_ITEM | NUMC | 6 | MSR_PROCESS_ITEM | ||||
| MSR_RET_REASON | Return Reason | MSR_RETURNS_REASON | CHAR | 3 | Assigned to domain | MSR_RETURNS_REASON | |||
| MSR_RET_REASON_TEXT | Return Reason Description | MSR_RET_REASON_TEXT | CHAR | 60 | TEXT60 | ||||
| MSR_FORW_VENDOR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| MSR_FWV_TITLE | Form-of-Address Key | AD_TITLE | CHAR | 4 | Assigned to domain | AD_TITLE | |||
| MSR_FWV_ADDRNUM | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| MSR_FWV_NAME1 | Name 1 | AD_NAME1 | CHAR | 40 | TEXT40 | ||||
| MSR_FWV_NAME2 | Name 2 | AD_NAME2 | CHAR | 40 | TEXT40 | ||||
| MSR_FWV_NAME3 | Name 3 | AD_NAME3 | CHAR | 40 | TEXT40 | ||||
| MSR_FWV_NAME4 | Name 4 | AD_NAME4 | CHAR | 40 | TEXT40 | ||||
| MSR_FWV_STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
| MSR_FWV_PO_BOX | PO Box | AD_POBX | CHAR | 10 | CHAR10 | ||||
| MSR_FWV_PO_BOX_LOC | PO Box city | AD_POBXLOC | CHAR | 40 | TEXT40 | CITY_NAME | |||
| MSR_FWV_CITY_CODE2 | City PO box code (City file) | AD_CIT2NUM | CHAR | 12 | Assigned to domain | ALPHA | CITY_CODE | ||
| MSR_FWV_COUNTRY | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| MSR_FWV_LANGU | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| MSR_FWV_POST_CODE1 | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
| MSR_FWV_CITY1 | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
| MSR_FWV_CITY2 | District | AD_CITY2 | CHAR | 40 | TEXT40 | CITY_PART | |||
| MSR_FWV_REGION | STATE (State, Province, County) | REGIO | CHAR | 3 | Assigned to domain | REGIO | |||
| RMA_VENDOR | Vendor RMA Number | MSR_VRMA_NR | CHAR | 20 | MSR_RMA_NR | ||||
| MSR_FORW_PLANT1 | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| MSR_PLANT1_TXT | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| MSR_FORW_PLANT2 | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| MSR_PLANT2_TXT | Name | NAME1 | CHAR | 30 | TEXT30 | ||||
| MSR_FORW_PLANT3 | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| MSR_PLANT3_TXT | Name | NAME1 | CHAR | 30 | TEXT30 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PEKPO using ABAP code?
As PEKPO 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 PEKPO as there is no data to select.How to access SAP table PEKPO
Within an ECC or HANA version of SAP you can also view further information about PEKPO 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