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

Syntra Standard Oracle Test Library

Oracle Fusion Reject Requisition Test Cases

Validate that an approver's rejection of a pending requisition is processed correctly in Oracle Fusion Procurement — the requisition status updates to Rejected, the rejection reason is retained, and the requester is notified where notifications are configured.

Test ID	ORCL.P2P.PROC.REQ.REJECT
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 18 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that an approver's rejection of a requisition pending approval is captured and applied correctly in Oracle Fusion Procurement, and that the resulting status, rejection reason and requester notification behave as expected.

The scenario should confirm that:

the correct requisition is moved out of pending approval when rejected
the requisition status is correctly updated to Rejected
the rejection reason entered by the approver is retained on the requisition record
the requester is notified of the rejection where notifications are configured
the rejection is recorded correctly regardless of single-level or multi-level approval routing
the requisition can be corrected and resubmitted, or otherwise progressed, where the business process allows it

This scenario covers the rejection of a requisition that is pending approval within Oracle Fusion Procurement TEST/UAT environments. It does not cover the requisition approval decision itself (Approve Requisition), general edits to requisition content (Change Requisition), or withdrawal of a requisition by the requester (Cancel Requisition), which are covered by the related scenarios in the same requisition workflow.

When to Use This Test

Functional testing of requisition rejection behavior for a new Oracle Fusion Procurement implementation
Regression testing of rejection status, rejection-reason retention and requester notification behavior after an Oracle quarterly update
UAT sign-off for approval and procurement teams that routinely reject requisitions requiring correction
Companion scenario to Approve Requisition, Change Requisition and Cancel Requisition within the same requisition approval workflow

Where This Test Fits in the Requisition Approval Workflow

Create Requisition

→

Submit for Approval

→

Approve

→

Reject

→

Change

→

Cancel

Reject is one of the two decisions available to an approver reviewing a submitted requisition, alongside Approve. A rejected requisition typically returns to the requester, who may correct and resubmit it through Change Requisition, or withdraw it through Cancel Requisition, depending on customer-specific business process and configuration.

Preconditions

A requisition exists in Oracle Fusion Procurement in Pending Approval status.
The test user is assigned as the approver, or an eligible approver, for the requisition and holds reject privileges within the approval workflow.
Where rejection-reason entry is required or offered by configuration, valid rejection reason values are available.
The requisition is visible in the approver's approvals worklist.

Exact approval routing, rejection-reason requirements and notification behavior may vary by Oracle Fusion implementation, business unit and customer-specific approval configuration.

Sample Test Data

Requisition Number	${REQUISITION_NUMBER}
Approver	${APPROVER}
Rejection Reason	${REJECTION_REASON}
Requester	${REQUESTER}
Business Unit	${BUSINESS_UNIT}
Requisition Amount	${REQUISITION_AMOUNT}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Rejection reason entry may be optional or required depending on customer-specific approval configuration.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to Approvals Worklist Sign in to Oracle Fusion using an authorised approver test user and navigate to the approvals worklist.	The approvals worklist opens and displays requisitions pending the approver's action.
2	Locate the Pending Requisition Search for and open the requisition awaiting approval in the worklist. ${REQUISITION_NUMBER} This single business step replaces multiple technical actions such as opening the worklist, entering search criteria and selecting the result.	The correct requisition opens showing its current pending-approval status.
3	Review Requisition Details Review the requisition header, lines, requester and amount before deciding on an approval action. ${REQUESTER}	Requisition details display correctly for the approver's review.
4	Select Reject Select the Reject action on the requisition approval task.	The reject entry screen or rejection-reason panel opens for the approver.
5	Enter Rejection Reason Enter the reason for rejecting the requisition, where reason entry is required or offered by configuration. ${REJECTION_REASON}	The rejection reason is accepted and attached to the pending rejection.
6	Confirm Rejection Confirm and submit the rejection for processing in the test environment. ${APPROVER}	Oracle Fusion processes the rejection without unexpected errors.
7	Verify Requisition Status Is RejectedBusiness assertion Reopen or refresh the requisition and confirm its resulting status. This is the primary business assertion for the scenario — a correctly updated Rejected status is the expected pass condition, not merely a successful submission.	The requisition status is correctly updated to Rejected.
8	Verify Rejection Reason and Requester NotificationBusiness assertion Review the requisition's approval history and confirm the rejection reason and notification behavior.	The rejection reason is retained on the requisition, and the requester is notified where notifications are configured.

Expected Results

The rejection is accepted and processed for the correct requisition.
The requisition status is correctly updated to Rejected.
The rejection reason entered by the approver is retained on the requisition.
The requester is notified of the rejection where notifications are configured.
The requisition can be corrected and resubmitted, or cancelled, depending on business process.
The rejection is visible and traceable in the requisition's approval history.

Key Validation Checkpoints

Requisition status is correctly updated to Rejected.
The rejection reason is retained on the requisition record.
The requester is notified of the rejection where notification is configured.
The requisition can be corrected and resubmitted if the business process allows it.

Core Business Scenario

Reject 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 Reject Requisition business scenario. Jarvis AI can extend this scenario by generating additional rejection-reason, routing, boundary and security variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every rejection reason or approval-routing combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Security variations for the customer's environment — covering single-level and multi-level approval routing, alternate rejection reasons, and access-control checks alongside the core rejection flow.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Reject Requisition business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Requisitions, Approvers, Rejection Reasons and Requesters.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant positive, negative, boundary and security variations.

Positive + Negative Test Variations

Valid rejection scenarios and edge cases such as unauthorized reject attempts, missing rejection reasons or already-approved requisitions.

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 a separate test page for every rejection reason, approval-routing configuration or access scenario, SyntraFlow maintains one core Reject Requisition scenario and allows Jarvis AI to generate reason-driven, routing-specific and security-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Reject a valid requisition that is currently pending approval
Reject using different, valid rejection reasons
Reject a requisition routed through single-level approval
Reject a requisition routed through multi-level approval
Reject a requisition, then correct and resubmit it for a new approval cycle

Negative Scenarios

Attempt to reject a requisition that is not currently in an approval-pending state
Unauthorized user attempts to reject a requisition they are not assigned to approve
Attempt to reject without entering a rejection reason where a reason is required
Attempt to reject a requisition that has already been approved or already cancelled

These are representative examples only. Negative-scenario behavior and available rejection-reason options can depend on the customer's Oracle Fusion configuration, approval rules and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every approver, rejection reason and approval-routing combination in a real Oracle Fusion Procurement environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Reject Requisition scenarios relevant to the customer's actual implementation.

Standard Library Definition

Requisition Number    ${REQUISITION_NUMBER}
Approver               ${APPROVER}
Rejection Reason        ${REJECTION_REASON}
Requester               ${REQUESTER}
Business Unit           ${BUSINESS_UNIT}
Requisition Amount      ${REQUISITION_AMOUNT}

DataVault

Requisitions
  Requisitions currently pending approval
Approvers
  Active approvers eligible for the requisition's routing
Rejection Reasons
  Configured rejection reason values
Requesters
  Requesters associated with pending requisitions
Business Units
  Business units in scope for approval testing

Jarvis AI Generates

Scenario 01 — Single-Level Reject with Standard Reason
Scenario 02 — Multi-Level Reject at First Approval Stage
Scenario 03 — Reject with Alternate Rejection Reason
Scenario 04 — Reject Then Requester Resubmits
Scenario 05 — Unauthorized User Attempts Reject
Scenario 06 — Missing Rejection Reason Where Required
...

Reject Requisition test data can include sensitive procurement categories such as requester identity, approver identity, business unit and requisition amount. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific requisition and approver dimensions remain within the customer's controlled SyntraFlow environment and access model, protected according to DataVault's data masking policies. See /datavault/ for details.

Example Test Variations

Representative examples of Reject Requisition scenarios Jarvis can generate from this business scenario, spanning rejection-reason, routing and security conditions. 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	Reject Valid Submitted Requisition	Positive	Standard rejection of a requisition pending approval	Syntra Ready
VAR-002	Reject with Standard Rejection Reason	Positive/Reason	Rejection recorded with a standard configured reason	Syntra Ready
VAR-003	Reject with Alternate Rejection Reason	Positive/Reason	Rejection recorded with a different valid reason value	Syntra Ready
VAR-004	Single-Level Approval Reject	Positive	Requisition routed through a single approval stage before rejection	Syntra Ready
VAR-005	Multi-Level Approval Reject	Positive	Requisition rejected at one stage of a multi-level approval chain	Syntra Ready
VAR-006	Reject Then Correct and Resubmit	Positive/Resubmit	Requester corrects the requisition and resubmits after rejection	Syntra Ready
VAR-007	Reject Then Requester Cancels	Positive/Resubmit	Requester cancels the requisition instead of resubmitting after rejection	Syntra Ready
VAR-008	Requisition Not in Approval	Negative	Reject attempted on a requisition not currently pending approval	Syntra Ready
VAR-009	Unauthorized Reject Attempt	Negative	User not assigned as approver attempts to reject the requisition	Syntra Ready
VAR-010	Missing Required Rejection Reason	Negative/Reason	Reject submitted without a required rejection reason	Syntra Ready
VAR-011	Reject Already Approved Requisition	Negative	Reject attempted on a requisition already approved	Syntra Ready
VAR-012	Reject Already Cancelled Requisition	Negative	Reject attempted on a requisition already cancelled	Syntra Ready
VAR-013	Resubmit After Reject with Corrected Data	Positive/Resubmit	Corrected requisition resubmitted and routed for a new approval cycle	Syntra Ready

Automatically Expand Positive and Negative Reject Requisition Coverage

Positive Testing

Jarvis generates scenarios using approvers, rejection reasons and approval-routing combinations expected to successfully reject a pending requisition while Oracle Fusion correctly updates status, retains the reason and notifies the requester.

Assigned Approver + Requisition Pending Approval + Valid Rejection Reason → Requisition Status Rejected and Requester Notified

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around approval state, required reason entry and reject-action security.

Requisition Not Pending Approval → Expected State Validation
Unauthorized User → Expected Access Restriction
Missing Required Rejection Reason → Expected Reason Validation
Already Approved or Cancelled Requisition → Expected State 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 Reject Requisition scenarios and group them into reusable execution packs.

Procurement Reject Requisition Regression Pack

Reject Valid Submitted Requisition
Reject with Standard Rejection Reason
Reject with Alternate Rejection Reason
Single-Level Approval Reject
Multi-Level Approval Reject
Reject Then Correct and Resubmit
Requisition Not in Approval
Unauthorized Reject Attempt
Missing Required Rejection Reason
Reject Already Approved Requisition

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

Once scheduled, SyntraFlow executes the selected Reject 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	Procurement Reject Requisition 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

Access to reject a requisition is controlled by Oracle Fusion's approval and security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that reject access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Approver	Reject Assigned Requisition	Allowed	PASS
Unauthorized User	Attempts Reject	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 Reject Requisition scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Security 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 Library — Reject Requisition, 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

Locate the Pending Requisition

May internally include

Open Approvals Worklist → Enter Requisition Number → Search → Select Requisition → Open Approval Task → Confirm

Business Step

Verify Requisition Status Is Rejected

May internally include

Reopen Requisition → Read Status Field → Compare Against Expected Rejected 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 rejection was recorded correctly, the reason was retained, or the requester was notified — 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 Rejection Reason	Pass	—
Confirm Rejection	Pass	—
Verify Requisition Status Is Rejected	Pass	Pass

Related Requisition Tests

Reject Requisition is one of several requisition approval-workflow scenarios within the same Procure-to-Pay process — explore the related approve, change and cancel scenarios below.

Approve Requisition Change Requisition Cancel Requisition

Turn This Standard Test into Your Oracle Procurement Reject Requisition Regression Suite

Start with the Syntra Standard Reject Requisition test, use DataVault to provide environment-specific test data, let Jarvis generate additional reason, routing and security 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

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

Frequently Asked Questions

What happens to a requisition after it is rejected in Oracle Fusion?

When an approver rejects a requisition, its status is updated to Rejected and it is removed from the active approvals worklist. Depending on customer-specific business process, the requester can then correct and resubmit the requisition, or cancel it, rather than the rejection being a final dead end.

Can a rejected requisition be resubmitted?

In many Oracle Fusion configurations, yes — the requester can amend the rejected requisition and resubmit it for a new approval cycle. This test validates the rejection itself; resubmission after correction is exercised as a related variation and, where content changes are involved, overlaps with the Change Requisition scenario.

How does requester notification work after a rejection?

Where notifications are configured, Oracle Fusion notifies the requester that their requisition has been rejected, typically including the rejection reason if one was entered. This test verifies that notification and reason retention occur as configured rather than asserting a single universal notification behavior.

How is security tested for the Reject Requisition scenario?

SyntraFlow can generate persona-based variations that confirm only an assigned or eligible approver is able to reject a given requisition, and that an unauthorized user attempting to reject it is correctly prevented from doing so by Oracle Fusion's security configuration.

Does this test use real requisition or requester data?

No. The public Syntra Standard Test Library uses illustrative placeholder test data such as ${REQUISITION_NUMBER} and ${REJECTION_REASON}, executed only against Oracle Fusion TEST/UAT environments. Where DataVault is connected, customer-specific test data can be used, protected according to DataVault's data masking policies.