JCO_ERROR_FIELD_NOT_FOUND

[Former Member]

I am installing GRC 5.3 and am currently testing. I am simulating a "new hire" and am assigning a user ID and roles in three backend systems (ECC, BI, and SRM). Everything is working fine until the auto provisioning takes place. The user ID is created in all three systems. Roles are pushed out to the user in ECC and BI, but the roles do not get pushed to SRM. We are on SRM 5.0. Here is the error log. Please help if you can.

2009-04-01 17:50:03,017 [SAPEngine_Application_Thread[impl:3]_12] ERROR com.sap.mw.jco.JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND: Field RETURN not a member of TABLES

com.sap.mw.jco.JCO$Exception: (127) JCO_ERROR_FIELD_NOT_FOUND: Field RETURN not a member of TABLES

at com.sap.mw.jco.JCO$MetaData.indexOf(JCO.java:9565)

at com.sap.mw.jco.JCO$Record.getTable(JCO.java:14282)

at com.virsa.ae.service.sap.SAPProvisionDAO.executeRoleOperation(SAPProvisionDAO.java:1699)

at com.virsa.ae.service.sap.SAPProvisionDAO.assignRoles(SAPProvisionDAO.java:1458)

at com.virsa.ae.service.sap.ProvisionSAPUserDAO.provisionInNonCUA(ProvisionSAPUserDAO.java:1232)

at com.virsa.ae.service.sap.ProvisionSAPUserDAO.provisionRole(ProvisionSAPUserDAO.java:932)

at com.virsa.ae.service.sap.ProvisionSAPUserDAO.provisionUser(ProvisionSAPUserDAO.java:118)

at com.virsa.ae.accessrequests.bo.ProvisioningBO.autoProvision(ProvisioningBO.java:216)

at com.virsa.ae.accessrequests.bo.RequestBO.autoProvisioningForApprove(RequestBO.java:4572)

at com.virsa.ae.accessrequests.bo.RequestBO.callAEExitService(RequestBO.java:5565)

at com.virsa.ae.accessrequests.bo.RequestBO.callExitService(RequestBO.java:5339)

at com.virsa.ae.accessrequests.bo.RequestBO.approveRequest(RequestBO.java:5191)

at com.virsa.ae.accessrequests.bo.RequestBO.approveRequest(RequestBO.java:4984)

at com.virsa.ae.accessrequests.actions.RequestViewAction.confirmRequestApproval(RequestViewAction.java:941)

at com.virsa.ae.accessrequests.actions.RequestViewAction.execute(RequestViewAction.java:103)

at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)

at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)

at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)

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(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

[Former Member]

After more testing, this is what I found out.

When I simulated a new hire (new user with roles), the following occured:

When user/roles for SRM system only - user and roles provisioned to backend system

When user/roles for BI and SRM - user and roles provisioned to backend systems

When user/roles for ECC and BI - user and roles provisioned to backend systems

When user/roles for ECC, BI, and SRM - user provisioned to all three systems, roles only provisioned to ECC and BI

When user/roles for ECC and SRM - user provisioned to both systems, roles only provisioned to ECC.

It looks like role provisioning does not work with the combination of ECC and SRM.

At first I thought the error I pasted in my previous step was the problem, but I get that error even when everything provisioned ok.

I then thought maybe there was a limitation on the number of roles you could provision, but when the ECC and BI combo worked that ruled it out because there are more roles with that combination than with ECC and SRM.

It really seems to be related to provisioning roles to ECC and SRM in the same request.

I will try this combination again and do a debug on the log and post it later in case that may help.

Thanks,

Peggy