{
  "test_id": "ORCL.P2P.PROC.REQ.CREATE",
  "scenario_name": "Create Purchase 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/create-purchase-requisition/",
  "objective": {
    "intro": "The objective of this test is to validate that a purchase requisition can be created in Oracle Fusion SCM using a valid requester, requisitioning Business Unit, item or category, supplier where applicable, quantity, price, deliver-to location and charge account, and that the resulting requisition is created with correct line detail.",
    "confirms": [
      "the requisition is created for the correct requester and requisitioning Business Unit",
      "line detail — item or category, quantity, unit of measure and price — is captured correctly",
      "the deliver-to location and charge account entered on the line are correct",
      "supplier and supplier site information is captured correctly where applicable",
      "the requisition receives a system-generated requisition number",
      "Oracle correctly enforces validation when data errors, configuration errors or security restrictions are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario covers creation of a single or multi-line purchase requisition in Oracle Fusion SCM Procurement TEST/UAT environments. It does not cover submission for approval, subsequent changes, or cancellation, which are covered by the separate Submit Requisition, Change Requisition and Cancel Requisition scenarios in the same Requisitions cluster."
  },
  "preconditions": [
    "A requisitioning Business Unit is configured in the target Oracle Fusion SCM environment.",
    "The test requester has appropriate access to raise a requisition for the requisitioning BU.",
    "The item or category being requisitioned is active in the item/category catalog.",
    "Where a supplier is required on the line, the supplier and supplier site are active.",
    "The charge account entered on the line is valid and open for the requisition date.",
    "The deliver-to location used on the requisition is configured and active."
  ],
  "test_data": [
    {
      "field": "Requisitioning BU",
      "example": "${REQUISITIONING_BU}"
    },
    {
      "field": "Requester",
      "example": "${REQUESTER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Category",
      "example": "${CATEGORY}"
    },
    {
      "field": "Supplier",
      "example": "${SUPPLIER}"
    },
    {
      "field": "Supplier Site",
      "example": "${SUPPLIER_SITE}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "UOM",
      "example": "${UOM}"
    },
    {
      "field": "Price",
      "example": "${PRICE}"
    },
    {
      "field": "Currency",
      "example": "${CURRENCY}"
    },
    {
      "field": "Deliver-to Location",
      "example": "${DELIVER_TO_LOCATION}"
    },
    {
      "field": "Charge Account",
      "example": "${CHARGE_ACCOUNT}"
    },
    {
      "field": "Need-by Date",
      "example": "${NEED_BY_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Procurement",
      "action": "Sign in to Oracle Fusion using an authorised procurement test user and navigate to the Procurement work area.",
      "test_data": "",
      "expected_result": "The Procurement work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Requisitions",
      "action": "Open the Requisitions page to begin creating a new purchase requisition.",
      "test_data": "${REQUISITIONING_BU}",
      "expected_result": "The requisition creation page opens for the correct requisitioning Business Unit.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Create New Requisition",
      "action": "Initiate a new requisition for the test requester.",
      "test_data": "${REQUESTER}",
      "expected_result": "A new, unsaved requisition is opened for the correct requester.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the create page, confirming the requester and confirming the requisitioning BU."
    },
    {
      "step_number": 4,
      "step_name": "Select Item or Enter Noncatalog Details",
      "action": "Search for and select a catalog item, or enter noncatalog line details including item description and category where a catalog item is not used.",
      "test_data": "${ITEM} / ${CATEGORY}",
      "expected_result": "The item or noncatalog line detail is accepted and added to the requisition.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Enter Quantity and Price",
      "action": "Enter the requisition line quantity, unit of measure and price.",
      "test_data": "${QUANTITY} / ${UOM} / ${PRICE} / ${CURRENCY}",
      "expected_result": "Quantity, UOM and price are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Select Deliver-to Location",
      "action": "Select the deliver-to location for the requisition line.",
      "test_data": "${DELIVER_TO_LOCATION}",
      "expected_result": "The deliver-to location is accepted and reflected on the line.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Select Charge Account",
      "action": "Select or confirm the charge account that the requisition line will be costed to.",
      "test_data": "${CHARGE_ACCOUNT}",
      "expected_result": "The charge account is accepted and reflected on the line.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Enter Need-by Date",
      "action": "Enter the date by which the requisitioned item or service is needed.",
      "test_data": "${NEED_BY_DATE}",
      "expected_result": "The need-by date is accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 9,
      "step_name": "Review Requisition",
      "action": "Review the requisition header and line detail as calculated by Oracle Fusion before saving.",
      "test_data": "",
      "expected_result": "The reviewed requisition reflects the entered requester, item/category, quantity, price, deliver-to location and charge account.",
      "validation_type": "action",
      "note": "Reviewing the requisition before saving lets the tester catch an incorrect field entry before the requisition is created."
    },
    {
      "step_number": 10,
      "step_name": "Save the Requisition",
      "action": "Save the requisition for creation in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the requisition without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 11,
      "step_name": "Verify Requisition Number and Status",
      "action": "Reopen or refresh the requisition and confirm the generated requisition number, status and line detail.",
      "test_data": "",
      "expected_result": "A requisition number is generated, the requisition status is correct, and requester, quantity, price, deliver-to location and charge account match the entered data.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly created requisition with accurate line detail is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "The requisition is created for the correct requester and requisitioning Business Unit.",
    "A system-generated requisition number is assigned.",
    "Line data — item/category, quantity, UOM and price — is correct.",
    "The deliver-to location and charge account on the line are correct.",
    "Supplier and supplier site are correct where applicable.",
    "The requisition status correctly reflects a newly created, unsubmitted requisition.",
    "The requisition is visible and traceable for the test requester."
  ],
  "validation_checkpoints": [
    "Requisition created.",
    "Requisition number generated.",
    "Line data correct.",
    "Requester correct.",
    "Quantity/price correct.",
    "Account/location correct.",
    "Status correct."
  ]
}