{
  "test_id": "ORCL.E2E.D2S",
  "scenario_name": "Demand-to-Supply",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "End-to-End SCM",
  "process": "Demand-to-Supply",
  "business_flow": "Plan-to-Produce",
  "scenario_type": "End-to-End / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard Journey",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/scm/end-to-end/demand-to-supply/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Demand-to-Supply journey in Oracle Fusion SCM — demand signal, planning, supply decision (buy, make or transfer), supply creation and demand coverage — with emphasis on the planning engine correctly recommending and reconciling the right supply source for each demand signal, without assuming a single universal supply-source recommendation applies to every item, rather than re-testing each stage's individual field-level validation, which is already covered on the linked Supply Planning, Procurement, Manufacturing and Inventory family pages this scenario orchestrates.",
    "confirms": [
      "the net demand quantity calculated from forecast, sales order or safety stock signals correctly drives the recommended supply quantity",
      "the planning engine correctly recommends the configured supply source — buy, make or transfer — per item and organization, rather than assuming one universal source",
      "the recommended supply source correctly creates the matching document type: purchase requisition, work order or transfer order",
      "supplier and manufacturing lead-time constraints are correctly factored into supply feasibility against the required date",
      "shortages, late supply and excess supply are correctly flagged rather than silently accepted",
      "created supply correctly reduces the open net requirement, with pegging correctly linking demand to its covering supply document",
      "unauthorized users are correctly blocked from creating a supply document at any stage of the journey"
    ],
    "scope_note": "This scenario validates the hand-offs and cross-stage data integrity of the Demand-to-Supply journey in Oracle Fusion SCM TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the Run Supply Plan, Demand Forecast, Supply Demand Balance, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Requisition, Create Work Order and Create Transfer Order family pages — this page links to and orchestrates those live pages into an end-to-end journey."
  },
  "preconditions": [
    "The Supply Planning, Procurement, Manufacturing and Inventory family pages referenced by this journey — Run Supply Plan, Demand Forecast, Supply Demand Balance, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Requisition, Create Work Order and Create Transfer Order — are individually functional in the target Oracle Fusion SCM environment.",
    "A valid item, organization, sourcing rule and supply plan are available and enabled for planning, procurement, manufacturing and inventory transfer.",
    "Collected supply and demand data is current for the supply plan under test.",
    "The test user holds the roles required to execute each stage of the journey, or alternate unauthorized-user personas are available for security testing.",
    "Sourcing rules, supplier lead times, manufacturing lead times and safety stock levels are configured according to the target environment — this scenario does not assume a single universal supply-source recommendation applies to every item."
  ],
  "test_data": [
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Planned Order",
      "example": "${PLANNED_ORDER}"
    },
    {
      "field": "Supply Source",
      "example": "${SUPPLY_SOURCE}"
    },
    {
      "field": "Required Date",
      "example": "${REQUIRED_DATE}"
    },
    {
      "field": "Plan Name",
      "example": "${PLAN_NAME}"
    },
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Review the Demand Signal",
      "action": "Review the demand signal — forecast, sales order or safety stock — driving net demand, referencing the standard Demand Forecast and Supply Demand Balance test scenarios.",
      "test_data": "${ITEM} / ${ORGANIZATION} / ${QUANTITY}",
      "expected_result": "The demand signal is correctly identified and net demand is available for planning.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Run or Review the Supply Plan's Net Requirement Calculation",
      "action": "Run or review the supply plan's net requirement calculation after netting existing supply, referencing the standard Run Supply Plan test scenario.",
      "test_data": "${PLAN_NAME} / ${ITEM} / ${QUANTITY}",
      "expected_result": "Net demand is correctly calculated after netting on-hand, existing purchase orders, work orders and transfer supply.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Review the Recommended Supply Source",
      "action": "Review the planning engine's recommended supply source — buy, make or transfer — for the net demand, referencing the standard Planned Orders and Planning Exceptions test scenarios.",
      "test_data": "${PLANNED_ORDER} / ${SUPPLY_SOURCE}",
      "expected_result": "The recommended supply source correctly reflects the item's configured sourcing rule, rather than a single universal recommendation.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Create the Corresponding Supply Document",
      "action": "Release the planned order and create the corresponding supply document — purchase requisition, work order or transfer order — referencing the standard Release Planned Order, Create Purchase Requisition, Create Work Order and Create Transfer Order test scenarios.",
      "test_data": "${PLANNED_ORDER} / ${SUPPLIER} / ${REQUIRED_DATE}",
      "expected_result": "The supply document created matches the recommended source type and carries forward quantity and required date.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Verify Supply Covers the Net Demand",
      "action": "Compare the created supply document against the originating net demand.",
      "test_data": "${ITEM} / ${QUANTITY} / ${SUPPLY_SOURCE}",
      "expected_result": "Created supply correctly reduces the open net requirement, with pegging correctly linking demand to its covering supply document.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — reconciled quantity and correct pegging across demand, planning recommendation and supply document is the expected pass condition, not merely a successful transaction."
    },
    {
      "step_number": 6,
      "step_name": "Verify Planning Rerun Reflects the Updated Balance",
      "action": "Rerun the supply plan after supply creation and review the updated supply/demand balance, referencing the standard Supply Demand Balance test scenario.",
      "test_data": "${PLAN_NAME} / ${ITEM} / ${REQUIRED_DATE}",
      "expected_result": "Planning rerun correctly reflects the updated supply/demand balance, with the previously open requirement now covered.",
      "validation_type": "business_assertion",
      "note": "This is the final business assertion for the scenario — an updated, correctly reconciled supply/demand balance after rerun is the expected pass condition for the full journey."
    }
  ],
  "expected_results": [
    "The demand signal — forecast, sales order or safety stock — is correctly identified and net demand is available for planning.",
    "Net demand is correctly calculated after netting on-hand, existing purchase orders, work orders and transfer supply.",
    "The recommended supply source correctly reflects the item's configured sourcing rule — buy, make or transfer — rather than a single universal recommendation.",
    "The created supply document matches the recommended source type and carries forward quantity and required date.",
    "Created supply correctly reduces the open net requirement, with pegging correctly linking demand to its covering supply document.",
    "Unauthorized supply document creation attempts are correctly blocked at any stage of the journey."
  ],
  "validation_checkpoints": [
    "net demand correctly calculated after netting existing supply",
    "the correct supply source type (buy/make/transfer) correctly recommended per configured sourcing rules",
    "supply document correctly created matching the recommendation",
    "lead-time constraints correctly factored into feasibility",
    "shortages and late supply correctly flagged rather than silently accepted",
    "planning rerun correctly reflects updated supply/demand balance",
    "pegging correctly links demand to its covering supply document"
  ]
}