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 PM

Hi
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

Similar Messages

  • 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,
    Jody

    Hello 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

  • 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,
    Nirav

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

  • Exch.rate type

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

    Hi 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

  • 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

  • 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

  • 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

  • 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

  • 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

  • Why exchange rate type "EURX" is used ?

    Dear all,
    I post with FB65 a document with currency EUR.
    The local currency is THB and group currency is CHF.
    The document type doesn't have specific exchange rate type ==> by default the type "M" is taken.
    But, when I post a document with currency EUR, the system doesn't take the type "M", but the type "EURX".
    In this case, I don't want to use "EURX", but I want to use "M".
    How can I do ?
    Thanks for your help
    Best regards

    Please check the configuration in OBBS.  You would have specified an alternate exch. rate type (EURX) for exch. rate type M for the currency pair in question.
    Please refer to the following notes as well.
    https://service.sap.com/sap/support/notes/139553
    https://service.sap.com/sap/support/notes/123819
    PS: OB22 would not tell you anything.

  • PO Condition types exch rate

    Dear All,
    My company code currency is INR. We have defined a PO with condition types(currency EUR) and maintained the exch rate(different from OB08 rate). While doing GR, system is picking Spot rate (OB08) for Material line items and for condition types, system is taking PO exch rate.
    Not able to understand why system is picking different exch rates for material & condition type lines.
    Can some one please clarify this?
    Regards,
    Ganagdhar

    Please review the following notes
    128    Exchange rate differences between GR/invoice
    331910 MR1M, MIRO: Postings in foreign currency/local currency
    191927 Posting logic: GR for foreign currency PO

  • Exch.rate-Accounting is fetching of typ 'M' insted 'P' VF01 for Sales Order

    Dear Experts,
             I'm facing some issues during creation of 'VF01' for a sales order(For Repairing Billings).Previously we are creating 'VF01' against OBD for local customers inside India,but we have started  doing for Outside India Customers.For OBD the rate type  and exchange rate-accounting value  is picking perfect (Type-'M') and the most recent exchange value of type 'M'..But for a Sales Order, As the exchange rate is already we mentioned as 'P'(Checked from 'VBAK' table,In customer Table 'KNA1') also in header the exchange rate is showing type'P' ,but picks the latest exchange rate value of 'M' type from 'TCURR' table .
    Process Flow.We goto first VF01.
                           Give Document no and press enter.
                           Then we move to Goto->header->header to check the exchange rate type and exchange rate-accnt.
    There exchange rate type is showing 'P' but Exchange value is picking of type'M'.
    .Why this problem arises and how to overcome from this please provide me a solution.In copy-control everything is perfect.
    So Please help me in this regard
    Thanking you

    Dear Sir,
                Thank you very much for your kind reply.
                 As per your answer I've changed moving average price in Material Master But still the Problem is not solved.
    Actually we r facing problem during Invoice creation with reference to sales Order .At that time the Exchange rate is picking of type 'M' in the Header though in the item Exchange rate is picking of type 'P' (which one is Correct).
    But in case of Creation of Invoice in reference to OBD Both in Header and Item the exchange rate is Picking of type 'P'.
    So please help me out in this regard.
    Thanking you
    Prabhu

  • 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 M  not  picked in  FB60  foreign currency entry

    Hi
    My  local  currency is   USD.  I   have  defined  exchange rate  for   ' USD  and  EUR   '    for  exchange     type  M and  type  EURX.  
    In  FB60,  system picks  the  exchange rate  defined  for  exc. type EURX,   but   I   want it to  pick  exch. type M.
    Also i   have  set   exch type  M  in  docu  type  KR.   Still  it  does not  pick   exc type M.
    Pl  advise
    Thanks
    kamala

    I am thinking that most likely you have specified EURX as Alt. ERT (alternate exchange rate type) for exchange rate type M for the currency pair USD:EUR in IMG node 'Define Translation Ratios for Currency Translation" (T Code OBBS).  Remove it and retest FB60; it should pick the M rate.

  • 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

Maybe you are looking for