Hello Everyone,
In UJ_VALIDATION tcode on certain Appset ID, I have created some rules based on a certain driver dimension 'ACCOUNT'. Rules 1 to 12 are defined through logic table and work well. Rules 13 onwards are to be processed through BADI "BADI_UJ_VALIDATION_RULE_LOGIC". I have created a custom enh. implementation and then implementated a BADI over this. Assigned an implementing class which has a method do_validation_logic. The entire built looks fine but somehow the logic do not work.
Now to make the BADI logic work, I have 4 questions:
1) In UJ_VALIDATION transaction, the text_box to input the BADI's name is not present. It simply is disappeared. Will the click on BADI button then by default take the above mentioned BADI.
2) Even though I have put a break-point, after save of data on BPC, the debugger does not break into the above method. Can any one indicate as to why this may happen. Debug user is assigned to the relevant BPC user. Also as mentioned in the blog "Troubleshooting BPC NetWeaver Data Manager Packages", I have put an external breakpoint to the run_package method, and the debugger successfully breaks into this method, but no further processing happens.
3) Do I have to create a filter necessarily? The filter can be created by the combination of Application ID, Dimension, and Rule Number.
4) DO_VALIDATION_LOGIC method has a parameter IS_DATA. What kind of structure and data this parameter holds.
Please suggest in addition to above, if I may have missed any more vital points.
Thanks in advance.
Regards,
Pankaj.