- SAP Community
- Products and Technology
- Additional Q&A
- CUP 5.3 (SP11) Risk Owner Approval in CUP workflow
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
CUP 5.3 (SP11) Risk Owner Approval in CUP workflow
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 03-17-2011 12:18 PM
Hi,
My apologies if this question was already asked and answered - I have searched the forum and the config guide but did not find any suitable solution.
I want to set up a workflow with 3 stages for the creation of a new user:
- functional owner (approves the request)
- role owner (approves the roles)
- risk owner (has to approve the request whenever 1 or more risks are involved)
I am able to set up my workflow and work with a detour that is taken on when "SOD violations" occur. This works perfectly when I use "Security Lead" as CAD for the "risk owner" stage. However, I want the Risk Owner, as identified in the RAR, to be contacted in case of SOD violations.
How can I do this?
I have configured my CAD Risk Owner as followed:
- CAD Type: Web Service
- Workflow Type: CUP
- URI: http://sapsrv07:50000/AEWFCADApproversServiceWS_5_2/Config1?wsdl&style=document
- Username: RAR_CUP_CONN
But whenever I reach the stage of the Risk Owner, the flow throws the following error: 'error processing your request'
see next post as this screws up my layout
Some additional info:
- I am testing with 2 roles, 1 role with violations, 1 without. The flow creates the user and provisions the role without the violations. The error is given on the role with violations.
- the RAR_CUP_CONN user has admin access to RAR (tried to logon and works)
Thanks for your help
Accepted Solutions (0)
Answers (2)
Answers (2)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi ,
Do you have any solution for this ? or what should be best to set risk approver stage , how should the workflow configured ?
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
No, I'm still looking for the solution. I find it hard to believe that the Risk Owners as identified in the RAR cannot be used in the CUP workflow.
There is a function "fetchApprovers" with field "riskDTOs" in the AEWFCADApproversServiceWS_5_2, but I don't know if this can be used. Currently still investigating.
As far as I know, the only alternative solutions are currently:
a) as risk owners are identified per business process (logistics, procurement, finance, etc), create a CAD based on the business process of the role. However, for risks that are cross-process this results in multiple risk owners having to approve/mitigate.
b) send any SOD violations to a risk team and let them discuss with the appropriate risk owner how the risk should be mitigated. The risk team then takes action in the CUP on behalf of the risk owner. Alternatively, the team could also just forward the risks to the appropriate risk owners; but this is a rather boring, manual job.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
I have a similar requirment as you have for the risk approver stage.
Role Approver -> Risk approver
Upon approval of the role (by respective role owners), the request should be forwarded to all the mitigation approvers.
As we have defined all the mitigation controls for each risk ID, the system should found all the mitigated approvers.
Is this possible? If it is possible, can you please let me know the way to configure it.
Also, you mentioned something about a function "fetchApprovers" with field "riskDTOs" in the AEWFCADApproversServiceWS_5_2. Could you please let me know where can we find this function and how to set this up.
Also, can you please let me know how does the CAD (webservice works), what does it do actually.
Thanks and Regards,
Ashwin
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Log file:
2011-03-17 12:31:08,907 [SAPEngine_Application_Thread[impl:3]_11] ERROR com.virsa.ae.service.sap.CustomApproveDeterminatorWSDAO : fetchApprovers() : : Exception in getting the approvers, error code : -1, error message : Starting.. Number of Custom Fields : 1and the Error is :null
2011-03-17 12:31:08,931 [SAPEngine_Application_Thread[impl:3]_11] ERROR Error in updating the database
com.virsa.ae.dao.DAOException: com.virsa.ae.service.ServiceException: Exception in getting the approvers, error code : -1, error message : Starting.. Number of Custom Fields : 1and the Error is :null
at com.virsa.ae.service.sap.CustomApproveDeterminatorWSDAO.fetchApprovers(CustomApproveDeterminatorWSDAO.java:92)
at com.virsa.ae.workflow.bo.ApproverDeterminatorHelperAdapter.getCustomApproversListFromWebService(ApproverDeterminatorHelperAdapter.java:705)
at com.virsa.ae.workflow.bo.ApproverDeterminatorHelperAdapter.getCustomApproversList(ApproverDeterminatorHelperAdapter.java:744)
at com.virsa.ae.workflow.bo.ApproverDeterminatorHelperAdapter.fetchApprovers(ApproverDeterminatorHelperAdapter.java:504)
at com.virsa.ae.workflow.bo.ApproverDeterminatorHelperAdapter.fetchApprovers(ApproverDeterminatorHelperAdapter.java:290)
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.handleApproversTransactions(WorkFlowBOHelper.java:1345)
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.handleApproversTransactions(WorkFlowBOHelper.java:1226)
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.runWorkflow(WorkFlowBOHelper.java:861)
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.runWorkflowForApprove(WorkFlowBOHelper.java:588)
at com.virsa.ae.workflow.bo.WorkFlowRequestApproveHelper.approveRequest(WorkFlowRequestApproveHelper.java:377)
at com.virsa.ae.workflow.bo.WorkFlowBO.approveRequest(WorkFlowBO.java:355)
at com.virsa.ae.accessrequests.bo.RequestBO.approveRequest(RequestBO.java:6604)
at com.virsa.ae.accessrequests.bo.RequestBO.approveRequest(RequestBO.java:6427)
at com.virsa.ae.accessrequests.actions.RequestViewAction.confirmRequestApproval(RequestViewAction.java:952)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.virsa.ae.service.ServiceException: Exception in getting the approvers, error code : -1, error message : Starting.. Number of Custom Fields : 1and the Error is :null
at com.virsa.ae.service.sap.CustomApproveDeterminatorWSDAO.fetchApprovers(CustomApproveDeterminatorWSDAO.java:84)
... 39 more
2011-03-17 12:31:08,946 [SAPEngine_Application_Thread[impl:3]_11] ERROR Error in updating the database
com.virsa.ae.core.BOException: Error in updating the database
at com.virsa.ae.workflow.bo.WorkFlowRequestApproveHelper.approveRequest(WorkFlowRequestApproveHelper.java:383)
at com.virsa.ae.workflow.bo.WorkFlowBO.approveRequest(WorkFlowBO.java:355)
at com.virsa.ae.accessrequests.bo.RequestBO.approveRequest(RequestBO.java:6604)
at com.virsa.ae.accessrequests.bo.RequestBO.approveRequest(RequestBO.java:6427)
at com.virsa.ae.accessrequests.actions.RequestViewAction.confirmRequestApproval(RequestViewAction.java:952)
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:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.virsa.ae.dao.DAOException: com.virsa.ae.service.ServiceException: Exception in getting the approvers, error code : -1, error message : Starting.. Number of Custom Fields : 1and the Error is :null
at com.virsa.ae.service.sap.CustomApproveDeterminatorWSDAO.fetchApprovers(CustomApproveDeterminatorWSDAO.java:92)
at com.virsa.ae.workflow.bo.ApproverDeterminatorHelperAdapter.getCustomApproversListFromWebService(ApproverDeterminatorHelperAdapter.java:705)
at com.virsa.ae.workflow.bo.ApproverDeterminatorHelperAdapter.getCustomApproversList(ApproverDeterminatorHelperAdapter.java:744)
at com.virsa.ae.workflow.bo.ApproverDeterminatorHelperAdapter.fetchApprovers(ApproverDeterminatorHelperAdapter.java:504)
at com.virsa.ae.workflow.bo.ApproverDeterminatorHelperAdapter.fetchApprovers(ApproverDeterminatorHelperAdapter.java:290)
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.handleApproversTransactions(WorkFlowBOHelper.java:1345)
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.handleApproversTransactions(WorkFlowBOHelper.java:1226)
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.runWorkflow(WorkFlowBOHelper.java:861)
at com.virsa.ae.workflow.bo.WorkFlowBOHelper.runWorkflowForApprove(WorkFlowBOHelper.java:588)
at com.virsa.ae.workflow.bo.WorkFlowRequestApproveHelper.approveRequest(WorkFlowRequestApproveHelper.java:377)
... 30 more
Caused by: com.virsa.ae.service.ServiceException: Exception in getting the approvers, error code : -1, error message : Starting.. Number of Custom Fields : 1and the Error is :null
at com.virsa.ae.service.sap.CustomApproveDeterminatorWSDAO.fetchApprovers(CustomApproveDeterminatorWSDAO.java:84)
... 39 more
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
No, apparently it doesn't show when I type it here, so I replace the server name with <server>
http://<server>:50000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
Edited by: Lanssens Tom on Mar 17, 2011 3:40 PM
- S/4 Flexible PO Workflow -Approval Limit Check in Supply Chain Management Q&A
- SAP S4HANA Cloud Public Edition Logistics FAQ in Enterprise Resource Planning Blogs by SAP
- SAP Build Process Automation Pre-built content for Finance Use cases in Technology Blogs by SAP
- New 1H 2024 SAP Successfactors Time (Tracking) Features in Human Capital Management Blogs by SAP
- Final Review Step in Onboarding 2.0 Process in Human Capital Management Blogs by Members
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.