Currency conversion via routine in transformation BI 7.0

Hi,
for an international data model we want to translate currencies via data load using a routine in the transformations. We are thinking about creating 2 key figures for local currency and group currency. Group currency is always EUR. We found to function modules but we are not sure about the differences and if we can us them at all: CONVERT_TO_LOCAL_CURRENCY and RSW_CURRENCY_TRANSLATION
Does anyone of you implemented currency conversion in a transformation before using a routine. And does anyone have experience with those function modules and can explain the differences? Thanks a lot in advance! Any help is appreciated!
Aline

Hi,
You can use the readily available functionality to convert the amounts from one currency to other.
Use transaction RSCUR (maintain currency translation types) to create the currency translation type nad use it directly in the transformations.
Regards,
Yogesh

Similar Messages

Currency conversion via Currency Type.

Hi all:
I have defined a Conversion Type to do currency conversion during transformation. Why can I use it only when the target is an Infocube and not when the target is a DSO?
Thanks.
Regards.

Hi,
unit conversion is not supported yet, when the target is DSO.for conversion we can use routine.
for more details..PFB the link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60c0ef09-c1a8-2b10-eb87-824b23577923
thnks.

Multiple currency conversion via one variable possible?

Hello,
following problem:
I have a report which contains different currencies (e.g. EUR, CHF, etc.).
In this report we have different calculated key figures (on cube level).
Each key figure have different currency conversion (maintained in rrc1).
Question: Is it possible, when the user starts (execute) a report one variable
pops up e.g. display all key figures in USD <b>all different currency conversions will be reflected</b>? In the system I don't know where.
Any idea?

Ok, I find a solution by myself.
In the AdminInfo object is a property called MultiCurrencyCheck. When this is set to cc_NoMessage, I can save the journal entry.
If you want to change this setting in Business One:
Select Administration --> System Initialization --> Document Settings --> Per Document tab --> Journal Entry tab
There is a check box "Allow multiple currency transactions". The description is wrong and it should say "Block multiple currency transactions", like the other. When it is unchecked, I can make multiple currency transaction otherwise not.

Currency Conversion loading...

Hi All,
I am going to perform currency conversion via update rule. I understand now to write the code in the start routine of the update rules. Some basic questions below:
1. How is the exchange rates loaded to BW? Via the transfer global settings?
2. How often do you load exchange rates in BW? What is typical?
3. Where in BW can I check the exchange rates?
4. Let's assume the rates are loaded to BW. Now, a dataload comes in and the currency conversion takes place in the update rule to the Cube. Let's say that 1 Euro = 1.15 USD on 1/19/06. So all data loaded to the Cube on 1/19/06 will get this exchange rate. Now, on 1/20/06 new rates are loaded and the conversion is now 1 Euro = 1.50 USD. So the next InfoPackage load will get these new rates?
Is this incorrect, or does the exchange rates in BW all have dates, so depending on the date of the document being loaded to the Cube the correct exchange rate is read to equal this date. Example document date = 1/19/06 so it gets the exchange rate 1/19/06, where all documents that are 1/20/06 will get exchange rates equal to 1/20/06???
Please excuse my ignorance on this subject. My invovlement with BW in the past has not involved currency conversion...until now
Cheers,
Mike

Hello MIke;
Go to T-code RSA1 > Sourec Systems > Transfer Exchange Rates > in the menu Program > Execute in Background > It brings up a screen for print parameters, but the settings apply to schedule this job as required.
The update of exchange rates is updating tables TCURR and TCURV. If you run at the same place the transfer of global settings, the tables TCURF, TCURS, TCURT, TCURV, TCURW, TCURX, TCURC and TCURN are updated.
For details check the programs RSIMPCUST (global settings) vs. RSIMPCURR (exchange rates).
Also if you see these tables for example TCURR then you will see the exchange rate type which you will be using according to your business scenarios and the pick the exchange rate from the tables.
Pls assign points if this hleps.
Regards:
BK

Assign currency via routine

Hi,
I have a key figure with an amount and currency. Both values need to be retrieved from another source than the one in the transformation rule. The solution for this is of course a routine where I'm able to assign the amount, but not the value. The only ways to assign a currency is via source (not the correct one) or conversion.
How can I assign a currency via a routine?
Eddy

Hi Eddy,
in BI 7, Tranformations, try with "Routine with Unit", here we take only Currency amount, and unit is assigned inside routine.
i am not sure this meets requirement.
Best Regards.

End routine for Currency conversion

Hi,
I have a requirement in which i have to convert sales and cost into three types of currency as GBP, INR and EUR in cube. i made 3 different fields for sales as well as for cost. But i am unable to write end routine for it.
Can anyone please help me that how can i solve this problem.
Roma

Hi,
In transformation itself you can do your currency conversion.
http://help.sap.com/saphelp_nw70/helpdata/en/de/6372426f0f9041e10000000a1550b0/content.htm
If you want to write a routine in to do conversion, you have to go for start routine instead of end routine.
Thanks
BVR

Currency Conversion Issue in Infocube Purchasing Data (0PUR_C01) Routine

Hi Gurus,
We are using SAP BI 7.0, We are having reports on Purchasing Data (0PUR_C01) under that 2 updates rules are there.
For the field Effective purchase order value (0ORDER_VAL), there is one standard routine only from the Datasource 2LIS_02_SCL.
My problem is that when there is Currency other than Local currency in field Order Currency, we dont get the Purchase Order Value though there is PO Quantity.
Thanks in advance.
Regards,
Rajdeep.

Hi Rajdeep,
Please verify that the PSA contains data in the fields mapped to the objects below, as they are all used in the currency conversion routine:
ORDER_VAL
DOC_DATE
ORDER_CURR
LOC_CURRCY
EXCHG_RATE
If something is mapped incorrectly or something like that the currency conversion might fail.
Hope it helps.
BR
Stefan

CONVERT_TO_LOCAL_CURRENCY currency conversion errors in Delta mode

Hello,
I have been working with SAP via customer messages for a month now with no resolution. As many of you have experienced, the SAP Level 1 support is pretty useless so I would like to check here to see if I can get some help.
I found a thread where another user has had the exact same problem as I have.
Problem: Exchange rate in Update rules with DELTA mode
However, there was no answer given to him. So, if anyone can help, I appreciate it. Here's the problem:
When a record comes through 2LIS_13_VDITM (for example), it had a document currency of EUR, a local currency of PLN and a statistical currency of USD. The first time the record comes through, it comes through just fine. The exchange rate from EUR to PLN is 3.533. The statistical currency value is calculated by taking the document currency value and multiplying it by the exchange rate from EUR to PLN to get the local currency. Then, this local currency is converted to USD by multiplying itself by the PLN to USD exchange rate of 1.519.
These are the exchange rates that are coming through as key figures on the transaction data. The problem is when a delta occurs. The data goes into the ODS and then once the update rules to the cube get it, the signs are backwards on the exchange rates. This makes sense so that the exchange rate key figures will cancel themselves out, but the SAP code says to calculate the local currency, it must first take the document currency and divide by the exchange rate. It should still be multiplying because the exchange rate from EUR to PLN is still 3.533. The negative on the key figure that is being zeroed out tells the code to divide though.
You cannot simply set the reversal indicator because the values that do come through ok would then be erraneous as the previous poster who had the same issue encountered. This is really causing some bad data for us. This is SAP delivered code. Any help would be appreciated.
Thanks,
Brent

hi,
chk out various application currency conversion links
Need Urgent Help on Currency Conversion Routine
Currency conversion using transformation rule
http://help.sap.com/saphelp_nw04/helpdata/en/bc/058f4073b2f30ee10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/16/088f4073b2f30ee10000000a155106/frameset.htm
Ramesh

How to turn off Currency Conversion within the execution of Fox code

Hi All:
We have a number of custom key figures defined in a Planning Layout.
We had wanted to define those fields as type CURR with 4 Decimals, however it appeared that 2 Decimals was the maximum we could specify. We therefore wound up using Type FLOATING POINT with 16 Decimals.
In some Fox code that calculates these custom key figures we then use a ROUND statement to produce values such as 3.2735000000000000.
When this Fox code executes in debug mode, I see a generated ABAP program running which includes Include programs RUPFGENTOP and RUPFGEN00. This program executes a Form F_00001, which is essentially the Fox code. Here I can see the ROUND statement producing the desired result. Right after though a Form TCURX_CONVERSION executes, which often reintroduces all 16 decimals, and I might get values, such as 3.2735000000000001 or 3.2734999999999998. These small fractions cause other issues later on in the process.
In our case we are not trying to convert an amount from one currency to another, so we don't understand why it even would try to do a currency conversion.
My question: is there any way to "turn off" this currency conversion routine?
Please advise - any suggestions would be most welcome.
Many thanks in advance,
Robert van der Kam

Hi Robert,
the solution suggested by Anass only works for key figures of type number. For key figures of type amout or quantity it is not allowed to change the number of decimals. Especially for amounts the number on the DB can only be intepreted correctly knowing the currency. Depending on the currency the value 1 on DB may be 100. This is why the FOX does the TCURX_CONVERSION, a better word would be currency shift since currency values have to be scaled depending on the values maintained in table TCURX. Since FOX needs one common number type for calculations the shift is neccessary.
This is the reason why amounts have only 2 decimals on DB, the real number of decimals comes from TCURX; no entry there means 2 decimals, i.e. not scaling is neccessary. This is why changing the number of decimals via domains might corrupt all data.
It seems that you are using release 7.0x, in releases 7.3x internally uses DECFLOAT data type, thus the 'problems' coming from binary arithmetic in ABAP FLOAT will not occur any more.
Regards,
Gregor

Currency Conversion for Exchange rate type "AS02"

Hi Experts,
I am gonna post the most challenging problem (regarding currency conversion) I ever faced in my 1 year of BW Carrier.Kindly provide a solution.
There are three types of currency to be used in the query for Key Figure 0NET_VALUE (so total 3 Key Figures to be created)
   1.Document currency (may be any currency)
   2.Local Currency (must be EURO)
   3.Global Currency (must be USD)
From Document currency to Local Currency(EURO) we are using Exchange rate Type "M" (in Conversion Type created in Trans RRC1) [There is no problem in this conversion]
Problem starts now--->
From Local Currency(EURO) to Global Currency(USD) we have to use Exchange rate type "AS02" (in conversion type to be created in RRC1)
but there is a Business requirement that currency rate should be as per the last day of the entered period;and this logic should work for the range of periods also.
Example :
we are executing query for the period 006/2006 (posting Period)
Last day of this period is 06/30/2006,
Currency rate would be as per 06/30/2006
And this currency rate should be same throughout the period 006/2006 in query
The example was for single period,but logic must be incorporated for the range of the periods.

Hi..
There is no corresponding source key figure in the InfoSource for the target key figureof the InfoCube.
a. A source key figure of the same type can be assigned to the target key figure
(for example, sales revenue instead of sales quantity revenue).
If the currencies of both of the key figures are the same, no currency
translation can take place.
If the currencies are different, a translation can take place either using a
currency translation type or by simply assigning a currency.
The following table provides an overview of possible combinations with different
currencies in the source and target key figures:
if Source key figure currency is fixed , Target key figure currency is variable then Currency translation (CT) No CT
if Source key figure currency is fixed , Target key figure currency is fixed then Currency translation (CT)   CT
if Source key figure currency is variable , Target key figure currency is fixed then Currency translation (CT)   CT
if Source key figure currency is variable , Target key figure currency is variable then Currency translation (CT) CT or assignment
b. If there is no corresponding source key figure of the same type, then you have
to fill the key figure for the data target from a routine.
If the target key figure has a fixed currency, no currency translation is
carried out. This means that if translation is required, you have to execute
it in the routine.
If the target key figure has a variable currency, you also have to assign
a variable source currency to the routine. Using the F4 help you can
select a currency from the variable currencies in the communication
structure. You have two options:
You can select a variable currency and assign it.
You select a currency translation type and a currency into which you
wish to translate (To currency).
The To currency is, by default, the target currency if it is included in the
communication structure.
Creating a Routine for Currency Translation:
If you want to translate currencies in the update even though the currency translation is not
available for one of the above reasons, you can create a routine. Choose Routine, set the
Unit Calculation in the Routine and choose Create Routine. In the routine editor you get
the additional return parameter UNIT, the value of which is used to determine the target
1. save the query and it under role
   see to it is in   : Restricted and calculated key figures --->   properties of k.f
2. exeute the query
3. the currency translation --> by target currency usd choose OK
conversion type : MEANTODAY Fixed target currency current date (MT)
4. Go back to the query definition by chossing chage query ( global definiton)
5. in the context menu for % share sales vouume of incoming orders, choose properties --> formula collision --> result form this formula choose OK
Note that -
your should alos set the currency translation in the properties for the two key figures sales voule EUR , choose properties ---> currency conversion key : fixed target currency , currrent date ( MT) --> target currency : American Dollar . choose   OK
<b>The translation key is a combination of different parameters that establish how the exchange rate for the translation is executed.
The parameters that determine the exchange rate are the source and the target currency, the exchange rate type and the time reference for the translation.</b>
The source currency is determined from the data record or dynamically from the master data of the specified InfoObject (currency attribute)
The target currency can either be fixed in the translation key or selected at the time of translation.
You can also use an InfoObject (currency attribute) to determine the target currency.
The exchange rate type distinguishes exchange rates that are valid in the same time frame next to each other, for example, the bid rate, ask rate or middle rate. The exchange rate types are stored and can be maintained in a central table (TCURV).
The time reference for the currency translation can be either fixed or variable
The fixed time reference can either be a fixed key date that is stored in the translation type, or be determined using the system date when executing the currency translation.
If the time reference is variable, then the point in time for the exchange rate determination comes from the value of a time characteristic (InfoObject). The reference can, for example, be the end or the start of a fiscal year or a calendar year, a period and a month or even to the exact day. It can also be determined using a customer-specific InfoObject (for example, trading day).
Currency translation in the BEx
When selecting a translation key with a fixed target currency     this currency will be added automatically to the query definition
Also, you can use translation keys selecting their target currency at the time of translation. These can be applied in two different ways:
Selection of a specific target currency in the query definition (1)
Entry by variable (2)
Dynamic translation keys require input from the InfoCube !
InfoObject value will be read during query execution
Examples:
dynamic time reference (p.eg. 0CALDAY)
      time characteristic
target currency determined by InfoObject (currency attribute)
     characteristic which contains currency in its attribute table
the corresponding InfoObject has to be part of the InfoCube
1.Define the currency attribute in the InfoObject maintenance
The currency attribute has to be a unit InfoObject of type currency
The unit InfoObject must be an attribute of the characteristic
The currency attribute should be filled in the master data table of the corresponding InfoObject (manual maintenance or upload via InfoSource)
2.Enter the InfoObject in the translation key maintenance
Only InfoObjects with a currency attribute can be used in translation keys (p.eg. 0COMP_CODE)
At the time of currency translation the value for the source currency / target currency is then derived for every record from the master data table of the specified InfoObject
All values for a query are translated ad hoc (after having executed the query) using a translation key
Depending on the translation key a fixed target currency will be used for translation or you will be able to select the target currency
The ad hoc currency translation offers only restricted functionality (selection of translation key and target currency) compared to the currency translation in the query definition
Do not forget to create your translation keys before starting your work in the Business Explorer Analyzer
Example:
You load the following record to your InfoCube:
Company Code:                1000
Amount in Source Currency:      500,-
Source Currency:                FRF
Target Currency:               ?
In the Update rules, you are now using a translation key which derives the target currency from the InfoObject 0COMP_CODE. During the Update Process the target currency will then be read for Company Code 1000 from the master date table of 0COMP_CODE.
With the currency translation in the Business Explorer, the source currency can currently only be determined from the data record.
Only translation keys with a fixed exchange rate type can be used in the BEx
Translation keys with a dynamic time reference (from an InfoObject) can only be used in the query definition. It is not possible to fill the InfoObject by a variable !
Translation keys getting their target currency from a currency attribute can only be selected in the query definition
When getting the dynamic reference from an InfoObject (p.eg. 0CALDAY) the currency translation will apply to each record read from the database. That means it will use the date in this record for the currency translation.
When using a variable you will restrict the output of your query to a certain amount of data. For example, you would translate all invoices of March 11 with the translation date March 11
This means, the requirement show me all invoices in my cube in group currency, conversion date: 14.07.2001 could not be solved by a variable input for 0CALDAY
I hope this would help...
with regards,
hari

Currency Conversion using RSW_CURRENCY_TRANSLATION

Hi all,
I have the following scenario:
We want to do currency conversion in the update rules between a cube A and a cube B using a start routine. Both cubes have exact the same structure. All key figures are of currency 0CURRENCY. In cube A all values are in EUR, meaning that 0CURRENCY is always 'EUR' for each record. We want to convert to a local currency (determined via "Company Code"), meaning that in the cube B the record should arrive with different key figure amounts and 0CURRENCY='LocalCurrencyAccordingToCompanyCode'.
We'd like to use a currency translation type, which is defined as follows:
Tab "Exchange Rate"
   --> Exchange Rate Type = EURX
   --> Dyn. Ex. Rate Determinatn (marked)
Tab "Source Curr."
   --> Source Curr. from Data Rec (marked)
Tab "Targ. Curr."
   --> InfoObject for Determining Tar. Currency = 0COMP_CODE
Tab "Time Ref."
   --> Variable Time Ref. (marked); Value set to 4 (= Beginning of period)
   --> Standard InfoObject (marked); Value set to '0FISCPER'
We have maintained EURX exchange rate for direction LC->EUR, meaning that in TCURR there are no entries for source currency 'EUR', but only for local currencies like GBP, USD, etc. How can we achieve, that the table is read "inverse" during currency conversion and that the conversion takes the inverse rate. Is it necessary to adjust the currency translation type and mark the "Inverse Ex.Rate" checkbox on the "Exchange Rate"?
Then, it is still unclear for me, how to exactly call the function module. I have tried in different ways, but mostly get a TCUR_CONFLICT exception. I also debugged the function module and it seems like he cannot determine the target currency correctly. But I think, I do not call the FM in the correct way. I have read various posts; the explanations on how to call the FM are not harmonized
Can you help me out?
Thanks to any answers in advance and kind regards,
Philipp

I found a solution. Indeed, we passed wrong parameters when calling the FM.

Triangulation in currency Conversion

Hi All,
Ive been happily using the currency conversion function module in the key figure routine in the transformation for billing docs.
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
      EXPORTING
        DATE             = SOURCE_FIELDS-/BIC/SST_UP_DT
        FOREIGN_AMOUNT   = SOURCE_FIELDS-/BIC/SSUBTOTA3
        FOREIGN_CURRENCY = SOURCE_FIELDS-DOC_CURRCY
        LOCAL_CURRENCY   = SOURCE_FIELDS-LOC_CURRCY
        RATE             = EX_RATE
        TYPE_OF_RATE     = 'M'
        READ_TCURR       = ' '
      IMPORTING
        LOCAL_AMOUNT     = VALUE
In our BW (7.0) system Exchange Rate Type M is maintained for all currencies to EUR only.
I have a new ERP system connection for Far East where doc currency = HKD, MYR, PHP etc
and Local currency = SGD
Requirement to convert doc currency (various) -> local currency SGD
Because our XC Rate Type M is only maintained to EUR it is not possible to do a direct doc curr -> loc curr conversion because the rates are not maintained to SGD.
My only solution is to triangulate the conversion i.e.
doc currency (e.g. HKD) -> EUR -> loc currency (SGD)
Has anyone any ideas as to how I would go about doing this?
I searched threads for info about triangulation but found nothing!
Hope help comes soon....

Hi Arun, thanks for message.
You mean fo rme to run the currency convesrion FM twice?
so run one: to convert to EUR
*this is part (1) to EURO
    CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
      EXPORTING
        DATE             = SOURCE_FIELDS-/BIC/SBILL_DAT
        FOREIGN_AMOUNT   = SOURCE_FIELDS-/BIC/SSUBTOTA3
        FOREIGN_CURRENCY = SOURCE_FIELDS-DOC_CURRCY
        LOCAL_CURRENCY   = 'EUR'
        RATE             = EX_RATE
        TYPE_OF_RATE     = I_F_RATETYPE
      READ_TCURR       = ''
      IMPORTING
        LOCAL_AMOUNT     = RESULT
      EXCEPTIONS
        NO_RATE_FOUND    = 4.
and then run two to convert to SGD
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
      EXPORTING
        DATE             = SOURCE_FIELDS-/BIC/SBILL_DAT
        FOREIGN_AMOUNT   = SOURCE_FIELDS-/BIC/SSUBTOTA3
        FOREIGN_CURRENCY = 'EUR'
        LOCAL_CURRENCY   = 'SGD'
        RATE             = EX_RATE
        TYPE_OF_RATE     = I_F_RATETYPE
      READ_TCURR       = ''
      IMPORTING
        LOCAL_AMOUNT     = RESULT
      EXCEPTIONS
        NO_RATE_FOUND    = 4.
I will try this and see what happens

Currency Conversation

Dear Friends,
CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER RULES?
cheers
Mohhan

Consider you InfoSource being connected 3 diff source systems having 3 diff currencies respectively.
This InfoSource updates your Cube..Doing it in update rules you just have to do conversion once.
(if you would have done it at transfer rule level then 3 times)
In special case, you can also run currency translation in user-defined routines in the transformation rules.
http://help.sap.com/saphelp_nw70/helpdata/en/ec/076f3b6c980c3be10000000a11402f/frameset.htm

Currency Conversion Type missing in BEx

I have created a new conversion translation type M1 based on Monthly Average exchange.
RSCUR definition for this conversion on the time ref tab to be a "variable time reference"- End of Period for
Standard Info Object Fiscal Period "0FISCPER".
Is this configuration the cause for placing a limiting restriction on the visability of this selection at runtime of query.
The following currency translation types are not available at the runtime of the query.
●      Translation types for which a variable is stored (variable time reference, source currency from variable, target currency from variable, and so on).
From BEx I am unable to select Currency Conversion (Convert to Currency USD) and Use of Currency Translation M1
Thank You ...... Dan

Andrey:
Once BEx query results are displayed in M/S excel ... the user navigates (right click) to (local) query properties:
Tab >> Currency Conversion >> select Convert to Currency will open option to determine Currency (USD) and Currency Translation (via drill down).
Those Currency conversion types configured with variable time reference on InfoObject 0FISCPER cannot re-determine
target currency values. Fixed Time reference conversion types can be selected through BEx.
I found a restriction/ limitation in the following thread.
http://help.sap.com/saphelp_nw70/helpdata/en/ec/076f3b6c980c3be10000000a11402f/frameset.htm
Restrictions:
The following currency translation types are not available at the runtime of the query.
●      Inactive translation types
●      Translation types for which a variable is stored (variable time reference, source currency from variable, target currency from variable, and so on)
●      Translation types in which an InfoObject is used for determining the source currency or target currency.
Are you aware of any way around this ??
Thank you ....... Dan

Currency Conversion at Query Level

Guys,
Can some one tell me step by step procedure to do Currency conversion from USD to Mexican PESO at query level in BI 7.0. I have read lot of threads but not clear in maintaining the Exchange rates and also in creating the variables.
Thank you,
Kumar

Hi Kumar ,,
You're able to convert the currency amount on the routine ...
Using this function :
CONVERT_TO_LOCAL_CURRENCY
Sample:
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
     EXPORTING
        DATE             = " current date.
        FOREIGN_AMOUNT   = " local currency amount (peso)
        FOREIGN_CURRENCY = " local currency
        LOCAL_CURRENCY   = 'USD'
     IMPORTING
        LOCAL_AMOUNT     = RESULT " result.
     EXCEPTIONS
        NO_RATE_FOUND    = 1
        OVERFLOW         = 2
        NO_FACTORS_FOUND = 3
        NO_SPREAD_FOUND = 4
        OTHERS           = 5.
To maintain the exchange rate, you can go to tcode: OB08
Hopefully it can help you a lot..
Regards,
Niel
thanks for the points you choose to assign.

Currency conversion via routine in transformation BI 7.0

Similar Messages

Maybe you are looking for