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

Syntra Standard Oracle Test Library

Oracle Fusion Run Supply Plan Test Cases

Validate that supply plans can be executed in Oracle Fusion SCM Supply Planning, including constrained and unconstrained plan options, single- and multi-organization scope, extended horizon and safety stock rule application, simulation runs, and plan status/log monitoring, without assuming every plan run type is enabled in every environment.

Test ID	ORCL.SCM.PLAN.RUN
Application	Oracle Fusion Cloud
Product	SCM
Module	Supply Planning
Process	Run Supply Plan
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 21 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate execution of supply plans in Oracle Fusion SCM Supply Planning, including constrained and unconstrained plan options, simulation runs, plan scope across single or multiple organizations, and plan status monitoring, without assuming every plan run type is enabled in every environment.

The scenario should confirm that:

the supply plan correctly executes with the selected plan options and organizational scope
constrained plans correctly respect resource and material constraints as configured
simulation plan runs correctly isolate from the published plan
plan run status and the plan run log are correctly available for monitoring
downstream processes such as Supply Demand Balance and Planned Orders can reference the resulting plan
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 execution of supply plans as configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It does not cover collection of planning data or downstream review of supply/demand balance and planned orders, which are covered by the separate Collect Planning Data, Supply Demand Balance and Planned Orders scenarios in the same Supply Planning cluster.

When to Use This Test

Functional testing of supply plan execution for a new Oracle Fusion SCM Supply Planning implementation
Regression testing of plan run behavior after an Oracle quarterly update
UAT sign-off for supply planners who execute constrained and unconstrained plans
Baseline case referenced by the Supply Demand Balance and Planned Orders scenarios within the same Supply Planning cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and SECURITY_ERROR conditions surfaced during plan execution before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Supply Planning Process

Navigate to Supply Plans

→

Select Plan Options

→

Run Supply Plan

→

Monitor Run Status

→

Review Run Log

→

Verify Resulting Plan

Run Supply Plan is the execution step of the Supply Planning scenario family and of the Plan-to-Produce business flow. Before a plan can run, planning data must be collected — covered by the Collect Planning Data scenario. After a plan runs, the resulting plan is reviewed through Supply Demand Balance and Planned Orders — covered by the corresponding scenarios in this same cluster. Exact plan options available, constraint enforcement and run behavior depend on the plan configuration and customer-specific Oracle Fusion setup.

← Previous Stage

Collect Planning Data

Next Stage →

Supply Demand Balance

Preconditions

The test user has appropriate Supply Planner or Planning Manager access to run supply plans.
Required supply plans and plan options are configured and active in the target Oracle Fusion environment.
Planning data has been collected for the organizations included in the plan (see Collect Planning Data).
The organization(s) included in the plan scope are configured to allow plan execution.
Safety stock rules and other plan-specific configuration referenced in test data are configured and active.

Exact plan options, constraint behavior and validation messages may vary by Oracle Fusion implementation, plan configuration and customer-specific setup. No single plan run type should be assumed to be enabled in every environment.

Sample Test Data

Plan Name	${PLAN_NAME}
Plan Options	${PLAN_OPTIONS}
Organization	${ORGANIZATION}
Planning Horizon	${PLANNING_HORIZON}
Safety Stock Rule	${SAFETY_STOCK_RULE}
Plan Status	${PLAN_STATUS}
Simulation Set	${SIMULATION_SET}
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 plan option or field applies to every plan type — for example, safety stock rules may not apply to a purely unconstrained plan.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to the Supply Plan Sign in to Oracle Fusion using an authorised Supply Planning test user and navigate to the target supply plan. ${PLAN_NAME}	The supply plan work area opens and the target plan is available for selection.
2	Select Plan Options and Organizational Scope Select the plan options — such as constrained or unconstrained execution — and the organizational scope for the plan run. ${PLAN_OPTIONS} / ${ORGANIZATION}	The selected plan options and organizational scope are accepted and reflected on the run request.
3	Submit the Plan Run Review the selected plan options, planning horizon and safety stock rule, then submit the supply plan for execution. ${PLANNING_HORIZON} / ${SAFETY_STOCK_RULE} Reviewing the run request before submission lets the tester catch an incorrect option or scope before the plan is executed.	Oracle Fusion accepts the plan run request without unexpected errors.
4	Monitor Plan Run Status Monitor the plan run status until the run reaches a completed, warning or error state. ${PLAN_STATUS}	The plan run status is correctly available and reflects the current state of the run.
5	Review Plan Run Log Open the plan run log to review completion details and any warnings or errors raised during the run.	The plan run log is accessible and reflects the outcome of the run, including any warnings or errors.
6	Verify Resulting Plan Reflects Selected Scope and OptionsBusiness assertion Open the resulting supply plan and confirm it reflects the plan options and organizational scope selected for the run. This is the primary business assertion for the scenario — a correctly generated plan reflecting the selected scope and options is the expected pass condition, not merely a completed run status.	The resulting plan correctly reflects the selected plan options, organizational scope and other run parameters.

Expected Results

The supply plan correctly executes with the selected plan options and organizational scope.
Constrained plans correctly respect resource and material constraints as configured.
Simulation plan runs correctly isolate from the published plan.
Plan run status and the plan run log are correctly available for monitoring.
Missing or stale collected data is correctly blocked or flagged before the run completes.
The resulting plan is available for downstream review in Supply Demand Balance and Planned Orders.

Key Validation Checkpoints

Plan correctly executes with the selected options and scope.
Constrained plans correctly respect resource and material constraints.
Simulation runs correctly isolate from the published plan.
Missing collected data correctly blocks or flags the run.
Concurrent plan run correctly blocked or queued.
Unauthorized plan run correctly blocked.

Core Business Scenario

Run Supply Plan

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 Run Supply Plan business scenario. Jarvis AI can extend this scenario by generating additional plan option, organization, horizon 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 plan option, organization or constraint combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including simulation runs and unauthorized plan-run attempts, 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 Run Supply Plan business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Plans, Organizations, Safety Stock Rules and Simulation Sets.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant plan option, scope, horizon and security variations.

Positive + Negative Test Variations

Valid plan run scenarios and edge cases such as invalid plan options, missing collected data or unauthorized runs.

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 plan option, organization, horizon or constraint combination, SyntraFlow maintains one core Run Supply Plan scenario and allows Jarvis AI to generate plan-run and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Run Supply Plan 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

Run unconstrained supply plans
Run constrained supply plans respecting resource and material constraints
Run plans scoped to a single organization and to multiple organizations
Run plans using specific plan options and an extended planning horizon
Run plans applying configured safety stock rules
Monitor plan run status and review the plan run log
Run simulation plans isolated from the published plan

Negative Scenarios

Attempt to run a plan using invalid or incompatible plan options
Attempt to run a plan where required collected data is missing or stale
Attempt to run a plan while a prior run of the same plan is already in progress
Attempt to run a plan that encounters an unexpected run failure
Attempt unauthorized plan run without the required access

These are representative examples only. Negative-scenario behavior and available plan 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 plan option, organization, horizon and safety stock combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Run Supply Plan scenarios relevant to the customer's actual implementation.

Standard Library Definition

Plan Name         ${PLAN_NAME}
Plan Options      ${PLAN_OPTIONS}
Organization      ${ORGANIZATION}
Planning Horizon  ${PLANNING_HORIZON}
Safety Stock Rule ${SAFETY_STOCK_RULE}
Plan Status       ${PLAN_STATUS}
Simulation Set    ${SIMULATION_SET}
User Role         ${USER_ROLE}

DataVault

Supply Plans
  Configured plans and their default options
Organizations
  Organizations enabled for supply planning
Safety Stock Rules
  Active safety stock rules by item/organization
Simulation Sets
  Configured simulation sets available for plan runs
User Roles
  Roles enabled for plan execution

Jarvis AI Generates

Scenario 01 — Unconstrained Plan Run, Organization A
Scenario 02 — Constrained Plan Run, Organization B
Scenario 03 — Multi-Organization Plan Run
Scenario 04 — Simulation Plan Run
Scenario 05 — Missing Collected Data
Scenario 06 — Unauthorized User Attempts Plan Run
...

Run Supply Plan test data can include plan, organization and safety stock configuration tied to supply chain planning. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific planning 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 15 individual Run Supply Plan test scenarios spanning constrained/unconstrained execution, simulation runs, plan options and negative/security plan-run 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-RUN-001	Run Unconstrained Supply Plan	Positive	Supply plan ${PLAN_NAME} is run using unconstrained plan options for organization ${ORGANIZATION}.	SyntraFlow Ready
PLAN-RUN-002	Run Constrained Supply Plan	Positive	Supply plan ${PLAN_NAME} is run using constrained plan options ${PLAN_OPTIONS}, respecting resource and material constraints.	SyntraFlow Ready
PLAN-RUN-003	Run Plan for Single Organization	Positive	Supply plan ${PLAN_NAME} is run scoped to a single organization ${ORGANIZATION}.	SyntraFlow Ready
PLAN-RUN-004	Run Plan for Multiple Organizations	Positive	Supply plan ${PLAN_NAME} is run scoped to multiple organizations including ${ORGANIZATION}.	SyntraFlow Ready
PLAN-RUN-005	Run Plan with Specific Plan Options	Positive	Supply plan ${PLAN_NAME} is run using plan options ${PLAN_OPTIONS} selected for the run.	SyntraFlow Ready
PLAN-RUN-006	Run Plan with Extended Horizon	Positive	Supply plan ${PLAN_NAME} is run using an extended planning horizon of ${PLANNING_HORIZON}.	SyntraFlow Ready
PLAN-RUN-007	Run Plan with Safety Stock Rules	Positive	Supply plan ${PLAN_NAME} is run applying safety stock rule ${SAFETY_STOCK_RULE} during plan generation.	SyntraFlow Ready
PLAN-RUN-008	Monitor Plan Run Status	Positive	The status of plan run ${PLAN_NAME} is monitored and confirmed as ${PLAN_STATUS}.	SyntraFlow Ready
PLAN-RUN-009	Review Plan Run Log	Positive	The run log for plan ${PLAN_NAME} is reviewed to confirm completion details and any warnings.	SyntraFlow Ready
PLAN-RUN-010	Simulation Plan Run	Positive	Supply plan ${PLAN_NAME} is run as a simulation using simulation set ${SIMULATION_SET}, isolated from the published plan.	SyntraFlow Ready
PLAN-RUN-011	Invalid Plan Options	Negative	Plan run is attempted using invalid or incompatible plan options ${PLAN_OPTIONS} for plan ${PLAN_NAME}.	SyntraFlow Ready
PLAN-RUN-012	Missing Collected Data	Negative	Plan run is attempted for organization ${ORGANIZATION} where planning data has not been collected or is stale.	SyntraFlow Ready
PLAN-RUN-013	Plan Run Already In Progress	Negative	A second run of plan ${PLAN_NAME} is attempted while a prior run of the same plan is already in progress.	SyntraFlow Ready
PLAN-RUN-014	Plan Run Failure	Negative	Plan run for ${PLAN_NAME} encounters an unexpected failure during execution.	SyntraFlow Ready
PLAN-RUN-015	Unauthorized Plan Run	Negative/Security	An unauthorized user with role ${USER_ROLE} attempts to run supply plan ${PLAN_NAME} without the required access.	SyntraFlow Ready

Automatically Expand Positive and Negative Plan Run Coverage

Positive Testing

Jarvis generates scenarios using plan options, organizational scope, horizon and safety stock combinations expected to successfully run a supply plan in Oracle Fusion.

Valid Plan Options + Valid Organization + Collected Data → Plan Generated

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around plan options, collected data, concurrency, configuration and security.

Invalid Plan Options → Expected Validation
Missing Collected Data → Expected Data Validation or Warning
Plan Run Already In Progress → Expected Concurrency Block or Queue
Unexpected Plan Run Failure → Expected Failure Handling
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 Run Supply Plan scenarios and group them into reusable execution packs.

SCM Supply Planning Run Supply Plan Regression Pack

Run Unconstrained Supply Plan
Run Constrained Supply Plan
Run Plan for Multiple Organizations
Run Plan with Extended Horizon
Run Plan with Safety Stock Rules
Simulation Plan Run
Invalid Plan Options
Missing Collected Data
Plan Run Already In Progress
Security Restriction — Unauthorized Plan Run

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

Once scheduled, SyntraFlow executes the selected Run Supply Plan 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 Run Supply Plan Regression Pack
Schedule	Quarterly Update Regression
Tests	15 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 run supply plans is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that plan-run access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Planning Analyst	Run Supply Plan	Allowed	PASS
Planning Manager	Run Constrained Supply Plan	Allowed	PASS
Unauthorized User	Attempts to Run Supply Plan	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 Run Supply Plan 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 — Run Supply Plan, 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 Plan Options and Organizational Scope

May internally include

Open Plan Options Panel → Select Constrained/Unconstrained → Select Organizations → Set Planning Horizon → Apply Safety Stock Rule → Confirm Scope

Business Step

Monitor Plan Run Status

May internally include

Open Scheduled Processes → Search Plan Run → Refresh Status → Capture Run Log → Confirm Completion 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 plan executed 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: Supply Plan Run Failed — Likely category: DATA_ERROR — Evidence: Collected data stale or missing for organization ${ORGANIZATION} — Recommendation: Rerun planning data collection before executing the supply plan. 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 Plan Options and Organizational Scope	Pass	—
Submit the Plan Run	Pass	—
Verify Resulting Plan Reflects Selected Scope and Options	Pass	Pass

Related Supply Planning Tests

Run Supply Plan is the execution step of the Supply Planning cluster — explore the related planning data collection and plan review scenarios below.

Collect Planning Data Supply Demand Balance Planned Orders

Turn This Standard Test into Your Oracle SCM Run Supply Plan Regression Suite

Start with the Syntra Standard Run Supply Plan test, use DataVault to provide environment-specific test data, let Jarvis generate additional plan option, organization 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

Is constrained or unconstrained plan execution always available in every Oracle Fusion environment?

No. Which plan run types — constrained, unconstrained, or both — are enabled depends on Oracle Fusion Supply Planning configuration and customer setup. This scenario is designed to validate plan execution as configured in the target environment rather than assuming every plan run type is universally enabled.

What is the difference between a simulation plan run and a published plan run?

A simulation plan run using ${SIMULATION_SET} is designed to execute in isolation from the published plan, allowing planners to evaluate what-if scenarios without affecting live supply and demand data. This scenario validates that simulation runs remain correctly isolated from the published plan.

How is extended horizon planning tested?

Scenario PLAN-RUN-006 runs the supply plan using an extended planning horizon (${PLANNING_HORIZON}) to confirm the plan correctly generates supply recommendations across the extended time window, as configured for the target environment.

What do the failure intelligence categories mean when a plan run 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, stale or missing collected data for organization ${ORGANIZATION} is a DATA_ERROR. 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 running supply plans?

Access to run supply plans 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 plan-run access behaves as expected, without asserting a single universal Oracle security model.