{
  "test_id": "ORCL.E2E.MTO",
  "scenario_name": "Make-to-Order",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "End-to-End SCM",
  "process": "Make-to-Order",
  "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/make-to-order/",
  "objective": {
    "intro": "Validate the complete Make-to-Order journey — customer order, demand, planning, work order, manufacture, finished goods, reserve, pick, ship, AR billing and customer receipt — with emphasis on customer demand correctly driving and reconciling against production output across Order Management, Supply Planning, Manufacturing and Financials AR, rather than re-testing each stage's atomic validation already covered on the linked family pages this scenario orchestrates.",
    "confirms": [
      "the sales order demand for a make-to-order item correctly flows through supply planning to generate a linked, released work order with matching quantity",
      "production completion correctly triggers reservation against the specific originating sales order",
      "pick release and shipment correctly consume the completed, reserved production quantity",
      "AR billing correctly reflects the shipped quantity tied back to the originating sales order",
      "the customer receipt correctly applies against the AR transaction, reducing the open balance",
      "a sales order cancellation after work order creation correctly flags the resulting orphaned work order",
      "unauthorized users are correctly blocked from completing a make-to-order work order without the production role"
    ],
    "scope_note": "This scenario validates the hand-offs and cross-module data integrity of the Make-to-Order journey in Oracle Fusion SCM TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the 18 linked family pages across Order Management, Supply Planning, Manufacturing and Financials AR — this page links to and orchestrates those live pages into the broadest cross-module journey on the site."
  },
  "preconditions": [
    "The Order Management, Supply Planning, Manufacturing and Financials AR family pages referenced by this journey are individually functional in the target Oracle Fusion SCM environment.",
    "A valid make-to-order item, customer, work definition, manufacturing organization and supply plan are available and enabled for sales, planning, production and billing.",
    "Work order auto-creation or manual linkage from the sales order via supply planning is configured for the test user's business unit.",
    "The test user holds the roles required to execute each stage of the journey, or alternate unauthorized-user personas are available for security testing.",
    "Reservation rules, production completion tolerances, pick/ship configuration and AR transaction type setup are configured according to the target environment — this scenario does not assume a universal configuration."
  ],
  "test_data": [
    {
      "field": "Sales Order",
      "example": "${SALES_ORDER}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Work Order",
      "example": "${WORK_ORDER}"
    },
    {
      "field": "Manufacturing Org",
      "example": "${MANUFACTURING_ORG}"
    },
    {
      "field": "Shipment",
      "example": "${SHIPMENT}"
    },
    {
      "field": "AR Transaction",
      "example": "${AR_TRANSACTION}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Create the Customer Sales Order for the Make-to-Order Item",
      "action": "Create a sales order for a make-to-order item, customer and quantity, referencing the standard Create Sales Order and Create Multi-Line Order test scenarios.",
      "test_data": "${SALES_ORDER} / ${CUSTOMER} / ${ITEM} / ${QUANTITY}",
      "expected_result": "The sales order is created with a confirmed make-to-order line, ready to generate demand.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Verify the Linked Planned and Released Work Order Matches Quantity",
      "action": "Confirm the sales order demand flows into the supply plan and generates a planned work order, then release it to production, referencing the standard Run Supply Plan, Release Planned Order, Create Work Order and Release Work Order test scenarios; compare the work order quantity to the sales order line quantity.",
      "test_data": "${WORK_ORDER} / ${SALES_ORDER} / ${QUANTITY} / ${MANUFACTURING_ORG}",
      "expected_result": "The released work order is correctly linked to the originating sales order with a matching quantity.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — matching quantity between the sales order line and the released work order is the expected pass condition, not merely a successfully released work order."
    },
    {
      "step_number": 3,
      "step_name": "Issue Material and Complete the Work Order",
      "action": "Issue component material to the work order and complete it in full or partially, referencing the standard Issue Material, Complete Work Order and Partial Completion test scenarios.",
      "test_data": "${WORK_ORDER} / ${QUANTITY} / ${MANUFACTURING_ORG}",
      "expected_result": "The work order completion is recorded with the correct completed quantity, and finished goods enter inventory.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Verify Production Completion Triggers Reservation Against the Sales Order",
      "action": "Confirm that the completed production quantity correctly triggers or updates a reservation against the specific originating sales order, referencing the standard Reserve Order test scenario.",
      "test_data": "${RESERVATION} / ${WORK_ORDER} / ${SALES_ORDER}",
      "expected_result": "The completed quantity is correctly reserved against the originating sales order, with any quantity mismatch flagged.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — the reservation must tie back to the specific sales order that generated the demand, not merely any open order."
    },
    {
      "step_number": 5,
      "step_name": "Release the Reserved Quantity for Pick",
      "action": "Release the reserved quantity to the warehouse for picking, referencing the standard Pick Release test scenario.",
      "test_data": "${RESERVATION} / ${SALES_ORDER}",
      "expected_result": "The reserved quantity is correctly released for picking.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Confirm Shipment of the Picked Quantity",
      "action": "Ship-confirm the picked quantity against the sales order, referencing the standard Ship Confirm test scenario.",
      "test_data": "${SHIPMENT} / ${SALES_ORDER}",
      "expected_result": "The shipment correctly consumes the picked, reserved quantity and updates the sales order fulfillment status.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Create the AR Billing Transaction Referencing the Shipment",
      "action": "Create the AR transaction for the shipped quantity, referencing the standard Create Transaction (Billing) test scenario.",
      "test_data": "${AR_TRANSACTION} / ${SHIPMENT} / ${SALES_ORDER}",
      "expected_result": "The AR transaction correctly reflects the shipped quantity and references the originating sales order.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Create and Apply the Customer Receipt",
      "action": "Create the customer receipt and apply it against the AR transaction, referencing the standard Create Standard Receipt test scenario.",
      "test_data": "${RECEIPT} / ${AR_TRANSACTION} / ${CUSTOMER}",
      "expected_result": "The customer receipt is created and correctly applied, reducing the open AR balance.",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Verify Full Audit Trail Links Every Document Together",
      "action": "Review the audit trail or document reference chain connecting the sales order, work order, reservation, shipment, AR transaction and receipt for the journey.",
      "test_data": "${SALES_ORDER} / ${WORK_ORDER} / ${AR_TRANSACTION} / ${RECEIPT}",
      "expected_result": "The sales order, work order, reservation, shipment, invoice and receipt are correctly linked in the audit trail, confirming the end-to-end journey is traceable.",
      "validation_type": "business_assertion",
      "note": "This is the final business assertion for the scenario — a traceable, correctly linked document chain across Order Management, Supply Planning, Manufacturing and Financials AR is the expected pass condition for the full journey."
    }
  ],
  "expected_results": [
    "The sales order is created and confirmed for the make-to-order item before production is initiated.",
    "The sales order demand correctly flows into the supply plan and generates a linked, released work order.",
    "Production completion correctly triggers reservation against the specific originating sales order.",
    "Pick release and shipment correctly consume the reserved, completed production quantity.",
    "AR billing correctly reflects the shipped quantity tied back to the originating sales order.",
    "The customer receipt correctly applies against the AR transaction, reducing the open balance.",
    "A sales order cancellation after work order creation is correctly flagged as an orphaned work order.",
    "Unauthorized work order completion attempts are correctly blocked at any stage of the journey."
  ],
  "validation_checkpoints": [
    "sales order demand correctly generates a linked work order with matching quantity",
    "production completion correctly triggers reservation against the specific originating sales order",
    "shipment correctly consumes the completed, reserved quantity",
    "AR billing correctly reflects shipped quantity tied back to the sales order",
    "quantity changes before production correctly re-flow through planning and the work order",
    "order cancellation after work order creation correctly flags the resulting orphaned work order",
    "production/shipment delay correctly surfaces as a fulfillment schedule impact",
    "unauthorized completion correctly blocked"
  ]
}