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

Syntra Standard Oracle Test Library

Oracle Fusion Planning Exceptions Test Cases

Validate that Oracle Fusion SCM Supply Planning correctly generates planning exceptions from the supply plan output — including past due orders, items to expedite or de-expedite, shortage exceptions, overcapacity, resource conflicts and order-change exceptions — and that exception review and resolution routing behaves correctly, without labeling every exception as an application defect before eliminating other causes.

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

Test Objective

The objective of this test is to validate that Oracle Fusion SCM Supply Planning correctly generates system planning exceptions from the supply plan output — including past due orders, items to expedite or de-expedite, shortage, overcapacity, resource conflict, excess supply and order-change exceptions — and that exception review and resolution routing behaves correctly, applying the site's Failure Intelligence discipline to planning-specific exceptions rather than assuming every exception is an application defect.

The scenario should confirm that:

each configured exception type is correctly detected and classified from the supply plan output
exception detail correctly displays the supporting order and item data behind the exception
severity-based filtering correctly narrows the exception list
resolution actions such as reschedule or cancellation correctly update the underlying order
invalid resolution actions and unauthorized resolution attempts are correctly rejected or 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 review and resolution of planning exceptions as generated and configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It does not cover the underlying plan run itself or plan-wide supply/demand analysis, which are covered by the separate Run Supply Plan and Plan Analysis scenarios in the same Supply Planning cluster. Not every exception type described here is necessarily configured or enabled in every environment.

When to Use This Test

Functional testing of planning exception generation for a new Oracle Fusion SCM Supply Planning implementation
Regression testing of exception detection and resolution routing after an Oracle quarterly update
UAT sign-off for supply planners who review and resolve planning exceptions
Verifying that resolution actions such as reschedule or cancellation correctly update the underlying order
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and SECURITY_ERROR conditions surfaced during exception review before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Supply Planning Process

Run Supply Plan

→

Generate Planning Exceptions

→

Review Exception Detail

→

Filter by Severity

→

Resolve Exception

→

Verify Order Updated

Planning Exceptions are the system-generated flags raised against a completed supply plan within the Supply Planning scenario family and the Plan-to-Produce business flow. Exceptions are only available once a supply plan has run — covered by the Run Supply Plan scenario. Resolving an exception updates the underlying planned or purchase order, which can be reviewed through the Planned Orders scenario in this same cluster. Exact exception types generated, severity thresholds and resolution actions available depend on the plan configuration and customer-specific Oracle Fusion setup.

← Previous Stage

Plan Analysis

Preconditions

The test user has appropriate Supply Planner or Planning Manager access to review and resolve planning exceptions.
A supply plan has been run and has completed, generating an exception workbench for review (see Run Supply Plan).
Required exception types are configured and active for the target supply plan in the target Oracle Fusion environment.
Test orders and items referenced in exception test data exist and are visible within the plan scope.
Severity thresholds and resolution action configuration referenced in test data are configured and active.

Exact exception types generated, severity classification and available resolution actions may vary by Oracle Fusion implementation, plan configuration and customer-specific setup. No single exception type should be assumed to be configured in every environment.

Sample Test Data

Plan Name	${PLAN_NAME}
Exception Type	${EXCEPTION_TYPE}
Order	${ORDER}
Item	${ITEM}
Severity	${SEVERITY}
Resolution Action	${RESOLUTION_ACTION}
Resource	${RESOURCE}
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 exception type or field applies to every plan — for example, resource conflict exceptions may not apply to a plan with no constrained resources.

Test Steps

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

#	User Action	Expected Result
1	Sign In and Navigate to the Planning Exceptions Workbench Sign in to Oracle Fusion using an authorised Supply Planning test user and navigate to the planning exceptions workbench for the target plan. ${PLAN_NAME}	The planning exceptions workbench opens and displays exceptions generated for the target plan.
2	Filter by Exception Type or Severity Filter the exception list by exception type and by severity level. ${EXCEPTION_TYPE} / ${SEVERITY}	The exception list correctly narrows to exceptions matching the selected type and severity.
3	Review Exception Detail and Supporting Data Open an individual exception and review its detail, including the supporting order and item data behind the exception. ${ORDER} / ${ITEM} Reviewing the underlying order and item data before acting lets the tester confirm the exception is genuinely applicable before resolution.	The exception detail correctly displays the supporting order and item data behind the exception.
4	Apply a Resolution Action Apply a resolution action to the exception, such as rescheduling the order or cancelling it, using ${RESOLUTION_ACTION}. ${RESOLUTION_ACTION}	Oracle Fusion accepts the resolution action without unexpected errors.
5	Verify the Exception Clears Refresh the exceptions workbench and confirm the resolved exception no longer appears in the active exception list.	The resolved exception correctly clears from the active exception list.
6	Verify Underlying Order Updates CorrectlyBusiness assertion Open the underlying order referenced by the resolved exception and confirm it reflects the resolution action applied. ${ORDER} This is the primary business assertion for the scenario — the exception clearing is not sufficient on its own; the underlying order must correctly reflect the resolution.	The underlying order correctly reflects the reschedule or cancellation applied during exception resolution.

Expected Results

Each configured exception type is correctly detected and classified from the supply plan output.
Exception detail correctly displays the supporting order and item data behind the exception.
Severity-based filtering correctly narrows the exception list.
Resolution actions correctly update the underlying order and clear the exception.
Invalid resolution actions are correctly rejected before being applied.
Unauthorized resolution attempts are correctly blocked.

Key Validation Checkpoints

Each exception type correctly detected and classified from the supply plan output.
Exception detail correctly displays supporting order and item data.
Severity filtering correctly narrows the exception list.
Reschedule and cancellation resolutions correctly update the underlying order.
Invalid resolution actions correctly rejected.
Unauthorized resolution correctly blocked.

Core Business Scenario

Planning Exceptions

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 Planning Exceptions business scenario. Jarvis AI can extend this scenario by generating additional exception type, severity, resolution 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 exception type or resolution combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including invalid resolution actions and unauthorized resolution 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 Planning Exceptions business process and automation logic.

Customer DataVault

Provides approved customer-specific test data and configuration required for scenario generation — Plans, Exception Types, Orders and Items.

Jarvis AI

Analyses the standard scenario together with available test data and generates relevant exception detection, resolution and security variations.

Positive + Negative Test Variations

Valid exception detection and resolution scenarios and edge cases such as invalid resolution actions or unauthorized resolution.

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 exception type, severity or resolution combination, SyntraFlow maintains one core Planning Exceptions scenario and allows Jarvis AI to generate exception-specific and security-specific variations using the customer's available test data.

AI-Generated Test Variations

The same Planning Exceptions 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

Detect past due order, expedite and de-expedite exceptions
Detect shortage, overcapacity and resource conflict exceptions
Detect excess supply, new planned order and cancelled order exceptions
Review exception detail and supporting order/item data
Filter the exception list by severity
Resolve exceptions via reschedule
Resolve exceptions via order cancellation

Negative Scenarios

Attempt to apply an invalid exception resolution action
Attempt unauthorized exception resolution without the required access

These are representative examples only. Negative-scenario behavior and available exception 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 exception type, severity and resolution combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Planning Exceptions scenarios relevant to the customer's actual implementation.

Standard Library Definition

Plan Name        ${PLAN_NAME}
Exception Type    ${EXCEPTION_TYPE}
Order             ${ORDER}
Item              ${ITEM}
Severity          ${SEVERITY}
Resolution Action ${RESOLUTION_ACTION}
Resource          ${RESOURCE}
User Role         ${USER_ROLE}

DataVault

Supply Plans
  Configured plans and their exception rules
Exception Types
  Exception types enabled per plan
Orders and Items
  Orders and items visible within plan scope
Severity Thresholds
  Configured severity classification rules
User Roles
  Roles enabled for exception resolution

Jarvis AI Generates

Scenario 01 — Past Due Order Exception, Order A
Scenario 02 — Shortage Exception, Item B
Scenario 03 — Overcapacity Exception, Resource C
Scenario 04 — Resolve via Reschedule
Scenario 05 — Invalid Resolution Action
Scenario 06 — Unauthorized User Attempts Resolution
...

Planning exception test data can include order, item and resource configuration tied to supply chain planning. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific planning exception 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 Planning Exceptions test scenarios spanning exception detection across past due, expedite, shortage, capacity and order-change categories, resolution routing and negative/security exception 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-EXC-001	Detect Past Due Order Exception	Positive	The exception workbench for plan ${PLAN_NAME} correctly flags order ${ORDER} as past due.	SyntraFlow Ready
PLAN-EXC-002	Detect Item to Expedite Exception	Positive	The exception workbench correctly flags item ${ITEM} as an item to expedite for order ${ORDER}.	SyntraFlow Ready
PLAN-EXC-003	Detect Item to De-Expedite Exception	Positive	The exception workbench correctly flags item ${ITEM} as an item to de-expedite for order ${ORDER}.	SyntraFlow Ready
PLAN-EXC-004	Detect Shortage Exception	Positive	The exception workbench correctly flags a shortage exception for item ${ITEM} within plan ${PLAN_NAME}.	SyntraFlow Ready
PLAN-EXC-005	Detect Overcapacity Exception	Positive	The exception workbench correctly flags an overcapacity exception for resource ${RESOURCE}.	SyntraFlow Ready
PLAN-EXC-006	Detect Resource Conflict Exception	Positive	The exception workbench correctly flags a resource conflict exception for resource ${RESOURCE}.	SyntraFlow Ready
PLAN-EXC-007	Detect Excess Supply Exception	Positive	The exception workbench correctly flags an excess supply exception for item ${ITEM}.	SyntraFlow Ready
PLAN-EXC-008	Detect New Planned Order Exception	Positive	The exception workbench correctly flags a new planned order exception for order ${ORDER}.	SyntraFlow Ready
PLAN-EXC-009	Detect Cancelled Order Exception	Positive	The exception workbench correctly flags a cancelled order exception for order ${ORDER}.	SyntraFlow Ready
PLAN-EXC-010	Review Exception Detail	Positive	Exception detail for ${EXCEPTION_TYPE} correctly displays the supporting order ${ORDER} and item ${ITEM} data.	SyntraFlow Ready
PLAN-EXC-011	Resolve Exception via Reschedule	Positive	Exception ${EXCEPTION_TYPE} on order ${ORDER} is resolved using resolution action ${RESOLUTION_ACTION} to reschedule the order.	SyntraFlow Ready
PLAN-EXC-012	Resolve Exception via Order Cancellation	Positive	Exception ${EXCEPTION_TYPE} on order ${ORDER} is resolved using resolution action ${RESOLUTION_ACTION} to cancel the order.	SyntraFlow Ready
PLAN-EXC-013	Exception Filter by Severity	Positive	The exception list for plan ${PLAN_NAME} is filtered by severity ${SEVERITY} and correctly narrows to matching exceptions.	SyntraFlow Ready
PLAN-EXC-014	Invalid Exception Resolution Action	Negative	An invalid resolution action ${RESOLUTION_ACTION} is attempted against exception ${EXCEPTION_TYPE} on order ${ORDER}.	SyntraFlow Ready
PLAN-EXC-015	Unauthorized Exception Resolution	Negative/Security	An unauthorized user with role ${USER_ROLE} attempts to resolve exception ${EXCEPTION_TYPE} on order ${ORDER} without the required access.	SyntraFlow Ready

Automatically Expand Positive and Negative Planning Exceptions Coverage

Positive Testing

Jarvis generates scenarios using exception type, severity, order and resolution action combinations expected to correctly detect and resolve planning exceptions in Oracle Fusion.

Valid Exception Type + Valid Order + Valid Resolution Action → Exception Resolved

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around resolution actions, configuration and security.

Invalid Resolution Action → Expected Validation
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 Planning Exceptions scenarios and group them into reusable execution packs.

SCM Supply Planning Planning Exceptions Regression Pack

Detect Past Due Order Exception
Detect Item to Expedite Exception
Detect Shortage Exception
Detect Overcapacity Exception
Detect Resource Conflict Exception
Review Exception Detail
Resolve Exception via Reschedule
Resolve Exception via Order Cancellation
Exception Filter by Severity
Security Restriction — Unauthorized Exception Resolution

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

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

Persona	Action	Expected	Syntra Result
Planning Analyst	Review Planning Exceptions	Allowed	PASS
Planning Manager	Resolve Exception via Reschedule	Allowed	PASS
Unauthorized User	Attempts to Resolve Planning Exception	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 Planning Exceptions 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 — Planning Exceptions, 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 by Exception Type or Severity

May internally include

Open Exceptions Workbench → Select Exception Type Filter → Select Severity Filter → Apply Filters → Refresh Exception List → Confirm Filtered Count

Business Step

Apply a Resolution Action

May internally include

Open Exception Detail → Select Resolution Action → Confirm Reschedule/Cancel Parameters → Submit Resolution → Confirm Acceptance → 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 exception was correctly resolved — 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: Planning Exception Not Resolved — Likely category: EXPECTED_VALIDATION — Evidence: Exception type ${EXCEPTION_TYPE} correctly flagged per configured planning rules — Recommendation: Review and apply a resolution action; this is expected system behavior, not a defect. 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 by Exception Type or Severity	Pass	—
Apply a Resolution Action	Pass	—
Verify Underlying Order Updates Correctly	Pass	Pass

Related Supply Planning Tests

Planning Exceptions are generated from a completed supply plan and resolve into changes on planned orders — explore the related plan execution and order review scenarios below.

Run Supply Plan Planned Orders Plan Analysis

Turn This Standard Test into Your Oracle SCM Planning Exceptions Regression Suite

Start with the Syntra Standard Planning Exceptions test, use DataVault to provide environment-specific test data, let Jarvis generate additional exception type, resolution 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 all planning exception types always configured in every Oracle Fusion environment?

No. Which exception types — such as past due, expedite, shortage or overcapacity — are generated depends on Oracle Fusion Supply Planning configuration and customer setup. This scenario is designed to validate exception detection and resolution as configured in the target environment rather than assuming every exception type is universally enabled.

What is the difference between resolving an exception via reschedule versus cancellation?

Rescheduling using ${RESOLUTION_ACTION} moves the underlying order ${ORDER} to a new date, while cancellation removes the order from the plan. Both are valid resolution paths depending on the exception type and business context; this scenario validates that each correctly updates the underlying order and clears the exception.

How is severity-based filtering tested?

Scenario PLAN-EXC-013 filters the exception list by ${SEVERITY} to confirm the workbench correctly narrows to matching exceptions, as configured for the target environment and plan.

What do the failure intelligence categories mean when a planning exception 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 exception type ${EXCEPTION_TYPE} correctly flagged per configured planning rules and awaiting resolution is EXPECTED_VALIDATION, not a defect. 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 resolving planning exceptions?

Access to resolve planning exceptions 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 exception-resolution access behaves as expected, without asserting a single universal Oracle security model.