Oracle ERP Testing Tool > Test Library > SCM > Order Management > Inquiry

Syntra Standard Oracle Test Library

Oracle Fusion Order Inquiry Test Cases

Validate that order inquiries in Oracle Fusion SCM Order Management return accurate order status, line detail and fulfillment progress across the full order lifecycle — from draft through submission, scheduling, shipment and return — without creating or modifying any order data.

Test ID	ORCL.O2C.OM.INQ.ORDER
Application	Oracle Fusion Cloud
Product	SCM / Order Management
Module	Order Management
Process	Inquiry
Business Flow	Order-to-Cash
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 7 business-readable test steps; SyntraFlow's automation executes approximately 16 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that order inquiries in Oracle Fusion SCM Order Management return accurate order and line status, fulfillment progress and lifecycle detail when filtered by order number, customer, item, status and date range, across the full order lifecycle from draft through submission, scheduling, reservation, picking, shipment and return. This is a read-only inquiry — the test verifies displayed data only and does not create, modify or move any order or fulfillment data.

The scenario should confirm that:

the displayed order and line status matches the expected value for the selected lifecycle stage (draft, submitted, scheduled, reserved, picked, shipped or returned)
fulfillment progress details such as scheduling, shipment and return activity are accurately reflected for the order
results are correctly scoped to the selected order number, customer, item, status and date range filters
results remain consistent across repeated inquiries when no intervening transaction has occurred
an over-restrictive filter combination correctly returns an empty result set rather than an error
Oracle correctly enforces validation and access restrictions when search criteria are invalid or when a user lacks access to a requested organization (DATA_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers read-only inquiry into sales order status, line detail and fulfillment progress in Oracle Fusion SCM Order Management TEST/UAT environments. No order data is created, modified or moved by this test — it only reads and verifies displayed order and line status, scheduling, shipment and return information. Transactions that create or change order data, such as creating, submitting, scheduling, reserving, shipping or returning orders, are covered by the separate scenarios in the Sales Orders, Order Changes, Holds, Fulfillment and Returns clusters.

When to Use This Test

Functional testing of order inquiry for a new Oracle Fusion SCM Order Management implementation
Regression testing of order inquiry behavior after an Oracle quarterly update
UAT sign-off for customer service, order management and fulfillment teams that routinely check order and line status
Diagnosing DATA_ERROR and SECURITY_ERROR conditions surfaced during order status research before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Order-to-Cash Order Management Process

Sales Orders

→

Order Changes

→

Holds

→

Fulfillment

→

Returns

→

Inquiry

Inquiry is a read-only process rather than a transactional stage in the Order Management lifecycle — it is used throughout to verify order and line status, fulfillment progress and return activity resulting from the Sales Orders, Order Changes, Holds, Fulfillment and Returns processes. This test does not itself create, modify or move any order data; it validates that the status and detail displayed by the inquiry are accurate. Exact fields available and access depend on order type, customer configuration, security profile and customer-specific Oracle Fusion configuration.

← Previous Stage

Create Return Order

Preconditions

Sales orders exist across a range of lifecycle statuses — draft, submitted, scheduled, reserved, picked, shipped and returned — in the target Oracle Fusion SCM environment.
At least one order has an associated return, so that return status and reference detail can be verified through the inquiry.
The test user has view/inquiry access to sales orders for the relevant business unit or organization.
Orders span multiple customers and order dates, so that customer and date-range filtering can be verified.

Exact fields available, filter options and access depend on Oracle Fusion implementation, order type, customer configuration, security profile and customer-specific configuration. Data availability requirements vary by implementation.

Sample Test Data

Order Number	${ORDER_NUMBER}
Customer	${CUSTOMER}
Item	${ITEM}
Order Status	${ORDER_STATUS}
Line Status	${LINE_STATUS}
As-Of Date	${AS_OF_DATE}
Date Range Start	${DATE_RANGE_START}
Date Range End	${DATE_RANGE_END}
Ship-To Location	${SHIP_TO}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Not every field needs to be populated for every inquiry — order number alone is often sufficient, while customer, item, status and date range narrow a broader inquiry.

Test Steps

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

#	User Action	Expected Result
1	Sign In Sign in to Oracle Fusion using an authorised order management test user.	The user is signed in successfully with access to Order Management.
2	Navigate to Order Management Navigate to the Order Management work area.	The Order Management work area opens successfully.
3	Open the Order Inquiry Open the order inquiry page used to search for and review sales orders. ${ORDER_NUMBER}	The order inquiry page opens successfully.
4	Apply Customer/Order/Date Filters Enter filters such as order number, customer, item, order status, line status or date range to scope the inquiry. ${ORDER_NUMBER} / ${CUSTOMER} / ${ITEM} / ${ORDER_STATUS} / ${LINE_STATUS} / ${AS_OF_DATE} This single business step replaces multiple technical actions such as populating individual filter fields and submitting the search.	The filters are accepted without unexpected errors and the inquiry can be executed.
5	Review Displayed Order and Line Status Review the order header status, line status and fulfillment progress details (scheduling, shipment, return) displayed for the selected order(s).	Order and line status, and fulfillment progress detail, are displayed for the selected scope.
6	Cross-Check Against Expected Lifecycle Stage Cross-check the displayed order and line status against the expected lifecycle stage for the order — draft, submitted, scheduled, reserved, picked, shipped or returned.	Displayed status matches the expected lifecycle stage.
7	Verify Results Scoped CorrectlyBusiness assertion Confirm that the returned results are correctly scoped to the selected filters, and remain consistent on a repeated inquiry. This is the primary business assertion for the scenario — accurate, correctly scoped order and line status and fulfillment progress are the expected pass condition, not merely a successful search.	Results are correctly scoped to the selected filters and remain consistent across repeated inquiries with no drift when no intervening transaction has occurred.

Expected Results

The displayed order and line status matches the expected value for the selected lifecycle stage.
Fulfillment progress details (scheduling, shipment, return) are accurately reflected for the order.
Results are correctly scoped to the selected order number, customer, item, status and date range filters.
Results remain consistent across repeated inquiries when no intervening transaction has occurred.
An over-restrictive filter combination correctly returns an empty result set rather than an error.
An unauthorized cross-organization inquiry is correctly access-restricted.
No order data is created, modified or moved by this inquiry.

Key Validation Checkpoints

Displayed order/line status matches expected lifecycle stage.
Fulfillment progress details (scheduling, shipment, return) accurately reflected.
Results correctly scoped to the selected filters.
Results consistent across repeated inquiries with no intervening transaction.

Core Business Scenario

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 Order Inquiry business scenario. Jarvis AI can extend this scenario by generating additional lifecycle-stage, customer, date-range 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 order status or filter combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Lifecycle Stage and Scope variations for the customer's environment — including orders at every stage from draft through return, since correctly surfacing status across the full order lifecycle is central to what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Order Inquiry business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Orders, Customers, Items, Statuses and Date Ranges.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant lifecycle-stage, customer, scope and security variations.

Positive + Negative Test Variations

Valid order inquiries across lifecycle stages and edge cases such as invalid filters, over-restrictive 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 order status, filter or lifecycle stage combination, SyntraFlow maintains one core Order Inquiry scenario and allows Jarvis AI to generate lifecycle-stage, scope and security-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Positive Scenarios

Inquiry on a draft order
Inquiry on a submitted order
Inquiry on a scheduled/reserved order
Inquiry on a shipped order
Inquiry on an order with an associated return
Inquiry filtered by customer/date range

Negative Scenarios

Invalid order number filter
Invalid customer filter
Invalid date range
Over-restrictive filter combination correctly returning no results
Unauthorized cross-organization inquiry attempted
Invalid status filter

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 order, customer, item and status combination in a real Oracle Fusion SCM Order Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Order Inquiry scenarios relevant to the customer's actual implementation.

Standard Library Definition

Order Number         ${ORDER_NUMBER}
Customer             ${CUSTOMER}
Item                 ${ITEM}
Order Status         ${ORDER_STATUS}
Line Status          ${LINE_STATUS}
As-Of Date           ${AS_OF_DATE}
Date Range Start     ${DATE_RANGE_START}
Date Range End       ${DATE_RANGE_END}
Ship-To Location     ${SHIP_TO}

DataVault

Orders
  Sales orders spanning draft, submitted, scheduled, reserved, picked, shipped and returned status
Customers
  Active customers with order history across a representative range of scopes
Items
  Items referenced on order lines across multiple statuses
Statuses
  Header and line status values reflecting each lifecycle stage
Date Ranges
  Order dates spanning a representative testing window

Jarvis AI Generates

Scenario 01 — Draft Order Inquiry
Scenario 02 — Submitted Order Inquiry
Scenario 03 — Scheduled/Reserved Order Inquiry
Scenario 04 — Shipped Order Inquiry
Scenario 05 — Order With Associated Return
Scenario 06 — Customer/Date Range Filtered Inquiry
Scenario 07 — Invalid Order Number Filter
Scenario 08 — Unauthorized Cross-Organization Inquiry
...

Order inquiry test data can include sensitive customer and commercial categories such as customer, item and order-value information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific order 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 Order Inquiry scenarios Jarvis can generate from this business scenario, spanning lifecycle stage, customer, date-range 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	Draft Order Inquiry	Positive/Lifecycle Stage	Inquiry on an order in Draft status	Syntra Ready
VAR-002	Submitted Order Inquiry	Positive/Lifecycle Stage	Inquiry on an order in Submitted status	Syntra Ready
VAR-003	Scheduled/Reserved Order Inquiry	Positive/Lifecycle Stage	Inquiry on an order that is Scheduled and Reserved	Syntra Ready
VAR-004	Picked Order Inquiry	Positive/Lifecycle Stage	Inquiry on an order with lines in Picked status	Syntra Ready
VAR-005	Shipped Order Inquiry	Positive/Lifecycle Stage	Inquiry on an order that has Shipped	Syntra Ready
VAR-006	Order With Associated Return	Positive/Lifecycle Stage	Inquiry on an order with an associated return correctly reflects return status	Syntra Ready
VAR-007	Customer/Date Range Filtered Inquiry	Positive/Scope	Inquiry filtered by customer and order date range	Syntra Ready
VAR-008	Invalid Order Number Filter	Negative	Inquiry submitted with an invalid or non-existent order number	Syntra Ready
VAR-009	Invalid Customer Filter	Negative	Inquiry submitted with an invalid or non-existent customer	Syntra Ready
VAR-010	Invalid Date Range	Negative	Inquiry submitted with an invalid or illogical date range	Syntra Ready
VAR-011	Over-Restrictive Filter Combination	Negative	Filter combination correctly returns an empty result set, not an error	Syntra Ready
VAR-012	Unauthorized Cross-Organization Inquiry	Negative	User without organization access attempts a cross-organization inquiry	Syntra Ready
VAR-013	Invalid Status Filter	Negative	Inquiry submitted with an invalid order or line status value	Syntra Ready

Automatically Expand Positive and Negative Order Inquiry Coverage

Positive Testing

Jarvis generates scenarios using order, customer, item, status and date-range combinations expected to successfully return accurate order and line status in Oracle Fusion, across the full order lifecycle from draft through return.

Valid Order + Customer + Shipped Status → Order and Line Status Correctly Displayed

Negative Testing

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

Invalid Order Number Filter → Expected Validation Message
Invalid Customer Filter → Expected Validation Message
Invalid Date Range → Expected Validation Message
Over-Restrictive Filter Combination → Expected Empty Result Set
Unauthorized Cross-Organization Inquiry → Expected Access Restriction

A negative scenario passes when Oracle correctly enforces the expected business rule or validation.

Scenario	Oracle Outcome	Test Result
Valid return order	Return created	PASS
Quantity exceeds shipped	Validation occurs	PASS
Item not return-eligible	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 Order Inquiry scenarios and group them into reusable execution packs.

SCM Order Management Inquiry Regression Pack

Draft Order Inquiry
Submitted Order Inquiry
Scheduled/Reserved Order Inquiry
Picked Order Inquiry
Shipped Order Inquiry
Order With Associated Return
Customer/Date Range Filtered Inquiry
Invalid Order Number Filter
Invalid Customer Filter
Over-Restrictive Filter Combination
Unauthorized Cross-Organization Inquiry
Invalid Status Filter

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

Once scheduled, SyntraFlow executes the selected 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 Order Management Inquiry Regression Pack
Schedule	Quarterly Update Regression
Tests	13 scenarios
Execution	Batch Mode
Start	10:00 PM
Environment	Oracle Fusion TEST
Status	Scheduled

Illustrative example — not a live schedule.

Review Results Across the Entire Test Pack

Users can drill from the regression pack into a scenario, its business steps, the underlying automation actions, and the evidence captured for each.

Illustrative example data — not actual production metrics.

Total Scenarios

Passed

Failed

Exceptions

Positive Tests

Negative Tests

Business Assertions

Regression Pack → Scenario → Business Step → Automation Action → Evidence

Security & Access Variations

Access to view orders for a given business unit or organization is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that order inquiry access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Customer Service Representative	View Order Inquiry	Allowed	PASS
Unauthorized User	Attempts Cross-Organization Inquiry	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 Order Inquiry scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Lifecycle Stage and Scope 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 — Order Inquiry, 7 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

Apply Customer/Order/Date Filters

May internally include

Open Filter Panel → Enter Order Number/Customer/Item/Status/Date Fields → Submit Inquiry → Wait for Results Grid

Business Step

Review Displayed Order and Line Status

May internally include

Open Order Detail → Read Order Header Status → Read Line Status → Read Scheduling/Shipment/Return Detail → Compare Against Expected Value

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 displayed order and line status are accurate — 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: Order Inquiry failed — Likely category: DATA_ERROR — Evidence: displayed line status does not match the expected fulfillment stage — Recommended action: verify the underlying order data and re-run the inquiry with supporting evidence before escalating. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Open the Order Inquiry	Pass	—
Apply Customer/Order/Date Filters	Pass	—
Verify Results Scoped Correctly	Pass	Pass

Related Order Management Tests

Order Inquiry is the read and verification counterpart to the transactional scenarios that create, fulfill and return orders — explore related Order Management scenarios below.

Create Sales Order Ship Confirm Create Return Order

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

Start with the Syntra Standard Order Inquiry test, use DataVault to provide environment-specific test data, let Jarvis generate additional lifecycle-stage, scope and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore Order Management Inquiry 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 Order Management Test Library Inquiry Test Library Syntra DataVault

Frequently Asked Questions

What lifecycle stages are visible through the order inquiry?

The order inquiry can display status for orders at any stage of the Order-to-Cash lifecycle covered by this module, including draft, submitted, scheduled, reserved, picked, shipped and returned. This test scenario includes variations that check inquiry results at each of these stages.

Does this test perform any transaction against an order?

No. Order Inquiry is a read-only scenario — it does not create, submit, schedule, ship, cancel or return any order. It only reads and verifies the order and line status, and fulfillment progress detail, displayed by Oracle Fusion for the selected order or filter criteria.

How do filters scope the inquiry results?

Filters such as order number, customer, item, order status, line status and date range narrow the inquiry to a specific order or set of orders. This scenario verifies that results are correctly scoped to the selected filters, and that an over-restrictive filter combination correctly returns an empty result set rather than an error.

How does security testing work for order inquiry?

Access to view orders for a given business unit or organization is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an authorized customer service representative versus an unauthorized user attempting a cross-organization inquiry — to confirm that inquiry access behaves as expected, without asserting a single universal Oracle security model.

Why might the same order show different status information across fields?

An order's header status and line status can differ — for example, an order can be Submitted at header level while individual lines are Scheduled, Shipped or Returned. This test verifies that both order-level and line-level status, along with fulfillment progress detail, are displayed accurately and consistently.