Oracle Fusion Change Order Quantity Test Cases
Validate changing the ordered quantity on an existing Oracle Fusion sales order line — covering increases and decreases, and the difference in allowed behavior before fulfillment starts versus after a reservation or shipment is already in progress.
| Test ID | ORCL.O2C.OM.CHG.QUANTITY |
| Application | Oracle Fusion Cloud |
| Product | SCM / Order Management |
| Module | Order Management |
| Process | Order Changes |
| 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 8 business-readable test steps; SyntraFlow's automation executes approximately 21 underlying Oracle Fusion UI actions to complete it.
Test Objective
The objective of this test is to validate changing the ordered quantity on an existing sales order line, covering both increases and decreases, and confirming that behavior differs correctly depending on whether fulfillment processing — reservation or shipment — has already started for that line.
The scenario should confirm that:
- an authorized user can open an existing order line and enter a new quantity
- quantity increases and decreases are each accepted where they are valid for the line's current status
- changes before fulfillment has started are processed differently from changes attempted after a reservation or shipment is already in progress
- line and order-level pricing recalculates correctly where the quantity change affects price
- downstream reservation or scheduling records are adjusted to reflect the revised quantity where applicable
- the change is recorded in the order's change history or audit trail rather than silently overwriting the prior value
This scenario covers changing the ordered quantity on an existing, already-submitted sales order line within Oracle Fusion Order Management TEST/UAT environments. It does not cover initial order creation, which is covered by the separate order-entry scenarios, or full line/order cancellation, which is covered by the separate Cancel Sales Order scenario in this same Order Changes cluster.
When to Use This Test
- Functional testing of quantity increase and decrease behavior for a new Oracle Fusion Order Management implementation
- Regression testing of quantity-change and pricing-recalculation behavior after an Oracle quarterly update
- UAT sign-off for order entry teams who routinely amend quantities before or after fulfillment has started
- Baseline case referenced by the requested-date, cancellation and hold scenarios within the same Order Changes cluster
Where This Test Fits in the Order Change Process
Change Order Quantity applies to a sales order line that already exists, adjusting the ordered quantity while the order itself remains open. It sits alongside other Order Changes scenarios such as Change Requested Date, Cancel Sales Order and Apply Order Hold. Exact allowed changes, timing restrictions and downstream impact depend on line status, fulfillment progress, customer workflow configuration and security setup.
Preconditions
- An existing, submitted sales order line is available for the test.
- For scenarios covering changes after fulfillment has started, the line has an active reservation or a shipment already in progress.
- The test user performing the change has the appropriate order-change privileges.
- The target new quantity values are valid and configured for the test tenant.
Exact eligible line statuses, quantity-change restrictions and validation messages may vary by Oracle Fusion implementation, order-management workflow configuration and security setup.
Sample Test Data
| Order Number | ${ORDER_NUMBER} |
| Order Line Number | ${LINE_NUMBER} |
| Item | ${ITEM} |
| Original Quantity | ${ORIGINAL_QUANTITY} |
| New Quantity | ${NEW_QUANTITY} |
| Unit of Measure | ${UOM} |
| Line Status | ${LINE_STATUS} |
| Business Unit | ${BUSINESS_UNIT} |
| Customer | ${CUSTOMER} |
Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Line Status reflects whether fulfillment processing — reservation or shipment — has already started, which determines which quantity changes are available for a given line.
Test Steps
8 business-readable steps. SyntraFlow's automation executes ~21 underlying UI actions to complete these steps — see How SyntraFlow Automates This Test.
| # | User Action | Expected Result |
|---|---|---|
| 1 | Sign In to Oracle Fusion Sign in to Oracle Fusion using an authorized Order Management test user. | Oracle Fusion signs the user in successfully and the home page loads. |
| 2 | Navigate to Order Management Navigate to the Order Management work area. | The Order Management work area loads and order search is available. |
| 3 | Locate the Sales Order Search for and open the sales order that contains the line to be changed. ${ORDER_NUMBER} This single business step replaces multiple technical actions such as opening order search, entering the order number, and selecting the result. | The correct sales order is located and its current line details are displayed. |
| 4 | Select the Order Line to Change Select the specific order line whose quantity will be changed. ${ITEM} | The selected line's current quantity, unit of measure and status are displayed. |
| 5 | Enter the New Quantity Update the ordered quantity on the selected line to the new value for this variation. ${NEW_QUANTITY} / ${UOM} | The new quantity is accepted without unexpected validation errors. |
| 6 | Review Recalculated Pricing and Reservation Impact Review the recalculated line pricing and any impact on the existing reservation or scheduling before submitting the change. Reviewing the impact before submitting lets the tester catch an unintended pricing or reservation consequence before it is committed. | The pricing and reservation impact shown are consistent with the intended quantity change for this variation. |
| 7 | Submit the Quantity Change Submit and save the quantity change in the test environment. | Oracle Fusion saves the change without unexpected errors. |
| 8 | Verify Line and Order Reflect the Updated QuantityBusiness assertion Reopen or refresh the order and confirm the line and order-level totals reflect the change. This is a primary business assertion for the scenario — a correctly updated line, order total and reservation record is the expected pass condition, not merely a successful save. | The order line, order totals, and downstream reservation or scheduling records accurately reflect the updated quantity. |
Expected Results
- The new quantity is accepted on the line without unexpected errors, for both increases and decreases where the change is valid.
- Downstream reservation and scheduling records are adjusted to reflect the revised quantity where applicable.
- Line and order-level pricing recalculates correctly when the quantity change affects price.
- Quantity decreases below an already-shipped quantity are correctly rejected rather than silently applied.
- A record of the quantity change is retained in the order's change history or audit trail.
- Unauthorized change attempts are correctly prevented.
Key Validation Checkpoints
- Quantity updated correctly on the line.
- Downstream reservation/scheduling correctly adjusted.
- Pricing recalculated where applicable.
- Change history/audit trail recorded.
Go Beyond the Standard Test with Jarvis AI
The Syntra Standard Test Library defines the core change-order-quantity business scenario. Jarvis AI can extend this scenario by generating additional timing, direction 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 combination of increase or decrease and every stage of fulfillment. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Timing and Direction variations for the customer's environment.
From Standard Test to Executed Regression Pack
Rather than maintaining a separate test page for every combination of increase, decrease and fulfillment timing, SyntraFlow maintains one core change-order-quantity scenario and allows Jarvis AI to generate timing-, direction- and security-specific variations using the customer's available test data.
AI-Generated Test Variations
The same Change Order Quantity 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 Order Changes.
- Increase quantity before fulfillment
- Decrease quantity before fulfillment
- Increase quantity after reservation (where allowed)
- Decrease quantity after partial shipment (where allowed)
- Quantity change with corresponding price recalculation
- Quantity change on one line among several
- Decrease below already-shipped quantity
- Increase exceeding available supply where blocked
- Invalid quantity (zero/negative)
- Change attempted on a closed/cancelled order
- Unauthorized user attempts change
- Change attempted after order fully invoiced
- Change conflicting with an active hold
These are representative examples only. Negative-scenario behavior and available quantity changes 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, item, customer and fulfillment status combination in a real Oracle Fusion environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct change-order-quantity scenarios relevant to the customer's actual implementation.
Standard Library Definition
Order Number ${ORDER_NUMBER}
Order Line Number ${LINE_NUMBER}
Item ${ITEM}
Original Quantity ${ORIGINAL_QUANTITY}
New Quantity ${NEW_QUANTITY}
Unit of Measure ${UOM}
Line Status ${LINE_STATUS}
Business Unit ${BUSINESS_UNIT}
Customer ${CUSTOMER}
DataVault
Sales Orders Open lines at varying fulfillment stages Items Active items with valid quantity ranges and units of measure Customers Active customers eligible for order changes Reservations Lines with and without an active reservation Pricing Quantity-tiered pricing and discount rules per item
Jarvis AI Generates
Scenario 01 — SO-7001 + Increase Quantity Before Fulfillment Scenario 02 — SO-7001 + Decrease Quantity Before Fulfillment Scenario 03 — SO-7002 + Increase Quantity After Reservation Scenario 04 — SO-7002 + Decrease Below Shipped Quantity Scenario 05 — Invalid Quantity Entered Scenario 06 — Unauthorized User Attempts Change ...
Customer-specific test data and AI-generated variations are not published to the Syntra Standard Test Library. Where DataVault is connected, customer-specific dimensions such as order, item, customer and reservation remain within the customer's controlled SyntraFlow environment and access model.
Example Test Variations
Representative examples of change-order-quantity scenarios Jarvis can generate from this business scenario, spanning positive, negative, timing and direction 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 | Increase Quantity Before Fulfillment | Positive/Direction | Quantity increased on a line before fulfillment has started | Syntra Ready |
| VAR-002 | Decrease Quantity Before Fulfillment | Positive/Direction | Quantity decreased on a line before fulfillment has started | Syntra Ready |
| VAR-003 | Increase Quantity After Reservation (Where Allowed) | Positive/Timing | Quantity increased after a reservation is already in place, where allowed by configuration | Syntra Ready |
| VAR-004 | Decrease Quantity After Partial Shipment (Where Allowed) | Positive/Timing | Quantity decreased after partial shipment, where allowed and within shipped-quantity limits | Syntra Ready |
| VAR-005 | Quantity Change With Price Recalculation | Positive/Direction | Quantity change triggers automatic price recalculation on the line | Syntra Ready |
| VAR-006 | Quantity Change on One Line Among Several | Positive/Timing | Quantity changed on a single line while other lines on the order remain unaffected | Syntra Ready |
| VAR-007 | Decrease Below Already-Shipped Quantity | Negative/Direction | Attempted decrease below the quantity already shipped | Syntra Ready |
| VAR-008 | Increase Exceeding Available Supply Where Blocked | Negative/Direction | Attempted increase beyond available supply where the configuration blocks it | Syntra Ready |
| VAR-009 | Invalid Quantity (Zero/Negative) | Negative/Direction | Zero or negative quantity entered on the line | Syntra Ready |
| VAR-010 | Change Attempted on Closed/Cancelled Order | Negative/Timing | Quantity change attempted on a closed or cancelled order | Syntra Ready |
| VAR-011 | Unauthorized Change Attempt | Negative/Timing | A user without change privileges attempts the quantity change | Syntra Ready |
| VAR-012 | Change Attempted After Order Fully Invoiced | Negative/Timing | Quantity change attempted after the order has been fully invoiced | Syntra Ready |
| VAR-013 | Change Conflicting With Active Hold | Negative/Timing | Quantity change attempted while an active hold exists on the order | Syntra Ready |
No variations match this filter.
Automatically Expand Positive and Negative Change Order Quantity Coverage
Positive Testing
Jarvis generates scenarios using quantity values and line status expected to successfully update an order line while correctly adjusting pricing and reservation records.
Submitted Order Line + Valid New Quantity + Change Before Fulfillment → Quantity, Pricing and Reservation Updated
Negative Testing
Jarvis can also generate scenarios designed to exercise Oracle's validations around quantity values, line status, order status and user authorization.
- Decrease Below Shipped Quantity → Expected Quantity Validation
- Invalid Quantity (Zero/Negative) → Expected Field Validation
- Closed/Cancelled Order → Expected Status Validation
- Active Hold on Order → Expected Hold Validation
- Unauthorized User → Expected Security Validation
A negative scenario passes when Oracle correctly enforces the expected business rule or validation.
| Scenario | Oracle Outcome | Test Result |
|---|---|---|
| Valid order change | Change applied | PASS |
| Invalid quantity | Validation occurs | PASS |
| Change conflicts with hold | 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 change-order-quantity scenarios and group them into reusable execution packs.
Change Order Quantity Regression Pack
- Increase Quantity Before Fulfillment
- Decrease Quantity Before Fulfillment
- Increase Quantity After Reservation (Where Allowed)
- Decrease Quantity After Partial Shipment (Where Allowed)
- Quantity Change With Price Recalculation
- Quantity Change on One Line Among Several
- Decrease Below Already-Shipped Quantity
- Change Attempted on Closed/Cancelled Order
- Change Conflicting With Active Hold
- Unauthorized Change Attempt
Run On-Demand or Schedule Automated Batch Execution
SyntraFlow can execute selected change-order-quantity scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.
Once scheduled, SyntraFlow executes the selected change-order-quantity scenarios unattended and records the outcome of each test and business assertion.
| Pack | Change Order Quantity 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.
Regression Pack → Scenario → Business Step → Automation Action → Evidence
Security & Persona Variations
Change privileges for an existing order line are typically restricted by role. Jarvis can generate persona-based variations to confirm that only authorized users can change an order quantity, and that unauthorized attempts are correctly prevented rather than silently allowed.
| Persona | Action | Expected | Syntra Result |
|---|---|---|---|
| Order Entry Specialist | Change Order Quantity | Allowed | PASS |
| Unauthorized User | Attempts Order Change | 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.
From Business Scenario to Execution Evidence
Business teams get readable test documentation; automation teams retain detailed execution traceability.
Meet Jarvis — SyntraFlow's AI Testing Engine
Jarvis extends the Syntra Standard Test Library by analysing the change-order-quantity scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Timing and Direction coverage for the customer's environment.
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.
Business Step → Underlying UI Actions
What SyntraFlow Captures Per Run
Action Status vs. Business Validation
A successful UI interaction does not automatically prove the quantity, pricing and reservation records were updated correctly — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.
| Step | Action Status | Business Validation |
|---|---|---|
| Enter the New Quantity | Pass | — |
| Submit the Quantity Change | Pass | — |
| Verify Line and Order Reflect the Updated Quantity | Pass | Pass |
Related Order Change Tests
Change Order Quantity is one of several ways an existing sales order can be amended within the same Order Changes cluster — explore the related requested-date, cancellation and hold scenarios below.
Turn This Standard Test into Your Oracle Order Quantity Regression Suite
Start with the Syntra Standard change-order-quantity test, use DataVault to provide environment-specific test data, let Jarvis generate additional timing, direction and security variations, and execute the resulting regression pack automatically with SyntraFlow.
Use This Oracle Fusion Test Case
Download Test Case
Excel, CSV or JSON export.
Coming soonAutomate with SyntraFlow
Run this script against your own tenant today.