Creating Mitigation Control from CUP

[Former Member]

Hi Guys,

Is this feature implemented in Access Control???? Or Stills as enhancement

[Former Member · Accepted solution]

This has been there for some time. You can surely create mitigation control from CUP.

Alpesh

[Former Member · Accepted solution]

Hi Alpesh

In order to your answer... Can you help me to identify what I doing wrong when I want to approve a mitigate control in CUP.

Path 1 : Approve request

Stage 1: Request

Stage 2: Security

Stage 3: Role Owner

Detour Path:

Type: CUP

Stage: Role Owner

Condition: SoD Review

Detour Path: Path 2

Path 2:

Stage 1: Approval -- > CAD : Mitigation Monitor

The request is send to the Mitigation Monitor but when we try to approve request show the next error:

2010-03-30 14:10:26,390 [SAPEngine_Application_Thread[impl:3]_25] ERROR Mitigation control TEST_5.1 could not be saved for user PRUEBAGRC_6

com.virsa.ae.core.BOException: Exception from the service : Mitigation record doesn't exist

at com.virsa.ae.accessrequests.bo.MitigationControlBO.insertMitigationControl(MitigationControlBO.java:207)

at com.virsa.ae.accessrequests.bo.MitigationControlBO.saveMitigationControls(MitigationControlBO.java:321)

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

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

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

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

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

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

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

Caused by: com.virsa.ae.service.ServiceException: Exception from the service : Mitigation record doesn't exist

at com.virsa.ae.service.sap.MitigationControlWS52DAO.checkForSuccess(MitigationControlWS52DAO.java:832)

at com.virsa.ae.service.sap.MitigationControlWS52DAO.executeUpdateUserMitigation(MitigationControlWS52DAO.java:287)

at com.virsa.ae.service.sap.MitigationControlWS52DAO.insertUserMitigation(MitigationControlWS52DAO.java:309)

at com.virsa.ae.accessrequests.bo.MitigationControlBO.insertMitigationControl(MitigationControlBO.java:195)

Can you help me please?? All URI are OK.

Thanks !!!!

Edited by: Karen_sans on Mar 31, 2010 7:45 PM

[Former Member · Accepted solution]

Sorry I insists... but anybody can help me please ??

Thanks a lot!!!!

Regards

[Former Member · Accepted solution]

Does anyone had the same error??

[Former Member · Accepted solution]

The issue was solved disabling the option in RAR of send email when reducing object is modified. Also, we have to configure the JAVA Mail Cliente in Visual Admin