{
  "test_id": "ORCL.HCM.E2E.RECRUIT2HIRE",
  "scenario_name": "Recruit-to-Hire",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "End-to-End HCM",
  "process": "Recruit-to-Hire",
  "business_flow": "Hire-to-Retire",
  "scenario_type": "End-to-End / Cross-Module",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard Journey",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/end-to-end/recruit-to-hire/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Oracle Fusion Recruit-to-Hire journey — job requisition, approval, job posting, candidate application, screening, interview, offer, offer acceptance, candidate-to-worker conversion, pending worker and hire — with emphasis on candidate and offer data (job, position, department, location, grade, legal employer, start date) correctly carrying forward into the hired worker record, not on re-testing each stage's own atomic, field-level validation. This page is an orchestration and journey test: it does not duplicate the scenario coverage already tested individually on the linked Job Requisition, Candidate Application, Candidate Screening, Interview, Job Offer, Candidate-to-Worker, Convert Pending Worker, Hire Employee, Jobs, Positions, Departments, Locations, Grades, User Access and Role Security pages. Instead, it links to those live pages and adds scenarios that specifically test the hand-offs and value continuity between them.",
    "confirms": [
      "job requisition, approval, posting, candidate, screening, interview, offer, offer acceptance and hire data correctly carry forward from one stage to the next",
      "requisition job and position correctly carry into the offer and then into the converted worker record",
      "department, location and grade on the offer correctly carry into the worker's assignment at hire",
      "legal employer correctly carries from requisition through to the hired worker",
      "proposed start date on the offer correctly carries into the worker's hire date where expected",
      "candidate identity correctly persists through candidate-to-worker conversion, with duplicate candidates and duplicate persons correctly detected",
      "Oracle correctly enforces validation when data errors, configuration errors, security restrictions or missing mandatory data are introduced at any stage of the journey (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario orchestrates and links to the individually tested Recruiting, Core HR, Workforce Structures and Security family pages listed on this page; it does not re-test each stage's own field-level validation, which remains covered on those pages. It covers the standard Recruit-to-Hire journey in Oracle Fusion Cloud HCM TEST/UAT environments and does not cover internal transfers or promotions without a preceding recruiting event, which are covered by separate Core HR scenarios outside this journey."
  },
  "preconditions": [
    "A job requisition ${REQUISITION} for job ${JOB}, position ${POSITION} and ${LEGAL_EMPLOYER} is ready to be created and approved in the target Oracle Fusion environment.",
    "Recruiting, Core HR and Workforce Structures — jobs, positions, departments, locations and grades — are configured for the legal employer.",
    "The test user or users hold appropriate access to progress a transaction through requisition, posting, screening, interview, offer and hire stages.",
    "A candidate identity ${CANDIDATE} without a pre-existing duplicate record is available for a standard external candidate journey.",
    "This scenario assumes each linked family page's own preconditions are separately satisfied — it does not re-verify field-level setup already covered on those pages."
  ],
  "test_data": [
    {
      "field": "Candidate",
      "example": "${CANDIDATE}"
    },
    {
      "field": "Requisition",
      "example": "${REQUISITION}"
    },
    {
      "field": "Offer",
      "example": "${OFFER}"
    },
    {
      "field": "Job",
      "example": "${JOB}"
    },
    {
      "field": "Position",
      "example": "${POSITION}"
    },
    {
      "field": "Legal Employer",
      "example": "${LEGAL_EMPLOYER}"
    },
    {
      "field": "Start Date",
      "example": "${START_DATE}"
    },
    {
      "field": "Worker",
      "example": "${WORKER}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Create and Approve the Job Requisition",
      "action": "Create job requisition ${REQUISITION} for job ${JOB}, position ${POSITION} and ${LEGAL_EMPLOYER}, and progress it through the configured approval routing, using the linked Job Requisition scenario.",
      "test_data": "${REQUISITION} / ${JOB} / ${POSITION}",
      "expected_result": "The requisition is correctly created and approved, ready for posting.",
      "validation_type": "action",
      "note": "This step orchestrates the Job Requisition family page rather than repeating its individual field-level test coverage."
    },
    {
      "step_number": 2,
      "step_name": "Post the Job",
      "action": "Post approved requisition ${REQUISITION} internally, externally or both, using the linked Job Requisition scenario's posting behavior.",
      "test_data": "${REQUISITION}",
      "expected_result": "The requisition is correctly posted and visible to the intended candidate audience.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Receive and Screen Candidate Applications",
      "action": "Receive an application from candidate ${CANDIDATE} against requisition ${REQUISITION}, and progress it through screening, using the linked Candidate Application and Candidate Screening scenarios.",
      "test_data": "${CANDIDATE}",
      "expected_result": "The candidate's application and screening outcome are correctly recorded.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Conduct Interviews and Record Feedback",
      "action": "Schedule and conduct an interview for candidate ${CANDIDATE} with ${HIRING_MANAGER}, and record interview feedback, using the linked Interview scenario.",
      "test_data": "${CANDIDATE} / ${HIRING_MANAGER}",
      "expected_result": "The interview and feedback are correctly recorded, and the candidate is correctly progressed or rejected based on the outcome.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Create and Approve the Offer",
      "action": "Create offer ${OFFER} for candidate ${CANDIDATE} carrying job ${JOB}, position ${POSITION}, department ${DEPARTMENT}, location ${LOCATION}, grade ${GRADE}, ${LEGAL_EMPLOYER} and proposed start date ${START_DATE}, and progress it through the configured approval routing, using the linked Job Offer scenario.",
      "test_data": "${OFFER} / ${START_DATE}",
      "expected_result": "The offer is correctly created and approved with accurate job, position, department, location, grade, legal employer and start date.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Process Offer Acceptance",
      "action": "Record candidate ${CANDIDATE}'s acceptance of offer ${OFFER}, using the linked Job Offer scenario.",
      "test_data": "${OFFER}",
      "expected_result": "Offer acceptance is correctly recorded, and the candidate is ready for conversion to a pending worker.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Convert the Candidate to a Pending Worker, Verifying Data Continuity",
      "action": "Convert accepted candidate ${CANDIDATE} to pending worker ${WORKER}, confirming candidate name, contact information, job, position, department, location, grade, legal employer and proposed start date correctly carry forward from the offer, using the linked Candidate-to-Worker and Convert Pending Worker scenarios.",
      "test_data": "${WORKER}",
      "expected_result": "Worker ${WORKER} is correctly created as a pending worker, with every offer data point carried forward without discrepancy.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Hire the Employee",
      "action": "Complete the hire for pending worker ${WORKER} at ${LEGAL_EMPLOYER} on ${START_DATE}, using the linked Hire Employee scenario.",
      "test_data": "${WORKER} / ${START_DATE}",
      "expected_result": "Worker ${WORKER} is correctly hired, with a worker number, assignment and manager relationship established.",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Verify Assignment, Manager Relationship, Security Access and Full Audit Trail",
      "action": "Confirm worker ${WORKER}'s assignment, manager relationship to ${HIRING_MANAGER} and security access are correctly established, and trace the completed transaction from requisition through hire to confirm the audit trail links every stage together.",
      "test_data": "",
      "expected_result": "The audit trail correctly links requisition ${REQUISITION}, candidate ${CANDIDATE}, offer ${OFFER} and worker ${WORKER} end-to-end, with assignment, manager relationship and security access correctly established.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a fully linked, correctly continuous worker record across every stage is the expected pass condition, not merely a successful hire."
    }
  ],
  "expected_results": [
    "The job requisition, approval, posting, candidate, offer, offer acceptance, pending worker and hire are correctly linked end-to-end.",
    "Requisition job and position correctly carry into the offer and then into the converted worker record.",
    "Department, location and grade on the offer correctly carry into the worker's assignment at hire.",
    "Legal employer correctly carries from requisition through to the hired worker.",
    "Proposed start date on the offer correctly carries into the worker's hire date where expected.",
    "Duplicate candidates, duplicate persons, missing mandatory data and unauthorized actions at any stage of the journey are correctly enforced."
  ],
  "validation_checkpoints": [
    "Requisition job and position correctly carry into the offer.",
    "Offer job, position and legal employer correctly carry into the converted worker.",
    "Offer start date correctly equals hire date where expected.",
    "Candidate identity correctly persists through conversion.",
    "Duplicate candidate or duplicate person correctly detected and blocked.",
    "Inactive position or invalid legal employer correctly blocks conversion.",
    "Worker number, assignment and manager relationship correctly created at hire.",
    "Security access correctly established where configured."
  ]
}