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

Syntra Standard Oracle Test Library

Oracle Fusion Cancel Requisition Test Cases

Validate cancellation of an eligible purchase requisition or requisition line in Oracle Fusion Procurement, and confirm the resulting status change and downstream processing impact.

Test ID	ORCL.P2P.PROC.REQ.CANCEL
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 7 business-readable test steps; SyntraFlow's automation executes approximately 17 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 requisition, or a specific line within it, in Oracle Fusion, and confirm the resulting status and downstream impact.

The scenario should confirm that:

the selected requisition or requisition line is eligible for cancellation
a full requisition can be cancelled, and a single line can be cancelled independently on a multi-line requisition
the cancellation reason is accepted and retained against the transaction
the requisition or line status correctly updates to Cancelled
a cancelled requisition or line is no longer available for downstream processing such as conversion to a purchase order
the cancellation is retained in requisition history rather than removing the record

This scenario does not claim that every downstream sourcing, budgetary control or purchase-order 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-requisition processing for a new implementation
Regression testing of cancellation eligibility, status and security validations after an Oracle quarterly update
UAT sign-off for requisition controls that must correctly restrict and record cancellations
Closing scenario referenced by the create, submit, approve, reject and change scenarios within the same requisition lifecycle

Where This Test Fits in the Requisition Lifecycle

Create Requisition

→

Submit for Approval

→

Approve / Reject

→

Change (Optional)

→

Cancel Eligible Requisition

→

Requisition Cancelled

This test covers cancellation of a requisition or requisition line that is still in an eligible status, and represents the terminal action available at several points in the requisition lifecycle. Exact eligibility rules and downstream impact depend on the customer's Oracle Fusion configuration.

← Previous Stage

Change Requisition

Preconditions

Oracle Fusion Procurement Requisitions is configured and available to the test user.
An existing requisition exists, with at least one line eligible for cancellation.
The requisition or line has not already been cancelled.
The requisition or line has not yet been converted to a purchase order, or cancellation is otherwise permitted at its current status.
The test user has the appropriate security/privilege to cancel requisitions.

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

Sample Test Data

Requisition Number	${REQUISITION_NUMBER}
Line Number	${LINE_NUMBER}
Requisition/Line Status	Incomplete / Pending Approval / Approved — eligible for cancellation
Cancellation Scope	Full Requisition or Specific Line
Cancellation Reason	${CANCELLATION_REASON}
Requester	${REQUESTER}

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

Test Steps

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

#	User Action	Expected Result
1	Sign In to Oracle Fusion Sign in to Oracle Fusion Cloud with a user that holds requisition cancellation privileges. ${REQUESTER}	The user successfully signs in and lands on the Oracle Fusion home page.
2	Navigate to the Requisition Navigate to the Requisitions work area and search for the target requisition. ${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 located and its current status is confirmed as eligible for cancellation.
3	Select Cancel (Full Requisition or Specific Line) Select the Cancel action for the full requisition, or for a specific line where only a line-level cancellation is required. ${LINE_NUMBER}	The Cancel Requisition (or Cancel Line) page or dialog opens for the selected scope.
4	Enter Cancellation Reason Enter the reason for cancelling the requisition 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 requisition's or line's status following the cancellation.	Requisition or line status updates to Cancelled, with the cancellation reason correctly recorded.
7	Verify Requisition/Line Unavailable for Downstream ProcessingBusiness assertion Confirm that the cancelled requisition or line can no longer be actioned for downstream processing, such as conversion to a purchase order, while remaining visible in requisition history. ${REQUISITION_NUMBER} This is the main business assertion for the scenario — a requisition cancellation must be enforced downstream and must not silently remove requisition history.	The cancelled requisition or line is correctly excluded from further downstream processing and remains traceable in history rather than being removed.

Expected Results

An eligible requisition or requisition line cancels successfully.
Requisition or line status updates correctly to Cancelled.
Cancellation reason is correctly recorded.
A cancelled full requisition and a cancelled single line both behave correctly and independently of other lines.
The cancelled requisition or line is unavailable for downstream processing such as conversion to a purchase order.
The cancellation remains traceable in requisition history.
No unexpected save errors occur.
The cancelled requisition or line does not silently disappear from history or reporting.

Key Validation Checkpoints

Requisition or line status becomes Cancelled.
Cancelled line/requisition is unavailable for downstream processing.
Cancellation is retained in requisition history.

Core Business Scenario

Cancel 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 cancel-requisition 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-requisition test dozens of times simply to cover different combinations of cancellation scope, timing 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 — requisitions, requesters, 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-requisition 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 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

Cancel a full requisition
Cancel a single requisition line
Cancel a requisition before it has been approved
Cancel a requisition after it has been rejected
Cancel with different valid cancellation reasons

Negative Scenarios

Attempt to cancel an already-cancelled requisition
Attempt to cancel a requisition line already converted to a purchase order, where cancellation is restricted
Cancellation attempted without the appropriate security/privilege
Cancellation attempted on a requisition or line in an invalid status
Required cancellation reason left blank

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 requisition statuses, lines and requesters in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct cancel-requisition variations relevant to the customer's actual implementation.

Standard Library Definition

Requisition Number   ${REQUISITION_NUMBER}
Line Number           ${LINE_NUMBER}
Cancellation Reason    ${CANCELLATION_REASON}
Requester              ${REQUESTER}

DataVault

Requisitions
  Incomplete / Pending Approval / Approved / Cancelled / PO-Converted
Lines
  Single-Line, Multi-Line
Requesters
  Requester A, Requester B, Requester C
Cancellation Reasons
  Duplicate Request, No Longer Required, Incorrect Item, Budget Constraint

Jarvis AI Generates

Scenario 01 — Full Requisition Cancellation, Reason = Duplicate Request
Scenario 02 — Single-Line Cancellation on Multi-Line Requisition
Scenario 03 — Cancellation Before Approval
Scenario 04 — Cancellation After Rejection
Scenario 05 — Already-Cancelled Requisition (Negative)
Scenario 06 — PO-Converted Line 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 requisition, requester and line details remain within the customer's controlled SyntraFlow environment and access model.

Example Test Variations

Representative examples of cancel-requisition 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 Requisition	Positive/Line/Full	Entire requisition cancelled	Syntra Ready
VAR-002	Cancel Single Requisition Line	Positive/Line/Full	Only one line of a multi-line requisition cancelled	Syntra Ready
VAR-003	Cancel Before Approval	Positive/Timing	Requisition cancelled while still pending approval	Syntra Ready
VAR-004	Cancel After Rejection	Positive/Timing	Requisition cancelled after being rejected by an approver	Syntra Ready
VAR-005	Cancel With Reason — Duplicate Request	Positive	Cancellation reason = Duplicate Request	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 requisition	Syntra Ready
VAR-008	Cancel by Original Requester	Positive	Cancelled by the original requester	Syntra Ready
VAR-009	Attempt to Cancel an Already-Cancelled Requisition	Negative	Requisition status is already Cancelled	Syntra Ready
VAR-010	Attempt to Cancel a PO-Converted Line	Negative/Line/Full	Requisition line already converted to a purchase order	Syntra Ready
VAR-011	Cancellation Attempted by Unauthorized User	Negative	User lacks the cancel-requisition privilege	Syntra Ready
VAR-012	Cancellation Attempted on Invalid Status	Negative/Timing	Requisition or line is in a status that does not support cancellation	Syntra Ready
VAR-013	Missing Cancellation Reason	Negative	Required cancellation reason left blank	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 requisition or requisition line.

Eligible Requisition + Valid Cancellation Reason → Requisition Cancelled Successfully

Negative Testing

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

Already-Cancelled Requisition → Expected Duplicate-Cancellation Validation
PO-Converted Line → Expected Cancellation-Restricted Validation
Missing Cancellation Reason → Expected Required-Field Validation
Unauthorized User → Expected Security Validation
Invalid Requisition Status → Expected Status Validation

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

Requisition Cancellation Regression Pack

Cancel Full Requisition
Cancel Single Requisition Line
Cancel Before Approval
Cancel After Rejection
Cancel With Reason — Duplicate Request
Cancel Multiple Lines Individually
Attempt to Cancel an Already-Cancelled Requisition
Attempt to Cancel a PO-Converted Line
Cancellation Attempted by Unauthorized User
Missing Cancellation Reason

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

Once scheduled, SyntraFlow executes the selected cancel-requisition 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	Requisition 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 requisition is a control action. Jarvis can generate persona-based variations to confirm that only authorized users can cancel requisitions, using role and privilege data available through DataVault.

Persona	Action	Expected	Syntra Result
Requester	Cancel Own Requisition	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 Requisition, 7 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 Requisition

May internally include

Open Requisitions Work Area → Focus Search → Enter Requisition Number → Search → Select Requisition → Confirm Eligible Status

Business Step

Confirm Cancellation

May internally include

Review Cancellation Details → Click Confirm/Submit → Capture Confirmation Response → Refresh Requisition Status

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 Requisition/Line Unavailable for Downstream Processing	Pass	Pass

Related Requisition Tests

Cancelling a requisition is the final stage of the requisition lifecycle covered in this cluster — explore the related change, reject and create scenarios below.

Change Requisition Reject Requisition Create Purchase Requisition

Turn This Standard Test into Your Oracle Requisition Regression Suite

Start with the Syntra Standard cancel-requisition 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 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 qualifies a requisition for cancellation?

A requisition or requisition line generally qualifies for cancellation when it is still in an eligible status — for example, incomplete, pending approval, or approved but not yet actioned downstream. Exact eligibility rules depend on the customer's Oracle Fusion configuration.

What is the difference between rejecting and cancelling a requisition?

Rejecting a requisition is typically an approver's response during the approval workflow, returning the requisition to the requester for correction or resubmission. Cancelling is a separate action, available at various stages, that permanently ends the requisition or line rather than routing it back for rework.

Can a requisition that has already been converted to a purchase order still be cancelled?

Typically not directly — once a requisition line has been converted to a purchase order, cancellation is usually restricted or must instead be handled through cancellation of the resulting purchase order, depending on the customer's Oracle Fusion configuration. This scenario includes a negative variation confirming that expected restriction.

What security considerations apply to cancelling a requisition?

Cancelling a requisition is a control action that should be restricted to authorized users. This scenario includes a negative variation confirming that a user without the appropriate security/privilege is correctly prevented from cancelling a requisition.

How does SyntraFlow help determine why a cancel-requisition test failed?

SyntraFlow's execution evidence is designed to help distinguish expected Oracle validations from genuine issues. For example: Cancel Requisition failed — likely category EXPECTED_VALIDATION — evidence: the requisition line had already been converted to a purchase order — recommended action: this is typically expected behavior once downstream processing has started, and no action is needed unless the purchase order itself requires cancellation. A failure should not be labeled an Oracle defect without supporting evidence.