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

Syntra Standard Oracle Test Library

Oracle Fusion Ship Confirm Test Cases

Validate that Oracle Fusion Order Management correctly confirms physical shipment for picked order lines, decrements on-hand inventory, updates order and line status, and makes the resulting shipment eligible for downstream AR Billing.

Test ID	ORCL.O2C.OM.FUL.SHIP
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 17 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate that Order Management correctly confirms the physical shipment of order lines that have already been picked and staged, and that the resulting shipment record accurately updates inventory and downstream billing eligibility.

The scenario should confirm that:

a picked and staged order line can be ship confirmed successfully
on-hand inventory is decremented correctly once the shipment is confirmed
the order line and order status update correctly to reflect shipment
the confirmed shipment is correctly flagged as eligible for downstream AR Billing
Oracle's validations correctly block ship confirm attempts against unpicked, held or already-shipped lines
ship confirm behavior is consistent across different ship methods and carriers

This scenario assumes order lines have already been picked via the separate Pick Release scenario and covers only the ship confirm action itself. It does not create a real physical shipment or a real financial transaction — this is test automation of Oracle Fusion Order Management, not an actual carrier pickup or AR invoice posting. Downstream AR Billing behavior is covered separately by the Accounts Receivable test library.

When to Use This Test

Functional testing of ship confirm processing for a new Oracle Fusion Order Management implementation
Regression testing of shipment confirmation and inventory decrement behavior after an Oracle quarterly update
UAT sign-off for warehouse and shipping teams that routinely confirm single-line, multi-line and partial shipments
Validation step referenced by the pick-release and fulfillment-exceptions scenarios within the broader Order-to-Cash flow

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

Schedule Order

→

Pick Release

→

Ship Confirm

→

Fulfillment Exceptions

Ship Confirm is the step that records the physical shipment of picked order lines in Oracle Fusion Order Management, decrementing inventory and making the shipment eligible for downstream Accounts Receivable billing. Exact downstream behavior depends on order type, item setup and customer configuration.

← Previous Stage

Pick Release

Next Stage →

Fulfillment Exceptions

Preconditions

Order lines have been picked and are staged for shipment via the Pick Release process.
A valid shipping method and carrier are configured for the order.
Packing and shipment documentation requirements have been met.
The user confirming the shipment holds the appropriate ship confirm privileges.
The test user is signed in to an Oracle Fusion Order Management TEST/UAT environment.

Exact ship confirm eligibility, inventory decrement timing and validation messages may vary by warehouse, item, shipping method and customer-specific Oracle Fusion configuration.

Sample Test Data

Order Number	${ORDER_NUMBER}
Item	${ITEM}
Picked Quantity	${PICKED_QUANTITY}
Ship Quantity	${QUANTITY}
Warehouse	${WAREHOUSE}
Ship Method	${SHIP_METHOD}
Carrier	${CARRIER}
Ship Date	${SHIP_DATE}
Tracking Number	${TRACKING_NUMBER}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Picked quantity, warehouse and carrier setup typically determine whether a given ship confirm attempt succeeds.

Test Steps

8 business-readable steps. SyntraFlow's automation executes ~17 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 used for ship confirm processing.	The Order Management work area opens successfully.
3	Locate the Picked Shipment Search for and open the shipment associated with the picked order lines to be confirmed. ${ORDER_NUMBER} This single business step replaces multiple technical actions such as opening shipment search, entering search criteria and selecting the result.	The correct picked shipment opens for review.
4	Review Lines and Quantities to Confirm Review the shipment lines and quantities to confirm they match what was picked. Confirming quantities before ship confirm helps distinguish a data-completeness issue from a ship confirm or configuration issue if the test later fails.	Lines and quantities are correct and ready for ship confirm.
5	Select Ship Method, Carrier and Capture Tracking Select the ship method and carrier for the shipment and capture the tracking number where applicable. ${SHIP_METHOD} / ${CARRIER} / ${TRACKING_NUMBER}	The ship method, carrier and tracking number are recorded on the shipment.
6	Confirm Shipment Select the option to confirm the shipment.	Oracle Fusion accepts the ship confirm action without unexpected errors.
7	Verify Inventory Decremented Review on-hand inventory for the shipped item and warehouse.	On-hand inventory is decremented correctly to reflect the confirmed shipment.
8	Verify Order Status Updated and Eligible for BillingBusiness assertion Reopen or refresh the order and review its status and downstream billing eligibility. This is the primary business assertion for the scenario — a correct status transition and billing eligibility are the expected pass condition, not merely an accepted ship confirm action.	The order line and order status update correctly to shipped, and the shipment becomes correctly flagged as eligible for downstream AR Billing.

Expected Results

The shipment is confirmed successfully once picked order lines are reviewed and a valid ship method and carrier are selected.
On-hand inventory is decremented correctly to reflect the confirmed shipment.
The order line and order status update correctly to shipped.
The confirmed shipment is correctly flagged as eligible for downstream AR Billing.
Ship confirm attempts against unpicked, held or already-shipped lines are correctly blocked.
Ship confirm history and audit trail are recorded for traceability.

Key Validation Checkpoints

The shipment is recorded accurately against the picked line.
On-hand inventory is correctly decremented.
The line and order status update to shipped.
The shipment is correctly flagged as eligible for downstream billing.

Core Business Scenario

Ship Confirm

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 Ship Confirm business scenario. Jarvis AI can extend this scenario by generating additional quantity, carrier, exception and security variations using customer-specific test data available through Syntra DataVault.

Teams do not need to manually build a separate test for every ship method, carrier or exception combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Quantity and Carrier variations for the customer's environment — with inventory and billing-eligibility coverage weighted especially heavily, since correctly decrementing inventory and flagging the shipment for billing is the core of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Ship Confirm business process and automation logic.

Customer DataVault

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

Jarvis AI

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

Positive + Negative Test Variations

Valid ship confirm scenarios and edge cases such as unpicked lines, held orders or unauthorized attempts.

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 ship method, carrier or exception condition, SyntraFlow maintains one core Ship Confirm scenario and allows Jarvis AI to generate quantity-driven, carrier-driven and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Ship Confirm 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 full-line ship confirm
Partial-quantity ship confirm where supported
Multiple lines confirmed together
Ship confirm using different ship methods and carriers
Ship confirm with tracking number captured
Ship confirm that correctly triggers downstream billing eligibility

Negative Scenarios

Attempt ship confirm on an unpicked line
Attempt ship confirm with a quantity exceeding the picked quantity
Attempt ship confirm on a held order
Attempt ship confirm with an invalid carrier or ship method
Attempt ship confirm by an unauthorized user
Attempt duplicate ship confirm on an already-shipped line
Attempt ship confirm with missing required shipment documentation

These are representative examples only. Negative-scenario behavior and available ship confirm 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 item, warehouse, carrier and shipping-method combination in a real Oracle Fusion Order Management environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Ship Confirm scenarios relevant to the customer's actual implementation.

Standard Library Definition

Order Number         ${ORDER_NUMBER}
Item                  ${ITEM}
Picked Quantity       ${PICKED_QUANTITY}
Ship Quantity         ${QUANTITY}
Warehouse             ${WAREHOUSE}
Ship Method           ${SHIP_METHOD}
Carrier               ${CARRIER}
Ship Date             ${SHIP_DATE}
Tracking Number       ${TRACKING_NUMBER}

DataVault

Picked Shipments
  Order lines picked and staged for shipment
Warehouses
  Active warehouses and shipping locations
Carriers
  Configured ship methods and carrier accounts
Items
  Active sellable items and catalog
Documentation Rules
  Required packing and shipment documentation
Users
  Active warehouse users with ship confirm privileges

Jarvis AI Generates

Scenario 01 — Standard Full-Line Ship Confirm
Scenario 02 — Partial-Quantity Ship Confirm
Scenario 03 — Multi-Line Ship Confirm
Scenario 04 — Ship Confirm Exceeding Picked Quantity
Scenario 05 — Ship Confirm on Held Order
Scenario 06 — Unauthorized User Attempts Ship Confirm
...

Ship Confirm test data can include sensitive commercial information such as carrier, warehouse and shipment detail. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific shipment 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 Ship Confirm scenarios Jarvis can generate from this business scenario, spanning quantity and carrier 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 Full-Line Ship Confirm	Positive	Full picked quantity confirmed and shipment recorded	Syntra Ready
VAR-002	Partial-Quantity Ship Confirm	Positive/Quantity	Less than the full picked quantity confirmed where supported	Syntra Ready
VAR-003	Multi-Line Ship Confirm	Positive	Multiple order lines confirmed together in one shipment	Syntra Ready
VAR-004	Alternate Ship Method and Carrier	Positive/Carrier	Ship confirm completed using a different ship method and carrier	Syntra Ready
VAR-005	Ship Confirm with Tracking Captured	Positive/Carrier	Tracking number captured and recorded on the shipment	Syntra Ready
VAR-006	Billing-Eligible Ship Confirm	Positive	Confirmed shipment correctly flagged eligible for downstream billing	Syntra Ready
VAR-007	Unpicked Line Ship Confirm Attempt	Negative	Ship confirm blocked because the line has not been picked	Syntra Ready
VAR-008	Quantity Exceeds Picked Quantity	Negative/Quantity	Ship confirm blocked because the entered quantity exceeds the picked quantity	Syntra Ready
VAR-009	Held Order Ship Confirm Attempt	Negative	Ship confirm blocked while the order is on hold	Syntra Ready
VAR-010	Invalid Carrier or Ship Method	Negative/Carrier	Ship confirm blocked due to an invalid carrier or ship method	Syntra Ready
VAR-011	Unauthorized Ship Confirm Attempt	Negative	Ship confirm attempt blocked for a user without ship confirm privileges	Syntra Ready
VAR-012	Duplicate Ship Confirm	Negative	A second ship confirm attempt on an already-shipped line is rejected	Syntra Ready
VAR-013	Missing Shipment Documentation	Negative	Ship confirm blocked when required shipment documentation is missing	Syntra Ready

Automatically Expand Positive and Negative Ship Confirm Coverage

Positive Testing

Jarvis generates scenarios using picked lines, ship methods and carriers expected to confirm successfully within Oracle Fusion Order Management.

Picked Line + Valid Carrier + Complete Documentation → Shipment Confirmed and Inventory Decremented

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around pick status, quantity, order holds, carrier setup, duplicate shipment and security.

Unpicked Line → Expected Pick-Status Validation
Quantity Exceeds Picked Quantity → Expected Quantity Validation
Held Order → Expected Hold Validation
Invalid Carrier or Ship Method → Expected Carrier Validation
Duplicate Ship Confirm → 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 Ship Confirm scenarios and group them into reusable execution packs.

Order Management Ship Confirm Regression Pack

Standard Full-Line Ship Confirm
Partial-Quantity Ship Confirm
Multi-Line Ship Confirm
Alternate Ship Method and Carrier
Ship Confirm with Tracking Captured
Billing-Eligible Ship Confirm
Unpicked Line Ship Confirm Attempt
Quantity Exceeds Picked Quantity
Held Order Ship Confirm Attempt
Unauthorized Ship Confirm 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 Ship Confirm scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected Ship Confirm 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 Ship Confirm 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 confirm a shipment is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that ship confirm access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Warehouse Operator	Ship Confirm	Allowed	PASS
Unauthorized User	Attempts Ship Confirm	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 Ship Confirm scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Quantity and Carrier 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 — Ship Confirm, 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 Picked Shipment

May internally include

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

Business Step

Verify Inventory Decremented

May internally include

Navigate to Item Inventory Inquiry → Enter Item and Warehouse → Read On-Hand Quantity → Compare Against Expected Post-Shipment Balance

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 inventory was decremented or the shipment was made billing-eligible 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
Confirm the Shipment	Pass	—
Verify Inventory Decremented	Pass	Pass
Verify Order Status and Billing Eligibility	Pass	Pass

Related Fulfillment Tests

Ship Confirm follows Pick Release in the Fulfillment scenario family and feeds downstream Accounts Receivable billing. Explore the related picking, exception-handling and receipt scenarios below.

Pick Release Fulfillment Exceptions Create Standard Receipt

Turn This Standard Test into Your Oracle Order Management Ship Confirm Regression Suite

Start with the Syntra Standard Ship Confirm test, use DataVault to provide environment-specific test data, let Jarvis generate additional quantity, carrier 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

What happens to inventory when a shipment is ship confirmed?

Ship confirm decrements on-hand inventory for the shipped item and warehouse to reflect that the goods have physically left the facility. This test validates that the inventory update is correct; it does not move real physical inventory itself.

How does Ship Confirm relate to AR Billing?

Confirming a shipment makes the order line eligible for Oracle Fusion's downstream Accounts Receivable billing process. This test validates that eligibility flag; it does not create a real invoice or any real financial transaction — that is covered separately by the Accounts Receivable test library, for example Create Standard Receipt.

How is a partial shipment handled?

Where Oracle Fusion order configuration supports it, a line can be ship confirmed for less than the full picked quantity, leaving the remaining quantity available for a later shipment. This scenario's positive variations include a partial-quantity ship confirm where supported.

How is security tested for ship confirm?

Jarvis can generate persona-based variations, such as an authorized warehouse operator compared with an unauthorized user, to confirm that ship confirm 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, quantity and carrier variations of Ship Confirm from this single canonical scenario definition rather than maintaining a separate indexable page for each combination.