Currency conversion possible before SPS9 - Functional enhancement document

Hi,
Functional enhancement document(https://websmp201.sap-ag.de/~sapidb/011000358700004483762006E) says "change of currency translation settings during runtime by end-user (SPS10)".
But if using varialbe that is asked after executing query, it seems to be possible.
So I cannot understand what this description means, is it only about the context menu?
Kind regards,
Masaaki

Hello Mr. G. Lakshmipathi,
Thanks! I'll try this function module READ_EXCHANGE_RATE.
However, I think this issue is not really related to the exchange rate. The amount conversion from USD to JOD happens correctly based on the current pricing forumla that we are using i.e. amounts in JOD have 3 decimals after conversion from USD, but when they are stored in pricing structure, the last decimal is truncated as the currency against the 3 condition types is USD (USD has 2 decimals). Hence, the amounts have 2 deicmals.
Thanks,
Amit

Similar Messages

  • How to add an entry in the currency conversion table

    Hi all,
    I am loading data to ODS from 2LIS_11_VAITM. i am getting an error as below in a record.How do we enter a missing entry in the currency conversion table? Please help.
    Kind Regards,
    Shanbagavalli.S
    Enter rate EUR / EUR rate type 00000000 for 2200016564 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.

    Hi,
    Goto RSA1 -> source system -> R/3 source system -> transfer exchange rates.
    Bye
    Dinesh

  • Currency conversion type by customer exit variable doesn't work

    Hi all.
    In my query I need amounts by quarter, applying quarters last date rates as currency conversion.
    Query has Year parameter. Based on this parameter, by customer exits I calculate every quarters last date and use them as currency conversion types.
    The problem is that query DOESN'T APPLY currency conversions!
    I checked TCURR table - currency conversions do exist for applied days
    I checked my customer exits - the date calculation works fine
    I suppose where is something wrong in query processes (customer exits/currency conversions) sequence before running it.
    Someone knows anything 'bout that?

    Check these docs.. and check again.
    [Creating Currency Translation Types|http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6813e07211d2acb80000e829fbfe/content.htm]
    [Use Variables for Currency Conversion|http://www.scribd.com/doc/7061035/How-to-Use-Variables-for-Currency-Conversion]

  • Error in Currence Conversion..............

    Hi All,
    When , iam trying to rum pay roll i'm getting an Currency conversion error can any one guide me please...
    THE ERROR IS ............
    Enter rate INR / FRF rate type M for 01.01.2008 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
    Thanks in advance,
    Vinod.

    Hai
    SM30,   V_TCURR
    maintain an entry for currency exchange type for M, for the relevant currencies... for the date..
    Edited by: Ram Manohar on Apr 1, 2008 12:25 PM

  • Currency conversion issue in SPM. We are getting incorrect results with SPM conversion function from one of the document currency to USD.

    Currently we are using SPM 2.0 version and we have been facing currency conversion issues.
    Please help me in following aspects.
    1) Where actually currency conversion happens in SPM. Is it the global program which does the conversion or other way.
    2) We have conversion issue for one of the currency where conversion function is giving incorrect results when converting from one of the document currency to USD. here The respective document currency is considering the 1:1 ratio with Dollar which is actually incorrect.
    3) We have verified in both BI side(currency tables) and even ECC side.
    Please help me in understanding this issue and let me know if you need more information on this.
    Its an production issue and appreciated your immediate inputs.
    Thanks
    Kiran

    Hi Arun,
    The following information may be helpful to you.The SSA_HELPER_PROGRAM has options regarding currency settings.
    EXCH_RATE_TYPE: This flag governs the exchange rate type which will be used for currency conversion in data management. For example if RSXAADMIN contains an entry EXCH_RATE_TYPE = „ZSPM‟ then the conversion type used for currency conversion is ZSPM. The default value for the exchange rate type is „M‟. More details can be found in the note 1278988.
    CURRENCYCONVERSION: By default data management converts all the measures in transaction currency to reporting currency and copies over to the corresponding measure in reporting currency. If the measure in reporting currency is already available in source it might be desirable to disable the currency conversion. To disable the conversion you can make an entry CURRENCYCONVERSION = „ „ in the table RSXAADMIN. This can also be achieved by running the program SSA_HELPER_PROGRAM with the option DEACTIVATE_CURRENCYCONVERSION. The conversion can be reactivated by running the same program with option ACTIVATE_CURRENCYCONVERSION.
    UNITCONVERSION: Similar to above. To deactivate unit conversion you can use the program with option and DEACTIVATE_UNITCONVERSION and to reactivate ACTIVATE_UNITCONVERSION. By default both the conversions are switched on
    EXTERNAL_CURRENCIES: Normally most of the international currencies are stored with two decimal places however certain currencies do have 0 and 1 decimal place too. For example JPY has 0 decimal places. SAP internal format stores even these currencies with 2 decimal places and at the time of display it changes the value to right decimal places. In case a file from external source is loaded to SPM it might have the format with 0 decimal places in the file. To convert it to SAP standard format post processing needs to be done on this value. If that is the case you can set the flat EXTERNAL_CURRENCIES = „X‟ in the table which will enable the post processing for these values. This flag can also be set and reset using the helper program using the option TURNON_EXT_CURRENCY_FORMAT and TURNOFF_EXT_CURRENCY_FORMAT.
    Kind Regards,
    John Harris
    Senior Support Engineer, SAP Active Global Support

  • Multiple currency conversion via one variable possible?

    Hello,
    following problem:
    I have a report which contains different currencies (e.g. EUR, CHF, etc.).
    In this report we have different calculated key figures (on cube level).
    Each key figure have different currency conversion (maintained in rrc1).
    Question: Is it possible, when the user starts (execute) a report one variable
    pops up e.g. display all key figures in USD <b>all different currency conversions will be reflected</b>? In the system I don't know where.
    Any idea?

    Ok, I find a solution by myself.
    In the AdminInfo object is a property called MultiCurrencyCheck. When this is set to cc_NoMessage, I can save the journal entry.
    If you want to change this setting in Business One:
    Select Administration --> System Initialization --> Document Settings --> Per Document tab --> Journal Entry tab
    There is a check box "Allow  multiple currency transactions". The description is wrong and it should say "Block multiple currency transactions", like the other. When it is unchecked, I can make multiple currency transaction otherwise not.

  • Required Document on Currency conversion Types

    Hi All,
    Can any body provide me link or send Document on Currency conversion types
    [email protected]
    Regards,
    C.V.
    Message was edited by: P.C.V.

    I sent to you an useful how to..
    Regards,
    Sergio

  • Currency Conversion Document

    Hi Friends
    I have been given a project to learn about SAP currency conversion. Can anybody please provide any documentation for Currency conversion from SIT to Euro and Old Turkish Lira(TRL) to New Turkish Lira (TRY).
    Thanks
    SAP FICO

    Hi,
    Hope the below links are useful:
    <u>http://www.sap.com/services/consulting/servicecategories/landscapeoptimization/currencyconversion.epx</u>
    <u>http://www.behnmeyer.com/bm_articles.asp?show_article=14</u>
    Regards,
    Hemanth

  • 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

  • Currency conversion with query selection mask and InfoObject 0Curtype

    Hi,
    question to following scenario:
    in the data source is an column with the currency type. This currency type column contains values like
    10 = company code currency
    20 = account area currency
    So for each data set in the table is an assignment of currency types.
    In the cube is an InfoObject called 0Curtype (for currency types 10,20,30 ...).
    In the BEx Query should a filter or selection be possible before the whole data is displayed.
    The user can select in which currency he wants to display the data. When he selects the 10 the whole data is displayed in different currencies which are available because its local currency (Euro, Dollar etc.). By selecting 20 the whole data is displayed in Euro.
    Does anybody knows how to achieve that? Is there any function module availabe which is provided by SAP and it is available for use?
    Thank you in advance!!!

    Hi There:
    You have two options available.
    One you can define currency conversion variable in transaction RSCUR. Then use this currency conversion variable at query run time using a formula Key figure and go to Conversions tab and select this variable. Then at query run time the query will convert your key figure from source currency type to target currency type. But this can significantly impact your query run time because the query will calculate this at query run time.
    The second option is to use a standard SAP function module CONVERT_TO_LOCAL_CURR in the back end and store this key figure in the back end during data load. This way the query will run faster for you. The difference is significant in my case.
    Good luck.
    Let me know if you need more information.
    MP.

  • Functional  Specification Documents for SAP Sales and Distribution

    Dear Gurus,
    I am having the problems of Invoice Output..... the default out put generated by the SAP is completely different from the hard copy of the Invoice of the Client. ppl say that I have 2 take the help of ABAPers to define the smart forms for the invoices of different company codes.... i had conversation with the ABAPers.... butthey are  asking the format, wht ever the change we are  looking for..... I am not be able to get the exact format.... how 2 provide this to ABAPers in FS format.
    can any one pls send me ( or provide me the link to download the same from the SDN website) these Functional Specification Documents for Sales and distribution.
    Wishes,
    Abhishek

    Hi there,
    1st try to understand what is a functional specification doc before asking for it.
    Functional specs is a doc in which you include what is the business requirement. If it requires a change to change to existing configs / code, then you will give the progs & the location where you will need to change. If the requirement is a totally new one, then yuo will explain the requirement in detail & possibly give the progs / code if there are any.
    In your case, your client has a specific invoice format which is different from which SAP gives, in such cases, you will need to define a new Invoice output for eg ZINV. Define it as a print output. You will need to define a new print prog for the new output in which you will call smart forms to define the layout & fields.
    Ask your business user to send the invoice copy which he has. Scan it & include it in the functional specs which you prepare. Mention all the fields which you want in the layout. Ask the ABAPer to code the invoice format in the same way. ABAPer is free to define any convinent name as per the guidelines (which he will be aware). You will need to assign that in the form routines of the output.
    As a functional consultant you will need to give the field mappings (from where you get the data) for all the fields which you wish to print in the output. All that should be included in the func specs.
    So there is no standard func specs that you can follow. Each func specs varies on the requirement. So dont ask these kind of questions in SDN forum. If you dont know how to define func specs, ask how to define. Dont ask people to send the sample func specs. Thats against the rules of conduct.
    Regards,
    Sivanand

  • Balance is not zero due to currency conversion

    Hello experts,
    could you please suggest me in a solution of the following issue? I use f-28 Incoming payment transaction. Document currency is usd, while local currency is euro. When currency conversion takes place rounding happens and instead of e.g. 3555,14 euro 3555,15 come up. But it appears from time to time due to rounding. Because of this, debit sum is not equal to credit sum (0,01 in our case) and consequently the balance is not zero. So, system displays the message Message no. F5060 "Posting is only possible with a zero balance; correct document".
    What are the ways to correct this issue?
    Regards,
    Alex
    Edited by: Aliaksei Klimovich on Nov 4, 2011 10:06 PM

    Hi,
    I checked OBY6 and the check box was already set. I also want to add some details. In F-28 I use BTE 1020 in order to split amount in bseg-dmbtr field. Have a look please. We have to make an incoming payment 5500 USD - this is document currency. In our functionality we split this amount into 2 amounts: 4500USD and 1000 USD, then we convert 4500 USD and 1000 USD into EURO as euro is local currency. After those conversion I get 2 line items with 4500 USD and 1000 USD in euro in bseg-dmbtr field (4500\fursf eur and 1000\kursf eur, accordingly) instead of line item with 5500 USD (5500\kursf eur). At the end of BTE 1020 FM I get a table with line items some of them are splited as I wrote above. And because of currency conversion while splitting balance is not zero.
    The only idea is to spread those difference by open item positions.
    Regards,
    Alex.

  • Currency Conversion - difference in behaviour of NW compared to Microsoft

    Hi Everyone,
    When migrating from BPC Microsoft 7.0 to Netweaver 7.5NW SP01 we setup the same reporting currency conversion as we had before. A simple conversion of reporting currency from LC into EUR and USD.
    We noticed:
    - the currency conversion of accounts that had no RATETYPE used to convert at a factor of 1. In NW the system ignores these accounts and does not convert them...USD and EUR are blank
    SAP help states this should be possible...
    [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/7b/4479fd9b394314a257d92d9be6a71f/content.htm]
    - EUR and USD in Microsoft version are considered calculated members and do not allow direct entry into them in the input schedules (the CALC property is Y). In NW version, we can enter directly numbers in these reporting currencies, which makes it confusing for users and may lead to errors
    Did anyone experience any of these behaviours?
    thanks for sharing,
    best regards,
    Luis

    Hi Luis,
    This is off the top of my head, but my experience matches yours. I think you will have to add a new rate type to all your accounts that you want to convert with the multiplier of 1, and set up a business rule with
    [COPYLC]
    in the formula. Maybe I'm missing something, but it looks to me like the documentation is simply incorrect on this point in the Netweaver version.
    As far as EUR and USD, are you using the STORED_CALC property in your MS system? In my brief tests of this functionality I've never been able to get this property to have the desired effect (setting CALC=Y for a base member) in the NW version. You may want to open a message for the issue if this is what you were using on the MS side and it's not working for you. It would be nice to have it working.
    Ethan

  • User Exits for transaction VF01 before saving the billing document

    Can any one say is there any user exit which exits before saving the billing document since i want to check the net value of the billing with the net value of sales order so that it should not go beyond the total amount specified in sales order.

    J_3RSINV
    SDVFX001  User exit header line in delivery to accounting
    SDVFX002  User exit for A/R line in transfer to accounting
    SDVFX003  User exit cash clearing in transfer to accounting
    SDVFX004  User exit G/L line in transfer to accounting
    SDVFX005  User exit reserves in transfer to accounting
    SDVFX006  User exit tax line in transfer to accounting
    SDVFX007  User exit: Billing plan during transfer to Accounting
    SDVFX008  User exit: Processing of transfer structures SD-FI
    SDVFX009  Billing doc. processing KIDONO (payment reference numbe
    SDVFX010  User exit item table for the customer lines
    SDVFX011  Userexit for the komkcv- and kompcv-structures
    V05I0001  User exits for billing index
    V05N0001  User Exits for Printing Billing Docs. using POR Procedu
    V60A0001  Customer functions in the billing document
    V60P0001  Data provision for additional fields for display in lis
    V61A0001  Customer enhancement: Pricing
    These are the Exits Available in the Package
    Jus try finding which will suffice ur Requirement.
    Regards,
    Mithun

  • Currency Conversion Error

    In one of my report for Foreign Currency Conversion I am using the FM 'CONVERT_TO_LOCAL_CURRENCY'
    The foreign Currency value is 19,120 but in debugging it is shown as 191.20 but finally displaying in the output as 19,120.
    After converting, Local currency calculated is shown as 47397 in debugging whereas it should be 473.97 and is displayed in the output as 474.
    Please suggest any possible solution to avoid the rounding of the last digits.

    Hi marina,
    in this FM 'CONVERT_TO_LOCAL_CURRENCY'  is correct  . in your case you have  :
    CLIENT
    DATE
    FOREIGN_AMOUNT
    FOREIGN_CURRENCY
    LOCAL_CURRENCY
    RATE
    TYPE_OF_RATE
    READ_TCURR
    as import parmaters.
    Type of rate    M=Average rate G=Bank buying rate B=bank selling rate rate.
    check the long text inside the function module -> import parameters.. then set the value accoriding to that.
    regards,
    safel
    In one of my report for Foreign Currency Conversion I am using the FM 'CONVERT_TO_LOCAL_CURRENCY'
    The foreign Currency value is 19,120 but in debugging it is shown as 191.20 but finally displaying in the output as 19,120.
    After converting, Local currency calculated is shown as 47397 in debugging whereas it should be 473.97 and is displayed in the output as 474.
    Please suggest any possible solution to avoid the rounding of the last digits.

Maybe you are looking for