multi-level allocation on different allocation groups

[Former Member]

Hi,

I've used multi-level allocation but couldn't achieve the desired behavior.

Question:

is it possible to have something like a hierarchy with a direct relationship between the hierarchies in allocation available?

Bsuiness scenario:

We are planning allocations on a very detailed level on a monthly base.

Unfortuenately the plan is not so accurate in some cases. This means that during the month we have to shift some quantities, lets say from one country to another one for one customer. We can not change the level of planning. So we have to stay with the detailed planning.

Example:

Our planning level for allocation is level 2 (see below example). Nevertheless when level 2 is allocated completely we want to search for more contingent on the more generell level (level 1). In the example below this would mean that a sales order for country A2 has requested quantity of 45 TO. With an allocation scheme procedure which checks first level 2 and afterwards level 1 in two different schemes I get a confirmation of 25 TO on the first scheme and 20 TO on the second one.

Level 1                A1: 100 TO

Level 2     A2: 25 TO          B2: 75 TO

Problem:

The problem is that there is no relationship between the allocation groups. In the planning area I can force this relationship via drill down.

A proper behavior for the business case would be that the level 2 allocated quantity is first consumed with level 1 available quantity and only afterwards the mulit-level check on level 1 can continue. Also we need to get the information of the more generel level back to the detailed level. Lets see the desired behavior for the example:

Level 1               A1: 55 TO

Level 2          A2: 0 TO     B2: 55 TO

I know that this is not the desired functionality of multi-level allocation, but is there a way to get this work?

Appreciate your thoughts on this.

Regards,

Stefan

[Former Member]

Stefan,

Are you talking about Product Allocation (GATP)?   Or.....?

Best Regards,

DB49

[Former Member]

Hi Dogboy,

yes, it's product allocation.

Thanks.

Stefan

[Former Member]

Stefan,

Product allocation is able to handle multiple characteristics.  As long as your characteristics are structured hierarchically, then product allocation can also be made to behave hierarchically.

Product allocation further is a restriction on sales.  In this I mean that you are setting maximum levels beyond which you do not wish to allow any further sales, by entering allocation values that are assigned to specific characteristic combinations.

In your examples, it is not clear what you mean.  You say a 'general' level.  What does that mean?  Your illustration makes it clear that 'A2' and 'B2' are characteristics that represent 'Countries'.  What does 'A1' represent?  Do you intend to enter product allocations against 'A1'? More importantly, how do you intend for A1 to relate to A2 and to B2?

Best Regards,

DB49

[Former Member]

Hi dogboy,

thank you for stepping into this.

Maybe I can describe the business scenario more in detail:

We are planning on product - country - customer level at the moment (referring to previous level 2).

During the month there is a lot of switching quantities along customers of different countries. Users want to have new checking level (referring previous level 1).

Here we check on product - region.

A region is set up of multiple countries.

We can not set up region as an attribute, because for different products region should be defined individual.

A1 means product - region level

A2 and B2 means product - country - customer level

That means that contingent of level A1 is the sum of both A2 and B2 and no extra exclusive contingent. When you use contingent of A2 then you need to substract this quantity from A1 before you check against A1.

I've transferred my contingent from planning area to both allocation groups and that worked fine. But during product allocation check there is no consumption of level 1 quantity with level 2 quantity.

Best Regards,

Stefan