QUESTION Creating Models and Dimensions for BPC Embedded

[former_member182305]

Hello Experts,

I am developing a Demo for BPC 11 Embedded version. I have a question regarding the Models and Dimensions:

In BPC Embedded the objects needs to be created in Hana Studio or eclipse. To create a model you clic in new-ADSO, but you can create the Adso based on other already created, I notice that I can set as model the default BPC ADSO that includes the workspace CPMB/<Tech ID>. If I create this way the DSO, the new ZDSO takes the standard BPC Dimension also with the workspace CPMB. My question is if this is a good practice or should I create all the dimension and attributes separately?

Thanks for the posts.

Best Regards.

[gregor_dieckmann · Accepted solution]

Hi Sebastian,

using 'Copy From' in the BW Modeling Tools to copy InfoObjects or ADSOs creates a deep copy not a reference; this is ok. A real reference would cause problems since BW objects in namspace /CPMB/ are under control of BPC Standard and have a different life-cycle as BW Embedded objects, the latter are global BW objects.

Regards,

Gregor

[Former Member]

Hi Sebastian Montero,

When we take a copy of existing ADSO to the new ADSO it will refer all the existing Characteristics and Key Figures.

In this case if any changes are performed on these existing characteristics the changes would be effected to all the Infoproviders that are referring.

Hence if we are sure enough that no one would do changes to existing masterdata then thats fine to copy else it is always a better idea to copy the characteristic's, keyfigure's and then create infoprovider using these new objects.

Regards,

NagaKiran

[gregor_dieckmann]

Hi Sebastian,

your terminology is unclear to me, what do you mean with 'default BPC ADSO' and with 'workspace'?

For the basic concepts you can read

https://blogs.sap.com/2014/10/21/concepts-compared-bpc-standard-and-bpc-embedded/

The idea of BPC Embedded is to use existing BW data models, but of course you can also create new ADSOs, CompositeProvider in BW and use these provider in BPC Embedded.

In BPC Standard you start to create BPC-specific dimensions (in the technical namespace /CPMB/) and then BPC Standard generates an ADSO in the namespace /CPMB/. These generated InfoProvider are under control of BPC Standard and should not be used again in BPC Embedded.

Regards,

Gregor

[former_member182305]

Thank you very much for the answer Gregror,

"what do you mean with 'default BPC ADSO' and with 'workspace'?" ->

A: In a classic Version of BPC, you activate the ENVIRONMENTSHELL wich you can visualize in Hana studio, all BPC objects are created from the admin and has the prefix /CPMB/ for the technical name.

I understand that I should not use BPC objects, but when you create an infoobject, you can set in the creatino copy from: "here is where I want to set BPC objects as reference" to create a bw object base on bpc configuration, but it wil not be the same, it is going to be a copy not a reference, do you think it could cause any trouble in the model??

Regards.