Oracle ERP Testing Tool > Test Library > SCM > Supply Planning

Syntra Standard Oracle Test Library

Oracle Fusion Release Planned Order Test Cases

Validate that planned orders can be released into their downstream execution documents in Oracle Fusion SCM Supply Planning — work orders for make orders, purchase requisitions for buy orders and transfer orders for transfer orders — including individual and batch release, firmed order release and negative/security release testing, without assuming every planned order releases automatically without review.

Test ID	ORCL.SCM.PLAN.RELEASE
Application	Oracle Fusion Cloud
Product	SCM
Module	Supply Planning
Process	Release Planned Order
Business Flow	Plan-to-Produce
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 6 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 release of planned orders into their downstream execution documents — work orders (make), purchase requisitions (buy) or transfer orders (transfer) — across Oracle Fusion SCM Supply Planning, including individual and batch release, without assuming every planned order releases automatically without review.

The scenario should confirm that:

the planned order correctly releases to the matching downstream document type — work order, purchase requisition or transfer order
firmed status is correctly required before release where configured
batch release correctly processes multiple eligible planned orders together
the resulting downstream document correctly reflects the planned order's quantity, date and supply source
duplicate and unauthorized release attempts are correctly blocked
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 release of planned orders as configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It orchestrates release of the resulting work order into the existing Manufacturing test coverage and the resulting purchase requisition into Procurement, but does not duplicate the detailed downstream scenario coverage for those documents — see the Create Work Order scenario in the Manufacturing test library and the corresponding purchase requisition creation scenario in the Procurement test library for that detailed coverage.

When to Use This Test

Functional testing of planned order release for a new Oracle Fusion SCM Supply Planning implementation
Regression testing of release behavior after an Oracle quarterly update
UAT sign-off for supply planners and buyers who release make, buy and transfer planned orders
Baseline case that hands off to the existing Create Work Order (Manufacturing) and purchase requisition (Procurement) scenarios rather than duplicating their coverage
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and SECURITY_ERROR conditions surfaced during release before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Supply Planning Process

Planned Orders

→

Review Planned Order

→

Release Planned Order

→

Downstream Document Created

→

Manufacturing / Procurement Execution

Release Planned Order is the action step of the Supply Planning scenario family and of the Plan-to-Produce business flow, converting a reviewed planned order into its downstream execution document. Before a planned order can be released, it must first be generated and reviewed — covered by the Planned Orders scenario. After release, the resulting work order, purchase requisition or transfer order is executed through the existing Manufacturing and Procurement test coverage — this scenario orchestrates release into those scenarios rather than duplicating them. Exact release behavior, firming requirements and downstream document creation depend on the plan configuration and customer-specific Oracle Fusion setup.

Preconditions

The test user has appropriate Supply Planner, Planning Manager or Buyer access to release planned orders.
One or more eligible planned orders of type make, buy or transfer exist and are available for release in the target Oracle Fusion environment.
Work definitions, supplier and transfer routing configuration required for downstream document creation are configured and active.
Firm/unfirm release rules and other release-specific configuration referenced in test data are configured and active.
The organization(s) included in the release scope are configured to allow planned order release.

Exact release behavior, firming requirements and downstream document creation may vary by Oracle Fusion implementation, plan configuration and customer-specific setup. No single planned order should be assumed to release automatically without review.

Sample Test Data

Planned Order	${PLANNED_ORDER}
Order Type	${ORDER_TYPE}
Work Order	${WORK_ORDER}
Purchase Requisition	${PURCHASE_REQUISITION}
Transfer Order	${TRANSFER_ORDER}
Organization	${ORGANIZATION}
Order Quantity	${ORDER_QUANTITY}
User Role	${USER_ROLE}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Not every field applies to every release type — for example, ${TRANSFER_ORDER} does not apply when releasing a make planned order to a work order.

Test Steps

6 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 and Navigate to the Planned Orders Workbench Sign in to Oracle Fusion using an authorised Supply Planning test user and navigate to the planned orders workbench. ${PLANNED_ORDER}	The planned orders workbench opens and the target planned order is available for selection.
2	Select the Planned Order or Orders to Release Select the planned order, or multiple planned orders for batch release, to be released. ${PLANNED_ORDER} / ${ORDER_TYPE}	The selected planned order(s) are correctly highlighted for release.
3	Review Order Type and Quantity/Date Review the planned order's type, quantity and suggested date, modifying quantity or date if required before release. ${ORDER_QUANTITY} Reviewing the order before release lets the tester catch an incorrect quantity or date, since not every planned order should be assumed to release automatically without review.	The reviewed order type, quantity and date are accepted and reflected on the release request.
4	Submit the Release Action Submit the release action for the selected planned order or orders. ${ORGANIZATION}	Oracle Fusion accepts the release request without unexpected errors.
5	Monitor Release Processing Monitor the release action until it completes and a downstream document reference becomes available.	The release correctly completes and a downstream document reference is returned for each released planned order.
6	Verify the Corresponding Downstream Document Is Created CorrectlyBusiness assertion Open the corresponding downstream document — work order, purchase requisition or transfer order — and confirm it reflects the planned order's type, quantity, date and source. ${WORK_ORDER} / ${PURCHASE_REQUISITION} / ${TRANSFER_ORDER} This is the primary business assertion for the scenario — a correctly created downstream document is the expected pass condition, not merely a completed release status.	The downstream document is correctly created and reflects the planned order's type, quantity, date and source.

Expected Results

The planned order correctly releases to the matching downstream document type — work order, purchase requisition or transfer order.
Firmed status is correctly required before release where configured.
Batch release correctly processes multiple eligible planned orders together.
Duplicate release of an already-released planned order is correctly blocked.
Release of an unfirmed order is correctly blocked where not permitted by configuration.
Unauthorized release is correctly blocked.

Key Validation Checkpoints

Planned order correctly releases to the matching downstream document type.
Firmed status correctly required where configured.
Batch release correctly processes multiple eligible orders together.
Duplicate release correctly blocked.
Unfirmed release correctly blocked where not permitted.
Unauthorized release correctly blocked.

Core Business Scenario

Release Planned 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 Release Planned Order business scenario. Jarvis AI can extend this scenario by generating additional release-type, firming, quantity, date and security variations using customer-specific test data and configuration available through Syntra DataVault.

Teams do not need to manually build a separate test for every planned order type or release combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including duplicate and unauthorized release attempts, since correctly enforced validation and access control is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

SCM

Oracle Fusion SCM product family within the Syntra Standard Test Library.

Supply Planning (Functional Area)

The Supply Planning functional area containing the Release Planned Order scenario family.

Release Planned Order (Process / Scenario Family)

Reusable Release Planned Order business process and automation logic.

Standard Test Scenarios

14 individual Syntra Standard scenarios covering make/buy/transfer release, single and batch release, and negative/security release testing.

DataVault Test Data

Provides approved customer-specific test data and configuration required for scenario generation — Planned Orders, Organizations, Order Types and Downstream Documents.

Jarvis Variations

Analyses the standard scenario together with available test data and generates relevant release-type, scope and security variations.

Regression Pack

Selected variations can be grouped into an executable suite.

Scheduled Execution

Execute immediately or schedule the regression pack for unattended batch execution.

Failure Intelligence

Capture execution results, business assertions, screenshots/evidence and exceptions, classified into failure categories such as DATA_ERROR, CONFIGURATION_ERROR and EXPECTED_VALIDATION.

Rather than maintaining a separate test page for every possible release type, firming state, quantity or date combination, SyntraFlow maintains one core Release Planned Order scenario and allows Jarvis AI to generate release- and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Release Planned 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 Supply Planning.

Positive Scenarios

Release make planned orders to work orders
Release buy planned orders to purchase requisitions
Release transfer planned orders to transfer orders
Release firmed planned orders where firming is required
Release planned orders with modified quantity or date
Release a single planned order and release across organizations
Batch release multiple eligible planned orders and verify downstream document creation

Negative Scenarios

Attempt to release an unfirmed planned order where firming is required and not permitted
Attempt to release a planned order with an invalid or incompatible supply source
Attempt to release a planned order that has already been released
Attempt unauthorized planned order release without the required access

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

Generated Using Your DataVault Test Data

Generic test data rarely represents every planned order type, organization and downstream document combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Release Planned Order scenarios relevant to the customer's actual implementation.

Standard Library Definition

Planned Order          ${PLANNED_ORDER}
Order Type              ${ORDER_TYPE}
Work Order              ${WORK_ORDER}
Purchase Requisition    ${PURCHASE_REQUISITION}
Transfer Order          ${TRANSFER_ORDER}
Organization            ${ORGANIZATION}
Order Quantity          ${ORDER_QUANTITY}
User Role               ${USER_ROLE}

DataVault

Planned Orders
  Configured planned orders and their order types
Organizations
  Organizations enabled for planned order release
Work Definitions
  Configuration required for work order creation
Suppliers
  Configuration required for purchase requisition creation
Transfer Routes
  Configuration required for transfer order creation
User Roles
  Roles enabled for planned order release

Jarvis AI Generates

Scenario 01 — Release Make Planned Order to Work Order
Scenario 02 — Release Buy Planned Order to Purchase Requisition
Scenario 03 — Release Transfer Planned Order to Transfer Order
Scenario 04 — Batch Release Multiple Planned Orders
Scenario 05 — Release Unfirmed Order Where Not Permitted
Scenario 06 — Unauthorized User Attempts Planned Order Release
...

Release Planned Order test data can include planned order, organization and downstream document configuration tied to supply chain planning. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific planned order data used in testing remain masked and synthetic within the customer's controlled SyntraFlow environment, protected according to DataVault's data masking policies. See /datavault/data-masking/ for details.

Example Test Variations

Representative examples of 14 individual Release Planned Order test scenarios spanning make/buy/transfer release to downstream documents, single and batch release and negative/security release testing that Jarvis can generate from this business scenario. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
PLAN-REL-001	Release Make Planned Order to Work Order	Positive	Planned order ${PLANNED_ORDER} of type make is released to create work order ${WORK_ORDER}.	SyntraFlow Ready
PLAN-REL-002	Release Buy Planned Order to Purchase Requisition	Positive	Planned order ${PLANNED_ORDER} of type buy is released to create purchase requisition ${PURCHASE_REQUISITION}.	SyntraFlow Ready
PLAN-REL-003	Release Transfer Planned Order to Transfer Order	Positive	Planned order ${PLANNED_ORDER} of type transfer is released to create transfer order ${TRANSFER_ORDER}.	SyntraFlow Ready
PLAN-REL-004	Release Firmed Planned Order	Positive	A firmed planned order ${PLANNED_ORDER} is released to its corresponding downstream document.	SyntraFlow Ready
PLAN-REL-005	Release Order with Modified Quantity	Positive	Planned order ${PLANNED_ORDER} is released after its quantity is modified to ${ORDER_QUANTITY}.	SyntraFlow Ready
PLAN-REL-006	Release Order with Modified Date	Positive	Planned order ${PLANNED_ORDER} is released after its suggested date is modified prior to release.	SyntraFlow Ready
PLAN-REL-007	Release Single Planned Order	Positive	A single planned order ${PLANNED_ORDER} is released individually rather than as part of a batch.	SyntraFlow Ready
PLAN-REL-008	Release Order Across Organizations	Positive	Planned order ${PLANNED_ORDER} is released for organization ${ORGANIZATION}, creating a downstream document in the correct destination organization.	SyntraFlow Ready
PLAN-REL-009	Batch Release Multiple Planned Orders	Positive	Multiple eligible planned orders including ${PLANNED_ORDER} are released together in a single batch release action.	SyntraFlow Ready
PLAN-REL-010	Verify Downstream Document Created	Positive	After releasing planned order ${PLANNED_ORDER}, the resulting downstream document is verified as correctly created.	SyntraFlow Ready
PLAN-REL-011	Release Unfirmed Order Where Not Permitted	Negative	Release of unfirmed planned order ${PLANNED_ORDER} is attempted where configuration does not permit release of unfirmed orders.	SyntraFlow Ready
PLAN-REL-012	Release Order with Invalid Source	Negative	Release of planned order ${PLANNED_ORDER} is attempted where the order type ${ORDER_TYPE} or supply source is invalid.	SyntraFlow Ready
PLAN-REL-013	Duplicate Release Attempt	Negative	A duplicate release of already-released planned order ${PLANNED_ORDER} is attempted.	SyntraFlow Ready
PLAN-REL-014	Unauthorized Release	Negative/Security	A user with role ${USER_ROLE} without release access attempts to release planned order ${PLANNED_ORDER}.	SyntraFlow Ready

Automatically Expand Positive and Negative Release Coverage

Positive Testing

Jarvis generates scenarios using release type, firming, quantity, date and scope combinations expected to successfully release a planned order to its downstream document in Oracle Fusion.

Eligible Planned Order + Valid Order Type + Required Firming Met → Downstream Document Created

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around firming, supply source, duplicate release and security.

Unfirmed Order Where Firming Required → Expected Validation
Invalid Supply Source → Expected Validation
Duplicate Release Attempt → Expected Validation or Block
Unauthorized User → Expected Access Restriction

A negative supply planning scenario passes when Oracle correctly enforces the expected data, configuration or security rule

Scenario	Oracle Outcome	Test Result
Valid planning data	Plan generated	PASS
Missing or stale collected data	Validation or warning occurs	PASS
Invalid plan configuration	Validation occurs	PASS
Unauthorized user	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

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

SCM Supply Planning Release Planned Order Regression Pack

Release Make Planned Order to Work Order
Release Buy Planned Order to Purchase Requisition
Release Transfer Planned Order to Transfer Order
Release Firmed Planned Order
Release Order with Modified Quantity
Release Order Across Organizations
Batch Release Multiple Planned Orders
Verify Downstream Document Created
Release Unfirmed Order Where Not Permitted
Security Restriction — Unauthorized 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 Release Planned Order scenarios individually or as a batch. Users can schedule regression packs according to their testing cycle.

Once scheduled, SyntraFlow executes the selected Release Planned 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 Supply Planning Release Planned Order Regression Pack
Schedule	Quarterly Update Regression
Tests	14 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 release planned orders is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that release access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Planning Analyst	Release Single Planned Order	Allowed	PASS
Planning Manager	Batch Release Planned Orders	Allowed	PASS
Unauthorized User	Attempts to Release Planned Order	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 Release Planned Order scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative and Security 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 — Release Planned Order, 6 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative + Security 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 Planned Order or Orders to Release

May internally include

Open Planned Orders Workbench → Filter by Organization → Select Row(s) → Apply Multi-Select for Batch → Confirm Selection

Business Step

Verify the Corresponding Downstream Document Is Created Correctly

May internally include

Open Downstream Document → Search by Reference → Compare Quantity/Date/Source → Confirm Document Status → Record Evidence

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 planned order released 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: Planned Order Release Failed — Likely category: EXPECTED_VALIDATION — Evidence: Planned order ${PLANNED_ORDER} is not firmed and firming is required before release — Recommendation: Firm the planned order before attempting release. A failure should never be labeled as an Oracle defect without eliminating data, configuration, security, automation and integration causes first.

Step	Action Status	Business Validation
Select the Planned Order or Orders to Release	Pass	—
Submit the Release Action	Pass	—
Verify the Corresponding Downstream Document Is Created Correctly	Pass	Pass

Related Supply Planning Tests

Release Planned Order orchestrates release into the existing Manufacturing and Procurement test scenarios rather than duplicating their coverage — explore the related planning and downstream scenarios below.

Planned Orders Create Work Order Planning Exceptions

Turn This Standard Test into Your Oracle SCM Release Planned Order Regression Suite

Start with the Syntra Standard Release Planned Order test, use DataVault to provide environment-specific test data, let Jarvis generate additional release-type, firming and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore SCM Supply Planning 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 Supply Planning Test Library Create Work Order (Manufacturing)Syntra DataVault DataVault Data Masking

Frequently Asked Questions

Is firming always required before a planned order can be released?

No. Whether a planned order must be firmed before release depends on Oracle Fusion Supply Planning configuration and customer setup. This scenario is designed to validate release behavior as configured in the target environment rather than assuming firming is universally required.

What is the difference between single and batch release?

Single release submits one planned order — such as ${PLANNED_ORDER} — for release individually, while batch release selects and submits multiple eligible planned orders together in a single release action. This scenario validates both paths, since customers may use either or both depending on their process.

What downstream document types are created when a planned order is released?

The downstream document type depends on the planned order's order type: a make planned order releases to a work order (see Create Work Order in the Manufacturing test library), a buy planned order releases to a purchase requisition in Procurement, and a transfer planned order releases to a transfer order. This scenario orchestrates release into those existing scenarios rather than duplicating their coverage.

What do the failure intelligence categories mean when a release test fails?

SyntraFlow's evidence trail is designed to help classify a failure as DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, AUTOMATION_ERROR, INTEGRATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — for example, an unfirmed planned order ${PLANNED_ORDER} where firming is required is an EXPECTED_VALIDATION. A failure should never be labeled as an Oracle defect without first eliminating data, configuration, security, automation and integration causes.

How is security tested for releasing planned orders?

Access to release planned orders is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations — such as a Planning Analyst, a Planning Manager and an unauthorized user — to confirm that release access behaves as expected, without asserting a single universal Oracle security model.