on 09-09-2010 3:29 PM
Hello,
If I want to have specific validations for journals in SAP BPC NW 7.5, do they have to be implemented in BW through the transactions UJ_VALIDATIONS with a BADI? Is there another way?
I dont want the users to enter a flow in the journals, which is afterwards calculated by the default logic.
I have tried to implement it with the rule table but it is not possible
Many thanks
Dani
Daniel,
Doesn't the journal need to include a value for every dimension in the application?
You may want to try out the EnableJRN functionality, which allows you to force the user to choose from a limited set of dimension members, which could allow you to force the user to pick a specific flow member: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/01/a889a0dba64ca2a2186696e7792a3e/frameset.htm].
Ethan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Many thanks for your reply.
As you mentioned all the dimensions have to be populated in a journal, however my problem is that for the balance sheet accounts, I dont want the users to enter the flow 999 while entering journals.
The first solutions could have been to enter the property ENABLEJRN on the FLOW dimension, but the FLOW 999 is the one used for entering P&L accounts.
I am thinking of using the BADI_UJ_VALIDATION_RULE_LOGIC, but I am afraid that this validations will not allow me to writeback any balance sheet accounts with flow 999. I need to limit it only for journals.
Is there a way to limit the dimension values when saving a journal?
Regards
Dani
Hi Dani,
You seem to have a good grasp of the problem I think you are correct that all the normal options in BPC won't work here for one reason or the other. The validation logic approach might work, but I think not for the reason you outline (can you make it only restrict posting to 999 for balance sheet accounts and not P&L accounts?).
I think you will probably have to use the write-back BADI to validate these entries or just engage in some careful end-user training on the topic.
Ethan
User | Count |
---|---|
15 | |
4 | |
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.