Cannot perform RFC lookup

Hi All,
We are getting below error in doing testing in PI mapping.
Cannot perform RFC lookup com.sap.aii.mapping.api.StreamTransformationException: Cannot perform RFC lookup at com.sap.aii.mappingtool.flib7.RfcLookup.cacheMore(RfcLookup.java:105) at com.sap.aii.mappingtool.tf7.rt.AMultiResIterator$MultiOutIterator.gotoNextContext(AMultiResIterator.java:95) at com.sap.aii.mappingtool.tf7.rt.C2CFunctionWrapper.cacheContext(C2CFunctionWrapper.java:77) at com.sap.aii.mappingtool.tf7.rt.C2CFunctionWrapper.gotoNextContext(C2CFunctionWrapper.java:42) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:317) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:410) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:410) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:410) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:410) at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:502) at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133) at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:632) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.transformInternal(ExecuteXiMappingCommand.java:197) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.execute(ExecuteXiMappingCommand.java:94) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.GeneratedMethodAccessor701.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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 $Proxy1525.execute(Unknown Source) at sun.reflect.GeneratedMethodAccessor700.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314) Caused by: com.sap.aii.mapping.lookup.LookupException: Connection to system RUNTIME using application RUNTIME lost. Detailed information: Error accessing "http://sapdevpid01:51000/run/system/int?container=web" with user "PIREPUSER". Response code is 401, response message is "Unauthorized" at com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:103) at com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:86) at com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClient.getSystemAccessor(LookupServiceProvider.java:73) at com.sap.aii.mapping.lookup.LookupService.getRfcAccessor(LookupService.java:258) at com.sap.aii.mappingtool.flib7.RfcLookup.cacheMore(RfcLookup.java:78) ... 52 more Caused by: com.sap.aii.utilxi.hmi.api.HmiCoreException: Connection to system RUNTIME using application RUNTIME lost. Detailed information: Error accessing "http://sapdevpid01:51000/run/system/int?container=web" with user "PIREPUSER". Response code is 401, response message is "Unauthorized" at com.sap.aii.utilxi.hmi.api.HmiCoreException.newCommunicationError(HmiCoreException.java:85) at com.sap.aii.utilxi.hmi.api.HmiHttpJDKClient.sendRequestAndReceiveResponse(HmiHttpJDKClient.java:184) at com.sap.aii.utilxi.hmi.api.HmiClientAdapter.invokeMethod(HmiClientAdapter.java:92) at com.sap.aii.ibrep.server.lookup.SystemAccessorHmiClient.<init>(SystemAccessorHmiClient.java:50) at com.sap.aii.ibrep.server.lookup.SystemAccessorHmiClient.getInstance(SystemAccessorHmiClient.java:71) at com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:96) ... 56 more Root Cause: com.sap.aii.mapping.lookup.LookupException: Connection to system RUNTIME using application RUNTIME lost. Detailed information: Error accessing "http://sapdevpid01:51000/run/system/int?container=web" with user "PIREPUSER". Response code is 401, response message is "Unauthorized" at com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:103) at com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:86) at com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClient.getSystemAccessor(LookupServiceProvider.java:73) at com.sap.aii.mapping.lookup.LookupService.getRfcAccessor(LookupService.java:258) at
Thank you very much for advance.
Ferran

hi
Check in SM59 the RFC destination is working fine
Check the RFC communication channel is without error
also
Please check if the RFC is imported properly and you are using RFCLookup function in the mapping.
Check if you have completd the parameter creation

Similar Messages

Can not perform RFC lookup

Hi All,
We are getting below error in doing testing in PI mapping.We are calling a RFC function module in PI.
Cannot perform RFC lookup com.sap.aii.mapping.api.StreamTransformationException: Cannot perform RFC lookup at com.sap.aii.mappingtool.flib7.RfcLookup.cacheMore(RfcLookup.java:105) at com.sap.aii.mappingtool.tf7.rt.AMultiResIterator$MultiOutIterator.gotoNextContext(AMultiResIterator.java:95) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:299) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:395) at com.sap.aii.mappingtool.tf7.AMappingProgram.processNode(AMappingProgram.java:395) at com.sap.aii.mappingtool.tf7.AMappingProgram.start(AMappingProgram.java:482) at com.sap.aii.mappingtool.tf7.Transformer.start(Transformer.java:133) at com.sap.aii.mappingtool.tf7.AMappingProgram.transform(AMappingProgram.java:612) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.transformInternal(ExecuteXiMappingCommand.java:197) at com.sap.aii.ibrep.server.mapping.exec.ExecuteXiMappingCommand.execute(ExecuteXiMappingCommand.java:94) at com.sap.aii.ib.server.mapping.exec.CommandManager.execute(CommandManager.java:43) at com.sap.aii.ibrep.server.mapping.ServerMapService.execute(ServerMapService.java:40) at com.sap.aii.ibrep.server.mapping.MapServiceBean.execute(MapServiceBean.java:40) at sun.reflect.GeneratedMethodAccessor743.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) 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 $Proxy1621.execute(Unknown Source) at sun.reflect.GeneratedMethodAccessor742.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:234) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304) Caused by: com.sap.aii.mapping.lookup.LookupException: Exception during processing the payload. Error when calling an adapter by using the communication channel BigWRFCReceiver (Party: , Service: KD3_300, Object ID: 4dcd47e22ff0367ea3779fe0e9dc7fd2) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. com.sap.aii.mapping.lookup.LookupException: Error when calling an adapter by using the communication channel BigWRFCReceiver (Party: , Service: KD3_300, Object ID: 4dcd47e22ff0367ea3779fe0e9dc7fd2) XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:92) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:55) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:140) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:73) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:167) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:212) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:337) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:238) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:532) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:670) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71) 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:71) 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:71) 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:71) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247) Caused by: com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: 'error while processing the request to rfc-client: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. Cause Exception: 'com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=KD3.AP.CSPLC.ORG SYSNR=22 GWHOST=KD3.AP.CSPLC.ORG GWSERV=sapgw22 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.227.148.123:sapgw22' not reached TIME Fri Aug 6 02:11:46 201 RELEASE 710 COMPONENT NI (network interface) VERSION 39 RC -10 MODULE nixxi.cpp LINE 2778 DETAIL NiPConnect: 10.227.148.123:3322 SYSTEM CALL connect ERRNO 239 ERRNO TEXT Connection refused COUNTER 27 '. at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214) at com.sap.aii.af.service.api.AdapterAccess.call
Please sugets how to resolve this issue.
Thanks
Mohit

Hi Mohit,
Do full CACHE refresh.
http://<host>:5<sys#>00/CPACache/refresh?mode=full
This may solve the issue.
Thanks,
Vijay.

Cannot perform RFC Look UP

Hi All,
When I executed the RFC Look up function in the mapping could see the following error.
"Run time exception when processing target field mapping. Cannot perform RFC Look Up".
I performed the below steps but still could find the same error again:
1.In the test tab of the message mapping I have assined a channel which I configured in the Interface determination of the configuration and also assigned a value to that channel.
2. Has given the values for the parameters in the operation mapping and also the binding is done successfully.
3. The function module I assined is also existing and could test the same for output values for the given input values.
Please help me resolve the error.
Thanks & Regards,
Kumar.

Hi,
This is the error I could see in the communication channel monitoring of RWB.
"Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>"
Help me with this error.
Thanks,
Kumar.

Cannot perform Bean lookup on signed Applet jar

Hi All,
I'm after developing an applet which runs from a number of jars on an Orion app server. Each one of these jars are signed and I can access the Applet okay. The problem is that I make remote reference to EJB's throughout the application. I cannot perform a Bean lookup on a signed jar. The only way it can be done is when the Client is granted all permissions. The client should pop up an option to grant permissions.

If u are signing all the jar file along with the applet it should work
It does work fine with me. my code given below
note that i carry the following jar files along with my applet jar.
orion.jar,ejb.jar,,jta.jar,jnet.jar,jsse.jar,jcert.jar,parser.jar
and have them in my archive attribute of my html code for the applet
also all these jars are signed
hope this helps
regards
raees
public void init()
     try
          Hashtable env = new Hashtable();
          env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
          env.put(Context.PROVIDER_URL, "ormi://solomon:23791/helloApp");
          env.put("java.naming.security.principal", "admin");
          env.put("java.naming.security.credentials", "secret");
          Context ic = new InitialContext (env);
          HelloHome hello_home = (HelloHome)ic.lookup("HelloBean");
     Hello hello = hello_home.create ();
          System.out.println (hello.helloWorld ());
     }catch(Exception e)
          e.printStackTrace();

Can we test RFC lookup from IR?

Hi All,
Can we test RFC Lookup from IR-Message mapping? If yes How?
Like we can test Graphical mapping in test tab of Message Mapping.
Regards

Hi Sarvesh,
got it...
But when I am displaying queue.
I am getting POPUP window saying -->
Problem When Displaying Queue
Cannot perform RFC lookup
Can you please guide how to resolve this?
Since RFC Lookup in run time uses Receiver RFC adapter.
I tested RFC adapter is configured properly.
Regards

Problem in RFC Lookup

Hi,
I am performing RFC lookup using Communication Channel.
I have used a function called "Z_MATERIAL_DETAILS".
Input to this function is "MATERIALID" and Output of the function is "MATNR".
I am using the following code in my UDF for performing lookup::
//write your code here
final String CHANNEL_NAME = "CC_RFC_LookUp",
 VALNOTFOUND = "VALUE_NOT_FOUND",
 SAPRFCNS = "urn:sap-com:document:sap:rfc:functions",
 TAG_FM = "Z_MATERIAL_DETAILS",
// TAG_QTB = "QUERY_TABLE",
 TAG_QFL = "UOMCODE"; //UOMCODE
 DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
 DocumentBuilder builder = null;
 factory.setNamespaceAware(false);
 factory.setValidating(false);
 try {
 builder = factory.newDocumentBuilder();
 } catch (Exception e) {
 // trace.addWarning("Error creating DocumentBuilder - " + e.getMessage());
 result.addValue(e.toString());
 Document docReq = null;
 try {
 // Building up RFC Request Document
 docReq = builder.newDocument();
 Node root = docReq.appendChild(docReq.createElementNS(SAPRFCNS, TAG_FM));
 root.appendChild(docReq.createElement(TAG_QFL)).appendChild(docReq.createTextNode(resultFieldName[0]));
 } catch (Exception e) {
 // trace.addWarning("Error while building RFC Request - " + e);
 result.addValue(e.toString());
 // trace.addInfo("RFC Request XML: " + docReq.toString());
 // Lookup
 Payload result1 = null;
 try {
 Channel channel = LookupService.getChannel("EC1CLNT800", "CC_RFC_LookUp");
 RfcAccessor accessor = LookupService.getRfcAccessor(channel);
 InputStream is = new ByteArrayInputStream(docReq.toString().getBytes());
 XmlPayload payload = LookupService.getXmlPayload(is);
 result1 = accessor.call(payload);
 } catch (LookupException e) {
 // trace.addWarning("Error during lookup - " + e);
 result.addValue(e.toString());
 // Parsing RFC Response Document
 Document docRsp = null;
 try {
 docRsp = builder.parse(result1.getContent());
 } catch (Exception e) {
 // trace.addWarning("Error when parsing RFC Response - " + e.getMessage());
 result.addValue(e.toString());
 //trace.addInfo("RFC Response XML: " + docRsp.toString());
 String res = "";
 try {
 res = docRsp.getElementsByTagName("UOMTEXT").item(0).getFirstChild().getNodeValue();
 } catch (Exception e) {
 // trace.addWarning("Result value not found in DOM - " + e.getMessage());
 result.addValue(e.toString()+VALNOTFOUND);
 result.addValue(res);
Code in Z_MATERIAL_DETAILS ::
""Local Interface:
*" IMPORTING
*" VALUE(UOMCODE) LIKE MARA-MFRPN OPTIONAL
*" EXPORTING
*" VALUE(UOMTEXT) LIKE MARA-MATNR
*" EXCEPTIONS
*" val_not_found
select single matnr from mara into uomtext where mfrpn = uomcode.
if sy-subrc <> 0.
raise val_not_found.
endif.
ENDFUNCTION.
When i send three material ids the function module will access the R/3 system thrice which will give rise to PERFORMANCE ISSUE.
So,is there any way to send all the materialids at one time to Function module and similarly receive all the MATNR from Function at once,so that we need to access R/3 system only once.

HI,
Check this link for passing table parameter in JCO call.
http://www.sapdevelopment.co.uk/java/jco/jco_callfunc.htm
Following is the code for retrieving table parameter in JCO call to function BAPI_PO_CREATE.
JCO.Table return_tab = function.getTablesParameterList().getTable("RETURN");
if (return_tab.getNumRows()) > 0 {
// Output the error messages
return_tab.firstRow();
do {
 System.out.println(return_tab.getString("MESSAGE");
while (return_tab.nextRow());
} else {
String PO_NUM = function.getExportParametersList().getString("PURCHASEORDER");
System.out.println("Purchase order " + PO_NUM + " created");
Thanks and Regards,
Sandeep Maurya.

Error While RFC Lookups

Hi
I am performing RFC Lookups in my java code and when ever I am testing this java mapping code from Operation Mapping Test Tab, I am getting following error.
Error while lookup Connection to system RUNTIME using application RUNTIME lost. Detailed information: Error accessing "http://pmichsappid16.app.pmi:8016/run/system/int?container=web" with user "PIREP_PID". Response code is 500, response message is "Internal Server Error"
Error while closing accessor Technical error when calling an adapter remotely. The HMI method with the ID close was called with an incorrect session status. The system accessor object is missing.
Could you please tell why I am getting this error.
Note:1) When I am testing it end to end my code is working fine with out any errors.This happens only when I am testing it from operational mapping test tab.Previously I am able to execute my code from operational mapping test tab also.
2) I am also closing accessor object in proper manner.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!PI 7.1 Strange behaviour!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Hi Prasanna,
I was facing the same error while testing JDBC lookup in the operational mapping. The problem was that while testing in the operation mapping or message mapping tab you need to provide the RFC channel created manually in the parameter. While end to end testing this is binded in the integration directory object,
I provided the JDBC channel created for lookup manually in the operation mapping and i got the result.
Hope this will help.
Thanks
Ajay Garg

Cannot resovle the Symbol error in UDF - Java mapping - RFC Lookup ?

Hi Friends ,
We are working on Java mapping - UDF for RFC Lookup . It is giving the Cannot resolve Symbol for all imported archive java class files even if we give again all imported files in import section of UDF we are still getting the same cannot resolve error .
We are using SP 12 of XI 3.0 . What could be the reason ?
Thanks.,
V.Rangarajan

Hi,
Can you try to open imported archive in IR and check if the path(folder structure like com.abc.xyz.etc) for classes is same as in import statement in UDF.Since we had experienced the same problem.
Thanks.
Regards,
Shweta

RFC Lookups codepage

Hi guys,
I am using RFC API to perform some lookups from within my mapping program.
In order to create the request in XML, I am using DOM xml parser.
My code works fine when input data is in English, but when it is in another language, e.g. Greek, input data is respresented wrongly in XML document.
The ppiece of code where I create the XML request is the following:
Document docReq = null;
// Building up RFC Request Document
docReq = builder.newDocument();
RFCInterfaceLine il = null;
Element documentElement = docReq.createElement("ns0:" + remoteFunctionName);
documentElement.setAttributeNS("http://www.w3.org/2000/xmlns/", "xmlns:ns0", "urn:sap-com:document:sap:rfc:functions");
Node root = docReq.appendChild(documentElement);
rfcInterfaceParametersLines = rfcInterfaceParameters.getLines();
for (int i = 0; i < functionParameters.size(); i++)
il = (RFCInterfaceLine) rfcInterfaceParametersLines.get(i);
if (il.getParameterType().equalsIgnoreCase("I"))
root.appendChild(docReq.createElement(il.getParameterName())).appendChild(docReq.createTextNode((String) functionParameters.get(i)));
RFCInterfaceLine is a class used to represent the parameters (inputs, outputs and exceptions) used by the Remote Function Module in ABAP. "I" stands for Import. So when I have an import parameter, I create an element in XML.
However, in the final XML document I cannot see as a header the encoding = "UTF" attribute. Is this the one that is missing to enable other languages as well??
Evaggelos

Hi refer these
If you want to use DOM, you'll also have to choose a parser, since DOM's specification doesn't specify a parser, just document and element handlers, so there are various implementations of parsers for DOM. I've used Xerces's DOMParser (org.apache.xerces.parsers.DOMParser) on Java Mappings with success (never tried on UDF, though) and it's very simple.
After you get the output stream from the rfc lookup, just use:
DOMParser parser = new DOMParser();
InputSource input = new InputSource(in);
parser.parse(input);
Document MyDoc = parser.getDocument();
to get the Document object. Then you can use regular DOM methods to get the value.
For example, with
String value = MyDoc.getDocumentElement().getFirstChild().getNodeValue();
you'd get the value of the first child of the root element.
following document on XI Mapping lookups RFC API by Michal?
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-code-samples/xi%20mapping%20lookups%20rfc%20api.pdf
Mapping lookups u0096 RFC API
Mapping Lookups (New)
http://help.sap.com/saphelp_erp2005/helpdata/en/0f/f084429fb4aa1ae10000000a1550b0/frameset.htm
For Mapping Lookups~
/people/alessandro.guarneri/blog/2006/03/27/sap-xi-lookup-api-the-killer
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
This blog and article deals with calling your RFC from your JAVA MAPPING / User Defined Function.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/801376c6-0501-0010-af8c-cb69aa29941c
Java Mapping
http://help.sap.com/saphelp_nw04/helpdata/en/e2/e13fcd80fe47768df001a558ed10b6/content.htm
DOM parser API
http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/package-frame.html
On how to create XML docs with SAX and DOM go thruugh these links:
http://www.cafeconleche.org/books/xmljava/chapters/ch09.html
http://www.cafeconleche.org/books/xmljava/chapters/ch06.html
Also go through these Blogs....
/people/prasad.ulagappan2/blog/2005/06/08/sax-parser
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-i
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-ii
/people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-iii
/people/sravya.talanki2/blog/2005/12/21/use-this-crazy-piece-for-any-rfc-mapping-lookups
Thanks !!

"Cannot perform operation, connection is closed" with Open MQ 4.4

I am using Sun MQ 4.4 with Glassfish 2.1.1 on Red Hat 5.7.
I am able to install glassfish cluster and all the instances are running fine. But, when I try to send a message to a topic, I get following exception
javax.jms.IllegalStateException: [C4062]: Cannot perform operation, connection is closed.
at com.sun.messaging.jmq.jmsclient.ConnectionImpl.checkConnectionState(ConnectionImpl.java:2468)
at com.sun.messaging.jmq.jmsclient.XAConnectionImpl.createSession(XAConnectionImpl.java:105)
at com.sun.messaging.jms.ra.ConnectionAdapter.createSession(ConnectionAdapter.java:383)
Following is part of the stateless EJB where I am creating the session.
@PostConstruct()
private void init() {
if (connectionFactory == null) {
if (log.isTraceEnabled()) log.trace("Connection factory not set. Retrieving from server context.");
InitialContext ic = new InitialContext();
connectionFactory = (ConnectionFactory) ic.lookup("jms/testConnectionFactory");
if (log.isTraceEnabled()) log.trace("Creating JMS connection.");
connection = connectionFactory.createConnection();
@WebMethod()
public void send(){
Session session = null;
session = connection.createSession(true, Session.SESSION_TRANSACTED);
I am trying to install these on a couple of new machines. Same application works on other machines so I am guessing this is a configuartion issue somewhere on these servers.
My question is what would be a good way to find the cause of this failure.
I have turned on log level to finest for ejb-container, jms, RA through glassfish Admin console, but no useful information.
Also, I don't have the name of the servers in DNS yet. I am using IP address for specifying instances.
Any suggestions ?
Thanks
Vineet

Hi Tom,
I used the demo/helloworld/helloworldmessage.java sample.
By the way, I should add that the broker log contains lines like:
[B1066] Closing [email protected]:2461 because "[B0061]: Client exited without closing connections"
Is this what one would expect for a connection.close() ?
It almost seems that this is happening only when the connection is nulled explicitly or the connection object is destroyed.
One last thing:
I was led down the garden path. The reason for the server being thread starved was that there were indeed connections not being closed/nulled.
Thanks in advance,
Patrice
Edited by: paubry04 on Sep 13, 2007 8:21 AM

RFC Lookup API error in PI 7.1?

Hi Guys,
The RFC lookup which has been developed in PI 7.0 using the lookup API is unable to find the CC defined in the directory for a business system. after upgrading to PI 7.1. We are getting the error as below. This look up works perfectly fine in Dev(PI 7.1) and QA(PI 7.1) but in Prod(PI 7.1). We are on PI 7.1 EHP1 SP03.
Errorcom.sap.aii.mapping.lookup.LookupException: Plain exception:Error when calling an adapter by using the communication channel In_RFC_SAPLookUp (Party: , Service: Test, Object ID: 74e5e47336133351bebcb8c6a6bc68c8) The channel with object ID 74e5e47336133351bebcb8c6a6bc68c8 could not be found in the Integration Server Java Cache. Check if the channel exists in the Integration Builder Directory and execute a refresh of the Java Cach.
We did the cache refresh and also restarted the prod server but the error still persists. We have tried connecting to the prod receiver sap system from QA and the lookup works perfectly fine. We dont understand why it dosent work in prod.
any help or suggestions would be really appreciated.
Thanks,
Srini

Hi Rajesh,
The CC has the correct business system. We have also tried even by creating a new cc and it always says it cannot find the defined cc from the RFC lookup. We are passing this value as a constant value to the RFC lookup.
I could not understand why it is not finding only this CC? Is this something that RFC lookup is unable to find the CC?
any help would be appreciated
Thanks,
Srini

Exception Handling in RFC lookup

Hi Experts,
I have a query in RFC Lookup function working with PI 7.1, file to Idoc scenario.
I am using Enhance Receiver Determination to find the dynamic recivers.Here we have used a Functional Module which gives an output according to the the input parameter (which comes from input file). thus i have used RFC lookup to the remote system to fetch this info from FM.
Problem -
When the remote system is down or if the RFC lookup attemped & exceptions raised for some reason (RFC user authority has been changed & it was not able to perform the intended Job at remote system) , the message stuck in queue and block the several other messages from another interfaces which belongs to teh same queue.
Queries-
This is not allowed in production as it affects other services.
1>how can we handle the RFC lookup exception (in case of remote system is down or if the RFC lookup exception)
2>how can we perform Local lookup at PI box rather then remote lookup (the FM fetches the data from remote system)
3>Is Value mapping is relevant in this case raher the RFC lookup ? I am not sure as the values are dynamic & selected as per the FM's output.
Please provide your valuable insight .
Thanks in advance !
-Jyoti

Hi Jyoti,
Answer for your 3 question.
1. RFC lookup will get execute on R/3 so if R/3 is down there no way that your RFC lookup will work as expected.
2. So if R/3 is down or RFC not able to get receiver system due to some problem.. then in that case.
          On your Receiver determination at bottom
          Configure u201Cif no receiver found proceed as followingu201D
           In this you can have 3 option.
                    a. Error message u2013 if you select this the transaction will end with error message in SXMB_MONI
                    b. Ignore: if you select this execution will get ignored and there will not be any entry in SXMB_MONI
                    c. Select the following receiver. You can select this and can configured default receiver system in case if RFC not able to determine receiver then interface will get route to receiver system configured here.
3. As you mentioned values are dynamic then Value mapping doesnu2019t make any sense here. RFCl ookup is the right option and above are few other option in case you RFC lookup flailed.
Thanks,
Bhupesh

Message-Mapping: Use same RFC lookup for different target fields

Hello,
I need to apply an RFC Lookup which delivers a boolean flag back (true or false). This RFC lookup should be used for different target fields.
Is there a way to execute the RFC lookup just once and then store the result in an internediate variable that I can use for all futher checks for different target fields?
If this is not possible and I have to apply the RFC lookup for all necessary target fields is it then executed for each target field ? This is exactly what I want to avoid in order not to slow down performance.
The input parameter (=source field value) would be the same.
Thank you for your advice!

Exactly.
Here is a UDF example I have that you could adapt to your needs.
Set
public String setCounter(String a,String b,Container container){
/* Store values in global datacontainer
a: mapping value and return valueparameter
b: name for stored value parameter
GlobalContainer myGlobalContainer;
myGlobalContainer = container.getGlobalContainer();
myGlobalContainer.setParameter(b.toUpperCase(), a);
return a;
Get
public String getCounter(String a,Container container){
//write your code here
GlobalContainer gc = container.getGlobalContainer();
if (gc.getParameter(a) != null) {
return String.valueOf(gc.getParameter(a));
} else {
return "1";

RFC Lookup Table Parameters Reusability

Dear All
My Requirement is to Map fields in IDoc from the File data ,there are some fields in idoc for which i need to fetch data from SAP.
For this i am using RFC Look up. i am retrieving values from table parameters for RFC.
and this Table parameters are being used muliple times in Mapping.
Right now i have to execute the same RFC for set of input data atleast 5 r 6 times.
This is effective Performance of the Interface
Is there any concept of Reusuability in RFC Lookup while Mapping in PI.?
Can we use Java Initialization section in mapping for executing the RFC once and using the output data in table parameters while mapping various target fields.
Hoping for a Positive Reply
Regards
Bhasker

Hi,
1) If it is PI 7.1 there are mapping enhancements, such as
a) Variables for storing intermediate mapping value,
b) for RFC lookup etc.
you can find the 7.1 pdfs from SDN
2) you can have a two stage mapping, putting them sequentially in Interface mapping object.
First step : Source to Target (orignal target structure)
here you can do all the mapping and also One time RFC lookup, but leaving the other fields where you need the lookup values again
Second step : Target to Target
here already mapped target becomes your input & you know the fields which have the value & the fields that you need to map again and all other fields are one to one mapping.
Regards
Vishnu

Code Sample: Easy RFC Lookup From XSLT Mappings Using a Java Helper Class

Hi everyone,
This is just a shameless plug for my article: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/05a3d62e-0a01-0010-14bc-adc8efd4ee14">Easy RFC Lookup From XSLT Mappings Using a Java Helper Class</a>. I hope you're interested in reading it, and I welcome your comments in this thread.
Kind regards,
Thorsten

Hi Stefan. Thanks for your post. I have already done that. It still does not work. As a base for my java helper class I have usesd Thorstens code.
The problem is quite confusing. I will try to ouline both issues here.
First of all, when try to test from within the Operation Mapping, I always get a java error saying it cannot find the communication channel (it is there and working because I have tested it with the RFCLookup in graphical mapping). I have found a way to work around this, and that is to uncheck the "Use SAP XMLToolkit" checkbox --> switch to test tab, enter my ReceiverService in the parameter tab (header parameter) --> switch back to Definition tab, check the "Use SAP XMLToolkit" checkbox --> switch to Test tab and run the test. Then the XSLT and call to java helper class will work. Of course this is not really something you want to do all the time. Maybe there is a bug.
Secondly, it never works when I try to do it "live". I am using a file adapter to pick up one file, convert it and a file adapter to drop the converted file. I get the following error code in SXMB_MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">TRANSFORMER_CONF_EX</SAP:Code>
<SAP:P1>ATJ_Accounting2XML_Accounting.xsl</SAP:P1>
<SAP:P2>http://rd.accounting.logica.com</SAP:P2>
<SAP:P3>fd552c30-bad9-11dd-9761-c21dac1b818c</SAP:P3>
<SAP:P4>-1</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>TransformerConfigurationException triggered while loading XSLT mapping ATJ_Accounting2XML_Accounting.xsl; http://rd.accounting.logica.comfd552c30-bad9-11dd-9761-c21dac1b818c-1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Using an XSLT without a call to a java helper class, works just fine.
I am totally at a loss here. Any more input would be much appreciated.
/Patrik

Cannot perform RFC lookup

Similar Messages

Maybe you are looking for