{
  "test_id": "ORCL.REGRESSION.PLAN2CASH",
  "scenario_name": "Plan-to-Cash Regression Pack",
  "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",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Regression Pack",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/regression-packs/plan-to-cash-regression/",
  "objective": {
    "intro": "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.",
    "confirms": [
      "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"
    ],
    "scope_note": "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."
  },
  "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."
  ],
  "test_data": [
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Plan Name",
      "example": "${PLAN_NAME}"
    },
    {
      "field": "Planned Order",
      "example": "${PLANNED_ORDER}"
    },
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Purchase Order",
      "example": "${PURCHASE_ORDER}"
    },
    {
      "field": "Work Order",
      "example": "${WORK_ORDER}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Sales Order",
      "example": "${SALES_ORDER}"
    },
    {
      "field": "Shipment",
      "example": "${SHIPMENT}"
    },
    {
      "field": "AR Transaction",
      "example": "${AR_TRANSACTION}"
    },
    {
      "field": "Receipt",
      "example": "${RECEIPT}"
    },
    {
      "field": "Required Date",
      "example": "${REQUIRED_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Select Pack Scenarios",
      "action": "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.",
      "test_data": "REG-P2CASH-001 … REG-P2CASH-028",
      "expected_result": "All 28 referenced scenario IDs are correctly included in the pack composition across all four modules.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Bind DataVault Test Data",
      "action": "Bind DataVault-supplied test data — items, organizations, suppliers, customers and plan context — to each scenario ID in the pack.",
      "test_data": "${ITEM} / ${ORGANIZATION} / ${CUSTOMER}",
      "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 28 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 Demand-to-Supply and Supply-to-Inventory Continuity",
      "action": "Review the cross-stage assertions confirming net demand correctly drives supply creation, and that received or completed supply correctly increases on-hand for ${ITEM}.",
      "test_data": "${PLANNED_ORDER} / ${WORK_ORDER} / ${QUANTITY}",
      "expected_result": "Net demand-driven supply and its resulting on-hand increase reconcile correctly across the Supply Planning, Manufacturing and Inventory family pages.",
      "validation_type": "business_assertion",
      "note": "Validates the SCM Planning-to-Production boundary of the pack."
    },
    {
      "step_number": 5,
      "step_name": "Review Inventory-to-Fulfillment and Shipment-to-Billing Continuity",
      "action": "Review the cross-stage assertions confirming on-hand availability correctly supports order reservation and shipment, and that shipped quantity correctly generates the AR transaction.",
      "test_data": "${SALES_ORDER} / ${SHIPMENT} / ${AR_TRANSACTION}",
      "expected_result": "Reserved, picked and shipped quantity reconcile correctly through to the AR transaction generated for ${CUSTOMER}.",
      "validation_type": "business_assertion",
      "note": "Validates the Inventory-to-Order Management-to-Financials boundary of the pack."
    },
    {
      "step_number": 6,
      "step_name": "Review Billing-to-Cash Continuity",
      "action": "Review the cross-stage assertion confirming the invoiced amount correctly carries into receipt creation and application, reducing the customer's open balance.",
      "test_data": "${AR_TRANSACTION} / ${RECEIPT}",
      "expected_result": "Applied receipt amount correctly reconciles against the AR transaction, with the customer's open balance correctly reduced.",
      "validation_type": "business_assertion",
      "note": "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."
    },
    {
      "step_number": 7,
      "step_name": "Classify Any Failures Across the Four-Module Flow",
      "action": "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.",
      "test_data": "Failure Intelligence",
      "expected_result": "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.",
      "validation_type": "business_assertion",
      "note": "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."
    }
  ],
  "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."
  ],
  "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"
  ]
}