O2C Integration Landscape and Architecture
Visualize the complete Order-to-Cash integration landscape, showing how 7 business steps flow 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. Nodinite builds the whole landscape from the Repository Binding in the demo Log Events.
On this page, you will:
- ✅ Understand the 7-step Order-to-Cash process spanning the 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

Animated walkthrough: open Mapify on the Integration INT1337 - Order-to-Cash. At Depth 1 it shows the four Systems; at Depth 2 their fourteen Services. Find Item on the forwarder Service INT1337-SND-Order-Incoming zooms to it, next to the Portal Service it forwards from. The Domains are on the BPM: they're four hops from the Integration, too dense to read at that depth.

The Integration Landscape for the Order-to-Cash process, with the four Systems and their Services.
Understanding the O2C Process Flow
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.
JSON"] P2["fa:fa-envelope Step 2: Order Confirmation
CSV"] end subgraph ERP["ERP (Planning)"] E1["fa:fa-server Step 1: Order Entry
XML"] E3["fa:fa-calendar Step 3: Production Scheduled
JSON"] end subgraph WMS["WMS (Logistics)"] W4["fa:fa-box Step 4: Ready for Transport
XML"] W5["fa:fa-truck Step 5: Order Delivered
PSV"] end subgraph FIN["ERP-Finance (Finance)"] F6["fa:fa-file-invoice-dollar Step 6: Order Invoiced
JSON"] end P0 --> E1 E1 --> P2 E1 --> E3 P2 --> E3 E3 --> W4 W4 --> W5 W5 --> F6 style P0 fill:#2678BD style P2 fill:#2678BD style E1 fill:#E47528 style E3 fill:#E47528 style W4 fill:#3F827B style W5 fill:#3F827B style F6 fill:#9E59BB
The 7 steps grouped by System and Domain: Portal/Sales (blue), ERP/Planning (orange), WMS/Logistics (teal), and ERP-Finance/Finance (purple), with each step's message format.
Steps Overview
| Step | Name | System | Domain | Message Type | Format | BPM Service (Direction) |
|---|---|---|---|---|---|---|
| 0 | Order Received | Portal | Sales | O2C.Order.Received/1.0 |
JSON | INT1337-RCV-Order-Incoming (Receive) |
| 1 | Order Entry | ERP | Planning | O2C.Order.Entry/1.0 |
XML | INT1337-ENT-Order-Entry (Send) |
| 2 | Order Confirmation | Portal | Sales | O2C.Order.Confirmation/1.0 |
CSV | INT1337-SND-Confirm-Outgoing (Send) |
| 3 | Production Scheduled | ERP | Planning | O2C.Order.Scheduled/1.0 |
JSON | INT1337-PLN-Order-Scheduled (Send) |
| 4 | Order Completed for Transport | WMS | Logistics | O2C.Order.Ready/1.0 |
XML | INT1337-PKG-Order-Packed (Send) |
| 5 | Order Delivered | WMS | Logistics | O2C.Order.Delivered/1.0 |
PSV | INT1337-RCV-Order-Delivered (Send) |
| 6 | Order Invoiced | ERP-Finance | Finance | O2C.Order.Invoice/1.0 |
JSON | INT1337-INV-Order-Invoiced (Send) |
The Message Type belongs to the business event of each step. The other event of the step, logged by the forwarder Service, uses O2C.Forwarding/1.0. In the generated data, each step's Receive event comes 30-300 seconds after the previous step, and its Send event 1-4 seconds later.
Systems and 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 |
Domain Summary
| Domain | Index | Steps | Message Types | Key Responsibility |
|---|---|---|---|---|
| Sales | 0 | 0, 2 | O2C.Order.Received/1.0 (JSON), O2C.Order.Confirmation/1.0 (CSV) | Customer interface - order reception & confirmation |
| Planning | 1 | 1, 3 | O2C.Order.Entry/1.0 (XML), O2C.Order.Scheduled/1.0 (JSON) | Transform orders into executable production plans |
| Logistics | 2 | 4, 5 | O2C.Order.Ready/1.0 (XML), O2C.Order.Delivered/1.0 (PSV) | Warehouse operations & shipment fulfillment |
| Finance | 3 | 6 | O2C.Order.Invoice/1.0 (JSON) | Invoice generation & revenue recognition |
Service Relations and Message Routing
The O2C process uses the Repository Binding context to define service relations between Services and manage message routing:
- ExternalServiceRelations: Define connections between Services in different Systems (Receive events)
- InternalServiceRelations: Define connections within the same System (Send events)
- BPM Metadata: Only the business event of each step includes Business Process Model (BPM) metadata for topology visualization; the forwarding event (
O2C.Forwarding/1.0) has none
From the Landscape to C4 Diagrams
New 7.12 Add C4 Diagrams in the toolbar opens Generate Architecture Diagrams (Generate from Integration Landscape), which draws C4 Diagrams from this landscape. Pick the Diagram Set with the shared Diagram Set picker: the Selected and All tabs, where All pages 10 sets at a time with Filter the result, and the Create new set toggle. Then pick the Diagram Types and click Generate:
| Diagram Type | Default | What it makes from this landscape |
|---|---|---|
| System Landscape | ✅ On | One L0 with the four Systems; one connector per System pair |
| Context | ✅ On | One L1 per System, with the Systems it exchanges messages with as neighbours; no Persons |
| Container | ✅ On | One L2 per System row of the table above, with the neighbouring Systems outside |
| Component | ❌ Off | One L3 per Service: 14 for the O2C, with each Service's Endpoints inside |
| Dynamic | ✅ On | One Dynamic of the Integration, its Services in step order |
The result counts what was Created, Updated, and Kept. Kept is an Active diagram of the same type, scope, and subject that the generator didn't make, such as an imported one: the generator leaves it as it is and makes no Draft beside it. Navigation between the diagrams is inferred when they open, so there are no links to create.
Three rules tie the C4 picture to the tables on this page:
- The cross-System service relations are the L0 connectors (one per System pair) and the
System_Extneighbours, with their Flows, on each L1 and L2. - Each generated Flow carries its sender's Message Types, from the sending Service's Transport Contracts. A forwarder's Flow therefore carries
O2C.Forwarding/1.0, such as Portal → ERP on the L0, L1, and L2. A pair related both ways gets Flows per direction. - The Domains are the four Domain boundaries around the Systems on the taught System Landscape (O2C C4 Diagrams).
Generating needs Create on C4 Diagram Sets, plus Create and Modify on Systems, Services, Integrations, and Domains (Permission Set for C4 Diagram Sets). Build the Order-to-Cash C4 set runs it after importing the taught examples: it adds 19 diagrams and keeps the imported 3.
Correlation and Traceability
The demo correlates all messages throughout the 7-step O2C process with a consistent Correlation ID, stored in ApplicationInterchangeId (see Search Fields for how to extract and search business identifiers):
- Format:
{PREFIX}-{YYYYMMDD}-{HHMM}-{SEQUENCE} - Example:
PIC-20251024-0930-0001 - Components:
{PREFIX}: Customer code (e.g.,PIC){YYYYMMDD}: Date the script runs (e.g.,20251024){HHMM}: Time the script generates the order (e.g.,0930for 09:30){SEQUENCE}: Order sequence number, starting at 0001
Context Properties in Every Step
The Context Options of every Log Event carry:
FileName: Order- and milestone-specific file nameOrderNumber: Order ID (e.g.,ORD-10001)CustomerId,CustomerName,OrderAmount: Customer and order data, which follow each order's customer and totalExtendedProperties/1.0#RepositoryBinding: The Repository Binding with the System, Service, Domain, and step
Key Characteristics
- Message Diversity: JSON (Portal, ERP-Finance), XML (ERP, WMS), CSV (Portal confirmations), PSV (WMS delivery)
- 7 Steps: Span 4 Systems and 4 Domains, with 14 events per complete order (2 per step)
- ~90% Progression: Orders advance to the next step with 90% probability
- ~1,070 Events: From 100 orders across all 7 steps
- Correlation: All messages are linked by the Correlation ID format
{PREFIX}-{YYYYMMDD}-{HHMM}-{SEQUENCE}
Next Steps
- Order-to-Cash Demo Overview – 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
- O2C C4 Diagrams – The same landscape as L0, L1, L2, L3, Dynamic, and Deployment C4 diagrams
- Build the Order-to-Cash C4 set – Import the taught diagrams and generate the rest
Related Topics
- O2C Demo: Process Steps, Systems, and Services – The seven steps and the 14 paired Services
- 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 run each process step
- Domains – Organizational swimlanes for multi-domain coordination
- Generate Demo Data Script – PowerShell script that creates 100 realistic O2C orders
- Message Types – Message formats for each step (JSON, XML, CSV, PSV)