Oracle Cloud Infrastructure Documentation

Integrate with Oracle e-Business Employee Reconciliation (HRMS)

You can establish a connection between Oracle e-Business Employee Reconciliation (HRMS) and Oracle Access Governance by entering connection details and configuring the connector. To achieve this, use the Orchestrated Systems functionality available in the Oracle Access Governance Console.

Preinstall

Before you install and configure a Oracle e-Business Employee Reconciliation (HRMS) orchestrated system, you should consider the following pre-requisites and tasks.

Certified Components

The system can be any one of the following:

  • Oracle E-Business Suite 12.1.1 through 12.1.3
  • Oracle E-Business Suite 12.2.x
These applications may run on Oracle Database 10g, 11g, 12c, or 19c as either single database or Oracle RAC implementation.
Note

If your system is running on Oracle Database release 19.x, then download and apply the Oracle Database patch 31142749 from My Oracle Support. Applying this patch ensures that provisioning operations work fine.

Supported Operations

The Oracle e-Business Employee Reconciliation (HRMS) orchestrated system supports the following operations:
  • Create person
  • Add address
  • Update address
  • Delete address
  • Add assignment
  • Update assignment
  • Delete assignment

Create a System User Account for Oracle e-Business Employee Reconciliation (HRMS) Orchestrated System Operations

Oracle Access Governance requires a user account to access the system during reconciliation operations. Depending on the system you are using, you can create the user in your system and assign specific permissions and roles to the user.

For Oracle e-Business Employee Reconciliation (HRMS):

  1. Download all the files present inside this https://github.com/oracle/docker-images/tree/main/OracleIdentityGovernance/samples/scripts/Oracle_EBS_HRMS/1.0 location and copy them to a temporary directory on either the system host computer or a computer on which the Oracle Database Client has been installed.
    Alternatively, you can run the following steps to get the scripts:
    1. wget https://github.com/oracle/docker-images/archive/refs/heads/main.zip
    2. unzip main.zip
    3. cp docker-images-main/OracleIdentityGovernance/samples/scripts/Oracle_EBS_HRMS/1.0/* TEMP_DIR

      Where TEMP_DIR is a temporary directory on either the system host computer or a computer on which the Oracle Database Client has been installed.

  2. On the computer where you copy the scripts directory, verify that there is a TNS entry in the tnsnames.ora file for the system database.
  3. Change to the directory containing the scripts directory and depending on the host platform, run either the Run_HRMS_DBScripts.sh or Run_HRMS_DBScripts.bat file. These files are present in this https://github.com/oracle/docker-images/tree/main/OracleIdentityGovernance/samples/scripts/Oracle_EBS_HRMS/1.0 location.
  4. When you run the script, you are prompted for the following information:

    • Enter the ORACLE_HOME

      Set a value for the ORACLE_HOME environment variable. This prompt is displayed only if the ORACLE_HOME environment variable has not been set on the computer on which you are running the script.

    • Enter the System User Name

      Enter the login (user name) of a DBA account with the privileges to create and configure a new database user.

    • Enter the name of the database

      Enter the connection string or service name given in the tnsnames.ora file to connect to the system database.

    • Would you like to create new user for connector operations [y/n]

      Enter y or n to specify whether you want to create a new user for connector operations.

      This connects you the SQL*Plus client.

    • Are you running this script with EBS target 12.1.x [y/n]

      Enter y if you are using Oracle E-Business Suite release 12.1.1 through 12.1.3. When you do so, version compatible scripts will run on your system.

      Enter n if you are using Oracle E-Business Suite 12.2.x and later versions.

    • Enter password

      Enter the password for the Oracle database login. If you entered n at the earlier prompt to create a new user for connector operations, then the Type and Package are created, and then the connection to the database is disconnected. If you entered y, then the Type and Package are created, and then the connection to the database remains.

    • Enter password

      Enter the password of the dba user.

    • Enter New database Username to be created

      Enter a user name for the database account that you want to create.

    • Enter the New user password

      Enter a password for the database account that you want to create.

      This installs all wrappers packages under the APPS schema, creates the new database account, and then grants all the required privileges on the tables and packages.

    • Connecting with newly created database user

      Enter the connection string or service name that you provided earlier.

    • Enter the hostname for network acl [Input will be ignored If DB version is earlier than 11g]

      Enter the name of the computer hosting network acl in the following format:

      *. DOMAIN_NAME .com

      This prompt is received only if you entered y at one of the earlier prompts to create a new user for connector operations.

Install

You can establish a connection between Oracle e-Business Employee Reconciliation (HRMS) and Oracle Access Governance by entering connection details and configuring your database environment. To achieve this, use the Orchestrated Systems functionality available in the Oracle Access Governance Console.

Navigate to the Orchestrated Systems Page

Navigate to the Orchestrated Systems page of the Oracle Access Governance Console, by following these steps:
  1. From the Oracle Access Governance navigation menu  icon Navigation menu, select Service Administration → Orchestrated Systems .
  2. Select the Add an orchestrated system button to start the workflow.

Select system

On the Select system step of the workflow, you can specify which type of application you would like to onboard.

  1. Select Oracle E-Business Suite HRMS.

Enter details

On the Add Details step of the workflow, enter the details for the orchestrated system:
  1. Enter a name for the system you want to connect to in the Name field.
  2. Enter a description for the system in the Description field.
  3. Decide if this orchestrated system is an authoritative source, and if Oracle Access Governance can manage permissions by setting the following check boxes.
    • This is the authoritative source for my identities

      Select one of the following:

      • Source of identities and their attributes: System acts as a source identities and associated attributes. New identities are created through this option .
      • Source of identity attributes only: System ingests additional identity attributes details and apply to existing identities. This option doesn't ingest or creates new identity records.
    • I want to manage permissions for this system
    The default value in each case is Unselected.
  4. Select Next.

Add owners

You can associate resource ownership by adding primary and additional owners. This drives self-service as these owners can then manage (read, update or delete) the resources that they own. By default, the resource creator is designated as the resource owner. You can assign one primary owner and up to 20 additional owners for the resources.
Note

When setting up the first Orchestrated System for your service instance, you can assign owners only after you enable the identities from the Manage Identities section.
To add owners:
  1. Select an Oracle Access Governance active user as the primary owner in the Who is the primary owner? field.
  2. Select one or more additional owners in the Who else owns it? list. You can add up to 20 additional owners for the resource.
You can view the Primary Owner in the list. All the owners can view and manage the resources that they own.

Account settings

On the Account settings step of the workflow, enter how you want Oracle Access Governance to manage accounts when the system is configured as a managed system:
  1. When a permission is requested and the account doesn't already exist, select this option to create new accounts . This option is selected by default. When selected, Oracle Access Governance creates an account if one doesn't exist when a permission is requested. If you clear this option, permissions are provisioned only for existing accounts in the orchestrated system. If no account exists, the provisioning operation fails.
  2. Select the recipients for notification emails when an account is created. The default recipient is User. If no recipients are selected, notifications aren't sent when accounts are created.
    • User
    • User manager
  3. Configure Existing Accounts
    Note

    You can only set these configurations if allowed by the system administrator. When global account termination settings are enabled, application administrators can't manage account termination settings at the orchestrated-system level.
    1. Select what to do with accounts when early termination begins: Choose the action to perform when an early termination begins. This happens when you need to revoke identity accesses before official termination date.
      • Delete: Deletes all accounts and permissions managed by Oracle Access Governance.
        Note

        If specific orchestrated system doesn't support the action, no action is taken.
      • Disable: Disables all accounts and disables permissions managed by Oracle Access Governance.
        • Delete the permissions for disabled accounts: To ensure zero residual access, select this to delete directly assigned permissions and policy-granted permissions during account disablement.
      • No action: No action is taken when an identity is flagged for early termination by Oracle Access Governance.
    2. Select what to do with accounts on the termination date: Select the action to perform during official termination. This happens when you need to revoke identity accesses on the official termination date.
      • Delete: Deletes all accounts and permissions managed by Oracle Access Governance.
        Note

        If specific orchestrated system doesn't support Delete action, then no action is taken.
      • Disable: Disables all accounts and disables permissions managed by Oracle Access Governance.
        • Delete the permissions for disabled accounts: To ensure zero residual access, select this to delete directly assigned permissions and policy-granted permissions during account disablement.
        Note

        If specific orchestrated system doesn't support the Disable action, then account is deleted.
      • No action: No action is taken on accounts and permissions by Oracle Access Governance.
  4. When an identity leaves your enterprise you must remove access to their accounts.
    Note

    You can only set these configurations if allowed by your system administrator. When global account termination settings are enabled, application administrators cannot manage account termination settings at the orchestrated-system level.

    Select one of the following actions for the account:

    • Delete: Delete all accounts and permissions managed by Oracle Access Governance.
    • Disable: Disable all accounts and mark permissions as inactive.
      • Delete the permissions for disabled accounts: Delete directly assigned and policy-granted permissions during account disablement to ensure zero residual access.
    • No action: Take no action when an identity leaves the organization.
    Note

    These actions are available only if supported by the orchestrated system type. For example, if Delete is not supported, you will only see the Disable and No action options.
  5. When all permissions for an account are removed, for example when an identity moves between departments, you may need to decide what to do with the account. Select one of the following actions, if supported by the orchestrated system type:
    • Delete
    • Disable
    • No action
  6. Manage accounts that aren't created by Access Governance: Select to manage accounts that are created directly in the orchestrated system. With this, you can reconcile existing accounts and manage them from Oracle Access Governance.
Note

If you don't configure the system as a managed system then this step in the workflow will display but is not enabled. In this case you proceed directly to the Integration settings step of the workflow.
Note

If your orchestrated system requires dynamic schema discovery, as with the Generic REST and Database Application Tables integrations, then only the notification email destination can be set (User, Usermanager) when creating the orchestrated system. You cannot set the disable/delete rules for movers and leavers. To do this you need to create the orchestrated system, and then update the account settings as described in Configure Orchestrated System Account Settings.

Integration settings

On the Integration settings step of the workflow, enter the configuration details required to allow Oracle Access Governance to connect to the target system.

  1. In JDBC URL Template field, Specify the jdbc driver connection URL in the format jdbc:oracle:thin:@[host]:[port]:[DB]. For more info, refer to the JDBC driver documentation.
  2. In the User field, enter the database user with permission to access account table.
  3. Enter the password of the target database user in the Password field. Confirm the password in the Confirm password field.
  4. In Delete Person field, specify whether the employee record must be completely deleted from the target system. When you delete an employee record, the employee record is just set to terminated, but the record is not completely deleted from the target system.
    • If you set the value of this parameter to true, then the employee record is completely deleted from the target system.
    • If you set the value of this parameter to false, then the employee record is not deleted from the target system, but its status is just set to terminated.
  5. In Include Future Hires field, specify whether the connector must detect and reconcile records with future dated start date values.
    • If you set the value of this parameter to true, then the connector reconciles all employee records with future dated Start Date values.
    • If you set the value of this parameter to false, then the connector does not reconcile employee records with future dated Start Date values.

    Default value is true.

Finish Up

The final step of the workflow is Finish Up where you are prompted to download the agent for your Orchestrated System. Once you have downloaded the agent, you can install and configure the agent in your environment using the instructions in Install Oracle Access Governance Agent.

You are given a choice whether to further configure your orchestrated system before running a data load, or accept the default configuration and initiate a data load. Select one from:
  • Customize before enabling the system for data loads
  • Activate and prepare the data load with the provided defaults

Postinstall

There are no postinstall steps associated with an Oracle E-Business HRMS system.