{
  "test_id": "ORCL.HCM.E2E.HIRE2RETIRE",
  "scenario_name": "Hire-to-Retire",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "End-to-End HCM",
  "process": "Hire-to-Retire",
  "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/hire-to-retire/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Oracle Fusion Hire-to-Retire employee lifecycle journey — hire, person management, assignment changes, compensation, benefits, time/absence, performance, promotion/transfer, payroll and termination — with emphasis on worker identity and assignment data correctly carrying forward across every lifecycle event, not on re-testing each stage's own atomic, field-level validation already covered on the linked family pages. This page is an orchestration and journey test: it does not duplicate the scenario coverage already tested individually on the 33 linked Core HR, Person Management, Compensation, Benefits, Absence Management, Time and Labor, Payroll, Performance Management, Learning and HCM Data and Security pages. Instead, it links to those live pages and adds scenarios that specifically test the hand-offs and continuity between them across nearly every HCM module.",
    "confirms": [
      "worker identity correctly persists across every lifecycle event from hire through termination",
      "assignment changes correctly reflect the latest approved job, position, department and manager",
      "compensation changes correctly reflect on the worker's current assignment",
      "benefits, time, absence, performance and learning events correctly link to the correct worker and assignment",
      "role and data access correctly update following transfers and manager changes",
      "termination correctly restricts downstream benefits, time and system access per configuration",
      "historical worker data correctly remains accessible to authorized HR after termination",
      "Oracle correctly enforces validation when data errors, configuration errors, security restrictions or timing boundaries 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 Core HR, Compensation, Benefits, Time and Labor, Absence Management, Performance Management, Learning, Payroll and HCM Data 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 Hire-to-Retire journey in Oracle Fusion Cloud HCM TEST/UAT environments and does not assume every worker follows every lifecycle event — available events depend on worker type, legal employer, legislative requirements and customer-specific configuration."
  },
  "preconditions": [
    "A worker ${WORKER} record can be created or already exists at legal employer ${LEGAL_EMPLOYER} in the target Oracle Fusion environment.",
    "Job ${JOB}, position ${POSITION}, grade and department structures are configured and available for assignment.",
    "The test user or users hold appropriate access to progress a worker through hire, assignment, compensation, benefits, time/absence, performance, payroll and termination stages.",
    "Benefits programs, absence plans, time entry rules, payroll relationships and performance templates relevant to the journey are configured in the target environment.",
    "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": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Legal Employer",
      "example": "${LEGAL_EMPLOYER}"
    },
    {
      "field": "Job",
      "example": "${JOB}"
    },
    {
      "field": "Position",
      "example": "${POSITION}"
    },
    {
      "field": "Manager",
      "example": "${MANAGER}"
    },
    {
      "field": "Salary",
      "example": "${SALARY}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    },
    {
      "field": "Termination Date",
      "example": "${TERMINATION_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Hire the Worker",
      "action": "Hire ${WORKER} into ${JOB} / ${POSITION} at ${LEGAL_EMPLOYER} reporting to ${MANAGER}, using the linked Hire Employee or Hire Contingent Worker scenario.",
      "test_data": "${WORKER} / ${LEGAL_EMPLOYER}",
      "expected_result": "The worker is hired and the person and assignment records are correctly created as the starting point of the journey.",
      "validation_type": "action",
      "note": "This step orchestrates the Hire Employee, Hire Contingent Worker and Convert Pending Worker family pages rather than repeating their individual field-level test coverage."
    },
    {
      "step_number": 2,
      "step_name": "Update Person Information as Needed",
      "action": "Update person information — address, contact information, national identifiers or emergency contacts — for ${WORKER}, using the linked Person Management scenarios.",
      "test_data": "${WORKER}",
      "expected_result": "Person information updates are correctly recorded without disrupting the worker's active assignment.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Process Assignment Changes (Promotion, Transfer, Global Transfer)",
      "action": "Progress ${WORKER} through assignment changes — change assignment, promotion, internal transfer or global transfer — using the linked Change Assignment, Promote Worker, Transfer Worker and Global Transfer scenarios.",
      "test_data": "${JOB} / ${POSITION} / ${MANAGER}",
      "expected_result": "Assignment changes are correctly approved and the current assignment reflects the latest job, position, department and manager.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Process Compensation Changes",
      "action": "Process a compensation change for ${WORKER} — salary change, individual compensation, workforce compensation or bonus allocation — using the linked Compensation scenarios.",
      "test_data": "${SALARY}",
      "expected_result": "The compensation change is correctly approved and reflected on the worker's current assignment.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Process Benefits Enrollment",
      "action": "Enroll ${WORKER} in benefits, and add dependents or beneficiaries as applicable, using the linked Benefits Enrollment, Dependent Management and Beneficiary Management scenarios.",
      "test_data": "${WORKER}",
      "expected_result": "Benefits enrollment is correctly linked to the worker's current assignment and eligibility.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Process Time / Absence Entries",
      "action": "Enter and approve time and absence for ${WORKER}, using the linked Absence Entry, Absence Approval, Timecard Entry and Timecard Approval scenarios.",
      "test_data": "${WORKER}",
      "expected_result": "Time and absence entries are correctly recorded and approved against the worker's current assignment.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Process Performance Evaluation",
      "action": "Create and complete a performance document for ${WORKER}, including employee evaluation, manager evaluation and goal updates, using the linked Performance Management scenarios.",
      "test_data": "${MANAGER}",
      "expected_result": "The performance document is correctly linked to the worker's current assignment and manager.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Run Payroll",
      "action": "Process payroll for ${WORKER} at ${LEGAL_EMPLOYER} for the current period, using the linked Payroll Processing scenario.",
      "test_data": "${LEGAL_EMPLOYER}",
      "expected_result": "Compensation, approved time and benefits deductions are correctly reflected in the payroll run.",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Process Termination and Verify Downstream Access Changes",
      "action": "Terminate ${WORKER} effective ${TERMINATION_DATE}, using the linked Terminate Worker scenario, then verify downstream benefits, time and system access change as configured.",
      "test_data": "${TERMINATION_DATE}",
      "expected_result": "Termination is correctly processed and downstream benefits, time and system access are correctly restricted per configuration, while historical data correctly remains accessible to authorized HR.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a fully linked worker record with correct downstream access restriction after termination is the expected pass condition, not merely a successful termination transaction."
    }
  ],
  "expected_results": [
    "Worker identity correctly persists across every lifecycle event from hire through termination.",
    "Assignment changes correctly reflect the latest approved job, position, department and manager.",
    "Compensation changes correctly reflect on the worker's current assignment.",
    "Benefits, time, absence, performance and learning events correctly link to the correct worker and assignment.",
    "Payroll correctly reflects compensation, approved time and benefits deductions for the current assignment.",
    "Termination correctly restricts downstream access per configuration, and unauthorized actions at any stage of the journey are correctly blocked."
  ],
  "validation_checkpoints": [
    "Worker identity correctly persists across every lifecycle event.",
    "Assignment changes correctly reflect the latest approved job, position, department and manager.",
    "Compensation changes correctly reflect on the worker's assignment.",
    "Benefits, time, absence, performance and learning events correctly link to the correct worker and assignment.",
    "Role and data access correctly update following transfers and manager changes.",
    "Termination correctly restricts downstream access per configuration.",
    "Historical data correctly remains accessible to authorized HR after termination.",
    "Effective-dated changes correctly preserve prior history."
  ]
}