- 0 minutes to read

2. Order Entry in ERP Finished

Step Overview

Step 2 occurs when the order has been successfully entered into the Enterprise Resource Planning (ERP) system. This confirms the order has been validated, added to inventory planning, and is ready for fulfillment.

Message Details

  • Message Type: O2C.Order.Entry/1.0
  • Domain: Planning
  • System: ERP
  • Service: ENT-Order-Entry
  • Direction: Send (Outgoing from ERP)
  • Format: XML
  • Log Status: 0 (Success) for complete entry, -1337 if entry fails
  • Timing: Typically 2-5 minutes after Order Received

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 XML Message

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

<?xml version="1.0" encoding="utf-8"?>
<OrderEntry xmlns="http://schemas.acme.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>Acme Corporation</CustomerName>
    <CustomerEmail>orders@acme.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 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-entry.xml",
  "OrderNumber": "ORD-10001",
  "CustomerId": "CUST-001",
  "CustomerName": "Acme Corporation",
  "OrderAmount": "99.95",
  "ERPReferenceNumber": "ERP-2025-10001",
  "ExtendedProperties/1.0#RepositoryBinding": "..."
}

Key Points for Step 2

  1. XML Format: Demonstrates structured data format for ERP integration (vs JSON in Step 1)
  2. Planning Domain Transition: First entry into Planning domain (Index 1, SequenceNo=1)
  3. External Service Relation: Repository Binding includes relation back to Step 1 (Portal) showing data dependency
  4. ERP Processing: Increased ProcessingTime reflects ERP system complexity (156ms vs 45ms in Step 1)
  5. Send Direction: Data flows outward from ERP (EndPointDirection: 1, EventDirection: 18)
  6. Cross-System Connection: First service relation connecting Portal (Step 1) to ERP (Step 2)