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

Syntra Standard Oracle Test Library

Oracle Fusion Absence Accrual Test Cases

Validate that Oracle Fusion Absence Management correctly accrues absence entitlement for eligible workers, applying the configured plan's accrual frequency, service and eligibility conditions to produce the expected balance, cap and carryover behavior.

Test ID	ORCL.HCM.ABS.ACCRUAL
Application	Oracle Fusion Cloud
Product	HCM
Module	Absence Management
Process	Absence Accrual
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 7 business-readable test steps; SyntraFlow's automation executes approximately 17 underlying Oracle Fusion UI actions to complete it.

Test Objective

This test validates accrual of absence entitlement according to configured plan rules, worker eligibility and service or effective-date conditions, confirming that Oracle Fusion Absence Management produces the correct accrued balance for the worker and plan under test.

The scenario should confirm that:

the worker's eligibility for the absence plan is correctly determined before accrual is applied
accrual is generated according to the plan's configured frequency, such as monthly or annual accrual rules
the accrued amount matches the plan's configured accrual rate and any applicable service-based tiers
the worker's absence balance is updated correctly following accrual
any configured accrual cap is respected and not exceeded
carryover of unused entitlement is applied correctly where the plan is configured to allow it

This scenario validates the core Absence Accrual process for a worker already enrolled in an absence plan. Absence entry, approval, balance inquiry and validation are covered by separate test scenarios within the same Absence Management flow.

When to Use This Test

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

Where This Test Fits in the Absence Management Process

Plan Enrollment & Eligibility

→

Absence Balance

→

Absence Accrual

→

Absence Entry

→

Absence Withdrawal

This test covers accruing absence entitlement for an eligible worker under a configured plan and confirming the resulting balance, cap and carryover behavior. It follows enrollment and balance setup, and precedes absence entry and withdrawal, within the same Absence Management flow.

Preconditions

A valid absence plan with configured accrual rules, frequency and rates is available.
The worker is enrolled in the absence plan and, where required, has met the plan's service or eligibility conditions.
The worker's hire date and service dates are recorded and available for eligibility evaluation.
Where configured, accrual cap and carryover rules are defined for the plan.
The test user has the appropriate Absence Management role and access to review or process accruals.

Exact accrual frequency, eligibility conditions, cap and carryover behavior vary by customer plan configuration and legislation; not every rule applies to every plan or worker.

Sample Test Data

Worker	${WORKER}
Absence Plan	${ABSENCE_PLAN}
Accrual Frequency	${ACCRUAL_FREQUENCY}
Service Date	${SERVICE_DATE}
Hire Date	${HIRE_DATE}
Accrual Amount	${ACCRUAL_AMOUNT}
Accrual Cap	${ACCRUAL_CAP}
Carryover	${CARRYOVER}
Effective Date	${EFFECTIVE_DATE}

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

Test Steps

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

#	User Action	Expected Result
1	Sign In to Oracle Fusion Absence Management 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 review worker absence plans and accruals.	The Absence Management work area opens successfully.
3	Locate the Worker's Absence Plan Locate the worker and the absence plan under test. ${WORKER} / ${ABSENCE_PLAN}	The worker's enrollment in the absence plan is found and confirmed.
4	Review Accrual Frequency and Eligibility Conditions Review the plan's configured accrual frequency along with the worker's service date, hire date and eligibility conditions. ${ACCRUAL_FREQUENCY} / ${SERVICE_DATE} / ${HIRE_DATE}	The reviewed accrual frequency and eligibility conditions are consistent with the plan's configuration.
5	Trigger or Verify the Accrual Trigger the accrual process for the worker and plan, or verify the results of an existing scheduled accrual, for the selected effective date. ${EFFECTIVE_DATE}	The accrual runs, or is confirmed to have run, without unexpected errors.
6	Review the Resulting Balance ChangeBusiness assertion Review the worker's absence balance following accrual and compare it against the expected accrual amount. ${ACCRUAL_AMOUNT} This is the central business assertion for this scenario. Illustrative example only, not a real accrual result or customer-specific formula: if the prior balance is ${ACCRUAL_AMOUNT} before accrual and the plan accrues an additional ${ACCRUAL_AMOUNT} for the period, the resulting balance should reflect that increase, subject to any configured cap. Test execution is designed to use ${PLACEHOLDER} tokens rather than real entitlement figures.	The worker's balance reflects the expected accrued amount for the plan and period.
7	Confirm Cap and Carryover Behavior Confirm that the accrual cap, where configured, is respected and that carryover of unused entitlement, where configured, has been applied correctly. ${ACCRUAL_CAP} / ${CARRYOVER}	The accrued balance does not exceed the configured cap, and carryover has been applied according to the plan's rules.

Expected Results

Absence accrual is generated correctly for the eligible worker and plan.
The accrued amount is correct according to the plan's configured accrual rules.
Worker eligibility for accrual is correctly determined based on service and eligibility conditions.
The worker's absence balance is updated correctly following accrual.
Any configured accrual cap is respected.
Carryover of unused entitlement is applied correctly where configured.

Key Validation Checkpoints

Accrual generated correctly for the worker and plan.
Accrual amount correct per plan rules.
Worker eligibility correctly determined.
Absence balance updated correctly.
Accrual cap respected where configured.
Carryover applied correctly where configured.

Core Business Scenario

Absence Accrual

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 Accrual scenario. Jarvis AI can extend this scenario by generating additional positive and negative accrual variations across plan types, accrual frequencies and eligibility conditions using customer-specific test data available through Syntra DataVault.

Teams do not need to manually build a separate accrual test for every plan, frequency and eligibility combination. Jarvis uses the standard Absence Accrual scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Enrollment & Eligibility Confirmed

The worker's enrollment and eligibility conditions for the absence plan are confirmed.

Run Absence Accrual

The Absence Accrual process is triggered or verified for the worker and plan.

Review Balance Change

The resulting absence balance change is reviewed against the plan's accrual rules.

Verify Cap and Carryover

Accrual cap and carryover behavior, where configured, are confirmed.

Confirm Accrual Status

Accrual completion status is confirmed for the worker and plan.

Regression Pack

Selected accrual 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 plan type, accrual frequency, service condition and worker population, SyntraFlow maintains one core Absence Accrual scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

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

Standard accrual for an eligible worker
Monthly accrual
Annual accrual
Prorated accrual for a partial period
New-hire accrual once eligibility conditions are met
Service-based accrual reflecting length-of-service tiers
Carryover of unused entitlement where configured

Negative Scenarios

Worker not eligible for the absence plan
Absence plan inactive
Incorrect or missing plan enrollment
Invalid service date
Invalid accrual setup on the plan
Maximum accrual cap reached
Invalid effective date for the accrual

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

Generated Using Your DataVault Test Data

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

Standard Library Definition

Worker              ${WORKER}
Absence Plan        ${ABSENCE_PLAN}
Accrual Frequency   ${ACCRUAL_FREQUENCY}
Service Date        ${SERVICE_DATE}
Hire Date           ${HIRE_DATE}
Accrual Amount      ${ACCRUAL_AMOUNT}
Accrual Cap         ${ACCRUAL_CAP}
Carryover           ${CARRYOVER}
Effective Date      ${EFFECTIVE_DATE}

DataVault

Absence Plans
  Configured plan types, accrual frequencies and rates
Workers
  Enrolled workers, hire dates and service dates
Eligibility Rules
  Plan-specific service and eligibility conditions
Cap and Carryover Rules
  Plan-specific accrual cap and carryover configuration (masked)

Jarvis AI Generates

Scenario 01 — Standard Accrual for Eligible Worker
Scenario 02 — Monthly Accrual
Scenario 03 — New-Hire Accrual After Eligibility Met
Scenario 04 — Service-Based Accrual Tier
Scenario 05 — Worker Not Yet Eligible
Scenario 06 — Maximum Accrual Cap Reached
...

Absence accrual test data can include sensitive information such as service dates, hire dates and entitlement balances. SyntraFlow test scenarios use ${PLACEHOLDER} tokens rather than real service-date, hire-date or accrual 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 Accrual scenarios Jarvis can generate from this business scenario, spanning accrual frequency 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	Standard Accrual for Eligible Worker	Positive/Eligibility	Baseline accrual for a worker who has met all plan eligibility conditions	Syntra Ready
VAR-002	Monthly Accrual	Positive/Frequency	Accrual generated on the plan's configured monthly frequency	Syntra Ready
VAR-003	Annual Accrual	Positive/Frequency	Accrual generated on the plan's configured annual frequency	Syntra Ready
VAR-004	Prorated Accrual	Positive/Frequency	Accrual prorated for a partial accrual period	Syntra Ready
VAR-005	New-Hire Accrual	Positive/Eligibility	Accrual begins once a new hire meets the plan's eligibility conditions	Syntra Ready
VAR-006	Service-Based Accrual	Positive/Eligibility	Accrual rate reflects a length-of-service tier defined on the plan	Syntra Ready
VAR-007	Carryover Applied	Positive	Unused entitlement is carried over according to the plan's carryover rules	Syntra Ready
VAR-008	Worker Not Eligible	Negative/Eligibility	Worker has not met the plan's service or eligibility conditions	Syntra Ready
VAR-009	Absence Plan Inactive	Negative	Accrual is attempted against a plan that is no longer active	Syntra Ready
VAR-010	Incorrect Enrollment	Negative/Eligibility	Worker is enrolled in the wrong plan or lacks a valid enrollment record	Syntra Ready
VAR-011	Invalid Service Date	Negative/Eligibility	Recorded service date is missing, invalid or inconsistent with the hire date	Syntra Ready
VAR-012	Invalid Accrual Setup	Negative/Frequency	Plan accrual configuration is incomplete or misconfigured	Syntra Ready
VAR-013	Maximum Accrual Cap Reached	Negative	Worker's balance is already at the plan's configured accrual cap	Syntra Ready
VAR-014	Invalid Effective Date	Negative/Frequency	Accrual is attempted with an effective date outside a valid accrual period	Syntra Ready

Positive and Negative Absence Accrual Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion Absence Management correctly accrues entitlement, respects caps and applies carryover when the worker, plan and service data are all valid.

Valid Worker + Valid Plan Enrollment + Eligibility Met → Accrual Generated and Balance Updated Correctly

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around plan eligibility, enrollment, service dates, accrual caps and security during accrual.

Worker Not Eligible → Expected Eligibility Validation
Absence Plan Inactive → Expected Plan Status Validation
Incorrect Enrollment → Expected Enrollment Validation
Invalid Service Date → Expected Date Validation
Maximum Accrual Cap Reached → Expected Cap Validation

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 accrual scenarios and group them into reusable execution packs.

HCM Absence Accrual Regression Pack

Standard Accrual for Eligible Worker
Monthly Accrual
Annual Accrual
Prorated Accrual
New-Hire Accrual
Service-Based Accrual
Carryover Applied
Worker Not Eligible
Absence Plan Inactive
Incorrect Enrollment
Invalid Service Date
Maximum Accrual Cap Reached

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

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

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

Pack	HCM Absence Accrual Regression Pack
Schedule	Nightly Regression
Tests	14 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 accrual variations from disconnected field values, Jarvis can draw on a DataVault persona — a pre-grouped, mutually consistent set of absence dimensions representative of a real new-hire worker profile, keeping hire date, plan enrollment, eligibility status and balance coherent.

Persona: New Hire

Hire Date	${HIRE_DATE} (recent)
Absence Plan	${ABSENCE_PLAN}
Accrual Frequency	${ACCRUAL_FREQUENCY}
Eligibility Status	${ELIGIBILITY_STATUS} (Eligible / Not Yet Eligible)
Balance	${ACCRUAL_AMOUNT} (parameterized)
Legal Employer	${LEGAL_EMPLOYER}

DataVault personas group dependent absence dimensions, such as hire date, plan enrollment, accrual frequency and eligibility status, so Jarvis generates coherent, internally consistent accrual scenarios — including realistic not-yet-eligible new-hire cases — 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 Accrual 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
HR Specialist	Review Accrual Configuration	Allowed	PASS
Payroll Administrator	View Accrual Impact on Payroll	Allowed where integrated	PASS
Unauthorized User	Attempts Accrual Configuration 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 Accrual scenario, available DataVault test data and expected business outcomes to generate additional accrual 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 — Absence Accrual, 7 Business Steps

↓

DataVault Persona — Absence-Specific Worker Test Data

↓

Jarvis AI — Generate Positive + Negative + Frequency + Eligibility 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 Accrual Frequency and Eligibility Conditions

May internally include

Open Absence Plan → Filter by Worker → Review Accrual Frequency → Review Service/Eligibility Dates

Business Step

Review the Resulting Balance Change

May internally include

Read Prior Balance → Read Accrual Amount → Read Resulting Balance → Compare Expected vs. Actual

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 Accrual failed — Likely category: EXPECTED_VALIDATION — Evidence: the worker has not yet met the service-date eligibility condition for this plan — Recommended action: this is expected behavior; verify the plan's eligibility rule and service date before treating the result as a failure. A failure should not be labeled as an Oracle application defect without supporting evidence; most failures trace back to test data, configuration or eligibility conditions.

Step	Action Status	Business Validation
Trigger or Verify the Accrual	Pass	—
Review the Resulting Balance Change	Pass	Pass
Confirm Cap and Carryover Behavior	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 Balance Absence Entry Absence Validation

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

Start with the Syntra Standard Absence Accrual test, use DataVault to provide environment-specific worker and plan 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 accrual frequency work in Oracle Fusion Absence Management?

Absence plans are configured with an accrual frequency, such as monthly or annual accrual, that determines how often entitlement is added to a worker's balance. Jarvis can generate positive accrual variations covering the frequencies configured on the customer's own absence plans using ${PLACEHOLDER} test data.

When does a new hire become eligible for accrual?

Eligibility timing depends on the absence plan's configured service and eligibility conditions relative to the worker's hire date. SyntraFlow test scenarios use ${HIRE_DATE} and ${SERVICE_DATE} placeholder tokens to exercise both eligible and not-yet-eligible new-hire conditions against the customer's own plan rules.

How are accrual caps tested?

Where a plan is configured with an accrual cap, SyntraFlow verifies that the accrued balance does not exceed the configured maximum, using ${ACCRUAL_CAP} test data. Behavior at or near the cap is customer-configuration specific, so Jarvis can generate boundary variations around the configured cap value.

What do the failure-intelligence categories mean?

SyntraFlow evidence is intended to help classify a failed accrual result 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 — for example, a worker not yet meeting a service-date eligibility condition is expected behavior, not a defect.

How is security tested for absence accrual?

SyntraFlow can exercise Absence Accrual under different personas, such as an HR Specialist, Payroll Administrator or an unauthorized user, to confirm Oracle correctly allows or prevents access to accrual configuration and results. Oracle Fusion roles and security are configured per customer, so actual behavior depends on the customer's own security model.