Skip to main content
Lumos partners with Merge.dev for the Lumos Oracle HCM integration. For more info on the integration requirements, review the Merge.dev documentation.

​
After this article

You’ll be able to connect Oracle HCM to Lumos and use it as a source of user (HRIS) data.

​
Capabilities

Merge-powered integrations are read-only by design: provisioning, group/role management, and deprovisioning actions are not available for Oracle HCM. See HRIS Integration Capabilities for what HRIS data Lumos syncs.

​
Required plan and roles

  • You must be an Administrator in your company’s Oracle Cloud HCM instance. Oracle HCM has no role literally named “Administrator,” so connect with the Human Capital Management Application Administrator role. This role is required and cannot be scoped down further while guaranteeing functionality.
  • The connecting user’s security profiles must be able to see all workers. In Oracle HCM, go to Setup and Maintenance > Manage Data Role and Security Profiles and verify that the Public Person Security Profile and Worker Security Profile can view all workers. If the account can only see a subset of people, Lumos will sync an incomplete employee list.
  • Permission scoping: this is a read-only integration. Lumos syncs accounts and employee data out of Oracle HCM but does not write back, so no provisioning permissions are needed.

​
Read-only access vs provisioning

Is read-only possible? Yes, and it’s the only mode. What read-only requires. A Human Capital Management Application Administrator account whose security profiles (Public Person Security Profile and Worker Security Profile) can view all workers, connected through the Merge Link flow described below. Watch out for. A restricted security profile is the most common cause of an incomplete or empty employee sync, since Lumos only sees the workers that connecting account’s security profiles allow. The connection can also start failing later if that user’s role changes or their account is deactivated in Oracle HCM.

​
Instructions

  1. In Oracle HCM, confirm the connecting user meets the role and security-profile requirements above.
  2. Click the Oracle HCM card in your Lumos integrations (Reconnect or add new).
  3. Click the Connect Oracle HCM button.
  4. Follow the instructions in the Merge Link pop-up that appears to finish connecting the integration. Credentials are requested during this flow. This is not a native Lumos OAuth app.
After you connect the integration, set it as a source of user data in Lumos Source of Truth settings. For details on the different source of truth settings, see Source of Truth.

​
API Endpoints Used

​
Troubleshooting

​
Common Issues

Ensure you fulfill all the requirements to set up the integration:
  • You are an Administrator in your company’s Oracle Cloud HCM instance (Human Capital Management Application Administrator role).
  • The connecting user’s Public Person Security Profile and Worker Security Profile can view all workers. A restricted security profile is the most common cause of an empty or incomplete employee sync.
  • A connection can link and sync successfully and then start failing later if the connecting user’s role is changed or their account is deactivated in Oracle HCM. Reconnect with a valid administrator account if this happens.
HRIS Integration Capabilities Merge.dev documentation