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

Syntra Standard Oracle Test Library

Oracle Fusion Absence Balance Test Cases

Validate absence-plan balance calculation in Oracle Fusion HCM Absence Management, confirming that approved, withdrawn, restored and accrued absence transactions correctly consume or restore a worker's available balance for the selected absence plan.

Test ID	ORCL.HCM.ABS.BALANCE
Application	Oracle Fusion Cloud
Product	HCM
Module	Absence Management
Process	Absence Balance
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 16 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates absence-plan balance calculation in Oracle Fusion Absence Management, confirming that approved absence requests, withdrawals, restorations and accruals correctly affect a worker's available balance for the selected absence plan.

The scenario should confirm that:

the worker's opening balance for the selected absence plan is displayed correctly
an approved absence request correctly consumes the expected amount from available balance
a withdrawn or cancelled absence correctly restores the expected amount to available balance
Opening Balance − Approved Absence + Restored/Accrued Amount = Closing Balance holds for the worker's absence plan balance as of the balance date
the absence transaction is reflected exactly once in the balance, with no duplicate impact
carryover, where configured, is applied correctly to the balance

This scenario validates the core Absence Balance calculation for a worker already enrolled in an absence plan with existing transactions. Upstream absence entry, accrual processing and withdrawal transactions are covered by separate test scenarios within the same Absence Management business flow.

When to Use This Test

Functional testing of absence balance calculation for a new Oracle Fusion HCM Absence Management implementation
Regression testing of balance consumption and restoration after an Oracle quarterly update affecting Absence Management
UAT sign-off for balance-calculation accuracy across absence plans before go-live
Verification after absence-plan, accrual rule or carryover-configuration changes

Where This Test Fits in the Absence Management Process

Absence Entry

→

Absence Balance

→

Absence Accrual

→

Absence Withdrawal

This test covers verifying the absence-plan balance calculation after absence transactions are entered, approved, withdrawn or accrued. It depends on absence entries already recorded for the worker, and its results are, in turn, exercised further by accrual processing and withdrawal scenarios within the same Absence Management business flow.

Preconditions

The worker is enrolled in the absence plan and has an active assignment.
An opening balance exists for the worker's absence plan as of the balance date.
Required absence-plan, accrual and carryover configuration is in place.
At least one approved, withdrawn or accrued absence transaction is available to exercise the balance calculation.
The test user has the appropriate Absence Management role and access to view the worker's balance.
The as-of date used for the balance query is within a valid, supported range for the plan.

Exact balance rules, accrual frequency, carryover limits and rounding behavior vary by customer absence-plan configuration and legislation; not every rule applies to every plan or worker.

Sample Test Data

Worker	${WORKER}
Absence Plan	${ABSENCE_PLAN}
Opening Balance	${OPENING_BALANCE}
Approved Absence Amount	${APPROVED_ABSENCE_AMOUNT}
Restored Amount	${RESTORED_AMOUNT}
Accrued Amount	${ACCRUED_AMOUNT}
Closing Balance	${CLOSING_BALANCE}
As-Of Date	${AS_OF_DATE}
Carryover	${CARRYOVER}

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

Test Steps

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

#	User Action	Expected Result
1	Sign In to Oracle Fusion Sign in to Oracle Fusion Cloud with a user account that has Absence Management access.	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 view a worker's absence plan balance.	The Absence Management work area opens successfully.
3	Locate the Worker's Absence Plan Balance Locate the worker's balance for the selected absence plan. ${WORKER} / ${ABSENCE_PLAN}	The worker's absence plan balance is found and displayed.
4	Review the Opening Balance Review the opening balance recorded for the worker's absence plan as of the balance date. ${OPENING_BALANCE} / ${AS_OF_DATE}	The opening balance is displayed and matches the expected starting value for the period.
5	Apply, Approve or Withdraw an Absence Apply and approve an absence request, or withdraw an existing absence, against the worker's absence plan. ${APPROVED_ABSENCE_AMOUNT} / ${RESTORED_AMOUNT}	The absence transaction is submitted, approved or withdrawn without unexpected errors.
6	Review the Recalculated Balance Review the worker's balance for the absence plan after the transaction has been processed. ${CLOSING_BALANCE}	A recalculated closing balance is displayed for the worker and absence plan.
7	Verify Arithmetic Against Expected FormulaBusiness assertion Verify that Opening Balance minus Approved Absence plus Restored/Accrued Amount equals the reported Closing Balance for the worker's absence plan. This is the central business assertion for this scenario. Illustrative example only, using round numbers, not a real balance or customer-specific formula: if ${OPENING_BALANCE}=120, ${APPROVED_ABSENCE_AMOUNT}=24, ${RESTORED_AMOUNT}=0 and ${ACCRUED_AMOUNT}=10, then ${CLOSING_BALANCE}=106. 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.	Opening Balance − Approved Absence + Restored/Accrued Amount = Closing Balance holds for the worker's absence plan.
8	Confirm No Duplicate Balance Impact Confirm that the absence transaction is reflected exactly once in the worker's balance, with no duplicate consumption or restoration.	The balance reflects the transaction exactly once and remains consistent on repeat query.

Expected Results

The worker's opening balance for the absence plan is displayed correctly.
The approved absence correctly consumes the expected amount from available balance.
A withdrawn or cancelled absence correctly restores the expected amount to available balance.
Opening Balance minus Approved Absence plus Restored/Accrued Amount equals Closing Balance.
The transaction is reflected exactly once in the balance, with no duplicate impact.
Carryover, where configured, is applied correctly to the balance.

Key Validation Checkpoints

Opening Balance − Approved Absence + Restored/Accrued Amount = Closing Balance, verified arithmetically.
Absence plan correct for the worker.
Transaction reflected exactly once in the balance, with no duplicate impact.
Balance as-of date correct.
Carryover applied correctly where configured.
Balance query returns consistent results without an intervening transaction.

Core Business Scenario

Absence Balance

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 Balance scenario. Jarvis AI can extend this scenario by generating additional positive and negative balance-calculation variations across absence plans, transaction types and carryover configurations using customer-specific test data available through Syntra DataVault.

Teams do not need to manually build a separate balance test for every plan, transaction type and carryover combination. Jarvis uses the standard Absence Balance scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Opening Balance Confirmed

The worker's opening balance for the absence plan is confirmed as of the balance date.

Absence Transaction Applied

An absence is approved, withdrawn, or an accrual is processed against the plan.

Closing Balance Reviewed

The recalculated closing balance is reviewed for the worker and plan.

Verify Arithmetic

Opening Balance minus Approved Absence plus Restored/Accrued Amount is confirmed to equal Closing Balance.

Duplicate Impact Check

The balance is re-queried to confirm the transaction is reflected exactly once.

Regression Pack

Selected balance 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 plan, transaction type and carryover configuration, SyntraFlow maintains one core Absence Balance scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Absence Balance 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

Check available balance
Full-day absence balance impact
Partial-day absence balance impact
Multi-day absence balance impact
Approved absence deduction from balance
Withdrawn absence restoration to balance
Carryover applied where configured
Balance query across multiple absence plans

Negative Scenarios

Insufficient balance for requested absence
Worker not enrolled in the absence plan
Absence plan inactive
Invalid balance as-of date
Unsupported absence type for the plan
Incorrect plan mapping for the worker
Duplicate transaction incorrectly applied to balance

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

Generated Using Your DataVault Test Data

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

Standard Library Definition

Worker                    ${WORKER}
Absence Plan              ${ABSENCE_PLAN}
Opening Balance           ${OPENING_BALANCE}
Approved Absence Amount   ${APPROVED_ABSENCE_AMOUNT}
Restored Amount           ${RESTORED_AMOUNT}
Accrued Amount            ${ACCRUED_AMOUNT}
Closing Balance           ${CLOSING_BALANCE}
As-Of Date                ${AS_OF_DATE}
Carryover                 ${CARRYOVER}

DataVault

Workers
  Eligible workers and absence plan enrollments
Absence Plans
  Configured absence plan and accrual definitions per legislation
Balances
  Opening and historical balance data (masked)
Transactions
  Approved, withdrawn and accrued absence transaction history
Carryover Rules
  Plan-specific carryover limits and effective dates

Jarvis AI Generates

Scenario 01 — Check Available Balance
Scenario 02 — Full-Day Absence Deduction
Scenario 03 — Multi-Day Absence Deduction
Scenario 04 — Withdrawn Absence Restoration
Scenario 05 — Carryover Applied at Period Start
Scenario 06 — Insufficient Balance
...

Absence balance test data can include sensitive worker information such as balance amounts, plan enrollment and transaction history. SyntraFlow test scenarios use ${PLACEHOLDER} tokens rather than real balance data, 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 Balance scenarios Jarvis can generate from this business scenario, spanning absence plan and transaction-type 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	Check Available Balance	Positive	Worker's current available balance is queried and displayed	Syntra Ready
VAR-002	Full-Day Absence Balance Impact	Positive/Transaction Type	A full-day approved absence consumes the expected amount from balance	Syntra Ready
VAR-003	Partial-Day Absence Balance Impact	Positive/Transaction Type	A partial-day approved absence consumes a fractional amount from balance	Syntra Ready
VAR-004	Multi-Day Absence Balance Impact	Positive/Transaction Type	A multi-day approved absence consumes the cumulative expected amount	Syntra Ready
VAR-005	Approved Absence Deduction	Positive/Transaction Type	Balance is recalculated correctly immediately after approval	Syntra Ready
VAR-006	Withdrawn Absence Restoration	Positive/Transaction Type	A withdrawn absence restores the expected amount to balance	Syntra Ready
VAR-007	Carryover Applied Where Configured	Positive/Plan	Carryover amount is reflected correctly in the new period's opening balance	Syntra Ready
VAR-008	Balance Query Across Multiple Plans	Positive/Plan	Worker enrolled in more than one plan; each plan balance is returned correctly	Syntra Ready
VAR-009	Insufficient Balance	Negative/Transaction Type	Requested absence amount exceeds the worker's available balance	Syntra Ready
VAR-010	Worker Not Enrolled in Plan	Negative/Plan	Worker does not have an active enrollment in the requested absence plan	Syntra Ready
VAR-011	Absence Plan Inactive	Negative/Plan	Balance is requested against a plan that is no longer active	Syntra Ready
VAR-012	Invalid Balance As-Of Date	Negative	Balance is requested using an as-of date outside a valid range	Syntra Ready
VAR-013	Unsupported Absence Type for Plan	Negative/Plan	Absence type submitted is not supported by the worker's absence plan	Syntra Ready
VAR-014	Incorrect Plan Mapping	Negative/Plan	Worker's absence request maps to the wrong absence plan	Syntra Ready
VAR-015	Duplicate Transaction Balance Impact	Negative/Transaction Type	A resubmitted or reprocessed transaction would incorrectly double-count against balance	Syntra Ready

Positive and Negative Absence Balance Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion correctly calculates opening balance, consumption, restoration, accrual and carryover for a worker's absence plan when the worker, plan and transaction data are all valid.

Valid Worker + Valid Absence Plan + Valid Transaction → Opening Balance − Approved Absence + Restored/Accrued Amount = Closing Balance

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around available balance, plan enrollment, plan status, balance dates and security during a balance check.

Insufficient Balance → Expected Balance Validation
Worker Not Enrolled in Plan → Expected Enrollment Validation
Absence Plan Inactive → Expected Plan Status Validation
Invalid Balance As-Of Date → Expected Date 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 balance scenarios and group them into reusable execution packs.

HCM Absence Balance Regression Pack

Check Available Balance
Full-Day Absence Balance Impact
Partial-Day Absence Balance Impact
Multi-Day Absence Balance Impact
Approved Absence Deduction
Withdrawn Absence Restoration
Carryover Applied Where Configured
Balance Query Across Multiple Plans
Insufficient Balance
Worker Not Enrolled in Plan
Absence Plan Inactive
Duplicate Transaction Balance Impact

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 Balance scenarios individually or as a batch. Users can schedule regression packs according to their absence-processing cycle.

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

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

Pack	HCM Absence Balance Regression Pack
Schedule	Nightly Regression
Tests	15 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 balance variations from disconnected field values, Jarvis can draw on a DataVault persona — a pre-grouped, mutually consistent set of absence-balance dimensions representative of a real worker profile, keeping plan, opening balance, carryover and effective date coherent.

Persona: Annual Leave Balance Worker

Worker	${WORKER}
Absence Plan	${ABSENCE_PLAN}
Opening Balance	${OPENING_BALANCE}
Carryover	${CARRYOVER}
Legal Employer	${LEGAL_EMPLOYER}
As-Of Date	${AS_OF_DATE}

DataVault personas group dependent absence-balance dimensions, such as plan enrollment, opening balance, carryover limits and effective dates, so Jarvis generates coherent, internally consistent balance 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 Balance 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	View Own Balance	Allowed	PASS
HR Specialist	View Worker Balance	Allowed	PASS
Unauthorized User	Attempts Balance Access	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 Balance scenario, available DataVault test data and expected business outcomes to generate additional balance-calculation 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 Absence Test — Absence Balance, 8 Business Steps

↓

DataVault Persona — Absence-Specific Worker Test Data

↓

Jarvis AI — Generate Positive + Negative + Plan + Transaction Type 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

Review the Recalculated Balance

May internally include

Open Absence Balance → Filter by Worker → Filter by Plan → Read Closing Balance

Business Step

Verify Arithmetic Against Expected Formula

May internally include

Read Opening Balance → Read Approved Absence Amount → Read Restored/Accrued Amount → Read Closing Balance → Compare Opening − Approved + Restored/Accrued to Closing

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 into one of eight categories: 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 Balance failed — Likely category: DATA_ERROR — Evidence: closing balance does not reconcile to opening balance minus approved absence plus restored/accrued amount — Recommended action: verify the underlying transaction history before escalating. 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
Apply, Approve or Withdraw an Absence	Pass	—
Review the Recalculated Balance	Pass	—
Verify Arithmetic Against Expected Formula	Pass	Pass

Related Absence Management Tests

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

Absence Entry Absence Accrual Absence Withdrawal

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

Start with the Syntra Standard Absence Balance 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 the absence balance formula work?

SyntraFlow verifies the arithmetic relationship Opening Balance − Approved Absence + Restored/Accrued Amount = Closing Balance using ${PLACEHOLDER} test data, never real or realistic worker balance data, and it does not publish any customer-specific balance formula or rate as fact.

How are carryover rules handled where configured?

Where an absence plan is configured with a carryover limit, Jarvis can generate variations that confirm the carryover amount is correctly reflected in the opening balance for the new period, subject to the customer's own plan configuration.

How does SyntraFlow help prevent a duplicate-transaction balance impact?

SyntraFlow's business assertion re-queries the balance after a transaction and confirms it changed by the expected amount exactly once, helping surface cases where a resubmitted or reprocessed transaction would otherwise double-count against the balance.

What do the failure-intelligence categories mean?

SyntraFlow evidence is intended to help classify a failed balance check 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 balance access?

SyntraFlow can exercise Absence Balance under different personas, such as an Employee viewing their own balance, an HR Specialist viewing a worker's balance, 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.