SAP ABAP Data Element MC_VITEM (Release version for production order item = 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
SAP_APPL (Software Component) Logistics and Accounting⤷
PP-IS (Application Component) Information System⤷
MCF (Package) R/3 application development: Shop Floor Information System
Basic Data
| Data Element | MC_VITEM |
| Short Description | Release version for production order item = 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 | Item |
| Medium | 15 | Item |
| Long | 20 | Rel.version, item |
| Heading | 4 | Item |
Documentation
Definition
You can define release versions for production orders on the header, item or transaction levels.
The release version is the version at the time of the release.
If production orders change quite often during your work, the target and actual values will align more and more so that the target/actual deviation will no longer be correctly calculated. You can counteract this problem by using release versions.
If you defined a release version on the item level, the following key figures will be updated from the communications structures:
- start date of the planned order
- delivery date of the planned order
- fixed production scrap quantity
- total planned order quantity
- item quantity order
- item scrap quantity
History
| Last changed by/on | SAP | 19950401 |
| SAP Release Created in |
