Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-MAP (Application Component) Merchandise and Assortment Planning⤷
WIS_PLAN (Package) Retail: Planning
Basic Data
| Data Element | WISP_THVLL |
| Short Description | Planning Hierarchy Version: Target Data |
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 | 10 | TargetData |
| Medium | 19 | Target Data Version |
| Long | 30 | Target Data Hierarchy Version |
| Heading | 30 | Target Data Hierarchy Version |
Documentation
Definition
If different planning hierarchy versions are assigned to the plan versions of the source and target planning steps, you need to determine which planning hierarchy version will be used for disaggregation.
If the indicator is set, the entries (for example, proportional factors) of the hierarchy tables of the planning hierarchy version, which is assigned to the plan version of the target planning step are used. If the indicator is not set, the hierarchy version of the plan version of the source planning step is used.
Note:
SAP recommends that you use the planning hierarchy of the target planning step as defining hierarchy (this is the default setting). This is because in manual planning, the planning data disaggregated by planning step linking in the target planning step is generally compared with the planning data from the target planning hierarchy.
History
| Last changed by/on | SAP | 20020520 |
| SAP Release Created in | 470 |
