{
  "test_id": "ORCL.O2C.OM.CHG.SHIPTO",
  "scenario_name": "Change Ship-To",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Order Management",
  "module": "Order Management",
  "process": "Order Changes",
  "business_flow": "Order-to-Cash",
  "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/order-management/order-changes/change-ship-to/",
  "objective": {
    "intro": "The objective of this test is to validate that the ship-to address on an existing, submitted sales order line can be changed in Oracle Fusion SCM Order Management, and that tax jurisdiction and fulfillment/warehouse sourcing downstream of the ship-to address are correctly re-evaluated as a result.",
    "confirms": [
      "the ship-to address on the order line is updated to the newly selected address or customer site",
      "tax is correctly re-determined for the new ship-to address, based on the tax configuration in the target environment",
      "fulfillment/warehouse sourcing is re-evaluated where the ship-to change affects the applicable sourcing rule",
      "a change history / audit trail entry is recorded for the ship-to change",
      "Oracle correctly enforces validation when an invalid, unregistered or unsupported ship-to address is used, or when a change is attempted on a shipped line, under a security restriction or against an active hold"
    ],
    "scope_note": "This scenario covers changing the ship-to address on a single existing sales order line in Oracle Fusion SCM Order Management TEST/UAT environments, both before and after the line has been scheduled. It does not cover the separate Change Order Quantity and Change Requested Date scenarios in the same Order Changes cluster, and it does not assert coverage of every possible tax jurisdiction — line-level tax calculation itself is covered in more depth by the related Create Order With Tax scenario."
  },
  "preconditions": [
    "An existing, submitted sales order line is present in the target Oracle Fusion SCM Order Management environment.",
    "An alternate valid ship-to address or customer site is available and associated with the customer account.",
    "For post-scheduling scenarios, the order line has already been scheduled against the original ship-to address.",
    "The order entry test user has appropriate access to change the ship-to address on the order line.",
    "Tax and fulfillment sourcing configuration relevant to both the original and new ship-to address is present in the target environment."
  ],
  "test_data": [
    {
      "field": "Order Number",
      "example": "${ORDER_NUMBER}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Original Ship-To",
      "example": "${ORIGINAL_SHIP_TO}"
    },
    {
      "field": "New Ship-To",
      "example": "${NEW_SHIP_TO}"
    },
    {
      "field": "Line Status",
      "example": "${LINE_STATUS}"
    },
    {
      "field": "Tax Jurisdiction",
      "example": "${TAX_JURISDICTION}"
    },
    {
      "field": "Fulfillment Warehouse",
      "example": "${FULFILLMENT_WAREHOUSE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion using an authorised order entry test user.",
      "test_data": "",
      "expected_result": "The test user is signed in successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Order Management",
      "action": "Navigate to the Order Management work area.",
      "test_data": "",
      "expected_result": "The Order Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Sales Order",
      "action": "Search for and open the existing sales order to be changed.",
      "test_data": "${ORDER_NUMBER}",
      "expected_result": "The correct sales order opens, showing its current lines and status.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Select the Order Line to Change",
      "action": "Select the order line whose ship-to address is to be changed.",
      "test_data": "${ITEM} / ${LINE_STATUS}",
      "expected_result": "The correct order line is selected, showing its current ship-to address.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Select the New Ship-To Address",
      "action": "Select the alternate valid ship-to address or customer site for the order line.",
      "test_data": "${ORIGINAL_SHIP_TO} / ${NEW_SHIP_TO}",
      "expected_result": "The new ship-to address is accepted and reflected on the line as a pending change.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review Tax and Fulfillment Impact",
      "action": "Review the tax jurisdiction and fulfillment warehouse Oracle Fusion recalculates for the new ship-to address before submitting the change.",
      "test_data": "${TAX_JURISDICTION} / ${FULFILLMENT_WAREHOUSE}",
      "expected_result": "The previewed tax jurisdiction and fulfillment warehouse reflect the newly selected ship-to address.",
      "validation_type": "action",
      "note": "Reviewing the recalculated impact before submitting lets the tester catch an unintended tax or sourcing consequence before the change is committed."
    },
    {
      "step_number": 7,
      "step_name": "Submit the Ship-To Change",
      "action": "Submit the ship-to change for the order line.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the ship-to change without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Updated Ship-To and Recalculated Tax",
      "action": "Reopen or refresh the order line and confirm the ship-to address, recalculated tax and fulfillment warehouse, and that a change history entry was recorded.",
      "test_data": "",
      "expected_result": "The order line reflects the updated ship-to address, correctly re-determined tax, re-evaluated fulfillment sourcing where applicable, and a recorded change history entry.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly updated ship-to with accurate downstream tax and fulfillment re-evaluation is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "The ship-to address on the order line is updated to the selected new address or customer site.",
    "Tax is correctly re-determined for the new ship-to address, based on the tax configuration in the target environment.",
    "Fulfillment/warehouse sourcing is re-evaluated where the ship-to change affects the applicable sourcing rule.",
    "The change is recorded in the order line's change history / audit trail.",
    "Lines already scheduled against the original ship-to reflect the change consistently after resubmission.",
    "Oracle correctly rejects or blocks the change where the new ship-to is invalid, unregistered, unsupported or conflicts with an active hold."
  ],
  "validation_checkpoints": [
    "Ship-to updated correctly on the line.",
    "Tax correctly re-determined for the new ship-to, based on configuration.",
    "Fulfillment sourcing re-evaluated where applicable.",
    "Change history / audit trail recorded."
  ]
}