{
  "test_id": "ORCL.O2C.OM.FUL.PICK",
  "scenario_name": "Pick Release",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Order Management",
  "module": "Order Management",
  "process": "Fulfillment",
  "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/fulfillment/pick-release/",
  "objective": {
    "intro": "The objective of this test is to validate release of scheduled and reserved order lines to the warehouse for physical picking through a generated pick wave, and to confirm that Oracle Fusion correctly determines which lines are included in, or excluded from, that release.",
    "confirms": [
      "scheduled and reserved order lines can be released to the warehouse via pick release",
      "a pick wave is generated correctly against the defined pick release criteria, such as warehouse and ship date range",
      "order line status updates correctly to reflect pick release",
      "the resulting warehouse task or pick slip correctly reflects item, quantity and location",
      "unscheduled lines, held orders and lines with insufficient reserved quantity are correctly excluded from release",
      "duplicate release of an already-released line and access by unauthorized users are correctly prevented"
    ],
    "scope_note": "This scenario assumes order lines have already been scheduled and, where required, reserved through the separate Schedule Order and Reserve Order scenarios. It covers the pick release action itself within Oracle Fusion Order Management TEST/UAT environments and does not cover the physical warehouse picking activity or the subsequent ship confirm step, which is covered by the separate Ship Confirm scenario."
  },
  "preconditions": [
    "Order lines have already been scheduled and, where required, reserved in Oracle Fusion Order Management.",
    "Pick release criteria, such as warehouse and ship date range, are configured for the release run.",
    "Sufficient on-hand or reserved quantity exists for the order lines expected to be released.",
    "The user initiating pick release holds the appropriate warehouse operator or order management privileges.",
    "The test user is signed in to an Oracle Fusion Order Management TEST/UAT environment."
  ],
  "test_data": [
    {
      "field": "Order Number",
      "example": "${ORDER_NUMBER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Warehouse",
      "example": "${WAREHOUSE}"
    },
    {
      "field": "Pick Wave Criteria",
      "example": "${PICK_WAVE_CRITERIA}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Ship Date Range",
      "example": "${SHIP_DATE_RANGE}"
    },
    {
      "field": "Pick Wave Number",
      "example": "${PICK_WAVE_NUMBER}"
    },
    {
      "field": "Lot / Serial Number",
      "example": "${LOT_SERIAL_NUMBER}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion using an authorised Order Management or warehouse operator test user.",
      "test_data": "",
      "expected_result": "Oracle Fusion Order Management is accessible to the signed-in test user.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Order Management",
      "action": "Navigate to the Order Management work area used to initiate pick release.",
      "test_data": "",
      "expected_result": "The Order Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Define Pick Release Criteria",
      "action": "Define the pick release criteria for the run, such as warehouse and ship date range.",
      "test_data": "${WAREHOUSE}, ${PICK_WAVE_CRITERIA}",
      "expected_result": "The pick release criteria are accepted and ready for submission.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the pick release form and entering each individual criterion field."
    },
    {
      "step_number": 4,
      "step_name": "Initiate Pick Release",
      "action": "Submit the pick release run against the defined criteria.",
      "test_data": "",
      "expected_result": "Oracle Fusion begins processing the pick release request.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Review the Generated Pick Wave",
      "action": "Open the resulting pick wave and review the lines it contains.",
      "test_data": "",
      "expected_result": "A pick wave is generated and available for review.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify Included and Excluded Lines Match Expectations",
      "action": "Compare the lines included in the pick wave against the order lines expected to qualify, and confirm unscheduled or held lines are absent.",
      "test_data": "",
      "expected_result": "Only eligible order lines are included in the pick wave; unscheduled, held or insufficiently reserved lines are correctly excluded.",
      "validation_type": "action",
      "note": "Confirming inclusion and exclusion before final release helps distinguish a criteria or eligibility issue from a release-processing issue if the test later fails."
    },
    {
      "step_number": 7,
      "step_name": "Confirm Release",
      "action": "Confirm the pick wave for release to the warehouse.",
      "test_data": "",
      "expected_result": "Oracle Fusion accepts the release without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Line Status Updated to Released for Picking",
      "action": "Reopen or refresh the order lines and the warehouse task or pick slip to review status.",
      "test_data": "",
      "expected_result": "Released order lines correctly update to a released-for-picking status, and the warehouse task or pick slip reflects the expected item, quantity and location.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correct status transition and an accurate warehouse task are the expected pass condition, not merely an accepted release."
    }
  ],
  "expected_results": [
    "Scheduled and reserved order lines are released successfully to the warehouse via pick release.",
    "The pick wave is generated correctly against the defined pick release criteria.",
    "Order line status updates correctly to reflect pick release.",
    "The warehouse task or pick slip correctly reflects item, quantity and location.",
    "Unscheduled lines, held orders and insufficiently reserved lines are correctly excluded from release.",
    "Duplicate release of an already-released line and access by unauthorized users are correctly prevented."
  ],
  "validation_checkpoints": [
    "The pick wave is correctly generated with the expected lines.",
    "Line status updates to reflect pick release.",
    "The warehouse task or pick slip correctly reflects item, quantity and location.",
    "Unscheduled or held lines are correctly excluded from release."
  ]
}