Application Development and Automation 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: 
Read only

Debugging is not Triggering inside Function Module Exit.

yarnagula_sudhir
Active Participant
0 Likes
3,211


Hi Experts,

In IDOC Scenario, my code is inside a Function Module Exit/Include.

In which Session and External Debugging are ON. Still debugging mode is not coming in this scenario.

Where as Code is getting executed and I'm getting the respective IDOC's.

Previously its working fine. I've checked all Debugging settings. But still I've didnt found the solution.

Kindly find the below pictures and help me out.

1.

2.

3. SICF:

4. SRDEBUG

With Regards,

Sudhir.

1 ACCEPTED SOLUTION
Read only

yarnagula_sudhir
Active Participant
0 Likes
2,410

Hi All.

I've found a temporary solution in case of Debugging point not triggering inside the code.

1. Make a logic of Infinite loop.

Data: CH.

Do.

If CH = 'X'.

EXIT.

Endif.

Enddo.

2. Execute your Program.

3. Go to TCode: SM50. As its infinite loop, due to performance issue, you will get the respective program details in SM50.

4. Now Goto Debugging option provided in SM50. Make CH = 'X'. and Debug your Code.

Note: Even though its not permanent solution, we can try this way. Let me know if any one has better solution.

With Regards,

Sudhir.

5 REPLIES 5
Read only

former_member182877
Participant
0 Likes
2,411

Hi Sudir,

1. Please make sure your EXIT is active!

2. Keep the break-point in the 'Calling' place and check whether it is getting triggered.

External debugging point is enough i think.

Cheers,

Kripa RAngachari.

Read only

0 Likes
2,411


Hi Kripa,

The Problem here is with the Debugging. Its not even stopping either at Session nor at External Debugging point.

Yes, my Enhancement/Project/FM and Include are Active. Still the issue is Same.

Find the solution which I'm posting below.

With Regards,

Sudhir.

Message was edited by: Yarnagula Sudhir

Read only

karthikeyan_p3
Contributor
0 Likes
2,411

Hi Yarnagula,

Set the update debugging ON. (Point 2). It should stop if it is getting triggered in update task.

Also set the breakpoint in

Function Module: IDOC_OUTPUT_DELINS_FAB

PERFORM call_user_exit_final_fab

and give a try.

Make sure you have additional session while debugging.

Thanks,

Karthikeyan

Read only

0 Likes
2,411


HI Karithikeyan,

1. Yes, I've tried with Update Debugging ON, but still it didn't stopped.

2. As the Process Code is ME13, I've tried with FM IDOC_OUTPUT_DELINS_FAB. But still the issue is Same.

Find the solution which I'm posting below.

With Regards,

Sudhir.

Read only

yarnagula_sudhir
Active Participant
0 Likes
2,412

Hi All.

I've found a temporary solution in case of Debugging point not triggering inside the code.

1. Make a logic of Infinite loop.

Data: CH.

Do.

If CH = 'X'.

EXIT.

Endif.

Enddo.

2. Execute your Program.

3. Go to TCode: SM50. As its infinite loop, due to performance issue, you will get the respective program details in SM50.

4. Now Goto Debugging option provided in SM50. Make CH = 'X'. and Debug your Code.

Note: Even though its not permanent solution, we can try this way. Let me know if any one has better solution.

With Regards,

Sudhir.