Multiple level consolidation on SAP BPC 10.1 NW

[Former Member]

Dear experts,

I am facing an issue that I am not able to solve in SAP BPC 10.1 Nw.

in my group I have an holding (let's call it C) that consolidates 2 entities. then we have the main holding (let's call it A) that consolidates C + other entities.

The problem is that Group A doesn't want to see Holding C and Entity B in it's consolidation: Group A wants to see the consolidated result of Group C.

I tried a first solution, wich is to store the result of Group C consolidation in a dummy entity (called CONSO_C) and then put CONSO_C into Group A consolidation.

this solution seems to work, but the problem is regarding IC eliminations.

Since Entity B and Holding C are no longer under Group A, their IC movements are not eliminated in Group A, which is not correct (e.g. Entity D has a credit towards Entity B --> this is not eliminated).

Do you have any suggestion? have you faced the same problem before?

Thanks a lot for your help

Best regards

Andrea

[Former Member]

Hi Andrea,

I don't think this is possible as such in BPC. The only approach I have found (but not tested) so far would be a script that re-classes IC data.

My idea was to use a property in the entity and intco dimension which in your case for entities Holding B and Holding C identifies the Conso C entity. You could then use a script and re-class all IC data on A, D and E that has B or C as the partner against this new Conso C entity (use a separate AuditID) and then have a specific rule in the consolidation that handles the IC elimination against Conso C.

BR,
Arnold

[Grégoire2Ombres]

Hi Andrea,

I never faced this requirement. I know this was sometimes required by large groups in the past where the consolidation was decentralized and operated on different consolidation systems (1 system by level). With this scenario you might get incorrect results because you will calculate the group share for CONSO_C with a unique rate, which is incorrect because B & C could have different rates.

Anyway, to achieve your scenario, it should be possible to adjust, using a script logic, the interco data of entities A, D, E by replacing the interco member B or C by CONSO_C.

Hope this helps.

Best regards,

Grégoire