Purpose:
======
This PL/SQL procedure will identity the users having both "provisioned" and "provisioning" accounts.
Once such users are identified, It will cleanup the 'Provisioning' accounts without touching 'Provisioned' account.
Customer will not see the duplicate account anymore on the UI.
User can have one or more 'Provisioning' accounts.
Note :
A) Access policy name (We don't touch other accounts provisioned by other AP).
B) Resource Object name
Output :
It cleans up the records in UD Parent table, ORC, OIU, OSI,OTI, OBI tables and Executed in a order to avoid referential integrity constraints. Also, we don't need to delete records in child table as there won't be any records because the account will be in 'Provisioning' status.
======
This PL/SQL procedure will identity the users having both "provisioned" and "provisioning" accounts.
Once such users are identified, It will cleanup the 'Provisioning' accounts without touching 'Provisioned' account.
Customer will not see the duplicate account anymore on the UI.
User can have one or more 'Provisioning' accounts.
Note :
A) Access policy name (We don't touch other accounts provisioned by other AP).
B) Resource Object name
Output :
It cleans up the records in UD Parent table, ORC, OIU, OSI,OTI, OBI tables and Executed in a order to avoid referential integrity constraints. Also, we don't need to delete records in child table as there won't be any records because the account will be in 'Provisioning' status.
No comments:
Post a Comment