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

Syntra Standard Oracle Test Library

Oracle Fusion Planned Orders Test Cases

Validate that system-generated planned orders resulting from an Oracle Fusion SCM Supply Planning run can be reviewed, filtered and firmed, including make, buy and transfer planned order types, quantity and due date review, and order source, without assuming every planned order type is generated for every item.

Test ID	ORCL.SCM.PLAN.ORDERS
Application	Oracle Fusion Cloud
Product	SCM
Module	Supply Planning
Process	Planned Orders
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 18 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate review, filtering and firming of system-generated planned orders — make, buy and transfer — resulting from an Oracle Fusion SCM Supply Planning run, including planned order type, quantity and due date review, without assuming every planned order type is generated for every item.

The scenario should confirm that:

planned orders are correctly categorized by type — make, buy or transfer — as generated by the supply plan run
planned order filters correctly narrow the list by item, organization and date range
planned order quantity, due date and source are correctly displayed for review
firming a planned order correctly converts it to a firm status
planned order quantity and date modifications are correctly applied where permitted by configuration
Oracle correctly enforces validation when invalid modifications, already-firmed orders or unauthorized changes are attempted (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)

This scenario covers review, filtering and firming of planned orders as configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It does not cover execution of the supply plan itself or release of a firmed planned order to a purchase order, work order or transfer order, which are covered by the separate Run Supply Plan and Release Planned Order scenarios in the same Supply Planning cluster.

When to Use This Test

Functional testing of planned order review and firming for a new Oracle Fusion SCM Supply Planning implementation
Regression testing of planned order behavior after an Oracle quarterly update
UAT sign-off for supply planners who review, filter and firm planned orders
Baseline case referenced by the Release Planned Order scenario within the same Supply Planning cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and SECURITY_ERROR conditions surfaced during planned order modification before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Supply Planning Process

Run Supply Plan

→

Review Supply Demand Balance

→

Review Planned Orders

→

Firm Planned Order

→

Release Planned Order

→

Review Planning Exceptions

Planned Orders review sits after Supply Demand Balance and before Release Planned Order in the Supply Planning scenario family and the Plan-to-Produce business flow. The supply plan run generates planned orders as configured — covered by the Run Supply Plan scenario. After planned orders are reviewed, filtered and firmed, firmed orders can be released — covered by the Release Planned Order scenario in this same cluster. Exact planned order types generated, firming behavior and modification permissions depend on the plan configuration and customer-specific Oracle Fusion setup.

← Previous Stage

Supply Demand Balance

Next Stage →

Release Planned Order

Preconditions

The test user has appropriate Supply Planner or Planning Manager access to review and firm planned orders.
A supply plan has been run and has generated planned orders for the organizations included in the plan (see Run Supply Plan).
The item(s) and organization(s) referenced in test data are configured and included in the plan scope.
Planned order firming and modification permissions are configured as expected for the test user's role.
The plan run used to generate the planned orders under test has completed without unexpected errors.

Exact planned order types generated, firming behavior and modification permissions may vary by Oracle Fusion implementation, plan configuration and customer-specific setup. No single planned order type should be assumed to be generated for every item.

Sample Test Data

Item	${ITEM}
Organization	${ORGANIZATION}
Planned Order	${PLANNED_ORDER}
Order Type	${ORDER_TYPE}
Order Quantity	${ORDER_QUANTITY}
Due Date	${DUE_DATE}
Order Source	${ORDER_SOURCE}
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 planned order type applies to every item — for example, a purchased item may generate only buy planned orders while a manufactured item may generate make planned orders.

Test Steps

6 business-readable steps. SyntraFlow's automation executes ~18 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 Supply Planning test user. ${USER_ROLE}	The user is signed in and Supply Planning navigation is available.
2	Navigate to the Planned Orders Workbench Navigate to the planned orders workbench for the target supply plan. ${PLANNED_ORDER}	The planned orders workbench opens and the supply plan's planned orders are available for review.
3	Filter Planned Orders by Item, Organization or Date Range Apply filters to narrow the planned order list by item, organization and/or due date range. ${ITEM} / ${ORGANIZATION}	The planned order list is correctly narrowed to match the selected filter criteria.
4	Review Planned Order Type, Quantity, Due Date and Source Review the planned order type — make, buy or transfer — along with order quantity, due date and order source for the filtered planned orders. ${ORDER_TYPE} / ${ORDER_QUANTITY} / ${DUE_DATE} / ${ORDER_SOURCE} Not every planned order type is generated for every item — review reflects only the order types actually produced by the plan run.	The planned order type, quantity, due date and source are correctly displayed for the selected planned orders.
5	Firm or Modify the Planned Order Where Permitted Firm the planned order, or modify its quantity or due date where permitted by configuration. ${PLANNED_ORDER} Firming and modification permissions depend on plan configuration and the test user's role.	Oracle Fusion accepts the firming or modification request without unexpected errors, or correctly rejects it when not permitted.
6	Verify Resulting Order Status and ValuesBusiness assertion Open the planned order and confirm the resulting status, quantity and due date reflect the firming or modification action taken. This is the primary business assertion for the scenario — correct resulting order status and values is the expected pass condition, not merely a completed action.	The planned order correctly reflects the firmed status or modified quantity/date, or the invalid/unauthorized change is correctly blocked.

Expected Results

Planned orders are correctly categorized by type — make, buy or transfer — as generated by the supply plan run.
Planned order filters correctly narrow the list by item, organization and date range.
Planned order quantity, due date and source are correctly displayed for review.
Firming a planned order correctly converts it to a firm status.
Quantity and date modifications are correctly applied where permitted by configuration.
Invalid modifications, repeat firming and unauthorized changes are correctly rejected or blocked.

Key Validation Checkpoints

Planned orders correctly categorized by type (make, buy, transfer).
Filters correctly narrow the planned order list by item, organization and date.
Firming correctly converts the planned order to a firm status.
Quantity/date modification correctly applied where permitted by configuration.
Invalid modification correctly rejected.
Unauthorized change correctly blocked.

Core Business Scenario

Planned Orders

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 Planned Orders business scenario. Jarvis AI can extend this scenario by generating additional order type, filter, firming, modification 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 item, organization or planned order type combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including invalid modifications and unauthorized planned order changes, since correctly enforced validation and access control is an important part of what this scenario proves.

From Standard Test to Executed Regression Pack

Syntra Standard Test

Reusable Planned Orders business process and automation logic.

Customer DataVault

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

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant filter, firming, modification and security variations.

Positive + Negative Test Variations

Valid planned order review and firming scenarios and edge cases such as invalid modifications, repeat firming or unauthorized changes.

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 item, organization, planned order type or modification combination, SyntraFlow maintains one core Planned Orders scenario and allows Jarvis AI to generate filter, firming and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Planned Orders 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

Review make planned orders generated by the supply plan run
Review buy planned orders generated by the supply plan run
Review transfer planned orders generated by the supply plan run
Filter planned orders by item, organization and date range
Review planned order quantity, due date and order source
Firm a planned order to lock its quantity and date
Modify planned order quantity and due date where permitted by configuration

Negative Scenarios

Attempt an invalid planned order modification
Attempt to firm a planned order that is already firmed
Attempt an unauthorized planned order change without the required access

These are representative examples only. Negative-scenario behavior and available planned order types 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 item, organization, planned order type and modification permission combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Planned Orders scenarios relevant to the customer's actual implementation.

Standard Library Definition

Item              ${ITEM}
Organization      ${ORGANIZATION}
Planned Order     ${PLANNED_ORDER}
Order Type        ${ORDER_TYPE}
Order Quantity    ${ORDER_QUANTITY}
Due Date          ${DUE_DATE}
Order Source      ${ORDER_SOURCE}
User Role         ${USER_ROLE}

DataVault

Items
  Items enabled for supply planning by organization
Organizations
  Organizations enabled for supply planning
Planned Orders
  Planned orders generated by recent plan runs
Sourcing Rules
  Make/buy/transfer sourcing configuration by item
User Roles
  Roles enabled for planned order firming and modification

Jarvis AI Generates

Scenario 01 — Review Make Planned Orders, Item A
Scenario 02 — Review Buy Planned Orders, Item B
Scenario 03 — Filter by Organization and Date Range
Scenario 04 — Firm Planned Order
Scenario 05 — Invalid Quantity Modification
Scenario 06 — Unauthorized User Attempts Planned Order Change
...

Planned order data used in testing can include item, organization and quantity/date 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 Planned Orders test scenarios spanning make/buy/transfer order review, filtering, firming, modification and negative/security planned-order 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-ORD-001	View Make Planned Orders	Positive	Planned orders for item ${ITEM} in organization ${ORGANIZATION} are filtered to show only make planned orders.	SyntraFlow Ready
PLAN-ORD-002	View Buy Planned Orders	Positive	Planned orders for item ${ITEM} in organization ${ORGANIZATION} are filtered to show only buy planned orders.	SyntraFlow Ready
PLAN-ORD-003	View Transfer Planned Orders	Positive	Planned orders for item ${ITEM} in organization ${ORGANIZATION} are filtered to show only transfer planned orders.	SyntraFlow Ready
PLAN-ORD-004	Filter Planned Orders by Item	Positive	The planned order list is filtered to show only planned orders for item ${ITEM}.	SyntraFlow Ready
PLAN-ORD-005	Filter Planned Orders by Organization	Positive	The planned order list is filtered to show only planned orders for organization ${ORGANIZATION}.	SyntraFlow Ready
PLAN-ORD-006	Filter Planned Orders by Date Range	Positive	The planned order list is filtered to show only planned orders with a due date within a selected date range around ${DUE_DATE}.	SyntraFlow Ready
PLAN-ORD-007	View Planned Order Quantity and Due Date	Positive	Planned order ${PLANNED_ORDER} is reviewed to confirm its order quantity ${ORDER_QUANTITY} and due date ${DUE_DATE}.	SyntraFlow Ready
PLAN-ORD-008	View Planned Order Source	Positive	Planned order ${PLANNED_ORDER} is reviewed to confirm its order source ${ORDER_SOURCE}.	SyntraFlow Ready
PLAN-ORD-009	Firm Planned Order	Positive	Planned order ${PLANNED_ORDER} is firmed, converting it to a firm status and locking its quantity and date.	SyntraFlow Ready
PLAN-ORD-010	Modify Planned Order Quantity Where Permitted	Positive	The order quantity of planned order ${PLANNED_ORDER} is modified to ${ORDER_QUANTITY} where permitted by configuration.	SyntraFlow Ready
PLAN-ORD-011	Modify Planned Order Date Where Permitted	Positive	The due date of planned order ${PLANNED_ORDER} is modified to ${DUE_DATE} where permitted by configuration.	SyntraFlow Ready
PLAN-ORD-012	Invalid Planned Order Modification	Negative	An invalid modification is attempted on planned order ${PLANNED_ORDER}, such as a quantity or date outside allowed configuration.	SyntraFlow Ready
PLAN-ORD-013	Firm Already-Firmed Order	Negative	A repeat firming action is attempted on planned order ${PLANNED_ORDER} that has already been firmed.	SyntraFlow Ready
PLAN-ORD-014	Unauthorized Planned Order Change	Negative/Security	A user with role ${USER_ROLE} without the required access attempts to modify planned order ${PLANNED_ORDER}.	SyntraFlow Ready

Automatically Expand Positive and Negative Planned Order Coverage

Positive Testing

Jarvis generates scenarios using item, organization, order type and firming/modification combinations expected to successfully review and update a planned order in Oracle Fusion.

Valid Planned Order + Permitted Modification + Valid User Role → Order Firmed or Modified

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around planned order modification, firming state, configuration and security.

Invalid Planned Order Modification → Expected Validation
Firm Already-Firmed Order → Expected Validation
Unauthorized Planned Order Change → 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 Planned Orders scenarios and group them into reusable execution packs.

SCM Supply Planning Planned Orders Regression Pack

View Make Planned Orders
View Buy Planned Orders
View Transfer Planned Orders
Filter Planned Orders by Item
Filter Planned Orders by Organization
Filter Planned Orders by Date Range
Firm Planned Order
Modify Planned Order Quantity Where Permitted
Invalid Planned Order Modification
Security Restriction — Unauthorized Planned Order Change

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

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

Persona	Action	Expected	Syntra Result
Planning Analyst	View and Filter Planned Orders	Allowed	PASS
Planning Manager	Firm Planned Order	Allowed	PASS
Unauthorized User	Attempts to Modify 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 Planned Orders 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 — Planned Orders, 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

Filter Planned Orders by Item, Organization or Date Range

May internally include

Open Planned Orders Workbench → Apply Item Filter → Apply Organization Filter → Apply Date Range Filter → Refresh List → Confirm Filtered Results

Business Step

Firm or Modify the Planned Order Where Permitted

May internally include

Select Planned Order → Open Firm/Modify Action → Enter Quantity or Date Change → Submit Change → Refresh Order 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 was correctly firmed or modified — 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 Firming Failed — Likely category: EXPECTED_VALIDATION — Evidence: Planned order ${PLANNED_ORDER} already firmed — Recommendation: Verify order status before attempting to firm again. 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
Filter Planned Orders by Item, Organization or Date Range	Pass	—
Firm or Modify the Planned Order Where Permitted	Pass	—
Verify Resulting Order Status and Values	Pass	Pass

Related Supply Planning Tests

Planned Orders review sits between plan execution and release in the Supply Planning cluster — explore the related supply/demand review, release and exception scenarios below.

Supply Demand Balance Release Planned Order Planning Exceptions

Turn This Standard Test into Your Oracle SCM Planned Orders Regression Suite

Start with the Syntra Standard Planned Orders test, use DataVault to provide environment-specific test data, let Jarvis generate additional filter, 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 Syntra DataVault DataVault Data Masking

Frequently Asked Questions

Are make, buy and transfer planned orders always generated for every item?

No. Which planned order types — make, buy, transfer, or a combination — are generated for a given item depends on the item's sourcing rule, supplier setup and Oracle Fusion Supply Planning configuration. This scenario is designed to validate planned order review as configured in the target environment rather than assuming every planned order type is universally generated.

What happens when a planned order is firmed?

Firming a planned order using ${PLANNED_ORDER} is designed to lock its quantity and date so the supply plan no longer automatically recalculates them on the next plan run. This scenario validates that firming correctly converts the planned order to a firm status as configured for the target environment.

Can planned order quantity and date always be modified?

No. Whether a planned order's quantity or due date can be modified — and by which roles — depends on plan configuration and Oracle Fusion security setup. Scenario PLAN-ORD-010 and PLAN-ORD-011 validate quantity and date modification only where permitted; PLAN-ORD-012 validates that an invalid modification is correctly rejected.

What do the failure intelligence categories mean when a planned orders 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, attempting to firm an already-firmed planned order ${PLANNED_ORDER} 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 planned order changes?

Access to firm or modify 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 planned order access behaves as expected, without asserting a single universal Oracle security model.