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

Syntra Standard Oracle Test Library

Oracle Fusion Collect Planning Data Test Cases

Validate that Oracle Fusion Supply Planning correctly collects items, on-hand balances, open supply and demand orders, forecasts, sourcing rules, bills of material, routings and calendars from source systems into the planning data store, covering both full and net-change collection, without assuming every data category is collected on every run.

Test ID	ORCL.SCM.PLAN.COLLECT
Application	Oracle Fusion Cloud
Product	SCM
Module	Supply Planning
Process	Collect Planning Data
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 collection of planning data — including items, on-hand balances, open supply and demand orders, forecasts, sourcing rules, bills of material, routings and calendars — from source systems into the Oracle Fusion Supply Planning data store, using a valid collection template ${COLLECTION_TEMPLATE}, without assuming that every data category is collected on every run.

The scenario should confirm that:

each selected data category is correctly collected into the planning data store as configured by the collection template
net-change collection correctly captures only records changed since the previous collection run
source system unavailability is correctly flagged rather than allowed to silently succeed
a collection run cannot be started while another collection job for the same template is already running
collected data is available for downstream plan generation once collection completes
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 collection of planning data as configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It does not cover generating a supply plan from the collected data, analyzing planning exceptions, or releasing planned orders, which are covered by the separate Run Supply Plan, Planning Exceptions and Release Planned Order scenarios in the same Supply Planning cluster.

When to Use This Test

Functional testing of planning data collection for a new Oracle Fusion SCM Supply Planning implementation
Regression testing of collection behavior after an Oracle quarterly update
UAT sign-off for planning analysts who rely on collected data to generate supply plans
Baseline case referenced by the Run Supply Plan, Demand Forecast and Supply Demand Balance scenarios within the same Supply Planning cluster
Diagnosing DATA_ERROR, CONFIGURATION_ERROR and INTEGRATION_ERROR conditions surfaced during planning data collection before escalating as a possible APPLICATION_ERROR

Where This Test Fits in the Supply Planning Process

Navigate to Supply Planning

→

Select Collection Template

→

Collect Planning Data

→

Run Supply Plan

→

Review Exceptions

→

Release Planned Orders

Collect Planning Data is the entry point of the Supply Planning scenario family and of the Plan-to-Produce business flow. Once planning data is collected, it is used to generate a supply plan, analyze exceptions and release planned orders — covered by the Run Supply Plan, Planning Exceptions and Release Planned Order scenarios in this same cluster. Exact data categories collected, collection type and validation depend on the collection template, source system configuration and customer-specific Oracle Fusion configuration.

Next Stage →

Run Supply Plan

Preconditions

The test user has appropriate Planning Analyst or Planning Administrator access to run planning data collection.
A valid collection template ${COLLECTION_TEMPLATE} is configured and active in the target Oracle Fusion environment.
Source systems referenced by the collection template, including ${SOURCE_SYSTEM}, are reachable and configured for collection.
The organization(s) ${ORGANIZATION} in which data is being collected are enabled for planning collection.
No other collection job for the same collection template is currently running.

Exact data categories available, collection options and validation messages may vary by Oracle Fusion implementation, collection template and customer-specific configuration. No single set of data categories should be assumed to be collected on every run.

Sample Test Data

Collection Template	${COLLECTION_TEMPLATE}
Organization	${ORGANIZATION}
Item	${ITEM}
Source System	${SOURCE_SYSTEM}
Collection Type	${COLLECTION_TYPE}
Job Status	${JOB_STATUS}
Data Category	${DATA_CATEGORY}
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 data category applies to every collection template — for example, bills of material and routings may not be relevant to a purely distribution-focused organization.

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 and Navigate to Supply Planning Sign in to Oracle Fusion using an authorised Supply Planning test user and navigate to the Supply Planning work area.	The Supply Planning work area opens successfully.
2	Navigate to the Collection Template Open the planning data collection template that defines which data categories and organizations are collected. ${COLLECTION_TEMPLATE}	The collection template opens and shows the configured collection options.
3	Select the Data Categories and Organizations to Collect Select the data categories and organizations to include in the collection run, as supported by the template. ${DATA_CATEGORY} / ${ORGANIZATION} Not every data category is collected on every run — the selection depends on the collection template and what is relevant to the target organization.	The selected data categories and organizations are accepted for the collection run.
4	Submit the Collection Run Submit the planning data collection run using the selected collection type, either full or net-change. ${COLLECTION_TYPE}	Oracle Fusion successfully submits the collection run without unexpected errors.
5	Monitor Job Status Monitor the collection job status until it completes, fails, or reports a partial exception. ${JOB_STATUS} A collection job already running for the same template should correctly block or queue a new run rather than starting a second, conflicting run.	The collection job status is visible and updates to a completed, errored or partially completed state.
6	Verify Collected Data Completeness and Error LogBusiness assertion Verify the completeness of the collected data for the selected categories and review any error log entries. This is the primary business assertion for the scenario — correctly and completely collected data is the expected pass condition, not merely a successful job submission.	The selected data categories are correctly collected into the planning data store, and any collection errors are logged rather than silently ignored.

Expected Results

Each selected data category is correctly collected into the planning data store as configured by the collection template.
Net-change collection correctly captures only records changed since the previous collection run.
Data and configuration validation errors, including an invalid collection template, are correctly enforced.
Source system unavailability is correctly flagged rather than allowed to silently succeed.
A concurrent collection run for the same template is correctly blocked or queued.
Collected data is available and complete for downstream supply plan generation.

Key Validation Checkpoints

Each selected data category correctly collected into the planning data store.
Net-change collection correctly captures only changed records.
Invalid collection template correctly rejected.
Source unavailability correctly flagged rather than silently succeeding.
Concurrent collection run correctly blocked or queued.
Unauthorized collection run correctly blocked.

Core Business Scenario

Collect Planning Data

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 Collect Planning Data business scenario. Jarvis AI can extend this scenario by generating additional data category, collection type 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 data category, source system or collection type combination. Jarvis uses the standard scenario as the foundation and generates relevant Positive, Negative and Security variations for the customer's environment — including net-change collection and unauthorized collection attempts. These generated variations are illustrative examples surfaced on this same page; they do not create additional public test-library pages.

From Standard Test to Executed Regression Pack

SCM

Oracle Fusion Cloud SCM product line.

Supply Planning

Functional area within SCM covering the Plan-to-Produce business flow.

Collect Planning Data

Process / scenario family covering collection of planning data into the planning data store.

Standard Test Scenarios

Reusable Collect Planning Data business process and automation logic.

DataVault Test Data

Provides approved, masked customer-specific test data and configuration — collection templates, source systems, organizations and data categories.

Jarvis Variations

Analyses the standard scenario together with available test data and generates relevant Positive, Negative and Security variations, without creating additional public test-library pages.

Regression Pack

Selected variations can be grouped into an executable suite.

Scheduled Execution

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

Failure Intelligence

Capture execution results, business assertions, screenshots/evidence and failure-category classification.

Rather than maintaining a separate test page for every possible data category, source system, collection type or security combination, SyntraFlow maintains one core Collect Planning Data scenario and allows Jarvis AI to generate data-category, collection-type and security-specific variations using the customer's available test data — without creating additional indexable pages.

AI-Generated Test Variations

The same Collect Planning Data 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

Collect item master data for planning
Collect on-hand balances, open supply orders and open demand orders
Collect sales order demand and forecast data
Collect sourcing rules
Collect bills of material and routings
Collect calendars and work days
Run net-change collection and verify collected data completeness

Negative Scenarios

Attempt collection using an invalid or misconfigured collection template
Attempt collection while a required source system is unavailable
Attempt to start a collection run while another collection job for the same template is already running
Encounter a partial collection failure across data categories
Attempt an unauthorized collection run without the required access

These are representative examples only. Negative-scenario behavior and available data category combinations can depend on the customer's Oracle Fusion configuration, collection templates, source systems and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every collection template, source system, data category and organization combination in a real Oracle Fusion SCM environment. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct Collect Planning Data scenarios relevant to the customer's actual implementation.

Standard Library Definition

Collection Template   ${COLLECTION_TEMPLATE}
Organization           ${ORGANIZATION}
Item                   ${ITEM}
Source System          ${SOURCE_SYSTEM}
Collection Type        ${COLLECTION_TYPE}
Job Status             ${JOB_STATUS}
Data Category          ${DATA_CATEGORY}
User Role              ${USER_ROLE}

DataVault

Collection Templates
  Configured collection templates and their selected data categories
Source Systems
  Source systems and organizations enabled for collection
Items
  Items in scope for planning collection
Data Categories
  Active data categories by collection template
Roles
  Roles enabled to run or configure planning collection

Jarvis AI Generates

Scenario 01 — Collect Item Master Data, Organization A
Scenario 02 — Collect On-Hand Balances, Organization B
Scenario 03 — Net-Change Collection Using Template X
Scenario 04 — Source System Unavailable for Forecast Data
Scenario 05 — Collection Job Already Running
Scenario 06 — Unauthorized User Attempts Data Collection
...

Collect Planning Data test data can include item, sourcing and organization information tied to supply chain configuration. The public Syntra Standard Test Library uses illustrative placeholder data only. Where DataVault is connected, customer-specific planning data used in testing remains 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 17 individual Collect Planning Data test scenarios spanning item, supply, demand, forecast and sourcing data collection, net-change collection and negative/security collection 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-COL-001	Collect Item Master Data	Positive	Item master data for ${ITEM} is collected from ${SOURCE_SYSTEM} into the planning data store for organization ${ORGANIZATION}.	SyntraFlow Ready
PLAN-COL-002	Collect On-Hand Balances	Positive	On-hand balance data for organization ${ORGANIZATION} is collected as part of collection template ${COLLECTION_TEMPLATE}.	SyntraFlow Ready
PLAN-COL-003	Collect Open Supply Orders	Positive	Open supply order data is collected for organization ${ORGANIZATION} using collection type ${COLLECTION_TYPE}.	SyntraFlow Ready
PLAN-COL-004	Collect Open Demand Orders	Positive	Open demand order data is collected for organization ${ORGANIZATION} as configured in ${COLLECTION_TEMPLATE}.	SyntraFlow Ready
PLAN-COL-005	Collect Sales Order Demand	Positive	Sales order demand data for item ${ITEM} is collected into the planning data store.	SyntraFlow Ready
PLAN-COL-006	Collect Forecast Data	Positive	Forecast data category ${DATA_CATEGORY} is collected from ${SOURCE_SYSTEM} for organization ${ORGANIZATION}.	SyntraFlow Ready
PLAN-COL-007	Collect Sourcing Rules	Positive	Sourcing rules applicable to item ${ITEM} and organization ${ORGANIZATION} are collected.	SyntraFlow Ready
PLAN-COL-008	Collect Bills of Material	Positive	Bill of material data for item ${ITEM} is collected as part of collection template ${COLLECTION_TEMPLATE}.	SyntraFlow Ready
PLAN-COL-009	Collect Routings	Positive	Routing data associated with item ${ITEM} is collected for organization ${ORGANIZATION}.	SyntraFlow Ready
PLAN-COL-010	Collect Calendars and Work Days	Positive	Calendar and work day data is collected for organization ${ORGANIZATION} to support plan generation.	SyntraFlow Ready
PLAN-COL-011	Net Change Collection	Positive	Collection type ${COLLECTION_TYPE} is set to net-change, and only records changed since the previous collection for ${DATA_CATEGORY} are collected.	SyntraFlow Ready
PLAN-COL-012	Invalid Collection Template	Negative	Collection is attempted using collection template ${COLLECTION_TEMPLATE} that is invalid or misconfigured.	SyntraFlow Ready
PLAN-COL-013	Source Data Unavailable	Negative	Collection is attempted while source system ${SOURCE_SYSTEM} is unavailable for data category ${DATA_CATEGORY}.	SyntraFlow Ready
PLAN-COL-014	Collection Job Already Running	Negative	A new collection run is submitted for collection template ${COLLECTION_TEMPLATE} while a prior collection job with status ${JOB_STATUS} is still running.	SyntraFlow Ready
PLAN-COL-015	Partial Collection Failure	Negative	Collection completes for some data categories but fails partway through for data category ${DATA_CATEGORY}.	SyntraFlow Ready
PLAN-COL-016	Verify Collected Data Completeness	Positive	Collected data for organization ${ORGANIZATION} is reviewed to confirm every selected data category ${DATA_CATEGORY} completed successfully.	SyntraFlow Ready
PLAN-COL-017	Unauthorized Collection Run	Negative/Security	A user with role ${USER_ROLE} lacking required access attempts to run collection template ${COLLECTION_TEMPLATE}.	SyntraFlow Ready

Automatically Expand Positive and Negative Planning Data Collection Coverage

Positive Testing

Jarvis generates scenarios using collection templates, data categories, organizations and sourcing configurations expected to successfully collect planning data in Oracle Fusion.

Valid Collection Template + Valid Data Category + Valid Organization → Data Collected

Negative Testing

Jarvis can also generate scenarios designed to exercise Oracle's validations around collection templates, source system availability, concurrency and security.

Invalid Collection Template → Expected Template Validation
Source Data Unavailable → Expected Error Flag, Not Silent Success
Collection Job Already Running → Expected Concurrency Block or Queue
Partial Collection Failure → Expected Error Logged Per Category
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 Collect Planning Data scenarios and group them into reusable execution packs.

SCM Supply Planning Collect Planning Data Regression Pack

Collect Item Master Data
Collect On-Hand Balances
Collect Open Supply Orders
Collect Forecast Data
Collect Sourcing Rules
Net Change Collection
Invalid Collection Template
Source Data Unavailable
Collection Job Already Running
Security Restriction — Unauthorized Collection 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 Collect Planning Data scenarios individually or as a batch. Users can schedule regression packs according to their planning collection cadence.

Once scheduled, SyntraFlow executes the selected Collect Planning Data 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 Collect Planning Data Regression Pack
Schedule	Quarterly Update Regression
Tests	17 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 and configure planning data collection is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that collection access behaves as expected for each role — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Planning Analyst	Run Planning Data Collection	Allowed	PASS
Planning Administrator	Configure Collection Template	Allowed	PASS
Unauthorized User	Attempts to Run Data Collection	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 Collect Planning Data scenario, available DataVault test data and expected business outcomes to generate additional Positive, Negative and Security coverage for the customer's environment — without creating additional public test-library pages for each variation.

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 — Collect Planning Data, 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 Data Categories and Organizations to Collect

May internally include

Open Collection Template → Expand Data Category List → Toggle Category Checkboxes → Select Organizations → Confirm Selections → Save Template Selection

Business Step

Monitor Job Status

May internally include

Open Scheduled Processes → Search Collection Job → Refresh Status → Open Job Log → Capture Status → Confirm Completion or Exception

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 job submission does not automatically prove the planning data was correctly and completely collected — 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, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically. For example: Planning Data Collection Failed — Likely category: INTEGRATION_ERROR — Evidence: Source system ${SOURCE_SYSTEM} unavailable for category ${DATA_CATEGORY} — Recommendation: Verify source system connectivity before rerunning collection. 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 Data Categories and Organizations to Collect	Pass	—
Submit the Collection Run	Pass	—
Verify Collected Data Completeness and Error Log	Pass	Pass

Related Supply Planning Tests

Collect Planning Data is the entry point of the Supply Planning cluster — explore the related plan generation and analysis scenarios below.

Run Supply Plan Demand Forecast Supply Demand Balance

Turn This Standard Test into Your Oracle SCM Collect Planning Data Regression Suite

Start with the Syntra Standard Collect Planning Data test, use DataVault to provide environment-specific test data, let Jarvis generate additional data category, collection type 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 the same data categories collected on every Collect Planning Data run?

No. Which data categories — items, on-hand balances, open supply and demand orders, forecasts, sourcing rules, bills of material, routings and calendars — are collected depends on how the collection template ${COLLECTION_TEMPLATE} is configured. This scenario is designed to validate collection as configured rather than assuming every data category is collected on every run.

What is the difference between net-change and full collection?

A full collection run collects the complete set of data for the selected categories and organizations. A net-change collection run, by contrast, is expected to capture only records changed since the previous collection. Both collection types are covered by this scenario, using the ${COLLECTION_TYPE} test data field.

What happens when a source system is unavailable during collection?

When a source system such as ${SOURCE_SYSTEM} is unavailable for a data category, the expected behavior is that Oracle Fusion flags the unavailability rather than silently completing the collection as if the data had been collected. This scenario is designed to verify that unavailability is correctly surfaced, not silently ignored.

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

SyntraFlow's evidence trail is designed to help classify a failure as DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — for example, an unreachable source system typically points to an INTEGRATION_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 planning data collection?

Access to run and configure planning data collection 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 Administrator and an unauthorized user — to confirm that collection access behaves as expected, without asserting a single universal Oracle security model.