{
  "test_id": "ORCL.HCM.ABS.VALIDATE",
  "scenario_name": "Absence Validation",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Absence Management",
  "process": "Absence Validation",
  "business_flow": "Workforce Management",
  "scenario_type": "Negative / Exception Handling",
  "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-validation/",
  "objective": {
    "intro": "This test validates Oracle Fusion absence business rules and confirms expected handling of ineligible, overlapping, insufficient-balance, date and configuration conditions across the eligibility, balance, dates, documentation/certification, security and configuration validation categories.",
    "confirms": [
      "the deliberately invalid eligibility, balance, dates, documentation/certification, security or configuration condition is correctly rejected or flagged rather than silently accepted",
      "the resulting validation message matches the expected classification for the category triggered",
      "absence status correctly reflects the blocked state rather than indicating a successful transaction",
      "no partial or inconsistent balance state results from a blocked transaction",
      "retrying the transaction after the triggering condition is corrected completes successfully",
      "audit/history evidence reflects both the attempted and corrected transaction"
    ],
    "scope_note": "A negative absence scenario passes when Oracle correctly raises the expected validation. This scenario does not attempt to certify a specific Oracle application defect. Where a validation appears unexpected or its cause is unclear, it is treated as requiring further investigation and supporting evidence rather than a confirmed conclusion. As the sixth and final page in the Absence Management cluster, this scenario aggregates exception coverage across every validation category rather than introducing a new business process."
  },
  "preconditions": [
    "Oracle Fusion HCM Absence Management access is available to the test user.",
    "Test data exists, or can be constructed via Syntra DataVault, to trigger each of the six validation categories — eligibility, balance, dates, documentation/certification, security and configuration.",
    "A worker profile with configurable employment status, absence plan enrollment and available balance is available for eligibility and balance exception construction.",
    "Absence types that require certification are configured so a missing or invalid documentation condition can be reproduced.",
    "At least one manager or HR persona without access to the target worker is available for security exception construction.",
    "The test user, or Syntra DataVault, can reproduce or observe exception conditions across all six validation categories."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Absence Plan",
      "example": "${ABSENCE_PLAN}"
    },
    {
      "field": "Absence Type",
      "example": "${ABSENCE_TYPE}"
    },
    {
      "field": "Employment Status",
      "example": "${EMPLOYMENT_STATUS}"
    },
    {
      "field": "Available Balance",
      "example": "${AVAILABLE_BALANCE}"
    },
    {
      "field": "Start Date",
      "example": "${START_DATE}"
    },
    {
      "field": "End Date",
      "example": "${END_DATE}"
    },
    {
      "field": "Certification",
      "example": "${CERTIFICATION}"
    },
    {
      "field": "Work Schedule",
      "example": "${WORK_SCHEDULE}"
    },
    {
      "field": "User Role",
      "example": "${USER_ROLE}"
    }
  ],
  "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 access to Absence Management.",
      "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 Absence Management area used to enter or review an absence transaction.",
      "test_data": "",
      "expected_result": "The Absence Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Construct a Scenario Expected to Trigger a Validation Exception",
      "action": "Construct an absence scenario that deliberately carries a condition expected to trigger a validation exception — for example an ineligible worker, insufficient balance, overlapping dates, missing certification or unauthorized access.",
      "test_data": "${WORKER} / ${EMPLOYMENT_STATUS} / ${ABSENCE_PLAN} / ${AVAILABLE_BALANCE}",
      "expected_result": "The constructed scenario reflects the deliberately invalid condition under test.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as selecting the worker, entering the deliberately invalid field values and preparing the transaction for submission."
    },
    {
      "step_number": 4,
      "step_name": "Attempt the Action at the Relevant Validation Category",
      "action": "Attempt the absence action at the relevant validation category — eligibility, balance, dates, documentation/certification or security.",
      "test_data": "${ABSENCE_TYPE} / ${START_DATE} / ${END_DATE} / ${CERTIFICATION} / ${USER_ROLE}",
      "expected_result": "Oracle Fusion processes the request against the validation condition rather than silently accepting it.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Capture the Resulting System Message",
      "action": "Capture the exception, error or validation message returned by Oracle Fusion at the point the condition is triggered.",
      "test_data": "",
      "expected_result": "A validation, error or exception message is displayed or logged for the transaction.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify the Message Matches the Expected Validation",
      "action": "Compare the observed message against the expected validation classification for the category under test.",
      "test_data": "",
      "expected_result": "The observed message matches the expected classification for the triggered condition.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Correct the Triggering Condition",
      "action": "Correct the underlying condition that triggered the validation — for example select an eligible plan, adjust the balance, correct the dates, attach the required certification, or reassign the action to an authorized user.",
      "test_data": "",
      "expected_result": "The triggering condition is corrected and the transaction is ready for resubmission.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Retry the Transaction",
      "action": "Resubmit the corrected absence transaction.",
      "test_data": "",
      "expected_result": "The transaction is resubmitted without the previously triggered validation.",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Verify Successful Completion After Correction",
      "action": "Confirm that the corrected transaction completes successfully and that absence status, balance and audit/history evidence accurately reflect both the original attempt and the corrected outcome.",
      "test_data": "",
      "expected_result": "The corrected transaction completes successfully; absence status, balance and audit/history evidence accurately reflect the attempted and corrected transaction.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — a correctly detected and correctly recoverable validation is a passing test, not a failure."
    }
  ],
  "expected_results": [
    "Each validation category correctly rejects or flags its deliberately invalid condition.",
    "The resulting message matches the expected classification for the category triggered.",
    "No partial or inconsistent balance state results from a blocked transaction.",
    "Absence status accurately reflects the blocked state rather than indicating success.",
    "Retrying the transaction after correction completes successfully.",
    "Audit/history evidence reflects both the attempted and corrected transaction."
  ],
  "validation_checkpoints": [
    "Each exception condition raises the correct, specific validation message.",
    "No partial or inconsistent balance state results from a blocked transaction.",
    "Absence status accurately reflects the blocked state.",
    "Retry after correction succeeds.",
    "Audit/history reflects the attempted and corrected transaction.",
    "Security-restricted workers and managers remain correctly inaccessible to unauthorized users."
  ]
}