How should the client handle standard BAPI errors ( BAPI_Salesorder_create )

[Former Member]

External Non SAP system is calling a BAPI for creating salesorder ( BAPI_Salesorder_create )
They want to know list of all possible errors that bapi can give and how to handle them.

For e.g. they want to know when to fill extra fields and resumit the request or just ignore the response as it is duplicate request etc..

My Q is Standard BAPI will have lot of possible errors. How can we give entire list. What should our answer be to the external system?

[DoanManhQuynh]

usually message is returned in a table and external system use it to show the message. what error could be there depend on the BAPI function, which there is no list about it. you may try to search inside BAPI for where the message raised, but i don't understand why external system need to know it, they just have to display error and end user would know what they missed.

[UweFetzer_se38]

Sorry, there is no answer to this question. This BAPI is so huge, the calls within the BAPI are going deep in the sales module, that you can't create a list of all possible errors. Alone the Message Class "V1" has around 900 different messages.

I think you have to focus on standard errors like missing fields or wrong unit of measures etc.

[Abinathsiva]

Hi, Hema s,

bapi returns messages can be captured for individual line item to an internal table and same can be listed or given in file output to user.

below mentioned image may be irrelavent to order creation but this is result screen of complete Order processing in add Sales Order error message in one field...

[FredericGirod]

The documentation of the BAPIs could be found in transaction BAPI. But there is not list of all possible errors