Oracle ERP Testing Tool > Test Library > SCM > Procurement > Purchase Orders

Syntra Standard Oracle Test Library

Oracle Fusion Approve Purchase Order Test Cases

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

Test ID	ORCL.P2P.PROC.PO.APPROVE
Application	Oracle Fusion Cloud
Product	SCM / Procurement
Module	Procurement
Process	Purchase Orders
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 26 underlying Oracle Fusion UI actions to complete it.

Test Objective

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

The scenario should confirm that:

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

This scenario does not claim that PO creation, change or cancellation are covered — those are addressed by separate test scenarios in the Purchase Orders lifecycle.

When to Use This Test

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

Where This Test Fits in the Purchase Order Approval Process

Create

→

Submit

→

Approve

→

Change

→

Cancel

This test covers approval of a purchase order that has already been submitted, and is a prerequisite for the PO becoming eligible for downstream processing such as receiving and invoicing.

← Previous Stage

Create Purchase Order

Next Stage →

Change Purchase Order

Preconditions

Oracle Fusion Procurement access is configured and available for the test user.
The purchase order has been submitted and is pending approval.
Approval rules are configured for the applicable procurement BU, supplier, 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 PO approvals.

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

Sample Test Data

PO Number	${PO_NUMBER}
Procurement BU	${PROCUREMENT_BU}
Supplier	${SUPPLIER}
Total Amount	${TOTAL_AMOUNT}
Approval Threshold	${APPROVAL_THRESHOLD} — customer-configured value, not a fixed amount
Buyer	${BUYER}
Approver	${APPROVER} — valid approver assigned to the applicable rule and level
Approval Rule Context	Amount-based, category-based, supplier-based, or BU-based — scenario-defined

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 ~26 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 purchase order. ${APPROVER}	The approver signs in successfully and lands on the home page.
2	Navigate to Approvals Worklist Navigate to the Approvals worklist to view purchase orders pending action.	The Approvals worklist opens and displays purchase orders awaiting the approver's action.
3	Open the Pending Purchase Order Locate and open the purchase order awaiting approval. ${PO_NUMBER} This single business step replaces multiple technical actions such as opening search, entering the PO number, clicking Search and selecting the result.	The correct purchase order is opened and its status confirms it is pending approval.
4	Review Purchase Order Details Review the PO lines, procurement BU, supplier and total amount presented to the approver.	Purchase order details are complete and available for review before an approval decision is made.
5	Verify Routing Rule Applied Correctly Confirm the purchase order routed to this approver based on the applicable approval rule. ${APPROVAL_THRESHOLD}	The purchase order routes to the correct approver based on the amount, category, supplier, or BU rule in effect.
6	Approve the Purchase Order Take the approval action on the purchase order.	The approval action is accepted by Oracle Fusion without unexpected errors.
7	Verify Status UpdatedBusiness assertion Confirm the purchase order 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.	Purchase order status accurately reflects the approval outcome — for example Approved, or Pending Next-Level Approval — consistent with the configured routing rule.
8	Verify Downstream EligibilityBusiness assertion Confirm the approved purchase order becomes eligible for downstream processing.	The approved purchase order is available for downstream activity such as receiving and invoicing, where applicable, and approval history shows the approver, action taken and date.

Expected Results

Purchase orders requiring approval route correctly to the configured approver based on the applicable rule (amount, category, supplier, or BU context).
Single-level and multi-level approval hierarchies are enforced as configured.
The approval action is correctly processed and PO status updates accordingly.
Approval history is captured and retained against the PO.
An approved PO becomes eligible for downstream processing such as receiving and invoicing where applicable.
Approvers without the appropriate role or access cannot action the PO.
PO approvals across different buyers and procurement BUs follow the correct rule for each context.

Key Validation Checkpoints

PO routes to the correct approver for the applicable rule and level.
PO status updates to Approved.
Approval history is retained against the PO.
PO becomes eligible for downstream processing where applicable.

Core Business Scenario

Approve Purchase Order

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 purchase order 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, procurement BU, supplier and buyer. 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, Buyers, Procurement BUs, Suppliers 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 Purchase Order 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 Purchase Orders.

Positive Scenarios

Auto approval
Single-level approval
Multi-level approval
Amount and category-based approval
Approval across different buyers and procurement BUs

Negative Scenarios

Missing approver
Unauthorized approver
Invalid routing
Rejected PO
Incomplete PO
Security restriction

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

PO Number                ${PO_NUMBER}
Procurement BU            ${PROCUREMENT_BU}
Supplier                  ${SUPPLIER}
Total Amount              ${TOTAL_AMOUNT}
Approval Threshold        ${APPROVAL_THRESHOLD}
Buyer                     ${BUYER}
Approver                  ${APPROVER}

DataVault

Approval Rules
  Amount-Based
  Category-Based
  Supplier-Based
  BU-Based
Approval Thresholds
  Per customer configuration (not published)
Approvers
  Approver A (Level 1)
  Approver B (Level 2)
Buyers
  Buyer A
  Buyer B
Procurement BUs
  BU A
  BU B
Suppliers
  Supplier A
  Supplier B

Jarvis AI Generates

Scenario 01 — Amount Below Threshold + Single-Level + Approve
Scenario 02 — Amount Above Threshold + Multi-Level + Approve
Scenario 03 — Supplier A + BU A Routing
Scenario 04 — Buyer B + BU B Routing
Scenario 05 — Missing Approver Configuration
Scenario 06 — Unauthorized Approver Attempt
...

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 Purchase Order	Auto	PO 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 purchase order	Syntra Ready
VAR-003	Multi-Level Approval — Second Level Approve	Multi-Level	PO routes to a second-level approver per configured rule	Syntra Ready
VAR-004	Amount-Based Approval — Below Threshold	Amount-Based/Single-Level	PO amount below ${APPROVAL_THRESHOLD}; single-level approval applies	Syntra Ready
VAR-005	Amount-Based Approval — Above Threshold	Amount-Based/Multi-Level	PO amount above ${APPROVAL_THRESHOLD}; routes to next approval level	Syntra Ready
VAR-006	Category-Based Approval Routing	Single-Level	Routing determined by the category-based rule configured for the PO	Syntra Ready
VAR-007	Different Buyer / Procurement BU Routing	Single-Level	Routing determined by the buyer- and BU-based rule for ${BUYER} and ${PROCUREMENT_BU}	Syntra Ready
VAR-008	Missing Approver	Negative	No approver is configured or assigned for the applicable approval rule	Syntra Ready
VAR-009	Unauthorized Approver Attempt	Negative	A user without approval authority attempts to action the purchase order	Syntra Ready
VAR-010	Invalid Routing Configuration	Negative	Approval rule configuration produces no valid routing path for the PO	Syntra Ready
VAR-011	Rejected Purchase Order	Negative	Approver rejects the purchase order instead of approving it	Syntra Ready
VAR-012	Incomplete Purchase Order	Negative	PO is missing required information and cannot be routed for approval	Syntra Ready
VAR-013	Security Restriction on Approval	Negative	Approver lacks the role or data access required to action the purchase order	Syntra Ready

Automatically Expand Positive and Negative Test Coverage

Positive Testing

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

PO 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 purchase order approval.

Unauthorized Approver Attempt → Expected Access Validation
Missing Approver Configuration → Expected Routing Failure
Rejected Purchase Order → Expected Status Update
Incomplete Purchase Order → Expected Routing Failure
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 PO	Purchase order created	PASS
Inactive supplier	Supplier 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 Purchase Order Regression Pack

Auto-Approved Purchase Order
Single-Level Approval — Approve
Multi-Level Approval — Second Level Approve
Amount-Based Approval — Above Threshold
Category-Based Approval Routing
Different Buyer / Procurement BU Routing
Missing Approver
Unauthorized Approver Attempt
Rejected Purchase Order
Incomplete Purchase Order

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 Purchase Order Regression Pack
Schedule	Quarterly Update 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

Security & Persona Variations

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

Persona	Action	Expected	Syntra Result
Approver	Approve Assigned PO	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 Purchase Order, 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 Purchase Order

May internally include

Open Worklist Search → Focus PO Number → Enter Number → Search → Select Purchase Order → Confirm

Business Step

Approve the Purchase Order

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 Purchase Order	Pass	—
Confirm Action Accepted	Pass	—
Verify Status Updated	Pass	Pass

Related Purchase Order Tests

Approval is one stage of the same Purchase Order lifecycle — explore the related creation, change and cancellation scenarios below.

Create Purchase Order Change Purchase Order Cancel Purchase Order

Turn This Standard Test into Your Oracle PO Approval Regression Suite

Start with the Syntra Standard purchase order 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 Purchase Orders 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

Purchase Orders 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 Purchase Order test validate in Oracle Fusion?

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

What does purchase order 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 procurement BU, supplier, 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 PO amount or configuration requires more than one approval level, the purchase order 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 purchase order, and that a user without the required role or access is correctly prevented from approving it — see the Security & Persona Variations section below.