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

Syntra Standard Oracle Test Library

Oracle Fusion Submit Requisition Test Cases

Validate that a complete draft requisition is submitted into Oracle Fusion's configured approval flow, that its status changes correctly, and that approval routing begins where approval is required.

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

Test Objective

The objective of this test is to validate that a complete draft requisition — with all mandatory header and line data captured — can be submitted into Oracle Fusion's configured approval flow, and that the requisition's status, approval routing and traceability reflect the submission correctly.

The scenario should confirm that:

the requisition submits successfully once all mandatory data is present
the requisition status changes from draft to the correct in-process or approval status
approval routing begins where an approval rule applies to the requisition
requisitions that do not require approval complete without unnecessary routing
the submitted requisition remains traceable back to the originating draft
Oracle's validations correctly prevent submission of an incomplete or ineligible requisition

This scenario covers submission of an already-complete draft requisition into the configured approval workflow within Oracle Fusion Procurement TEST/UAT environments. It does not cover creation of the requisition itself, which is covered by the separate Create Purchase Requisition scenario, or the approval action itself, which is covered by the separate Approve Requisition scenario in the same Requisitions family.

When to Use This Test

Functional testing of requisition submission and approval-routing initiation for a new Oracle Fusion Procurement implementation
Regression testing of submission and status-transition behavior after an Oracle quarterly update
UAT sign-off for procurement teams that routinely submit single-line, multi-line, low-value and high-value requisitions
Baseline case referenced by the approve-requisition and change-requisition scenarios within the same Requisitions family

Where This Test Fits in the Requisition-to-Approval Flow

Create Requisition

→

Submit Requisition

→

Approve Requisition

→

Change Requisition

Submit Requisition is the step that moves a complete draft requisition out of edit mode and into Oracle Fusion's configured approval flow. Exact routing, approval hierarchy and eligibility rules depend on requisitioning business unit, category, amount thresholds and customer-specific Oracle Fusion configuration.

← Previous Stage

Create Purchase Requisition

Next Stage →

Approve Requisition

Preconditions

A complete draft requisition exists in Oracle Fusion Procurement with all mandatory header and line data captured.
The requester submitting the requisition holds the appropriate submit privileges.
An approval workflow is configured for the requisitioning business unit and category, where applicable.
The requisition's charge account, category and supplier (where entered) are valid and active.
The test user is signed in to an Oracle Fusion Procurement TEST/UAT environment.

Exact submission eligibility, approval rule evaluation and validation messages may vary by requisitioning business unit, category, amount threshold and customer-specific Oracle Fusion configuration.

Sample Test Data

Requisition Number	${REQUISITION_NUMBER}
Requisitioning BU	${REQUISITIONING_BU}
Requester	${REQUESTER}
Total Amount	${TOTAL_AMOUNT}
Category	${CATEGORY}
Charge Account	${CHARGE_ACCOUNT}
Need-By Date	${NEED_BY_DATE}
Line Count	${LINE_COUNT}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Total amount, category and business unit typically determine which approval rule, if any, applies to a given submission.

Test Steps

8 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 using an authorised procurement test user.	Oracle Fusion Procurement is accessible to the signed-in test user.
2	Navigate to Requisitions Navigate to the Requisitions work area.	The Requisitions work area opens successfully.
3	Locate the Draft Requisition Search for and open the complete draft requisition to be submitted. ${REQUISITION_NUMBER} This single business step replaces multiple technical actions such as opening requisition search, entering search criteria and selecting the result.	The correct draft requisition opens for review.
4	Review Requisition Details Review the requisition header and line details, including requester, requisitioning BU, category and charge account.	Requisition header and line details display as expected for the draft.
5	Confirm Mandatory Data Is Complete Confirm that all mandatory header and line fields required for submission are populated. Confirming completeness before submission helps distinguish a data-completeness issue from a submission or configuration issue if the test later fails.	No mandatory fields are missing before submission is attempted.
6	Submit the Requisition Select the option to submit the requisition into the configured approval flow.	Oracle Fusion accepts the submission without unexpected errors.
7	Verify Status Changed CorrectlyBusiness assertion Reopen or refresh the requisition and review its status. This is a primary business assertion for the scenario — a correct status transition is the expected pass condition, not merely an accepted submission.	The requisition status correctly reflects submission, such as In Process or Pending Approval.
8	Verify Approval Routing Initiated Where ConfiguredBusiness assertion Review the requisition's approval history or status where an approval rule applies to this requisition.	Approval routing begins correctly where an approval rule applies; requisitions with no applicable rule complete without unnecessary routing.

Expected Results

The requisition submits successfully once all mandatory data is present.
The requisition status changes correctly to reflect submission.
Approval routing begins where an approval rule applies to the requisition.
Requisitions that do not require approval complete without unnecessary routing.
The submitted requisition remains traceable back to the originating draft.
Fields not part of the submission action remain unchanged.

Key Validation Checkpoints

Submission succeeds for a complete, eligible requisition.
Requisition status changes correctly following submission.
Approval routing begins where configured for the requisition.
The requisition remains traceable throughout the submission process.

Core Business Scenario

Submit 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 Submit Requisition business scenario. Jarvis AI can extend this scenario by generating additional value, category, business-unit, security and configuration variations using customer-specific test data available through Syntra DataVault.

Teams do not need to manually build a separate test for every category, business unit or approval-threshold combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Value, Category and Security variations for the customer's environment — with approval-routing coverage weighted especially heavily, since correct status transition and routing initiation are the core of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Submit Requisition business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — requisitions, categories, accounts and business units.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant value, category and security variations.

Positive + Negative Test Variations

Valid submission scenarios and edge cases such as missing data, invalid accounts or security restrictions.

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 possible category, business unit, value tier or security condition, SyntraFlow maintains one core Submit Requisition scenario and allows Jarvis AI to generate value-driven, category-driven and security-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Submit a valid, complete requisition
Submit a single-line requisition
Submit a multi-line requisition
Submit a low-value requisition
Submit a high-value requisition
Submit requisitions across different categories
Submit requisitions across different requisitioning business units
Submit a requisition that requires approval routing

Negative Scenarios

Attempt submission with missing mandatory data
Attempt submission with an invalid charge account
Attempt submission with an invalid supplier
Attempt submission referencing an inactive item
Attempt submission of a requisition not eligible for submission
Attempt submission blocked by a security restriction
Attempt submission blocked by configuration that prevents submission

These are representative examples only. Negative-scenario behavior and available submission paths 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 every category, business unit, value tier and account combination in a real Oracle Fusion Procurement environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Submit Requisition scenarios relevant to the customer's actual implementation.

Standard Library Definition

Requisition Number   ${REQUISITION_NUMBER}
Requisitioning BU    ${REQUISITIONING_BU}
Requester            ${REQUESTER}
Total Amount         ${TOTAL_AMOUNT}
Category             ${CATEGORY}
Charge Account       ${CHARGE_ACCOUNT}
Need-By Date         ${NEED_BY_DATE}
Line Count           ${LINE_COUNT}

DataVault

Requisitions
  Complete draft requisitions eligible for submission
Business Units
  Active requisitioning business units
Categories
  Active procurement category catalog
Accounts
  Valid charge accounts per business unit
Approval Rules
  Configured thresholds and routing per category / BU
Requesters
  Active requesters with submit privileges

Jarvis AI Generates

Scenario 01 — Low-Value Office Supplies Requisition
Scenario 02 — High-Value IT Equipment Requisition
Scenario 03 — Multi-Line Requisition Across Categories
Scenario 04 — Requisition Requiring Approval Routing
Scenario 05 — Invalid Charge Account
Scenario 06 — Unauthorized User Attempts Submission
...

Submit Requisition test data can include sensitive procurement categories such as amounts, accounts and supplier information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific requisition 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 Submit Requisition scenarios Jarvis can generate from this business scenario, spanning value, category 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	Submit Valid Requisition	Positive	Complete requisition submitted successfully into the approval flow	Syntra Ready
VAR-002	Single-Line Requisition	Positive	Requisition with a single line submitted successfully	Syntra Ready
VAR-003	Multi-Line Requisition	Positive	Requisition with multiple lines submitted successfully	Syntra Ready
VAR-004	Low-Value Requisition	Positive/Value	Requisition below approval threshold submits without routing	Syntra Ready
VAR-005	High-Value Requisition	Positive/Value	Requisition above approval threshold triggers approval routing	Syntra Ready
VAR-006	Different Category Requisition	Positive/Category	Requisition submitted successfully across a different procurement category	Syntra Ready
VAR-007	Different Business Unit Requisition	Positive	Requisition submitted successfully from a different requisitioning business unit	Syntra Ready
VAR-008	Approval-Required Requisition	Positive	Requisition submission correctly initiates configured approval routing	Syntra Ready
VAR-009	Missing Mandatory Data	Negative	Submission attempted with missing mandatory header or line data	Syntra Ready
VAR-010	Invalid Charge Account	Negative	Submission attempted with an invalid or inactive charge account	Syntra Ready
VAR-011	Invalid Supplier	Negative	Submission attempted with an invalid or inactive supplier	Syntra Ready
VAR-012	Inactive Item	Negative	Submission attempted referencing an inactive item	Syntra Ready
VAR-013	Requisition Not Eligible for Submission	Negative	Submission attempted on a requisition that does not meet eligibility conditions	Syntra Ready
VAR-014	Security Restriction	Negative/Security	Submission attempted by a user without submit privileges for the requisition	Syntra Ready
VAR-015	Configuration Prevents Submission	Negative	Submission blocked by configuration, such as a missing or invalid approval rule	Syntra Ready

Automatically Expand Positive and Negative Submit Requisition Coverage

Positive Testing

Jarvis generates scenarios using requisition values, categories and business units expected to submit successfully into Oracle Fusion's configured approval flow.

Complete Requisition + Valid Category + Valid Charge Account → Requisition Submitted and Status Updated

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around mandatory data, account and supplier validity, item status, eligibility, security and configuration.

Missing Mandatory Data → Expected Data Validation
Invalid Charge Account → Expected Account Validation
Invalid Supplier → Expected Supplier Validation
Unauthorized User → Expected Access Restriction
Configuration Prevents Submission → Expected Configuration 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 Submit Requisition scenarios and group them into reusable execution packs.

Procurement Submit Requisition Regression Pack

Submit Valid Requisition
Single-Line Requisition
Multi-Line Requisition
Low-Value Requisition
High-Value Requisition
Different Category Requisition
Missing Mandatory Data
Invalid Charge Account
Security Restriction
Configuration Prevents Submission

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

Once scheduled, SyntraFlow executes the selected Submit 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 Submit Requisition Regression Pack
Schedule	Quarterly Update Regression
Tests	15 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 submit a requisition is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that submit access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Requester	Submit Own Requisition	Allowed	PASS
Unauthorized User	Attempts Submit	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 Submit Requisition scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Value, Category 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 — Submit 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 Draft Requisition

May internally include

Open Requisition Search → Enter Requisition Number → Search → Select Requisition → Open Requisition Details → Confirm

Business Step

Verify Approval Routing Initiated Where Configured

May internally include

Open Approval History → Read Routing Status → Compare Against Applicable Approval Rule

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 requisition was routed or statused correctly — 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
Submit the Requisition	Pass	—
Verify Status Changed Correctly	Pass	Pass
Verify Approval Routing Initiated Where Configured	Pass	Pass

Related Requisition Tests

Submit Requisition is part of the same requisition-to-approval lifecycle — explore the related create, approve and change scenarios below.

Create Purchase Requisition Approve Requisition Change Requisition

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

Start with the Syntra Standard Submit Requisition test, use DataVault to provide environment-specific test data, let Jarvis generate additional value, category 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 does this test validate?

This test validates that a complete draft requisition can be submitted into Oracle Fusion's configured approval flow, that its status changes correctly, and that approval routing begins where an approval rule applies.

What happens if mandatory data is missing from the requisition?

Oracle Fusion is expected to prevent submission and surface a validation message identifying the missing mandatory data. This test's negative variations exercise that behavior as an expected pass condition, not a failure.

How does approval routing get triggered on submission?

Approval routing depends on the approval rules configured for the requisitioning business unit, category and amount thresholds. Where an applicable rule exists, submission is expected to initiate the corresponding approval routing; where no rule applies, the requisition is expected to complete without unnecessary routing.

Do all these variations need separate test library pages?

No. Jarvis AI generates positive, negative, value, category and security variations of Submit Requisition from this single canonical scenario definition rather than maintaining a separate indexable page for each combination.

Does this test use real requisition or supplier data?

No. The public Syntra Standard Test Library uses illustrative placeholder test data such as ${REQUISITION_NUMBER} and ${TOTAL_AMOUNT}, 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.