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

Syntra Standard Oracle Test Library

Oracle Fusion Cancel Purchase Order Test Cases

Validate cancellation of an eligible purchase order or purchase order line in Oracle Fusion Procurement, and confirm the resulting status change, open-quantity adjustment and downstream fulfillment impact.

Test ID	ORCL.P2P.PROC.PO.CANCEL
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 19 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to verify that an authorized Procurement user can cancel an eligible purchase order, or a specific line within it, in Oracle Fusion, and confirm the resulting status, open quantity and downstream impact.

The scenario should confirm that:

the selected purchase order or PO line is eligible for cancellation
a full purchase order can be cancelled, and a single line can be cancelled independently on a multi-line PO
the cancellation reason is accepted and retained against the transaction
the purchase order or line status correctly updates to Cancelled
the open (unfulfilled) quantity is correctly adjusted, while any already-received quantity is left unaffected
downstream fulfillment activity such as further receiving is correctly blocked once a PO or line is cancelled
the cancellation is retained in purchase order history rather than removing the record

This scenario does not claim that every downstream receiving, invoicing or budgetary control interaction is covered — those depend on the customer's specific Oracle Fusion configuration and are addressed by separate test scenarios.

When to Use This Test

Functional testing of Oracle Fusion Procurement cancel-purchase-order processing for a new implementation
Regression testing of cancellation eligibility, open-quantity handling and security validations after an Oracle quarterly update
UAT sign-off for purchase order controls that must correctly restrict and record cancellations
Testing referenced alongside the create, change and close scenarios within the same purchase order lifecycle

Where This Test Fits in the Purchase Order Lifecycle

Create Purchase Order

→

Approve Purchase Order

→

Change (Optional)

→

Receive / Fulfill

→

Cancel Eligible PO or Line

→

Close Purchase Order

This test covers cancellation of a purchase order or PO line that is still in an eligible status, and represents an action available at several points in the purchase order lifecycle rather than only at the end of it. Exact eligibility rules and downstream impact depend on the customer's Oracle Fusion configuration.

← Previous Stage

Change Purchase Order

Next Stage →

Close Purchase Order

Preconditions

Oracle Fusion Procurement Purchase Orders is configured and available to the test user.
An existing purchase order exists, with at least one line eligible for cancellation.
The purchase order or line is not fully received and not already closed.
The purchase order or line has not already been cancelled.
The test user has the appropriate security/privilege to cancel purchase orders.

Exact cancellation eligibility rules and security privileges may vary by Oracle Fusion implementation and configuration.

Sample Test Data

PO Number	${PO_NUMBER}
Line Number	${LINE_NUMBER}
PO/Line Status	Open / Approved — eligible for cancellation
Cancellation Scope	Full Purchase Order or Specific Line
Open Quantity	${OPEN_QUANTITY}
Cancellation Reason	${CANCELLATION_REASON}
Buyer	${BUYER}

Sample values are illustrative. Replace them with valid data from the target Oracle Fusion environment.

Test Steps

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

#	User Action	Expected Result
1	Sign In to Oracle Fusion Sign in to Oracle Fusion Cloud with a user that holds purchase order cancellation privileges. ${BUYER}	The user successfully signs in and lands on the Oracle Fusion home page.
2	Navigate to the Purchase Order Navigate to the Purchase Orders work area and search for the target purchase order. ${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 located and its current status is confirmed as eligible for cancellation.
3	Select Cancel (Full PO or Specific Line) Select the Cancel action for the full purchase order, or for a specific line where only a line-level cancellation is required. ${LINE_NUMBER}	The Cancel Purchase Order (or Cancel Line) page or dialog opens for the selected scope.
4	Enter Cancellation Reason Enter the reason for cancelling the purchase order or line. ${CANCELLATION_REASON}	The cancellation reason is accepted without unexpected validation errors.
5	Confirm Cancellation Confirm and submit the cancellation.	Oracle Fusion successfully processes the cancellation request without unexpected errors.
6	Verify Status UpdatedBusiness assertion Confirm the purchase order's or line's status following the cancellation.	Purchase order or line status updates to Cancelled, with the cancellation reason correctly recorded.
7	Verify Open Quantity AdjustedBusiness assertion Confirm the open (unfulfilled) quantity on the purchase order or line after cancellation. ${OPEN_QUANTITY}	The open quantity is correctly reduced to reflect the cancellation, while any already-received quantity remains unaffected.
8	Verify Downstream Fulfillment Blocked AppropriatelyBusiness assertion Confirm that the cancelled purchase order or line can no longer be actioned for downstream fulfillment, such as further receiving, while remaining visible in purchase order history. ${PO_NUMBER} This is the main business assertion for the scenario — a PO cancellation must be enforced downstream and must not silently remove purchase order history.	The cancelled purchase order or line is correctly excluded from further downstream fulfillment and remains traceable in history rather than being removed.

Expected Results

An eligible purchase order or PO line cancels successfully.
Purchase order or line status updates correctly to Cancelled.
Cancellation reason is correctly recorded.
A cancelled full purchase order and a cancelled single line both behave correctly and independently of other lines.
Open (unfulfilled) quantity is correctly adjusted, while already-received quantity is unaffected.
The cancelled purchase order or line is unavailable for further downstream fulfillment such as additional receiving.
The cancellation remains traceable in purchase order history.
No unexpected save errors occur.

Key Validation Checkpoints

Purchase order or line status becomes Cancelled.
Downstream fulfillment is blocked appropriately for the cancelled scope.
Cancellation is retained in purchase order history.
Open quantity is correctly adjusted.

Core Business Scenario

Cancel 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 cancel-purchase-order 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 cancel-purchase-order test dozens of times simply to cover different combinations of cancellation scope, receipt status and reason. Jarvis uses the standard business scenario as the foundation and generates relevant variations for the customer's environment.

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 — purchase orders, buyers, line items 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 cancel-purchase-order test, SyntraFlow maintains the core business scenario and allows Jarvis AI to generate relevant variations using the customer's available test data.

AI-Generated Test Variations

The same Cancel 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

Cancel a full purchase order
Cancel a single purchase order line
Cancel a purchase order before any receipt is recorded
Cancel the remaining unfulfilled quantity on a partially received line
Cancel with different valid cancellation reasons

Negative Scenarios

Attempt to cancel a fully received purchase order
Attempt to cancel a closed purchase order
Attempt to cancel an already-cancelled purchase order
Cancellation attempted without the appropriate security/privilege
Cancellation attempted on a purchase order or line in an invalid status

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

Generated Using Your DataVault Test Data

Generic test data rarely represents the full range of purchase order statuses, lines and buyers in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct cancel-purchase-order variations relevant to the customer's actual implementation.

Standard Library Definition

PO Number             ${PO_NUMBER}
Line Number            ${LINE_NUMBER}
Open Quantity           ${OPEN_QUANTITY}
Cancellation Reason     ${CANCELLATION_REASON}
Buyer                   ${BUYER}

DataVault

Purchase Orders
  Open / Approved / Partially Received / Fully Received / Closed / Cancelled
Lines
  Single-Line, Multi-Line
Buyers
  Buyer A, Buyer B, Buyer C
Cancellation Reasons
  Duplicate Order, No Longer Required, Incorrect Item, Supplier Change

Jarvis AI Generates

Scenario 01 — Full PO Cancellation, Reason = Duplicate Order
Scenario 02 — Single-Line Cancellation on Multi-Line PO
Scenario 03 — Cancellation Before Receipt
Scenario 04 — Cancellation of Unfulfilled Quantity on Partially Received Line
Scenario 05 — Fully Received PO Cancellation Attempt (Negative)
Scenario 06 — Closed PO Cancellation Attempt (Negative)
...

Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific data such as purchase order, buyer and line details remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of cancel-purchase-order 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	Cancel Full Purchase Order	Positive/Line/Full	Entire purchase order cancelled	Syntra Ready
VAR-002	Cancel Single Purchase Order Line	Positive/Line/Full	Only one line of a multi-line PO cancelled	Syntra Ready
VAR-003	Cancel Before Receipt	Positive/Status	PO cancelled before any receipt has been recorded	Syntra Ready
VAR-004	Cancel Unfulfilled Quantity	Positive/Status	Only the remaining open quantity on a partially received line is cancelled	Syntra Ready
VAR-005	Cancel With Reason — Duplicate Order	Positive	Cancellation reason = Duplicate Order	Syntra Ready
VAR-006	Cancel With Reason — No Longer Required	Positive	Cancellation reason = No Longer Required	Syntra Ready
VAR-007	Cancel Multiple Lines Individually	Positive/Line/Full	Each line cancelled independently on the same purchase order	Syntra Ready
VAR-008	Cancel by Original Buyer	Positive	Cancelled by the original buyer of record	Syntra Ready
VAR-009	Attempt to Cancel a Fully Received Purchase Order	Negative/Status	Purchase order line is fully received and not eligible for cancellation	Syntra Ready
VAR-010	Attempt to Cancel a Closed Purchase Order	Negative/Status	Purchase order has already been closed	Syntra Ready
VAR-011	Attempt to Cancel an Already-Cancelled Purchase Order	Negative/Status	Purchase order or line status is already Cancelled	Syntra Ready
VAR-012	Cancellation Attempted by Unauthorized User	Negative	User lacks the cancel-purchase-order privilege	Syntra Ready
VAR-013	Cancellation Attempted on Invalid PO Status	Negative/Status	Purchase order or line is in a status that does not support cancellation	Syntra Ready

Why a Blocked Cancellation Attempt Can Be a Passing Test

Positive Testing

Jarvis generates scenarios using combinations expected to successfully cancel an eligible purchase order or PO line.

Eligible PO + Valid Cancellation Reason → Purchase Order Cancelled Successfully

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's cancellation eligibility rules, validations and security around purchase order cancellation.

Fully Received PO → Expected Cancellation-Restricted Validation
Closed PO → Expected Cancellation-Restricted Validation
Already-Cancelled PO → Expected Duplicate-Cancellation Validation
Unauthorized User → Expected Security Validation
Invalid PO Status → Expected Status Validation

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

Purchase Order Cancellation Regression Pack

Cancel Full Purchase Order
Cancel Single Purchase Order Line
Cancel Before Receipt
Cancel Unfulfilled Quantity
Cancel With Reason — Duplicate Order
Cancel Multiple Lines Individually
Attempt to Cancel a Fully Received Purchase Order
Attempt to Cancel a Closed Purchase Order
Attempt to Cancel an Already-Cancelled Purchase Order
Cancellation Attempted by Unauthorized User

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

Once scheduled, SyntraFlow executes the selected cancel-purchase-order 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	Purchase Order Cancellation 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

Cancelling a purchase order is a control action. Jarvis can generate persona-based variations to confirm that only authorized users can cancel purchase orders, using role and privilege data available through DataVault.

Persona	Action	Expected	Syntra Result
Buyer	Cancel Own PO	Allowed	PASS
Unauthorized User	Attempts Cancel	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 across Positive, Negative, Boundary and Security categories.

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 — Cancel Purchase Order, 8 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

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

Navigate to the Purchase Order

May internally include

Open Purchase Orders Work Area → Focus Search → Enter PO Number → Search → Select Purchase Order → Confirm Eligible Status

Business Step

Confirm Cancellation

May internally include

Review Cancellation Details → Click Confirm/Submit → Capture Confirmation Response → Refresh PO Status and Open Quantity

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
Enter Cancellation Reason	Pass	—
Confirm Cancellation	Pass	—
Verify Open Quantity Adjusted	Pass	Pass
Verify Downstream Fulfillment Blocked Appropriately	Pass	Pass

Related Purchase Order Tests

Cancelling a purchase order is one of several actions available across the purchase order lifecycle covered in this cluster — explore the related change, close and create scenarios below.

Change Purchase Order Close Purchase Order Create Purchase Order

Turn This Standard Test into Your Oracle Purchase Order Regression Suite

Start with the Syntra Standard cancel-purchase-order test, use DataVault to provide environment-specific test data, 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 qualifies a purchase order for cancellation?

A purchase order or PO line generally qualifies for cancellation when it is still in an eligible status — for example, open or approved but not fully received and not yet closed. Exact eligibility rules depend on the customer's Oracle Fusion configuration.

What is the difference between cancelling a full purchase order and cancelling a PO line?

Cancelling the full purchase order ends every remaining eligible line on the PO, while cancelling a specific line only ends that line and leaves the remaining lines on the purchase order unaffected. Both scopes are covered by this scenario.

What happens to the open quantity when a purchase order or line is cancelled?

The open, or unfulfilled, quantity on the purchase order or line is reduced as part of the cancellation. Any quantity already received or invoiced prior to cancellation is generally unaffected and remains in the purchase order's transaction history.

Can a fully received or closed purchase order still be cancelled?

Typically not — once a purchase order or line has been fully received, or the purchase order has been closed, cancellation is usually restricted. This scenario includes negative variations confirming those expected restrictions.

What security testing approach does SyntraFlow use for cancel purchase order?

SyntraFlow can generate persona-based variations, using role and privilege data available through DataVault, to confirm that only authorized users such as buyers can cancel a purchase order, and that unauthorized users are correctly prevented from doing so.