{
  "test_id": "ORCL.HCM.BEN.DEPENDENT",
  "scenario_name": "Dependent Management",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Benefits",
  "process": "Dependent Management",
  "business_flow": "Benefits-to-Pay",
  "scenario_type": "Positive / Negative / Security",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/benefits/dependent-management/",
  "objective": {
    "intro": "This test validates adding, updating and removing dependents on a worker's Oracle Fusion Benefits record, and confirms correct eligibility and coverage impact, using masked/synthetic dependent data only — dependents are often minors or other family members, so this scenario family treats dependent data with the same or greater care as the worker's own data.",
    "confirms": [
      "a dependent can be added, updated and removed for a worker using only masked/synthetic dependent data, with the intended relationship, date of birth and identifier recorded correctly",
      "age, relationship and effective-date eligibility rules are correctly applied before a dependent is linked to a plan",
      "a dependent can be correctly enrolled in and linked to the intended plan and coverage level",
      "removing a dependent, including one with active coverage, correctly updates the resulting coverage",
      "dependent eligibility is correctly recalculated after a qualifying life event",
      "deliberately invalid submissions — duplicate dependent, missing relationship, invalid or future date of birth, missing required identifier, ineligible dependent, dependent already covered, unauthorized update — are correctly rejected or flagged rather than silently accepted"
    ],
    "scope_note": "A negative or security Dependent Management scenario passes when Oracle correctly enforces the expected eligibility, data or access rule; this test does not attempt to certify a specific Oracle application defect. This page catalogs 26 individual Dependent Management scenarios as a single comprehensive reference rather than as separate indexable pages, and every dependent data value referenced throughout is a masked/synthetic placeholder — never a real dependent's name, date of birth or identifier."
  },
  "preconditions": [
    "Oracle Fusion Benefits access is available to the test user.",
    "A representative ${WORKER} with an active benefits enrollment is available or can be constructed.",
    "Masked/synthetic ${DEPENDENT} test data, including valid and invalid ${RELATIONSHIP} and ${DEPENDENT_DOB} values, is available through DataVault.",
    "At least one ${PLAN} with configured age, relationship and effective-date eligibility rules is available for testing.",
    "A configured ${COVERAGE_LEVEL} and ${EFFECTIVE_DATE} scenario is available for enrollment and removal testing.",
    "A representative ${LIFE_EVENT} is available for testing eligibility recalculation.",
    "A user without the required Benefits security access is available for security testing, and only masked/synthetic dependent identifiers are used — never real dependent PII."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Dependent",
      "example": "${DEPENDENT}"
    },
    {
      "field": "Relationship",
      "example": "${RELATIONSHIP}"
    },
    {
      "field": "Date of Birth",
      "example": "${DEPENDENT_DOB}"
    },
    {
      "field": "Identifier",
      "example": "${DEPENDENT_IDENTIFIER}"
    },
    {
      "field": "Plan",
      "example": "${PLAN}"
    },
    {
      "field": "Coverage Level",
      "example": "${COVERAGE_LEVEL}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    },
    {
      "field": "Life Event",
      "example": "${LIFE_EVENT}"
    }
  ],
  "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/Dependent Record",
      "action": "Navigate to the Benefits work area and open ${WORKER}'s dependent record.",
      "test_data": "${WORKER}",
      "expected_result": "The worker's benefits and dependent record opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Add or Update Dependent Details",
      "action": "Add a new dependent or update an existing dependent's name, date of birth, relationship, address or identifier.",
      "test_data": "${DEPENDENT} / ${RELATIONSHIP} / ${DEPENDENT_DOB} / ${DEPENDENT_IDENTIFIER}",
      "expected_result": "The dependent record is created or updated with the entered masked/synthetic details recorded correctly, or a deliberately invalid submission is rejected with the expected validation.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Verify Eligibility (Age, Relationship, Effective Date)",
      "action": "Confirm that the dependent's age, relationship and effective date are evaluated against the plan's configured eligibility rules.",
      "test_data": "${DEPENDENT_DOB} / ${RELATIONSHIP} / ${EFFECTIVE_DATE}",
      "expected_result": "Age, relationship and effective-date eligibility are correctly evaluated, and an ineligible dependent is correctly flagged.",
      "validation_type": "action",
      "note": "Exact eligibility rules depend on the customer's own plan configuration."
    },
    {
      "step_number": 5,
      "step_name": "Link Dependent to Plan/Coverage",
      "action": "Link the eligible dependent to the selected plan and coverage level, or remove the dependent from existing coverage.",
      "test_data": "${PLAN} / ${COVERAGE_LEVEL}",
      "expected_result": "The dependent is correctly linked to or removed from the selected plan and coverage level.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Submit",
      "action": "Submit the dependent add, update, enrollment or removal action for processing.",
      "test_data": "",
      "expected_result": "The submission is accepted and processed, or a deliberately invalid submission is rejected with the expected validation.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Dependent Record and Coverage Impact",
      "action": "Confirm the resulting dependent record and its impact on coverage after the add, update, enrollment or removal action.",
      "test_data": "${COVERAGE_LEVEL} / ${EFFECTIVE_DATE}",
      "expected_result": "The dependent record and coverage impact accurately reflect a valid submission, 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 26 Dependent Management variations."
    }
  ],
  "expected_results": [
    "Each dependent recorded correctly with the intended relationship, date of birth and identifier, using masked/synthetic data only.",
    "Age, relationship and effective-date eligibility rules correctly applied before a dependent is linked to a plan.",
    "Dependent correctly enrolled in and linked to the selected plan and coverage level.",
    "Removing a dependent, including one with active coverage, correctly updates the resulting coverage.",
    "Dependent eligibility correctly recalculated after a qualifying life event.",
    "Deliberately invalid, duplicate, ineligible or unauthorized submissions raised the expected validation rather than being silently accepted."
  ],
  "validation_checkpoints": [
    "Dependent record correctly created/updated with masked test data.",
    "Relationship and age eligibility correctly enforced.",
    "Dependent correctly linked to enrolled plan/coverage.",
    "Duplicate dependents correctly blocked.",
    "Removal correctly updates coverage.",
    "Unauthorized access to dependent data correctly blocked."
  ]
}