Send data to another BPC cube

[Former Member]

Hello!

We need to send data to another cube, but it is needed to do some transformations to the original data, using a dimension that does not exist on the destination model.

We thought on 3 scenarios:

1. On the source model, use the DESTINATION_APP functionality. Is it possible to call a BADI using this functionality?
2. On the source model, use a custom logic BADI. Can it send data to another cube?
3. On the destination model, use a custom logic BADI. Can it real data from another cube?

Which of these scenarios are possible? And which of them, is the best one?

Thanks.

Best regards,

Simone Farinha

[former_member182305]

Hello, I did somthing similar using a Data Manager Load Transactional Data from BW Infoprovider UI Process Chain: CPMB/LOAD_INFOPROV_UI.

Then look for the BPC Cube in the Wizard.

If the dimension in the Source doesn't exist in the Destination cube, it doesn't matter, just don't Map it in the tranformation file

For instance if you have:

Source Dimensions      Destination cube Dimensions

Category                     Category

Account                       Account

Time                            Time

Entity                           Entity

Currency                      Currency

Version    ->                 Does not exist in destination.  (don't map it)

What BPC will do is Merge Data in Version and reporting by version won't be posible in the new cube.

NOTE: You have to map BW Technical Dimensions name, you can see them in RSA1

Hope this helps.

Regards.

[former_member186338]

With CPMB/LOAD_INFOPROV_UI you will not transfer data for yellow requests! Not recommended!

[former_member200327]

Hi Simone,

Why using BADI is in all your options?

I'd suggest considering first options without BADI. In this case since you need to use Dimension that is not in the the target Model, DESTINATION_APP could be the most suitable option.

Without knowing what kind of transformations you need, as Vadim said, it's hard to tell if you can use it or not.

Regards,

Gersh

[former_member186338]

I agree that the first attempt has to be done without any badi, using only script logic!

[Former Member]

Hello!

Using DESTINATION_APP is not enough since based on two dimensions on the source model (company and value field) and a property of a third dimension (material) is necessary to define a dimension on the destination model (group account).

With this requirement we think that DESTINATION_APP is not enough, it is needed to use a BADI.

We thought on 3 scenarios:

1. On the source model, use the DESTINATION_APP functionality. Is it possible to call a BADI using this functionality?
2. On the source model, use a custom logic BADI. Can it send data to another cube?
3. On the destination model, use a custom logic BADI. Can it real data from another cube?

Which of these scenarios are possible? And which of them, is the best one?

Thanks!

Best regards,

Simone Farinha

[former_member186338]

"Using DESTINATION_APP is not enough since based on two dimensions on the source model (company and value field) and a property of a third dimension (material) is necessary to define a dimension on the destination model (group account)."

Sorry, but not clear! Please explain in details using sample with dimension members etc...!

"On the source model, use the DESTINATION_APP functionality. Is it possible to call a BADI using this functionality?" sorry, but what is the relation between DESTINATION_APP and badi ????

"On the source model, use a custom logic BADI. Can it send data to another cube?" - Yes

"On the destination model, use a custom logic BADI. Can it real data from another cube?" - Yes

[former_member186338]

Sorry, but not clear! Everything is possible (all 3)

Please explain in details the process!