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

Similar Messages

Treatment of exchange rate difference- company code not appear in the list

Dear guru,
I am configuring the treatment of exchange rate difference (SPRO> MM> LIV > Incoming invoice> configure how exchange rate differences are treated). However,the company codes that needed to be configured are not appear in the list. Please note that in the config screen, dont have the option of "New entry", we only set base on the list of existing company codes.
Also, please be noted that we configured accounts for KDM, PRD in OBYC already
Appreciate your respond.
Thanks and best regards,
Hong

Hi,
Check in table "T169P" & "T169V", whether your Co. code exists or not? If not then maintain following config settings.
SPRO > Materials Management > Logistics Invoice Verification > Incoming Invoice
> Maintain Default Values for Tax Codes (After maintaining this entry by "New Entries", it will start appearing for following options)
> Configure How Exchange Rate Differences Are Treated
> Configure How Unplanned Delivery Costs Are Posted
> Edit PO Supplement Text in Invoice Verification
> Set Check for Duplicate Invoices

RMB/CNY exchange rate Chinese company code

Dear all,
When posting an invoice for a PO made in RMB(chinese renminbi) SAP errors that no exchange rate is maintained for this currency. This is correct because we only maintain CNY currency because it's the same and it's set as company code currency. Can I set a exchange rate CNY/RMB=1 and how to do this so no more errors occur, or do you guys have any suggestions?
Also when in OA08 and OE00 I see that currency is set to RMB for China, will this cause any problems in the future?
Thanks in advance,
Michaë

Thanks for the input,
I don't make PO's in RMB they were already created, and in ME22 I can't change currency.
I guess I could ask all users not to use RMB currency in their PO's. I don't think this is the ideal solution though because one day someone will create a PO in RMB again. But for now I don't want to delete RMB currency or implement any changes unless well advised because I'm inexperienced and my colleague is in maternity leave.
Further advise would be helpful,
Best regards,
Michaë

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

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

Different exchange rate type for budgetting internal orders

Hi,
we would like to use a different exchange rate types when budgetting on internal orders depending on the order type.
In our current set-up the internal order types are linked to a budget profile, in this budget profile we have specified the exchange rate type to use.
Unfortunately this doesn't work (I guess this is only used to translate the total budget)
We do availability control in company code currency and on a yearly base, but each time we approve some budget we want to translate this at the most recent (monthly) exchange rate.
This works if we change the exchange rate type P each month so that it contains the most recent exchange rate on the first of januari.
Unfortunately this P-rate is also used for other things (other budget on other order types and cost center planning) here we want to be able to keep the same exchange rate throughout the whole year.
If anyone could help it would be greatly appreciated!
Thanx in advance
Sven

Please check the following help http://help.sap.com/erp2005_ehp_03/helpdata/EN/1b/75a9371c726343e10000009b38f842/content.htm

Exchange rate type for vendor invoice

Hi,
How to know which exchange rate type is being considered during postings vendor invoice in foreign currency.
Company code currency is EUR and I am posting an invoice in USD.
I checked OB08 and exchange rate with type M does not match with one calculated in FB60.
I checked document type KR (OBA7) -exchange rate type 'M' is mentioned.
I checked additional currencies for company code (OB22) - all currencies use exchange rate type 'M'
So how to check which exchange rate type is being used by system.
Thanks.

Hi
For posting vendor invoice which doc type are you using. If other than KR check that one also in oba7. And for OB08 you have to check for Ex rate M from EUR to USD what is the curr rate.
Regards
Mani.S
Edited by: smanimba1 on Nov 28, 2011 5:49 AM

Payment Program and Spot Exchange Rate Type

Hi Everyone,
When performing wire transfers in foreign currency, my company wants to be able to have the payment program, F110, be able to convert the payment to the vendor based on the bank's spot rate at that moment in time. I found that we can use exchange rate type "G", update the rate within OB08 prior to running F110, input the exchange rate type "G" within the Parameter section within "Exchange rate type" and process the payment program as normal.
My question is this: We have a few separate companies that would use this feature with the possibility of receiving different rates from their respective banks. How would this work if 2 companies had 2 separate exchange rates for the same conversion on the same day? I found that once you enter in an exchange rate for a conversion, you are stuck with that rate for that particular day, so the amount can not be over written with another rate to be used by the second company code. Is there a way around this or is there a different way to accomplish the converting of currencies at the payment program?
Thanks.
Pete
Edited by: Peter Zaborowski on Sep 26, 2008 2:35 PM

Hi Peter
Use two different exchange rate type for bank1 and bank1. Upload the exchange rate into the system. Select house bank and specified rate type during the payment run.
Regards
Srinivas

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

Exchange Rate Type upon PO/PR

Hi Experts,
Is there a config to default exchange rate type upon PO/PR creation? I was told that by default it will read type 'M' and I'll be the happiest man if it can link to type 'M'.
In my case, it reads from other type i.e. '2004'. Thus, I was wondering how does it reads and is it based on configuration? Thanks in advance.

I suggest you to check global company code(mentioned in po/pr) setting
for exchange rates in spro financial accounting ??.
Whether new po's / pr's were created from existing or old documents ?
Edited by: Jeyakanthan A on Dec 4, 2011 1:33 AM

Exchange rate type company code dependent

Similar Messages

Maybe you are looking for