on ‎2015 Jul 09 7:33 AM
HI EXPERTS,
Can you Please explain that how many write back BADI's one can have in a BPC implementation & can we link the BADI with particular input schedule.
Thanks
Request clarification before answering.
If you want to execute a BADI only for one input schedule,
use the Custom Logic BADI, call it in a script logic and link this script to a DM package.
Add a button to your input schedule which executes this DM package.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Wouter,
Not sure that the button in the input schedule is the desired solution - it's not an equivalent of write back badi data processing... In reality it's always possible to find some universal criteria to check in write back badi to work correctly for all input schedules.
Vadim
Sample:
You have account PRICE that is maintained in the DUMMY member of CUSTOMER dimension.
In default.lgf you perform calculations like [ACCOUNT].[QTY]*([ACCOUNT].[PRICE],[CUSTOMER].[DUMMY])=AMOUNT for each specific customer.
If user will change PRICE the AMOUNT have to be recalculated for all customers. And it's better to perform this recalculation in the write back badi (to have instant result) or to launch DM package after data entry. Default.lgf is not a good option for PRICE changes.
"Write Back Badi's for scenario's like Currency Conversion" -??? Why?? In most cases you don't need currency conversion to happen immediately!
Inside single write back badi you can check for particular environment and model and use different code...
Vadim
P.S.
IF ( I_APPSET_ID = 'SIMDEV' ) AND ( I_APPL_ID = 'ADVSALES' ).
...
Hi Natasha,
You can have as many different implementations of same BADI as many different combinations of Filter parameters you can come up with. So, in your case since APPSET_ID and APP_ID are fixed you can have 3 write-back BADIs: MAN, DM and JRN. But if you need it for Input templates only then it's only ONE.
Sorry to inform you:),
Gersh
"can we link the BADI with particular input schedule" - NO! And it's a bad idea in general. All data send to the cube using any input schedule will be processed using the same write back. Inside write back badi you can have conditions based on scope...
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Natasha,
There is only one write back, so you must be-careful what you put in it as it will affect all your write back actions.
What do you want do to? modify write back should be the last resort.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 41 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.