Error: .CPAObjectNotFoundException

[Former Member]

Hi Experts,

I have moved some objects from QA to Prod. message is flowing from ECC to target system which is using JMS adapter. I got the following error. Could you please tell me why i am getting the following error?

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

  <SAP:Category>XIAdapterFramework</SAP:Category>

  <SAP:Code area="MESSAGE">GENERAL</SAP:Code>

  <SAP:P1 />

  <SAP:P2 />

  <SAP:P3 />

  <SAP:P4 />

  <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=UASCC_Prod;TS=XXXxxx;AN=Test_In;ANS=xyz/pi; in the current context [Unknown].</SAP:AdditionalText>

  <SAP:Stack />

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

  </SAP:Error>

Thanks,

Srinivas

[Former Member]

The url may be wrong, please follow the instructions given under prerequisites in the following link:

Configuring the Sender SOAP Adapter - Configuring the SOAP Adapter in the Integration Directory/PCK ...

[baskar_gopalakrishnan2]

Also please use Integration Directory builder test tool and see whether all the configuration objects are in place. This is one simple approach.

[former_member184681]

Hi Srinivas,

First of all, make sure that the required Receiver Agreement does exist. If yes, then perform a full CPA cache refresh, by entering the following URL in your web browser:

http://host:port/CPACache/refresh?mode=full

Regards,

Greg

[Former Member]

Hi Grzeg,

I have tested the payload manually in the test configuration of interface determination. It was successful there. but during run time its failing.

[former_member184681]

Based on that additional info, I am almost certain that it's a cache issue. Just perform the cache refresh by opening the URL I mentioned in my previous post.

Regards,

Greg

[naveen_chichili]

Hi Srinivas,

Issue is with Cache, Just perform full cache refresh and try..

Regards,

Naveen