Create a Account and Lock it in SAP

[BT]

We have a requirement to create a SAP account for all employees as per birthright provisioning, which we are able to do using OOB SAP connector .

Now there is a requirement where the accounts created should be locked immediately for few users who have their user Customattribute15 column as No.

Basically this requirement is because of the license limitation on that particular application , so even though account needs to be created for all users , it should be locked for the user with Customattribute15 column as No. (This arrangement is because there are another SAP application that has a dependency on having the account in the first SAP application )

Customattribute15 is a field that is populated during user creation in Saviynt itself and is not a field that is updated at later stage .

Can anyone please suggest how this can be achieved. 

[Manu269]

You can use the below JSON in Status Threshold Config to read the user lock from SAP Tables via Import process.

Sample JSON
------------------
"lockedStatusColumn": "userlock",
"lockedStatusMapping": {
"Locked": [
32,
64,
128,
192
],
"Unlocked": [
0
]

If you are looking for Unlock and Lock action as part of provisioning. Currently connector is not supporting (V2020.1) Lock/Unlcok provisiong action, but you can do the same Operations using Enable/Disable.

Internal BAPI calls will do all the provisioning and deprovisioning actions.

Also : an Idea is also in place : Implement Lock/Unlock feature via ARS | Saviynt Ideas Portal

[BT]

@Manu269  got it , but any way we can disable the user (to lock account) immediately after creating the user in SAP.

[rushikeshvartak]

What is business use case?

[rushikeshvartak · Accepted solution]

You can use actionable analytics report

[BT]

@rushikeshvartak 

Basically this requirement is because of the license limitation on SAP PEC , so even though account needs to be created for all users , it should be locked for the user with Customattribute15 column as No. (This arrangement is because there are another SAP application (SAP BP) that has a dependency on having the account in the first SAP application and it doesn't matter if it is disabled )

Customattribute15 is a field that is populated during user creation in Saviynt itself and is not a field that is updated at later stage

[rushikeshvartak · Accepted solution]

Go with Actionable Report

[BT]

@rushikeshvartak @Manu269  😊 Thank you both for all the help Actionable Report did the trick.