Skip to Content

Default logic currency translation works in LoadInfoProvider only on COPY ratetype?

Hello,

we have a strange behaviour in our BPC 10.0 environment.

As already stated in the headline, the currency translation in the default logic is not working properly in conjunction with the LoadInfoProvider package.

We are using the following (widely used) coding in the DEFAULT.LGX:

________________________________________________________________________________________________

// Currency conversion Modell

*LOOKUP Rates                         

*DIM R_ACCOUNT = KEYFIGURES.RATETYPE      

*DIM R_ENTITY = "Global"                  

*DIM KURS:INPUTCURRENCY = ENTITY.CURRENCY 

*DIM MEASURES = "PERIODIC"                

*ENDLOOKUP

*WHEN RPTCURRENCY

*IS LC                               

*WHEN KEYFIGURES.RATETYPE             

*IS COPY

*REC(EXPRESSION = %VALUE%,RPTCURRENCY = EUR)                

*IS AVG

*REC(EXPRESSION = %VALUE%/LOOKUP(KURS),RPTCURRENCY = EUR)   

*IS END

*REC(EXPRESSION = %VALUE%/LOOKUP(KURS),RPTCURRENCY = EUR)    

*ENDWHEN

*ENDWHEN

________________________________________________________________________________________________

The coding is working as expected when executed following a 'Save data' in an input schedule.

But when executed following a LoadInfoProvider package which imports data from a BW cube, only data with the RATETYPE 'COPY' is calculated (and same value is saved in EUR).

As said, when done after 'SAVE', the coding works as designed and delivers EUR values also for the other 2 ratetypes AVG and END!

Also if the 'normal' FX_RESTATEMENT Package is executed, all keyfigures are calculated into EUR, COPY as well as AVG and END ratetypes.

Exchange rates for the periods/ratetypes are definately maintained (otherwise it would not show proper values in the other 2 modes...)!

It looks like the lookup for the rates is not working properly if executed after the LoadInfoProvider...

Any ideas anyone?

p.s.:

Target model is PERIODIC,

calculation engine is JAVASCRIPT  (ABAP not possible because of nested operations used in other logics)

patch level:

     SAP BW:  7.40  SP 5

     CPMBPC:  8.01  SP 6

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 13, 2015 at 02:59 PM

    Hi Robin,

    Can you show the import result without launching default.lgf?

    Vadim

    P.S. And also please describe all dimensions in the model...

    Add comment
    10|10000 characters needed characters exceeded