SAP BPC 10.1 NW Consolidation question

[srikanth_ramachandran]

Hello experts - this might be a fairly basic question but when a full Consolidation is done, my understanding is that all the base records (S_NONE Unconsolidated) are copied to the higher level scope points and the eliminations are created on top of that. For example, if the below is a sample record of base data -

Entity AAAA

Interco I_BBBB

Scope S_NONE

Audittrail GL

Account 112233

Segment YYYY

Category Actual

Flow F_BAL

Amount 150,000

Assuming Entity A and Entity B (property value of Interco member I_BBBB) both roll up to Consolidation Scope ENT_CONS

When Consolidation is run, won't BPC create a record identical to the one above, but with Scope = ENT_CONS in lieu of S_NONE?

And then create ELIM records on top of that (given that Account 112233 is an intercompany account and ELIMACC is set)?

In my test system, I am finding only the ELIM records created after consolidation - the base data is not replicated at the higher level scope point. Am I missing a property or configuration setting somewhere?

Thanks,

Sri

[srikanth_ramachandran]

After a lot more research I have figured that there is something missing due to which the 'no scope' data is not being copied to the group level during consolidation; only the new elimination entries are being created. I have created EUR as a RPTCURRENCY member and set it to type R; balances are being loaded in the cube with EUR and group S_NONE. I do not have any configuration in the Rates model. Audit trail properties are correct; so are Entity and Interco. Entities for which EUR balances are loaded have the Currency set to USD in their properties. Am thinking that may be the problem .. and that perhaps I need to set up rates etc. to enable translation. Any pointers are welcome.

[former_member186338]

Sorry, but it's impossible to answer this question without full analysis of consolidation setup...

[srikanth_ramachandran]

Thanks Vadim - good to hear from you. I understand that ..

[srikanth_ramachandran · Accepted solution]

To close the loop on this issue - it was resolved vide the solution described in KBA 1665088.