ECM: Currency Exchange Rate - Rate Type in TCURR

Does anyone know if the Rate Type that ECM uses to do currency conversions in ECM can be changed?
Standard ECM functionality uses rate type "M" from TCURR, my client would like to use rate type "P" from table TCURR.
Thanks
Tony

The exchange rate type 'M' is hardcoded in the function call 'HR_ECM_CONVERT_CURRENCY'. I don't think there is an option to change the rate type without modifying SAP code.
function hr_ecm_convert_currency.
*"*"Local interface:
*" IMPORTING
*"     VALUE(OLD_AMOUNT) TYPE P
*"     REFERENCE(OLD_CURRE) TYPE WAERS
*"     REFERENCE(NEW_CURRE) TYPE WAERS
*"     REFERENCE(CONVERSION_DATE) TYPE DATUM
*"     REFERENCE(MESSAGE_HANDLER) TYPE REF TO IF_HRPA_MESSAGE_HANDLER
*" EXPORTING
*"     VALUE(NEW_AMOUNT) TYPE P
*"     REFERENCE(IS_OK) TYPE BOOLE_D
data: char_date(10) type c.
is_ok = true.
clear new_amount.
check not old_amount is initial.
if old_curre = new_curre.
    new_amount = old_amount.
    exit.
endif.
call function 'CONVERT_TO_LOCAL_CURRENCY'
    exporting
      date             = conversion_date
      foreign_amount   = old_amount
      foreign_currency = old_curre
      local_currency   = new_curre
      type_of_rate     = 'M' "<---- hardcoded here
    importing
      local_amount     = new_amount
    exceptions
      no_rate_found    = 1
      overflow         = 2
      no_factors_found = 3
      no_spread_found = 4
      others           = 5.
if sy-subrc <> 0.
    is_ok = false.
    write conversion_date to char_date.
    call function 'HR_ECM_ADD_MESSAGE'
      exporting
        message_handler = message_handler
        msgty           = error_msg
        msgid           = hrecm00service
        msgno           = '006'
        msgv1           = old_curre
        msgv2           = new_curre
        msgv3           = char_date.
    exit.
endif.
endfunction.
~Suresh

Similar Messages

Replication of Currency exchange rate types

Hi,
I had changed the currency exchange (eg:USD to INR) rate types in R/3 system.now I need to replicate from R/3 to SRM.
please let's know how to replicate the Curreny exchange rate types from R/3 to SRM.
Kindly suggest me.
Regards,
sss

hi
eevry day you might run this job right ?
report se38 BBP_GET_EXRATE - this bring every day exchange rate update from ECC to SRM
muthu

Group Currency Exchange rate type.

Hi
We wanted to post a foreign currency document, with a specific Exchange rate, that is specified in the Document type.
Doument Currency is getting converted into Local Currency (Company code currency) based on the exchange rate type specifed in the Document type used for posting.
But, the Group Currency is getting converted from Document currency based on the Exchange rate type : "M" but based on the Exchange rate type specified in the Document type.
Is there any way, apart from specifying Exchange rate type in Parallel Currencies.
We wanted the conversion of Both Local (Company code) & Group currencies be converted based on the Exchange rate type specified in the document type, for some specific postings.
Following is our Scenario :
Co.Code Cur - EUR
Doc.Cur          GBP
Grp Cur           USD
Document type : XY -- Exchange rate type "1111" specified in the document type.
Now when a document is posted with Document type "XY" in Document Cur : GBP.
Both Local & Grp currency to be converted based on the Exchange rate type " 1111".
Thanks
Kalyan

Hello Kaylan,
I will try to explain the system behavior, regarding to the exchange
rate question, "M" is standard exchange rate type used in R/3 so it's
not possible to change this default setting. However you can assign the
exchange rate type to each FI document type at transaction OBA7. The
exchange rate type assigned here applies to both online/batch postings.
Therefore you can assign a different exchange rate type to the document
types, but not per company code. The exchange rate that you customize at
document type level is validfor the first local currency. However, for
parallel currencies, the system will always use the exchange rate type
defined in transaction OB22. Please, check your customizing there to
check your changes.
If you want to use exchange rate type B, for example, instead of M, in
customizing you have to give Alt Ex.Type as B against M. So that it will
take B rate whenever M is applicable. If you want this B rate to be
applicable for specific document types then you can do the same at
document type definition itself. Otherwise you can do the same at
payment program level/ Revaluation. These are the only places where
exchange type comes into picture.
See also the following attached OSS notes notes for details:
     335608 Trnsln of 2nd and 3rd lcl crcy fm 1st lcl/trns crcy
     526623 Different treatment of local and parallel currency in ML
     547946 FAQ Interface: Currency translation, rounding, field status
     518114 FAQ: Goods movements in foreign currency
regards
Ray

ECM: Global Compensation - Currency Exchange Rate

Has anyone implemented ECM for multiple countries? If so, what currency exchange rate type did you use?
Standard SAP uses exchange rate type 'M'. I'm aware that this is hard coded but my client would like to use rate type 'P'.
I would like to know if anyone else has run into this issue and what other clients have done to resolve it.
Thanks
Tony

You might want to check the OSS Note# 901896 & see if that can be of any help..
~Suresh

Error while determ. loc. crcy: exchange rate type M

Hi ALL,
after posting goods issue using VL02N i am getting popop
with 'update termination'
In log it is showing error as 'M2 815: Error while determ. loc. crcy: exchange rate type M'
can any one solve my problem
thanks
vinod

Hello Vinod,
Plz check in the table TCURR if an entry is maintained for exchange rate type M. (TCURR-KURST = 'M' & TCURR-TCURR = 'loc. crcy.')
I think the error is b'coz system cannot find an entry in this table & hence cannot carry out the locl. crcy. conversion.
BR,
Suhas

Currency conversion with the wrong exchange rate type

Hi,
I need a currency conversion in my bex query. I have defined a currency translation key with a assignment to the exchange rate type "M".
When I check the results in the query it works with exchange rate type "EURX".
Exchange rates are in the TCURR.
Can anyone help me.
Thanks in advance
Jürgen

Hello,
We just had the same issue, and in checking the Currencies: Translation Ratios in transaction OBBS, I noticed that the currency translation key in question was set up with an entry of "EURX" in the "Alt. ERT" column.
I copied the line and created a new entry with a "Valid From" date of the current month, but without the "EURX" Alt. ERT alternate and that seemed to solve it.
Anything entered with a date after the new Valid From date would use the manually entered exchange rate, while anything with a prior date continued to use the EURX rate.
It appears to me that the "Alt. ERT" functions more as an override than an alternate, so if you want the system to actually use the "M" rate, I believe you have to ensure there is nothing in the "Alt. ERT" column.
I hope this helps.
Blaine

HOw to see currency pairs in Exchange rate type

Hi,
Can anyone tell me how to see currency pairs in an exchange rate type?
Thanks

Hi,
I am not sure this is a right solution. But I have some inputs on your requirements:
1. For traveller cheques you may create a new payment method and do the required configuration for automatic payment program. Don't generate any payment medium while running APP.
2. For currency notes (cash payment) I am not sure how it works. But probably it is possible by creating an account (account ID) for a particular house bank and use that (house bank & account id) for making payment.
Per my knowledge we have never used payment method cash (currency notes) in APP. But logically it would work by create a new payment method and doing the required config for APP.
Please update if you found a better way to do this.
thanks & regards,
Kumar

Exchange rate type M not picked in FB60 foreign currency entry

Hi
My local currency is   USD. I   have defined exchange rate for   ' USD and EUR   '    for exchange     type M and type EURX.
In FB60, system picks the exchange rate defined for exc. type EURX,   but   I   want it to pick exch. type M.
Also i   have set   exch type M in docu type KR.   Still it does not pick   exc type M.
Pl advise
Thanks
kamala

I am thinking that most likely you have specified EURX as Alt. ERT (alternate exchange rate type) for exchange rate type M for the currency pair USD:EUR in IMG node 'Define Translation Ratios for Currency Translation" (T Code OBBS). Remove it and retest FB60; it should pick the M rate.

Alternate Exchange Rate Type Not Picked while converting from Document Currency to Group Currency

Hello Gurus,
We have setup an alternate Exchange Rate type MNB for rate M for the postings happening in Hungary. Local currency is HUF. Group currency is USD.
If the document currency is, lets say, EUR, latest MNB rate is correctly picked up (EUR to HUF) and postings are correctly converted into local currency (HUF).
Although, for the same document, when a group currency is being calculated (EUR to USD), exchange rate type M is being picked up. Same happens if document currency is HUF. Even then, the conversion is based on exchange rate type M.
Is this a normal SAP behavior? How to prevent/correct this? This is also throwing off balances when we check in FAGLB03 or BSEG values in local and group currencies. In OB22, we have local currency1 and local currency 2 setup with exchange rate type M and we may not want to make any changes there as it is setup at global level.
Do we need to run any valuations after the fact? if so, how?
Thank you for your inputs in advance.
Regards,
Sagar

Hi,
You mentioned that "in OB22, we have local currency1 and local currency 2 setup with exchange rate type M". Then, I'm wondering how MNB is picked up for the first local curr. conversion to HUF? It should be 'M' instead. There must be some settings in your instance for such behavior. Can you check that?
Actually, Group Curr. conversion happens with the rate defined for 2nd Loc.Curr.in OB22 which is 'M' in your case. Therefore, all the transactions are converted with M instead of MNB.
Since you can't change OB22 per global co.policy, the exch.rate defined in OBA7 will overrule OB22. However, you've to make sure it's set up for all doc.types which are affected and posted in different curr. than HUF.
As a workaround, another thought would be to maintain the same conversion rate for both exch.rate types MNB & M, for eg. HUF > USD rate is the same both exch.rate type MNB & M. This way, you ensure all transactions are posted with correct exch.rate irrespective of whatever rate type is used.
From business, & global org. perspective, I'm sure they are sending the 'M' exch.rates to all their sister concerns monthly, so they would like to consolidate results as per standard rate in their system. Then, why ,as a local company, would you like to fiddle with standard process? It's a management decision, please run them through again before going ahead.
Thanks,
Nirav

Exchange rate type - Reference Currency

Dear all,
Below is my case,
I have maintain a reference currency (USD) for exchange rate type M.
Therefore, the system can calculate the exchange rate e.g. from (EUR) to (AUD) through (USD).
However, what if, there are some pair of currencies in type M that I want to maintain their rate directly?
E.g. (EUR) to (JYP) in type M, not through (USD)
I have tried the configuration. System tells "For exchange rate type M, only rates with to-currency USD are relevant".
Could any one suggest me what should I do? And what will be the impact?
Regards,
Yin

I have the same requirement for RON (Romanian), vs. other triangulation (Ref = USD) for other countries. What did you finally do?
Thanks,
- Tim

Exchange rate types with referency currencies in BW currency translations

Hello Guru's:
Will BW currency translation keys utilize 'reference currency' functionality on exchange rate types? I want to translate between two currencies (CNY to HKD) that don't have a direct rate, but both have rates for USD.
I have:
- exchange rate type BU10 defined with USD as reference currency
- exchange rates for BU10 with relevant validity dates entered from CNY to USD and from HKD to USD.
- exchange rate factors for BU10 relevant validity dates entered for CNY to USD, HKD to USD, USD to CNY, and USD to HKD.
- a currency translation key defined taking source currency from transactional data (0CURKEY_LC), exchange rate type from a variable, target currency from a variable, and time reference as end of 0FISCPER.
The translation from CNY and HKD to USD works, as does translation from USD to either HKD or CNY, but not CNY to HKD or vise versa. So I wonder whether BW currency translation keys can even use the reference currency concept. Or maybe there are constraints on translation key configuration that must be observed to make them work for this situation.
Kind regards,
Aron

I solve it after using RSRT to debug the currency translation. The must be an additional entry in TCURF for the source and target currencies, not just for the source currency to reference currency and reference currency to the target currency. In my example from the original post, an entry from CNY to HKD is required.
Edited by: Aron Weaver on Oct 21, 2010 11:15 PM

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

Diffrent Exchange rate type for 1st Local Currency

Hello,
I have following problem:
E.g.
One company code in Germany having Local Currency as EUR and Another Company Code in France having Same Local Currency as EUR.
If i am posting transaction say on 12/09/2008 in USD for both company code and Exchange rate in Two Countries are as follows:
Germany -EUR to USD -1.25 on -12/09/2008 EXRTTY: M
France -EUR to USD -1.50 on -12/09/2008 EXRTTY: M
By default system picks up "M" exhchange Rate Type [EXRTTY]. And we cannot change exchange rate type for Currency "10" Local Currency.
Please help me how take care of such situation.
Regards,
Manish

Hi,
No i want system to pick diffrent exchange rate so i want to change exchange rate type for 1st Local Currency.
But that area is greyed out. Is there any system setting where i can maintain diffrent Exchange rate type for 1st Local Currency instead of "M". or is there any other way out that system will pick up diffrent exchange rate.
Problem is that two entities are operating in different market having same local currency but conversion rate for Foreign currency will be diffrent e.g. Local Currency EUR Exchange rate between EUR -USD in France 1.20 and Exchange rate between EUR-USD in Germany 1.25.
Is there any wayout to deal with such situation.
Please suggest.
Regards,
Manish

Utilizing different exchange rate type for same currency combination

Hello Gurus,
I wanted to get your opinion/experience in handling the following scenario.
We have company codes in different countries operating using different local currencies. There is alternate exchange rate type EURX defined for Exchange rate type M for many currency combinations due to business requirements. One country with local currency EUR is utilizing EURX SEK - EUR exchange rate combination.
Other country with local currency HUF is making use of exchange rate type MNB as an alternate exchange rate. In one of its transaction, where VAT is being calculated on its foreign transaction, HUF company is trying to seek rate of MNB SEK- EUR where country currency is SEK and document currency is EUR.
But since on the 'translation ratios for currency translation' table EURX being the alternate currency for that particular combination, even when we set MNB SEK EUR exchange rate, the system is obviously picks up EURX rate.
Has anyone come across similar scenario where different countries trying to get different exchange rate types for the same combination of currency? and If so, how would that be possibly handled through config or using something custom?
Thanks all for your replies in advance.
Regards,
Sagar K.

Hi Sagar,
In tcode OBBS, if Alt.exchange rate is used for any currency pair, then that rate is used ( EURX in this case).
All countries in EMU region uses EURX ( which is mostly fixed after introduction of EUR).
If the company is in different countries in Europe, then mostly EUR is used as Alt. exchange rate. which uses EUR as reference currency.
Ther is no country specific settings in std. sap for a currency pair.
Cheers,

Default Exchange rate type at document type level for parallel currencies

Hi,
I have a scenario wherein 2 parallel currencies have been maintained (Grp & index based) against a Co Code and have maintained a default exchange type (Z2) in the Document type settings (OBA7).
But when I want to post a foreign currency document, system picks Z2 rates for Co Code currency conversion and not for Grp & index based. In fact it picks M rate for these addtional currencies.
I know that for parallel currencies, the system will always use the exchange rate type defined in transaction OB22 ( "M" rate) which is at Co Code level but I want default exchange rate type Z2 to be picked at Document Type level for all the parallel currencies.
Please suggest how to archive this.
Thanks,
Sam

Dear Sam,
The exchange rate type defined in the FI document type (-> field
exchange rate type in transaction OBA7) is only used for the currency
translation from transaction/document currency into first local
currency, not for the currency translation into second local (group)
currency or for the currency translation into third local currency.
The exchange rate types for the currency translation into second
local (group) currency and third local currency are defined in
transaction OB22.
Unfortunately there is no option to change the exchange rate of 2nd or
3rd local currency in our posting transactions. The design doesn't
regard that requirement. But you have the chance to adjust the parallel
currencies in OB22 or to change the amounts manually.
I hope this helps.
Mauri

ECM: Currency Exchange Rate - Rate Type in TCURR

Similar Messages

Maybe you are looking for