How do we load plans that are being handled through cost element category 43 type cost elements

[Former Member]

Hi

Currently we have some allocation cycles in ECC that are posted using secondary cost elements of category 43. This means we cannot post manually to these cost elements. They can only accept postings through the execution of the allocation cycle in ECC.

Now, we are carrying out planning through BPC. Hence, the solution covers of the creation of some allocation BPC scripts that replicate how these plan cycles work in ECC. For the proof of concept I used a secondary cost element that did allow manual postings to ECC. In the end game, all the actual assessment cycles are run through ECC during period end and all plan assessment cycles are run through BPC. The actual assessments use the aforementioned 43 category cost element, and the plan cycles (in BPC) use a different secondary cost element.

However, now we have a problem. The allocated plans are retracted to ECC to allow plan v actual analysis. And in this case, all the reports will show plans per cost centre on 2 lines - one for the cost element reading from the actuals, and one for those from plans.

Unless I ask the business to stop using ECC for plan v actual (which will be a step change), would anyone have any experience of such problems during Planning implementations using BPC allocations?

regards

Shrikant

[former_member186338 · Accepted solution]

Hi Shrikant,

We use exactly this: "Unless I ask the business to stop using ECC for plan v actual" We perform plan vs actual comparison in BPC reports. The rest is more less the same (allocation in ECC and allocation in BPC).

B.R. Vadim

[Former Member · Accepted solution]

Hello,

Cost elements category 43 are used for activity allocations, not assessments and indeed cannot be manually posted in ECC.

A work around solution to report plan/actual in ECC is to define cost element groups for each combination of the planning cost element (posted from BPC) and the activity allocation cost element (posted in ECC).

Regards

Thomas