CASE STUDY

From Legacy ECC to Fiori-Ready

How Aditheos modernised mapERP’s SAP product platform — converting 4 legacy ECC applications to a fully Fiori-based setup with launchpad, roles architecture, and S/4HANA-aligned backend solutions.

Client  mapERP   |   Industry  SAP Solutions & GIS Field Services   |   Duration  3 Months   |   Stack  SAP Fiori · Launchpad · ABAP · Roles & Auth

BACKGROUND

A strategic decision to modernise ahead of the curve

mapERP is a specialist SAP solutions company with deep expertise in geo-enabled field service management, enterprise mobility, and SAP EAM. Their product suite — including Smart Execute, Smart Planning Board, and Smart Crew Management — is used by utilities, infrastructure, and public sector organisations to manage crews, work orders, and field operations.

mapERP’s product applications were built on SAP ECC — a solid and proven foundation. As SAP’s roadmap moved decisively toward S/4HANA and client environments began shifting toward browser-based, mobile-first solutions, mapERP made a proactive decision to modernise their platform ahead of the transition — rather than wait for the migration to force the change.

CLIENT

mapERP — SAP Solutions & GIS Field Services

ENGAGEMENT

Direct client engagement

DURATION

3 Months

TECHNOLOGY

SAP Fiori · SAP Launchpad · ABAP · Roles & Authorisations · SAP ECC

THE CHALLENGE

Three forces pushing modernisation

With SAP’s roadmap clear and client expectations evolving, mapERP chose to modernise their platform proactively.

Legacy UI Barrier

mapERP’s product applications were SAPGUI-based — functional and reliable, but not optimised for the browser-based, mobile-first environments that clients were increasingly moving towards.

No Unified Navigation

Without a launchpad, users had no single entry point across the product suite — onboarding new users required SAP transaction code knowledge and significant training overhead.

S/4HANA Technical Debt

With SAP’s ECC roadmap clearly defined, mapERP chose to align their applications to the Fiori design paradigm now — ensuring a smooth, cost-effective path to S/4HANA rather than a disruptive rework during migration.
WHAT WE DELIVERED

A complete Fiori transformation, end to end

Fiori Application Conversion

All 4 legacy ECC applications were rebuilt as SAP Fiori apps — delivering a responsive, browser-based experience accessible on desktop, tablet, and mobile across the full mapERP product suite.

SAP Fiori Launchpad

A unified Fiori Launchpad was designed and configured — giving users a single, tile-based entry point across all mapERP products, replacing the fragmented SAPGUI transaction-based navigation.

Roles & Authorisation Architecture

A clean roles framework was designed from scratch — mapping access to job functions (field crew, planner, supervisor, contact centre agent) and replacing ad-hoc legacy authorisation assignments with a defensible, auditable structure.

ABAP & Backend Solutions

Backend enhancements were delivered to support the Fiori layer — ensuring data consistency, performance, and full compatibility with the target S/4HANA architecture for mapERP’s future migration.
THE OUTCOME

Modern, mobile-ready and S/4HANA aligned

mapERP’s product suite now matches the standard their clients expect — and is ready for what SAP’s roadmap demands next.

legacy ECC applications converted to SAP Fiori

%

reduction in user onboarding time with Fiori launchpad

months to deliver the full transformation

%

S/4HANA ready — zero rework required on migration

  • ✓  All 4 products accessible on desktop, tablet and mobile for the first time
  • ✓  Unified launchpad replaced fragmented SAPGUI transaction navigation
  • ✓  Clean roles architecture removed overlapping legacy permissions
  • ✓  Applications S/4HANA-compliant — no rework needed on future migration
TECHNOLOGIES USED

SAP FioriSAP LaunchpadABAPOData ServicesSAP Roles & AuthorisationsSAP ECC

Ready to modernise your SAP platform?

Tell us what you need. We’ll show you how SAP BTP can solve it.

Book a Discovery Call