Mitigation control workflow for AC10

We are configuring the Mitigation control workflow during the implementation of AC 10.
I would like to know whether its mandatory to have the workflow for Mitigation approver and monitor. As per the implementation team there is no requirement for them as this is not covered during the rampup.  But I think this should be mandatory to have the mitigation approval worflow so all the mitigation risk should be approved before mitigating. Otherwise, security admin can mitigate any risk and complete the request.
Please advice.

Hi,
Yes. It will be a manual process. In some of the organizations, risks identification and mitigation will be performed manually by the Business process owners, which means in reality there will not be any risks that pop-up in CUP or RAR since they are already mitigated for the user.
If you don't want to enable the mitigation process in the workflow, you have to do it and record the evidences manually.
Hope this answers.
Regards,
Raghu

Similar Messages

  • Disable mitigation control workflow

    Hi community,
    one pretty simple question: I would like to be disable the mitigation control workflow, meaning, I would like to be able to directly save mitigation controls, without sending this through an approval process. I cannot find the associated activity in the spro. Can you please assist me on this?
    The way I saw this some time ago was that, if one disabled the mitigation control workflow, the Save button was visible in the mitigation control maintenance screen. When the workflow was enabled, the Submit button was visible (which, of course, makes sense). Now, I would like to be able to do this change.
    I did also look into transaction GRFNMW_CONFIGURE_WD - nothing suspicious here.
    Any help is highly appreciated. Thanks in advance!
    EM

    Hi EM,
    Please set 1061 and 1062 to NO as per your requirement for mitigation assignment and mitigation maintenance.
    BR,
    Mangesh

  • Mitigated risks workflow for SoD detour approval

    Hi All,
    Please assist. I have configured a workflow for requests as follows:
    Super user submits request - Workflow to Business Analyst (if there are violations they can assign an existing mitigation control) - Auto Provision
    If no existing control is available - Detour to SoD officer (to compile a new control with Business Analyst) - workflow to GRC administrator to capture new control on the system - Auto provision
    The problem that I have now is with the first part of the workflow wherein there are violations and there is a control in place that can be applied to mitigate the risk. If mitigate the risks associated with the request, the worflow still goes to SoD officer in spite of all risks mitigated.
    Is there a way I can set this to enforce the assigned controls? Checking from RAR, the user is only linked to the control upon closing the request.
    I have set Risk Analysis defaults on CUP to "Consider Mitigation Controls"
    GRC 5.3 SP13
    Any help will be appreciated.
    Thanks,

    Hi Sabrina,
    For Access Request workflow, we generally use GRAC_MSMP_DETOUR_SODVIOL to implement routing rule(based on detour condition - risk found). Purpose of same (if I am not mistaken) is to through the request to another level of approver wherein mitigation monitor agent reviews the mitigation performed by role owner stage and approve/reject the request.
    But, when we create a role same is not the condition as we do not mitigate role level risk thus no need to go for mitigation monitor stage. May be you have some business scenario, if you can let us know will be gr8.
    For the rule ID, did you try adding the rule ID ?(you may already know, still would like to cross check with you).
    GRAC_MSMP_DETOUR_SODVIOL under list of rules for "
    Role Approval Workflow" In the screenshot you have shown, just click on ADD feed -
    Rule ID -GRAC_MSMP_DETOUR_SODVIOL.
    Rule description - same as Access request.
    Rule type - Function module based
    rule kind - routing rule.
    Add this and check if it works and let us know the result too.
    Regards,
    Nishant

  • Issue in Process Controlled workflow for Shopping cart in Quality system.

    Hello All,
    I ahve configured a Process controlled workflow in SRM 7.0  with custom resolver, and I am facing an issue taht the Workflow works well in Development but in Quality the approvers are dropped after SC is ordered in Quality system.
    The SC Workflow drops the approvers picked up from the Interface  method /SAPSRM/IF_EX_WF_RESP_RESOLVERGET_AREA_TO_ITEM_MAP and IF_EX_WF_RESP_RESOLVERGET_APPROVERS_BY_AREA_GUID of BADI /SAPSRM/BD_WF_RESP_RESOLVER. The approvers can be seen in the shopping cart Approval preview Tab until the SC is ordered.
    I have compared the OSS notes relevant for Workflow, all of them have been transported, Also I compared and checked general Workflow settings, BRF Config and  Process level  settings in Dev and Quality, everything is same.
    Also while debugging; the approvers can be seen in the decision set table in the create_process_forecast method of class /SAPSRM/CL_WF_PROCESS_MANAGER.
    Kindly let me know what else i can check to find the root cause.
    Thank you in advance for help!
    Regards
    Prasuna.

    Hello Vinita;
    Thanks for the input and sorry for the not so "ASAP" reply;
    From what I'm seeing in from your 2 screenshot, i strongly believe that the problem is even before the Z implementation /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID (in which the FM i ZSRM_GET_USER_FROM_PGRP is called. I think the problem could be in the process level determination  ZSRM_WF_BRF_0EXP000_SC_APP100. Let me explain:
    In your  cases where not buyer is determined,  in the approval tab there is not even a process level for buyer approval. If the problem were indeed in the implementation  /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID  then the process level would be there, but the system will display, instead of the name of the buyer(if the buyer determination fails) a red label with the message:  "With the strategy "Buyer determination" an approver could not be determined (or something like that..please check the image at the end of the text)".
    I can propose a way to discard this: Implement the method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS of class ZCL_BADI_SC_WC (in case you didn't know, in this method you can specify an "default" approver in case that the determination of approver in GET_APPROVERS_BY_AREA_GUID fails). The idea is to specify an default approval and see how it behaves:
    If the user you indicated in the method GET_FALLBACK_AGENTS appears as approver, then yes, the problem is arises from implementation GET_APPROVERS_BY_AREA_GUID, in which case it could be a data problem (peharps in pposa_bbp?). You could also check in TX SU53 with the users with this problem to see if there's a missing authorization objetc.
    If, in the other hand, the "default" approver is not shown, it means that the process level buyer determination is not even called, so you should check in more detail ZSRM_WF_BRF_0EXP000_SC_APP100 and /SAPSRM/CL_WF_PROCESS_MANAGER > Determine process restart –method ----- (i have never used this method, so i could not tell if  it could be the source of the problem).
    Also, you could implement the method GET_FALLBACK_AGENTS in this way so the default approver would be the WF administrator indicated in the customizing (or you could just append directly any user you want):
    METHOD /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS.
       DATA: lv_admin_expr TYPE swd_shead-admin_expr,
             lv_admin      TYPE swd_shead-wfi_admin,
             lv_admin_type TYPE sy-input,
             ls_agent      TYPE  /sapsrm/s_wf_approver.
       CALL FUNCTION 'SWD_WF_DEFINITION_ADMIN_GET'
         IMPORTING
           default_admin_expr = lv_admin_expr
           default_admin      = lv_admin
           default_admin_type = lv_admin_type.
       ls_agent-approver_id = lv_admin.
       APPEND ls_agent TO rt_agent.
    ENDMETHOD.
    Error of agent determination:
    Please let me know the result of the test with the implementation of method GET_FALLBACK_AGENT. By doing this we could ensure if really the problem is in method GET_APPROVERS_BY_AREA_GUID or before.  I just made the test in our system and I'm almost sure that you wont get the default approver, but i could be wrong. 
    Any question please let me know.
    Best regards
    Cristian R.

  • Request creation error for mitigation control workflow

    Dear Expert,
             I had activiate the workflow from RAR to CUP on Mitigated User assignment, I had completed following customizing:
    1)RAR->configaration->Workflow
    2)CUP->configaration->initiator, stage, path.
    but when I created mitigated user assignments in RAR, after click "Submit", error popup: "Request creation error"
    can some one help?
    thanks!

    Dear,
         the log is below:
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 1:33:16 PM com.virsa.cc.common.SAPAdapter serverExceptionOccurred
    INFO: Exception in Server YYY:
    com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Thu May 20 13:33:16 CST 2010.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 3600 seconds.
    Could not start server: Connect to SAP gateway failed
    Connect parameters: TPNAME=YYY GWHOST=visoil01 GWSERV=SAPGW00
    ERROR       service 'SAPGW00' unknown
    TIME        Thu May 20 13:33:16 2010
    RELEASE     701
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -3
    MODULE      niuxi.c
    LINE        1732
    DETAIL      NiPGetServByName2: service 'SAPGW00' not found
    SYSTEM CALL getservbyname_r
    COUNTER     375
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    INFO: END POOINT URL: http://9.186.143.129:50100/AEWFRequestSubmissionService_5_2/Config1?style=document
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    INFO: before submit:
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    INFO: wftype: MITIOBJ reqid: GRC01
    May 20, 2010 2:10:50 PM com.virsa.cc.rulearchitect.dao.dto.MitObjDTO getObjContext
    FINEST: validfrom: 2010-05-20 validto: 2011-05-20
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: MITREFNO
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MOMITREFNO
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: CT01
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: RISKID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MORISKID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: ZC02
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: LANG
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: LANG
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: EN
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: MONITORID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MONITORID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: GRC01
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: Integer
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: STATUS
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MOSTATUS
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: 0
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: DATE
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: VALIDFROM
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: VALIDFROM
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: 05/20/2010
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: DATE
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: VALIDTO
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: VALIDTO
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: 05/20/2011
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: BU ID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: BUID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: null
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: Approver ID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: MOAPPROVERID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: null
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: OBJTYPE
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: OBJTYPE
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: U
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Data Type: String
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Descripton: OBJID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Name: OBJID
    May 20, 2010 2:10:50 PM com.virsa.cc.xsys.aewf.SubmitAEWorkflow setProcessContext
    INFO: Value: 207471
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    INFO: Return code: 2010 Message: com.virsa.ae.core.ObjectNotFoundException: Invalid Priority Value : MO_HIGH workflow id: null Status: null
    May 20, 2010 2:10:50 PM com.virsa.cc.workflow.bo.WorkflowBO submit
    WARNING: 2010: null

  • Process Controlled WF for Shopping Cart

    Hi,
    We have implemented process controlled workflow for shopping cart approval.
    1. Created a bespoke schema for the approval process
    2. Defined 5 process levels in the schema
    3. changed the BRF event at the schema evaluation level. It now
    contains a constant with the name of new schema create in step 1.
    4. Decision set used is item based approval for partial documents (Type 4)
    4. The first process level is get the technical approval from bespoke
    table based on material group. For that we have first created a
    Responsibility Resolver Name - ZTECHNICAL_APPROVER.
    We have implemented the BADI - /SAPSRM/BD_WF_RESP_RESOLVER. Assigned
    the filter as BUS2121 and ZTECHNICAL_APPROVER.
    5. Now we have placed the external debugger in BADi. when we create
    the shopping cart the flow doesn't stop at the break point. The item
    reaches to the last step of Automatic approval (Rejected).
    6. We think that schema is getting evaluated, however the process
    level is not getting called.
    7. Before we created schema, all the carts wer getting "Approved" by
    automatic step. In our schema the automatic step is "Rejected", hence
    the carts are getting rejected.
    Could you please let me know what could be reason for BADI
    implementation not being called or is there any config step which we
    are missing?

    Hi,
      I think your process level evaluation id is not true, that is the reason system skips the process level.. Can you check your evaluation event-expression code. What do you see in SLG1?  For testing purpose change the evaluation id to 0EV000 and check. Make Sure you debug through the user(requester) that you are creating the SC. Please test and let me know...
    Saravanan

  • Dump on screen when configuring Process controlled workflow

    Hi Experts,
    I am facing 1 problem in SAP SRM 7 ehp1.  I am configuring Process controlled workflow. Previous workflow settings was Application controlled workflow as its been upgraded from SRM 5. If i run a RFX (BUS2200) cycle in application controlled workflow environment, it works flawlessly.
    But when i change my workflow framework to process controlled workflow for all Business Objects. I face a dump when I am creating an RFX. The dump on the portal is:
    http://dl3803.ltisap.com:8040/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif
    DATREF_NOT_ASSIGNED
    No access possible via the 'NULL' data reference
    Method: PARTICIPATING_IN_ACTIVE_WF of program /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
    Method: EDIT_DURING_WORKFLOW of program /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
    Method: /SAPSRM/IF_PDO_META_CONF_BO~GET_BO_HDR_ACTION_METADATA of program /SAPSRM/CL_PDO_META_CONF_PROV=CP
    Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_BO_RFQ====CP
    Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_BO_RFQ_ADVCP
    Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_HANDLER===CP
    Method: UPDATE_ACTIONS of program /SAPSRM/CL_CH_WD_MAP_IDENT====CP
    Method: /SAPSRM/IF_CLL_MAPPER~REFRESH of program /SAPSRM/CL_CH_WD_MAP_IDENT====CP
    Method: /SAPSRM/IF_CLL_MAPPER~REFRESH of program /SAPSRM/CL_CH_WD_IDEN_MAP_RFQ=CP
    Method: OVERRIDE_LEAVE_INIT_SCREEN of program /SAPSRM/CL_FPM_OVRIDE_OIF=====CP
    & when i check in st22. I get the dump as:
    Category               ABAP Programming Error
    Runtime Errors         DATREF_NOT_ASSIGNED
    ABAP Program           /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
    Application Component  SRM-EBP-PD
    Date and Time          17.12.2011 15:46:56
    and get dump at:
      1 method PARTICIPATING_IN_ACTIVE_WF.
      2   " this method returns ABAP_TRUE if the logon user has an active work item,
      3   " i.e. he participates in an active approval workflow process.
      4
      5   DATA lv_curr_workitem_id    TYPE /sapsrm/wf_workitem_id.
      6   DATA lr_process_info        TYPE ref to /SAPSRM/S_PDO_WF_PROCESS_INFO.
      7
      8   " the default:
      9   rv_participates_in_active_wf = abap_false.
    10
    11   " The scenario is not valid for application-controlled workflow:
    12   " Any agents who may edit the document (approver and requester)
    13   " enter "Edit" mode right-away. No special handling possible.
    14   lr_process_info = io_apf_md_context->get_process_info_ref( ).
    >>>   IF lr_process_info->wf_version NE /sapsrm/if_wf_process_c=>GC_APF_VERSION_0200.
    16     return.
    17   endif.
    18
    19   " check if a valid workitem exists
    20   lv_curr_workitem_id = io_apf_md_context->get_workitem_id( ).
    21   IF lv_curr_workitem_id IS INITIAL.
    22     RETURN.
    23   ENDIF.
    the only configuration I change in the system is I changed the workflow framework to process controlled workflow.
    Kindly help.
    Thanks
    Anand

    Hello Anand,
    As per standard SAP recommendations the application-controlled workflow framework is only intended to be used if you are upgrading from SAP SRM 5.0 or earlier and you need to continue using your existing work-flows.
    The default workflow framework setting is the process-controlled workflow from SRM 6.0 on-wards and the user will be provided a option to switch to the application-controlled workflow framework.  The option to switch to process-controlled workflows is available only after you have once switched to application-controlled work flows but there will be a big caution that " If you switch from the application-controlled workflow framework to the process-controlled workflow framework; once a process-controlled workflow has been run, it is not supported that you switch back to application-controlled work-flows".
    As per the details given i got a feel that we have tried executing the scenario by switching between application and process controlled workflow and hence the system have become inconsistent and its dumping.
    I suggest you to raise a OSS ticket to SAP to resolve the issue.
    Best Regards,
    Rahul

  • Approval Level in Process Controlled workflows

    Hi Sap Gurus,
    How can i find the number of approval levels in process controlled workflows for Shopping Cart, Purchase Order....
    Thanks in advance

    Hello,
    IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Business Workflow > Process-Controlled Workflow > Business Process Configuration > Define Process Levels
    For concerned object type, select "Process Schema Definition" directory.
    Then, select correct process level schema to display "Process Level Configuration" directory: here are the process levels defined.
    Regards.
    Laurent.

  • SRM 7.0 Process Controlled Workflow-Level Type in Process level config

    Hello Experts,
    In SRM 7.0 for Process controlled workflow,for Level Type in Process Level configuration we have 3 different options
    1) Approval with Completion
    2) Approval
    3) Automatic(System User)
    Can you plz explain what is the difference between these 3 diffrent potion for Level Type in Process Level configuration.
    Your help will be highly appreciated,
    Thanks & Regards,
    RKS

    1. Approval with completion : This allows approvers to make any changes to document while approving. Generally you define this type for buyer in SC approval.
    2. Approval :  above minus change
    3. Automatic (system approval) : If no process level is determined, you need to set up a process level with automatic approval to approve the document by system.

  • Shopping Cart - Process Controlled Workflow - replace standard task

    Hallo,
    I am on SRM 7.0 SAPKIBKV09 using NWBC.
    I use Process Controlled Workflow for Shopping Cart, and in the process schema definition,
    I replaced the standard workflow task 40007952,
    (with name - SRM Shopping Cart Completion),
    with a copy of task 40007952, task 90000010
    (with name - SRM Shopping Cart BUYER Completion)
    I did that for the following Reason: to ensure that in the Shopping Cart Approval Log, I can distinguish between diffrent approval level, all of type completion.
    Issue is that now when approver is executing the task from NWBC, I get the following error:
    ´No default action found for task TS90000010´
    Any idea?
    tried to apply Note 1409276 - Not all tasks have default action in inbox config, (as this applies to SAPKIBKV06)
    but no success.
    Thank you
    Marco

    Hi,
    I wanted to add that there is standard report /SAPSRM/IBO_FILL_TABLES in SRM 7.0 that updates these tables for all standard tasks:
    IBO_C_WF_ACS
    IBO_C_WF_APS
    IBO_C_WF_CAS
    IBO_C_WF_TAS
    IBO_C_WF_TTAS
    Use these views in SM30 to create entries for customer specific tasks:
    IBO_V_WF_ACC
    IBO_V_WF_APC
    IBO_V_WF_CAC
    IBO_V_WF_IRA
    IBO_V_WF_TAC
    IBO_V_WF_TTAC
    Best Regards,
    Marcus
    Edited by: Marcus Mock on Jun 6, 2011 11:56 AM
    Edited by: Marcus Mock on Jun 6, 2011 11:59 AM

  • Implementing Mitigation Control IDs

    Hi,
    We are planning to implement mitigation control ids in GRC. Currently we are only having 1 mitigation control id and all the users are mitigated into this id.
    Now, the plan is to include the mitigation control advise/comments by the SOD approvers into the GRC and thus by introducing multiple mitigation control id we could achieve this.
    In our system users are mapped as per the Business Unit and we have around 25-30 business units. so each BU is have a seprate mitigation control approval (SOD Approver).
    We have around 150 Risk IDs.
    We are not able to understand how to design mitigation control IDs in such case? Is it a best practice to create mitigation control ID for each Risk ID in the system (May be we can group similar Risk IDs)? Your help is appreciated.
    Thanks,
    Umesh

    Hi Umesh,
    No, for 1 Mitigation COntrol there are serveral Monitors and users who are mitigated are added to only 1 mitigation control id.
    Which means you have multiple people monitoring every risk in your system. Does all of the monitors belong to the same functional group?? If yes, what happens if there is a risk in other functional groups? How they can identify and monitor it??
    If no, why a FI functional group monitor, needs to monitor the risk related to other groups?
    Can you pls explain more on primary and secondary functions?
    If the risk is related to one functional area only, the respective functional area will own it. If it is a cross functional risk, then it will be owned by both the functional area managers, which is often referred as primary and secondary functions.
      and what are the disadvantage of creating 1 mitigation control id for each risk (may be grouping some risks) considering the fact that we have 25 business units.
    It is just like giving 1 coke with 100 straws while you still have a stock in your refrigerator
    Regards,
    Raghu

  • Single Step approval BRF Workflow for RFx.

    Hi,
    I am facing one problem in process controlled workflow for RFx. I have the scenario where I have only one approver but 7-8 reviewer are there in between of approver and initiator for example:
    Initiator >reviewer1>reviewer2->reviewer3->....reviewer8-->approver.
    For acheiving this I have activated standard single step approval workflow.
    But while I am trying to add reviewers to the RFx at the time of creation of RFx the system is not shwing the reviewers. it gets refreshed only reviewers line is added to the reviewers Tab but system did not display any reviewer.
    And while I publish the RFx it directly goes to the approver and while i tried to add the reviewer from approver end the same problem is coming.
    Please help me. How I cam achieve this functionality.
    Thanks & Regards,
    Sachin

    Hello Ashutosh,
    Thanks For your reply. I want to add reviewers at the time of creation of RFx not ad-hoc approvers.
    As I explain in my question that I have only one approver in whole approval process rest all are the reviewers only who only do the review and add comments not the approving authority.
    Thanks,
    Sachin

  • RAR 5.3 SP10 Mitigating Control Import Utility

    All -
    I exported my mitigating controls from a RAR 5.3 SP9 system and imported them into a 5.3 SP10 system. I received a successful confirmation of the import, but when I "searched" my mitigating controls there were duplicated mitigating control numbers. It looks like the import tool duplicated the mitigating control ID for every "monitor" assigned to the mitigating control number. For example, mitigating control MC00000001 with Monitor1, Monitor2, & Monitor3 equated to 3 entries of MC00000001. If I try to delete 2 of the 3 entries, I receive a "Successfully deleted" message and get the error "Exception!!. No relavent language message available in database for :0053". When I "search" again, the mtigating control is no longer there (as expected).
    I confirmed my mitigating control import file does not have the multiple entries.
    Any ideas?
    Thanks,
    Daniel

    Venky,
    Thank you for your response. The message issue actually wasn't the one that I was asking about, but thanks for the heads up. The main issue is that RAR (5.3 SP10) is multiplying mitigating control entries for the number of monitors assigned to the mitigating control. It appears to be an issue with SP10 as it did not occur in SP9. I'm trying to see if anyone knows what the fix is.
    Thanks,
    Daniel

  • Process Control Workflow Configuration error on portal

    Hi Experts,
    We are using process controlled workflow for BUS2121 and activated a BC Set "/SAPSRM/C_SC_600_000_SP04" Shopping cart without approval.
    For this We have created a Event and a Expression in BRF as constant  for Process schema evaluation. No approval is required as of now. But when try to shop from the portal it shows a dump as:
    The following error text was processed in system SRD : Dynamic type conflict when assigning references
    The error occurred on the application server dl3803_SRD_40 and in the work process 2 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: INIT_BRF_TRACE of program /SAPSRM/CL_WF_BRF_MSG=========CP
    Method: CONSTRUCTOR of program /SAPSRM/CL_WF_BRF_MSG=========CP
    Method: INITIALIZE_BRF_MSG of program /SAPSRM/CL_WF_BRF_MSG=========CP
    Method: /SAPSRM/IF_WF_RULE_CONNECTOR~EVALUATE of program /SAPSRM/CL_WF_BRF_CONNECTOR===CP
    Method: /SAPSRM/IF_WF_RULE_CONNECTOR~EVALUATE of program /SAPSRM/CL_WF_SCHEME_PROVIDER=CP
    Method: GET_SCHEME of program /SAPSRM/CL_WF_SCHEME_PROVIDER=CP
    Method: GET_PROCESS_SCHEME of program /SAPSRM/CL_WF_CONFIGURATION===CP
    Method: CREATE_PROCESS_LEVEL_SEQUENCE of program /SAPSRM/CL_WF_CONFIGURATION===CP
    Method: CREATE_PROCESS_INSTANCE of program /SAPSRM/CL_WF_PROCESS_MANAGER=CP
    Method: CREATE_PROCESS_FORECAST of program /SAPSRM/CL_WF_APV_FACADE======CP
    Kindly help to solve this problem.

    Hi Anand,
    I am facing the same problem. Were you able to resolve that issue? if so, what is the solution? I don't find any relevant note for this.
    Probelm: BRF is activated and when you do save/check on SC, throws short dump with error message as
    "Dynamic type conflict when assigning references".
    "MOVE_CAST_ERROR" "CX_SY_MOVE_CAST_ERROR"
    Thanks
    Akbar

  • Risks has been removed but Mitigating Control still stays with the users?

    Hi all,
        I have a situation where after a risk has been removed from the users by removing the violating roles, however the Mitigating Control still remains tagged to the same user. Is there any efficient way of removing Mitigating Controls from users where the risks no longer exists?

    Hi Joseph, thanks for the info. My problem comes in when the user request to have the violating role removed via CUP and it so happens that the Mitigating Control assigned for the old risk still has 6 more months of validity left. It seem like there is no mechanism to auto remove this MC when the role has been removed after the request in CUP have been approved and auto-provision.
    My problem is that there might be many more of such users with redundant MC assigned to them in RAR. I can't find a way to search for such redundant MCs for cleanup. There is a possibility that when the same roles are assigned back to the users via request in CUP, these redundant MC if applicable will cause the Risk Analysis via CUP to not flag out any SoD issue.

Maybe you are looking for