Conversion factor missing for Exchange rate type BE

Dear Friends,
I am getting error while doing GR as " Conversion factor missing for exchange rate type INR TO USD"
waiting for your advice.
Thanks

Hi
In OBBS maintain the translation ratios between USD & INR and in OB08 enter the exchange rate for this pair of currencies
Anil

Similar Messages

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

Translation date for exchange rate type 'M'

Hello friends,
How do I change the translation date for an exchange rate type, for a particular company code?
My client wants the translation date for the exchange rate type 'M' to be document date instead of posting date. It is required as per Romanian Law of land.
Regards,
Mike

Mike,
I assumed your question is for an additional local currency for a company code (this can be changed in OB22). For the first local currency, the translation date type in OB22 is always set to 3 (Translation Date) and cannot be changed (hence, greyed out). Following that, in accounting entry transactions (for example FB01), you will see a field (Translation Date) where you can specify a date for which you want the system to fetch exch. rate from the exch. rate table. In your situation, you will have to enter 'document date' there.
PS: The reply above by Ravi applies only to tax items' translation, not for all items. He is basically talking about the indicator that you see in OBY6.

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

ROE for exchange rate type M_CN

Hello,
The exchange rate type M_CN has been defined to capture the "Bank of china ROE" and the customer master data is also updated with M_CN.
However, the accounting posting consider the ROE for Normal posting rate M.
What could be wrong?
Regards,
Swapnali..

Hello ,
sorry....Please read the above as the exchange rate is picked from the payer master record. so if it is different payer then priority is payer master
secondly the exchnage rate by default is M . you have to click the get exchange rate in sales order to get the correct rate for the M_CN each time for the order
you could also maybe add a user exit to redetermien the exchange rate each time a sales order is created
Thanks
akasha

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,

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

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

Exchange Rate type B in invoice

Hi Experts
I have configured for the exchange rate type to pick at the invoice for billing date. The customer master has exchange rate type as B. The sale order also has the exchange rate B from OB08. But when I create the invoice it shows as customer exchange rate as B but picks the value for exchange rate type M in header level. At item level it is copying from sale order exchange rate.
Please let me know if I have missed any configuration so that the exchange rate B is picked in invoice

Have a look at the following note:-
Note 22781 - Exchange rate in accounting, exchange rate type
G. Lakshmipathi

Exchange Rate Type M in MIRO

Hi
We have some issue in exchange rate . When i am doing MIRO this time i have geeting error enter rate / USD rate type M for 04.12.2009 in system setting.we have process different types Invoices with different currency in Miro to get this error message.
After i m exit in this MIRO screen. Than again enter MIRO T. COde and enter PO number this time i have no geeting any error.
We have check all the seeting in OB08 all are perfect. Colud please help me on this issue.
Thanks in advance
Why this error is geeting in first time.

Srikanth,
Yes, exactly it is the rate upon 28.01.2011that should be relevant for the actual document.
Exchange rate has not entered manually in document header by interface nor by user. Interface only feed document amount and currency i.e. no rates.
Standard quotation in table TCURN for GBP=>USD is:"1" Direct quotation valid from 01.01.1800
Standard quotation in table TCURN for "Blank"=>GBP is:"2" Indirect quotation valid from 01.01.1800
Translation ratio for currency pair GBP => USD for exch rate type M is 1:1, valid from 01.01.1800, alt ERT=blank.
Translation ratio for currency pair USD=> GBP for exch rate type M is 1:1, valid from 01.01.1800, alt ERT=blank.
Translation ratio for currency pair USD=> GBP for exch rate type M is 1:1, valid from 31.10.2010, alt ERT=blank.
Maintained exchange rate valid for the period 31.12.2010 - 30.01.2011 for exchange rate type M is 1 USD= 0.64114 GBP
Amounts in document are
Doc. Curr. Amount= 187.44 GBP
LC2 Amount= 281.16 USD
Rate used for LC2 Amount in document equals 1 USD = 0.6667 GBP
Correct LC2 Amount with rate 1 USD= 0.64114 GBP should be 292,35 USD.
Kind regards,
Linda

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.

Selling Exchange rate type is not picking while billing

Hi,
We have maintained Exchange rate type B for selling and the same was assigned in customer master as well as the RV document type. While raising sale order system is picking the B rate from OB08 table, but at the time of billing system is taking the M rate. Where do i set a control to pickup only B rate? Can anybody help me on this.
govind.

Hi,
Ideally at the time of billing, exchange rate type is picked up from the document type (RV in your case). However if the rate is picked up for standard exchange rate type, check if there is user exit being called for exchange rate type.
Thanks,
Aman

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 type settings

Hello,
In same client one company code use reference currency as local currency (XYZ) for exchange rate type u2018Mu2019. Exchange rates are maintained on daily base for the exchange rate type.
New company code with different local currency would like to maintain exchange rate on monthly.
Both company codes use same document types in FI and other modules.
As per my understanding it is not possible to have to different exchange rate settings for same exchange rate type u2018Mu2019 in one client.
In case if we have to use different exchange rate type for new company code what are the things to be considered or is there any alternate way please advise.
Thanks!
Raju

Hi,
    You will have to create a new exchange rate type.
Throughout SAP rate M will be used for actual postings unless a different rate type is specified.
You can do this in:-
                  a) Document type
                  b) F110 - rate to be used can be specified
                  c) Customer Master Sales org data (for use in SD).
Doing a complete duplicate set of document types is unrealistic.You need to identify where the FX transactions are and create Document types only where needed.You will also need a new FX valuation type that uses the new rate.
When faced with this situation i only create 1 additional document type, to be used for Inbound invoices.This plus b) & c) for my companies covers 90+% of the FX postings.
Kind regards

Exchange Rate Type M getting updated automatically next day

Hi ,
We upload rate through t.code TBDM for MTRE exchange rate type but very next system turn up same result for exchange rate type M
For example
Suppose today 09.09.2011 i upload rate only for MTRE exchange rate type for following currency
AED                 EUR           MTRE04092011                   5.26447
ANG                 EUR           MTRE04092011                   2.52369
ARS                 EUR           MTRE04092011                   6.01392
AUD                 EUR            MTRE04092011                   1.33905
latter on if check in TCURR table or OB08 tcode i will get below entry
ExRt From To Valid from Exch. Rate Ratio Ratio
M    AED EUR 05.09.2011   /5,26447    0     0
M    ANG EUR 05.09.2011   /2,52369    0     0
M    ARS EUR 05.09.2011   /6,01392    0     0
M    AUD EUR 05.09.2011   /1,33905    0     0
MTRE AED EUR 04.09.2011   /5,26447    1     1
MTRE ANG EUR 04.09.2011   /2,52369    1     1
MTRE ARS EUR 04.09.2011   /6,01392    1     1
MTRE AUD EUR 04.09.2011   /1,33905    1     1
my question how M is getting update.
Regards
Prakash Sharma

Hi
Here you need to concentrate on Direct or indirect quotation
If you are using EUR to SEK (LC) - use direct quotation as 8.8307 1:1 relation
If you are using SEK to EUR - use indirect quotaion as 0.1132 1:1 relation
Pls let me know if you required further help
Reg
Vishnu

Conversion factor missing for Exchange rate type BE

Similar Messages

Maybe you are looking for