Oracle ERP Testing Tool > Test Library > Regression Packs

Syntra Regression Pack Oracle Test Library

Oracle Fusion Plan-to-Cash Regression Pack

The flagship, broadest-scope regression pack in the SyntraFlow library — 28 regression-critical scenario IDs spanning SCM Planning, Manufacturing, Inventory, Order Management and Financials AR, composed into one executable, schedulable pack that validates continuity across the full demand-to-cash flow. This pack is deliberately distinct from, and cross-linked to, the narrower single-process Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys and the SCM Critical and O2C Regression module packs it draws from.

Test ID	ORCL.REGRESSION.PLAN2CASH
Application	Oracle Fusion Cloud
Product	Regression
Module	Regression
Process	Plan-to-Cash Regression
Business Flow	Plan-to-Cash Regression Pack
Scenario Type	Regression Pack / Composition
Test Usage	Functional Testing / Regression Testing / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Regression Pack

Note on test design: SyntraFlow executes the detailed Oracle Fusion UI interactions across each referenced Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable family page automatically while presenting the pack as business-readable test steps for documentation, review and reporting. This scenario is presented as 7 business-readable test steps; SyntraFlow's automation executes approximately 148 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of the Plan-to-Cash Regression Pack is to give release and QA teams a single, repeatable set of 28 flagship scenario IDs — spanning SCM Planning, Manufacturing, Inventory, Order Management and Financials Accounts Receivable — that can be run together ahead of a quarterly update, patch or configuration change, rather than re-running the narrower Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys, or the SCM Critical, Financials Critical and O2C Regression module packs, individually every cycle. This is the broadest cross-module pack in the SyntraFlow library and is designed to be the top-of-funnel release gate that references, rather than replaces, that deeper coverage.

The scenario should confirm that:

the 28 referenced REG-P2CASH scenario IDs are correctly composed from their underlying Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable family pages
demand, quantity, document and amount data correctly carry across the full Demand, Supply Planning, Buy/Make, Inventory, Sales Order, Fulfillment, Billing and Receipt flow
negative and exception scenarios — component shortage, planning delay, fulfillment failure, billing failure, cash application failure — are correctly enforced across the composed pack rather than only within a single module
a batch execution of the pack correctly records pass/fail status per scenario, with failures classified into a likely root-cause category and traced to the specific stage that broke
the pack can be scheduled and re-run on a defined cadence, such as ahead of a quarterly Oracle update, as the single broadest release-readiness signal across SCM and Financials

This pack does not duplicate the individual field-level scenario coverage already tested on the Demand Forecast, Run Supply Plan, Planned Orders, Release Planned Order, Purchase Orders, Work Orders, Completions, On-Hand, Sales Orders, Fulfillment, AR Billing and AR Receipts family pages, nor the detailed step-by-step coverage on the Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journey pages, nor the SCM Critical, Financials Critical and O2C Regression module packs. It references 28 regression-critical scenario IDs by ID and composes them into one executable, schedulable, cross-module pack with cross-stage continuity assertions. For full step-by-step detail on any single process, see the linked end-to-end journeys; for narrower module regression, see the linked module-critical packs.

When to Use This Test

Regression testing ahead of an Oracle quarterly update, patch or configuration change across SCM Planning, Manufacturing, Inventory, Order Management and Financials AR in a single pack
Release sign-off requiring one flagship, cross-module evidence set rather than re-running the Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys, or the SCM Critical, Financials Critical and O2C Regression packs, separately every cycle
Validating Demand-to-Cash continuity — for example net demand correctly driving supply creation, completed finished goods correctly increasing on-hand, reserved quantity carried into shipment, and invoiced amount carried into receipt application — rather than re-testing each family page's individual field-level scenarios
Scheduled nightly or pre-release batch execution with Failure Intelligence classification when a scenario or hand-off fails anywhere across the four-module flow
The top-level composition reference when a release decision needs one broad, defensible signal spanning planning, production, fulfillment and cash application, with drill-down into the narrower journeys and module packs it references

Plan-to-Cash Regression Pack Composition

Demand

→

Supply Planning

→

Buy / Make

→

Inventory

→

Sales Order

→

Fulfillment

→

Billing

→

Receipt

The Plan-to-Cash Regression Pack composes 28 scenarios across this eight-stage Demand-to-Cash flow, referencing the Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable family pages rather than duplicating their individual scenario coverage. This flagship pack is broader than, and cross-linked to, the narrower Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys — each of which documents a single segment of this flow in full step-by-step detail — and the SCM Critical and O2C Regression module packs. It adds cross-stage continuity assertions spanning all four modules, DataVault-driven test data, batch scheduling and Failure Intelligence classification on top of the referenced scenarios.

Preconditions

The Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable family pages referenced by this pack's 28 scenario IDs are individually functional in the target Oracle Fusion SCM and Financials environment.
A valid item, organization, sourcing rule, supplier, customer and supply plan are available and enabled across the referenced planning, manufacturing, inventory, order management and AR scenario areas.
The test user holds the roles required to execute each referenced scenario across all four modules, or alternate unauthorized-user personas are available for security testing.
DataVault test data bindings for the referenced scenario IDs are current for the environment under test, and remain internally consistent from item and organization through to customer and AR transaction.
Sourcing rules, supplier and manufacturing lead times, reservation policy, AR billing rules and receipt application logic are configured according to the target environment — this pack does not assume a single universal configuration applies to every scenario.

Exact sourcing, manufacturing, reservation, billing and receipt application behavior may vary by Oracle Fusion implementation and customer-specific configuration. This pack validates that Oracle correctly enforces whatever configuration is in place for each referenced scenario and hand-off, not a single universal rule.

Sample Test Data

Item	${ITEM}
Organization	${ORGANIZATION}
Quantity	${QUANTITY}
Plan Name	${PLAN_NAME}
Planned Order	${PLANNED_ORDER}
Supplier	${SUPPLIER}
Purchase Order	${PURCHASE_ORDER}
Work Order	${WORK_ORDER}
Customer	${CUSTOMER}
Sales Order	${SALES_ORDER}
Shipment	${SHIPMENT}
AR Transaction	${AR_TRANSACTION}
Receipt	${RECEIPT}
Required Date	${REQUIRED_DATE}

Sample values are illustrative placeholder tokens. Replace with valid data from the target Oracle Fusion SCM and Financials TEST/UAT environments. Not every field applies to every pack scenario — for example, ${SUPPLIER} and ${PURCHASE_ORDER} apply only to buy-path scenarios and are not used for make-path or pure AR scenarios.

Test Steps

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

#	User Action	Expected Result
1	Select Pack Scenarios Select the 28 REG-P2CASH regression-critical scenario IDs from the Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable family pages into the Plan-to-Cash Regression Pack. REG-P2CASH-001 … REG-P2CASH-028	All 28 referenced scenario IDs are correctly included in the pack composition across all four modules.
2	Bind DataVault Test Data Bind DataVault-supplied test data — items, organizations, suppliers, customers and plan context — to each scenario ID in the pack. ${ITEM} / ${ORGANIZATION} / ${CUSTOMER}	Each scenario in the pack correctly resolves its required test data before execution.
3	Execute the Pack in Batch Execute all 28 scenarios in the pack as a single scheduled or on-demand batch run against the target Oracle Fusion environment. Batch Mode	Each scenario in the pack runs to completion and records a pass, fail or exception status.
4	Review Demand-to-Supply and Supply-to-Inventory ContinuityBusiness assertion Review the cross-stage assertions confirming net demand correctly drives supply creation, and that received or completed supply correctly increases on-hand for ${ITEM}. ${PLANNED_ORDER} / ${WORK_ORDER} / ${QUANTITY} Validates the SCM Planning-to-Production boundary of the pack.	Net demand-driven supply and its resulting on-hand increase reconcile correctly across the Supply Planning, Manufacturing and Inventory family pages.
5	Review Inventory-to-Fulfillment and Shipment-to-Billing ContinuityBusiness assertion Review the cross-stage assertions confirming on-hand availability correctly supports order reservation and shipment, and that shipped quantity correctly generates the AR transaction. ${SALES_ORDER} / ${SHIPMENT} / ${AR_TRANSACTION} Validates the Inventory-to-Order Management-to-Financials boundary of the pack.	Reserved, picked and shipped quantity reconcile correctly through to the AR transaction generated for ${CUSTOMER}.
6	Review Billing-to-Cash ContinuityBusiness assertion Review the cross-stage assertion confirming the invoiced amount correctly carries into receipt creation and application, reducing the customer's open balance. ${AR_TRANSACTION} / ${RECEIPT} This is a primary business assertion for the pack — reconciled amount from invoice through applied receipt is the expected pass condition, not merely a successful transaction.	Applied receipt amount correctly reconciles against the AR transaction, with the customer's open balance correctly reduced.
7	Classify Any Failures Across the Four-Module FlowBusiness assertion Where a scenario or hand-off fails, classify the likely root cause using the 8-category failure taxonomy and identify which upstream stages already passed and which downstream stages remain blocked. Failure Intelligence This is the final business assertion for the pack — correct stage-level failure attribution across SCM and Financials is the expected pass condition for the full flow.	Failed scenarios are correctly classified and traced to the specific stage and module boundary at which the hand-off broke, without asserting the cause automatically.

Expected Results

All 28 referenced REG-P2CASH scenario IDs are correctly composed from their underlying family pages across Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable.
Net demand correctly drives the recommended and created supply document (planned purchase order or planned work order).
Received or completed supply correctly increases on-hand for the finished good.
Reserved, picked and shipped quantity correctly carries into the AR transaction.
Invoiced amount correctly carries into receipt creation and application, reducing the customer's open balance.
Component shortage, planning delay, fulfillment failure, billing failure and cash application failure scenarios are correctly flagged rather than silently accepted.
Unauthorized access attempts at any referenced stage are correctly blocked.
A batch execution of the pack correctly records pass/fail per scenario, with failures classified and traced to the specific stage that broke.

Key Validation Checkpoints

all 28 REG-P2CASH scenario IDs correctly included in the pack composition
net demand correctly drives recommended and created supply across buy and make paths
received or completed supply correctly increases on-hand for the finished good
reserved, picked and shipped quantity correctly carried into the AR transaction
invoiced amount correctly carried into applied receipt and customer balance
component shortage, planning delay, fulfillment, billing and cash application failures correctly flagged rather than silently accepted
unauthorized access correctly blocked at any referenced stage
batch execution correctly records pass/fail and traces failures to the specific stage and module boundary

Core Business Scenario

Plan-to-Cash Regression

Pack Scenarios

28 Scenarios

Flow Stages

8 Stages

Linked Family Pages

15 Linked Pages

Test Data

DataVault-Driven

Automation

SyntraFlow Ready

Jarvis AI

Go Beyond the Standard Pack with Jarvis AI

The Syntra Standard Test Library defines the Plan-to-Cash Regression Pack as a composition of 28 regression-critical scenario IDs across the Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable family pages within SCM and Financials. Jarvis AI extends this flagship pack by following the pipeline from SCM/Financials 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 this Regression Pack and Scheduled Execution, with results surfaced through Failure Intelligence.

Teams do not need to manually assemble which planning, production, fulfillment and AR scenarios matter most for a release. Jarvis uses this flagship pack composition as the foundation and generates relevant Positive, Negative, Boundary, Integration and Security variations for the customer's environment — including component shortages, planning delays, fulfillment and billing failures, and cash-application exceptions — since correctly enforced continuity across all four modules, not just individually correct transactions, is what this pack 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 references, nor the end-to-end journeys and module packs it links to.

From Standard Test to Executed Regression Pack

SCM / Financials

Oracle Fusion SCM Planning, Manufacturing, Inventory, Order Management and Financials AR product areas.

Functional Areas — Supply Planning, Manufacturing, Inventory, Order Management, AR Billing, AR Receipts

The six coverage areas this flagship pack composes scenarios from across the Demand-to-Cash flow.

Process / Scenario Family — Plan-to-Cash Regression

28 regression-critical scenario IDs selected as high-risk, high-frequency transactions spanning demand through cash.

Standard Test Scenarios

Reusable scenario definitions maintained individually on each referenced family page and on the Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys.

Customer DataVault

Provides approved customer-specific test data and configuration required for pack execution — Items, Organizations, Suppliers, Customers and Plans.

Jarvis Variations

Analyses the referenced scenarios 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

The 28 selected scenario IDs are grouped into this executable, schedulable Plan-to-Cash Regression Pack, with Smoke, Continuity-Only and Negative-Only sub-packs available.

Scheduled Execution

Execute immediately or schedule the pack for unattended batch execution.

Failure Intelligence

Capture execution results, business assertions, screenshots/evidence and exceptions, classified into likely failure categories and traced to the specific stage.

Rather than re-testing every demand signal, planned order, work order, sales order, shipment, AR transaction and receipt field individually — already covered on their respective family pages and the Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys — SyntraFlow maintains one flagship Plan-to-Cash Regression Pack composed of 28 regression-critical scenario IDs, documented in the browser below, and allows Jarvis AI to generate item, organization, customer and security-specific pack variations using the customer's available test data. These variations do not create additional public SEO pages.

AI-Generated Test Variations

The same Plan-to-Cash Regression Pack 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 Plan-to-Cash Cross-Module Process Regression.

Positive Scenarios

Pack validating forecast and sales-order demand correctly drives net demand into the supply plan
Pack validating buy and make recommendations correctly create the matching purchase order or work order
Pack validating received components and completed finished goods correctly increase on-hand
Pack validating on-hand availability correctly supports sales order reservation, pick and ship
Pack validating shipped quantity correctly generates the AR transaction at matching quantity
Pack validating invoiced amount correctly reduces the customer's open balance on receipt application
Pack validating end-to-end stage traceability across all eight flow stages for a single item and customer

Negative Scenarios

Pack scenario where a component shortage is correctly flagged rather than silently accepted
Pack scenario where a planning delay against the required date is correctly flagged
Pack scenario where a fulfillment failure is correctly flagged rather than silently confirmed
Pack scenario where a billing failure is correctly flagged rather than an AR transaction silently created
Pack scenario where a cash application failure is correctly flagged rather than a receipt silently applied
Pack scenario where an unauthorized user is correctly blocked from creating or approving a transaction at any referenced stage

These are representative examples only. Pack behavior, sourcing rules, reservation policy and available transaction paths can depend on the customer's Oracle Fusion configuration and security — not every Oracle configuration behaves identically.

Generated Using Your DataVault Test Data

Generic test data rarely represents every item, organization, supplier, customer and exception path referenced across a real Oracle Fusion Plan-to-Cash Regression Pack run. Where connected, Jarvis can use approved test data available through Syntra DataVault to construct pack scenarios relevant to the customer's actual implementation.

Standard Library Definition

Item                 ${ITEM}
Organization         ${ORGANIZATION}
Quantity             ${QUANTITY}
Plan Name            ${PLAN_NAME}
Planned Order        ${PLANNED_ORDER}
Supplier             ${SUPPLIER}
Purchase Order       ${PURCHASE_ORDER}
Work Order           ${WORK_ORDER}
Customer             ${CUSTOMER}
Sales Order          ${SALES_ORDER}
Shipment             ${SHIPMENT}
AR Transaction       ${AR_TRANSACTION}
Receipt              ${RECEIPT}
Required Date        ${REQUIRED_DATE}

DataVault

Items
  Active items with sourcing rules and organization assignments
Organizations
  Planning, manufacturing, inventory, order management and billing organizations
Supply Plans
  Collected supply and demand data by plan
Suppliers
  Approved suppliers and lead times by item
Customers
  Active customers with receipt methods and credit terms
Security
  Roles authorised at each referenced scenario stage across all four modules

Jarvis AI Generates

Scenario 01 — Forecast Demand for ${ITEM}
Scenario 02 — Buy Recommendation via ${SUPPLIER}
Scenario 03 — Manufacture Finished Good in ${ORGANIZATION}
Scenario 04 — Ship ${SALES_ORDER} for ${CUSTOMER}
Scenario 05 — Apply ${RECEIPT} to ${AR_TRANSACTION}
Scenario 06 — Unauthorized User Attempts Receipt Application
...

Demand, planning, production, order, billing and receipt data used in Plan-to-Cash Regression Pack 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, supplier and customer 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 the 28 scenario IDs composed into the Plan-to-Cash Regression Pack — the flagship, broadest-scope pack in the SyntraFlow library — across Supply Planning, Procurement, Manufacturing, Inventory, Order Management, AR Billing and AR Receipts, plus cross-stage continuity and negative coverage. Each row references the real family page — or the relevant end-to-end journey — the underlying scenario is defined on; this pack does not duplicate that field-level or step-by-step definition.

ID	Variation	Type	Key Difference	Execution
REG-P2CASH-001	Forecast demand	Planning	Regression-critical instance validating that forecast demand for ${ITEM} in ${ORGANIZATION} correctly generates net demand within supply plan ${PLAN_NAME}. Source: Demand Forecast (/oracle-erp-testing-tool/test-library/scm/supply-planning/demand-forecast/)	Illustrative
REG-P2CASH-002	Sales-order demand	Planning	Regression-critical instance validating that an open sales order for ${ITEM} correctly generates net demand within supply plan ${PLAN_NAME}, distinct from forecast-driven demand. Source: Sales Orders (/oracle-erp-testing-tool/test-library/scm/order-management/sales-orders/)	Illustrative
REG-P2CASH-003	Run supply plan	Planning	Regression-critical instance validating that running supply plan ${PLAN_NAME} correctly nets on-hand and existing supply against demand for ${ITEM} in ${ORGANIZATION}. Source: Run Supply Plan (/oracle-erp-testing-tool/test-library/scm/supply-planning/run-supply-plan/)	Illustrative
REG-P2CASH-004	Planned purchase order	Planning	Regression-critical instance validating that a buy recommendation for ${ITEM} correctly generates planned order ${PLANNED_ORDER} sourced from ${SUPPLIER}. Source: Planned Orders (/oracle-erp-testing-tool/test-library/scm/supply-planning/planned-orders/)	Illustrative
REG-P2CASH-005	Planned work order	Planning	Regression-critical instance validating that a make recommendation for ${ITEM} correctly generates planned order ${PLANNED_ORDER} for production in ${ORGANIZATION}. Source: Planned Orders (/oracle-erp-testing-tool/test-library/scm/supply-planning/planned-orders/)	Illustrative
REG-P2CASH-006	Release planned supply	Planning	Regression-critical instance validating that releasing planned order ${PLANNED_ORDER} correctly creates the matching purchase order or work order document type. Source: Release Planned Order (/oracle-erp-testing-tool/test-library/scm/supply-planning/release-planned-order/)	Illustrative
REG-P2CASH-007	Receive purchased component/item	Inventory	Regression-critical instance validating that receiving ${QUANTITY} of ${ITEM} against purchase order ${PURCHASE_ORDER} correctly increases on-hand in ${ORGANIZATION}. Source: Purchase Orders (/oracle-erp-testing-tool/test-library/scm/procurement/purchase-orders/)	Illustrative
REG-P2CASH-008	Manufacture finished good	Manufacturing	Regression-critical instance validating that completing work order ${WORK_ORDER} for ${ITEM} correctly consumes component supply and reports the finished-good quantity ${QUANTITY}. Source: Completions (/oracle-erp-testing-tool/test-library/scm/manufacturing/completions/)	Illustrative
REG-P2CASH-009	Finished goods on-hand validation	Inventory	Regression-critical instance validating that the completed finished-good quantity for ${ITEM} correctly reflects as available on-hand in ${ORGANIZATION}. Source: On-Hand (/oracle-erp-testing-tool/test-library/scm/inventory-management/on-hand/)	Illustrative
REG-P2CASH-010	Create sales order	Order	Regression-critical instance validating that a sales order for ${CUSTOMER} with ${ITEM} at ${QUANTITY} is correctly created as ${SALES_ORDER}. Source: Sales Orders (/oracle-erp-testing-tool/test-library/scm/order-management/sales-orders/)	Illustrative
REG-P2CASH-011	Schedule	Order	Regression-critical instance validating that scheduling ${SALES_ORDER} correctly assigns a ship date consistent with ${REQUIRED_DATE} and available supply. Source: Sales Orders (/oracle-erp-testing-tool/test-library/scm/order-management/sales-orders/)	Illustrative
REG-P2CASH-012	Reserve	Order	Regression-critical instance validating that reserving on-hand supply for ${SALES_ORDER} correctly allocates ${QUANTITY} of ${ITEM} against the order. Source: Fulfillment (/oracle-erp-testing-tool/test-library/scm/order-management/fulfillment/)	Illustrative
REG-P2CASH-013	Pick	Order	Regression-critical instance validating that picking the reserved quantity for ${SALES_ORDER} correctly relieves the reservation ahead of ship confirm. Source: Fulfillment (/oracle-erp-testing-tool/test-library/scm/order-management/fulfillment/)	Illustrative
REG-P2CASH-014	Ship	Order	Regression-critical instance validating that ship confirm for ${SALES_ORDER} correctly generates shipment ${SHIPMENT} at the picked quantity. Source: Fulfillment (/oracle-erp-testing-tool/test-library/scm/order-management/fulfillment/)	Illustrative
REG-P2CASH-015	Generate AR transaction	Billing	Regression-critical instance validating that shipment ${SHIPMENT} correctly generates AR transaction ${AR_TRANSACTION} for ${CUSTOMER} at matching quantity and amount. Source: AR Billing (/oracle-erp-testing-tool/test-library/financials/accounts-receivable/billing/)	Illustrative
REG-P2CASH-016	Create customer receipt	Billing	Regression-critical instance validating that a customer receipt ${RECEIPT} for ${CUSTOMER} is correctly created against the open balance of ${AR_TRANSACTION}. Source: AR Receipts (/oracle-erp-testing-tool/test-library/financials/accounts-receivable/receipts/)	Illustrative
REG-P2CASH-017	Apply receipt	Billing	Regression-critical instance validating that applying ${RECEIPT} to ${AR_TRANSACTION} correctly reduces ${CUSTOMER}'s open AR balance. Source: AR Receipts (/oracle-erp-testing-tool/test-library/financials/accounts-receivable/receipts/)	Illustrative
REG-P2CASH-018	Demand-to-supply continuity	Continuity	Regression-critical instance validating that net demand for ${ITEM} correctly drives the recommended and created supply document, carried across planning through release. Source: Demand-to-Supply End-to-End Journey (/oracle-erp-testing-tool/test-library/scm/end-to-end/demand-to-supply/)	Illustrative
REG-P2CASH-019	Supply-to-inventory continuity	Continuity	Regression-critical instance validating that received or completed supply for ${ITEM} correctly increases on-hand, carried across production through inventory. Source: Make-to-Order End-to-End Journey (/oracle-erp-testing-tool/test-library/scm/end-to-end/make-to-order/)	Illustrative
REG-P2CASH-020	Inventory-to-fulfillment continuity	Continuity	Regression-critical instance validating that on-hand availability for ${ITEM} correctly supports reservation, pick and ship for ${SALES_ORDER}. Source: Order-to-Fulfillment End-to-End Journey (/oracle-erp-testing-tool/test-library/scm/end-to-end/order-to-fulfillment/)	Illustrative
REG-P2CASH-021	Shipment-to-billing continuity	Continuity	Regression-critical instance validating that shipped quantity on ${SHIPMENT} correctly carries into AR transaction ${AR_TRANSACTION} at matching quantity. Source: Order-to-Fulfillment End-to-End Journey (/oracle-erp-testing-tool/test-library/scm/end-to-end/order-to-fulfillment/)	Illustrative
REG-P2CASH-022	Billing-to-cash continuity	Continuity	Regression-critical instance validating that the invoiced amount on ${AR_TRANSACTION} correctly carries into applied receipt ${RECEIPT} and reduces ${CUSTOMER}'s open balance. Source: AR Billing (/oracle-erp-testing-tool/test-library/financials/accounts-receivable/billing/) and AR Receipts (/oracle-erp-testing-tool/test-library/financials/accounts-receivable/receipts/)	Illustrative
REG-P2CASH-023	Component shortage negative test	Negative	Regression-critical negative instance validating that an insufficient component quantity for ${ITEM} against purchase order ${PURCHASE_ORDER} is correctly flagged as a shortage rather than silently received. Source: Purchase Orders (/oracle-erp-testing-tool/test-library/scm/procurement/purchase-orders/)	Illustrative
REG-P2CASH-024	Planning delay scenario	Negative	Regression-critical negative instance validating that recommended supply for ${ITEM} due after ${REQUIRED_DATE} is correctly flagged as a planning delay rather than silently accepted. Source: Run Supply Plan (/oracle-erp-testing-tool/test-library/scm/supply-planning/run-supply-plan/)	Illustrative
REG-P2CASH-025	Fulfillment failure scenario	Negative	Regression-critical negative instance validating that a failed ship confirm for ${SALES_ORDER} is correctly flagged rather than a shipment silently generated. Source: Fulfillment (/oracle-erp-testing-tool/test-library/scm/order-management/fulfillment/)	Illustrative
REG-P2CASH-026	Billing failure scenario	Negative	Regression-critical negative instance validating that a failed AR transaction generation for shipment ${SHIPMENT} is correctly flagged rather than silently skipped, leaving the shipment uninvoiced. Source: AR Billing (/oracle-erp-testing-tool/test-library/financials/accounts-receivable/billing/)	Illustrative
REG-P2CASH-027	Cash application failure scenario	Negative	Regression-critical negative instance validating that a receipt ${RECEIPT} that cannot be matched to an open AR transaction is correctly flagged rather than silently applied. Source: AR Receipts (/oracle-erp-testing-tool/test-library/financials/accounts-receivable/receipts/)	Illustrative
REG-P2CASH-028	End-to-end stage traceability	Continuity	Regression-critical instance validating that a single item and customer can be traced across all eight stages of the flow — demand signal through supply, production, inventory, order, fulfillment, billing and receipt — with correct document linkage at each hand-off. Source: Demand-to-Supply End-to-End Journey (/oracle-erp-testing-tool/test-library/scm/end-to-end/demand-to-supply/), Make-to-Order End-to-End Journey (/oracle-erp-testing-tool/test-library/scm/end-to-end/make-to-order/) and Order-to-Fulfillment End-to-End Journey (/oracle-erp-testing-tool/test-library/scm/end-to-end/order-to-fulfillment/)	Illustrative

Positive and Negative Pack Testing

Positive Testing

Jarvis generates pack scenarios using item, organization, supplier and customer combinations expected to successfully complete each referenced scenario and its cross-stage continuity check across the full Demand-to-Cash flow in Oracle Fusion.

Correctly Forecast/Sales-Order Demand → Supply Created (Buy/Make) → Received/Completed → Reserved → Shipped → AR Transaction → Receipt Applied → Customer Balance Reduced

Negative Testing

Jarvis can also generate pack scenarios designed to exercise Oracle's validations around component shortages, planning delays, fulfillment failures, billing failures, cash-application failures and unauthorized access at any referenced stage.

Component Shortage → Expected Flag Rather Than Silent Receipt
Planning Delay Against Required Date → Expected Flag Rather Than Silent Acceptance
Fulfillment Failure → Expected Flag Rather Than Silent Ship Confirm
Billing Failure → Expected Flag Rather Than Silent AR Transaction Creation
Cash Application Failure → Expected Flag Rather Than Silent Receipt Match
Unauthorized User Attempts Supply Release or Receipt Application → 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 data at every referenced stage across all four modules	Pack scenario completes end-to-end	PASS
Data mismatch between composed stages	Validation or warning occurs	PASS
Missing required upstream document (supply, shipment or invoice)	Validation occurs	PASS
Unauthorized user at any referenced stage	Access prevented	PASS
Unexpected application exception	Unexpected failure	FAIL

Turn AI-Generated Variations into a Regression Pack

The Plan-to-Cash Regression Pack is the flagship, broadest-scope pack in the SyntraFlow regression library — it is explicitly distinct from and cross-linked to the narrower single-process Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys, and to the module-scoped SCM Critical, Financials Critical and O2C Regression packs. Users can select generated Plan-to-Cash scenarios and group them into this reusable, cross-module execution pack, or use one of the smaller named sub-packs below for a faster, narrower run.

Plan-to-Cash Regression Pack

Forecast Demand
Run Supply Plan
Manufacture Finished Good
Create Sales Order
Ship
Generate AR Transaction
Apply Receipt
End-to-End Stage Traceability

Add Selected to Regression Pack(coming soon)Run Now(coming soon)Schedule(coming soon)Export Evidence(coming soon)

Run On-Demand or Schedule Automated Batch Execution

SyntraFlow can execute the Plan-to-Cash Regression Pack's 28 scenarios individually or as a batch. Users can schedule the pack, or any of its named sub-packs, according to their release or testing cycle.

Once scheduled, SyntraFlow executes the Plan-to-Cash Regression Pack's scenarios unattended and records the outcome of each scenario and cross-stage business assertion across all four modules.

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

Pack	Plan-to-Cash Regression Pack
Schedule	Quarterly Update Regression
Tests	28 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 pack into a scenario, its business steps, the underlying automation actions across each referenced Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable 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 composite persona groups the linked-entity dimensions that must stay consistent across the Plan-to-Cash Regression Pack as DataVault-supplied test data flows from demand and supply planning through production, inventory, order fulfillment, billing and receipt application.

Persona: Plan-to-Cash Regression Tester

Item	${ITEM}
Organization	${ORGANIZATION}
Quantity	${QUANTITY}
Plan Name	${PLAN_NAME}
Planned Order	${PLANNED_ORDER}
Supplier	${SUPPLIER}
Purchase Order	${PURCHASE_ORDER}
Work Order	${WORK_ORDER}
Customer	${CUSTOMER}
Sales Order	${SALES_ORDER}
Shipment	${SHIPMENT}
AR Transaction	${AR_TRANSACTION}
Receipt	${RECEIPT}
Required Date	${REQUIRED_DATE}

Keeping these dimensions linked across DataVault-supplied test data lets Jarvis generate pack variations that remain internally consistent from demand signal and supply planning through to whichever referenced scenario — production, inventory, order fulfillment, AR billing or receipt application — the regression pack composes.

Security & Approval Variations

Access to each stage referenced by this pack — reviewing or releasing planned supply, receiving components, completing a work order, creating a sales order, shipping, creating an AR transaction, or applying a receipt — is controlled by Oracle Fusion's security configuration, which varies by customer. Jarvis can generate representative persona-based variations across all four modules to confirm that access behaves as expected — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Procurement Buyer	Review Planned Purchase Order Recommendation and Release to Purchase Order	Allowed	PASS
Procurement Approver	Approve and Release a Planned Work Order for Production	Allowed	PASS
Finance AP Specialist	Attempt to Create or Adjust an AR Transaction Without an AR Billing Role	Access prevented	PASS
Finance AP Manager	Attempt to Apply a Customer Receipt Without an AR Role	Access prevented	PASS
Unauthorized User	Attempts to Release Planned Supply or Ship a Sales Order Without the Required Role	Access prevented	PASS

Cross-Stage Business Assertions

These assertions validate that quantity, document linkage, date and amount data remain consistent as the flow crosses from SCM Planning into Manufacturing, Inventory, Order Management and Financials AR.

QUANTITY_CONTINUITYDOCUMENT_LINKAGEDATE_CONTINUITYAMOUNT_CONTINUITY

Stage Transition	Assertion	Example	Status
Demand -> Supply Planning	Net Demand Qty = Recommended Supply Qty	Net demand ${QUANTITY} for ${ITEM} = recommended supply qty on ${PLANNED_ORDER}	PASS
Supply Planning -> Buy / Make	Recommended source correctly creates the matching document type (purchase order or work order)	Buy recommendation for ${ITEM} creates ${PURCHASE_ORDER}; make recommendation creates ${WORK_ORDER}	PASS
Buy / Make -> Inventory	Received or completed Qty correctly increases on-hand	Completion of ${WORK_ORDER} for ${ITEM} correctly increases on-hand in ${ORGANIZATION}	PASS
Inventory -> Sales Order	On-hand availability correctly supports reservation for ${SALES_ORDER}	On-hand ${QUANTITY} of ${ITEM} in ${ORGANIZATION} correctly reserves against ${SALES_ORDER}	PASS
Sales Order -> Fulfillment	Reserved Qty = Shipped Qty (or correctly flagged as partial)	Reservation of ${QUANTITY} for ${ITEM} on ${SALES_ORDER} correctly relieves at ship confirm for ${SHIPMENT}	PASS
Fulfillment -> Billing	Shipped Qty = AR Transaction Qty	Shipment ${SHIPMENT} correctly generates ${AR_TRANSACTION} at matching quantity for ${CUSTOMER}	PASS
Billing -> Receipt	Invoice Amount = Applied Receipt Amount (full or partial)	${RECEIPT} correctly applies against the open balance of ${AR_TRANSACTION}	PASS

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

Stage-by-Stage Execution Evidence

This example shows illustrative execution status recorded at each real stage of the Demand-to-Cash flow in one representative Plan-to-Cash Regression Pack batch run, including how a failure at one stage blocks downstream stages.

1Demand

PASS

2Supply Planning

PASS

3Buy / Make

PASS

4Inventory

PASS

5Sales Order

PASS

6Fulfillment

PASS

7Billing

FAIL

8Receipt

NOT RUN

Failed Stage

Billing

Upstream Passed

Downstream Blocked

Illustrative example run — not a live execution.

Journey Failure Model

This example shows how a failure at the Billing stage — after six upstream stages spanning three modules already passed — is classified and reported without blocking visibility into where in the flow the hand-off broke down.

Journey: Plan-to-Cash Regression Pack Failed Stage: Billing

Upstream Status

Demand	PASS
Supply Planning	PASS
Buy / Make	PASS
Inventory	PASS
Sales Order	PASS
Fulfillment	PASS

Scenario

Billing Failure Scenario (REG-P2CASH-026)

Expected Result

Shipment ${SHIPMENT} correctly generates AR transaction ${AR_TRANSACTION} for ${CUSTOMER} at the shipped quantity and amount.

Actual Result

No AR transaction was generated for ${SHIPMENT}; the shipped quantity remains uninvoiced.

Failure Classification

INTEGRATION_ERROR

Blocking Impact / Downstream Status

The Receipt stage remains blocked; ${CUSTOMER} cannot be correctly invoiced or collected against for the shipped quantity, despite demand, supply, production, inventory, order and fulfillment all completing correctly.

Recommended Action

Verify the AR auto-invoice or shipment-to-billing interface program and related integration setup, and escalate only after eliminating data, configuration, security, automation and environment causes.

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.

Plan-to-Cash Smoke

Forecast Demand
Run Supply Plan
Create Sales Order
Generate AR Transaction
Apply Receipt

Plan-to-Cash Continuity Only

Demand-to-Supply Continuity
Supply-to-Inventory Continuity
Inventory-to-Fulfillment Continuity
Shipment-to-Billing Continuity
Billing-to-Cash Continuity
End-to-End Stage Traceability

Plan-to-Cash Negative Only

Component Shortage Negative Test
Planning Delay Scenario
Fulfillment Failure Scenario
Billing Failure Scenario
Cash Application Failure Scenario

Understand Why a Test Failed

SyntraFlow execution evidence can help distinguish business-data failures, configuration issues, automation problems and potential application defects.

DataConfigurationSecurityAutomationApplicationEnvironmentExpected Validation

Jarvis Failure Intelligence — Coming Soon

From Business Scenario to Execution Evidence

Business teams get readable test documentation; automation teams retain detailed execution traceability.

Standard Business Scenario

AI-Generated Variation

Regression Pack

Business Test Step

Automation Actions

Business Assertion

Screenshot / Evidence

Execution Result

Meet Jarvis — SyntraFlow's AI Testing Engine

Jarvis extends the Syntra Standard Test Library by analysing the Plan-to-Cash Regression Pack's 28 referenced scenarios, 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/Financials → 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 family pages it references, nor the end-to-end journeys and module packs it links to.

Generate

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

Parameterize

Use relevant test data from DataVault.

Assemble

Build and maintain this reusable flagship regression pack and its sub-packs.

Execute

Run pack scenarios autonomously across referenced family pages spanning four modules.

Schedule

Execute unattended test batches.

Validate

Evaluate expected cross-stage business outcomes across the full Demand-to-Cash flow.

How SyntraFlow Automates This Test

The Standard Test defines the scenario; DataVault, Jarvis AI and SyntraFlow's execution engine take it from a single reusable business definition to executed, evidenced regression coverage.

Standard Library — Plan-to-Cash Regression, 28 Referenced Scenarios

↓

DataVault — Customer-Specific Test Data

↓

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

↓

Regression Pack — Select Relevant Scenario Coverage

↓

SyntraFlow Execution — Each Pack Scenario

↓

Detailed UI Actions Across Referenced Family Pages

↓

Cross-Stage Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Execute the Pack in Batch

May internally include

Open Regression Pack → Select Plan-to-Cash Regression → Confirm 28 Scenario IDs → Run Now / Schedule → Confirm Batch Started

Business Step

Review Billing-to-Cash Continuity

May internally include

Open Batch Results → Select Scenario → Review Cross-Stage Assertion Rows → Confirm Amount Continuity → Confirm Status

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 batch run does not automatically prove every cross-stage hand-off across all four modules 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 scenario in the pack 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. 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
Execute the Pack in Batch	Pass	—
Review Billing-to-Cash Continuity	Pass	Pass
Classify Any Failures Across the Four-Module Flow	Pass	Pass

Related Regression Packs & End-to-End Journeys

The Plan-to-Cash Regression Pack composes the Supply Planning, Procurement, Manufacturing, Inventory, Order Management and Accounts Receivable family pages into one flagship, cross-module pack, and links directly to the individual family pages, the narrower Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys, and the SCM Critical and O2C Regression module packs it references.

Demand-to-Supply (End-to-End Journey)Make-to-Order (End-to-End Journey)Order-to-Fulfillment (End-to-End Journey)Regression Packs

Turn This Standard Pack into Your Oracle Plan-to-Cash Regression Suite

Start with the Syntra Standard Plan-to-Cash Regression Pack, use DataVault to provide environment-specific test data, let Jarvis generate additional item, customer and security variations, and execute the resulting pack automatically with SyntraFlow.

Automate with SyntraFlow Explore the Demand-to-Supply End-to-End Journey

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

Regression Packs Demand-to-Supply (End-to-End Journey)Make-to-Order (End-to-End Journey)Supply Planning Manufacturing Accounts Receivable SCM Critical Regression Pack O2C Regression Pack

Frequently Asked Questions

How does this Plan-to-Cash Regression Pack differ from the Demand-to-Supply, Make-to-Order and Order-to-Fulfillment end-to-end journeys?

Each of those end-to-end journey pages documents one segment of the flow — demand through supply decision, supply through production, and order through fulfillment — in full step-by-step detail. This pack is the broadest, flagship composition: it spans all the way from demand signal through supply, production, inventory, order fulfillment, billing and cash application, referencing 28 regression-critical scenario IDs drawn from those journeys' underlying family pages rather than duplicating their step-by-step content. For full step-by-step detail on any single segment, see the linked end-to-end journey.

How does this pack differ from the SCM Critical, Financials Critical and O2C Regression packs?

The SCM Critical and Financials Critical packs are module-scoped regression packs, and the O2C Regression pack covers the narrower Order-to-Cash segment. The Plan-to-Cash Regression Pack is the flagship, cross-module composition that spans SCM Planning, Manufacturing, Inventory, Order Management and Financials AR in one pack, explicitly cross-linked to and distinct from those narrower packs — use the narrower packs for module- or segment-focused regression, and this pack for the broadest single release-readiness signal.

How does this pack differ from the individual Demand Forecast, Work Orders, Sales Orders, AR Billing and other family pages?

This page does not duplicate the atomic scenario coverage already tested individually on the Demand Forecast, Run Supply Plan, Planned Orders, Release Planned Order, Purchase Orders, Work Orders, Completions, On-Hand, Sales Orders, Fulfillment, AR Billing and AR Receipts family pages. Instead, it references 28 regression-critical scenario IDs drawn from those pages and composes them into one executable, schedulable pack with cross-stage continuity assertions spanning all four modules.

What do the smaller named packs — Plan-to-Cash Smoke, Continuity Only and Negative Only — offer that the full 28-scenario pack doesn't?

They let a team run a faster, narrower slice of this flagship pack when the full 28-scenario batch isn't warranted — a quick smoke check across each module, a continuity-only run focused purely on the cross-stage hand-offs, or a negative-only run focused on shortage, delay and failure scenarios — while still referencing the same underlying REG-P2CASH scenario IDs rather than duplicating them.

What does the Cross-Stage Business Assertions section show?

It shows illustrative examples of quantity, document, date and amount data carried correctly along the Demand → Supply Planning → Buy/Make → Inventory → Sales Order → Fulfillment → Billing → Receipt flow — for example that shipped quantity correctly generates the AR transaction, and that invoice amount correctly carries into applied receipt. This is representative, not a live execution.

What do the failure-intelligence categories mean for a failed Plan-to-Cash Regression Pack run?

When a scenario or hand-off fails anywhere across the four-module flow, 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 — and identify which upstream stages already passed and which downstream stages remain blocked. A failure should never be labeled as an Oracle defect without first eliminating data, configuration, security, automation, environment and integration causes.