{
  "test_id": "ORCL.HCM.RECRUIT.C2W",
  "scenario_name": "Candidate-to-Worker",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Recruiting",
  "process": "Candidate-to-Worker",
  "business_flow": "Recruit-to-Hire",
  "scenario_type": "Positive / Negative / Boundary / Security / Integration",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/recruiting/candidate-to-worker/",
  "objective": {
    "intro": "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.",
    "confirms": [
      "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"
    ],
    "scope_note": "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."
  },
  "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."
  ],
  "test_data": [
    {
      "field": "Candidate",
      "example": "${CANDIDATE}"
    },
    {
      "field": "Requisition",
      "example": "${REQUISITION}"
    },
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Position",
      "example": "${POSITION}"
    },
    {
      "field": "Grade",
      "example": "${GRADE}"
    },
    {
      "field": "Work Location",
      "example": "${WORK_LOCATION}"
    },
    {
      "field": "Manager",
      "example": "${MANAGER}"
    },
    {
      "field": "National Identifier",
      "example": "${NATIONAL_IDENTIFIER} (masked)"
    },
    {
      "field": "Hire Date",
      "example": "${HIRE_DATE}"
    },
    {
      "field": "Background Check Status",
      "example": "${BACKGROUND_CHECK_STATUS}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion HCM",
      "action": "Sign in to Oracle Fusion Cloud with a user account that has Recruiting and Core HR access.",
      "test_data": "",
      "expected_result": "The Oracle Fusion Cloud home page loads successfully for the authenticated user.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Accepted-Offer Candidate",
      "action": "Navigate to the Recruiting work area and open the accepted-offer candidate record for ${CANDIDATE} on ${REQUISITION}.",
      "test_data": "${CANDIDATE} / ${REQUISITION}",
      "expected_result": "The candidate's accepted-offer record opens successfully with the conversion action available.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Initiate Background Check and Confirm Clearance",
      "action": "Initiate the background check for ${CANDIDATE} and confirm the result reaches a cleared status before proceeding.",
      "test_data": "${BACKGROUND_CHECK_STATUS}",
      "expected_result": "The background check is recorded correctly, and conversion is gated until the cleared status is reached.",
      "validation_type": "business_assertion",
      "note": "A flagged or not-yet-cleared background check correctly blocking conversion is a passing outcome for negative and gating scenarios, not a failure."
    },
    {
      "step_number": 4,
      "step_name": "Assign and Complete Onboarding Tasks",
      "action": "Assign the configured onboarding task list to ${CANDIDATE} and complete the required onboarding forms and work eligibility verification.",
      "test_data": "",
      "expected_result": "Onboarding tasks and forms are recorded as complete, and work eligibility verification is confirmed.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Initiate the Candidate-to-Worker Conversion",
      "action": "Initiate the candidate-to-worker conversion action for ${CANDIDATE} once the background check and onboarding are complete.",
      "test_data": "${CANDIDATE} / ${WORKER}",
      "expected_result": "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.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Data Transfer to the New Person and Assignment Record",
      "action": "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.",
      "test_data": "${POSITION} / ${GRADE} / ${WORK_LOCATION} / ${MANAGER} / ${NATIONAL_IDENTIFIER}",
      "expected_result": "All transferred fields on the new person and assignment record match the source candidate and offer data accurately.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 7,
      "step_name": "Execute the New Hire Action",
      "action": "Execute the new hire action for ${WORKER} on ${HIRE_DATE}.",
      "test_data": "${HIRE_DATE}",
      "expected_result": "The hire executes correctly and the worker record is activated with the correct hire date.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Requisition and Headcount Update",
      "action": "Confirm that ${REQUISITION} is marked filled and that headcount tracked against the approved budget is correctly decremented after the hire.",
      "test_data": "${REQUISITION}",
      "expected_result": "Requisition status and headcount tracking accurately reflect the completed hire.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 9,
      "step_name": "Verify New Hire Appears Across Core HR, Workforce Structures and Time and Labor",
      "action": "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.",
      "test_data": "${WORKER}",
      "expected_result": "The new hire is correctly visible and synchronized across Core HR, Workforce Structures, Time and Labor and Payroll.",
      "validation_type": "business_assertion",
      "note": "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."
    }
  ],
  "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."
  ],
  "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."
  ]
}