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

Syntra Standard Oracle Test Library

Oracle Fusion Plan Analysis Test Cases

Validate that published and simulation supply plans can be analyzed and compared in Oracle Fusion SCM Supply Planning, including plan metrics dashboards, plan-to-plan and simulation-to-published comparisons, organization filtering and export, without assuming every metric is enabled or meaningful for every plan type.

Test ID	ORCL.SCM.PLAN.ANALYSIS
Application	Oracle Fusion Cloud
Product	SCM
Module	Supply Planning
Process	Plan Analysis
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 analysis and comparison of published and simulation supply plans in Oracle Fusion SCM Supply Planning, including key planning metrics and plan-to-plan comparison views, without assuming every metric is enabled or meaningful for every plan type.

The scenario should confirm that:

plan metrics such as on-time delivery, fill rate and utilization are correctly calculated and displayed on the dashboard, where enabled for the plan type
plan-to-plan comparison between two published plans correctly aligns matching organizations and time periods
comparison between a simulation plan and the published plan correctly isolates simulation-only changes
plan analysis results can be correctly filtered by organization and exported for offline review
invalid comparison selections and analysis attempted on a plan with no run history are correctly rejected or flagged
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 analysis and comparison of published and simulation supply plans as configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It does not cover execution of the underlying supply plans, which is covered by the separate Run Supply Plan scenario, or review of supply/demand balance and planning exceptions, which are covered by the corresponding scenarios in the same Supply Planning cluster. Not every planning metric should be assumed to be enabled or meaningful for every plan type.

When to Use This Test

Functional testing of plan analysis and metrics review for a new Oracle Fusion SCM Supply Planning implementation
Regression testing of plan-to-plan and simulation-to-published comparison behavior after an Oracle quarterly update
UAT sign-off for supply planners who review plan metrics and compare plan scenarios
Baseline case for reviewing plan output following the Run Supply Plan scenario within the same Supply Planning cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and SECURITY_ERROR conditions surfaced during plan analysis before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Supply Planning Process

Navigate to Plan Analysis Dashboard

→

Select Plan and Comparison Plan

→

Plan Analysis

→

Compare Published and Simulation Plans

→

Apply Organization Filters

→

Reconcile Comparison Values

Plan Analysis is the review and comparison step of the Supply Planning scenario family and of the Plan-to-Produce business flow. It is typically performed after Run Supply Plan generates a published or simulation plan, and can draw on Supply Demand Balance and Planning Exceptions data for deeper review. Exact metrics available, comparison views and analysis behavior depend on the plan configuration and customer-specific Oracle Fusion setup.

← Previous Stage

Planning Exceptions

Preconditions

The test user has appropriate Supply Planner or Planning Manager access to view and compare supply plans.
The published plan and comparison plan (or simulation set) referenced in test data have completed at least one plan run.
Required plan metrics are configured and enabled for the plan types under test, where applicable.
The organization(s) referenced in test data are included in the scope of the plans being analyzed.
Simulation sets referenced in test data are configured and available for simulation-to-published comparison.

Exact metrics available, comparison views and analysis behavior may vary by Oracle Fusion implementation, plan configuration and customer-specific setup. Not every metric should be assumed to be enabled or meaningful for every plan type.

Sample Test Data

Plan Name	${PLAN_NAME}
Comparison Plan	${COMPARISON_PLAN}
Metric	${METRIC}
Organization	${ORGANIZATION}
Time Period	${TIME_PERIOD}
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 metric or comparison view applies to every plan type — for example, resource utilization may not be meaningful for a purely unconstrained plan.

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 signs in successfully and the Supply Planning work area is accessible.
2	Navigate to the Plan Analysis Dashboard Navigate to the plan analysis dashboard for the target supply plan. ${PLAN_NAME}	The plan analysis dashboard opens and the target plan is available for review.
3	Select the Plan and Comparison Plan or Time Period Select the primary plan along with the comparison plan or time period to be analyzed. ${PLAN_NAME} / ${COMPARISON_PLAN} / ${TIME_PERIOD}	The selected plan and comparison plan or time period are accepted and reflected on the analysis view.
4	Review Key Metrics Review key planning metrics such as on-time delivery, fill rate and utilization, where enabled for the plan type. ${METRIC} Not every metric is enabled or meaningful for every plan type; the tester should confirm which metrics apply before treating an absence as a defect.	Key metrics are correctly calculated and displayed on the dashboard, as configured for the plan type.
5	Apply Organization Filters Apply organization filters to narrow the analysis to the relevant scope. ${ORGANIZATION}	The analysis view correctly reflects the selected organization filter.
6	Verify Comparison Values Reconcile with Underlying Plan DataBusiness assertion Verify that the comparison values shown in the analysis view reconcile with the underlying plan data for both plans. This is the primary business assertion for the scenario — correctly reconciled comparison values are the expected pass condition, not merely a rendered dashboard.	The comparison values correctly reconcile with the underlying published and/or simulation plan data.

Expected Results

Plan metrics are correctly calculated and displayed on the dashboard, as configured for the plan type.
Plan-to-plan comparison correctly aligns matching organizations and time periods.
Simulation-to-published comparison correctly isolates simulation-only changes.
Invalid comparison selections are correctly rejected.
Analysis on a plan with no run history is correctly blocked or flagged.
Unauthorized analysis access is correctly blocked.

Key Validation Checkpoints

Plan metrics correctly calculated and displayed on the dashboard.
Plan-to-plan comparison correctly aligns matching organizations and time periods.
Simulation-to-published comparison correctly isolates simulation-only changes.
Invalid comparison selections correctly rejected.
Analysis on a plan with no run history correctly blocked or flagged.
Unauthorized analysis access correctly blocked.

Core Business Scenario

Plan Analysis

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 Plan Analysis business scenario. Jarvis AI can extend this scenario by generating additional metric, comparison, organization 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 metric, comparison type or organization combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including simulation-to-published comparisons and unauthorized analysis 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 Plan Analysis business process and automation logic.

Customer DataVault

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

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant metric, comparison, scope and security variations.

Positive + Negative Test Variations

Valid plan analysis scenarios and edge cases such as invalid comparison selections, plans with no run history or unauthorized analysis access.

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 metric, comparison type or organization combination, SyntraFlow maintains one core Plan Analysis scenario and allows Jarvis AI to generate metric, comparison and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Plan Analysis 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 plan metrics dashboard including on-time delivery, fill rate and utilization, as configured for the plan type
Compare two published plans using the plan-to-plan comparison view
Compare a plan across different time periods
Filter plan analysis by organization
Export plan analysis results
Compare a simulation plan to the published plan, isolating simulation-only changes

Negative Scenarios

Attempt an invalid comparison selection between incompatible plans
Attempt analysis on a plan with no run history
Attempt unauthorized plan analysis access without the required access

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

Standard Library Definition

Plan Name         ${PLAN_NAME}
Comparison Plan   ${COMPARISON_PLAN}
Metric            ${METRIC}
Organization      ${ORGANIZATION}
Time Period       ${TIME_PERIOD}
Simulation Set    ${SIMULATION_SET}
User Role         ${USER_ROLE}

DataVault

Supply Plans
  Configured plans and their run history
Comparison Plans
  Plans available for plan-to-plan comparison
Metrics
  Planning metrics enabled by plan type
Organizations
  Organizations enabled for supply planning
Simulation Sets
  Configured simulation sets available for comparison
User Roles
  Roles enabled for plan analysis

Jarvis AI Generates

Scenario 01 — Plan Metrics Dashboard Review
Scenario 02 — Plan-to-Plan Comparison
Scenario 03 — Time Period Comparison
Scenario 04 — Simulation-to-Published Comparison
Scenario 05 — Invalid Comparison Selection
Scenario 06 — Unauthorized User Attempts Plan Analysis
...

Plan analysis test data can include plan, metric and organization information 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 12 individual Plan Analysis test scenarios spanning metrics dashboards, plan-to-plan and simulation-to-published comparisons and negative/security analysis 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-ANL-001	View Plan Metrics Dashboard	Positive	The plan metrics dashboard for plan ${PLAN_NAME} is opened and key metrics are reviewed as configured for the plan type.	SyntraFlow Ready
PLAN-ANL-002	Review On-Time Delivery Metric	Positive	The on-time delivery metric ${METRIC} is reviewed for plan ${PLAN_NAME}, where enabled for the plan type.	SyntraFlow Ready
PLAN-ANL-003	Review Fill Rate Metric	Positive	The fill rate metric ${METRIC} is reviewed for plan ${PLAN_NAME}, where enabled for the plan type.	SyntraFlow Ready
PLAN-ANL-004	Review Resource Utilization Metric	Positive	The resource utilization metric ${METRIC} is reviewed for plan ${PLAN_NAME}, where enabled for the plan type.	SyntraFlow Ready
PLAN-ANL-005	Compare Two Published Plans	Positive	Published plan ${PLAN_NAME} is compared to published plan ${COMPARISON_PLAN} using the plan-to-plan comparison view.	SyntraFlow Ready
PLAN-ANL-006	Compare Plan Across Time Periods	Positive	Plan ${PLAN_NAME} is compared across time period ${TIME_PERIOD} to review metric trends.	SyntraFlow Ready
PLAN-ANL-007	Filter Analysis by Organization	Positive	Plan analysis for ${PLAN_NAME} is filtered to organization ${ORGANIZATION}.	SyntraFlow Ready
PLAN-ANL-008	Export Plan Analysis	Positive	Plan analysis results for ${PLAN_NAME} are exported for offline review.	SyntraFlow Ready
PLAN-ANL-009	Compare Simulation Plan to Published Plan	Positive	Simulation plan using simulation set ${SIMULATION_SET} is compared to published plan ${PLAN_NAME} to isolate simulation-only changes.	SyntraFlow Ready
PLAN-ANL-010	Invalid Comparison Selection	Negative	An invalid comparison selection is attempted between plan ${PLAN_NAME} and an incompatible comparison plan ${COMPARISON_PLAN}.	SyntraFlow Ready
PLAN-ANL-011	Analysis on Plan with No Run History	Negative	Analysis is attempted on comparison plan ${COMPARISON_PLAN} that has no run history.	SyntraFlow Ready
PLAN-ANL-012	Unauthorized Plan Analysis Access	Negative/Security	An unauthorized user with role ${USER_ROLE} attempts to access plan analysis for ${PLAN_NAME} without the required access.	SyntraFlow Ready

Automatically Expand Positive and Negative Plan Analysis Coverage

Positive Testing

Jarvis generates scenarios using metric, comparison and organization combinations expected to successfully analyze and compare supply plans in Oracle Fusion.

Valid Plan + Valid Comparison Plan + Run History → Comparison Generated

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around comparison selection, run history, configuration and security.

Invalid Comparison Selection → Expected Validation
Analysis on Plan with No Run History → Expected Data Validation or Warning
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 Plan Analysis scenarios and group them into reusable execution packs.

SCM Supply Planning Plan Analysis Regression Pack

View Plan Metrics Dashboard
Review On-Time Delivery Metric
Review Fill Rate Metric
Review Resource Utilization Metric
Compare Two Published Plans
Compare Plan Across Time Periods
Filter Analysis by Organization
Compare Simulation Plan to Published Plan
Invalid Comparison Selection
Security Restriction — Unauthorized Plan Analysis Access

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

Once scheduled, SyntraFlow executes the selected Plan Analysis 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 Plan Analysis 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 & Approval Variations

Access to plan analysis is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that plan analysis access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Planning Analyst	View Plan Metrics Dashboard	Allowed	PASS
Planning Manager	Compare Simulation to Published Plan	Allowed	PASS
Unauthorized User	Attempts to Access Plan Analysis	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 Plan Analysis 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 — Plan Analysis, 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 Plan and Comparison Plan or Time Period

May internally include

Open Plan Analysis Dashboard → Select Primary Plan → Select Comparison Plan → Select Time Period → Apply Selection → Load Comparison View

Business Step

Review Key Metrics

May internally include

Open Metrics Panel → Load On-Time Delivery → Load Fill Rate → Load Utilization → Capture Metric Values → 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 analysis is correct — 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: Plan Comparison Failed — Likely category: DATA_ERROR — Evidence: Comparison plan ${COMPARISON_PLAN} has no run history — Recommendation: Run the comparison plan before attempting analysis. 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 Plan and Comparison Plan or Time Period	Pass	—
Review Key Metrics	Pass	—
Verify Comparison Values Reconcile with Underlying Plan Data	Pass	Pass

Related Supply Planning Tests

Plan Analysis is the review and comparison step of the Supply Planning cluster — explore the related plan execution and exception review scenarios below.

Run Supply Plan Supply Demand Balance Planning Exceptions

Turn This Standard Test into Your Oracle SCM Plan Analysis Regression Suite

Start with the Syntra Standard Plan Analysis test, use DataVault to provide environment-specific test data, let Jarvis generate additional metric, comparison 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

Do the same plan metrics apply to every plan type?

No. Which metrics — such as on-time delivery, fill rate or resource utilization — are enabled or meaningful depends on the plan type and Oracle Fusion Supply Planning configuration. This scenario is designed to validate metrics as configured for the target plan rather than assuming every metric is universally enabled.

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

A simulation-to-published comparison using simulation set ${SIMULATION_SET} is designed to isolate simulation-only changes from the published plan ${PLAN_NAME}, letting planners evaluate what-if scenarios without affecting live data. This scenario validates that the comparison correctly isolates those simulation-only differences.

How does plan-to-plan comparison work?

Plan-to-plan comparison aligns matching organizations and time periods between two published plans — for example ${PLAN_NAME} and ${COMPARISON_PLAN} — so planners can review differences in metrics and quantities. This scenario validates that the comparison view correctly aligns and reconciles that data.

What do the failure intelligence categories mean when a plan analysis 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, a comparison plan with no run history 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 plan analysis?

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