cancel
Showing results for 
Search instead for 
Did you mean: 

Updating User in IDM Does Not Reflect in Connected SAP AS ABAP System

former_member273752
Participant
0 Kudos
509

Hello Experts,

We are working on a IDM scenario on IDM 7.2. We have done the configuration as per the configuration guide, and successfully done an initial load of the users from a connected SAP ABAP system. From the IDM UI, when we change an user (Via web enabled tasks), the user record gets modified in IDM, but the changes do not get reflected in the connected ABAP system. When we look for system logs or tasks in the Identity Center, we do not find any entries. Can you please guide us in with some pointers, so as to why this behavior might be occurring?

Thanks and Regards,

Sid

View Entire Topic
ChrisPS
Advisor
Advisor
0 Kudos

Hello Sid,

              in such a case the hook task to create an abap user as defined in the repository should be called. Check the job log for this task and see if there is any information. Also ensure that this task is enabled and assigned a dispatcher.

Thanks,

Chris

former_member273752
Participant
0 Kudos

Hello Chris,

Thanks for the reply. We could find from the provisioning queue that the standard task "223/2. Modify ABAP User" gets called when we change the identity in IDM (This is as per our repository configuration, as indicated by image below):

However, the update requests are stuck there in the provisioning queue, and we do not find any log of the task. The "Job Status" column is also empty.

Any pointers as to where we can check why the entries in the provisioning queue are not processed?

Thanks and Regards,

Sid

Former Member
0 Kudos

Hi Siddhartha,

When you have something stuck in your provisioning queue, you should go in you SQL developer and execute this select:

select * from mcmv_audit where auditref= auditID(or something like that);

    - and the result will have the answer, why this task is stuck(if this lead you to another task just take this task auditID and at the end you will see why this task is stuck).

BR,

Simona

0 Kudos

Christopher Leonard wrote:

Hello Sid,

              in such a case the hook task to create an abap user as defined in the repository should be called. Check the job log for this task and see if there is any information. Also ensure that this task is enabled and assigned a dispatcher.

Thanks,

Chris

The hook task MX_HOOK7_TASK is assigned the value 370/7. Disable ABAP User, but unfortunately the task is not getting called when I disable the user in the IDM UI. The task is enabled and the job enderneath it 3258/LockUnlockAbapUser is assigned a dispatcher. Where do I need to assign event task that would trigger this provision?