{
  "test_id": "ORCL.SCM.MFG.WO.RELEASE",
  "scenario_name": "Release Work Order",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "Manufacturing",
  "process": "Release 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/release-work-order/",
  "objective": {
    "intro": "The objective of this test is to validate single, batch and exception release of work orders in Oracle Fusion SCM Manufacturing, including component availability checks, without assuming a universal shortage-tolerance policy across Oracle Fusion implementations.",
    "confirms": [
      "a work order with valid status, work definition and component setup is released successfully, individually or as part of a batch",
      "component on-hand availability is checked and reflected before release, including shortage warnings where the manufacturing organization's configuration permits release with a shortage",
      "the work order status correctly transitions to Released once the release action completes",
      "release of a work order that is already Released, Cancelled or Closed is correctly blocked",
      "release of a work order with a missing work definition or invalid component setup is correctly blocked",
      "Oracle correctly enforces validation and security restrictions when data, configuration or authorization issues are introduced (DATA_ERROR, CONFIGURATION_ERROR, SECURITY_ERROR, EXPECTED_VALIDATION)"
    ],
    "scope_note": "This scenario covers single, batch and exception release of work orders in Oracle Fusion SCM Manufacturing TEST/UAT environments, including component availability checks. Component shortage tolerance at release is governed by customer-specific manufacturing organization parameters — this scenario does not assume a universal shortage-tolerance policy across Oracle Fusion implementations. It does not cover creation or update of the work order itself, which are covered by the separate Create Work Order and Update Work Order scenarios in the same Work Orders cluster."
  },
  "preconditions": [
    "The work order exists in Oracle Fusion SCM Manufacturing with a status eligible for release (typically Unreleased).",
    "The work order has an associated work definition with valid operations.",
    "Components required by the work order are set up in the manufacturing organization, with on-hand quantities visible where applicable.",
    "The test user has appropriate access to release work orders for the manufacturing organization.",
    "For batch release, multiple eligible work orders are available for selection."
  ],
  "test_data": [
    {
      "field": "Work Order",
      "example": "${WORK_ORDER}"
    },
    {
      "field": "Manufacturing Organization",
      "example": "${MANUFACTURING_ORG}"
    },
    {
      "field": "Component",
      "example": "${COMPONENT}"
    },
    {
      "field": "Work Definition",
      "example": "${WORK_DEFINITION}"
    },
    {
      "field": "Work Order Status",
      "example": "${WORK_ORDER_STATUS}"
    },
    {
      "field": "Start Date",
      "example": "${START_DATE}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "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": "",
      "expected_result": "The Manufacturing work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to the Work Order",
      "action": "Open the work order to be released from the work order list.",
      "test_data": "${WORK_ORDER} / ${MANUFACTURING_ORG}",
      "expected_result": "The work order details page opens with the correct status, work definition and component detail.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Verify Component Availability",
      "action": "Review component on-hand availability for the work order before release.",
      "test_data": "${COMPONENT}",
      "expected_result": "Component availability is displayed, including a shortage warning where applicable.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the availability check and comparing on-hand to required quantity."
    },
    {
      "step_number": 4,
      "step_name": "Release the Work Order",
      "action": "Release the work order individually, or select it along with other eligible work orders and release as a batch.",
      "test_data": "${WORK_ORDER_STATUS} / ${QUANTITY}",
      "expected_result": "Oracle Fusion successfully processes the release action without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Verify the Work Order Status Changes to Released",
      "action": "Reopen or refresh the work order and confirm the status.",
      "test_data": "",
      "expected_result": "The work order status correctly shows Released.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a work order correctly transitioning to Released status is the expected pass condition, not merely a successful save."
    },
    {
      "step_number": 6,
      "step_name": "Verify Shortage Warnings Display Correctly",
      "action": "Where a component shortage exists, confirm that the shortage warning is displayed correctly on the released work order.",
      "test_data": "${COMPONENT}",
      "expected_result": "Shortage warnings, where applicable, are displayed accurately and do not silently prevent release when configuration permits release with a shortage.",
      "validation_type": "business_assertion"
    }
  ],
  "expected_results": [
    "The work order correctly transitions to Released status.",
    "Component availability is correctly checked and reflected before release.",
    "Batch release correctly processes multiple work orders in a single action.",
    "Release of a work order in an invalid status (Released, Cancelled or Closed) is correctly blocked.",
    "Release of a work order with a missing work definition or invalid component setup is correctly blocked.",
    "Unauthorized release is correctly blocked."
  ],
  "validation_checkpoints": [
    "Work order correctly transitions to Released status.",
    "Component availability correctly checked before release.",
    "Batch release correctly processes multiple orders.",
    "Release of invalid-status orders correctly blocked.",
    "Missing work definition or invalid component setup correctly blocked.",
    "Unauthorized release correctly blocked."
  ]
}