Oracle ERP Testing Tool > Test Library > HCM > Core HR > Hire-to-Retire

Syntra Standard Oracle Test Library

Oracle Fusion Convert Pending Worker Test Cases

Validate conversion of an eligible pending worker into an active worker and employment relationship in Oracle Fusion HCM, using valid legal employer, hire date, job, position, department and manager information, and confirm the resulting active worker record is correctly established.

Test ID	ORCL.HCM.COREHR.WORKER.CONVERT.PENDING
Application	Oracle Fusion Cloud HCM
Product	Human Capital Management
Module	Core HR
Process	Hire-to-Retire
Business Flow	Employee Lifecycle
Scenario Type	Positive / Functional
Test Usage	Functional Testing / Regression Testing / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 11 business-readable test steps; SyntraFlow's automation executes approximately 30 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates that Oracle Fusion HCM can convert an eligible pending worker into an active worker and employment relationship using valid hire and assignment information.

The scenario should confirm that:

the eligible pending worker record is correctly identified and available for conversion
required hire information — legal employer, hire date, job, position and department — is captured and accepted
Oracle Fusion converts the pending worker into an active worker and employment record
the resulting active worker retains an appropriate link back to the originating pending worker reference where applicable
the worker's assignment, job and position are correctly established at conversion
the worker's employment status correctly reflects an active worker following conversion

This scenario validates conversion of a pending worker that already exists in Oracle Fusion HCM. Creating a new worker directly is covered by the separate Hire Employee and Hire Contingent Worker scenarios within the same Hire-to-Retire lifecycle.

When to Use This Test

Functional testing of pending-worker conversion for a new Oracle Fusion HCM implementation
Regression testing of worker conversion after an Oracle quarterly update affecting Core HR
UAT sign-off for recruiting-to-HCM handoff processes before go-live
Baseline case referenced by downstream Change Assignment, Promote and Transfer scenarios within the same worker lifecycle

Where This Test Fits in the Hire-to-Retire Process

Pending Worker Exists

→

Locate Pending Worker

→

Review Pending Data

→

Complete Hire Information

→

Assign Job / Position / Manager

→

Submit Conversion

→

Verify Active Worker

This test covers converting an existing eligible pending worker into an active worker and confirming the resulting employment record. It follows the Hire stage for workers who entered Oracle Fusion HCM as pending records — for example, through a recruiting handoff — and precedes subsequent lifecycle events such as Change Assignment, Promote and Transfer.

Preconditions

An eligible pending worker record exists in Oracle Fusion HCM, for example created through a recruiting handoff or a pre-hire process.
The pending worker's required base data is present and available for review prior to conversion.
A valid legal employer is configured and available for the conversion.
A valid, active job and position are available for assignment.
A valid department and, where required, work location are available for assignment.
The test user has the appropriate HR role and access needed to convert a pending worker.
The intended hire/conversion date falls within a valid, open period for the legal employer.

Exact preconditions, eligibility rules and field requirements vary by Oracle Fusion implementation, legal employer, worker type and legislative configuration.

Sample Test Data

Pending Worker Reference	${PENDING_WORKER_REFERENCE}
Legal Employer	${LEGAL_EMPLOYER}
Hire Date	${HIRE_DATE}
Job	${JOB}
Position	${POSITION}
Department	${DEPARTMENT}
Location	${LOCATION}
Manager	${MANAGER}
Salary Basis	${SALARY_BASIS}
Salary Amount	${SALARY_AMOUNT}

Sample values are illustrative placeholders. Replace them with valid legal employer, job, position and compensation data from the target Oracle Fusion TEST/UAT environment; not every field applies to every worker type or legislative configuration.

Test Steps

11 business-readable steps. SyntraFlow's automation executes ~30 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Sign In to Oracle Fusion Sign in to Oracle Fusion Cloud with a user account that has Core HR pending-worker conversion access.	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to Workforce Management Navigate to the My Client Groups / Workforce work area used for managing pending workers.	The workforce management work area opens successfully.
3	Open Pending Workers Open the task used to view and manage pending worker records.	A list of pending worker records is displayed.
4	Locate Eligible Pending Worker Locate the eligible pending worker to be converted. ${PENDING_WORKER_REFERENCE}	The pending worker record is found and marked as eligible for conversion.
5	Review Pending Worker Data Review the existing pending worker data prior to conversion.	The pending worker's available data is displayed for review without error.
6	Complete Hire Information Complete or confirm the required hire information, including legal employer and hire date. ${LEGAL_EMPLOYER} / ${HIRE_DATE}	The legal employer and hire date are accepted without validation errors.
7	Select Job, Position and Department Select the job, position, department and, where applicable, work location for the resulting active worker. ${JOB} / ${POSITION} / ${DEPARTMENT} / ${LOCATION} This single business step replaces multiple technical actions such as searching for and selecting each field individually.	The selected job, position, department and location are accepted for the conversion.
8	Assign Manager Assign the reporting manager for the resulting active worker. ${MANAGER}	The selected manager is accepted and associated with the worker's assignment.
9	Review Conversion Details Review the completed conversion details, including compensation where required. ${SALARY_BASIS} / ${SALARY_AMOUNT}	The conversion details are displayed correctly and ready for submission.
10	Submit Conversion Submit the pending worker for conversion into an active worker.	Oracle Fusion processes the conversion and returns a confirmation.
11	Verify Active Worker Status and RecordBusiness assertion Retrieve the resulting worker record and confirm the pending worker was converted into an active worker. This is the main business assertion for the scenario — the test does not stop merely because the submit action succeeded; the resulting active worker must be retrievable with the correct details.	The worker record is retrievable, the employment status reflects an active worker, and the job, position, department and manager match the entered conversion data.

Expected Results

The eligible pending worker is converted successfully into an active worker using valid hire and assignment data.
The correct legal employer, hire date, job, position and department are applied.
The reporting manager is correctly associated with the worker's assignment.
The pending-worker status is updated to reflect completed conversion.
The employment status correctly reflects an active worker following conversion.
The resulting active worker record is retrievable for subsequent Hire-to-Retire lifecycle scenarios such as Change Assignment, Promote and Transfer.

Key Validation Checkpoints

Pending-worker status updated to reflect conversion.
Active worker record created correctly.
Assignment created for the active worker.
Worker number or reference preserved appropriately where applicable.
Correct job and position applied.
Correct hire date applied.
Correct employment status following conversion.

Core Business Scenario

Convert Pending Worker

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core Convert Pending Worker scenario. Jarvis AI can extend this scenario by generating additional positive and negative worker-conversion variations across legal employers, jobs, positions, departments and eligibility conditions using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate conversion test for every legal employer, job, position and eligibility combination. Jarvis uses the standard Convert Pending Worker scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Open Pending Workers

The pending worker list is opened within the workforce management work area.

Select Conversion Details

Legal employer, hire date, job, position, department and manager are selected for the pending worker.

Convert Worker

The conversion is submitted and processed in Oracle Fusion HCM.

Confirm Active Worker

Employment status and the resulting worker record are confirmed.

Available for Lifecycle Events

The converted worker is available for Change Assignment, Promote, Transfer and related scenarios.

Regression Pack

Selected worker-conversion variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Rather than maintaining a separate test for every legal employer, job, position, department and eligibility combination, SyntraFlow maintains one core Convert Pending Worker scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Convert Pending Worker business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to HCM Core HR Hire-to-Retire.

Positive Scenarios

Convert pending employee
Different legal employers
Different jobs
Different positions
Different departments
Different locations
Different hire dates
Compensation completion where required
Convert after recruiting handoff where applicable

Negative Scenarios

Pending worker not eligible for conversion
Required conversion data incomplete
Invalid position
Inactive job
Invalid legal employer
Invalid hire date
Duplicate conversion attempt
Missing manager
Security/access restriction
Legislative-data issue

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion configuration, worker types, legislative rules and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely reflects the legal employers, jobs, positions and eligibility rules configured in a real Oracle Fusion HCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct worker-conversion scenarios relevant to the customer's actual implementation.

Standard Library Definition

Pending Worker Reference   ${PENDING_WORKER_REFERENCE}
Legal Employer              ${LEGAL_EMPLOYER}
Hire Date                   ${HIRE_DATE}
Job                          ${JOB}
Position                    ${POSITION}
Department                  ${DEPARTMENT}
Location                    ${LOCATION}
Manager                     ${MANAGER}
Salary Basis                 ${SALARY_BASIS}
Salary Amount                ${SALARY_AMOUNT}

DataVault

Legal Employers
  Configured legal employers and legislative rules
Jobs / Positions
  Active jobs and positions available for assignment
Departments / Locations
  Configured departments and work locations
Managers
  Active managers available for assignment
Pending Workers
  Eligible and ineligible pending worker records
Compensation
  Salary basis and ranges per job/position

Jarvis AI Generates

Scenario 01 — Standard Pending Worker Conversion
Scenario 02 — Alternate Legal Employer
Scenario 03 — Alternate Job/Position
Scenario 04 — Conversion After Recruiting Handoff
Scenario 05 — Pending Worker Not Eligible
Scenario 06 — Missing Manager
...

Pending worker and active worker test data can include sensitive HCM data categories such as personal identifiers, compensation and legislative information. Where DataVault is connected, this data remains within the customer's controlled SyntraFlow environment and access model, with masking available through Syntra DataVault and DataVault Data Masking for non-production use.

Example Test Variations

Representative examples of Convert Pending Worker scenarios Jarvis can generate from this business scenario, spanning legal employer, job/position and eligibility conditions. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
VAR-001	Basic Pending Worker Conversion	Positive	Standard eligible pending worker converted with complete data	Syntra Ready
VAR-002	Different Legal Employer	Positive/Legal Employer	Conversion performed under an alternate legal employer	Syntra Ready
VAR-003	Different Job	Positive/Job/Position	Alternate job assigned during conversion	Syntra Ready
VAR-004	Different Position	Positive/Job/Position	Alternate position assigned during conversion	Syntra Ready
VAR-005	Different Department	Positive	Alternate department assigned to the resulting worker	Syntra Ready
VAR-006	Different Location	Positive	Alternate work location assigned during conversion	Syntra Ready
VAR-007	Different Hire Date	Positive	Alternate valid hire/conversion date used	Syntra Ready
VAR-008	Compensation Completed at Conversion	Positive	Salary basis and amount confirmed where required by the process	Syntra Ready
VAR-009	Convert After Recruiting Handoff	Positive/Eligibility	Pending worker originating from a recruiting handoff is converted	Syntra Ready
VAR-010	Manager Assigned at Conversion	Positive	Reporting manager confirmed as part of the conversion	Syntra Ready
VAR-011	Pending Worker Not Eligible	Negative/Eligibility	Pending worker record is not eligible for conversion	Syntra Ready
VAR-012	Required Conversion Data Incomplete	Negative	Mandatory hire field left incomplete	Syntra Ready
VAR-013	Invalid Position	Negative/Job/Position	Position invalid or unavailable for the selected job	Syntra Ready
VAR-014	Inactive Job	Negative/Job/Position	Job is inactive or not open for assignment	Syntra Ready
VAR-015	Invalid Legal Employer	Negative/Legal Employer	Legal employer reference invalid or inaccessible to the user	Syntra Ready
VAR-016	Invalid Hire Date	Negative	Hire/conversion date falls outside a valid or open range	Syntra Ready
VAR-017	Duplicate Conversion Attempt	Negative/Eligibility	Worker already converted is submitted for conversion again	Syntra Ready
VAR-018	Missing Manager	Negative	Required reporting manager field left blank	Syntra Ready
VAR-019	Security/Access Restriction	Negative	User lacks pending-worker conversion access	Syntra Ready
VAR-020	Legislative Data Issue	Negative/Eligibility	Required legislative information incomplete for the legal employer	Syntra Ready

Positive and Negative Conversion Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion HCM successfully converts an eligible pending worker into an active worker when the legal employer, job, position, department and hire date are all valid.

Eligible Pending Worker + Valid Legal Employer/Job/Position → Worker Converted Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around eligibility, position/job configuration, legal employer and security during conversion.

Pending Worker Not Eligible → Expected Eligibility Validation
Inactive Job → Expected Configuration Validation
Invalid Legal Employer → Expected Legal Employer Validation
Missing Manager → Expected Mandatory Field Validation
Unauthorized User → Expected Security Validation

A negative scenario passes when Oracle correctly enforces the expected business rule, security rule or validation.

Scenario	Oracle Outcome	Test Result
Valid hire	Worker created	PASS
Inactive position	Position validation	PASS
Unauthorized user	Access prevented	PASS
Invalid effective date	Date validation	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated worker-conversion scenarios and group them into reusable execution packs.

HCM Convert Pending Worker Regression Pack

Basic Pending Worker Conversion
Different Legal Employer
Different Job
Different Position
Different Department
Convert After Recruiting Handoff
Compensation Completed at Conversion
Pending Worker Not Eligible
Invalid Legal Employer
Missing Manager
Duplicate Conversion Attempt
Security/Access Restriction

Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute selected worker-conversion scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected worker-conversion scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	HCM Convert Pending Worker Regression Pack
Schedule	Nightly Regression
Tests	20 scenarios
Execution	Batch Mode
Start	10:00 PM
Environment	Oracle Fusion TEST
Status	Scheduled

Illustrative example — not a live schedule.

Review Results Across the Entire Test Pack

Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.

Illustrative example data — not actual production metrics.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

Hire-to-Retire Lifecycle

Not every worker follows every lifecycle event. Available actions depend on worker type, legal employer, legislative requirements, position/job setup, security and customer configuration. Stages link to the corresponding test scenario family.

Hire→

Convert / Activate

→Change Assignment→Promote→Transfer→Global Transfer→Terminate

DataVault HCM Persona

Rather than combining unrelated field values at random, DataVault groups worker-conversion test data into coherent personas so that legal employer, department, job, position, location and payroll dimensions stay consistent with a realistic worker profile.

Persona: US Recruiting Handoff — New Employee

Legal Employer	US Legal Employer
Country	United States
Worker Type	Employee
Department	Sales
Job	Account Executive
Position	Account Executive II
Location	Chicago
Manager	Active Manager
Salary Basis	Annual
Payroll	US Biweekly

This persona represents a pending worker originating from a US recruiting handoff who is converted into an active Sales employee. Grouping dimensions this way keeps generated scenarios internally consistent — for example, a US legal employer paired with a compatible payroll and salary basis — rather than combining values that would not occur together in a real Oracle Fusion HCM environment.

Security & Persona Variations

Jarvis can generate persona-based variations of this scenario to help confirm that pending-worker conversion honors the customer's Oracle Fusion security configuration. SyntraFlow does not assume a single universal Oracle role or security model applies across all customers.

Persona	Action	Expected	Syntra Result
HR Specialist	Convert Pending Worker	Allowed	PASS
Unauthorized User	Attempts Conversion	Access prevented	PASS
HR Manager (Restricted Business Unit)	Attempts Conversion Outside Assigned Area	Access prevented	PASS
Recruiter (View-Only Access)	Attempts Conversion	Access prevented	PASS

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the Convert Pending Worker scenario, available DataVault test data and expected business outcomes to generate additional worker-conversion coverage for the customer's environment.

Generate

Positive and negative variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business outcomes.

How SyntraFlow Automates This Test

The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.

Standard Library — Convert Pending Worker, 11 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Select Job, Position and Department

May internally include

Open Job Search → Select Job → Select Position → Select Department → Select Location → Confirm

Business Step

Submit Conversion

May internally include

Validate Form → Submit Conversion Request → Poll Confirmation → Capture Resulting Worker Reference

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.

Step	Action Status	Business Validation
Submit Conversion	Pass	—
Complete Hire Information	Pass	—
Verify Active Worker Status and Record	Pass	Pass

Related Hire-to-Retire Tests

Converting a pending worker is one entry point into the same Hire-to-Retire worker lifecycle — explore the related hire and assignment scenarios below.

Hire Employee Hire Contingent Worker Change Assignment

Turn This Standard Test into Your Oracle HCM Worker Conversion Regression Suite

Start with the Syntra Standard Convert Pending Worker test, use DataVault to provide environment-specific legal employer, job and position data, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Hire-to-Retire Test Library

Use This Oracle Fusion Test Case

Download Test Case

Excel, CSV or JSON export.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

Oracle ERP Testing Tool Test Library HCM Test Library Core HR Hire-to-Retire Syntra DataVault DataVault Data Masking

Frequently Asked Questions

What does "pending worker" mean in Oracle Fusion?

A pending worker is a worker record that exists in Oracle Fusion HCM ahead of a full hire — for example, created through a recruiting handoff or pre-hire process — but has not yet been converted into an active worker with a complete employment relationship.

How does Convert Pending Worker differ from Hire Employee?

Hire Employee creates a new worker record directly. Convert Pending Worker starts from a pending worker record that already exists in Oracle Fusion HCM and completes the required hire and assignment information to establish it as an active worker.

What happens if required conversion data is incomplete?

Jarvis can generate negative variations, such as missing manager or incomplete legislative data, that are designed to confirm Oracle Fusion correctly prevents conversion or raises validation until the required information is provided.

How does security testing work for this scenario?

Jarvis can generate persona-based variations that confirm an authorized HR role can convert an eligible pending worker while an unauthorized user is correctly prevented from doing so, consistent with the customer's Oracle Fusion security configuration. SyntraFlow does not assume a single universal Oracle role or security model applies across all customers.

Does SyntraFlow convert real employee records when running this test?

No. SyntraFlow automates the Oracle Fusion HCM user interface within a test or UAT environment using placeholder test data; it is a test automation product and does not create or modify real employment relationships for real people.