Skip to main content

How to Obtain Outcome Data Status via-flat-file Integration for Oracle (ORC)

This guide covers how Oracle Recruiting Cloud pushes outcome data to Sapia.ai via flat-file (CSV), ensuring application statuses stay up to date automatically.

E
Written by Elbert Pranoto

For Oracle, application status change data (Outcome Data) collection can be collected via flat-file data transfer.
Clients can automate this through Oracle reporting system or any other data export service, with files transferred to Sapia.ai on a regular schedule via sFTP.

sFTP Folder: StatusChangeData

For complete sFTP details and setup instructions, refer to: https://help.sapia.ai/en/articles/12394560-importing-data-via-sftp


CSV Specification

File Type/Format: CSV (Comma Separated Value)

Column Header

Required?

Description

externalTenantID

Optional

This value is provided by Sapia.ai and remains constant across all records.

externalApplicationID

Required

Maps to candidateToken in Oracle.
e.g.:
Aenc2_3aPvVIOJ1nrvZ0eoxl2QprXD0SoWaeqHY6BS3_2bDwtG1ydCirubqd6SlVsNVGRZaRyIWYgq4bCdEls4OwAzhWFtRedek2ug0nggvto9NoqjUMHJDDe93gaKst48he_2freoAeDbrwe_2bOvD02PhSyNKn8OKgLItOjxzEFPUfXIoQvhA41h8q4emnI_3d

This value is sent to Sapia.ai through the assessment integration)

applicationStatus

Required

The Candidate phase-state name as configured in your Oracle tenant (e.g. Offer-Accetped).

Contact Sapia.ai to configure the mapping between your Oracle status phase-state and the corresponding Sapia.ai stages:
APPS_APPLICATION_NEW
APPS_APPLICATION_LONGLISTED
APPS_APPLICATION_SHORTLISTED
APPS_APPLICATION_INTERVIEW
APPS_APPLICATION_DECLINED
APPS_APPLICATION_OFFERED
APPS_APPLICATION_HIRED
APPS_APPLICATION_WITHDRAWN

The phase-state names must be provided to Sapia.ai verbatim

Note: The Phase–State values below are provided as a reference only — your configuration may differ.
https://docs.oracle.com/en/cloud/saas/talent-management/farqa/what-are-the-phases-and-states-of-a-candidate-selection-process.html#u30255844

date

Required

Format: yyyy-MM-dd

Timestamp when the status change occurred

comment

Optional

Free-text field for additional information about the status change

Note on column order and headers: Column headers and their order do not need to match this specification exactly. Sapia.ai supports configuration mapping, so columns can be mapped to the correct fields during setup on Sapia.ai's configuration

Below is the sample file:

Did this answer your question?