Oracle ERP Testing Tool > Test Library > SCM > End-to-End SCM

Syntra Standard Journey Oracle Test Library

Oracle Fusion Demand-to-Supply Test Scenarios

Validate the complete Demand-to-Supply journey in Oracle Fusion SCM — demand signal, planning, supply decision (buy, make or transfer), supply creation and demand coverage — with emphasis on the planning engine correctly recommending and reconciling the right supply source for each demand signal, orchestrating rather than duplicating the individual Supply Planning, Procurement, Manufacturing and Inventory family pages this journey links to.

Test ID	ORCL.E2E.D2S
Application	Oracle Fusion Cloud
Product	SCM
Module	End-to-End SCM
Process	Demand-to-Supply
Business Flow	Plan-to-Produce
Scenario Type	End-to-End / Functional
Test Usage	Functional Testing / Regression Testing / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Standard Journey

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions across each Supply Planning, Procurement, Manufacturing and Inventory family page automatically while presenting the journey 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 94 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of this test is to validate the complete Demand-to-Supply journey in Oracle Fusion SCM — demand signal, planning, supply decision (buy, make or transfer), supply creation and demand coverage — with emphasis on the planning engine correctly recommending and reconciling the right supply source for each demand signal, without assuming a single universal supply-source recommendation applies to every item, rather than re-testing each stage's individual field-level validation, which is already covered on the linked Supply Planning, Procurement, Manufacturing and Inventory family pages this scenario orchestrates.

The scenario should confirm that:

the net demand quantity calculated from forecast, sales order or safety stock signals correctly drives the recommended supply quantity
the planning engine correctly recommends the configured supply source — buy, make or transfer — per item and organization, rather than assuming one universal source
the recommended supply source correctly creates the matching document type: purchase requisition, work order or transfer order
supplier and manufacturing lead-time constraints are correctly factored into supply feasibility against the required date
shortages, late supply and excess supply are correctly flagged rather than silently accepted
created supply correctly reduces the open net requirement, with pegging correctly linking demand to its covering supply document
unauthorized users are correctly blocked from creating a supply document at any stage of the journey

This scenario validates the hand-offs and cross-stage data integrity of the Demand-to-Supply journey in Oracle Fusion SCM TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the Run Supply Plan, Demand Forecast, Supply Demand Balance, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Requisition, Create Work Order and Create Transfer Order family pages — this page links to and orchestrates those live pages into an end-to-end journey.

When to Use This Test

Regression testing that net demand correctly drives the recommended supply source — buy, make or transfer — and that the created supply document matches the recommendation
Validating hand-offs across the linked Supply Planning, Procurement, Manufacturing and Inventory family pages — Run Supply Plan, Demand Forecast, Supply Demand Balance, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Requisition, Create Work Order and Create Transfer Order — rather than re-testing each page's individual field-level scenarios
UAT sign-off for planning, procurement, manufacturing and inventory teams who need confidence the full demand-to-supply journey works end-to-end, not just each transaction in isolation
Diagnosing cross-stage data mismatches, shortages, late supply or blocked supply creation before escalating as a possible APPLICATION_ERROR
Baseline orchestration scenario referenced when validating that the planning engine correctly reconciles demand signals with the right supply source across Oracle Fusion SCM

The Demand-to-Supply Journey

Demand Signal

→

Planning

→

Supply Decision

→

Buy / Make / Transfer

→

Supply Created

→

Demand Covered

This Demand-to-Supply scenario spans the full demand-signal-to-supply-source-decision journey across Supply Planning, Procurement, Manufacturing and Inventory within Oracle Fusion SCM, orchestrating the Run Supply Plan, Demand Forecast, Supply Demand Balance, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Requisition, Create Work Order and Create Transfer Order family pages rather than duplicating their individual scenario coverage. From supply creation, covered demand typically continues into downstream order fulfillment, production or further planning cycles.

Preconditions

The Supply Planning, Procurement, Manufacturing and Inventory family pages referenced by this journey — Run Supply Plan, Demand Forecast, Supply Demand Balance, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Requisition, Create Work Order and Create Transfer Order — are individually functional in the target Oracle Fusion SCM environment.
A valid item, organization, sourcing rule and supply plan are available and enabled for planning, procurement, manufacturing and inventory transfer.
Collected supply and demand data is current for the supply plan under test.
The test user holds the roles required to execute each stage of the journey, or alternate unauthorized-user personas are available for security testing.
Sourcing rules, supplier lead times, manufacturing lead times and safety stock levels are configured according to the target environment — this scenario does not assume a single universal supply-source recommendation applies to every item.

Exact sourcing rules, lead times, safety stock levels and supply-source recommendations vary by Oracle Fusion implementation and customer-specific configuration. This scenario validates that Oracle correctly enforces whatever configuration is in place at each hand-off, not a single universal rule.

Sample Test Data

Item	${ITEM}
Organization	${ORGANIZATION}
Quantity	${QUANTITY}
Planned Order	${PLANNED_ORDER}
Supply Source	${SUPPLY_SOURCE}
Required Date	${REQUIRED_DATE}
Plan Name	${PLAN_NAME}
Supplier	${SUPPLIER}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM TEST/UAT environment. Not every field applies to every journey variation — for example, supplier fields apply only to buy-recommendation scenarios and are not used for make or transfer scenarios.

Test Steps

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

#	User Action	Expected Result
1	Review the Demand Signal Review the demand signal — forecast, sales order or safety stock — driving net demand, referencing the standard Demand Forecast and Supply Demand Balance test scenarios. ${ITEM} / ${ORGANIZATION} / ${QUANTITY}	The demand signal is correctly identified and net demand is available for planning.
2	Run or Review the Supply Plan's Net Requirement Calculation Run or review the supply plan's net requirement calculation after netting existing supply, referencing the standard Run Supply Plan test scenario. ${PLAN_NAME} / ${ITEM} / ${QUANTITY}	Net demand is correctly calculated after netting on-hand, existing purchase orders, work orders and transfer supply.
3	Review the Recommended Supply Source Review the planning engine's recommended supply source — buy, make or transfer — for the net demand, referencing the standard Planned Orders and Planning Exceptions test scenarios. ${PLANNED_ORDER} / ${SUPPLY_SOURCE}	The recommended supply source correctly reflects the item's configured sourcing rule, rather than a single universal recommendation.
4	Create the Corresponding Supply Document Release the planned order and create the corresponding supply document — purchase requisition, work order or transfer order — referencing the standard Release Planned Order, Create Purchase Requisition, Create Work Order and Create Transfer Order test scenarios. ${PLANNED_ORDER} / ${SUPPLIER} / ${REQUIRED_DATE}	The supply document created matches the recommended source type and carries forward quantity and required date.
5	Verify Supply Covers the Net DemandBusiness assertion Compare the created supply document against the originating net demand. ${ITEM} / ${QUANTITY} / ${SUPPLY_SOURCE} This is a primary business assertion for the journey — reconciled quantity and correct pegging across demand, planning recommendation and supply document is the expected pass condition, not merely a successful transaction.	Created supply correctly reduces the open net requirement, with pegging correctly linking demand to its covering supply document.
6	Verify Planning Rerun Reflects the Updated BalanceBusiness assertion Rerun the supply plan after supply creation and review the updated supply/demand balance, referencing the standard Supply Demand Balance test scenario. ${PLAN_NAME} / ${ITEM} / ${REQUIRED_DATE} This is the final business assertion for the scenario — an updated, correctly reconciled supply/demand balance after rerun is the expected pass condition for the full journey.	Planning rerun correctly reflects the updated supply/demand balance, with the previously open requirement now covered.

Expected Results

The demand signal — forecast, sales order or safety stock — is correctly identified and net demand is available for planning.
Net demand is correctly calculated after netting on-hand, existing purchase orders, work orders and transfer supply.
The recommended supply source correctly reflects the item's configured sourcing rule — buy, make or transfer — rather than a single universal recommendation.
The created supply document matches the recommended source type and carries forward quantity and required date.
Created supply correctly reduces the open net requirement, with pegging correctly linking demand to its covering supply document.
Unauthorized supply document creation attempts are correctly blocked at any stage of the journey.

Key Validation Checkpoints

net demand correctly calculated after netting existing supply
the correct supply source type (buy/make/transfer) correctly recommended per configured sourcing rules
supply document correctly created matching the recommendation
lead-time constraints correctly factored into feasibility
shortages and late supply correctly flagged rather than silently accepted
planning rerun correctly reflects updated supply/demand balance
pegging correctly links demand to its covering supply document

Core Business Scenario

Demand-to-Supply

Journey Scenarios

26 Scenarios

Journey Stages

6 Stages

Linked Family Pages

9 Linked Pages

Test Data

DataVault-Driven

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Test with Jarvis AI

The Syntra Standard Test Library defines the core Demand-to-Supply journey as an orchestration across the Supply Planning, Procurement, Manufacturing and Inventory family pages within SCM. Jarvis AI extends this scenario by following the pipeline from SCM to Functional Area, Process/Scenario Family and Standard Test Scenarios, then combining it with DataVault test data to generate Jarvis Variations — organized as Positive, Negative, Boundary, Integration and Security categories — before they can be assembled into a Regression Pack and Scheduled Execution, with results surfaced through Failure Intelligence.

Teams do not need to manually stitch together demand signal, planning, supply-source-decision and supply-creation tests for every item, organization or exception path. Jarvis uses the standard journey as the foundation and generates relevant Positive, Negative, Boundary, Integration and Security variations for the customer's environment — including inventory shortages, late supply, demand spikes and supplier or manufacturing lead-time constraints — since correctly enforced supply-source decisions between stages, not just individually correct transactions, is what this journey scenario proves. These Jarvis-generated variations do not create additional public SEO pages, and this page itself does not duplicate the individual scenario coverage already tested on the family pages it links to; this page remains the canonical reference for the end-to-end journey.

From Standard Test to Executed Regression Pack

SCM

Oracle Fusion SCM product area.

Functional Area — End-to-End SCM

Cross-module orchestration functional area spanning Supply Planning, Procurement, Manufacturing and Inventory within SCM.

Process / Scenario Family — Demand-to-Supply

The Demand-to-Supply journey spanning demand signal through planning, supply decision and supply creation.

Standard Test Scenario — Demand-to-Supply

Reusable end-to-end journey definition orchestrating the Supply Planning, Procurement, Manufacturing and Inventory family pages.

Customer DataVault

Provides approved customer-specific test data and configuration required for journey generation — Items, Organizations, Sourcing Rules, Suppliers and Plans.

Jarvis Variations

Analyses the standard journey together with available test data and generates Positive, Negative, Boundary, Integration and Security variations. These variations do not create additional public test-library pages.

Regression Pack

Selected journey 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 exceptions, classified into likely failure categories.

Rather than re-testing every demand signal, planned order, purchase requisition, work order and transfer order field individually — already covered on their respective family pages — SyntraFlow maintains one core Demand-to-Supply journey scenario, with 26 example end-to-end scenarios documented below, and allows Jarvis AI to generate item, organization and security-specific journey variations using the customer's available test data. These variations do not create additional public SEO pages.

AI-Generated Test Variations

The same Demand-to-Supply 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 End-to-End.

Positive Scenarios

Journey validating forecast, sales order and safety stock demand signals correctly drive net demand
Journey validating on-hand and existing supply (purchase order, work order or transfer) correctly cover demand without unnecessary new supply
Journey validating buy, make and transfer recommendations correctly reflect the item's configured sourcing rule
Journey validating multiple supply sources are correctly reconciled for a single demand signal
Journey validating supplier and manufacturing lead-time constraints are correctly factored into supply feasibility
Journey validating excess supply is correctly detected and flagged for rebalancing
Journey validating a planning rerun and supply/demand pegging correctly reflect the updated balance

Negative Scenarios

Journey where an inventory shortage is correctly flagged rather than silently accepted
Journey where late supply against the required date is correctly flagged
Journey where a demand spike or decrease is correctly detected and re-planned rather than left unresolved
Journey where a cancelled demand correctly removes the open requirement rather than leaving stale supply

These are representative examples only. Journey behavior, supply-source recommendations and available hand-off paths can depend on the customer's Oracle Fusion configuration, sourcing rules and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every item, organization, sourcing rule and exception path in a real Oracle Fusion Demand-to-Supply journey. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct journey scenarios relevant to the customer's actual implementation.

Standard Library Definition

Item                 ${ITEM}
Organization         ${ORGANIZATION}
Quantity             ${QUANTITY}
Planned Order        ${PLANNED_ORDER}
Supply Source        ${SUPPLY_SOURCE}
Required Date        ${REQUIRED_DATE}
Plan Name            ${PLAN_NAME}
Supplier             ${SUPPLIER}

DataVault

Items
  Active items with sourcing rules by organization
Organizations
  Planning, procurement, manufacturing and inventory organizations
Supply Plans
  Collected supply and demand data by plan
Suppliers
  Approved suppliers and lead times by item
Security
  Roles authorised at each stage of the journey

Jarvis AI Generates

Scenario 01 — Standard Journey, ${ITEM}
Scenario 02 — Buy Recommendation via ${SUPPLIER}
Scenario 03 — Make Recommendation in ${ORGANIZATION}
Scenario 04 — Inventory Shortage Flagged
Scenario 05 — Supplier Lead-Time Constraint
Scenario 06 — Unauthorized User Attempts Release
...

Demand, planning and supply document data used in Demand-to-Supply testing are masked or synthetic through Syntra DataVault — never real production data. The public Syntra Standard Test Library uses illustrative placeholder data only, and where DataVault is connected, customer-specific item, organization and sourcing-rule dimensions remain within the customer's controlled SyntraFlow environment and access model, protected according to DataVault's data masking policies. See /datavault/data-masking/ for details.

Example Test Variations

This catalog spans 26 end-to-end Demand-to-Supply journey scenarios validating demand-signal-to-supply-source-decision continuity across Supply Planning, Procurement, Manufacturing and Inventory, plus negative/boundary journey testing. These are illustrative, not separate indexable pages — the canonical page for all of them remains this one.

ID	Variation	Type	Key Difference	Execution
E2E-D2S-001	Forecast Demand	Positive	Net demand for ${ITEM} in ${ORGANIZATION} is generated from forecast demand within supply plan ${PLAN_NAME}; the planning engine correctly calculates net requirement quantity ${QUANTITY}.	SyntraFlow Ready
E2E-D2S-002	Sales Order Demand	Positive	Net demand for ${ITEM} is generated from an open sales order rather than forecast; the planning engine correctly nets the sales-order quantity ${QUANTITY} into the required supply.	SyntraFlow Ready
E2E-D2S-003	Safety Stock Demand	Positive	Net demand for ${ITEM} in ${ORGANIZATION} is generated from a safety stock shortfall; the planning engine correctly calculates the replenishment quantity ${QUANTITY} needed to restore the safety stock level.	SyntraFlow Ready
E2E-D2S-004	On-Hand Covers Demand	Positive	Net demand for ${ITEM} is fully covered by existing on-hand inventory in ${ORGANIZATION}; the planning engine correctly recommends no new supply for quantity ${QUANTITY}.	SyntraFlow Ready
E2E-D2S-005	Existing PO Covers Demand	Positive/Integration	Net demand for ${ITEM} is covered by an existing open purchase order rather than a new recommendation; the planning engine correctly nets the open PO quantity against ${QUANTITY} of demand, referencing Create Purchase Requisition.	SyntraFlow Ready
E2E-D2S-006	Existing Work Order Covers Demand	Positive/Integration	Net demand for ${ITEM} is covered by an existing open work order in ${ORGANIZATION}; the planning engine correctly nets the open work order quantity against ${QUANTITY} of demand, referencing Create Work Order.	SyntraFlow Ready
E2E-D2S-007	Transfer Supply Covers Demand	Positive/Integration	Net demand for ${ITEM} is covered by an existing open transfer order into ${ORGANIZATION}; the planning engine correctly nets the in-transit transfer quantity against ${QUANTITY} of demand, referencing Create Transfer Order.	SyntraFlow Ready
E2E-D2S-008	Buy Recommendation	Positive/Integration	Net demand for ${ITEM} generates a buy recommendation on planned order ${PLANNED_ORDER}; releasing it correctly creates a purchase requisition for supplier ${SUPPLIER}, referencing Create Purchase Requisition.	SyntraFlow Ready
E2E-D2S-009	Make Recommendation	Positive/Integration	Net demand for ${ITEM} generates a make recommendation on planned order ${PLANNED_ORDER}; releasing it correctly creates a work order in ${ORGANIZATION}, referencing Create Work Order.	SyntraFlow Ready
E2E-D2S-010	Transfer Recommendation	Positive/Integration	Net demand for ${ITEM} generates a transfer recommendation on planned order ${PLANNED_ORDER}; releasing it correctly creates a transfer order into ${ORGANIZATION}, referencing Create Transfer Order.	SyntraFlow Ready
E2E-D2S-011	Multiple Supply Sources	Positive/Integration	Net demand for ${ITEM} across multiple organizations is correctly recommended with different supply sources per organization — buy for one, make for another — rather than a single universal recommendation for ${ITEM}.	SyntraFlow Ready
E2E-D2S-012	Supplier Lead-Time Constraint	Positive/Boundary	A buy recommendation for ${ITEM} from supplier ${SUPPLIER} is correctly evaluated against the supplier's configured lead time relative to required date ${REQUIRED_DATE}, confirming feasibility is correctly factored into the recommendation.	SyntraFlow Ready
E2E-D2S-013	Manufacturing Lead-Time Constraint	Positive/Boundary	A make recommendation for ${ITEM} in ${ORGANIZATION} is correctly evaluated against the item's configured manufacturing lead time relative to required date ${REQUIRED_DATE}, confirming feasibility is correctly factored into the recommendation.	SyntraFlow Ready
E2E-D2S-014	Excess Supply	Positive/Boundary	Existing supply for ${ITEM} in ${ORGANIZATION} exceeds net demand quantity ${QUANTITY}; the planning engine correctly detects and flags the excess supply condition for rebalancing rather than leaving it unflagged.	SyntraFlow Ready
E2E-D2S-015	Inventory Shortage	Negative/Boundary	Available supply for ${ITEM} in ${ORGANIZATION} is insufficient to cover net demand quantity ${QUANTITY} by required date ${REQUIRED_DATE}; the planning engine correctly flags the shortage rather than silently understating the requirement.	SyntraFlow Ready
E2E-D2S-016	Late Supply	Negative/Boundary	Recommended supply for ${ITEM} on planned order ${PLANNED_ORDER} is due after required date ${REQUIRED_DATE}; the planning engine correctly flags the late-supply condition rather than silently accepting it as on-time.	SyntraFlow Ready
E2E-D2S-017	Demand Spike	Positive/Boundary	A sudden increase in demand for ${ITEM} in ${ORGANIZATION} is correctly detected against supply plan ${PLAN_NAME}, and the planning engine correctly recalculates net demand quantity ${QUANTITY} to reflect the spike.	SyntraFlow Ready
E2E-D2S-018	Demand Decrease	Positive/Boundary	A sudden decrease in demand for ${ITEM} in ${ORGANIZATION} is correctly detected against supply plan ${PLAN_NAME}, and the planning engine correctly recalculates net demand quantity ${QUANTITY} downward to reflect the decrease.	SyntraFlow Ready
E2E-D2S-019	Planned Order Reschedule	Positive	A change in required date for ${ITEM} correctly generates a reschedule recommendation for planned order ${PLANNED_ORDER} to align with the updated required date ${REQUIRED_DATE}.	SyntraFlow Ready
E2E-D2S-020	Expedite Supply	Positive	A demand pull-in for ${ITEM} correctly generates an expedite recommendation for planned order ${PLANNED_ORDER}, moving the recommended due date earlier to meet required date ${REQUIRED_DATE}.	SyntraFlow Ready
E2E-D2S-021	Defer Supply	Positive	A demand push-out for ${ITEM} correctly generates a defer recommendation for planned order ${PLANNED_ORDER}, moving the recommended due date later to align with required date ${REQUIRED_DATE}.	SyntraFlow Ready
E2E-D2S-022	Cancel Excess Supply	Positive	Excess supply for ${ITEM} in ${ORGANIZATION} correctly generates a cancel recommendation for planned order ${PLANNED_ORDER} rather than leaving unneeded supply in the plan.	SyntraFlow Ready
E2E-D2S-023	Demand Cancelled	Negative	The originating sales order or forecast demand for ${ITEM} is cancelled; the planning engine correctly removes the open net requirement rather than leaving stale demand for quantity ${QUANTITY}.	SyntraFlow Ready
E2E-D2S-024	Planning Rerun	Positive	After supply document creation for ${ITEM}, rerunning supply plan ${PLAN_NAME} correctly reflects the updated supply/demand balance, with the previously open requirement for quantity ${QUANTITY} now shown as covered.	SyntraFlow Ready
E2E-D2S-025	Supply/Demand Pegging	Positive/Integration	The created supply document for ${ITEM} — whether purchase requisition, work order or transfer order — is correctly pegged to the originating net demand, confirming the document reference chain from ${PLANNED_ORDER} through to the supply document.	SyntraFlow Ready
E2E-D2S-026	End-to-End Exception Resolution	Positive/Integration	A planning exception raised for ${ITEM} — shortage, late supply or reschedule — is correctly resolved by creating or adjusting the recommended supply document, and a subsequent planning rerun confirms the exception is correctly cleared.	SyntraFlow Ready

Positive and Negative Journey Testing

Positive Testing

Jarvis generates journey scenarios using demand signal, item, organization and sourcing-rule combinations expected to successfully complete the Demand-to-Supply journey in Oracle Fusion.

Correctly Recommended Buy/Make/Transfer Source + Feasible Lead Time + Created Supply Document → Net Demand Covered

Negative Testing

Jarvis can also generate journey scenarios designed to exercise Oracle's validations around shortages, late supply, demand changes and supply-creation security at any stage of the hand-off.

Inventory Shortage → Expected Flag Rather Than Silent Acceptance
Late Supply Against Required Date → Expected Flag Rather Than Silent Acceptance
Demand Cancelled After Planning → Expected Removal of Open Requirement
Unauthorized User Attempts Supply Document Creation → Expected Access Restriction

A negative end-to-end scenario passes when Oracle correctly enforces the expected data, configuration or security rule at any stage of the journey.

Scenario	Oracle Outcome	Test Result
Valid journey data at every stage	Journey completes end-to-end	PASS
Data mismatch between stages	Validation or warning occurs	PASS
Missing required upstream document	Validation occurs	PASS
Unauthorized user at any stage	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

Users can select generated Demand-to-Supply journey scenarios and group them into reusable execution packs.

SCM End-to-End Demand-to-Supply Regression Pack

Forecast Demand
Sales Order Demand
Buy Recommendation
Make Recommendation
Transfer Recommendation
Supplier Lead-Time Constraint
Inventory Shortage
Late Supply
Planning Rerun
Supply/Demand Pegging

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

Once scheduled, SyntraFlow executes the selected Demand-to-Supply journey scenarios unattended and records the outcome of each stage hand-off and business assertion.

Run immediatelyNightly regressionWeekly regressionBefore releaseAfter configuration changesAfter environment refreshQuarterly Oracle update testingPre-UAT validation

Pack	SCM End-to-End Demand-to-Supply Regression Pack
Schedule	Quarterly Update Regression
Tests	26 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 journey scenario, its business steps, the underlying automation actions across each Supply Planning, Procurement, Manufacturing and Inventory family page, 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

DataVault Journey Persona

This persona groups the linked-entity dimensions that must stay consistent across the Demand-to-Supply journey as DataVault-supplied test data flows from the demand signal through to the created supply document.

Persona: Standard Demand-to-Supply Planning Journey

Item	${ITEM}
Organization	${ORGANIZATION}
Demand Source	${DEMAND_SOURCE}
Net Demand Quantity	${QUANTITY}
Supply Source	${SUPPLY_SOURCE}
Planned Order	${PLANNED_ORDER}
Requisition	${REQUISITION}
Work Order	${WORK_ORDER}
Transfer Order	${TRANSFER_ORDER}
Required Date	${REQUIRED_DATE}
Plan Name	${PLAN_NAME}

Keeping these dimensions linked across DataVault-supplied test data lets Jarvis generate journey variations that remain internally consistent from demand signal through to whichever supply document — requisition, work order or transfer order — the recommendation correctly produces.

Security & Approval Variations

Access to each stage of the Demand-to-Supply journey — reviewing recommendations, creating a supply document across buy, make or transfer, or resolving exceptions — is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations to confirm that access behaves as expected at each stage — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Planning Analyst	Review Demand and Supply Recommendations	Allowed	PASS
Planning Manager	Create Supply Document from Recommendation	Allowed	PASS
Unauthorized User	Attempts to Create Supply Document Without Role	Access prevented	PASS

Cross-Stage Business Assertions

These assertions validate that quantity, document linkage and date data remain consistent as the journey crosses from Supply Planning into Procurement, Manufacturing or Inventory.

QUANTITY_CONTINUITYDOCUMENT_LINKAGEDATE_CONTINUITY

Stage Transition	Assertion	Example	Status
Demand -> Supply Decision	Net Demand Qty = Recommended Supply Qty	Net demand ${QUANTITY} for ${ITEM} = recommended supply qty on ${PLANNED_ORDER}	PASS
Supply Decision -> Supply Created	Recommended source correctly creates the matching document type (PO, work order or transfer order)	Buy recommendation for ${ITEM} creates requisition ${REQUISITION}	PASS
Supply Created -> Demand Covered	Created supply correctly reduces the open net requirement	Supply from ${SUPPLY_SOURCE} reduces net requirement for ${ITEM} to zero	PASS

Illustrative example using DataVault variables — not hard-coded production values.

Stage-by-Stage Execution Evidence

This example shows execution status recorded at each stage of one illustrative Demand-to-Supply journey run, including how a failure at one stage blocks downstream stages.

1Demand Signal

PASS

2Planning

PASS

3Supply Decision

PASS

4Buy / Make / Transfer

FAIL

5Supply Created

NOT RUN

6Demand Covered

NOT RUN

Failed Stage

Buy / Make / Transfer

Upstream Passed

Downstream Blocked

Illustrative example run — not a live execution.

Journey Failure Model

This example shows how a failure at the Buy / Make / Transfer stage is classified and reported without blocking visibility into which upstream stages already passed.

Journey: Demand-to-Supply Failed Stage: Buy / Make / Transfer

Upstream Status

Demand Signal	PASS
Planning	PASS
Supply Decision	PASS

Scenario

Supplier Lead-Time Constraint

Expected Result

Recommended supply source is created within the item's required lead time.

Actual Result

Supplier lead time of 21 days exceeds the required date, leaving demand uncovered by the need date.

Failure Classification

CONFIGURATION_ERROR

Blocking Impact / Downstream Status

Demand remains uncovered by the required date; downstream consuming orders at risk.

Recommended Action

Verify supplier lead-time setup, consider an alternate supply source, or expedite where the planning rules permit.

Do not label as an Oracle application defect without eliminating data, configuration, security, automation, environment and integration causes first.

Additional Named Regression Packs

This journey can be executed as one pack or split into focused packs covering specific behavior.

Demand-to-Supply Standard Pack

Forecast Demand
Buy Recommendation
Make Recommendation
Transfer Recommendation
Supply/Demand Pegging

Demand-to-Supply Exception Pack

Inventory Shortage
Late Supply
Demand Spike
Supplier Lead-Time Constraint
Manufacturing Lead-Time Constraint

Demand-to-Supply Rebalancing Pack

Planned Order Reschedule
Expedite Supply
Defer Supply
Cancel Excess Supply
Planning Rerun

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 Demand-to-Supply journey, available DataVault test data and expected business outcomes to generate additional Positive, Negative, Boundary, Integration and Security coverage for the customer's environment, following the SCM → Functional Area → Scenario Family → Standard Test Scenarios → DataVault Test Data → Jarvis Variations → Regression Pack → Scheduled Execution → Failure Intelligence pipeline. These variations do not create additional public SEO pages, and this page itself does not duplicate the individual scenario coverage already tested on the Supply Planning, Procurement, Manufacturing and Inventory family pages it links to and orchestrates.

Generate

Positive, Negative, Boundary, Integration and Security journey variations.

Parameterize

Use relevant test data from DataVault.

Assemble

Build reusable regression packs.

Execute

Run journey scenarios autonomously across family pages.

Schedule

Execute unattended test batches.

Validate

Evaluate expected cross-stage 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 — Demand-to-Supply, 6 Business Steps

↓

DataVault — Customer-Specific Test Data

↓

Jarvis AI — Generate Positive + Negative + Boundary + Integration + Security Variations

↓

Regression Pack — Select Relevant Journey Coverage

↓

SyntraFlow Execution — Each Journey Variation

↓

Detailed UI Actions Across Family Pages

↓

Cross-Stage Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Review the Recommended Supply Source

May internally include

Open Planned Orders → Search Planned Order → Review Recommended Source Type → Confirm Sourcing Rule Applied → Confirm Quantity/Date

Business Step

Create the Corresponding Supply Document

May internally include

Open Release Planned Order → Confirm Order Type → Release → Open Create Purchase Requisition/Work Order/Transfer Order → Confirm Document Created → Confirm Cross-Reference to Planned Order

What SyntraFlow Captures Per Run

Cross-page journey orchestrationParameterised input valuesReusable navigation across family pagesAutomation action traceScreenshots / evidence captureExecution timingBusiness assertions across stagesEnvironment-independent test data

Action Status vs. Business Validation

A successful UI interaction at any single stage does not automatically prove the end-to-end journey is correct — this is illustrative of how SyntraFlow separates action success from cross-stage business validation; it does not reflect a specific live execution. When a hand-off fails, SyntraFlow's evidence trail is designed to help a tester classify the likely cause across an 8-category taxonomy — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR — without asserting the cause automatically. For example: Supply Document Not Created Within Lead Time — Likely category: CONFIGURATION_ERROR — Evidence: Supplier lead time for ${ITEM} exceeds ${REQUIRED_DATE} — Recommendation: Verify supplier lead-time setup or consider an alternate supply source. A failure should never be labeled as an Oracle defect without first eliminating data, configuration, security, automation, environment and integration causes.

Step	Action Status	Business Validation
Create the Corresponding Supply Document	Pass	—
Verify Supply Covers the Net Demand	Pass	Pass
Verify Planning Rerun Reflects the Updated Balance	Pass	Pass

Related End-to-End Journeys & Family Tests

Demand-to-Supply orchestrates the Supply Planning, Procurement, Manufacturing and Inventory family pages into a single journey, and links directly to the individual family pages it references.

Plan-to-Produce (End-to-End)Plan-to-Procure (End-to-End)Run Supply Plan

Turn This Standard Journey into Your Oracle SCM Demand-to-Supply Regression Suite

Start with the Syntra Standard Demand-to-Supply journey, use DataVault to provide environment-specific test data, let Jarvis generate additional item, organization and security variations, and execute the resulting regression pack automatically with SyntraFlow.

Automate with SyntraFlow Explore SCM End-to-End 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 SCM End-to-End Test Library Run Supply Plan Demand Forecast Supply Demand Balance Planned Orders Release Planned Order Planning Exceptions Create Purchase Requisition Create Work Order Create Transfer Order Syntra DataVault DataVault Data Masking

Frequently Asked Questions

How does this Demand-to-Supply page differ from the individual Run Supply Plan, Create Purchase Requisition and other family pages?

This page does not duplicate the atomic scenario coverage already tested individually on the Run Supply Plan, Demand Forecast, Supply Demand Balance, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Requisition, Create Work Order and Create Transfer Order family pages, which span Supply Planning, Procurement, Manufacturing and Inventory. Instead, it describes and links to those live pages, showing how they connect into an end-to-end demand-to-supply flow, and adds scenarios that specifically test the hand-offs and cross-stage data integrity between them — for example, whether the recommended supply source correctly creates the matching document type, and whether created supply correctly covers the originating net demand.

What does the Journey Failure Model on this page show?

The Journey Failure Model shows a representative example of how a failure at one stage — for example, Buy / Make / Transfer — is captured alongside which upstream stages already passed, the expected versus actual result, a failure classification, and the downstream impact. It is illustrative, not a live execution, and is designed to help a tester quickly understand where in the journey a hand-off broke down.

Does this scenario assume a single supply-source recommendation — buy, make or transfer — applies to every item?

No. The recommended supply source depends on the item's configured sourcing rule, organization and available supply, and is never treated as a universal recommendation. This scenario validates that the planning engine correctly recommends and reconciles whatever supply source is configured for each item, rather than assuming one recommendation type applies across the board.

What does supply/demand pegging validate in this journey?

Pegging validates that a created supply document — a purchase requisition, work order or transfer order — is correctly cross-referenced back to the specific net demand that generated it, rather than merely existing as an unrelated open document. This confirms the document reference chain from demand signal through planning recommendation to the covering supply document.

What do the failure-intelligence categories mean for a failed Demand-to-Supply journey test?

When a hand-off between stages fails, SyntraFlow's evidence trail helps a tester classify the likely cause across an 8-category taxonomy — DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION, INTEGRATION_ERROR, AUTOMATION_ERROR, ENVIRONMENT_ERROR or APPLICATION_ERROR. A failure should never be labeled as an Oracle defect without first eliminating data, configuration, security, automation, environment and integration causes.

How does security testing work across a multi-stage journey like this?

Access to each stage — reviewing recommendations, creating a supply document across buy, make or transfer, or resolving exceptions — is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations across the journey, such as a planning analyst or planning manager versus an unauthorized user, to confirm that access behaves as expected at each stage, without asserting a single universal Oracle security model.