{
  "test_id": "ORCL.P2P.PROC.PO.CHANGE",
  "scenario_name": "Change Purchase Order",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Procurement",
  "module": "Procurement",
  "process": "Purchase Orders",
  "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/purchase-orders/change-purchase-order/",
  "objective": {
    "intro": "The objective of this test is to validate change-order processing on eligible Oracle Fusion purchase orders — confirming that allowed changes such as quantity, price, need-by date, ship-to, terms and lines are accepted, correctly applied, and preserved alongside the purchase order's prior values and version history.",
    "confirms": [
      "an eligible purchase order can be opened for change by an authorized user",
      "the target field or fields accept a valid new value without unexpected errors",
      "the change order is created and the revised values are reflected accurately once saved",
      "the purchase order's version and change history retain a record of the change rather than silently overwriting it",
      "reapproval is re-triggered where the customer's workflow configuration requires it",
      "the purchase order status remains correct and consistent with the change performed"
    ],
    "scope_note": "This scenario covers changing an existing purchase order within Oracle Fusion Procurement TEST/UAT environments. It does not cover initial PO creation, which is covered by the separate Create Purchase Order scenario, or PO cancellation, which is covered by the separate Cancel Purchase Order scenario. Individual field-level changes such as quantity, price or terms are represented as data-driven variations of this same test rather than as separate published test pages."
  },
  "preconditions": [
    "A purchase order exists and is in a status that is eligible for change.",
    "The buyer or authorized user performing the change has the appropriate change privileges.",
    "The target values for the change — quantity, price, date, ship-to, terms or line — are valid and configured for the test tenant.",
    "The test user has permission to open and edit purchase orders in Oracle Fusion Procurement."
  ],
  "test_data": [
    {
      "field": "Business Unit",
      "example": "${BUSINESS_UNIT}"
    },
    {
      "field": "PO Number",
      "example": "${PO_NUMBER}"
    },
    {
      "field": "Current PO Status",
      "example": "${PO_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 Ship-To",
      "example": "${NEW_SHIP_TO}"
    },
    {
      "field": "New Terms",
      "example": "${NEW_TERMS}"
    },
    {
      "field": "Line Number",
      "example": "${LINE_NUMBER}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion using an authorized Procurement test user.",
      "test_data": "",
      "expected_result": "Oracle Fusion signs the user in successfully and the home page loads.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Purchase Order",
      "action": "Navigate to the Purchase Orders work area and search for the purchase order eligible for change.",
      "test_data": "${PO_NUMBER}",
      "expected_result": "The correct purchase order 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 PO search, entering the PO number, and selecting the result."
    },
    {
      "step_number": 3,
      "step_name": "Open the Purchase Order for Change",
      "action": "Select the option to open the located purchase order for change.",
      "test_data": "",
      "expected_result": "The purchase order 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, ship-to, line or terms.",
      "test_data": "${NEW_QUANTITY} / ${NEW_PRICE} / ${NEW_NEED_BY_DATE} / ${NEW_SHIP_TO} / ${NEW_TERMS} / ${LINE_NUMBER}",
      "expected_result": "The new value is accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Review Revised Values and Version",
      "action": "Review the revised field values and the resulting change-order version before saving.",
      "test_data": "",
      "expected_result": "The revised values and version 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 Purchase Order",
      "action": "Submit and save the change order in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully saves the change order without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Verify Version and History Updated",
      "action": "Review the purchase order's version and change history after saving.",
      "test_data": "",
      "expected_result": "The purchase order version increments and the change history reflects the change performed.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for the scenario — a correctly recorded version and history is the expected pass condition, not merely a successful save."
    },
    {
      "step_number": 8,
      "step_name": "Verify Revised Values Retained",
      "action": "Reopen or refresh the purchase order and confirm the revised field values are present.",
      "test_data": "",
      "expected_result": "The purchase order reflects the revised values accurately.",
      "validation_type": "business_assertion"
    },
    {
      "step_number": 9,
      "step_name": "Verify Reapproval Triggered Where Configured",
      "action": "Review the purchase order's approval status after the change is saved.",
      "test_data": "",
      "expected_result": "Where the customer's workflow configuration requires it, reapproval is triggered and the purchase order status reflects this correctly.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "The target field or fields accept the new value without unexpected errors.",
    "A change order is created and the revised values are reflected accurately once saved.",
    "The purchase order's version and change history retain a record of both the prior and new values.",
    "Reapproval is triggered where the customer's workflow configuration requires it.",
    "The purchase order status remains correct and consistent with the change performed.",
    "Unauthorized change attempts are correctly prevented."
  ],
  "validation_checkpoints": [
    "Change order is created.",
    "Revised values are retained on the purchase order.",
    "Version and history are updated.",
    "Reapproval is triggered where configured."
  ]
}