Oracle ERP Testing Tool > Test Library > SCM > Procurement > Requisitions

Syntra Standard Oracle Test Library

Oracle Fusion Approve Requisition Test Cases

Validate requisition approval routing and successful approval according to configured approval rules, using parameterised approval thresholds rather than fixed dollar amounts.

Test ID	ORCL.P2P.PROC.REQ.APPROVE
Application	Oracle Fusion Cloud
Product	SCM / Procurement
Module	Procurement
Process	Requisitions
Business Flow	Procure-to-Pay
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 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 27 underlying Oracle Fusion UI actions to complete it.

Test Objective

Validate requisition approval routing and successful approval according to configured rules — including how a submitted requisition is routed to the correct approver, how the approval action updates requisition status, and how approval history is retained for audit purposes.

The scenario should confirm that:

a submitted requisition awaiting approval is correctly identified and appears in the approver's worklist
the requisition routes to the correct approver based on the applicable rule (amount, category, or requisitioning BU context)
single-level and multi-level approval hierarchies are enforced as configured
the approval action is correctly processed and requisition status updates accordingly
approval history is captured and retained against the requisition
an approved requisition becomes available for downstream purchasing activity where applicable
approvers without the appropriate role or access cannot action the requisition

This scenario does not claim that requisition creation, submission, rejection or subsequent changes are covered — those are addressed by separate test scenarios in the Requisitions lifecycle.

When to Use This Test

Functional testing of a new Oracle Fusion Procurement requisition approval workflow implementation
Regression testing after an Oracle quarterly update
UAT sign-off for requisition approval routing and access control
Baseline case referenced by requisition submission, rejection and change scenarios within the same lifecycle

Where This Test Fits in the Requisition Approval Process

Create

→

Submit

→

Approve

→

Reject

→

Change

This test covers approval of a requisition that has already been submitted, and is a prerequisite for the requisition becoming available for downstream purchasing activity such as purchase order creation.

Preconditions

Oracle Fusion Procurement access is configured and available for the test user.
The requisition has been submitted and is pending approval.
Approval rules are configured for the applicable requisitioning BU, category and amount ranges.
A valid approver is assigned to the applicable approval rule and level.
The test user (or approver context) has the appropriate role and access to action Requisition approvals.

Exact approval workflow configuration, routing rules, approval levels and approver assignments vary by Oracle Fusion implementation and security setup.

Sample Test Data

Requisition Number	${REQUISITION_NUMBER}
Requisitioning BU	${REQUISITIONING_BU}
Category	${CATEGORY}
Total Amount	${TOTAL_AMOUNT}
Approval Threshold	${APPROVAL_THRESHOLD} — customer-configured value, not a fixed amount
Approver	${APPROVER} — valid approver assigned to the applicable rule and level
Approval Rule Context	Amount-based, category-based, or BU-based — scenario-defined
Approval Action	Approve / Delegate, where applicable

Approval rules, routing hierarchies and approval thresholds are defined per Oracle Fusion customer implementation. This test intentionally uses ${APPROVAL_THRESHOLD} as a placeholder rather than a fixed dollar amount — actual threshold values should be sourced from DataVault or the customer's approval configuration, not hard-coded into the test.

Test Steps

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

#	User Action	Expected Result
1	Sign In as Approver Sign in to Oracle Fusion as the approver assigned to the requisition. ${APPROVER}	The approver signs in successfully and lands on the home page.
2	Navigate to Approvals Worklist Navigate to the Approvals worklist to view requisitions pending action.	The Approvals worklist opens and displays requisitions awaiting the approver's action.
3	Open the Pending Requisition Locate and open the requisition awaiting approval. ${REQUISITION_NUMBER} This single business step replaces multiple technical actions such as opening search, entering the requisition number, clicking Search and selecting the result.	The correct requisition is opened and its status confirms it is pending approval.
4	Review Requisition Details Review the requisition lines, requisitioning BU, category and total amount presented to the approver.	Requisition details are complete and available for review before an approval decision is made.
5	Verify Routing Rule Applied Correctly Confirm the requisition routed to this approver based on the applicable approval rule. ${APPROVAL_THRESHOLD}	The requisition routes to the correct approver based on the amount, category, or BU rule in effect.
6	Approve the Requisition Take the approval action on the requisition.	The approval action is accepted by Oracle Fusion without unexpected errors.
7	Verify Status UpdatedBusiness assertion Confirm the requisition status updates to reflect the approval outcome. This is the main business assertion for the scenario — the test does not stop merely because the approval action was accepted successfully.	Requisition status accurately reflects the approval outcome — for example Approved, or Pending Next-Level Approval — consistent with the configured routing rule.
8	Verify Approval History RetainedBusiness assertion Review the requisition's approval history to confirm the action and approver are recorded.	Approval history is retained against the requisition, showing the approver, the action taken and the date.

Expected Results

Requisitions requiring approval route correctly to the configured approver based on the applicable rule (amount, category, or BU context).
Single-level and multi-level approval hierarchies are enforced as configured.
The approval action is correctly processed and requisition status updates accordingly.
Approval history is captured and retained against the requisition.
An approved requisition becomes available for downstream purchasing activity where applicable.
Approvers without the appropriate role or access cannot action the requisition.
Delegated approvals, where configured, are correctly attributed to the delegate.

Key Validation Checkpoints

Correct approver is identified for the applicable rule and level.
Requisition status updates to Approved.
Approval history is retained against the requisition.
Requisition becomes available for purchasing where applicable.

Core Business Scenario

Approve Requisition

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 requisition approval business scenario. Jarvis AI can extend this scenario by generating additional positive and negative test variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually duplicate the same approval test dozens of times simply to cover different combinations of approval rule, approval level, requisitioning BU and category. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's configured approval rules — including threshold-relative amounts, without assuming a fixed dollar value.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Approval Rules, Approval Thresholds, Approvers, Requisitioning BUs, Categories and other relevant test attributes.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant scenario variations.

Positive + Negative Test Variations

Positive, negative, boundary and configuration-specific scenarios.

Regression Pack

Selected variations can be grouped into an executable suite.

On-Demand / Scheduled / Batch Execution

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

Results + Evidence + Exceptions

Capture execution results, business assertions, screenshots/evidence and exceptions.

Rather than maintaining dozens of near-duplicate copies of the same approval test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available approval configuration — including threshold-relative amounts sourced from DataVault or customer configuration, never a hard-coded dollar value.

AI-Generated Test Variations

The same Approve Requisition 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 SCM Procurement Requisitions.

Positive Scenarios

Auto approval
Single-level approval
Multi-level approval
Amount-based approval
Category-based approval
BU-based routing
Approver delegates, where applicable

Negative Scenarios

Missing approver
Unauthorized approver
Invalid routing
Approval rule not satisfied
Security restriction
Attempt approval after cancellation

These are representative examples only. Approval rules, approval thresholds and expected behavior depend on the customer's Oracle Fusion configuration — not every Oracle configuration behaves identically, and approval thresholds are never hard-coded; they are sourced from DataVault or the customer's configuration where available.

Generated Using Your DataVault Test Data

Generic test data cannot represent a real Oracle Fusion approval configuration. Where connected, Jarvis can use approved test data available through Syntra DataVault — approval rule context, approver, and amount relative to ${APPROVAL_THRESHOLD} — to create variations relevant to the customer's actual implementation, rather than assuming a fixed threshold value.

Standard Library Definition

Requisition Number       ${REQUISITION_NUMBER}
Requisitioning BU        ${REQUISITIONING_BU}
Category                 ${CATEGORY}
Total Amount             ${TOTAL_AMOUNT}
Approval Threshold       ${APPROVAL_THRESHOLD}
Approver                 ${APPROVER}

DataVault

Approval Rules
  Amount-Based
  Category-Based
  BU-Based
Approval Thresholds
  Per customer configuration (not published)
Approvers
  Approver A (Level 1)
  Approver B (Level 2)
  Approver C (Delegate)
Requisitioning BUs
  BU A
  BU B
Categories
  Category A
  Category B

Jarvis AI Generates

Scenario 01 — Amount Below Threshold + Single-Level + Approve
Scenario 02 — Amount Above Threshold + Multi-Level + Approve
Scenario 03 — Category A + BU A Routing
Scenario 04 — Category B + BU B Routing
Scenario 05 — Delegate Approval
Scenario 06 — Missing Approver Configuration
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Approval configuration — including approval rules, routing hierarchies and approval thresholds — is customer-specific and, where DataVault is connected, is sourced from DataVault or the customer's own configuration rather than assumed by SyntraFlow.

Example Test Variations

Representative examples of scenarios Jarvis can generate from this business scenario. 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-Approved Requisition	Auto	Requisition meets auto-approval criteria; no manual approver action required	Syntra Ready
VAR-002	Single-Level Approval — Approve	Single-Level	One approval level required; approver approves the requisition	Syntra Ready
VAR-003	Multi-Level Approval — Second Level Approve	Multi-Level	Requisition routes to a second-level approver per configured rule	Syntra Ready
VAR-004	Amount-Based Approval — Below Threshold	Amount-Based/Single-Level	Requisition amount below ${APPROVAL_THRESHOLD}; single-level approval applies	Syntra Ready
VAR-005	Amount-Based Approval — Above Threshold	Amount-Based/Multi-Level	Requisition amount above ${APPROVAL_THRESHOLD}; routes to next approval level	Syntra Ready
VAR-006	Category-Based Approval — Category A	Single-Level	Routing determined by the category-based rule configured for Category A	Syntra Ready
VAR-007	BU-Based Routing — Requisitioning BU A	Single-Level	Routing determined by the BU-based rule configured for Requisitioning BU A	Syntra Ready
VAR-008	Approver Delegates Approval	Single-Level	Assigned approver delegates the approval action to an alternate approver, where configured	Syntra Ready
VAR-009	Missing Approver	Negative	No approver is configured or assigned for the applicable approval rule	Syntra Ready
VAR-010	Unauthorized Approver Attempt	Negative	A user without approval authority attempts to action the requisition	Syntra Ready
VAR-011	Invalid Routing Configuration	Negative	Approval rule configuration produces no valid routing path for the requisition	Syntra Ready
VAR-012	Approval Rule Not Satisfied	Negative	Requisition does not satisfy the condition required by the configured approval rule	Syntra Ready
VAR-013	Security Restriction on Approval	Negative	Approver lacks the role or data access required to action the requisition	Syntra Ready
VAR-014	Attempt Approval After Cancellation	Negative	An attempt to approve a requisition that has already been cancelled	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

Jarvis generates scenarios using combinations expected to successfully complete the requisition approval business process.

Requisition Within ${APPROVAL_THRESHOLD} + Single Approver → Approved Correctly

Negative Testing

Jarvis can generate scenarios designed to exercise Oracle's approval validations, routing rules and access controls around requisition approval.

Unauthorized Approver Attempt → Expected Access Validation
Missing Approver Configuration → Expected Routing Failure
Approval Rule Not Satisfied → Expected Routing Failure
Attempt Approval After Cancellation → Expected Block
Security Restriction → Expected Access Prevented

A negative scenario passes when Oracle correctly enforces the expected business rule or validation.

Scenario	Oracle Outcome	Test Result
Valid requisition	Requisition created	PASS
Inactive item	Item validation occurs	PASS
Invalid account	Account validation occurs	PASS
Security restriction	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

Approve Requisition Regression Pack

Auto-Approved Requisition
Single-Level Approval — Approve
Multi-Level Approval — Second Level Approve
Amount-Based Approval — Above Threshold
Category-Based Approval — Category A
BU-Based Routing — Requisitioning BU A
Approver Delegates Approval
Missing Approver
Unauthorized Approver Attempt
Attempt Approval After Cancellation

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

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

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

Pack	Approve Requisition Regression Pack
Schedule	Quarterly Update 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

Security & Persona Variations

SyntraFlow validates requisition approval access control by confirming that an authorized approver can action a requisition assigned to them, and that an unauthorized user is correctly prevented from doing the same.

Persona	Action	Expected	Syntra Result
Approver	Approve Assigned Requisition	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 business scenario, available DataVault test data and expected business outcomes to generate additional test coverage for the customer's environment, including Positive, Negative, Boundary and Approval variations relative to ${APPROVAL_THRESHOLD}.

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 Library — Approve Requisition, 8 Business Steps

↓

DataVault — Customer-Specific Approval Configuration

↓

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

Open the Pending Requisition

May internally include

Open Worklist Search → Focus Requisition Number → Enter Number → Search → Select Requisition → Confirm

Business Step

Approve the Requisition

May internally include

Open Approval Action Menu → Select Approve → Enter Comments (optional) → Confirm Action

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.

Step	Action Status	Business Validation
Approve the Requisition	Pass	—
Confirm Action Accepted	Pass	—
Verify Status Updated	Pass	Pass

Related Requisition Tests

Approval is one stage of the same Requisition lifecycle — explore the related submission, rejection and change scenarios below.

Submit Requisition Reject Requisition Change Requisition

Turn This Standard Test into Your Oracle Requisition Approval Regression Suite

Start with the Syntra Standard requisition approval test, use DataVault to provide environment-specific approval configuration, let Jarvis generate additional positive and negative variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Requisitions 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

Requisitions Test Library Procurement Test Library SCM Test Library Oracle Fusion Test Library Oracle ERP Testing Tool Syntra DataVault

Frequently Asked Questions

What does the Approve Requisition test validate in Oracle Fusion?

It validates that a submitted requisition routes to the correct approver, that the approval action correctly updates requisition status, and that approval history is retained for audit purposes.

What does requisition approval routing depend on?

Approval routing is determined by the approval rules configured for a given Oracle Fusion implementation, and can depend on factors such as requisitioning BU, category, and amount relative to the configured approval threshold.

Does this test use a specific dollar-amount approval threshold?

No. Approval thresholds vary by Oracle Fusion implementation and customer configuration, so this test uses a parameterised placeholder (${APPROVAL_THRESHOLD}) rather than a hard-coded dollar amount. Actual threshold values are sourced from DataVault or the customer's approval configuration.

How does multi-level approval work in this scenario?

Where a requisition amount or configuration requires more than one approval level, the requisition routes from one approver to the next according to the configured hierarchy. This scenario includes single-level and multi-level approval variations.

How is security tested as part of this scenario?

SyntraFlow includes variations that confirm an authorized approver can action an assigned requisition, and that a user without the required role or access is correctly prevented from approving it — see the Security & Persona Variations section below.