Regional Consolidation BPC 10

[Former Member]

My client is using BPC 10 NW Standard. Currently they are doing consolidation at the entity level, so on the financial statement currently they see some like this .

France /  Span/ Germany/ USA/ Canada/ India/ China/ Japan/Total Consolidated.

Now the client to enhance their ownership structure, so they want to see consolidation group per region as well, they want some like this:

Group Europe/      Group NA         Group Asia

1-France                1-USA              1-India

2-Span                   2 Canada         2-China

3-Germany                                      3- Japan

I know that grouping entities per region can be done if I change the ownership structuration and Maintain the entity dimension. My question is that what additional change need to be done ? should that have to change or added additional business rules for the group to work ? or everything is going to automatically roll up.

Please advice rewarded point will be done  !!!

Hermann

[former_member225135]

Hi Hermann,

No changes are required if you want to see the reports at consolidated level (except the change in entity dimension and ownership structure)

Alternatively, you can use "STORE_ENTITY" property in scope/group dimension, so that the consol results are posted in E_**** (E_group level) member of entity dimension.

Regards,

Rahul

[Former Member]

Rahul,

I really appreciated your reply and it is certainly helpful but my other concern is that. Entities belonging to a group do not have percentage of ownership between each other. The company just own 100% of each entities.  I am just wondering when I set up my ownership Structure should that have to ignore the relationship among entities and just set up 100% POWN  and PCON at the group level ? Is that going to work ?

Please advice

Thanks!

[former_member225135]

Hi Hermann,

Do you require consolidated balances at each group or it is just a presentation?

If you require a consolidated balances (after interco elimination) at each group level, then you have to enter the POWN/PCON/PCTRL as the case may be and then only you can generate the consolidated balance at that group level.

and if it is just a presentation, then change your entity structure to rearrange the entity based on reporting and maintain normal ownership. For report, you can then use the entity hierarchy. (assuming that the no intercompany balances are required to eliminated for each group)

Regards,

Rahul

[Former Member]

Rahul,

I want the elimination to occur at the entities and I want the balance to roll up at the group level. If I follow you advise base on my expectation, I need to enter PCON/POWN/PCTRL at each sub-groups at 100% of every entities. . Also, I will maintain another 100% PCON/POWN relation between the single Group and the different sub-Groups.

Please tell me if that make sense for you.

Thank!

[former_member225135]

Hi Hermann,

In that case, you will required to maintain POWN/PCON/PCTRL for each entity in their respective group.

Regards,

Rahul

[Former Member]

Rahul,

I have two questions

1- The change of the entity structure to hierarchical group will need any critical change in the BW staging cube? or it will be essentially on the transformation file.

2- This is the transformation for scope dimension.

scope=*STR(SC_ALL) where  SC_ALL is the only member of the scope dimension as well as Ownership Manager. By creating an hierarchical structure how can maintained a new transformation logic. Let used our previous example a I give above.

Thanks!

[former_member225135]

Hi Fermann,

1. No changes at BW staging level

2. You have to create different scope member (Europe, Asia in your case). It is quite strange that the scope dimension doesn't have non group member (CURRENCY_TYPE=N). Once the different scope members are created, you can then maintain ownership for that group

Normally what i use to do is that whenever the data gets loaded in BPC, the scope is hard coded as non group and when executing the consolidation, system will post the data on different scope member depending on the execution level of consolidation.

Regards,

Rahul