{
  "test_id": "ORCL.E2E.PLAN2PRODUCE",
  "scenario_name": "Plan-to-Produce",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "End-to-End SCM",
  "process": "Plan-to-Produce",
  "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/plan-to-produce/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Oracle Fusion Plan-to-Produce journey — demand through supply plan, planned work order, release, material availability, operations, completion, finished goods inventory and planning rerun — with emphasis on cross-stage data continuity, specifically demand correctly driving planned supply, component shortage correctly driving procurement, and completion correctly feeding back into the next planning cycle. This scenario does not re-test each stage's atomic field-level validation, which is already covered on the 16 linked Supply Planning, Manufacturing and Procurement family pages this journey orchestrates.",
    "confirms": [
      "demand from forecast, sales order or shortage correctly drives generation of a planned work order of the correct quantity and due date",
      "existing supply is correctly netted against demand before a new planned work order is generated",
      "a planned work order correctly releases with the correct work definition and component requirements from the bill of material",
      "a component shortage at release or material availability correctly drives a planned purchase requisition and receipt before the work order proceeds",
      "material issue, backflush and operation completion correctly consume and record components and quantities against the released work order",
      "work order completion correctly reconciles against the released quantity and updates finished goods on-hand",
      "a planning rerun after completion correctly reflects the new supply and reduces the outstanding net requirement"
    ],
    "scope_note": "This scenario validates the hand-offs and cross-stage data integrity of the Plan-to-Produce 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, Planned Orders, Release Planned Order, Supply Demand Balance, Planning Exceptions, Create Work Order, Release Work Order, Issue Material, Material Shortage, Start Operation, Complete Operation, Complete Work Order, Partial Completion, Manufacturing Exceptions, Create Purchase Requisition and Receive Purchase Order family pages — this page links to and orchestrates those live pages into an end-to-end journey."
  },
  "preconditions": [
    "The 16 Supply Planning, Manufacturing and Procurement family pages referenced by this journey are individually functional in the target Oracle Fusion SCM environment.",
    "A valid item, bill of material, work definition, manufacturing organization and supply plan are available and enabled for planning and manufacturing.",
    "Collected supply and demand data is current for the supply plan under test, including forecast and sales order demand where applicable.",
    "The test user holds the roles required to execute each stage of the journey, or alternate unauthorized-user personas are available for security testing.",
    "Component availability, lead times, work definitions and shortage-handling configuration are set according to the target environment — this scenario does not assume a universal shortage or configuration rule."
  ],
  "test_data": [
    {
      "field": "Plan Name",
      "example": "${PLAN_NAME}"
    },
    {
      "field": "Planned Order",
      "example": "${PLANNED_ORDER}"
    },
    {
      "field": "Work Order",
      "example": "${WORK_ORDER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Component",
      "example": "${COMPONENT}"
    },
    {
      "field": "Manufacturing Organization",
      "example": "${MANUFACTURING_ORG}"
    },
    {
      "field": "Due Date",
      "example": "${DUE_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Run the Supply Plan and Review Planned Work Orders",
      "action": "Run the supply plan and review planned work orders generated from forecast, sales order or shortage-driven demand, referencing the standard Run Supply Plan and Planned Orders test scenarios.",
      "test_data": "${PLAN_NAME} / ${ITEM} / ${QUANTITY}",
      "expected_result": "The supply plan runs successfully and planned work orders are generated for the required item, quantity and due date.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Release a Planned Work Order",
      "action": "Release a planned work order with the correct work definition, referencing the standard Release Planned Order and Create Work Order test scenarios.",
      "test_data": "${PLANNED_ORDER} / ${WORK_ORDER} / ${DUE_DATE}",
      "expected_result": "The work order is created from the planned order with quantity, due date and work definition correctly carried forward.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Verify Component Availability and Resolve Shortages",
      "action": "Check component availability against the bill of material and, where a shortage is detected, raise a planned purchase requisition and confirm receipt before proceeding, referencing the standard Material Shortage, Create Purchase Requisition and Receive Purchase Order test scenarios.",
      "test_data": "${WORK_ORDER} / ${COMPONENT} / ${MANUFACTURING_ORG}",
      "expected_result": "Components are confirmed available, or a shortage is correctly flagged and resolved through procurement before material issue proceeds.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Issue Required Material",
      "action": "Issue or backflush the material components required by the work order's bill of material, referencing the standard Issue Material test scenario.",
      "test_data": "${WORK_ORDER} / ${COMPONENT} / ${QUANTITY}",
      "expected_result": "Required components are correctly consumed against the work order's bill of material requirement.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Start and Complete Operations",
      "action": "Start and complete each operation on the work order, including partial completion, reject and scrap handling where applicable, referencing the standard Start Operation and Complete Operation test scenarios.",
      "test_data": "${WORK_ORDER} / ${OPERATION} / ${QUANTITY}",
      "expected_result": "Operations are correctly recorded, with completed, rejected and scrapped quantities correctly captured against the work order.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Complete the Work Order",
      "action": "Complete the work order for the produced quantity, whether full or partial, referencing the standard Complete Work Order and Partial Completion test scenarios.",
      "test_data": "${WORK_ORDER} / ${QUANTITY} / ${COMPLETED_QUANTITY}",
      "expected_result": "The work order completion is correctly recorded and reconciles against the released work order quantity.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Finished Goods On-Hand Updates",
      "action": "Confirm that finished item on-hand inventory correctly increases by the completed quantity following work order completion.",
      "test_data": "${ITEM} / ${MANUFACTURING_ORG} / ${COMPLETED_QUANTITY}",
      "expected_result": "Finished goods on-hand for the item correctly reflects the completed work order quantity.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — completed supply correctly reaching finished goods on-hand is the expected pass condition, not merely a successful completion transaction."
    },
    {
      "step_number": 8,
      "step_name": "Verify Planning Rerun Reflects the New Supply",
      "action": "Rerun the supply plan and confirm the net requirement for the item correctly reduces to reflect the newly completed supply.",
      "test_data": "${PLAN_NAME} / ${ITEM} / ${WORK_ORDER}",
      "expected_result": "The planning rerun correctly reflects the new on-hand supply and reduces the outstanding net requirement for the item.",
      "validation_type": "business_assertion",
      "note": "This is the final business assertion for the scenario — a planning rerun that correctly reflects completed supply, closing the loop from demand back into planning, is the expected pass condition for the full journey."
    }
  ],
  "expected_results": [
    "The supply plan runs successfully and generates planned work orders for the required item, quantity and due date from forecast, sales order or shortage-driven demand.",
    "Planned work order quantity, due date and work definition correctly carry forward into the released work order.",
    "Component availability is correctly confirmed at release, or a shortage correctly drives a planned purchase requisition and receipt before the journey proceeds.",
    "Material issue and operations correctly consume and record components and quantities against the released work order.",
    "The completed work order quantity correctly reconciles against the released quantity, including partial completions, rejections and scrap.",
    "Finished goods on-hand correctly updates to reflect the completed quantity.",
    "A subsequent planning rerun correctly reflects the new supply and reduces the outstanding net requirement."
  ],
  "validation_checkpoints": [
    "demand correctly generates planned supply of the correct quantity and date",
    "released work order correctly reflects the planned order and correct work definition",
    "components correctly derive from the bill of material",
    "material issue correctly consumes required components",
    "completion correctly reconciles against the released work order quantity",
    "finished goods correctly update on-hand",
    "planning rerun correctly reflects new supply and reduces net requirement"
  ]
}