Debugging a Popup Window
Sometimes we might want to start debugging from a
popup window / information message, in this case we cannot type "/h"
as the “OK Code” box is not available.
Method 1: From any SAP windows press the
“Customize Local Layout” button (Alt + F12) and select
“Create Shortcut…” Select
system command in Type and and put /h in Command Provide desktop in location
and click on finish. A file
is generated on your desktop. Now drag the file onto the popup window /
information message or click on file and debugging is enabled!
Method 2: Create a notepad file with below
details:
[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommand
Then
save the above text file as a batch file. You can name it as debug.bat for example.
Debugging a Popup Window
Sometimes we might want to start debugging from a
popup window / information message, in this case we cannot type "/h"
as the “OK Code” box is not available.
Method 1: From any SAP windows press the
“Customize Local Layout” button (Alt + F12) and select
“Create Shortcut…” Select
system command in Type and and put /h in Command Provide desktop in location
and click on finish. A file
is generated on your desktop. Now drag the file onto the popup window /
information message or click on file and debugging is enabled!
Method 2: Create a notepad file with below
details:
[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommand
Then
save the above text file as a batch file. You can name it as debug.bat for example.
How to debug a background
job which is running in an endless loop
Now
imagine that you have a background job that is running and running, and you
want to analyze its behavior. Just use the Process
Overview (transaction
SM50), select the running process, and choose from the transaction menuProgram->Debugging.
Now
imagine that you have a background job that is running and running, and you
want to analyze its behavior. Just use the Process
Overview (transaction
SM50), select the running process, and choose from the transaction menuProgram->Debugging.
How to debug a finished or
crashed background job
Now
just imagine that your background job finishes its execution so quickly, that
you don't have a chance to attach a debugger to it in the Process Overview (SM50), or even worse: it crashed with
a dump and you need to analyze what caused the dump. Just choose your job in
the Job Overview (transaction SM37) and type
"jdbg" into the command field. The debugger will start, and you just
would need to press a couple of times Return (F7) to get out of the spool
functions checks and you can debug your finished or crashed background job
online in dialog.
Now
just imagine that your background job finishes its execution so quickly, that
you don't have a chance to attach a debugger to it in the Process Overview (SM50), or even worse: it crashed with
a dump and you need to analyze what caused the dump. Just choose your job in
the Job Overview (transaction SM37) and type
"jdbg" into the command field. The debugger will start, and you just
would need to press a couple of times Return (F7) to get out of the spool
functions checks and you can debug your finished or crashed background job
online in dialog.
Hi, This is shalini from Chennai learned SAP Training in Chennai from mr.karthick. The training really was good and i got selected in leading mnc company as SAP Consultant.
ReplyDeleteYou can contact 8122241286 for Best SAP Training in Chennai or reach www.thecreatingexperts.com
Download the HP HPE2-E67 Q&A PDF file easily to prepare HPE Sales Certified – IT Business Conversations [2017] exam. It is particularly designed for HP HPE2-E67 exam and our HP specialists have created this HPE2-E67 Question Dumps observing the original HPE2-E67 exam.
ReplyDelete