{
  "test_id": "ORCL.O2C.OM.RET.CREATE",
  "scenario_name": "Create Return Order",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Order Management",
  "module": "Order Management",
  "process": "Returns",
  "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/returns/create-return-order/",
  "objective": {
    "intro": "The objective of this test is to verify that an authorised Order Management user can create a return order that references a previously shipped sales order, with correct return reason, quantity and disposition recorded on the new return order.",
    "confirms": [
      "the return order correctly references a valid, previously shipped original sales order and item",
      "the return reason is accepted",
      "the return quantity does not exceed the quantity originally shipped on the referenced order",
      "the disposition, such as return-to-stock or scrap/inspect, is correctly recorded",
      "the return order receives a system-generated order number and correct status",
      "the return order is available for downstream receipt processing",
      "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 creation of a customer return order that references a previously shipped sales order in Oracle Fusion SCM Order Management TEST/UAT environments. It does not cover physical receipt of the returned goods against the return order, which is covered by the separate Receive Return scenario in the same Returns cluster."
  },
  "preconditions": [
    "The original sales order exists and has been shipped in Oracle Fusion SCM Order Management.",
    "The item being returned is eligible for return per the customer's configured return policy.",
    "Return reason codes required for the return are configured.",
    "The test user has appropriate access to create return orders in Oracle Fusion Order Management."
  ],
  "test_data": [
    {
      "field": "Business Unit",
      "example": "${BUSINESS_UNIT}"
    },
    {
      "field": "Original Order Number",
      "example": "${ORIGINAL_ORDER_NUMBER}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Originally Shipped Quantity",
      "example": "${SHIPPED_QUANTITY}"
    },
    {
      "field": "Return Quantity",
      "example": "${RETURN_QUANTITY}"
    },
    {
      "field": "Return Reason",
      "example": "${RETURN_REASON}"
    },
    {
      "field": "Disposition",
      "example": "${DISPOSITION}"
    },
    {
      "field": "Return Date",
      "example": "${RETURN_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion Order Management as an authorised customer service test user.",
      "test_data": "",
      "expected_result": "Oracle Fusion opens successfully for the test user.",
      "validation_type": "action"
    },
    {
      "step_number": 2,
      "step_name": "Navigate to Order Management",
      "action": "Navigate to the Order Management work area to begin processing a customer return.",
      "test_data": "${BUSINESS_UNIT}",
      "expected_result": "The Order Management work area opens successfully for the correct business unit.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Original Shipped Order",
      "action": "Search for and open the previously shipped sales order the customer is returning against.",
      "test_data": "${ORIGINAL_ORDER_NUMBER} / ${CUSTOMER}",
      "expected_result": "The correct original order is located and its shipped item and quantity detail are displayed.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening order search, entering search criteria, and opening the located result."
    },
    {
      "step_number": 4,
      "step_name": "Initiate Create Return Order",
      "action": "Initiate a return order from the located original order.",
      "test_data": "",
      "expected_result": "A new return order is opened and pre-populated with the original order and item reference.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Enter Return Quantity and Reason",
      "action": "Enter the quantity being returned for the item and select the return reason.",
      "test_data": "${ITEM} / ${RETURN_QUANTITY} / ${RETURN_REASON}",
      "expected_result": "The return quantity and reason are accepted without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Select Disposition",
      "action": "Select the disposition for the returned item, such as return-to-stock or scrap/inspect.",
      "test_data": "${DISPOSITION}",
      "expected_result": "The disposition is accepted and reflected on the return order line.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Review and Submit the Return Order",
      "action": "Review the complete return order, including original order reference, item, quantity, reason and disposition, then submit it.",
      "test_data": "",
      "expected_result": "Oracle Fusion processes the return order request without unexpected errors.",
      "validation_type": "action",
      "note": "Reviewing the return order before submission lets the tester catch an incorrect quantity, reason or disposition before the return order is created."
    },
    {
      "step_number": 8,
      "step_name": "Verify Return Order Created and Correctly Referencing the Original Order",
      "action": "Confirm that the return order is created with a system-generated number, correctly references the original order and item, and is available for downstream receipt processing.",
      "test_data": "",
      "expected_result": "A return order number is generated, the return order correctly references the original order and item, return quantity and disposition match the entered data, and the return order is available for receipt.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly created return order that traces back to the original shipped order is the expected pass condition, not merely a successful save. Physical receipt of the returned goods is covered separately by the Receive Return scenario."
    }
  ],
  "expected_results": [
    "A return order is created successfully for the correct business unit and customer.",
    "A system-generated return order number is assigned.",
    "The return order correctly references the original shipped sales order and item.",
    "Return quantity does not exceed the quantity originally shipped.",
    "The return reason and disposition are correctly retained on the return order.",
    "The return order status correctly reflects a newly created return order.",
    "No unexpected save errors occur.",
    "The return order is available for downstream receipt processing."
  ],
  "validation_checkpoints": [
    "Return order correctly references the original order and item.",
    "Return quantity does not exceed the shipped quantity.",
    "Disposition is correctly recorded.",
    "Return order is available for downstream receipt processing."
  ]
}