Conjola connects several modules into one continuous path: from your SAP extracts, through a feature map with real usage and AI-analyzed custom developments, to functional specs that decisions can rest on. No module stands alone — they build on each other.
Structures business areas, capabilities, features and feature details into a living map of your application landscape.
Four levels from domain to feature detail, standard and custom told apart, linked to the transactions behind them — a shared language between business, IT and consulting.
Links usage and org data to features and reveals what is used where, and how intensively.
Configurable metrics per company code and transaction usage from ST03N per system — shows what is used intensively, rarely or not at all. A basis for scoping, decommissioning and licensing decisions.
Analyzes your Z-programs with AI, groups them by topic and maps them to your business themes.
An unmanageable list becomes a topical map: where developments overlap functionally, what role an object plays in its bundle, what changed since the last import.
Functional specs and system documentation right next to the data they are about — with an AI assistant doing the groundwork.
Versioned pages with templates, linked to features, processes and custom developments. The assistant proposes changes — you accept or discard them.
Chat in plain language with your feature map, custom developments, data model and knowledge base — answers from your real SAP data.
Ask your system without transaction codes or table knowledge. Aurola, the AI assistant inside Conjola, pulls the links between code, features, data model and documentation — answers with context.
Opens feature map, custom developments, data model and knowledge base to Claude Code and other MCP-capable coding agents — read-only.
The coding agent queries what it needs instead of assembling context. Token fixed to tenant and landscape, read-only, valid for at most 90 days, enabled by the tenant — custom-code source as its own switch.
Reconstructs Order-to-Cash from your SAP document chains — with variants, frequencies, cycle times and a process model per subprocess.
Each sales order becomes a case with its follow-on documents, identical step sequences become a variant. Pivot and filter by SAP characteristics such as company code, sales organization, order type or origin — measured rather than modelled, with no parameters.
Measures which SAP Public Cloud scope items you really run and takes every point of your additional need to a reasoned decision.
One probe per scope item measures relevance per company code and year. Whatever hangs off the features beyond that gets an approach in the workshop — from standard to side-by-side on SAP BTP — and a decision with a name and a reason.
Checks vendors and customers for gaps and duplicates with standard checks — every finding with its reason and affected view.
Duplicates via email, phone and tax numbers as well as similar names and addresses, within the same country. What is mandatory is up to you, per account group. In development: checking several SAP systems together ahead of a migration.
The extracts from your system — development objects, usage, data model, org structure — come in by browser upload. No system access by Conjola.
Usage and org data attach to business areas, capabilities and features — revealing what is used where, and how intensively.
The AI works out the purpose and topic of every custom development and maps it onto the Feature Map — backed by anchors in the code where they exist.
Functional specs are written next to the data, with the assistant working on the same basis — and become the foundation for decisions.
Three things run through every module:
A standardized import for development objects, usage, data model and org structures — the shared data foundation of every analysis. Once the extracts are in, results are ready on the next business day.
With every new extract the technical elements carry forward — features, usage and custom code stay current. The business context you enter once stays anchored to them.
Multi-tenant with strict data isolation, role-based, OIDC sign-in with mandatory two-factor authentication — ready for consulting across multiple clients.
We use AI where it genuinely earns its place: understanding custom developments and clustering them by topic — and the AI assistant that answers your questions from the knowledge base and makes suggestions while you write. Feature and transaction usage, org structure and data model, by contrast, come deterministically from your extracts — traceable, not guessed by a model. That is exactly what makes Conjola the reliable, current knowledge base your own AI agents need to work meaningfully on SAP.
In a short demo we'll show you how Conjola turns your system data into a basis for decisions.
Book a demo