Aggregation Level & Selection ID in Demand Planing Background job

[Former Member]

Folks

Whle creating a Demand Planning job in the background, we need to make few selection such as

1. Choosing a Selection ID(One, Several & Select All) and

2. Choosing an Aggregation level.

My question is : Doesn't the selection ID already have the aggregation level defined with in as selection ID is basically something defined or shown as Product by Location and then by Sales Org etc. Isn't this the same as the aggregation level ???

Why do we need to have Selection Id as well as Aggregation level in Background job ?

In the interactive planning do we need the aggregation Level ? If so where do we specify the same ?

TIA

[Former Member]

The aggregation level can make a big difference to the forecast results. If you run the forecast on a high level (for example, at division level), the system aggregates the historical data (for example, the historical data of all products in a division) before it carries out the forecast. However, if you run the forecast on a low level (for example, for just one product), the system creates the forecast based on the historical data at this level, and then aggregates the forecast results in the planning screen at runtime.

The default level is the most detailed level.Here values will be disaggregated to the lowest detailed level and forecast will be executed in that level for each CVC.

say

PRD LOC PRD_GRP

A A1 PG1

B A1 PG1

C A1 PG1

A B1 PG1

B B1 PG1

C B1 PG1

here forecast wil be carried out for 6 CVCs

However, in real time, as you have many CVCs, we dont follow this.

Say we specify the aggregation level as PRD_GRP and LOC.. Then system aggregates values at product group and location level..executes forecast and then disaggregates.

in this case forecst will be carried out for

PRD LOC PRD_GRP

• A1 PG1

• B1 PG1.

Selection ID on the other hand will be used for specific selections.

Suppose if u want to execute one profile for PRDGRP PG1 at LOC A1 , you create a selection ID with this selection like in interactive planning..

How ever, if your selection is

PRD *

PRDGRP *

LOC *,

then , here ur aggregation level helps how to disaggregate values before running the forecast

[Former Member]

Hi Uma maheshwar

I appreciate your detailed reply.

So what you say is, in interactive planning, selection ID mostly does the job of choosing an aggregation level and in mass processing aggregation level is excluisvely specified as selection ID's with multiple selections ( with *) might not be sufficient enough to carry out disaggregation.

I do have one more question. If I have a selection ID, in your example, in which I choose Product group & Location with values PG1, A1 & B. In interactive planning aggregation is carried out at this level. However, if I select this selection ID and a different aggregation level in background activity, which aggregation level would be considered ?

TIA

[Former Member]

Hi,

In the case suggested by you the aggregation level chosen would carry no meaning as you have given a specific selection ID with specific MPOS values for execution of the background.

I guess going through the case below might help you understand the selection ID and aggregation levels concept better.

MPOS Characteristics

Product Hierarchy - Product Group > SKU

Customer Hierarchy - Dist Chnl > Customer

(Possible Values Dist Chnl - 01,02,03,04)

Now I have a selection ID which is given by Dist Chnl - 01

If in the above case I create a background job and give a selection ID "Dist Chnl - 01" and aggregation level as all checked (Product Grp, SKU, Dist Chnl, Customer)

then the background job would be executed the all Product, SKU, & Customer combination existing for Dist Chnl 01 only.

Hope this clarifies the usage of selection ID and Aggregation level

Regards