BPC NW 10.1 embedded BW 7.4SP13 : fox - copy with other infoprovider

[wissler_bastien]

HI,

I would like to copy data records from info provider A to info provider B

But I have two problems of mapping :

the codification of key figure in infoprovider B is not the same : 0AMOUNT1 and not 0AMOUNT

The codification of characteristic in info provider B is not the same : 0ACCOUNT1 and not 0AMOUNT

INFOPROVIDER A	INFOPROVIDER B
0ACCOUNT	0ACCOUNT1
0AMOUNT	0AMOUNT1

I would like tu use the FOX formula

DATA ACCOUNT TYPE 0ACCOUNT1.

INFOPROVIDER A.

FOREACH ACCOUNT.

{0AMOUNT1;ACCOUNT}=A.{0AMOUNT;ACCOUNT}.

ENDFOR.

But, it's KO, How to manage the mapping for KF 0AMMOUNT and the characteristic 0ACCOUNT?

Thanks

Bastien

[gregor_dieckmann]

Hi Bastien,

the situation is not clear. As I understand you have two key figures 0AMOUNT and 0AMOUNT1 and you want to copy key figures values from 0AMOUNT to 0AMOUNT1. This can be done using a planning function of type FOX.

But you also mention that you have two dimensions (i.e. characteristics) 0ACCOUNT and 0ACCOUNT1. Here it is not clear whether these dimension have exactly the same dimension values or whether also some dimension value of 0ACCOUNT have to be mapped to 0ACCOUNT1. If the values are exactly the same in BW 0ACCOUNT1 should be modeled as a reference dimension (characteristic) referencing 0ACCOUNT.

If you are using referencing characteristics you can create a MultiProvider M (or CompositeProvider) with InfoCubes A, B as part providers you map dimensions as follows:

A: 0ACCOUNT -> M: 0ACCOUNT1

B: 0ACCOUNT1 -> M: 0ACCOUNT1

Key figures cannot be mapped. Thus you include 0AMOUNT, 0AMOUNT1 in the aggregation level.

Then you create an aggregation level on top of M and there you define the FOX planning function with characteristics to be changed: 0INFOPROV. The FOX code then is just on line:

{0AMOUNT1,B} = {0AMOUNT,A}.

Thus you also don't need the new FOX feature to read data from other InfoProviders.

To understand why this works you should read how planning functions work in general, namely that planning function code is executed per block (thus often loops in FOX are not needed); cf.

Process Flow of Planning Function: Distribution by Key - Planning Business Data with BW Integrated P...

in section 5.

In addition I always recommend to read the FOX documentation in the FOX editor (press the Info Button). There you find many examples.

Regards,

Gregor

[wissler_bastien]

Hi Gregor,

I will test your solution.

Currently, there is not a multi for the infoprovider A and B because there is different  two process

With the 'classic BPC', it's possible to use the following function :

*RENAME_DIM 0ACCOUNT = 0ACCOUNT1

Is it this function with BPC Embedded?

Regards

Bastien

[gregor_dieckmann]

Hi Bastien,

no, such a function does not exist. I also wonder what such a functions does if 0ACCOUNT and 0ACCOUNT1 have different data types and different values.

For a comparison on BPC Standard and BPC Embedded concepts the following link might be helpful:

In general I recommend to learn some basic BW concepts; this will be very helpful to use BPC Embedded. Observe that BPC Embedded is not a reimplementation of BPC Standard.

Regards,

Gregor