J_1IBPOTAB SAP (BPO structure for ERS - CIN) Structure details
Description: BPO structure for ERS - CIN
Structure field list including key, data, relationships and ABAP select examples
J_1IBPOTAB 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 "BPO structure for ERS - CIN" 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_J_1IBPOTAB TYPE J_1IBPOTAB.
The J_1IBPOTAB table consists of various fields, each holding specific information or linking keys about BPO structure for ERS - CIN data available in SAP. These include EBELP (Item Number of Purchasing Document), BELNR (Accounting Document Number), GJAHR (Fiscal Year), BUZEI (Number of Line Item Within Accounting 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: Not classified
SAP J_1IBPOTAB 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 |
| 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 | ||
| BELNR | Accounting Document Number | BELNR_D | CHAR | 10 | ALPHA | BELNR | BLN | ||
| GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| BUZEI | Number of Line Item Within Accounting Document | BUZEI | NUMC | 3 | BUZEI | BUZ | |||
| BPMNG | Quantity in Purchase Order Price Unit | BPMNG | QUAN | 13(3) | MENG13 | ||||
| DMBTR | Amount in Local Currency | DMBTR | CURR | 13(2) | WERT7 | ||||
| LIFRE | Different Invoicing Party | LIFRE | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LRE | |
| MENGE | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
| MWSKZ | Tax on sales/purchases code | MWSKZ | CHAR | 2 | Assigned to domain | MWSKZ | |||
| PSTYP | Item Category in Purchasing Document | PSTYP | CHAR | 1 | Assigned to domain | PSTYP | |||
| TXJCD | Tax Jurisdiction | TXJCD | CHAR | 15 | Assigned to domain | TXJCD | TXJ | ||
| WEBRE | Indicator: GR-Based Invoice Verification | WEBRE | CHAR | 1 | XFELD | ||||
| WRBTR | Amount in document currency | WRBTR | CURR | 13(2) | WERT7 | ||||
| ZEKKN | Sequential Number of Account Assignment | DZEKKN | NUMC | 2 | NUM02 | ||||
| LFBNR | Document No. of a Reference Document | LFBNR | CHAR | 10 | ALPHA | BELNR |
| Key field | Non-key field |
How do I retrieve data from SAP structure J_1IBPOTAB using ABAP code?
As J_1IBPOTAB 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 J_1IBPOTAB as there is no data to select.How to access SAP table J_1IBPOTAB
Within an ECC or HANA version of SAP you can also view further information about J_1IBPOTAB 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