Exchange Rate type determination in PO

Dear all,
During purchase order creation for a foreign vendor, system looks into the exchange rate tables to determine the exchange
rate between the local currency and order currency (foreign currency).
During the rate processing system always takes the rate mainatined with exchange rate type "M".
We have a requirment where we want the system to look into the specfic exchange rate type for a company code.
For Eg, PO's created for the hungary company code, should look into the exchange rate maintained with exchange rate type HU01 which is mainatined in exchange rate tables and not from exchange rate type "M".
I searched all config elements on the MM side but could not find any. I also understand that we could set this using the invoice document type, but we need to have the po determined the right exchange rate type.
We are implementing SRM and the shopping cart or the PO created goes through the same logic , it finds the rate maintained in exchange rate type "M"only.
Kindly advise if we could set this config somehwere or could control through data.
Regard
Harish

Hi,
it is the sap std behaviour while creating the PO, picking of the exchange rate from the specified tables and from specified type.Seems you can not change.
Regards,

Similar Messages

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

Determining Exchange Rate type

Hi
For a export customer we have made a copy of exchange rate type M and named it as E
In Ob08 the direct and indirect rate for E has been maintained and in customer master and accounting document configuration too E has been maintained
During generation of accounting document the rate determined by the system is not of E but of M
The validity of E is greater than that of M but still system is determining rate as per entry maintained for M
Can anyone please suggest what should be done
Thanks and Regards
Sunil Srinivasan

Hi
I have prepared the routine as per the note
But where should this note be applied in SAP .Is this at aSD-FI interface point
Thanks and Regards
Sunil

How to determine exchange rate type in shipment costs document?

I would like to determine exchange rate type in shipment costs document, but I don't want to do it manually.
Can anyone please give me a hint on how to do it?
Thanks & Regards
BJ

System will determine the exchange rate type based on value maintained in exchange rate table.Tcode OB08.
It will post the difference if any in the GL mentioned in transaction event key KDM in tcode OBYC.
Reward if helpful

Exchange rate type P is replaced with M

Hi,
We are using CATS for time booking and the process is as follows:
1) CAT2 -> Hours booked.. Lets assume: 9 HRs
2) CATS_APPR_LITE - > Time sheet approval -> Approved 9 Hrs
3) CAT9 -> CATS data transfer to cost object(PM order) -> During this transaction, system does calculate the amount needs to be tranferred based on price maintained in KP26 and hours booked. Lets say KP26 price is $100. That means controlling document will be generated for amount $900.
Note - As per system configuration, exchange rate type will always be P whenever CATS posting will happen and controlling document gets generated. That means, currency conversion will take place based on the exchange rates maintained for type P.
So as per business requirement, we have done an enhancement to the existing CATS process:
Price is manually determined at the time of CAT2 and same will be considered till the controlling document is generated. So, no price determination during CAT9. Therefore the strategy says it is a manual determiination of price and the Exchange rate type is determined as "M" and thats an issue because we do want to pass manual price but we want Exchange rate type as "P" as well.
Is there any way out or settings availabe in SAP or any user exit or an enhancement to achieve this functionality?
Thanks,
Aby

Hi Aby,
I believe these notes contain good information for this case:
1073979 (which I think is already in your system and therefore this behavior).
and
691613 (which explains the strategies)
Also, please check the entry you have defined in the transaction OKEV.
There, the system will make the translation depending on the
exchange rate defined.
I hope this helps.
Regards,
Lucas

Exchange Rate Type 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

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

Exchange rate type & pricing procedure

Dear all,
I new defined an exchange rate type and assigned it to a specific customer, but PR00 missing when creating sales order.
So could you please make me clear about the relationship of exchange rate type and pricing procedure?
Moreover, How the system determine the exchange rate when creating a sales order? I found it's not the rate in the rate type assigned in customer master data.
Thanks so much.

Hi
There is no relation with Pricing procedure and Exchange rate.
Check the condition records of PR00 in VK12.
Exchange Rate determination
The system proposes a valid exchange rate from the table where exchange
rates are maintained. You can change the rate in the sales document. If
you change the exchange rate, the system recalculates prices for the
entire document. (Info from SAP Help)
Hope it helps you
Regards,
Ramesh
Edited by: Ramesh on Apr 2, 2009 8:08 AM

Pricing exchange rate type

Hello All,
Please expalin the on pricing exchange rate type in copy controls.
Copy from sales order
Price exchange rate = Accouting rate
Exchange rate determination according to billing date
Exchange rate determination according to pricing date
Exchange rate determination according to current date
Exch.rate determination accord.to date of services rendered
User will change the bill to party during billing based the bill to part currency will be determined at billing header.
But currency in sales order is INR and if user changes the bill to party(Foreign) currency in billing will be EURO
and user want to cancel the invoice cannot able to cancel because currency from sales order to billing is different.
How can we fix the issue. Can we use any of the above mentioned pricing exchange rate types to fix the issue.
Best regards,
ramesh

Hi
See SAP Note 22781 - Exchange rate in accounting, exchange rate type, problem C. It explains how to work the data en table TVCPF (data mantained in tcode VTFA). I suggest to set a break point in this coding and debug it to undertand how it works.
I hope this helps you
REgards
Eduardo

Pricing Exchange Rate Type in Copy Control VTFL

Hello,
We have Pricing Exchange Rate type in the Copy control from Delivery To billing ( VTFL) at item level.
This Exchange rate type is used for price determination in the billing document. there are several options available for this field.
A     Copy from sales order
B     Price exchange rate = Accouting rate
C     Exchange rate determination according to billing date
D     Exchange rate determination according to pricing date
E     Exchange rate determination according to current date
F     Exch.rate determination accord.to date of services rendered
Normally the Exchange Rate in the accounting document is determined based on the rate available in the system on the billing date.
now what is the difference between "B" and "C".
I could not find any change in the way it processed when i put B or when i put C .
Does any one know what is the impact on the system if we select B or C. In what scenarios we use "B" and in what scenarios we use "C"
Your answers are much appreciated.

Hi,
what is the difference between "B" and "C".
B Price exchange rate = Accouting rate
This value is used to determine the EXCHANGE RATE based on the Rate maintain in the ACCOUNTING DOCUMENT TYPES in OBA7 Transaction code irrespective of what determined in the ORDER
C Exchange rate determination according to billing date
This value determines the EXCHANGE rate based on the Rates maintained in the Transaction code OB08 and get the values from the table TCURR based on the BILLING DOCUMENT DATE.
regards,
santosh

Exchange Rate Types Used In What Transactions

Hi Experts!
I was inquiring on if there is a way to see all exchange rate types ("M" and alternative exchange rate types), with respects to where they are used, posted, and most importantly, what all transactions use them. The exchange rate types we use are M (system), Z1 (custom), and 0011 (custom). Even if there is a SAP note, on this, that would be helpful too. Urgent! Thank you for your time!
WC

Hi Will,
Execute transaction code OB07 to see all the exchange rate types within your system.
The following should help you to understand where they are used and which transactions used them.
In planning, exchange rate types are used to specify exchange rates used for different purposes at the same time in the system. Existing entries may not be deleted.
When exchange rate conversions take place between many different currencies, using a reference currency can simplify maintenance of exchange rates. For the exchange rate types concerned, you then only have to specify the exchange rates in relationship to the reference currency for all currencies. The SAP R/3 System then carries out all exchange rate conversions in two steps, using the reference currency.
As well as a buying rate "G", you can also maintain a selling rate "B".
The buying rate is that under which the average rate "M" is recorded.
When maintaining a buying rate, enter the appropriate currency type for the average rate. This reduces the amount of work required in the conversion table.
The selling rate is that under which the average selling rate is recorded.
The user need only maintain the conversions for the average rate. The conversion occurs by determining the average rate and then adding the difference between the rates to this rate.
If an entry for a currency conversion is missing, the indicator Invert ensures that the reversed currency relationship, should one exist, is available for the conversion.
Standard settings
The standard R/3 System includes exchange rate type P (standard translation for cost center accounting).
Note
When you create a controlling area, the SAP R/3 System creates version 000 automatically for 5 years. Rate type P is defaulted.
The R/3 System uses rate type M for currency conversion during postings and clearings of documents.
Recommendation
Before creating your own exchange rate types, check those offered by SAP and use them if appropriate.
I hope the above helps.
Do not forget to award the points please.
Regards,
Jacob

AP- Why exchange rate type between Post invoice and Post payment is differe

AP- Why exchange rate type between Post invoice and Post payment is different ?
Hello,
I have question
when post AP invoice , document type KR
document date = 11.12.2009
posting date = 31.12.2009
entry date = 05.01.2010
this document using exchange rate type B (standard translation at bank selling rate) on 31.12.2009 (use posting date )
but when post payment for above document,document type ZP
document date = 25.06.2010
posting date = 25.06.2010
entry date = 24.06.2010
this document using exchange rate type M (standard translation at average rate) on 23.06.2010
please answer
why do post invoice and post payment use different exchange rate type?
and why at payment donot use posting date for get exchange rate ?

Nanas,
Sorry if im not being clear...
My point is: the difference rates customization for payments is done at FBZP.
At Paying Company Codes, you have 4 flags for exchange rates differentes.
At Control Data look:
*Do not Post any Exchange Rate Differences:
If the indicator is not set, the difference between the exchange rate at the time of posting and the exchange rate at the time of payment is determined for items which are posted in foreign currency. The payment program uses the translation rate in the currency table in the system for this purpose.
*No Exchange Rate Differences for Partial Payments:
Has the effect that the payment program for partial payments (requests for payment using transaction F-59) does not post exchange rate differences.
*Processing of Bill of Exchange Payments:
*Separate Payment for each Payment Reference
Regards
Bruno

User-Exit to modify exchange rate type for Accouting document

Hi,
My requirement is as follows.
I am creating an incoming invoices which in turn creates an accounting document.
The document currency for the accouting document is different from the Company code currency. In such a case, the "Exchange rate type" provided in the customization of the "Accouting doc type" is picked up and the exchange rate is determined for the conversion.
I need some user-exit/badi/bte where I can override default "Exchange rate type" for my accouting document.
Regards,
Abhishek

Provide the exchange rate in the BAPI to create the incoming invoice document.

Different Exchange rate type is picked while creating PO

Hi All,
We are maintaining daily exchange rates under exchange rate type "M" for currency GBP to INR. We have also maintained exchange rate type "ZCIG" but we are not maintaining daily exchange rates under this exchange rate type.
Still system is promting us to maintain the exchange rate under exchange rate type ZCIG instead of "M" while creating Purchase order. Becoz of this error i could not save the PO.
Please guide me on this issue.
Thanks
Sonal

Hello,
Could you please let me know how you have solved this problem.
I want a particular exchange rates for a particular vendor posting.
Thanks,
Srini

Mass update exchange rate type (not rate) in open sales orders

Hi all,
Our requirement is to update the exchange rate type at sales order header (VBAK-KURST) for all open sales orders with a new type created. (Z001). This field does not appear in MASS transaction for sales orders despite being present in the structure MASSSDHEAD.
This field cannot be located even in VA02 transaction (I am not sure if standard SAP masks or shows this field at header; I also can't find any transaction variants assigned).
Can anyone suggest how this field can be updated for sales orders either individually or in mass mode.
Regards,
KC
SAP SD

You are correct in indicating that Exchange rate type field is not seen in Header data of sales order. I checked screen layouts for various screens for sales order data and this field is not suppressed. The only reason could be that this field is not used in sales order screens
If you are interested, you could also check in the following way
1. Go to SE11, enter database table as VBAK
2. Once inside data dictionary table, click where used list button, select programs and screens and execute
3. click continue (don't select background)
4. now you would have list of programs and screens, this table is used
5. now start another session and go to transaction SE51
6. indicate program name as SAPMV45A and screen numbers as listed in step 4. you can check all screen numbers to see whether Exchange rate type field is listed in sales order layout.
7. Of particular interest would be screen number 4311 as this contains Financial accounting data & 4303 Billing data
8. you can check screen layout for screen 4311 & 4303. you would see Exchange rate type field is not indicated.
9. in case you could find this field in any screen, you could ask your ABAP consultant to add this field in the layout screen.
Hope this answers your question

Exchange Rate type determination in PO

Similar Messages

Maybe you are looking for