Supported Features

SailPoint's Oracle HCM Cloud SaaS connector supports the following features:

  • Full Account Aggregation

  • Single Account Aggregation

  • Delta Aggregation

  • Discover Schema

  • Update Account

Note
The Oracle HCM Cloud connector will aggregate the attributes associated with primary workrelationship based on the workRelationships.PrimaryFlag value as true and its corresponding assignments whose workRelationships.assignments.EffectiveStartDate is closer to the aggregation date. In order to change this behavior refer to JSON Path Mapping.

Update Account Operation

Note

  • In order for the update operation to work, the source must have attribute synchronization configured. For more information, refer to Synchronizing Attributes.
  • To update USER_NAME and WORK_EMAIL, the worker must have an Oracle HCM account on the Oracle tenant.

The Update Account operation is only supported for the following attributes:

  • USER_NAME

  • WORK_EMAIL

Note: The following delta aggregation support applies when you use the ATOM Feeds API. Delta aggregation via Worker CSV Extractor (HCM Extract) works differently and returns all changed records as configured in the Oracle HCM Extract change-only mode. For more information about supported ATOM feeds, refer to Delta Aggregation.

Supported Use Cases

Category Example Supported in Full Aggregation and Delta Aggregation via CSV Extracts Supported in Delta Aggregation [Atom Feeds API]

Joiner

  • A new person who is joining the organization.

Yes

Yes

Joiner /Rehire use case

  • A person who was a contractor in the past and is getting rehired as a full time employee.

Yes

Yes

Joiner /Rehire use case/Conversion use case

  • A person who has a primary workrelationship as a contractor and a secondary workrelationship assigned as an employee at the time of full aggregation as contractor.

  • During the employee lifecyle contractor workrelationship, the person is getting terminated.

Yes

No

Mover use case

  • The person has a single workrelationship and a single assignment, and now there is a change to that in terms of events, such as the person being promoted, demoted, location changed, etc.

Yes

Yes

Mover use case

  • The person has multiple workrelationships with each having multiple assignments, and now there is a change to that in terms of events, such as the person being promoted, demoted, location changed, etc.

  • The end user is interested in pulling data specific to a particular workrelationship and its associated assignment.

Yes

Partially supported. The Oracle Atom Feeds API has a restriction of not returning the relationship of assignment and its parent work relationship.

Mover use case

  • The person is getting promoted with a change in both workrelationship and assignment.

Yes

Yes

Mover use case

  • The person has multiple work relationships and assignments with one being primary and the other being secondary.

  • The end user has a requirement to fetch the primary relationship, and during the employee lifecycle event the primary relationship is getting changed to a secondary relationship, or vice versa.

Yes

No

Mover use case

  • The person's manager is getting changed.

Yes

Partially supported. Only line manager changes are supported.

Leaver use Case

  • The person is leaving the organization.

Yes

Yes

Accounts Attribute

Support for fetching the below Information associated with the person:

  • Name details

  • Address Details

  • Phone Details

  • WorkRelationship Details

  • Assignment details

 

Yes

Partially supported. Limited attributes are supported in the Oracle Atom Feeds API.

For the list of attributes, refer to Oracle's documentation:

Note
The Oracle links provided correspond to the Oracle Fusion HCM 24 D release, and are the latest links as per the Oracle guide.

All supported scenarios for a non-worker. For example, joiner, mover and leaver, and account update.

  • A non-worker is joining the organization.

  • A non-worker is getting promoted.

  • A non-workers is getting terminated.

  • A non-workers person details (such as, first name, email, etc) is getting changed.

Yes

No. The Oracle Atom Feeds API does not support non-workers.

Back-dated joiner, mover, leaver and account update.

  • An employee is being terminated with the effective date in the past.

  • An employee is being hired with the effective date in the past.

  • An employee's details (such as, first name, email, etc) is being changed with the effective date in the past.

  • An employee is being promoted with the effective date in the past.

Yes

 

Partially supported. Changes related to employment (such as hiring, termination, etc) will be captured .