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

Syntra Standard Oracle Test Library

Oracle Fusion Absence Withdrawal Test Cases

Validate withdrawal or cancellation of an eligible absence request in Oracle Fusion HCM Absence Management, confirming that the absence status is updated correctly and any balance consumed by the request is properly restored.

Test ID	ORCL.HCM.ABS.WITHDRAW
Application	Oracle Fusion Cloud
Product	HCM
Module	Absence Management
Process	Absence Withdrawal
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 that Oracle Fusion Absence Management correctly processes the withdrawal or cancellation of an eligible absence request, confirming that the request status, approval history and worker balance are all updated correctly as a result.

The scenario should confirm that:

an eligible absence request can be withdrawn or cancelled by the worker or an authorized representative
the absence status is correctly updated to reflect the withdrawal
any balance consumed by the original request is correctly restored
approval history for the original request remains intact and auditable after withdrawal
downstream processes such as payroll or time, where applicable, correctly reflect the withdrawal
withdrawal is correctly prevented for requests that are not eligible, already processed, or already withdrawn

This scenario assumes an eligible absence request already exists, created through the Absence Entry scenario and potentially already approved through Absence Approval. It focuses specifically on the withdrawal or cancellation step and its downstream effect on status and balance; upstream request creation and approval are covered by separate test scenarios within the same Workforce Management business flow.

When to Use This Test

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

Where This Test Fits in the Absence Management Process

Absence Entry

→

Absence Approval

→

Absence Balance Check

→

Absence Withdrawal

→

Balance Restoration

This test covers withdrawing or cancelling an eligible absence request and confirming that status and balance are updated correctly. It typically follows absence entry and, where applicable, approval, and precedes any downstream payroll or time processing, within the same Workforce Management business flow.

← Previous Stage

Absence Balance

Preconditions

An eligible absence request already exists for the worker, created via Absence Entry and, where applicable, approved via Absence Approval.
The absence request is in a status that permits withdrawal or cancellation under the customer's Oracle Fusion configuration.
The absence effective dates have not yet been fully processed by payroll or time, where such processing would block withdrawal.
The worker's absence balance reflects the amount consumed by the original request prior to withdrawal.
The test user has the appropriate Absence Management role and access to withdraw the request, either as the worker or on the worker's behalf.
Where a withdrawal reason is required by configuration, a valid reason value is available for entry.

Exact withdrawal eligibility, required approvals and balance-restoration behavior vary by customer absence-plan configuration, absence type and legislation; not every absence request or status is eligible for withdrawal in every configuration.

Sample Test Data

Worker	${WORKER}
Absence Request	${ABSENCE_REQUEST}
Absence Type	${ABSENCE_TYPE}
Absence Status	${ABSENCE_STATUS}
Withdrawal Reason	${WITHDRAWAL_REASON}
Effective Date	${EFFECTIVE_DATE}
Balance Before	${BALANCE_BEFORE}
Balance After	${BALANCE_AFTER}

Sample values are illustrative ${PLACEHOLDER} tokens, not real absence or balance data. Replace them with valid worker, absence and balance data from the target Oracle Fusion environment; SyntraFlow never publishes real or realistic worker or balance 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 HCM 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 and act on absence requests.	The Absence Management work area opens successfully.
3	Locate the Eligible Absence Request Locate the worker's eligible absence request to be withdrawn or cancelled. ${WORKER} / ${ABSENCE_REQUEST} / ${ABSENCE_TYPE} / ${ABSENCE_STATUS}	The absence request is found and is eligible for withdrawal in its current status.
4	Initiate Withdrawal Initiate the withdrawal or cancellation action on the located absence request. ${EFFECTIVE_DATE}	The withdrawal action opens successfully for the selected request.
5	Provide a Withdrawal Reason Enter a withdrawal reason where required by configuration. ${WITHDRAWAL_REASON}	The withdrawal reason is accepted and recorded against the request.
6	Submit the Withdrawal Submit the withdrawal request for processing.	The withdrawal is submitted without unexpected errors.
7	Verify Status Updated and Balance RestoredBusiness assertion Verify that the absence status reflects the withdrawal and that the consumed balance has been restored. ${BALANCE_BEFORE} / ${BALANCE_AFTER} This is the central business assertion for this scenario. Illustrative example only, not a real balance figure: if ${BALANCE_BEFORE}=3 days consumed and the withdrawal is accepted, ${BALANCE_AFTER} is expected to reflect the restored balance for the worker. Test execution is designed to use ${PLACEHOLDER} tokens rather than real balance figures, and this page does not publish any customer-specific balance calculation as fact.	The absence status is Withdrawn/Cancelled and the worker's balance reflects the expected restoration.

Expected Results

The eligible absence request is withdrawn or cancelled successfully.
The absence status is correctly updated to reflect the withdrawal.
The balance consumed by the original request is correctly restored.
Approval history for the original request remains intact and auditable.
Downstream processes such as payroll or time, where applicable, correctly reflect the withdrawal.
Withdrawal is correctly prevented for requests that are not eligible for withdrawal.

Key Validation Checkpoints

Status correctly updated to withdrawn/cancelled.
Balance correctly restored.
Approval history retained.
Downstream impact updated where applicable (e.g. payroll/time).
Absence remains auditable after withdrawal.
No duplicate balance restoration on repeat withdrawal attempts.

Core Business Scenario

Absence Withdrawal

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 Withdrawal scenario. Jarvis AI can extend this scenario by generating additional positive and negative withdrawal variations across absence types, request statuses and timing conditions using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate withdrawal test for every absence type, status and timing combination. Jarvis uses the standard Absence Withdrawal scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Absence Request Located

An eligible absence request is located for the worker.

Withdrawal Initiated

Withdrawal or cancellation of the request is initiated.

Reason Captured

A withdrawal reason is provided and captured with the record where required.

Status Updated

The absence status is updated to reflect the withdrawal.

Balance Restored

Any balance consumed by the absence is restored for the worker.

Regression Pack

Selected withdrawal 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, request status and timing scenario, SyntraFlow maintains one core Absence Withdrawal scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

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

Withdraw a pending absence request
Withdraw an approved absence where permitted by policy
Partial cancellation of an absence period where supported
Withdrawal across different absence types
Withdraw a future-dated absence
Withdrawal with a documented reason

Negative Scenarios

Attempt to withdraw an absence that is already completed
Attempt to withdraw an absence not eligible for withdrawal
Attempt withdrawal with an invalid effective date
Attempt withdrawal by an unauthorized user
Withdrawal blocked because payroll or time processing has already used the absence
Attempt to withdraw an absence that has already been withdrawn
Attempt withdrawal without providing a required withdrawal reason

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

Generated Using Your DataVault Test Data

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

Standard Library Definition

Worker              ${WORKER}
Absence Request     ${ABSENCE_REQUEST}
Absence Type        ${ABSENCE_TYPE}
Absence Status      ${ABSENCE_STATUS}
Withdrawal Reason   ${WITHDRAWAL_REASON}
Effective Date      ${EFFECTIVE_DATE}
Balance Before      ${BALANCE_BEFORE}
Balance After       ${BALANCE_AFTER}

DataVault

Workers
  Eligible workers and absence-eligible assignments
Absence Requests
  Existing requests across statuses (pending, approved, completed, withdrawn)
Absence Types and Plans
  Configured absence types, plans and eligibility rules
Balances
  Worker absence balances before and after consumption
Approval History
  Retained approval records for withdrawn requests (masked)

Jarvis AI Generates

Scenario 01 — Withdraw Pending Absence Request
Scenario 02 — Withdraw Approved Absence
Scenario 03 — Partial Cancellation of Absence Period
Scenario 04 — Withdraw Future-Dated Absence
Scenario 05 — Absence Already Completed
Scenario 06 — Already-Withdrawn Request
...

Absence withdrawal test data can include sensitive worker information such as withdrawal reasons and balances. SyntraFlow test scenarios use ${PLACEHOLDER} tokens rather than real worker or balance data, and masked or placeholder worker and absence data sourced through Syntra DataVault is 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 Withdrawal scenarios Jarvis can generate from this business scenario, spanning request status and timing 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	Withdraw Pending Absence Request	Positive/Status	Worker withdraws a request that is still in Pending Approval status	Syntra Ready
VAR-002	Withdraw Approved Absence	Positive/Status	Worker withdraws an already-approved absence where policy permits	Syntra Ready
VAR-003	Partial Cancellation of Absence Period	Positive	Only part of a multi-day absence period is withdrawn where supported	Syntra Ready
VAR-004	Withdrawal Across Different Absence Types	Positive	The same withdrawal flow is validated across different configured absence types	Syntra Ready
VAR-005	Withdraw Future-Dated Absence	Positive/Timing	The absence effective date is in the future relative to the withdrawal date	Syntra Ready
VAR-006	Withdrawal with Documented Reason	Positive	A withdrawal reason is provided and retained with the record	Syntra Ready
VAR-007	Withdraw Already-Completed Absence	Negative/Status/Timing	The absence effective dates have already passed and been processed	Syntra Ready
VAR-008	Absence Not Eligible for Withdrawal	Negative/Status	The absence type or status configuration blocks withdrawal	Syntra Ready
VAR-009	Invalid Effective Date	Negative/Timing	Withdrawal is attempted with an out-of-range or invalid effective date	Syntra Ready
VAR-010	Unauthorized User Attempts Withdrawal	Negative	A user without appropriate security attempts to withdraw the request	Syntra Ready
VAR-011	Payroll/Time Processing Prevents Withdrawal	Negative/Timing	The absence has already been consumed by payroll or time processing	Syntra Ready
VAR-012	Withdraw Already-Withdrawn Request	Negative/Status	Withdrawal is attempted again on a request already withdrawn	Syntra Ready
VAR-013	Missing Required Withdrawal Reason	Negative	Withdrawal is submitted without a reason required by configuration	Syntra Ready

Positive and Negative Absence Withdrawal Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion Absence Management correctly withdraws or cancels an eligible absence request and restores the worker's balance when the request, status and timing data are all valid.

Valid Worker + Eligible Absence Request + Valid Effective Date → Status Updated and Balance Restored Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around eligibility, request status, effective dates and security during withdrawal.

Absence Already Completed → Expected Eligibility Validation
Absence Not Eligible for Withdrawal → Expected Status Validation
Invalid Effective Date → Expected Date Validation
Unauthorized User → Expected Access Restriction
Already-Withdrawn Request → Expected Duplicate Prevention

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

HCM Absence Withdrawal Regression Pack

Withdraw Pending Absence Request
Withdraw Approved Absence
Partial Cancellation of Absence Period
Withdrawal Across Different Absence Types
Withdraw Future-Dated Absence
Withdrawal with Documented Reason
Withdraw Already-Completed Absence
Absence Not Eligible for Withdrawal
Invalid Effective Date
Unauthorized User Attempts Withdrawal
Payroll/Time Processing Prevents Withdrawal
Withdraw Already-Withdrawn Request

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

Once scheduled, SyntraFlow executes the selected withdrawal 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 Withdrawal Regression Pack
Schedule	Nightly Regression
Tests	13 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 withdrawal 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 worker profile, keeping withdrawal timing and balance-restoration dimensions coherent.

Persona: Withdrawn Absence Request Worker

Worker	${WORKER}
Absence Type	${ABSENCE_TYPE}
Absence Status Before	${ABSENCE_STATUS}
Withdrawal Reason	${WITHDRAWAL_REASON}
Balance Before	${BALANCE_BEFORE}
Balance After	${BALANCE_AFTER}

DataVault personas group dependent absence dimensions, such as absence type, status, timing and balance impact, so Jarvis generates coherent, internally consistent withdrawal 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 Withdrawal 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	Withdraw Own Absence via Self-Service	Allowed where configured	PASS
HR Specialist	Withdraw on Behalf of Worker	Allowed	PASS
Unauthorized User	Attempts Withdrawal	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 Withdrawal scenario, available DataVault test data and expected business outcomes to generate additional withdrawal 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 Withdrawal, 7 Business Steps

↓

DataVault Persona — Absence-Specific Worker Test Data

↓

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

Locate the Eligible Absence Request

May internally include

Open Absence Management → Search Worker → Filter by Status → Open Absence Request

Business Step

Verify Status Updated and Balance Restored

May internally include

Read Absence Status → Read Balance Before → Read Balance After → Compare Balance Restoration → Confirm Status = Withdrawn

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 Withdrawal failed — Likely category: EXPECTED_VALIDATION — Evidence: the absence has already been processed by payroll and withdrawal is restricted — Recommended action: this is expected behavior; use a correction process appropriate for post-payroll changes. 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
Initiate Withdrawal	Pass	—
Submit the Withdrawal	Pass	—
Verify Status Updated and Balance Restored	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 Entry

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

Start with the Syntra Standard Absence Withdrawal test, use DataVault to provide environment-specific worker and absence 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

What is the difference between withdrawing a pending request and withdrawing an approved absence?

Withdrawing a pending request typically cancels a request that has not yet completed approval, while withdrawing an approved absence reverses a request that has already been approved and may have consumed balance. Both are covered as positive scenarios where the customer's Oracle Fusion configuration permits withdrawal, but the underlying validations and downstream impact can differ.

What happens if the absence has already been processed by payroll?

Where payroll or time has already processed the absence, Oracle Fusion is typically expected to restrict a standard withdrawal. This is treated as an expected validation rather than a defect, and a correction process appropriate for post-payroll changes is generally used instead.

When is the worker's balance restored after withdrawal?

Balance restoration timing depends on the customer's Oracle Fusion Absence Management configuration and accrual setup. This test verifies that the balance is correctly restored following withdrawal; it does not assume a specific restoration timeframe applies universally.

What do the failure-intelligence categories mean?

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

SyntraFlow can exercise Absence Withdrawal under different personas, such as an employee withdrawing their own request, an HR Specialist withdrawing on a worker's behalf, 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.