HRIS

Oracle HCM

Connect Oracle Fusion Cloud HCM to Ploy to see every user account in your Oracle tenant, the roles each account holds, and whether it is suspended. Ploy can also create user accounts, suspend and reactivate them, delete them, and give or remove Oracle roles one at a time.

This integration is in beta

The Oracle HCM integration is in beta. It was built from Oracle's REST API documentation and has not yet been checked against a live Oracle tenant, so some details may need adjusting once customers connect it. Beta does not limit what the integration can do.

The first step of setup is a consent checkbox. Ticking it lets Ploy capture redacted error data when a request to Oracle fails: the error response Oracle sends back, with personal details, passwords and other secrets removed. Ploy uses it only to fix problems with this integration. You must tick the box to continue.

What Ploy reads

  • Every user account (login) in your Oracle tenant, with its username

  • The Oracle roles each account holds, shown by their role code

  • Whether each account is active or suspended

Ploy reads user accounts, not worker records. It does not read pay, personal details, assignments or any other HR data.

Before you start

  • Ploy signs in to Oracle's HCM REST API with the username and password of an Oracle user. Create a dedicated integration user for Ploy rather than using a person's account.

  • You need to be able to create users and assign roles in Oracle's Security Console.

  • Know your Oracle Fusion address, for example acme.fa.us2.oraclecloud.com. It is the address you sign in to Oracle Fusion Cloud at.

Create the integration user in Oracle

  1. Sign in to Oracle Fusion Cloud as a security administrator and open the Security Console.

  2. Create a new user for Ploy, for example PLOY_INTEGRATION, and set a password. Use a password policy that does not expire it, or plan to update the connection in Ploy whenever it changes.

  3. Give the user a role that can view and manage user accounts and their roles, such as IT Security Manager. Ploy needs to read every user account and its roles; to create, suspend, delete and change roles, the role must allow those changes too. Your Oracle administrator may prefer a custom role with only those privileges.

  4. Save the user and confirm you can sign in with it.

Connect Oracle HCM in Ploy

  1. In Ploy, open Integrations and choose Oracle HCM.

  2. Tick the beta consent checkbox.

  3. Enter your Oracle Fusion address, for example acme.fa.us2.oraclecloud.com. You can paste the full sign-in address; Ploy keeps only the host.

  4. Enter the integration user's username and password.

  5. Click Test. Ploy reads one user account to check the address and sign-in work.

  6. Finish the setup. The first scan starts straight away and repeats every hour.

Things to know

  • Ploy shows each Oracle role by its role code (for example ORA_PER_EMPLOYEE_ABSTRACT), because the role's display name lives in a separate catalog Ploy does not read yet.

  • Roles are given and removed from the Oracle tenant's page under Resources in Ploy. Only roles someone in the tenant already holds can be given.

  • Accounts created from Ploy use the person's email address as the Oracle username and start with no roles. They are not linked to a worker record.

  • Suspending an account in Ploy suspends the Oracle login. It does not terminate the worker.

  • Deleting an account removes the Oracle login. The worker record and its history stay in Oracle.

  • If someone's username in Oracle is not an email address, Ploy still shows the account but cannot match it to an employee by email.

  • Ploy only connects to Oracle Fusion addresses ending in .oraclecloud.com. To connect a test environment as well, add a second Oracle HCM connection with its own address.

  • If the integration user's password changes or expires, scans stop. Update the password in the Oracle HCM connection in Ploy.

Was this helpful?
Was this helpful?