How get a dimenshion hierarchy from SAP BPC Dimension.

[Former Member]

Hello friends, we need to get hierarchy from the dimension ACCOUNT of system of the SAP BPC 10.1 for transfer to another project. Ino faced with the fact that BW is not possible to extract hierarchies from the objects of the consolidation system. Our integrator advised the to include the info-provider property: InfoSource with direct update. Please tell me whether it is possible to do so and has this changing is dangerous for our system Consolidation

[former_member186338 · Accepted solution]

In general it's not recommended to use BW methods to directly update BPC objects. Use standard DM packages.

Same question:

Why not to export dimension to text file and then import this text file using BPC standard chains?

[Former Member · Accepted solution]

If this can be done in a standard way, then of course we would like to use it. But we did not see the chains for export the dimensions hierarchies from the consolidation system(Only MD EXPORT). Can you give more details about this standard DM package.

[former_member186338 · Accepted solution]

Yes, MD Export! It will export PARENTHx... What's the issue?

[Former Member · Accepted solution]

The problem is that we need a hierarchy to ACCOUNT the sign of the consolidation system for another project (not in the consolidation system) in which we must set up the InfoObject Characteristics for reporting by analogy with the infoObject ACCOUNT of Consolidation. But the format of uploading data from the consolidation system is not particularly suitable for this.

[former_member186338 · Accepted solution]

Sorry, but you are talking about theoretical things, without samples! Please provide something...

After exporting text file you can perform transformation and conversion on import!

[Former Member · Accepted solution]

"In general it's not recommended to use BW methods to directly update BPC objects. Use standard DM packages."
Can you tell me why SAP does not recommend changing its objects?

[former_member186338 · Accepted solution]

Because in BPC there are a lot of extra tables containing data related to infoobjects. If you use BW methods then the mentioned tables will be out of sync (resulting in not working system).

[Former Member · Accepted solution]

Can you recommend the source of this information for your reference?

[former_member186338 · Accepted solution]

Sorry, but it's a common sense point. BPC models are based on BW objects. But in addition to BW objects there are a lot of BPC related tables - just look in SE16: UJ*

[Former Member]

we have 2 landscape bap and wap and we want to create a DataSource for extracting hierarchy of dimension(ACCOUNT) from BAP to WAP by analogy with the image. But we can not activate the export data source in BW on /CPMB/M4D5BJE due to the invalid namespace /CPMB/.
AND Our integrator advised the to include the info-provider property: InfoSource with direct update on dimension ACCOUNT (/CPMB/M4D5BJE). Please tell me whether it is possible to do so and has this changing is dangerous for our system Consolidation

oblem wneh try to create a DataSource

[former_member186338]

Can you explain the business logic behind the process?

[former_member186338]

Not clear what do you want to achieve... You can export hierarchy as a text file for example!