E1AFKOL SAP (Production order header (AFKO, AUFK)) IDoc segment structure details
Dictionary Type: IDoc segment structure
Description: Production order header (AFKO, AUFK)
Description: Production order header (AFKO, AUFK)
IDoc segment structure field list including key, data, relationships and ABAP select examples
E1AFKOL is a standard SAP Structure which is used to define the field attributes of IDoc segment E1AFKOL. The segment is used within the below IDoc to send Production order header (AFKO, AUFK) information via the IDoc send process
/SAPMP/LOIPRO01LOIPRO01
LOIPRO02
LOIPRO03
Below is the standard documentation available and a few details of the fields which make up this IDoc segment structure. To view further details checkout the IDoc links above or use relevant transactions such as WE30(IDoc development), WE31 (segment development)...Also check here for more IDoc related development help, or you can obviously also use standard dictionary object dev tcodes such as SE11, SE80 etc...
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP E1AFKOL idoc segment 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 |
| AUFNR | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
| APRIO | Priority of Vacancy Assignment | APRIO | CHAR | 4 | SUBTY | ||||
| APROZ | Character Field With Field Length 7 | CHAR07 | CHAR | 7 | TEXT7 | ||||
| AUART | Order Type | AUFART | CHAR | 4 | Assigned to domain | AUFART | AAT | ||
| AUFLD | Date of BOM Explosion/Routing Transfer | CO_AUFLD | DATS | 8 | DATUM | ||||
| AUTYP | Order category | AUFTYP | NUMC | 2 | AUFTYP | ||||
| BAUMNG | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| BMEINS | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| BMENGE | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| CY_SEQNR | Seq. number order | CY_SEQNR | NUMC | 14 | CY_SEQNR | ||||
| 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 | ||
| FHORI | Scheduling Margin Key for Floats | FHORI | CHAR | 3 | Assigned to domain | FHORI | |||
| FLG_MLTPS | Order with multiple items | CO_MLTPS | CHAR | 1 | KREUZ | ||||
| FREIZ | Release period (in days) | FREIZ | NUMC | 3 | NUM3 | ||||
| FTRMI | Actual release date | CO_FTRMI | DATS | 8 | DATUM | ||||
| FTRMS | Scheduled release date | CO_FTRMS | DATS | 8 | DATUM | ||||
| GAMNG | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| GASMG | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| GETRI | Confirmed Order Finish Date | CO_GETRI | DATS | 8 | DATUM | ||||
| GEUZI | Confirmed order finish (time) | CO_GEUZI | TIMS | 6 | UHRZT | ||||
| GLTRI | Actual finish date | CO_GLTRI | DATS | 8 | DATUM | ||||
| GLTRP | Basic finish date | CO_GLTRP | DATS | 8 | DATUM | ||||
| GLTRS | Scheduled finish | CO_GLTRS | DATS | 8 | DATUM | ||||
| GLUZP | Basic finish (time) | CO_GLUZP | TIMS | 6 | UHRZT | ||||
| GLUZS | Scheduled finish time | CO_GLUZS | TIMS | 6 | UHRZT | ||||
| GMEIN | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| GSTRI | Actual start date | CO_GSTRI | DATS | 8 | DATUM | ||||
| GSTRP | Basic start date | CO_GSTRP | DATS | 8 | DATUM | ||||
| GSTRS | Scheduled start | CO_GSTRS | DATS | 8 | DATUM | ||||
| GSUZP | Basic start time | CO_GSUZP | TIMS | 6 | UHRZT | ||||
| GSUZS | Scheduled Start (Time) | CO_GSUZS | TIMS | 6 | ATIME | ||||
| IASMG | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| IGMNG | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| LODIV | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| PLAUF | Date for routing transfer | CO_PLAUF | DATS | 8 | DATUM | ||||
| PLGRP | Responsible planner group/department | VAGRP | CHAR | 3 | Assigned to domain | VAGRP | H_T024A | ||
| PLNAL | Group Counter | PLNAL | CHAR | 2 | ALPHA | ALTNR | PAL | ||
| PLNME | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| PLNNR | Key for Task List Group | PLNNR | CHAR | 8 | ALPHA | PLNNR | PLN | PLKS | |
| PLNTY | Task List Type | PLNTY | CHAR | 1 | Assigned to domain | PLNTY | PTY | H_TCA01 | |
| PLSVB | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| PLSVN | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| PSPEL | Character field length 24 | CHAR24 | CHAR | 24 | CHAR24 | ||||
| REDKZ | Reduction indicator for scheduling | REDKZ | CHAR | 1 | REDKZ | ||||
| RGEKZ | Indicator: Backflush | RGEKZ | CHAR | 1 | XFELD | ||||
| RMNGA | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| SBMEH | 3-Byte field | CHAR3 | CHAR | 3 | CHAR3 | ||||
| SBMNG | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| SICHZ | Float after production (in days) | SICHZ | NUMC | 3 | NUM3 | ||||
| SLSBS | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| SLSVN | Text field length 14 | CHAR14 | CHAR | 14 | CHAR14 | ||||
| STLAL | Alternative BOM | STALT | CHAR | 2 | ALPHA | ALTNR | |||
| STLAN | BOM Usage | STLAN | CHAR | 1 | Assigned to domain | STLAN | CSV | ||
| STLNR | Bill of material | STNUM | CHAR | 8 | NUMCV | STNUM | STLNR | ||
| TERKZ | Scheduling type | TERMKZ | CHAR | 1 | Assigned to domain | TERART | |||
| VORGZ | Float before production (in days) | VORGZ | NUMC | 3 | NUM3 | ||||
| WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
| MATNR_EXTERNAL | 0 | ||||||||
| MATNR_VERSION | 0 | ||||||||
| MATNR_GUID | 0 | ||||||||
| PRUEFLOS | 0 | ||||||||
| LTEXT | 0 | ||||||||
| STLTY | 0 | ||||||||
| KDAUF | 0 | ||||||||
| KDPOS | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure E1AFKOL using ABAP code?
As E1AFKOL 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 E1AFKOL as there is no data to select.How to access SAP table E1AFKOL
Within an ECC or HANA version of SAP you can also view further information about E1AFKOL 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