ERP Integration

Stream

● Idle

Events / sec

0.0

Total Events

Connected ERPs

Cross-ERP Customers

Throughput

SAP S/4HANA Precision Mfg ● waiting

Connecting to SAP S/4HANA feed...

NetSuite Distribution ● waiting

Connecting to NetSuite feed...

Workday Eng. Services ● waiting

Connecting to Workday feed...

Oracle EBS Aerospace ● waiting

Connecting to Oracle EBS feed...

1 / 5 Loading... Ready

CxUs Extracted

Avg Confidence

Documents Ingested

0 / 4

Context Retrieval

"What do I need to know to sync a $72K PO from SAP to NetSuite?"

PYRANA™ Cortex

CxU

Source Doc

ERP (database)

Front End Customer / rep facing intake flow

Multi Source Context

Sales orders can originate from many different sources. The process gets messy fast — it depends on where the order came in from, who the customer is, and what they're ordering.

Pyrana uses context units (CxUs) to capture the knowledge specific to each order — including which system it should be booked in.

This flow is a mock-up showing how different CxUs activate to control different scenarios. The point is to eliminate a lot of the manual grunt work needed for clean order entry.

A solution like this lets many individual ordering agents operate under a consistent and evolving knowledge base.

Back End Pyrana Cortex — context engine

PYRANA™ Cortex idle

CxU Source ERP Retrieved

Retrieved CxUs 0

CxUs activated by the agent will appear here as the scenario runs.

Front End Order Processing — PO #4500012847

Same PO, every-system view

This is the canonical $72K Meridian PO that arrived in the Order Intake demo (EDI scenario). Now we follow it through the full processing chain.

The Order Intake Agent picks it up. The Validation Agent checks policy, credit, and completeness. The Approval Router pauses for two VPs. The Sync Agent maps fields across SAP → NetSuite. The Learning Agent reflects on the cycle and proposes CxU changes for next time.

Agent steps appear on the left; the order, approval, sync, and reflection artifacts appear on the right. The Pyrana Cortex panel shows which CxUs activate at each step.

Back End Pyrana Cortex — context engine

PYRANA™ Cortex idle

CxU Source ERP Retrieved

Retrieved CxUs 0

CxUs activated by the agents will appear here as the scenario runs.

In-flight0

Auto-processing0

Awaiting external0

Needs your action0

Your job: supervise the flow. Click a card for the full timeline and to act.

Auto-Processing 0

Awaiting External 0

Needs Your Input 0

Awaiting Approval 0

Total Revenue$0

Orders0

Avg Order$0

ERPs0

Customers0

Revenue by ERP System (Monthly)

Revenue by Line of Business

Top Customers — Cross-ERP View

Unified Sales Orders

Source	LOB	SO / PO #	Customer	Category	Amount	Status

Agent LLM Calls

Every LLM call made during agent execution — composed prompt, injected CxUs, model parameters, and raw response.

LLM Calls 0

Run the order processing flow to capture LLM calls.

Select an LLM call from the list to view its composed prompt, injected CxUs, and response.

Pyrana ERP Integration Demo

Agentic middleware for multi-ERP landscapes — a 22-minute guided experience

What You're Looking At

AcmeMfg is a Fortune 500 manufacturer that has grown through acquisition, inheriting four different ERP systems across its lines of business. This demo shows how Pyrana's agentic middleware creates a unified knowledge layer across all four ERPs — enabling cross-system order processing, policy enforcement, and real-time synchronization without ripping and replacing any existing system.

SAP S/4HANA

Precision Manufacturing — hydraulic actuators, sensor assemblies, control systems (original business)

NetSuite

Industrial Distribution — components resale, spare parts kits, distribution services (acquired 2022)

Workday

Engineering Services — consulting, maintenance contracts, field services (acquired 2023)

Oracle EBS

Aerospace Division — aerospace actuators, avionics components, MRO services (acquired 2024)

How Multi-Agent Processing Works

On the Order Processing tab, six specialized agents collaborate to move a purchase order from SAP into NetSuite. Each agent has a narrow responsibility but shares a common context layer — the CxU knowledge graph.

Order Intake Agent picks up the PO and retrieves every CxU relevant to the transaction — field mappings, approval thresholds, GL rules. These CxUs are injected directly into the agent's prompt as structured context.

Validation Agent receives the PO payload plus the retrieved CxUs and evaluates policy thresholds. It doesn't re-fetch context — it reasons over what Intake already gathered, citing specific CxU IDs in its decisions.

Approval Router reads the Validation output, finds the $50K dual-approval CxU, and creates a human-in-the-loop task routed to the correct VPs based on the approval matrix CxU.

Sync Agent executes the cross-system write. Each field mapping (SAP VBAK-BSTNK → NetSuite tranid, GL accounts, etc.) is driven by a specific CxU — no hardcoded transformations.

Learning Agent reflects on the completed transaction, detects patterns (e.g., customer nearing credit limit), and proposes new CxUs back into the knowledge graph.

The key insight: not every agent needs every bit of context, but what they do use is derived from a shared knowledge base through CxUs — every decision is traceable, every transformation is auditable, and adding a new ERP means adding new CxUs, not rewriting agent code.

Key Insights to Experience

Context Units (CxUs) — Every policy rule, field mapping, and business constraint is captured as a traceable CxU with provenance back to its source document. Watch them get extracted in real-time on the Context Ingestion tab.

Cross-ERP Customer View — On the Sales Orders tab, notice how customers like Meridian Industrial appear across multiple ERPs. Pyrana connects these fragmented identities into a holistic view.

Agent Reasoning with Citations — On Order Processing, watch 6 specialized agents process a $72K PO. Every decision cites the specific CxU that authorized it — full auditability for SOX compliance.

Dual VP Approval — The $72K PO exceeds the $50K threshold from Corporate Policy CP-FIN-042 §3.2. The system automatically routes for dual VP approval with human-in-the-loop.

Agent Self-Reflection — After processing, the Learning Agent sees the customer is at 96% of their credit limit. Based on their historical order size ($68K avg), it predicts the next purchase would breach the limit and proactively flags SAP for a credit extension — preventing a block before it happens.

Oracle Onboarding in Minutes — On Context Ingestion, use "Onboard Oracle EBS" to ingest 3 new documents. The system extracts ~27 CxUs and immediately integrates Oracle data — no months-long integration project.

Tab Guide

Dashboard

Live API monitor showing real-time data flowing across all four ERPs with streaming SSE feeds

Context Ingestion

Upload and ingest source documents — watch CxU extraction happen in real-time with pill links back to source text

PYRANA™ Cortex

3D visualization of the knowledge network — CxU clusters orbiting source documents, connected to ERPs

Order Processing

End-to-end agent orchestration: intake → validation → approval → cross-system sync → self-reflection

Sales Orders

Unified sales view across all ERPs with customer flip-tiles showing cross-ERP purchasing patterns

Agent Output

Raw agent execution traces and structured output for technical deep-dives

There is a lot to see in this demo

PYRANA™ Cortex

Multi Source Context

Same PO, every-system view

Revenue by ERP System (Monthly)

Revenue by Line of Business

Unified Sales Orders

Agent LLM Calls

Settings

Pyrana ERP Integration Demo

What You're Looking At

How Multi-Agent Processing Works

Key Insights to Experience

Tab Guide