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

Syntra Standard Oracle Test Library

Oracle Fusion Schedule Order Test Cases

Validate that a submitted sales order line schedules correctly in Oracle Fusion Order Management — determining the sourcing warehouse and a confirmed ship date based on available supply — and that scheduling is correctly blocked where supply, status or security conditions are not met.

Test ID	ORCL.O2C.OM.FUL.SCHEDULE
Application	Oracle Fusion Cloud
Product	SCM / Order Management
Module	Order Management
Process	Fulfillment
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 15 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a submitted sales order line can be scheduled in Oracle Fusion Order Management — with the correct warehouse sourced and a confirmed ship date determined from actual supply availability — and that Oracle correctly blocks scheduling where supply, status or authorization conditions are not met.

The scenario should confirm that:

the order line schedules successfully once supply is confirmed at an eligible warehouse
the confirmed ship date correctly reflects available supply for the item and quantity requested
the correct warehouse is sourced according to configured sourcing rules
the order line status updates to scheduled once scheduling completes
scheduling is correctly blocked on held or cancelled order lines
unauthorized manual scheduling overrides are correctly prevented

This scenario covers scheduling of an already-submitted order line within Oracle Fusion Order Management TEST/UAT environments. It does not cover submission of the order itself, which is covered by the separate Submit Sales Order scenario, or the downstream reservation, pick release and ship confirm steps, which are covered by their own scenarios in this Fulfillment cluster.

When to Use This Test

Functional testing of order scheduling and warehouse sourcing logic for a new Oracle Fusion Order Management implementation
Regression testing of scheduling and supply-availability behavior after an Oracle quarterly update
UAT sign-off for fulfillment teams that routinely process standard, split and multi-warehouse scheduling scenarios
First validation step referenced by the reserve-order, pick-release and ship-confirm scenarios within the broader Fulfillment cluster

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

Submit Sales Order

→

Schedule Order

→

Reserve Order

→

Pick Release

→

Ship Confirm

Schedule Order is the first step in Oracle Fusion Order Management's Fulfillment cluster, determining warehouse sourcing and a confirmed ship date for a submitted order line before reservation and downstream pick and ship processing begin. Exact scheduling logic depends on sourcing rules, supply data and customer-specific Oracle Fusion configuration.

Preconditions

A sales order line exists in Oracle Fusion Order Management with a status of Submitted and is eligible for scheduling.
Supply and inventory availability data for the ordered item is available across the candidate warehouses considered by the sourcing rule.
Sourcing rules and warehouse configuration relevant to the item and order type are set up in the environment.
The user performing scheduling holds the appropriate Order Management scheduling privileges.
The test user is signed in to an Oracle Fusion Order Management TEST/UAT environment.

Exact scheduling behavior, sourcing outcomes and available ship dates may vary by item, warehouse configuration, sourcing rule, order type and customer-specific Oracle Fusion configuration.

Sample Test Data

Order Number	${ORDER_NUMBER}
Item	${ITEM}
Quantity	${QUANTITY}
Requested Date	${REQUESTED_DATE}
Warehouse (Sourced)	${WAREHOUSE}
Schedule Ship Date	${SCHEDULE_SHIP_DATE}
Order Type	${ORDER_TYPE}
Business Unit	${BUSINESS_UNIT}
Sourcing Rule	${SOURCING_RULE}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Supply availability at each candidate warehouse typically determines the sourced warehouse and confirmed ship date.

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 Action	Expected 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 Submitted Order Search for and open the submitted sales order containing the line to be scheduled. ${ORDER_NUMBER} This single business step replaces multiple technical actions such as opening order search, entering search criteria and selecting the result.	The correct submitted order opens and the target order line is visible.
4	Initiate Scheduling Select the order line and initiate the scheduling action.	Oracle Fusion begins evaluating supply and sourcing for the selected line.
5	Review Supply Availability and Sourcing Recommendation Review the supply availability and warehouse sourcing recommendation Oracle Fusion presents for the requested item and quantity. ${ITEM}, ${QUANTITY} Reviewing the recommendation before confirming helps distinguish a supply-data issue from a scheduling or configuration issue if the test later fails.	Oracle Fusion presents a sourcing recommendation and available supply consistent with configured sourcing rules.
6	Confirm or Adjust the Ship Date Confirm the recommended ship date, or review the adjusted date Oracle Fusion proposes where full supply is not available on the requested date. ${REQUESTED_DATE}	A ship date consistent with available supply is confirmed or presented for confirmation.
7	Submit the Scheduling Action Submit the scheduling action for the order line.	Oracle Fusion accepts the scheduling action without unexpected errors.
8	Verify Line Status Updated to Scheduled with Correct Warehouse and DateBusiness assertion Reopen or refresh the order line and review its status, sourced warehouse and confirmed ship date. ${WAREHOUSE}, ${SCHEDULE_SHIP_DATE} This is the primary business assertion for the scenario — a correct warehouse, confirmed ship date and status transition are the expected pass condition, not merely an accepted scheduling action.	The order line status updates correctly to scheduled, with the correct warehouse sourced and a confirmed ship date reflecting available supply.

Expected Results

The order line schedules successfully once supply is confirmed at an eligible warehouse.
The confirmed ship date correctly reflects available supply for the item and quantity.
The correct warehouse is sourced according to configured sourcing rules.
Scheduling attempts on held or cancelled order lines are correctly blocked.
Insufficient supply, invalid item/warehouse combinations and invalid requested dates are correctly rejected.
The order line status updates to scheduled once the warehouse and ship date are confirmed.

Key Validation Checkpoints

The confirmed ship date reflects actual supply availability.
The correct warehouse is sourced based on configured sourcing rules.
The order line status updates to scheduled.
Scheduling is correctly blocked on held or cancelled order lines.

Core Business Scenario

Schedule Order

Business Steps

Test Variations

AI-Generated

Test Data

DataVault-Driven

Execution

On-Demand / Scheduled / Batch

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core Schedule Order business scenario. Jarvis AI can extend this scenario by generating additional supply, warehouse, status and security variations using customer-specific test data available through Syntra DataVault.

Teams do not need to manually build a separate test for every supply condition, warehouse combination or security scenario. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Supply and Warehouse variations for the customer's environment — with sourcing and ship-date accuracy weighted especially heavily, since correctly determining the warehouse and confirmed ship date from real supply availability is the core of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Schedule Order business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — orders, items, warehouses and supply.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant supply, warehouse and security variations.

Positive + Negative Test Variations

Valid scheduling scenarios and edge cases such as insufficient supply, held orders or unauthorized overrides.

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 supply condition, warehouse combination or security restriction, SyntraFlow maintains one core Schedule Order scenario and allows Jarvis AI to generate supply-driven, warehouse-driven and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Schedule 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

Schedule a standard order line with full supply available
Schedule an order line with partial supply resulting in a split, where supported
Schedule an order line sourced from an alternate warehouse
Schedule an order line confirming the originally requested ship date
Schedule an order line with a later confirmed date due to supply constraints
Schedule multiple order lines on the same order

Negative Scenarios

Attempt scheduling when no supply is available at any candidate warehouse
Attempt scheduling with an invalid item/warehouse combination
Attempt scheduling on a held order
Attempt scheduling on a cancelled order line
Attempt a manual scheduling override as an unauthorized user
Attempt scheduling with an invalid requested date
Attempt scheduling that conflicts with a closed calendar period

These are representative examples only. Negative-scenario behavior and available scheduling paths can depend on the customer's Oracle Fusion configuration, sourcing rules and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every item, warehouse, supply condition and sourcing rule combination in a real Oracle Fusion Order Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Schedule Order scenarios relevant to the customer's actual implementation.

Standard Library Definition

Order Number         ${ORDER_NUMBER}
Item                  ${ITEM}
Quantity              ${QUANTITY}
Requested Date        ${REQUESTED_DATE}
Warehouse (Sourced)   ${WAREHOUSE}
Schedule Ship Date    ${SCHEDULE_SHIP_DATE}
Order Type            ${ORDER_TYPE}
Business Unit         ${BUSINESS_UNIT}
Sourcing Rule         ${SOURCING_RULE}

DataVault

Sales Orders
  Submitted order lines eligible for scheduling
Items
  Active sellable items and catalog
Warehouses
  Candidate warehouses and sourcing rules
Supply
  On-hand and available-to-promise supply by warehouse
Calendars
  Open and closed scheduling periods
Users
  Active fulfillment users with scheduling privileges

Jarvis AI Generates

Scenario 01 — Standard Scheduling with Full Supply
Scenario 02 — Partial Supply Split Scheduling
Scenario 03 — Alternate Warehouse Sourcing
Scenario 04 — Later Confirmed Date Due to Supply Constraint
Scenario 05 — No Supply at Any Warehouse
Scenario 06 — Scheduling Attempted on Held Order
...

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

ID	Variation	Type	Key Difference	Execution
VAR-001	Standard Scheduling with Full Supply	Positive/Supply	Order line scheduled with full supply available at the sourced warehouse	Syntra Ready
VAR-002	Partial Supply Split Scheduling	Positive/Supply	Partial supply results in a split schedule, where supported	Syntra Ready
VAR-003	Alternate Warehouse Sourcing	Positive/Warehouse	Line sourced from an alternate warehouse when the primary lacks supply	Syntra Ready
VAR-004	Requested Date Confirmed	Positive	Confirmed ship date matches the originally requested date	Syntra Ready
VAR-005	Later Date Due to Supply Constraint	Positive/Supply	Confirmed ship date moves later based on actual supply availability	Syntra Ready
VAR-006	Multiple Lines Scheduled on Same Order	Positive	Multiple order lines on the same order scheduled successfully	Syntra Ready
VAR-007	No Supply at Any Warehouse	Negative/Supply	Scheduling blocked when no candidate warehouse has supply	Syntra Ready
VAR-008	Invalid Item/Warehouse Combination	Negative/Warehouse	Scheduling blocked for an invalid item/warehouse combination	Syntra Ready
VAR-009	Scheduling Attempted on Held Order	Negative	Scheduling blocked while the order remains on hold	Syntra Ready
VAR-010	Scheduling Attempted on Cancelled Line	Negative	Scheduling blocked for a cancelled order line	Syntra Ready
VAR-011	Unauthorized Manual Override Attempt	Negative	Manual scheduling override blocked for an unauthorized user	Syntra Ready
VAR-012	Invalid Requested Date	Negative	Scheduling blocked or rejected for an invalid requested date	Syntra Ready
VAR-013	Closed Calendar Period Conflict	Negative/Warehouse	Scheduling blocked when it conflicts with a closed calendar period	Syntra Ready

Automatically Expand Positive and Negative Schedule Order Coverage

Positive Testing

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

Submitted Line + Supply Available + Valid Warehouse → Order Scheduled with Confirmed Ship Date

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around supply availability, warehouse configuration, order and line status, calendar periods and security.

No Supply at Any Warehouse → Expected Supply Validation
Invalid Item/Warehouse Combination → Expected Configuration Validation
Held Order → Expected Status Validation
Cancelled Line → Expected Status Validation
Unauthorized User → Expected Access Restriction

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

Scenario	Oracle Outcome	Test Result
Valid order scheduled	Order scheduled	PASS
Insufficient supply	Validation occurs	PASS
Held order	Scheduling blocked	PASS
Security restriction	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

Order Management Schedule Order Regression Pack

Standard Scheduling with Full Supply
Partial Supply Split Scheduling
Alternate Warehouse Sourcing
Requested Date Confirmed
Later Date Due to Supply Constraint
Multiple Lines Scheduled on Same Order
No Supply at Any Warehouse
Invalid Item/Warehouse Combination
Scheduling Attempted on Held Order
Scheduling Attempted on Cancelled Line
Unauthorized Manual Override Attempt
Closed Calendar Period Conflict

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

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

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

Pack	Order Management Schedule Order 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 & Persona Variations

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

Persona	Action	Expected	Syntra Result
Order Fulfillment Specialist	Schedule Order	Allowed	PASS
Unauthorized User	Attempts Manual Scheduling Override	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 Schedule Order scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Supply and Warehouse 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 — Schedule 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 Submitted Order

May internally include

Open Order Search → Enter Order Number → Search → Select Order → Open Order Details → Confirm

Business Step

Verify Line Status Updated to Scheduled with Correct Warehouse and Date

May internally include

Refresh Order Line → Read Line Status → Read Sourced Warehouse → Read Confirmed Ship Date → Compare Against Expected Values

What SyntraFlow Captures Per Run

Parameterised input valuesReusable navigationAutomation action traceScreenshots / evidence captureExecution timingPass / fail statusBusiness assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction does not automatically prove the order line was sourced or dated 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
Submit the Scheduling Action	Pass	—
Verify Line Status Updated to Scheduled	Pass	Pass
Verify Correct Warehouse and Confirmed Ship Date	Pass	Pass

Related Fulfillment Tests

Schedule Order is the first step in the Fulfillment scenario cluster — the scheduled line now flows into reservation, pick release and ship confirmation. Explore the related fulfillment scenarios below.

Reserve Order Pick Release Ship Confirm

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

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

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

Frequently Asked Questions

How is the sourcing warehouse determined during scheduling?

Oracle Fusion evaluates configured sourcing rules together with available supply at each candidate warehouse for the requested item and quantity, and recommends the warehouse that satisfies those rules. This test validates that the correct warehouse is sourced; it does not itself define or change sourcing rule configuration.

What happens when there isn't enough supply to schedule the order line?

Where no candidate warehouse has sufficient supply on the requested date, Oracle Fusion is expected to either propose a later confirmed ship date or block scheduling, depending on configuration. This test's negative variations exercise insufficient-supply conditions as expected pass outcomes, not failures.

Does SyntraFlow test split scheduling scenarios?

Where partial supply is available and Oracle Fusion's configuration supports it, Jarvis can generate a split-scheduling variation to confirm the line is scheduled correctly across the available supply. Split behavior depends on the customer's order-management setup.

How is security tested for the scheduling action?

Jarvis can generate persona-based variations, such as an authorized Order Fulfillment Specialist compared with a user attempting an unauthorized manual scheduling override, to confirm that scheduling access is enforced according to the customer's Oracle Fusion security configuration.

How does SyntraFlow help distinguish an Oracle defect from expected validation when a scheduling test fails?

SyntraFlow's execution evidence is reviewed against failure categories such as data, configuration, security, expected validation, automation, integration, environment and application issues. For example, if Schedule Order fails because no supply is available at any candidate warehouse for the requested date, the evidence points to an expected validation outcome, not an application defect — the recommended action is to adjust the requested date or select an alternate item or warehouse. A scheduling failure should not be labeled an Oracle defect without supporting evidence.