Skip to Content
avatar image
Former Member

GRC 10.0 : Unable to generate data for SOD Review MSMP Process ID

Here is what I see when I create a job in NWBC Background Scheduler. I have followed all the instructions available in Performing Segregation of Duties Reviews in Access Control 10.0 to set up SAP_GRAC_SOD_RISK_REVIEW.

Here is the job log:

Job ID : 11321700 created

Extraction of user-risk data started

Total Number of Users:0

Extraction of user-risk data completed

Request to be group by risk owners

Request generation started

Request generation completed

Total number of request created: 0

I am not sure if I am missing something here. Any help will be appreciated.

Thank you,

Pawan

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Feb 05, 2013 at 03:01 PM

    Hi Pawan,

    I had a similar issue with User Access Review, opened a message in SAP and they sent me SAP Note 1729482 to be applied to BACKENDs.

    Then the  synchronization jobs (mentioned above by Asok kumar Christian) started to work correctly.

    Maybe it can help.

    Good luck,

    Vaner

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 07, 2013 at 03:24 PM

    Hello,

    Does anyone have an idea why I am unable to generate data SAP_GRAC_SOD_RISK_REVIEW workflow?

    Please help.

    Thanks,

    Pawan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Pawan,

      1. Before running the SoD Review data job, ensure that the Batch Risk Analysis job (GRAC_BATCH_RISK_ANALYSIS) is executed.

      2. Risk owners are defined in the Risk

      Thanks,

      Kailash

  • Jan 08, 2013 at 01:02 AM

    Hi Pawan,

       Have you tried as Kailash said. Apart from that you might need to run the below jobs in this sequence.

    GRAC_ROLEREP_PROFILE_SYNC

    Synchronizes all profiles in the repository

    GRAC_ROLEREP_ROLE_SYNC

    Synchronizes all roles in the repository

    GRAC_ROLEREP_USER_SYNC

    Synchronizes all users, and roles used by these users

    GRAC_BATCH_RISK_ANALYSIS

    Performs batch Risk Analysis

    GRAC_ACTION_USAGE_SYNC

    Retrieves the action usage for users

    GRAC_ROLE_USAGE_SYNC

    Retrieves the role usage

    BR,

    Asok

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 16, 2013 at 12:40 PM

    Hi Pawan,

    have u fixed this issue? Because I face the same issue in getting same results:

    Job ID : 11321700 created

    Extraction of user-risk data started

    Total Number of Users:0

    Extraction of user-risk data completed

    Request to be group by risk owners

    Request generation started

    Request generation completed

    Total number of request created: 0

    Does Anybody have a solution?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I can now generate the workflows, but!! I get no information about the actual transactions in the report, even though there's a field for it... Is that just me or are you seeing that as well?

      /henrik

  • avatar image
    Former Member
    Jun 19, 2013 at 09:03 PM

    Steps to try

    1. you need to enable "Offline Risk Analysis" in the GRC system

    2. Again run Batch jobs

    GRAC_ROLEREP_PROFILE_SYNC

    GRAC_ROLEREP_ROLE_SYNC

    GRAC_ROLEREP_USER_SYNC

    GRAC_BATCH_RISK_ANALYSIS

    GRAC_ACTION_USAGE_SYNC

    GRAC_ROLE_USAGE_SYNC

    3. Make sure Risk owners and Coordinator are updated

    4. then run the jobs to get data for SOD

    Hope this helps.

    Thanks

    Kailash


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Mahesh , Can you confirm whether we can keep just * in the UserID field .My job getting cancelled every time for the review.

      Also I havent updated Risk Owner for each Risk . Will this impact the SoD review report. ?? Is there any easy to update Risk Owners rather than to update each Risk ?