SAP ABAP Data Element WISP_DISAGG (Disaggregation for Planning Hierarchy)

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_DISAGG
Short Description	Disaggregation for Planning Hierarchy

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	X
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	Disag.type
Medium	15	Disaggreg. type
Long	20	Disaggregation type
Heading	1	C

Documentation

Definition

Key figure that defines that the planning data is to be disaggregated at posting according to the proportions from the planning hierarchy and not according to current proportions.

Use

Generally, planning data is always saved at the highest planning level in a planning step. Therefore, if you have maintained planning data at a higher planning level, the planning data is distributed to all the concerned characteristic features below this planning level when you save the data.

To do this, you can use proportional factors that have been maintained in the planning hierarchy. If you have already maintained planning data at a higher level, you can use the current proportions that result from the planning data in disaggregation.

Notes

• You are recommended to use the quotas from the planning hierarchy in a top-down procedure and to use current quotas in a bottom-up procedure.
• If no planning data is available at a detailed level, disaggregation is always executed in accordance with the planning hierarchy.

History

Last changed by/on	SAP	19990301
SAP Release Created in