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

Syntra Standard Oracle Test Library

Oracle Fusion Absence Approval Test Cases

Validate approval and rejection of absence requests in Oracle Fusion HCM Absence Management, confirming that requests route to the correct approver and that approval decisions are applied correctly according to the customer's configured approval rules.

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

Test Objective

This test validates that Oracle Fusion Absence Management correctly processes the approval or rejection of a submitted absence request, routing the request to the appropriate approver and applying the resulting decision according to the customer's configured approval rules.

The scenario should confirm that:

the absence request routes to the approver(s) defined by the configured approval rule
an approver can view the full details of the pending absence request
an approval decision (approve or reject) is captured and recorded correctly
approved absences update the worker's absence balance and status appropriately
rejected absences are returned to the worker with the decision reason retained
the approval history for the request is retained for audit purposes

This scenario validates the core Absence Approval process for a request already submitted and pending action. Absence request entry, balance calculation and withdrawal are covered by separate test scenarios within the same Absence Management module. Approval routing structures vary by customer configuration and are not assumed to follow a single universal rule.

When to Use This Test

Functional testing of absence approval routing for a new Oracle Fusion HCM Absence Management implementation
Regression testing of approval and rejection behavior after an Oracle quarterly update affecting Absence Management
UAT sign-off for approval routing and decision handling across worker types before go-live
Verification after approval-rule or absence-plan configuration changes

Where This Test Fits in the Absence Management Process

Absence Entry

→

Absence Approval

→

Absence Balance

→

Absence Withdrawal

This test covers approving or rejecting a submitted absence request and confirming that the resulting status, balance and notification behavior follow the configured approval rules. It follows absence entry and precedes balance review and withdrawal handling within the same Absence Management module.

Preconditions

An absence request has been submitted by the worker and is pending approval.
The approver(s) required by the configured approval rule have been identified.
The approver has the appropriate role and access to review and act on the pending request.
The absence type and plan applicable to the request are configured.
Where applicable, the worker's absence balance has been calculated for the request period.
The test user has access to the Absence Management approval work area, such as the worklist or approvals inbox.

Exact approval routing, number of approval levels and approver eligibility vary by customer configuration, absence type and business rules; not every absence request follows the same routing structure.

Sample Test Data

Worker	${WORKER}
Absence Request	${ABSENCE_REQUEST}
Absence Type	${ABSENCE_TYPE}
Approver	${APPROVER}
Approval Level	${APPROVAL_LEVEL}
Decision	${DECISION}
Decision Reason	${DECISION_REASON}
Effective Date	${EFFECTIVE_DATE}

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

Test Steps

7 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 Absence Management Sign in to Oracle Fusion Cloud with a user account that has absence approval access.	The Oracle Fusion Cloud home page loads successfully for the authenticated user.
2	Navigate to Absence Management Navigate to the approvals work area used to review pending absence requests, such as the worklist or approvals inbox.	The approvals work area opens successfully.
3	Locate the Pending Absence Request Locate the pending absence request awaiting the approver's decision. ${WORKER} / ${ABSENCE_REQUEST}	The pending absence request is found in the approver's queue.
4	Review the Absence Request Details Review the absence type, requested dates and balance impact of the pending request. ${ABSENCE_TYPE} / ${EFFECTIVE_DATE}	The reviewed details match the absence request as submitted by the worker.
5	Approve or Reject with a Reason Record an approval or rejection decision for the request at the current approval level, entering a decision reason where required. ${DECISION} / ${DECISION_REASON} / ${APPROVER} / ${APPROVAL_LEVEL}	The decision is captured for the approver and approval level.
6	Submit the Decision Submit the approval or rejection decision to Oracle Fusion.	The decision is processed without unexpected errors.
7	Verify Status and Balance ImpactBusiness assertion Verify that the absence request status reflects the recorded decision, and that the worker's absence balance and notification behave as configured. This is the central business assertion for this scenario. Approval routing, balance impact and notification behavior depend on the customer's configuration and are not assumed to follow a universal rule.	The request status is correct for the decision; on approval, the balance is updated appropriately; on rejection, the request is returned to the worker with the decision reason retained.

Expected Results

The absence request routes to the correct approver based on the configured approval rule.
The approver can review the complete details of the pending request.
The approval or rejection decision is captured and recorded correctly.
Approved requests update the worker's absence balance and status appropriately.
Rejected requests are returned to the worker with the decision reason retained.
The approval history for the request is retained for audit purposes.

Key Validation Checkpoints

Correct approver selected based on configured routing.
Approval or rejection status correct.
Approval history retained.
Balance updated appropriately on approval.
Worker notified where configured.
Rejection routes back to worker correctly.

Core Business Scenario

Absence Approval

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 Approval scenario. Jarvis AI can extend this scenario by generating additional positive and negative approval variations across approval levels, absence types and decision outcomes using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate approval test for every routing path, approval level and decision outcome. Jarvis uses the standard Absence Approval scenario as the foundation and generates relevant variations for the customer's environment.

From Standard Test to Executed Regression Pack

Absence Request Submitted

A worker's absence request is submitted and pending approval.

Route to Approver

The request routes to the approver(s) defined by the configured approval rule.

Review Request Details

The approver reviews the absence type, dates and balance impact of the request.

Approve or Reject

The approver records an approval or rejection decision with a reason.

Apply Decision

Oracle applies the decision, updating status, balance and worker notification as configured.

Regression Pack

Selected approval 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 approval level, absence type, routing path and decision outcome, SyntraFlow maintains one core Absence Approval scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

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

Auto approval where the absence type is configured for automatic approval
Manager approval of a direct report's absence request
Single-level approval routing
Multi-level approval routing
Approve absence request
Reject absence request

Negative Scenarios

Missing approver — no approver configured for the absence type or worker
Unauthorized approver attempts to act on the request
Invalid approval routing configuration
Absence request no longer eligible for approval, such as after cancellation
Approval attempted after the request has been withdrawn
Security restriction prevents the approval action
Duplicate decision attempted on an already-decided request

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

Generated Using Your DataVault Test Data

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

Standard Library Definition

Worker              ${WORKER}
Absence Request     ${ABSENCE_REQUEST}
Absence Type        ${ABSENCE_TYPE}
Approver            ${APPROVER}
Approval Level      ${APPROVAL_LEVEL}
Decision            ${DECISION}
Decision Reason     ${DECISION_REASON}
Effective Date      ${EFFECTIVE_DATE}

DataVault

Workers
  Worker records and reporting hierarchies
Absence Requests
  Submitted requests pending approval
Approvers
  Approver eligibility and routing configuration
Approval Rules
  Configured approval levels and routing logic
Absence Types and Plans
  Absence type and plan configuration per legal employer

Jarvis AI Generates

Scenario 01 — Manager Approval, Single Level
Scenario 02 — Multi-Level Approval
Scenario 03 — Auto Approval
Scenario 04 — Rejection with Reason
Scenario 05 — Missing Approver
Scenario 06 — Unauthorized Approver Attempt
...

Absence approval test data can include worker and approver identity information. SyntraFlow test scenarios use ${PLACEHOLDER} tokens rather than real worker or approver 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 Approval scenarios Jarvis can generate from this business scenario, spanning approval level, routing and decision outcome. 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	Auto Approval	Positive/Decision	Absence type is configured for automatic approval without manual action	Syntra Ready
VAR-002	Manager Approval	Positive	Direct manager approves the worker's absence request	Syntra Ready
VAR-003	Single-Level Approval	Positive/Approval Level	Request requires and completes a single approval level	Syntra Ready
VAR-004	Multi-Level Approval	Positive/Approval Level	Request requires and completes more than one approval level	Syntra Ready
VAR-005	Approve Absence Request	Positive/Decision	Approver records an approval decision for the request	Syntra Ready
VAR-006	Reject Absence Request	Positive/Decision	Approver records a rejection decision with a reason	Syntra Ready
VAR-007	Missing Approver	Negative/Approval Level	No approver is configured for the worker's absence type	Syntra Ready
VAR-008	Unauthorized Approver	Negative	A user without approval authority attempts to act on the request	Syntra Ready
VAR-009	Invalid Approval Routing	Negative/Approval Level	Approval rule routes to an invalid or misconfigured approver	Syntra Ready
VAR-010	Absence No Longer Eligible	Negative	Request is no longer eligible for approval, such as after cancellation	Syntra Ready
VAR-011	Approval After Withdrawal	Negative/Decision	Approval is attempted after the worker has withdrawn the request	Syntra Ready
VAR-012	Security Restriction	Negative	Approver's security access does not permit the required action	Syntra Ready
VAR-013	Duplicate Decision	Negative/Decision	A second decision is attempted on an already-decided request	Syntra Ready

Positive and Negative Absence Approval Testing

Positive Testing

Jarvis generates scenarios designed to confirm that Oracle Fusion correctly approves absence requests and applies the resulting status, balance and notification changes when the worker, approver and routing data are all valid.

Valid Worker + Valid Approver + Valid Routing → Absence Request Approved and Balance Updated Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around approver assignment, routing configuration, eligibility and security during absence approval.

Missing Approver → Expected Routing Validation
Unauthorized Approver → Expected Access Restriction
Invalid Approval Routing → Expected Configuration Validation
Absence No Longer Eligible → Expected Eligibility Validation
Approval After Withdrawal → Expected State 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 approval scenarios and group them into reusable execution packs.

HCM Absence Approval Regression Pack

Auto Approval
Manager Approval
Single-Level Approval
Multi-Level Approval
Approve Absence Request
Reject Absence Request
Missing Approver
Unauthorized Approver
Invalid Approval Routing
Absence No Longer Eligible
Approval After Withdrawal
Duplicate Decision

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

Once scheduled, SyntraFlow executes the selected approval 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 Approval 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 approval variations from disconnected field values, Jarvis can draw on a DataVault persona — a pre-grouped, mutually consistent set of approver and routing dimensions representative of a real approval scenario, keeping worker, absence type, approver and routing configuration coherent.

Persona: Manager-Approved Absence Request

Worker	${WORKER}
Absence Type	${ABSENCE_TYPE}
Approver	${APPROVER}
Approval Level	${APPROVAL_LEVEL}
Legal Employer	${LEGAL_EMPLOYER}
Decision	${DECISION}

DataVault personas group dependent approval dimensions, such as absence type, approver assignment, approval level and legal employer, so Jarvis generates coherent, internally consistent approval 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 Approval 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
Line Manager	Approve Direct Report's Absence	Allowed	PASS
HR Specialist	Approve on Behalf Where Configured	Allowed	PASS
Unauthorized User	Attempts Approval	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 Approval scenario, available DataVault test data and expected business outcomes to generate additional approval 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 Approval, 7 Business Steps

↓

DataVault Persona — Manager-Approved Absence Request Test Data

↓

Jarvis AI — Generate Positive + Negative + Approval Level + Decision 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 Absence Request Details

May internally include

Open Approvals Worklist → Open Request → Read Absence Type → Read Dates → Read Balance Impact

Business Step

Verify Status and Balance Impact

May internally include

Read Request Status → Read Approval History → Read Updated Balance → Compare to Expected Decision

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 Approval failed — Likely category: CONFIGURATION_ERROR — Evidence: no approver is configured for the worker's absence type — Recommended action: complete the approval routing configuration 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
Approve or Reject with a Reason	Pass	—
Submit the Decision	Pass	—
Verify Status and 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 Entry Absence Balance Absence Withdrawal

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

Start with the Syntra Standard Absence Approval test, use DataVault to provide environment-specific worker, approver and routing 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 is absence approval routing determined?

Absence approval routing is defined by the customer's own Oracle Fusion configuration, such as approval rules, hierarchies or absence-type-specific routing, and is not a universal or fixed structure. SyntraFlow validates that requests route according to the customer's configured rules rather than assuming a single approval model.

What is the difference between auto approval and manual approval?

Some absence types or plans can be configured for automatic approval, where the request is approved without manual intervention once submitted, while others require a manual decision from one or more designated approvers. SyntraFlow can validate both paths where they are configured in the customer's environment.

How is multi-level approval tested?

Where an absence type requires approval at more than one level, SyntraFlow can validate that the request correctly progresses through each configured approval level and that the final decision reflects the outcome at every stage, rather than assuming a fixed number of approval levels.

What do the failure-intelligence categories mean?

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

SyntraFlow can exercise Absence Approval under different personas, such as a Line Manager, HR Specialist or an unauthorized user, to confirm Oracle correctly allows or prevents approval actions. Oracle Fusion roles and security are configured per customer, so actual behavior depends on the customer's own security model.