/MIVE/S_SALES_SOS_DETAIL SAP (MIV Apps: Sales Order Schedule Line detail structure) Structure details
Description: MIV Apps: Sales Order Schedule Line detail structure
Related tables to /MIVE/S_SALES_SOS_DETAIL
Access table /MIVE/S_SALES_SOS_DETAIL
Structure field list including key, data, relationships and ABAP select examples
/MIVE/S_SALES_SOS_DETAIL 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 "MIV Apps: Sales Order Schedule Line detail 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_/MIVE/S_SALES_SOS_DETAIL TYPE /MIVE/S_SALES_SOS_DETAIL.
The /MIVE/S_SALES_SOS_DETAIL table consists of various fields, each holding specific information or linking keys about MIV Apps: Sales Order Schedule Line detail structure data available in SAP. These include SO_NUMBER_KEY (MIV Apps: Sales Order number), ITEM_NUMBER_KEY (MIV Apps: Sales Order Item number), SCHED_NUMBER_KEY (MIV Apps: Sales Order Schedule Line number), SO_NUMBER (MIV Apps: Sales Order number).. 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 /MIVE/S_SALES_SOS_DETAIL 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 |
SO_NUMBER_KEY | MIV Apps: Sales Order number | /MIVE/SALES_SO_NUMBER | CHAR | 10 | ALPHA | /MIVE/SALES_SO_NUMBER | |||
ITEM_NUMBER_KEY | MIV Apps: Sales Order Item number | /MIVE/SALES_ITEM_NUMBER | CHAR | 6 | ALPHA | /MIVE/SALES_ITEM_NUMBER | |||
SCHED_NUMBER_KEY | MIV Apps: Sales Order Schedule Line number | /MIVE/SALES_SCHED_NUMBER | CHAR | 4 | ALPHA | /MIVE/SALES_SCHED_NUMBER | |||
SO_NUMBER | MIV Apps: Sales Order number | /MIVE/SALES_SO_NUMBER | CHAR | 10 | ALPHA | /MIVE/SALES_SO_NUMBER | |||
ITEM_NUMBER | MIV Apps: Sales Order Item number | /MIVE/SALES_ITEM_NUMBER | CHAR | 6 | ALPHA | /MIVE/SALES_ITEM_NUMBER | |||
SCHED_NUMBER | MIV Apps: Sales Order Schedule Line number | /MIVE/SALES_SCHED_NUMBER | CHAR | 4 | ALPHA | /MIVE/SALES_SCHED_NUMBER | |||
SCHED_DATE | MIV Apps: Sales Order Schedule Line date | /MIVE/SALES_SCHED_DATE | DATS | 8 | DATUM | ||||
SCHED_DATE_FORMATTED | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
REQ_QUANTITY | MIV Apps: Sales Order Schedule line quantity | /MIVE/SALES_SCHED_QUANTITY | QUAN | 13(3) | MENG13 | ||||
CNF_QUANTITY | MIV Apps: Sales Order Schedule line quantity | /MIVE/SALES_SCHED_QUANTITY | QUAN | 13(3) | MENG13 | ||||
QUANTITY_UOM | MIV Apps: Sales generic unit of measure | /MIVE/SALES_UOM | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
QUANTITY_UOM_TEXT | MIV Apps: Sales generic unit of measure text | /MIVE/SALES_UOM_TEXT | CHAR | 30 | TEXT30 | ||||
REQ_QUANTITY_FORMATTED | Char 80 | CHAR80 | CHAR | 80 | CHAR80 | ||||
CNF_QUANTITY_FORMATTED | Char 80 | CHAR80 | CHAR | 80 | CHAR80 | ||||
DEL_QUANTITY | MIV Apps: Sales Order Schedule line quantity | /MIVE/SALES_SCHED_QUANTITY | QUAN | 13(3) | MENG13 | ||||
DEL_QUANTITY_FORMATTED | Char 80 | CHAR80 | CHAR | 80 | CHAR80 | ||||
MB_DATE | MIV Apps: Sales Order Schedule Line date | /MIVE/SALES_SCHED_DATE | DATS | 8 | DATUM | ||||
MB_DATE_FORMATTED | Character Field Length = 10 | CHAR10 | CHAR | 10 | CHAR10 | ||||
ARRIVAL_TIME | MIV Apps: Sales Order Schedule Line time | /MIVE/SALES_SCHED_TIME | TIMS | 6 | UZEIT | ||||
ARRIVAL_TIME_FORMATTED | Char 15 | CHAR15 | CHAR | 15 | CHAR15 | ||||
DELIVERY_BLOCK | MIV Apps: Delivery Block | /MIVE/SALES_DELIVERY_BLOCK | CHAR | 2 | |||||
DELIVERY_BLOCK_TEXT | MIV Apps: Delivery Block Text | /MIVE/SALES_DELIVERY_BLK_TEXT | CHAR | 20 | |||||
SHIPPING_POINT | MIV Apps: Sales Order Schedule Line shipping point | /MIVE/SALES_SCHED_SHPOINT | CHAR | 4 | /MIVE/SALES_SCHED_SHPOINT | ||||
SHIPPING_POINT_TEXT | MIV Apps: Sales Order Schedule Line shipping point descr. | /MIVE/SALES_SCHED_SHPOINT_TEXT | CHAR | 30 | TEXT30 | ||||
PLANT | MIV Apps: Sales Order plant | /MIVE/SALES_ORDER_PLANT | CHAR | 4 | Assigned to domain | WERKS | |||
PLANT_TEXT | MIV Apps: Sales Order plant text | /MIVE/SALES_ORDER_PLANT_TEXT | CHAR | 30 | TEXT30 | ||||
MOVEMENT_TYPE | MIV Apps: Movement Type | /MIVE/SALES_MOVEMENT_TYPE | CHAR | 3 | |||||
MOVEMENT_TYPE_TEXT | MIV Apps: Movement Type text | /MIVE/SALES_MOVEMENT_TYPE_TEXT | CHAR | 20 | |||||
STORAGE_LOC | MIV Apps: Storage location | /MIVE/SALES_STORAGE_LOC | CHAR | 4 | |||||
STORAGE_LOC_TEXT | MIV Apps: Storage location description | /MIVE/SALES_STORAGE_LOC_TEXT | CHAR | 16 | TEXT16 | ||||
MATERIAL | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
Key field | Non-key field |
How do I retrieve data from SAP structure /MIVE/S_SALES_SOS_DETAIL using ABAP code?
As /MIVE/S_SALES_SOS_DETAIL 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 /MIVE/S_SALES_SOS_DETAIL as there is no data to select.How to access SAP table /MIVE/S_SALES_SOS_DETAIL
Within an ECC or HANA version of SAP you can also view further information about /MIVE/S_SALES_SOS_DETAIL 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