Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Soft warnings not seen in BAPI_CUSTOMERRETURN_CREATE

Former Member

‎2007 Apr 02 5:02 PM

0 Likes
411

I am using BAPI_CUSTOMERRETURN_CREATE to create return document via a Web dynpro app. The document does get created and I am able to review it in R3. The issue I have is some of the soft-warnings that we see in VA01, we dont see it comming via the RFC. Soft-warnings not seen are as follows:

1) Duplicate PO - If you enter an RMA with a duplicate PO via VA01, we get a message that the PO is duplicate.

2) Duplicate reference document - If a return is created w/ref to a sales document, and another subsequently created w/ref to the same sales document, a soft warning is displayed in VA01 - Create with ref option.

What param, if any, should be set in the RFC to receive these warnings?

Thanks in advance for your response.

I am using BAPI_CUSTOMERRETURN_CREATE to create return document via a Web dynpro app. The document does get created and I am able to review it in R3. The issue I have is some of the soft-warnings that we see in VA01, we dont see it comming via the RFC. Soft-warnings not seen are as follows:

1) Duplicate PO - If you enter an RMA with a duplicate PO via VA01, we get a message that the PO is duplicate.

2) Duplicate reference document - If a return is created w/ref to a sales document, and another subsequently created w/ref to the same sales document, a soft warning is displayed in VA01 - Create with ref option.

What param, if any, should be set in the RFC to receive these warnings?

Thanks in advance for your response.

Reply
1 REPLY 1
Read only

Jelena_Perfiljeva
Active Contributor

‎2007 Apr 02 8:52 PM

0 Likes
369

I don't think there is any parameter that could help, it's just the way it is, unfortunately. The problem is that the messages are kind of displayed (if you run this FM in the background in SAP you'll most likely see the warning messages in the job log), but they are not returned in the RETURN table. Hence you won't see them via RFC.

You might want to send a message to SAP about this. However, there are several notes that pretty much say that BAPIs do not work the same way as the online transaction and SAP just tried their best...

On a second thought, try BEHAVE_WHEN_ERROR flag. It could produce hard error instead of the soft error but, depending on your requirements, this might be a better option...

Good luck!