Exchange rate type from infoobject 0RTYPE

In my query I need to do currency conversion using the exchange rate type value in the infoobject 0RTYPE of my infocube.
Query only allows me to use the variable on 0RTYPE but not the value available in the infocube for 0RTYPE.
If one of the record had 0RTYPE = 'M' then the amount of that record should be converted using 'M' if another record in the cube has 0RTYPE = 'EURX' then the amount of that record should be converted using 'EURX' as the exchange rate type.
But if I use the variable on 0RTYPE at any time I'm able to convert using just one exchange rate type.Is it possible that I can convert based on the exchange rate type 0RTYPE value in the infocube of each data record.
Thanks,
A Pothuneedi

closed

Similar Messages

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

Exchange rate types with referency currencies in BW currency translations

Hello Guru's:
Will BW currency translation keys utilize 'reference currency' functionality on exchange rate types? I want to translate between two currencies (CNY to HKD) that don't have a direct rate, but both have rates for USD.
I have:
- exchange rate type BU10 defined with USD as reference currency
- exchange rates for BU10 with relevant validity dates entered from CNY to USD and from HKD to USD.
- exchange rate factors for BU10 relevant validity dates entered for CNY to USD, HKD to USD, USD to CNY, and USD to HKD.
- a currency translation key defined taking source currency from transactional data (0CURKEY_LC), exchange rate type from a variable, target currency from a variable, and time reference as end of 0FISCPER.
The translation from CNY and HKD to USD works, as does translation from USD to either HKD or CNY, but not CNY to HKD or vise versa. So I wonder whether BW currency translation keys can even use the reference currency concept. Or maybe there are constraints on translation key configuration that must be observed to make them work for this situation.
Kind regards,
Aron

I solve it after using RSRT to debug the currency translation. The must be an additional entry in TCURF for the source and target currencies, not just for the source currency to reference currency and reference currency to the target currency. In my example from the original post, an entry from CNY to HKD is required.
Edited by: Aron Weaver on Oct 21, 2010 11:15 PM

Exchange rate type for planning cost

Hy all,
our release is 4.7 .
Is it possible to change now the exchange rate type from M to P for costing and fix a budget figure valid for the whole year to evaluate standard cost?
Thanks in advance
Vir

Dear Vir,
http://help.sap.com/saphelp_nw04/helpdata/en/a8/352537b1d21763e10000009b38f889/frameset.htm
You can define the exchange rate for a currency pair using either direct or indirect quotation.
Indirect exchange rates are always given with the local currency or reference currency as the to-currency.
Hope this will help.
Regards,
Naveen.

Exchange rate type mismatch in the invoice

Hi experts,
When I am creating an invoice, invoice is picking up wrong exchange rate type MTR which is not at all maintained in the customer details. The sold to party is having the exchange rate type TR2. Can anybody please help on the issue.?

Hi,
If it is not picking correct exchange rate type from the sold to party, please check the change log in the SP customer master for the field. It could've been changed after sales order creation and invoice would've referred to your S.O details.
Also, please check whether the below info is useful.
[http://www.sap-img.com/sap-sd/exchange-rate-billing-documents.htm]
Regards,
P Gomatheeswaran
Edited by: Gomatheeswaran Palaniappan on Aug 29, 2011 7:32 PM

Replication of Currency exchange rate types

Hi,
I had changed the currency exchange (eg:USD to INR) rate types in R/3 system.now I need to replicate from R/3 to SRM.
please let's know how to replicate the Curreny exchange rate types from R/3 to SRM.
Kindly suggest me.
Regards,
sss

hi
eevry day you might run this job right ?
report se38 BBP_GET_EXRATE - this bring every day exchange rate update from ECC to SRM
muthu

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

From where system picks exchange rate type in GR

We have already defined 'G' for import exchange rate type and attcahed in OBA7 in 'WE' doc type., but at time Gr system giving message ;For M. convesion from GBP to INR missing..it is already maitained at G exchange rate type , why system asking for M.
Pl clarify me
Thanks,
Dharmveer

If fixed Exchange rate is not given in PO header details, the it will take exhange rate maintained using T code OB08.
Pl maintain exhange rate both ways for Type M ie IR to GBB & GBB to INR.
Regards
Bhavesh Mistry

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

One Conversion Type and two Exchange Rate Types in one report

I have Conversion Type called TEST. In this Conversion Type there is Exchange Rate Type D selected (D-daily). I have also Fixed Target Currency selected. And the report works perfectly fine....BUT.......there is also Exchange Rate Type M defined in the system (and it used for the exchange rate used last day of the month).
The question is: how to put both Exchange Rate Types into one Conversion Type so both types are used in the reports?

Hi,
You can go for a variable exchange rate type.
Creating variable:
For this you have create a varible which can take diffrent exchange rate types.
Open query designer create a new dummy query in that search for infoprovider 0RTYPE.
It will have one dimension(name ->key) with 0RTYPE in it.
create a variable for 0RTYPE.
Save and close the query.
goto RSCUR -> give your translation type -> go to exchange rate tab -> choose Ex. Rate from var option -> give the variable you have created prviously for 0RTPYE.
Rest all same but just for completion...
Go to your query in which in u want to do cur conversion.
Double click on the key fig
Go to conversions tab-> select the conversion type u created in RSCUR.
When you run the query you can select the exchange rate type in the variable screen.
rgds,
Raghu

Add Exchange rate type to Selection Screen in BEx

BW Experts,
Business raised a request to add Exchange Rate Type(KURST) from TCURR table in the selection screen of BEx so that they can select the required rate and target currency for a particular key figure.
In Query Designer we can provide variable for currency by going into the context menu of key figure but not sure how to provide a variable on Currency Conversion Key.
Please suggest.
Thanks in advance.
-Bobby.

Hi there,
You could with user exit define a variable ready for imput but in step 1 prefill the variable with only those values, but this would still when the user executes when pressing F4 be able to check all that. Nevertheless that variable would be prefilled with the values you wish in user exit.
Another option is to mark 0RTYPE in RSD1 as authorization relevant and manage different authorization values for the users. This way you could when the user presses F4 see only values he/she is authorized.
Diogo.

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

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

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

Exchange Rate Type M in MIRO

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

ME22N change Exchange rate type at price condition level

Hello,
In ME22N exchange rate type is 'M' by default. When a price condition has currency different than purchase order this 'M' rate is used.
Now I need to change this 'M' rate but for particular price conditions (and exchange rate type can be different for each price condition). Don't ask me why:-) This requirement comes from business consultant and he knows that there is no user exit for this. I need to modify standard. The problem concerns items price conditions.
I'm not asking you for a complete solution, but maybe you can give me a hint where to start? What is the function module which perform price calculation (where exchange rate is used) in ME22N.
I tried to change KOMK-KURST in price condition rule (the procedure which is called to check if price condition has to be calculated or not). It is called for each price condition and I know a name of price condition. But I think the exchange rate type is read at the beginning and stays unchanged even I changed KURST.
I also found function module READ_EXCHANGE_RATE, which has rate type 'M' by default. I could put my modification in place where it is called. But it is not called when I press button Update price. It is only called when I change the currency of condition and press enter. This FM is called in few places in ME22N but not when I'm refreshing prices. Maybe during a refresh it has already an exchange rate? If so, READ_EXCHANGE_RATE could be a solution, but... It is not called when price conditions are created for the very first time (when I create PO item). Maybe system calls different FM?
I also tried to use trace (ST05) to see where systems reads from TCURR, but I think some buffers are used and TCURR is not in trace.
So now I'm stuck hoping for your help.
Best regards
Rafal

Prabhu Peram wrote:
Hello Rafal ,
>
> still im trying to understand your requirements , anyhow if you change/propose new exchange rate at header level , then system wont put type as 'M'.
>
The problem is that if I set a new exchange rate type, it will be the same for all price conditions. My requirement is to have different exchange rate type for each price condition. The pricing procedure will loop at each price condition, and depending on condition name I need to have different exchange rate type.
Example:
condition XMER is in EUR and must be converted to USD (factor should be 1,234)
condition XMET is in EUR and must be converted to USD (factor should be 1,567)
Now the factor is the same for all price conditions.
I have found interesting table XKOMV. It contains price conditions and there is a field with factor value. Now I will look for the place where this table is filled with data or for the place where I can modify factor values before XKOMV is used in pricing procedure.
Best regards
Rafal

Exchange rate type from infoobject 0RTYPE

Similar Messages

Maybe you are looking for