Saviynt should automate module provisioning for Oracle EBS

[Akumar00]

Hello Team,

There is a need to automatically assign the modules currently available to access EIS for the users getting provisioned with Oracle EBS accounts. We have an SQL query to perform the action on target but we are trying to find best optimal way to achieve the requirement.

We tried using actionable analytics, technical rules but it did not work as expected. We are seeking your assistance in creating a SQL/powqershell script using the SQL query and try saaving invoke the same.

Please let. Us know if there any other method that can be opted.

Please find the SQL query that can be used to do the module assignment to users on their Oracle EBS account provisioning

[This post has been edited by a Moderator to merge two posts.]

[SB]

Is this module currently created as an Entitlement in Saviynt?

[Akumar00]

Hi Sahil,

These modules are not being created as Entitlement in Saviynt.

Regards

[Akumar00]

Hello Team,

Kindly assist with an update, please let me know if any information is required

[dgandhi]

Can you elaborate more on the ask? If you want to automatically assign some module in target from Saviynt then those module should be present in Saviynt as an entitlement value.

once the entitlement is present in Saviynt then you can write actionable analytics to provision this module from Saviynt to target.

[Akumar00]

Hello @dgandhi 

The requirement is to automatically assign some module in Oracle EBS from Saviynt, there are close to 9-10 modules that needs to be assigned to users as part of birthright

Currently these modules are being manually assigned on target application, i appreciate your time sharing the solution but was curious to know if we can directly use the Connection (AddAccessJSON) and make the below SQL DB call to assign modules directly to users  on target

xxeis.eis_rs_utility.grant_module_access(2801,90001,sysdate,null,x_status,null); //the script has been attached above, as currently the connection json is configured with the sql query for provisioning

[Akumar00]

Hello @dgandhi 

Could you please elaborate if  we can use existing Entitlement Types (OEBS-Roles/OEBS-Responsibility/OEBS-Function) or we need to create any new Entitlement Type for assigning the modules

[Akumar00]

Hello @dgandhi 

Can you please assist with reference documentation that can be followed to fulfill the requirement.

[SB]

@Akumar00 You can use the below doc to create Technical/Birthright rule. If these entitlements can be created under existing Entitlement types then can use the same else you can create them as separate entitlementtypes.

https://docs.saviyntcloud.com/bundle/EIC-Admin-v23x/page/Content/Chapter05-Policies/Creating-Technic...

https://docs.saviyntcloud.com/bundle/EIC-Admin-v23x/page/Content/Chapter13-Access-Requests/ars-uc-im...

P.S: You can browse through the above documentation for other useful topics.

[Akumar00]

Hello Team,

Thank you for sharing details.

I have created new entitlement type to include the EIS modules to provision to user. The Add Access JSON has been modified accordingly to provision the modules. Currently, I am seeking assistance as I am facing issue in declaring bind variable required for provisioning of modules. The Stored procedure query was successfully executed on the DB server but from Saviynt the assignment is failing.

Can you please assist in correcting the below Add Access JSON configured in Saviynt

Add Access JSON (Saviynt)

"EIS Modules":["CALL xxeis.eis_rs_utility.grant_module_access('${accountName.toUpperCase()}','${task.entitlement_valueKey.entitlement_value}',SYSDATE,'',:x_status''')"]

Output From DB server

SQL> declare

    x_status        VARCHAR2(240);

begin

    xxeis.eis_rs_utility.grant_module_access(102034,702,SYSDATE,'',x_status,'');

end;

  2    3    4    5    6

  7  /

PL/SQL procedure successfully completed.

SQL> commit;

Commit complete.

[rushikeshvartak]

What is error you are getting in Saviynt logs ?

[Akumar00]

Hello @rushikeshvartak 

In Saviynt I am able to see generic error message both in provisioning comments and logs

Error Message: Exception occured while Excecuting Query Error while assigning access

Below Add Access JSON when executed on DB server without declaring bind variables gave below error

SQL> CALL xxeis.eis_rs_utility.grant_module_access(102034,702,SYSDATE,'','','');
CALL xxeis.eis_rs_utility.grant_module_access(102034,702,SYSDATE,'','','')
     *
ERROR at line 1:
ORA-06577: output parameter not a bind variable

But once bind variable was defined and query got executed on DB server as shared in early message

[Akumar00]

Hello @rushikeshvartak 

Currently, below are the configuration and error message

AddAccessJSON

"EIS Modules":["DECLARE @x_status varchar EXEC @x_status = CALL xxeis.eis_rs_utility.grant_module_access('${task.accountKey.accountID}','${task.entitlement_valueKey.entitlement_value}',SYSDATE,'',:x_status,'')"]"

Error in Saviynt
Error while assigning access - 702 to account - XXXXXXXXX -Missing IN or OUT parameter at index:: 1

[Akumar00]

Hello Team,

Even the below add access config is giving error (missing in OUT parameter)

"EIS Modules":["CALL xxeis.eis_rs_utility.grant_module_access('${task.accountKey.accountID}','${task.entitlement_valueKey.entitlement_value}',SYSDATE,'',:x_status,'')""]
}

[Akumar00]

"EIS Modules":["CALL xxeis.eis_rs_utility.grant_module_access('${task.accountKey.accountID}','${task.entitlement_valueKey.entitlement_value}',SYSDATE,'',:x_status,'')"]
}

[Akumar00]

Hello Team,

Kindly assist with the observed issue.

[SB]

From what I know it will not work as the connector does not support for out parameters in procedures calls.

[Akumar00]

Hello @SB 

Is there any other way to achieve the requirement. 

[Akumar00]

referring below post, it worked for an user

https://forums.saviynt.com/t5/identity-governance/using-bind-variable-in-remove-access-in-database-c...

I tried following the syntax format but did not work. Could you please assist with the correct one

[rushikeshvartak]

Ask application team to create SP without OUT parameter