Oracle ERP Testing Tool > Test Library > HCM > Recruiting

Syntra Standard Oracle Test Library

Oracle Fusion Candidate-to-Worker Test Cases

Validate the conversion of an accepted candidate into a Core HR worker record — background checks, onboarding, data transfer, new-hire execution and Recruiting-to-Core-HR/Payroll integration — a comprehensive catalog of 40 individual Candidate-to-Worker test scenarios, the sixth and final family page of the Recruiting library and the cross-module bridge into Core HR, using masked, synthetic candidate, national-identifier and compensation data only.

Test ID	ORCL.HCM.RECRUIT.C2W
Application	Oracle Fusion Cloud
Product	HCM
Module	Recruiting
Process	Candidate-to-Worker
Business Flow	Recruit-to-Hire
Scenario Type	Positive / Negative / Boundary / Security / Integration
Test Usage	Functional Testing / Regression Testing / UAT Sign-Off
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard

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

Test Objective

This test validates the conversion of an accepted candidate into a Core HR worker record — background checks, onboarding, data transfer from the candidate profile to the person and assignment record, new-hire execution, and integration correctness between Recruiting and Core HR/Payroll — using masked, synthetic candidate, national-identifier and compensation test data only.

The scenario should confirm that:

background checks and onboarding tasks correctly gate the candidate-to-worker conversion before it is permitted to proceed
candidate profile data correctly transfers into the new Core HR person record, and offer compensation, position, grade, work location and manager data correctly transfer into the new assignment record
national identifier and compensation data used during conversion testing are masked, synthetic DataVault values rather than real or realistic identifiers or salary figures
the new hire action correctly executes on the agreed hire date, and the source requisition and headcount are correctly updated once the hire completes
the new hire correctly appears in Core HR Person Management, Workforce Structures and Time and Labor as an eligible worker, and remains correctly synchronized with Payroll
deliberately invalid conversions — missing background check clearance, no accepted offer, incomplete onboarding, duplicate worker, date conflicts, withdrawn candidates, invalid positions, exceeded headcount, integration failures and unauthorized access — are correctly rejected, flagged or surfaced rather than silently accepted

A negative or boundary Candidate-to-Worker scenario passes when Oracle correctly enforces the expected data, eligibility, integration or security rule; this test does not attempt to certify a specific Oracle application defect. As the cross-module bridge between Recruiting and Core HR, every candidate, worker, national-identifier and compensation value referenced in this catalog is a masked, synthetic ${PLACEHOLDER} token generated through Syntra DataVault — never a real or realistic identifier or salary figure — consistent with the same masked-only standard applied to the HCM Core HR Manage National Identifiers test. This page catalogs 40 individual Candidate-to-Worker scenarios — tied with Job Requisition as the largest catalog in the Recruiting library — as a single comprehensive reference rather than as separate indexable pages.

When to Use This Test

Functional testing of candidate-to-worker conversion for a new Oracle Fusion HCM Recruiting and Core HR implementation
Regression testing of background-check gating, onboarding and data-transfer logic after an Oracle quarterly update affecting Recruiting or Core HR
UAT sign-off validating the full recruit-to-hire handoff, including Recruiting-to-Payroll integration
Cross-module integration testing between Recruiting and Core HR Person Management, Workforce Structures and Time and Labor
Comprehensive scenario coverage for teams standardizing on a single Candidate-to-Worker regression pack instead of dozens of near-duplicate scripts, using masked DataVault test data throughout

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

Job Requisition

→

Candidate Application

→

Candidate Screening

→

Job Offer

→

Candidate-to-Worker

Candidate-to-Worker is the sixth and final scenario family in the Recruiting cluster, and the cross-module bridge into Core HR Hire-to-Retire. It exercises background checks, onboarding, data transfer, new-hire execution and Recruiting-to-Core-HR/Payroll integration, together with negative, boundary, security and integration validation, converting the output of Job Offer into a Core HR person and assignment record. Exact background-check providers, onboarding task lists and integration touchpoints depend entirely on customer-specific Oracle Fusion configuration — no universal configuration is assumed.

← Previous Stage

Job Offer

Next Stage →

Hire Employee (Core HR)

Preconditions

Oracle Fusion Recruiting and Core HR access is available to the test user.
An accepted-offer ${CANDIDATE} for ${REQUISITION} is available, with a representative ${POSITION} and ${GRADE} configured.
A masked, synthetic ${NATIONAL_IDENTIFIER} test value is available through Syntra DataVault; no real or realistic national identifier is used.
A masked, synthetic compensation value for the accepted offer is available; no real or realistic salary figure is used.
${WORK_LOCATION} and ${MANAGER} are configured and available for assignment transfer testing.
A background check provider or simulated ${BACKGROUND_CHECK_STATUS} outcome is configured for testing cleared and flagged results.
A user without the required Recruiting or Core HR security access is available for security testing, and a withdrawn ${CANDIDATE} plus an inactive ${POSITION} are available for negative testing.

Exact background-check provider, onboarding task list and integration touchpoints may vary by Oracle Fusion implementation and customer-specific configuration; all candidate, worker, national-identifier and compensation values used in testing are masked, synthetic DataVault data — never real or realistic identifiers or salary figures.

Sample Test Data

Candidate	${CANDIDATE}
Requisition	${REQUISITION}
Worker	${WORKER}
Position	${POSITION}
Grade	${GRADE}
Work Location	${WORK_LOCATION}
Manager	${MANAGER}
National Identifier	${NATIONAL_IDENTIFIER} (masked)
Hire Date	${HIRE_DATE}
Background Check Status	${BACKGROUND_CHECK_STATUS}

Sample values are illustrative ${PLACEHOLDER} tokens generated through Syntra DataVault, not real candidate, worker, national-identifier or compensation data. National identifier and compensation values are masked, synthetic data only, modeled on the same standard applied to the HCM Core HR Manage National Identifiers test — see /datavault/data-masking/. Replace tokens with valid masked test data from the target Oracle Fusion TEST or UAT environment; not every field applies to every scenario.

Test Steps

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

#	User Action	Expected Result
1	Sign In to Oracle Fusion HCM Sign in to Oracle Fusion Cloud with a user account that has Recruiting and Core HR access.	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to the Accepted-Offer Candidate Navigate to the Recruiting work area and open the accepted-offer candidate record for ${CANDIDATE} on ${REQUISITION}. ${CANDIDATE} / ${REQUISITION}	The candidate's accepted-offer record opens successfully with the conversion action available.
3	Initiate Background Check and Confirm ClearanceBusiness assertion Initiate the background check for ${CANDIDATE} and confirm the result reaches a cleared status before proceeding. ${BACKGROUND_CHECK_STATUS} A flagged or not-yet-cleared background check correctly blocking conversion is a passing outcome for negative and gating scenarios, not a failure.	The background check is recorded correctly, and conversion is gated until the cleared status is reached.
4	Assign and Complete Onboarding Tasks Assign the configured onboarding task list to ${CANDIDATE} and complete the required onboarding forms and work eligibility verification.	Onboarding tasks and forms are recorded as complete, and work eligibility verification is confirmed.
5	Initiate the Candidate-to-Worker Conversion Initiate the candidate-to-worker conversion action for ${CANDIDATE} once the background check and onboarding are complete. ${CANDIDATE} / ${WORKER}	The conversion flow opens correctly with the candidate's profile ready for transfer, or is correctly blocked if a required gate has not been met.
6	Verify Data Transfer to the New Person and Assignment RecordBusiness assertion Verify that candidate profile data, ${POSITION}, ${GRADE}, ${WORK_LOCATION}, ${MANAGER} and the offer's compensation data correctly transfer to the new person and assignment record for ${WORKER}, and that ${NATIONAL_IDENTIFIER} is captured using masked test data only. ${POSITION} / ${GRADE} / ${WORK_LOCATION} / ${MANAGER} / ${NATIONAL_IDENTIFIER}	All transferred fields on the new person and assignment record match the source candidate and offer data accurately.
7	Execute the New Hire Action Execute the new hire action for ${WORKER} on ${HIRE_DATE}. ${HIRE_DATE}	The hire executes correctly and the worker record is activated with the correct hire date.
8	Verify Requisition and Headcount UpdateBusiness assertion Confirm that ${REQUISITION} is marked filled and that headcount tracked against the approved budget is correctly decremented after the hire. ${REQUISITION}	Requisition status and headcount tracking accurately reflect the completed hire.
9	Verify New Hire Appears Across Core HR, Workforce Structures and Time and LaborBusiness assertion Confirm that ${WORKER} correctly appears in Core HR Person Management, the relevant Workforce Structures, and Time and Labor as an eligible worker, and that Recruiting-to-Core-HR and Recruiting-to-Payroll integration completed without error. ${WORKER} This is the main business assertion for the scenario across the full catalog of 40 Candidate-to-Worker variations, and validates the cross-module integration between Recruiting and Core HR/Payroll.	The new hire is correctly visible and synchronized across Core HR, Workforce Structures, Time and Labor and Payroll.

Expected Results

Background checks and onboarding tasks correctly gated the candidate-to-worker conversion before it was permitted to proceed.
Candidate profile data, position, grade, work location, manager and offer compensation correctly transferred from the candidate/offer record to the new person and assignment record.
National identifier and compensation data captured during conversion were masked, synthetic DataVault values, never real or realistic identifiers or salary figures.
The new hire action executed correctly on the agreed hire date, and the source requisition and headcount were correctly updated.
The new hire correctly appeared in Core HR Person Management, Workforce Structures and Time and Labor as an eligible worker, and remained correctly synchronized with Payroll.
Deliberately invalid conversions raised the expected data, eligibility, integration or security validation rather than being silently accepted.

Key Validation Checkpoints

Candidate profile data correctly transfers to the new person and assignment record.
Compensation, position, grade and location correctly carried over from the accepted offer.
Background check and onboarding completion correctly gate the hire action.
Requisition and headcount correctly updated after hire.
New hire correctly appears in Core HR, Workforce Structures and Time and Labor as an eligible worker.
Unauthorized conversion attempts correctly blocked.

Core Business Scenario

Candidate-to-Worker

Scenario Catalog

40 Scenarios

Business Steps

Test Data

DataVault-Driven (Masked)

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 Candidate-to-Worker scenario — the cross-module bridge between Recruiting and Core HR. Jarvis AI can extend this scenario by systematically generating additional Positive, Negative, Boundary, Security and Integration variations using masked, synthetic candidate, national-identifier and compensation data available through Syntra DataVault.

Teams do not need to manually construct dozens of near-identical conversion scenarios to cover every background-check outcome, data-transfer field and integration path. Jarvis uses the standard conversion scenario as the foundation and generates coverage relevant to the customer's environment — without creating additional indexable pages, and without ever using real candidate, worker or national-identifier data.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Candidate-to-Worker scenario and automation logic.

Customer DataVault

Provides masked, synthetic candidate, worker, national-identifier and compensation test data required for variation generation — Candidate, Requisition, Worker, Position, Grade, Work Location, Manager, National Identifier, Hire Date and Background Check Status.

Jarvis AI

Analyses the standard conversion scenario together with available masked test data and generates Positive, Negative, Boundary, Security and Integration variations.

Positive + Negative + Boundary + Security + Integration Variations

Correctly gated, transferred and executed conversions and deliberately invalid, boundary, unauthorized or misconfigured conditions.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

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

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exception classification.

Rather than maintaining a separate test for every possible background-check outcome, data-transfer field and integration path, SyntraFlow maintains one core Candidate-to-Worker scenario and allows Jarvis AI to generate Positive, Negative, Boundary, Security and Integration variations using masked, synthetic candidate, national-identifier and compensation test data. These variations do not create additional SEO pages and never use real candidate, worker or national-identifier data.

AI-Generated Test Variations

The same Candidate-to-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 Recruiting.

Positive Scenarios

Background check and onboarding completion prior to conversion
Candidate-profile-to-person-record data transfer
Compensation, position, location and manager assignment transfer from the accepted offer
New-hire execution on the agreed hire date
Internal-candidate conversion to a new assignment and rehire of a former worker
Recruiting-to-Core-HR and Recruiting-to-Payroll integration validation
Post-hire data-integrity checks across the person and assignment record

Negative Scenarios

Conversion attempted without a cleared background check
Conversion attempted without an accepted offer
Missing required onboarding data
Duplicate worker record created
Hire date conflict with an existing assignment
Conversion attempted for a withdrawn candidate
Integration failure between Recruiting and Core HR or Payroll

These are representative examples only. Background-check providers, onboarding task lists, integration touchpoints and validation messages can depend on the customer's Oracle Fusion configuration — not every Oracle configuration behaves identically. All example values are masked, synthetic ${PLACEHOLDER} tokens, never real candidate, worker or national-identifier data.

Generated Using Your DataVault Test Data

Generic test data rarely represents every background-check outcome, position, grade and integration combination in a real Oracle Fusion HCM Recruiting-to-Core-HR environment. Where connected, Jarvis can use masked, synthetic test data available through Syntra DataVault — Candidate, Worker, Position, Grade, Work Location, Manager, National Identifier, Hire Date and Background Check Status — to construct realistic Candidate-to-Worker variations relevant to the customer's actual implementation, without ever using real candidate or national-identifier data.

Standard Library Definition

Candidate               ${CANDIDATE}
Requisition              ${REQUISITION}
Worker                   ${WORKER}
Position                 ${POSITION}
Grade                    ${GRADE}
Work Location            ${WORK_LOCATION}
Manager                  ${MANAGER}
National Identifier      ${NATIONAL_IDENTIFIER} (masked)
Hire Date                ${HIRE_DATE}
Background Check Status  ${BACKGROUND_CHECK_STATUS}

DataVault

Candidates and Offers
  Accepted-offer candidates with valid and invalid background-check and onboarding states
Positions and Grades
  Positions with valid and invalid grade/compensation combinations for transfer testing
National Identifiers
  Masked, synthetic identifier values only — never real or realistic identifiers
Compensation
  Masked, synthetic compensation values only — never real or realistic salary figures
Security
  Roles with and without conversion and national-identifier view authorization

Jarvis AI Generates

Scenario 01 — Initiate Candidate-to-Worker Conversion
Scenario 02 — Background Check Cleared
Scenario 03 — Candidate Profile Data Transfers to Person Record
Scenario 04 — Conversion Attempted Without a Cleared Background Check
Scenario 05 — Recruiting-to-Core-HR Integration Validation
Scenario 06 — Unauthorized User Initiates Conversion
...

Candidate-to-Worker testing touches the most sensitive data in the Recruiting cluster — national identifiers and compensation figures carried from the accepted offer into the new Core HR person and assignment record. Every candidate, worker, national-identifier and compensation value used across this page's 40 scenarios is a masked, synthetic value generated through Syntra DataVault — never a real or realistic identifier or salary figure — modeled on the same masked-only standard applied to the HCM Core HR Manage National Identifiers test. See /datavault/data-masking/ for how DataVault masking and privacy controls protect this data end to end.

Example Test Variations

A comprehensive catalog of 40 individual Candidate-to-Worker test scenarios — the cross-module bridge between Recruiting and Core HR — spanning background checks, onboarding, data transfer, new-hire execution, Recruiting-to-Core-HR/Payroll integration and negative/security testing, all using masked, synthetic candidate and identifier data. Filter or search below.

ID	Variation	Type	Key Difference	Execution
REC-C2W-001	Initiate Candidate-to-Worker Conversion	Positive	Validate that the candidate-to-worker conversion process can be initiated for ${CANDIDATE} after ${REQUISITION} reaches an accepted-offer status; Oracle Fusion correctly opens the conversion flow for the accepted candidate.	SyntraFlow Ready
REC-C2W-002	Background Check Initiated	Positive	Validate that a background check can be initiated for ${CANDIDATE} as part of the conversion process; Oracle Fusion correctly records the background check as initiated with status ${BACKGROUND_CHECK_STATUS}.	SyntraFlow Ready
REC-C2W-003	Background Check Cleared	Positive	Validate that a background check for ${CANDIDATE} completing with a cleared result is correctly recorded; Oracle Fusion updates ${BACKGROUND_CHECK_STATUS} to cleared and allows the conversion to proceed.	SyntraFlow Ready
REC-C2W-004	Background Check Flagged	Positive	Validate that a background check for ${CANDIDATE} completing with a flagged result is correctly recorded; Oracle Fusion updates ${BACKGROUND_CHECK_STATUS} to flagged and surfaces the flagged outcome for review before conversion can proceed.	SyntraFlow Ready
REC-C2W-005	Pre-Employment Screening Completed	Positive	Validate that pre-employment screening tasks for ${CANDIDATE} can be completed ahead of conversion; Oracle Fusion correctly records the completed screening status.	SyntraFlow Ready
REC-C2W-006	Onboarding Task Assignment	Positive	Validate that onboarding tasks can be assigned to ${CANDIDATE} once the offer is accepted; Oracle Fusion correctly assigns the configured onboarding task list to the new hire.	SyntraFlow Ready
REC-C2W-007	New Hire Completes Onboarding Forms	Positive	Validate that ${CANDIDATE} can complete the required onboarding forms prior to conversion; Oracle Fusion correctly records each completed onboarding form.	SyntraFlow Ready
REC-C2W-008	Work Eligibility Verification Completed	Positive	Validate that work eligibility verification for ${CANDIDATE} is completed prior to conversion; Oracle Fusion correctly records the verified work eligibility status.	SyntraFlow Ready
REC-C2W-009	Candidate Profile Data Transfers to Person Record	Positive	Validate that ${CANDIDATE} profile data correctly transfers into a new Core HR person record for ${WORKER} during conversion; Oracle Fusion creates the person record with the candidate's profile data carried over accurately.	SyntraFlow Ready
REC-C2W-010	Offer Compensation Data Transfers to Assignment	Positive	Validate that the accepted offer's ${COMPENSATION} data correctly transfers to the new assignment record for ${WORKER}; Oracle Fusion carries the compensation data from the offer to the assignment without discrepancy.	SyntraFlow Ready
REC-C2W-011	Position and Grade Transfer to Assignment	Positive	Validate that ${POSITION} and ${GRADE} from the accepted offer correctly transfer to the new assignment record for ${WORKER}; Oracle Fusion records the position and grade on the assignment accurately.	SyntraFlow Ready
REC-C2W-012	Work Location Transfer to Assignment	Positive	Validate that ${WORK_LOCATION} from the accepted offer correctly transfers to the new assignment record for ${WORKER}; Oracle Fusion records the work location on the assignment accurately.	SyntraFlow Ready
REC-C2W-013	Manager Assignment Transfer	Positive	Validate that ${MANAGER} designated on the accepted offer correctly transfers to the new assignment record for ${WORKER}; Oracle Fusion records the reporting manager on the assignment accurately.	SyntraFlow Ready
REC-C2W-014	National Identifier Captured Using Masked Test Data	Positive	Validate that a national identifier can be captured for ${WORKER} during conversion using masked, synthetic ${NATIONAL_IDENTIFIER} test data only; Oracle Fusion correctly records the identifier field without exposing or requiring any real identifier value in testing.	SyntraFlow Ready
REC-C2W-015	Work Eligibility Data Captured	Positive	Validate that verified work eligibility data for ${CANDIDATE} is correctly captured on the new person record for ${WORKER} during conversion; Oracle Fusion records the work eligibility outcome accurately.	SyntraFlow Ready
REC-C2W-016	Execute New Hire Action	Positive	Validate that the new hire action can be executed for ${WORKER} on ${HIRE_DATE} once background check, onboarding and data transfer are complete; Oracle Fusion correctly executes the hire and activates the worker record.	SyntraFlow Ready
REC-C2W-017	Convert Internal Candidate to New Assignment	Positive	Validate that an existing internal worker applying as ${CANDIDATE} can be converted to a new assignment for ${POSITION} rather than a new person record; Oracle Fusion correctly creates a new assignment against the existing worker record for ${WORKER}.	SyntraFlow Ready
REC-C2W-018	Rehire a Former Worker	Positive	Validate that a former worker returning as ${CANDIDATE} can be rehired into ${WORKER} on ${HIRE_DATE}; Oracle Fusion correctly reactivates or recreates the worker record according to the customer's configured rehire rule.	SyntraFlow Ready
REC-C2W-019	Hire Date Matches Offer Start Date	Positive	Validate that the hire date recorded for ${WORKER} correctly matches the start date accepted on the offer for ${CANDIDATE}; Oracle Fusion records ${HIRE_DATE} consistently between the offer and the new assignment.	SyntraFlow Ready
REC-C2W-020	Requisition Marked Filled After Hire	Positive	Validate that ${REQUISITION} is correctly marked as filled once ${CANDIDATE} is converted to ${WORKER}; Oracle Fusion updates the requisition status to reflect the completed hire.	SyntraFlow Ready
REC-C2W-021	Headcount Decremented After Hire	Positive	Validate that headcount tracked against the approved budget for ${REQUISITION} is correctly decremented once ${CANDIDATE} is hired as ${WORKER}; Oracle Fusion updates the tracked headcount accurately.	SyntraFlow Ready
REC-C2W-022	Recruiting-to-Core-HR Integration Validation	Positive/Integration	Validate that Recruiting and Core HR remain correctly integrated during conversion; Oracle Fusion correctly synchronizes the new person and assignment record for ${WORKER} between the Recruiting and Core HR modules.	SyntraFlow Ready
REC-C2W-023	Recruiting-to-Payroll Integration Validation	Positive/Integration	Validate that Recruiting and Payroll remain correctly integrated during conversion; Oracle Fusion correctly makes ${WORKER}'s assignment and ${COMPENSATION} data available to Payroll for processing.	SyntraFlow Ready
REC-C2W-024	New Hire Appears in Core HR Person Management	Positive/Integration	Validate that ${WORKER} correctly appears in Core HR Person Management following conversion; Oracle Fusion correctly surfaces the new person record in the Person Management work area.	SyntraFlow Ready
REC-C2W-025	New Hire Assignment Appears in Workforce Structures	Positive/Integration	Validate that ${WORKER}'s new assignment correctly appears within the relevant Workforce Structures — including ${POSITION} and organization hierarchy — following conversion; Oracle Fusion correctly reflects the assignment in workforce structure reporting.	SyntraFlow Ready
REC-C2W-026	Conversion Attempted Without a Cleared Background Check	Negative	Validate that attempting to convert ${CANDIDATE} to ${WORKER} while ${BACKGROUND_CHECK_STATUS} has not reached cleared is handled correctly; Oracle Fusion blocks the conversion and raises the expected gating validation.	SyntraFlow Ready
REC-C2W-027	Conversion Attempted Without an Accepted Offer	Negative	Validate that attempting to initiate conversion for ${CANDIDATE} without an accepted offer on ${REQUISITION} is handled correctly; Oracle Fusion prevents the conversion and raises the expected validation.	SyntraFlow Ready
REC-C2W-028	Missing Required Onboarding Data	Negative	Validate that attempting conversion for ${CANDIDATE} with required onboarding data or forms incomplete is handled correctly; Oracle Fusion raises the expected data validation rather than converting the incomplete record.	SyntraFlow Ready
REC-C2W-029	Duplicate Worker Record Created	Negative	Validate that a duplicate worker record is not silently created for ${CANDIDATE} during conversion when a matching worker record for ${WORKER} may already exist; Oracle Fusion raises the expected duplicate validation or requires explicit resolution.	SyntraFlow Ready
REC-C2W-030	Hire Date Conflict with an Existing Assignment	Negative	Validate that setting ${HIRE_DATE} for ${WORKER} in conflict with an existing active assignment is handled correctly; Oracle Fusion raises the expected date-conflict validation rather than creating an overlapping assignment.	SyntraFlow Ready
REC-C2W-031	Conversion Attempted for a Withdrawn Candidate	Negative	Validate that attempting to convert ${CANDIDATE} after the candidate has withdrawn from ${REQUISITION} is handled correctly; Oracle Fusion prevents the conversion and raises the expected validation.	SyntraFlow Ready
REC-C2W-032	Conversion to an Invalid Position	Negative	Validate that attempting to convert ${CANDIDATE} to ${WORKER} against an invalid or inactive ${POSITION} is handled correctly; Oracle Fusion raises the expected data validation rather than accepting the invalid position reference.	SyntraFlow Ready
REC-C2W-033	Conversion Exceeds Approved Headcount	Negative/Boundary	Validate that converting ${CANDIDATE} to ${WORKER} when doing so would exceed the approved headcount budget for ${REQUISITION} is handled correctly; Oracle Fusion raises the expected budget validation rather than silently exceeding the approved headcount.	SyntraFlow Ready
REC-C2W-034	Integration Failure Between Recruiting and Core HR	Negative/Integration	Validate that a failure synchronizing ${WORKER}'s new person and assignment record between Recruiting and Core HR is correctly surfaced rather than silently dropped; Oracle Fusion raises the expected integration exception for investigation.	SyntraFlow Ready
REC-C2W-035	Integration Failure Between Recruiting and Payroll	Negative/Integration	Validate that a failure making ${WORKER}'s assignment and ${COMPENSATION} data available to Payroll is correctly surfaced rather than silently dropped; Oracle Fusion raises the expected integration exception for investigation.	SyntraFlow Ready
REC-C2W-036	Unauthorized User Initiates Conversion	Negative/Security	Validate that a user without the required Recruiting or Core HR security access attempting to initiate conversion for ${CANDIDATE} is blocked; Oracle Fusion raises the expected security validation and prevents the unauthorized conversion.	SyntraFlow Ready
REC-C2W-037	New Hire Person Record Data Integrity Check	Positive	Validate that the completed person record for ${WORKER} accurately reflects the source candidate, national identifier and work eligibility data used during conversion; Oracle Fusion maintains data integrity between the candidate profile and the new person record.	SyntraFlow Ready
REC-C2W-038	New Hire Assignment Data Integrity Check	Positive	Validate that the completed assignment record for ${WORKER} accurately reflects ${POSITION}, ${GRADE}, ${WORK_LOCATION}, ${MANAGER} and ${COMPENSATION} carried over from the accepted offer; Oracle Fusion maintains data integrity on the new assignment record.	SyntraFlow Ready
REC-C2W-039	New Hire Appears in Time and Labor as an Eligible Worker	Positive	Validate that ${WORKER} correctly appears in Time and Labor as an eligible worker following conversion; Oracle Fusion correctly makes the new hire's assignment available for time reporting.	SyntraFlow Ready
REC-C2W-040	End-to-End Recruit-to-Hire Regression Validation	Positive	Validate the full Recruit-to-Hire path end to end for ${CANDIDATE} — requisition, application, screening, offer and conversion to ${WORKER} — as a single regression check; Oracle Fusion correctly completes and links every stage for the hired worker.	SyntraFlow Ready

Positive and Negative Candidate-to-Worker Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion HCM correctly converts an accepted candidate into a Core HR worker record when the background check, onboarding, data transfer and integration conditions are all valid.

Cleared Background Check + Completed Onboarding + Valid Offer → Candidate Converted to Worker with Data Correctly Transferred

Negative Testing

Jarvis can also generate scenarios that deliberately violate a gating, data or security rule to confirm Oracle correctly rejects, blocks or surfaces the condition rather than silently accepting it.

Background Check Not Cleared → Conversion Blocked
No Accepted Offer → Conversion Prevented
Missing Onboarding Data → Expected Data Validation Displayed
Duplicate Worker Record → Expected Duplicate Validation Displayed
Hire Date Conflict → Expected Date-Conflict Validation Displayed
Withdrawn Candidate → Conversion Prevented
Unauthorized User → Access Prevented

A negative recruiting scenario passes when Oracle correctly enforces the expected data, eligibility or security rule

Scenario	Oracle Outcome	Test Result
Valid requisition data	Requisition created	PASS
Missing required field	Validation occurs	PASS
Headcount exceeds budget	Validation occurs	PASS
Unauthorized user	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Candidate-to-Worker scenarios and group them into reusable execution packs.

HCM Candidate-to-Worker Regression Pack

Initiate Candidate-to-Worker Conversion
Background Check Cleared
Candidate Profile Data Transfers to Person Record
Offer Compensation Data Transfers to Assignment
Execute New Hire Action
Recruiting-to-Core-HR Integration Validation
Conversion Attempted Without a Cleared Background Check
Duplicate Worker Record Created
Integration Failure Between Recruiting and Payroll
Unauthorized User Initiates Conversion

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 Candidate-to-Worker scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected Candidate-to-Worker 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 Candidate-to-Worker Regression Pack
Schedule	Weekly Regression
Tests	40 scenarios
Execution	Batch Mode
Start	9: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

318

Business Assertions

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

DataVault HCM Persona

Rather than generating variations from disconnected field values, Jarvis can draw on a DataVault persona built for candidate-to-worker conversion — a pre-grouped, internally consistent set of fully synthetic candidate, national-identifier and compensation dimensions, so the recruit-to-hire conversion is testable end-to-end without touching real PII.

Persona: Standard New Hire Conversion

Candidate	${CANDIDATE}
Requisition	${REQUISITION}
Position	${POSITION}
Grade	${GRADE}
Work Location	${WORK_LOCATION}
Manager	${MANAGER}
National Identifier	${NATIONAL_IDENTIFIER} (masked)
Hire Date	${HIRE_DATE}
Background Check Status	${BACKGROUND_CHECK_STATUS}

DataVault personas group dependent recruiting and Core HR dimensions so Jarvis generates coherent, internally consistent Candidate-to-Worker scenarios using fully synthetic data, rather than arbitrary field combinations or any real candidate, worker or national-identifier value.

Security & Access Variations

Oracle Fusion HCM Recruiting and Core HR role and security configuration is customer-specific, so SyntraFlow can exercise candidate-to-worker conversion and national identifier access under different personas to confirm the customer's own access model behaves as expected, rather than assuming a universal Oracle security model.

Persona	Action	Expected	Syntra Result
HR Specialist	Execute New Hire Conversion	Allowed	PASS
Recruiter	View Conversion Status	Allowed	PASS
Unauthorized User	Attempts to Initiate Conversion	Access prevented	PASS
Unauthorized User	Attempts to View National Identifier Data	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 Candidate-to-Worker scenario, available masked DataVault test data and expected business outcomes to systematically generate Positive, Negative, Boundary, Security and Integration coverage for the customer's environment. These variations do not create additional SEO pages and never use real candidate, worker or national-identifier data.

Generate

Positive, Negative, Boundary, Security and Integration variations.

Parameterize

Use masked candidate, worker and national-identifier 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 — Candidate-to-Worker, 9 Business Steps

↓

DataVault — Masked HCM Persona-Specific Test Data

↓

Jarvis AI — Generate Positive/Negative/Boundary/Security/Integration 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

Verify Data Transfer to the New Person and Assignment Record

May internally include

Open New Person Record → Compare Candidate Profile Fields → Compare Offer Compensation/Position/Grade/Location → Compare Manager Assignment → Capture Field-Level Diff

Business Step

Execute the New Hire Action

May internally include

Validate Conversion Readiness → Click Hire → Confirm Hire Date → Capture Person/Assignment ID → Capture Status

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 a candidate was correctly converted to a worker, or that background checks, onboarding, data transfer and cross-module integration all completed correctly — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. Because this page aggregates 40 individual scenarios spanning background checks, onboarding, data transfer, new-hire execution and Recruiting-to-Core-HR/Payroll integration, evidence-based failure classification matters most here. When a step or business assertion fails, SyntraFlow's evidence is intended to help classify the likely cause into one of eight categories — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — rather than assuming a defect. For example: New hire did not appear in Core HR after conversion — Likely category: INTEGRATION_ERROR or APPLICATION_ERROR depending on evidence — Evidence: the person and assignment record either failed to synchronize between Recruiting and Core HR, or synchronized with an unexpected error — Recommended action: verify the Recruiting-to-Core-HR integration configuration and reattempt with supporting evidence before escalating. A failure should not be labeled as an Oracle application defect until data, configuration, security, automation and integration causes have been eliminated.

Step	Action Status	Business Validation
Assign and Complete Onboarding Tasks	Pass	—
Execute the New Hire Action	Pass	—
Verify New Hire Appears Across Core HR, Workforce Structures and Time and Labor	Pass	Pass

Related Recruiting Tests

Candidate-to-Worker is the sixth and final scenario family in the Recruiting cluster, converting the output of Job Offer into a Core HR worker record and bridging into the Hire-to-Retire lifecycle.

Job Offer Job Requisition Hire Employee — Core HR

Turn This Standard Test into Your Oracle HCM Candidate-to-Worker Regression Suite

Start with the Syntra Standard Candidate-to-Worker test, use DataVault to provide masked, environment-specific candidate, worker and national-identifier data, let Jarvis generate additional Positive, Negative, Boundary, Security and Integration variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore HCM Recruiting 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 HCM Recruiting HCM Core HR User Access Test Cases Syntra DataVault DataVault Data Masking

Frequently Asked Questions

How are national identifiers and compensation data protected during Candidate-to-Worker conversion testing?

Every national identifier and compensation value used across this page's 40 Candidate-to-Worker scenarios is a masked, synthetic value generated through Syntra DataVault — never a real or realistic national identifier or salary figure. This follows the same masked-only standard applied to the HCM Core HR Manage National Identifiers test. See /datavault/data-masking/ for how DataVault masking and privacy controls protect this data across Recruiting and Core HR.

How does this page relate to the Core HR Hire-to-Retire flow?

Candidate-to-Worker is the sixth and final scenario family in the Recruiting cluster and the cross-module bridge into Core HR. Once conversion completes, the new worker record enters the Hire-to-Retire lifecycle covered by the Core HR Hire Employee test and subsequent lifecycle events such as assignment change, promotion and transfer.

How does background-check gating logic work in these test scenarios?

Dedicated scenarios initiate a background check, confirm a cleared result allows conversion to proceed, and confirm a flagged or not-yet-cleared result correctly blocks conversion. Actual background-check providers and clearance rules depend entirely on the customer's own Oracle Fusion Recruiting configuration.

How is Recruiting-to-Payroll integration tested?

Dedicated scenarios confirm that the new worker's assignment and masked compensation data are correctly made available to Payroll after conversion, and confirm that an integration failure between Recruiting and Payroll is correctly surfaced rather than silently dropped. Actual integration touchpoints depend on the customer's own Oracle Fusion Payroll configuration.

How does SyntraFlow classify a failed Candidate-to-Worker test?

When a step or business assertion fails, SyntraFlow's evidence is intended to help classify the likely cause into one of eight categories — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — along with supporting evidence and a recommended action. For example, a new hire not appearing in Core HR after conversion is likely an INTEGRATION_ERROR or APPLICATION_ERROR depending on the evidence. A failure should not be labeled as an Oracle application defect until data, configuration, security, automation and integration causes have been eliminated.

How is security tested for Candidate-to-Worker conversion?

SyntraFlow can exercise conversion under different personas — an HR Specialist executing the new hire conversion, a Recruiter viewing conversion status, and an unauthorized user attempting to initiate conversion or view national identifier data — to confirm Oracle correctly allows or blocks each action. Actual behavior depends on the customer's own Oracle Fusion Recruiting and Core HR security configuration.