{
  "test_id": "ORCL.O2C.OM.SO.CREATE",
  "scenario_name": "Create 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/create-sales-order/",
  "objective": {
    "intro": "The objective of this test is to validate that a standard sales order can be created in Oracle Fusion SCM Order Management using a valid customer, item, quantity, unit of measure, warehouse, requested date and price list, and that the resulting sales order is created with correct header and line detail, pricing and status.",
    "confirms": [
      "the sales order is created for the correct business unit and customer",
      "customer account status and credit checks are enforced correctly",
      "item, quantity, UOM and warehouse detail is captured accurately on the line",
      "pricing is calculated correctly from the applicable price list",
      "the sales order receives a system-generated order number and correct status",
      "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 single or multi-line standard sales order in Oracle Fusion SCM Order Management TEST/UAT environments. It does not cover order submission for fulfillment, scheduling or shipment, which are covered by the separate Submit Sales Order and related scenarios in the same Sales Orders cluster."
  },
  "preconditions": [
    "The customer account used on the sales order is active and creditworthy according to configured credit checks.",
    "The item being ordered is active and orderable in the item catalog.",
    "A price list applicable to the customer and item combination is configured and active.",
    "The order entry specialist has appropriate access to create a sales order for the business unit.",
    "The warehouse and requested date used on the sales order are valid and available."
  ],
  "test_data": [
    {
      "field": "Business Unit",
      "example": "${BUSINESS_UNIT}"
    },
    {
      "field": "Customer",
      "example": "${CUSTOMER}"
    },
    {
      "field": "Item",
      "example": "${ITEM}"
    },
    {
      "field": "Quantity",
      "example": "${QUANTITY}"
    },
    {
      "field": "UOM",
      "example": "${UOM}"
    },
    {
      "field": "Price List",
      "example": "${PRICE_LIST}"
    },
    {
      "field": "Warehouse",
      "example": "${WAREHOUSE}"
    },
    {
      "field": "Requested Date",
      "example": "${REQUESTED_DATE}"
    },
    {
      "field": "Payment Terms",
      "example": "${PAYMENT_TERMS}"
    },
    {
      "field": "Order Type",
      "example": "${ORDER_TYPE}"
    }
  ],
  "business_steps": [
    {
      "step_number": 1,
      "step_name": "Sign In to Oracle Fusion",
      "action": "Sign in to Oracle Fusion using an authorised order entry 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 creating a sales order.",
      "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": "Initiate Create Sales Order",
      "action": "Start a new sales order from the Order Management work area.",
      "test_data": "${ORDER_TYPE}",
      "expected_result": "A new, unsaved sales order is opened for the correct business unit and order type.",
      "validation_type": "action",
      "note": "This single business step replaces multiple technical actions such as opening the create page and confirming the order type."
    },
    {
      "step_number": 4,
      "step_name": "Select Customer",
      "action": "Search for and select the customer for the sales order.",
      "test_data": "${CUSTOMER}",
      "expected_result": "The customer is accepted and reflected on the sales order header.",
      "validation_type": "action"
    },
    {
      "step_number": 5,
      "step_name": "Add Item Lines",
      "action": "Search for and add the item to the sales order, entering quantity and unit of measure.",
      "test_data": "${ITEM} / ${QUANTITY} / ${UOM}",
      "expected_result": "The item line is accepted and added to the sales order without unexpected validation errors.",
      "validation_type": "action"
    },
    {
      "step_number": 6,
      "step_name": "Select Warehouse and Requested Date",
      "action": "Select the shipping warehouse and enter the requested date for the sales order line.",
      "test_data": "${WAREHOUSE} / ${REQUESTED_DATE}",
      "expected_result": "The warehouse and requested date are accepted and reflected on the line.",
      "validation_type": "action"
    },
    {
      "step_number": 7,
      "step_name": "Review Pricing",
      "action": "Review the pricing calculated for the line and header based on the applicable price list and payment terms.",
      "test_data": "${PRICE_LIST} / ${PAYMENT_TERMS}",
      "expected_result": "The reviewed sales order reflects pricing consistent with the applicable price list.",
      "validation_type": "action",
      "note": "Reviewing pricing before saving lets the tester catch an incorrect price list or line entry before the order is created."
    },
    {
      "step_number": 8,
      "step_name": "Review and Submit the Sales Order",
      "action": "Review the complete sales order and save it for creation in the test environment.",
      "test_data": "",
      "expected_result": "A sales order number is generated, the order status is correct, and customer, item, quantity, pricing and totals match the entered data.",
      "validation_type": "business_assertion",
      "note": "This is the primary business assertion for the scenario — a correctly created sales order with accurate header and line detail is the expected pass condition, not merely a successful save. Formal submission for scheduling and fulfillment is covered separately by the Submit Sales Order scenario."
    }
  ],
  "expected_results": [
    "The sales order is created for the correct business unit and customer.",
    "A system-generated order number is assigned.",
    "Item, quantity, UOM and warehouse detail on the line are correct.",
    "Pricing is calculated correctly from the applicable price list.",
    "The requested date and payment terms are correctly reflected.",
    "The sales order status correctly reflects a newly created order.",
    "Credit checks are correctly enforced where the customer requires them."
  ],
  "validation_checkpoints": [
    "Order created with correct status.",
    "Customer, item and pricing details are accurate.",
    "Order is available for downstream processing, such as scheduling.",
    "Credit check is correctly enforced where applicable."
  ]
}