OPERATION_DETAILS SAP (Details of Operation) Structure details
Description: Details of Operation
Related tables to OPERATION_DETAILS
Access table OPERATION_DETAILS
Structure field list including key, data, relationships and ABAP select examples
OPERATION_DETAILS 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 "Details of Operation" 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_OPERATION_DETAILS TYPE OPERATION_DETAILS.
The OPERATION_DETAILS table consists of various fields, each holding specific information or linking keys about Details of Operation data available in SAP. These include UVORN (Suboperation), LTXA1 (Operation short text), VSTTXT (System Status), STEUS (Control key).. 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 OPERATION_DETAILS 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 |
VORNR | Operation/Activity Number | VORNR | CHAR | 4 | NUMCV | VORNR | VGN | ||
UVORN | Suboperation | UVORN | CHAR | 4 | NUMCV | VORNR | |||
LTXA1 | Operation short text | LTXA1 | CHAR | 40 | TEXT40 | ||||
VSTTXT | System Status | CO_STTXT | CHAR | 40 | CHAR40 | ||||
STEUS | Control key | STEUS | CHAR | 4 | Assigned to domain | STEUS | |||
KTSCH | Standard text key | KTSCH | CHAR | 7 | Assigned to domain | KTSCH | |||
TPLNR | Functional Location | TPLNR | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFL | IFLM |
EQUNR | Equipment Number | EQUNR | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | EQN | EQUI |
MLSTN | Usage | MILESTONE | CHAR | 5 | Assigned to domain | MILESTONE | |||
RUECK | Completion confirmation number for the operation | CO_RUECK | NUMC | 10 | CO_RUECK | RCK | |||
ARBPL | Work center | ARBPL | CHAR | 8 | ARBPL | AGR | |||
WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
KTEXT | Work center description | KTXT40 | CHAR | 40 | TEXT40 | ||||
MGVRG | Operation Quantity | MGVRG | QUAN | 13(3) | MENG13 | ||||
MEINH | Unit of Measure for Activity/Operation | VORME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
LARNT | Activity Type | LSTAR | CHAR | 6 | Assigned to domain | LSTAR | LAR | LART_EMPTY | |
PREIS | Price | PREIS | CURR | 11(2) | WERT11 | ||||
WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
PEINH | Price Unit | PEINH | DEC | 5 | PACK3 | ||||
FSAVD | Earliest scheduled start: Execution (date) | FSAVD | DATS | 8 | DATUM | ||||
FSAVZ | Earliest scheduled start: Execution (time) | FSAVZ | TIMS | 6 | ATIME | ||||
SSEDD | Latest scheduled finish: Execution (date) | SSEDD | DATS | 8 | DATUM | ||||
SSEDZ | Latest scheduled finish: Execution (time) | SSEDZ | TIMS | 6 | ATIME | ||||
ISMNW | Actual work | CO_ISMNW | QUAN | 13(3) | MENG13 | ||||
ARBEH | Unit for work | ARBEITE | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
PUFGP | Total float (from forecast) | PPUFF_GESM | DEC | 3 | PUFFER | ||||
BANFN | Purchase requisition number | CO_BANFN | CHAR | 10 | ALPHA | BANFN | |||
ARBEI | Work involved in the activity | ARBEIT | QUAN | 7(1) | ARBEIT | ||||
DAUNO | Normal duration of the activity | DAUNOR | QUAN | 5(1) | DAUER_4_1 | ||||
DAUNE | Normal duration/unit | DAUNORE | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
ANZZL | Number of capacities required | ANZKAP | INT1 | 3 | INT1 |
Key field | Non-key field |
How do I retrieve data from SAP structure OPERATION_DETAILS using ABAP code?
As OPERATION_DETAILS 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 OPERATION_DETAILS as there is no data to select.How to access SAP table OPERATION_DETAILS
Within an ECC or HANA version of SAP you can also view further information about OPERATION_DETAILS 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