Debugging Problem

[former_member186413]

Hi Expert,

It's great, if someone tells me how to find the location of when the exception is threw or it set up a paticular value for SY-MSGID, SY-MSGTY and etc.

The backgroud is the program calling the BAPI funcation for creating a Sale Order,  meanwhile, it usally create the deliver oder  for the sales order. but sometimes it depends on the material, the deliver order wouldn't be created.  Thus, I need to know when it sets Sy_MSG* parameter in the program, so to  ping-point the problem from the material's data.

[arindam_m]

Hi,

Try doing it by the Breakpoint at.. feature in the breakpoint menu. You can set it for a particular message. The Other option is Watchpoints on SY-MSG parameter.

Cheers,

Arindam

[former_member186413]

Ya, I have used this method, but it dosn't work. It seems it detect something from the buttom of message, but never show up the location of the code.

[arindam_m]

Hi,

Not clear on what location you looking for. But if you observe the Stack in desktop2 in the debugger should give you a idea of the flow that might help you to get to the exact point.

Cheers,

Arindam

[Former Member]

Hi,

Set a break point at statement Message. Thanks.

Best Regards

Ravi.

[Former Member]

Hi Hai,

When you get the error click on it it will open a window with message.

Click on the technical details ICON it will give you the MSG ID and MSG No.

Now debung the program again.

Create Watch point

SY-MSGTY = 'E'

SY-MSGNO = the message no

SY-MSGID = the message id.

Also press F9 it will open the breakpoint window

Select the Message TAB and enter the same details

Also set the UPDATE DEBUGGING feature on so it halts even if you are getting in an update function.

Regards

[Former Member]

Hi,

Activate SQL Trace using ST05 then run your Program or T-Code, after error goto ST05 and deactivate SQL trace , Now Goto Log and serach for message it will give you excat location and program name.

Regards,

Salil Chavan

[Former Member]

Hi,

are there any differences in the BAPI's RETURN table in both cases? Then you can get the information there. Otherwise table VBFA might help you solving your issue.

For there are many possible reasons that delivery order will not be created, the messages may differ.

Regards,

Klaus

[former_member186413]

Thanks  Klaus, your answer might close to what I want.  Another Question that I want to ask is, how you are going to solve the problem via the VBFA table?

[Former Member]

VBFA has the SD document flow. Basically, you can check if any delivery was created for a particular sales order number.

[former_member188827]

Please see if following link helps:

http://help.sap.com/saphelp_nw04s/helpdata/en/c6/617cbee68c11d2b2ab080009b43351/content.htm

Regards

[Former Member]

Hi!

There a two presentations around by SAP's Olga Dolinskaja on the new feature of ABAP Debugger Scripting (requires SAP NetWeaver 7.0 EhP2) - from what you have described (exception traceability) the use of ABAP Debugger Scripting solves your problem.

Each presentation takes less than ten minutes to watch - and it's definitely worth the time.

Type	Link
basic usage demonstration	http://scn.sap.com/docs/DOC-10249
advanced topics demonstration	http://scn.sap.com/docs/DOC-10250

Regards,

   Chris

[Aiolos]

please use this tool to achieve your requirement

[nabheetscn]

Hi

Basically what i think is the BAPI is filling the return table rather than throwing messages starightaway. It will be good if you can track where the return parameters are filled. Put a watchpoint or check some gloabl variable being set as indicator of error.

Nabheet

[gaurab_banerji]

sometimes not catching exceptions can lead to dumps. check if the FM return has exceptions and add them in the function call