EDX_INV_POSITION_DATA_STRUCT SAP (EDX: Inbound Invoice position data structure) Structure details
Description: EDX: Inbound Invoice position data structure
Related tables to EDX_INV_POSITION_DATA_STRUCT
Access table EDX_INV_POSITION_DATA_STRUCT
Structure field list including key, data, relationships and ABAP select examples
EDX_INV_POSITION_DATA_STRUCT 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 "EDX: Inbound Invoice position data structure" 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_EDX_INV_POSITION_DATA_STRUCT TYPE EDX_INV_POSITION_DATA_STRUCT.
The EDX_INV_POSITION_DATA_STRUCT table consists of various fields, each holding specific information or linking keys about EDX: Inbound Invoice position data structure data available in SAP. These include RBLGP (Document Item in Invoice Document), WRBTR (Amount in document currency), MENGE (Quantity), MEINS (Purchase Order Unit of Measure).. 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 EDX_INV_POSITION_DATA_STRUCT 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 |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
RBLGP | Document Item in Invoice Document | RBLGP | NUMC | 6 | NUMC6 | ||||
WRBTR | Amount in document currency | WRBTR | CURR | 13(2) | WERT7 | ||||
MENGE | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
MEINS | Purchase Order Unit of Measure | BSTME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
IDNLF | Material Number Used by Vendor | IDNLF | CHAR | 35 | IDNEX | ||||
TXZ01 | Short Text | TXZ01 | CHAR | 40 | TEXT40 | ||||
NETPR | Net price | NETPR | CURR | 11(2) | WERTV6 | ||||
MWSKZ | Tax on sales/purchases code | MWSKZ | CHAR | 2 | Assigned to domain | MWSKZ | |||
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 | ||
XBLNR | Number of External Delivery Note | LFSNR | CHAR | 16 | XBLNR | ||||
WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
KALSM | Procedure (Pricing, Output Control, Acct. Det., Costing,...) | KALSM_D | CHAR | 6 | Assigned to domain | KALSM | |||
SELKZ | General Flag | FLAG | CHAR | 1 | FLAG |
Key field | Non-key field |
How do I retrieve data from SAP structure EDX_INV_POSITION_DATA_STRUCT using ABAP code?
As EDX_INV_POSITION_DATA_STRUCT 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 EDX_INV_POSITION_DATA_STRUCT as there is no data to select.How to access SAP table EDX_INV_POSITION_DATA_STRUCT
Within an ECC or HANA version of SAP you can also view further information about EDX_INV_POSITION_DATA_STRUCT 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