{
  "test_id": "ORCL.HCM.E2E.HIRE2BEN",
  "scenario_name": "Hire-to-Benefits",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "End-to-End HCM",
  "process": "Hire-to-Benefits",
  "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-benefits/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Oracle Fusion Hire-to-Benefits journey — hire, benefits eligibility determination, new hire life event, enrollment opportunity, plan selection, dependents, beneficiaries, submission and payroll deduction — with emphasis on the submitted enrollment election correctly generating the resulting payroll benefit deduction, since configuration varies by customer. This page is an orchestration and journey test: it does not re-test each stage's own atomic, field-level validation already covered on the linked Hire Employee, Benefits Eligibility, Life Event, Benefits Enrollment, Dependent Management, Beneficiary Management, Payroll Calculation and Payroll Processing pages. Instead, it links to those live pages and adds scenarios that specifically test the hand-offs and continuity between hiring, benefits enrollment and payroll.",
    "confirms": [
      "the worker, eligibility, life event, enrollment and payroll data correctly carry forward from one stage to the next",
      "the elected coverage tier, dependents and beneficiaries are correctly captured in the submitted enrollment",
      "beneficiary allocation is correctly validated to total 100% before submission is permitted",
      "the employee contribution amount correctly equals the resulting payroll benefit deduction",
      "changed or waived coverage correctly updates the resulting payroll deduction",
      "Oracle correctly enforces validation when data errors, configuration errors, security restrictions or missing upstream documents 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 HCM Core HR, Benefits and Payroll 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-Benefits journey for a new hire enrolling during the new hire enrollment window in Oracle Fusion Cloud HCM TEST/UAT environments and does not cover open enrollment or qualifying life event changes outside the new hire enrollment window, which are covered by separate Benefits scenarios outside this journey."
  },
  "preconditions": [
    "A new hire ${WORKER} is created in the target Oracle Fusion environment with an active assignment eligible for benefits.",
    "Benefits is configured for the current benefits offering, including eligibility rules, waiting periods, life event definitions and enrollment windows.",
    "Plan ${PLAN}, coverage tiers, and dependent and beneficiary designation rules are configured for the benefits offering.",
    "Payroll is configured with the benefit element mapping required to generate a deduction from a submitted enrollment election.",
    "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": "Life Event",
      "example": "${LIFE_EVENT}"
    },
    {
      "field": "Plan",
      "example": "${PLAN}"
    },
    {
      "field": "Coverage Tier",
      "example": "${COVERAGE_TIER}"
    },
    {
      "field": "Dependent",
      "example": "${DEPENDENT}"
    },
    {
      "field": "Beneficiary",
      "example": "${BENEFICIARY}"
    },
    {
      "field": "Contribution Amount",
      "example": "${CONTRIBUTION_AMOUNT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Hire the Worker",
      "action": "Hire ${WORKER} into the target Oracle Fusion environment, using the linked Hire Employee scenario.",
      "test_data": "${WORKER}",
      "expected_result": "The worker is correctly hired and available for benefits eligibility processing.",
      "validation_type": "action",
      "note": "This step orchestrates the Hire Employee family page rather than repeating its individual field-level test coverage."
    },
    {
      "step_number": 2,
      "step_name": "Determine Benefits Eligibility and Waiting Period",
      "action": "Determine benefits eligibility for ${WORKER}, including any configured waiting period, using the linked Benefits Eligibility scenario.",
      "test_data": "${WORKER}",
      "expected_result": "Eligibility and any applicable waiting period are correctly determined for ${WORKER}.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Generate the New Hire Life Event and Enrollment Opportunity",
      "action": "Generate life event ${LIFE_EVENT} for ${WORKER} and confirm the corresponding enrollment opportunity is created, using the linked Life Event scenario.",
      "test_data": "${LIFE_EVENT}",
      "expected_result": "The new hire life event and enrollment opportunity are correctly generated for ${WORKER}.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Select Plans and Coverage Tier",
      "action": "Elect plan ${PLAN} and coverage tier ${COVERAGE_TIER} for ${WORKER} within the enrollment opportunity, using the linked Benefits Enrollment scenario.",
      "test_data": "${PLAN} / ${COVERAGE_TIER}",
      "expected_result": "The plan and coverage tier elections are correctly recorded.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Add Dependents and Beneficiaries",
      "action": "Add dependent ${DEPENDENT} and beneficiary ${BENEFICIARY} to ${WORKER}'s enrollment, using the linked Dependent Management and Beneficiary Management scenarios.",
      "test_data": "${DEPENDENT} / ${BENEFICIARY}",
      "expected_result": "Dependent and beneficiary records are correctly added and linked to the enrollment, with beneficiary allocations correctly totaling 100%.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Submit the Enrollment",
      "action": "Submit the completed enrollment for ${WORKER}.",
      "test_data": "",
      "expected_result": "The enrollment is correctly submitted with all required elections, dependents and beneficiaries captured.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify the Resulting Payroll Benefit Deduction",
      "action": "Trace the submitted enrollment for ${WORKER} to the first scheduled payroll run, using the linked Payroll Calculation and Payroll Processing scenarios, to confirm employee contribution ${CONTRIBUTION_AMOUNT} correctly generates the corresponding payroll deduction.",
      "test_data": "",
      "expected_result": "The submitted enrollment election correctly generates the corresponding payroll benefit deduction, with the full hire-to-benefits chain correctly linked end-to-end.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly submitted enrollment that generates the matching payroll deduction is the expected pass condition, not merely a successful enrollment submission."
    }
  ],
  "expected_results": [
    "The worker, eligibility, life event and enrollment opportunity are correctly linked end-to-end.",
    "The elected coverage tier, dependents and beneficiaries are correctly captured in the submitted enrollment.",
    "Beneficiary allocations correctly total 100% before submission is permitted.",
    "Employee and employer contributions are correctly calculated for the elected plan and coverage tier.",
    "The submitted enrollment election correctly generates the corresponding payroll benefit deduction.",
    "Changed or waived coverage correctly updates the resulting payroll deduction, and unauthorized actions at any stage of the journey are correctly blocked."
  ],
  "validation_checkpoints": [
    "Eligibility is correctly determined based on hire and waiting period rules.",
    "The enrollment window is correctly enforced.",
    "The elected coverage tier is correctly reflected in the submission.",
    "Beneficiary allocation is correctly validated to total 100%.",
    "The employee contribution is correctly calculated and sent to payroll as a deduction.",
    "Changed or waived coverage correctly updates the payroll deduction."
  ]
}