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

Syntra Standard Oracle Test Library

Oracle Fusion Change Requested Date Test Cases

Validate that changing the customer-requested delivery date on an existing Oracle Fusion sales order line is applied correctly, and that downstream scheduling — including lines that have already been scheduled against the original date — correctly reflects the update.

Test ID	ORCL.O2C.OM.CHG.DATE
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 22 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that the customer-requested delivery date on an existing, submitted Oracle Fusion Order Management sales order line can be changed — whether moved earlier (expedited) or later (postponed) — and that the change is correctly reflected in downstream scheduling and, where applicable, reservation.

The scenario should confirm that:

the requested date on the selected order line is updated to the new value entered
postponing the requested date is handled correctly for a line that has not yet been scheduled
expediting the requested date is handled correctly, including where supply cannot support the earlier date
a line that has already been scheduled against the original requested date is correctly rescheduled once the date changes
reservation is re-evaluated where applicable once the requested date changes
Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers changing the requested date on an existing order line in Oracle Fusion SCM Order Management TEST/UAT environments, both before and after scheduling has run against the original date. It does not cover changing order quantity, ship-to address or cancelling a line, which are covered by the separate Change Order Quantity, Change Ship-To and Cancel Sales Order scenarios in the same Order Changes cluster.

When to Use This Test

Functional testing of requested-date changes for a new Oracle Fusion Order Management implementation
Regression testing of date-change and rescheduling behavior after an Oracle quarterly update
UAT sign-off for order administrators or customer service representatives who routinely change requested dates
Validating that a line already scheduled against the original requested date is correctly rescheduled once the date changes
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and scheduling-related conditions before escalating as a possible APPLICATION_ERROR

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

Navigate to Order Management

→

Locate Order

→

Select Line

→

Change Requested Date

→

Review Scheduling Impact

→

Submit Change

Change Requested Date is one of several scenarios in the Order Changes cluster within Order-to-Cash, alongside Change Order Quantity, Change Ship-To and Cancel Sales Order. It applies to an order line that has already been submitted and, in many cases, already scheduled — so this scenario specifically tests how a date change interacts with scheduling and reservation that has already run. Exact behavior depends on scheduling rules, supply availability, hold configuration and customer-specific Oracle Fusion setup.

← Previous Stage

Change Order Quantity

Next Stage →

Change Ship-To

Preconditions

A sales order exists in Oracle Fusion Order Management with at least one submitted line carrying a requested date.
For pre-scheduling scenarios, the order line has not yet been scheduled against its original requested date.
For post-scheduling scenarios, the order line has already been scheduled against the original requested date.
The test user has appropriate access to open the order and change the requested date on the relevant line.
Item supply/availability data needed to evaluate expedited requested-date scenarios exists in the test environment.

Exact field availability, scheduling behavior and validation messages may vary by Oracle Fusion implementation, scheduling rules, supply configuration and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Order Number	${ORDER_NUMBER}
Order Line	${ORDER_LINE}
Item	${ITEM}
Customer	${CUSTOMER}
Original Requested Date	${ORIGINAL_REQUESTED_DATE}
New Requested Date	${NEW_REQUESTED_DATE}
Line Status	${LINE_STATUS}
Change Reason	${CHANGE_REASON}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Line status and whether scheduling has already run determine which positive and negative variations are relevant for a given order line.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~22 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.	Sign-in completes successfully.
2	Navigate to Order Management Navigate to the Order Management work area.	The Order Management work area opens successfully.
3	Locate the Order Search for and open the sales order to be changed. ${ORDER_NUMBER}	The correct order opens, showing its current lines and line statuses.
4	Select the Line to Change Select the order line whose requested date is to be changed. ${ORDER_LINE} / ${ITEM}	The selected line opens showing its current requested date and status.
5	Enter the New Requested Date Enter the new requested date on the line, either earlier (expedite) or later (postpone) than the original date. ${ORIGINAL_REQUESTED_DATE} / ${NEW_REQUESTED_DATE}	The new requested date is accepted on the line without unexpected validation errors.
6	Review Scheduling Impact Review any scheduling or availability impact Oracle Fusion presents as a result of the requested-date change before submitting. For a line already scheduled against the original date, this step is where Oracle surfaces the anticipated reschedule or supply impact of the new date.	Any scheduling or supply impact of the date change is presented for review.
7	Submit the Change Submit the requested-date change for processing. ${CHANGE_REASON}	Oracle Fusion successfully processes the change without unexpected errors.
8	Verify Updated Date and ScheduleBusiness assertion Reopen or refresh the order line and confirm the requested date, scheduling and reservation status. This is the primary business assertion for the scenario — a correctly updated requested date with correctly reflected scheduling is the expected pass condition, not merely a successful save.	The line reflects the new requested date, and downstream scheduling — and reservation where applicable — correctly reflects the updated date.

Expected Results

The requested date on the selected order line is updated to the new value entered.
Postponing the requested date is accepted for a line that has not yet been scheduled.
Expediting the requested date is accepted where supply supports the earlier date, and correctly rejected or flagged where it does not.
A line already scheduled against the original date is correctly rescheduled to reflect the new date.
Reservation is re-evaluated where applicable once the requested date changes.
A record of the requested-date change is retained in the order's change history.
Other lines on the same order remain unaffected by a change to a single line.

Key Validation Checkpoints

Requested date updated correctly on the line.
Downstream scheduling correctly reflects the new date.
Reservation re-evaluated where applicable.
Change history/audit trail recorded.

Core Business Scenario

Change Requested Date

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 Change Requested Date business scenario. Jarvis AI can extend this scenario by generating additional direction, timing and security variations — postponing versus expediting, before versus after scheduling — using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every direction and timing combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Direction and Timing variations for the customer's environment — including expedited dates that available supply cannot support and date changes attempted against an already-scheduled or held line, since correctly enforced validation in these edge conditions is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Change Requested Date business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Orders, Order Lines, Customers, Items and Scheduling states.

Jarvis AI

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

Positive + Negative Test Variations

Valid requested-date change scenarios and edge cases such as past dates, unsupported expedites or held orders.

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 date direction, timing or line-status combination, SyntraFlow maintains one core Change Requested Date scenario and allows Jarvis AI to generate direction-, timing- and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Change Requested Date 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.

Positive Scenarios

Postpone the requested date on a line before scheduling has run
Expedite the requested date on a line before scheduling has run
Postpone the requested date on a line that has already been scheduled, triggering a reschedule
Expedite the requested date on an already-scheduled line where available supply supports the earlier date
Change the requested date on one line among several lines on the same order

Negative Scenarios

Attempt to set a requested date in the past
Attempt to expedite to a date that available supply cannot support
Attempt a requested-date change on a line that has already shipped
Attempt the change as an unauthorized user
Attempt a requested-date change that conflicts with an active hold on the order
Enter the new requested date in an invalid format

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

Generated Using Your DataVault Test Data

Generic test data rarely represents every order, item, customer and scheduling-state combination in a real Oracle Fusion Order Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Change Requested Date scenarios relevant to the customer's actual implementation.

Standard Library Definition

Order Number            ${ORDER_NUMBER}
Order Line               ${ORDER_LINE}
Item                     ${ITEM}
Customer                 ${CUSTOMER}
Original Requested Date  ${ORIGINAL_REQUESTED_DATE}
New Requested Date       ${NEW_REQUESTED_DATE}
Line Status              ${LINE_STATUS}
Change Reason            ${CHANGE_REASON}

DataVault

Orders / Order Lines
  Submitted lines eligible for a requested-date change, in both pre- and post-scheduling states
Customers
  Active customers associated with test orders
Items
  Items with known supply/availability characteristics
Holds
  Orders with and without an active hold configured
Users
  Personas with and without access to change the requested date

Jarvis AI Generates

Scenario 01 — Postpone Requested Date, Not Yet Scheduled
Scenario 02 — Expedite Requested Date, Not Yet Scheduled
Scenario 03 — Postpone Requested Date, Already Scheduled
Scenario 04 — Expedite Requested Date, Already Scheduled, Supply Available
Scenario 05 — Requested Date in the Past
Scenario 06 — Unauthorized User Attempts Change Requested Date
...

Change Requested Date test data can include sensitive order and customer scheduling information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific order and scheduling 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 Change Requested Date scenarios Jarvis can generate from this business scenario, spanning direction, timing 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	Postpone Date Before Scheduling	Positive/Direction/Timing	Requested date pushed later on a line that has not yet been scheduled	Syntra Ready
VAR-002	Expedite Date Before Scheduling	Positive/Direction/Timing	Requested date pulled earlier on a line that has not yet been scheduled	Syntra Ready
VAR-003	Postpone Date After Scheduling (Reschedule)	Positive/Direction/Timing	Requested date pushed later on an already-scheduled line, triggering a reschedule	Syntra Ready
VAR-004	Expedite Date After Scheduling, Supply Available	Positive/Direction/Timing	Requested date pulled earlier on an already-scheduled line where supply supports the change	Syntra Ready
VAR-005	Date Change on One of Several Lines	Positive	Requested date changed on a single line while other order lines remain unaffected	Syntra Ready
VAR-006	Multiple Lines, Mixed Directions	Positive/Direction	One line postponed and another line expedited on the same order	Syntra Ready
VAR-007	Requested Date in the Past	Negative	New requested date entered is earlier than the current system date	Syntra Ready
VAR-008	Expedite Beyond Available Supply	Negative/Direction/Timing	Expedited date requested cannot be supported by available supply	Syntra Ready
VAR-009	Change Attempted on Shipped Line	Negative/Timing	Requested-date change attempted on a line that has already shipped	Syntra Ready
VAR-010	Unauthorized User Attempts Change	Negative	Requesting user lacks access to change the requested date	Syntra Ready
VAR-011	Change Conflicts With Active Hold	Negative	Requested-date change attempted while an active hold applies to the order	Syntra Ready
VAR-012	Invalid Date Format	Negative	New requested date entered in an invalid or unrecognized format	Syntra Ready

Automatically Expand Positive and Negative Requested Date Coverage

Positive Testing

Jarvis generates scenarios using direction (postpone/expedite) and timing (before/after scheduling) combinations expected to successfully update the requested date on an Oracle Fusion order line.

Line Not Yet Scheduled + Valid New Requested Date + Within Supply → Requested Date Updated

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around date validity, supply availability, order status and security.

Requested Date in the Past → Expected Date Validation
Expedited Date Beyond Available Supply → Expected Scheduling Validation
Change on Shipped Line → Expected Status Validation
Change Conflicting With Active Hold → Expected Hold 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 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 Requested Date scenarios and group them into reusable execution packs.

SCM Order Management Change Requested Date Regression Pack

Postpone Date Before Scheduling
Expedite Date Before Scheduling
Postpone Date After Scheduling (Reschedule)
Expedite Date After Scheduling, Supply Available
Date Change on One of Several Lines
Requested Date in the Past
Expedite Beyond Available Supply
Change Attempted on Shipped Line
Unauthorized User Attempts Change
Change Conflicts With Active Hold

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

Once scheduled, SyntraFlow executes the selected Change Requested Date 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 Change Requested Date Regression Pack
Schedule	Quarterly Update Regression
Tests	12 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 change the requested date on an order line is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that requested-date change access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Order Entry Specialist	Change Requested Date	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.

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 Change Requested Date scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Direction and Timing coverage — including expedited dates beyond available supply and date changes on already-scheduled or held lines — 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 — Change Requested Date, 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

Select the Line to Change

May internally include

Open Order Search → Enter Order Number → Open Order → Select Line → Open Line Detail Panel

Business Step

Review Scheduling Impact

May internally include

Open Schedule Order Action → Read Scheduled Ship/Arrival Dates → Compare Against New Requested Date

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 requested-date change was applied and scheduled correctly — 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: Change Requested Date failed — Likely category: DATA_ERROR — Evidence: the expedited date cannot be supported by available supply — Recommended action: verify supply availability or select a later requested date. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Enter the New Requested Date	Pass	—
Submit the Change	Pass	—
Verify Updated Date and Schedule	Pass	Pass

Related Order Change Tests

Change Requested Date is part of the same Order Changes cluster — explore the related quantity, ship-to and cancellation scenarios below.

Change Order Quantity Change Ship-To Cancel Sales Order

Turn This Standard Test into Your Oracle SCM Change Requested Date Regression Suite

Start with the Syntra Standard Change Requested Date test, use DataVault to provide environment-specific order and scheduling test data, let Jarvis generate additional direction, timing and security variations, and execute the resulting regression pack automatically with SyntraFlow.

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

Frequently Asked Questions

What does this test validate when the requested date changes?

This test validates that changing the customer-requested delivery date on an existing Oracle Fusion Order Management sales order line — whether postponed or expedited — is applied correctly to the line, and that downstream scheduling and, where applicable, reservation correctly reflect the updated date.

What happens when a requested date is expedited past what available supply can support?

Oracle Fusion's scheduling logic is expected to evaluate whether available supply can support an earlier requested date. Where supply cannot support the expedited date, this scenario is designed to confirm that Oracle surfaces the corresponding scheduling limitation rather than silently accepting a date it cannot fulfil. Exact behavior depends on supply configuration and customer-specific setup.

What is the impact on a line that has already been scheduled against the original date?

For an order line already scheduled against its original requested date, this scenario tests that changing the date triggers a reschedule so that scheduling — and reservation where applicable — reflects the new date, rather than leaving the line scheduled against the outdated original date.

What date validation rules does this test cover?

Representative validations include rejecting or flagging a requested date entered in the past, rejecting an invalid or unrecognized date format, and confirming that a date change is not accepted where it conflicts with an active hold on the order. Exact validation messages and enforcement depend on the customer's Oracle Fusion configuration.

How does security testing work for changing the requested date?

Access to change the requested date on an order line is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as an authorised order entry specialist versus an unauthorized user — to confirm that access behaves as expected. This is test automation executed against Oracle Fusion TEST/UAT environments only and does not create real order fulfillment or financial transactions.