nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can anyone describe the disaggregation in Anaplan

Nirmal2255

Accepted answers

TristanS

@Nirmal2255 In most cases, I've heard disaggregation performed in demand planning models. Disaggregation in demand planning is the process of breaking down or decomposing high-level aggregate demand forecasts into more detailed and specific forecasts for individual products, regions, time periods, or customer segments. It involves the transformation of a consolidated or summarized demand forecast into more granular and actionable plans that can be used for production, inventory management, and other operational purposes.

The purpose of disaggregation is to create more accurate and relevant forecasts at a lower level of granularity, considering the unique characteristics and demand patterns of different subcategories within the overall demand.

For example, Coca cola's demand plan application could only be generating demand forecasts for it's soft drinks at a brand level / volume, e.g. 20,000 litres of coke for Monday, 30,000 litres of coke for Tuesday but manufacturing would require more detailed information such as specific volume (2 litre bottle, 250 ml can, 1 litre bottle) and variety (coke zero, coke classic, coke vanilla). So to bridge the gap between the detail in which demand plan model forecasts and detail in which manufacturing require to produce, the demand planning application would "disaggregate" breakdown the brand level/volume forecast in to more granular components.

So the 20,000 litres for coke forecast on Monday would be disaggregated down to

1,000 units of 2 litre coke zero
800 units of 2 litre coke classic
100 units of coke vanilla
2,000 units of 250 ml can of coke zero
3,000 units of 250 ml can of coke classic
etc …

How it is disaggregated down to these units can have different rules behind them such as historical ratios, etc

Nirmal2255

@TristanS Thanks a lot. It was very helpful.

All comments

Vinay VaradarajM

@Nirmal2255 Pls could you provide more details about the problem statement.

TristanS

So the 20,000 litres for coke forecast on Monday would be disaggregated down to

1,000 units of 2 litre coke zero
800 units of 2 litre coke classic
100 units of coke vanilla
2,000 units of 250 ml can of coke zero
3,000 units of 250 ml can of coke classic
etc …

How it is disaggregated down to these units can have different rules behind them such as historical ratios, etc

Nirmal2255

@TristanS Thanks a lot. It was very helpful.

Quick Links

Can you help?

Unanswered questions

Handling Month–Year vs Year–Month format issues in Anaplan imports?
In our current setup on a Global Engagement, most regions use a Month–Year format (e.g., Jan-26) for the time range in the forecast upload template. However, the US region follows a Year–Month format (e.g., 26-Jan) in their local Excel files. This mismatch creates a challenge: When US users download the template, it is…
An Update on Anaplan Audit Log Reporting: A No-Code Approach
A while back, I shared a pattern for extracting and reporting on Anaplan audit data using a Python project hosted on GitHub. I wrote that during my time on the Operational Excellence Group (OEG) at Anaplan. The Python solution still works, and plenty of teams are running it today. The problem it solves hasn't changed:…
Looking for Anaplan End-Users to take a short survey!
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…