{
  "test_id": "ORCL.HCM.E2E.COMP2PAY",
  "scenario_name": "Compensation-to-Pay",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "End-to-End HCM",
  "process": "Compensation-to-Pay",
  "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/compensation-to-pay/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Oracle Fusion Compensation-to-Pay journey — salary/compensation change, approval, worker compensation update, payroll, retro pay where applicable, prepayments and payment — with emphasis on approved compensation changes correctly reflecting in the payroll calculation and, for backdated changes, correctly triggering a retro adjustment. 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 Salary Change, Individual Compensation, Bonus Allocation, Compensation Approval, Payroll Calculation, Payroll Processing, Retro Pay, Prepayments, Payment Processing and Costing pages. Instead, it links to those live pages and adds scenarios that specifically test the hand-offs and continuity between compensation and pay.",
    "confirms": [
      "the salary/compensation change, approval, worker compensation, payroll, retro, prepayments and payment data correctly carry forward from one stage to the next",
      "approved compensation changes correctly reflect in the payroll calculation for the current pay period",
      "backdated compensation changes correctly trigger a retro adjustment for the affected periods",
      "unapproved compensation changes correctly do not affect payroll",
      "terminated workers are correctly excluded from compensation changes effective after termination",
      "Oracle correctly enforces validation when data errors, configuration errors, security restrictions or missing upstream approvals 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 Compensation 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 Compensation-to-Pay journey in Oracle Fusion Cloud HCM TEST/UAT environments and does not cover off-cycle payroll adjustments or manual payments made outside the standard payroll cycle, which are covered by separate Payroll scenarios outside this journey."
  },
  "preconditions": [
    "A worker ${WORKER} is active in the target Oracle Fusion environment, assigned to grade ${GRADE} with a current salary of ${CURRENT_SALARY} and reporting to approver ${MANAGER}.",
    "Compensation is configured for salary basis, grade ranges and approval hierarchies applicable to ${WORKER}.",
    "Payroll ${PAYROLL} is configured for pay period ${PAY_PERIOD}, including the payroll elements, prepayment and payment methods relevant to the journey.",
    "Retro processing and costing are configured in the target environment for backdated compensation changes.",
    "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": "Current Salary",
      "example": "${CURRENT_SALARY}"
    },
    {
      "field": "New Salary",
      "example": "${NEW_SALARY}"
    },
    {
      "field": "Grade",
      "example": "${GRADE}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    },
    {
      "field": "Payroll",
      "example": "${PAYROLL}"
    },
    {
      "field": "Pay Period",
      "example": "${PAY_PERIOD}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Submit the Salary or Compensation Change",
      "action": "Submit a salary or compensation change from ${CURRENT_SALARY} to ${NEW_SALARY} for ${WORKER} effective ${EFFECTIVE_DATE}, using the linked Salary Change, Individual Compensation and Bonus Allocation scenarios.",
      "test_data": "${WORKER} / ${NEW_SALARY}",
      "expected_result": "The compensation change is correctly submitted and recorded pending approval.",
      "validation_type": "action",
      "note": "This step orchestrates the Salary Change, Individual Compensation and Bonus Allocation family pages rather than repeating their individual field-level test coverage."
    },
    {
      "step_number": 2,
      "step_name": "Route for Approval",
      "action": "Route the submitted compensation change for ${WORKER} to approver ${MANAGER}, using the linked Compensation Approval scenario.",
      "test_data": "${MANAGER}",
      "expected_result": "The change correctly routes for approval per the configured approval hierarchy.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Verify the Approved Change Reflects on Worker Compensation",
      "action": "Confirm the approved compensation change for ${WORKER} correctly updates the worker's compensation record with new salary ${NEW_SALARY} effective ${EFFECTIVE_DATE}.",
      "test_data": "${NEW_SALARY} / ${EFFECTIVE_DATE}",
      "expected_result": "The approved change is correctly reflected on the worker's assignment and compensation record.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Run Payroll and Verify It Picks Up the Change",
      "action": "Run payroll for ${PAYROLL} in ${PAY_PERIOD}, using the linked Payroll Calculation and Payroll Processing scenarios, confirming the payroll salary basis correctly reflects new salary ${NEW_SALARY} for ${WORKER}.",
      "test_data": "${PAYROLL} / ${PAY_PERIOD}",
      "expected_result": "Payroll correctly picks up the approved compensation change for the current pay period.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Verify Retro Calculation for Backdated Changes",
      "action": "For a backdated compensation change effective ${EFFECTIVE_DATE}, verify Retro Pay correctly generates and calculates a retro adjustment for ${WORKER}, using the linked Retro Pay scenario.",
      "test_data": "${EFFECTIVE_DATE}",
      "expected_result": "Retro pay is correctly generated and calculated for the affected periods where the change is backdated.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Generate Prepayments",
      "action": "Generate prepayments for ${PAYROLL} in ${PAY_PERIOD}, using the linked Prepayments scenario, confirming prepayment records for ${WORKER} correctly reflect the approved compensation.",
      "test_data": "${PAYROLL}",
      "expected_result": "Prepayments are correctly generated reflecting the approved compensation and any retro adjustment.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Payment Amount and Costing",
      "action": "Trace the payment issued to ${WORKER} for ${PAY_PERIOD}, using the linked Payment Processing and Costing scenarios, to confirm the payment amount and costing correctly reflect the approved compensation change end-to-end.",
      "test_data": "",
      "expected_result": "The payment amount and costing correctly reflect the approved compensation change, with the full salary-change-to-payment chain correctly linked end-to-end.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly approved compensation change reflected in payroll, retro where applicable, and payment is the expected pass condition, not merely a successful submission."
    }
  ],
  "expected_results": [
    "The salary/compensation change, approval, worker compensation, payroll, retro, prepayments and payment data are correctly linked end-to-end.",
    "Approved compensation changes correctly reflect in the payroll calculation for the current pay period.",
    "Backdated compensation changes correctly trigger a retro adjustment for the affected periods.",
    "Unapproved compensation changes correctly do not affect payroll.",
    "Prepayments and payment amounts correctly reflect the approved compensation change and any retro adjustment.",
    "Terminated workers are correctly excluded from changes effective after termination, and unauthorized actions at any stage of the journey are correctly blocked."
  ],
  "validation_checkpoints": [
    "Approved compensation change correctly reflects on the worker's assignment.",
    "Payroll salary basis correctly reflects the approved change.",
    "Backdated changes correctly trigger retro for the affected periods.",
    "Unapproved changes correctly do NOT affect payroll.",
    "Costing correctly updates to reflect the new compensation.",
    "Terminated workers correctly excluded from changes effective after termination."
  ]
}