{
  "test_id": "ORCL.O2C.OM.SO.SUBMIT",
  "scenario_name": "Submit Sales Order",
  "application": "Oracle Fusion Cloud",
  "product": "SCM / Order Management",
  "module": "Order Management",
  "process": "Sales Orders",
  "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/sales-orders/submit-sales-order/",
  "objective": {
    "intro": "The objective of this test is to validate that a complete drafted sales order — with all required lines, pricing and tax already calculated — can be submitted in Oracle Fusion Order Management, and that the order's status, downstream eligibility and traceability reflect the submission correctly.",
    "confirms": [
      "the order submits successfully once all required order lines are complete and priced",
      "the order status changes from draft to submitted correctly",
      "the submitted order becomes visible to downstream scheduling, reservation and fulfillment processing",
      "Oracle's validations correctly block submission of an incomplete, credit-held or invalid order",
      "resubmission succeeds once a validation error has been corrected",
      "duplicate or unauthorized submission attempts are correctly prevented"
    ],
    "scope_note": "This scenario covers submission of an already-complete draft sales order within Oracle Fusion Order Management TEST/UAT environments. It does not cover creation of the order itself, which is covered by the separate Create Sales Order and Create Multi-Line Order scenarios, or the scheduling action itself, which is covered by the separate Schedule Order scenario in Fulfillment."
  },
  "preconditions": [
    "A complete draft sales order exists in Oracle Fusion Order Management with all required order lines captured.",
    "The customer's credit status is acceptable for the order to proceed to submission.",
    "Pricing and tax have been fully calculated on all order lines.",
    "The user submitting the order holds the appropriate order-entry submit 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": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "Order Total",
      "example": "${ORDER_TOTAL}"
    },
    {
      "field": "Order Type",
      "example": "${ORDER_TYPE}"
    },
    {
      "field": "Line Count",
      "example": "${LINE_COUNT}"
    },
    {
      "field": "Requested Ship Date",
      "example": "${REQUESTED_SHIP_DATE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion using an authorised Order Management 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.",
      "test_data": "",
      "expected_result": "The Order Management work area opens successfully.",
      "validation_type": "action"
    },
    {
      "step_number": 3,
      "step_name": "Locate the Draft Order",
      "action": "Search for and open the drafted sales order to be submitted.",
      "test_data": "${ORDER_NUMBER}",
      "expected_result": "The correct draft sales order opens for review.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening order search, entering search criteria and selecting the result."
    },
    {
      "step_number": 4,
      "step_name": "Review Order Lines for Completeness",
      "action": "Review all order lines, including item, quantity, pricing and tax, to confirm the order is complete.",
      "test_data": "",
      "expected_result": "All required order lines are complete, priced and ready for submission.",
      "validation_type": "action",
      "note": "Confirming completeness before submission helps distinguish a data-completeness issue from a submission or configuration issue if the test later fails."
    },
    {
      "step_number": 5,
      "step_name": "Initiate Submission",
      "action": "Select the option to submit the order.",
      "test_data": "",
      "expected_result": "Oracle Fusion begins processing the submission.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Resolve Validation Errors, If Surfaced",
      "action": "Review and resolve any validation errors Oracle Fusion surfaces during submission, such as missing data or an unresolved credit hold.",
      "test_data": "",
      "expected_result": "Validation errors, where present, are resolved and the order becomes eligible for submission.",
      "validation_type": "action",
      "note": "This step covers the correction path exercised when a negative variation surfaces an expected validation error."
    },
    {
      "step_number": 7,
      "step_name": "Confirm Submission",
      "action": "Confirm the submission once any validation errors have been resolved.",
      "test_data": "",
      "expected_result": "Oracle Fusion accepts the submission without unexpected errors.",
      "validation_type": "action"
    },
    {
      "step_number": 8,
      "step_name": "Verify Order Status Updated and Available for Scheduling",
      "action": "Reopen or refresh the order and review its status and downstream availability.",
      "test_data": "",
      "expected_result": "The order status updates correctly to submitted, and the order becomes visible to downstream scheduling, reservation and fulfillment processes.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correct status transition and downstream visibility are the expected pass condition, not merely an accepted submission."
    }
  ],
  "expected_results": [
    "The order submits successfully once all required order lines are complete and priced.",
    "The order status changes correctly to reflect submission.",
    "The order becomes eligible for downstream scheduling, reservation and fulfillment.",
    "Validation errors correctly block submission until resolved.",
    "Duplicate or unauthorized submission attempts are correctly prevented.",
    "Submission history and audit trail are recorded for traceability."
  ],
  "validation_checkpoints": [
    "The order status transitions correctly from draft to submitted.",
    "The order becomes visible to downstream scheduling and fulfillment processes.",
    "Validation errors block submission until they are resolved.",
    "Submission history and audit trail are recorded for the order."
  ]
}