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

Syntra Standard Oracle Test Library

Oracle Fusion Pick Release Test Cases

Validate that scheduled and reserved order lines can be released to the warehouse for physical picking in Oracle Fusion Order Management, that a pick wave is generated correctly against the defined criteria, and that ineligible lines are correctly excluded from release.

Test ID	ORCL.O2C.OM.FUL.PICK
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 release of scheduled and reserved order lines to the warehouse for physical picking through a generated pick wave, and to confirm that Oracle Fusion correctly determines which lines are included in, or excluded from, that release.

The scenario should confirm that:

scheduled and reserved order lines can be released to the warehouse via pick release
a pick wave is generated correctly against the defined pick release criteria, such as warehouse and ship date range
order line status updates correctly to reflect pick release
the resulting warehouse task or pick slip correctly reflects item, quantity and location
unscheduled lines, held orders and lines with insufficient reserved quantity are correctly excluded from release
duplicate release of an already-released line and access by unauthorized users are correctly prevented

This scenario assumes order lines have already been scheduled and, where required, reserved through the separate Schedule Order and Reserve Order scenarios. It covers the pick release action itself within Oracle Fusion Order Management TEST/UAT environments and does not cover the physical warehouse picking activity or the subsequent ship confirm step, which is covered by the separate Ship Confirm scenario.

When to Use This Test

Functional testing of pick release and pick wave generation for a new Oracle Fusion Order Management implementation
Regression testing of pick release criteria and exclusion logic after an Oracle quarterly update
UAT sign-off for warehouse and order management teams that routinely release single orders and batch pick waves
Validation of security restrictions around who is permitted to initiate pick release

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

Schedule Order

→

Reserve Order

→

Pick Release

→

Ship Confirm

Pick Release is the step that releases scheduled and reserved order lines into a pick wave so the warehouse team can begin physical picking. Exact criteria, wave logic and warehouse task generation depend on the customer's Oracle Fusion Warehouse Management and Order Management configuration.

Preconditions

Order lines have already been scheduled and, where required, reserved in Oracle Fusion Order Management.
Pick release criteria, such as warehouse and ship date range, are configured for the release run.
Sufficient on-hand or reserved quantity exists for the order lines expected to be released.
The user initiating pick release holds the appropriate warehouse operator or order management privileges.
The test user is signed in to an Oracle Fusion Order Management TEST/UAT environment.

Exact pick release criteria options, wave-building logic and exclusion behavior may vary by warehouse, order type, lot/serial control and customer-specific Oracle Fusion configuration.

Sample Test Data

Order Number	${ORDER_NUMBER}
Item	${ITEM}
Warehouse	${WAREHOUSE}
Pick Wave Criteria	${PICK_WAVE_CRITERIA}
Quantity	${QUANTITY}
Ship Date Range	${SHIP_DATE_RANGE}
Pick Wave Number	${PICK_WAVE_NUMBER}
Lot / Serial Number	${LOT_SERIAL_NUMBER}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion TEST/UAT environment. Warehouse configuration, reserved quantity and pick release criteria typically determine which lines are included in a given pick wave.

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 or warehouse operator 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 to initiate pick release.	The Order Management work area opens successfully.
3	Define Pick Release Criteria Define the pick release criteria for the run, such as warehouse and ship date range. ${WAREHOUSE}, ${PICK_WAVE_CRITERIA} This single business step replaces multiple technical actions such as opening the pick release form and entering each individual criterion field.	The pick release criteria are accepted and ready for submission.
4	Initiate Pick Release Submit the pick release run against the defined criteria.	Oracle Fusion begins processing the pick release request.
5	Review the Generated Pick Wave Open the resulting pick wave and review the lines it contains.	A pick wave is generated and available for review.
6	Verify Included and Excluded Lines Match Expectations Compare the lines included in the pick wave against the order lines expected to qualify, and confirm unscheduled or held lines are absent. Confirming inclusion and exclusion before final release helps distinguish a criteria or eligibility issue from a release-processing issue if the test later fails.	Only eligible order lines are included in the pick wave; unscheduled, held or insufficiently reserved lines are correctly excluded.
7	Confirm Release Confirm the pick wave for release to the warehouse.	Oracle Fusion accepts the release without unexpected errors.
8	Verify Line Status Updated to Released for PickingBusiness assertion Reopen or refresh the order lines and the warehouse task or pick slip to review status. This is the primary business assertion for the scenario — a correct status transition and an accurate warehouse task are the expected pass condition, not merely an accepted release.	Released order lines correctly update to a released-for-picking status, and the warehouse task or pick slip reflects the expected item, quantity and location.

Expected Results

Scheduled and reserved order lines are released successfully to the warehouse via pick release.
The pick wave is generated correctly against the defined pick release criteria.
Order line status updates correctly to reflect pick release.
The warehouse task or pick slip correctly reflects item, quantity and location.
Unscheduled lines, held orders and insufficiently reserved lines are correctly excluded from release.
Duplicate release of an already-released line and access by unauthorized users are correctly prevented.

Key Validation Checkpoints

The pick wave is correctly generated with the expected lines.
Line status updates to reflect pick release.
The warehouse task or pick slip correctly reflects item, quantity and location.
Unscheduled or held lines are correctly excluded from release.

Core Business Scenario

Pick Release

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 Pick Release business scenario. Jarvis AI can extend this scenario by generating additional batch, exclusion and security variations using customer-specific test data available through Syntra DataVault.

Teams do not need to manually build a separate test for every warehouse, criteria combination or exclusion condition. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative, Batch and Exclusion variations for the customer's environment — with exclusion coverage weighted especially heavily, since correctly withholding unscheduled, held or under-reserved lines is central to what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Pick Release business process and automation logic.

Customer DataVault

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

Jarvis AI

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

Positive + Negative Test Variations

Valid release scenarios and edge cases such as unscheduled lines, held orders or insufficient reserved quantity.

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 warehouse, criteria combination or exclusion scenario, SyntraFlow maintains one core Pick Release scenario and allows Jarvis AI to generate batch-driven, exclusion-driven and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Pick Release 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

Release a single order to a pick wave
Release a multi-order batch by pick release criteria
Release order lines requiring lot or serial allocation
Release a partial line quantity where supported
Release a pick wave spanning multiple warehouses processed separately

Negative Scenarios

Attempt pick release on an unscheduled order line
Attempt pick release on a held order
Attempt release with insufficient reserved quantity at release time
Attempt release using invalid pick release criteria
Attempt pick release by an unauthorized user
Attempt duplicate pick release of an already-released line

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

Generated Using Your DataVault Test Data

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

Standard Library Definition

Order Number         ${ORDER_NUMBER}
Item                  ${ITEM}
Warehouse             ${WAREHOUSE}
Pick Wave Criteria    ${PICK_WAVE_CRITERIA}
Quantity              ${QUANTITY}
Ship Date Range       ${SHIP_DATE_RANGE}
Pick Wave Number      ${PICK_WAVE_NUMBER}
Lot / Serial Number   ${LOT_SERIAL_NUMBER}

DataVault

Sales Orders
  Scheduled and reserved order lines eligible for release
Warehouses
  Active warehouses and subinventories
Items
  Active sellable items with lot/serial control flags
Reservations
  Reserved quantity per order line
Pick Release Criteria
  Configured warehouse and ship date defaults
Users
  Active warehouse operators with pick release privileges

Jarvis AI Generates

Scenario 01 — Standard Single-Order Pick Release
Scenario 02 — Multi-Order Batch Pick Release
Scenario 03 — Pick Release with Lot/Serial Allocation
Scenario 04 — Pick Release Attempted on Unscheduled Line
Scenario 05 — Pick Release Attempted on Held Order
Scenario 06 — Unauthorized User Attempts Pick Release
...

Pick Release test data can include operational detail such as warehouse, item and order information. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific warehouse and 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 Pick Release scenarios Jarvis can generate from this business scenario, spanning batch and exclusion 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	Single-Order Pick Release	Positive	One order released to a pick wave successfully	Syntra Ready
VAR-002	Multi-Order Batch Release	Positive/Batch	Multiple qualifying orders released by criteria in one run	Syntra Ready
VAR-003	Lot/Serial Allocation Release	Positive	Pick wave includes lot or serial allocation detail	Syntra Ready
VAR-004	Partial Line Quantity Release	Positive	Only a partial line quantity is released where supported	Syntra Ready
VAR-005	Multi-Warehouse Pick Wave	Positive/Batch	Lines spanning multiple warehouses processed as separate waves	Syntra Ready
VAR-006	Unscheduled Line Release Attempt	Negative/Exclusion	Release blocked because the line has not been scheduled	Syntra Ready
VAR-007	Held Order Release Attempt	Negative/Exclusion	Release blocked while the order is on hold	Syntra Ready
VAR-008	Insufficient Reserved Quantity	Negative/Exclusion	Release blocked due to insufficient reserved quantity at release time	Syntra Ready
VAR-009	Invalid Pick Release Criteria	Negative	Release blocked or errors due to invalid criteria entry	Syntra Ready
VAR-010	Unauthorized Pick Release Attempt	Negative	Release attempt blocked for a user without pick release privileges	Syntra Ready
VAR-011	Duplicate Pick Release	Negative/Exclusion	A second release attempt on an already-released line is rejected	Syntra Ready
VAR-012	Exclusion Verification Across a Batch	Batch/Exclusion	Batch run correctly excludes unscheduled and held lines while including eligible ones	Syntra Ready

Automatically Expand Positive and Negative Pick Release Coverage

Positive Testing

Jarvis generates scenarios using orders, warehouses and lines expected to release successfully into a pick wave within Oracle Fusion Order Management.

Scheduled and Reserved Line + Valid Criteria → Pick Wave Generated and Line Released

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around scheduling status, holds, reserved quantity, criteria and security.

Unscheduled Line → Expected Eligibility Validation
Held Order → Expected Hold Enforcement
Insufficient Reserved Quantity → Expected Availability Validation
Invalid Pick Release Criteria → Expected Criteria 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 Pick Release scenarios and group them into reusable execution packs.

Order Management Pick Release Regression Pack

Single-Order Pick Release
Multi-Order Batch Release
Lot/Serial Allocation Release
Partial Line Quantity Release
Multi-Warehouse Pick Wave
Unscheduled Line Release Attempt
Held Order Release Attempt
Insufficient Reserved Quantity
Invalid Pick Release Criteria
Duplicate Pick Release

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

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

Persona	Action	Expected	Syntra Result
Warehouse Operator	Pick Release	Allowed	PASS
Unauthorized User	Attempts Pick Release	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 Pick Release scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Batch and Exclusion 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 — Pick Release, 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

Define Pick Release Criteria

May internally include

Open Pick Release Form → Select Warehouse → Enter Ship Date Range → Enter Additional Criteria → Confirm

Business Step

Verify Line Status Updated to Released for Picking

May internally include

Refresh Order Lines → Read Line Status → Open Pick Slip → Compare Item, Quantity and Location Against Expected

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 correct lines were released or the pick slip was accurate — 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 Pick Release	Pass	—
Verify Line Status Updated to Released for Picking	Pass	Pass
Verify Pick Slip Reflects Item, Quantity and Location	Pass	Pass

Related Fulfillment Tests

Pick Release sits between reservation and ship confirm in the Fulfillment scenario family — released lines move on to physical picking and shipment. Explore the related fulfillment scenarios below.

Reserve Order Ship Confirm Fulfillment Exceptions

Turn This Standard Test into Your Oracle Order Management Pick Release Regression Suite

Start with the Syntra Standard Pick Release test, use DataVault to provide environment-specific test data, let Jarvis generate additional batch, exclusion 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 do pick release criteria work?

Pick release criteria, such as warehouse, ship date range and order type, determine which scheduled and reserved order lines are eligible to be pulled into a pick wave. Only lines matching the defined criteria and meeting reservation requirements are included when the release is submitted.

What is the difference between a single-order and a batch pick release?

A single-order pick release targets one specific order, while a batch pick release applies the defined criteria across multiple qualifying orders at once, grouping their eligible lines into one or more pick waves for the warehouse team to work from.

What gets excluded from a pick release, and why?

Lines that have not been scheduled, orders that are on hold, and lines without sufficient reserved quantity at the time of release are expected to be excluded. This test's negative variations exercise these conditions as expected pass outcomes, confirming Oracle correctly withholds ineligible lines rather than releasing them in error.

How is security tested for pick release?

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