Combining receiver values in KEU5 allocation cycles.

[unit]

Dear Experts,

We are creating allocation cycle for distributing travel cost based on revenue at product level.

Sender is cost center

Receiver are = Location + Product

With this receiver combination if there are   10 Locations and 100 Products, system generates = 1000 receiver line item.

Client requirement is that while posting, 1000 receiver line items are summarized to 10 line items representing 10 locations.  For business complications we cannot create segments only at location levels.  However, while posting we wish to summarize by blanking the product value.   Is this possible ?

Surfing different OSS notes, I understood that there are no user exit available in allocation cycles.

Please share your experience with alternate options, if any.

Regards

Unit.

[kamalkumar_biswas2 · Accepted solution]

Hi Maru

At present combination system is doing rightly..

I think you may make a prod group of 100 products and make combination Location+Prod Grp as receiver.

Kamal

[unit · Accepted solution]

Thanx Kamal.

This means, while there are no customization or user-exit options within Allocation cycles, only option available would be to create additional characteristic within COPA (Product group).

Regards

Unit

[DaveS4 · Accepted solution]

Hi Maru,

Did you try top down distribution?

Top down Distribution explained with an example - ERP Financials - SCN Wiki

regards,

Dave

[kamalkumar_biswas2 · Accepted solution]

Maru

In my opinion that may be the option in your case...

Kamal

[unit]

Thank you everybody for your inputs.

Considering the fact that there are no No User-exit / substitutions available within Allocation Cycle, I summarize the options available

a) Use Top down distribution

c) Create additional characteristic in COPA and use same as tracing factor.

I close the thread

Regards

Unit.

[kamalkumar_biswas2]

Hi Maru

Close your thread with marking correct/helpful answer so that other can get help...

kamal

[suryavarma_co]

Hi Jayesh,

In my humble opinion, i think, the requirement is a little flawed. What kind of business need will require Product and Location to be part of the Receivers in a Cycle and  Product not to be part of the entry that get written to COPA.

Why not remove Product as receiver from the Cycle.

If that is no possible for some "business reasons" then the only option would be to write a derivation rule to Clear Product. It may look like this

CLEAR PRODUCT

Condition

If SKOST <> Blank or you can specify the Cost Center for which this rule needs to work.

Note:

If you put SKOST as blank, it will apply to all COPA Assessment cycles.

Test the solution thoroughly in Test system before doing in Prd System as the repercussions of Changing Derivation Rule are huge.

Thanks & Regards

Surya