Reading your process logs...
For SAP · Oracle · ERP Transformations

Your Process Mining Shows What Happened. Patchify Explains Why.

Celonis and Signavio can map your process. They cannot explain why condition ZPR5 was overridden, why Region LATAM bypasses approval Step 12, or why a decade of tribal pricing knowledge is missing from your SOPs. Patchify can.

$4.2M+
Avg. margin leakage
identified in 90 days
6×
Faster process
documentation
89%
Previously undocumented
exceptions surfaced
Scroll
The Problem

The Blind Spot at the Heart of
Every ERP Transformation

✓ What Process Mining Sees
✓Sequence of process steps and activity order
✓Process variants and execution paths
✓Bottlenecks and throughput times
✓Rework loops and repeat cycles
✓Event frequency and case volume
✓User IDs and timestamps
Blind Spot
✗ What It Cannot See
✗Business intent and pricing logic
✗Policy interpretation and SOP compliance
✗Human reasoning behind exceptions
✗Tribal knowledge and undocumented rules
✗Cross-system dependencies (SAP ↔ Oracle ↔ Excel)
✗Unstructured inputs — emails, PDFs, chat approvals
✗BAdI logic, user exits, and Z-table rules
✗Missing documentation and approval bypasses
Celonis can tell you: "Step 14 → Step 15 → Step 16". It cannot answer: "Why did the pricing engine override the discount? Why does LATAM always bypass Step 12? Why did the approver reject this case?"

Process mining shows the movie. Patchify explains the script.
Why This Happens

SAP Pricing Logic Lives in
20+ Different Places.
Process Mining Reads None of Them.

Pricing logic in SAP and Oracle doesn't live in one place. It's scattered across database tables, custom code, manual overrides, email chains, and the institutional memory of analysts who've been there since 2009. No single tool has ever read all of it — until now.

KONV / KONP Tables VK11 Condition Records Z-Tables Access Sequences BAdIs User Exits Pricing Procedures Custom Routines Excel Overrides Email Approvals Manual Adjustments Undocumented SOPs Contract Clauses Approval Workflows Tribal Knowledge Change History
✗
Process mining reads only the event log. Everything above — 16 distinct sources of pricing logic — is completely invisible to it. No exception in Celonis or Signavio can tell you why it happened.
✓
Patchify reads all of it. Every table, every email, every BAdI, every undocumented rule. Then it tells you exactly why your process behaved the way it did.
The Difference

From Surface Counts to
Root Cause Intelligence

Before Patchify
Celonis / Signavio / Process Mining
Your process mining dashboard reports that 1,200 pricing exceptions occurred in Q3 across the Order-to-Cash process. Variant analysis shows 23 distinct paths. Rework is elevated in steps 8 through 11.
"There were 1,200 pricing exceptions."
No root cause. No fix. No context.
After Patchify
Patchify AI Reasoning Layer
Patchify cross-references the event log with SOP 4.2, the LATAM pricing contracts, condition table KONP, and six months of email approval threads — then explains exactly what happened and why.
"82% of exceptions occur because SOP 4.2 contradicts the LATAM pricing table. Condition ZPR5 is overridden because the access sequence is misaligned with the discount matrix. Approval delays are caused by ambiguous language in contract clause 4.2(b). Three fixes will resolve 76% of exceptions."
Architecture

Three Layers. One
Intelligence Engine.

Layer 1 — Data Ingestion
01 / 03
Structured Crawlers
  • SAP connector (ODP, CDS, RFC, BAPI)
  • Oracle ERP connector
  • Pricing tables — KONV, KONP, KONH
  • Condition records — VK11, VK12
  • Event logs and change history
  • Approval workflow logs
Unstructured Crawlers
  • Email ingestion — Outlook / Gmail APIs
  • SharePoint / OneDrive / Google Drive
  • PDF and Excel file ingestion
  • Jira and ServiceNow tickets
  • Slack and Teams messages
  • Contract and SOP repositories
Code & Config Crawlers
  • ABAP code reader
  • BAdI and user exit extractor
  • Pricing procedure parser
  • Access sequence reader
  • Oracle PL/SQL logic reader
  • Z-table definition crawler
Layer 2 — AI Reasoning
02 / 03
Rule Extraction
  • Extracts rules from SOPs
  • Reads contract obligations
  • Parses pricing sheets
  • Interprets approval policies
  • Reads ABAP/PL/SQL logic
Behavior Interpretation
  • Compares what should happen
  • vs. what actually happened
  • Identifies SOP vs. log gaps
  • Maps variants to root causes
Exception Explanation
  • Explains why exception occurred
  • Whether it was justified
  • Whether it was undocumented
  • Whether it signals a broken rule
Tribal Knowledge Mapper
  • Identifies undocumented patterns
  • Links analyst behavior to rules
  • Surfaces hidden pricing logic
  • Flags single-analyst knowledge
Layer 3 — Patch Recommendation Engine
03 / 03
Root Cause & Impact
  • Root cause per exception cluster
  • Margin impact scoring
  • Compliance risk rating
  • Prioritised fix queue
Recommended Fix
  • Updated pricing rule text
  • Updated approval logic
  • Suggested automation points
  • Configuration change guidance
SOP Auto-Writer
  • Auto-generates updated SOPs
  • Aligned to actual process behavior
  • Documents discovered tribal rules
  • Version-controlled and auditable
Product — MVP

Four Tools. One Mission:
Explain Your Processes.

01
Why Map
Visual Intelligence
A living knowledge graph that connects your process variants to their actual causes — pricing rules, SOP gaps, tribal knowledge, broken approval paths, and cross-system dependencies. See everything your process mining tool cannot.
You See
Pricing variant PV-082 traced to condition ZPR5 override → caused by missing clause in SOP 4.2 → impacting $840K in LATAM contracts
02
Explain This Case
Transaction Intelligence
Click any transaction in your process mining tool or SAP and ask Patchify why it behaved the way it did. Receive a natural language explanation that references the actual source — the contract clause, the email approval, the Z-table, the BAdI logic.
You Ask
"Why was a 23% discount applied on SO-2024-91847 instead of the standard 12%?"
Patchify Answers
Exception justified. Contract clause 4.2(b) permits up to 25% for Tier 2 LATAM >$500K. Rule not in SOP 4.2.
03
Patch Suggestions
Prescriptive Fixes
For every root cause identified, Patchify generates a prioritised fix — ranked by margin impact, compliance risk, and implementation effort. Not a dashboard. A to-do list for your ERP transformation team with business case already written.
Patch #1 — Priority: Critical
Formalise LATAM Tier 2 discount rule as exception ZE_LATAM_T2 in condition table. Resolves 82% of exceptions. Est. margin recovery: $3.4M/year.
04
SOP Auto-Writer
Knowledge Preservation
Patchify watches what your team actually does, compares it to what your SOPs say, and automatically drafts updated process documentation. Tribal knowledge that would walk out the door when your senior analyst retires — captured and formalised.
Auto-Generated SOP Update
SOP 4.2 §3.1 updated: "For Tier 2 LATAM customers with annual spend >$500K, pricing analyst may apply discount up to 25% under contract clause 4.2(b). Override must be logged in KONP with reason code ZE_LATAM_T2."
In Practice

What Patchify Looks Like
in the Real World

Patchify AI — Explain This Case
Transaction
SO-2024-91847 — Sales Order, LATAM region, customer C-4821 (Tier 2)
Pricing exception flagged: 23% discount applied vs. standard 12% list price.
Process mining shows: variant PV-082 — bypassed standard approval Step 9.
Patchify Explains
Exception is documented and compliant. Condition ZPR5 was overridden by pricing analyst J. Martinez per contract clause 4.2(b) — applicable to Tier 2 LATAM customers with annual spend exceeding $500K. Customer C-4821 qualifies ($640K YTD).

Step 9 approval bypass is permitted under the same clause. However, this rule exists only in an email thread from March 2023 and is absent from SOP 4.2. If J. Martinez leaves, this logic is lost.

Patchify recommends: Formalise as pricing exception rule ZE_LATAM_T2 in condition table KONP. Update SOP 4.2 §3.1. Estimated similar cases at risk: 847 per quarter.
Create SOP Update →
Formalise Pricing Rule →
Assess Full Margin Impact →
Find Similar Cases →
Strategy

Wedge. Expand. Platform.
A Category-Creating Roadmap.

Phase 1 — Now
Pricing Exception Intelligence
SAP & Oracle SD / OTC
  • SAP pricing table ingestion (KONV, KONP, KONH)
  • SOP and contract PDF crawling
  • Exception root cause explanation
  • Why Map and Explain This Case
  • Patch Suggestions with margin impact
  • SOP Auto-Writer (MVP)
Highest pain. Fastest ROI.
Phase 2 — Next
Order-to-Cash & Procure-to-Pay
Full process cycle coverage
  • Approval logic and credit check reasoning
  • Master data exception explanation
  • Invoice dispute root cause
  • Procurement rule interpretation
  • Email and Teams ingestion
  • Multi-system dependency mapping
Expand the footprint.
Phase 3 — Platform
Enterprise Reasoning Layer
Sits above any process mining tool
  • Works with Celonis, Signavio, Apromore, UiPath
  • RBAC, audit logs, SOC 2 compliance
  • Multi-tenant enterprise architecture
  • API-first for custom integrations
  • Continuous SOP sync and governance
  • AI-driven process governance layer
$100M+ category.
Integrations

Works With Your Existing
Process Mining Stack

Patchify is not a replacement for your process mining investment. It's the reasoning layer that sits above it — giving your existing tools the ability to explain the "why" behind what they visualise.

Celonis
Process Mining
Connect Patchify to your Celonis event logs. Patchify explains the variants Celonis can't.
SAP Signavio
Process Intelligence
Native SAP environment. Patchify reads SAP tables Signavio cannot access.
Apromore
Process Mining
Plug Patchify into Apromore's process log exports for full root cause coverage.
SAP S/4HANA
ERP Source System
Direct connector via ODP, CDS views, RFC, and BAPI for deep table access.
Oracle ERP Cloud
ERP Source System
REST API and PL/SQL logic reader for Oracle pricing and approval configurations.
UiPath Process Mining
Process Mining
Integrate Patchify into UiPath workflows to add reasoning to automation triggers.
Get Started

See Patchify on Your
Own SAP Data

We'll show you why your pricing exceptions exist — in your environment, with your data, in 30 minutes.

We connect to your process mining export or SAP event log
We run Patchify's exception explanation engine on a real sample
You see the root causes, tribal knowledge gaps, and patch recommendations
We quantify the margin leakage and compliance risk in your process

hello@patchify.ai · patchify.ai