- 4 minutes to read

O2C Demo: Process Steps, Systems, and Services

This page is part of the Order-to-Cash demo. It lists the seven business steps of an order, the Systems and Services that run them, and how the order moves through the four business Domains. The Integration Landscape page draws the same Services as a topology.

O2C Process Milestones

The following table defines the seven key steps in the Order-to-Cash process. Each step represents a domain-specific action that generates a Log Event. The Message Type Name determines which Search Field Expressions Nodinite evaluates to extract business data.

Step # Milestone Domain Message Type Name System Service Direction Format
1 Order Received from Customer Sales O2C.Order.Received/1.0 Portal INT1337-RCV-Order-Incoming Receive JSON
2 Order Entry in ERP Finished Planning O2C.Order.Entry/1.0 ERP INT1337-ENT-Order-Entry Send XML
3 Order Confirmation Delivered to Customer Sales O2C.Order.Confirmation/1.0 Portal INT1337-SND-Confirm-Outgoing Send CSV
4 Order Planned Planning O2C.Order.Scheduled/1.0 ERP INT1337-PLN-Order-Scheduled Send JSON
5 Order Completed for Transport Logistics O2C.Order.Ready/1.0 WMS INT1337-PKG-Order-Packed Send XML
6 Order Delivered Logistics O2C.Order.Delivered/1.0 WMS INT1337-RCV-Order-Delivered Send PSV
7 Order Invoiced Finance O2C.Order.Invoice/1.0 ERP-Finance INT1337-INV-Order-Invoiced Send JSON

The table lists the business (BPM-visible) Log Event of each step. Each step also logs a second, forwarding Log Event with the Message Type O2C.Forwarding/1.0 (see Forwarder Services).

Each step page shows the message sample, the business data, the Context Properties, and the key points for that step's Domain or System transition. The BPM Expected Layout page shows how the steps appear in the BPM matrix.

Systems

  • Portal: Customer-facing portal where orders are received
  • ERP: Enterprise Resource Planning system handling planning and finance
  • WMS: Warehouse Management System for logistics operations
  • ERP-Finance: Finance module within the ERP for invoicing

Services Architecture

The demo includes 14 paired Services (7 primary + 7 forwarders) organized as 7 complete business milestones. Each milestone generates 2 Log Events: a Receive event and a Send event, creating a full audit trail.

Primary Business Services

These 7 Services run the actual O2C milestones with BPMs tracking:

  • INT1337-RCV-Order-Incoming (Portal, Receive) - Step 0
  • INT1337-ENT-Order-Entry (ERP, Send) - Step 1
  • INT1337-SND-Confirm-Outgoing (Portal, Send) - Step 2
  • INT1337-PLN-Order-Scheduled (ERP, Send) - Step 3
  • INT1337-PKG-Order-Packed (WMS, Send) - Step 4
  • INT1337-RCV-Order-Delivered (WMS, Send) - Step 5
  • INT1337-INV-Order-Invoiced (ERP-Finance, Send) - Step 6

Forwarder Services

These 7 Services bridge Receive-to-Send transitions (no BPM, architectural only). Their Log Events carry the Message Type O2C.Forwarding/1.0:

  • INT1337-SND-Order-Incoming (Portal, Send) - Step 0 forwarder
  • INT1337-RCV-Order-Entry (ERP, Receive) - Step 1 forwarder
  • INT1337-RCV-Confirm-Incoming (Portal, Receive) - Step 2 forwarder
  • INT1337-RCV-Planned-Incoming (ERP, Receive) - Step 3 forwarder
  • INT1337-RCV-Packing-Incoming (WMS, Receive) - Step 4 forwarder
  • INT1337-RCV-Order-Delivered-Incoming (WMS, Receive) - Step 5 forwarder
  • INT1337-RCV-Invoice-Incoming (ERP-Finance, Receive) - Step 6 forwarder

Why 14 events per order? Each of the 7 steps generates a paired Receive→Send event sequence. The primary Service (with BPMs metadata) represents the business milestone. The forwarder Service creates the architectural connection needed for proper service relations. See Integration Landscape for the complete Service topology, and O2C Demo: Repository Binding for how the relations are declared.

Domain Transitions

The O2C process traverses 4 distinct business Domains: Sales → Planning → Logistics → Finance.

SALES DOMAIN (Index 0)
├─ Step 1: Portal receives orders (Receive)
├─ Step 3: Portal confirms orders (Send)
└─ Customer notifications

    ↓ (transition via order confirmation)

PLANNING DOMAIN (Index 1)
├─ Step 2: ERP enters orders (Send)
├─ Step 4: ERP schedules production (Send)
└─ Resource allocation

    ↓ (transition via schedule)

LOGISTICS DOMAIN (Index 2)
├─ Step 5: WMS packs orders (Send)
├─ Step 6: WMS delivers orders (Send)
└─ Shipment tracking

    ↓ (transition via delivery proof)

FINANCE DOMAIN (Index 3)
└─ Step 7: Finance invoices orders (Send)
   Payment terms, revenue recognition

Next Steps