- 5 minutes to read

Order-to-Cash (O2C) Process Demo - Complete Package

This demo showcases an Order-to-Cash (O2C) business process (BPM) using Nodinite Log Events and the Log API. The scenario follows a complete order lifecycle from the initial customer order through the final invoice, and shows how to log business transactions across multiple Domains, Systems, and Services in multiple message formats (JSON, XML, flat files).

The package features 100 order interchanges that follow a probabilistic happy-path scenario and generate approximately 1,070 Log Events for analysis and visualization in Nodinite. 100 is the script's default; its -OrderCount parameter sets the number, so your environment may hold more or fewer orders.

Order-to-Cash demo tour from the BPM Designer to a grouped Log View and one order rendered as a business document, animated walkthrough (7.12)
Animated walkthrough: the Order-to-Cash BPM in the Designer, then a grouped Log View where a search on O2C - Order ID = ORD-10005 finds the order, and View message formatted as 'O2C - View Order' renders it as an Order Report. Every run of the demo script logs the order again with its own interchange id, so the search returns one group per run, newest first.

BPM Viewer opened with Show BPMs from the grouped Log View, one order lit from Order Received to Order Invoiced across the Sales, Planning, Logistics, and Finance domains (7.12)
One order in the BPM Viewer: the seven steps across four Domains, with the order's events on each step. See Follow one order in Nodinite.

Business Context

The Order-to-Cash process is a typical enterprise integration scenario where customer orders flow through four business Domains:

  • Sales Domain - Customer order reception and delivery confirmation
  • Planning Domain - ERP order entry and production scheduling
  • Logistics Domain - Order fulfillment and delivery
  • Finance Domain - Invoice generation and accounting

Each step generates Log Events that create an audit trail, enable real-time monitoring, and populate the Repository Model with integration landscape metadata through the Repository Binding context option.

Note

⚠️ Critical: To enable automatic landscape creation from Log Events, set the System Parameter AllowRepositoryAutomapping to true. This is the point of the demo: each Log Event carries a Repository Binding JSON structure that Nodinite uses to build and maintain your integration landscape (Systems, Services, and service relations) without manual configuration.

What You Gain

Approach Result
❌ Without Repository Binding You must create all Systems, Services, and relations manually in the Web Client
✅ With Repository Binding Nodinite builds the landscape automatically from logging

With the landscape built from logging, every order becomes something the business can follow: a row in a grouped Log View, a path through the BPM, a timeline of where it waited, and the message behind each step.

By completing this demo, you will understand:

  • ✅ JSON Log Event structure (mandatory + optional fields)
  • ✅ Multi-format message handling (JSON, XML, flat files)
  • ✅ Base64 payload encoding
  • ✅ Context Property usage
  • ✅ Correlation ID patterns
  • ✅ DateTime time zone handling
  • ✅ Log Status codes
  • ✅ HTTP request structure to the Log API
  • ✅ Repository Binding automation
  • ✅ BPM workflow visualization
  • ✅ End-to-end process tracing
  • ✅ Business metrics extraction

Understanding the O2C Demo Architecture

graph LR Script["fa:fa-terminal PowerShell demo script"] --> LogAPI["fa:fa-cloud-arrow-down Log API"] LogAPI --> LS["fa:fa-gears Logging Service"] LS --> Repo["fa:fa-sitemap Repository Model
Integration, Systems, Services"] LS --> BPM["fa:fa-diagram-project BPM
INT1337 - Order-to-Cash Flow"] LS --> LV["fa:fa-magnifying-glass Log Views
Search Fields"] Repo --> C4["fa:fa-diagram-project C4 Diagram Set
Order-to-Cash Demo"] BPM --> C4 style Script fill:#9E59BB style LogAPI fill:#2678BD style LS fill:#3F827B style Repo fill:#93d16d style BPM fill:#93d16d style LV fill:#93d16d style C4 fill:#E47528

The demo script (purple) posts Log Events to the Log API (blue); the Logging Service (teal) reads the Repository Binding and builds the Repository Model, the BPM, and searchable Log Events (green). See Search Fields. New 7.12 From the Repository Model and the BPM you build the C4 Diagrams set Order-to-Cash Demo (orange) in the product: import the taught examples, click C4 Dynamic on the BPM, and run Generate from Integration Landscape (Build the Order-to-Cash C4 set).

What's in This Example

Page What it holds
O2C Demo: Process Steps, Systems, and Services The seven milestones and their Message Types, the Systems, the 14 paired Services and their forwarders, and the Domain transitions
O2C Demo: Log Event Structure The fields and Context Properties of each Log Event, the Log Agent settings, the Log API call, the Correlation ID format, Log Status codes, a full example, and the Search Fields to extract
O2C Demo: Repository Binding The Repository Binding JSON, what each property means, and how the Logging Service builds the landscape and BPM from it
O2C Demo: Data Generation The sample orders, customers, and products, and how the script decides which steps each order completes
Generate O2C Demo Data Run the script: parameters, customers and products, and grouping the orders
Generate O2C Demo Data Script The PowerShell script source
O2C Demo: Follow One Order Follow one order in Nodinite through the BPM, the timeline, and the event details
Integration Landscape The Systems, Services, and service relations as a topology
BPM Expected Layout How the steps appear in the BPM matrix
O2C C4 Diagrams The six taught C4 diagrams: System Landscape (L0), Portal's Context (L1) and Container (L2), the Component (L3) of INT1337-RCV-Order-Incoming, the Dynamic, and the Deployment
Build the Order-to-Cash C4 set The full demo set of 25 C4 diagrams, built through the product with zero stored links
O2C Demo Stylesheets Stylesheets that render the messages as business documents
Steps 1, 2, 3, 4, 5, 6, 7 One page per step: the message sample (JSON, XML, CSV, or PSV), the business data, and the Context Properties

Next Steps