{
  "test_id": "ORCL.E2E.PLAN2PROC",
  "scenario_name": "Plan-to-Procure",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "End-to-End SCM",
  "process": "Plan-to-Procure",
  "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-procure/",
  "objective": {
    "intro": "The objective of this test is to validate the complete Plan-to-Procure journey in Oracle Fusion SCM — demand, planning data collection, supply plan run, planned purchase order generation, release, purchase order, supplier, receipt and inventory update — with emphasis on the planning-to-procurement hand-off, specifically that a planned order correctly becomes a real procurement document with the correct quantity, date and supplier, rather than re-testing each stage's individual field-level validation, which is already covered on the linked Supply Planning and Procurement family pages this scenario orchestrates.",
    "confirms": [
      "the net demand quantity calculated during planning data collection and the supply plan run correctly drives the recommended purchase requirement",
      "the supply plan correctly generates a planned purchase order of the correct quantity, date and supplier for net demand",
      "releasing the planned purchase order correctly creates a matching purchase order that carries forward quantity, date and supplier",
      "the purchase order correctly requires and receives approval per configuration before it is available for receipt",
      "a full or partial receipt correctly reconciles against the purchase order quantity, and inventory on-hand correctly updates",
      "late supply and other exceptions are correctly flagged rather than silently accepted",
      "an invalid supplier source, non-purchasable item or invalid organization assignment correctly blocks planned order release",
      "unauthorized users are correctly blocked from creating or approving a procurement document at any stage of the journey"
    ],
    "scope_note": "This scenario validates the hand-offs and cross-stage data integrity of the Plan-to-Procure journey in Oracle Fusion SCM TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the Collect Planning Data, Run Supply Plan, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Order, Approve Purchase Order, Receive Purchase Order and Partial Receipt family pages — this page links to and orchestrates those live pages into an end-to-end journey."
  },
  "preconditions": [
    "The Supply Planning and Procurement family pages referenced by this journey — Collect Planning Data, Run Supply Plan, Planned Orders, Release Planned Order, Planning Exceptions, Create Purchase Order, Approve Purchase Order, Receive Purchase Order and Partial Receipt — are individually functional in the target Oracle Fusion SCM environment.",
    "A valid item, organization, sourcing rule, supplier and supply plan are available and enabled for planning and procurement.",
    "Collected planning 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.",
    "Supplier lead times, purchasing approval hierarchies and item purchasing/organization assignments are configured according to the target environment — this scenario does not assume a single universal supplier or approval configuration applies to every item."
  ],
  "test_data": [
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Plan Name",
      "example": "${PLAN_NAME}"
    },
    {
      "field": "Planned Order",
      "example": "${PLANNED_ORDER}"
    },
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Purchase Order",
      "example": "${PURCHASE_ORDER}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Receipt",
      "example": "${RECEIPT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Collect Planning Data",
      "action": "Collect current supply and demand planning data for the supply plan, referencing the standard Collect Planning Data test scenario.",
      "test_data": "${ITEM} / ${ORGANIZATION} / ${PLAN_NAME}",
      "expected_result": "Planning data collection completes successfully and current supply and demand data is available to the supply plan.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Run the Supply Plan and Review Planned Purchase Orders",
      "action": "Run the supply plan and review the planned purchase orders generated for net demand, referencing the standard Run Supply Plan and Planned Orders test scenarios.",
      "test_data": "${PLAN_NAME} / ${PLANNED_ORDER} / ${QUANTITY}",
      "expected_result": "The supply plan correctly generates planned purchase order ${PLANNED_ORDER} for the correct quantity and required date.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Release the Planned Order to a Purchase Order",
      "action": "Release the planned purchase order to create a procurement document, referencing the standard Release Planned Order test scenario.",
      "test_data": "${PLANNED_ORDER} / ${SUPPLIER} / ${REQUIRED_DATE}",
      "expected_result": "Release correctly creates purchase order ${PURCHASE_ORDER} carrying forward the planned order's quantity, date and supplier.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Approve the Purchase Order",
      "action": "Route the purchase order for approval per the configured approval hierarchy, referencing the standard Approve Purchase Order test scenario.",
      "test_data": "${PURCHASE_ORDER}",
      "expected_result": "The purchase order correctly requires and receives approval before it is available for receipt.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Receive Against the Purchase Order",
      "action": "Record a full or partial receipt against the approved purchase order, referencing the standard Receive Purchase Order and Partial Receipt test scenarios.",
      "test_data": "${PURCHASE_ORDER} / ${RECEIPT} / ${QUANTITY}",
      "expected_result": "The receipt correctly reconciles against the purchase order quantity, whether full or partial.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Inventory On-Hand Updates",
      "action": "Compare on-hand inventory for the item and organization before and after the receipt.",
      "test_data": "${ITEM} / ${ORGANIZATION} / ${RECEIPT}",
      "expected_result": "Inventory on-hand correctly increases by the received quantity following the receipt transaction.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — correctly updated on-hand inventory following receipt is the expected pass condition, not merely a successful transaction."
    },
    {
      "step_number": 7,
      "step_name": "Verify Planning Rerun Reflects the New Supply",
      "action": "Rerun the supply plan after receipt and review the updated supply/demand balance, referencing the standard Run Supply Plan test scenario.",
      "test_data": "${PLAN_NAME} / ${ITEM} / ${REQUIRED_DATE}",
      "expected_result": "Planning rerun correctly reflects the newly received supply, 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": [
    "Planning data collection completes successfully and current supply and demand data is available to the supply plan.",
    "The supply plan correctly generates a planned purchase order of the correct quantity and required date for net demand.",
    "Releasing the planned order correctly creates a purchase order carrying forward the planned order's quantity, date and supplier.",
    "The purchase order correctly requires and receives approval before it is available for receipt.",
    "Receipt correctly reconciles against the purchase order quantity, whether full or partial.",
    "Inventory on-hand correctly increases by the received quantity following the receipt transaction.",
    "Planning rerun correctly reflects the newly received supply, with the previously open requirement now covered."
  ],
  "validation_checkpoints": [
    "net demand correctly generates a planned purchase order of the correct quantity and date",
    "planned order supplier correctly carries into the released purchase order",
    "purchase order correctly requires approval per configuration",
    "receipt correctly reconciles against the purchase order quantity",
    "late supply correctly flagged rather than silently accepted",
    "planning rerun correctly reflects updated supply after receipt",
    "invalid source/item/organization correctly blocks planned order release"
  ]
}