- 0 minutes to read

Nodinite O2C Integration Landscape and Architecture

Visualize the complete Order-to-Cash integration landscape showing how 7 business steps flow seamlessly across 4 systems, 4 organizational domains, and 14 correlated events. This demo illustrates real-world multi-system integration with Nodinite BPM tracking and end-to-end logging.

On this page, you will:

✅ Understand the 7-step Order-to-Cash process spanning Portal, ERP, WMS, and Finance systems
✅ See how Domains (Sales, Planning, Logistics, Finance) coordinate across Systems
✅ Learn correlation patterns that track transactions end-to-end
✅ Discover how service relations enable multi-system orchestration
✅ Explore how Business Process Models visualize the integration topology

O2C Integration Landscape
This diagram illustrates the Integration Landscape for the Order-to-Cash process, highlighting the key Systems and Services involved.

The 7-Step Order-to-Cash Process

The O2C process spans 7 steps (0-6) across 4 Systems and 4 business Domains. Each step generates two events: a Receive event and a Send event, for a total of 14 events per complete order.

Steps Overview

Step Name System Domain Message Type Format Duration
0 Order Received Portal Sales O2C.Order.Received/1.0 JSON 00:00-01:00 min
1 Order Entry ERP Planning O2C.Order.Entry/1.0 XML 01:00-05:00 min
2 Order Confirmation Portal Sales O2C.Order.Confirmation/1.0 CSV 05:00-10:00 min
3 Production Scheduled ERP Planning O2C.Order.Scheduled/1.0 JSON 10:00-20:00 min
4 Order Completed for Transport WMS Logistics O2C.Order.Ready/1.0 XML 20:00-30:00 min
5 Order Delivered WMS Logistics O2C.Order.Delivered/1.0 PSV 30:00-60:00 min
6 Order Invoiced ERP-Finance Finance O2C.Order.Invoice/1.0 JSON 60:00-90:00 min

Systems & Services Overview

System Domain Steps Services Format Role
Portal Sales (0) 0, 2 RCV-Order-Incoming, SND-Order-Incoming, RCV-Confirm-Incoming, SND-Confirm-Outgoing JSON, CSV Customer interface - receives orders & sends confirmations
ERP Planning (1) 1, 3 RCV-Order-Entry, ENT-Order-Entry, RCV-Planned-Incoming, PLN-Order-Scheduled XML, JSON Order processing & production scheduling
WMS Logistics (2) 4, 5 RCV-Packing-Incoming, PKG-Order-Packed, RCV-Order-Delivered-Incoming, RCV-Order-Delivered XML, PSV Warehouse operations & delivery
ERP-Finance Finance (3) 6 RCV-Invoice-Incoming, INV-Order-Invoiced JSON Invoice generation & revenue recognition

Process Flow Diagram 

                    ORDER-TO-CASH PROCESS FLOW (7 Steps)

     SALES              PLANNING            LOGISTICS            FINANCE
    (Portal)             (ERP)               (WMS)            (ERP-Finance)
       │                  │                   │                   │
       │                  │                   │                   │
    ┌──┴──┐          ┌────┴─────┐       ┌────┴────┐          ┌────┴─────┐
    │ Step 0           │ Step 1    │     │ Step 4  │          │ Step 6    │
    │ RCV: JSON        │ RCV: XML  │     │ RCV: XML│          │ RCV: JSON │
    │ Order            │ Order     │     │ Ready   │          │ Invoice   │
    │ Received         │ Entry     │     │ for     │          │           │
    └────┬─────────────┼────┬──────┘     │ Transport
         │             │    │            └──┬──────┐
         │             │    │               │      │
    ┌────┴─┐      ┌────┴──┐│          ┌────┴──┐  ┌┴──┐
    │Step 2 │      │Step 3 ││          │Step 5 │  │   │
    │SND: CSV      │SND:   ││          │SND:   │  │   │
    │Confirm  JSON │ Schedul  PSV │  │   │
    │       Scheduled

Service Relations and Message Routing

The O2C process uses RepositoryBinding context to define service relations and manage message routing:

  • ExternalServiceRelations: Define connections between Services in different Systems (Receive events)
  • InternalServiceRelations: Define connections within the same Systems (Send events)
  • BPM Metadata: Each step includes Business Process Model (BPM) for topology visualization

Correlation and Traceability

All messages throughout the 7-step O2C process are correlated using a consistent CorrelationId format (see Search Fields & Correlation for implementation details):

  • Format: {PREFIX}-{YYYYMMDD}-{HHMM}-{SEQUENCE}
  • Example: PIC-20251024-0930-0001
  • Components:
    • {PREFIX}: Integration identifier (e.g., PIC for Portal Integration)
    • {YYYYMMDD}: Order date (e.g., 20251024)
    • {HHMM}: Order time (e.g., 0930 for 09:30 UTC)
    • {SEQUENCE}: Unique order number starting at 0001

Context Properties carried through all 7 steps:

  • CorrelationId: The correlation ID format above
  • ApplicationInterchangeId: Order ID (e.g., ORD-10001)
  • MessageType: Current step's Message Types (e.g., O2C.Order.Entry/1.0)
  • Step: Current step number (0-6)
  • Domain: Current Domains (Sales, Planning, Logistics, Finance)
  • SystemName: Current system (Portal, ERP, WMS, ERP-Finance)

Domain Summary

Domain Index Steps Message Types Key Responsibility
Sales 0 0, 2 Message Types: O2C.Order.Received/1.0 (JSON), O2C.Order.Confirmation/1.0 (CSV) Customer interface - order reception & confirmation
Planning 1 1, 3 Message Types: O2C.Order.Entry/1.0 (XML), O2C.Order.Scheduled/1.0 (JSON) Transform orders into executable production plans
Logistics 2 4, 5 Message Types: O2C.Order.Ready/1.0 (XML), O2C.Order.Delivered/1.0 (PSV) Warehouse operations & shipment fulfillment
Finance 3 6 Message Types: O2C.Order.Invoice/1.0 (JSON) Invoice generation & revenue recognition

Key Characteristics

  • Message Diversity: JSON (Portal, ERP-Finance), XML (ERP, WMS), CSV (Portal confirmations), PSV (WMS delivery)
  • 7 Steps: Span 4 systems, 4 domains, with 14 events per complete order (2 per step)
  • ~90% Progression: Orders advance to next step with 90% probability
  • ~653 Events: From 100 orders across all 7 steps
  • Correlation: All messages linked via CorrelationId format: {PREFIX}-{YYYYMMDD}-{HHMM}-{SEQUENCE}

Next Steps

Ready to see the O2C demo in action? Start with the Overview:

Order-to-Cash Demo Overview – Complete introduction to the 7-step process, all 4 systems, and how to generate demo data
BPM Expected Layout – Detailed breakdown of the Business Process Model matrix visualization

Understand the integration patterns:

Repository Model – Overall integration architecture framework
Business Process Model (BPM) – Visual process documentation and monitoring
Search Fields & Correlation – How to extract and correlate business identifiers across steps
Services – Integration services that execute each process step
Domains – Organizational swimlanes for multi-domain coordination

Demo data and generation:

Generate Demo Data Script – PowerShell script that creates 100 realistic O2C orders
Message Types – Standard message formats for each step (JSON, XML, CSV, PSV)