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

Similar Messages

  • Where we assign Exchange rate type at company code level,

    Dear All,
    Where we assign Exchange rate type at company code level, In 0BA7 we assign by Document type wise and OB22 will assign by controlling area wise , but we are not maintain Controlling area, exactly where we assign , and how it will pick at the time of PO creation ,
    Thanks in advance
    Vijay

    Hi,
    In OB22 we assign Exchange rate type against company code and not against controlling area .
    Regards,
    Shayam

  • Exchange rate type company code dependent

    Hi Experts,
    as I know in SAP it's not possible to maintain exchange rate types per company code. In function module FI_CURRENCY_CHECK the exchange rate type "M" will be always set for all postings.
    Now I need a possibility to maintain exchange rates company code dependent. Do you think it's a good idea to change the above mentioned function module so it's possible to set an own exchange rate per company code? Do anyone have experiences or other solutions?
    I also know that it's possible to set per document type an own exchange rate type and also it's possible to set in V_TCURF an alternative exchange rate type for "M". But both are not an option for me.
    Best regards
    Christian

    Hi,
    You cannot have diff exch rate types for different company codes, since exch rate maintainance will be at client level only.
    Practically yours is a peccular requirement.
    We can't figure out how system will behave in case if you modify th eFM as you said.
    REgards,
    Srinu

  • Exchange rate maintainance as per company code or ledger in OB08

    Hello,
    Is it possible to maintain exchange rate as per company code or ledger in exchange rate table.
    If not, please suggest any other alternative where I can maintain exchange rate as per company code or ledger.
    Regards,
    Tapan

    In table T882, you can see ledger and company code assignment; with currency keys and additional currency types used for company code/ledger. You have option to choose the currencies at ledger and company code level, but not the currency type. Exchange rate type 'M' is used and even hard coded in many programs/transactions for actual postings. In planning, to some extent you have the option to choose exchange rate type, default is 'P'.
    Regards,
    Ganesh

  • 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

  • Default document type for F-28 per company code wise.

    Hi SAP Experts
    My client wants to default document types per company code wise for F-28.
    As per my knowledge in OBU1 is cross client and OBZO is accepting only customer invoice and credit memo but not customer payment.
    Please help with possible ideas to solve this issue, including any idea relates to substitution also. Your help is appreciated.
    Thanks in advance
    Prathima

    Hi Prathima,
    As mouri said it can be done only by Substitutions
    Since OBZO is only for enjoy transactions
    I have verified the notes aslo but there is no possibility for F-28 by company codes
    Better you can use
    Prerequisite
    SYST-TCODE = F-28
    Substitution
    use Exit
    Inside exit you need fetch the document type as per the companycode
    to achieve this you need define one ztable with company code and document type columns
    Thanks
    Vishnu

  • Exchange rate type determination

    Hi,
    Just wanted to know how a exchange rate TYPE is determined by SAP in sales order or any FI document?
    Currently for us, the exchange rate type used by SAP is EURX and I am wondering how this type is determined (not type M), if:
    1. Nothing is defined in customer master
    2. Nothing is defined in Additional Local currencies (OB22)
    The company is Poland and company code currency is EUR. Is it to do anything with Euro currency.
    Please help me?
    Thanks in Advance

    Hi,
    The system by default uses Exchange Rate Type M for any currency translation in the system.  You can use a different exchange rate type in your system, instead of Type M, by defining the alternative exchange rate type in transaction code OBBS.
    Please assign points.
    Thanks,
    Madhav Nanduri

  • Exchange rate type  not visible

    I want to maintain my own currency convertion method in BW ,we can do this in T-code RSCUR
    I have maintaned  my Exchange rate type in the table TCURR and then use this as the Exchange rate type in T-code RSCUR but when I press F4 ifor Exchange rate type in RSCUR I am unable to see my value
    Pls help me out
    priya

    Dear Maya,
    I guess this is because exchange rate types are stored in a separate table TCURV. In TCURR you just have exchange rates.
    Could you please check if your exchange rate type is stored in this table as intended?
    Greetings,
    Stefan

  • Exchange Rate Type default different from M for a company code

    Dear SAP guru,
    Would you shed some light on this?
    How would we be able to default/assign a different exchange rate type from M at a company code level?
    I have a company code - finance company - that every foreign currenty transaction needs to be translated using different exchange rate type (i.e. daily hedge rate) than other operating companies.
    The OB22 screen makes it appear as M rate is specificied as 1st currency in company code, but grayed out and not able to change.
    Please help me with your expertise on this.
    Kind regards
    taro

    Hi,
    ExRateType is hardcoded in
    Main Program     SAPL0F03
    Source code of   L0F03I01
    *------- Daten zur ersten Hauswährung -
      rfcu4-curtp = '10'.
      rfcu4-bwer1 = '0'.                                        "AT 23039
      rfcu4-kurst = 'M'.               <<<<<
      rfcu4-cursr = '1'.
      rfcu4-curdt = '3'.
    The reason why the assignment of exchange rate type M to the first company code currency is a historical reason. A lot of coding within the SAP system is directly developed under the prerequisite that the exchange rate type for the first company code currency is M.
    As you described you want to setup several company codes in one client that all have the same first company code currency but should use different exchange rates. To solve that issue there are 2 ways available:
    The first way is that you use the functionality to assign an exchange rate type to a document type. That would mean a lot of work because in that case you would have to define all document types seperatly for
    every company code.
    The second possible solution is that you use different names for the fist company code currency.
    That means for example that you name the first company code currency in company code 0001 USD and in company code 0002 US1. So you can use different exchange rates for the same currency.because in that examle USD and US1 are only different names for the same currency. Using this approach you can have different exchange rates for different companies with the same company code currency by setting only different names even though the exchange rate type M is fix asigend to the first company code currency.
    Best Regards,
    Gladys xing

  • Different exchange rate type M in different company codes

    Dear all,
    I am facing the following very inconvenience problem:
    I am an SAP consultant and has ALWAYS set up exchangre rate type M, the same rate used for all company codes in the Group.
    My new customer wants to have different exhange rates for ALL company codes, that means we cannot use exchange rate type M for all company codes. All company codes in Sweden could have the same exchange rate type and so on, since all the rates within a country is updated with the rate from banks in the particular countries.
    I think a solution could be to create worklists for every country and to always maintain all the rates against the local currencies within the country. This means in Sweden all the rates will be maintained against SEK, but never in any other way. That menas we can never maintain the rates from SEK to EUR in Sweden, we only maintain the rates against Sweden. I Finland however, all rates will be maintained against EUR (the local currency för all company codes in Finalnd).
    Could this cause problems (or inconsistency) that incorrect rates will be used?
    I am very very thankful for all help I can get in this question!
    Best Regards, Åsa

    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

  • Exchange Rate type Assignment to Company Code

    Hi,
    I'm working on the implementation of a new company code on a SAP R/3 4.6c release. I've created a new exchange rate type EURH (with transaction OC47) and I would like to know hot to assign it to my new Company Code.
    Is there a specifc standard transaction? Could you please suggest me a possible solution.
    Thanks!

    Hi
    Exchange rate type you cannot assign to a company code. Where as you can specify explicitly while document entry.
    By default in SAP for a new company code system will use 'M' rate as standard. If you want to replce this exachange rate type with your new exchange rate type then goto SPRO --> General Settings --> Currencies --> Define transilation ratios for currency translation
    Maintain new exchange rate type as Alt.ERT against 'M' rate then system will take new exchange rate instead of 'M' rate. Otherwise as I said earlier, you can use created exchange rate type in any company code by specifying in document entry or payment program, or  you even can assign ex.rate type to a Document type, etc.,
    Hope above helps.
    Regards
    Siva
    Message was edited by:
            Siva Satyanarayana

  • 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

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

  • 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

Maybe you are looking for

  • Error while upgrading Oracle SOA 10.1.3.3 to 10.1.3.5

    Hi, Iam trying to upgrade Oracle SOA ver.10.1.3.3 to 10.1.3.5 on a windows server.The following steps were followed. 1. SOA was stopped. Back up of the SOA folder was taken. 2. SOA uses the default Olite database. Connected to the BPEL schema and run

  • Photoshop CC 64 bit

    I run a 64-bit operating system. Before Photoshop CC changed to Photoshop CC 2014, it installed both in my Program Files, and Program Files (x86) folders. Now, it only displays in the Program Files folder. Topaz Labs, installs in the (x86) folder, an

  • I got Exception when i try to start default weblogic server

    Hi, I download a trial version weblogic application server 6.1 and installed succesfully by using GUI mode and my Operating system is WINDOWS NT 4.0(service pack6). When i try start default weblogic server and i got the following excetion any could m

  • Check spelling - is it just me...?

    Does anyone else find it quite tricky to see where spelling mistakes/queries actually are on the page when you run run Edit > Spelling > Check Spelling ? I would find it a lot easier to use if it had an option where it pointed at the word in question

  • FAQ on Webdynpro for ABAP

    Can i get the FAQ on Webdynpro for ABAP ?