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

Syntra Standard Oracle Test Library

Oracle Fusion Create Purchase Requisition Test Cases

Validate that a purchase requisition is created correctly in Oracle Fusion SCM using a valid requester, requisitioning Business Unit, item or category, supplier where applicable, quantity, price, deliver-to location and charge account.

Test ID	ORCL.P2P.PROC.REQ.CREATE
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 11 business-readable test steps; SyntraFlow's automation executes approximately 26 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a purchase requisition can be created in Oracle Fusion SCM using a valid requester, requisitioning Business Unit, item or category, supplier where applicable, quantity, price, deliver-to location and charge account, and that the resulting requisition is created with correct line detail.

The scenario should confirm that:

the requisition is created for the correct requester and requisitioning Business Unit
line detail — item or category, quantity, unit of measure and price — is captured correctly
the deliver-to location and charge account entered on the line are correct
supplier and supplier site information is captured correctly where applicable
the requisition receives a system-generated requisition number
Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers creation of a single or multi-line purchase requisition in Oracle Fusion SCM Procurement TEST/UAT environments. It does not cover submission for approval, subsequent changes, or cancellation, which are covered by the separate Submit Requisition, Change Requisition and Cancel Requisition scenarios in the same Requisitions cluster.

When to Use This Test

Functional testing of purchase requisition creation for a new Oracle Fusion SCM Procurement implementation
Regression testing of requisition creation behavior after an Oracle quarterly update
UAT sign-off for procurement teams that routinely raise catalog and noncatalog requisitions
Baseline case referenced by the Submit Requisition, Change Requisition and Cancel Requisition scenarios within the same Requisitions cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during requisition creation before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Procure-to-Pay Requisitions Process

Navigate to Procurement

→

Create Requisition

→

Enter Item/Category

→

Enter Quantity/Price

→

Select Deliver-to

→

Select Charge Account

→

Review

Create Purchase Requisition is the entry point of the requisition-to-purchase-order flow within Procure-to-Pay. Once a requisition is created, it is typically submitted for approval, and may subsequently be changed or cancelled — covered by the Submit Requisition, Change Requisition and Cancel Requisition scenarios in this same cluster. Exact fields available, approval routing and validation depend on requisitioning BU configuration, item/category setup and customer-specific Oracle Fusion configuration.

Next Stage →

Submit Requisition

Preconditions

A requisitioning Business Unit is configured in the target Oracle Fusion SCM environment.
The test requester has appropriate access to raise a requisition for the requisitioning BU.
The item or category being requisitioned is active in the item/category catalog.
Where a supplier is required on the line, the supplier and supplier site are active.
The charge account entered on the line is valid and open for the requisition date.
The deliver-to location used on the requisition is configured and active.

Exact field availability, mandatory fields, approval routing and validation messages may vary by Oracle Fusion implementation, requisitioning BU configuration, procurement category setup and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Requisitioning BU	${REQUISITIONING_BU}
Requester	${REQUESTER}
Item	${ITEM}
Category	${CATEGORY}
Supplier	${SUPPLIER}
Supplier Site	${SUPPLIER_SITE}
Quantity	${QUANTITY}
UOM	${UOM}
Price	${PRICE}
Currency	${CURRENCY}
Deliver-to Location	${DELIVER_TO_LOCATION}
Charge Account	${CHARGE_ACCOUNT}
Need-by Date	${NEED_BY_DATE}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Not every field applies to every line — for example, supplier and supplier site typically apply to noncatalog lines, while catalog lines may derive supplier information from the catalog source.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to Procurement Sign in to Oracle Fusion using an authorised procurement test user and navigate to the Procurement work area.	The Procurement work area opens successfully.
2	Navigate to Requisitions Open the Requisitions page to begin creating a new purchase requisition. ${REQUISITIONING_BU}	The requisition creation page opens for the correct requisitioning Business Unit.
3	Create New Requisition Initiate a new requisition for the test requester. ${REQUESTER} This single business step replaces multiple technical actions such as opening the create page, confirming the requester and confirming the requisitioning BU.	A new, unsaved requisition is opened for the correct requester.
4	Select Item or Enter Noncatalog Details Search for and select a catalog item, or enter noncatalog line details including item description and category where a catalog item is not used. ${ITEM} / ${CATEGORY}	The item or noncatalog line detail is accepted and added to the requisition.
5	Enter Quantity and Price Enter the requisition line quantity, unit of measure and price. ${QUANTITY} / ${UOM} / ${PRICE} / ${CURRENCY}	Quantity, UOM and price are accepted without unexpected validation errors.
6	Select Deliver-to Location Select the deliver-to location for the requisition line. ${DELIVER_TO_LOCATION}	The deliver-to location is accepted and reflected on the line.
7	Select Charge Account Select or confirm the charge account that the requisition line will be costed to. ${CHARGE_ACCOUNT}	The charge account is accepted and reflected on the line.
8	Enter Need-by Date Enter the date by which the requisitioned item or service is needed. ${NEED_BY_DATE}	The need-by date is accepted without unexpected validation errors.
9	Review Requisition Review the requisition header and line detail as calculated by Oracle Fusion before saving. Reviewing the requisition before saving lets the tester catch an incorrect field entry before the requisition is created.	The reviewed requisition reflects the entered requester, item/category, quantity, price, deliver-to location and charge account.
10	Save the Requisition Save the requisition for creation in the test environment.	Oracle Fusion successfully processes the requisition without unexpected errors.
11	Verify Requisition Number and StatusBusiness assertion Reopen or refresh the requisition and confirm the generated requisition number, status and line detail. This is the primary business assertion for the scenario — a correctly created requisition with accurate line detail is the expected pass condition, not merely a successful save.	A requisition number is generated, the requisition status is correct, and requester, quantity, price, deliver-to location and charge account match the entered data.

Expected Results

The requisition is created for the correct requester and requisitioning Business Unit.
A system-generated requisition number is assigned.
Line data — item/category, quantity, UOM and price — is correct.
The deliver-to location and charge account on the line are correct.
Supplier and supplier site are correct where applicable.
The requisition status correctly reflects a newly created, unsubmitted requisition.
The requisition is visible and traceable for the test requester.

Key Validation Checkpoints

Requisition created.
Requisition number generated.
Line data correct.
Requester correct.
Quantity/price correct.
Account/location correct.
Status correct.

Core Business Scenario

Create Purchase 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 Create Purchase Requisition business scenario. Jarvis AI can extend this scenario by generating additional item/category, supplier, quantity, currency, account 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 item, supplier, quantity or account combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Security variations for the customer's environment — including large-quantity and high-value boundary cases, since correctly enforced validation at the edges of expected values is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Create Purchase Requisition business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Requesters, Items, Categories, Suppliers, Accounts and Locations.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant item, supplier, quantity, currency and security variations.

Positive + Negative Test Variations

Valid requisition scenarios and edge cases such as inactive items, invalid suppliers or restricted access.

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 item, category, supplier, quantity, currency or account combination, SyntraFlow maintains one core Create Purchase Requisition scenario and allows Jarvis AI to generate item, supplier, quantity, currency and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Create Purchase 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

Create a single-line requisition
Create a multi-line requisition
Create a requisition using a catalog item
Create a requisition using a noncatalog item, where supported
Create requisitions with different quantities
Create requisitions in different currencies
Create requisitions with different suppliers
Create requisitions with different categories
Create requisitions with different delivery locations
Create requisitions with different charge accounts
Create a requisition with a future need-by date

Negative Scenarios

Attempt to requisition an inactive item
Enter an invalid category
Enter an invalid supplier
Enter an invalid supplier site
Enter a zero or negative quantity
Enter an invalid unit of measure
Enter an invalid charge account
Attempt to save without a deliver-to location
Enter an invalid need-by date
Attempt to save with a missing mandatory field
Attempt creation under a security restriction preventing access

These are representative examples only. Negative-scenario behavior and available field combinations 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 item, category, supplier, quantity, currency and account combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Create Purchase Requisition scenarios relevant to the customer's actual implementation.

Standard Library Definition

Requisitioning BU      ${REQUISITIONING_BU}
Requester              ${REQUESTER}
Item                   ${ITEM}
Category               ${CATEGORY}
Supplier               ${SUPPLIER}
Supplier Site          ${SUPPLIER_SITE}
Quantity               ${QUANTITY}
UOM                    ${UOM}
Price                  ${PRICE}
Currency               ${CURRENCY}
Deliver-to Location    ${DELIVER_TO_LOCATION}
Charge Account         ${CHARGE_ACCOUNT}
Need-by Date           ${NEED_BY_DATE}

DataVault

Requesters
  Active requesters eligible to raise a requisition
Items / Categories
  Active catalog and noncatalog item/category values
Suppliers / Supplier Sites
  Active suppliers and sites per requisitioning BU
Accounts
  Valid, open charge accounts
Locations
  Configured deliver-to locations
Need-by Date
  Valid dates within an open period

Jarvis AI Generates

Scenario 01 — Requester A + Catalog Item + Single Line
Scenario 02 — Requester A + Noncatalog Item + Multi-Line
Scenario 03 — Requester B + Different Supplier and Currency
Scenario 04 — Requester C + Future Need-by Date
Scenario 05 — Inactive Item
Scenario 06 — Unauthorized User Attempts Create Requisition
...

Create Purchase Requisition test data can include sensitive procurement categories such as supplier, account and pricing information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific procurement 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 Create Purchase Requisition scenarios Jarvis can generate from this business scenario, spanning item/category, supplier, account and currency 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	Single-Line Requisition	Positive	Requisition created with a single requisition line	Syntra Ready
VAR-002	Multi-Line Requisition	Positive	Requisition created with multiple requisition lines	Syntra Ready
VAR-003	Catalog Item	Positive/Item/Category	Line created using a catalog-sourced item	Syntra Ready
VAR-004	Noncatalog Item	Positive/Item/Category	Line created using a manually entered noncatalog description and category	Syntra Ready
VAR-005	Different Quantities	Positive	Requisition created with a range of valid line quantities	Syntra Ready
VAR-006	Different Currencies	Positive/Currency	Requisition created in a currency other than the default	Syntra Ready
VAR-007	Different Suppliers	Positive/Supplier	Requisition created against an alternate active supplier and site	Syntra Ready
VAR-008	Different Categories	Positive/Item/Category	Requisition created using an alternate active procurement category	Syntra Ready
VAR-009	Different Delivery Locations	Positive	Requisition created with an alternate configured deliver-to location	Syntra Ready
VAR-010	Different Charge Accounts	Positive/Account	Requisition created against an alternate valid charge account	Syntra Ready
VAR-011	Future Need-by Date	Positive	Requisition created with a need-by date ahead of the current date	Syntra Ready
VAR-012	Inactive Item	Negative/Item/Category	Selected item is inactive as of the requisition date	Syntra Ready
VAR-013	Invalid Category	Negative/Item/Category	Selected category does not exist or is inactive	Syntra Ready
VAR-014	Invalid Supplier	Negative/Supplier	Selected supplier is invalid or inactive	Syntra Ready
VAR-015	Invalid Supplier Site	Negative/Supplier	Selected supplier site is invalid for the chosen supplier	Syntra Ready
VAR-016	Zero or Negative Quantity	Negative	Line quantity entered as zero or a negative value	Syntra Ready
VAR-017	Invalid UOM	Negative	Unit of measure entered does not exist or is invalid for the item	Syntra Ready
VAR-018	Invalid Account	Negative/Account	Charge account entered is invalid or closed	Syntra Ready
VAR-019	Missing Deliver-to Location	Negative	Requisition saved without a deliver-to location	Syntra Ready
VAR-020	Invalid Need-by Date	Negative	Need-by date entered outside a supported or open range	Syntra Ready
VAR-021	Missing Mandatory Field	Negative	A mandatory header or line field is left blank	Syntra Ready
VAR-022	Security Restriction — Unauthorized Create Requisition	Negative	Requesting user lacks access to create a requisition for the requisitioning BU	Syntra Ready

Automatically Expand Positive and Negative Requisition Coverage

Positive Testing

Jarvis generates scenarios using requester, item/category, supplier, quantity, price and account combinations expected to successfully create a purchase requisition in Oracle Fusion.

Valid Requester + Active Item + Valid Account + Valid Deliver-to Location → Requisition Created

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around item/category status, supplier status, account validity and security.

Inactive Item → Expected Item Validation
Invalid Supplier → Expected Supplier Validation
Invalid Charge Account → Expected Account Validation
Missing Deliver-to Location → Expected Mandatory Field Validation
Unauthorized User → Expected Access Restriction

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 Create Purchase Requisition scenarios and group them into reusable execution packs.

SCM Procurement Create Requisition Regression Pack

Single-Line Requisition
Multi-Line Requisition
Catalog Item
Noncatalog Item
Different Suppliers
Different Currencies
Different Charge Accounts
Future Need-by Date
Invalid Account
Security Restriction — Unauthorized Create 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 Create Purchase Requisition scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected Create Purchase 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	SCM Procurement Create Requisition Regression Pack
Schedule	Quarterly Update Regression
Tests	22 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 & Approval Variations

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

Persona	Action	Expected	Syntra Result
Requester	Create Requisition	Allowed	PASS
Unauthorized User	Attempts Create Requisition	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 Create Purchase 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 — Create Purchase Requisition, 11 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

Select Item or Enter Noncatalog Details

May internally include

Open Item Search → Enter Search Criteria → Select Item or Switch to Noncatalog → Enter Description/Category → Add Line → Confirm

Business Step

Review Requisition

May internally include

Open Requisition Preview → Read Calculated Header/Line Fields → Compare Against Entered Values

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 created correctly — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution. When a step fails, SyntraFlow's evidence trail is designed to help a tester classify the likely cause — for example DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically. For example: Create Requisition failed — Likely category: DATA_ERROR — Evidence: selected item is inactive — Recommended action: select an active item and rerun. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Quantity and Price	Pass	—
Save the Requisition	Pass	—
Verify Requisition Number and Status	Pass	Pass

Related Requisition Tests

Create Purchase Requisition is the entry point of the Requisitions cluster — explore the related submit, change and cancel scenarios below.

Submit Requisition Change Requisition Cancel Requisition

Turn This Standard Test into Your Oracle SCM Create Requisition Regression Suite

Start with the Syntra Standard Create Purchase Requisition test, use DataVault to provide environment-specific test data, let Jarvis generate additional item, supplier, account and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Procurement 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 on a purchase requisition?

This test validates that a purchase requisition can be created in Oracle Fusion SCM with correct requester, requisitioning Business Unit, item or category, supplier where applicable, quantity, price, deliver-to location and charge account, and that the requisition is assigned a system-generated requisition number with the correct status.

What is the difference between a catalog and a noncatalog item on a requisition?

A catalog item is selected from a configured item or punchout catalog and typically pre-populates attributes such as description, price and supplier. A noncatalog line is entered manually with a description, category and price when the item is not held in a catalog. This scenario covers both paths where supported by the customer's Oracle Fusion configuration.

Do all the listed positive and negative variations need separate test library pages?

No. Rather than maintaining a separate public page for every quantity, currency, supplier, category or account combination, SyntraFlow maintains this one core Create Purchase Requisition scenario and uses Jarvis AI to generate the underlying variations from customer-specific DataVault test data. This page remains the canonical reference for all of them.

How does security testing work for requisition creation?

Access to create a requisition for a given requisitioning Business Unit is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an authorised requester versus an unauthorized user — to confirm that access behaves as expected, without asserting a single universal Oracle security model.

Does this test create real purchase orders or real spend in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not create real procurement transactions, real purchase orders or real spend in a production environment.