Error Message Debugging

Whenever you have an error in SAP you can try this approach to resolve it. There are three tricks to learn in this debugging approach:

1. Find out the error message number................................................................................................3

2. Find ABAP code where the error message is issue..........................................................................5

3. Find the related customizing to resolve the error.........................................................................11

For example you receive the following error message:

1. Find out the error message number

Since this error message is not displayed in SAP GUI (Graphical User Interface) you cannot see the error message number. If you are in SAPGUI and you can see the error message skip this paragraph. In order to find out error message in Web GUI, copy the exact text from the error.

Use the transaction SE16.

Enter table name: T100

Sometimes an error contains inserted values, in such case replace values with *. Just in case enter the first words from the error text with asterisk behind and press F8 or execute icon.

You can see that our error message has number 401 and the message class is CRM_PRIDOC_COM.

2. Find ABAP code where the error message is issue

Use the transaction SE91. Enter message class and message number and press on Where-Used List icon.

Always select all options and hit enter.

Double click on the short description.

Leave cursor on IF statement which wraps up both error calls. Click on external breakpoint icon. In case you receive an error in SAPGUI you can use an internal breakpoint which is icon left of external breakpoint. Advantage of internal breakpoint is that it gets deleted once you log out. External breakpoint remains set. Also be particularly careful with setting up an external breakpoint for RFC user. It may stop for everybody logged in the system and you will receive their debugging screens on your computer and they will be not able to continue unless you press F8 on those debugging screens.

You will see the ext. breakpoint icon placed on the left side of the coding line.

Please note that the external breakpoint does not get deleted after 2 hours so be diligent to delete the breakpoint once you finish you troubleshooting.

By debugging you can see that the table for Pricing Procedure Determination: CRM_PRCPROC_DET does not contain values for:

O 50000125 30 H 600000

Now how did I know that the table is for Pricing Procedure Determination? You can firstly look at what is a description of Function Module. In our case it was not translated to English. Never mind. From the description of the Function Group you can get idea that it is related to Price Determination.

The easiest thing is to double click on the table name in the function module.

You will get to the table definition (where you can get if you the transaction SE11). Here, you can see not the perfect translation, but better than nothing. In order to find where you can find related customizing, click on the Contents icon.

3. Find the related customizing to resolve the error

Leave cursor on the first field and press F1 for help on this field.

Path: SAP Customizing Implementation Guide -> Customer Relationship Management -> Basic Functions -> Pricing -> Pricing in the Business Transaction -> Determine Pricing Procedures

In case the first field does not bring you to correct customizing try other fields.

Click on New Entries.

Enter the missing entry:O 50000125 30 H 600000

And save it.

After you save, go back and you should see it in the overview screen: