Error with Exchange rate type

Hello all,
While releasing the billing document to accounting, getting the error:
'An exchange rate type is not defined for country US'.
In customer master, have maintained Exchange rate as 'M'.
where do we maintain the exchange rate type for country.
Thanks
Gauravjit.

HI Gauravjit,
Try this:
SPRO-F5- General Settings-Currencies-Define Translation ratos for currency translaction
Reward if it helps
regards
Srini

Similar Messages

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

CKUC - Exchange Rate Type P

Dear All,
We are using CKUC Multilevel Unit Costing for doing costing simulation.
It is giving error "There is no exchange rate for exchange rate type P on 03.01.2012: USD -> INR".
It is understood that Exchange rate 'P' is not maintained in OB08.
But I would like to know under what instance system will try to use exchange rate type 'P'?
Regards
Ratna Palit

Dear All,
After further testing and analysis done , it is observed that there are material components in multi leve lunit costing BOM which do not have info record maintained in production system.
The valuation variant for multi level unit costing contains following sequence of priority for picking up material rate.
Priority Strategy Sequence
1. Price from Purchasing Info Record
2. Moving Average Price
3. Planned Price 1
4. Standard Price
Sub-Strategy Sequence with Purchasing Info Record Valuation -
Priority Strategy Sequence
1. Net Purchase Order Price
2. Net Quotation Price
Hence as system is not finding info record for above materials,
a. it is checking the sub sequence strategy for net purchase order price.
b. simultaneously for purchase order scenario - it is also checking for Exchange Rate type 'P'.
In this case there is neither exchange rate type 'P' maintained nor purchase order is maintained in production server.
Hence system is giving both errors "for Exchange rate type 'P' " and "for Valid Source of Supply".
In past whenever unit costing was run successfully in production server, info record was also available for applicable materials in BOM. Hence system did not give any error.
Thanks & Regards
Ratna
If our priority sub sequence remains as Net purchase order price, exchange rate type "P" has to be maintained.

How to change exchange rate type for specific pricing condition type

Hello every one,
I have a requirement for billing ie VF01.
currently all the exchange rate are being calculated with exchange rate type 'M' by default.
but now client want it should calculate exchange rate with type 'E' for two pricing condition type for all others it should calculate with type 'M'
Please any body can help me with the exit and code which i can use.
I have checked exits SDVFX008.
but how to change exchange rate with type 'E' only for two conditions.
as changing exchange rate at document header will change exchange rate for all condition type.

You need to assign KOMK-KURST = 'E', for those two condition types. If it had been item number specific, you could have used USEREXIT_PRICING_PREPARE_TKOMK(RV60AFZZ).
Do one thing, put a breakpoint on FM 'PRICING' and then do selective runtime analysis.
Check whether any user exit/BADI/ explicit enhancement are available when condition types are processed in a loop. If nothing is available, try implicit enhancement.
Link to refer for selective runtime analysis - Runtime Analysis for VOFM
Also try with VOFM requirements ( not sure whether changing KOMK-KURST is permissable in requirement as normally we only set sy-subrc values to suppress/allow condition types ). Don't forget to assign requirements against condition types in pricing procedure.

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 For MIRO

Hi, expert
My customer has a specific requirement. For AP, use exchange rate type B, for AR use exchange rate type G. The easist way is to set in the document type (Table T003), but this table is cross company code. Here only one company code need it.
So my proposal are following:
FI direct posting:
AR and AP exchange rate are substituted by a user exit. In the substitution, the field BKPF-KURSF should be release for substitution, change the table GB01
SD invoice posting:
Set Exchange rate type G in the customer master of sales area, then the AR is posted with exchange rate type G. The substitution in FI is not effective in SD invoice posting.
MM LIV posting:
During MIRO , the substitution in FI don't work here. and other User Exit not work.
Is there any other method to make sure the exchange rate type change to B in the MIRO?
Thanks!

Please check SAP Note : 518114

Exchange Rate type determination in PO

Dear all,
During purchase order creation for a foreign vendor, system looks into the exchange rate tables to determine the exchange
rate between the local currency and order currency (foreign currency).
During the rate processing system always takes the rate mainatined with exchange rate type "M".
We have a requirment where we want the system to look into the specfic exchange rate type for a company code.
For Eg, PO's created for the hungary company code, should look into the exchange rate maintained with exchange rate type HU01 which is mainatined in exchange rate tables and not from exchange rate type "M".
I searched all config elements on the MM side but could not find any. I also understand that we could set this using the invoice document type, but we need to have the po determined the right exchange rate type.
We are implementing SRM and the shopping cart or the PO created goes through the same logic , it finds the rate maintained in exchange rate type "M"only.
Kindly advise if we could set this config somehwere or could control through data.
Regard
Harish

Hi,
it is the sap std behaviour while creating the PO, picking of the exchange rate from the specified tables and from specified type.Seems you can not change.
Regards,

Exchange rate type P not getting picked up while executing KSUB-Plan Assess

Hi,
We have Exchange rate type "P" maintained in SPRO in Maintain versions for the Fiscal Year 2010, but even then when I execute KSUB, it posts with Exchange rate type M.
Has anyone faced this issue? We want it to pick up P and not M.
Regards,
SAPFICO

Hi, set it here IMG-Controlling-Cost Center Accounting-Planning-Basic Settings for Planning-Define versions-Maintain Settings of Version in Controlling Area then Setting for each f. year , double click on current f.year

Exchange rate type error

Hi,
I am trying to Purchase order PO so that time i am facing error as
Enter rate USD / INR rate type for 19.01.2011 in the system settings
Message no. SG105
Diagnosis
For the conversion of an amount into another currency, an entry is missing in the currency conversion table.
Procedure
Add the missing entry in the currency conversion table.
Execute function
You can then continue to process the commercial transaction
i have configured in OB08 and OBBS maintain the exchange rate type M for USD and INR.
but still i am facing error, please guide me to resolve this issue.
Thanks
Shital D

Hi,
I have checked with FI consultant Direct and Indirect Quo has maintaned,
please suggest me any other config is required to resolve this issue.
Thanks
Shital D

Exchange rate type for version - error message GP541 during confirmation

Hi FICO Experts,
I bumped into a problem during confirmation in CO15. (I would like to get the SFG by mvt 101 and consume the raw material by 261).
The error messase I get is:
Maintain the exchange rate type for version 000 in 2009
Message no. GP541
Diagnosis
You want to use plan version 000 with controlling area 1000 in fiscal year 2009.
You have not specified an exchange rate type for this plan version for fiscal year 2009. Since the update of all currencies in 2009 is active in the control indicators of the controlling area, currency conversions are possible and sometimes also needed.
It is therefore necessary to specify an exchange rate type for plan version 000 in year 2009.
System Response
The system will not accept your entry.
Procedure
1. Please maintain plan version 000 first using the function 'Change Plan Version', or
2. correct your typing error.
I'd like to ask you to please help to resolve this issue.
Thanks,
Csaba

go to Maintain Version at SPRO-Controlling-General Controlling-Organization->Maintan Version and do what ever it says. Provide Exchange rate type P or M would resolve your issue

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

Error while determ. loc. crcy: exchange rate type M date 01/26/2011 frm SGD

Hi,
There is an issue like after order is created,while creating invoice(third party order) after saving there is message as its saved.
But when trying to go with either vf02 or vf03 there is an update termination as 'Error while determ. loc. crcy: exchange rate type M date 01/26/2011 from SGD to'...so any suggestions on this?

HI Srilatha,
Go to T.code OB08 there position the exange rate Ex: M in you case and valid from 01.01.2011 then give currency if it is INR give 1INR X 1 INR = 1 give according to you document currecy.
Thanks
Vinayak

ERROR in MIRO : An exchange rate type is not defined for country IN

Experts:
When I try to enter the invoice received from the vendor, I am getting the following message.
An exchange rate type is not defined for country IN
Message no. FF802
Can anyone provide me a solution for this?
Thanks,
Vijai

This is the explanation given in note 974619 for the above error message
Summary
Symptom
When you post an FI document, the system issues error message FF 801 or FF 802.
Other terms
Plants abroad, FF 801, FF802
Reason and Prerequisites
You use the 'Plants abroad' function.
See Note 882132 for more information about this.
Solution
If the 'Plants abroad' function is active, additional fields appear when you maintain the country global parameters (transaction OY01, table T005):
- Country currency       (Field WAERS)
- Exchange rate type     (Field KURST)
- Net discount base      (Field XSKFN)
- Net tax base           (Field XMWSN)
You must maintain the fields 'Country currency' and 'Exchange rate type'.
Otherwise, the system issues error message FF 801 or FF 802.
thanks
G. Lakshmipathi

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

Exchange rate type P is replaced with M

Hi,
We are using CATS for time booking and the process is as follows:
1) CAT2 -> Hours booked.. Lets assume: 9 HRs
2) CATS_APPR_LITE - > Time sheet approval -> Approved 9 Hrs
3) CAT9 -> CATS data transfer to cost object(PM order) -> During this transaction, system does calculate the amount needs to be tranferred based on price maintained in KP26 and hours booked. Lets say KP26 price is $100. That means controlling document will be generated for amount $900.
Note - As per system configuration, exchange rate type will always be P whenever CATS posting will happen and controlling document gets generated. That means, currency conversion will take place based on the exchange rates maintained for type P.
So as per business requirement, we have done an enhancement to the existing CATS process:
Price is manually determined at the time of CAT2 and same will be considered till the controlling document is generated. So, no price determination during CAT9. Therefore the strategy says it is a manual determiination of price and the Exchange rate type is determined as "M" and thats an issue because we do want to pass manual price but we want Exchange rate type as "P" as well.
Is there any way out or settings availabe in SAP or any user exit or an enhancement to achieve this functionality?
Thanks,
Aby

Hi Aby,
I believe these notes contain good information for this case:
1073979 (which I think is already in your system and therefore this behavior).
and
691613 (which explains the strategies)
Also, please check the entry you have defined in the transaction OKEV.
There, the system will make the translation depending on the
exchange rate defined.
I hope this helps.
Regards,
Lucas

Error with Exchange rate type

Similar Messages

Maybe you are looking for