{
  "test_id": "ORCL.O2C.OM.CHG.DATE",
  "scenario_name": "Change Requested Date",
  "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-requested-date/",
  "objective": {
    "intro": "The objective of this test is to validate that the customer-requested delivery date on an existing, submitted Oracle Fusion Order Management sales order line can be changed — whether moved earlier (expedited) or later (postponed) — and that the change is correctly reflected in downstream scheduling and, where applicable, reservation.",
    "confirms": [
      "the requested date on the selected order line is updated to the new value entered",
      "postponing the requested date is handled correctly for a line that has not yet been scheduled",
      "expediting the requested date is handled correctly, including where supply cannot support the earlier date",
      "a line that has already been scheduled against the original requested date is correctly rescheduled once the date changes",
      "reservation is re-evaluated where applicable once the requested date changes",
      "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 changing the requested date on an existing order line in Oracle Fusion SCM Order Management TEST/UAT environments, both before and after scheduling has run against the original date. It does not cover changing order quantity, ship-to address or cancelling a line, which are covered by the separate Change Order Quantity, Change Ship-To and Cancel Sales Order scenarios in the same Order Changes cluster."
  },
  "preconditions": [
    "A sales order exists in Oracle Fusion Order Management with at least one submitted line carrying a requested date.",
    "For pre-scheduling scenarios, the order line has not yet been scheduled against its original requested date.",
    "For post-scheduling scenarios, the order line has already been scheduled against the original requested date.",
    "The test user has appropriate access to open the order and change the requested date on the relevant line.",
    "Item supply/availability data needed to evaluate expedited requested-date scenarios exists in the test environment."
  ],
  "test_data": [
    {
      "field": "Order Number",
      "example": "${ORDER_NUMBER}"
    },
    {
      "field": "Order Line",
      "example": "${ORDER_LINE}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Original Requested Date",
      "example": "${ORIGINAL_REQUESTED_DATE}"
    },
    {
      "field": "New Requested Date",
      "example": "${NEW_REQUESTED_DATE}"
    },
    {
      "field": "Line Status",
      "example": "${LINE_STATUS}"
    },
    {
      "field": "Change Reason",
      "example": "${CHANGE_REASON}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In",
      "action": "Sign in to Oracle Fusion using an authorised order management test user.",
      "test_data": "",
      "expected_result": "Sign-in completes 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 Order",
      "action": "Search for and open the sales order to be changed.",
      "test_data": "${ORDER_NUMBER}",
      "expected_result": "The correct order opens, showing its current lines and line statuses.",
      "validation_type": "action"
    },
    {
      "step_number": 4,
      "step_name": "Select the Line to Change",
      "action": "Select the order line whose requested date is to be changed.",
      "test_data": "${ORDER_LINE} / ${ITEM}",
      "expected_result": "The selected line opens showing its current requested date and status.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Enter the New Requested Date",
      "action": "Enter the new requested date on the line, either earlier (expedite) or later (postpone) than the original date.",
      "test_data": "${ORIGINAL_REQUESTED_DATE} / ${NEW_REQUESTED_DATE}",
      "expected_result": "The new requested date is accepted on the line without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Review Scheduling Impact",
      "action": "Review any scheduling or availability impact Oracle Fusion presents as a result of the requested-date change before submitting.",
      "test_data": "",
      "expected_result": "Any scheduling or supply impact of the date change is presented for review.",
      "validation_type": "action",
      "note": "For a line already scheduled against the original date, this step is where Oracle surfaces the anticipated reschedule or supply impact of the new date."
    },
    {
      "step_number": 7,
      "step_name": "Submit the Change",
      "action": "Submit the requested-date change for processing.",
      "test_data": "${CHANGE_REASON}",
      "expected_result": "Oracle Fusion successfully processes the change without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Updated Date and Schedule",
      "action": "Reopen or refresh the order line and confirm the requested date, scheduling and reservation status.",
      "test_data": "",
      "expected_result": "The line reflects the new requested date, and downstream scheduling — and reservation where applicable — correctly reflects the updated date.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly updated requested date with correctly reflected scheduling is the expected pass condition, not merely a successful save."
    }
  ],
  "expected_results": [
    "The requested date on the selected order line is updated to the new value entered.",
    "Postponing the requested date is accepted for a line that has not yet been scheduled.",
    "Expediting the requested date is accepted where supply supports the earlier date, and correctly rejected or flagged where it does not.",
    "A line already scheduled against the original date is correctly rescheduled to reflect the new date.",
    "Reservation is re-evaluated where applicable once the requested date changes.",
    "A record of the requested-date change is retained in the order's change history.",
    "Other lines on the same order remain unaffected by a change to a single line."
  ],
  "validation_checkpoints": [
    "Requested date updated correctly on the line.",
    "Downstream scheduling correctly reflects the new date.",
    "Reservation re-evaluated where applicable.",
    "Change history/audit trail recorded."
  ]
}