- SAP Community
- Products and Technology
- Additional Q&A
- Adaptive RFC for non-HR Connection not working
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Adaptive RFC for non-HR Connection not working
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 07-09-2009 10:04 PM
GCD is my GRC system that is having ABAP + JAVA. I am trying to configure Adaptive RFC in GCD-RAR for GCD-ABAP system.
I get error when I try to use debugger to test the connection for non-hR system that I have configured.
http://<hostname>:<port>/webdynpro/dispatcher/sap.com/grc~ccappcomp/CCDebugger
I get the following error message in GCD system when I try the above link..
VIRSAXSR3_01: Cannot execute BAPI UserList
ErrorCannot extract data from system (GCD); for more details, refer to ccappcomp.n.log
and when I try to check the log, it gives me a message as below.
Jul 9, 2009 12:33:25 PM com.virsa.cc.comp.VirsaXSR3_01Interface execute
WARNING: VIRSAXSR3_01: Cannot execute BAPI UserList
java.lang.NullPointerException
at com.virsa.cc.common.ModelNodeUtil.copyNodeTreeToModel(ModelNodeUtil.java:42)
at com.virsa.cc.comp.VirsaXSR3_01Interface.execute(VirsaXSR3_01Interface.java:267)
at com.virsa.cc.comp.wdp.InternalVirsaXSR3_01Interface.execute(InternalVirsaXSR3_01Interface.java:1341)
at com.virsa.cc.comp.wdp.InternalVirsaXSR3_01Interface$External.execute(InternalVirsaXSR3_01Interface.java:1376)
at com.virsa.cc.comp.BackendAccessInterface.executeBAPIModel(BackendAccessInterface.java:3392)
at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:407)
at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
at com.virsa.cc.comp.BackendAccessInterface.searchUser(BackendAccessInterface.java:756)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.searchUser(InternalBackendAccessInterface.java:4279)
at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.searchUser(InternalBackendAccessInterface.java:4744)
at com.virsa.cc.dataextractor.bo.DataExtractorSAP.searchUser(DataExtractorSAP.java:548)
at com.virsa.cc.comp.BgJobInvokerView.onActionsearchObj(BgJobInvokerView.java:603)
at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdInvokeEventHandler(InternalBgJobInvokerView.java:356)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
FYI, I have already configured and tested the WebDynpro's "VIRSAXSR3_01_METADATA" & "VIRSAXSR3_01_MODEL"
The following are the components on GCD Abap system...
SAP_ABA 700 0019 SAPKA70019 Cross-Application Component Appl. Interface SP
SAP_BASIS 700 0019 SAPKB70019 SAP Basis Component Basis Support Pkg.
PI_BASIS 2005_1_700 0019 SAPKIPYJ7J PI_BASIS 2005_1_700 Component Supp. Pkg.
SAP_BW 700 0021 SAPKW70021 SAP NetWeaver BI 7.0 Component Supp. Pkg.
VIRSANH 530_700 0008 SAPK-53308INVIRSANH SAP GRC Access Controls 5.3 for 700 HR a Component Supp. Pkg.
Regards,
Giridhara
Accepted Solutions (0)
Answers (3)
Answers (3)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
The problem would be resolved after you apply the note 1060673, restart java engine and activate the SAP Adapter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
The error which you are facing is generally caused when the RTA is not installed on SAP system.
As you have already installed the RTA as per your reply, can you please check if necessary authorization is there with the user which you have given while configuring the JCO.
Please try giving SAP_ALL and SAP_NEW to this user and make sure that this user is a service user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Giridhara,
I would like to say that there are user with different role.If the role is not assigned the process is disturbed so we need to provide authrization and role to the user.Supporting this fact i have a SAp document which might be help on the error user list error.Have a look on it.
Link[Usererror|http://help.sap.com/saphelp_nwmobile71/helpdata/en/44/76aaf7a08555cee10000000a1553f6/content.htm]
Hoping your query resolves soon.
Have a best day ahead
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- SAP Sustainability for Financial Services - Portfolio and Solutions in Financial Management Blogs by SAP
- Context Based Adaptation not working. in Enterprise Resource Planning Q&A
- SAC BW live connection: Error Illegal State: data area already existing in Technology Q&A
- First Half 2024 Release: What’s New in SAP SuccessFactors HCM in Human Capital Management Blogs by SAP
- AI-powered supply chain solutions: Better decisions, better outcomes in Supply Chain Management Blogs by SAP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.