Master Data On The Fly (SAP BPC 10.1 Embedded)

[former_member223971]

Hi experts

In the classic version of SAP BPC 10, Exist a package "master data on the fly" the question is ¿in the version embedded of SAP BPC 10.1, I can use this package "master data on the fly"?

Best Regards!!!!!

Juan Pablo Chaparro.

[former_member186338 · Accepted solution]

Hi Juan,

I think - no, embedded model use different approach of master data handling...

Vadim

[former_member223971 · Accepted solution]

Hi Vadim

Thanks for the answer.

¿you know any solution for enter master data in the version embeded from analysis for microsoft?

Regards.

Juan Pablo

[gregor_dieckmann · Accepted solution]

Hi Juan,

why do you want to maintain master data in the Excel client (EPM Add-In or AO)? You can do so in the admin client. Is this not good enough for end users?

In BPC embedded by now there exist no master data maintenance except in the admin client (and of course in BW, transaction RSD1). Are there just some master data values end user want to create/change and how is this related to the normal planning (i.e. create/change InfoCube data)?

In BPC embedded on the back-end we have a user session with buffered transaction data and of course also master data. Changing this on the fly might invalidate buffers and also 'consumers' of the data; in addition BPC embedded has constraints based on master data (and master data attributes), so changing master data might lead to a realignment problem in the buffered data. This is why there exist - by now - no out of the box way to maintain master data together with transaction data in the user session.

Depending on your requirements you can try the following work around:

- assume you want to maintain values 0PRODUCT, the description and the attribute COLOR

- create a planning enabled DataStore object (DSO) that contains the fields you want to maintain in the master data table; in the DSO you might need other InfoObjects without a master data table, e.g. create an InfoObject ZPRODUCT without master data table and ZCOLOR and ZTEXT for the COLOR and ZTEXT for the description. The latter two you put in the data part of the DSO, ZPRODUCT is the key. It is possible to use ZCOLOR and ZTEXT as key figures (flag in DSO maintenance).

- Create an aggregation level on top of the DSO and an input-ready BEx Query on the aggregation level; use the characteristics ZCOLOR and ZTEXT as key figures in the key figure structure of the query. Using the BEx query in EPM AddIn or AO you get a DSO maintenance for free. Instead of ZCOLOR you might use the original InfoObject COLOR in the DSO; if COLOR has a master data table at least in AO you also get a value help for free

- Now you have your 'master data' in the DSO; you can read the DSO and use a BW API to read the DSO and to update the master data table you want to maintain; e.g. the function modules in package RSNDI, function group RSNDI_MD.

- To trigger this copy from DSO to master data table you might write an exit planning function that reads the DSO and and does the create/update on the master data table 0PRODUCT; you can expose the function in EPM AddIn or AO as a button.

Remark:

If you update master data and transaction data in one user session you have to restart all BEx queries in Excel to avoid problems with buffered data. You should avoid this and do the master data maintenance first and the do the normal planning on transaction data.

This is one idea. At least you get the 'maintenance UI' for free and you have all features of the BEx query to model the UI as you like.

Regards,

Gregor

[former_member223971 · Accepted solution]

Hi Mater Gregor

Is the answer that comes closest to the solution I'm looking for.

thank very much!!!!!!!!!!!

Best Regards.

Juan Pablo Chaparro.