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

Similar Messages

  • New Exchange Rate type settings

    Hi gurus,
    I have created a new exchange rate type for imports i.e. I and for exports i.e. E.
    I have maintained translation ratios for exchange rate types.
    I have maintained the exchange rates.
    I have maintained exchange rate type in company code settings at tax on goods movement>India-> basic settings-->maintain company code settings.
    After the above settings, while i am creating an import PO the exchange rate is not picking up from I.
    Is there any other settings.

    Dear,
    It will pick from the EURX only. not from your code. For this we have OSS notes also. That's only for MM postings.
    Regards,
    Dharma Rao. Yekula.
    Edited by: Dharma Rao. Yekula on May 8, 2009 9:02 AM

  • 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

  • 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 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

  • Exchange Rate Type not working during plan assessment in T Code KSUB

    Hello Experts
    We had different exchange rate types created for different plan versions. We had Exchange Rate Type Z1 for Plan Version 01.
    We had maintained the same in Planning settings for the fiscal year 2011.
    We had created a new plan assessment cycle with version 1.
    Now when we execute assessment cycle it is not using the exchange rate from 01/01/2011. Instead it is selecting the rate from 01/01/2010.
    Is there something wrong when we copied fiscal year 2011 from 2010 for version 01.
    Request your inputs and help on this.
    Thanks
    Satya Alapati

    Hi Ajay
    Thanks for the information.
    We had not maintained the value date for any of our versions since we keep changing the rates for every period and wish to have the system pick the latest rate for the period.
    It has been the case in earlier years also.
    Thanks
    Satya

  • Exchange rate type not defined for country

    Hi All,
    I have noticed an error message during testing of postings using tax codes. The error message nbr is FF802 (Exchange rate type is not defined for country XX). When we are testing postings on accounts for which tax code is ignored (not relevant) it is ok. Could you please let me know where exactly we have settings and how it is related to the tax codes ? I have never seen that connection previously.
    Thanks,
    Points will be rewarded afterwards.
    Tomasz

    Hi Tomasz,
    The exchange rate types are defined at country level in General Settings and the company codes with that country can access that. Normally the exchange rate types are defined as M, P, B and G. M is for average rate and is used in FI,  while P is for planning in CO.
    Regd
    Bharat

  • 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

  • Implications of change of Exchange Rate Type from P to M in Version in CO

    Hi SAP Experts,
    We have a requirement to change the exchange rate type in Versions. In fact, exchange rate type P has been configured in Version 0. This version is being used in Costing Variant PPC1. Price updations are being made with this costing variant. Costing Variant PPC2 is being used for internal evaluations. No price updations have been done using this costing variant.
    Client wants exchange rate type M in a new version to use in costing variant PPC2. I have created a new version X and assigned exchange rate type M in new version X. I have assigned the same version in Receiver version of Profitability Analysis and Version for indicators actual.allocations in Orders/Projects tab in T-code OKEQ. In Settings for Operating Concern, I have assigned currency type "Operating Concern currency" and exchange rate type M. Cost center activity price planning (KP26) has been done with new version X for all the cost centers.
    My question is "Will the above changes affect any Plan or Actual values of other versions existed in the system ?"
    Please let me know will there any affect on already planned data in the system with any version.
    Thanks in advance.
    Best Regards,
    K.S.K

    I don't think it's going to impact other versions but you may need to do simple test for other versions. One more thing is versions are controlling area specific and the M or P rates will be applied based on value date you setup in OKEQ configuration.
    You don't need to assign the version for  'Version for ind.act.alloc.'  indicator until unless you use WBS for project planning. By default it will be assigned to zero version.
    Thanks
    BR

  • Exchange Rate Type per Company Code

    HI Experts,
    In our system the conversion rates for EURX are maintained since there are several European companies working with the system.
    Now we would like to use the same SAP-system for companies in China & Taiwan. In both countries there is an individual "official" exchange rate which does not equal the exchange rates stated from the German banks and thus fed into the system.
    Is there any possibility to connect a company (code) with one particular exchange rate type? Since we are dealing with countries outside of the EU.
    Thanks in Advance
    Siva

    Hi,
    as you may have recognized, the assignment cannot be made on company code (or country) level, but only on currency level. In particular, this is table TCURF.
    When (almost) all possible currency combinations (from-to) are redirected to rate type EURX, then this looks like standard SAP delivery settings that you can freely change according to your needs.
    If you are not familiar with TCURF maintenance, however, you should be very careful here and test every change before importing it to the productive environment.
    The basic idea that I have always followed for the same or similar requirements is that local rules for a particular rate type are always control the rates to be applied when converting from any foreign currency to the currency of the particular country.
    If you are a China company and your local company code currency (curr.type 10) is CNY, then you have to make the following changes to table TCURF:
    First, find out all the foreign (non-CNY) currencies that you are dealing with. This may include EUR, USD, and any other currency of the world.
    Then, determine (or create) a new exchange rate type in table TCURV. This should be the rate type for your "own" rates. Let's name it rate type "L" (for Local rates). Note: you can use the standard M rate type as well, but it is more transparent if you define a separate one.
    Then have a look into table TCURF and find the entries as follows:
    Rate type: M
    From-currency: all that you are using in your business (all non-CNY that you use)
    To-Currency: CNY
    Valid-from: find the recent entry for each combination
    With all of these entries displayed, you will find that the alternate exchange rate type field (ABWCT) in these entries is set to EURX.
    Now you want to create a new TCURF entry as follows:
    Rate type: M
    From: the same foreign currencies as above
    To: CNY
    Valid-from: a newer date than the last current entry
    Alternate exchange rate type: L (your new rate type) - in case you want to use just M, then leave ABWCT empty.
    If you are using the L type (which I recommend), then you have to add 2 new entries to TCURF for each foreign currency:
    1.
    Rate type:  L
    From: foreign curr
    To: CNY
    Valid-from: 1.1.1800 (yes!)
    Ratio from and to: as you want, it should be the same as in the corresponding M entry, usually 1:1, but it depends
    Alternate exchange rate type: leave it blank.
    2.
    Rate type:  L
    From: CNY
    To: foreign curr.
    Valid-from: 1.1.1800 (yes!)
    Ratio from and to: as you want, it should be the same as in the corresponding M entry, usually 1:1, but it depends
    Alternate exchange rate type: leave it blank.
    Finally, in OB08, you have to maintain rates like
    type L,  foreign curr to CNY
    You are done
    What is happening is the following (example you post a document in USD in your China company code)
    Doc.currency USD --> must be converted to your local currency CNY
    First, the system looks the current ratios for the M entry:
    M, USD to CNY, valid from: recent, 1:1 and ABWCT = L !!!! (the entry you have added before)
    Then it checks the ratios for L:
    L, USD to CNY, valid from 1.1.1800, 1:1, ABWCT = blank
    Based on TCURF, the system will look for the current rate entered under rate type L, your local rate )
    Now what if a USD-based company has to post something in CNY? No changes there as the TCURF settings were not touched. They should look like this:
    M  CNY to USD, alt.exch.rate type EURX (or blank)
    If it is EURX, then the rates enterd under EURX rate type (once USd to EUR and then CNY toi EUR) are read and the cross-rate CNY to USD is calculated.
    If it is blank, then the rate entered under rate type M is used.
    In both cases, no change to your current process.
    It works similar if the company code is EUR based.
    The main idea is: redirect all M entries in TCURF where <anycurr> to CNY to the new rate type L, but leave all other TCURF entries untouched. Direction <any> to CNY are only relevant for the China company code, the rest of the world does not care about that conversion. They might be interested in conversions like CNY to <any>, like in the above example, CNY to USD, or CNY to EUR, but that could be their German or ECB rate, you do not have to care about.
    <removed_by_moderator>
    Csaba

  • Exchange rate type in BW

    Hi,
    I have an issue on Exchange rate type in BW.
    A new exchange rate type was created in R3, now I want to use the same in BW. For this, I have done the Global settings in BW on R3 source system and updated the exchange rate.
    After this, I could able to see the new exchange rate in Exchange rate type selection, but I could not able to see the newly updated exchage rate in T-code RRC1(F4 help). In this F4 I can see all other exchange type except this newly updated one.
    Kindly suggest.
    Thanks
    Ravi

    hI
    Replicate the entire source system
    Rigt click on source system  replicate meta data  then
    search it
    Cheers
    Ogeti

  • 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

  • Use an alternative Exchange Rate Type for activity actual price

    Dear All,
    I try to use an alternative Exchange Rate (not M)  in controlling area version "0", I need to use a custom currency exchange rate like in planned price (here I create a new planned version with exchange rate "N").
    I find same notes and it seems that standard Sap use only Exchange Rate "M" for actual price but I notice that for example in transaction KB21N (activity allocation) system shows in additional info exchange rate "N" (input in version "0").
    Is not possibile to use other Exchange Rate for actual price, activity allocation, for confirmed activity in production order?
    Controlling area has currency type 30 (group currency EUR), this company has MXN.
    Thanks in advance for your support
    Daria

    In KB21N (activity allocation), system uses the exchange rate type you have maintained in controlling area version plan settings (transaction OKEQN). Activity allocation during the month always happen at the planned price maintained in KP26 at the exchange rate specified in plan version. During actual price calculation and revaluation during month end, it calculates actual activity price at (uses M rate to convert to controlling area currency) and revaluates consumption.
    I think you cannot use other exchange rate, see the coding in include LKSPIF00 that is used in KSII where currency type is hard coded to M, if this is plan price calculation it's picking tka07-kurst.
    Best Regards,
    Venkata Ganesh Perumalla

  • 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

    Dear All,
    If we do not assign any exchange rate type to any document type or customer / vendor master data, the system picks the default 'M' exchange rate type. Can anyone let me know where this default setting has been made and whether this setting can be changed? What if I do not maintain exchange rates for 'M' instead I do it for 'M1'
    I have a scenario, wherein I want to make exchange rate type other than 'M' as default and we do not want to make it at the document type level or customer / vendor master data level.
    To make things more clear, this is not related to the realignment / foreign currency valuation. This is related to recording of invoice export / import or credit / debit notes..
    Can anyone let me know how would this be possible?
    Full points guaranted

    Hi Swapvik,
    The exchange rate type always is set "M" as default. The only way to
    change the exchange rate type is with the customizing in the document type. If you are running the automatic payment program, you can also select a different exchange rate type. However, for normal document postings (trans. FB01), there is no other solution but to choose a different document type.
    For example:
    If you want to use exchange rate type B 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 exch.type comes into picture.
    Please be advised that you can not change the default exchange rate type
    for the 1st local currency. The default type for 1st local currency KURST of M cannot be changed. SAP does not allow for customers to setup a company code with an exchenage rate type other than M for the 1st local currency (because this could lead to exchange rate differences in the system which are not allowed).
    Exchange rates are defined in SAP at a Global level via transaction OB08. In the IMG documentation for transaction OB08 (path General Settings > Currencies > Enter exchange rates) it explains that:
    'The exchange rates apply to all company codes'
    'The system uses the type M exchange rates for foreign currency
    translation when posting and clearing documents. An entry must exist in
    the system for this exchange rate type. The exchange rates apply to ALL
    Company Codes.'
    Hope this information helps.
    Regards,
    Lucas Dornelles
    FI Support Consultant
    SAP Active Global Support - Financials

Maybe you are looking for