Outbound proxy error

[Former Member]

Hi,

My scenario is SOAP(XI protocol)-PI-File.  ECC_Q is old ECC_NQ is new ECC system. Scenaio is working good in ECC_Q ,now we are trying to send proxy message from ECC_NQ to PI . We didnt change any configurations at PI side, since we are using soap adapter with XI 3.0 Message protocol. Same scenario worked in Dev without any changs in PI.

We have sent 1 proxy message fromSAP System, it is failed in ECC system itself with below error ..

It is nt reaching PI system. We checked below configurations in ECC System.

1)      RFC Destination – Its pointing to PI correctly

2)      SLDAPICUST  - PI SLD  server is checked

3)      SLDCHECK – Connectivity working ..

Pls let me know what other details need to check ???

<SAP:Stack>com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=ECC_NQ;TS=;AN=SI_ESKER_OUT;ANS=urn:MAS:SAP:ECC:FINANCE:ESKER; at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:237) at com.sap.aii.af.service.cpa.impl.lookup.CommonLookup.getInboundBinding(CommonLookup.java:167) 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:519) at com.sap.aii.adapter.soap.web.MessageServlet.getBinding(MessageServlet.java:875) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:439) 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:162) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81) at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:124) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:83) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) 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.MemoryStatisticFilter.process(MemoryStatisticFilter.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.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) 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:428) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) 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:327

Thanks

--Jeevitha

[Former Member]

Hi ,

This  scenario was working fine in Dev env.  but its not working in Dev also today.

Getting below error in moni (ECC side)

<SAP:Stack>com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values:

Pls guide me what needs to check here

Thanks

Jeevitha

[markangelo_dihiansan]

Hi Jeevitha,

You need to create a sender cc and sender agreement for that.

Regards,

Mark

[Former Member]

Hi Vadim and Mark,

But we have nt created  new sender details(ECC_ND) in dev env. it is same as before (ECC_D).

It is ICO sceanrio.

Thanks

--Jeevitha

[vadimklimov]

Hello Jeevitha,

It should be there in Development environment as well. When the proxy call reaches PI, PI will look for the respective binding searching for sender party, business system name, interface and namespace - and the respective object (in your case, ICo) should be there before a message can be handled and processed by PI.

Can it be so that you didn't have a new business system maintained in SLD, but the new ECC system replaced the old one and had the same name (ECC_D)? In this case, transition from old ECC to new ECC will be transparent for PI since neither business system name, nor interface name changed. Otherwise, I would expect you either receive similar error as in QA environment, or corresponding new ICo object should have been configured in advance.

Best regards,

Vadim

[Former Member]

I agree with Mark. There is some of your objects that are missing or inactive.

Regards,

Jannus

[Former Member]

Hi Vadim,

We didnt do any changes in dev environment , ECC_D(MED) is pointing to old ecc only, we are using ECC_ND for new ECC system(MCD).

Since it is SOAP sender channel (using XI message protocol) we are not giving any details here... Pls clarify ,.

Thanks

Jeevitha

[vadimklimov]

Hi Jeevitha,

Well, I would still suggest to create an ICo and corresponding SOAP-XI sender channel for your new ECC system. It shold not work without doing so, since the original channel has an old ECC system as the communication component, and PI's runtime will not be able to find the appropriate bidning if the proxy call comes from a different business system for which ICo is missing.

Regards,

Vadim

[vadimklimov]

Hello Jeevitha,

You should have the scenario maintained in Integration Directory of your PI system, which would correspond to the new sender SAP ECC system. Depending on installation option and release of the PI system you use, it can be classic scenario or any of Java-only scenarios (Integrated Configuration or Integration Flow). Please check if the corresponding scenario where the sender component is ECC_NQ, sender interface SI_ESKER_OUT in namespace urn:MAS:SAP:ECC:FINANCE:ESKER, is maintained in Integration Directory. If it is not maintained, please configure it (can be done by making an adjusted copy of the old scenario for ECC_Q). If it is already maintained, check CPA Cache in the PI system and ensure that it is in there.

Best regards,

Vadim