topic Re: BAPI Return Errors in Application Development and Automation Discussions

BAPI Return Errors

Former Member — Fri, 19 Oct 2012 10:44:27 GMT

I am using BAPI_ACC_DOCUMENT_CHECK/POST to post to fb01.

there are some cases in which this bapi returns error with no PARAMATER or ROW.this make it difficult to identify which exact line item is causing error.

1-is there any way to identify exact ;line items in such cases

2)--is there any way to get list of all errors return by this BAPI.i was thinking if we can filter by ID/NUM of error messages can atleast identify such messages?

Re: BAPI Return Errors

ThomasZloch — Fri, 19 Oct 2012 14:13:26 GMT

Not all errors are specific to an item, there is header data checks and there are checks on the complete document, e.g. a zero balance.

Not sure what you mean with 2), please clarify.

Thomas

Re: BAPI Return Errors

Former Member — Fri, 19 Oct 2012 14:19:36 GMT

hello,

check the message class used in the BAPI and it includes. From that you will know the errors/warnings.

best regards,

swanand

Re: BAPI Return Errors

Former Member — Fri, 19 Oct 2012 14:23:06 GMT

Agree with header checks and zero balance which is overall document issue.

But say one of my line items has a GL account ,whose fieldstatus configuration has marked profit centre has mandatory.

then if i dont pass it through BAPI, then

its returning me an error saying

Field Profit Ctr is a required field for G/L account 0100 190’

and this partciular error comes without any line number.

So this is a case where error returns with no line number although it is not header data /zero balance case.

So i need to know the generic nature of just messages.what causes them to produce no line number.or list of message ids?

Re: BAPI Return Errors

ThomasZloch — Fri, 19 Oct 2012 14:30:01 GMT

Well, to find out why that particular check is not returning the ROW number you would have to dive into the code. It is even possible that some messages are condensed before RETURN is being filled, so that you don't see so many identical messages, e.g. when the same G/L account is concerned and used in many items.

Thomas