# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Oracle HCM Cloud SaaS connector uses the following default correlation and object configurations.

## Default Correlation Configuration

Before you aggregate accounts from this source, you can map account attributes with their corresponding identity attributes based on your requirements.

You can customize the correlation configuration. Refer to [Assigning Source Accounts to Identities](<https://documentation.sailpoint.com/saas/help/accounts/correlation.html>) for more information.

When you first create the Oracle HCM Cloud SaaS source, the default correlation mapping is:

| Account Attribute | Operation | Identity Attribute |
| --- | --- | --- |
| WORK\_EMAIL | Equals | Work Email |

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| PERSON\_NUMBER | Account |

### Default Account Attributes

The Oracle HCM Cloud SaaS connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| PERSON\_NUMBER | Unique identifier for the person. This is an Account ID which must not be changed. |
| HIRE\_DATE | The hiring date of the person. |
| TERMINATION\_DATE | Termination date of the person. |
| PERIOD\_OF\_SERVICE\_ID | Unique identifier for the person WorkRelationship. |
| WORKER\_TYPE | Type of the person, for example Employee/Contingent. |
| WORKRELATIONSHIP\_PRIMARY\_FLAG | Flag indicating whether WorkRelationship is primary or not. |
| ASSIGNMENT\_ACTION\_CODE | Primary assignment's action code of the person. For example, `HIRE` |
| ASSIGNMENT\_EFFECTIVE\_START\_DATE | Primary assignment effective start date of the person. |
| ASSIGNMENT\_EFFECTIVE\_END\_DATE | Primary assignment effective end date of the person. |
| ASSIGNMENT\_PRIMARY\_FLAG | Flag indicating whether assignment is primary or not. |
| ASSIGNMENT\_STATUS | Primary assignment status of the person. |
| WORK\_EMAIL | Work Email for the person |

> [!NOTE]
>
> The connector internally generates a JSON path for the above attributes where the PrimaryFlag is set to true. If a customer wants to aggregate data where the PrimaryFlag is false, they should add a JSON path mapping for that specific attribute.

### Additional Account Attributes

> [!NOTE]
>
> These attributes are calculated attributes based on the mandatory account schema and should not be part of the HCM Export Files.

| Attribute Name | Description |
| --- | --- |
| FUTURE\_WORKRELATIONSHIP\_START\_DATE | The future hire date of the person. |
| FUTURE\_ASSIGNMENT\_START\_DATE | The future assignment start date of the person. This attribute is only supported as part of full aggregation. |
| FUTURE\_WORKRELATIONSHIP\_END\_DATE | The future termination date of the person. |
| FUTURE\_ASSIGNMENT\_ACTION | The future action of the person. This attribute is only supported as part of full aggregation. |

> [!NOTE]
>
> You must manually add these attributes in the account schema.