exchange rate aggregation

[Former Member]

Hi, Is there any way to avoid aggregation of key figure in InfoCube. Beacuse for multiple records , I want same exhcnage rate in infocube.

E. g :

In DSO:

Doc N     ItemNo   Ex.Rate amount

Doc_1 LineItem1 59.0          100.00

Doc_1 LineItem2 59.0          200.00    

Doc_1 LineItem3 59.0          300.00

Doc_1 LineItem4 59.0          100.00

Doc_1 LineItem5 59.0          200.00

In InfoCube, I want like this :

Doc No  ExcRate    Amount

Doc_1   59.0          900.00

But, It is coming like this, because it is aggregating key figures :

Doc_1   295.0     900.00

Thanks,

[Former Member]

Hi,

Is it not possible to keep the 'Exchange Rate' field as a Characteristic instead of a Key Figure?

Br, Harish

[Former Member]

No, Exchange rate is DEC type, and hence only act as key figure.

[Former Member]

Hi Seema,

Yes, I understand that the Exchange rate is of DEC type.

My idea would be to add a characteristic infoObject to your infocube and load the exchange rate value.

This way, the data will not get aggregated at the infocube level.

Alternatively, you can create a new DSO for storing Exchange rates for Documents and build a Composite provider on top of your infocube and DSO.

Br, Harish

[former_member586947]

Hi Seema,

     Have you tried the second point of my previous reply.

Regards,

Satya.

[Former Member]

Hi,

But, It is coming like this, because it is aggregating key figures :

Doc_1   295.0     900.00

if "item no" is not added to cube , then data gets summarized.

where is the " Item no" in cube? isin't it added? are you trying to maintain header level data in cube? cube data is always aggregated.

[Former Member]

Hi, Line Item field is not in Infocube, it is already there in DSO. I want aggreagted data at header level.

[Former Member]

if you requirement is for reporting, then you can achieve by creating a bex query on top of info cube , 

otherwise, your requirement is not directly possible in cube to my knowledge.

[former_member586947]

Hi Seema,

     Try to manage this case in the start routine. In the start routine (transformation from DSO to Cube) change the SOURCE_PACKAGE in such way that only the first item should have the exchange rate and remaining item's exchange rate should be zero. Make sure to use the semantic group (Sale order and Item) in your DTP. If you opt this then you have to do a full load every time.

Another way is to make exchange rate as a characteristic. Create exchange rate info object of type Char and add it in the cube. Map this filed in the transformation from DSO to Cube with exchange rate from DSO.

This will solve your problem.

Regards,

Satya.