Async SOAP to Proxy interface using ICO giving error in ECC

[Former Member]

Hello Gurus,

I am trying to use ICO for a Async SOAP to Proxy call on ECC. I was able to successfully test the Synchronous calls but the Async call is giving an error in ECC.

I created a XI 3.0 channel on SAP side where I generated Inbound proxy and am trying to save the data to a DB table.

I used the same channel for Sync scenario and it is working without any issue, I am unable to get the Async interface working.

I am getting the following error on ECC side,

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

- <!--  Call Integration Server

  -->

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

  <SAP:Category>XIProtocol</SAP:Category>

  <SAP:Code area="PARSER">UNEXPECTED_VALUE</SAP:Code>

  <SAP:P1>Main/@versionMajor</SAP:P1>

  <SAP:P2>000</SAP:P2>

  <SAP:P3>003</SAP:P3>

  <SAP:P4 />

  <SAP:AdditionalText />

  <SAP:ApplicationFaultMessage namespace="" />

  <SAP:Stack>XML tag Main/@versionMajor has incorrect value 000; expected value is 003</SAP:Stack>

  <SAP:Retry>M</SAP:Retry>

  </SAP:Error>

Please let me know what could be the issue here.

Thanks,

Paul.

[Former Member]

Hello,

The error I am getting is the following,

Any idea what could be the reason ?

Thanks,

Paul.

[former_member186851]

After applying the note your getting this error?

Make sure your proxy code is active.

[Former Member]

Hi Raghuram,

Yes, the Proxy is active.

Thanks,

Paul.

[former_member186851]

Paul,

Since you moved from Sync to Async,

Do a consitency check in the sproxy and also ensure Execute_Async code is in place and correct.

[Former Member]

Hello Raghuraman,

My PI installation is on 7.1 EHP1 and I suppose use of Execute_Async is not needed as I use SI rather than MI. Please correct me if I am wrong.

[nitindeshpande]

Hi Paul,

Yes, Execute_Async is only required for PI version <7.0 and not for >7.1.

For your problem, please try to implement the correction mentioned in the below note -

1349125 - Error in communication between ABAP Proxy Application & AAE

Regards,

Nitin

[Former Member]

Resolved the issue.

I tried various options like using a different namespace etc.,

Main reason is,

The root node of the input and output messages must be same, i.e. for the Async interface to work without the Operation Mapping, both inbound and outbound Service interfaces should use the same Message type.

[former_member186851]

Hello Paul,

Check this note-1748814