Skip to Content
avatar image
Former Member

BPC Embedded Design - Guidance required

Hi ,

We are starting to design Sales , Opex , HR and PL planning in BPC 11 version .

In standard version , Normally we will create separate model for each area ( one for sales , one for HR ...) and load actual data to BPC cubes and will do detail level planning in each model level and send aggregated to Finance cube for PL statement .

In BPC embedded , i want some guidance before start design plan ADSO and aggregation levels .

Approach 1 : Can I fallow same like standard approach like create Sales plan ADSO and create Composit provider ( CP ) for both actual sales ADSO and plan sales ADSO and create aggregation level , input query and send total sales to Plan finance ADSO for prepare PL ?


Approach 2 : create only one plan ADSO for all plan data ( Sales , Opex , HR ) ?

My understanding

if I fallow approach 1 , i can easy debug if any error like issues on revenue , then will go Plan sales ADSO , but need to create so many CP's for reporting purpose and create logic's while sending data between plan ADSO's .

If I fallow approach 2 , All data i have one Plan ADSO , then it can reduce no of CP's for reporting and don't required logic's while sending data to finance for prepare PL , but huge data ( detail level and aggregated level ) stored in one cube may cause performance issue later stage .

As a best practice in Embedded BPC , what is best the approcah ?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 07, 2018 at 02:37 PM

    One stupid question - why do you need embedded model at all?

    Add comment
    10|10000 characters needed characters exceeded