{
  "test_id": "ORCL.P2P.PROC.REQ.SUBMIT",
  "scenario_name": "Submit 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/submit-requisition/",
  "objective": {
    "intro": "The objective of this test is to validate that a complete draft requisition — with all mandatory header and line data captured — can be submitted into Oracle Fusion's configured approval flow, and that the requisition's status, approval routing and traceability reflect the submission correctly.",
    "confirms": [
      "the requisition submits successfully once all mandatory data is present",
      "the requisition status changes from draft to the correct in-process or approval status",
      "approval routing begins where an approval rule applies to the requisition",
      "requisitions that do not require approval complete without unnecessary routing",
      "the submitted requisition remains traceable back to the originating draft",
      "Oracle's validations correctly prevent submission of an incomplete or ineligible requisition"
    ],
    "scope_note": "This scenario covers submission of an already-complete draft requisition into the configured approval workflow within Oracle Fusion Procurement TEST/UAT environments. It does not cover creation of the requisition itself, which is covered by the separate Create Purchase Requisition scenario, or the approval action itself, which is covered by the separate Approve Requisition scenario in the same Requisitions family."
  },
  "preconditions": [
    "A complete draft requisition exists in Oracle Fusion Procurement with all mandatory header and line data captured.",
    "The requester submitting the requisition holds the appropriate submit privileges.",
    "An approval workflow is configured for the requisitioning business unit and category, where applicable.",
    "The requisition's charge account, category and supplier (where entered) are valid and active.",
    "The test user is signed in to an Oracle Fusion Procurement TEST/UAT environment."
  ],
  "test_data": [
    {
      "field": "Requisition Number",
      "example": "${REQUISITION_NUMBER}"
    },
    {
      "field": "Requisitioning BU",
      "example": "${REQUISITIONING_BU}"
    },
    {
      "field": "Requester",
      "example": "${REQUESTER}"
    },
    {
      "field": "Total Amount",
      "example": "${TOTAL_AMOUNT}"
    },
    {
      "field": "Category",
      "example": "${CATEGORY}"
    },
    {
      "field": "Charge Account",
      "example": "${CHARGE_ACCOUNT}"
    },
    {
      "field": "Need-By Date",
      "example": "${NEED_BY_DATE}"
    },
    {
      "field": "Line Count",
      "example": "${LINE_COUNT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion using an authorised procurement test user.",
      "test_data": "",
      "expected_result": "Oracle Fusion Procurement is accessible to the signed-in test user.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Requisitions",
      "action": "Navigate to the Requisitions work area.",
      "test_data": "",
      "expected_result": "The Requisitions work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Draft Requisition",
      "action": "Search for and open the complete draft requisition to be submitted.",
      "test_data": "${REQUISITION_NUMBER}",
      "expected_result": "The correct draft requisition opens for review.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening requisition search, entering search criteria and selecting the result."
    },
    {
      "step_number": 4,
      "step_name": "Review Requisition Details",
      "action": "Review the requisition header and line details, including requester, requisitioning BU, category and charge account.",
      "test_data": "",
      "expected_result": "Requisition header and line details display as expected for the draft.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Confirm Mandatory Data Is Complete",
      "action": "Confirm that all mandatory header and line fields required for submission are populated.",
      "test_data": "",
      "expected_result": "No mandatory fields are missing before submission is attempted.",
      "validation_type": "action",
      "note": "Confirming completeness before submission helps distinguish a data-completeness issue from a submission or configuration issue if the test later fails."
    },
    {
      "step_number": 6,
      "step_name": "Submit the Requisition",
      "action": "Select the option to submit the requisition into the configured approval flow.",
      "test_data": "",
      "expected_result": "Oracle Fusion accepts the submission without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Status Changed Correctly",
      "action": "Reopen or refresh the requisition and review its status.",
      "test_data": "",
      "expected_result": "The requisition status correctly reflects submission, such as In Process or Pending Approval.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the scenario — a correct status transition is the expected pass condition, not merely an accepted submission."
    },
    {
      "step_number": 8,
      "step_name": "Verify Approval Routing Initiated Where Configured",
      "action": "Review the requisition's approval history or status where an approval rule applies to this requisition.",
      "test_data": "",
      "expected_result": "Approval routing begins correctly where an approval rule applies; requisitions with no applicable rule complete without unnecessary routing.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "The requisition submits successfully once all mandatory data is present.",
    "The requisition status changes correctly to reflect submission.",
    "Approval routing begins where an approval rule applies to the requisition.",
    "Requisitions that do not require approval complete without unnecessary routing.",
    "The submitted requisition remains traceable back to the originating draft.",
    "Fields not part of the submission action remain unchanged."
  ],
  "validation_checkpoints": [
    "Submission succeeds for a complete, eligible requisition.",
    "Requisition status changes correctly following submission.",
    "Approval routing begins where configured for the requisition.",
    "The requisition remains traceable throughout the submission process."
  ]
}