Allocation check at aggregate level

[Zoom]

Hi all,

The scenario is this :

Allocations are maintained at sales organization level. Allocation check is working fine.

The requirement is that the check should happen at sales org. group level.

e.g. sorg 'a1' and 'a2' belong to sorg group 'A'. Allocations to be maintained at level A. User to enter sorg a1 at the time of sales order creation in ECC but the allocation should be checked at A.

Thanks in advance,
Zoom

[Golfi]

Hi Zoom,

Sales Group (OVX4 in ERP) is already defined in ERP, as a subset of Distribution Chain (which by itself is a combination of Sales Org & Dist Channel).

It sounds like you are saying that this "Sales org group" characteristic you are describing is to be a superset of Sales Org, yes? Is there a field in the Sale documents that corresponds to this object? Where in ERP are you defining/maintaining this object?

For Allocation to work, the organizational level where you wish to maintain the allocation should exist in the Sales Documents that you wish to control. If the object does not exist, you will have to create it some way, and use enhancements to get the object over to the APO allocation functionality. Once this is done, you can use standard Allocation functionality (collective characteristics) combined with standard DP functionality (aggregation) to manage the object.

Best Regards,
Golfi

[Zoom]

Hi Golfi,

It sounds like you are saying that this "Sales org group" characteristic you are describing is to be a superset of Sales Org.

Yes. I am expecting the same. I will try to work in the same direction.

Once this is done, you can use standard Allocation functionality (collective characteristics) combined with standard DP functionality (aggregation) to manage the object.

Here I have a specific query. I have tried the functionality collective characteristics not exactly relevant to this particualr scenario..
e.g. I have following chars. combination.
Product Sales Org.
400555 ####
400555 a1
Allocation is maintained for collective combination i.e. 400555 ####
Now if I create sales order for the product with sorg a1, system is not getting any allocations at this level i.e. 400555 a1. In this case, system does not search at collective level because it has already found the char combination at lower level. Here the expectation is that even if char combination is found at lower level at which no allocations are maintained, system should check allocations at collective level.
Relating this to original query, this check should happen at sales org superset level.
So to achieve this, allocations in combination with aggregation in DP is must?

Regards,
Zoom