{
  "test_id": "ORCL.P2P.PROC.PO.APPROVE",
  "scenario_name": "Approve 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/approve-purchase-order/",
  "objective": {
    "intro": "Validate purchase order approval routing and successful approval according to configured rules — including how a submitted PO is routed to the correct approver, how the approval action updates PO status, and how approval history is retained for audit purposes.",
    "confirms": [
      "a submitted PO awaiting approval is correctly identified and appears in the approver's worklist",
      "the PO routes to the correct approver based on the applicable rule (amount, category, supplier, or procurement BU context)",
      "single-level and multi-level approval hierarchies are enforced as configured",
      "the approval action is correctly processed and PO status updates accordingly",
      "approval history is captured and retained against the PO",
      "an approved PO becomes eligible for downstream processing such as receiving and invoicing where applicable",
      "approvers without the appropriate role or access cannot action the PO"
    ],
    "scope_note": "This scenario does not claim that PO creation, change or cancellation are covered — those are addressed by separate test scenarios in the Purchase Orders lifecycle."
  },
  "preconditions": [
    "Oracle Fusion Procurement access is configured and available for the test user.",
    "The purchase order has been submitted and is pending approval.",
    "Approval rules are configured for the applicable procurement BU, supplier, category and amount ranges.",
    "A valid approver is assigned to the applicable approval rule and level.",
    "The test user (or approver context) has the appropriate role and access to action PO approvals."
  ],
  "test_data": [
    {
      "field": "PO Number",
      "example": "${PO_NUMBER}"
    },
    {
      "field": "Procurement BU",
      "example": "${PROCUREMENT_BU}"
    },
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Total Amount",
      "example": "${TOTAL_AMOUNT}"
    },
    {
      "field": "Approval Threshold",
      "example": "${APPROVAL_THRESHOLD} — customer-configured value, not a fixed amount"
    },
    {
      "field": "Buyer",
      "example": "${BUYER}"
    },
    {
      "field": "Approver",
      "example": "${APPROVER} — valid approver assigned to the applicable rule and level"
    },
    {
      "field": "Approval Rule Context",
      "example": "Amount-based, category-based, supplier-based, or BU-based — scenario-defined"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In as Approver",
      "action": "Sign in to Oracle Fusion as the approver assigned to the purchase order.",
      "test_data": "${APPROVER}",
      "expected_result": "The approver signs in successfully and lands on the home page.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Approvals Worklist",
      "action": "Navigate to the Approvals worklist to view purchase orders pending action.",
      "test_data": "",
      "expected_result": "The Approvals worklist opens and displays purchase orders awaiting the approver's action.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Open the Pending Purchase Order",
      "action": "Locate and open the purchase order awaiting approval.",
      "test_data": "${PO_NUMBER}",
      "expected_result": "The correct purchase order is opened and its status confirms it is pending approval.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening search, entering the PO number, clicking Search and selecting the result."
    },
    {
      "step_number": 4,
      "step_name": "Review Purchase Order Details",
      "action": "Review the PO lines, procurement BU, supplier and total amount presented to the approver.",
      "test_data": "",
      "expected_result": "Purchase order details are complete and available for review before an approval decision is made.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Verify Routing Rule Applied Correctly",
      "action": "Confirm the purchase order routed to this approver based on the applicable approval rule.",
      "test_data": "${APPROVAL_THRESHOLD}",
      "expected_result": "The purchase order routes to the correct approver based on the amount, category, supplier, or BU rule in effect.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Approve the Purchase Order",
      "action": "Take the approval action on the purchase order.",
      "test_data": "",
      "expected_result": "The approval action is accepted by Oracle Fusion without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Status Updated",
      "action": "Confirm the purchase order status updates to reflect the approval outcome.",
      "test_data": "",
      "expected_result": "Purchase order status accurately reflects the approval outcome — for example Approved, or Pending Next-Level Approval — consistent with the configured routing rule.",
      "validation_type": "business_assertion",
      "note": "This is the main business assertion for the scenario — the test does not stop merely because the approval action was accepted successfully."
    },
    {
      "step_number": 8,
      "step_name": "Verify Downstream Eligibility",
      "action": "Confirm the approved purchase order becomes eligible for downstream processing.",
      "test_data": "",
      "expected_result": "The approved purchase order is available for downstream activity such as receiving and invoicing, where applicable, and approval history shows the approver, action taken and date.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "Purchase orders requiring approval route correctly to the configured approver based on the applicable rule (amount, category, supplier, or BU context).",
    "Single-level and multi-level approval hierarchies are enforced as configured.",
    "The approval action is correctly processed and PO status updates accordingly.",
    "Approval history is captured and retained against the PO.",
    "An approved PO becomes eligible for downstream processing such as receiving and invoicing where applicable.",
    "Approvers without the appropriate role or access cannot action the PO.",
    "PO approvals across different buyers and procurement BUs follow the correct rule for each context."
  ],
  "validation_checkpoints": [
    "PO routes to the correct approver for the applicable rule and level.",
    "PO status updates to Approved.",
    "Approval history is retained against the PO.",
    "PO becomes eligible for downstream processing where applicable."
  ]
}