BBPEKBE SAP (Transfer Structure for PO History) Structure details
Description: Transfer Structure for PO History
Structure field list including key, data, relationships and ABAP select examples
BBPEKBE 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 "Transfer Structure for PO History" 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_BBPEKBE TYPE BBPEKBE.
The BBPEKBE table consists of various fields, each holding specific information or linking keys about Transfer Structure for PO History data available in SAP. These include SERIAL_NO (Sequential Number of Account Assignment), PROCESS_ID (Transaction/event type, purchase order history), DOC_YEAR (Material Document Year), MAT_DOC (Number of Material Document).. 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: Cannot Be Enhanced
SAP BBPEKBE 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 |
| PO_ITEM | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
| SERIAL_NO | Sequential Number of Account Assignment | BBPZEKKN | NUMC | 2 | NUM02 | ||||
| PROCESS_ID | Transaction/event type, purchase order history | VGABE | CHAR | 1 | VGABE | ||||
| DOC_YEAR | Material Document Year | MJAHR | NUMC | 4 | GJAHR | GJAHR | MJA | ||
| MAT_DOC | Number of Material Document | MBLNR | CHAR | 10 | ALPHA | BELNR | MBN | ||
| MATDOC_ITM | Item in Material Document | MBLPO | NUMC | 4 | MBLPO | POS | |||
| HIST_TYPE | PO history category | BEWTP | CHAR | 1 | Assigned to domain | BEWTP | |||
| MOVE_TYPE | Movement Type (Inventory Management) | BWART | CHAR | 3 | Assigned to domain | BWART | BWA | ||
| PSTNG_DATE | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| QUANTITY | Quantity | BBPMENGE | QUAN | 13(3) | MENG13 | ||||
| VAL_LOCCUR | Currency Amount in BAPI Interfaces | BBPCURR | DEC | 23(4) | BBPCURR | ||||
| VAL_FORCUR | Currency Amount in BAPI Interfaces | BBPCURR | DEC | 23(4) | BBPCURR | ||||
| CURRENCY | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| CL_VAL_LOC | Currency Amount in BAPI Interfaces | BBPCURR | DEC | 23(4) | BBPCURR | ||||
| BLOCKED_QY | Goods Receipt Blocked Stock in Order Unit | WESBS | QUAN | 13(3) | MENG13 | ||||
| BL_QTY | Quantity in GR blocked stock in order price unit | BPWES | QUAN | 13(3) | MENG13 | ||||
| DB_CR_IND | Debit/Credit Indicator | SHKZG | CHAR | 1 | SHKZG | ||||
| VAL_TYPE | Valuation type | BBPBWTAR | CHAR | 10 | CHAR10 | BWT | |||
| NO_MORE_GR | 'Delivery Completed' Indicator | ELIKZ | CHAR | 1 | XFELD | ||||
| REF_DOC_NO | Reference Document Number | XBLNR | CHAR | 16 | XBLNR | ||||
| REF_DOC_YR | Fiscal Year of a Reference Document | LFBJA | NUMC | 4 | GJAHR | GJAHR | |||
| REF_DOC | Document No. of a Reference Document | LFBNR | CHAR | 10 | ALPHA | BELNR | |||
| REF_DOC_IT | Item of a Reference Document | LFPOS | NUMC | 4 | MBLPO | ||||
| MOVE_REAS | Reason for Movement | MB_GRBEW | NUMC | 4 | Assigned to domain | MB_GRBEW | |||
| ENTRY_DATE | Day On Which Accounting Document Was Entered | CPUDT | DATS | 8 | DATUM | ||||
| ENTRY_TIME | Time of Entry | CPUTM | TIMS | 6 | UZEIT | ||||
| IVVAL_LOC | Currency Amount in BAPI Interfaces | BBPCURR | DEC | 23(4) | BBPCURR | ||||
| IVVAL_FOR | Currency Amount in BAPI Interfaces | BBPCURR | DEC | 23(4) | BBPCURR | ||||
| MATERIAL | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| PLANT | Plant | BBPWERKS | CHAR | 4 | CHAR4 | WRK | |||
| CONF_SER | Sequential Number of Vendor Confirmation | ETENS | NUMC | 4 | NUM04 | ||||
| CONDITION | Number of the document condition | KNUMV | CHAR | 10 | KNUMV | ||||
| TAX_CODE | Tax on sales/purchases code | MWSKZ | CHAR | 2 | Assigned to domain | MWSKZ | |||
| DELIV_QTY | Quantity in Unit of Measure from Delivery Note | LSMNG | QUAN | 13(3) | MENG13 | ||||
| DELIV_UNIT | Unit of Measure From Delivery Note | LSMEH | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| PUR_MAT | Material Number | EMATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | |
| LOC_CURR | Local currency key | HSWAE | CUKY | 5 | Assigned to domain | WAERS | |||
| BATCH | Batch number | BBPCHARG | CHAR | 10 | CHAR10 | CHA | |||
| DOC_DATE | Document Date in Document | BLDAT | DATS | 8 | DATUM |
| Key field | Non-key field |
How do I retrieve data from SAP structure BBPEKBE using ABAP code?
As BBPEKBE 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 BBPEKBE as there is no data to select.How to access SAP table BBPEKBE
Within an ECC or HANA version of SAP you can also view further information about BBPEKBE 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