Hierarchy
⤷ LO-MD (Application Component) Logistics Basic Data
⤷ WRF_CM_MD (Package) Category Management - Master Data
Basic Data
Data Element | WRF_SIMU_COPY_GENERAL_CHECKS |
Short Description | General Checks: Simulate and Copy |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
A list of the checks that are run when the simulation is executed:
- Assignment of Materials to Non-End Nodes in the Source Hierarchy
Checks if all materials are attached to end nodes (you can deactivate this check in Customizing for value-only materials). Materials to be copied to an activated target hierarchy must be assigned to the end nodes (higher- or lower-level nodes) of the source hierarchy that is to be copied.
- Multiple Material Assignment in the Target Hierarchy
This indicator displays all date records of a material that are assigned under a category in the target hierarchy. The indicator is always displayed when a material to be copied from a source hierarchy to a target hierarchy is already assigned under the target category. When this is the case, all existing material assignments of the target hierarchy are displayed.
- Missing Node Attributes in the Target Hierarchy
Checks for the mandatory field attribute. When you copy changes to an activated target hierarchy, you can check using a BAdI implementation if attribute assignment is mandatory for the node assignments that are to be copied.
- Uniqueness of Node ID in the Target Hierarchy
Checks if the node IDs of the nodes to be copied are unique in the target hierarchy.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20050615 |
SAP Release Created in | 600 |