Lookup using RFC & JCO.
Hi All,
We are develloping Lookup logic using custom java code.
Our Xi server is at SP12.The code is working fine in java IDE.
But when I imported classes into Repository & tested its rebooting services of XI j2ee engine & I am getting message dispatcher running no server conncted the monitoring tool shows
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"SYSTEM FAILURE" during JCo call.</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Any idea what is going wrong ?
Thanks,
Tuhin
Hi,
Did u import the required java JCO libraries into imported archives...?
Have u mentioned the same in imports of your advanced java function...?
Look at "How to Perform SAP Data Lookups Within XI Mappings" by "Jerome Delune" in articles section to perform the lookup.
But i personally recommend you to upgrade the server to SP13 and use the new lookup API's provided. U can refer to "XI Mapping lookups RFC API" article by "Michal" to perform the lookup.
Cheers,
Siva Maranani.
Similar Messages
-
RFC Lookup using Java Mapping program - Examples
Dear Experts,
I am working on a scenario which is using 1:N mapping. For deciding the target message I have to use RFC Lookup to call the backend ERP system and there are 2 ERP systems involved in this integration. As I am using Java Mapping and never did a RFC Lookup in Java. I kindly request you to give me some examples which I could use for my RFC calls in my Java Mapping. Simple example will do.
Client is adamant to use Java mapping, I could achieve this easily using XSLT or Graphical Mapping.
Advance Thanks,
PradeepHello,
why don't you use Extended Receiver Determination Defining Extended (Dynamic) Receiver Determination - Integration Directory - SAP Library?
What you can do is create a Message Mapping between your source message and Receivers message type. In this message mapping you can use your RFC to generate the target message.
For example, lets say we have the function ZFM_GET_INTERFACE_INFO used to generate the List of Receivers given a source message. You could create a Message Mapping as below:
In this case, the RFCLookup box look as below:
The receiver determination configuration would look as follows:
Afterwards, you will need two specific message mappings for the two ERP systems.
Summarizing, you'll need:
1.- A Message Mapping: Source Message to Receivers Message Type (This one uses the RFC Lookup)
2.- A Message Mapping: Source Message to Target Message for ERP 1
3.- A Message Mapping: Source Message to Target Message for ERP 2
In Integration Directory you'll have 1 Receiver Determination(Source system, Target System determined Dynamically) and 2 Interface Determinations (Source System to ERP1, Source System to ERP2), etc.
I hope you find it useful.
Regards! -
RFC Lookup using Java Mapping issues
Dear Experts,
I am trying to use RFC Lookup in my Java program but for some reason I am getting a null point exception on the result variable when the program is executing the following code(rfcin = result.getContent();). Could anyone give me some advise on this issue please? screen print of the code attached with this email.
Advance Thanks,
PradeepThanks Steve,
Please find the dump after the proposed change.
java.lang.RuntimeException:
com.sap.aii.mapping.lookup.LookupException: Plain
exception:Error when calling an adapter by using the
communication channel ccRFCReceiverNPI (Party: , Service:
BS_ECD, Object ID: 00b61d6e4363334d8bd052dfb9c2c09a) The
channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
com.sap.aii.mapping.lookup.LookupException:
Error when calling an adapter by using the communication
channel ccRFCReceiverNPI (Party: , Service: BS_ECD, Object ID:
00b61d6e4363334d8bd052dfb9c2c09a) The channel with object ID
00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:130)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.<init>(SystemAccessorInternal.java:46)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.getConnection(SystemAccessorHmiServer.java:265)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:69)
at
com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:139)
at
com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:224)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:370)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:271)
at
com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:570)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:711)
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:276)
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)
Caused
by:
com.sap.aii.ibrun.server.cache.channel.ChannelReader$CachedChannelNotFoundException:
The channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a
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 Cache.
at
com.sap.aii.ibrun.server.cache.channel.ChannelPersistor.read(ChannelPersistor.java:56)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:109)
53 more
at
ConsignmentTrackingMapping.execute(ConsignmentTrackingMapping.java:272)
at
ConsignmentTrackingMapping.transform(ConsignmentTrackingMapping.java:46)
at
com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:92)
at
com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60)
at
com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87)
at
com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:54)
at
com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:139)
at
com.sap.aii.ibrep.server.mapping.exec.ExecuteIfMapCommand.execute(ExecuteIfMapCommand.java:33)
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.GeneratedMethodAccessor640.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:597)
at
com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
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:47)
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:37)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
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:25)
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:17)
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:138)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at
$Proxy1181.execute(Unknown Source)
at
sun.reflect.GeneratedMethodAccessor639.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:597)
at
com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:240)
at
com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:459)
at
com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at
com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at
com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at
com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:983)
at
com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at
com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
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)
Caused
by: com.sap.aii.mapping.lookup.LookupException: Plain
exception:Error when calling an adapter by using the
communication channel ccRFCReceiverNPI (Party: , Service:
BS_ECD, Object ID: 00b61d6e4363334d8bd052dfb9c2c09a) The
channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
com.sap.aii.mapping.lookup.LookupException:
Error when calling an adapter by using the communication
channel ccRFCReceiverNPI (Party: , Service: BS_ECD, Object ID:
00b61d6e4363334d8bd052dfb9c2c09a) The channel with object ID
00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:130)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.<init>(SystemAccessorInternal.java:46)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.getConnection(SystemAccessorHmiServer.java:265)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:69)
at
com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:139)
at
com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:224)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:370)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:271)
at
com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:570)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:711)
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:276)
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)
Caused
by:
com.sap.aii.ibrun.server.cache.channel.ChannelReader$CachedChannelNotFoundException:
The channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a
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 Cache.
at
com.sap.aii.ibrun.server.cache.channel.ChannelPersistor.read(ChannelPersistor.java:56)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:109)
53 more
at
com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:102)
at
com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:88)
at
com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClient.getSystemAccessor(LookupServiceProvider.java:75)
at
com.sap.aii.mapping.lookup.LookupService.getSystemAccessor(LookupService.java:138)
at
ConsignmentTrackingMapping.execute(ConsignmentTrackingMapping.java:254)
48 more
Caused by:
com.sap.aii.utilxi.hmi.api.HmiMethodFault: Plain
exception:Error when calling an adapter by using the
communication channel ccRFCReceiverNPI (Party: , Service:
BS_ECD, Object ID: 00b61d6e4363334d8bd052dfb9c2c09a) The
channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
com.sap.aii.mapping.lookup.LookupException:
Error when calling an adapter by using the communication
channel ccRFCReceiverNPI (Party: , Service: BS_ECD, Object ID:
00b61d6e4363334d8bd052dfb9c2c09a) The channel with object ID
00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:130)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.<init>(SystemAccessorInternal.java:46)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.getConnection(SystemAccessorHmiServer.java:265)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:69)
at
com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:139)
at
com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:224)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:370)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:271)
at
com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:570)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:711)
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:276)
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)
Caused
by:
com.sap.aii.ibrun.server.cache.channel.ChannelReader$CachedChannelNotFoundException:
The channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a
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 Cache.
at
com.sap.aii.ibrun.server.cache.channel.ChannelPersistor.read(ChannelPersistor.java:56)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:109)
53 more
at
com.sap.aii.utilxi.hmi.api.HmiMethodFault.parseGdi(HmiMethodFault.java:156)
at
com.sap.aii.utilxi.hmi.core.msg.HmiResponse.setState(HmiResponse.java:190)
at
com.sap.aii.utilxi.hmi.core.msg.HmiResponse.parseGdi(HmiResponse.java:141)
at
com.sap.aii.utilxi.hmi.api.HmiHttpJDKClient.sendRequestAndReceiveResponse(HmiHttpJDKClient.java:257)
at
com.sap.aii.utilxi.hmi.api.HmiClientAdapter.invokeMethod(HmiClientAdapter.java:92)
at
com.sap.aii.ibrep.server.lookup.SystemAccessorHmiClient.<init>(SystemAccessorHmiClient.java:52)
at
com.sap.aii.ibrep.server.lookup.SystemAccessorHmiClient.getInstance(SystemAccessorHmiClient.java:73)
at
com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:98)
52 more
Root Cause:
com.sap.aii.mapping.lookup.LookupException:
Plain exception:Error when calling an adapter by using the
communication channel ccRFCReceiverNPI (Party: , Service:
BS_ECD, Object ID: 00b61d6e4363334d8bd052dfb9c2c09a) The
channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
com.sap.aii.mapping.lookup.LookupException:
Error when calling an adapter by using the communication
channel ccRFCReceiverNPI (Party: , Service: BS_ECD, Object ID:
00b61d6e4363334d8bd052dfb9c2c09a) The channel with object ID
00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:130)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.<init>(SystemAccessorInternal.java:46)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.getConnection(SystemAccessorHmiServer.java:265)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:69)
at
com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:139)
at
com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:224)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:370)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:271)
at
com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:570)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:711)
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:276)
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)
Caused
by:
com.sap.aii.ibrun.server.cache.channel.ChannelReader$CachedChannelNotFoundException:
The channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a
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 Cache.
at
com.sap.aii.ibrun.server.cache.channel.ChannelPersistor.read(ChannelPersistor.java:56)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:109)
53 more
at
com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:102)
at
com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:88)
at
com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClient.getSystemAccessor(LookupServiceProvider.java:75)
at
com.sap.aii.mapping.lookup.LookupService.getSystemAccessor(LookupService.java:138)
at
ConsignmentTrackingMapping.execute(ConsignmentTrackingMapping.java:254)
at
ConsignmentTrackingMapping.transform(ConsignmentTrackingMapping.java:46)
at
com.sap.aii.ib.server.mapping.execution.JavaMapping.executeStep(JavaMapping.java:92)
at
com.sap.aii.ib.server.mapping.execution.Mapping.execute(Mapping.java:60)
at
com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:87)
at
com.sap.aii.ib.server.mapping.execution.MappingHandler.map(MappingHandler.java:54)
at
com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:139)
at
com.sap.aii.ibrep.server.mapping.exec.ExecuteIfMapCommand.execute(ExecuteIfMapCommand.java:33)
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.GeneratedMethodAccessor640.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:597)
at
com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
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:47)
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:37)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at
com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
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:25)
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:17)
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:138)
at
com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at
$Proxy1181.execute(Unknown Source)
at
sun.reflect.GeneratedMethodAccessor639.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:597)
at
com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:240)
at
com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:459)
at
com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at
com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at
com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at
com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:983)
at
com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at
com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
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)
Caused
by: com.sap.aii.utilxi.hmi.api.HmiMethodFault: Plain
exception:Error when calling an adapter by using the
communication channel ccRFCReceiverNPI (Party: , Service:
BS_ECD, Object ID: 00b61d6e4363334d8bd052dfb9c2c09a) The
channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
com.sap.aii.mapping.lookup.LookupException:
Error when calling an adapter by using the communication
channel ccRFCReceiverNPI (Party: , Service: BS_ECD, Object ID:
00b61d6e4363334d8bd052dfb9c2c09a) The channel with object ID
00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:130)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.<init>(SystemAccessorInternal.java:46)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.getConnection(SystemAccessorHmiServer.java:265)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:69)
at
com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:139)
at
com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:224)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:370)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:271)
at
com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:570)
at
com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:711)
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:276)
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)
Caused
by:
com.sap.aii.ibrun.server.cache.channel.ChannelReader$CachedChannelNotFoundException:
The channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a
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 Cache.
at
com.sap.aii.ibrun.server.cache.channel.ChannelPersistor.read(ChannelPersistor.java:56)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:109)
53 more
at
com.sap.aii.utilxi.hmi.api.HmiMethodFault.parseGdi(HmiMethodFault.java:156)
at
com.sap.aii.utilxi.hmi.core.msg.HmiResponse.setState(HmiResponse.java:190)
at
com.sap.aii.utilxi.hmi.core.msg.HmiResponse.parseGdi(HmiResponse.java:141)
at
com.sap.aii.utilxi.hmi.api.HmiHttpJDKClient.sendRequestAndReceiveResponse(HmiHttpJDKClient.java:257)
at
com.sap.aii.utilxi.hmi.api.HmiClientAdapter.invokeMethod(HmiClientAdapter.java:92)
at
com.sap.aii.ibrep.server.lookup.SystemAccessorHmiClient.<init>(SystemAccessorHmiClient.java:52)
at
com.sap.aii.ibrep.server.lookup.SystemAccessorHmiClient.getInstance(SystemAccessorHmiClient.java:73)
at
com.sap.aii.ibrep.server.lookup.LookupServiceProvider$RemoteClientDelegator.<init>(LookupServiceProvider.java:98)
52 more
Root Cause:
com.sap.aii.utilxi.hmi.api.HmiMethodFault:
Plain exception:Error when calling an adapter by using the
communication channel ccRFCReceiverNPI (Party: , Service:
BS_ECD, Object ID: 00b61d6e4363334d8bd052dfb9c2c09a) The
channel with object ID 00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
com.sap.aii.mapping.lookup.LookupException:
Error when calling an adapter by using the communication
channel ccRFCReceiverNPI (Party: , Service: BS_ECD, Object ID:
00b61d6e4363334d8bd052dfb9c2c09a) The channel with object ID
00b61d6e4363334d8bd052dfb9c2c09a 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 Cache.
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:130)
at
com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.<init>(SystemAccessorInternal.java:46) -
RFC Lookup using RFC_READ_TABLE
Hi,
I'm doing RFC lookup using RFC_READ_TABLE to read data from table "LIPS". I am getting the following error with the XML signature
DVEBMGS01/j2ee/cluster/server0/./temp/classpath_resolver/Mapb16b89b090ec11debb52001e0b450820/source/com/sap/xi/tf/_MM_GetCompanyDetails_.java:72: ';' expected String rfcXML = "<?xml version="1.0" encoding="UTF-8"?><ns0:RFC_READ_TABLE xmlns:ns0="urn:sap-com:document:sap:rfc:functions"><QUERY_TABLE>"+ DBTABLE + "</QUERY_TABLE><DATA></DATA><FIELDS><item><FIELDNAME>"+ FIELDS "</FIELDNAME></item></FIELDS><OPTIONS><item><TEXT>" WHERE_CLAUSE +"</TEXT></item></OPTIONS></ns0:RFC_READ_TABLE>" ; ^ 1 error.
Please let me know how this works
Regards,
RaviHi Ravi,
This seems to me like a syntax error. Fix that and it should work fine.
Regards,
Neetesh -
Error while creating RFC Jco provider in visual Admin
Hi,
I have crated a rfc jco provider in visual admin , I have given all the ECC related details both in registered server AND Spcific application server. In both of these I have given R/3 related details like host of ecc and all.
All i have given correct used ID and passowrd also (I am using my own user id and password in this jco rfc provider). that user id is there in ecc with sap all in profile and in roles also i have given 2 roles for that used id, namely sap_bc_jsf_communication AND sap_bc_usr_cua_client_rfc
Still when i try to start it its giving me error: Error starting bundle
please helpThis I am getting:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=sapecdsrv SYSNR=00 GWHOST=sapecdsrv GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR hostname 'sapecdsrv' unknown
TIME Wed May 26 14:26:21 2010
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -2
MODULE nixxhsl.cpp
LINE 223
DETAIL NiHsLGetNodeAddr: hostname cached as unknown
COUNTER 2
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1025)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3255)
at com.sap.mw.jco.JCO$Pool.initPool(JCO.java:4725)
at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6180)
at com.sap.mw.jco.JCO$PoolManager.getClient(JCO.java:6135)
at com.sap.mw.jco.JCO.getClient(JCO.java:8803)
at com.sap.engine.services.rfcengine.Bundle.startAll(Bundle.java:248)
at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(RFCRuntimeInterfaceImpl.java:350)
at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.changeBundleConfiguration(RFCRuntimeInterfaceImpl.java:654)
at sun.reflect.GeneratedMethodAccessor401.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172 -
R/3 to PI using RFC Sender Adaptor as Asynchronous scenario
Hello Folks,
RFC Adp. SOAP Adp.
ECC-->XI--
>ARIBA
I am new to PI and doing a scenario mention above. we are using RFC sender adaptor to send the data to XI in asynchronous process.
I have config the Sender comm. channel as below.
Appl. Server(Gateway): My Ecc Server host name
Appl. Server Service (Gateway) : My Ecc server
Program Id : XYZ.
Note : while creating the the Service interface and Message mapping and Operation mapping I am using the RFCname.respone message type is that ok in asynchronous process?
And then I went to ECC in Tcode SM59 and created a RFC destination of type TCP/IP
and put the same information as given above and test the connection which is working fine.
I have created a FM at ECC end make it remote enabled. and calling the FM in back ground task using destination in a Work flow code.
When I run the Work flow code It ran successfully but i went to XI side there is no msg in the SXMB_MONI.
Then i went to the component monitoring->Adatptor engine>Comm. channnel Monitoring and found that under my RFC sender comm. channel there is an error msg saying
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'BS_ECC', toParty '', toService '', interface 'YFPS_MM_I_0242_PO_APPROVAL_OUT', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_0242_PO_Approval_RFC_Sender' (channelId 19585252a58335ee871e4c3a771b027f)
Where as i have checked that in the sxi_cache t-code there is a sender agreement for my scenario under the sender agreement tab.
Please Help me in this to resolve the above error. I am totally stuck at this point.I would really appreciate a quick answer.Appl. Server Service (Gateway) : My Ecc server
Confused with this statement.....
it should have the format sapgwXX ....
XX is the system number which comes from the j2ee port mentioned in the XI homepage URL
http://<hostName>:5XX00:rep/start/index.jsp
How to configure sender RFC adapter...check this blog:
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1438
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:
senderAgreement not found:
Sender Agreement is Expected in this communication which does not seem to be present in ID....create sender agreement using the RFC communication channel....
Regards,
Abhishek.
Edited by: abhishek salvi on May 2, 2009 1:24 AM -
Hi,
I'm a little bit confused by the help on NW 7.10 SP7. I normally use RFC connections from web Dynpro but this time I have to use RFC from an EJB. As before I tried "SAP Enterprise Connector" which seems to be depricated.
I followed the example how to use Destination Service. It imports "cam.sap.mw.jco.JCO". After correcting one error in the given source (could never run that way), I get the JCO marked as deprecated as well. So this source code there seems to be a left over from NW 2004?
Is the destination service itself also depricated?
So I found out JCO is now depricated and I should use SAP Java Resource Adapter instead. Can I combine it with destination service or is there something similar as in web dynpro? For Ehp 1 I found this adaptive RFC package, but seems not to be available in 7.10?
What I clearly want to avoid is to give any user, password or system parameters in the source code as I'm used from Web Dynpro. Can I use the web dynpro mechanism maybe somehow?
Maybe someone can bring some light in all this
Thx,
FrankHi Frank
>After correcting one error in the given source (could never run that way), I get the JCO marked as deprecated as well. So this source code there seems to be a left over from NW 2004?
Not exactly. The deprecation means that the JCo API version is 2.X while JCo 3.0 is already available. However, this does not mean that you cannot use the "com.sap.mw.jco.JCO". I know lots of projects running even on 7.11 and 7.20 that still use the JCo 2.X.
>Is the destination service itself also depricated?
No, no, no.
>So I found out JCO is now depricated and I should use SAP Java Resource Adapter instead. Can I combine it with destination service or is there something similar as in web dynpro? For Ehp 1 I found this adaptive RFC package, but seems not to be available in 7.10?
Java Resource Adapter is just a new JEE container for JCo API. Still it's also has some problems. So I'd not recommend you to use it.
>What I clearly want to avoid is to give any user, password or system parameters in the source code as I'm used from Web Dynpro. Can I use the web dynpro mechanism maybe somehow?
Use JCo 2.X + Destination Service. Ignore the API deprecation.
BR, Siarhei -
Call remote function on a satellite system using RFC target sys option
Hi all,
I am on the Java stack and I would like to call the ABAP stack of a statellite system. I can create a JCo connection on this system directly but for security reason I am not allowed to do that. I would like to call this system through the ABAP stack of my machine (I am in dual stack environment).
- How can I use RFC target sys (available in SE37 for Remote-Enabled functions) with my JCo connection?
- Or, is there a generic function which can call all other functions on a remote system (still using RFC target sys)?
Many thanks,
StephanSiddhesh - thank you for the link; the blogs by Thomas are required reading as far as I am concerned.
Hi Raja;
<i> do you mean another ABAP system (was6.40)?
and from here using another FM you call the 4.6c
system RFC ?</i>
Yes, that is what we are doing. We are calling a web service from an Intranet form to the 6.40 system that, in turn will call the 4.6C system and pass the data back to the Intranet form (through 6.40)
<i> may be you could pass the RFC destination as import
parameter to the 6.40 RFC and use the same will the
call to 4.6C RFC from the 6.40 RFC</i>
That would work, but it would be more beneficial to just use the function module on the 6.40 system as a proxy to the function on 4.6c and not have to enter code in it each time.
I had thought of writing just one function module in the 6.40 system that could dynamically call any different function module in 4.6c (based on the input parameters), but since were are trying to accomplish SOA, we need visiblity to each web service (ergo function module).
If it's not possible, that is OK I am just hoping someone had found a way to pull this off.
Thanks!
John -
GSS4480 and CSS using RFC 1918 addressing
We are in the process of testing out a load balancing/redundancy setup using the GSS4480 and a CSS11506. Right now the CSS is setup with RFC 1918 addressing and we NAT out to the internet using a Checkpoint firewall. If I setup my VIP answer file to poll the 1918 address of the CSS, then that will be the answer that is given out when a client requests a name lookup which won't work. There has to be a way to configure this or then all diagrams I have seen are using internet routable name spaces. Looking at the docs and playing with the GUI I don't see any way of configuring it to use RFC 1918 addressing behind the firewall and still give out internet routable domain names. The docs show's the GSS and CSS being behind firewalls. I guess I am just missing something. Can the CSS be configured to link the RFC1918 address to a public address for KAP-AP purposes? Also is there any issues with NATing to RFC 1918 addresses for the health probes to other GSS's. We would like the health probes to go out over the internet not over our back end. Thanks
our issue really isn't the DNS request as more it is the APP session between the GSS and CSS. We have 2 GSS devices that will be located at different data centers. Going by how the GSS docs say they work, the primary GSS synchronizes its database to the secondary when it comes online. With this the case we can't give our GSS(s) 1918 addresses since they'll be in different locations the secondary won't be able to reach the 1918 address of the primary. We have not proven this, but going on what the documentation says this is how it works. Now if we can configure our GSS(s) with 1918 addresses and just NAT their connection as they go out the FW and that's how they learn of each other then that issue becomes moot.
Going with our current problem here's the rest. Since the GSS(s) are outside the firewall they are polling CSS(s) that are located behind the firewall. All NAT is done on the FW so the CSS is completely 1918 addressed. The GSS is polling the circuit IP of the CSS which is a real address that the FW NATs to the 1918 address. The problem arises when the GSS queries the CSS the request is received, however it's for a real address and not a 1918 address.
We thought about duplicating all the content rules with the real addresses as the VIP; this works, but since the users aren't going through those rules the GSS is never going to get anything more than 2 on the load. -
Unable to send table to function module using RFC
Hi all,
I'm trying to send a table from XI to a function module using RFC. I tested the process first using indivdual parameters. At this point there were no problems. Now I changed the import parameter of
the FM into a table and imported the changes into XI. I changed the Message mapping and tested it with multiple records. When I run the process XI calls the FM but the FM doesn't receive any data. I tested this by puting a break-point in the FM. There are no errors in the XML Messages Monitor. I found this message in the Communication Channel Monitoring:
Short Log:
Server 0 10_39293 Receiver channel 'CC_BackendIn' for party '', service 'BS_Backend' (internal name 'RfcClient[CC_BackendIn]')
Client data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=610, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=Admin, jco.client.sysnr=10, jco.client.ashost=192.168.51.8}
Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=610, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=Admin, jco.client.sysnr=10, jco.client.ashost=192.168.51.8}
Current pool size: 0, maximum pool size : 1
Channel History
- OK: 2009-02-18 01:35:14 CET: Message processed for interface MIIA_BapiIn
Any ideas?
Thanks for your help!
Regards,
Ivo van EeHi everyone,
thanks for your prompt response! I tested the mapping in XI and didn't find any error here. So I concentrated on the receiver side. There were some communication channels running on the server that were generating errors. I stopped alle the communication channels and started just the two communication channels for this process. This time the table was successfully exported to the function module! Problem solved. Still not sure what caused the problem in the first place, but everything is working fine now.
Thanks for your help.
Regards,
Ivo -
Creation of Production order in Past dates using RFC
Hi all,
I am using RFC to Create a production order based on the datas available from MES systems.Here the process flow is From MES system datas are passed to interface in file format then from interface will calll the RFC so that the RFC will do the function of Creating the Production order & release in SAP.
Here i face an issue that i have 3 shifts at the end of every shift i have to tranfer the datas from MES to SAP .Which means i have to create 3 Production orders for a day.My issue here is the third shift datas will be availble for me in the next day morning after that only i am able to transfer theses datas to SAP.In this case i want the SAP to create th Production order for third shift in the Previous day time.
Ashift - 7AM t0 3PM
BShift-3PM to 11PM
CShift-11 PM to Next day morning 7 AM
I need SAP to create Production order for Shift C on 11 PM of the Previous day when i transfer it on next day morning 7AM.
Is this possible.
Thanks in Advance,
MBNHi,
I mean the Production Created date as the basic date only.
My requirement is for the C shift i will get the output from the MES on the next day morning.After that i wwill transfer the production datas to SAP throgh Interface at that time i need the basic start date & time of the production order to be the C shift starting time that is previous day night 11.00 PM.
Eg.
C shift date 12.04.2010 night 11PM to 7AM
i transfer the c shift production datas from MES to SAP on 13/04/2010 Morning 7AM.But i want these datas to create basic start date & time of the production order on 12/04/2010 11PM.
What should be done to get these.
Thanks in advance,
MBN -
Data is not getting updated in table using RFC
Hi Experts,
In my scenario, I am calling one RFC using RFC receiver channel. After running scenario, channel is showing status that RFC executed successfully. But when I am checking tables in R/3 system, data is not getting updated.
Moreover , when we tried to execute the RFC manually in R/3 system, that time data uploaded into table successfully.
Could anybody tell me what would the reason that data not uploading into table when we send it through XI.
Regards,
SariHI Sari,
as you have scenario with RFC receiver.. and as you mentioned that it not updating tables when run through PI but when you execute RFC manually tables got updates.. then following are the options you can check..
-- if you check RFC communication channel and if everything ok on then.. this means that your RFC is getting triggered successfully..but as you said tables are not updated.. for this you can go to SXMB_MONI and check the log take payload after mapping.. and compare it with the input when you try to execute it manually.. I think the input when you try manually and input to RFC when you try through PI is different and that is causing the Problem.. you will be able to see the difference in input then check.. I think the problem is data and not RFC communication channel..so by using this you will come to know difference
-- else if possible configure your ID in PI in RFC Receiver and then check and put breakpoint on ABAP side.. so that when PI will hit RFC you will get it in debug mode and able to see what is going wrong..
Thanks,
Bhupesh -
How to use a JCO connection pool in an EJB?
Hi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
LarsHi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
Lars -
Automation of service ticket creation using RFC
Hello Friends,
Here is our new requirement.
In general, in HR team , a manager / employee will perform an action that triggers a workflow in ECC. Then they will call an agent in CRM to raise a service ticket for that. Our requirement is to automate this generation of service ticket when the manager/employee performs an action. But sometimes CRM system will be down. so at that time we need to save the data and create the service ticket when the system becomes active.
Approach:
The workflow will have a method(custom enhancement) that updates a custom table in ECC.
We(CRM) have to develop a RFC function module to read the data from ECC and update it in the custom table of CRM.
we have to create a program to loop the data from custom table and create a service order/ticket by using a function module.
As of now the process looked good.
1. But we don't see any link between the record in the custom table and service ticket generated. we cannot compare the service ticket and from which record it generated?
2. After using RFC we read the data into CRM custom table. How do we compare both the tables and delete the ECC table as soon as the CRM tables is updated?
3. when the service ticket failed to generate we should update the field in the custom table (CRM), the number of failures
Please help me .....Suggest me if there are any other approaches?For question 1 look at the attachments in oss note 940882 Frequently Asked Questions about ERMS
a mailform can be used but is not required.
For question #2, John Burton wrote an article in CRM expert a few years back that explains this concept well. The email coming into the agent inbox doesn't create the ticket until processed but his article explains how it can and give and auto repsonse to the sender with the ticket number attached. -
Sales order creation using rfc
hi
can any one tell me how to create sales order using RFC .
what is the function module we have to use .
Moderator message: please do some research before asking.
Edited by: Thomas Zloch on Mar 17, 2011 1:21 PMMist first line was :-)
The customer numbers must be in table parameter SALES_PARTNERS.
Try [SALES_PARTNERS-PARTN_ROLE|http://www.sdn.sap.com/irj/scn/advancedsearch?query=sales_partners+partn_role] = 'WE', 'SP' etc.
Regards,
Raymond
Maybe you are looking for
-
Imac g5 (no iSight) - powers off randomly, please help!
greetings! my imac g5 (approx 2.5 yrs old) has recently started to power off all of a sudden while i'm working on it. after it powers off, i am not able to turn it back on until after approximately 10-15 minutes. i'm thinking about taking it to the a
-
Problem in displaying update page when multiple results table regions.....
Hi, In Search page, I have 4 Search result table regions.(1.PropertyResultsTable,2.HouseDetailResultsTable,3.WaterDetailsResultsTable,4.ElectricityResultsTable) In PropertyResultsTable Search result table region when I click the update Icon its showi
-
How do I change the titles of a couple of pages, eg "Biography" to "About" and how do I delete some pages?
-
Re: Forte 3.0 Runtime Installation to large userbase
Hi ka. You can install forte on every client with your NetWizard program, and finally, you can create a small VB application to write in registry the Forte configuration Information, you can also use an Install Shield Wizard Setup program, to install
-
After taking full database backup I issued RMAN> report unrecoverable; Report of files that need backup due to unrecoverable operations File Type of Backup Required Name 5 full or incremental /u06/oradata/WRHS/data01.dbf 7 full or incremental /u06/or