topic Re: Tracing BAPI_INQUIRY_CREATEFROMDATA2? in Application Development and Automation Discussions

Tracing BAPI_INQUIRY_CREATEFROMDATA2?

Former Member — Thu, 28 Jun 2007 20:01:20 GMT

We're trying to create Inquiries with configurable materials using BAPI_INQUIRY_CREATEFROMDATA2. We're passing the structures inquiry_cfgs_value, inquiry_cfgs_ref, inquiry_cfgs_part_of, inquiry_cfgs_ref and inquiry_items_in and are able to configure simple scenarios. However, when we try to create more complicated Inquires we get the very generic "Internal error: 10, 000010, NOT_ALL_INPUT" error message and the document is not created. I think we're passing bad configuration data however it is difficult to troubleshoot. Is there a way to trace this where we could get more meaningful error info?

Much Thanks,

Greg

Re: Tracing BAPI_INQUIRY_CREATEFROMDATA2?

Former Member — Thu, 28 Jun 2007 20:50:58 GMT

You have to get the message id and the number from the RETURN parameter of the BAPI. You can then do a search for this in the BAPI code. Sometimes it may be coming from some other function modules called from within the BAPI. So it will take some digging. You can also try SE91, give the message ID and number and then look at it's where-used list.

Once identify where the error is issued from, you can either put a breakpoint there or you can deduct the error from the code before that.

Re: Tracing BAPI_INQUIRY_CREATEFROMDATA2?

Former Member — Fri, 29 Jun 2007 21:02:46 GMT

I revisted CUTRC and found the reason I wasn't seeing logged data was I needed to apply a couple of notes. I'm in business. Thanks, Greg

Re: Tracing BAPI_INQUIRY_CREATEFROMDATA2?

Former Member — Fri, 29 Jun 2007 21:03:19 GMT

Answered.