cancel
Showing results for 
Search instead for 
Did you mean: 

CUP Parameter ID's

Former Member
0 Kudos

Experts,

I'm trying to auto assign Parameter ID's based on the roles requested by the end user.

What I have done is created user defaults with the Parameter ID's and mapped the PIDs to a specific role. The assumption being when the end user requests that role the PID's will be assigned too.

I created and approved a request and the role was auto provisioned, however the PID's did not show up. Any idea on why this would happen? Can PID's be auto provisioned?

Any help would be greatly appreciated.

Thanks,

Kunal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Kunal,

Are any of the user defaults being transfered at all? If not, check that that "USER_DEFAULTS" action is assigned to all applicable Request Types in the Configuration tab. In my case, they were not there by default and I had to manually add them in.

-Dylan

Former Member
0 Kudos

Guys,

I'm still having a problem, the error log shows that I'm not able to find the Parameter: Any thoughts on why this is occuring.

Error log below:

com.virsa.ae.core.BOException: Search could not be completed

at com.virsa.ae.search.bo.SearchSAPParameterBO.searchSAPParameter(SearchSAPParameterBO.java:73)

at com.virsa.ae.configuration.bo.UserDefaultBO.getUserDefaultPIDOptions(UserDefaultBO.java:618)

at com.virsa.ae.configuration.actions.UserDefaultAction.pageLoadWithPO(UserDefaultAction.java:299)

at com.virsa.ae.configuration.actions.UserDefaultAction.pageLoadForView(UserDefaultAction.java:236)

at com.virsa.ae.configuration.actions.UserDefaultAction.execute(UserDefaultAction.java:60)

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

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.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)

Answers (1)

Answers (1)

martin_trachsel
Participant
0 Kudos

Hi Kunal,

If you are going to define the user defaut mapping, you have select conditions. These conditions have to be correct, for provisioning the PIDs in your backend system. If the conditions are not equal, than the user defaut mapping will be ignored.

The other aspect is, that you can just define one backend system, where you can catch your PIDs information.

If the conditions are equal and well-defined, then it should works.

Cheers,

Martin