Couldn't retrieve inbound binding for the given P/S/A values

[Former Member]

I am finalising a PI 7.31 upgrade and i am having issues with one of the interfaces.

i have imported SAP Delivered content for HMRC, the ECC system is patched to the correct level (as this works in Production)

When i trigger the program in SAP ECC i get the following error:

  <?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="PARSING">GENERAL</SAP:Code>

  <SAP:P1 />

  <SAP:P2 />

  <SAP:P3 />

  <SAP:P4 />

  <SAP:AdditionalText />

  <SAP:ApplicationFaultMessage namespace="" />

  <SAP:Stack>com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=SAPERD320;TS=;AN=HR_GB_EFI_DPSretrieve;ANS=http://sap.com/xi/HR; at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:250) at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:171) at com.sap.aii.af.service.cpa.InboundRuntimeLookup.<init>(InboundRuntimeLookup.java:88) at com.sap.aii.af.service.cpa.impl.lookup.AbstractLookupManager.getBinding(AbstractLookupManager.java:597) at com.sap.aii.adapter.soap.web.MessageServlet.getBinding(MessageServlet.java:672) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:366) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103) at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)</SAP:Stack>

  <SAP:Retry>N</SAP:Retry>

  </SAP:Error>

I have tried reimporting the content.  i have tried rebuilding the Integration Scenarios in the ID.

i have tried calling it from an HTTP test tool, but each time i get this error...

i have checked the Cache and all show green lights in the RWB.

does anyone have any idea?

[Former Member · Accepted solution]

okay.  this has been resolved.  by the time SAP dialled in, i had my first success.

i had to rebuild everything. 

i had to make changes to all the delivered content.  every referenced object in the ESR - external definitions, service interfaces, message mapping, operational mapping, actions and integration scenarios, then save and activate it. 

then i had to delete everything in the ID and rebuild the scenario.  this did not work the first time, so i flagged the Adapter to enforce validation on the adapter which then triggered a different error.  i then removed the validation tick and the process started working!

why this scenario out of the six did not work is beyond me.  everything not in the 2011 namespace worked first time.  this one - needed a lot of encouragement....

[Former Member]

Could you please post some screenshots of the integrated configuration? Maybe there's a mismatch somewhere...

[Former Member]

Thanks again Harald

here you go:

all built from:

i have deleted everything several times and reconfigured and it always turns out the same!

[Former Member]

Hi Barry,

1. Select the Software Component Version of the Sender Interface (1st screenshot)

2. Why is there a communication party selected at the receiver? I would only use the Communication Component BC_GG_MAILBOX or ist it an A2B scenario?

Try to correct this and try again.

Best Regards

Harald

[Former Member]

Thanks for the help Harald

i have changed the SWCV to 6.04 and no difference.

yes it is an A2B scenario.

i have a message open with SAP as it is ESR  Content. i just butchered it to fit PI7.31 AEX!

[Former Member]

Ok...at the moment I have no other idea, I am sorry. Let me know what SAP says 🙂

[Former Member]

Hi Harald

i have just found the following;

https://service.sap.com/sap/support/notes/1866275

Symptom

You have a scenario where your application ack fails through the soap adapter processing with below exception noticed in XPI trace and audit log of the affected message- com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values:FP=;TP=;FS=;TS=;AN=Acknowledgment;ANS=http://sap.com/xi/XI/Message/30;

Other terms

Soap Adapter, XI protocol, Nullpointer, Acknowledgement

Reason and Prerequisites

Program Error

Solution

The issue has been resolved by code correction. The archives and the support package stack guide can be found on the SAP Service Market place as described in SAP Note 952402.

applying it now.  hopefully this may fix it....

[Former Member]

Hi Barry,

This sounds like a similar problem I recently had with some other ES Content. Did you try to check the SOAP Header of the XML sent from the backend proxy to the PI. Does this information match with the PI configuration? Maybe the PI configuration is not correct. Usually this error indicates that the configuration in the Integration Directory does not match the configuration expected by the sending system.

Best Regards

Harald

[Former Member]

Hi Harald

thanks for your response.

here is the soap header:

and this is the sender in PID.

so it seems to be the same....

even copying and pasting the details from the sender channel into an HTTP Test tool i get the same error in response!  Bizarre!

i am confused!! 

[Former Member]

Hi Barry,

Did you manually test the outbound proxy to PI with SPROXY? Did you also regenerate the proxies? Maybe something went wrong here.

Do you use AEX or Double-Stack PI, thus Integrated Configuration or classical configuration?

Best Regards

H.

[Former Member]

Hi Harald

i am running AEX single stack.

i get this error when running it via the proxy....

PARSING.GENERAL

Exception of class CX_AI_SYSTEM_FAULT