SAP ABAP Data Element MC_VOPER (Release version for production order operation = active)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ PP-IS (Application Component) Information System
⤷ MCF (Package) R/3 application development: Shop Floor Information System
⤷ PP-IS (Application Component) Information System
⤷ MCF (Package) R/3 application development: Shop Floor Information System
Basic Data
Data Element | MC_VOPER |
Short Description | Release version for production order operation = active |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1 | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Operation |
Medium | 15 | Operation |
Long | 20 | Rel. version, oper. |
Heading | 5 | Oper. |
Documentation
Definition
You can define release versions for production orders on header, item or transaction levels.
The release version is the version at the time of the release.
If production orders are changed quite often during your work, the target and actual values will align more and more so that the target/ actual deviation can no longer be correctly calculated. You can counteract this problem by using the release versions.
If you have defined a release version on the transaction level, the following key figures will be updated from the communications structures:
- transaction quantity
- scrap quantity transaction
- earliest scheduled start
- latest scheduled start
- earliest scheduled finish
- latest scheduled finish
History
Last changed by/on | SAP | 19950401 |
SAP Release Created in |