{
  "test_id": "ORCL.HCM.ABS.ENTRY",
  "scenario_name": "Absence Entry",
  "application": "Oracle Fusion Cloud",
  "product": "HCM",
  "module": "Absence Management",
  "process": "Absence Entry",
  "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-entry/",
  "objective": {
    "intro": "This test validates that Oracle Fusion Absence Management correctly creates and submits an absence request for an eligible worker, using a valid absence type, absence plan, start and end dates, duration and any supporting information the absence type requires.",
    "confirms": [
      "an eligible worker can enter an absence request for a valid absence type and plan",
      "start date, end date and duration are captured and calculated correctly",
      "the request correctly reflects the available balance for the selected absence plan",
      "reason and certification information, where required, are captured on the request",
      "the absence request is created with the expected status once submitted",
      "approval routing is initiated where the absence type is configured to require approval"
    ],
    "scope_note": "This scenario covers absence entry generically across the range of configured absence types, plans and durations — no single absence type is treated as the sole focus of this test. Downstream approval decisions, balance recalculation and absence reporting are covered by separate test scenarios within the same Absence Management area."
  },
  "preconditions": [
    "The worker is active and eligible to enter absences under the applicable absence plan.",
    "The required absence types and absence plans are configured and available to the worker.",
    "The worker's work schedule and absence plan enrollment are set up correctly.",
    "Where required, an available balance exists for the selected absence plan.",
    "The test user has the appropriate role and access to enter an absence, either through self-service or on behalf of a worker.",
    "Absence approval configuration, where applicable, is set up for the selected absence type."
  ],
  "test_data": [
    {
      "field": "Worker",
      "example": "${WORKER}"
    },
    {
      "field": "Legal Employer",
      "example": "${LEGAL_EMPLOYER}"
    },
    {
      "field": "Absence Type",
      "example": "${ABSENCE_TYPE}"
    },
    {
      "field": "Absence Plan",
      "example": "${ABSENCE_PLAN}"
    },
    {
      "field": "Start Date",
      "example": "${START_DATE}"
    },
    {
      "field": "End Date",
      "example": "${END_DATE}"
    },
    {
      "field": "Duration",
      "example": "${DURATION}"
    },
    {
      "field": "Work Schedule",
      "example": "${WORK_SCHEDULE}"
    },
    {
      "field": "Available Balance",
      "example": "${BALANCE}"
    },
    {
      "field": "Reason",
      "example": "${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 access to enter an absence request.",
      "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 a new absence request.",
      "test_data": "",
      "expected_result": "The Absence Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Select the Worker and Absence Type",
      "action": "Select the eligible worker and choose a valid absence type and absence plan for the request.",
      "test_data": "${WORKER} / ${LEGAL_EMPLOYER} / ${ABSENCE_TYPE} / ${ABSENCE_PLAN}",
      "expected_result": "The selected absence type and plan are accepted as valid for the worker.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Enter Start Date, End Date and Duration",
      "action": "Enter the absence start date, end date and duration, referencing the worker's work schedule where relevant.",
      "test_data": "${START_DATE} / ${END_DATE} / ${DURATION} / ${WORK_SCHEDULE}",
      "expected_result": "Dates and duration are accepted and calculated consistently with the entered values.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Review Absence Balance Impact",
      "action": "Review the available balance for the selected absence plan and the impact the requested absence has on that balance.",
      "test_data": "${BALANCE}",
      "expected_result": "The displayed balance impact is consistent with the requested duration and the available balance.",
      "validation_type": "business_assertion",
      "note": "This is a central business assertion for this scenario. Illustrative example only, not a real balance calculation: if ${BALANCE}=15 days and ${DURATION}=3 days, the remaining balance after the request should reflect 12 days. Test execution is designed to use ${PLACEHOLDER} tokens rather than real balance figures, and this page does not publish any customer-specific balance formula as fact."
    },
    {
      "step_number": 6,
      "step_name": "Provide Reason and Certification Where Required",
      "action": "Enter a reason for the absence and attach or reference certification where the absence type requires it.",
      "test_data": "${REASON}",
      "expected_result": "Reason and, where required, certification information are captured on the request.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Submit the Absence Request",
      "action": "Submit the absence request for processing.",
      "test_data": "",
      "expected_result": "The absence request is submitted without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Status and Approval Routing",
      "action": "Verify the resulting status of the absence request and confirm approval routing has been initiated where the absence type is configured to require approval.",
      "test_data": "",
      "expected_result": "The absence request reflects the expected status, and approval routing is initiated where configured.",
      "validation_type": "action"
    }
  ],
  "expected_results": [
    "The absence request is created successfully for the eligible worker.",
    "Start date, end date and duration are recorded correctly.",
    "The selected absence type and plan are recorded correctly.",
    "The available balance correctly reflects the requested absence.",
    "The absence request reflects the expected status once submitted.",
    "Approval routing is initiated where the absence type is configured to require approval."
  ],
  "validation_checkpoints": [
    "Absence request created correctly.",
    "Dates and duration correct.",
    "Absence type correct.",
    "Balance impact correct.",
    "Status correct.",
    "Approval initiated where configured."
  ]
}