IODISP SAP (Database structure for dispatching) Structure details
Description: Database structure for dispatching
Structure field list including key, data, relationships and ABAP select examples
IODISP 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 "Database structure for dispatching" 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_IODISP TYPE IODISP.
The IODISP table consists of various fields, each holding specific information or linking keys about Database structure for dispatching data available in SAP. These include AUFPL (Routing number of operations in the order), BDMNG (Requirement Quantity), ARBID (Object ID of the resource), ARBPL (Work center).. 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 IODISP 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 | |||
AUFPL | Routing number of operations in the order | CO_AUFPL | NUMC | 10 | AUFPL | ||||
BDMNG | Requirement Quantity | BDMNG | QUAN | 13(3) | MENG13 | ||||
ARBID | Object ID of the resource | CR_OBJID | NUMC | 8 | Assigned to domain | CR_OBJID | |||
ARBPL | Work center | ARBPL | CHAR | 8 | ARBPL | AGR | |||
APWRK | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
OLD_ARBID | Old operating resource obj.identific.(OIS:order dispatchng) | IO_OOBJID | NUMC | 8 | Assigned to domain | CR_OBJID | |||
OLD_ARBPL | Old work center (OIS: order dispatching) | IO_OARBPL | CHAR | 8 | ARBPL | ||||
OLD_APWRK | Old plant (OIS: order dispatching) | IO_OWERKS | CHAR | 4 | Assigned to domain | WERKS | |||
KALID | Factory Calendar | WFCID | CHAR | 2 | TFACD | WFCID | FCI | ||
AUFNR | Order Number | AUFNR | CHAR | 12 | AUFK | ALPHA | AUFNR | ANR | |
PLNUM | Planned order number | PLNUM | CHAR | 10 | Assigned to domain | ALPHA | PLNUM | PAF | |
PRODNET | Indicator: Order is part of collective order | CO_PRODNET | CHAR | 1 | KREUZ | ||||
LEAD_AUFNR | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
AUART | Order Type | AUFART | CHAR | 4 | Assigned to domain | AUFART | AAT | ||
AUTYP | Order category | AUFTYP | NUMC | 2 | AUFTYP | ||||
MATNR | Material Number | MATNR | CHAR | 18 | MARA | MATN1 | MATNR | MAT | S_MAT1 |
WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
RSNUM | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | Assigned to domain | RSNUM | RES | ||
KDAUF | Sales Order Number | KDAUF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
PSPEL | WBS Element | PS_POSNR | NUMC | 8 | Assigned to domain | ABPSP | PS_POSNR | ||
SOBKZ | Special Stock Indicator | SOBKZ | CHAR | 1 | Assigned to domain | SOBKZ | |||
GAMNG | Total order quantity | GAMNG | QUAN | 13(3) | MENG13 | ||||
GMEIN | Common unit of measure for all order items | CO_GMEIN | UNIT | 3 | T006 | CUNIT | MEINS | ||
GLTRP | Basic finish date | CO_GLTRP | DATS | 8 | DATUM | ||||
OBJNR | Object number | J_OBJNR | CHAR | 22 | ONR00 | J_OBJNR | ONR | ||
SFCPF | Production Scheduling Profile | CO_PRODPRF | CHAR | 6 | Assigned to domain | CO_PRODPRF | |||
DISPO | MRP controller for the order | CO_DISPO | CHAR | 3 | Assigned to domain | DISPO | DGR | ||
FEVOR | Production Supervisor | FEVOR | CHAR | 3 | Assigned to domain | FEVOR | CFV | ||
RETCODE | Subroutines for return code | SUBRC | NUMC | 2 | EK08R_RC | ||||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
XFEHL | Missing Part | XFEHL | CHAR | 1 | XFELD | ||||
VFMNG | Committed quantity for order acc. to ATP check components | CO_VFMNG | QUAN | 13(3) | MENG13 | ||||
GSBTR | Overall commitment date | CO_GSBTR | DATS | 8 | DATUM | ||||
BSFAK | Confirmation factor confirmed qty. for order quantity | CO_BSFAK | QUAN | 3 | RSDQUAN | ||||
PROZENT | Unit for the Rate (Percent) | QPROZENT | UNIT | 2 | QPROZENT | ||||
BSDIF | Difference betw. rqmts. date and order date in fact.cal.days | BSDIF | CHAR | 3 | CHAR3 | ||||
EINHEIT | Time unit | DZEITEINH | UNIT | 2 | LAUFZ | ||||
TBSTR | Partial commitment date | TBSTR | DATS | 8 | DATUM | ||||
TBSMG | Quantity partially committed | TBSMG | QUAN | 13(3) | MENG13 | ||||
TABIX | Field defined as in SY-TABIX | TABIX_D | INT4 | 10 | TABIX | ||||
KZAVC | Indicator for type of availability check | KZAVC | CHAR | 1 | KZAVC | ||||
MDPBV | Planned order: confirmation of availability | MDPBV | CHAR | 1 | MDPBV | ||||
STUFE | Order level | AUFST | NUMC | 2 | AUFST | ||||
ARSNR | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | Assigned to domain | RSNUM | RES | ||
ARSPS | Item Number of Reservation/Dependent Requirement | RSPOS | NUMC | 4 | RSPOS | RPO | |||
GASMG | Total scrap quantity in the order | GASMG | QUAN | 13(3) | MENG13 | ||||
PLWRK | Planning Plant | PLWRK | CHAR | 4 | Assigned to domain | WERKS | WRK | ||
STTXT | System Status | CO_STTXT | CHAR | 40 | CHAR40 | ||||
ASTEX | User status active | CO_ASTEX | CHAR | 1 | KREUZ | ||||
ASTTX | Field displaying user status | CO_ASTTX | CHAR | 40 | CHAR40 | ||||
KUNNR | Customer Numbers | KUNNR | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | C_KUNNR |
KDAUF_AUFK | Sales Order Number | KDAUF | CHAR | 10 | VBUK | ALPHA | VBELN | AUN | |
KDPOS_AUFK | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
CY_SEQNR | Seq. number order | CY_SEQNR | NUMC | 14 | CY_SEQNR | ||||
APRIO | Order priority | CO_APRIO | CHAR | 1 | CHAR1 | ||||
FTRMS | Scheduled release date | CO_FTRMS | DATS | 8 | DATUM | ||||
FTRMI | Actual release date | CO_FTRMI | DATS | 8 | DATUM | ||||
FTRMP | Planned release date | CO_FTRMP | DATS | 8 | DATUM | ||||
GSTRP | Basic start date | CO_GSTRP | DATS | 8 | DATUM | ||||
GLTRS | Scheduled finish | CO_GLTRS | DATS | 8 | DATUM | ||||
GSTRS | Scheduled start | CO_GSTRS | DATS | 8 | DATUM | ||||
GSTRI | Actual start date | CO_GSTRI | DATS | 8 | DATUM | ||||
GLTRI | Actual finish date | CO_GLTRI | DATS | 8 | DATUM | ||||
ARBTX | Work center description | KTXT40 | CHAR | 40 | TEXT40 | ||||
RELERR | Indicator: Release fields | IORELERR | CHAR | 1 | FLAG | ||||
FLG_DSP | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
FLG_REL | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
FLG_UPD | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
KZ_MARK | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
INDEX_NODE | Field defined as in SY-TABIX | TABIX_D | INT4 | 10 | TABIX | ||||
INDEX_INT | Field defined as in SY-TABIX | TABIX_D | INT4 | 10 | TABIX |
Key field | Non-key field |
How do I retrieve data from SAP structure IODISP using ABAP code?
As IODISP 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 IODISP as there is no data to select.How to access SAP table IODISP
Within an ECC or HANA version of SAP you can also view further information about IODISP 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