- 5 minutes to read

2. Order Entry in ERP Finished

Step 2 occurs when the Enterprise Resource Planning (ERP) system has entered the order. This confirms that the ERP has validated the order, added it to inventory planning, and made it ready for fulfillment. The Log Event for this step is the first one in the Planning Domain.

Order Entry step of order ORD-10005 in BPM Log Search: Show Details on its event, then Context Values with the file name, order number, customer, amount, and Repository Binding, animated walkthrough (7.12)
Animated walkthrough: in BPM Log Search, open Show Details on the Order Entry in ERP Finished 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 2

graph LR Prev["fa:fa-inbox Step 1: Order Received
Portal (Sales)"] --> This["fa:fa-server Step 2: Order Entry
ERP (Planning)"] This --> Next1["fa:fa-envelope Step 3: Confirmation
Portal (Sales)"] This --> Next2["fa:fa-calendar Step 4: Order Planned
ERP (Planning)"] This -->|"Log Event
O2C.Order.Entry/1.0"| LogAPI["fa:fa-cloud-arrow-down Log API"] style Prev fill:#2678BD style This fill:#E47528 style Next1 fill:#2678BD style Next2 fill:#2678BD style LogAPI fill:#3F827B

Step 2 (orange) receives the order from Step 1 and splits the flow into two paths, confirmation and planning (blue); its Log Event goes to the Log API (teal).

Message Details

  • Message Type: O2C.Order.Entry/1.0 (Message Types)
  • Domain: Planning (Domains)
  • System: ERP (Systems)
  • Service: INT1337-ENT-Order-Entry (Services)
  • Direction: Send (outgoing from ERP)
  • Format: XML
  • Log Status: 0 (Success); -1337 on the Send event when the order stops at this step
  • Timing: In the generated data, 30-300 seconds after Step 1

Log Events in This Step

Step 2 logs two Log Events with the same Body. Only the business event appears in the BPM.

SequenceNo (sent) Service Direction EndPointName Message Type LogText In BPM
3 INT1337-RCV-Order-Entry Receive ERP-OrderEntry-Receive O2C.Forwarding/1.0 Order Entry Received ❌ No
4 INT1337-ENT-Order-Entry Send ERP-OrderEntry-Send O2C.Order.Entry/1.0 Order Entry in ERP Finished ✅ 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 XML Message

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

<?xml version="1.0" encoding="utf-8"?>
<OrderEntry xmlns="http://schemas.Contoso.example/O2C/1.0">
  <OrderHeader>
    <OrderId>ORD-10001</OrderId>
    <OrderDate>2025-10-14T09:15:00Z</OrderDate>
    <EntryDate>2025-10-14T09:18:30Z</EntryDate>
    <OrderStatus>ENTERED</OrderStatus>
  </OrderHeader>
  <Customer>
    <CustomerId>CUST-001</CustomerId>
    <CustomerName>Contoso Corporation</CustomerName>
    <CustomerEmail>orders@Contoso.example.com</CustomerEmail>
  </Customer>
  <OrderLines>
    <OrderLine>
      <LineId>1</LineId>
      <SKU>SKU-DEMO-001</SKU>
      <Description>Demo Widget</Description>
      <Quantity>1</Quantity>
      <UnitPrice>99.95</UnitPrice>
      <LineTotal>99.95</LineTotal>
      <InventoryReserved>true</InventoryReserved>
    </OrderLine>
  </OrderLines>
  <OrderTotal>99.95</OrderTotal>
  <Currency>USD</Currency>
  <ERPReferenceNumber>ERP-2025-10001</ERPReferenceNumber>
</OrderEntry>

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-order-entry-in-erp-finished.xml",
  "OrderNumber": "ORD-10001",
  "CustomerId": "CUST-001",
  "CustomerName": "Contoso Corporation",
  "OrderAmount": "99.95",
  "ExtendedProperties/1.0#RepositoryBinding": "..."
}

The ERP reference number (ERP-2025-10001) stays in the message body, not in the Context.

View the Message in Nodinite

With the demo Stylesheet installed, users read this XML message as an ERP order document. In the BPM Viewer, or a Log View, open Action on the Order Entry in ERP Finished event and choose View message formatted as 'O2C - View Order Entry'.

Order Entry ORD-10005 for Tailspin Toys rendered by the O2C - View Order Entry Stylesheet (7.12)
The message rendered by the XSLT Stylesheet: ERP reference, dates, status, and the order lines with their reservation.

Key Points for Step 2

  1. XML Format: Demonstrates a structured data format for ERP integration (vs JSON in Step 1)
  2. Planning Domain Transition: First entry into the Planning domain (Index 1, Step 1; the business event is sent with SequenceNo 4)
  3. External Service Relation: The Receive event (INT1337-RCV-Order-Entry) has an ExternalServiceRelations entry back to the Step 1 Send Service (INT1337-SND-Order-Incoming, Portal), showing the data dependency
  4. Internal Service Relation: The Send event (INT1337-ENT-Order-Entry) has an InternalServiceRelations entry to the Receive Service of the same step
  5. ERP Processing: The script gives Send events a random ProcessingTime of 40-300 ms and Receive events 5-50 ms
  6. Send Direction: Data flows outward from the ERP (EndPointDirection: 1, EventDirection: 18)
  7. Cross-System Connection: First service relation connecting the Portal (Step 1) to the ERP (Step 2)

Next Steps