Oracle ERP Testing Tool > Test Library > Regression Packs

Syntra Regression Pack Oracle Test Library

Oracle Fusion SCM Critical Regression Pack

The SCM Critical Regression Pack composes 24 high-risk, high-frequency Oracle Fusion SCM scenarios spanning Procurement, Inventory, Order Management, Manufacturing, Product Management and Supply Planning into a single reusable regression suite, referencing rather than duplicating the individual family pages each scenario ID is drawn from, with cross-area continuity assertions, DataVault-driven test data, scheduling and Failure Intelligence classification layered on top.

Test ID	ORCL.REGRESSION.SCM.CRITICAL
Application	Oracle Fusion Cloud
Product	Regression
Module	Regression Packs
Process	SCM Critical Regression
Business Flow	Cross-Module SCM Regression
Scenario Type	Regression Pack / Composition
Test Usage	Regression Testing / Release Validation / UAT
Priority	High
Automation	SyntraFlow Ready
Library	Syntra Regression Pack

Note on test design: These business steps describe running the composed SCM Critical Regression Pack itself — selecting scenario IDs, binding test data, executing the batch and classifying results — not the detailed field-level steps of each of the 24 referenced scenarios, which are documented individually on their family pages. This scenario is presented as 6 business-readable test steps; SyntraFlow's automation executes approximately 128 underlying Oracle Fusion UI actions to complete it.

Test Objective

The objective of the SCM Critical Regression Pack is to give release and QA teams a defined, repeatable set of 24 high-risk Oracle Fusion SCM scenarios — spanning Procurement, Inventory, Order Management, Manufacturing, Product Management and Supply Planning — that can be run together ahead of a quarterly update, patch or configuration change, rather than re-testing each module's full scenario library from scratch every cycle.

The scenario should confirm that:

the 24 referenced REG-SCM scenario IDs are correctly composed from their underlying Procurement, Inventory, Order Management, Manufacturing, Product Management and Supply Planning family pages
quantity and document linkage correctly carry across SCM area boundaries — for example from PO receipt into inventory on-hand, or from sales order reservation into shipment
negative and security validations are correctly enforced across the composed pack rather than only within a single family page
a batch execution of the pack correctly records pass/fail status per scenario, with failures classified into a likely root-cause category
the pack can be scheduled and re-run on a defined cadence, such as ahead of a quarterly Oracle update

This pack does not duplicate the individual field-level scenario coverage already tested on the Requisitions, Purchase Orders, Receiving, Transfers, Item Transactions, Sales Orders, Fulfillment, Work Orders, Material Transactions, Completions, Create Item, Run Supply Plan and Release Planned Order family pages. It references those pages by scenario ID and composes them into one regression-critical execution unit with cross-area assertions.

When to Use This Test

Regression testing ahead of an Oracle quarterly update, patch or configuration change across Procurement, Inventory, Order Management, Manufacturing and Planning
Release sign-off requiring evidence that SCM-critical scenarios still pass rather than re-running the full module-level test library
Validating cross-area continuity — for example quantity carried from PO receipt into inventory on-hand, or reservation carried into shipment — 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 fails
Baseline reference pack when assembling a broader cross-module pack such as Plan-to-Cash Regression

SCM Critical Regression Pack Composition

Procurement

→

Inventory

→

Order Management

→

Manufacturing

→

Planning

The SCM Critical Regression Pack composes 24 scenarios across these five coverage areas of Oracle Fusion SCM, referencing the Procurement, Inventory Management, Order Management, Manufacturing, Product Management and Supply Planning family pages rather than duplicating their individual scenario coverage. The pack adds cross-area continuity assertions, DataVault-driven test data, batch scheduling and Failure Intelligence classification on top of the referenced scenarios.

Preconditions

The Procurement, Inventory Management, Order Management, Manufacturing, Product Management and Supply Planning family pages referenced by this pack's 24 scenario IDs are individually functional in the target Oracle Fusion SCM environment.
A valid item, organization, supplier, customer and supply plan are available and enabled across the referenced scenario areas.
The test user holds the roles required to execute each referenced scenario, 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.
Approval hierarchies, sourcing rules and security roles are configured according to the target environment — this pack does not assume a single universal configuration applies to every scenario.

Exact approval hierarchies, sourcing rules, security roles and item configuration vary by Oracle Fusion implementation and customer-specific setup. This pack validates that Oracle correctly enforces whatever configuration is in place for each referenced scenario, not a single universal rule.

Sample Test Data

Item	${ITEM}
Organization	${ORGANIZATION}
Quantity	${QUANTITY}
Requisition	${REQUISITION}
PO Number	${PO_NUMBER}
Sales Order	${SALES_ORDER}
Work Order	${WORK_ORDER}
Plan Name	${PLAN_NAME}

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 referenced scenario — for example, Work Order applies only to Manufacturing-area scenarios and is not used for Procurement-only scenarios.

Test Steps

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

#	User Action	Expected Result
1	Select Pack Scenarios Select the 24 REG-SCM regression-critical scenario IDs from the Procurement, Inventory, Order Management, Manufacturing, Product Management and Supply Planning family pages into the SCM Critical Regression Pack. REG-SCM-001 … REG-SCM-024	All 24 referenced scenario IDs are correctly included in the pack composition.
2	Bind DataVault Test Data Bind DataVault-supplied test data — items, organizations, suppliers, customers and plans — to each scenario ID in the pack. ${ITEM} / ${ORGANIZATION} / ${SUPPLIER}	Each scenario in the pack correctly resolves its required test data before execution.
3	Execute the Pack in Batch Execute all 24 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 Cross-Area AssertionsBusiness assertion Review the cross-area business assertions confirming quantity and document linkage carried correctly between coverage areas — for example PO receipt into inventory on-hand, or reservation into shipment. ${ITEM} / ${QUANTITY} / ${SALES_ORDER} This is a primary business assertion for the pack — cross-area continuity, not just individual scenario pass status, is the expected pass condition.	Quantity and document references remain correctly consistent as data crosses from one coverage area into another.
5	Classify Any FailuresBusiness assertion For any scenario that fails, review the evidence trail and classify the likely root cause using the 8-category failure taxonomy before escalating. DATA_ERROR / CONFIGURATION_ERROR / SECURITY_ERROR / EXPECTED_VALIDATION / INTEGRATION_ERROR / AUTOMATION_ERROR / ENVIRONMENT_ERROR / APPLICATION_ERROR	A failed scenario is correctly classified into a likely root-cause category rather than assumed to be an Oracle application defect.
6	Record the Release DecisionBusiness assertion Record the pack's aggregate pass/fail outcome as evidence supporting a release go/no-go decision. ${PLAN_NAME} This is the final business assertion for the pack — an aggregate, correctly classified pass/fail result across all 24 scenarios is the expected pass condition.	The pack's aggregate result is correctly available as evidence for the release decision.

Expected Results

All 24 referenced REG-SCM scenario IDs are correctly included and resolvable against the target environment.
Test data binds correctly to each scenario via DataVault before execution.
Each scenario in the batch run records a pass, fail or exception status.
Quantity and document linkage remain correctly consistent as data crosses coverage-area boundaries.
Any failure is correctly classified into a likely root-cause category rather than assumed to be an Oracle defect.
The pack's aggregate result is available as evidence for a release go/no-go decision.

Key Validation Checkpoints

all 24 scenario IDs correctly resolved from their referenced family pages
DataVault test data correctly bound to each scenario before execution
batch execution correctly records pass/fail/exception per scenario
cross-area quantity and document continuity correctly maintained
negative and security scenarios correctly enforce the expected restriction
failed scenarios correctly classified using the 8-category taxonomy
aggregate pack result correctly available for release sign-off

Core Business Scenario

SCM Critical Regression

Pack Scenarios

24 Scenarios

Coverage Areas

5 Areas

Linked Family Pages

13 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 SCM Critical Regression Pack as a composition of 24 regression-critical scenario IDs across the Procurement, Inventory Management, Order Management, Manufacturing, Product Management and Supply Planning family pages within SCM. Jarvis AI extends this pack 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 this Regression Pack and Scheduled Execution, with results surfaced through Failure Intelligence.

Teams do not need to manually assemble which requisition, purchase order, sales order and work order scenarios matter most for a release. Jarvis uses the standard pack composition as the foundation and generates relevant Positive, Negative, Boundary, Integration and Security variations for the customer's environment — including quantity mismatches, blocked approvals and security exceptions — since correctly enforced continuity between SCM areas, 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; this page remains the canonical reference for the pack.

From Standard Test to Executed Regression Pack

SCM

Oracle Fusion SCM product area.

Functional Areas — Procurement, Inventory, Order Management, Manufacturing, Planning

The five coverage areas this pack composes scenarios from within SCM.

Process / Scenario Family — SCM Critical Regression

24 regression-critical scenario IDs selected as high-risk, high-frequency SCM transactions.

Standard Test Scenarios

Reusable scenario definitions maintained individually on each referenced family page.

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 24 selected scenario IDs are grouped into this executable, schedulable SCM Critical Regression Pack.

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.

Rather than re-testing every requisition, purchase order, receipt, transfer, sales order, work order and planned order field individually — already covered on their respective family pages — SyntraFlow maintains one SCM Critical Regression Pack composed of 24 regression-critical scenario IDs, documented in the browser below, and allows Jarvis AI to generate item, organization 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 SCM Critical 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 SCM Module Critical.

Positive Scenarios

Pack validating requisition-to-PO-to-receipt continuity correctly increases inventory on-hand for the received item
Pack validating sales-order-to-pick-release-to-ship-confirm continuity correctly relieves reserved inventory
Pack validating work-order-to-material-issue-to-completion continuity correctly reports finished quantity into inventory
Pack validating a released planned order correctly creates the recommended supply document type
Pack validating approval hierarchies are correctly enforced for requisitions and purchase orders

Negative Scenarios

Pack scenario where an invalid item/organization combination is correctly rejected rather than silently accepted
Pack scenario where an unauthorized user is correctly blocked from creating or approving a transaction at any referenced stage
Pack scenario where a quantity mismatch between two composed areas is correctly flagged rather than silently reconciled

These are representative examples only. Pack behavior, approval routing and available transaction 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, supplier, customer and plan referenced across a real Oracle Fusion SCM Critical 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}
Requisition          ${REQUISITION}
PO Number            ${PO_NUMBER}
Sales Order          ${SALES_ORDER}
Work Order           ${WORK_ORDER}
Plan Name            ${PLAN_NAME}

DataVault

Items
  Active items with organization assignments and sourcing rules
Organizations
  Procurement, inventory, order management, manufacturing and planning organizations
Suppliers & Customers
  Approved suppliers and customers by item and territory
Supply Plans
  Collected supply and demand data by plan
Security
  Roles authorised at each referenced scenario stage

Jarvis AI Generates

Scenario 01 — Requisition-to-Receipt, ${ITEM}
Scenario 02 — Sales-Order-to-Ship-Confirm, ${SALES_ORDER}
Scenario 03 — Work-Order-to-Completion, ${WORK_ORDER}
Scenario 04 — Planned Order Release for ${PLAN_NAME}
Scenario 05 — Unauthorized User Attempts Approval
...

Requisition, order, work order and receipt data used in SCM Critical 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 and supplier 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 24 scenario IDs composed into the SCM Critical Regression Pack across Procurement, Inventory, Order Management, Manufacturing and Planning, plus cross-area negative and security smoke coverage. Each row references the real family page the underlying scenario is defined on — this pack does not duplicate that field-level definition.

ID	Variation	Type	Key Difference	Execution
REG-SCM-001	Create Requisition	Procurement	Regression-critical instance validating that a purchase requisition for ${ITEM} in ${ORGANIZATION} is correctly created with quantity ${QUANTITY} and routed for approval. Source: Requisitions (/oracle-erp-testing-tool/test-library/scm/procurement/requisitions/)	Illustrative
REG-SCM-002	Approve Requisition	Procurement	Regression-critical instance validating that requisition ${REQUISITION} is correctly approved by an authorized approver and released for purchase order creation. Source: Requisitions (/oracle-erp-testing-tool/test-library/scm/procurement/requisitions/)	Illustrative
REG-SCM-003	Create PO	Procurement	Regression-critical instance validating that a purchase order for supplier ${SUPPLIER} is correctly created from an approved requisition, carrying forward item ${ITEM} and quantity ${QUANTITY}. Source: Purchase Orders (/oracle-erp-testing-tool/test-library/scm/procurement/purchase-orders/)	Illustrative
REG-SCM-004	Approve PO	Procurement	Regression-critical instance validating that purchase order ${PO_NUMBER} is correctly approved according to the configured approval hierarchy before it becomes available for receiving. Source: Purchase Orders (/oracle-erp-testing-tool/test-library/scm/procurement/purchase-orders/)	Illustrative
REG-SCM-005	Receive PO	Procurement	Regression-critical instance validating that a receipt against purchase order ${PO_NUMBER} correctly records received quantity ${QUANTITY} and increases on-hand for item ${ITEM}. Source: Receiving (/oracle-erp-testing-tool/test-library/scm/procurement/receiving/)	Illustrative
REG-SCM-006	Miscellaneous Receipt	Inventory	Regression-critical instance validating that a miscellaneous receipt for item ${ITEM} in ${ORGANIZATION} correctly increases on-hand quantity outside of a purchase order receipt. Source: Item Transactions (/oracle-erp-testing-tool/test-library/scm/inventory-management/item-transactions/)	Illustrative
REG-SCM-007	Subinventory Transfer	Inventory	Regression-critical instance validating that a subinventory transfer for item ${ITEM} correctly moves quantity ${QUANTITY} between subinventories within ${ORGANIZATION} without changing total on-hand. Source: Transfers (/oracle-erp-testing-tool/test-library/scm/inventory-management/transfers/)	Illustrative
REG-SCM-008	Transfer Order	Inventory	Regression-critical instance validating that a transfer order for item ${ITEM} correctly moves quantity ${QUANTITY} between organizations, reducing on-hand at the source and increasing it at the destination. Source: Transfers (/oracle-erp-testing-tool/test-library/scm/inventory-management/transfers/)	Illustrative
REG-SCM-009	Create Sales Order	Order Management	Regression-critical instance validating that a sales order for item ${ITEM} and quantity ${QUANTITY} is correctly created for customer ${CUSTOMER} and enters order orchestration. Source: Sales Orders (/oracle-erp-testing-tool/test-library/scm/order-management/sales-orders/)	Illustrative
REG-SCM-010	Schedule Order	Order Management	Regression-critical instance validating that sales order ${SALES_ORDER} is correctly scheduled against available or planned supply, assigning a schedule ship date consistent with ${REQUIRED_DATE}. Source: Sales Orders (/oracle-erp-testing-tool/test-library/scm/order-management/sales-orders/)	Illustrative
REG-SCM-011	Reserve Order	Order Management	Regression-critical instance validating that sales order ${SALES_ORDER} correctly reserves on-hand quantity for item ${ITEM} in ${ORGANIZATION}, reducing available-to-promise supply. Source: Sales Orders (/oracle-erp-testing-tool/test-library/scm/order-management/sales-orders/)	Illustrative
REG-SCM-012	Pick Release	Order Management	Regression-critical instance validating that pick release for sales order ${SALES_ORDER} correctly generates a pick slip for reserved quantity ${QUANTITY} of item ${ITEM}. Source: Fulfillment (/oracle-erp-testing-tool/test-library/scm/order-management/fulfillment/)	Illustrative
REG-SCM-013	Ship Confirm	Order Management	Regression-critical instance validating that ship confirm for sales order ${SALES_ORDER} correctly relieves inventory for the shipped quantity and updates order status to shipped. Source: Fulfillment (/oracle-erp-testing-tool/test-library/scm/order-management/fulfillment/)	Illustrative
REG-SCM-014	Create Work Order	Manufacturing	Regression-critical instance validating that a work order for item ${ITEM} and quantity ${QUANTITY} is correctly created in ${ORGANIZATION} against the item's work definition. Source: Work Orders (/oracle-erp-testing-tool/test-library/scm/manufacturing/work-orders/)	Illustrative
REG-SCM-015	Issue Material	Manufacturing	Regression-critical instance validating that component material is correctly issued to work order ${WORK_ORDER}, reducing on-hand for the consumed component items. Source: Material Transactions (/oracle-erp-testing-tool/test-library/scm/manufacturing/material-transactions/)	Illustrative
REG-SCM-016	Complete Work Order	Manufacturing	Regression-critical instance validating that completing work order ${WORK_ORDER} correctly reports finished quantity ${QUANTITY} of item ${ITEM} into inventory. Source: Completions (/oracle-erp-testing-tool/test-library/scm/manufacturing/completions/)	Illustrative
REG-SCM-017	Create Item	Planning	Regression-critical instance validating that a new item ${ITEM} is correctly created with the attributes and organization assignments required for downstream procurement, inventory, order management, manufacturing and planning transactions. Source: Create Item (/oracle-erp-testing-tool/test-library/scm/product-management/create-item/)	Illustrative
REG-SCM-018	Run Supply Plan	Planning	Regression-critical instance validating that supply plan ${PLAN_NAME} correctly runs and calculates net requirements for item ${ITEM} in ${ORGANIZATION} after netting existing supply. Source: Run Supply Plan (/oracle-erp-testing-tool/test-library/scm/supply-planning/run-supply-plan/)	Illustrative
REG-SCM-019	Release Planned Order	Planning	Regression-critical instance validating that releasing planned order ${PLANNED_ORDER} correctly creates the recommended supply document — requisition, work order or transfer order — for item ${ITEM}. Source: Release Planned Order (/oracle-erp-testing-tool/test-library/scm/supply-planning/release-planned-order/)	Illustrative
REG-SCM-020	SCM negative validation	Negative	Cross-area negative regression instance confirming Oracle correctly rejects an invalid requisition, purchase order or sales order — for example an unconfigured item/organization combination or a quantity of zero — rather than silently accepting it. Individual field-level negative scenarios are covered on the referenced family pages. Source: Requisitions, Purchase Orders & Sales Orders (/oracle-erp-testing-tool/test-library/scm/procurement/requisitions/)	Illustrative
REG-SCM-021	SCM security smoke	Negative	Cross-area security smoke instance confirming an unauthorized user is correctly blocked from creating or approving a requisition, purchase order, work order or shipment across the referenced family pages, rather than one universal SCM security model being assumed. Source: Requisitions, Purchase Orders, Work Orders & Fulfillment (/oracle-erp-testing-tool/test-library/scm/procurement/purchase-orders/)	Illustrative
REG-SCM-022	Inventory quantity continuity	Inventory	Cross-area continuity instance confirming on-hand quantity for item ${ITEM} remains correctly reconciled as receipts, transfers, reservations and material issues are posted against ${ORGANIZATION}, referencing the Item Transactions and Transfers family pages. Source: Item Transactions & Transfers (/oracle-erp-testing-tool/test-library/scm/inventory-management/item-transactions/)	Illustrative
REG-SCM-023	Order fulfillment continuity	Order Management	Cross-area continuity instance confirming sales order ${SALES_ORDER} carries a consistent reserved and shipped quantity for item ${ITEM} from order entry through pick release and ship confirm, referencing the Sales Orders and Fulfillment family pages. Source: Sales Orders & Fulfillment (/oracle-erp-testing-tool/test-library/scm/order-management/sales-orders/)	Illustrative
REG-SCM-024	Plan-to-Produce smoke	Planning	Cross-area smoke instance confirming a make-recommended planned order for item ${ITEM} correctly flows from supply plan ${PLAN_NAME} through work order creation, material issue and completion, referencing the Run Supply Plan and Work Orders family pages. Source: Run Supply Plan & Work Orders (/oracle-erp-testing-tool/test-library/scm/supply-planning/run-supply-plan/)	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-area continuity check in Oracle Fusion.

Correctly Created Requisition → Approved PO → Receipt → Inventory On-Hand Increased

Negative Testing

Jarvis can also generate pack scenarios designed to exercise Oracle's validations around invalid data, blocked approvals and unauthorized access at any referenced stage.

Invalid Item/Organization Combination → Expected Rejection Rather Than Silent Acceptance
Quantity Mismatch Between Composed Areas → Expected Flag Rather Than Silent Reconciliation
Unauthorized User Attempts Approval or Transaction → Expected Access Restriction
Missing Required Upstream Document → Expected Validation Rather Than Silent Creation

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	Pack scenario completes end-to-end	PASS
Data mismatch between composed areas	Validation or warning occurs	PASS
Missing required upstream document	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

Users can select generated SCM Critical scenarios and group them into this reusable execution pack.

SCM Critical Regression Pack

Create Requisition
Approve PO
Receive PO
Transfer Order
Create Sales Order
Ship Confirm
Complete Work Order
Run Supply Plan

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 the SCM Critical Regression Pack's 24 scenarios individually or as a batch. Users can schedule the pack according to their release or testing cycle.

Once scheduled, SyntraFlow executes the SCM Critical Regression Pack's scenarios unattended and records the outcome of each scenario and cross-area business assertion.

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

Pack	SCM Critical Regression Pack
Schedule	Quarterly Update Regression
Tests	24 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 Procurement, Inventory, Order Management, Manufacturing and Planning 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 SCM Critical Regression Pack as DataVault-supplied test data flows from requisition and item creation through procurement, inventory, order management, manufacturing and planning.

Persona: SCM Regression Tester

Item	${ITEM}
Organization	${ORGANIZATION}
Requisition	${REQUISITION}
PO Number	${PO_NUMBER}
Supplier	${SUPPLIER}
Sales Order	${SALES_ORDER}
Customer	${CUSTOMER}
Work Order	${WORK_ORDER}
Planned Order	${PLANNED_ORDER}
Plan Name	${PLAN_NAME}
Quantity	${QUANTITY}

Keeping these dimensions linked across DataVault-supplied test data lets Jarvis generate pack variations that remain internally consistent from requisition and item creation through to whichever referenced scenario — procurement, inventory, order management, manufacturing or planning — the regression pack composes.

Security & Approval Variations

Access to each stage referenced by this pack — creating or approving a requisition, purchase order, work order or shipment — 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 — not to assert a single universal Oracle security model.

Persona	Action	Expected	Syntra Result
Procurement Buyer	Create Requisition and Purchase Order	Allowed	PASS
Procurement Approver	Approve Requisition and Purchase Order	Allowed	PASS
Security Administrator	Review Role Assignments Across Referenced Scenarios	Allowed	PASS
Unauthorized User	Attempts to Approve Purchase Order Without Role	Access prevented	PASS

Pack Composition Assertions

These assertions validate that quantity, document linkage and date data remain consistent as the pack crosses from one SCM coverage area into another — for example from Procurement into Inventory, or from Order Management into Manufacturing.

QUANTITY_CONTINUITYDOCUMENT_LINKAGEDATE_CONTINUITY

Stage Transition	Assertion	Example	Status
Procurement -> Inventory	PO Receipt Qty = Inventory On-Hand Increase	Receipt of ${QUANTITY} for ${ITEM} against ${PO_NUMBER} increases on-hand in ${ORGANIZATION}	PASS
Order Management -> Inventory	Reserved Qty = On-Hand Reduction at Ship Confirm	Ship confirm for ${SALES_ORDER} reduces reserved on-hand for ${ITEM} by shipped quantity	PASS
Planning -> Manufacturing	Released Planned Order Qty = Work Order Qty	Planned order ${PLANNED_ORDER} for ${ITEM} correctly creates work order ${WORK_ORDER} at matching quantity	PASS
Manufacturing -> Inventory	Completed Work Order Qty = Finished-Goods On-Hand Increase	Completion of ${WORK_ORDER} increases on-hand for ${ITEM} by completed quantity ${QUANTITY}	PASS

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

Pack Execution Summary

This example shows illustrative execution status recorded across the SCM Critical Regression Pack's five coverage areas in one representative batch run.

1Procurement

PASS

2Inventory

PASS

3Order Management

PASS

4Manufacturing

FAIL

5Planning

PASS

Failed Stage

Upstream Passed

Downstream Blocked

Illustrative example run — not a live execution. Values above represent Total Scenarios Run / Passed / Failed or Blocked for this pack.

Pack Failure Classification Model

This example shows how a failure within one referenced scenario of the SCM Critical Regression Pack is classified and reported without blocking visibility into which other areas already passed.

Journey: SCM Critical Regression Pack Failed Stage: Manufacturing

Upstream Status

Procurement	PASS
Inventory	PASS
Order Management	PASS

Scenario

Complete Work Order (REG-SCM-016)

Expected Result

Completing work order ${WORK_ORDER} correctly reports finished quantity ${QUANTITY} of item ${ITEM} into on-hand inventory.

Actual Result

Work order ${WORK_ORDER} status shows Complete, but on-hand for ${ITEM} in ${ORGANIZATION} was not increased by the completed quantity.

Failure Classification

APPLICATION_ERROR

Blocking Impact / Downstream Status

Finished-goods on-hand for ${ITEM} understated; downstream sales order fulfillment scenarios in the pack are at risk of an incorrect reservation.

Recommended Action

Verify the completion transaction posted correctly in Oracle Fusion, 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.

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 SCM Critical Regression Pack's 24 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 → 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 and composes.

Generate

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

Parameterize

Use relevant test data from DataVault.

Assemble

Build and maintain this reusable regression pack.

Execute

Run pack scenarios autonomously across referenced family pages.

Schedule

Execute unattended test batches.

Validate

Evaluate expected cross-area 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 — SCM Critical Regression, 24 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-Area Business Assertions

↓

Evidence

↓

PASS / FAIL

Business Step → Underlying UI Actions

Business Step

Execute the Pack in Batch

May internally include

Open Regression Pack → Select SCM Critical → Confirm 24 Scenario IDs → Run Now / Schedule → Confirm Batch Started

Business Step

Review Cross-Area Assertions

May internally include

Open Batch Results → Select Scenario → Review Cross-Area Assertion Rows → Confirm Quantity/Document Continuity → Confirm Status

What SyntraFlow Captures Per Run

Cross-page pack compositionParameterised input valuesReusable navigation across referenced family pagesAutomation action traceScreenshots / evidence captureExecution timingCross-area business assertionsEnvironment-independent test data

Action Status vs. Business Validation

A successful batch run does not automatically prove every cross-area hand-off in the pack is correct — this is illustrative of how SyntraFlow separates action success from cross-area 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. For example: Work Order Completion Fails to Update On-Hand — Likely category: APPLICATION_ERROR — Evidence: Completed quantity for ${WORK_ORDER} not reflected in on-hand for ${ITEM} — Recommendation: Verify the completion transaction posted and escalate if data, configuration, security, automation and environment causes are eliminated. 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 Cross-Area Assertions	Pass	Pass
Classify Any Failures	Pass	Pass

Related Regression Packs & SCM Test Library

The SCM Critical Regression Pack composes the Procurement, Inventory Management, Order Management, Manufacturing, Product Management and Supply Planning family pages into one pack, and links directly to the individual family pages it references.

Regression Packs SCM End-to-End Journeys SCM Test Library

Turn This Standard Pack into Your Oracle SCM Critical Regression Suite

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

Automate with SyntraFlow Explore SCM 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

Regression Packs SCM Test Library Procurement Inventory Management Order Management Manufacturing Supply Planning SCM End-to-End Journeys Syntra DataVault

Frequently Asked Questions

How does this SCM Critical Regression Pack differ from the individual Requisitions, Purchase Orders and other family pages?

This page does not duplicate the atomic scenario coverage already tested individually on the Requisitions, Purchase Orders, Receiving, Transfers, Item Transactions, Sales Orders, Fulfillment, Work Orders, Material Transactions, Completions, Create Item, Run Supply Plan and Release Planned Order family pages. Instead, it references 24 regression-critical scenario IDs drawn from those pages and composes them into one executable, schedulable pack with cross-area continuity assertions.

What does the Pack Composition Assertions section show?

It shows illustrative examples of quantity and document linkage carried correctly between SCM coverage areas — for example a PO receipt increasing inventory on-hand, or a sales order reservation carrying through to shipment. These assertions validate the hand-off between areas, not each area's individual field-level behavior.

What does the Pack Execution Summary show?

It shows an illustrative example of how many of the pack's 24 scenarios were run, passed, and failed or blocked in one representative batch execution, broken out by coverage area. It is illustrative, not a live execution.

What does the Pack Failure Classification Model show?

It shows a representative example of how a single failed scenario within the pack is captured alongside which areas already passed, the expected versus actual result, a failure classification from the 8-category taxonomy, and the downstream impact. It is illustrative, not a live execution.

Can individual scenarios from this pack be run on their own?

Yes. Each of the 24 referenced scenario IDs can also be run individually on its underlying family page. The pack exists to group regression-critical scenarios for batch execution ahead of a release, quarterly update or configuration change, not to replace running them individually when needed.

How does security testing work across a composed pack like this?

Access to each referenced scenario — creating or approving a requisition, purchase order, work order or shipment — is controlled by Oracle Fusion's security configuration, which varies by customer. SyntraFlow can execute representative persona-based variations across the pack, such as a procurement buyer or approver versus an unauthorized user, to confirm access behaves as expected, without asserting a single universal Oracle security model.