Currency Translation and Account Transformation Business Rules Together?

Hi I am fresh out of college and working on a BPC project. I have this working but fear down the road problems.
We are using currency translation and struggling with getting our NetIncome to write the correct value to the Current Year Retained Earnings when it converts from LC to USD; USD value did not match Net Income in P&L.
Initially, we did the Account Transformation first in our default logic only on LC, then FX runs and creates the corresponding USD value which does not match the Net Income.
It looks like the logic is correctly summing the YTD value but it converts using the AVG rate for the period (as opposed to multiplying each month by that monthu2019s average rate) creating a variance.
Weu2019ve moved the account transformation to run after FX and have it also running on USD. This currently works but seems like a workaround, and as we configure the remaining CTA rules will we run into problems?
Have any experts run into this issue before and what should I do?
Edited by: MichaelUCF2010 on Oct 12, 2010 10:18 PM

Hi, perhaps this is my lack of accounting knowledge rearing itself.
RE = BS = End (if you take into account translation adjustment for Net Income and Additions/Substractions & OB)
However If you are talking about the RE Reserve (and computing that correctly)
RE Reserve
OB - Opening
Inc - Avg
Sub - Avg
NI - Avg [I assume it is this line you are talking about - please try the apply periodic option for avg]
CTA - calculated
CB - End

Similar Messages

Calcaccount procedure - account transformation business rules

Hi I have a question concerning the calcaccount procedure.
I already made some Cashflow accounts
I already filled in some lines in the account transformation business rules
But now I was wondering how to run these business rules:
I have made the following calcaccount logic, but when I run it I get nothing for the moment
*XDIM_MEMBERSET INTCO=GLTOT
*XDIM_MEMBERSET GROUPS=C_WDP
*XDIM_MEMBERSET ENTITY=E_TOTAL
*IGNORE_STATUS
*RUN_STORED_PROCEDURE = SPRUNCALCACCOUNT([FINANCE],[%CATEGORY_SET%],[C_WDP],[%SCOPETABLE%],[%LOGTABLE%],[CF])
*COMMIT
I don't have a clue if this logic is even correct or not
Please help me

Hi Alwin,
I tried this but it doesnt work
*XDIM_MEMBERSET INTCO=GLTOT
*XDIM_MEMBERSET GROUPS=C_WDP
*XDIM_MEMBERSET ENTITY=E_TOTAL
*IGNORE_STATUS
*RUN_STORED_PROCEDURE = SPRUNCALCACCOUNT([FINANCE],[%CATEGORY_SET%],[C_WDP],[%SCOPETABLE%],[%LOGTABLE%])
*COMMIT
I have the following in the formula log:
Start time --->3:36:33 PM - Date:9/24/2008 (build code:254)
User:WDP\Administrator
Appset:WDP_ONTWIKKELING
App:FINANCE
Logic mode:1
Logic by:
Scope by:
Data File:
Debug File:D:\BPC\Data\Webfolders\WDP_ONTWIKKELING\FINANCE\PrivatePublications\Administrator\TempFiles
DebugLogic_7_.Log
Logic File:D:\BPC\Data\WebFolders\WDP_ONTWIKKELING\FINANCE
..\AdminApp\FINANCE\Calcaccount.lgx
Selection:D:\BPC\Data\WebFolders\WDP_ONTWIKKELING\FINANCE\PrivatePublications\Administrator\TempFiles\FROM_7_.TMP
Run mode:1
Query size:0
Delim:,
Query type:0
Simulation:0
Calc diff.:0
Formula script:
Max Members:
Test mode:0
Is Modelling:1
Number of logic calls:1
Call no. 1, logic:D:\BPC\Data\WebFolders\WDP_ONTWIKKELING\FINANCE
..\AdminApp\FINANCE\Calcaccount.lgx
signeddata is YTD
Building sub-query 1
Query Type:0
Max members:
Executing SPRUNCALCACCOUNT [FINANCE],[ACTUAL],[C_WDP],[SPSCOPE_312035],[SPLOG_394894]
SPRunCalcAccount Version 2.06
2 Rows Calculated
2 Rows Updated
Time to run stored procedure:26.5 sec.
call 1 completed and data posted in 26.7 sec.
Run completed in 27.3 sec.
End time --->3:36:59 PM - Date:9/24/2008
As you can see he doenst post records to the cashflowaccounts..
Do you know what is wrong?

Account transformation business rule

Hi experts,
I hace defined Account Transformation rule in the default.lgf file. and I have defined source and destionation account in the corresponding table.
Now I am running the rule from Data manager package - Default formula.It is running successfully.
But when I see Package log it is not executing SPRUNCALCACCOUNT at all.
Would be great help if anyone can give some guidance.

Can you post the exact logic script?
Maybe a stupid guess, but did you put a *COMMIT directly after the *RUN_STORED_PROCEDURE logic statement?
Regards,
Joost

Account Transformation Business Rules: Apply to YTD is not working

Hello Friends,
I am using Account Transformation Rules for Re-classification of Accounts in MS version of BPC. And i am trying to use Apply to YTD. But it is not working and i am getting the same periodic values in YTD column also. For example if i am running a report for Dec 2009, i am getting the only Dec 2009 values under YTD also.
I appreciate any ideas on resolving the issue.
Regards,
Mohan

Hi Nilanjan,
I observed the following:
1. If I check the Apply to YTD in Account Transformation rules, it is always showing YTD only irrespective of what i choose in in Measures in CV.
2. If i do not check the Apply to YTD in Account Transformation rules, it is showing only monthly values irrespectinve of what i choose in Measures in CV.
YTD is working fine in the same Appset for other dimension members eg not used in the Account Transformation Rules.(for other reports).
Thank you,
Mohan

Help PLEASE !!!!!!!!!! Accout Transformation Business Rule

Hi 
I am trying to use the account transformation Business Rule in BPC 7 for MS. I have stored data gainst the the following 
application = legal 
period = 2009.006 
category = Actual 
ConsolView = LC 
Intco = I_9005 
Measure = Periodic 
DataSourceL = input 
Account =650110 and 650115 
I have built a report to display this data and to display account 100000
 
My logic to call the rule is
 
*RUN_STORED_PROCEDURE=SPRUNCALCACCOUNT( '%APP%', 'ACTUAL' ,'LC', %SCOPETABLE%, '%LOGTABLE%', 'ABC',99 ) 
*Commit
 
I run my logic in debugger and in the Region tab I set Category to Actual and the Time to 2009.006
 
In the Business Rule I have a transformation group of ABC and in it I have two rows. I have tried many combinations of parameter values but generally I set the source account to 650110 and 650015 and the destination account to 100000 and leave all other fields empty.
 
When I run there are no error messages but no data is moved to account 100000.
 
The log contents are;
 
 
Start time --->5:01:13 PM - Date:26/06/2009 (build code:254)
 
 
 
User:EXTENDTEC\BPC_SYSADMIN
 
Appset:Austereo
 
App:Legal
 
Logic mode:1
 
Logic by:
 
Scope by:
 
Data File:
 
Debug 
File:C:\BPC\DATA\WebFolders\Austereo\Legal\PrivatePublications\BPC_SYSADMIN\TempFiles\DebugLogic.Log
 
Logic File:Acct Transform ABC.LGF
 
Selection:DIMENSION:Category|ACTUAL|DIMENSION:Time|2009.006|
 
Run mode:1
 
Query size:2
 
Delim:,
 
Query type:0
 
Simulation:0
 
Calc diff.:1
 
Formula script:
 
Max Members:
 
Test mode:0
 
Is Modelling:1
 
Number of logic calls:1
 
 
Call no. 1, logic:C:\BPC\DATA\WebFolders\Austereo\AdminApp\Legal\Acct Transform ABC.LGF
 
 
Building sub-query 1
 
 
Query Type:0
 
Max members:
 
Executing SPRUNCALCACCOUNT 'Legal', 'ACTUAL' ,'LC', SPSCOPE_428552, 'SPLOG_486004', 'ABC',99
 
 
SPRunCalcAccount Version 7.0.112
 
 
Time to run stored procedure:.6 sec.
 
call 1 completed and data posted in 0.7 sec.
 
Run completed in 0.7 sec.
 
 
End time --->5:01:14 PM - Date:26/06/2009
 
 
I have spent two days trying to get this thing to work. Am I correct in assuming the purpose of this is to copy data from the source account to the destination account. Can somebody please tell me whether there are other factors that control a business rule.
 
I have spoken to most of the Australian BPC experts and none have successfully invoked the SPRUNCALCACCOUNT. I have read all available documentation and not found an explanation that sheds light on what I am doing wrong. Has anyone successfully used theis Business rule?
 
Thanks in advance
 

Hi Bronwen
Whether you included the System_contants.LGL and Consolidation_Library.LGL in the logic file.
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB CONSOLIDATION_LIBRARY.LGL
Syntax used & its works.
*RUN_STORED_PROCEDURE=SPRUNCALCACCOUNT([%APP%],[ACTUAL],[LC],[%Scopetable%],[%Logtable%],[ABCC])
Give a try!
Note: Use the Square brackets [[%APP%]] in the syntax.
after posting this thread, syntax is showing as URL.
Cheers
Uma
Edited by: Uma Swaminathan on Jun 26, 2009 9:37 AM

Reporting level Currency translation and group level Currency translation

Hi All,
Could any body explain me reporting level Currency translation and group level Currency translation.Please expalin me step by step scenario.
Thanks in advance.
Setty.

Hi Jian,
In my recent implementation completed, business only had one currency to deal with i.e. USD. Data was coming from ECC and we loaded all the data in LC instead of USD using transformation *NEWCOL(LC). Next, you can maintain a rate of 1 in the rate model and run the currency conversion.
This will generate the same data values against USD. So, your statement " if we load LC and than convert it into USD, the data vulu will de double." is incorrect. In the system, you will have same set of values against LC as well as USD.
I suggest that you configure Currency Conversion for future reqmts if any.
Regarding BCF, balances from previous year (Balance Sheet Accounts) will need to be carried forward as opening balances to next year else your BS won't give true picture.
Regards,
Ashish

CTR (currency translation reserve) account calculating

Hello, colleagues!
We have met another issue:
When RU's currency not the same as reporting currency, equity historical change should be shown on account CTR (currency translation reserve) separately (according to IAS 27). We implemented rule, which perform it, but this rule should be applyed only for RU, which currency not the same as consolidation currency. How rule can distinquesh it? In other words, how FC can understand for what RUs CTR should be calculated through the proccess of consolidation, and who which RUs not?
Thanks!

First of all you have to forget the V# in your expressions on the context you are working. This is managed by the if statement. Second, what you do here means that you are done with translation and now you are in calculation at the <Parent Currency> level. So, you also forget Sub Translate, this will never work. A third problem I can see is that you should specify base members for C3 and C4 in the left side of your HS.Exp expression (it is not necessary to do the same in HS.Clear though).
Finally I have some doubts on the way you are trying to do this. You have two parent accounts A#BS400000 and A#BS899999, and you try to assign their difference in a descendant account. I'm not sure how this cyclic reference would work. However, it could work if BS500600 was not in any of the hierarchies of the above parents. Then the piece of code below could work.
If HS.Value.IsTransCur() Then
HS.Clear "A#BS500600.C1#[None].C2#C200185.I#[ICP None]"
HS.Exp "A#BS500600.C1#[None].C2#C200185.I#[ICP None].C3#[None].C4#[None] = A#BS400000.C1#AllCustom1.C2#AllCustom2.I#[ICP Top] " & _
" - A#BS899999.C1#AllCustom1.C2#AllCustom2.I#[ICP Top]"
End If
Regards

Problem with currency translation and variable time ref. with 0FISCPER

Hello,
We have a problem with a currency conversion with a variable time reference (as iobject we use 0fiscper)
We created a currency conversion for several key fig:
Our settings:
Exchange rate Type: EURX
dynamic ex rate determination
Source cur from datarecord
Fixed Target Curr (EUR)
Variable time ref.: End of Period
Special Infoobject: 0fiscper
When we run the DTP we get the following error:
Enter rate GBP / EUR rate type EURX for 00.00.0000 in the system settings.
ending the DTP in a message type X.
In table TCURR and T009/T009B all necessary information is available.
After debugging the function module, it looks like the created date (created from the FISCPER) is set to 00.00.0000. This results in the error above.
Does anybody have experience with this error and more important know how to solve it?
We also have a 0FISCYEAR available but in the TCURR table al rates are defined per end of the month. When trying to use 0FISCYEAR as InfoObject in the variable time reference, a diffrent error occurs: Enter rate GBP / EUR rate type EURX for 01.01.1001 in the system settings. While the 0FISCPER is 2001001.
Is there a bug in the function module? (couldn't find a SAP note)
We are working with BI 7.0 and SP12
Best regards
Steven

Please can you give more detail on how you were able to resolve this issue? How did you add 0fiscper to the transformation? I am on BW 3.5, how do I fix this same issue on it? Please help, this is urgent.

Currency translation code at transformations

hi
i ahve written this code for source currency to target currency usd based on system date. please and let me know any modifications nedd
DATA : w_to_amt     TYPE /bi0/oiamount,
           w_from_curr TYPE /bi0/oicurrency,
           calmonth type sy-datum.
    CONSTANTS: c_bs     TYPE tcurv-kurst VALUE 'BS' ,
               c_usd    TYPE tcurr-tcurr VALUE 'USD' .
      CALL FUNCTION 'CONVERT_FOREIGN_TO_FOREIGN_CUR'
        EXPORTING
          date             = sy-datum
          type_of_rate     = c_bs
          from_amount      = SOURCE_FIELDS-/BIC/ZSR_TVSTV
          from_currency    = SOURCE_FIELDS-LOC_CURRCY
          to_currency      = c_usd
          local_currency   = c_usd
        IMPORTING
          to_amount        = w_to_amt
        EXCEPTIONS
          no_rate_found    = 1
          overflow         = 2
          no_factors_found = 3
          no_spread_found = 4
          derived_2_times = 5
          OTHERS           = 6.
      IF sy-subrc EQ 0.
      RESULT = w_to_amt.
      endif.

hi Suneel,
the code looks fine, since your local_currency same as to_currency (USD), using one of following function module may give same result.
CONVERT_FOREIGN_TO_FOREIGN_CUR you used is actually combination of these 2 function modules :
*first convert fcrom FROM_CURRENCY to LOCAL_CURRENCY
CALL FUNCTION 'CONVERT_TO_LOCAL_CURRENCY'
next convert fcrom LOCAL_CURRENCY to TO_CURRENCY
CALL FUNCTION 'CONVERT_TO_FOREIGN_CURRENCY'
hope this helps.

Business Rules for Account Transformation - Execute a Transformation Group

Hello,
when executing a package for account transformation, I want to select a specific transformation group
only.
The transformation group is the first column in the definitions.
My question:
Can I pass this to script logic as a parameter?
What is it like?
I think this should have a performance effect when using account transformation in default logic.
Thanks for an answer
Jochen

Hi Jochen,
Your best bet is the documentation at [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/2b/8f059920de465b88be2893e2117fbe/frameset.htm], however in this case it does not do a very good job of explaining what is happening. Fortunately the CALC= property is just about the only one that you have control over for the account transformation business rules.
The other option (and the only way to truly know what is going on) is to investigate the ABAP programs that actually execute the business rule logic in BW. You can find these programs in SE80, under the UJ package, in the UJP sub-package. You will be most interested in the classes available there. There tends to be one class per business rule group, as well as classes for allocations and validations.
Cheers,
Ethan

Account transformation accumulating values

Hi Forum,
A quick question is there an option for account transformations not to 'add' to values that exist in the bpc database already. I want to overwrite values in existing accounts but the account transformation seems to be accumulating the value.
Thanks,
Brian

Hi..
I'm working on CAPEX application. My problem is :- 1st time data loading, opening and closing are correct but the subsequent data uploading, opening and closing figure will accumulate. Please advice what coding should I include in my script logic.
In my testing,
1) I'll upload - Jan'2006 opening, Jan'2006 to Dec'2006 Movement
2) use account transformation to calculate "opening + movement = closing"
3) use script logic for carry-forward monthly opening
Account Transformation business rule:
Transf group   Source Acc Source flow            Source d/source Destination acc
A                        1410220          FA_ExistDepr_OPE                                1410220
A                        1410220          FA_ExistDepr                                         1410220
A                        1410220          FA_AddDepr_OPE                                  1410220
A                        1410220          FA_AdditionsDepr                                   1410220
A                        1410220          FA_ADepr_OPE                                      1410220
A                        1410220          FA_ADepr                                               1410220
A                        1410220          FA_DispDepr_OPE                                  1410220
A                        1410220          FA_DisposalDepr                                     1410220
A                        1410220          FA_TranInDepr_OPE                                1410220
A                        1410220          FA_TransferInDepr                                    1410220
A                        1410220          FA_TranOut_OPE                                     1410220
A                        1410220          FA_TransferOutDepr                                  1410220
Dest. flow          Dest. d/source   Rev sign Source Period AppytoYTD Remark LEVEL
FA_ExistDepr_CLO                                                                         Y
FA_ExistDepr_CLO                                                                         Y
FA_AddDepr_CLO                                                                           Y
FA_AddDepr_CLO                                                                           Y
FA_ADepr_CLO                                                                               Y
FA_ADepr_CLO                                                                               Y
FA_DispDepr_CLO                                                                           Y
FA_DispDepr_CLO                                                                           Y
FA_TranInDepr_CLO                                                                         Y
FA_TranInDepr_CLO                                                                         Y
FA_TranOutDepr_CLO                                                                      Y
FA_TranOutDepr_CLO                                                                      Y
Default.lgf Script logic:
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB SYSTEM_LIBRARY.LGL
// Default base level logic - applies to all base members in all dimensions
//Move Net Income to Balance Sheet
//ROLLTOBS( CYNI, CALCNI, FINSTMT, PL, DEC )
// Perform Currency translation
*INCLUDE FXTrans
Perform ACCOUNT TRANFORMATION
*RUN_STORED_PROCEDURE = SPRUNCALCACCOUNT([CAPEX],[%CATEGORY_SET%],[LC],'%SCOPETABLE%','%LOGTABLE%', 'A')
*COMMIT
//-- ACCOUNT TRANFORMATION END--
TO CALCULATE MONTH OPENING
*SELECT(%AccountList%, "ID", "CapAccount", "[Group] = 'Test1'")
*xdim_memberset CapAccount= %AccountList%
*xdim_memberset CapAcctDetail = FA_ExistDepr_OPE,FA_ExistDepr_CLO,FA_AddDepr_OPE,FA_AddDepr_CLO,FA_ADepr_OPE,FA_ADepr_CLO,FA_DispDepr_OPE,FA_DispDepr_CLO,FA_TranInDepr_OPE,FA_TranInDepr_CLO,FA_TranOutDepr_OPE,FA_TranOutDepr_CLO
*When CapAcctDetail
*IS FA_ExistDepr_CLO
*REC(CapAcctDetail=FA_ExistDepr_OPE,TIME=NEXT)
*IS FA_AddDepr_CLO
*REC(CapAcctDetail=FA_AddDepr_OPE,TIME=NEXT)
*IS FA_ADepr_CLO
*REC(CapAcctDetail=FA_ADepr_OPE,TIME=NEXT)
*IS FA_DispDepr_CLO
*REC(CapAcctDetail=FA_DispDepr_OPE,TIME=NEXT)
*IS FA_TranInDepr_CLO
*REC(CapAcctDetail=FA_TranInDepr_OPE,TIME=NEXT)
*IS FA_TranOutDepr_CLO
*REC(CapAcctDetail=FA_TranOutDepr_OPE,TIME=NEXT)
*EndWhen
*COMMIT
Please advice. Thanks.
Regards,
Clarissa Chung

Account Transformation CALCACCOUNT.LGF returns 0 records

Hi,
Account transformation through CALCACCOUNT.LGF returning 0 records.
Created a Account Transformation Business rule as follows -
Transformation group Name - AST
Source Account - CASH
Category - ACTUAL
Source Flow - NONE
Source DatsSrc - SYSTEM
Similarly maintained values for -
Destination Account - D_CASH
Destination Category - ACTUAL
Destination Source Flow - ENDBAL
Destination DatsSrc - SYSTEM
Source period = -1
all other values like Source Year,Apply to YTD,Remark,Level, Forced into Member are left blank.
Scrip Logic -
*RUN_PROGRAM CALC_ACCOUNT
CATEGORY = %CATEGORY_SET%
CURRENCY = %RPTCURRENCY_SET%
TID_RA = %TIME_SET%
ENTITY=%ENTITY_SET%
CALC=AST
*ENDRUN_PROGRAM
Script runs succesfully, however returns 0 records.
RUN CALC_ACCOUNT
0 SUBMITTED, 0 SUCCESS, 0 FAIL.
SCRIPT RUNNING TIME IN TOTAL:1.94 s.
LOG END TIME:2011-06-28 01:38:25
Can some one please advise on the "checks" to be performed to run the script succesfully.
I know out of experience even if a simple property is not set, script does not run.
Inputs appreciated.
Thanks.

With this, one thing to be aware of is that if you have run an account transformation rule on a data set already, and you a re-running it yet the data has not changed - there will be 0 records generated.
I recommend changing the data - do a simple zero and input data then save - then re-run, check if that works.
Nick

Account Transformation with 13 periods

Hi All,
Has anyone had experience using the account transformation using 13 periods/months? The Account Transformation business rules have properties for SourceYear and SourcePeriod. These fields can hold either a specific value (2009, 2010, JAN, P01, etc) or a relative value (+1, -3, etc).
The class that implements the transformations, CL_UJP_CALC_ACCOUNT, has a method, CALC_TIMESCOPE_P, that converts a relative SourcePeriod to an absolute SourcePeriod by first adding the relative number (example +2) to the period the transformation program is being run for (example monthNum 11) and the "rolling" years.
We are using a fiscal year variant for 13 periods and the code appears to assume that a year has 12 months. In the example above, Monthnum 11 + 2 = 13 ==> Month 13 is treated as month 1 of next year. We need it to be treated as "month" 13 of the current year.
Any, and all, suggestions are appreciated.
Thanks,
Pam

Opened message with SAP; scheduled to be an enhancement in a future BPC 7.5 NW service pack.

Business rules config does not save to UJP_ELIM and UJP_ELIMH

Hi folks,
I completed the configuration of currency translation and the calculation of ultimate ownership in a consolidation application that I am building in BPC 7.5. I then started to work on the business rules for Consolidation. These are my findings:
The first field is called Adjustment ID on the screen (but it is actually Elim ID in the Elim table and ElimH tables).
When I populate this field and save, I get an error message saying "Input rule data does not match the rule name ELIMH.
When I populate all the fields on the Auto adj defn screen and try to save or try to validate, I get the same error.
Nothing gets saved to the tables and Both the Elim and Elimh tables have no values in them.
In 7.0 NW, when I created a new adjustment id and saved, it automatically went and saved it to the database and this was the same in 5.1 as well.
What am I missing?
Would very much appreciate any light that you can shed on this.
Thank you
Tara Sitaram

Hi Tara,
Can you check that your BPC ABAP, BPC .net Server and BPC client are the same service pack?
Thanks,
John

Business rules and calculation manager

Hi ,
Could anyone pls tell me the difference between the calculation manager and business rules?

Calculation manager is a web component that is designed to manage business rules from a web interface. It is enabled to build calculations also using a graphic interface, although this mode is more suitable for simple calculations than for complex ones. Calculation manager allows you also to use complex templates that you can customize with prompts in order to adapt them to each rule without being force to change the code. Basically it is an evolution of the essbase business rules macro function. Once a business rule is created it has to be deployed in order to be used with planning applications. The deploy activity copies the rule on the database, both in the calculation manager tables in and the planning tables.
Business rules are instead essbase artifacts. They aren't available any more from version 11.1.2.2 on.
In versions older than the 11.1.2.2 you were forced to use calculation manager for epma applications, while essbase business rules were used in classic applications. In terms of calculations there is no difference between the two technologies, they behave exactly in the same way. There is only a small difference in the prompts syntax, {} in calculation manager and [] in essbase business rules.
Although i find the calculation manager web editor quite slow and imprecise to use, I anyway advice to use it in order to make eventual release upgrades easier.

Currency Translation and Account Transformation Business Rules Together?

Similar Messages

Maybe you are looking for