How to troubleshoot SAP messages

1.Many times you may have SAP message that does not make good sense or otherwise difficult to understand. See an example of such message in Excel row 3 below.

Note: There are 4 different types of SAP messages.

•     E: Error message. This type of messages must be fixed. Intended action was not successful.

•     W:Warning  message. This type of messages indicates something wrong and action MAY be required by you. However, transaction was able to pass beyond this message. Generally this also means, (If there was no other Error message present,) transaction was successful despite this warning message.

•     I: Information message. This type of messages are only for information purpose. Usually       no action is required for them.

•     A: Abort message. This type of message indicates some internal errors and are similar to

Error messages.

"Status" column in Excel will indicate what type of message it is along with message class and ID assigned in your SAP system.

(See a separate note on how to control what and how many message should Process Runner report)

2. You can run the transaction in Debug or Step-by-Step mode and further diagnose this problem.

There are two Debug options in Process Runner. Debug - All or  Debug -Error.

Debug - All: This option will show you all the screens in SAP GUI, one after another in sequence you recorded.

Debug - Error: This option directly takes you to first Error screen in SAP GUI. If you have a very large transaction and if you want to quickly go to Error screen, use this option.

3.Click on "Debug - All" icon and follow the instruction

Note: You can also access this from pull down menu "Edit" -> Run - Stop All"

4.You will be prompted with SAP Logon prompts. Select correct SAP system and provide Logon information.

5.SAP GUI with your transaction and data from Excel row 3 will be displayed. You will also notice a small floating "OK Code" window. Within this "OK Code" window you will see a "Green Check Mark". Pressing this "Green Check Mark" takes you to next screen.

Note: You will see that data from  Excel is already filled in with red color and "OK Code" is already inserted in "OK Code" window. This "OK Code" is coming from your original recording and is also visible in "Mapper" (Advance view)

6.Press "Green Check Mark" and ask SAP to go to next screen.  If there is any problem, SAP will report that issue in yours screen.

Notes:

1.   You have option to correct the transaction and move forward by pressing Enter key or       simply exit the transaction and take corrective action later.

2.   In example above, it's Error message. So you cannot continue to next screen without correcting the problem. If this was a Warning or Information message, you can simply       press Enter and continue to the next screen.

7.Once you exit out from current transaction, either by correcting the data and pressing Enter or by aborting the transaction as explained at the end of this document, Process Runner may ask if you want to Debug another transaction or not.

Selecting "Yes" will stop further debug process.

8.At any time, you may terminate the transaction by typing /NEND in "OK Code" window and clicking on "Green Check Mark"

Note: If you execute the transaction in debug mode, it will actually save your transaction unless you exit out before it saves.