MCAFKOB SAP (Order header data PP orders) Structure details
Dictionary Type: Structure
Description: Order header data PP orders
Description: Order header data PP orders
Structure field list including key, data, relationships and ABAP select examples
MCAFKOB 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 "Order header data PP orders" 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_MCAFKOB TYPE MCAFKOB.
The MCAFKOB table consists of various fields, each holding specific information or linking keys about Order header data PP orders data available in SAP. These include AUFNR (Order Number), AUFPL (Routing number of operations in the order), AUART (Order Type), AUTYP (Order 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 or numeric)
SAP MCAFKOB 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 |
| SUPKZ | Statistics update indicator (post in/post out) | SUPKZ | CHAR | 1 | SUPKZ | ||||
| AUFNR | Order Number | AUFNR | CHAR | 12 | AUFK | ALPHA | AUFNR | ANR | |
| AUFPL | Routing number of operations in the order | CO_AUFPL | NUMC | 10 | AUFPL | ||||
| AUART | Order Type | AUFART | CHAR | 4 | T003O | AUFART | AAT | ||
| AUTYP | Order category | AUFTYP | NUMC | 2 | AUFTYP | ||||
| ERDAT | Created on | AUFERFDAT | DATS | 8 | DATUM | ||||
| AEDAT | Change date for Order Master | AUFAEDAT | DATS | 8 | DATUM | ||||
| OBJNR | Object number | J_OBJNR | CHAR | 22 | ONR00 | J_OBJNR | ONR | ||
| BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| WERKS | Plant | WERKS_D | CHAR | 4 | T001W | WERKS | WRK | H_T001W_C | |
| PLGRP | Responsible planner group/department | VAGRP | CHAR | 3 | T024A | VAGRP | H_T024A | ||
| DISPO | MRP controller for the order | CO_DISPO | CHAR | 3 | T024D | DISPO | DGR | ||
| FEVOR | Production Supervisor | FEVOR | CHAR | 3 | T024F | FEVOR | CFV | ||
| GLTRP | Basic finish date | CO_GLTRP | DATS | 8 | DATUM | ||||
| GSTRP | Basic start date | CO_GSTRP | DATS | 8 | DATUM | ||||
| FTRMS | Scheduled release date | CO_FTRMS | 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 | ||||
| GETRI | Confirmed Order Finish Date | CO_GETRI | DATS | 8 | DATUM | ||||
| GLTRI | Actual finish date | CO_GLTRI | DATS | 8 | DATUM | ||||
| FTRMI | Actual release date | CO_FTRMI | DATS | 8 | DATUM | ||||
| FTRMP | Planned release date | CO_FTRMP | DATS | 8 | DATUM | ||||
| GASMG | Total Scrap Quantity in the Order | MC_GASMG | QUAN | 15(3) | MENGV15 | ||||
| GAMNG | Total order quantity | MC_GAMNG | QUAN | 15(3) | MENGV15 | ||||
| GMEIN | Base Unit of Measure | MEINS | UNIT | 3 | T006 | CUNIT | MEINS | ||
| VERID | Production Version | VERID | CHAR | 4 | Assigned to domain | VERID | VER | ||
| MDV01 | Production line | MDV01 | CHAR | 8 | T437P | MDVXX | |||
| MDV02 | Planning identification 2 | MDV02 | CHAR | 8 | T437P | MDVXX | |||
| KUNUM | Customer Number | KUNUM | CHAR | 10 | KNA1 | ALPHA | KUNNR | KUN | |
| AMEIN | Unit of measure for in-house production | CO_AUFME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| VDATU | Date of update for statistics updating | MC_VDATUM | DATS | 8 | DATUM | ||||
| TERKZ | Scheduling type | TERMKZ | CHAR | 1 | Assigned to domain | TERART | |||
| FA_FREI | Order has status RELEASED | MC_FA_FREI | CHAR | 1 | X | ||||
| FA_GLFT | Order has status DELIVERED | MC_FA_GLFT | CHAR | 1 | X | ||||
| FA_RUECK | Order has status CONFIRMED | MC_FA_RUECK | CHAR | 1 | X | ||||
| FA_TGLI | Order has Status PDLV | MC_FA_TGLI | CHAR | 1 | X | ||||
| FA_TRUEC | Order has status PARTIALLY CONFIRMED | MC_FA_TRUEC | CHAR | 1 | X | ||||
| GLUZS | Scheduled finish time | CO_GLUZS | TIMS | 6 | UHRZT | ||||
| GSUZS | Scheduled Start (Time) | CO_GSUZS | TIMS | 6 | ATIME | ||||
| GSUZI | Actual start time | CO_GSUZI | TIMS | 6 | UHRZT | ||||
| GEUZI | Confirmed order finish (time) | CO_GEUZI | TIMS | 6 | UHRZT | ||||
| PLNME | Task list unit of measure | PLNME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| LEAD_AUFNR | Leading order in current processing | CO_LAUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ||
| MAUFNR | Number of superior order | MAUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | UAF | |
| A | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY | ||||
| DUMMY | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY |
| Key field | Non-key field |
How do I retrieve data from SAP structure MCAFKOB using ABAP code?
As MCAFKOB 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 MCAFKOB as there is no data to select.How to access SAP table MCAFKOB
Within an ECC or HANA version of SAP you can also view further information about MCAFKOB 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