topic Re: turn on / off implementation is active in Application Development and Automation Discussions

turn on / off implementation is active

Former Member — Wed, 14 Oct 2009 07:09:09 GMT

HI All ,

I have a badi and i want to do to him unit test ,

in the badi there is flag implementation is active .

my question is if i can turn on / off this badi flag from outside ,i.e. program etc

since I want to do for him unit test .

Regards

Chris

Re: turn on / off implementation is active

matt — Wed, 14 Oct 2009 08:35:08 GMT

As you can do it via SE18/19, then it can be done programatically. Try debugging the code that's triggered when you deactivate manually.

matt

Re: turn on / off implementation is active

Former Member — Wed, 14 Oct 2009 08:42:58 GMT

HI Matt ,

I try it without success

there is FM or method which can manage this flags ?

Regards

Chris

Edited by: Chris Teb on Oct 14, 2009 12:36 PM

Re: turn on / off implementation is active

matt — Wed, 14 Oct 2009 11:31:42 GMT

I won't tell you directly what the FM is, but it took me about 2 minutes. Instead I'll tell you how to do it.

In SE19, change your BADI implementation. Start the debugger, hit the deactivate button. Debug through till you're in the processing of the okcode. ( Module "ok_code" of SAPLSEXO ). The function module is obvious. When you've found it, post the answer here.

When you've found the name of the function module, look at it through SE37. Then click on "Display Object List" to see the other function modules in the group.

If you find these things out for yourself, you'll develop very useful skills for the future. Anyway - try again, following my guidelines above.

regards

matt

Re: turn on / off implementation is active

Former Member — Wed, 14 Oct 2009 11:57:52 GMT

Thanks Matt

When deactivate and debug it I get

CALL SUBSCREEN : SUBS_1,

SUBS_2,

SUBS_3,

SUBS_4,

SUBS_5,

....

i inside the screen i dont see any FM except the field catalog FM

Any Idea?

Regards

Chris

Re: turn on / off implementation is active

matt — Wed, 14 Oct 2009 12:48:10 GMT

What I do is:

Go into implementation in change mode from SE19. Enter /h in the okcode box. Hit "deactivate". In the classic debugger (though not the new one), I set a breakpoint in the flow logic, to stop at MODULE ok_code.

I then single step into that module. And have a quick look at the ABAP. It appears that the field "ok_code" is the one being tested to decide what to do. It has the value DEACTIVATE. I step into the form common_ok_code, but it appears DEACTIVATEisn't one of them. So I keep single stepping. I get to case ok_code.. Then next step I get to is WHEN seex_deactivate. A quick look at the code below the WHEN, and I see FM: SXO_IMPL_DACTVE - which has one parameter, imp_name, which is my implementation name!

I then look at the function group of SXO_IMPL_DACTVE, and find there is also a function module SXO_IMPL_ACTIVE.

The only wrinkle in this is that there might be some global parameters being set by a previous call to another function module in the same group, earlier on. So you might need to set a breakpoint within a few other FM in the same group, and go through the process again, so you can get the right sequence of function module calls.

matt