Process Orchestration 7.4 : Error in receiver SOAP channel for abap proxy

[sunilchandra007]

Hi,

We have created ICO in Process Orchestration 7.4 for File to abap proxy scenario with receiver SOAP channel(XI protocol).

When we run the scenario, it is received successfully in SAP when checked with sxmb_moni. But in PI monitoring the message goes in waiting mode with the receiver soap channel in error state. After 1 rety by default, it process the message successfully with warning.

Error

Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: Unexpected exception caught while executing mapping: com.sap.aii.adapter.xi.routing.RoutingException: Unable to retrieve interface determination: No interface determination set in lookup context.

Warning

SOAP: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: System Error Received. HTTP Status Code = 200: However System Error received in payload ErrorCode = DUPLICATE_DETECTED ErrorCategory = XIProtocol Parameter1 = 16452534617511E3A93600000076D806 Parameter2 = RECEIVER ECD ( 240 ) tpcides_ECD_00 ) tpcides Parameter3 =  Parameter4 =  Additional text =  ErrorStack = Message ID 16452534617511E3A93600000076D806 already exists in called system (pipeline RECEIVER ECD ( 240 ) tpcides_ECD_00  tpcides)
 [http://sap.com/xi/XI/Message/30^Error "DUPLICATE_DETECTED"]

It seems weird when ICO fails with error related to interface determination.

Please suggest.

[iaki_vila · Accepted solution]

Hi Sunil,

This is a known issue in prior PI releases 1796510 - Duplicate Message Handling in Java SOAP - XI Adapter, the question is if there is a patch for PI 7.4, i think the best way is that you ask directly to SAP.

Regards.

[sunilchandra007 · Accepted solution]

Thanks Inaki. If you have checked the screenshot attached, the main error is "No interface determination set in lookup context" although the message is received successfully at SAP but marked as failed at PI. Since it is marked as failed, it retries on its own by default and is updated as success with delivered status. So the duplicate message error seems the outcome of the main error.

Regards,

Sunil Chandra

[Former Member · Accepted solution]

Hi Sunil,

Were you able to resolve the issue? we are facing same issue in PO 7.4.

Thank you,
Venkat

[sunilchandra007 · Accepted solution]

I have raised it to SAP and awaiting for the response.

Regards,

Sunil Chandra

[Former Member · Accepted solution]

Hi Sunil, We are also facing the same issue. Did you get a response from SAP on this issue? Could you please let us know if the issue is resolved? Thanks, Shailesh

[sunilchandra007 · Accepted solution]

The issue was resolved by patch upgrade. Please check note 1939203 for details.

Regards,

Sunil Chandra

[Former Member]

We resolved the issue by applying note 1821649.

SAP has corrected the code in latest patch of SAP PI 7.4 SP04.

Thank you,

Venkat

[chitti_prakash]

Hi,

I am still getting the error even after upgrading the patch of SP7 of PI 7.40(to the latest one) i.e.,

XIAF PI 7.40 SP7 PL 31 and MESSAGING PI 7.40 SP7 PL 28.

Could anyone help in resolving the problem? It is very urgent and critical.

Best regards,

Prakash