E2BIVIT SAP (BBP Incoming Invoice Item) Structure details
Description: BBP Incoming Invoice Item
Structure field list including key, data, relationships and ABAP select examples
E2BIVIT 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 "BBP Incoming Invoice Item" 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_E2BIVIT TYPE E2BIVIT.
The E2BIVIT table consists of various fields, each holding specific information or linking keys about BBP Incoming Invoice Item data available in SAP. These include PLANT (Plant), AMOUNT (Amount in document currency), QUANTITY (Quantity), UNIT (Order unit (purchasing)).. 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 E2BIVIT 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 |
MATERIAL | Material | 0 | |||||||
PLANT | Plant | 0 | |||||||
AMOUNT | Amount in document currency | 0 | |||||||
QUANTITY | Quantity | 0 | |||||||
UNIT | Order unit (purchasing) | 0 | |||||||
TAX_CODE | Tax code | 0 | |||||||
TEXT | Line item text | 0 | |||||||
GL_ACCOUNT | G/L account | 0 | |||||||
PO_NUMBER | Purchasing document number | 0 | |||||||
PO_ITEM | Item number of purchasing document | 0 | |||||||
COMPANY | Company code | 0 | |||||||
DISTR_PERC | Percentace of Accounting Distibution | 0 | |||||||
ACC_CAT | 0 | ||||||||
BUS_AREA | Business area | 0 | |||||||
COST_CTR | Cost Center | 0 | |||||||
SD_DOC | SD document number | 0 | |||||||
SDOC_ITEM | Sales document item | 0 | |||||||
SCHED_LINE | Schedule line | 0 | |||||||
ASSET_NO | Main asset number | 0 | |||||||
SUB_NUMBER | Asset sub-number | 0 | |||||||
ORDER_NO | Order Number | 0 | |||||||
CO_AREA | Controlling area | 0 | |||||||
PROF_SEGM | Profitability segment number (CO-PA) | 0 | |||||||
PROFIT_CTR | Profit center | 0 | |||||||
WBS_ELEM_E | Work breakdown structure element (WBS element) | 0 | |||||||
NETWORK | Network number for account assignment | 0 | |||||||
ACTIVITY | Operation number | 0 | |||||||
ROUTING_NO | Task list no. for operations in order | 0 | |||||||
RL_ESK_KEY | Internal key for real estate object | 0 | |||||||
COUNTER | Internal counter | 0 | |||||||
REC_IND | Recovery indicator | 0 | |||||||
PART_ACCT | Partner customer number | 0 | |||||||
CMMT_ITEM | Commitment item | 0 | |||||||
FUNDS_CTR | Funds center | 0 | |||||||
FUND | Fund | 0 | |||||||
FUNC_AREA | Functional area | 0 | |||||||
REF_DATE | Reference date for account settlement | 0 | |||||||
COST_OBJ | Cost object | 0 | |||||||
REF_DOC | Document number of a reference document | 0 | |||||||
REF_DOC_YR | Fiscal year of current period | 0 | |||||||
REF_DOC_IT | Item of a reference document | 0 | |||||||
SERIAL_NO | Serial number of PO account assignment | 0 | |||||||
DCIND | Debit/credit indicator | 0 | |||||||
ITEM_NUM | Item number | 0 | |||||||
FUNC_AREAL | 0 | ||||||||
GRANT_NBR | 0 | ||||||||
CMMT_ITEML | 0 | ||||||||
PACKNO | Package number | 0 | |||||||
INTROW | Internal line number for limits | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure E2BIVIT using ABAP code?
As E2BIVIT 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 E2BIVIT as there is no data to select.How to access SAP table E2BIVIT
Within an ECC or HANA version of SAP you can also view further information about E2BIVIT 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