OI0BW_OIAQS_S_NEW SAP (Transfer structure: EXG quantity schedule (delta-enabled)) Structure details
Description: Transfer structure: EXG quantity schedule (delta-enabled)
Related tables to OI0BW_OIAQS_S_NEW
Access table OI0BW_OIAQS_S_NEW
Structure field list including key, data, relationships and ABAP select examples
OI0BW_OIAQS_S_NEW 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: EXG quantity schedule (delta-enabled)" 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_OI0BW_OIAQS_S_NEW TYPE OI0BW_OIAQS_S_NEW.
The OI0BW_OIAQS_S_NEW table consists of various fields, each holding specific information or linking keys about Transfer structure: EXG quantity schedule (delta-enabled) data available in SAP. These include EXGNUM (Exchange agreement number), EXGPTR (Exchange partner (vendor number)), VBELN (Sales and Distribution Document Number), POSNR (Item number of the SD 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: Can be enhanced (character-type or numeric)
SAP OI0BW_OIAQS_S_NEW 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 |
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| EXGNUM | Exchange agreement number | OIA_EXGNUM | CHAR | 10 | Assigned to domain | ALPHA | OIA_EXGNUM | OI1 | OIAE |
| EXGPTR | Exchange partner (vendor number) | OIA_EXGPTR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KREDO |
| VBELN | Sales and Distribution Document Number | VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
| POSNR | Item number of the SD document | POSNR | NUMC | 6 | Assigned to domain | POSNR | |||
| 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 | ||
| SUBITM | Sub-item number | OIA_SUBITM | NUMC | 4 | OIA_SUBITM | ||||
| SEQENT | Sequential segment number | OIA_SEQENT | NUMC | 4 | OIA_SEQENT | ||||
| CIND | Contract / call-off indicator | OIA_CIND | CHAR | 1 | OIA_CIND | ||||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| SCHDDT | Schedule date | OIA_SCHDDT | DATS | 8 | DATUM | ||||
| SMENGE | Called-off/delivered/goods receipt quantity | OIA_SMENGE | QUAN | 13(3) | OIA_MENGE | ||||
| INTQTY | Quantity scheduled to be exchanged | OIA_INTQTY | QUAN | 13(3) | MENGE | ||||
| RECQTY | Quantity intended against an exchange | OIA_RECQTY | QUAN | 13(3) | MENGE | ||||
| MEINS | Quantity schedule-related UoM | OIA_MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | H_OI0_BUS | |
| ENTLU | Breakdown ind. for scheduling on contract/call-off level | OIA_ENTLU | CHAR | 1 | Assigned to domain | OIA_ENTLU | |||
| SPLIT | How to split quantity in quantity schedule | OIA_SPLIT | CHAR | 1 | OIA_SPLIT | ||||
| MOD | Mode of transport | OIA_MOD | CHAR | 2 | OIA_MOD | ||||
| OIPRIOR | Priority of an exchange agreement for load balancing | OIA_PRIOR | NUMC | 3 | OIA_PRIOR | ||||
| UPDMOD | APO-TSW:BW Delta Process record mode | OIJ_EL_BWUPDMOD | CHAR | 1 | OIJ_EL_BWUPDMOD |
| Key field | Non-key field |
How do I retrieve data from SAP structure OI0BW_OIAQS_S_NEW using ABAP code?
As OI0BW_OIAQS_S_NEW 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 OI0BW_OIAQS_S_NEW as there is no data to select.How to access SAP table OI0BW_OIAQS_S_NEW
Within an ECC or HANA version of SAP you can also view further information about OI0BW_OIAQS_S_NEW 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