need some debugging tips or ideas to debug a standard bapi

[Former Member]

hello abap gurus

I am trying to debug my program which is calling a standard bapi BAPI_QUOTATION_CREATEFROMDATA2.

When i try to call this program I am getting an error message '112 enter sold-to-party'. I have been sending that variable but still keep getting this error message. However, when I run manually I don't see this.

I have been calling committ transaction bapi also.

So my question is as follows.

BAPI_QUOTATION_CREATEFROMDATA2 calls several other functions which inturn are calling other functions and so on.

So I want to see if there is an easier way to search this function tree to see where exactly this message

'112 Enter Sold-To-Party' is getting generated.

Your help will be highly appreciated.

Thanks

Ram

[Former Member]

Hi,

First just put on the debugger by giving /h. Once the control stops at the first statement then use breakpoint---->Break Point at statement-->give the statement as 'message' thus it will put the break points on for all 'Message' statements in the pgm. Keep on observing the control till it comes to the error code you are interested in.

OR

If you know the message code then SE91---->Give message class & Message no & use ;Where use' button. Put the break point on all those statements.

I hope this helps,

Regards

Raju Chitale