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

Syntra Standard Oracle Test Library

Oracle Fusion Create Purchase Order Test Cases

Validate that a purchase order is created correctly in Oracle Fusion SCM using a valid supplier, supplier site, procurement Business Unit, item or category, quantity, price, currency, ship-to location and charge account.

Test ID	ORCL.P2P.PROC.PO.CREATE
Application	Oracle Fusion Cloud
Product	SCM / Procurement
Module	Procurement
Process	Purchase Orders
Business Flow	Procure-to-Pay
Scenario Type	Positive / Functional
Test Usage	Functional Testing / Regression Testing / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions automatically while presenting the scenario as business-readable test steps for documentation, review and reporting. This scenario is presented as 11 business-readable test steps; SyntraFlow's automation executes approximately 30 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a purchase order can be created in Oracle Fusion SCM using a valid supplier, supplier site, procurement Business Unit, buyer, item or category, quantity, price, currency, ship-to and bill-to location and charge account, and that the resulting purchase order is created with correct header and line detail.

The scenario should confirm that:

the purchase order is created for the correct procurement Business Unit and buyer
supplier and supplier site information is captured correctly
line detail — item or category, quantity, unit of measure and unit price — is captured correctly
ship-to, bill-to and charge account information on the line is correct
the purchase order receives a system-generated PO number and correct status
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 order in Oracle Fusion SCM Procurement TEST/UAT environments, whether created manually or from an approved requisition. It does not cover approval, subsequent changes, or inquiry, which are covered by the separate Approve Purchase Order, Change Purchase Order and Purchase Order Inquiry scenarios in the same Purchase Orders cluster.

When to Use This Test

Functional testing of purchase order creation for a new Oracle Fusion SCM Procurement implementation
Regression testing of PO creation behavior after an Oracle quarterly update
UAT sign-off for buyers who routinely create purchase orders from requisitions or manually
Baseline case referenced by the Approve Purchase Order, Change Purchase Order and Purchase Order Inquiry scenarios within the same Purchase Orders cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during PO creation before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Procure-to-Pay Purchase Orders Process

Navigate to Purchase Orders

→

Create PO

→

Select Supplier/Site

→

Enter Item/Category

→

Enter Quantity/Price

→

Select Ship-to

→

Review

Create Purchase Order is the entry point of the Purchase Orders scenario family within Procure-to-Pay, following on from the Requisitions cluster where a requisition is raised and submitted. Once a purchase order is created, it is typically approved, and may subsequently be changed or inquired upon — covered by the Approve Purchase Order, Change Purchase Order and Purchase Order Inquiry scenarios in this same cluster. Exact fields available, approval routing and validation depend on procurement BU configuration, supplier and item setup and customer-specific Oracle Fusion configuration.

Next Stage →

Approve Purchase Order

Preconditions

A procurement Business Unit is configured in the target Oracle Fusion SCM environment.
The supplier and supplier site being used on the purchase order are active.
The buyer has appropriate access to create a purchase order for the procurement BU.
The item or category being ordered is active in the item/category catalog.
The charge account entered on the line is valid and open for the purchase order date.
The ship-to and bill-to locations used on the purchase order are configured and active.

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

Sample Test Data

Procurement BU	${PROCUREMENT_BU}
Requisitioning BU	${REQUISITIONING_BU}
Supplier	${SUPPLIER}
Supplier Site	${SUPPLIER_SITE}
Buyer	${BUYER}
Item	${ITEM}
Category	${CATEGORY}
Quantity	${QUANTITY}
UOM	${UOM}
Unit Price	${UNIT_PRICE}
Currency	${CURRENCY}
Ship-to	${SHIP_TO}
Bill-to	${BILL_TO}
Charge Account	${CHARGE_ACCOUNT}
Payment Terms	${PAYMENT_TERMS}

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, a PO created from a requisition may inherit supplier, item and account detail rather than requiring re-entry.

Test Steps

11 business-readable steps. SyntraFlow's automation executes ~30 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 buyer test user and navigate to the Procurement work area.	The Procurement work area opens successfully.
2	Navigate to Purchase Orders Open the Purchase Orders page to begin creating a new purchase order. ${PROCUREMENT_BU}	The purchase order creation page opens for the correct procurement Business Unit.
3	Create New Purchase Order Initiate a new purchase order for the test buyer, either manually or sourced from an approved requisition. ${BUYER} This single business step replaces multiple technical actions such as opening the create page, confirming the buyer and confirming the procurement BU.	A new, unsaved purchase order is opened for the correct buyer and procurement BU.
4	Select Supplier and Site Search for and select the supplier and supplier site for the purchase order. ${SUPPLIER} / ${SUPPLIER_SITE}	The supplier and supplier site are accepted and reflected on the purchase order header.
5	Enter Item or Category Search for and select a catalog item, or enter category and line description details where a catalog item is not used. ${ITEM} / ${CATEGORY}	The item or category line detail is accepted and added to the purchase order.
6	Enter Quantity and Unit Price Enter the purchase order line quantity, unit of measure, unit price and currency. ${QUANTITY} / ${UOM} / ${UNIT_PRICE} / ${CURRENCY}	Quantity, UOM, unit price and currency are accepted without unexpected validation errors.
7	Select Ship-to and Bill-to Select the ship-to and bill-to locations for the purchase order line. ${SHIP_TO} / ${BILL_TO}	The ship-to and bill-to locations are accepted and reflected on the line.
8	Select Charge Account Select or confirm the charge account and payment terms that the purchase order line will be costed to. ${CHARGE_ACCOUNT} / ${PAYMENT_TERMS}	The charge account and payment terms are accepted and reflected on the line.
9	Review Purchase Order Totals Review the purchase order header, line detail and calculated totals as computed by Oracle Fusion before saving. Reviewing the purchase order before saving lets the tester catch an incorrect field entry before the PO is created.	The reviewed purchase order reflects the entered supplier, site, item/category, quantity, price and totals.
10	Save the Purchase Order Save the purchase order for creation in the test environment.	Oracle Fusion successfully processes the purchase order without unexpected errors.
11	Verify PO Number and StatusBusiness assertion Reopen or refresh the purchase order and confirm the generated PO number, status and line detail. This is the primary business assertion for the scenario — a correctly created purchase order with accurate header and line detail is the expected pass condition, not merely a successful save.	A PO number is generated, the purchase order status is correct, and supplier, site, quantity, price and totals match the entered data.

Expected Results

The purchase order is created for the correct procurement Business Unit and buyer.
A system-generated PO number is assigned.
Supplier and supplier site are correct.
Line data — item/category, quantity, UOM and unit price — is correct.
Ship-to, bill-to and charge account on the line are correct.
The purchase order status correctly reflects a newly created purchase order.
The purchase order is visible and traceable for the test buyer.

Key Validation Checkpoints

PO created.
PO number generated.
Supplier/site correct.
Lines correct.
Totals correct.
Status correct.

Core Business Scenario

Create Purchase Order

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core Create Purchase Order business scenario. Jarvis AI can extend this scenario by generating additional supplier, item/category, 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 supplier, item, quantity or currency combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Approval variations for the customer's environment — including large-quantity, high-value boundary cases and purchase orders that exceed ${APPROVAL_THRESHOLD} and are expected to route for approval, 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 Order business process and automation logic.

Customer DataVault

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

Jarvis AI

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

Positive + Negative Test Variations

Valid purchase order scenarios and edge cases such as inactive suppliers, invalid accounts 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 supplier, item, category, quantity, currency or account combination, SyntraFlow maintains one core Create Purchase Order scenario and allows Jarvis AI to generate supplier, item, quantity, currency and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Create Purchase Order business scenario can produce many test variations without creating separate public library pages. Below is a real slice of SyntraFlow's Build Scripts library, filtered to SCM Procurement Purchase Orders.

Positive Scenarios

Create a standard purchase order
Create a single-line purchase order
Create a multi-line purchase order
Create a purchase order from an approved requisition
Create a purchase order manually, without a source requisition
Create purchase orders with different suppliers
Create purchase orders in different currencies
Create purchase orders with different items or categories
Create purchase orders with different quantities and prices
Create purchase orders with different payment terms

Negative Scenarios

Attempt to order against an inactive supplier
Enter an invalid supplier site
Attempt to order an invalid item
Enter an invalid charge account
Attempt to save without a ship-to location
Enter a zero or negative quantity
Enter an invalid currency
Attempt to save with missing mandatory data
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 supplier, item, category, 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 Order scenarios relevant to the customer's actual implementation.

Standard Library Definition

Procurement BU         ${PROCUREMENT_BU}
Requisitioning BU       ${REQUISITIONING_BU}
Supplier                ${SUPPLIER}
Supplier Site           ${SUPPLIER_SITE}
Buyer                   ${BUYER}
Item                    ${ITEM}
Category                ${CATEGORY}
Quantity                ${QUANTITY}
UOM                     ${UOM}
Unit Price              ${UNIT_PRICE}
Currency                ${CURRENCY}
Ship-to                 ${SHIP_TO}
Bill-to                 ${BILL_TO}
Charge Account          ${CHARGE_ACCOUNT}
Payment Terms           ${PAYMENT_TERMS}

DataVault

Suppliers / Supplier Sites
  Active suppliers and sites per procurement BU
Buyers
  Buyers eligible to create a purchase order
Items / Categories
  Active catalog and noncatalog item/category values
Accounts
  Valid, open charge accounts
Locations
  Configured ship-to and bill-to locations
Payment Terms
  Configured payment terms codes

Jarvis AI Generates

Scenario 01 — Supplier A + Catalog Item + Single Line
Scenario 02 — Supplier A + Noncatalog Item + Multi-Line
Scenario 03 — Supplier B + Different Currency and Terms
Scenario 04 — PO Created from Approved Requisition
Scenario 05 — Inactive Supplier
Scenario 06 — Unauthorized User Attempts Create Purchase Order
...

Create Purchase Order 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 Order scenarios Jarvis can generate from this business scenario, spanning supplier, item/category, currency and terms 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	Standard Purchase Order	Positive	Purchase order created with valid supplier, item and pricing data	Syntra Ready
VAR-002	Single-Line Purchase Order	Positive	PO created with a single purchase order line	Syntra Ready
VAR-003	Multi-Line Purchase Order	Positive	PO created with multiple purchase order lines	Syntra Ready
VAR-004	PO Created from Requisition	Positive	PO generated from an approved purchase requisition	Syntra Ready
VAR-005	Manual Purchase Order	Positive	PO created manually without a source requisition	Syntra Ready
VAR-006	Different Suppliers	Positive/Supplier	PO created against an alternate active supplier and site	Syntra Ready
VAR-007	Different Currencies	Positive/Currency	PO created in a currency other than the default	Syntra Ready
VAR-008	Different Items/Categories	Positive/Item/Category	PO line created using an alternate active item or category	Syntra Ready
VAR-009	Different Quantities/Prices	Positive	PO created with a range of valid line quantities and unit prices	Syntra Ready
VAR-010	Different Payment Terms	Positive/Terms	PO created with an alternate configured payment terms code	Syntra Ready
VAR-011	Large Quantity Boundary PO	Positive	PO line created at a boundary quantity value	Syntra Ready
VAR-012	High-Value PO Approval Threshold	Positive/Terms	PO total exceeds ${APPROVAL_THRESHOLD} and is expected to route for approval	Syntra Ready
VAR-013	Inactive Supplier	Negative/Supplier	Selected supplier is inactive as of the PO date	Syntra Ready
VAR-014	Invalid Supplier Site	Negative/Supplier	Selected supplier site is invalid for the chosen supplier	Syntra Ready
VAR-015	Invalid Item	Negative/Item/Category	Selected item is invalid or inactive	Syntra Ready
VAR-016	Invalid Charge Account	Negative	Charge account entered is invalid or closed	Syntra Ready
VAR-017	Missing Ship-to	Negative	Purchase order saved without a ship-to location	Syntra Ready
VAR-018	Invalid Quantity	Negative	Line quantity entered as zero or a negative value	Syntra Ready
VAR-019	Invalid Currency	Negative/Currency	Currency entered is not configured for the procurement BU	Syntra Ready
VAR-020	Missing Mandatory Data	Negative	A mandatory header or line field is left blank	Syntra Ready
VAR-021	Security Restriction — Unauthorized Create PO	Negative	Requesting user lacks access to create a purchase order for the procurement BU	Syntra Ready

Automatically Expand Positive and Negative Purchase Order Coverage

Positive Testing

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

Valid Supplier + Active Item + Valid Account + Valid Ship-to Location → Purchase Order Created

Negative Testing

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

Inactive Supplier → Expected Supplier Validation
Invalid Item → Expected Item Validation
Invalid Charge Account → Expected Account Validation
Missing Ship-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 PO	Purchase order created	PASS
Inactive supplier	Supplier validation occurs	PASS
Invalid account	Account validation occurs	PASS
Security restriction	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Create Purchase Order scenarios and group them into reusable execution packs.

SCM Procurement Create Purchase Order Regression Pack

Standard Purchase Order
Single-Line Purchase Order
Multi-Line Purchase Order
PO Created from Requisition
Different Suppliers
Different Currencies
Different Payment Terms
High-Value PO Approval Threshold
Invalid Charge Account
Security Restriction — Unauthorized Create PO

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

Once scheduled, SyntraFlow executes the selected Create Purchase Order scenarios unattended and records the outcome of each test and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	SCM Procurement Create Purchase Order Regression Pack
Schedule	Quarterly Update Regression
Tests	21 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 order for a given procurement Business Unit is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that PO-creation access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Buyer	Create Purchase Order	Allowed	PASS
Unauthorized User	Attempts Create PO	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 Order scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Approval coverage — including purchase orders that exceed ${APPROVAL_THRESHOLD} and are expected to route for approval — 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 Order, 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 Supplier and Site

May internally include

Open Supplier Search → Enter Search Criteria → Select Supplier → Select Supplier Site → Confirm Site Attributes → Add to Header

Business Step

Review Purchase Order Totals

May internally include

Open PO Preview → Read Calculated Header/Line Totals → 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 purchase order 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 Purchase Order failed — Likely category: DATA_ERROR — Evidence: selected supplier is inactive — Recommended action: select an active supplier and rerun. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Quantity and Unit Price	Pass	—
Save the Purchase Order	Pass	—
Verify PO Number and Status	Pass	Pass

Related Purchase Order Tests

Create Purchase Order is the entry point of the Purchase Orders cluster — explore the related approve, change and inquiry scenarios below.

Approve Purchase Order Change Purchase Order Purchase Order Inquiry

Turn This Standard Test into Your Oracle SCM Create Purchase Order Regression Suite

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

Automate with SyntraFlow Explore Procurement Purchase Orders Test Library

Use This Oracle Fusion Test Case

Download Test Case

Excel, CSV or JSON export.

Coming soon

Automate with SyntraFlow

Run this script against your own tenant today.

Related Oracle Testing Resources

Oracle ERP Testing Tool Test Library SCM Test Library Procurement Test Library Purchase Orders Test Library Syntra DataVault

Frequently Asked Questions

What does this test validate on a purchase order?

This test validates that a purchase order can be created in Oracle Fusion SCM with correct supplier, supplier site, procurement Business Unit, buyer, item or category, quantity, price, currency, ship-to and bill-to location and charge account, and that the purchase order is assigned a system-generated PO number with the correct status.

What is the difference between a PO created from a requisition and a manual PO?

A purchase order created from a requisition sources supplier, item and account detail from an approved purchase requisition, typically through requisition-to-PO automation. A manual purchase order is created directly by a buyer without a source requisition, with supplier, item and account data entered at the PO. 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 Order 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 purchase order creation?

Access to create a purchase order for a given procurement 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 buyer 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.