Oracle ERP Testing Tool > Test Library > SCM > Order Management > Fulfillment
Syntra Standard Oracle Test Library

Oracle Fusion Reserve Order Test Cases

Validate hard-reservation of specific on-hand inventory against a scheduled sales order line in Oracle Fusion Order Management, confirming the reserved quantity is correctly protected from allocation to other demand.

Test IDORCL.O2C.OM.FUL.RESERVE
ApplicationOracle Fusion Cloud
ProductSCM / Order Management
ModuleOrder Management
ProcessFulfillment
Business FlowOrder-to-Cash
Scenario TypePositive / Functional
Test UsageFunctional Testing / Regression Testing / UAT
PriorityHigh
AutomationSyntraFlow Ready
LibrarySyntra 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 15 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a scheduled sales order line can be hard-reserved against specific on-hand inventory in Oracle Fusion Order Management, and that the reserved quantity is correctly protected from allocation to other demand.

The scenario should confirm that:

  • a scheduled order line can be reserved against specific on-hand inventory in the sourced warehouse and subinventory
  • the reserved quantity is correctly held apart from other demand once reservation completes
  • available-to-promise correctly reflects the reservation once it is applied
  • lot- and serial-controlled items can be reserved to the correct lot or serial
  • Oracle's validations correctly block reservation when on-hand is insufficient, the order is held, or the location is invalid
  • reservation history and audit trail are recorded for traceability

This scenario covers hard reservation of a line that has already been scheduled, distinguishing a 'reserved' line — specific on-hand inventory protected for this order — from a merely 'scheduled' line, which is a supply commitment without a hard reservation. Scheduling itself is covered by the separate Schedule Order scenario; the release of reserved inventory to a pick task is covered by the separate Pick Release scenario.

When to Use This Test

  • Functional testing of hard-reservation behavior for a new Oracle Fusion Order Management implementation
  • Regression testing of reservation, lot/serial allocation and available-to-promise behavior after an Oracle quarterly update
  • UAT sign-off for fulfillment teams that routinely reserve standard, lot-controlled and serial-controlled items
  • Coverage step referenced by the pick-release and ship-confirm scenarios within the broader Fulfillment flow

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

Schedule Order
Reserve Order
Pick Release
Ship Confirm

Reserve Order is the step that hard-commits specific on-hand inventory to a scheduled order line, protecting it from being consumed by other demand ahead of pick release. Not every implementation uses manual reservation for every order type — exact behavior depends on item, warehouse and customer-specific Oracle Fusion configuration.

Preconditions

  1. The sales order line has been scheduled and carries a valid schedule ship date.
  2. Sufficient on-hand inventory exists in the sourced warehouse and subinventory to support the reservation.
  3. Lot and/or serial control, where applicable, is correctly configured for the item.
  4. The user performing the reservation holds the appropriate Order Management / inventory reservation privileges.
  5. The test user is signed in to an Oracle Fusion Order Management TEST/UAT environment.

Exact reservation behavior, on-hand availability and lot/serial eligibility may vary by item, warehouse, subinventory and customer-specific Oracle Fusion configuration.

Sample Test Data

Order Number${ORDER_NUMBER}
Order Line${ORDER_LINE}
Item${ITEM}
Quantity${QUANTITY}
Warehouse${WAREHOUSE}
Subinventory${SUBINVENTORY}
Lot${LOT}
Serial${SERIAL}
Reservation Type${RESERVATION_TYPE}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Lot and serial fields apply only to lot- or serial-controlled items; on-hand availability in the sourced warehouse and subinventory typically determines whether a given reservation succeeds.

Test Steps

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

#User ActionExpected Result
1
Sign In to Oracle Fusion
Sign in to Oracle Fusion using an authorised Order Management test user.
Oracle Fusion Order Management is accessible to the signed-in test user.
2
Navigate to Order Management
Navigate to the Order Management work area.
The Order Management work area opens successfully.
3
Locate the Scheduled Order
Search for and open the sales order containing the scheduled line to be reserved.
${ORDER_NUMBER}

This single business step replaces multiple technical actions such as opening order search, entering search criteria and selecting the result.

The correct scheduled order opens for review.
4
Initiate Reservation
Select the scheduled order line and initiate the reservation action.
${ORDER_LINE}
Oracle Fusion begins processing the reservation request for the selected line.
5
Review Available On-Hand and Reservation Candidates
Review the on-hand quantity, warehouse, subinventory and any lot/serial candidates available to satisfy the reservation.
${WAREHOUSE} / ${SUBINVENTORY}

Reviewing availability before confirming helps distinguish an availability issue from a reservation or configuration issue if the test later fails.

Available on-hand and eligible reservation candidates are displayed for the item.
6
Confirm Reservation Details
Confirm the reservation quantity and, where the item is lot- or serial-controlled, select the specific lot or serial to reserve.
${LOT} / ${SERIAL}
Reservation details, including lot or serial selection where applicable, are accepted.
7
Submit Reservation
Submit the reservation for processing.
Oracle Fusion accepts the reservation without unexpected errors.
8
Verify Reserved Quantity Protected and Reflected in AvailabilityBusiness assertion
Reopen or refresh the order line and review the reservation status and available-to-promise quantity.

This is the primary business assertion for the scenario — correctly protecting the reserved quantity and reflecting it in availability is the expected pass condition, not merely an accepted reservation request.

The reserved quantity is correctly tied to the order line, protected from allocation to other demand, and available-to-promise reflects the reservation.

Expected Results

  • The order line reserves successfully once sufficient on-hand inventory exists in the sourced warehouse and subinventory.
  • The reserved quantity is correctly protected from allocation to other demand.
  • Available-to-promise correctly reflects the reservation once it is applied.
  • Lot- and serial-controlled items reserve correctly to the selected lot or serial.
  • Oracle's validations correctly block reservation when on-hand is insufficient, the order is held, or the warehouse/subinventory is invalid.
  • Reservation history and audit trail are recorded for traceability.

Key Validation Checkpoints

  • The reserved quantity is correctly protected from allocation to other demand.
  • Available-to-promise correctly reflects the reservation.
  • The reservation is correctly tied to the specific order line.
  • Reservation history and audit trail are recorded.
Core Business Scenario
Reserve Order
Business Steps
8
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 Reserve Order business scenario. Jarvis AI can extend this scenario by generating additional lot/serial, availability and security variations using customer-specific test data available through Syntra DataVault.

Teams do not need to manually build a separate test for every warehouse, lot-control setup or availability condition combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Lot/Serial and Availability variations for the customer's environment — with reservation-protection coverage weighted especially heavily, since correctly protecting reserved on-hand from other demand is the core of what this scenario proves.

From Standard Test to Executed Regression Pack

01
Syntra Standard Test
Reusable Reserve Order business process and automation logic.
02
Customer DataVault
Provides approved customer-specific test data and configuration required for scenario generation — orders, items, warehouses, subinventories and lot/serial data.
03
Jarvis AI
Analyses the standard scenario together with available test data and generates relevant lot/serial, availability and security variations.
04
Positive + Negative Test Variations
Valid reservation scenarios and edge cases such as insufficient on-hand, held orders or unauthorized attempts.
05
Regression Pack
Selected variations can be grouped into an executable suite.
06
On-Demand / Scheduled / Batch Execution
Execute immediately or schedule the regression pack for unattended batch execution.
07
Results + Evidence + Exceptions
Capture execution results, business assertions, screenshots/evidence and exceptions.

Rather than maintaining a separate test page for every possible warehouse, lot-control setup or availability condition, SyntraFlow maintains one core Reserve Order scenario and allows Jarvis AI to generate lot/serial-driven, availability-driven and security-specific variations using the customer's available test data.

AI-Generated Test Variations

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

Positive Scenarios
  • Standard reservation against available on-hand
  • Lot-controlled reservation
  • Serial-controlled reservation
  • Reservation across multiple lots to satisfy full quantity
  • Reservation on one line among several
Negative Scenarios
  • Attempt reservation with insufficient on-hand to fully reserve
  • Attempt reservation against an invalid warehouse/subinventory
  • Attempt reservation on a held order
  • Attempt reservation twice on the same line
  • Attempt manual reservation by an unauthorized user
  • Attempt reservation when lot/serial is unavailable for reservation

These are representative examples only. Negative-scenario behavior and available reservation paths 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 warehouse, subinventory, lot-control setup and item combination in a real Oracle Fusion Order Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Reserve Order scenarios relevant to the customer's actual implementation.

Standard Library Definition

Order Number         ${ORDER_NUMBER}
Order Line            ${ORDER_LINE}
Item                  ${ITEM}
Quantity              ${QUANTITY}
Warehouse             ${WAREHOUSE}
Subinventory          ${SUBINVENTORY}
Lot                   ${LOT}
Serial                ${SERIAL}
Reservation Type      ${RESERVATION_TYPE}

DataVault

Sales Orders
  Scheduled order lines eligible for reservation
Items
  Active sellable items, lot/serial control attributes
Inventory
  On-hand quantity by warehouse and subinventory
Lots / Serials
  Available lot and serial numbers per item
Users
  Active fulfillment users with reservation privileges

Jarvis AI Generates

Scenario 01 — Standard Reservation Against Available On-Hand
Scenario 02 — Lot-Controlled Reservation
Scenario 03 — Serial-Controlled Reservation
Scenario 04 — Multi-Lot Reservation
Scenario 05 — Insufficient On-Hand Reservation Attempt
Scenario 06 — Unauthorized User Attempts Manual Reservation
...

Reserve Order test data can include sensitive commercial and inventory information such as customer, item and warehouse detail. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific reservation 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 Reserve Order scenarios Jarvis can generate from this business scenario, spanning lot/serial and availability conditions. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

IDVariationTypeKey DifferenceExecution
VAR-001Standard Reservation Against Available On-HandPositiveReservation applied against available on-hand in the sourced warehouse and subinventorySyntra Ready
VAR-002Lot-Controlled ReservationPositive/Lot/SerialReservation applied to a specific lot for a lot-controlled itemSyntra Ready
VAR-003Serial-Controlled ReservationPositive/Lot/SerialReservation applied to specific serial numbers for a serial-controlled itemSyntra Ready
VAR-004Multi-Lot ReservationPositive/Lot/SerialReservation spans multiple lots to satisfy the full order quantitySyntra Ready
VAR-005Reservation on One Line Among SeveralPositiveReservation applied correctly to one line without affecting sibling order linesSyntra Ready
VAR-006Availability Verification After ReservationPositive/AvailabilityAvailable-to-promise correctly reflects the reserved quantity after reservationSyntra Ready
VAR-007Insufficient On-HandNegative/AvailabilityReservation blocked or partially satisfied due to insufficient on-hand quantitySyntra Ready
VAR-008Invalid Warehouse/SubinventoryNegativeReservation blocked when the sourced warehouse or subinventory is invalidSyntra Ready
VAR-009Reservation on Held OrderNegativeReservation blocked while the order remains on holdSyntra Ready
VAR-010Duplicate Reservation AttemptNegativeA second reservation attempt on an already-reserved line is rejectedSyntra Ready
VAR-011Unauthorized Manual Reservation AttemptNegativeManual reservation attempt blocked for a user without reservation privilegesSyntra Ready
VAR-012Lot/Serial UnavailableNegative/Lot/SerialReservation blocked when the requested lot or serial is not availableSyntra Ready

Automatically Expand Positive and Negative Reserve Order Coverage

Positive Testing

Jarvis generates scenarios using order lines, items and inventory expected to reserve successfully within Oracle Fusion Order Management.

Scheduled Line + Sufficient On-Hand + Valid Warehouse/Subinventory → Line Reserved and Protected from Other Demand

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around on-hand availability, location validity, order holds, duplicate reservation, lot/serial availability and security.

  • Insufficient On-Hand → Expected Availability Validation
  • Invalid Warehouse/Subinventory → Expected Location Validation
  • Held Order → Expected Hold Validation
  • Duplicate Reservation → Expected Status Validation
  • Unauthorized User → Expected Access Restriction

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

ScenarioOracle OutcomeTest Result
Valid order scheduledOrder scheduledPASS
Insufficient supplyValidation occursPASS
Held orderScheduling blockedPASS
Security restrictionAccess preventedPASS
Unexpected application exceptionUnexpected failureFAIL

Turn AI-Generated Variations into a Regression Pack

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

Order Management Reserve Order Regression Pack

  • Standard Reservation Against Available On-Hand
  • Lot-Controlled Reservation
  • Serial-Controlled Reservation
  • Multi-Lot Reservation
  • Reservation on One Line Among Several
  • Insufficient On-Hand
  • Invalid Warehouse/Subinventory
  • Reservation on Held Order
  • Duplicate Reservation Attempt
  • Unauthorized Manual Reservation Attempt
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 Reserve Order scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected Reserve 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
PackOrder Management Reserve Order Regression Pack
ScheduleQuarterly Update Regression
Tests12 scenarios
ExecutionBatch Mode
Start10:00 PM
EnvironmentOracle Fusion TEST
StatusScheduled

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.

12
Total Scenarios
10
Passed
1
Failed
1
Exceptions
6
Positive Tests
6
Negative Tests
24
Business Assertions

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

Security & Persona Variations

Access to manually reserve a sales order line is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that reservation access behaves as expected for each role — not to assert a single universal Oracle security model.

PersonaActionExpectedSyntra Result
Order Fulfillment SpecialistReserve OrderAllowedPASS
Unauthorized UserAttempts Manual ReservationAccess preventedPASS

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 Reserve Order scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Lot/Serial and Availability 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 — Reserve Order, 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
Locate the Scheduled Order
May internally include
Open Order Search → Enter Order Number → Search → Select Order → Open Order Details → Confirm
Business Step
Verify Reserved Quantity Protected and Reflected in Availability
May internally include
Refresh Order Line → Read Reservation Status → Read Available-to-Promise → Compare Against Expected Reserved Quantity

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 reservation was correctly applied and protected — this is illustrative of how SyntraFlow separates action success from business validation; it does not reflect a specific live execution.

StepAction StatusBusiness Validation
Submit the ReservationPass
Verify Reserved Quantity ProtectedPassPass
Verify Available-to-Promise Reflects ReservationPassPass

Related Fulfillment Tests

Reserve Order sits between scheduling and pick release in the Fulfillment scenario family. Explore the related stages below.

Turn This Standard Test into Your Oracle Order Management Reserve Order Regression Suite

Start with the Syntra Standard Reserve Order test, use DataVault to provide environment-specific test data, let Jarvis generate additional lot/serial, availability 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 soon

Automate with SyntraFlow

Run this script against your own tenant today.

Frequently Asked Questions

What is the difference between a scheduled order line and a reserved order line?
A scheduled line has a supply commitment — a schedule ship date backed by expected supply — but no specific inventory is set aside. A reserved line goes further: specific on-hand inventory in a warehouse and subinventory (and, where applicable, a specific lot or serial) is hard-committed to that line and protected from allocation to other demand.
What happens if there is insufficient on-hand inventory to reserve?
Oracle Fusion is expected to block or partially satisfy the reservation depending on configuration, and this test's negative variations exercise that condition as an expected pass outcome — the reservation correctly reflects the available quantity rather than reserving more than is on hand.
How are lot- and serial-controlled items handled during reservation?
For lot-controlled items, the test validates reservation against a specific lot or, where required, across multiple lots to satisfy the full quantity. For serial-controlled items, the test validates reservation against specific serial numbers. Both are exercised as positive variations of this scenario.
How is security tested for order reservation?
Jarvis can generate persona-based variations, such as an authorized order fulfillment specialist compared with an unauthorized user, to confirm that manual reservation access is correctly enforced according to the customer's Oracle Fusion security configuration.
Do all these variations need separate test library pages?
No. Jarvis AI generates positive, negative, lot/serial and availability variations of Reserve Order from this single canonical scenario definition rather than maintaining a separate indexable page for each combination.