{
  "test_id": "ORCL.HCM.BEN.BENEFICIARY",
  "scenario_name": "Beneficiary Management",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Benefits",
  "process": "Beneficiary 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/beneficiary-management/",
  "objective": {
    "intro": "This test validates adding, updating and allocating beneficiaries on a worker's Oracle Fusion Benefits record for plans that require a beneficiary, such as life insurance, and confirms correct allocation-total and eligibility rules, using masked/synthetic beneficiary data only — beneficiaries are third parties, for example life insurance recipients, so this scenario family treats beneficiary data with particular care.",
    "confirms": [
      "a beneficiary can be added, updated, allocated and removed for a worker using only masked/synthetic beneficiary data, with the intended designation type, relationship and allocation percentage recorded correctly",
      "primary beneficiary allocation percentages are correctly validated to total 100% before a submission is accepted",
      "primary and contingent designation types are correctly enforced and can be correctly changed",
      "plans that require a beneficiary correctly block submission without one, and plans that do not require a beneficiary correctly allow submission without one",
      "beneficiary details can be correctly updated after enrollment is already active",
      "deliberately invalid submissions — allocation below or above 100%, zero allocation, missing beneficiary, duplicate beneficiary, invalid relationship, invalid effective date, unauthorized access — are correctly rejected or flagged rather than silently accepted"
    ],
    "scope_note": "A negative or security Beneficiary Management scenario passes when Oracle correctly enforces the expected allocation, eligibility, data or access rule; this test does not attempt to certify a specific Oracle application defect. This page catalogs 23 individual Beneficiary Management scenarios as a single comprehensive reference rather than as separate indexable pages, and every beneficiary data value referenced throughout is a masked/synthetic placeholder — never a real beneficiary's name, relationship or allocation detail. Beneficiaries are third parties, such as life insurance recipients, who have not themselves consented to being part of a test environment."
  },
  "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 ${BENEFICIARY} test data, including valid and invalid ${RELATIONSHIP} and ${BENEFICIARY_TYPE} values, is available through DataVault.",
    "At least one ${PLAN} that requires a beneficiary designation, such as a life-insurance-type plan, is available for testing.",
    "At least one ${PLAN} that does not require a beneficiary designation is available for testing.",
    "A configured ${DESIGNATION_TYPE} and ${ALLOCATION_PERCENT} scenario is available for allocation-total testing.",
    "A user without the required Benefits security access is available for security testing, and only masked/synthetic beneficiary identifiers are used — never real third-party PII."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Beneficiary",
      "example": "${BENEFICIARY}"
    },
    {
      "field": "Beneficiary Type",
      "example": "${BENEFICIARY_TYPE}"
    },
    {
      "field": "Relationship",
      "example": "${RELATIONSHIP}"
    },
    {
      "field": "Allocation Percent",
      "example": "${ALLOCATION_PERCENT}"
    },
    {
      "field": "Plan",
      "example": "${PLAN}"
    },
    {
      "field": "Designation Type",
      "example": "${DESIGNATION_TYPE}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    }
  ],
  "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/Beneficiary Record",
      "action": "Navigate to the Benefits work area and open ${WORKER}'s beneficiary record.",
      "test_data": "${WORKER}",
      "expected_result": "The worker's benefits and beneficiary record opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Add or Update Beneficiary Details",
      "action": "Add a new beneficiary or update an existing beneficiary's name, relationship, beneficiary type or identifying details.",
      "test_data": "${BENEFICIARY} / ${RELATIONSHIP} / ${BENEFICIARY_TYPE}",
      "expected_result": "The beneficiary 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": "Set Designation Type and Allocation Percentage",
      "action": "Set the beneficiary's designation type (primary or contingent) and allocation percentage.",
      "test_data": "${DESIGNATION_TYPE} / ${ALLOCATION_PERCENT}",
      "expected_result": "The designation type and allocation percentage are recorded correctly for the beneficiary.",
      "validation_type": "action",
      "note": "Exact designation and allocation rules depend on the customer's own plan configuration."
    },
    {
      "step_number": 5,
      "step_name": "Verify Allocation Totals",
      "action": "Confirm that the sum of allocation percentages across all beneficiaries of the same designation type correctly totals 100% where required.",
      "test_data": "${ALLOCATION_PERCENT} / ${PLAN}",
      "expected_result": "Allocation totals are correctly validated, and an incomplete or over-allocated total is correctly flagged.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Submit",
      "action": "Submit the beneficiary add, update, allocation 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 Beneficiary Record and Allocation",
      "action": "Confirm the resulting beneficiary record and allocation after the add, update, allocation or removal action.",
      "test_data": "${DESIGNATION_TYPE} / ${ALLOCATION_PERCENT} / ${EFFECTIVE_DATE}",
      "expected_result": "The beneficiary record and allocation 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 23 Beneficiary Management variations."
    }
  ],
  "expected_results": [
    "Each beneficiary recorded correctly with the intended designation type, relationship and allocation percentage, using masked/synthetic data only.",
    "Primary allocation percentages correctly validated to total 100% before a submission is accepted.",
    "Primary and contingent designation types correctly enforced and correctly changed when required.",
    "Plans requiring a beneficiary correctly block submission without one, and plans that do not require a beneficiary correctly allow submission without one.",
    "Beneficiary details correctly updated after enrollment is already active.",
    "Deliberately invalid, duplicate or unauthorized submissions raised the expected validation rather than being silently accepted."
  ],
  "validation_checkpoints": [
    "Beneficiary record correctly created with masked test data.",
    "Allocation percentages correctly validated to sum to 100% where required.",
    "Primary/contingent designation correctly enforced.",
    "Plans requiring a beneficiary correctly block submission without one.",
    "Duplicate beneficiaries correctly blocked.",
    "Unauthorized access to beneficiary data correctly blocked."
  ]
}