Business Area
The functional domain — e.g. Finance, Procurement, Sales. The top-level frame for your landscape.
Feature Map
Your SAP landscape as a living map
The Feature Map structures your application landscape into three levels: business areas, capabilities and features. Real usage attaches directly to this structure — turning a static catalog into a map that keeps growing with you.
The hierarchy 01 02 03
Three levels, from broad domain to concrete function.
Capability
A business capability within the domain — e.g. Accounts Payable, Inventory Management.
Feature
The concrete function — e.g. Invoice Verification (MIRO), as it actually appears in the documents.
Example
Finance Accounts Payable Invoice Verification
What you see with it
The map connects structure with real activity.
Usage on the structure
Every feature carries its real usage: document volume, involved org units, last activity. Dead branches stand out instantly.
Coverage per domain
Which capabilities are heavily used, which barely at all? The map shows focus areas and blind spots at a glance.
Bridge to the app
Features point to the underlying SAP transactions and tables — from the map straight into the document.
Standard vs. custom
The map distinguishes what SAP ships from what you built yourself.
Standard functionality
SAP delivered functions you use — the basis for any cloud fit, because they map onto scope items.
Custom functionality
Custom developments, Z-transactions and enhancements. This is exactly where the effort of a clean-core path is decided.
Ready to understand your SAP landscape?
In a short demo we'll show you how Conjola turns your document data into a basis for decisions.
Book a demo