03-29-2016 9:02 AM
Hi,
In my project, i have a requirement in which i have to deactivate many BADIs. Is there any tool to do this easily.
03-29-2016 10:10 AM
Hi.
What do you mean by BADIs ? Custom BADIs?
In that case you should know that CL_EXITHANDLER is the standard class to GET INSTANCE of a BADI.
IF you bypass this get instance for your BADIs, you'll deactivate all instances of BADIs... but it's not a solution.
For you I suppose you should implement a custom report, receiving your BADIs' name list, with a batch input that replicate deactivation from SE19 transaction, including in a transport request.
Hope to help
Bye
03-29-2016 10:25 AM
That's true for classical BADIs, but not for Kernel BADIs, which are instantiated by the statement GET BADI. Please consider.
03-29-2016 10:23 AM
Maybe you could use the switch-framework. We use it to switch between an old addon-implementation and a new one. Our solution is to assign the switch to a package in which all the BADI implementations are located. If we switch off the switch all depending BADI implementations are de-activated. (In our case we have of course two packages and two switches, whereby only one of the switches can be active at one time.)
03-29-2016 2:34 PM
Write a simple BDC with the help of SE19. Would take you less time to implement.
03-29-2016 3:27 PM
Isn't there a simpler way to break the system... if that's what you are trying to do?
Thanks.
03-29-2016 3:36 PM
Hi,
why were 1000s of badis active in the first place?
Usually these actions are part of a clean up project where every badi is checked against current business requirements and then evaluated if it can be deleted or merged with a different badi implmentation.
Kind regards, Rob Dielemans
03-29-2016 3:42 PM
Exactly my point... shouldn't this be done by analyzing each individual BADI and its impacts - rather than submitting a program and waiting for it to finish?
Thanks