{
  "test_id": "ORCL.P2P.PROC.REQ.CHANGE",
  "scenario_name": "Change 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/change-requisition/",
  "objective": {
    "intro": "The objective of this test is to validate that allowed changes to an existing requisition — such as quantity, price, need-by date, deliver-to location, supplier or charge account — are accepted, correctly applied, and preserved alongside the requisition's original values and audit history in Oracle Fusion Procurement.",
    "confirms": [
      "an eligible requisition can be opened for change by an authorized user",
      "the target field or fields accept a valid new value without unexpected errors",
      "the changed value is reflected accurately once the requisition is saved",
      "the requisition's audit history retains a record of the change rather than silently overwriting it",
      "approval is re-triggered where the customer's workflow configuration requires it",
      "the requisition status remains correct and consistent with the change performed"
    ],
    "scope_note": "This scenario covers changing an existing requisition within Oracle Fusion Procurement TEST/UAT environments. It does not cover initial requisition creation, which is covered by the separate Create Purchase Requisition scenario, or requisition cancellation, which is covered by the separate Cancel Requisition scenario. Individual field-level changes such as quantity, price or supplier are represented as data-driven variations of this same test rather than as separate published test pages."
  },
  "preconditions": [
    "A requisition exists and is in a status that is eligible for change.",
    "The requester or authorized user performing the change has the appropriate change privileges.",
    "The target values for the change — item, account, supplier or location — are valid and configured for the test tenant.",
    "The test user has permission to open and edit requisitions in Oracle Fusion Procurement."
  ],
  "test_data": [
    {
      "field": "Business Unit",
      "example": "${BUSINESS_UNIT}"
    },
    {
      "field": "Requisition Number",
      "example": "${REQUISITION_NUMBER}"
    },
    {
      "field": "Current Requisition Status",
      "example": "${REQUISITION_STATUS}"
    },
    {
      "field": "New Quantity",
      "example": "${NEW_QUANTITY}"
    },
    {
      "field": "New Price",
      "example": "${NEW_PRICE}"
    },
    {
      "field": "New Need-By Date",
      "example": "${NEW_NEED_BY_DATE}"
    },
    {
      "field": "New Deliver-To Location",
      "example": "${NEW_DELIVER_TO_LOCATION}"
    },
    {
      "field": "New Supplier",
      "example": "${NEW_SUPPLIER}"
    },
    {
      "field": "New Charge Account",
      "example": "${NEW_CHARGE_ACCOUNT}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Requisitions",
      "action": "Sign in to Oracle Fusion using an authorized Procurement test user and navigate to the Requisitions work area.",
      "test_data": "",
      "expected_result": "The Requisitions work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Locate the Existing Requisition",
      "action": "Search for and open the requisition that is eligible for change.",
      "test_data": "${REQUISITION_NUMBER}",
      "expected_result": "The correct requisition is located and its current status and values are displayed.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening requisition search, entering the requisition number, and selecting the result."
    },
    {
      "step_number": 3,
      "step_name": "Open the Requisition for Editing",
      "action": "Select the option to edit the located requisition.",
      "test_data": "",
      "expected_result": "The requisition opens in an editable state showing its current field values.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Modify the Target Field or Fields",
      "action": "Update the field or fields relevant to this variation — quantity, price, need-by date, deliver-to location, supplier or charge account.",
      "test_data": "${NEW_QUANTITY} / ${NEW_PRICE} / ${NEW_NEED_BY_DATE} / ${NEW_DELIVER_TO_LOCATION} / ${NEW_SUPPLIER} / ${NEW_CHARGE_ACCOUNT}",
      "expected_result": "The new value is accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Review Changed Values Before Saving",
      "action": "Review the updated field values against the original values before saving the requisition.",
      "test_data": "",
      "expected_result": "The changed values shown match the intended change for this variation.",
      "validation_type": "action",
      "note": "Reviewing the change before saving lets the tester catch an incorrect value entry before it is committed."
    },
    {
      "step_number": 6,
      "step_name": "Save the Changed Requisition",
      "action": "Submit and save the change to the requisition in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully saves the change without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Changes Are Retained",
      "action": "Reopen or refresh the requisition and confirm the new field values are present.",
      "test_data": "",
      "expected_result": "The requisition reflects the changed values accurately.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the scenario — a correctly retained change is the expected pass condition, not merely a successful save."
    },
    {
      "step_number": 8,
      "step_name": "Verify Change History Is Preserved",
      "action": "Review the requisition's audit or history record for the change performed.",
      "test_data": "",
      "expected_result": "The prior value and the change are visible in the requisition's history rather than being silently overwritten.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 9,
      "step_name": "Verify Re-Approval Triggered Where Configured",
      "action": "Review the requisition's approval status after the change is saved.",
      "test_data": "",
      "expected_result": "Where the customer's workflow configuration requires it, re-approval is triggered and the requisition status reflects this correctly.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "The target field or fields accept the new value without unexpected errors.",
    "The changed value is reflected accurately once the requisition is saved.",
    "The requisition's audit history retains a record of both the prior and new values.",
    "Re-approval is triggered where the customer's workflow configuration requires it.",
    "The requisition status remains correct and consistent with the change performed.",
    "Unauthorized change attempts are correctly prevented."
  ],
  "validation_checkpoints": [
    "Changed values are retained on the requisition.",
    "Change history is preserved.",
    "Approval is re-triggered where configured.",
    "Requisition status is correct after the change."
  ]
}