Application Development 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: 

BAPI Fails in XI

Former Member

‎2006 Jan 24 1:01 AM

0 Kudos
80

Hi Guys

we were using a custom BAPI until a few days ago and something weird happened.we have a BAPI_SALESORDER_CHANGE customized to our needs.if we use this BAPI to add a line item to the SO,it works perfect but when we try cancelling a line item,it fails from XI showing the following error

<?xml version="1.0" encoding="UTF-8"?>

<ns15:salesOrderModifyResponse xmlns:ns15="http://ls.sbc.com/OMS/salesOrderCreate"><sapOrderNo></sapOrderNo><sapOrderStatus></sapOrderStatus><sapMaterialAvailabilityFlag></sapMaterialAvailabilityFlag><sapRevisedAvailabilityDate>0000-00-00</sapRevisedAvailabilityDate><errorReturn>0</errorReturn><return><item><errorCode>V4</errorCode><errorMsg1>ORDER_HEADER_IN has been processed successfully</errorMsg1><errorMsg2>VBAKKOM</errorMsg2><type>S</type></item><item><errorCode>V4</errorCode><errorMsg1>ITEM_IN has been processed successfully</errorMsg1><errorMsg2>VBAPKOM</errorMsg2><type>S</type></item><item<u><b>><errorCode>V1</errorCode><errorMsg1>Reason for rejection

is not defined</errorMsg1><</b></u>errorMsg2>

</errorMsg2><type>E</type></item><item><errorCode>V4</errorCode><errorMsg1>Error in ITEM_IN 020000</errorMsg1><errorMsg2>VBAPKOM</errorMsg2><type>E</type></item><item><errorCode>V4</errorCode><errorMsg1>SCHEDULE_IN has been processed successfully</errorMsg1><errorMsg2>VBEPKOM</errorMsg2><type>S</type></item><item><errorCode>V4</errorCode><errorMsg1>Sales document 0040000396 was not changed</errorMsg1><errorMsg2>0040000396</errorMsg2><type>E</type></item></return></ns15:salesOrderModifyResponse

the BAPI still works flawless from R/3 and does what is needed.if we plug in the request from XI into R/3 it works.now there is no BDC in here which can fail due GUI problems.this is a standard BAPI call.

it would be great if anyone can suggest anything?

we have pretty much tried out all our options.

Thanks a lot for your patient reading.

take care

1 REPLY 1

Former Member

‎2006 Jan 24 10:40 PM

0 Kudos
48

Hi Guys

we found the culprit.the XI parser was passing some garbage values to R/3 after we did an upgrade.that was the reason R/3 was taking a dump.

regards,

Sanket