- 0 minutes to read

1. Order Received from Customer

Step Overview

Step 1 in the Order-to-Cash process occurs when a customer order is received through the company's portal. This is the entry point for all orders into the system and triggers downstream planning and fulfillment activities.

Message Details

  • Message Type: O2C.Order.Received/1.0
  • Domain: Sales
  • System: Portal
  • Service: RCV-Order-Incoming
  • Direction: Receive (Incoming from external customer)
  • Format: JSON
  • Log Status: 0 (Success) for complete orders, -1337 if order reception fails

Business Data (Happy Path)

All orders in the demo use the same customer and product data:

  • Order ID: ORD-10001 through ORD-11000 (increments by 1 per interchange)
  • Customer ID: CUST-001
  • Customer Name: Acme Corporation
  • Customer Email: orders@acme.example.com
  • Product SKU: SKU-DEMO-001
  • Product Description: Demo Widget
  • Quantity: 1
  • Unit Price: USD 99.95
  • Order Total: USD 99.95
  • Currency: USD

Sample JSON Message

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

{
  "batchId": "batch-2025-10-14-001",
  "generatedAt": "2025-10-14T12:00:00Z",
  "orderId": "ORD-10001",
  "customer": {
    "customerId": "CUST-001",
    "name": "Acme Corporation",
    "email": "orders@acme.example.com"
  },
  "orderDate": "2025-10-14T09:15:00Z",
  "orderRows": [
    {
      "rowId": 1,
      "sku": "SKU-DEMO-001",
      "description": "Demo Widget",
      "quantity": 1,
      "unitPrice": 99.95,
      "lineTotal": 99.95
    }
  ],
  "orderTotal": 99.95,
  "currency": "USD"
}

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-received.json",
  "OrderNumber": "ORD-10001",
  "CustomerId": "CUST-001",
  "CustomerName": "Acme Corporation",
  "OrderAmount": "99.95",
  "ExtendedProperties/1.0#RepositoryBinding": "..."
}

Key Points for Step 1

  1. Entry Point: This is the first step in the O2C process (Step 0 in the BPM, SequenceNo=0)
  2. No Incoming Relations: Repository Binding has empty ServiceRelations array since no prior step feeds data into this step
  3. Sales Domain: This step occurs in the Sales domain (Index 0) and happens in the Portal system
  4. Direction: This is a Receive endpoint (data flows into Portal from external customer)
  5. Correlation Establishment: The Correlation ID is generated here and remains constant through all 7 steps of the order
  6. Repository Binding Initiation: This step initiates the automatic BPM visualization with the first domain transition point