Oracle ERP Testing Tool > Test Library > HCM > Absence Management

Syntra Standard Oracle Test Library

Oracle Fusion Absence Entry Test Cases

Validate creation and submission of an absence request in Oracle Fusion HCM Absence Management, confirming that an eligible worker, valid absence type, dates, duration and any required supporting information produce a correctly recorded absence with the expected balance impact and approval routing.

Test ID	ORCL.HCM.ABS.ENTRY
Application	Oracle Fusion Cloud
Product	HCM
Module	Absence Management
Process	Absence Entry
Business Flow	Workforce Management
Scenario Type	Positive / Functional
Test Usage	Functional Testing / Regression Testing / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard

Note on test design: SyntraFlow executes the detailed Oracle Fusion Absence Management UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 8 business-readable test steps; SyntraFlow's automation executes approximately 18 underlying Oracle Fusion UI actions to complete it.

Test Objective

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.

The scenario should confirm that:

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

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.

When to Use This Test

Functional testing of absence entry for a new Oracle Fusion HCM Absence Management implementation
Regression testing of absence entry after an Oracle quarterly update affecting Absence Management
UAT sign-off for absence entry across absence types, plans and worker types before go-live
Verification after absence-type, absence-plan or eligibility-configuration changes

Where This Test Fits in the Absence Management Process

Absence Entry

→

Absence Validation

→

Absence Approval

→

Absence Balance

→

Absence Reporting

This test covers creating and submitting an absence request for an eligible worker. It is the starting point of the Absence Management flow and precedes validation of the entered data, approval routing where configured, and the resulting balance update.

Next Stage →

Absence Validation

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.

Exact absence-type eligibility, mandatory fields and approval behavior vary by customer absence-plan configuration and legislation; not every field or absence type applies to every worker.

Sample Test Data

Worker	${WORKER}
Legal Employer	${LEGAL_EMPLOYER}
Absence Type	${ABSENCE_TYPE}
Absence Plan	${ABSENCE_PLAN}
Start Date	${START_DATE}
End Date	${END_DATE}
Duration	${DURATION}
Work Schedule	${WORK_SCHEDULE}
Available Balance	${BALANCE}
Reason	${REASON}

Sample values are illustrative ${PLACEHOLDER} tokens, not real worker data. Replace them with valid worker, absence-type and absence-plan data from the target Oracle Fusion environment; SyntraFlow never publishes real or realistic worker or balance data.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~18 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.

#	User Action	Expected Result
1	Sign In to Oracle Fusion HCM Sign in to Oracle Fusion Cloud with a user account that has access to enter an absence request.	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to Absence Management Navigate to the Absence Management area used to enter a new absence request.	The Absence Management work area opens successfully.
3	Select the Worker and Absence Type Select the eligible worker and choose a valid absence type and absence plan for the request. ${WORKER} / ${LEGAL_EMPLOYER} / ${ABSENCE_TYPE} / ${ABSENCE_PLAN}	The selected absence type and plan are accepted as valid for the worker.
4	Enter Start Date, End Date and Duration Enter the absence start date, end date and duration, referencing the worker's work schedule where relevant. ${START_DATE} / ${END_DATE} / ${DURATION} / ${WORK_SCHEDULE}	Dates and duration are accepted and calculated consistently with the entered values.
5	Review Absence Balance ImpactBusiness assertion Review the available balance for the selected absence plan and the impact the requested absence has on that balance. ${BALANCE} 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.	The displayed balance impact is consistent with the requested duration and the available balance.
6	Provide Reason and Certification Where Required Enter a reason for the absence and attach or reference certification where the absence type requires it. ${REASON}	Reason and, where required, certification information are captured on the request.
7	Submit the Absence Request Submit the absence request for processing.	The absence request is submitted without unexpected errors.
8	Verify Status and Approval Routing Verify the resulting status of the absence request and confirm approval routing has been initiated where the absence type is configured to require approval.	The absence request reflects the expected status, and approval routing is initiated where configured.

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.

Key Validation Checkpoints

Absence request created correctly.
Dates and duration correct.
Absence type correct.
Balance impact correct.
Status correct.
Approval initiated where configured.

Core Business Scenario

Absence Entry

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core Absence Entry scenario. Jarvis AI can extend this scenario by generating additional positive and negative absence-entry variations across absence types, durations and worker types using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate absence-entry test for every absence type, duration pattern and eligibility condition. Jarvis uses the standard Absence Entry scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Worker and Absence Type Confirmed

An eligible worker, valid absence type and absence plan are confirmed for the request.

Enter Absence Request

Start date, end date and duration are entered for the absence.

Review Balance Impact

The available balance and the impact of the requested absence are reviewed.

Provide Supporting Information

Reason and certification, where required, are captured on the request.

Submit and Confirm Status

The request is submitted and the resulting status and approval routing are confirmed.

Regression Pack

Selected absence-entry variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Rather than maintaining a separate test for every absence type, plan, duration and worker type, SyntraFlow maintains one core Absence Entry scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Absence Entry business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to HCM Absence Management.

Positive Scenarios

Annual leave entry
Sick leave entry
Unpaid leave entry
Single-day absence
Multi-day absence
Partial-day absence where supported
Future-dated absence
Absence within available balance

Negative Scenarios

Worker not eligible for the absence type
Invalid absence type
Insufficient balance
Overlapping absence
Invalid dates
End date before start date
Missing mandatory reason
Certification required but missing

These are representative examples only. Negative scenarios and expected behavior can depend on the customer's Oracle Fusion Absence Management configuration, absence-plan rules and legislation — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely reflects the workers, absence plans and balances configured in a real Oracle Fusion Absence Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct absence-entry scenarios relevant to the customer's actual implementation.

Standard Library Definition

Worker              ${WORKER}
Legal Employer      ${LEGAL_EMPLOYER}
Absence Type        ${ABSENCE_TYPE}
Absence Plan        ${ABSENCE_PLAN}
Start Date          ${START_DATE}
End Date            ${END_DATE}
Duration            ${DURATION}
Work Schedule       ${WORK_SCHEDULE}
Available Balance   ${BALANCE}
Reason              ${REASON}

DataVault

Workers
  Eligible workers, work schedules and legal employer assignments
Absence Plans
  Configured absence types, plans and eligibility rules
Balances
  Available balance per worker and absence plan (masked)
Approvers
  Manager and approval-hierarchy data used for routing
Calendars
  Work schedule and legislation-specific calendar data

Jarvis AI Generates

Scenario 01 — Annual Leave, Single-Day Absence
Scenario 02 — Sick Leave, Multi-Day Absence
Scenario 03 — Unpaid Leave, Future-Dated
Scenario 04 — Partial-Day Absence Where Supported
Scenario 05 — Overlapping Absence Request
Scenario 06 — Insufficient Balance
...

Absence test data can include sensitive information such as worker, balance and certification data. SyntraFlow test scenarios use ${PLACEHOLDER} tokens for masked or placeholder worker and absence data rather than real worker records, and where DataVault masking and privacy controls are configured, they apply to the underlying customer test data used to generate variations of this scenario. See /datavault/ and /datavault/data-masking/ for more detail on DataVault privacy and masking controls.

Example Test Variations

Representative examples of Absence Entry scenarios Jarvis can generate from this business scenario, spanning absence type, duration and eligibility conditions. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
VAR-001	Annual Leave Entry	Positive/Absence Type	Standard entry for an annual leave absence type within available balance	Syntra Ready
VAR-002	Sick Leave Entry	Positive/Absence Type	Entry for a sick leave absence type, including certification where required	Syntra Ready
VAR-003	Unpaid Leave Entry	Positive/Absence Type	Entry for an unpaid leave absence type with no balance deduction expected	Syntra Ready
VAR-004	Single-Day Absence	Positive/Duration	Start date and end date are the same calendar day	Syntra Ready
VAR-005	Multi-Day Absence	Positive/Duration	Absence spans multiple consecutive calendar days	Syntra Ready
VAR-006	Partial-Day Absence Where Supported	Positive/Duration	A portion of a single day is entered as the absence duration where the absence type supports it	Syntra Ready
VAR-007	Future-Dated Absence	Positive	Absence request is entered with a start date in the future	Syntra Ready
VAR-008	Absence Within Available Balance	Positive	Requested duration is confirmed to remain within the worker's available balance	Syntra Ready
VAR-009	Worker Not Eligible	Negative	Worker is not eligible for the selected absence type or plan	Syntra Ready
VAR-010	Invalid Absence Type	Negative/Absence Type	An absence type not configured or not applicable to the worker is selected	Syntra Ready
VAR-011	Insufficient Balance	Negative	Requested duration exceeds the worker's available balance for the absence plan	Syntra Ready
VAR-012	Overlapping Absence	Negative/Duration	Requested dates overlap an existing approved absence for the worker	Syntra Ready
VAR-013	Invalid Dates	Negative/Duration	Start or end date falls outside a valid or permitted range	Syntra Ready
VAR-014	End Date Before Start Date	Negative/Duration	The entered end date precedes the entered start date	Syntra Ready
VAR-015	Missing Mandatory Reason	Negative	Reason field is left blank where the absence type requires it	Syntra Ready
VAR-016	Certification Required But Missing	Negative	Absence type requires certification, but no certification is provided on submission	Syntra Ready

Positive and Negative Absence Entry Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion Absence Management correctly creates and submits an absence request when the worker, absence type, dates, duration and supporting information are all valid.

Eligible Worker + Valid Absence Type + Valid Dates and Duration → Absence Request Created and Submitted Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around eligibility, balance, dates, overlaps and required supporting information during absence entry.

Worker Not Eligible → Expected Eligibility Validation
Invalid Absence Type → Expected Type Validation
Insufficient Balance → Expected Balance Validation
Overlapping Absence → Expected Overlap Validation
Missing Mandatory Reason → Expected Data Validation
Unauthorized User → Expected Access Restriction

An absence negative scenario passes when Oracle correctly enforces the expected eligibility, balance, date or security rule.

Scenario	Oracle Outcome	Test Result
Valid annual leave	Request accepted	PASS
Insufficient balance	Balance validation appears	PASS
Overlapping absence	Overlap validation appears	PASS
Unauthorized user	Access prevented	PASS
Unexpected system exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated absence-entry scenarios and group them into reusable execution packs.

HCM Absence Entry Regression Pack

Annual Leave Entry
Sick Leave Entry
Unpaid Leave Entry
Single-Day Absence
Multi-Day Absence
Partial-Day Absence Where Supported
Future-Dated Absence
Absence Within Available Balance
Worker Not Eligible
Insufficient Balance
Overlapping Absence
Missing Mandatory Reason

Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute selected Absence Entry scenarios individually or as a batch. Users can schedule regression packs according to their absence-management processing cycle.

Once scheduled, SyntraFlow executes the selected absence-entry scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore payroll closeAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	HCM Absence Entry Regression Pack
Schedule	Nightly Regression
Tests	16 scenarios
Execution	Batch Mode
Start	10:00 PM
Environment	Oracle Fusion TEST
Status	Scheduled

Illustrative example — not a live schedule.

Review Results Across the Entire Test Pack

Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.

Illustrative example data — not actual production metrics.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

DataVault HCM Persona

Rather than generating absence-entry variations from disconnected field values, Jarvis can draw on a DataVault persona — a pre-grouped, mutually consistent set of worker, plan and balance dimensions representative of a real worker profile, keeping worker, plan, eligibility, balance and approval data logically consistent.

Persona: Full-Time Salaried Employee

Worker Status	Active
Legal Employer	${LEGAL_EMPLOYER}
Work Schedule	Mon-Fri
Absence Plan	Annual Leave
Available Balance	${BALANCE}
Manager	${MANAGER}

DataVault personas group dependent absence dimensions, such as worker status, legal employer, work schedule, absence plan, available balance and manager, so Jarvis generates coherent, internally consistent absence-entry scenarios rather than arbitrary and potentially invalid field combinations.

Security & Persona Variations

Oracle Fusion Absence Management role and security configuration is customer-specific, so SyntraFlow can exercise Absence Entry under different personas to confirm the customer's own access model behaves as expected, rather than assuming a universal Oracle security model.

Persona	Action	Expected	Syntra Result
Employee	Enter Own Absence via Self-Service	Allowed where configured	PASS
HR Specialist	Enter Absence on Behalf of Worker	Allowed	PASS
Unauthorized User	Attempts Absence Entry	Access prevented	PASS

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the Absence Entry scenario, available DataVault test data and expected business outcomes to generate additional absence-entry coverage for the customer's environment.

Generate

Positive and negative variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run scenarios autonomously.

Schedule

Execute unattended test batches.

Validate

Evaluate expected business outcomes.

How SyntraFlow Automates This Test

The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.

Standard Test — Enter Annual Leave, 8 Business Steps

↓

DataVault Persona — Worker + Plan + Balance + Dates + Manager

↓

Jarvis AI — Generate Positive + Negative + Eligibility + Boundary Variations

↓

Regression Pack — Select Relevant Coverage

↓

SyntraFlow Execution — Each Variation

↓

Detailed UI Actions

↓

Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Select the Worker and Absence Type

May internally include

Search Worker → Select Worker → Open Absence Type List → Select Absence Type → Select Absence Plan

Business Step

Review Absence Balance Impact

May internally include

Read Available Balance → Read Requested Duration → Compare Balance Before vs. Balance After Request

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the business outcome — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. When a step or business assertion fails, SyntraFlow's evidence is intended to help classify the likely cause, for example DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR, rather than assuming a defect. For example: Absence Entry failed — Likely category: DATA_ERROR — Evidence: the requested absence overlaps an existing approved absence — Recommended action: verify existing absence records before resubmitting. A failure should not be labeled as an Oracle application defect without supporting evidence; most failures trace back to test data, configuration or environment conditions.

Step	Action Status	Business Validation
Enter Start Date, End Date and Duration	Pass	—
Submit the Absence Request	Pass	—
Review Absence Balance Impact	Pass	Pass

Related Absence Management Tests

Part of the same Oracle Fusion Absence Management flow within Workforce Management. Linked cards are live; explore adjacent absence scenarios below.

Absence Approval Absence Balance Absence Validation

Turn This Standard Test into Your Oracle HCM Absence Entry Regression Suite

Start with the Syntra Standard Absence Entry test, use DataVault to provide environment-specific worker, plan and balance data, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore HCM Absence Management Test Library

Use This Oracle Fusion Test Case

Download Test Case

Excel, CSV or JSON export.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

Oracle ERP Testing Tool Test Library HCM Test Library Absence Management Test Library Syntra DataVault DataVault Data Masking

Frequently Asked Questions

How does absence type and absence plan eligibility work?

Available absence types and absence plans depend on the worker's eligibility, work schedule and legal employer configuration in Oracle Fusion. SyntraFlow's standard test selects a valid absence type and plan for the eligible worker, and Jarvis can generate variations that exercise eligible and ineligible combinations using the customer's own configuration.

What is the difference between self-service and HR entry for an absence?

An employee can typically enter their own absence through self-service, while an HR specialist or manager may be permitted to enter an absence on a worker's behalf where security allows it. SyntraFlow can exercise both entry paths as separate persona-based variations of this scenario.

How is an overlapping absence handled?

Where a requested absence overlaps an existing approved absence, Oracle Fusion is expected to surface an overlap validation rather than allow the duplicate request. SyntraFlow treats a correctly surfaced overlap validation as a passing negative test outcome.

What do the failure-intelligence categories mean?

SyntraFlow evidence is intended to help classify a failed absence entry into categories such as DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR. A failure should not be labeled as an Oracle application defect without supporting evidence.

How is security tested for absence entry?

SyntraFlow can exercise Absence Entry under different personas, such as an Employee, an HR Specialist entering on behalf of a worker, or an unauthorized user, to confirm Oracle correctly allows or prevents access. Oracle Fusion roles and security are configured per customer, so actual behavior depends on the customer's own security model.