Exchange rate maintenance

HI gurus,
I have fixed the exchange rate as  40 (say) in the PO header.
Now when I do Migo after miro, it throws the following error;
Enter rate USD / INR rate type B for 06.09.2007 in the system settings
Message no. SG105
Diagnosis :For the conversion of an amount into another currency, an entry is missing in the currency conversion table.
Procedure
Add the missing entry in the currency conversion table.
Execute function
You can then continue to process the commercial transaction.
When execute this function, it goes to OB08.Even after giving the rate also for 6th Sep,unable to post MIGO, Please help .
Thanks
Kumar

Hi James,
The SAP NetWeaver MDM discussion forum is not the right for your query. Please check the appropriate forum. You may try "ABAP Programming".
Best regards,
Markus

Similar Messages

  • Opening period & Closing, Exchange Rate Maintenance in PROD

    as we all know the production is non-modifiable system, how we able to maintain the period & closing, Exchange Rate Maintenance in system. as the system give message "non-modifiable

    Hi,
    to continue to above suggetions, if you are not having authorisation in prod, then you close the period in quality server with new request and transport it to production. This is with the help of basis guy. make sure that the quality system is updated with production.
    This will helps to solve your problem.
    Assign points if useful.
    Raghav

  • OBA1 exchange rate maintenance for the new accounts

    Dear All,
    The following three bank G/L accounts 1833280, 1833285 and 1833288 have been created in India Charts of accounts IN01 and extended to company AE10.
    The G/L accounts can now be used in AE10.
    Now tell me how can I make OBA1 exchange rate maintenance for the new accounts.
    Please share your valuable opinions with me.
    Thanks a lot in advance!!

    Hi,
    The relevant transaction in OBA1 for the bank accounts is KDF.
    Double click on KDF, a new screen will open up, where you do the following:
    You enter the bank GL account here.  If the account is to be differently handled at the level of the currency and currency type then you can further limit the exchange rate difference based on these 2 parameters.
    Once you have entered the bank GL, save and then double click the bank GL account.  A new screen will open up where you define accounts for the following:
    The accounts below will carry the forex gain loss that you when you clear foreign currency transactions.
    1.  Exchange Rate difference realised:
    Loss                 XXXXXX
    Gain                 YYYYY
    The accounts below will carry the difference while valuating you open items for
    2.  Valuation:
    Val.loss 1           XXXXXX
    Val.gain 1           YYYYY
    Bal.sheet adj.1      ZZZZZZ
    The accounts below will carry transaltion losses.
    3.  Translation
    Loss
    Bal.sheet adj.loss
    Gain
    Bal.sheet adj.gain
    Cheers...

  • Exchange Rate Maintenance for two company codes..

    Friends,
    My client is having two company codes
    X = India
    Y = USD
    US Company code is live for the last few years and India Company code is created recently and the same is live now.
    Now when the US company code creates Purchase Orders /  Scheduling agreements, the following error is encountered.
    "Enter rate INR/EUR rate type M for 31.07.2008 in the system settings.:"
    Now my question to the forum is that
    1. If we maintain the exchange rates in OB08 will there any other effect ?
    2. Is this error because One more company code is added to the same client which is operating in INR ?
    3. When US Company code is not all transacting with India Company Code why is this error encountered.
    Appreciate if some one can explain the pros and cons of this please. I am basically an MM consultant and I would also like to know the FI impact in this scenario, hence posted this question in FI forum.
    Regards

    Hi,
    At the time of initial installation SAP would make EUR as base currency, so any new company code you create needs to have an exchange rate defined to the base currency EUR.
    In your case you can define exchange rate to EUR and process PO, as per my knowledge there will not be any impact of this.
    Thanks,
    Ramesh.

  • Currency Exchange rate maintenance

    Hi all FI Master,
    My local currency is in GBP. I maintain foreign currency exchange rate like USD to GBP, SGD to GBP and so on. My question is do I need to maintain the exchange rate in the other way round (like GBP to USD)?
    Secondly, if my vendor bill me is foreign currency USD, and I pay in foreign curr SGD, do I need to maintain the exchange rate from SGD to USD?
    Thank you.

    Hi Cire,
           The Answer depends on your settings for the Exchange rate type
    (SPRO > General Settings > Currencies > Check exchange rate types)
       1)    No if  Invert flag is set for the exchange rate type.
              Yes if flag is not set.
       2)    No if you have specified GBP as the Ref.crcy.
              Yes if no Ref.Crcy is specified.
    Kind regards

  • Dual Exchange Rate Maintenance

    Dear All,
    I have one issue on exchange rate . our client do import and export.
    So custom department fix the exchange rate at the start of  every month which is applicable for the full month.
    But in case of receipt or payment  in bank we have to consider the current exchange rate
    So how we can maintain 2 rate in system.
    Example
    Import Rate from 01.04.2010-30.04.2010  is  1 USD = 40INR
    Payment and receipt rate on 1.04.2010 is 1 USD = 46 INR
    Payment and receipt rate on 2.04.2010 is 1 USD = 45 INR and so on.
    Regards,
    Shayam

    Hi
    You can create another exchange rate type and maintain the monthly fixed rate in that and assign it to all relevant doc. types.
    However, for bank related postings, you can use exchange rate type M in which the current exchanges needs to be updated at regular intervals.
    Regards

  • Maintenance of Exchange Rate

    Hi All,
    We are facing a problem with maintenance of Exchange Rate.If someone can give me a good suggestion i will be happy.
    The scenario is : we are maintening 2 companies(A & B) in our server now and there is a proposal of adding another company has come. Now the problem is Company A and Company B have 2 different currencies so we were maintening the exchange rate without any problem but now the 3rd Company C has the same currency as Company A.So we are in a position how to maintain the exchange rate between these 2 companies? Both companies have a different day of closing..so please suggest me with a good idea.
    Thanks in Advance
    Ajoy.

    Hi All,
    Thanks for the immediate reply but my problem is different.
    Company A - USD
    Company B - EUR
    Company C - USD - New addition
    In this case we cant do the year end or month end closing for these 2 companies on the same day.There will be overlapping while maintaining the Exchange rate during the Closing operations.Both these companies will be maintaining the same currency(USD) and exchange rate for that currency.Is there anything to avoid this or any other option is there to maintain 2 different exchange rate for same currency?
    Thanks in advance
    Ajoy

  • "An Exchange Rate Does not Exist" error while creating an item

    Hi..
    Pre-requisites: RMS is installed without base data
    We are trying to create an item in RMS by filling the required information in "Item Maintenance window" and "Supplier details" screen. After this is done when we select the "Retail by Zone" link and the application prompts an error message : "An Exchange Rate Does not Exist", and all the values in "Retail by zone" screen are not populated. How do we ressolve this?
    Thanks in Advance
    Yamini

    Also, make sure that if a currency has a rate entry for example, 01-jul-2010, then make sure that ALL other currencies have a rate entry for 01-jul-2010, even if the rate has not changed for other currencies - a little trick I learned from an Oracle consultant.
    Alan

  • Exchange rate issue at PO & Invoice area

    Hi Gurus,
    I have a scenario, Creation of PO time i'm getting EUR conversion rate 1.345 to an USD rather than to get 1.502. Prior to this i have checked the OB08 there my rate shows 1.502 for the particular period but by default it's pulling the conversion rate as 1.345 which wrong right now, if the user not know abt this conversion rate then it become an issue.
    How to restrict and get it correct rate, what could be the reason plz.
    Could any body through some light on this issue plz.
    Points are avail, thanks in advance.
    Rgds,
    Vyas

    Hi All,
    This was happend bcoz of alternative Ex. rate existing for "M" Ex. rate as "EURX".
    At Ex. rate table maintenance, I take out the 'EURX'  rate for 'M' than the problem was solved.. it's picking the 'M' Ex. rate promptly..
    You can see at query: M exchange rate is over riding by Eurx... in sdn.sap.com, it gives more understanding.
    Thanks for your valuable inputs..
    Vyas

  • Exchange rate diff. influencing the available cost of WBS-element

    Hi all,
    here is a intricate problem I need help to solve. I am not so very experienced withon CO/PS, my main competence is within PM. This issue involves PM/MM/PS and CO so I am not sure if this is the correct group to post to, but I give it a try..
    In PM (Plant Maintenance) workorders the u201DPlanned Costu201D is calculated.  Exchange rate type for the u201DPlanned costu201D is picked from the CO Cost Version u201D0u201D that uses exchange rate type u201DPu201D. This is a exchange rate type that have one yearly fixed exchange rate. The actual costs are posted with exchange rate type M, which is daily updated.
    The Planned cost in the workorder is a part of the u201DAssigned Costu201D that are influencing the available budget on the WBS-element. u201DRemaining/Residual order planu201D.
    In cases where the PRQ/PO are created in other currency than the Company code currency we have a problem:
    The difference in exchange rate are causing the u201DAvailable budgetu201D to be too low u2013 and the only workaround I have found is to decrease the planned cost in the WO to release the available cost for the Budget. (make the available cost higher )
    Does anyone have an idea how to solve this?
    - I have thought of setting the exchange rate type for the planned cost to be the same as for the actual costs u2013 but it is not recommended to change the exchange rate type in CO for cost version u201D0u201D and not a good ide to change the exchange rate type for actual cost eather. This will also not solve the problem of exchange rate difference caused by PRQ/PO beeing created for a whole year for varying exchange rates.
    - Is there a way to exclude the u201D Remaining/Residual order planu201D from the u201DAssigned Costu201D? And what consequences will this have? Only cost from PRQ/PO will appear? (Since internal material (reservations) and internal hours not triggers a PRQ/PO)? I see there is a transaction CJE5 where you can exclude the u201D Remaining/Residual order planu201D from the u201DAssigned costu201D u2013 but I think this will only exclude it from beeing shown in the report S_ALR_87013558?- not from the calculation of available cost at the WBS-element?  which is what I need. (see Note 668240)
    -Is there any u201DExchange rate differenceu201D setting in the customizing u2013 how exchange rate difference are treated for PM orders? And will this help my problem?
    Best regards
    Ellen

    Hi ,
    try this way...
    Go to T-code>CJE0>Enter CO Area-->and execute the report 12KST1A  ->in the selection screen -->
    go to menu -->system -->status check the program name and ...copy
    next go to se38 and copy yhe above program name and execute and use submit report with selections,,,,
    Prabhudsa

  • 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 expression Direct and Indirect qutation

    Hello,
    Please can you explain whether there are any issues or risks in
    switching the Exchange Rate Types used in SAP to allow inverted rates
    to be used - or any reasons why it was designed not to have inverted
    rates switched on. I think to reduce the maintenance of the foreign
    exchange rate table, it doesn't make sense, for example, to enter both
    a GBP/USD rate and a USD/GBP rate
    The other issue is that my client publish internally the month-end
    rates as direct quotations - i.e. 1 Israeli New Shekel (ILS) = 0.1584
    British Pounds but somehow, the rate used in the revaluation program is
    different. This could be because a rounded reciprocal of this rate is
    entered, or the rate is entered with a different number of decimal
    places. If only direct rates are entered, and these are the ones our client
    publish, there is hopefully a better chance that the revalued figures
    are in line with what client expect them to be.
    Thanks in advance for your help.
    regards,
    Satya

    2

  • 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

  • To maintain foreign currency exchange rates

    Hi,
    Please help me with this scenario.
    I want to maintain  foreign currency exchange rates.Kindly tell me the process to maintain these rates. and also please tell me that is their any feasibility to maintain exchange rates on daily basis.
    Regards,
    Pavani reddy

    Hello,
    you can also use currency worklists in order to maintain exchange rates on daily basis. In order to enable this functionality you have to maintain the following configuration:
    1) Define Currency Worklist using the following path: SAP Netweaver - General Setting - Currencies - Define Worklist for Exchange Rate Entry (specify the name of the worklist, short description and maintenance interval);
    - assign exchange rate to the worklist using the following path: SAP Netweaver - General Setting - Currencies
    2) Assign Exchange Rate to the Worklist (please specify your exchange rate type, from and to currencies, the name of the worklist previously created as well as quotation type).
    3) In order to maintain exchange rates you will have to use t-code TCURMNT (you can also find this transaction under standard SAP Menu (Fin. Accounting - GL - Environment - Current Settings - Enter Exchange Rates using a Worklist).
    In my opinion, this t-code is more user-friendly than the standard OB08. But it's now up to you to decide whichever to use.
    Best regards,
    The Wirtschaftsmann

  • Reporting multi-currency on reports, without hardcoding the exchange rates

    I've seen this problem posted in a few different spots, and the general answer is, reporting only reports in a single currency per report. Unless you do some calculations in a column to get a new currency value.
    Problem... 1. we dont really want to hardcode exchange rates into every report that needs the conversion
    2. If rates change often there could be a painful maintenance issue to update all those reports
    So here is a solution I used for a customer, that worked a treat.
    [http://www.synergility.com.au/content/faqs/49/77.html|http://www.synergility.com.au/content/faqs/49/77.html]

    Hello,
    I can't find Oracle provide a tech note (749419.1) documents to metalink, Could you please send me?
    and I cant prepare this report beceuse some information missing for example it doesnt work rate prompt field and fx revenue field.
    please you can send to me step by step information?
    thank you for hep

Maybe you are looking for