{
  "test_id": "ORCL.E2E.O2F",
  "scenario_name": "Order-to-Fulfillment",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "End-to-End SCM",
  "process": "Order-to-Fulfillment",
  "business_flow": "Order-to-Cash",
  "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/order-to-fulfillment/",
  "objective": {
    "intro": "The objective of this test is to validate the narrower Order-to-Fulfillment journey within Oracle Fusion SCM — create through submit, schedule, reserve, pick and ship — with particular emphasis on order holds correctly blocking downstream fulfillment stages until released, and inventory shortages correctly triggering backorder rather than a silent failure. This is an orchestration test that links together and validates the hand-offs between the individual Order Management family pages that already cover each stage's field-level validation in detail; it does not re-test each stage's atomic validation already covered on those pages.",
    "confirms": [
      "order data entered at creation correctly carries forward through submit, schedule, reserve, pick and ship",
      "order holds correctly block scheduling and every downstream fulfillment stage until the hold is released, and fulfillment correctly resumes once released",
      "inventory shortages at reservation correctly trigger a backorder rather than a silent failure or an inconsistent partial state",
      "short picks are correctly flagged rather than silently confirmed as a full pick",
      "order changes made after scheduling — quantity, requested date, ship-to — correctly re-flow through the downstream stages they affect",
      "cancelling an order before or after partial fulfillment correctly releases the applicable reserved and picked inventory"
    ],
    "scope_note": "This scenario validates the Order-to-Fulfillment journey and the hand-offs between stages in Oracle Fusion SCM Order Management TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the Create Sales Order, Submit Sales Order, Schedule Order, Reserve Order, Pick Release, Ship Confirm, Fulfillment Exceptions, Apply Order Hold, Release Order Hold and Order Changes family pages, which remain the canonical reference for each stage's atomic test coverage — this page focuses on cross-stage data integrity, holds correctly blocking downstream stages, and shortages correctly triggering backorder."
  },
  "preconditions": [
    "A valid customer, item and pricing setup exists for sales order creation in Oracle Fusion Order Management.",
    "The fulfillment organization(s) used in the journey are configured and enabled for scheduling, reservation, pick release and ship confirmation.",
    "Inventory is available in the fulfillment organization for standard journey scenarios, and intentionally constrained or unavailable for backorder and no-inventory scenarios.",
    "Order hold types used in hold-related scenarios are configured in Oracle Fusion Order Management, and at least one lot-controlled and one serial-controlled item are available for lot- and serial-controlled shipment scenarios.",
    "The test user or users hold appropriate role-based access for each stage of the journey being exercised, including a fulfillment-specific role for pick release and ship confirmation scenarios."
  ],
  "test_data": [
    {
      "field": "Sales Order",
      "example": "${SALES_ORDER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Hold Type",
      "example": "${HOLD_TYPE}"
    },
    {
      "field": "Ship Date",
      "example": "${SHIP_DATE}"
    },
    {
      "field": "Lot",
      "example": "${LOT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Create and Submit the Sales Order",
      "action": "Create a sales order with item and quantity, then submit it for processing — the detailed field-level steps for this stage are covered on the Create Sales Order and Submit Sales Order test pages.",
      "test_data": "${SALES_ORDER} / ${ITEM} / ${QUANTITY}",
      "expected_result": "The sales order is created and submitted successfully with a valid order number.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Schedule the Order",
      "action": "Schedule the submitted order against ${ORGANIZATION}, confirming that order data carries forward correctly from submission.",
      "test_data": "${ORGANIZATION} / ${SHIP_DATE}",
      "expected_result": "The order is scheduled with a valid ship date and organization, or scheduling is correctly blocked where order hold ${HOLD_TYPE} is active.",
      "validation_type": "action",
      "note": "Where a hold is applied to the order, this step confirms scheduling is correctly blocked until the hold is released — see the Apply Order Hold and Release Order Hold scenarios."
    },
    {
      "step_number": 3,
      "step_name": "Reserve Inventory",
      "action": "Reserve available inventory for the order against ${ORGANIZATION}, confirming that the scheduled quantity carries forward correctly into reservation.",
      "test_data": "${QUANTITY} / ${ORGANIZATION}",
      "expected_result": "Inventory is reserved for the order, or the order is correctly placed on backorder where on-hand inventory is insufficient.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Release for Picking",
      "action": "Release the reserved order for picking, confirming that reserved quantity carries forward correctly into pick release, including lot ${LOT} where the item is lot-controlled.",
      "test_data": "${LOT}",
      "expected_result": "A pick is generated for the reserved quantity, or the pick is correctly flagged short where the picked quantity is less than reserved.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Confirm Shipment",
      "action": "Confirm shipment of the picked order on ${SHIP_DATE}, including partial and multiple-shipment scenarios where applicable.",
      "test_data": "${SHIP_DATE}",
      "expected_result": "The shipment is confirmed and the order's fulfilled and remaining open quantity are correctly updated.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Cross-Stage Audit Trail",
      "action": "Review the order, reservation, pick and shipment records together to confirm they are correctly linked end-to-end for ${SALES_ORDER}.",
      "test_data": "",
      "expected_result": "The order, reservation, pick and shipment records are correctly linked and reflect consistent data across every stage.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the journey — correctly linked cross-stage records with consistent data is the expected pass condition, not merely each stage completing individually."
    }
  ],
  "expected_results": [
    "The sales order is created, submitted, scheduled, reserved, picked and shipped with data carrying forward correctly at every stage.",
    "Order holds correctly block scheduling and downstream fulfillment stages until released, and fulfillment correctly resumes once the hold is released.",
    "Inventory shortages correctly trigger a backorder rather than a silent failure.",
    "Short picks are correctly flagged rather than silently confirmed as a full pick.",
    "Order changes made after scheduling correctly re-flow through the downstream stages they affect.",
    "Cancelling an order before or after partial fulfillment correctly releases the applicable reserved and picked inventory."
  ],
  "validation_checkpoints": [
    "Order data correctly carries through scheduling, reservation, pick and ship.",
    "Holds correctly block downstream fulfillment stages until released.",
    "Shortages correctly trigger backorder rather than silent failure.",
    "Short picks are correctly flagged.",
    "Order changes correctly re-flow through downstream stages.",
    "Cancellation correctly releases reserved inventory."
  ]
}