{
  "test_id": "ORCL.REGRESSION.O2C",
  "scenario_name": "O2C Regression Pack",
  "application": "Oracle Fusion Cloud",
  "product": "Regression",
  "module": "Regression",
  "process": "O2C Regression",
  "business_flow": "O2C 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/o2c-regression/",
  "objective": {
    "intro": "The objective of the O2C Regression Pack is to give release and QA teams a defined, repeatable set of 20 Order-to-Cash scenario IDs — spanning Sales Orders, Fulfillment, Order Changes, Returns, AR Billing and AR Receipts — that can be run together ahead of a quarterly update, patch or configuration change, rather than re-running the full 37-scenario Order-to-Cash end-to-end journey or each family page's full scenario library every cycle. For full step-by-step detail across all 9 O2C stages, see the Order-to-Cash end-to-end journey.",
    "confirms": [
      "the 20 referenced REG-O2C scenario IDs are correctly composed from their underlying Sales Orders, Fulfillment, Order Changes, Returns, AR Billing and AR Receipts family pages",
      "quantity and amount correctly carry across the Customer, Sales Order, Schedule, Reserve, Pick, Ship, AR Billing, Receipt and Apply Receipt flow",
      "negative and exception scenarios — inventory shortage, shipping failure, billing failure — 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 Sales Orders, Fulfillment, Order Changes, Returns, AR Billing and AR Receipts family pages, nor the detailed 37-scenario step-by-step coverage on the Order-to-Cash end-to-end journey page. It references 20 regression-critical scenario IDs by ID and composes them into one executable, schedulable pack with cross-stage assertions. For full step-by-step detail, see the Order-to-Cash end-to-end journey at /oracle-erp-testing-tool/test-library/scm/end-to-end/order-to-cash/."
  },
  "preconditions": [
    "The Sales Orders, Fulfillment, Order Changes, Returns, AR Billing and AR Receipts family pages referenced by this pack's 20 scenario IDs are individually functional in the target Oracle Fusion SCM and Financials environment.",
    "A valid customer, item, organization and pricing/tax configuration 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.",
    "Reservation policy, shipping methods, 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": "Sales Order",
      "example": "${SALES_ORDER}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Shipment",
      "example": "${SHIPMENT}"
    },
    {
      "field": "AR Transaction",
      "example": "${AR_TRANSACTION}"
    },
    {
      "field": "Receipt",
      "example": "${RECEIPT}"
    },
    {
      "field": "Return Order",
      "example": "${RETURN_ORDER}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Select Pack Scenarios",
      "action": "Select the 20 REG-O2C regression-critical scenario IDs from the Sales Orders, Fulfillment, Order Changes, Returns, AR Billing and AR Receipts family pages into the O2C Regression Pack.",
      "test_data": "REG-O2C-001 … REG-O2C-020",
      "expected_result": "All 20 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 — customers, items, organizations and pricing/tax context — to each scenario ID in the pack.",
      "test_data": "${CUSTOMER} / ${ITEM} / ${ORGANIZATION}",
      "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 20 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-Stage Assertions",
      "action": "Review the cross-stage business assertions confirming quantity and amount carried correctly along the Customer → Sales Order → Schedule → Reserve → Pick → Ship → AR Billing → Receipt → Apply Receipt flow.",
      "test_data": "${ITEM} / ${QUANTITY} / ${SALES_ORDER}",
      "expected_result": "Quantity and amount remain correctly consistent as data crosses from one stage of the flow into the next.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the pack — cross-stage 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"
    }
  ],
  "expected_results": [
    "All 20 referenced REG-O2C 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 amount remain correctly consistent as data crosses the Customer-to-Cash flow.",
    "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 20 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-stage quantity and amount continuity correctly maintained",
    "negative and exception scenarios correctly enforce the expected restriction",
    "failed scenarios correctly classified using the 8-category taxonomy",
    "aggregate pack result correctly available for release sign-off"
  ]
}