{
  "test_id": "ORCL.P2P.PROC.PO.INQUIRY",
  "scenario_name": "Purchase Order Inquiry",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Procurement",
  "module": "Procurement",
  "process": "Purchase Orders",
  "business_flow": "Procure-to-Pay",
  "scenario_type": "Positive / Functional",
  "priority": "High",
  "automation_status": "SyntraFlow Ready",
  "library": "Syntra Standard",
  "canonical_url": "https://www.syntraflow.cloud/oracle-erp-testing-tool/test-library/scm/procurement/purchase-orders/purchase-order-inquiry/",
  "objective": {
    "intro": "The objective of this test is to validate that purchase order information can be accurately searched, retrieved and verified in Oracle Fusion SCM Procurement using PO number, supplier, buyer, status, date range, item and Business Unit as search criteria, and that the retrieved purchase order reflects correct line, receipt, invoice match and change history detail.",
    "confirms": [
      "the correct purchase order is retrieved for a given set of search criteria",
      "purchase order amounts and quantities displayed match the underlying purchase order",
      "purchase order status is displayed correctly",
      "supplier and supplier site information on the retrieved purchase order is correct",
      "receipt and invoice match state information is available and accurate",
      "purchase order change history is available and traceable",
      "Oracle correctly enforces validation and access restrictions when search criteria are invalid or when a user lacks access to a requested purchase order (DATA_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario covers search, retrieval and verification of existing purchase order information in Oracle Fusion SCM Procurement TEST/UAT environments. It does not cover creation, approval, change or cancellation of purchase orders, which are covered by the separate Create Purchase Order and related scenarios in the same Purchase Orders cluster."
  },
  "preconditions": [
    "Eligible purchase orders exist in the target Oracle Fusion SCM environment across a representative range of statuses.",
    "The test user has view/inquiry access to Purchase Orders for the relevant procurement Business Unit.",
    "Purchase orders used in the scenario have associated receipt and/or invoice match data where match-state verification is required.",
    "Search indexes and view objects underlying purchase order inquiry are current for the test environment."
  ],
  "test_data": [
    {
      "field": "PO Number",
      "example": "${PO_NUMBER}"
    },
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Supplier Site",
      "example": "${SUPPLIER_SITE}"
    },
    {
      "field": "Buyer",
      "example": "${BUYER}"
    },
    {
      "field": "Status",
      "example": "${STATUS}"
    },
    {
      "field": "Date Range",
      "example": "${DATE_RANGE}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Procurement BU",
      "example": "${PROCUREMENT_BU}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Procurement",
      "action": "Sign in to Oracle Fusion using an authorised procurement test user and navigate to the Procurement work area.",
      "test_data": "",
      "expected_result": "The Procurement work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Purchase Order Inquiry",
      "action": "Open the Purchase Orders inquiry/search page for the relevant procurement Business Unit.",
      "test_data": "${PROCUREMENT_BU}",
      "expected_result": "The purchase order search page opens for the correct procurement Business Unit.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Enter Search Criteria",
      "action": "Enter one or more search criteria — such as PO number, supplier, buyer, status, date range or item — to locate the target purchase order.",
      "test_data": "${PO_NUMBER} / ${SUPPLIER} / ${BUYER} / ${STATUS} / ${DATE_RANGE} / ${ITEM}",
      "expected_result": "The search criteria are accepted without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Review Search Results",
      "action": "Review the list of purchase orders returned by the search.",
      "test_data": "",
      "expected_result": "The returned purchase orders match the entered search criteria.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as submitting the search and reading the results grid."
    },
    {
      "step_number": 5,
      "step_name": "Open the Target Purchase Order",
      "action": "Select and open the specific purchase order to be verified.",
      "test_data": "${PO_NUMBER}",
      "expected_result": "The purchase order opens and displays header and line detail.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review PO Lines and Totals",
      "action": "Review the purchase order lines, quantities, prices and totals.",
      "test_data": "",
      "expected_result": "Line quantities, prices and totals displayed match the underlying purchase order.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Review Receipt and Invoice Match Status",
      "action": "Review the receipt status and invoice match state associated with the purchase order lines.",
      "test_data": "",
      "expected_result": "Receipt and invoice match state information is displayed and reflects the underlying receiving and matching data.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Review Change History",
      "action": "Review the change history recorded against the purchase order, including any prior amendments.",
      "test_data": "",
      "expected_result": "Change history is available and consistent with changes previously made to the purchase order, and all retrieved header, line, receipt, match and history detail is confirmed correct.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly retrieved purchase order with accurate line, receipt, match and history detail is the expected pass condition, not merely a successful search."
    }
  ],
  "expected_results": [
    "The correct purchase order is retrieved for the entered search criteria.",
    "Purchase order line amounts and quantities displayed match the underlying purchase order.",
    "Purchase order status is displayed correctly.",
    "Supplier and supplier site information is displayed correctly.",
    "Receipt and invoice match state information is available and accurate.",
    "Purchase order change history is available and traceable.",
    "A search with no matching criteria returns a correctly empty result set, and an unauthorized search is correctly access-restricted."
  ],
  "validation_checkpoints": [
    "Correct PO retrieved.",
    "Amounts and quantities correct.",
    "Status correct.",
    "Supplier and site correct.",
    "Change history available."
  ]
}