OIA03_UPD SAP (Exchange item data update structure - purchase) Structure details
Description: Exchange item data update structure - purchase
Structure field list including key, data, relationships and ABAP select examples
OIA03_UPD 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 "Exchange item data update structure - purchase" 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_OIA03_UPD TYPE OIA03_UPD.
The OIA03_UPD table consists of various fields, each holding specific information or linking keys about Exchange item data update structure - purchase data available in SAP. These include MANDT (Client), EXGNUM (Exchange agreement number), EBELN (Purchasing Document Number), BSTYP (Purchasing Document Category).. 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)
SAP OIA03_UPD 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 | T000 | MANDT | |||
| EXGNUM | Exchange agreement number | OIA_EXGNUM | CHAR | 10 | OIA01 | ALPHA | OIA_EXGNUM | OI1 | OIAE |
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | EKKO | ALPHA | EBELN | BES | MEKK_C |
| BSTYP | Purchasing Document Category | BSTYP | CHAR | 1 | BSTYP | ||||
| BSART | Order Type (Purchasing) | BSART | CHAR | 4 | T161 | BSART | BSA | ||
| REORG | Reorganization date | OIA_REORG | DATS | 8 | DATUM | ||||
| LVORM | Deletion Indicator | LVORM | CHAR | 1 | XFELD | ||||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
| TEXT | Text (80 Characters) | TEXT80 | CHAR | 80 | TEXT80UEB | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| ERTIM | Time of creation | OI0_ERTIM | TIMS | 6 | UZEIT | ||||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| AETIM | Time of day the record was changed | OI0_AETIM | TIMS | 6 | UZEIT | ||||
| AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| UPDKZ | Update indicator | OIA_UPDATE | CHAR | 1 | OIA_ANDOR |
| Key field | Non-key field |
How do I retrieve data from SAP structure OIA03_UPD using ABAP code?
As OIA03_UPD 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 OIA03_UPD as there is no data to select.How to access SAP table OIA03_UPD
Within an ECC or HANA version of SAP you can also view further information about OIA03_UPD 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