{
  "test_id": "ORCL.HCM.COMP.INDIVIDUAL",
  "scenario_name": "Individual Compensation",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Compensation",
  "process": "Individual Compensation",
  "business_flow": "Compensation-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/compensation/individual-compensation/",
  "objective": {
    "intro": "This test validates one-time and recurring individual compensation awards, allowances and adjustments made for a worker outside a formal compensation cycle, without hard-coding any specific dollar figure as a universal amount or limit.",
    "confirms": [
      "one-time and recurring individual compensation awards can be added, updated, future-dated and end-dated for a worker outside a formal compensation cycle",
      "eligibility rules configured for the compensation plan are correctly enforced before an award is entered",
      "award amounts are correctly validated against configured minimum and maximum limits",
      "awards correctly route for approval where required, and apply directly where approval is not required",
      "approved awards are correctly reflected in payroll and compensation history",
      "deliberately invalid submissions — ineligible worker, invalid or inactive plan, zero/negative amount, amount outside configured limits, missing reason, invalid effective date, unauthorized user — are correctly rejected or flagged rather than silently accepted"
    ],
    "scope_note": "A negative or boundary Individual Compensation scenario passes when Oracle correctly enforces the expected data, eligibility or limit rule; this test does not attempt to certify a specific Oracle application defect, and does not hard-code any specific dollar figure as a universal limit — configured minimum and maximum amounts depend entirely on customer-specific Oracle Fusion 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 26 individual Individual Compensation scenarios as a single comprehensive reference rather than as separate indexable pages."
  },
  "preconditions": [
    "Oracle Fusion Compensation access is available to the test user.",
    "A representative ${WORKER} with an active assignment eligible for individual compensation is available.",
    "A configured ${COMPENSATION_PLAN}, including its eligibility rules and minimum/maximum award limits (${LIMIT_MIN} / ${LIMIT_MAX}), is available.",
    "Valid ${AWARD_TYPE} values, covering one-time, recurring, bonus-type and allowance awards where configured, are available.",
    "A ${MANAGER} test user with the appropriate Compensation security access is available.",
    "A configured approval rule for individual compensation awards meeting or not meeting the approval criteria is in place.",
    "A user without the required Compensation security access is available for security testing, and an inactive ${COMPENSATION_PLAN} is available for negative testing."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Compensation Plan",
      "example": "${COMPENSATION_PLAN}"
    },
    {
      "field": "Award Type",
      "example": "${AWARD_TYPE}"
    },
    {
      "field": "Award Amount",
      "example": "${AWARD_AMOUNT}"
    },
    {
      "field": "Minimum Limit",
      "example": "${LIMIT_MIN}"
    },
    {
      "field": "Maximum Limit",
      "example": "${LIMIT_MAX}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    },
    {
      "field": "End Date",
      "example": "${END_DATE}"
    },
    {
      "field": "Change Reason",
      "example": "${CHANGE_REASON}"
    }
  ],
  "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 Compensation 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 the Worker's Compensation Record",
      "action": "Navigate to the individual compensation record for the target worker within Oracle Fusion HCM Compensation.",
      "test_data": "${WORKER}",
      "expected_result": "The worker's compensation record opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select the Compensation Plan and Award Type",
      "action": "Select the compensation plan and award type for the individual award.",
      "test_data": "${COMPENSATION_PLAN} / ${AWARD_TYPE}",
      "expected_result": "The plan and award type are selected correctly, reflecting the plan's configured eligibility rules.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Enter the Amount and Effective Date with a Reason",
      "action": "Enter the award amount, effective date and change reason for the individual award.",
      "test_data": "${AWARD_AMOUNT} / ${EFFECTIVE_DATE} / ${CHANGE_REASON}",
      "expected_result": "The amount, effective date and reason are recorded correctly, or the expected validation is displayed for a deliberately invalid entry.",
      "validation_type": "action",
      "note": "Configured minimum and maximum limits, and required-reason rules, depend entirely on customer-specific Oracle Fusion Compensation configuration."
    },
    {
      "step_number": 5,
      "step_name": "Submit for Approval Where Required",
      "action": "Submit the award for approval according to the configured approval rule.",
      "test_data": "",
      "expected_result": "The award routes to the required approver, applies directly where approval is not required, or a deliberately invalid submission is rejected with the expected validation.",
      "validation_type": "action",
      "note": "Exact approval requirement depends on the customer's own configured approval rule for individual compensation."
    },
    {
      "step_number": 6,
      "step_name": "Verify the Award Recorded Correctly",
      "action": "Confirm that the award is recorded correctly against the compensation plan with the correct amount, award type and effective date.",
      "test_data": "",
      "expected_result": "The recorded award correctly matches the submitted plan, amount, type and effective date, or the expected validation for an invalid submission.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario across the full catalog of 26 Individual Compensation variations."
    },
    {
      "step_number": 7,
      "step_name": "Verify Payroll and History Reflect the Award",
      "action": "Confirm that the award is reflected in the next payroll run and retained correctly in compensation history.",
      "test_data": "",
      "expected_result": "Payroll and compensation history accurately reflect the award, including after subsequent updates or end-dating.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "Each individual compensation award recorded correctly with the intended plan, award type, amount and effective date.",
    "Eligibility correctly enforced for the worker and compensation plan before the award is entered.",
    "Award amount correctly validated against configured minimum and maximum limits.",
    "Approval correctly routed where required, and applied directly where not required.",
    "Approved awards correctly reflected in the next payroll run.",
    "Deliberately invalid submissions raised the expected data, eligibility, limit or security validation rather than being silently accepted."
  ],
  "validation_checkpoints": [
    "Award correctly recorded against the intended plan and effective date.",
    "Eligibility correctly enforced before award creation.",
    "Amount correctly validated against configured limits.",
    "Approval correctly routed where required.",
    "Payroll correctly reflects the award.",
    "Compensation history correctly retained after updates or end-dating."
  ]
}