{
  "test_id": "ORCL.REGRESSION.SCM.CRITICAL",
  "scenario_name": "SCM Critical Regression Pack",
  "application": "Oracle Fusion Cloud",
  "product": "Regression",
  "module": "Regression Packs",
  "process": "SCM Critical Regression",
  "business_flow": "Cross-Module SCM Regression",
  "scenario_type": "Regression Pack / Composition",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Regression Pack",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/regression-packs/scm-critical/",
  "objective": {
    "intro": "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.",
    "confirms": [
      "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"
    ],
    "scope_note": "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."
  },
  "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."
  ],
  "test_data": [
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Requisition",
      "example": "${REQUISITION}"
    },
    {
      "field": "PO Number",
      "example": "${PO_NUMBER}"
    },
    {
      "field": "Sales Order",
      "example": "${SALES_ORDER}"
    },
    {
      "field": "Work Order",
      "example": "${WORK_ORDER}"
    },
    {
      "field": "Plan Name",
      "example": "${PLAN_NAME}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Select Pack Scenarios",
      "action": "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.",
      "test_data": "REG-SCM-001 … REG-SCM-024",
      "expected_result": "All 24 referenced scenario IDs are correctly included in the pack composition.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Bind DataVault Test Data",
      "action": "Bind DataVault-supplied test data — items, organizations, suppliers, customers and plans — to each scenario ID in the pack.",
      "test_data": "${ITEM} / ${ORGANIZATION} / ${SUPPLIER}",
      "expected_result": "Each scenario in the pack correctly resolves its required test data before execution.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Execute the Pack in Batch",
      "action": "Execute all 24 scenarios in the pack as a single scheduled or on-demand batch run against the target Oracle Fusion environment.",
      "test_data": "Batch Mode",
      "expected_result": "Each scenario in the pack runs to completion and records a pass, fail or exception status.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Review Cross-Area Assertions",
      "action": "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.",
      "test_data": "${ITEM} / ${QUANTITY} / ${SALES_ORDER}",
      "expected_result": "Quantity and document references remain correctly consistent as data crosses from one coverage area into another.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the pack — cross-area continuity, not just individual scenario pass status, is the expected pass condition."
    },
    {
      "step_number": 5,
      "step_name": "Classify Any Failures",
      "action": "For any scenario that fails, review the evidence trail and classify the likely root cause using the 8-category failure taxonomy before escalating.",
      "test_data": "DATA_ERROR / CONFIGURATION_ERROR / SECURITY_ERROR / EXPECTED_VALIDATION / INTEGRATION_ERROR / AUTOMATION_ERROR / ENVIRONMENT_ERROR / APPLICATION_ERROR",
      "expected_result": "A failed scenario is correctly classified into a likely root-cause category rather than assumed to be an Oracle application defect.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 6,
      "step_name": "Record the Release Decision",
      "action": "Record the pack's aggregate pass/fail outcome as evidence supporting a release go/no-go decision.",
      "test_data": "${PLAN_NAME}",
      "expected_result": "The pack's aggregate result is correctly available as evidence for the release decision.",
      "validation_type": "business_assertion",
      "note": "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."
    }
  ],
  "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."
  ],
  "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"
  ]
}