Unfamiliar inherited systems
You take over SAP systems that nobody on your team built. How they are actually used and which custom developments they hold is unclear at first.
Merger, post-merger integration or carve-out due diligence: you inherit one or more unfamiliar SAP systems and need to gauge overlap, redundancy and integration effort. Conjola prepares each system individually from its own extracts — feature map, usage, custom developments — and puts the systems side by side, as a data-based basis for your assessment.
You take over SAP systems that nobody on your team built. How they are actually used and which custom developments they hold is unclear at first.
Each system brings its own, often outdated documentation — in different depth and structure. A clean comparison is barely possible this way.
Where do the systems overlap, where do things run twice, where do they differ? Without a data basis, integration and harmonization effort stay a guess.
Within one tenant, each system gets its own landscape. The systems stay separate and are each examined on their own.
Feature map, transaction usage and AI-assisted custom-code analysis run per system on its own extracts — same structure, same depth.
You put the landscapes' feature maps, usage and custom developments next to each other: where do both systems use the same functions, where does one have its own developments, where do they differ?
Each inherited system comes into the same tenant as its own landscape — separate from the others, yet set up the same way.
Extracts are created and uploaded per system. Conjola turns them into a feature map, a usage picture and an analyzed custom-code map.
The landscapes are placed side by side. Common ground and differences in functional scope, usage and custom developments become visible.
On this factual basis you gauge integration and harmonization effort — and back your decisions with data instead of assumptions.
In a short demo we'll show you how Conjola turns your system data into a basis for decisions.
Book a demo