Configure the Oracle HCM Inbound Integration from EverCheck

The Oracle HCM Inbound Integration from EverCheck integration flow retrieves the file with the verified employee licenses, registrations and certifications data from EverCheck. This file is transformed to DAT file format in Oracle Integration. As an optional step, a filter can be applied in which certain statuses are separated for manual review. You can also configure a lookup table to translate Issuing Authority statuses into seeded HCM Certification status. Subsequently, the DAT file with the details is uploaded into Oracle HCM Cloud using the HCM Data Loader.

The following high-level steps are required to configure the Oracle HCM Inbound Integration from EverCheck integration flow:
  1. Configure the Integration Variables
  2. Configure the Filter Conditions in the Integration
  3. Configure the Use of the Lookup Table in the Integration

Configure the Integration Variables

  1. In the Integration section of the project workspace in Oracle Integration, click the Oracle HCM Inbound Integration from EverCheck integration.
  2. Click the AssignGlobalParams Assign action, and configure the following:
    Field Information to Enter
    ftpPickUpFolder

    By default EverCheck uses the compliancechek folder for processed records. Validate this with your EverCheck implementation specialist.

    Validate this with your EverCheck implementation specialist.
    ftpDropOffFolder

    Exception reports will be written in this folder. These records are returned from EverCheck, but are not automatically processed and loaded into Oracle HCM Cloud. They have to be validated. Specify the folder location on your sFTP where the file can be placed for further processing or manual review.

    zipFileName

    This value refers to the name of the zip file containing the dat file being loaded into UCM and processed by HCM Data Loader. It can be left as is or changed based on your preference. The recipe is configured to return the file name dateTime format. For example: talentCertification_2024-02-12T16_00_34.434Z.zip.

    zipIssuesFileName

    This value refers to the name of the exception records file being written out as part of the recipe. It can be left as is or changed based on your preference. The recipe is configured to return the file name dateTime format. For example: employeeLicenseIssues_2024-02-12T17_39_04.931Z.zip

    Note that other values set in the AssignGlobalParams action should be left as is, since they are referenced throughout the recipe.

Configure the Filter Conditions in the Integration

The default filter condition configured within the recipe allows for separate processing of licenses, certifications, and registrations into two different work streams.

If values returned from EverCheck indicate a license is Active or Current, then the license record is processed and loaded into Oracle HCM Cloud. Any other values will result in the license record being written to the Exception Notification file and sent to an sFTP server.

You can edit the filter conditions to implement your business requirements.

  1. In the Integration section of the project workspace in Oracle Integration, click the Oracle HCM Inbound Integration from EverCheck integration.
  2. Click the For-Each action, and expand the Switch action under it.
  3. Click Route 1, and then click Actions Actions icon and select Edit.
  4. In the Configure route panel, you can click an expression and edit it if required.

Configure the Use of the Lookup Table in the Integration

Within the integration mapping as part of the generation of a DAT file, the existing mappings received from EverCheck are mapped to Oracle HCM Cloud values. This is done using the lookup table configured in the recipe. See Configure the Lookup Table.

The mapping occurs in the Map to writeTempEmployeeLicenseFile element.

  1. In the Integration section of the project workspace in Oracle Integration, click the Oracle HCM Inbound Integration from EverCheck integration.
  2. Click the For-Each action, and expand the Switch action under it.
  3. Click the Map to writeTempEmployeeLicenseFile element, and then click Actions Actions icon and select Edit to open the mapper.
  4. On the target side of the mapping screen, expand the Ever Check License Employee Record Set Name until the License Status field is shown.
  5. Select the License Status field to see the expression for the field.
    At this point, you can do one of the following, depending on your requirements:
    • Leave as is and leverage the default values of the lookup table within the integration to transform the inbound License Status to reflect the values within Oracle HCM Cloud. This may require additional values to be added to the lookup table and configurations in Oracle HCM Cloud.
    • Remove the lookup table reference and simply map the values which are being returned from EverCheck to the Statuses maintained in Oracle HCM Cloud. To achieve this, clear the Expression box and drag the License Status on the source side to the License Status on the target side. Note that additional configurations may also need to be made in Oracle HCM Cloud.