- 0 minutes to read

4. Order Planned

Step Overview

Step 4 occurs when the order has been scheduled and planned within the ERP production system. This step confirms that raw materials have been allocated, production scheduling is complete, and the order is ready for warehouse fulfillment.

Message Details

  • Message Type: O2C.Order.Scheduled/1.0
  • Domain: Planning
  • System: ERP
  • Service: PLN-Order-Scheduled
  • Direction: Send (Outgoing from ERP)
  • Format: JSON
  • Log Status: 0 (Success) for confirmed planning, -1337 if scheduling fails
  • Timing: Typically 15-30 minutes after Order Entry

Business Data (Happy Path)

Same customer and product data as Step 1:

  • Order ID: ORD-10001 (same as source order)
  • Customer ID: CUST-001
  • Product SKU: SKU-DEMO-001
  • Quantity: 1
  • Order Total: USD 99.95

Sample JSON Message

This is the raw message payload that would be base64-encoded in the Log Event Body field.

{
  "scheduleId": "SCH-2025-10001",
  "orderId": "ORD-10001",
  "customerId": "CUST-001",
  "customerName": "Acme Corporation",
  "orderDate": "2025-10-14T09:15:00Z",
  "scheduleDate": "2025-10-14T09:37:45Z",
  "productionLines": [
    {
      "lineId": "LINE-01",
      "lineName": "Assembly Line A",
      "scheduledStart": "2025-10-16T06:00:00Z",
      "scheduledEnd": "2025-10-16T14:30:00Z",
      "expectedDuration": 510,
      "shift": "DAY",
      "capacity": 50
    }
  ],
  "materials": [
    {
      "materialId": "MAT-SKU-DEMO-001",
      "sku": "SKU-DEMO-001",
      "description": "Demo Widget",
      "quantityRequired": 1,
      "quantityAllocated": 1,
      "availableAtScheduleTime": true
    }
  ],
  "orderQuantity": 1,
  "orderAmount": 99.95,
  "currency": "USD",
  "priorityLevel": "NORMAL",
  "schedulingStatus": "CONFIRMED",
  "estimatedCompletionDate": "2025-10-16T14:30:00Z"
}

Nodinite Log Event (JSON formatted)

This step creates a Log Event sent to the Nodinite Log API. Refer to Log Event Reference for the complete Log Event structure and field definitions.

Context Properties (Business Data) 

{
  "FileName": "ORD-10001-planning.json",
  "OrderNumber": "ORD-10001",
  "CustomerId": "CUST-001",
  "CustomerName": "Acme Corporation",
  "OrderAmount": "99.95",
  "ScheduleId": "SCH-2025-10001",
  "ProductionLine": "LINE-01",
  "EstimatedCompletion": "2025-10-16T14:30:00Z",
  "ExtendedProperties/1.0#RepositoryBinding": "..."
}

Key Points for Step 4

  1. JSON Redux: JSON reused with different structure than Step 1 (shows format reusability)
  2. Planning Domain: Stays within Planning domain (Index 1, Step 3) after confirmation from Sales
  3. Production Details: Message includes production scheduling (lines, materials, capacity allocation)
  4. Extended Processing: 312ms reflects complex ERP scheduling calculations
  5. Internal Step: This represents the internal production planning workflow within ERP before handoff to WMS
  6. Longest Timing Gap: First major time gap in the process (15-30 minutes after Step 3)