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

Syntra Standard Oracle Test Library

Oracle Fusion Purchase Order Inquiry Test Cases

Validate that purchase order information — including line detail, status, receipts, invoice match state and change history — can be accurately searched, retrieved and verified in Oracle Fusion SCM Procurement.

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

Test Objective

The objective of this test is to validate that purchase order information can be accurately searched, retrieved and verified in Oracle Fusion SCM Procurement using PO number, supplier, buyer, status, date range, item and Business Unit as search criteria, and that the retrieved purchase order reflects correct line, receipt, invoice match and change history detail.

The scenario should confirm that:

the correct purchase order is retrieved for a given set of search criteria
purchase order amounts and quantities displayed match the underlying purchase order
purchase order status is displayed correctly
supplier and supplier site information on the retrieved purchase order is correct
receipt and invoice match state information is available and accurate
purchase order change history is available and traceable
Oracle correctly enforces validation and access restrictions when search criteria are invalid or when a user lacks access to a requested purchase order (DATA_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers search, retrieval and verification of existing purchase order information in Oracle Fusion SCM Procurement TEST/UAT environments. It does not cover creation, approval, change or cancellation of purchase orders, which are covered by the separate Create Purchase Order and related scenarios in the same Purchase Orders cluster.

When to Use This Test

Functional testing of purchase order search and retrieval for a new Oracle Fusion SCM Procurement implementation
Regression testing of purchase order inquiry behavior after an Oracle quarterly update
UAT sign-off for procurement and AP teams that routinely research PO status, receipts and invoice match state
Diagnosing DATA_ERROR and SECURITY_ERROR conditions surfaced during purchase order research before escalating as a possible APPLICATION_ERROR

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

Create PO

→

Approve PO

→

Send to Supplier

→

Receive Against PO

→

Match & Account

→

Change PO

→

Close PO

→

Inquiry

Purchase Order Inquiry is not a single terminal step in the Procure-to-Pay process — it is used throughout the purchase order lifecycle to verify state, for example confirming a newly created PO exists, checking receipt and invoice match status, or reviewing a change or closure. This test covers search, retrieval and verification of purchase order information and does not itself create, approve, change, cancel or close purchase orders. Exact fields available and access depend on procurement BU configuration, security profile and customer-specific Oracle Fusion configuration.

← Previous Stage

Close Purchase Order

Preconditions

Eligible purchase orders exist in the target Oracle Fusion SCM environment across a representative range of statuses.
The test user has view/inquiry access to Purchase Orders for the relevant procurement Business Unit.
Purchase orders used in the scenario have associated receipt and/or invoice match data where match-state verification is required.
Search indexes and view objects underlying purchase order inquiry are current for the test environment.

Exact field availability, search options and access depend on Oracle Fusion implementation, procurement BU configuration, security profile and customer-specific configuration. Data availability requirements vary by implementation.

Sample Test Data

PO Number	${PO_NUMBER}
Supplier	${SUPPLIER}
Supplier Site	${SUPPLIER_SITE}
Buyer	${BUYER}
Status	${STATUS}
Date Range	${DATE_RANGE}
Item	${ITEM}
Procurement BU	${PROCUREMENT_BU}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Not every search field needs to be populated for every search — a PO number alone is typically sufficient, while the other fields narrow a broader search.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~19 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 Purchase Order Inquiry Open the Purchase Orders inquiry/search page for the relevant procurement Business Unit. ${PROCUREMENT_BU}	The purchase order search page opens for the correct procurement Business Unit.
3	Enter Search Criteria Enter one or more search criteria — such as PO number, supplier, buyer, status, date range or item — to locate the target purchase order. ${PO_NUMBER} / ${SUPPLIER} / ${BUYER} / ${STATUS} / ${DATE_RANGE} / ${ITEM}	The search criteria are accepted without unexpected errors.
4	Review Search Results Review the list of purchase orders returned by the search. This single business step replaces multiple technical actions such as submitting the search and reading the results grid.	The returned purchase orders match the entered search criteria.
5	Open the Target Purchase Order Select and open the specific purchase order to be verified. ${PO_NUMBER}	The purchase order opens and displays header and line detail.
6	Review PO Lines and Totals Review the purchase order lines, quantities, prices and totals.	Line quantities, prices and totals displayed match the underlying purchase order.
7	Review Receipt and Invoice Match Status Review the receipt status and invoice match state associated with the purchase order lines.	Receipt and invoice match state information is displayed and reflects the underlying receiving and matching data.
8	Review Change HistoryBusiness assertion Review the change history recorded against the purchase order, including any prior amendments. This is the primary business assertion for the scenario — a correctly retrieved purchase order with accurate line, receipt, match and history detail is the expected pass condition, not merely a successful search.	Change history is available and consistent with changes previously made to the purchase order, and all retrieved header, line, receipt, match and history detail is confirmed correct.

Expected Results

The correct purchase order is retrieved for the entered search criteria.
Purchase order line amounts and quantities displayed match the underlying purchase order.
Purchase order status is displayed correctly.
Supplier and supplier site information is displayed correctly.
Receipt and invoice match state information is available and accurate.
Purchase order change history is available and traceable.
A search with no matching criteria returns a correctly empty result set, and an unauthorized search is correctly access-restricted.

Key Validation Checkpoints

Correct PO retrieved.
Amounts and quantities correct.
Status correct.
Supplier and site correct.
Change history available.

Core Business Scenario

Purchase Order Inquiry

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 Purchase Order Inquiry business scenario. Jarvis AI can extend this scenario by generating additional search-field, status, line, receipt, match-state 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 search field or result-set condition. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Security variations for the customer's environment — including large result-set boundary cases, since correctly handling a broad or narrow search is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Purchase Order Inquiry business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — PO Numbers, Suppliers, Buyers, Statuses and Procurement BUs.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant search-field, status, line, receipt and security variations.

Positive + Negative Test Variations

Valid search-and-retrieve scenarios and edge cases such as no matching results, invalid search criteria 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 PO number, supplier, buyer, status or date combination, SyntraFlow maintains one core Purchase Order Inquiry scenario and allows Jarvis AI to generate search-field, status, line, receipt and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Purchase Order Inquiry 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

Search by PO number
Search by supplier
Search by buyer
Search by status
Search by date
Search by item
Search by Business Unit
Review PO lines
Review receipts
Review invoice match state
Review change history

Negative Scenarios

Search with no matching results
Invalid search criteria
Unauthorized access to restricted PO
Invalid date range
Security restriction on Business Unit access

These are representative examples only. Negative-scenario behavior and available search fields 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 PO number, supplier, buyer, status and date range combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Purchase Order Inquiry scenarios relevant to the customer's actual implementation.

Standard Library Definition

PO Number               ${PO_NUMBER}
Supplier                ${SUPPLIER}
Supplier Site           ${SUPPLIER_SITE}
Buyer                   ${BUYER}
Status                  ${STATUS}
Date Range              ${DATE_RANGE}
Item                    ${ITEM}
Procurement BU          ${PROCUREMENT_BU}

DataVault

Purchase Orders
  Active POs across a representative range of statuses
Suppliers / Supplier Sites
  Active suppliers and sites per procurement BU
Buyers
  Active buyers eligible to raise or research POs
Statuses
  Open, Closed, Cancelled and On Hold POs
Procurement BUs
  Configured procurement Business Units
Receipts / Invoices
  POs with associated receipt and invoice match data

Jarvis AI Generates

Scenario 01 — Search by PO Number + Open Status
Scenario 02 — Search by Supplier + Date Range
Scenario 03 — Search by Buyer + Procurement BU
Scenario 04 — Review Lines, Receipts and Match State
Scenario 05 — No Matching Results
Scenario 06 — Unauthorized User Attempts Restricted PO Access
...

Purchase Order Inquiry test data can include sensitive procurement categories such as supplier, pricing and buyer 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 Purchase Order Inquiry scenarios Jarvis can generate from this business scenario, spanning search field, status, line, receipt and history 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	Search by PO Number	Search Field	Search performed using an exact purchase order number	Syntra Ready
VAR-002	Search by Supplier	Search Field	Search performed using supplier name across purchase orders	Syntra Ready
VAR-003	Search by Buyer	Search Field	Search performed using the assigned buyer	Syntra Ready
VAR-004	Search by Status	Search Field/Status	Search filtered to a specific purchase order status	Syntra Ready
VAR-005	Search by Date Range	Search Field	Search filtered to purchase orders within a date range	Syntra Ready
VAR-006	Search by Item	Search Field	Search performed using an item on the purchase order line	Syntra Ready
VAR-007	Search by Procurement BU	Search Field	Search scoped to a specific procurement Business Unit	Syntra Ready
VAR-008	Open Status PO	Status	Retrieved purchase order is in Open status	Syntra Ready
VAR-009	Closed Status PO	Status	Retrieved purchase order is in Closed status	Syntra Ready
VAR-010	Cancelled Status PO	Status	Retrieved purchase order is in Cancelled status	Syntra Ready
VAR-011	Review Single-Line PO	Lines	Review of line amounts and totals on a single-line purchase order	Syntra Ready
VAR-012	Review Multi-Line PO	Lines	Review of line amounts and totals across multiple purchase order lines	Syntra Ready
VAR-013	Review Full Receipt	Receipts	Review of a purchase order fully received against ordered quantity	Syntra Ready
VAR-014	Review Partial Receipt	Receipts	Review of a purchase order partially received against ordered quantity	Syntra Ready
VAR-015	Review Invoice Match State	Receipts	Review of two-way, three-way or four-way match state and any match exceptions	Syntra Ready
VAR-016	Review Change History	History	Review of recorded amendments to quantity, price, account or supplier	Syntra Ready
VAR-017	Search With No Matching Results	Search Field	Search criteria return a correctly empty result set	Syntra Ready

Automatically Expand Positive and Negative Purchase Order Inquiry Coverage

Positive Testing

Jarvis generates scenarios using PO number, supplier, buyer, status, date and item search combinations expected to successfully retrieve and verify purchase order information in Oracle Fusion.

Valid PO Number + Authorized User → Purchase Order Retrieved and Verified

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around search criteria, result sets and security.

No Matching Results → Expected Empty Result Set
Invalid Search Criteria → Expected Validation Message
Invalid Date Range → Expected Validation Message
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 Purchase Order Inquiry scenarios and group them into reusable execution packs.

SCM Procurement Purchase Order Inquiry Regression Pack

Search by PO Number
Search by Supplier
Search by Status
Search by Date Range
Review PO Lines and Totals
Review Receipts
Review Invoice Match State
Review Change History
Search With No Matching Results
Security Restriction — Unauthorized PO Access

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

Once scheduled, SyntraFlow executes the selected Purchase Order Inquiry 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 Purchase Order Inquiry Regression Pack
Schedule	Quarterly Update Regression
Tests	17 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 & Access Variations

Access to view purchase orders 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 purchase order inquiry access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Buyer	View Own POs	Allowed	PASS
Unauthorized User	Attempts View Restricted 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 Purchase Order Inquiry 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 — Purchase Order Inquiry, 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

Enter Search Criteria

May internally include

Open Search Panel → Enter PO Number/Supplier/Buyer/Status/Date Range Fields → Submit Search → Wait for Results Grid

Business Step

Review Change History

May internally include

Open PO Detail → Navigate to History Tab → Read Change Log Entries → Compare Against Expected Change Events

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 that a purchase order was correctly retrieved and verified — 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: Purchase Order Inquiry failed — Likely category: SECURITY_ERROR — Evidence: user does not have Business Unit access to the requested PO — Recommended action: review data access/security profile configuration. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter Search Criteria	Pass	—
Open the Target Purchase Order	Pass	—
Review Change History	Pass	Pass

Related Purchase Order Tests

Purchase Order Inquiry is the read and verification counterpart to the create, change, approve, cancel and close scenarios in the Purchase Orders cluster — explore the related scenarios below.

Create Purchase Order Close Purchase Order Receive Purchase Order

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

Start with the Syntra Standard Purchase Order Inquiry test, use DataVault to provide environment-specific test data, let Jarvis generate additional search-field, status, line, receipt 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 inquiry?

This test validates that a purchase order can be searched for and retrieved in Oracle Fusion SCM Procurement using criteria such as PO number, supplier, buyer, status, date range and item, and that the retrieved purchase order's line amounts, quantities, status, supplier detail, receipt and invoice match state, and change history are all displayed correctly.

What does "invoice match state" mean in the context of purchase order inquiry?

Invoice match state describes whether a purchase order line has been matched to a supplier invoice, and if so, whether that match is a two-way, three-way or four-way match and whether any match exceptions such as price, quantity or receipt variances exist. This scenario verifies that the match state displayed for a purchase order is consistent with the underlying receipt and invoice data.

How is purchase order change history tracked and tested?

Oracle Fusion retains a history of changes made to a purchase order, such as quantity, price, account or supplier changes processed through the Change Purchase Order scenario. This test confirms that the change history displayed for a purchase order in inquiry is complete and consistent with the changes that were previously made.

How does security and access testing work for purchase order inquiry?

Access to view purchase orders 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 authorized buyer versus an unauthorized user — to confirm that inquiry access behaves as expected, without asserting a single universal Oracle security model.

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

No. This is test automation executed against Oracle Fusion TEST/UAT environments only, and Purchase Order Inquiry is a read-only scenario — it does not create, change or modify real purchase orders or real spend in a production environment.