{
  "test_id": "ORCL.P2P.PROC.REQ.APPROVE",
  "scenario_name": "Approve Requisition",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Procurement",
  "module": "Procurement",
  "process": "Requisitions",
  "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/requisitions/approve-requisition/",
  "objective": {
    "intro": "Validate requisition approval routing and successful approval according to configured rules — including how a submitted requisition is routed to the correct approver, how the approval action updates requisition status, and how approval history is retained for audit purposes.",
    "confirms": [
      "a submitted requisition awaiting approval is correctly identified and appears in the approver's worklist",
      "the requisition routes to the correct approver based on the applicable rule (amount, category, or requisitioning BU context)",
      "single-level and multi-level approval hierarchies are enforced as configured",
      "the approval action is correctly processed and requisition status updates accordingly",
      "approval history is captured and retained against the requisition",
      "an approved requisition becomes available for downstream purchasing activity where applicable",
      "approvers without the appropriate role or access cannot action the requisition"
    ],
    "scope_note": "This scenario does not claim that requisition creation, submission, rejection or subsequent changes are covered — those are addressed by separate test scenarios in the Requisitions lifecycle."
  },
  "preconditions": [
    "Oracle Fusion Procurement access is configured and available for the test user.",
    "The requisition has been submitted and is pending approval.",
    "Approval rules are configured for the applicable requisitioning BU, 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 Requisition approvals."
  ],
  "test_data": [
    {
      "field": "Requisition Number",
      "example": "${REQUISITION_NUMBER}"
    },
    {
      "field": "Requisitioning BU",
      "example": "${REQUISITIONING_BU}"
    },
    {
      "field": "Category",
      "example": "${CATEGORY}"
    },
    {
      "field": "Total Amount",
      "example": "${TOTAL_AMOUNT}"
    },
    {
      "field": "Approval Threshold",
      "example": "${APPROVAL_THRESHOLD} — customer-configured value, not a fixed amount"
    },
    {
      "field": "Approver",
      "example": "${APPROVER} — valid approver assigned to the applicable rule and level"
    },
    {
      "field": "Approval Rule Context",
      "example": "Amount-based, category-based, or BU-based — scenario-defined"
    },
    {
      "field": "Approval Action",
      "example": "Approve / Delegate, where applicable"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In as Approver",
      "action": "Sign in to Oracle Fusion as the approver assigned to the requisition.",
      "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 requisitions pending action.",
      "test_data": "",
      "expected_result": "The Approvals worklist opens and displays requisitions awaiting the approver's action.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Open the Pending Requisition",
      "action": "Locate and open the requisition awaiting approval.",
      "test_data": "${REQUISITION_NUMBER}",
      "expected_result": "The correct requisition 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 requisition number, clicking Search and selecting the result."
    },
    {
      "step_number": 4,
      "step_name": "Review Requisition Details",
      "action": "Review the requisition lines, requisitioning BU, category and total amount presented to the approver.",
      "test_data": "",
      "expected_result": "Requisition 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 requisition routed to this approver based on the applicable approval rule.",
      "test_data": "${APPROVAL_THRESHOLD}",
      "expected_result": "The requisition routes to the correct approver based on the amount, category, or BU rule in effect.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Approve the Requisition",
      "action": "Take the approval action on the requisition.",
      "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 requisition status updates to reflect the approval outcome.",
      "test_data": "",
      "expected_result": "Requisition 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 Approval History Retained",
      "action": "Review the requisition's approval history to confirm the action and approver are recorded.",
      "test_data": "",
      "expected_result": "Approval history is retained against the requisition, showing the approver, the action taken and the date.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "Requisitions requiring approval route correctly to the configured approver based on the applicable rule (amount, category, or BU context).",
    "Single-level and multi-level approval hierarchies are enforced as configured.",
    "The approval action is correctly processed and requisition status updates accordingly.",
    "Approval history is captured and retained against the requisition.",
    "An approved requisition becomes available for downstream purchasing activity where applicable.",
    "Approvers without the appropriate role or access cannot action the requisition.",
    "Delegated approvals, where configured, are correctly attributed to the delegate."
  ],
  "validation_checkpoints": [
    "Correct approver is identified for the applicable rule and level.",
    "Requisition status updates to Approved.",
    "Approval history is retained against the requisition.",
    "Requisition becomes available for purchasing where applicable."
  ]
}