Hierarchy
ECC-DIMP (Software Component) DIMP⤷
LO-MD-MM (Application Component) Material Master⤷
MGV_MATNR (Package) Material number conversion (long mat. no.)
Basic Data
| Data Element | VERS_CREATE_DEF |
| Short Description | Logistic Switch Settings |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | VERS_CREATE_DEF | |
| 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 | Def.Log.S. |
| Medium | 20 | Default Log. Switch |
| Long | 29 | Default Values Log. Switch |
| Heading | 29 | Default Values Log. Switch |
Documentation
Definition
Determines for a particular plant, whether the logistics are linked to the header material, the material versions, or a combination of the two.
The following settings are possible:
- H = Logistics linked to header material
Specifies for the entire plant, that the logistics only apply to header materials. This means that users are unable to create data at plant level for material versions.
The switch at header material level has no purpose.
- L = Logistics linked to header material or versions
Within the plant, the user can decide for each individual header material, whether material versions data can be created at for this plant level or not.
- V = Logistics linked to versions
Plant data is automatically created for the entire plant for each material version. The switch at header material level has no purpose.
CAUTION: Once the logistic switch V = Logistics linked to versions is set, this setting cannot be reversed.
Effects of the maintenance switch in transaction TCLSVERS
The maintenance switch is set within the Customizing transaction TCLSVERS for each plant. This setting is evaluated during transfer of plant data, when material masters are created or changed, and also when data is transferred using ALE.
If the setting L is made for the plant in the transaction TCLSVERS, you can determine for each header material individually, whether plant data is permitted for the material versions or not.
Possible settings for the maintenance switch in the header material:
- " " |@3P@ (inactive) = Plant data is not permitted for material versions.
- "X" |@0R@ (active) = Plant data is permitted for material versions.
Creation of a material version
The creation of plant data for a material version is not permitted by the system, when the maintenance switch in the header material is set to |@3P@. If plant data is not scheduled for the header material, the create switch will be transferred from table TCLSVERS. If no entry is available there for that particular plant, an error message will appear.
If you only wish to create basic data for a version, ensure using the select views, that only the corresponding register are selected.
Creation of a header material
During the creation of a header material, the maintenance switch is visible, assuming that the header material possesses plant data. If a maintenance switch is available in the header material, its value is displayed by the system in the top group box Material.
The character |@3P@ displays the maintenance switch setting " " (no plant data permitted in versions). This status can be switched over for each header material, on the assumption that the setting from the transaction TCLSVERS for that particular plant permits this.
The character |@0R@ displays the maintenance switch setting "X" (plant data permitted in versions). This status cannot be reset for a header material.
The passing-on and distribution of the data
During changes to header materials or versions, changes in all versions are dragged from the system. The set version type for each header material / version is important at this point.
Data is also however distributed amongst the plants. Data is maintained in several plants for a header material, for example. Should changes be made to the plant data of a header material or a version, then these changes are also made to all related header materials or versions.
The maintenance switch is evaluated here in such a way, that the distribution is only carried out, if this is permitted by that particular header materials maintenance switch |@0R@.
It should be ensured as the data is distributed amongst the plants, that when a new version for a plant is created, that this version is also created in all other plants, providing that this is permitted by the maintenance switch for that particular material in that particular work.
History
| Last changed by/on | SAP | 20050301 |
| SAP Release Created in | 46C |
