on 03-06-2013 5:23 AM
hi bpc gurus:
I m enrolled on a financial planning project with BPC NW 10, what I d like to ask here is about how to implement the the mirror register, what do I mean by "mirror register" ? It s for example I m planning an account of "Profit and Loss Statement" for a Entity, profit center, period and year; when I finish entering the amounts and press "Save" button, I want the system to create (automatically) a mirror register on "Balance Sheet Statement", considering this way that every account on "profit and loss" has to have a mirror account on "balance sheet".
For example:
I input:
Year=2014
Period=01
Entity=Company1
Account= X1
Profit center= PC1
Amount = 5000
at pressing "save", bpc saves 2 lines on the model:
Line 1:
Year=2014
Period=01
Entity=Company1
Account= X1 (account of P&L)
Profit center= PC1
Amount = 5000
Line 2: (mirror register)
Year=2014
Period=01
Entity=Company1
Account= Y1 (account of BS) ---> in some point the system must know that Y1 is the mirror account of X1
Profit center= PC1
Amount = 5000
How you guys have faced this situacion before?
I m considering these options:
option 1: using a script logic which calls a BADI, this script would be called in default.lgf
option 2: create some properties in account dimension to tell the system what account is the mirror of the original account and save it using a script logic
Regards
jav
Hi Jav,
As you said that you want this to be done while clicking on the save button, this would mean that the code should be maintained in the default logic. This is not advisable; since you might be using other planning templates also for sending other type of data, however, these templates will also execute the default script and that puts load on the system, unnecessarily.
This is a standard requirement in lot of projects; since P&L, BS and CF are inter-related statements.
For these type of requirements, we typically use account transformation BR. However, you can use a script for doing this, but should be executed separately (not through default).
Your points are correct. But I wont suggest to keep the logic in default script.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jav,
We have a working example where the information is entered in one cube and in default.lgf some calculations are done by script logic and the results are stored in another cube. The first cube is a sales planning cube where the users enter price, quantity and discount and the net sales is calculated in the script logic and copied to the P&L cube. Due to the fact that each planner is working with a limited sub-scope there are no performance issues.
We have net sales account in both cubes, in the sales cube the account dimension have a property: PLACCOUNT where the target account of P&L cube is defined. Copy is done in default.lgf using DESTINATION_APP and is based on the PLACCOUNT property.
B.R. Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
any help about it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
16 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.