> Continuous Process Improvement > Hire to Retire Employee Lifecycle > Oracle HCM Onboarding > Data Template

Data Template: Hire to Retire - Employee Lifecycle

Oracle HCM Onboarding

Hire to Retire - Employee Lifecycle Attributes (22) Hire to Retire - Employee Lifecycle Activities (15) Extraction Guides (3)

Your Hire to Retire - Employee Lifecycle Data Template

This template provides a clear roadmap for collecting the essential data needed to analyze your Hire to Retire - Employee Lifecycle process. It outlines the key attributes to gather, the critical activities to track, and practical guidance on how to extract this information from your source system. Use this resource to ensure you capture all necessary data points for a comprehensive process mining analysis.

Recommended attributes to collect
Key activities to track
Extraction guidance

New to event logs? Learn how to create a process mining event log.

Download Template

Hire to Retire - Employee Lifecycle Attributes

These are the recommended data fields to include in your event log for comprehensive Hire to Retire - Employee Lifecycle analysis.

3 Required 7 Recommended 12 Optional

	Name	Description
	Activity ActivityName	The name of a specific event or task that occurred in the employee's lifecycle, such as 'Offer Accepted' or 'Performance Review Conducted'.
Description The Activity Name describes a single step or milestone within the Hire to Retire process. These events are the building blocks of the process map, representing key actions taken by HR personnel, managers, or the system itself. Examples include initiating a background check, completing onboarding tasks, or approving a promotion. Analyzing these activities allows for the visualization of the process flow, identification of bottlenecks, and measurement of frequencies for different process steps. Understanding the sequence and distribution of activities is fundamental to discovering how the employee lifecycle process actually operates versus how it is designed. Why it matters This attribute defines the steps in the process, enabling the visualization of process maps and the analysis of process flow and variations. Where to get This is typically derived from event types, task names, or status changes within various Oracle HCM Onboarding and Core HR modules. Examples Offer AcceptedBackground Check CompletedPayroll Setup CompletedTermination Initiated
	Employee ID EmployeeId	The unique identifier for an employee, serving as the case ID for their entire lifecycle within the organization.
Description The Employee ID is the cornerstone of the Hire to Retire process analysis, uniquely identifying each employee's journey from their initial application to their final offboarding. Every event, status change, and transaction recorded in Oracle HCM Onboarding is linked to this identifier, creating a continuous event log for each individual. In process mining, this attribute is used to correlate all related activities, such as 'Offer Accepted', 'Background Check Completed', and 'Termination Initiated', into a single, cohesive case. This enables a holistic view of the employee lifecycle, allowing analysts to visualize complete employee journeys, measure end-to-end cycle times, and identify common or divergent paths employees take through the organization. Why it matters It is the primary key that connects all employee-related events, making it possible to reconstruct and analyze the entire employee lifecycle from hire to retire. Where to get This is a core attribute in Oracle HCM Cloud, typically found in the Person or Worker records. Examples 100234598765E-0054321
	Start Time EventTimestamp	The exact date and time when a specific lifecycle activity occurred.
Description This timestamp marks the precise moment an activity was recorded in the system. It is the temporal foundation for all process mining analysis, providing the chronological order of events for each employee's case. This attribute is critical for calculating cycle times, durations, and wait times between activities. For instance, the time difference between 'Background Check Initiated' and 'Background Check Completed' timestamps reveals the lead time for that specific step. Analyzing these timestamps helps identify bottlenecks, measure process performance against SLAs, and understand the temporal dynamics of the employee journey. Why it matters It establishes the chronological sequence of events, which is essential for calculating all time-based metrics like cycle times and identifying process delays. Where to get This corresponds to the creation or completion date and time fields associated with tasks, events, or status changes in Oracle HCM transaction data. Examples 2023-03-15T09:00:00Z2023-08-01T14:35:10Z2024-01-20T11:21:05Z
	Department DepartmentName	The department to which the employee is assigned, such as 'Sales', 'Engineering', or 'Finance'.
Description This attribute represents the organizational unit where the employee works. It is a critical dimension for segmenting and comparing process performance across different parts of the business. Analyzing the Hire to Retire process by department allows for powerful comparative analysis. For example, you can identify which departments have the longest onboarding times, the highest turnover rates, or the lowest adherence to performance review cycles. These insights help tailor process improvement initiatives to the specific needs and challenges of each department. Why it matters It allows for segmentation and comparison of process metrics, such as turnover rates and cycle times, across different business units. Where to get Consult Oracle HCM Onboarding documentation. This information is a standard part of an employee's assignment record in Oracle HCM. Examples SalesEngineeringFinanceHuman Resources
	End Time EventEndTime	The exact date and time when an activity was completed.
Description The Event End Time marks the completion of a specific task or process step. While Start Time indicates when an activity began, End Time signifies its conclusion. The presence of both timestamps allows for the precise measurement of the processing time for individual activities. This attribute is essential for calculating activity-level durations, distinguishing between processing time (End Time minus Start Time) and waiting time (the gap between one activity's End Time and the next's Start Time). This level of detail is critical for root cause analysis of bottlenecks, as it helps determine whether delays are due to long tasks or long waits between tasks. Why it matters It enables the precise calculation of activity processing times, which helps differentiate active work time from idle waiting time in the process. Where to get Consult Oracle HCM Onboarding documentation. This often corresponds to completion or resolution date fields in transaction data. Examples 2023-03-15T17:30:00Z2023-08-02T10:00:15Z2024-01-20T11:25:00Z
	Hire Date HireDate	The official start date of the employee's employment with the company.
Description The Hire Date is a key milestone in every employee's lifecycle, marking their official entry into the organization. It serves as a baseline for measuring various time-sensitive processes and compliance checks. This attribute is used in multiple KPIs and analyses. For example, it is the deadline against which the 'Payroll Setup On-Time Rate' is measured. It also provides the starting point for calculating employee tenure and for analyzing how onboarding times may have changed over different periods. Why it matters It serves as a critical baseline date for calculating employee tenure and for measuring the timeliness of initial onboarding and setup activities. Where to get Consult Oracle HCM documentation. This is a fundamental attribute of the employee record in Core HR. Examples 2023-04-012022-09-152024-02-12
	Job Role JobRole	The employee's specific job title or role, such as 'Software Engineer' or 'Account Manager'.
Description The Job Role attribute defines the specific position or title held by the employee. This provides a more granular level of detail than the department and is essential for role-specific process analysis. This attribute is crucial for dashboards like 'Employee Turnover by Role & Dept' and for calculating KPIs like 'Critical Role Turnover Rate'. It helps organizations understand if certain roles are harder to fill, have longer onboarding cycles, or experience higher turnover. These insights can inform workforce planning, talent management strategies, and role-specific process optimizations. Why it matters It enables role-based analysis, helping to identify process issues, compliance gaps, or turnover patterns specific to certain job functions. Where to get Consult Oracle HCM Onboarding documentation. This is part of the employee's job or position data in Core HR. Examples Software EngineerSenior Account ManagerHR Business PartnerFinancial Analyst
	Recruitment Source RecruitmentSource	The channel through which the employee was hired, such as 'LinkedIn', 'Employee Referral', or 'Company Website'.
Description This attribute tracks the origin of a successful hire, indicating which recruitment channel led to the candidate's application and subsequent employment. This data is typically captured early in the recruitment phase and is associated with the new hire's record. Analyzing recruitment sources is key to optimizing talent acquisition strategies. It supports the 'Recruitment Source Performance' dashboard by allowing the business to measure conversion rates, time-to-hire, and quality of hire for each channel. This helps focus recruitment efforts and budget on the most effective and efficient sources. Why it matters It is essential for evaluating the effectiveness of different talent acquisition channels and optimizing recruitment strategies and spending. Where to get Consult Oracle HCM Onboarding or Oracle Recruiting Cloud documentation. This is often captured during the application process. Examples LinkedInEmployee ReferralCompany Careers PageIndeed
	Termination Reason TerminationReason	The reason for the employee's departure, such as 'Voluntary Resignation' or 'Involuntary - Performance'.
Description This attribute provides context for why an employee's lifecycle with the company ended. It categorizes terminations into different types, which is fundamental for understanding employee turnover. In process mining, this is a critical dimension for analyzing attrition patterns. By filtering on termination reason, analysts can investigate if certain process experiences, such as long promotion cycles or infrequent performance reviews, are correlated with voluntary resignations. This insight helps HR develop targeted retention strategies. Why it matters It provides crucial context for turnover analysis, helping to distinguish between voluntary and involuntary attrition and informing retention strategies. Where to get Consult Oracle HCM documentation. This is a standard field captured during the termination process in Core HR. Examples Voluntary - Resignation for another opportunityInvoluntary - PerformanceInvoluntary - Reduction in ForceRetirement
	User UserId	The identifier of the user, such as an HR representative or manager, who performed the activity.
Description This attribute captures the person responsible for executing a specific task in the employee lifecycle process. This could be the recruiter who extended an offer, the HR administrator who completed the I-9 verification, or the manager who approved a promotion. Analyzing the process by user helps identify training opportunities, workload distribution, and performance variations among individuals or teams. For example, it can reveal if certain users are consistently associated with process delays or deviations, or if they are high-performers who handle tasks more efficiently. Why it matters It attributes process activities to specific individuals, enabling analysis of workload, resource performance, and identification of training needs. Where to get Consult Oracle HCM Onboarding documentation. This is typically found in 'Created By' or 'Last Updated By' fields on transaction records. Examples j.smithe.davishr.admin01
	Background Check Status BackgroundCheckStatus	The final outcome of the background check process, such as 'Completed - Clear' or 'Requires Review'.
Description This attribute captures the result of the background check, which is a critical gate in the onboarding process. The status determines whether the hiring process can proceed smoothly or if additional steps and reviews are required. Analyzing the distribution of different statuses can help in understanding the quality of candidate pools from various recruitment sources. It is also essential for analyzing the 'Background Check Cycle Time' dashboard, as cases that require review may naturally have longer cycle times. This context prevents misinterpretation of the data. Why it matters It provides the outcome of a key onboarding step, adding context to cycle time analysis and helping to identify rework or exception paths. Where to get Consult Oracle HCM Onboarding documentation. This data may come from the onboarding module or an integrated third-party background check provider. Examples Completed - ClearRequires ReviewCancelledIn Progress
	Business Unit BusinessUnitName	The larger business division or unit the employee belongs to.
Description A Business Unit is a high-level organizational structure, often representing a distinct product line, service area, or geographical region. It provides a broader organizational context than a department. Analyzing processes at the Business Unit level is valuable for senior leadership to compare performance across major divisions of the company. It can help identify systemic issues or best practices within a large business unit that can then be addressed or shared across the organization. Why it matters It allows for high-level aggregation and comparison of process metrics across major organizational divisions. Where to get Consult Oracle HCM documentation. This is typically part of the employee's assignment and organizational hierarchy data. Examples Consumer ProductsEnterprise SoftwareCloud ServicesGlobal Consulting
	Employee Type EmployeeType	Categorizes the employee's employment status, such as 'Full-Time', 'Part-Time', or 'Contractor'.
Description This attribute classifies the nature of the employment relationship. Different types of employees often follow different process variants for onboarding, performance management, and offboarding. Analyzing the process based on Employee Type can reveal significant differences. For instance, the onboarding process for a contractor may be much shorter and involve fewer steps than that for a full-time employee. Segmenting the analysis by this attribute ensures that comparisons are meaningful and helps identify opportunities to streamline processes for each specific employment type. Why it matters It allows for process analysis to be segmented by employment status, revealing different process paths and requirements for different types of workers. Where to get Consult Oracle HCM documentation. This is part of the standard employee assignment information in Core HR. Examples Full-Time EmployeePart-Time EmployeeContractorIntern
	Is Compliant IsCompliant	A flag that indicates if a case followed the expected process path according to compliance rules.
Description This is a calculated boolean attribute that assesses whether an employee's lifecycle events adhere to predefined compliance models or business rules. For example, a rule might state that a background check must be completed before an offer is finalized, or that certain training must be assigned within 30 days of hire. This attribute directly supports the 'HR Compliance Violation Rate' KPI. By flagging non-compliant cases, it allows for easy quantification of compliance risk and enables root cause analysis to understand why deviations are occurring. It simplifies complex compliance checking into a single field for easy reporting and monitoring. Why it matters It quantifies adherence to critical business rules and regulations, allowing for proactive monitoring and mitigation of compliance risks. Where to get This is calculated in the process mining tool or data transformation layer by applying a set of business rules to the sequence of activities and their attributes. Examples truefalse
	Is Critical Role IsCriticalRole	A flag indicating whether the employee's job role is considered critical to the organization's success.
Description This is a derived boolean attribute that identifies positions that are vital for business continuity, strategic initiatives, or possess unique skills that are difficult to replace. This classification is typically maintained by HR and leadership based on workforce planning. This flag is essential for calculating the 'Critical Role Turnover Rate' KPI. It allows the analysis to focus specifically on the attrition of key talent, helping the organization to prioritize retention efforts where they will have the most impact. Dashboards can be filtered by this attribute to highlight process issues affecting the most important employees. Why it matters It allows the organization to specifically monitor and analyze the lifecycle and turnover of its most vital employees, helping to prioritize retention efforts. Where to get This is derived by mapping the 'JobRole' attribute against a predefined list of critical roles provided by the business. Examples truefalse
	Job Requisition ID JobRequisitionId	The unique identifier for the job requisition that led to the hiring of the employee.
Description The Job Requisition ID links a new hire back to the original request to fill a position. This identifier connects the recruiting and onboarding processes to earlier steps in the talent acquisition lifecycle. By including this ID, it becomes possible to conduct a more comprehensive end-to-end analysis, starting from the time a job was opened. It is essential for calculating the full 'Time to Hire' KPI and for analyzing how characteristics of the requisition, such as priority or role level, impact the subsequent hiring and onboarding process. Why it matters It links the employee's journey back to the initial hiring request, enabling true end-to-end time-to-hire analysis and connecting hiring outcomes to requisition details. Where to get Consult Oracle Recruiting Cloud or HCM documentation. This ID is generated in the recruiting module and should be associated with the new hire's record. Examples REQ-2023-05-102JR-FIN-00348001567
	Last Data Update LastDataUpdate	The timestamp indicating the last time the data for this event was refreshed from the source system.
Description This attribute records when the data was last extracted and loaded into the process mining environment. It is a metadata field that reflects the freshness of the dataset, rather than a timestamp of a business event itself. This information is vital for understanding the timeliness of the analysis and the dashboards. It allows users to know if they are looking at data from yesterday, last week, or last month, which is critical for making informed, up-to-date business decisions. It is usually displayed prominently on dashboards to provide context to all viewers. Why it matters It ensures transparency about data freshness, allowing users to understand how current the process analysis is and to trust the insights provided. Where to get This timestamp is generated by the data pipeline or ETL tool at the end of a successful data refresh cycle. Examples 2024-05-21T04:00:00Z2024-05-20T04:00:00Z
	Location Location	The physical work location or country of the employee.
Description This attribute specifies the geographical location, such as the office, city, or country, where the employee is based. HR processes can vary significantly based on local labor laws and regional business practices. Using Location as a dimension for analysis helps uncover regional variations in process performance. For example, background check completion times might be longer in certain countries due to local regulations. This allows for geographically-aware process monitoring and improvement. Why it matters It enables geographical analysis of the process, highlighting regional variations in cycle times, compliance, and process flows. Where to get Consult Oracle HCM documentation. This is a standard part of the employee's assignment or personal data. Examples USAGermanyIndiaUnited Kingdom
	Payroll Setup On Time PayrollSetupOnTime	A flag that indicates if an employee's payroll was set up before their official hire date.
Description This calculated boolean attribute measures adherence to a critical onboarding SLA: completing payroll setup before the employee's start date. It is derived by comparing the timestamp of the 'Payroll Setup Completed' activity with the employee's 'Hire Date'. This attribute directly supports the 'Payroll Setup On-Time Rate' KPI. It simplifies analysis by converting a date comparison into a simple true or false value, making it easy to filter, aggregate, and visualize compliance on dashboards. This helps to quickly identify departments or regions that are struggling with timely payroll setup, a key factor in new hire satisfaction. Why it matters It directly measures compliance with a critical onboarding SLA, providing a clear metric for payroll setup efficiency and its impact on new hire experience. Where to get This is calculated during data transformation by comparing 'EventTimestamp' of the 'Payroll Setup Completed' activity with the 'HireDate' attribute for each case. Examples truefalse
	Performance Rating PerformanceRating	The rating assigned to an employee during a performance review cycle, such as 'Exceeds Expectations'.
Description This attribute captures the outcome of a performance evaluation. The rating provides a quantitative or qualitative measure of an employee's performance against their goals and company expectations. Analyzing this data in conjunction with the process flow can yield powerful insights. For example, it can be used to investigate correlations between performance ratings and promotion times, or to see if high-performing employees who resign have experienced process-related frustrations, such as delayed role changes. It is a key element for the 'Performance Review Cycle Adherence' dashboard. Why it matters It adds a qualitative outcome to performance review events, allowing for analysis of how employee performance correlates with career progression and retention. Where to get Consult Oracle HCM Performance Management module documentation. This is typically stored in performance review forms or records. Examples Exceeds ExpectationsMeets ExpectationsNeeds Improvement5
	Source System SourceSystem	Identifies the system from which the event data was extracted, such as 'Oracle HCM Onboarding'.
Description This attribute specifies the originating information system for each event record. In a complex HR landscape, employee data might come from the core HCM, a dedicated onboarding module, a payroll system, or a performance management tool. Tagging each event with its source system is crucial for data governance and troubleshooting. In analysis, knowing the source system helps in understanding data integration points and potential discrepancies. For example, if delays are observed around payroll setup, it is useful to know if those events originate from the core HCM or a separate payroll application. Why it matters It provides crucial context about data origin, which is important for data validation, integration analysis, and understanding a multi-system process landscape. Where to get This is typically a static value added during the data extraction process to label the dataset's origin. Examples OracleHCMOnboardingOracleCoreHROracleRecruiting
	Termination Date TerminationDate	The official last day of an employee's employment.
Description The Termination Date marks the official end of an employee's tenure with the company. It is a key date in the offboarding process, serving as a reference point for final payroll calculations, benefits termination, and system access revocation. In process mining, this date is used to calculate the total employee tenure when combined with the Hire Date. It also serves as the anchor for analyzing the offboarding process, helping to measure if all offboarding tasks were completed in a timely manner relative to the employee's departure. Why it matters It defines the endpoint of the employee lifecycle, enabling tenure calculations and analysis of the offboarding process timeliness. Where to get Consult Oracle HCM documentation. This is a standard field captured during the termination process in Core HR. Examples 2024-05-312023-12-152024-01-05

Required Recommended Optional

Hire to Retire - Employee Lifecycle Activities

These are the key process steps and milestones to capture in your event log for accurate process discovery and optimization.

6 Recommended 9 Optional

	Activity	Description
	Employee Onboarded	This is the official hire date when the employee becomes an active part of the organization. It represents the conversion from a pending worker to an active employee record in the core HR system.
Why it matters This is a primary milestone in the employee lifecycle. It serves as the baseline for measuring onboarding duration and time-to-productivity. Where to get This corresponds to the 'Hire Date' field being populated and the employee's HR status becoming 'Active'. It's a fundamental transaction in the Core HR module. Capture Captured from the effective date of the 'Hire' action on the employee's record. Event type explicit
	Offboarding Tasks Completed	This activity represents the completion of all required offboarding steps, such as asset return, knowledge transfer, and final payroll processing. It marks the clean closure of the employee's record.
Why it matters This is the final activity in the employee lifecycle. It's the end point for measuring the Average Offboarding Cycle Time and ensuring a compliant and efficient process. Where to get This is inferred from the completion of the master offboarding journey or checklist assigned to the employee in Oracle HCM. Capture Inferred from the completion timestamp of the overall offboarding journey or the last task in the sequence. Event type inferred
	Offer Accepted	This activity marks the point where a candidate formally accepts the employment offer. It is the trigger for the pre-boarding and onboarding processes within Oracle HCM.
Why it matters This is a critical starting point for the employee's journey. Analyzing the time from this event to subsequent steps helps measure the efficiency of the hiring-to-onboarding handoff. Where to get Typically captured from the recruiting module when a candidate's offer status is updated to 'Accepted' or a similar state, which then triggers the onboarding journey. Capture Inferred from a status change on the candidate's job offer record. Event type inferred
	Onboarding Journey Initiated	This activity signifies the creation and assignment of the formal onboarding plan or checklist to the new employee. It represents the official start of their onboarding experience in the system.
Why it matters Marks the transition from pre-boarding to active onboarding. It is a key milestone for measuring overall onboarding cycle time and consistency. Where to get This is an explicit event logged when an HR specialist or automated process assigns an onboarding 'Journey' to the pending worker or employee record. Capture Logged from the creation event of the Onboarding Journey assigned to the employee. Event type explicit
	Payroll Setup Completed	Marks the point where the new employee's information is fully processed and they are active in the payroll system. This includes bank details, tax withholdings, and salary information.
Why it matters Timely payroll setup is critical for new hire satisfaction and is a key indicator of HR operational efficiency. This activity helps measure the Payroll Setup On-Time Rate KPI. Where to get Can be inferred from the completion of payroll-related tasks in the onboarding journey or from a status update in the core payroll module for that employee. Capture Inferred from the completion date of all payroll-related onboarding tasks. Event type inferred
	Termination Initiated	This is the formal start of the offboarding process, triggered by a resignation or a decision to terminate employment. It initiates all subsequent offboarding tasks.
Why it matters This event is the start of the final phase of the employee lifecycle. It's the trigger for measuring offboarding cycle time and analyzing turnover. Where to get This is an explicit HR action recorded in Oracle Core HR when a manager or HR administrator submits a termination request for an employee. Capture Captured from the effective date of the 'Termination' action on the employee's record. Event type explicit
	Background Check Completed	Marks the successful completion of the background screening process. The outcome of this check determines if the hiring process can proceed.
Why it matters This event's timestamp is crucial for calculating the total cycle time of the background check. Delays here directly impact the employee's start date. Where to get Captured when the 'Background Check' task status is updated to 'Completed' or 'Cleared' in the employee's onboarding journey. Capture Inferred from the status change of the background check task to a terminal 'completed' state. Event type inferred
	Background Check Initiated	Represents the formal start of the background screening process for a new hire. This is usually managed as a specific task within the onboarding checklist or journey.
Why it matters The duration of background checks is a common bottleneck. Tracking this start time is essential for measuring and optimizing the Background Check Lead Time KPI. Where to get This is likely recorded when the 'Background Check' task is assigned or its status changes to 'In Progress' within the employee's onboarding journey in Oracle HCM. Capture Inferred from the status change or creation date of the background check task. Event type inferred
	Exit Interview Conducted	Marks the completion of the exit interview with the departing employee. This is often managed as a task within an offboarding journey.
Why it matters Provides qualitative data on reasons for departure. Tracking its completion ensures that this valuable feedback is consistently collected. Where to get Typically tracked as a manual task within an offboarding checklist or journey. The event is the completion of this task. Capture Inferred from the completion date of the 'Exit Interview' task in the offboarding journey. Event type inferred
	I-9 Verification Completed	This marks the completion of the mandatory U.S. Form I-9, Employment Eligibility Verification. This is a critical compliance step for all U.S. hires.
Why it matters Tracking this activity is essential for ensuring regulatory compliance and avoiding legal penalties. It is a non-negotiable step in the onboarding process. Where to get Captured from the completion status of the dedicated I-9 task within the Oracle HCM onboarding journey, which often has specific fields for verification dates. Capture Inferred from the completion status and timestamp of the Form I-9 task. Event type inferred
	New Hire Data Submitted	Represents the completion of personal data collection tasks by the new hire. This includes filling out personal information, tax forms, and other required documentation.
Why it matters Completeness and timeliness of this activity are critical for subsequent steps like payroll setup. Delays here can cause significant downstream issues. Where to get Inferred from the completion timestamp of a specific task or group of tasks related to personal data collection within the onboarding journey. Capture Inferred from the completion date of the 'Personal Information' or equivalent task. Event type inferred
	Performance Review Conducted	Marks the completion of a formal performance review cycle for an employee. This is a recurring event throughout the employee's tenure.
Why it matters Analyzing the frequency and regularity of reviews is key to understanding performance management adherence and its impact on employee development and retention. Where to get This information is captured in the Oracle HCM Performance Management module. The event corresponds to the final approval or completion status of a review document. Capture Inferred from the completion date of the performance review form or process. Event type inferred
	Promotion Approved	This activity marks the final approval of an employee's promotion. This is a key positive milestone in an employee's career progression.
Why it matters This event concludes the internal mobility process, allowing for the calculation of the Internal Mobility Approval Time KPI and analysis of career path velocity. Where to get Captured when the promotion transaction receives its final approval in the workflow. The effective date of the promotion is recorded. Capture Logged from the workflow system upon final approval of the promotion action. Event type explicit
	Role Change Initiated	Represents the start of a process to change an employee's job, department, or location. This can be a promotion, lateral transfer, or other internal move.
Why it matters This activity is the starting point for measuring internal mobility efficiency. Long durations between initiation and approval can indicate process bottlenecks. Where to get Logged when a manager or HR specialist initiates a 'Change Job' or 'Promotion' action for an employee in Core HR. Capture Captured from the transaction log for HR actions like 'Job Change', 'Transfer', or 'Promotion'. Event type explicit
	Training Assigned	This activity represents the assignment of mandatory or role-specific training to the new employee. This is typically done through an integrated Learning Management System (LMS).
Why it matters Ensures that new hires are compliant and equipped for their roles. Analyzing this helps measure the Timely Training Assignment Rate and identify gaps. Where to get Captured from Oracle Learning Cloud or a third-party LMS integration. The event is the creation of a training assignment linked to the employee ID. Capture Logged when a learning administrator or automated rule assigns a course to the employee. Event type explicit

Recommended Optional

Extraction Guides

How to get your data from Oracle HCM Onboarding

Steps

Access BI Publisher: Log in to your Oracle HCM Cloud instance. Use the Navigator menu to go to Tools > Reports and Analytics. Click the Browse Catalog button to open the Business Intelligence Publisher interface.
Create a New Data Model: Inside the catalog, click the New dropdown menu and select Data Model. This will open the data model editor.
Define a SQL Query Dataset: In the Diagram view of the data model editor, click the + icon and select SQL Query. A dialog box will appear.
Configure the Dataset: Name the dataset (e.g., DS_EmployeeLifecycle), select ApplicationDB_HCM as the Data Source, and set the Type of SQL to Standard SQL.
Enter the SQL Query: Copy the complete SQL provided in the query section of this document and paste it into the SQL Query text area. This query is designed to extract all required lifecycle events.
Define Parameters: The query uses parameters :p_start_date and :p_end_date for filtering. Go to the Parameters section of the data model, click +, and create two parameters with these exact names. Set their data type to Date and configure them as mandatory.
Save the Data Model: Save the data model in a shared folder, giving it a descriptive name like Employee Lifecycle Event Log Data Model.
Create a New Report: Navigate back to the catalog, click New, and select Report. In the creation wizard, choose Use Data Model and select the data model you just saved.
Configure Report Layout: The wizard will guide you through layout settings. Choose a simple Table layout. Do not group any data. Ensure the output format is set to CSV by default. You can do this in the View a List layout editor by deselecting other output formats under the report properties.
Save and Run the Report: Save the report in the same folder as the data model. To run it, click View Report. You will be prompted to enter the start and end dates. The system will then generate and download the CSV event log file.
Schedule the Extraction (Optional): For continuous monitoring, schedule the report to run automatically. Find the saved report in the catalog, click More, and then Schedule. Configure the frequency, date parameters (e.g., using date functions), and delivery destination, such as a content server.

Configuration

Permissions: The user creating and running the report needs a role with BI Administrator or BI Author privileges, along with appropriate data access permissions to view HCM person, assignment, recruitment, and performance records.
Data Source: The data model must be configured to use the ApplicationDB_HCM data source, which provides direct access to the transactional tables.
Date Range Filtering: Using p_start_date and p_end_date parameters is critical for managing data volume. For the first extraction, consider a period of the last 12 to 24 months. For subsequent delta loads, schedule the report to run for the previous week or month.
Output Format: It is mandatory to configure the report's default output format as CSV. This ensures a clean, tabular file that can be directly ingested by process mining tools without further transformation.
Performance Considerations: For organizations with tens of thousands of employees, this comprehensive query can take significant time to run. Schedule large extractions during off-peak hours to avoid impacting system performance for other users.

a Sample Query sql

WITH EmployeeData AS (
  SELECT
    papf.person_id,
    papf.person_number,
    paam.assignment_id,
    paam.effective_start_date,
    paam.effective_end_date,
    ppnf.full_name,
    haouf.name AS department_name,
    pjfl.name AS job_role,
    paam.recruitment_activity_id,
    paam.original_date_of_hire,
    pdp.reason_code AS termination_reason
  FROM
    per_all_people_f papf
    JOIN per_person_names_f ppnf ON papf.person_id = ppnf.person_id AND ppnf.name_type = 'GLOBAL'
    JOIN per_all_assignments_m paam ON papf.person_id = paam.person_id
    LEFT JOIN hr_all_organization_units_f_vl haouf ON paam.organization_id = haouf.organization_id
    LEFT JOIN per_jobs_f_vl pjfl ON paam.job_id = pjfl.job_id
    LEFT JOIN per_periods_of_service ppos ON paam.period_of_service_id = ppos.period_of_service_id
    LEFT JOIN per_termination_details_f ptdf ON ppos.period_of_service_id = ptdf.period_of_service_id
    LEFT JOIN per_reasons_vl pdp ON ptdf.termination_reason_id = pdp.reason_id
  WHERE
    paam.assignment_type IN ('E', 'C', 'N') AND paam.primary_flag = 'Y'
    AND SYSDATE BETWEEN papf.effective_start_date AND papf.effective_end_date
    AND SYSDATE BETWEEN ppnf.effective_start_date AND ppnf.effective_end_date
    AND SYSDATE BETWEEN paam.effective_start_date AND paam.effective_end_date
    AND SYSDATE BETWEEN haouf.effective_start_date(+) AND haouf.effective_end_date(+)
    AND SYSDATE BETWEEN pjfl.effective_start_date(+) AND pjfl.effective_end_date(+)
)
-- 1. Offer Accepted
SELECT
  ed.person_number AS "EmployeeId",
  'Offer Accepted' AS "ActivityName",
  CAST(offers.accepted_on AS TIMESTAMP) AS "EventTimestamp",
  NULL AS "EventEndTime",
  offers.last_updated_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  subs.source_type AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM irc_offers offers
JOIN irc_submissions subs ON offers.submission_id = subs.submission_id
JOIN EmployeeData ed ON subs.person_id = ed.person_id
WHERE offers.offer_status = 'EXTENDED' AND offers.offer_resolution = 'ACCEPTED'
AND offers.accepted_on BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 2. Background Check Initiated & 3. Background Check Completed
SELECT
  ed.person_number AS "EmployeeId",
  CASE WHEN task.task_status = 'COMPLETED' THEN 'Background Check Completed' ELSE 'Background Check Initiated' END AS "ActivityName",
  CASE WHEN task.task_status = 'COMPLETED' THEN CAST(task.actual_completion_date AS TIMESTAMP) ELSE CAST(task.creation_date AS TIMESTAMP) END AS "EventTimestamp",
  CAST(task.actual_completion_date AS TIMESTAMP) AS "EventEndTime",
  task.last_updated_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM per_allocated_tasks task
JOIN per_checklist_definitions_vl chk ON task.checklist_id = chk.checklist_id
JOIN EmployeeData ed ON task.person_id = ed.person_id
WHERE chk.category = 'ONBOARDING' AND chk.name LIKE '%Background Check%'
AND (task.creation_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD') OR task.actual_completion_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD'))

UNION ALL

-- 4. Onboarding Journey Initiated
SELECT
  ed.person_number AS "EmployeeId",
  'Onboarding Journey Initiated' AS "ActivityName",
  CAST(journey.creation_date AS TIMESTAMP) AS "EventTimestamp",
  NULL AS "EventEndTime",
  journey.created_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM per_allocated_checklists journey
JOIN per_checklist_definitions_vl chk ON journey.checklist_id = chk.checklist_id
JOIN EmployeeData ed ON journey.person_id = ed.person_id
WHERE chk.category IN ('ONBOARDING', '[Your Onboarding Journey Category]')
AND journey.creation_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 5. New Hire Data Submitted & 6. I-9 Verification Completed
SELECT
  ed.person_number AS "EmployeeId",
  CASE WHEN chk.name LIKE '%I-9%' THEN 'I-9 Verification Completed' ELSE 'New Hire Data Submitted' END AS "ActivityName",
  CAST(task.actual_completion_date AS TIMESTAMP) AS "EventTimestamp",
  NULL AS "EventEndTime",
  task.last_updated_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM per_allocated_tasks task
JOIN per_checklist_definitions_vl chk ON task.checklist_id = chk.checklist_id
JOIN EmployeeData ed ON task.person_id = ed.person_id
WHERE chk.category = 'ONBOARDING' AND task.task_status = 'COMPLETED'
AND (chk.name LIKE '%Personal Data%' OR chk.name LIKE '%I-9%')
AND task.actual_completion_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 7. Employee Onboarded
SELECT
  ed.person_number AS "EmployeeId",
  'Employee Onboarded' AS "ActivityName",
  CAST(pao.actual_date AS TIMESTAMP) AS "EventTimestamp",
  NULL AS "EventEndTime",
  pao.last_updated_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM per_action_occurrences pao
JOIN per_actions_vl pav ON pao.action_id = pav.action_id
JOIN EmployeeData ed ON pao.person_id = ed.person_id
WHERE pav.action_code = 'HIRE'
AND pao.actual_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 8. Payroll Setup Completed
SELECT 
  ed.person_number AS "EmployeeId",
  'Payroll Setup Completed' AS "ActivityName",
  CAST(pra.effective_date AS TIMESTAMP) AS "EventTimestamp",
  NULL AS "EventEndTime",
  pra.created_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM pay_payroll_rel_actions pra
JOIN pay_payroll_assignments ppa ON pra.payroll_assignment_id = ppa.payroll_assignment_id
JOIN EmployeeData ed ON ppa.person_id = ed.person_id
WHERE pra.action_status = 'C' -- Completed
AND pra.action_type = 'H' -- Hire or Rehire
AND pra.effective_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 9. Training Assigned
SELECT
  ed.person_number AS "EmployeeId",
  'Training Assigned' AS "ActivityName",
  CAST(we.creation_date AS TIMESTAMP) AS "EventTimestamp",
  CAST(we.completed_date AS TIMESTAMP) AS "EventEndTime",
  we.created_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM wlf_enrollments we
JOIN EmployeeData ed ON we.person_id = ed.person_id
WHERE we.creation_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 10. Performance Review Conducted
SELECT
  ed.person_number AS "EmployeeId",
  'Performance Review Conducted' AS "ActivityName",
  CAST(he.evaluation_complete_date AS TIMESTAMP) AS "EventTimestamp",
  NULL AS "EventEndTime",
  he.last_updated_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM hra_evaluations he
JOIN EmployeeData ed ON he.person_id = ed.person_id
WHERE he.evaluation_status = 'COMPLETED'
AND he.evaluation_complete_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 11. Role Change Initiated & 12. Promotion Approved
SELECT 
  ed.person_number AS "EmployeeId",
  CASE WHEN pao.action_reason = 'PROMOTION' THEN 'Promotion Approved' ELSE 'Role Change Initiated' END AS "ActivityName",
  CAST(pao.actual_date AS TIMESTAMP) AS "EventTimestamp",
  NULL AS "EventEndTime",
  pao.last_updated_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  NULL AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM per_action_occurrences pao
JOIN per_actions_vl pav ON pao.action_id = pav.action_id
JOIN EmployeeData ed ON pao.person_id = ed.person_id
WHERE pav.action_code IN ('PROMOTION', 'TRANSFER', 'ASG_CHANGE')
AND pao.status = 'A' -- Approved
AND pao.actual_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 13. Termination Initiated
SELECT
  ed.person_number AS "EmployeeId",
  'Termination Initiated' AS "ActivityName",
  CAST(ptdf.creation_date AS TIMESTAMP) AS "EventTimestamp",
  CAST(ptdf.actual_termination_date AS TIMESTAMP) AS "EventEndTime",
  ptdf.created_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  ed.termination_reason AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM per_termination_details_f ptdf
JOIN per_periods_of_service ppos ON ptdf.period_of_service_id = ppos.period_of_service_id
JOIN EmployeeData ed ON ppos.person_id = ed.person_id
WHERE ptdf.creation_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

UNION ALL

-- 14. Exit Interview Conducted & 15. Offboarding Tasks Completed
SELECT
  ed.person_number AS "EmployeeId",
  CASE WHEN chk.name LIKE '%Exit Interview%' THEN 'Exit Interview Conducted' ELSE 'Offboarding Tasks Completed' END AS "ActivityName",
  CAST(task.actual_completion_date AS TIMESTAMP) AS "EventTimestamp",
  NULL AS "EventEndTime",
  task.last_updated_by AS "UserId",
  ed.department_name AS "DepartmentName",
  ed.job_role AS "JobRole",
  NULL AS "RecruitmentSource",
  ed.termination_reason AS "TerminationReason",
  ed.original_date_of_hire AS "HireDate"
FROM per_allocated_tasks task
JOIN per_checklist_definitions_vl chk ON task.checklist_id = chk.checklist_id
JOIN EmployeeData ed ON task.person_id = ed.person_id
WHERE chk.category = 'OFFBOARDING' AND task.task_status = 'COMPLETED'
AND task.actual_completion_date BETWEEN TO_DATE(:p_start_date, 'YYYY-MM-DD') AND TO_DATE(:p_end_date, 'YYYY-MM-DD')

Steps

Access BI Cloud Connector (BICC): Log into your Oracle Cloud Applications instance and navigate to the BI Cloud Connector console. This is typically found under the Tools menu, labeled as 'BI Cloud Connector'.
Configure External Storage: Before creating an extract, define the target storage location for your data files. Navigate to 'Configure External Storage' and set up a connection to either Oracle Universal Content Management (UCM) or an OCI Object Storage bucket. This is where BICC will deposit the extracted CSV files.
Enable the HCM Offering: In the BICC console, select 'Manage Offerings'. Ensure that the 'Human Capital Management' offering is enabled. This makes all HCM-related Public View Objects (PVOs) available for extraction.
Identify and Select PVOs: Navigate to 'Manage Extract Objects'. Use the search functionality to find and select the PVOs required for the Hire to Retire process. Key PVOs include objects related to Recruiting (Offers), Onboarding (Journeys, Tasks), Core HR (Person, Assignments, Work Relationship), Talent (Performance), and Learning (Training). Refer to the query section for a detailed list.
Select Columns for Each PVO: For each selected PVO, click on the 'Configure' icon. Deselect all columns by default and then explicitly choose the specific columns needed for the event log, such as Person ID, relevant dates (Hire Date, Task Completion Date, Offer Accepted Date), and attributes like Department, Job Role, and Status. This minimizes extract size and complexity.
Create a New Extract Schedule: Go to 'Manage Extract Schedules' and create a new schedule. Give it a descriptive name like 'ProcessMining_HireToRetire_Extract'.
Add PVOs to the Schedule: Add the PVOs you configured in step 5 to your new schedule. For each PVO, you can set advanced filters.
Apply Date Filters: To manage data volume, apply a filter on the LastUpdatedDate column available in most PVOs. This enables incremental extracts, which is crucial for ongoing monitoring. For the initial run, you may need a broader filter or none at all to get historical data.
Schedule and Run the Job: Schedule the job to run automatically (e.g., daily) or launch it manually using the 'Start' button. You can monitor the job's progress in the 'Manage Extract Schedules' dashboard.
Retrieve Extracted Data: Once the job completes successfully, the data will be available as a set of compressed CSV files in the external storage location you configured in step 2. Download and decompress these files.
Transform and Merge Data into an Event Log: BICC produces one CSV file per PVO. Use a scripting language like Python with the pandas library or an ETL tool to process these files. For each file, read the data, rename columns to match the event log schema (EmployeeId, ActivityName, EventTimestamp), and create the ActivityName based on the file's context (e.g., all rows from the OfferPVO extract become 'Offer Accepted'). Union the processed data from all files into a single table.
Export Final Event Log: Save the final, unified table as a single CSV file. Ensure the headers match the required attributes and the timestamps are in a consistent format. This file is now ready for upload into the ProcessMind platform.

Configuration

Offerings: The 'Human Capital Management' offering must be enabled in BICC to access the necessary data objects.
Public View Objects (PVOs): You must carefully select a collection of PVOs to cover the entire employee lifecycle. Key objects include HcmTopModelAnalyticsGlobalAM.RecruitingAM.OfferPVO, HcmTopModelAnalyticsGlobalAM.OnboardingAM.ChecklistTaskPVO, HcmTopModelAnalyticsGlobalAM.CoreAM.WorkRelationshipPVO, HcmTopModelAnalyticsGlobalAM.CoreAM.AssignmentPVO, HcmTopModelAnalyticsGlobalAM.TalentManagementAM.PerformanceDocumentPVO, and HcmTopModelAnalyticsGlobalAM.CoreAM.ActionPVO.
Column Selection: To optimize performance and reduce file size, only select the specific columns required for the event log from each PVO. Avoid using the 'Select All' option.
Incremental Extracts: Use the LastUpdatedDate filter in your extract schedule to pull only new or changed records after the initial historical load. This is critical for performance and efficient daily updates.
Date Range: For the initial historical data load, consider extracting data for the last 6 to 12 months to build a meaningful process baseline. For subsequent incremental loads, the date range will be since the last successful run.
Prerequisites: Users configuring BICC extracts require a role with the necessary privileges, typically the 'BI Cloud Connector Administrator' (BICC_ADMIN) application role.

a Sample Query config

/*
This is a configuration plan for Oracle BI Cloud Connector (BICC).
It is not a single executable SQL script. Instead, it details which PVOs
and columns to select within the BICC user interface to generate the raw
data files needed for the Hire to Retire event log.
The post-processing script mentioned in the 'howto' section will use these
files to construct the final event log by mapping columns and assigning
the correct ActivityName.
*/

-- PVO 1: Offer Data
-- Purpose: Capture Offer Accepted events.
PVO_NAME: HcmTopModelAnalyticsGlobalAM.RecruitingAM.OfferPVO
COLUMNS:
  - PersonId (as EmployeeId)
  - OfferAcceptedDate (as EventTimestamp)
  - [RecruitmentSource] (as RecruitmentSource)
  - [DepartmentName] (as DepartmentName)
  - [JobRole] (as JobRole)
EVENT_LOG_MAPPING:
  - ActivityName: 'Offer Accepted'
  - Filter: OfferAcceptedDate IS NOT NULL AND OfferStatus = 'ORA_ACCEPTED'

-- PVO 2: Onboarding and Offboarding Tasks
-- Purpose: Capture multiple task-based events from checklists.
PVO_NAME: HcmTopModelAnalyticsGlobalAM.OnboardingAM.ChecklistTaskPVO
COLUMNS:
  - PersonId (as EmployeeId)
  - TaskName
  - TaskCreationDate
  - TaskCompletionDate
  - TaskPerformerPersonId (as UserId)
EVENT_LOG_MAPPING:
  - WHEN TaskName LIKE 'Background Check%' THEN ActivityName: 'Background Check Initiated', EventTimestamp: TaskCreationDate
  - WHEN TaskName LIKE 'Background Check%' AND TaskStatus = 'ORA_COMPLETED' THEN ActivityName: 'Background Check Completed', EventTimestamp: TaskCompletionDate
  - WHEN TaskName LIKE '%Personal Data%' AND TaskStatus = 'ORA_COMPLETED' THEN ActivityName: 'New Hire Data Submitted', EventTimestamp: TaskCompletionDate
  - WHEN TaskName LIKE '%I-9 Verification%' AND TaskStatus = 'ORA_COMPLETED' THEN ActivityName: 'I-9 Verification Completed', EventTimestamp: TaskCompletionDate
  - WHEN TaskName LIKE '%Payroll Setup%' AND TaskStatus = 'ORA_COMPLETED' THEN ActivityName: 'Payroll Setup Completed', EventTimestamp: TaskCompletionDate
  - WHEN TaskName LIKE '%Exit Interview%' AND TaskStatus = 'ORA_COMPLETED' THEN ActivityName: 'Exit Interview Conducted', EventTimestamp: TaskCompletionDate
  - WHEN [Category] = 'OFFBOARDING' AND TaskStatus = 'ORA_COMPLETED' THEN ActivityName: 'Offboarding Tasks Completed', EventTimestamp: TaskCompletionDate

-- PVO 3: Onboarding Journey Initiation
-- Purpose: Capture the start of the formal onboarding process.
PVO_NAME: HcmTopModelAnalyticsGlobalAM.OnboardingAM.JourneyPVO
COLUMNS:
  - PersonId (as EmployeeId)
  - CreationDate (as EventTimestamp)
  - AssignorPersonId (as UserId)
  - JourneyStatus
EVENT_LOG_MAPPING:
  - ActivityName: 'Onboarding Journey Initiated'
  - Filter: JourneyStatus IS NOT NULL

-- PVO 4: Core HR Work Relationship
-- Purpose: Capture hire and termination events.
PVO_NAME: HcmTopModelAnalyticsGlobalAM.CoreAM.WorkRelationshipPVO
COLUMNS:
  - PersonId (as EmployeeId)
  - DateStart (as HireDate, and as EventTimestamp for 'Employee Onboarded')
  - TerminationDate (as EventTimestamp for 'Termination Initiated')
  - [TerminationReason] (as TerminationReason)
EVENT_LOG_MAPPING:
  - ActivityName: 'Employee Onboarded', EventTimestamp: DateStart, Filter: DateStart IS NOT NULL
  - ActivityName: 'Termination Initiated', EventTimestamp: TerminationDate, Filter: TerminationDate IS NOT NULL

-- PVO 5: Learning Assignments
-- Purpose: Capture training assignment events.
PVO_NAME: HcmTopModelAnalyticsGlobalAM.LearningManagementAM.LearningAssignmentPVO
COLUMNS:
  - PersonId (as EmployeeId)
  - AssignmentCreationDate (as EventTimestamp)
  - AssignerId (as UserId)
  - LearningItemTitle
EVENT_LOG_MAPPING:
  - ActivityName: 'Training Assigned'

-- PVO 6: Performance Reviews
-- Purpose: Capture performance review completion.
PVO_NAME: HcmTopModelAnalyticsGlobalAM.TalentManagementAM.PerformanceDocumentPVO
COLUMNS:
  - WorkerPersonId (as EmployeeId)
  - CompletionDate (as EventTimestamp)
  - ManagerPersonId (as UserId)
  - DocumentStatus
EVENT_LOG_MAPPING:
  - ActivityName: 'Performance Review Conducted'
  - Filter: DocumentStatus = 'ORA_COMPLETED' AND CompletionDate IS NOT NULL

-- PVO 7: HR Actions
-- Purpose: Capture role changes and promotions.
PVO_NAME: HcmTopModelAnalyticsGlobalAM.CoreAM.ActionPVO
COLUMNS:
  - PersonId (as EmployeeId)
  - ActionCode
  - ActionName
  - ActionReasonCode
  - EffectiveDate (as EventTimestamp)
EVENT_LOG_MAPPING:
  - WHEN ActionCode IN ('PROMOTION', 'ORA_PROMOTION') THEN ActivityName: 'Promotion Approved', EventTimestamp: EffectiveDate
  - WHEN ActionCode IN ('TRANSFER', 'ORA_TRANSFER', 'ROLE_CHANGE') THEN ActivityName: 'Role Change Initiated', EventTimestamp: EffectiveDate

Steps

Prerequisites and Environment Setup: Ensure you have Python 3.6 or newer installed. Install the necessary libraries using pip: pip install requests pandas. This script will use the requests library to communicate with the Oracle HCM REST APIs and pandas to structure the data into an event log.
Oracle HCM Security Configuration: Create a dedicated integration user in Oracle HCM Cloud. Assign the user the Human Capital Management Integration Specialist role, which provides broad read-access to the required APIs. Note the username and password for use in the script.
Identify Your HCM Cloud API URL: Determine the base URL for your Oracle HCM Cloud instance. It typically follows the format https://[instance_name].fa.em2.oraclecloud.com. This URL is the foundation for all API endpoint calls.
Configure the Python Script: Copy the provided Python script into a file, for example, extract_hcm_data.py. Update the placeholder variables at the top of the script: HCM_BASE_URL, USERNAME, PASSWORD, START_DATE, and END_DATE. The date range determines the window of data to be extracted.
Understand API Endpoints: The script is pre-configured to call multiple REST API endpoints to gather data for the entire employee lifecycle. Key endpoints include /workers for core employee and assignment data, /recruitingCECandidateOffers for offer details, and /onboardingJourneys for onboarding and offboarding task status.
Execute the Extraction Script: Run the script from your command line using python extract_hcm_data.py. The script will authenticate, send requests to each endpoint, handle pagination to retrieve all records, and print progress updates to the console.
Process API Responses: For each API call, the script parses the JSON response. It iterates through the returned items (e.g., workers, tasks, offers) and extracts the specific fields needed for the event log.
Map Data to Activities: The script contains logic to map different data points to the standardized activity names required for process mining. For example, a worker's HireDate becomes the 'Employee Onboarded' activity, and an offer's AcceptedDate becomes the 'Offer Accepted' activity.
Structure the Event Log: The extracted and mapped data from all sources is collected into a single list of events. The pandas library is then used to convert this list into a structured DataFrame, ensuring all required and recommended columns are present.
Export the Final CSV: Once all data is processed, the script saves the DataFrame to a CSV file named hire_to_retire_event_log.csv. This file is formatted correctly for direct upload into the ProcessMind platform.

Configuration

Prerequisites: An Oracle HCM Cloud user with the Human Capital Management Integration Specialist role or equivalent API access is required. Python 3.6+ with requests and pandas libraries must be installed.
Authentication: The script uses Basic Authentication. Ensure the credentials provided are for a user with sufficient permissions across the HR, Recruiting, Onboarding, Learning, and Performance modules.
API Base URL: The HCM_BASE_URL variable must be set to your specific Oracle Cloud instance URL. This is the most critical configuration point.
Date Range: The START_DATE and END_DATE variables control the extraction window. For the initial run, a 3 to 6-month period is recommended to ensure a manageable data size and reasonable execution time. The format should be YYYY-MM-DD.
Pagination Limit: The script uses a limit of 100 records per API request to manage memory and avoid overwhelming the API. This value can be adjusted, but 100 is a safe default.
Field Selection: The script uses the fields query parameter in API calls to request only the necessary data attributes. This improves performance by reducing the size of the JSON payload returned from the server.
Performance: For environments with hundreds of thousands of employee records, the full extraction may take a significant amount of time. It is recommended to run the script during off-peak hours.

a Sample Query python

import requests
import pandas as pd
import os
from datetime import datetime

class=class="hl-string">"hl-comment"># --- Configuration Settings --- #
class=class="hl-string">"hl-comment"># Replace with your Oracle HCM Cloud instance URL
HCM_BASE_URL = class="hl-string">"https://[your_instance_name].fa.em2.oraclecloud.com"
class=class="hl-string">"hl-comment"># Replace with your integration user credentials
USERNAME = class="hl-string">"your_api_username"
PASSWORD = class="hl-string">"your_api_password"

class=class="hl-string">"hl-comment"># Set the date range for extraction (YYYY-MM-DD)
START_DATE = class="hl-string">"2023-01-01"
END_DATE = class="hl-string">"2023-12-31"

class=class="hl-string">"hl-comment"># --- End of Configuration --- #

class=class="hl-string">"hl-comment"># Global list to hold all event data
event_log = []

def get_paginated_data(endpoint, params={}):
    class="hl-string">"""Helper function to handle pagination for Oracle HCM REST API calls."""
    all_items = []
    url = fclass="hl-string">"{HCM_BASE_URL}{endpoint}"
    params.setdefault(class="hl-string">'limit', 100)
    offset = 0
    
    while True:
        params[class="hl-string">'offset'] = offset
        print(fclass="hl-string">"Fetching from {url} with offset {offset}...")
        try:
            response = requests.get(url, auth=(USERNAME, PASSWORD), params=params)
            response.raise_for_status() class=class="hl-string">"hl-comment"># Raise an exception for bad status codes
            data = response.json()
            items = data.get(class="hl-string">'items', [])
            all_items.extend(items)
            
            if not data.get(class="hl-string">'hasMore', False):
                break
            offset += len(items)
        except requests.exceptions.RequestException as e:
            print(fclass="hl-string">"Error fetching data from {endpoint}: {e}")
            break
            
    print(fclass="hl-string">"Fetched a total of {len(all_items)} items from {endpoint}.")
    return all_items

def extract_recruiting_and_onboarding_events():
    class="hl-string">"""Extracts events from Recruiting and Onboarding modules."""
    print(class="hl-string">"\n--- Starting Recruiting and Onboarding Extraction ---")
    class=class="hl-string">"hl-comment"># Fetch Offer Data
    offer_params = {
        class="hl-string">'q': fclass="hl-string">"AcceptedDate between '{START_DATE}' and '{END_DATE}'",
        class="hl-string">'fields': class="hl-string">'OfferId,AcceptedDate,CandidateNumber,assignments'
    }
    offers = get_paginated_data(class="hl-string">'/hcmRestApi/resources/11.13.18.05/recruitingCECandidateOffers', offer_params)
    for offer in offers:
        if offer.get(class="hl-string">'AcceptedDate'):
            event_log.append({
                class="hl-string">'EmployeeId': offer.get(class="hl-string">'CandidateNumber'), class=class="hl-string">"hl-comment"># Using CandidateNumber as early identifier
                class="hl-string">'ActivityName': class="hl-string">'Offer Accepted',
                class="hl-string">'EventTimestamp': offer[class="hl-string">'AcceptedDate'],
                class="hl-string">'EventEndTime': None,
                class="hl-string">'UserId': None, 
                class="hl-string">'DepartmentName': offer.get(class="hl-string">'assignments', [{}])[0].get(class="hl-string">'DepartmentName'),
                class="hl-string">'JobRole': offer.get(class="hl-string">'assignments', [{}])[0].get(class="hl-string">'JobName'),
                class="hl-string">'RecruitmentSource': offer.get(class="hl-string">'assignments', [{}])[0].get(class="hl-string">'RecruitingSource'),
                class="hl-string">'TerminationReason': None,
                class="hl-string">'HireDate': None
            })

    class=class="hl-string">"hl-comment"># Fetch Onboarding/Offboarding Journey Data
    journey_params = {
        class="hl-string">'q': fclass="hl-string">"CreationDate between '{START_DATE}' and '{END_DATE}'",
        class="hl-string">'fields': class="hl-string">'PersonNumber,JourneyType,CreationDate,CreatedBy,tasks;fields=TaskName,TaskStatus,ActualCompletionDate,LastUpdatedBy'
    }
    journeys = get_paginated_data(class="hl-string">'/hcmRestApi/resources/11.13.18.05/onboardingJourneys', journey_params)
    for journey in journeys:
        person_id = journey.get(class="hl-string">'PersonNumber')
        journey_type = journey.get(class="hl-string">'JourneyType')
        
        activity_name = class="hl-string">'Onboarding Journey Initiated' if journey_type == class="hl-string">'ONBOARD' else class="hl-string">'Offboarding Journey Initiated'
        
        event_log.append({
            class="hl-string">'EmployeeId': person_id,
            class="hl-string">'ActivityName': activity_name,
            class="hl-string">'EventTimestamp': journey[class="hl-string">'CreationDate'],
            class="hl-string">'EventEndTime': None,
            class="hl-string">'UserId': journey.get(class="hl-string">'CreatedBy'),
            class="hl-string">'DepartmentName': None,
            class="hl-string">'JobRole': None,
            class="hl-string">'RecruitmentSource': None,
            class="hl-string">'TerminationReason': None,
            class="hl-string">'HireDate': None
        })
        
        class=class="hl-string">"hl-comment"># Process tasks within the journey
        for task in journey.get(class="hl-string">'tasks', []):
            task_activity = None
            task_name_lower = task.get(class="hl-string">'TaskName', class="hl-string">'').lower()
            if class="hl-string">'background check' in task_name_lower:
                task_activity = class="hl-string">'Background Check Initiated' if task[class="hl-string">'TaskStatus'] != class="hl-string">'COMPLETED' else class="hl-string">'Background Check Completed'
            elif class="hl-string">'personal data' in task_name_lower and task[class="hl-string">'TaskStatus'] == class="hl-string">'COMPLETED':
                task_activity = class="hl-string">'New Hire Data Submitted'
            elif class="hl-string">'i-9' in task_name_lower and task[class="hl-string">'TaskStatus'] == class="hl-string">'COMPLETED':
                task_activity = class="hl-string">'I-9 Verification Completed'
            elif class="hl-string">'exit interview' in task_name_lower and task[class="hl-string">'TaskStatus'] == class="hl-string">'COMPLETED':
                task_activity = class="hl-string">'Exit Interview Conducted'
            
            if task_activity and task.get(class="hl-string">'ActualCompletionDate'):
                event_log.append({
                    class="hl-string">'EmployeeId': person_id,
                    class="hl-string">'ActivityName': task_activity,
                    class="hl-string">'EventTimestamp': task[class="hl-string">'ActualCompletionDate'],
                    class="hl-string">'EventEndTime': task[class="hl-string">'ActualCompletionDate'],
                    class="hl-string">'UserId': task.get(class="hl-string">'LastUpdatedBy'),
                    class="hl-string">'DepartmentName': None,
                    class="hl-string">'JobRole': None,
                    class="hl-string">'RecruitmentSource': None,
                    class="hl-string">'TerminationReason': None,
                    class="hl-string">'HireDate': None
                })
        
        class=class="hl-string">"hl-comment"># Offboarding Tasks Completed (approximated by last task completion)
        if journey_type == class="hl-string">'OFFBOARD':
            completed_tasks = [t for t in journey.get(class="hl-string">'tasks', []) if t.get(class="hl-string">'ActualCompletionDate')]
            if completed_tasks and all(t[class="hl-string">'TaskStatus'] == class="hl-string">'COMPLETED' for t in journey.get(class="hl-string">'tasks', [])):
                last_completion_date = max(t[class="hl-string">'ActualCompletionDate'] for t in completed_tasks)
                event_log.append({
                    class="hl-string">'EmployeeId': person_id,
                    class="hl-string">'ActivityName': class="hl-string">'Offboarding Tasks Completed',
                    class="hl-string">'EventTimestamp': last_completion_date,
                    class="hl-string">'EventEndTime': last_completion_date,
                    class="hl-string">'UserId': None,
                    class="hl-string">'DepartmentName': None, class="hl-string">'JobRole': None, class="hl-string">'RecruitmentSource': None, class="hl-string">'TerminationReason': None, class="hl-string">'HireDate': None
                })

def extract_worker_and_lifecycle_events():
    class="hl-string">"""Extracts core worker data and major lifecycle events like hire, promotion, termination."""
    print(class="hl-string">"\n--- Starting Worker and Lifecycle Extraction ---")
    worker_params = {
        class="hl-string">'q': fclass="hl-string">"(workRelationships.assignments.CreationDate between '{START_DATE}' and '{END_DATE}') or (workRelationships.TerminationDate between '{START_DATE}' and '{END_DATE}')",
        class="hl-string">'onlyData': class="hl-string">'true',
        class="hl-string">'fields': class="hl-string">'PersonNumber,workRelationships;fields=assignments;fields=CreationDate,LastUpdateDate,ActionCode,JobId,DepartmentId,BusinessUnitId,JobName,DepartmentName,EffectiveStartDate,assignmentsDFF,HireDate,TerminationDate,TerminationReason'
    }
    workers = get_paginated_data(class="hl-string">'/hcmRestApi/resources/11.13.18.05/workers', worker_params)
    for worker in workers:
        person_id = worker.get(class="hl-string">'PersonNumber')
        for rel in worker.get(class="hl-string">'workRelationships', []):
            hire_date = rel.get(class="hl-string">'HireDate')
            for assign in rel.get(class="hl-string">'assignments', []):
                if hire_date and hire_date.startswith(START_DATE[:4]): class=class="hl-string">"hl-comment"># Simple check for new hires
                    event_log.append({
                        class="hl-string">'EmployeeId': person_id, class="hl-string">'ActivityName': class="hl-string">'Employee Onboarded', class="hl-string">'EventTimestamp': hire_date,
                        class="hl-string">'EventEndTime': None, class="hl-string">'UserId': None, class="hl-string">'DepartmentName': assign.get(class="hl-string">'DepartmentName'),
                        class="hl-string">'JobRole': assign.get(class="hl-string">'JobName'), class="hl-string">'RecruitmentSource': None, class="hl-string">'TerminationReason': None, class="hl-string">'HireDate': hire_date
                    })
                
                action = assign.get(class="hl-string">'ActionCode')
                if action in (class="hl-string">'PROMOTION', class="hl-string">'ASG_CHANGE_PROMOTION'):
                    event_log.append({
                        class="hl-string">'EmployeeId': person_id, class="hl-string">'ActivityName': class="hl-string">'Promotion Approved', class="hl-string">'EventTimestamp': assign.get(class="hl-string">'EffectiveStartDate'),
                        class="hl-string">'EventEndTime': None, class="hl-string">'UserId': None, class="hl-string">'DepartmentName': assign.get(class="hl-string">'DepartmentName'), 
                        class="hl-string">'JobRole': assign.get(class="hl-string">'JobName'), class="hl-string">'RecruitmentSource': None, class="hl-string">'TerminationReason': None, class="hl-string">'HireDate': hire_date
                    })
                elif action in (class="hl-string">'TRANSFER', class="hl-string">'GLB_TRANSFER', class="hl-string">'POS_CHANGE', class="hl-string">'ASG_CHANGE'):
                    event_log.append({
                        class="hl-string">'EmployeeId': person_id, class="hl-string">'ActivityName': class="hl-string">'Role Change Initiated', class="hl-string">'EventTimestamp': assign.get(class="hl-string">'EffectiveStartDate'),
                        class="hl-string">'EventEndTime': None, class="hl-string">'UserId': None, class="hl-string">'DepartmentName': assign.get(class="hl-string">'DepartmentName'),
                        class="hl-string">'JobRole': assign.get(class="hl-string">'JobName'), class="hl-string">'RecruitmentSource': None, class="hl-string">'TerminationReason': None, class="hl-string">'HireDate': hire_date
                    })
            
            if rel.get(class="hl-string">'TerminationDate'):
                event_log.append({
                    class="hl-string">'EmployeeId': person_id, class="hl-string">'ActivityName': class="hl-string">'Termination Initiated', class="hl-string">'EventTimestamp': rel[class="hl-string">'TerminationDate'],
                    class="hl-string">'EventEndTime': None, class="hl-string">'UserId': None, class="hl-string">'DepartmentName': rel.get(class="hl-string">'assignments', [{}])[0].get(class="hl-string">'DepartmentName'),
                    class="hl-string">'JobRole': rel.get(class="hl-string">'assignments', [{}])[0].get(class="hl-string">'JobName'), class="hl-string">'RecruitmentSource': None,
                    class="hl-string">'TerminationReason': rel.get(class="hl-string">'TerminationReason'), class="hl-string">'HireDate': hire_date
                })

def extract_other_hcm_events():
    class="hl-string">"""Extracts events from other modules like Performance, Learning, and Payroll."""
    print(class="hl-string">"\n--- Starting Ancillary HCM Event Extraction ---")
    class=class="hl-string">"hl-comment"># Performance Reviews
    perf_params = {class="hl-string">'q': fclass="hl-string">"ReviewPeriodEndDate between '{START_DATE}' and '{END_DATE}' and DocumentStatus='COMPLETED'", class="hl-string">'fields': class="hl-string">'PersonNumber,OverallRating,ReviewPeriodEndDate,ManagerPersonNumber'}
    reviews = get_paginated_data(class="hl-string">'/hcmRestApi/resources/11.13.18.05/performanceDocuments', perf_params)
    for review in reviews:
        event_log.append({
            class="hl-string">'EmployeeId': review.get(class="hl-string">'PersonNumber'), class="hl-string">'ActivityName': class="hl-string">'Performance Review Conducted', class="hl-string">'EventTimestamp': review.get(class="hl-string">'ReviewPeriodEndDate'),
            class="hl-string">'EventEndTime': review.get(class="hl-string">'ReviewPeriodEndDate'), class="hl-string">'UserId': review.get(class="hl-string">'ManagerPersonNumber'),
            class="hl-string">'DepartmentName': None, class="hl-string">'JobRole': None, class="hl-string">'RecruitmentSource': None, class="hl-string">'TerminationReason': None, class="hl-string">'HireDate': None
        })

    class=class="hl-string">"hl-comment"># Learning Assignments
    learn_params = {class="hl-string">'q': fclass="hl-string">"AssignedOn between '{START_DATE}' and '{END_DATE}'", class="hl-string">'fields': class="hl-string">'LearnerPersonNumber,AssignedOn,LearningItemName'}
    learnings = get_paginated_data(class="hl-string">'/learningRestApi/resources/latest/learnerLearningRecords', learn_params)
    for item in learnings:
        event_log.append({
            class="hl-string">'EmployeeId': item.get(class="hl-string">'LearnerPersonNumber'), class="hl-string">'ActivityName': class="hl-string">'Training Assigned', class="hl-string">'EventTimestamp': item.get(class="hl-string">'AssignedOn'),
            class="hl-string">'EventEndTime': None, class="hl-string">'UserId': None,
            class="hl-string">'DepartmentName': None, class="hl-string">'JobRole': None, class="hl-string">'RecruitmentSource': None, class="hl-string">'TerminationReason': None, class="hl-string">'HireDate': None
        })

    class=class="hl-string">"hl-comment"># Payroll Setup (Approximation)
    payroll_params = {class="hl-string">'q': fclass="hl-string">"CreationDate between '{START_DATE}' and '{END_DATE}'", class="hl-string">'fields': class="hl-string">'PersonNumber,CreationDate'}
    pay_records = get_paginated_data(class="hl-string">'/hcmRestApi/resources/11.13.18.05/personalPaymentMethods', payroll_params)
    for record in pay_records:
        event_log.append({
            class="hl-string">'EmployeeId': record.get(class="hl-string">'PersonNumber'), class="hl-string">'ActivityName': class="hl-string">'Payroll Setup Completed', class="hl-string">'EventTimestamp': record.get(class="hl-string">'CreationDate'),
            class="hl-string">'EventEndTime': None, class="hl-string">'UserId': None,
            class="hl-string">'DepartmentName': None, class="hl-string">'JobRole': None, class="hl-string">'RecruitmentSource': None, class="hl-string">'TerminationReason': None, class="hl-string">'HireDate': None
        })

if __name__ == class="hl-string">"__main__":
    print(class="hl-string">"Starting Hire to Retire data extraction from Oracle HCM Cloud...")
    
    class=class="hl-string">"hl-comment"># Execute extraction functions
    extract_recruiting_and_onboarding_events()
    extract_worker_and_lifecycle_events()
    extract_other_hcm_events()
    
    if not event_log:
        print(class="hl-string">"No events found for the given criteria. Exiting.")
    else:
        class=class="hl-string">"hl-comment"># Create DataFrame and perform final transformations
        df = pd.DataFrame(event_log)
        
        class=class="hl-string">"hl-comment"># Convert timestamps to consistent format
        df[class="hl-string">'EventTimestamp'] = pd.to_datetime(df[class="hl-string">'EventTimestamp'], errors=class="hl-string">'coerce').dt.strftime(class="hl-string">'%Y-%m-%d %H:%M:%S')
        df[class="hl-string">'EventEndTime'] = pd.to_datetime(df[class="hl-string">'EventEndTime'], errors=class="hl-string">'coerce').dt.strftime(class="hl-string">'%Y-%m-%d %H:%M:%S')
        df.dropna(subset=[class="hl-string">'EmployeeId', class="hl-string">'ActivityName', class="hl-string">'EventTimestamp'], inplace=True)
        
        class=class="hl-string">"hl-comment"># Fill missing employee attributes by forward/backward filling within each employee's history
        df = df.sort_values(by=[class="hl-string">'EmployeeId', class="hl-string">'EventTimestamp'])
        df[class="hl-string">'DepartmentName'] = df.groupby(class="hl-string">'EmployeeId')[class="hl-string">'DepartmentName'].fillna(method=class="hl-string">'ffill').fillna(method=class="hl-string">'bfill')
        df[class="hl-string">'JobRole'] = df.groupby(class="hl-string">'EmployeeId')[class="hl-string">'JobRole'].fillna(method=class="hl-string">'ffill').fillna(method=class="hl-string">'bfill')
        df[class="hl-string">'HireDate'] = df.groupby(class="hl-string">'EmployeeId')[class="hl-string">'HireDate'].fillna(method=class="hl-string">'ffill').fillna(method=class="hl-string">'bfill')
        
        class=class="hl-string">"hl-comment"># Define final column order
        final_columns = [
            class="hl-string">'EmployeeId', class="hl-string">'ActivityName', class="hl-string">'EventTimestamp', class="hl-string">'EventEndTime', class="hl-string">'UserId',
            class="hl-string">'DepartmentName', class="hl-string">'JobRole', class="hl-string">'RecruitmentSource', class="hl-string">'TerminationReason', class="hl-string">'HireDate'
        ]
        df = df[final_columns]

        class=class="hl-string">"hl-comment"># Save to CSV
        output_filename = class="hl-string">'hire_to_retire_event_log.csv'
        df.to_csv(output_filename, index=False)
        print(fclass="hl-string">"\nExtraction complete. Event log saved to '{output_filename}'. Total events: {len(df)}")

Data Template: Hire to Retire - Employee Lifecycle

Your Hire to Retire - Employee Lifecycle Data Template

Hire to Retire - Employee Lifecycle Attributes

Hire to Retire - Employee Lifecycle Activities

Extraction Guides

Oracle HCM BI Publisher Report Data Extraction

Steps

Configuration

a Sample Query sql

Oracle BI Cloud Connector (BICC) Bulk Data Extract

Steps

Configuration

a Sample Query config

Python Script Extraction via Oracle HCM REST APIs

Steps

Configuration

a Sample Query python

Ready to Get Started?

Start Optimizing Your Hire to Retire Lifecycle Today