Currency Conversion using RATEENTITY

[Former Member]

Hi,

We have the following requirement at our Client:

Entities in the same country uses different Exchange rates, example : 2001 " Mexico" and 2002 " Mexico" uses two different exchange rates.

To achieve the above requirement I configured NW BPC 7.5 with patch level 9 to use RATEENTITIES.

Example

There will be two rate entities like

1) Global - being used for Company Code 2001

2) P_2002 - being used for Company code 2002.

So I maintained different rates for Mexican Pesos in Global and P_2002 RATEENTITIES.

In ENTITY master we maintained a property - RATEENTITY and maintained the values as GLOBAL for entity 2001 and P_2002 for entity 2002.

I used the following Script Logic:

XDIM_FILTER ENTITY = ENTITY.PROPERTIES(u201CRATEENTITYu201D) = u201CP_2002u201D

*RUN_PROGRAM CURR_CONVERSION

CATEGORY = %CATEGORY_SET%

TID_RA = %TIME_SET%

CURRENCY = %RPTCURRENCY_SET%

ENTITY = %ENTITY_SET%

RATEENTITY = P_2002

*ENDRUN_PROGRAM

*COMMIT

So even after using this setup, BPC is converting values for both ENTITIES (2001 and 2002) using rate from RATEENTITY P_2002.

I also tried to run Currency Conversion by hard coding company code by enter ENTITY = 2002 and that did not work either.

Is there a way to achieve this requirement.

[Former Member]

Thank you Tom,

Issue has been resolved when I added RATEENTITY same as ENTITY.

Even when I commented RATEENTITY= GLOBLA, it worked fine.

So, now my Script logic is as follows:

*RUN_PROGRAM CURR_CONVERSION

CATEGORY = %CATEGORY_SET%

TID_RA = %TIME_SET%

CURRENCY = %RPTCURRENCY_SET%

RATEENTITY = GLOBAL

*ENDRUN_PROGRAM

*COMMIT

Thanks

[Former Member]

You are welcome

[Former Member]

Hi,

Whatever you define in the RUN_PROGRAM it will use as parameters to convert LC to GC, so your script logic set up like this will exchange all entities using the RATEENTITY P_2002.

First thing you should do is the RATEENTITIES should be valid members of your ENTITY dimension. So if your entity is 2002, there should be a member of the RATEENTITY dimension called 2002, not P_2002. You should then remove the RATEENTITY=P_2002 parameter from the RUN_PROGRAM completely (if it doesn't run without the parameter, try putting it back with GLOBAL as the value).

With both of these things done, when currency conversion is called for a particular entity it will look for a corresponding entry in the RATE application against the same entity, otherwise it will use what is stored in GLOBAL.

Let me know if that solves your problem.

Tom.