SNP Disaggregation with Capacity Leveling

[Former Member]

Hi,

we are implementing the Apo-SNP aggregated planning scenario with the capacity leveling functionality and we need to understand the system behaviour in this case.

The case is the following:

Location Product hierarchy, with 3 Product: Prod1, Prod2 and Prod3, and an aggregated product (PRODAGGR), without Quota Arrangements.

Prod1 has a forecast of 100 PCs in the weekly bucket 1.

Prod2 has a forecast of 200 PCs in the weekly bucket 1.

Prod3 has no forecast requirements.

After a heuristic run at aggregated level, PRODAGGR has a planned order of 300 PCs in the bucket 1.

At this point we have a capacity overload for the resource in the bucket 1 and, performing a capacity leveling, the system shifts planned orders for PRODAGGR, in the following way:

100 PCs in the bucket 1, 100 PCs in the bucket 2 and 100 PCs in the bucket 3.

At this point, performing a run of Disaggregation (Disaggregation method according to demand, Disaggregation Mode u201CPeriod Based u2013 Bucket Orientedu201D), the system disaggregates planned orders at sub-products level, in the following way:

Bucket 1: Prod1 33 PCs, Prod2 67 PCs.

Bucket 2: Prod1 33 PCs, Prod2 33 PCs, Prod3 34PCs.

Bucket 3: Prod1 33 PCs, Prod2 33 PCs, Prod3 34PCs.

In this way, we miss the link with forecast elements, and we are planning orders for Product (for example Prod3), that donu2019t have Demand; meanwhile, we are not able to satisfy demand for Prod2, generating a shortage.

My question is: this is a system behaviour, and itu2019s not possible to change it following the standard, or itu2019s possible to manage our requirements in some way?

Thanks in advance,

Regards.

[Former Member]

Hi,

Have you tried to use Network disaggregation.

It may give different results as it will read forecast also.

There is BADI to influence disaggregation which you can use.

Vipul