{
  "test_id": "ORCL.SCM.MFG.WO.UPDATE",
  "scenario_name": "Update Work Order",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "Manufacturing",
  "process": "Update Work Order",
  "business_flow": "Plan-to-Produce",
  "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/manufacturing/work-orders/update-work-order/",
  "objective": {
    "intro": "The objective of this test is to validate quantity, date, priority and description changes to a work order in Oracle Fusion SCM Manufacturing at different lifecycle stages, and to confirm that updates are correctly permitted or blocked according to the work order's status and the customer's configuration rather than a single universal rule.",
    "confirms": [
      "the work order quantity can be increased or decreased and the change is correctly reflected on the work order",
      "start date, completion date and priority changes are correctly applied and reflected on the work order",
      "the work order description can be updated and is correctly saved",
      "quantity cannot be reduced below the quantity already reported as complete on the work order",
      "updates before release, after release and after partial completion are permitted or blocked in line with the work order's lifecycle stage and the customer's configuration",
      "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 updating an existing work order's quantity, dates, priority and description in Oracle Fusion SCM Manufacturing TEST/UAT environments. It does not cover initial work order creation or release, which are covered by the separate Create Work Order and Release Work Order scenarios, or work order cancellation, covered by Cancel Work Order, in the same Work Orders cluster."
  },
  "preconditions": [
    "A work order identified by ${WORK_ORDER} already exists in the target Oracle Fusion SCM Manufacturing environment.",
    "The work order is in a status (${WORK_ORDER_STATUS}) that is relevant to the update being tested — for example before release, released, or after partial completion.",
    "The test user holds a role (${USER_ROLE}) with visibility to the work order, and a separate unauthorized-user persona is available for negative security testing.",
    "For quantity-reduction testing, the work order has a recorded completed quantity (${COMPLETED_QUANTITY}) against which the new quantity can be compared.",
    "Work definition, routing and organization setup for the work order are configured and active."
  ],
  "test_data": [
    {
      "field": "Work Order",
      "example": "${WORK_ORDER}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Completed Quantity",
      "example": "${COMPLETED_QUANTITY}"
    },
    {
      "field": "Start Date",
      "example": "${START_DATE}"
    },
    {
      "field": "Completion Date",
      "example": "${COMPLETION_DATE}"
    },
    {
      "field": "Priority",
      "example": "${PRIORITY}"
    },
    {
      "field": "Work Order Status",
      "example": "${WORK_ORDER_STATUS}"
    },
    {
      "field": "User Role",
      "example": "${USER_ROLE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to Manufacturing",
      "action": "Sign in to Oracle Fusion using an authorised manufacturing test user and navigate to the Manufacturing work area.",
      "test_data": "${USER_ROLE}",
      "expected_result": "The Manufacturing work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Work Order",
      "action": "Search for and open the work order to be updated.",
      "test_data": "${WORK_ORDER} / ${WORK_ORDER_STATUS}",
      "expected_result": "The work order opens and its current status, quantity and dates are displayed.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Modify Quantity, Dates, Priority or Description as Applicable",
      "action": "Update the work order quantity, start date, completion date, priority or description as applicable to the work order's current lifecycle stage.",
      "test_data": "${QUANTITY} / ${START_DATE} / ${COMPLETION_DATE} / ${PRIORITY}",
      "expected_result": "The changed field values are accepted for editing on the work order.",
      "validation_type": "action",
      "note": "Which fields are editable depends on the work order's lifecycle stage and the customer's Oracle Fusion configuration — not every field is expected to be open for change at every stage."
    },
    {
      "step_number": 4,
      "step_name": "Submit the Update",
      "action": "Submit the work order update for processing in the test environment.",
      "test_data": "",
      "expected_result": "Oracle Fusion successfully processes the update without unexpected errors, or returns an expected validation message for out-of-bounds or disallowed changes.",
      "validation_type": "action",
      "note": "Some scenarios in this family are designed to trigger an expected validation rather than a successful save — for example an invalid date or a quantity below completed quantity."
    },
    {
      "step_number": 5,
      "step_name": "Verify Change Is Correctly Applied",
      "action": "Reopen or refresh the work order and confirm the updated quantity, dates, priority or description match the entered data.",
      "test_data": "",
      "expected_result": "The work order reflects the updated values accurately, and no unrelated field was changed as a side effect.",
      "validation_type": "business_assertion",
      "note": "This is a primary business assertion for positive update scenarios — a correctly applied change is the expected pass condition, not merely a successful submission."
    },
    {
      "step_number": 6,
      "step_name": "Verify Blocked Updates Return Expected Validation",
      "action": "For negative scenarios, confirm that the disallowed update was rejected with an appropriate validation message rather than silently applied.",
      "test_data": "",
      "expected_result": "Quantity below completed quantity, invalid dates, updates to closed or cancelled work orders, and unauthorized update attempts are each correctly blocked.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for negative and security scenarios in this family — Oracle correctly enforcing the rule is the expected pass condition."
    }
  ],
  "expected_results": [
    "Quantity, date and priority changes are correctly applied and reflected on the work order.",
    "Description updates are correctly saved.",
    "Quantity cannot be reduced below the already-completed quantity.",
    "Invalid dates are correctly rejected with an expected validation message.",
    "Updates to closed or cancelled work orders are correctly blocked.",
    "Update permissions correctly vary by lifecycle stage and by user role."
  ],
  "validation_checkpoints": [
    "Quantity, date and priority changes correctly applied and reflected on the work order.",
    "Quantity cannot be reduced below already-completed quantity.",
    "Date validation correctly enforced.",
    "Updates to closed or cancelled orders correctly blocked.",
    "Update permissions correctly vary by lifecycle stage (before/after release).",
    "Unauthorized update correctly blocked."
  ]
}