{
  "test_id": "ORCL.P2P.PROC.REQ.REJECT",
  "scenario_name": "Reject 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/reject-requisition/",
  "objective": {
    "intro": "The objective of this test is to validate that an approver's rejection of a requisition pending approval is captured and applied correctly in Oracle Fusion Procurement, and that the resulting status, rejection reason and requester notification behave as expected.",
    "confirms": [
      "the correct requisition is moved out of pending approval when rejected",
      "the requisition status is correctly updated to Rejected",
      "the rejection reason entered by the approver is retained on the requisition record",
      "the requester is notified of the rejection where notifications are configured",
      "the rejection is recorded correctly regardless of single-level or multi-level approval routing",
      "the requisition can be corrected and resubmitted, or otherwise progressed, where the business process allows it"
    ],
    "scope_note": "This scenario covers the rejection of a requisition that is pending approval within Oracle Fusion Procurement TEST/UAT environments. It does not cover the requisition approval decision itself (Approve Requisition), general edits to requisition content (Change Requisition), or withdrawal of a requisition by the requester (Cancel Requisition), which are covered by the related scenarios in the same requisition workflow."
  },
  "preconditions": [
    "A requisition exists in Oracle Fusion Procurement in Pending Approval status.",
    "The test user is assigned as the approver, or an eligible approver, for the requisition and holds reject privileges within the approval workflow.",
    "Where rejection-reason entry is required or offered by configuration, valid rejection reason values are available.",
    "The requisition is visible in the approver's approvals worklist."
  ],
  "test_data": [
    {
      "field": "Requisition Number",
      "example": "${REQUISITION_NUMBER}"
    },
    {
      "field": "Approver",
      "example": "${APPROVER}"
    },
    {
      "field": "Rejection Reason",
      "example": "${REJECTION_REASON}"
    },
    {
      "field": "Requester",
      "example": "${REQUESTER}"
    },
    {
      "field": "Business Unit",
      "example": "${BUSINESS_UNIT}"
    },
    {
      "field": "Requisition Amount",
      "example": "${REQUISITION_AMOUNT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Approvals Worklist",
      "action": "Sign in to Oracle Fusion using an authorised approver test user and navigate to the approvals worklist.",
      "test_data": "",
      "expected_result": "The approvals worklist opens and displays requisitions pending the approver's action.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Locate the Pending Requisition",
      "action": "Search for and open the requisition awaiting approval in the worklist.",
      "test_data": "${REQUISITION_NUMBER}",
      "expected_result": "The correct requisition opens showing its current pending-approval status.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the worklist, entering search criteria and selecting the result."
    },
    {
      "step_number": 3,
      "step_name": "Review Requisition Details",
      "action": "Review the requisition header, lines, requester and amount before deciding on an approval action.",
      "test_data": "${REQUESTER}",
      "expected_result": "Requisition details display correctly for the approver's review.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Select Reject",
      "action": "Select the Reject action on the requisition approval task.",
      "test_data": "",
      "expected_result": "The reject entry screen or rejection-reason panel opens for the approver.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Enter Rejection Reason",
      "action": "Enter the reason for rejecting the requisition, where reason entry is required or offered by configuration.",
      "test_data": "${REJECTION_REASON}",
      "expected_result": "The rejection reason is accepted and attached to the pending rejection.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Confirm Rejection",
      "action": "Confirm and submit the rejection for processing in the test environment.",
      "test_data": "${APPROVER}",
      "expected_result": "Oracle Fusion processes the rejection without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Requisition Status Is Rejected",
      "action": "Reopen or refresh the requisition and confirm its resulting status.",
      "test_data": "",
      "expected_result": "The requisition status is correctly updated to Rejected.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly updated Rejected status is the expected pass condition, not merely a successful submission."
    },
    {
      "step_number": 8,
      "step_name": "Verify Rejection Reason and Requester Notification",
      "action": "Review the requisition's approval history and confirm the rejection reason and notification behavior.",
      "test_data": "",
      "expected_result": "The rejection reason is retained on the requisition, and the requester is notified where notifications are configured.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "The rejection is accepted and processed for the correct requisition.",
    "The requisition status is correctly updated to Rejected.",
    "The rejection reason entered by the approver is retained on the requisition.",
    "The requester is notified of the rejection where notifications are configured.",
    "The requisition can be corrected and resubmitted, or cancelled, depending on business process.",
    "The rejection is visible and traceable in the requisition's approval history."
  ],
  "validation_checkpoints": [
    "Requisition status is correctly updated to Rejected.",
    "The rejection reason is retained on the requisition record.",
    "The requester is notified of the rejection where notification is configured.",
    "The requisition can be corrected and resubmitted if the business process allows it."
  ]
}