{
  "test_id": "ORCL.HCM.BEN.LIFE_EVENT",
  "scenario_name": "Life Event",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Benefits",
  "process": "Life Event",
  "business_flow": "Benefits-to-Pay",
  "scenario_type": "Positive / Negative / Boundary / Security",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/benefits/life-event/",
  "objective": {
    "intro": "This test validates life-event detection, processing and resulting benefits enrollment opportunities across Oracle Fusion HCM Benefits, without assuming a universal set of supported personal-event types.",
    "confirms": [
      "employment-driven life events — new hire, rehire, termination, and transfer or assignment-change events where configured — are correctly detected and processed",
      "personal life events — marriage, divorce, birth, adoption, dependent gain and dependent loss — are correctly detected and processed where each is configured as a qualifying event for the customer",
      "a detected life event correctly opens an enrollment opportunity with the correct enrollment window and effective date",
      "multiple or sequenced life events for the same worker are evaluated and processed in the correct order",
      "backdated and future-dated life events are processed with the correct resulting window and effective date",
      "deliberately invalid submissions — invalid event date, duplicate event, unsupported event type, ineligible worker, event outside the permitted reporting window, missing supporting information, already-processed event, conflicting events, unauthorized processing — are correctly rejected or flagged rather than silently accepted"
    ],
    "scope_note": "A negative or boundary Life Event scenario passes when Oracle correctly enforces the expected eligibility, plan or enrollment-window rule; this test does not attempt to certify a specific Oracle application defect, and does not assume a universal set of supported personal-event types — which personal events are configured as qualifying life events depends entirely on customer-specific Oracle Fusion Benefits configuration. Where an entry or validation appears unexpected or its cause is unclear, it is treated as requiring further investigation and supporting evidence rather than a confirmed conclusion. This page catalogs 32 individual Life Event scenarios as a single comprehensive reference rather than as separate indexable pages."
  },
  "preconditions": [
    "Oracle Fusion Benefits access is available to the test user.",
    "A representative ${WORKER} record, including active employment and family/dependent data where applicable, is available or can be constructed.",
    "Valid and invalid ${LIFE_EVENT_TYPE} and ${EVENT_DATE} combinations are available for testing employment and personal events.",
    "At least one ${DEPENDENT} record is available for personal life events that add or remove a dependent.",
    "A configured ${BENEFITS_PROGRAM} with an associated ${ENROLLMENT_WINDOW} and ${EFFECTIVE_DATE} rule is in place for ${LEGAL_EMPLOYER}.",
    "A representative ${SUPPORTING_DOCUMENT} is available for life events that require supporting evidence where configured.",
    "A user without the required Benefits security access is available for security testing, and a worker who is not eligible for ${BENEFITS_PROGRAM} is available for negative testing."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Life Event Type",
      "example": "${LIFE_EVENT_TYPE}"
    },
    {
      "field": "Event Date",
      "example": "${EVENT_DATE}"
    },
    {
      "field": "Dependent",
      "example": "${DEPENDENT}"
    },
    {
      "field": "Supporting Document",
      "example": "${SUPPORTING_DOCUMENT}"
    },
    {
      "field": "Enrollment Window",
      "example": "${ENROLLMENT_WINDOW}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    },
    {
      "field": "Legal Employer",
      "example": "${LEGAL_EMPLOYER}"
    },
    {
      "field": "Benefits Program",
      "example": "${BENEFITS_PROGRAM}"
    }
  ],
  "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 Benefits 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 Worker's Benefits Record",
      "action": "Navigate to the benefits work area and open ${WORKER}'s benefits record.",
      "test_data": "${WORKER}",
      "expected_result": "The worker's benefits record opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Record or Detect the Life Event",
      "action": "Record the ${LIFE_EVENT_TYPE} life event dated ${EVENT_DATE}, or confirm it was correctly detected from the underlying data change.",
      "test_data": "${LIFE_EVENT_TYPE} / ${EVENT_DATE}",
      "expected_result": "The life event is correctly recorded or detected and queued for processing, or a deliberately invalid event is rejected with the expected validation.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Verify Enrollment Opportunity and Window Created",
      "action": "Confirm that the life event correctly created an enrollment opportunity with the expected ${ENROLLMENT_WINDOW}.",
      "test_data": "${ENROLLMENT_WINDOW}",
      "expected_result": "The enrollment opportunity and its window are created correctly for a qualifying event, or correctly not created for a non-qualifying event.",
      "validation_type": "business_assertion",
      "note": "Correctly withholding an enrollment opportunity for a non-qualifying or ineligible event is a passing outcome for negative scenarios, not a failure."
    },
    {
      "step_number": 5,
      "step_name": "Attach Supporting Information Where Required",
      "action": "Attach ${SUPPORTING_DOCUMENT} where the life event requires supporting documentation.",
      "test_data": "${SUPPORTING_DOCUMENT}",
      "expected_result": "Supporting information is correctly attached and recorded, or processing is correctly withheld where required documentation is missing.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Process the Life Event",
      "action": "Process the life event and confirm the resulting eligibility and enrollment evaluation for ${BENEFITS_PROGRAM}.",
      "test_data": "${BENEFITS_PROGRAM}",
      "expected_result": "The life event is processed correctly, or a deliberately invalid, duplicate or already-processed event is correctly rejected.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Resulting Enrollment Window and Effective Date",
      "action": "Confirm that the resulting ${ENROLLMENT_WINDOW} and ${EFFECTIVE_DATE} applied to elections are correct for the processed life event.",
      "test_data": "${EFFECTIVE_DATE}",
      "expected_result": "The enrollment window and effective date accurately reflect a valid life event, or an expected validation for an invalid one.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario across the full catalog of 32 Life Event variations."
    }
  ],
  "expected_results": [
    "Employment and personal life events correctly detected and classified with the intended event type and date.",
    "Detected life events correctly opened an enrollment opportunity with the correct enrollment window, where the event is configured as qualifying.",
    "Effective date for resulting elections correctly determined according to the configured effective-date rule.",
    "Multiple or sequenced life events correctly evaluated and processed in the correct order.",
    "Duplicate, already-processed and conflicting life events correctly identified and handled.",
    "Deliberately invalid submissions raised the expected data, eligibility or security validation rather than being silently accepted."
  ],
  "validation_checkpoints": [
    "Life event correctly detected and classified.",
    "Enrollment window correctly opened with correct duration.",
    "Effective date correctly determined.",
    "Duplicate/conflicting events correctly handled.",
    "Ineligible worker events correctly blocked.",
    "Unsupported or invalid events correctly rejected."
  ]
}