SAP Modernization Shifts Responsibility Beyond Go-Live

RISE with SAP changes the way customers think about their SAP environment.

Many enter the transition expecting the cloud model to simplify who owns the day-to-day work. What they often emerge with instead is a different division of responsibility — one that can be less obvious until the new environment is already running.

“The most expensive misconception is that RISE means someone else runs your SAP,” said Mario de Felipe, VP of SAP Data and AI at Apiphani. “RISE moves infrastructure and a defined slice of Basis; it does not move accountability for application behavior, integration health, custom code, or your data.”

Customers often discover that gap only after go-live, de Felipe said, usually when an incident forces the question of who is responsible. “It’s a bad time to discover it.”

Apiphani manages the work that remains with customers through a common operating model, combining SAP engineering with Luumen, its observability and automation platform, and Deep Automation for repeatable operational tasks.

De Felipe is extending that model into SAP data and AI.

SAP Modernization Extends Beyond Go-Live

Going live with SAP S/4HANA or RISE with SAP marks the beginning of a different operating model. The work shifts from completing a transformation to continuously governing the environment that results.

That ongoing work becomes more important as companies adopt clean-core principles, expand SAP Business Technology Platform (BTP), and connect SAP data with other platforms. De Felipe argues that these are not activities to complete during implementation and revisit later. “Clean core, BTP governance, and extraction hygiene are run-state disciplines,” he said. “If nobody owns them continuously, you re-accumulate technical debt inside the new system faster than you removed it from the old one.”

The operating model also changes how SAP customers should think about support. Responsibility may now span SAP, cloud providers, internal teams, and partners. Many respond to that complexity by adding headcount, but de Felipe says service quality does not scale with staffing alone. “It scales with automation and with senior engineers who don’t need three handoffs to resolve something.”

AI Needs Business Context From SAP Data

Once companies begin connecting S/4HANA with analytics platforms, SAP Business Data Cloud (BDC) or AI, they need to manage how SAP data moves beyond the core system while preserving enough business context for that data to remain useful.

De Felipe sees SAP’s current platform strategy as reinforcing that requirement. “SAP has now made that argument structural — at Sapphire it folded BTP, BDC, and its AI foundation into the SAP Business AI Platform. But the platform can only expose semantics customers have actually built; no platform layer invents governance you never did.”

The problem becomes particularly clear when customers have invested in SAP BDC or Datasphere, but the semantic work needed to make that data usable has not followed.

“The entitlement is bought, the semantic work never started,” he said. Other organizations rely on ad hoc SAP data extraction, leaving platforms such as Databricks, Snowflake, Microsoft Fabric or Palantir with data that lacks consistent governance and lineage.

AI raises the stakes because agents need more than access to SAP data; they need the business meaning behind it. De Felipe sees some agent projects stalling “not because the model is weak, but because nothing in the landscape carries business meaning the agent can read.” Semantic modeling and governance then become prerequisites for AI.

Apiphani Connects Automation, Observability, Governance, and SAP Expertise

Warning signs that the SAP operating model is under strain can appear across the estate.

Users may notice performance problems before monitoring tools do, ticket volumes may outgrow internal Basis capacity, or an upcoming upgrade may exceed the team’s available capacity. Elsewhere, BTP can expand without clear governance, cloud costs can rise, and BDC or Datasphere investments can fall short of intended AI use cases.

The common problem is a loss of visibility and control across the SAP environment. “The moment you can no longer tell whether your SAP environment is healthy, compliant, or ready for what you want to build on top of it, that’s the conversation,” de Felipe said.

Apiphani calls this approach its Managed Intelligence Provider (MIP) model, combining automation with senior SAP expertise rather than scaling support primarily through headcount. Deep Automation handles repeatable work through preconfigured and customer-specific runbooks, while Luumen gives engineers a SaaS workbench for identifying issues and responding across the environment. Aegis adds security and governance, and Apiphani’s SAP practice provides the engineering expertise behind those capabilities.

“Think of it as four layers around the same estate,” de Felipe said.

The software and services reinforce each other. Production incidents, runbooks and remediation work can feed back into Luumen, helping the platform handle similar work better over time. “The platform is what lets small senior teams operate at enterprise scale,” de Felipe said. “The services are what make the platform smart.”

Apiphani’s strongest fit is therefore defined less by the size of an SAP estate than by the consequences when that estate becomes difficult to operate or govern. In regulated industries, manufacturing, utilities and other 24×7 environments, gaps in visibility, technical capacity or data readiness can quickly become business constraints.

What This Means for SAPinsiders

• Modernization requires continuous ownership. RISE and S/4HANA can simplify parts of SAP operations, but they also create new boundaries that need active management. Clear ownership after go-live helps protect the value of the modernization investment.
• Automation can make SAP expertise more effective. Apiphani uses automation to absorb repeatable operational work, giving senior engineers more time to address complex SAP issues. That can help customers expand support capacity without relying only on additional headcount.
• Data readiness extends the modernization business case. A stable SAP environment becomes more valuable when its data can support analytics and AI with consistent business context. Connecting operations, governance and data readiness can help customers carry modernization benefits into their next investments.