{
  "test_id": "ORCL.SCM.PLAN.RELEASE",
  "scenario_name": "Release Planned Order",
  "application": "Oracle Fusion Cloud",
  "product": "SCM",
  "module": "Supply Planning",
  "process": "Release Planned 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/supply-planning/release-planned-order/",
  "objective": {
    "intro": "The objective of this test is to validate release of planned orders into their downstream execution documents — work orders (make), purchase requisitions (buy) or transfer orders (transfer) — across Oracle Fusion SCM Supply Planning, including individual and batch release, without assuming every planned order releases automatically without review.",
    "confirms": [
      "the planned order correctly releases to the matching downstream document type — work order, purchase requisition or transfer order",
      "firmed status is correctly required before release where configured",
      "batch release correctly processes multiple eligible planned orders together",
      "the resulting downstream document correctly reflects the planned order's quantity, date and supply source",
      "duplicate and unauthorized release attempts are correctly blocked",
      "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 release of planned orders as configured in the target Oracle Fusion SCM Supply Planning TEST/UAT environment. It orchestrates release of the resulting work order into the existing Manufacturing test coverage and the resulting purchase requisition into Procurement, but does not duplicate the detailed downstream scenario coverage for those documents — see the Create Work Order scenario in the Manufacturing test library and the corresponding purchase requisition creation scenario in the Procurement test library for that detailed coverage."
  },
  "preconditions": [
    "The test user has appropriate Supply Planner, Planning Manager or Buyer access to release planned orders.",
    "One or more eligible planned orders of type make, buy or transfer exist and are available for release in the target Oracle Fusion environment.",
    "Work definitions, supplier and transfer routing configuration required for downstream document creation are configured and active.",
    "Firm/unfirm release rules and other release-specific configuration referenced in test data are configured and active.",
    "The organization(s) included in the release scope are configured to allow planned order release."
  ],
  "test_data": [
    {
      "field": "Planned Order",
      "example": "${PLANNED_ORDER}"
    },
    {
      "field": "Order Type",
      "example": "${ORDER_TYPE}"
    },
    {
      "field": "Work Order",
      "example": "${WORK_ORDER}"
    },
    {
      "field": "Purchase Requisition",
      "example": "${PURCHASE_REQUISITION}"
    },
    {
      "field": "Transfer Order",
      "example": "${TRANSFER_ORDER}"
    },
    {
      "field": "Organization",
      "example": "${ORGANIZATION}"
    },
    {
      "field": "Order Quantity",
      "example": "${ORDER_QUANTITY}"
    },
    {
      "field": "User Role",
      "example": "${USER_ROLE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In and Navigate to the Planned Orders Workbench",
      "action": "Sign in to Oracle Fusion using an authorised Supply Planning test user and navigate to the planned orders workbench.",
      "test_data": "${PLANNED_ORDER}",
      "expected_result": "The planned orders workbench opens and the target planned order is available for selection.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Select the Planned Order or Orders to Release",
      "action": "Select the planned order, or multiple planned orders for batch release, to be released.",
      "test_data": "${PLANNED_ORDER} / ${ORDER_TYPE}",
      "expected_result": "The selected planned order(s) are correctly highlighted for release.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Review Order Type and Quantity/Date",
      "action": "Review the planned order's type, quantity and suggested date, modifying quantity or date if required before release.",
      "test_data": "${ORDER_QUANTITY}",
      "expected_result": "The reviewed order type, quantity and date are accepted and reflected on the release request.",
      "validation_type": "action",
      "note": "Reviewing the order before release lets the tester catch an incorrect quantity or date, since not every planned order should be assumed to release automatically without review."
    },
    {
      "step_number": 4,
      "step_name": "Submit the Release Action",
      "action": "Submit the release action for the selected planned order or orders.",
      "test_data": "${ORGANIZATION}",
      "expected_result": "Oracle Fusion accepts the release request without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Monitor Release Processing",
      "action": "Monitor the release action until it completes and a downstream document reference becomes available.",
      "test_data": "",
      "expected_result": "The release correctly completes and a downstream document reference is returned for each released planned order.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Verify the Corresponding Downstream Document Is Created Correctly",
      "action": "Open the corresponding downstream document — work order, purchase requisition or transfer order — and confirm it reflects the planned order's type, quantity, date and source.",
      "test_data": "${WORK_ORDER} / ${PURCHASE_REQUISITION} / ${TRANSFER_ORDER}",
      "expected_result": "The downstream document is correctly created and reflects the planned order's type, quantity, date and source.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly created downstream document is the expected pass condition, not merely a completed release status."
    }
  ],
  "expected_results": [
    "The planned order correctly releases to the matching downstream document type — work order, purchase requisition or transfer order.",
    "Firmed status is correctly required before release where configured.",
    "Batch release correctly processes multiple eligible planned orders together.",
    "Duplicate release of an already-released planned order is correctly blocked.",
    "Release of an unfirmed order is correctly blocked where not permitted by configuration.",
    "Unauthorized release is correctly blocked."
  ],
  "validation_checkpoints": [
    "Planned order correctly releases to the matching downstream document type.",
    "Firmed status correctly required where configured.",
    "Batch release correctly processes multiple eligible orders together.",
    "Duplicate release correctly blocked.",
    "Unfirmed release correctly blocked where not permitted.",
    "Unauthorized release correctly blocked."
  ]
}