Help, XIServer:NO_MAPPINGPROGRAM_FOUND

[Former Member]

Hello, I am doing a scenario is SOAP ->RFC. The function module is 'RFC_read_table' ,and I am getting the following error. I tried to modified  the mapping and reactive ,refresh the cache, also restart the PI server, but the error always came.

How can I do? What is the problem?

Thank you all.

<SOAP:Body>

      <SOAP:Fault>

         <faultcode>SOAP:Server</faultcode>

         <faultstring>Server Error</faultstring>

         <detail>

            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

               <context>XIAdapter</context>

               <code>ADAPTER.JAVA_EXCEPTION</code>

               <text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:NO_MAPPINGPROGRAM_FOUND:

          at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1192)

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

          at java.lang.reflect.Method.invoke(Method.java:592)

          at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)

          at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

          at $Proxy519.process(Unknown Source)

          at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:287)

          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

          at java.lang.reflect.Method.invoke(Method.java:592)

          at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)

          at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

          at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)

          at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

          at $Proxy307.process(Unknown Source)

          at com.sap.aii.adapter.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:187)

          at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:513)

          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:469)

          at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:299)

          at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)

          at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)

          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:84)

          at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

          at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)

          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)</text>

            </s:SystemError>

         </detail>

      </SOAP:Fault>

   </SOAP:Body>

[former_member184681]

Hi,

Check the SAP Note 1523941 - PI mapping errors: RESOURCE_NOT_FOUND and NO_MAPPINGPROGRAM_FOUND, it looks like a relevant one for your problem.

Regards,

Greg

[deviprasad_pothireddy]

Hi,

I have also faced same problem,

some times, I have seen strange errors like , quantity filed error, seen many dumps at SAP ecc/r3 side in st22. some times, I did not see any dump also, but getting same error. Some time I have jco error.

Finally I have rectified the problem by changing password in rfc communication channel.

So, check your rfc user has proper authorizations or not, that user expired or not, locked or not. this helps you to solve this problem

Regards,

Deviprasad.

[Former Member]

Is this a standard RFC or custom one?Please test your RFC by giving the proper input parameter.Please check all PI configuration as well.make sure you are giving the proper credentials for RFC channel.

Thanks

[Former Member]

Hi mahani,

It's standard RFC.

Thank you very much.

[rhviana]

Hi Liu,

Could you post the image of test scenario into Directory ? Also the SP's lvl of machine ?

Yesterday I was with the problem in SAP PI 7.3 AEX because the sp's was old.

Thanks

[rhviana]

Hi Liu,

This error it´s caractecs when during the PIPELINE in integration engine could not find the correspondent programa mapping in java stack.

Could you do CPA FULL CASH refresh and after that sxi_cache, maybe your problem will fix after that.

Thanks man

See ya.

[rhviana]

Hi Liu,

One question the sender adapter are you using SOAP/ XI 3.0 and you create the URL ? If yes, you must change SOAP / HTTP.

Because I got the same error here with the same scenario.

Kind regards,

Viana.

[Former Member]

Hi Viana,

The sender adapter I used SOAP/HTTP.

Thank you.

[baskar_gopalakrishnan2]

Few cents...

1) Please check in your interface determination whether you specified right or valid message mapping object

2) Check in your operation mapping whether you specified request and response accordingly for the source and target messages.

3) Did you made changes to mapping object and activate recently. If so you can refresh the cache one more time

4) As previous experts mentioned, could be due to short dump error in the target system.

[iaki_vila]

Hi Liu,

Few cents, check st22 in the endpoint as Greg says

http://scn.sap.com/thread/1969289

With this kind error you could check this steps:

1. The Mapping in the Request is correct. Check in the sxmb_moni that you produce a correct xml to the RFC.

2. Check no errors in st22 ECC endpoint with your call. Check manually the RFC with the same parameters.

3. Check the RFC out in the sxmb_moni, take the XML from monitoring and test it in the ESR.

Regards.

[Former Member]

Hi Vila,

I found some errors with st22, and I don't understand what it really means.

Thank you very much.

[iaki_vila]

Hi Liu,

This st22 log seems to me the XI abap-side st22 log, it's neccesary to study the ECC endpoint log, in order to study if the RFC call failed. In the ECC, also you could filter with the user with you make the connection.

Normally ,DDIC and SAPSYS users are not used as communication users, forget them in this case

Regards

[former_member184681]

Hi,

Search the SDN with "XIServer:NO_MAPPINGPROGRAM_FOUND" phrase, you will find numerous useful hints that I do not wish to repeat here, as they are already described in details in the other threads. To start with, make sure that the function module you are calling doesn't cause a short dump in the receiver system.

Regards,

Greg

[Former Member]

Hi Greg,

I used T-Code ST22, and find some errors I didn't know how to solve it.

and the detail is below.

Thank you very much.

[former_member184681]

Hi,

It sounds like good news for you, since the problem is not related with your PI development. It is strictly related to the ECC objects you are trying to reach from PI. As a solution, implement the following SAP Note in ECC:

Note 1229062 - DDIC_TYPELENG_INCONSISTENT in package SWNC

Regards,

Greg