Oracle ERP Testing Tool > Test Library > SCM > Order Management > Sales Orders

Syntra Standard Oracle Test Library

Oracle Fusion Create Multi-Line Order Test Cases

Validate that a sales order containing multiple, distinct line items can be created in Oracle Fusion Order Management, with each line independently priced and schedulable by item, quantity, warehouse and requested date.

Test ID	ORCL.O2C.OM.SO.MULTILINE
Application	Oracle Fusion Cloud
Product	SCM / Order Management
Module	Order Management
Process	Sales Orders
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 34 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that a sales order containing multiple, independently priced and schedulable line items can be created in Oracle Fusion Order Management, and that each line captures its own item, quantity, unit of measure, warehouse and requested date without cross-line interference.

The scenario should confirm that:

the order header captures the correct customer and order-level attributes
each line item is created with the correct item, quantity, unit of measure, warehouse and requested date
line-level scheduling and warehouse assignment can differ independently across lines on the same order
line-level status is tracked independently and does not default to the status of other lines on the order
the order-level status correctly reflects the aggregate status of its underlying lines
Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario extends the single-line Create Sales Order scenario to cover orders containing multiple distinct line items, each potentially scheduled, warehoused or priced independently. It does not cover single-line order creation, which is covered by the separate Create Sales Order scenario, or order-level discounting and tax calculation, covered by Create Order With Discount and Create Order With Tax, within the same Sales Orders cluster.

When to Use This Test

Functional testing of multi-line sales order creation for a new Oracle Fusion Order Management implementation
Regression testing of line-level scheduling and warehouse assignment after an Oracle quarterly update
UAT sign-off for order entry specialists who routinely enter orders with multiple distinct line items
Validating that a validation issue on one order line does not corrupt or block the other valid lines on the same order
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during multi-line order creation before escalating as a possible APPLICATION_ERROR

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

Navigate to Order Management

→

Create Sales Order

→

Select Customer

→

Add Multiple Lines

→

Schedule Lines

→

Review Order

→

Submit

Create Multi-Line Order builds on the single-line Create Sales Order scenario within the Sales Orders cluster, extending it to orders where multiple line items must each be entered, scheduled and warehoused independently. Once a multi-line order is created, downstream scenarios such as Create Order With Discount and Create Order With Tax in the same cluster cover order-level pricing behavior. Exact field availability, scheduling rules and validation depend on item setup, warehouse configuration and customer-specific Oracle Fusion configuration.

← Previous Stage

Create Sales Order

Next Stage →

Create Order With Discount

Preconditions

Multiple items used on the order are active and orderable in the target Oracle Fusion Order Management environment.
The customer used on the order is active and enabled for order capture.
The price list assigned to the order covers every item included across all order lines.
The warehouses referenced on individual lines are active and enabled for the items being ordered.
The order entry specialist has appropriate access to create sales orders for the relevant business unit.

Exact field availability, mandatory fields and validation messages may vary by Oracle Fusion implementation, item and warehouse configuration, and customer-specific configuration. State and readiness requirements vary by implementation.

Sample Test Data

Customer	${CUSTOMER}
Item 1	${ITEM_1}
Item 2	${ITEM_2}
Item 3	${ITEM_3}
Quantity	${QUANTITY}
UOM	${UOM}
Warehouse	${WAREHOUSE}
Requested Date	${REQUESTED_DATE}
Price List	${PRICE_LIST}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion Order Management TEST/UAT environment. Each line on a multi-line order may reference a different item, quantity, warehouse or requested date rather than reusing the same value across every line.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to Order Management Sign in to Oracle Fusion using an authorised order entry specialist test user and navigate to the Order Management work area.	The Order Management work area opens successfully.
2	Navigate to Sales Orders Open the Sales Orders page to begin creating a new sales order.	The sales order creation page opens for the correct business unit.
3	Initiate Create Sales Order Initiate a new sales order for the test order entry specialist. This single business step replaces multiple technical actions such as opening the create page and confirming the business unit.	A new, unsaved sales order is opened, ready for header and line entry.
4	Select Customer Search for and select the customer for the sales order. ${CUSTOMER}	The customer is accepted and reflected on the order header, and an applicable price list is assigned.
5	Add Multiple Item Lines Add three or more distinct item lines to the order, entering an independent quantity, unit of measure, warehouse and requested date for each line. ${ITEM_1} / ${ITEM_2} / ${ITEM_3} / ${QUANTITY} / ${UOM} / ${WAREHOUSE} / ${REQUESTED_DATE}	Each line is added to the order with its own item, quantity, UOM, warehouse and requested date accepted without unexpected validation errors.
6	Review All Lines Review every line on the order, comparing item, quantity, warehouse and requested date against the entered test data before submitting. Reviewing every line before submission lets the tester catch an incorrect line entry before the order is submitted.	All lines reflect the entered item, quantity, warehouse and requested date detail correctly.
7	Submit the Sales Order Submit the sales order for processing in the test environment.	Oracle Fusion successfully processes the sales order without unexpected errors.
8	Verify Order-Level and Line-Level StatusBusiness assertion Reopen or refresh the sales order and confirm the order-level status together with the status of each individual line. This is the primary business assertion for the scenario — correctly created lines with accurate, independently tracked status is the expected pass condition, not merely a successful submission.	The order-level status correctly reflects the aggregate status of its lines, and each line shows its own correct, independently tracked status.

Expected Results

The sales order is created with all entered line items present.
Each line reflects its own item, quantity, UOM, warehouse and requested date.
Line-level status is tracked independently for each line.
Order-level status correctly reflects the aggregate status of its lines.
A validation issue on one line does not prevent the other valid lines from being created.
The order is visible and traceable for the test order entry specialist.

Key Validation Checkpoints

All lines are created with correct item, quantity, warehouse and scheduling details.
Line-level status is tracked independently from the status of other lines on the order.
Order-level status correctly reflects the aggregate status of its underlying lines.
A failure on one line does not corrupt or block the other valid lines on the order.

Core Business Scenario

Create Multi-Line 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 Create Multi-Line Order business scenario. Jarvis AI can extend this scenario by generating additional warehouse, scheduling, item, quantity and line-count variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every warehouse, date or line-count combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Boundary and Line Isolation variations for the customer's environment — including large line-count orders and orders where a validation issue on a single line is expected to be isolated from the remaining valid lines, since correctly enforced line-level isolation is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Create Multi-Line Order business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Customers, Items, Warehouses, Price Lists and Requested Dates.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant warehouse, scheduling, quantity and line-count variations.

Positive + Negative Test Variations

Valid multi-line order scenarios and edge cases such as invalid lines, duplicate items or line-count limits.

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 warehouse, scheduling, item or line-count combination, SyntraFlow maintains one core Create Multi-Line Order scenario and allows Jarvis AI to generate warehouse, scheduling, quantity and line-count-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Create Multi-Line 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 Sales Orders.

Positive Scenarios

Create a multi-line order with all lines from the same warehouse
Create a multi-line order with lines from different warehouses
Create a multi-line order with different requested dates per line
Create a multi-line order with mixed units of measure across lines
Create a multi-line order with a large number of line items

Negative Scenarios

Include one invalid line among otherwise valid lines
Enter the same item on separate lines where duplicates are disallowed
Enter an invalid quantity on one line only
Attempt to save a line without a warehouse assignment
Enter inconsistent pricing across lines on the same order
Attempt to create an order whose line count exceeds the configured limit

These are representative examples only. Negative-scenario behavior and available field combinations 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 item, warehouse, scheduling and line-count combination in a real Oracle Fusion Order Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Create Multi-Line Order scenarios relevant to the customer's actual implementation.

Standard Library Definition

Customer                ${CUSTOMER}
Item 1                  ${ITEM_1}
Item 2                  ${ITEM_2}
Item 3                  ${ITEM_3}
Quantity                ${QUANTITY}
UOM                     ${UOM}
Warehouse               ${WAREHOUSE}
Requested Date          ${REQUESTED_DATE}
Price List              ${PRICE_LIST}

DataVault

Customers
  Active customers enabled for order capture
Items
  Active, orderable catalog items
Warehouses
  Active warehouses enabled per item
Price Lists
  Price lists covering the items on the order
Requested Dates
  Valid scheduling windows per warehouse and item

Jarvis AI Generates

Scenario 01 — Same Warehouse, Three Lines
Scenario 02 — Different Warehouses per Line
Scenario 03 — Different Requested Dates per Line
Scenario 04 — Mixed UOM Across Lines
Scenario 05 — Large Line-Count Order
Scenario 06 — Invalid Line Among Valid Lines
...

Create Multi-Line Order test data can include sensitive commercial categories such as customer, pricing and warehouse information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific order dimensions remain within the customer's controlled SyntraFlow environment and access model, protected according to DataVault's data masking policies. See /datavault/ for details.

Example Test Variations

Representative examples of Create Multi-Line Order scenarios Jarvis can generate from this business scenario, spanning warehouse, scheduling, UOM and line-count 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 Multi-Line Order	Positive	Order created with three or more valid, independently entered lines	Syntra Ready
VAR-002	Same Warehouse Multi-Line Order	Positive	All lines shipped from a single, common warehouse	Syntra Ready
VAR-003	Mixed Warehouse Multi-Line Order	Positive	Lines shipped from two or more different warehouses on the same order	Syntra Ready
VAR-004	Different Requested Dates	Positive/Scheduling	Each line scheduled against its own independent requested date	Syntra Ready
VAR-005	Mixed UOM Multi-Line Order	Positive	Lines entered using different units of measure for their respective items	Syntra Ready
VAR-006	Large Line Count Order	Positive/Line Count	Order created with a large number of valid line items	Syntra Ready
VAR-007	Invalid Line Among Valid Lines	Negative	One line references invalid data while remaining lines are valid	Syntra Ready
VAR-008	Duplicate Item on Separate Lines	Negative	Same item entered on two separate lines where duplicates are disallowed	Syntra Ready
VAR-009	Invalid Quantity on One Line	Negative	A single line entered with a zero or negative quantity	Syntra Ready
VAR-010	Missing Warehouse on One Line	Negative	A single line saved without a warehouse assignment	Syntra Ready
VAR-011	Inconsistent Pricing Across Lines	Negative	Line pricing does not align with the applicable price list	Syntra Ready
VAR-012	Line Count Exceeds Configured Limit	Negative/Line Count	Order line count exceeds the customer's configured maximum	Syntra Ready

Automatically Expand Positive and Negative Multi-Line Order Coverage

Positive Testing

Jarvis generates scenarios using item, quantity, warehouse and scheduling combinations expected to successfully create every line on a multi-line sales order in Oracle Fusion.

Valid Customer + Multiple Active Items + Valid Warehouses per Line + Price List Coverage → Sales Order Created With All Lines

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around individual lines, so that a problem on one line is correctly isolated from the rest of the order.

Invalid Line Among Valid Lines → Expected Line-Level Validation, Other Lines Unaffected
Duplicate Item on Separate Lines → Expected Duplicate-Line Validation
Invalid Quantity on One Line → Expected Quantity Validation
Missing Warehouse on One Line → Expected Mandatory Field 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 sales order	Order created	PASS
Invalid customer	Customer validation occurs	PASS
Credit hold	Credit check enforced	PASS
Security restriction	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Create Multi-Line Order scenarios and group them into reusable execution packs.

SCM Order Management Create Multi-Line Order Regression Pack

Standard Multi-Line Order
Same Warehouse Multi-Line Order
Mixed Warehouse Multi-Line Order
Different Requested Dates
Mixed UOM Multi-Line Order
Large Line Count Order
Invalid Line Among Valid Lines
Duplicate Item on Separate Lines
Missing Warehouse on One Line
Line Count Exceeds Configured Limit

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

Once scheduled, SyntraFlow executes the selected Create Multi-Line 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	SCM Order Management Create Multi-Line Order 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 & Approval Variations

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

Persona	Action	Expected	Syntra Result
Order Entry Specialist	Create Multi-Line Order	Allowed	PASS
Unauthorized User	Attempts Order Creation	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 Create Multi-Line Order scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary and Line Isolation coverage — including large line-count orders and orders where a problem on one line must be correctly isolated from the rest — 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 — Create Multi-Line 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

Add Multiple Item Lines

May internally include

Open Add Line → Search Item → Enter Quantity/UOM → Select Warehouse → Set Requested Date → Add Line → Repeat for Each Line

Business Step

Review All Lines

May internally include

Open Lines Grid → Read Each Line's Item/Quantity/Warehouse/Date → Compare Against Entered 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 that every line on a multi-line order was created 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: Create Multi-Line Order failed — Likely category: DATA_ERROR — Evidence: one line references an item not covered by the applicable price list — Recommended action: verify price list coverage for all items before submission. A failure should never be labeled as an Oracle defect without supporting evidence.

Step	Action Status	Business Validation
Add Multiple Item Lines	Pass	—
Submit the Sales Order	Pass	—
Verify Order-Level and Line-Level Status	Pass	Pass

Related Sales Order Tests

Create Multi-Line Order extends the single-line Create Sales Order scenario within the Sales Orders cluster — explore the related discount and tax scenarios below.

Create Sales Order Create Order With Discount Create Order With Tax

Turn This Standard Test into Your Oracle SCM Create Multi-Line Order Regression Suite

Start with the Syntra Standard Create Multi-Line Order test, use DataVault to provide environment-specific test data, let Jarvis generate additional warehouse, scheduling and line-count variations, and execute the resulting regression pack automatically with SyntraFlow.

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

Frequently Asked Questions

How does SyntraFlow isolate a failure on one order line from the other lines?

SyntraFlow tracks a business assertion at the line level as well as the order level. When one line fails validation — for example an invalid item or missing warehouse — the evidence trail is designed to show that failure against that specific line, while the remaining valid lines are checked independently for their own correct creation and status.

Can each line on a multi-line order have its own warehouse and requested date?

Yes, where supported by the customer's Oracle Fusion Order Management configuration, individual lines on the same order can be scheduled from different warehouses and against different requested dates. This scenario is designed to confirm that line-level scheduling and warehouse assignment work independently across lines on the same order.

Is there a limit to how many lines a multi-line order can contain?

Any line-count limit depends on the customer's Oracle Fusion configuration rather than a single universal Oracle limit. Jarvis can generate a large-line-count boundary variation and a variation that exceeds a configured limit to confirm that Oracle enforces the expected behavior at the edges of what is supported.

How does security testing work for multi-line order creation?

Access to create a sales order for a given business unit 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, without asserting a single universal Oracle security model.

Does this test create real sales orders or real fulfillment in Oracle Fusion?

No. This is test automation executed against Oracle Fusion TEST/UAT environments only. It does not create real sales transactions, real fulfillment activity or real financial postings in a production environment.