{
  "test_id": "ORCL.HCM.ABS.APPROVAL",
  "scenario_name": "Absence Approval",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Absence Management",
  "process": "Absence Approval",
  "business_flow": "Workforce Management",
  "scenario_type": "Positive / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/hcm/absence-management/absence-approval/",
  "objective": {
    "intro": "This test validates that Oracle Fusion Absence Management correctly processes the approval or rejection of a submitted absence request, routing the request to the appropriate approver and applying the resulting decision according to the customer's configured approval rules.",
    "confirms": [
      "the absence request routes to the approver(s) defined by the configured approval rule",
      "an approver can view the full details of the pending absence request",
      "an approval decision (approve or reject) is captured and recorded correctly",
      "approved absences update the worker's absence balance and status appropriately",
      "rejected absences are returned to the worker with the decision reason retained",
      "the approval history for the request is retained for audit purposes"
    ],
    "scope_note": "This scenario validates the core Absence Approval process for a request already submitted and pending action. Absence request entry, balance calculation and withdrawal are covered by separate test scenarios within the same Absence Management module. Approval routing structures vary by customer configuration and are not assumed to follow a single universal rule."
  },
  "preconditions": [
    "An absence request has been submitted by the worker and is pending approval.",
    "The approver(s) required by the configured approval rule have been identified.",
    "The approver has the appropriate role and access to review and act on the pending request.",
    "The absence type and plan applicable to the request are configured.",
    "Where applicable, the worker's absence balance has been calculated for the request period.",
    "The test user has access to the Absence Management approval work area, such as the worklist or approvals inbox."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Absence Request",
      "example": "${ABSENCE_REQUEST}"
    },
    {
      "field": "Absence Type",
      "example": "${ABSENCE_TYPE}"
    },
    {
      "field": "Approver",
      "example": "${APPROVER}"
    },
    {
      "field": "Approval Level",
      "example": "${APPROVAL_LEVEL}"
    },
    {
      "field": "Decision",
      "example": "${DECISION}"
    },
    {
      "field": "Decision Reason",
      "example": "${DECISION_REASON}"
    },
    {
      "field": "Effective Date",
      "example": "${EFFECTIVE_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion Absence Management",
      "action": "Sign in to Oracle Fusion Cloud with a user account that has absence approval 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 Absence Management",
      "action": "Navigate to the approvals work area used to review pending absence requests, such as the worklist or approvals inbox.",
      "test_data": "",
      "expected_result": "The approvals work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Pending Absence Request",
      "action": "Locate the pending absence request awaiting the approver's decision.",
      "test_data": "${WORKER} / ${ABSENCE_REQUEST}",
      "expected_result": "The pending absence request is found in the approver's queue.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Review the Absence Request Details",
      "action": "Review the absence type, requested dates and balance impact of the pending request.",
      "test_data": "${ABSENCE_TYPE} / ${EFFECTIVE_DATE}",
      "expected_result": "The reviewed details match the absence request as submitted by the worker.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Approve or Reject with a Reason",
      "action": "Record an approval or rejection decision for the request at the current approval level, entering a decision reason where required.",
      "test_data": "${DECISION} / ${DECISION_REASON} / ${APPROVER} / ${APPROVAL_LEVEL}",
      "expected_result": "The decision is captured for the approver and approval level.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Submit the Decision",
      "action": "Submit the approval or rejection decision to Oracle Fusion.",
      "test_data": "",
      "expected_result": "The decision is processed without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Status and Balance Impact",
      "action": "Verify that the absence request status reflects the recorded decision, and that the worker's absence balance and notification behave as configured.",
      "test_data": "",
      "expected_result": "The request status is correct for the decision; on approval, the balance is updated appropriately; on rejection, the request is returned to the worker with the decision reason retained.",
      "validation_type": "business_assertion",
      "note": "This is the central business assertion for this scenario. Approval routing, balance impact and notification behavior depend on the customer's configuration and are not assumed to follow a universal rule."
    }
  ],
  "expected_results": [
    "The absence request routes to the correct approver based on the configured approval rule.",
    "The approver can review the complete details of the pending request.",
    "The approval or rejection decision is captured and recorded correctly.",
    "Approved requests update the worker's absence balance and status appropriately.",
    "Rejected requests are returned to the worker with the decision reason retained.",
    "The approval history for the request is retained for audit purposes."
  ],
  "validation_checkpoints": [
    "Correct approver selected based on configured routing.",
    "Approval or rejection status correct.",
    "Approval history retained.",
    "Balance updated appropriately on approval.",
    "Worker notified where configured.",
    "Rejection routes back to worker correctly."
  ]
}