COPA0004 Change in Exch.rate type
Hi,
We’ve a costing based CO-PA in our instance which is shared by other co.codes in our environment. Now, with new business requirement, we
may have to use a separate exchange rate type for CO-PA than M. We’re trying to achieve this with exit COPA0004. We’ve also read the note 429517 on Currency translation billing document -> CO-PA to understand the value flow to COPA.
Please note that we don’t want to affect current exch.rate settings of existing co.codes which is ‘M’. However, for a new co.code we want
to move values to COPA with ‘P’ exchange rate.
Question-
Is it possible to achieve it through user exit COPA0004 to default exchange rate in COPA based on company code? Or is it a blanket change
for all co.codes if we change the rate from ‘M’ to ‘P’.
We’re evaluating the solution before implementing in system.
Thanks,
Nirav
Hello Nirav,
planning version settings in CO-PA do only affect planning data!
Conversion with actual data will always be done with rate type 'M'.
Enhancement COPA0004 offers however a possibility to use different
rate type in case of actual data.
Function module EXIT_SAPLKECU_001 can be used to change the exchange
rate type for currency translation when actual data is processed in
Profitability Analysis. By default, the system always translates the
values using the exchange rate type "M". You can change this type
(export parameter E_KURST) for a specific operating concern (import
parameter I_ERKRS). The import parameters I_CURRENCY_FROM and
I_CURRENCY_TO contain the currency key of the currencies involved in the
translation.
You can only change the exchange rate type for translating actual
values! For planning, you specify the exchange rate type in Customizing
when you define your plan versions.
Best regards,
Ronghua Fan
Similar Messages
-
Default New exch.rate type at Purchase Order.
Hi,
We would like PO to be created with new Exch.rate type.
Are there any settings in MM/FI to default a different exch.rate type say u201CZu201D instead of u201CMu201D at the time of PO?
There is one in FI Doc. type, but it refers at the time of GR or IV, whereas we want to change at PO.
Will appreciate if someone can throw some lights?
Thanks,
NiravHi,
Thanks for your reply.
Is the user exit for exch.rate type?? I understand the exit to keep the exch.rate fixed.
but, I believe it should be std. config. in SAP to define somewhere which exch.rate type should be used by PO.Because, currently PO is refering to "M" which we want to replace with new exch.rate type.
Thanks,
Nirav -
Hi,
According Russian legislation need to do posting for all operations in foreign currency using exch.rate set by Cental Bank of Russian Federation.
Currently when we try to do posting in EUR, system uses exch.rate type EURX, which is managed not only by Russia and sometimes is different from needed exchange rate.
So, need some change in customizing to start using exch.rate type M.
And also, any authorization change or org.procedure change, that will prevent change of this exchange rate by non-Russia users.
So, what are the configuration have to do for this?
Thanks in advance.
SwethaHi Swetha,
1) Define Additional curriences
2) Mantain exchange rate types (OB07)
3) Currency translation ratio ( OBBS )
4) Currency Exchange Rates ( OB08)
5) Define Valuation Method (OB59)
6) Automatic posting procedure (OBA1)
Hope this will help You
Regards -
User exit/BADI for changing the exchage rate type in MIGO
Dear guru's,
Please help me in finding the user exit/BADI to change the exchange rate type in MIGO.
Regards,
Abdul Rahimdid you check this one MB_GOODSMOVEMENT?
also exchange rates needs to be changed at Purchase order level and those will be reflected while creating MIGO. -
Exch.Rate Type for Determining the Proposed Rate
Dears,
I defined, in the document type to be used for Goods Receipt, the field T003-KURST (Exch.Rate Type for Determining the Proposed Rate) equal to u2018Pu2019: exchange rate type used also for standard translation for cost planning.
Then, I created a Purchase Order using a vendor in foreign currency, and in the header section within tab u2018Delivery/Invoiceu2019 in field "Exchange Rate" I filled in the exchange rate valid at the moment of the Purchase Order creation and I also put the flag in the indicator "Fixing of Exchange Rate".
Afterwards, I posted the Goods Receipt against the Purchase Order created at the previous step.
My expectations were to find in FI accounting:
- 1 line item for stock increase (transaction BSX) valuated using the exchange rate defined in the document type in field T003-KURST;
- 1 line item for GR/IR increase (transaction WRX) valuated using the exchange rate defined in the Purchase Order and indicated as fixed;
- 1 line item for difference (transaction PRD) between stock and GR/IR.
but when I checked the accounting document, these my expectations were not met, because:
- the line item for stock increase (transaction BSX) has not been valuated using the exchange rate defined in the document type in field T003-KURST, but a differet exchange rate that I didnu2019t find defined for this couple of currencies;
- the line for GR/IR increase (transaction WRX) has been valuated as expected using the exchange rate defined in the Purchase Order and indicated as fixed;
- the line item for difference (transaction PRD) between stock and GR/IR has been created.
The help (F1) for field T003-KURST, show the following indication:
Exch.Rate Type for Determining the Proposed Rate
Rate type under which the proposed rate is defined for foreign currency documents.
Use
If no exchange rate is specified in the document header when entering documents in foreign currencies, the system will automatically select a rate from the currency translation rate table. The system then converts all amounts in the document's line items using this exchange rate.
The system uses the average rate as a default value as long as no other exchange rate type is entered here.
Based on this message, my expectation is that all documentu2019s line items have to be converted at the exchange rate type defined in field T003-KURST. And in the case mentioned above, the line for stock (BSX) should be converted at exchange rate type defined in field T003-KURST.
While, correctly, the line for GR/IR (WRX) has been converted at the exchanged rate fixed in the purchase order.
Can you please let me know how can be fixed the problem for the line related to the stock allowing the conversion using the exchange rate type defined in field T003-KURST?
Thanks and Regards,
JodyHello Jody,
kindly consider the information contained under the attached note:
191927 - Posting logic: GR for foreign currency PO.
As stated in it:
Postings to the material stock account (BSX):
In order to be able to determine the value of the stock posting, the
valuation methods which exist in the material master in local currency
(standard price, total value of stock) must be converted into document
currency. This translation is thus carried out on the posting date with
the exchange rate type that is assigned to the FI document type used,
that is, independent from the exchange rate defined in the purchase
order!
If no exchange rate type is assigned to an FI document type, the system
uses exchange rate type M.
Please, check in your system the settings stored in the customizing
transaction OBF4 for the document type WE (Goods receipt). If the field
'Exch.Rate Type for foreign currency documents' is empty, the exchange
rate type M is used.
The fixed conversion rate in the purchase order refers to the valuation
approach in the purchase order and, therefore, to the costs for the
purchased material. Therefore, the posting amount to the GR/IR clearing
account (WRX) is converted according to the fixed conversion rate in the
purchase order header.
On the other side the fixed conversion rate in the purchase order is not
designed for converting the posting values to the material stock account
(BSX). This conversion reflects the situation of the valuation of the
material stock and is therefore designed to be independent of the
conversion rate defined in the purchase order. This is what note 191927
outlines.
In the note 191927 you will also locate relevant information about the
postings to the KDM key:
Exchange rate differences (KDM):
As of Release 4.0A, exchange rate differences (KDM) can be posted to a
separate account. The exchange rate differences result from the
difference of the clearing value on the GR/IR clearing account (WRX) in
document currency that is translated to the current exchange rate stored
in the system in local currency from the clearing value in local
currency that is determined with the conversion factor from the purchase
order or the invoices.
The offsetting entry for the exchange rate differences is settled with
the price difference.
(Price difference = GR/IR amount - stock value - exchange rate
difference)
KDM is only posted during the GR if the flag T169P-XPLCU is initial,
therefore, KDM postings will not occur during incoming invoices.
This is determined in the IMG path:
Materials Management
-> Logistics Invoice Verification
-> Incoming Invoice
-> Configure How Exchange Rate Differences Are Treated
Here, you have the following options per Company Code:
.- The exchange rate differences will be calculated from the difference
between the exchange rate at the time of the goods receipt and the
exchange rate at the time of the invoice receipt.
.- The exchange rate differences will be calculated from the difference
between the exchange rate at the time of the invoice receipt and an
assumed exchange rate that is valid for a specific amount of time,
such as a year or a season.
.- No exchange rate differences will be calculated. Instead, differences
from exchange rate variations will be considered as price differences
and posted to a price difference account.
The field T001A-CURDT for the company code will determine which date is
relevant to calculate the exchange rate difference.
This is set under the IMG path:
Financial Accounting
-> Financial Accounting Global Settings
-> Company Code
-> Multiple Currencies
-> Define Additional Local Currencies
So, finally, the value for KDM calculates as difference between
GR/IR amount in local currency - GR/IR amount in foreign
currency*exchange rate.
I hope this information can be of help.
cheers
ray -
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.KI 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 -
Manual Clg - Exch.Rate Type
Hii all of you..
When we go for manual clearing in F-32,44 system is picking the exchange rate type "M".
For fluctuation accounting purpose we are maintaining the exchange rate for "M"
Now i want a different exchange rate type like "B" , "G" for manual clearing purpose , otherwise it is effecting the entire system i.e. MM , SD modules (Standard Translation type-M)
Plss suggest me how to assign the exchange rate type for manual clearing..??
Thanks & Regards
Ramki
Edited by: Ramki on May 19, 2008 4:56 PMHi
Try at the Document Type level. Here give the Ex rate Type accordingly. so the system will pick the Ex. type which u have given(not M by default)
Rgds
Anjali -
I've changed the exch. rate, but the Amount in Local Curr.EUR isn't changed
Hi All,
I've posted a bank document in USD dollars. In FB03 I can see for that document the "Amount in document currency" (USD $) and the Amount in Local Currency (EUR).
Later I've set the "exchange rate" in S_BCE_68000174.
If i turn to display that document, I can see that the the Amount in Local Currency (EUR) isn't changed.
Could anyone tell me how to obtain the Amount in Local Currency (EUR) modified?
Thanks
GandalfHi,
After the posting of the document the amount is stored based on the exchange rate which was valid during the posting. You cannot, and justified, modify it afterwards. You can reverse the document and post it again if you'd like.
Regards,
Eli -
Hi
I am viewing the "change log" from OB08 transaction. However, in the change log display status, the message is appearing like "Logging is switched off". How can I switch on the log.Hi,
Try transaction code : SCU3 - Table History with table : V_TCURR.
Note that before that you need to activate Table logging ask for BASIS team for more clearance.
Regards,
Kishore K -
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,
SagarHi,
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 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
SivaHi,
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 -
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 guarantedHi 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 -
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
ChristianHi,
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 -
Hi
We have some issue in exchange rate . When i am doing MIRO this time i have geeting error enter rate / USD rate type M for 04.12.2009 in system setting.we have process different types Invoices with different currency in Miro to get this error message.
After i m exit in this MIRO screen. Than again enter MIRO T. COde and enter PO number this time i have no geeting any error.
We have check all the seeting in OB08 all are perfect. Colud please help me on this issue.
Thanks in advance
Why this error is geeting in first time.Srikanth,
Yes, exactly it is the rate upon 28.01.2011that should be relevant for the actual document.
Exchange rate has not entered manually in document header by interface nor by user. Interface only feed document amount and currency i.e. no rates.
Standard quotation in table TCURN for GBP=>USD is:"1" Direct quotation valid from 01.01.1800
Standard quotation in table TCURN for "Blank"=>GBP is:"2" Indirect quotation valid from 01.01.1800
Translation ratio for currency pair GBP => USD for exch rate type M is 1:1, valid from 01.01.1800, alt ERT=blank.
Translation ratio for currency pair USD=> GBP for exch rate type M is 1:1, valid from 01.01.1800, alt ERT=blank.
Translation ratio for currency pair USD=> GBP for exch rate type M is 1:1, valid from 31.10.2010, alt ERT=blank.
Maintained exchange rate valid for the period 31.12.2010 - 30.01.2011 for exchange rate type M is 1 USD= 0.64114 GBP
Amounts in document are
Doc. Curr. Amount= 187.44 GBP
LC2 Amount= 281.16 USD
Rate used for LC2 Amount in document equals 1 USD = 0.6667 GBP
Correct LC2 Amount with rate 1 USD= 0.64114 GBP should be 292,35 USD.
Kind regards,
Linda -
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
SvenPlease check the following help http://help.sap.com/erp2005_ehp_03/helpdata/EN/1b/75a9371c726343e10000009b38f842/content.htm
Maybe you are looking for
-
My entire music collection was recently deleted on accident. It was my fault (and partially my external harddrive's ridiculously touchy USB cord's fault), but anyways I was able to use an undelete software to get the files back. Some are gone, some a
-
MAC OSX 10.4.11 I succumbed to the constant messages telling me that I didn't have the latest version, despite being happy with the one I had. My old version and all my bookmarks have been deleted and now my Mac says it doesn't support Firefox!!!!! H
-
Contact pictures not showing Pre 2
I have had two Pre 2, and neither of them show the contacts' pictures in either the SMS app or Just Type, not only does it look terrible, but I associate certain images with certain people for speed of recognition. I tried Palm support and got the us
-
If I buy an I Pad mini will there be a problem getting it hooked up in China
I am buying an I pad mini with cellular and wi fi to give as gift to a CHinese national living in China. Will they be able to get service fro a local Chinese carrier on this?
-
Nested schema usage in JDeveloper
We are building a BPEL process that makes use of a schema nested to multiple levels. Some schema types have an extension to other base types. When trying to create variables for such types, JDeveloper throws an error "Problem building schema" with me