Issue regarding currency conversion

Hi Experts,
I'm having issue with currency conversion. Default report output values are displaying in 'EURO' and I had created a toolabar with currency conversion buttons. When this button is selected, values has to be changed into user select currency like INR, USD, AUD. Here im triggering with issues, all the values are converted into 0's. Total value is only converting for first time. From next time. its not converting. I'm using FM's  CONVERT_FOREIGN_TO_FOREIGN_CUR,CONVERT_TO_LOCAL_CURRENCY,READ_EXCHANGE_RATE.
Please provide ur solutions to solve the issue.  
Thanks and Regards,
Bharat

Hi ,
You can use this block of code..It is used in our project.
  data : l_rate type ukurs_curr,           "Exchange rate
         l_rate_type type kurst_curr,      "Type of rate
         l_l_fact type i,                  "Local factor
         l_f_fact type i.                  "Foreign factor
check local currency ,foreign currency local amount are not initial
  check foreign_currency is not initial and
        local_currency is not initial and
        local_amount is not initial.
Calculate exchange rate
    if local_currency = 'MXN' and foreign_currency = 'USD'.
      l_rate_type = 'MXNT'.
   else.
     l_rate_type = 'M'.
   endif.
*Call FUNCTION module to get exchange rate
  call function 'READ_EXCHANGE_RATE'
    exporting
      date                    = sy-datum
      foreign_currency        = local_currency
      local_currency          = foreign_currency
      type_of_rate            = l_rate_type
   importing
     exchange_rate           = l_rate
     foreign_factor          = l_f_fact
     local_factor            = l_l_fact
   exceptions
     no_rate_found           = 1
     no_factors_found        = 2
     no_spread_found         = 3
     derived_2_times         = 4
     overflow                = 5
     zero_rate               = 6
     others                  = 7
  if sy-subrc eq 0.
if l_rate le 0.
  l_rate = l_rate * -1.
endif.
Foreign amount
  if l_rate_type = 'MXNT'.
    foreign_amount = local_amount / l_rate .
  else.
    foreign_amount = local_amount * l_rate .
endif.
  endif.

Similar Messages

  • Issues performing currency conversion

    Guys while i am trying to run default currency conversion the package status shows as ( CANCELLED) not error or even completed which i came across for the first time. I checked all my DIM and data files. Can anyone help on this issue.
    Also i would like to know that how do you run 2 application 1.) finance 2.)  Rate in a single report(evdre)...
    Experts please HELP.

    Hey Nilanjan thanks
    That is not the issue with currency conversion. I checked whether it performed the currency conversion after the package status showed cancelled but it did not. Now i made some changes to the FX trans logic and it is showing an error that          ""Task name LOAD:""
    ""Error running default logic (Member "LC" not exist)"""
    I have maintained LC in data file as well as RPT currency DIM.
    Regarding the 2evdre in single report.
    When i create a report using =evdre() it opens a finance report if in my CV i have selected finance app.
    When i am in RATE app it creates Rate report.
    My question was how do i get the both in single sheet or even different sheets, because when i open finance report and then try and change the application to rate and then click expand all the previously created report is also converted to finance.
    I hope oyou understand and help me out.
    Thanks always.
    Dharmik

  • Questions regarding currency conversion using SPRUNCONVERSION.

    Hi all,
    I have implemented currency conversion using SPRUNCONVERSION stored procedure. I have following questions regarding how does it work.
    1. Is it mandatory to create FxTrans Business Rules with SPRUNCONVERSION?
    2. How does it work internally? How does it look up rate from the rate application?
    Any help will be greatly appreciated. Any reference to any documents will help.
    Thanks&Regards,
    Diksha.
    (PS: How to document does not explain about how it works).

    Hi Diksha,
    1. Yes since it will base it's translation rules based on what is defined on the currency conversion business rules.
    2. The stored procedure SPRUNCONVERSION scans all records found in the selected region of data and translates them according to the RATETYPE property assigned to the ACCOUNT specified in each record, based on the following mechanism:
    Note:
    All ACCOUNTS with no RATETYPE (ratetype = blank) will be translated with a factor of 1
    All ACCOUNTS with the reserved RATETYPE = NOTRANS will not be translated
    All other ACCOUNTS will be translated according to the definitions contained in the table of parameters called clcFXTRANS.
    How the RATE table is selected
    While most customers require a single table of rates, there are situations when more than one set of rates is required. In this situation, the translation procedure uses the RateEntity dimension to select the correct table of rates to use.
    Whenever a destination currency is selected, the procedure searches for a RateEntity member flagged with this currency in the Currency property. For example, if translating into USD, the system uses the RateEntity member that has the Currency property set to USD.
    If there is no RateEntity flagged as the destination currency, the system will use the RateEntity with Currency = 'u2019 (blank).
    In addition to this, some exceptions by ENTITY can be applied. For example, some entities just entering in the consolidation perimeter may need to be converted at their own specific set of rates. These entities may have a corresponding RateEntity member in the RATE cube. All ENTITIES having a corresponding RateEntity member in the RATE cube will use that member as rate table. For example, if there is a RateEntity member named like the ENTITY USOps, the RateEntity member USOps will be used to translate the values of entity ENTITY USOps.
    The RateEntity member, when representing an ENTITY, may be any of the following:
    A valid base level or parent member ID from the ENTITY dimension of the main cube
    A list of members of the ENTITY dimension, as defined filtering the members using a value of the DIMLIST property (or any property whose name begins with "DIMLISTu201D) of such dimension.
    For more info, you could refer to the Administration Help found on the Admin console.
    Hope this helps,
    Marvin

  • Currency conversion JPY to USD issue

    Hi Friends ,
    I am facing an issue while currency conversion from JPY to USD . I have defined currency conversion type in RSCUR , it is working fine for all other currencies except JPY . I have the exchange rate maintained in TCURR but still it shows exchange rate not maintained while running the query  . Could  you please tell what can be possible reasons for it .
    Thanks in Advance .

    Hi,
    Check the time reference based on which the currency conversion rate is maintained. Run function module READ_EXCHANGE_RATE by giving the date, JPY to USD and check if returns values.

  • Currency conversion not working for foreign entity

    I am having an issue with currency conversion not generating the correct values for foreign entities. For entities where the currency is USD, I am able to see the LC amount being written to USD. However, for entites that have currencies other than USD, I just see zeros. I have double-checked to make sure that rates exist for the given currencies. Below is the logic script I am using which is a modificatio nof the multicurrency.lgl. Any help would be greatly appreciated.
    // filter the appropriate currencies and rates
    *SELECT(%REPORTING_CURRENCIES%, "[ID]", "RptCurrency", "[REPORTING] = 'Y'")
    *SELECT(%FX_RATES%,"[ID]","RATE","[GROUP]='FX RATE'")
    // set the appropriate region to clear
    //(all reporting currencies)
    *CLEAR_DESTINATION
    *DESTINATION RPTCURRENCY=%REPORTING_CURRENCIES%
    // load the rates from the RATE cube
    *LOOKUP RATE
    *DIM RATESRC="RATECALC"
    *DIM Rate=ARFIELD.RATETYPE
    *DIM SOURCECURR: INPUTCURRENCY=LOC_MILLOTH.CURRENCY
    *FOR %CURR%=%REPORTING_CURRENCIES%
    *DIM %CURR%:INPUTCURRENCY="%CURR%"
    *NEXT
    *ENDLOOKUP
    // define the translation rule
    *WHEN ARFIELD.RATETYPE
    *IS "NOTRANS"
    // translate
    *IS %FX_RATES%
           *FOR %CURR%=%REPORTING_CURRENCIES%
               *REC(FACTOR=LOOKUP(SOURCECURR)/LOOKUP(%CURR%),RptCurrency="%CURR%")
           *NEXT
    *ELSE
           *FOR %CURR%=%REPORTING_CURRENCIES%
               *REC(RptCurrency="%CURR%")
           *NEXT
    *ENDWHEN
    *FOR %CURR%=%REPORTING_CURRENCIES%
             [RptCurrency].[#%CURR%]=null
    *NEXT
    *COMMIT
    Regards,
    Karen

    Hi Karen,
    I'm no script logic expert so I won't comment on your code. If it's working for USD then the code is probably fine.
    There are a few other things you could check (these are based on investigation using the standard multicurrency script). They should line up with the standard Finance application from AppSet
    In the InputCurrency dimension for the currencies you want to convert into :
       Check property Reporting is equal to "Y"
       Check property Group is set to "Report"
       Check propoerty MD has a value of "M" or "D"
    In the RptCurrency dimension you need to have entries for the the currencies you want to convert into (AppSet only has USD and EUR to start). Also for each of the currencies :
       Check property Reporting is equal to "Y"
       Check property Group is equal to "Report"
       Check property Transfer is equal to "Y"
    I'm not convinced that the Transfer value is required but from my testing if you get the above set up and use the standard multicurrency script it will work.
    The testing I did was translating into USD, EUR, GBP, CHF, AUD etc
    Hope this helps.
    Thanks.
    Bradley Newcombe.
    Edited by: Bradley Newcombe on Apr 28, 2009 1:30 PM

  • Currency conversion variable

    I have a question regarding currency conversion variable.
    We have USD and CAD currencies in BW. I created a currency conversion variable in the properties of a key figure using average rate for current date (0MEANTODAY) and that variable was working fine for a long time. Now I noticed that variable got corrupted in BWD but still works in BWQ and BWP systems. I can see in BWD that variable has nothing in a Variable Represent box and Ready for Input checkbox is not checked. It doesn’t let me to fix or repair this variable. I cannot run any existing queries in BWD that use this variable. The error message is “Variable 0MEANTODAY is not permitted for the target currency”
    I created another currency conversion variable that works in BWD. I know it is ok to have multiple variables for a dimension, let’s say Cal Year/Month has a number of variables. I am not sure whether it is allowed to have multiple currency conversion variables and use different currency conversion variables in different queries. We have about 40 queries that use old currency conversion variable in BWP. If I’ll move new query with a new currency conversion variable to BWP, will it cause any problems for the existing reports that use an old variable? I want to know whether it will present a problem running 40 reports that are already in prod besides the fact it will be inconsistent for a while until I’ll switch all reports to use a new variable.
    I don’t know why that variable got corrupted.  A few weeks ago basis applied some patches in BWP and copied it to BWQ and BWD systems but I am not sure that caused a problem.
    I am relatively new to BW and will very much appreciate any help. I haven’t done transport to production for more that a week and cannot wait any more.
    Thanks,
    Polina
    BWD – DEV;  BWQ – QA  and BWP - Production

    I was dealing with this problem for more than a week. Finally I got help from SAP today. As it was explained to me, we were using very old version of BW front end (part of SAP GUI) which became incompatible with the new patches we applied in BWP and copied to BWQ and BWD. Basically, I was told to upgrade BW front end that caused problems especially in the Variable Wizard area.
    I repaired the currency conversion variable and move it to production. So far all reports run ok in production.
    If anybody will have problems with currency conversion variables, please check your front end version.
    Thanks.

  • 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 issue while creating PO from Shopping cart

    Hello Experts,
    I'm facing an issue in SRM during Limit purchase order creation from Limit shopping cart.
    Scenario:
    Shopping cart was created on 1st of June and Approved on 20th June & Po was created on the same day. But the currency conversion is no ware matching and couldn't able to trace out the same. I have tried several times to replicate the issue it never done in test environments.
    But the PO is creating with refer to Vendor currency. For example if SC was created in USD and vendor order currency in EUR then PO is created in EUR.
    the relevant notes were already updated in the system and it is working fine when the SC is created and approved on the same day.
    Please give me some idea how to fix this issue.
    Is there any way to make SC currency is priority than Vendor Order Currency while creating PO?
    Regards
    Pratap J

    Hello,
    Read information available in KBA 1862453.
    It mentions this issue.
    Regards,
    Ricardo

  • Currency Conversion Issue

    HI experts,
    i have an issue with my currency report,
    where user want see the sales volume data converting from CAD to US $.
    when i checked the query the conversion type is Avg rate M source to CAD and the Target currency is CAD only.
    but when he execute the report he want to see the volume data in USD $.
    and when i execute the report i can see below error.
    Could not find any data to display. This might be due to the current selection of variable or filter values.
    can some please help me out this issue.
    thanks
    Raj

    Hi venu
    thanks for the post,
    there's no selection criteria being used by the user, has web link, once he click on link, he directly checking the report.
    so there's no section screen available.
    and there's no variable created for the  currency conversion type .
    here my requirement is to display currency in USD $ from CAD $.
    target currency maintained as CAD in RSCUR tcode.
    how would i do this,
    and again the same report is being used by CAD user also, so view shouldn't be change for the both users.
    what im thinking is
    is there any possibility to create variable on currency to select the required currency dynamically by user in selection screen
    please let us know possible solutions like without changing the view for CAD users
    please let me know for more info
    regards
    raj

  • 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

  • Currency Conversion Issue in Infocube Purchasing Data (0PUR_C01) Routine

    Hi Gurus,
         We are using SAP BI 7.0, We are having reports on Purchasing Data (0PUR_C01) under that 2 updates rules are there.
    For the field Effective purchase order value (0ORDER_VAL), there is one standard routine only from the Datasource 2LIS_02_SCL.
    My problem is that when there is Currency other than Local currency in field Order Currency, we dont get the Purchase Order Value though there is PO Quantity.
    Thanks in advance.
    Regards,
    Rajdeep.

    Hi Rajdeep,
    Please verify that the PSA contains data in the fields mapped to the objects below, as they are all used in the currency conversion routine:
    ORDER_VAL
    DOC_DATE
    ORDER_CURR
    LOC_CURRCY
    EXCHG_RATE
    If something is mapped incorrectly or something like that the currency conversion might fail.
    Hope it helps.
    BR
    Stefan

  • Regarding Consolidations and Currency conversions.

    I have a query and have through help.sap.com and has all criteria set-up for consolidation appication and Rate(non-reporting) type application.
    How do i connect currency conversion to the finance appl;ication or consolidation application created.
    Can you please provide any good document material with same IC eliminations tooo.
    I understood from help.sap.com, but need good example. please help me out as i have to prepare consolidation demo.
    planning and reporting demo i have given it and the customer asking consolidation demo. please help me out.
                       Thank you.

    Hello,
    Please go through the following links:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/6052a57b-8c64-2c10-b3a5-b0378ff21243
    Thanks.
    With regards,
    Anand Kumar

  • Currency Conversion issue in BW reporting

    Hello Experts - I have a Revenue KF in COPA cube. For one specific record the currency type is TWD. When I run the report using the Key Figure (along with other Chars), the value is multiplied by 100. I do not have any scaling factor set at the report level or currency conversion set for the Key Figures. It works fine for other records with other currency types. Does it has any thing to do with the TCURF / TCURV tables? Appreciate your help.
    Rgds,
    Venu.

    Hi Venu,
    For different currency types there are scaling factors set by default. When you will run the report, the displayed result is calculated with the scaling factor.
    Regards,
    VA

  • Currency Conversion issue for YTD model

    Hello,
    Currently our Client is using YTD (year to date) model to maintain data into BPC 7.5NW, and planning to use BPC for currency conversion from LC to USD. They are not converting the values in Transactional system. When performing this all Balance sheet accounts will be using YTD model for conversion, but income statement accounts should be using Periodic values for conversion.
    We have two different Entity FX types: one is USDFNC - USD functional and NUSDFNC - Non USD functional. One of the differences between these two FX types is CTA account, USDFNC is using expense Account to Book CTA and NUSDFNC is using Equity Account to book CTA.
    To achieve the above mentioned requirement, I did configure BPC as follows:
    1) Use RATE type AVG (average for Income statement accounts)
    2) Use RATE type END (spot rate for Balance sheet Accounts)
    3) In business rules for Account rate type AVG- formula would be [AVG], apply to periodic flag will be checked.
    5) in business rules for Account Rate Type END - Formula would be [END], apply to periodic flag will be blank.
    6) To calculate CTA for ENTITY FX type- NUSDFNC, I configured the following in Account Rate type AVG - destination account is equity account, Formula is [END]-[AVG], apply to periodic flag will be blank and Entity FX type is NUSDFNC.
    7) To calculate CTA for ENTITY FX type- USDFNC, I configured the following in Account Rate type AVG - destination account is expense account, Formula is [END]-[AVG], apply to periodic flag will be blank and Entity FX type is USDFNC.
    Above configuration is giving me correct converted result for all Balance sheet accounts and income statement accounts are showing the correct values when I use the formula (current period LC amount-previous period LC amount)*(current period AVG rate). But I saw difference in Balance sheet, so further analyzed CTA (currency Translation Accounts) and found that the difference is because of CTA amount only. Similar CTA differences exist for both USDFNC entities and NUSDFNC entities. So, I think my logic to calculate CTA is not working.
    I am using the standard script logic to run Currency Conversion:
    *RUN_PROGRAM CURR_CONVERSION
         CATEGORY  = %CATEGORY_SET% 
         TID_RA = %TIME_SET%
         CURRENCY = %RPTCURRENCY_SET%
         RATEENTITY = GLOBAL
    *ENDRUN_PROGRAM
    *COMMIT
    Can any one help me to understand whether this configuration is correct? I feel that I may need to change the logic for calculating CTA. But not sure about what and where
    Edited by: amarnathputta on Nov 24, 2011 5:36 AM

    Thank you Ethan,
    Let me try to explain this with few dollar amounts:
    Let us consider that I have data for 1st month (Jan) of the year 2011,
    Net income for Jan. 2011 in LC = 59916152.19
    Net income for Jan. 2011 in USD calculated using Average rate is  = $ 9,223,013.14
    CTA for the same month is  (net income in LC X spot rate) - net income in USD at average rate =((59916152.19)*(0.154617))-9223013.14 = 41,042.564
    This value is correct.
    For the month of Feb 2011:
    Net income for Feb.2011in LC = 60415519.01
    Net income for Feb.2011 in USD at average rate (with periodic flag on) = 9,300,112.38 ( I calculated this value manually and it is correct after conversion)
    calculated CTA for the same month is (60415519.01*0.154083)-9300112.38 = 8,892.035.
    But actually BPC calculated CTA is 18,547.56 (I felt that this may be because I am not using the Flag apply periodic value while calculating CTA and when I flagged that, BPC is giving me a very big difference in CTA)
    My balance sheet is exactly off with the difference in CTA.
    Hope this helps you to understand my problem.
    Edited by: amarnathputta on Nov 25, 2011 2:43 PM

  • Regarding error while running currency conversion

    While running currency conversion delivered package FXTRANS.LGF, I am getting an error as
    'Failed to analyse prompt %CURRENCY_DIM%. Can you please help me out.
    I checked currency dimensions----- Input currency and rpt currency and was fine with dimension type currency.
    Can anyone please suggest some solutions.
                            thank you.

    Are your performing the currency conversion for a financial or consolidation application ?
    If it is a consolidation application, you need to include in your script the "Group" dimension, not the "currency" one

Maybe you are looking for