{
  "test_id": "ORCL.P2P.PROC.PO.CLOSE",
  "scenario_name": "Close Purchase Order",
  "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/close-purchase-order/",
  "objective": {
    "intro": "The objective of this test is to verify that an authorized Procurement user can manually close an eligible purchase order, or a specific line within it, in Oracle Fusion, and confirm the resulting status and downstream impact — separately from the business-driven closure that Oracle can apply automatically once a line is fully fulfilled.",
    "confirms": [
      "the selected purchase order or purchase order line is eligible for closure",
      "a full purchase order can be closed, and a single line can be closed independently on a multi-line purchase order",
      "closure can be applied for receiving, for invoicing, or for both, where the customer's configuration supports it",
      "the purchase order or line status correctly updates to Closed",
      "a closed purchase order or line is no longer available for further receiving or invoicing where that restriction is expected",
      "the closure is retained in purchase order history rather than removing the record"
    ],
    "scope_note": "This scenario does not claim that every downstream receiving, invoicing or budgetary-control interaction is covered — those depend on the customer's specific Oracle Fusion configuration and are addressed by separate test scenarios."
  },
  "preconditions": [
    "Oracle Fusion Procurement Purchase Orders is configured and available to the test user.",
    "An existing purchase order exists, with at least one line in a status eligible for closure.",
    "No blocking open obligations remain against the purchase order or line, such as an outstanding receipt or unmatched invoice, where the customer's configuration treats these as blocking.",
    "The purchase order or line has not already been closed.",
    "The test user has the appropriate security/privilege to close purchase orders."
  ],
  "test_data": [
    {
      "field": "Purchase Order Number",
      "example": "${PO_NUMBER}"
    },
    {
      "field": "Line Number",
      "example": "${LINE_NUMBER}"
    },
    {
      "field": "PO/Line Status",
      "example": "Open / Partially Received / Fully Received / Invoiced — eligible for closure"
    },
    {
      "field": "Closure Scope",
      "example": "Full Purchase Order or Specific Line"
    },
    {
      "field": "Close Reason",
      "example": "${CLOSE_REASON}"
    },
    {
      "field": "Buyer",
      "example": "${BUYER}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion Cloud with a user that holds purchase order closure privileges.",
      "test_data": "${BUYER}",
      "expected_result": "The user successfully signs in and lands on the Oracle Fusion home page.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Purchase Order",
      "action": "Navigate to the Purchase Orders work area and search for the target purchase order.",
      "test_data": "${PO_NUMBER}",
      "expected_result": "The correct purchase order is located and its current status and lines are displayed.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening search, entering the purchase order number, clicking Search and selecting the result."
    },
    {
      "step_number": 3,
      "step_name": "Verify Eligibility for Closure",
      "action": "Review the purchase order or line status and any open obligations to confirm it is eligible for closure.",
      "test_data": "${LINE_NUMBER}",
      "expected_result": "The purchase order or line is confirmed as eligible for closure, with no unresolved blocking obligations.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Select Close (Full Purchase Order or Line)",
      "action": "Select the Close action for the full purchase order, or for a specific line where only a line-level closure is required, and enter a close reason where applicable.",
      "test_data": "${CLOSE_REASON}",
      "expected_result": "The Close Purchase Order (or Close Line) page or dialog opens for the selected scope and accepts the close reason without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Confirm Closure",
      "action": "Confirm and submit the closure.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the closure request without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Status Updated",
      "action": "Confirm the purchase order's or line's status following the closure.",
      "test_data": "",
      "expected_result": "Purchase order or line status updates to Closed, with the close reason correctly recorded where applicable.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 7,
      "step_name": "Verify Downstream Behavior Is Correct",
      "action": "Confirm that the closed purchase order or line correctly restricts further receiving and/or invoicing as expected for the closure scope selected, while remaining visible in purchase order history.",
      "test_data": "${PO_NUMBER}",
      "expected_result": "The closed purchase order or line correctly blocks the expected downstream activity — such as further receiving or invoicing — and remains traceable in history rather than being removed.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — a purchase order closure must be enforced downstream and must not silently remove purchase order history."
    }
  ],
  "expected_results": [
    "An eligible purchase order or purchase order line closes successfully.",
    "Purchase order or line status updates correctly to Closed.",
    "Close reason is correctly recorded where applicable.",
    "A closed full purchase order and a closed single line both behave correctly and independently of other lines.",
    "The closed purchase order or line correctly restricts further receiving and/or invoicing where that restriction is expected.",
    "The closure remains traceable in purchase order history.",
    "No unexpected save errors occur.",
    "The closed purchase order or line does not silently disappear from history or reporting."
  ],
  "validation_checkpoints": [
    "Purchase order or line closure status is correct.",
    "Downstream receiving/invoicing behavior is correct.",
    "Closure is retained in purchase order history."
  ]
}