SAP BPC 10.0. NW Currency Translation

Hello,
I am using BPC NW 801 SP04. In below script logic code, I am tring to make currency translation but getting same value as is in USD currency.
Could anyone please help me what mistake I am doing in given below code.
*SELECT(%REPORTING_CURRENCIES%, "[ID]", "RPTCURRENCY", "[REPORTING] = 'Y'")
*SELECT(%FX_RATES%, "[ID]", "R_ACCOUNT", "[GROUP] = 'FX RATE'")
*WHEN RPTCURRENCY
*IS %REPORTING_CURRENCIES%
*REC(EXPRESSION=0)
*ENDWHEN
*LOOKUP Rates
*DIM R_ENTITY="Global"
*DIM R_ACCOUNT=EXPACCOUNT.RATETYPE
*DIM SOURCECURR:INPUTCURRENCY=COMPANY.CURRENCY
*FOR %CURR%=%REPORTING_CURRENCIES%
*DIM C_%CURR%:INPUTCURRENCY="%CURR%"
*NEXT
*ENDLOOKUP
// define the translation rule
*WHEN RPTCURRENCY
*IS "LC"
*WHEN ACCOUNTDIM.RATETYPE
*IS "NOTRANS"
// skip
*IS AVG,END,ENDFLOW
// translate
*FOR %CURR%=%REPORTING_CURRENCIES%
*REC(FACTOR=LOOKUP(SOURCECURR)/LOOKUP(C_%CURR%),RPTCURRENCY="USD")
*NEXT
*ELSE
// take as is
*FOR %CURR%=%REPORTING_CURRENCIES%
*REC(RPTCURRENCY="%CURR%")
*NEXT
*ENDWHEN
*ENDWHEN
Best Regards,
Deepa Palsaniya

Hello Arnold,
I used code as you suggested above but package got aborted every time with different scenario. Could you please help in this why this is happening.
*RUN_PROGRAM CURR_CONVERSION
CATEGORY=%CATEGORY_SET%
ENTITY = %COMPANY_SET%
CURRENCY=%RPTCURRENCY_SET%
TID_RA=%TIME_SET%
RATEENTITY=Global
*ENDRUN_PROGRAM
Best Regards,
Deepak Palsaniya

Similar Messages

How To run Currency translation for Consolidation Application in BPC NW

In "How To do Currency Translation for Financial Application in BPC 7 NW", the author mention that there is another "How To run Currency translation for Consolidation Application in BPC NW", anybody know where to get it?

Hi...
Check if the below links are useful to you.....
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/6052a57b-8c64-2c10-b3a5-b0378ff21243&overridelayout=true
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0ea1fd8-d6d3-2a10-c1ab-e8164dd98316
You can find all How-to docs in the below link
http://wiki.sdn.sap.com/wiki/display/BPX/EnterprisePerformanceManagement%28EPM%29How-to+Guides

Currency translation on future dates in SAP BW-BEX

Hello All We have a requirement where in user needs to do a currency translation at run time for data in future periods. For example : Savings data on a purchase order .Total savings for PO is $100,000.00 in year/month 2014/008 . We have a from and to date based on which the savings is equally distributed for each month. From 008/2014 to 008/2015. So each month savings in this case is $8333.33. This data is stored in cubes. Currency translation is based on data in TCURR and TCURX tables . We do not have future currency rates in these tables. Table is up to date only as of today . Therefore the question arises WHAT RATE WILL BEX USE TO CALCULATE DATA IN FUTURE PERIODS? (It is doing the conversion from USD to CAD - but there is no idea what rate it is using? The currency translation variable is based on 0calmonth. Please help me understand what are the default settings for currency translations in this case ? Thank your your help. Sainath Kumar

Hello Yasemin Thank you for your answer, we too think that could be the case. But is there any documentation confirming the same. Also in this case the future values will keep changing based on the availability of the data in TCURR table. Thus the report values will not be constant.Technically it makes no sense to convert rate today for a value in future. I am looking for a concrete answer from SAP saying that this is what the Bex query will do in case the future rates are not present. This will give the business a base to work with .

Foreign Currency Translation at Year End - How SAP Works for P&L items?

Hi All,
I wanted to know "How SAP works on Foreign Currency Translation at year end" from Local Currency to Group Currency for P&L Items.
I know how SAP works for Balance sheet items but am really confused with when the translation was done for P&L Items.
Configuration:
We are on ECC 6.0 . Local Currency is CAD and we have 2nd Local Currency as "USD - Group Curr".
We have set up Valuation Method - 4
We have set up Valuation Area - 40
For Account Determination for Currency Translation, GL accounts (Loss, Gain and B/S Adj) were setup for the combination of Chart of Accounts, Val Area and Fin Stmt Ver.
Sales Account Balance
CAD (LC)        USD (2nd LC)
1000                   920
Using tcode "FAGL_FC_TRANS", we translated our P&L items.
Local Currency is CAD and Group Currency is USD.
CAD 1000 and USD 920 are cumulative balances over a period of time.
Since at the end of year CAD became stronger, exchange rate is 1.11 as an example
Sales Account Balance
CAD (LC)        USD (2nd LC)        Translated Value in USD
1000                   920                        900
System passed the following entry in USD:
Debit Balance Sheet Adj A/c 20
Credit Translation Gain / Loss A/c 20
Here are the questions:
1. How does over all translation work? - Should we get any Gain / Loss and have an effect on P&L when all accounts (P&L, B/S) are translated?
2. How can there be a gain entry when USD value has really fallen from 920 to 900 in the current case.
Thanks for your time.
Vijay

Hi,
I had this issue too. The entry was just opposite to what it should be. I just flipped the accounts in table FAGL_T030TR.
Example: 410000 is sales account which normally should have a credit balance. Here are some entries that were posted to sales in 03/2009 and I am running FAGL_FC_TRANS at the end of the month.
March 1, 2009 Cr. Sales CAD 1000- USD 900-
March 2, 2009 Cr. Sales CAD 500- USD 480-
During FC translation transaction, system takes the balance in the account for the period (if you execute it with 'Val. period balance only' checkbox checked) and not the cumulative balance. SAP recommends translating period balance only (and not cumulative balance) for P&L accounts. It sees a balance in LC (this again depends on the config. you have in OB22 - whether the indicator is 1 (TC as source currency) or 2 (LC as source currency for translation)) which is 1500, converts that at month end rate. After conversion, lets say the balance is 1400-.
In this case, we expect a credit entry on sales account
March 31, 2009 Cr. Sales CAD 0 USD 20-
But system was just posting the opposite. I then flipped the accounts in FC translation configuration. I know it is misleading. In that configuration, system says balance sheet adjustment account, but what you should actually give there is your gain/loss account. Our gain/loss a/c. falls in the same GL account range as the main account. For example, for 410000, it is 410999 and for 510000, it is 510999. We report accounts 410000 to 410999 in the same node in the FSV.
Pl. feel free to ask further questions about this. Pl. test in your system and correct me if my above reply is wrong.
Cheers!

SAP reporting - currency translation

Hello Guys,
In SAP report S_ALR_87013558 - the output is beeing displayed in unwanted currency.
The database currency is XXX but the report is beeing displayed in List currency YYY.
When checking report painter form: 12KST1A, I can see that the key figure is set to 'Overal in CAC'
Controlling area currency = XXX. How to remove the YYY currency from the report if I don't want to use the Currency translation. Where is it taking the YYY currency from?
Thank you..

Hello Didier,
My case is little relevant to the cureent post.
I have created a variable with RSCUR transaction code to get user input date.
This variable prompts in the sap query.
Upon my SAP super query we have built an universe, to build bo reports.
As this variable is created with RSCUR transaction code, it is not reflecting with universe designer to get translated.
Can you please provide me any approach, on taging this variable with other dimension at sap query level or any other approach to solve this issue.
My requirement is to include it with sap query, to get reflected with universe.
Please let me know the approach on passing values from one varaible to other variable, which i guess would solve this issue.
Thanks.

BPC 7.5 NW - Exchange Rates & Currency Translation

Hello All,
I have a couple of questions regarding the BPC currency translation process.
1. We have two options to store the exchange rates - either as a direct quote or as an indirect quote. How are the exchange rates stored in the BPC system?
2. We have a property called "MD" in the InputCurrency dimension, which is used as a 'factor' in the currency translation process. I would like to know how this property is used, in conjunction with the direct/indirect method of maintaining the exchange rates.
As always, thanks for all your responses.
Best regards,
Van.

Thanks for the response. I do realize that we can enter the exchange rates either via a flat file or an Input Schedule, and also how the "MD" factor is utilized in the currency translation process.
I will try to rephrase my questions, as below:
1. In ECC, we have the option to maintain the exchange rates either as a direct rate or an indirect rate. Similary, I would like to know how the exchange rates are "_stored_" in the BPC system - as indirect quotations or direct quotations.
2. In addition, I would also like to know how the "MD" property in the InputCurrency dimension should be maintained. In other words, let us say that the exchange rates are stored as direct quotes. How do we maintain the "MD" property in the inputcurrency dimension for this exchange rate - M or D?
Hope my questions are a bit more clear now.
Appreciate all your responses.

How To Currency Translation in BPC

"How To Currency Translation in BPC".

Hi,
The Finance application has standard default advanced rules that run currency translation. The
default formula includes the FXTRANS.xls advanced rule, which sets up currency translation by running
the system TRANSLATE_LDI formula.
The Rate application contains currency translation rates and Intercompany elimination logic. The rate
application was created first, then the Finance application was created and tied to the Rate application
when the multi-currency option was chosen.
below is an example for currency trans:
*DIM CATEGORY=CATEGORY
*DIM TIME=TIME
In the following example, a currency translation in the two reporting
currencies USD, and EURO is performed.
Get the rates
*LOOKUP RATE
*DIM ENTITY2="DEFAULT"
*DIM RATE=ACCOUNT.RATETYPE
*DIM SOURCECURR:INPUTCURRENCY=ENTITY.CURR
*DIM DESTCURR1: INPUTCURRENCY="USD"
*DIM DESTCURR2: INPUTCURRENCY="EURO"
*ENDLOOKUP
// Translate
*WHEN ACCOUNT.RATETYPE
*IS "AVG","END"
*REC(FACTOR=LOOKUP(DESTCURR1)/LOOKUP(SOURCECURR),CURRENCY=u201DUSDu201D)
*REC(FACTOR=LOOKUP(DESTCURR2)/LOOKUP(SOURCECURR),CURRENCY=u201DEUROu201D)
*ELSE
*REC(CURRENCY=u201DUSDu201D)
*REC(CURRENCY=u201DEUROu201D)
*ENDWHEN
*COMMIT
thnks.

BPC Currency translation..

1. The currency translation need to be done for 2 reporting currencies..USD, EURO respectively.
How does the CT works...can we translate all global entity codes transation to USD and then translate USD translated figures to EURO
or... Directly translate all the entity date to EURO directly?
2. How the rates are loaded to BPC from BI TCURR tables...is there any automation possible.
Please let me know the options..

In the BADI UJ_CUSTOM_LOGIC do this logic:
*From your CT_DATA which may contain the rate/currency/translation date, etc.:
     CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
          EXPORTING
               date                     = "This is your translation Date (most cases sy-datum is used)
               foreign_amount   = "The amount you wished to be converted
               foreign_currency = "The currency you wanted to change
               local_currency   =   "The target currency
               rate                     = ""If rate is provided (or most likely you will have to refer on translation date, whichever is convenient)
          IMPORTING
               local_amount     = "This will return the value of the converted rate
          EXCEPTIONS
               no_rate_found    = 1
               overflow         = 2
               no_factors_found = 3
               no_spread_found = 4
               derived_2_times = 5
               OTHERS           = 6.
Take note that this conversion doesnt mean just a local currency, it can be any currency you wish to convert.
modify whatever value you need to modify in your CT_DATA
and youre done.

BPC NW10.0 Execute the currency translation in DEFAULT.LGF

Hello,
I would like to execute the task currency translation in DEFAULT.LGF
Nb : we used the DEFAULT.LGF when we import the actual and budget data with Excel file (.csv)
I created the DEFAULT.LGF and inserted the following rows:
*XDIM_MEMBERSET CATEGORY=%CATEGORY_SET%
*XDIM_MEMBERSET RPTCURRENCY=LC
*XDIM_MEMBERSET TIME=%TIME_SET%
*XDIM_MEMBERSET DATASRC=INPUT
* INCLUDE FXTRANS.LGF
But, not currency translation when we import the actual and budget data
Nb : When I execute FXTRANS.LGF (FX_STATEMENT), it's OK , the system created the new records for translation currency
Best regards
Bastien

Hi,
If I used the input schedule, the records are converted in EUR
If I used manually the fonction the currency translation , the records are converted in EUR
Example of conversion
COSTCENTER
COSTELEMENT
INTERCO
COMPANY
DATASOURCE
CATEGORY
RPTCURRENCY
TIME
Measures
S169100
G502
P_SND
S0168
IMPORT_SAP
BUDGET
LC
2013.OCT
100,0000000
S169100
G502
P_SND
S0168
IMPORT_SAP
BUDGET
EUR
2013.OCT
68,0000000
Bastien

How to use the RateEntity dimension in SAP BPC?

Hello everbody,
I am implementing a consolidation process using SAP BPC. I want to use the RateEntity dimension, to translate a same currency into different exchange rates depending on the company.
I want the company which ID is GFU (which is from Brazil) in LegalEntity dimension is converted using a special exchange rate. I have added a GFU member in RateEntity dimension, and I have entered the exchange rates for the member GFU and for the member Global in RateEntity dimension.
But the problem is that after I run the FX Restatement package, converted data for this company is not the proper one, because Global exchange rates have been used instead of GFU exchange rates. Does anybody know why? Do I have to do anything else?
Thank you very much for your time

Do you see the search functionality in the upper left of the screen?
Okay, now type in ecatt, press enter and in the next screen filter on blogs.

Currency Translation - Rolling Forecast

Hi,
Scenario is: We're doing 13 months rolling forecast which goes beyond one year. When currency translation happens, as part of default logic, it converts the records only for the year of forecast (selected in current view) and not beyond the current view year.
For instance, if selected forecast period 2011.JAN, we expect user to input numbers from 2011.JAN through to 2012.JAN. System run the currency conversion package and translate records for periods 2011.JAN - 2011.DEC, and doesn't convert 2012.JAN because it is the next year (not selected in current view).
Following is the code I'm using in the FX Conversion package:
*RUN_PROGRAM CURR_CONVERSION
      CATEGORY     = %VERSION_SET%
      CURRENCY = USD
      TID_RA = %TIME_SET%
      RATEENTITY = GLOBAL
      OTHER = ENTITY=%CURRENCY_SET%
*ENDRUN_PROGRAM
Can you please suggest any resolution, i.e. how I can enhance the code to convert records whatever I get from runtime (template) and not just restricted to CV Year?
Many thanks,
Shabbar

Hi Shabbar,
While executing Currency translation, if you can select 13 months (say,from 2011.Jan to 2012.Jan ) in data manager parameter, Conversion executes for all 13 months as %TIME_SET% take value from your data manager prompt.
If you are identify %TIME_SET% based on Year in Category dimension, you can try below code.
*SELECT(%YEAR%, [YEAR], CATEGORY, "[ID]='FORECAST'")
*SELECT(%TIMEMBR%,[ID],TIME,"[YEAR]=%YEAR%")
*XDIM_MEMBERSET TIME=%TIMEMBR%,%YEAR+1%.JAN
//standard currency translation code.
If you are working on BPC NW 7.5, you can consider using TMVL(OFFSET,Time member) to define the scope.You can refer to http://help.sap.com/saphelp_bpc75_nw/helpdata/en/c8/d961d0dbfd4745af4b667279573702/content.htm for more details on TMVL.
Pls post here if you require further clarification.
Regards,
Kranthi

Difference between SAP BPC & SEM BCS

Hi Gurus,
What is the difference between SAP BPC & SEM BCS And throw some light on both?
Thanks in Advance,
Sandy.

Hi Sandy,
The functionality in BPC mainly 1) Planning 2) Consolidation
1) Planning : You can have any type planning scenario. Ex.: Sales planning. Based on the actual previous data
we will have some projection reports on the sales for future sales, so we can have planning scenario here . We can change
the projections as per our requirement for any number of times.
Ex 2: HR Planning. Based on the market condition we have recruitment planning, based on the actual data (Existing Emp.)
Ex 3: Accounts Expenditure planning like this we can have planning forecastings.
2) Consolidations : We can consolidate the group company, companies with currency translations, allocations, Inter Unit
eliminations, consolidated P&L accounts & Consolidated Balance Sheets are possible in this.
But where as in BCS you can do only 2 part. The first part is not possible. Hence I personally suggest you to learn BPC NW
it will be more useful. BPC is now going to integrated with BO (Buss. Objects) also from 7.5 ver onwards.
I hope this may help you.
Regards,
B.S.RAGHU

Limited Currency Translation pt2

Hey Experts!   Apparently I tried to post too much information into that last post. Here's the high level:
We're running BPC 7.0 (SQL 2008 DB)
We've recently setup FX tranlation usign Script Logic in BPC. After setting it up, we realized that we need to filter the data being converted. A few months ago, I was sent a document from SAP support named "How To Configure Limited Currency Translation".
I've followed this document very closely and I'm getting the following error when trying to send data to my system:
ExecuteBaseLogic::Error in step 1 of QueryCubeAndDebug: -2147467259 Query (1, 99) Parser: The syntax for ',' is incorrect.
I know this is telling me that there's a comma in the wrong spot somewhere, but I've checked the code 10x over and it matches SAPs document perfectly.
Does anyone know what is causing this? I can try to post my FXTrans script a reply. Maybe that'll work.

FX Trans.lgf
//============================================= // Currency translation logic //=============================================
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB SYSTEM_LIBRARY.LGL
//=================================================================================
// MULTI-CURRENCY TRANSLATION LOGIC
//=================================================================================
// filter the appropriate currencies and rates
*SELECT(%REPORTING_CURRENCIES%, "[ID]", "RPTCURRENCY", "[REPORTING] = 'Y'")
*SELECT(%FX_RATES%, "[ID]", "RATE", "[GROUP] = 'FX RATE'")
//Filter the Actuals Category from the Currency Conversion
*SELECT(%FX_CATEGORIES%, "[ID]", "CATEGORYDIM", "[IS_CONVERTED] = 'Y'")
// set the appropriate region to clear
//(all reporting currencies)
*XDIM_MEMBERSET RPTCURRENCY=LC
*CLEAR_DESTINATION
*DESTINATION RPTCURRENCY=%REPORTING_CURRENCIES%
*DESTINATION CATEGORYDIM=%FX_CATEGORIES%
// load the rates from the RATE cube
*LOOKUP RATE
                *DIM RATE=ACCOUNT.RATETYPE
                *FOR %CURR%=%REPORTING_CURRENCIES%
                                *DIM %CURR%:INPUTCURRENCY=BUSINESSUNIT.CURRENCY
                                *DIM %CURR%:RATEENTITY="%CURR%_RATE"
                *NEXT
*ENDLOOKUP
// define the translation rule
*XDIM_FILTER CATEGORYDIM=%FX_CATEGORIES%
*WHEN ACCOUNT.RATETYPE
*IS "NOTRANS"
                // skip
*IS %FX_RATES%
                // translate
                *FOR %CURR%=%REPORTING_CURRENCIES%
                  *REC(FACTOR=LOOKUP(%CURR%),RPTCURRENCY="%CURR%")
                *NEXT
*ELSE
                // take as is
                *FOR %CURR%=%REPORTING_CURRENCIES%
                    *REC(RPTCURRENCY="%CURR%")
                *NEXT
*ENDWHEN
*COMMIT

Limited Currency Translation

Hey Experts!
We're running BPC 7.0 (SQL 2008 DB)
We've recently setup FX tranlation usign Script Logic in BPC. After setting it up, we realized that we need to filter the data being converted. A few months ago, I was sent a document from SAP support named "How To Configure Limited Currency Translation".
I've followed this document very closely and I'm getting the following error when trying to send data to my system:
ExecuteBaseLogic::Error in step 1 of QueryCubeAndDebug: -2147467259 Query (1, 99) Parser: The syntax for ',' is incorrect.
I know this is telling me that there's a comma in the wrong spot somewhere, but I've checked the code 10x over and it matches SAPs document perfectly.
Here's my FXTrans.lgl:
//============================================= // Currency translation logic //=============================================
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB SYSTEM_LIBRARY.LGL
//=================================================================================
// MULTI-CURRENCY TRANSLATION LOGIC
//=================================================================================
// filter the appropriate currencies and rates
*SELECT(%REPORTING_CURRENCIES%, "[ID]", "RPTCURRENCY", "[REPORTING] = 'Y'")
*SELECT(%FX_RATES%, "[ID]", "RATE", "[GROUP] = 'FX RATE'")
//Filter the Actuals Category from the Currency Conversion
*SELECT(%FX_CATEGORIES%, "[ID]", "CATEGORYDIM", "[IS_CONVERTED] = 'Y'")
// set the appropriate region to clear
//(all reporting currencies)
*XDIM_MEMBERSET RPTCURRENCY=LC
*CLEAR_DESTINATION
*DESTINATION RPTCURRENCY=%REPORTING_CURRENCIES%
*DESTINATION CATEGORYDIM=%FX_CATEGORIES%
// load the rates from the RATE cube
*LOOKUP RATE
                *DIM RATE=ACCOUNT.RATETYPE
                *FOR %CURR%=%REPORTING_CURRENCIES%
                                *DIM %CURR%:INPUTCURRENCY=BUSINESSUNIT.CURRENCY
                                *DIM %CURR%:RATEENTITY="%CURR%_RATE"
                *NEXT
*ENDLOOKUP
// define the translation rule
*XDIM_FILTER CATEGORYDIM=%FX_CATEGORIES%
*WHEN ACCOUNT.RATETYPE
*IS "NOTRANS"
                // skip
*IS %FX_RATES%
                // translate
                *FOR %CURR%=%REPORTING_CURRENCIES%
                  *REC(FACTOR=LOOKUP(%CURR%),RPTCURRENCY="%CURR%")
                *NEXT
*ELSE
                // take as is
                *FOR %CURR%=%REPORTING_CURRENCIES%
                    *REC(RPTCURRENCY="%CURR%")
                *NEXT
*ENDWHEN
*COMMIT
Here's the FXTRANS.LGX:
*XDIM_MEMBERSET RPTCURRENCY=LC
*CLEAR_DESTINATION
*DESTINATION RPTCURRENCY=USD,EUR
*DESTINATION CATEGORY=NPACTUAL,INTLPRODACTUAL,JANFCST,FEBFCST,MARFCST,APRFCST,MAYFCST,JUNFCST,JULFCST,AUGFCST,SEPFCST,OCTFCST,NOVFCST,DECFCST,BUDGET,BUDGETVA,BUDGETVB,BUDGETV1,BUDGETV2,BUDGETV3,BUDGETV4,BUDGETV5,BUDGETV6,BUDGETMD,BUDGETMDV2,BUDGETMDV3,BUDGETMDV4,BUDGETFIELDV1,BUDGETFIELDV2,BUDGETFIELDV3,BUDGETFIELDV4,BUDGETFIELDV5,COMPPLAN,Q2COMPPLAN,Q4COMPPLAN,COMP_REVENUE,QUOTA_PLAN,ACTBUD,FCSTINPUT
*LOOKUP RATE
*DIM RATE=ACCOUNT.RATETYPE
*DIM USD:INPUTCURRENCY=BUSINESSUNIT.CURRENCY
*DIM USD:RATEENTITY="USD_RATE"
*DIM EUR:INPUTCURRENCY=BUSINESSUNIT.CURRENCY
*DIM EUR:RATEENTITY="EUR_RATE"
*ENDLOOKUP
*XDIM_FILTER CATEGORY=NPACTUAL,INTLPRODACTUAL,JANFCST,FEBFCST,MARFCST,APRFCST,MAYFCST,JUNFCST,JULFCST,AUGFCST,SEPFCST,OCTFCST,NOVFCST,DECFCST,BUDGET,BUDGETVA,BUDGETVB,BUDGETV1,BUDGETV2,BUDGETV3,BUDGETV4,BUDGETV5,BUDGETV6,BUDGETMD,BUDGETMDV2,BUDGETMDV3,BUDGETMDV4,BUDGETFIELDV1,BUDGETFIELDV2,BUDGETFIELDV3,BUDGETFIELDV4,BUDGETFIELDV5,COMPPLAN,Q2COMPPLAN,Q4COMPPLAN,COMP_REVENUE,QUOTA_PLAN,ACTBUD,FCSTINPUT
*WHEN ACCOUNT.RATETYPE
*IS "NOTRANS"
*IS AVG,END
*REC(FACTOR=LOOKUP(USD),RPTCURRENCY="USD")
*REC(FACTOR=LOOKUP(EUR),RPTCURRENCY="EUR")
*ELSE
*REC(RPTCURRENCY="USD")
*REC(RPTCURRENCY="EUR")
*ENDWHEN
*COMMIT
Does anyone have any idea why this is failing?
Any help would be greatly appreciated.
Thanks!
Sean

There was a problem with the way this message posted. Re-posted message.

Currency translation [AS_IS] formula on FX Simulation Category

Hi,
We are currently experiencing the following problem on currency translation, any assistance will be appreciated.
The [AS_IS] formula in the currency translation business rule , does not leave the USD amount in the FX Simulation Category (ACTSTAT) , it replaces the amount with the USD amount in the source category (ACTUAL) when currency translation package is run for ACTSTAT.
Background info:
We are running SAP BPC 10 NW EP 801 SP4
Our financial year is OCT 2013 – SEP 2014
We have two categories ACTUAL used for management reporting and ACTSTAT used for
statutory reporting
All data is entered in LC against the category ACTUAL and FX translation for ACTUAL
represent the management accounting numbers where the simulation of category
ACTSTAT on the base data provide us with the statutory translation
We have two sets of rates that are applicable for management reporting and one for
statutory reporting.
We have a problem with the rules we use for FX translation for accounts that should
be reported at historic values.
We use the formula [AS_IS] to leave group currency values unchanged when values
are carried forward from one year to the next. This is the intention of
the formula as explained in documentation
For this example we used reporting currency USD ( US Dollars)
ACTSTAT is a FX simulation category with ACTUAL as the base / source category ( No data
is loaded to LC)
We have a FX translated value closing balance for the prior year on ACTUAL
(management accounting) and ACTSTAT (statutory reporting) that are different
from each other. The rule builds the closing balance through opening
balance against historic values plus any movements at an average periodic rate.
We execute the carry forward of closing balances which transfers the closing
balance to the opening balance of the respective categories – ACTUAL and
ACTSTAT. This works beautifully
When we run the FX translation in the new year the system does not leave the
translated value unchanged in the category ACTSTAT as the formula [AS_IS] was
designed to do.
Data after carry forward is run:
Sep-13
Oct-13
Nov-13
Dec-13
Jan-14
Feb-14
Mar-14
Apr-14
May-14
Jun-14
Jul-14
Aug-14
Sep-14
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
F99 - Closing
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
200000 - Ordinary share capital
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
Problem
The AS_IS formula retrieves the data from the ACTUAL category USD amount and
replaces the USD amount on ACTSTAT.
After
currency translation:
Sep-13
Sep-13
Oct-13
Nov-13
Dec-13
Jan-14
Feb-14
Mar-14
Apr-14
May-14
Jun-14
Jul-14
Aug-14
Sep-14
ACTUAL
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
F99 - Closing
F99 - Closing
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
F00
F00
F00
F00
F00
F00
F00
F00
F00
F00
F00
F00
200000 - Ordinary share capital
3 750.00
-3 193.89
3750
3750
3750
3750
3750
3750
3750
3750
3750
3750
3750
3750
Thanks
Gavin

Hi Gavin,
I don't think there is a way to customise the FX business rule by category, so you would have to use a script. I would create an additional flow (say Fxx), then amend the carry forward rule to copy from F99 to F00 and to Fxx.
After you run the FX conversion you could then for ACTSTAT only copy the Fxx amount in converted currency back to F00. Essentially overwriting the amount the system took from ACTUAL again with the carried forward amount.
BR,
Arnold

SAP BPC 10.0. NW Currency Translation

Similar Messages

Maybe you are looking for