What isn't used at all?
Which features show no activity — no transaction calls, no data in their insights? Clear decommissioning candidates and a case for a leaner project scope.
Feature Insights links usage and org data to your Feature Map. It reveals which functions are used how heavily per company code, per system and over time — the factual basis for license, scope and decommissioning decisions.
Which features show no activity — no transaction calls, no data in their insights? Clear decommissioning candidates and a case for a leaner project scope.
Which few features does the volume concentrate on? This is where optimization pays off and migration needs extra care.
Which company codes use a feature exclusively? Crucial before someone switches off something a plant still relies on.
Three axes along which usage can be broken down.
Metrics you define yourself — table, fields, aggregation — plus transaction usage from ST03N. From workhorse to dead weight.
A matrix per company code — plants, purchasing and sales organizations feed in through the org-structure mapping. Transaction usage additionally per system: development, quality assurance, production.
Metrics grouped by year — is usage growing, stagnating or fading out?
Usage data becomes a basis for decisions.
Are you paying for functionality nobody uses? Insights sharpens your license model and project scope down to what's actually needed.
Unused features and Z-transactions without calls become evidenced — retirable with a clear view of whether any company code still depends on them.
In a short demo we'll show you how Conjola turns your system data into a basis for decisions.
Book a demo