How are REGION_1, REGION_2, and REGION_3 address fields mapped when using RChilli with Oracle HCM Cloud?

RChilli Candidate Profile Import follows the Oracle HCM Cloud Profile Import address mapping for country subdivisions. The address fields are mapped as follows:

• REGION_1 → County
• REGION_2 → State
• REGION_3 → Province

REGION_3 represents the Province value and is populated from the candidate’s parsed address information when the applicable country uses a province-based address structure.

RChilli includes State and Province attributes in the standard Oracle integration payload to support different address formats worldwide. The appropriate field should contain the address value according to the country’s geographic structure. For example:

• An address using a State should use REGION_2.
• An address using a Province should use REGION_3.
• An address using a County should use REGION_1.

The REGION_3 attribute cannot simply be removed from the standard Oracle HCM Cloud payload. For countries that do not use a Province field, REGION_3 can remain blank while the applicable address subdivision is populated in the appropriate region field.

RChilli’s Candidate Profile Import integration is designed for Oracle Fusion HCM Cloud. Oracle EBS uses different field mappings and is not directly mapped by the RChilli Candidate Profile Import integration. If Oracle HCM Cloud data is subsequently transferred to Oracle EBS, the EBS integration must handle the corresponding address-field mapping appropriately.

If a downstream integration reports an error related to REGION_3, verify the following:

1. The country-specific geography configuration in Oracle HCM Cloud.
2. Whether the address should use County, State, or Province.
3. The mapping between Oracle HCM Cloud region fields and the downstream system.
4. Whether unused region fields are being passed as blank values as expected.

For assistance with RChilli’s Oracle HCM Cloud integration, contact RChilli Support.