Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Implicit enhancement not showing during debugging

anish_asokan
Explorer
0 Kudos

Hi,

I have created an implicit enhancement at the end of a function module(code type) and activated the same .However, when i go to debugging, I see the code written is not shown and endfunction of the concerned FM is showing the icon of enhancement .Even after putting hard break-point and user break-points, its not getting triggered and functionality written in the implicit enhancement is as well not triggerred. Kindly help on what needs to be done to resolve the same.I tried activating in Se80 and Se19, but although its activated its showing the same issue.I tried making the implicit enhancement as declaration type , which did not help either.

Any help on this regards will be appreciated.

Thanking You,

Anish Asokan

16 REPLIES 16

jayanthi_jayaraman
Active Contributor
0 Kudos

Hi,

Check in SE19, check the runtime behaviour and check whether it is active there.

0 Kudos

Hi Jayanthi,

In Se19 it is very much active.I suppose you wanted to check runtime behaviour while executing the tcode/program.Not sure how that is helping.Kindly elaborate.

Thanks..

ipravir
Active Contributor
0 Kudos

Hi Anish,

Put a break-point in Enhancement point.

And then start your transaction. The enhancement point will not be display in Debugging mode, because it's a very much a extra logic, so it will execute, once your program reach the particular line, where you have declare the Enhancement .

that's why, put a BREAK-POINT inside the enhancement point to stop the process.

and also check, the Enhancement Point in activate or not.

regards.

Praveer.

0 Kudos

Hi Praveen,

As i mentioned earlier, although the debugger shows the enhancement is there, it is not getting triggered.Again, any type of break point is not going through the code including hard  break point.

0 Kudos

Hi Anish,

Are you facing the problem in Dev system?

Regards

Rajkumar Narasimman

0 Kudos

Hi Rajkumar,

I am implementating the same in dev for first time,so yes the issue is currently indev.

thanks..

0 Kudos

Hi anish,

I faced the same problem two times in different system. Let me share, I hope it may solve your problem.

In Dev system:

  It is due to more number of includes in implicit enhancement, I refereed some note, it pointed me to re-create the same enhancement.  Done the same and it worked in dev system.

1561880 - Implicit enhancement is not executed

In QAS System:

This is due to error in activation of TR because of some objects missed. Here I able to see the enhancement but during debugging, it is missed. TR is re-imported with the all the missed objects and it is worked fine in QAS System.

Regards

Rajkumar Narasimman

GirieshM
Active Contributor
0 Kudos

Hi Anish,

I have faced the issue twice in Implicit enhancement. I guess sometimes there is impact in implicit enhancement. I have raised OSS for the first time but I am sorry I am not aware of it now and the second time it was rectified by SP Upgrade. Check by setting the Break point in enhancement and even if it didn't gets triggered raise OSS.

With Regards,

Giriesh M

0 Kudos

HI Anish,

Implicit enhancement will not work for some T codes bec of the Version. Raise OSS note and then try.

Thanks

Paul

Former Member
0 Kudos

Hi Anish,

activate your enhancment and put hard break point. once your program reach particuler line, debug will be start. some time what happend we have implemet the code but this from/include/suboutine not execute while process the tcode.

before implement the enhacment you 1st put breakpoint on standard program line. if debug is hit  this place sure your enhacment also execute.

0 Kudos

Hi Sudhir,

even after putting the breakpoint in standard code, in debugging mode, its not going into the code implemented.In other words, the implicit enhancement is not called at runtime.

0 Kudos

Hi Anish,

Is your problem got resolved. If not kindly check by placing break-point at the beginning of the FM ME_REL_STRATEGIE_EBAN as shown below

I think Implicit enhancement is written at the end of FM ME_REL_STRATEGIE_EBAN.


I saw there are multiple check and exit conditions are written inside the FM. If those conditions are executed, then in that case the cursor will go at the end of function and it will not trigger the implicit enhancement.

Place the break point in Check and Exit condition in debugger. Kindly check the same.

Regards

Rajkumar Narasimman

Former Member
0 Kudos

Hi,

i had a similar issue. I did an implicit enhancement in a FORM and when i was debugging it the enhancement was not displayed. The problem in my case was that the include which contained the FORM was use in 2 different main programs. The enhancement is main program specific so you have to make sure you pick the right one. I also recommend to use F5 while debugging!

Kr Nicoleta

former_member306787
Active Participant
0 Kudos

Hi,

Are you working in the same client? Or is the programming and your test in 2 different clients?

If you have 2 different clients, try activating your enhancement in the other client. I've encountered this several times where it was necessary to activate it in each client and even after importing the transport to QAS/PRD.

If you have implemented a badi in SE19, check if it's a single use badi or not.

Best regards,

Zhou

Former Member
0 Kudos

Hi all.

I have the same problem to debug a implicit enhancement, but I can´t apply this sap note mentioned above because I´m using the sap version 740.

Could you help me?

davestevenson01
Explorer

I had a similar issue, where I thought my enhancement wasn't being called, but the advice above to add a hard break-point worked for me and showed my code working in the debugger.

All I would add is, rather than adding a hard break-point, use checkpoint group in transaction 'SAAB'.

This means you can turn on/off the breakpoint, rather than changing code:

I hope that helps some of you.