Caary forward of balance sheet accounts

Question

Hello,
I do have a problem with the carrying forward of balance sheet accounts. I would like to write the closing balance of the accounts of the previous month to the opening balance of the following month. It is for operative planning. I have created following business rule within the Finance application of BPC for the account technical equipment:
Account                    Account Detail      Account   Account Detail   Reverse   Data       Same    YTD
                                 (Closing Bal.)                       (Opening Bal.)    Sign    Src. Type  Period
11101020_TEEQMAOW  ACLO      11101020_TEEQMAOW  AOPE          False     ALL     False    False     
I have also created an account transformation rule with analogue specification.
I have referenced both of them in the default.lgf:
*SysLib Stored_Procedure_wrapper.lgl
RunCopyOpening(FINANCE,%RptCurrency_Set%,%Category_Set%)
*Commit
*SysLib Stored_Procedure_wrapper.lgl
RunCalcAccount(FINANCE,%Category_Set%,%RptCurrency_Set%)
*Commit
I have also tried the RunCalcAccount formula with fixed values instead of variable ones.
Before and after I send data with EVDRE, I ran the data manager default package, it runs OK, but it doesn't seem to make any calculations.
Is there any SQL logic or do I have to run the data manger differently? I already have tried some other logic from the user guide and the help, but it didn't work.
Can anybody help me, I'm happy to provide more information.
Thanks in advance!
Christopher

Answer 1

>
Tim Klem wrote:
> Hi Christopher.
>
> The SPCopyOpening works in a very specific manner -- it only copies the closing balance of the prior year's closing period (December, for example -- assuming the fiscal year matches the calendar year) into opening balance of the current period (the period for which you execute the logic).
>
> It doesn't support the ability to copy the prior month's closing period into the current period (e.g., May close into June open).
>
> In other words, SPCopyOpening is really designed to only support a YTD data structure -- YTD P&L values, and a YTD cash flow statement, for instance.
>
> If you have periodic movements, and want to copy May close into June open, you'll need to use the SPRunCalcAccount business rule. This allows you to set a relative period offset (-1), and has a few different options, and a separate business rule table setup, compared to the SPCopyOpening.
>
> Just to test if your SPCopyOpening setup is correct, you might try to load a few numbers into the prior year's December. But if the YTD data structure won't work for you, I wouldn't even waste the time -- focus on the SPRunCalcAccount syntax, and the corresponding "account transformation" business rule table.
>
> Regards,
>
> Tim
Thank you very much Tim!
I know have tried to compose a SPRunCalcAccount Logic , as well as two SQL logics. Sadly, none of them works.
SPRunCalcAccount Logic:
*RUN_STORED_PROCEDURE=SPRUNCALCACCOUNT([Finance], [CPlan1])
I have filled out the Business Rule table for the account transformation with the following information:
11101020_TEEQMAOW    ACLO  11101020_TEEQMAOW  AOPE   False     -1     False   0
Is it OK to fill in -1 for Period and to leave the data source empty?
I have written the logic in the default.lgf to test it, but nothing happened? Do I have to include a Time member?
The two script logics are as follows:
*CALC_EACH_PERIOD
*WHEN ACCOUNT
*IS AOPE, MOVEMENTS
*REC(ACCOUNT=ACLO)
*REC(ACCOUNT=AOPE,TIME=NEXT)
*ENDWHEN
AOPE stands for the Opening Balance within the Account subtable Acctdetail. ACLO stands for the Closing Balance.
*WHEN ACCOUNT.FINSTMT
*IS BS
*REC(FACTOR=GET(ACCTDETAIL=ACLO, TIME=PRIOR), ACCTDETAIL=AOPE)
*ENDWHEN
BS stands for Balance Sheet within the Account Property FINSTMT (Financial Statement).
Hope this is enough information for you. I thank you very much in advance!
Christopher