{
  "test_id": "ORCL.SCM.E2E.P2R",
  "scenario_name": "Procure-to-Receive",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "End-to-End SCM",
  "process": "Procure-to-Receive",
  "business_flow": "Procure-to-Pay",
  "scenario_type": "End-to-End / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/scm/end-to-end/procure-to-receive/",
  "objective": {
    "intro": "The objective of this test is to validate the end-to-end Procure-to-Receive journey in Oracle Fusion SCM — requisition creation and approval, purchase order creation and approval, and goods receipt including partial and exception receipts — with emphasis on data correctly carrying forward across each stage (quantity, price, supplier, item), rather than re-testing each stage's individual field-level validation, which is already covered on the linked Procurement family pages this scenario orchestrates.",
    "confirms": [
      "the approved requisition's item, quantity and pricing data correctly carry forward into the purchase order",
      "the approved purchase order's item, quantity, supplier and pricing data correctly carry forward into the goods receipt",
      "partial receipts correctly track remaining open quantity across the journey",
      "inspection-required items correctly route to acceptance or to receiving exceptions",
      "a purchase order change made after requisition approval is correctly reflected in subsequent receiving",
      "unauthorized users are correctly blocked from receiving at any stage of the journey"
    ],
    "scope_note": "This scenario validates the hand-offs and cross-stage data integrity of the Procure-to-Receive journey in Oracle Fusion SCM TEST/UAT environments. It does not duplicate the individual field-level scenario coverage already tested on the Create Purchase Requisition, Approve Requisition, Create Purchase Order, Approve Purchase Order, Receive Purchase Order, Partial Receipt, Inspect Receipt and Receiving Exceptions family pages — this page links to and orchestrates those live pages into an end-to-end journey."
  },
  "preconditions": [
    "The requisitioning, approval, purchase order and receiving Procurement family pages referenced by this journey are individually functional in the target Oracle Fusion SCM environment.",
    "A valid supplier, item and organization are available and enabled for procurement and receiving.",
    "Approval workflows for requisitions and purchase orders are 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.",
    "Receiving tolerances, inspection requirements and receiving exception routing are configured according to the target environment — this scenario does not assume a universal tolerance or inspection configuration."
  ],
  "test_data": [
    {
      "field": "Requisition",
      "example": "${REQUISITION}"
    },
    {
      "field": "Purchase Order",
      "example": "${PURCHASE_ORDER}"
    },
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Receipt",
      "example": "${RECEIPT}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "User Role",
      "example": "${USER_ROLE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Create and Approve Purchase Requisition",
      "action": "Create a purchase requisition for the required item and quantity, then route it through approval, referencing the standard Create Purchase Requisition and Approve Requisition test scenarios.",
      "test_data": "${REQUISITION} / ${ITEM} / ${QUANTITY}",
      "expected_result": "The requisition is created and approved, with its status correctly reflecting approval before purchase order creation begins.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Create and Approve Purchase Order Referencing the Requisition",
      "action": "Create a purchase order sourced from the approved requisition and route it through approval, referencing the standard Create Purchase Order and Approve Purchase Order test scenarios.",
      "test_data": "${PURCHASE_ORDER} / ${SUPPLIER} / ${REQUISITION}",
      "expected_result": "The purchase order is created referencing the approved requisition and is approved before receiving begins.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Receive Against the Purchase Order",
      "action": "Receive against the approved purchase order — in full, as a partial receipt, or capturing an inspection or receiving exception where the scenario calls for it — referencing the standard Receive Purchase Order, Partial Receipt, Inspect Receipt and Receiving Exceptions test scenarios.",
      "test_data": "${RECEIPT} / ${PURCHASE_ORDER} / ${ORGANIZATION}",
      "expected_result": "The receipt is recorded against the purchase order with the correct quantity, and any inspection or exception is routed as expected.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Verify Quantity and Pricing Consistency Across Stages",
      "action": "Compare the item, quantity and price captured at the requisition, purchase order and receipt stages of the journey.",
      "test_data": "${ITEM} / ${QUANTITY}",
      "expected_result": "Quantity and pricing data correctly carry forward from the requisition to the purchase order to the receipt, with any deviations correctly flagged.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the journey — matching data across all three stages is the expected pass condition, not merely three individually successful transactions."
    },
    {
      "step_number": 5,
      "step_name": "Verify Inspection-Required Items Route Appropriately",
      "action": "Where the received item requires inspection, confirm the inspection result correctly routes the receipt to acceptance or to receiving exceptions.",
      "test_data": "${ITEM} / ${RECEIPT}",
      "expected_result": "Inspection-required items are correctly routed to acceptance on pass or to receiving exceptions on reject.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Audit Trail Links Requisition, Purchase Order and Receipt",
      "action": "Review the audit trail or document reference chain connecting the requisition, purchase order and receipt for the journey.",
      "test_data": "${REQUISITION} / ${PURCHASE_ORDER} / ${RECEIPT}",
      "expected_result": "The requisition, purchase order 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 is the expected pass condition for the full journey."
    }
  ],
  "expected_results": [
    "The requisition is created and approved before purchase order creation begins.",
    "The purchase order correctly reflects the approved requisition's item, quantity and pricing data.",
    "The goods receipt correctly reflects the purchase order's item, quantity and supplier data, including partial and exception receipts.",
    "Inspection-required items are correctly routed to acceptance or to receiving exceptions.",
    "Purchase order changes made after requisition approval are correctly reflected in subsequent receiving.",
    "Unauthorized receiving attempts are correctly blocked at any stage of the journey."
  ],
  "validation_checkpoints": [
    "requisition data correctly carries forward into the purchase order",
    "purchase order data correctly carries forward into the receipt",
    "partial receipts correctly track remaining open quantity across the journey",
    "inspection results correctly route to acceptance or exception handling",
    "PO changes correctly reflect in subsequent receiving",
    "unauthorized receipt actions correctly blocked at any stage"
  ]
}