4. Order Planned
Step 4 occurs when the ERP production system has scheduled and planned the order. This step confirms that raw materials are allocated, production scheduling is complete, and the order is ready for warehouse fulfillment. The Log Event for this step stays in the Planning Domain.

Animated walkthrough: in BPM Log Search, open Show Details on the Production Scheduled in ERP event of order ORD-10005 (Tailspin Toys), then the Context Values tab with the step's business data. The walkthrough shows ORD-10005; the examples below use order 1.
Understanding Step 4
ERP (Planning)"] --> This["fa:fa-calendar Step 4: Order Planned
ERP (Planning)"] Prev2["fa:fa-envelope Step 3: Confirmation
Portal (Sales)"] --> This This --> Next["fa:fa-box Step 5: Order Ready
WMS (Logistics)"] This -->|"Log Event
O2C.Order.Scheduled/1.0"| LogAPI["fa:fa-cloud-arrow-down Log API"] style Prev1 fill:#2678BD style Prev2 fill:#2678BD style This fill:#E47528 style Next fill:#2678BD style LogAPI fill:#3F827B
Step 4 (orange) is the convergence point: it follows both order entry and confirmation (blue), hands the order to the warehouse, and logs to the Log API (teal).
Message Details
- Message Type:
O2C.Order.Scheduled/1.0(Message Types) - Domain: Planning (Domains)
- System: ERP (Systems)
- Service: INT1337-PLN-Order-Scheduled (Services)
- Direction: Send (outgoing from ERP)
- Format: JSON
- Log Status:
0(Success);-1337on the Send event when the order stops at this step - Timing: In the generated data, 30-300 seconds after Step 3
Log Events in This Step
Step 4 logs two Log Events with the same Body. Only the business event appears in the BPM, where it shows as Production Scheduled and its incoming connectors are labeled Order Planned.
| SequenceNo (sent) | Service | Direction | EndPointName | Message Type | LogText | In BPM |
|---|---|---|---|---|---|---|
| 7 | INT1337-RCV-Planned-Incoming | Receive | ERP-Planning-Receive | O2C.Forwarding/1.0 |
Planning Request Received | ❌ No |
| 8 | INT1337-PLN-Order-Scheduled | Send | ERP-Planning-Send | O2C.Order.Scheduled/1.0 |
Production Scheduled in ERP | ✅ Yes |
The demo sends SequenceNo 1 to 14 per order. Nodinite keeps that value as the event's ServiceInstanceSequenceNo and gives the event its own SequenceNo, a running number in the Log Database.
Business Data (Happy Path)
The data of the order from Step 1, here order 1. Other orders carry their own customer, product, quantity, and total, the same in every step (see Generate O2C Demo Data):
- 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 the Log Event carries base64-encoded in its Body field.
{
"scheduleId": "SCH-2025-10001",
"orderId": "ORD-10001",
"customerId": "CUST-001",
"customerName": "Contoso 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 that the demo sends to the Nodinite Log API. See Log Event Reference for the O2C Log Event structure, and JSON formatted Log Event for every field.
Context Properties (Business Data)
The Context Options carry the business data and the Repository Binding:
{
"FileName": "ORD-10001-production-scheduled-in-erp.json",
"OrderNumber": "ORD-10001",
"CustomerId": "CUST-001",
"CustomerName": "Contoso Corporation",
"OrderAmount": "99.95",
"ExtendedProperties/1.0#RepositoryBinding": "..."
}
The schedule details (scheduleId, productionLines, estimatedCompletionDate) stay in the message body, not in the Context.
View the Message in Nodinite
With the demo Stylesheet installed, users read this JSON message as a production schedule. In the BPM Viewer, or a Log View, open Action on the Production Scheduled in ERP event and choose View message formatted as 'O2C - View Order Planned'.

The message rendered by the Liquid Stylesheet: priority, ready-by date, the production lines, and the materials.
Key Points for Step 4
- JSON Redux: Reuses JSON with a different structure than Step 1 (shows format reusability)
- Planning Domain: Stays within the Planning domain (Index 1, Step 3) after confirmation from Sales
- Production Details: The message includes production scheduling (lines, materials, capacity allocation)
- Convergence Point: Both Step 2 and Step 3 point to this step in the BPM, with connectors labeled "Order Planned"
- Internal Step: Represents the internal production planning workflow within the ERP before handoff to the WMS
- Business Dates vs Log Times: The payload dates (scheduled for 2025-10-16) are fixed sample values; the Log Event timestamps come 30-300 seconds after the previous step
Next Steps
- Order Planned Stylesheet — Render this message as a production schedule
- 5. Order Completed for Transport — Continue to Step 5
Related Topics
- 3. Order Confirmation Delivered to Customer — Previous step
- Order-to-Cash Process Demo — Overview of the complete 7-step demo process
- Log Event Reference — The O2C Log Event structure