—
Ask most people outside enterprise IT what keeps a multinational company’s finances, supply chain, and manufacturing operations running, and few would guess the answer: a decades-old piece of German enterprise software called SAP, now increasingly stitched into hybrid and private cloud environments that most employees never think about. Ask the engineers responsible for that software, though, and they’ll tell you the real work isn’t the software itself – it’s everything around it. Provisioning. Monitoring. Data harmonization. Configuration. The plumbing.
That plumbing is where Srinivas Kakarla has spent much of the past year, and it’s the subject of two research articles he published within an eight-month span. The first, released in November 2021 in the International Journal of Engineering Technology Research & Management, looked at how enterprises monitor and manage sprawling SAP landscapes that straddle on-premise data centers and Microsoft Azure. The second, published in July 2022 in the International Journal of Innovative Research in Computer and Communication Engineering, turned to a newer and thornier problem: implementing SAP Central Finance on SAP’s own RISE Private Cloud Edition.
Neither topic is likely to trend on social media. Both, however, sit at the center of decisions that large enterprises are making right now about how to modernize systems that, if they fail, can stop a company from shipping products or closing its books.
The problem with hybrid landscapes
Kakarla’s November 2021 paper, “Hybrid Cloud Landscape Monitoring for SAP Using SAP Landscape Management (LaMa): Automating VM Provisioning and Administration Across On-Premise and Azure Environments,“Â starts from a reality that many enterprises are living through but rarely discuss in public: very few companies move their entire SAP estate to the cloud in one motion. Instead, systems end up split – some virtual machines still running in a company’s own data center, others provisioned in Azure, all of it needing to be monitored and administered as though it were a single, coherent landscape.
SAP Landscape Management, or LaMa, is SAP’s own tool for handling exactly that kind of complexity, and Kakarla’s paper focuses on how to put it to work automating virtual machine provisioning and administrative tasks across both environments at once. Rather than treating on-premise and Azure infrastructure as two landscapes managed by two separate processes, the paper describes an approach where LaMa becomes the common layer – provisioning new VMs, applying administrative changes, and giving operations teams a single point of control regardless of where a given system physically lives.
The practical upshot, according to the paper, is fewer manual handoffs between infrastructure teams and fewer opportunities for configuration drift between environments that are supposed to mirror each other but often don’t. For enterprises in the middle of a multi-year cloud migration – which describes a large share of SAP’s customer base – that kind of consistency isn’t a minor convenience. It’s often the difference between a migration that stays on schedule and one that quietly accumulates technical debt with every VM provisioned outside the standard process.
Central Finance meets RISE
The next benchmark research paper takes on newer territory. SAP RISE, the company’s managed private cloud offering, has become one of the most closely watched shifts in the SAP ecosystem – a move away from customers managing their own infrastructure and toward a model where SAP itself operates the private cloud environment on the customer’s behalf. That shift changes the rules for almost every other SAP initiative running on top of it, including Central Finance.
In “Implementing SAP Central Finance on SAP RISE Private Cloud Edition: Integration Challenges, Data Harmonization Strategies, and Configuration Best Practices,“Â published in July 2022, Kakarla examines what happens when Central Finance – the tool many large enterprises use to consolidate financial postings from multiple source systems into one unified view – gets deployed on top of RISE rather than customer-managed infrastructure.
The paper walks through the integration challenges that surface in that combination: how source systems continue feeding financial data into a Central Finance instance that a customer no longer directly controls at the infrastructure level, and how differences in chart-of-accounts structures, currency handling, and posting logic across source systems get reconciled once they land in Central Finance. That reconciliation work – data harmonization, in the paper’s terms – tends to be where Central Finance projects either succeed quietly or fail loudly, and the shift to RISE adds a layer of coordination between customer and vendor that didn’t exist in earlier deployment models. The paper’s configuration recommendations are aimed squarely at that gap, giving implementation teams a set of practices for keeping the harmonization work aligned even as more of the surrounding infrastructure moves outside their direct control.
Two papers, one underlying concern
Read side by side, the two papers don’t share a subject so much as a preoccupation: what happens to enterprise SAP operations when infrastructure ownership becomes distributed – split between on-premise and Azure in one case, handed to SAP itself under RISE in the other. In both scenarios, the technical challenge is less about whether the underlying cloud or hosting model works, and more about whether the operational and financial processes built on top of it can stay coherent as control becomes more fragmented.
That is, increasingly, the actual state of enterprise SAP environments. Few companies get a clean, single-environment migration; most are managing some combination of legacy infrastructure, public cloud, and now vendor-managed private cloud, often simultaneously. Kakarla’s two papers don’t resolve that complexity so much as give architects and implementation teams concrete patterns for operating inside it – one focused on keeping infrastructure administration unified across environments, the other on keeping financial data trustworthy as infrastructure control shifts to a vendor.
It’s not the kind of work that makes headlines. But for the finance and operations teams whose systems depend on it running correctly, it’s the work that decides whether a migration project becomes a case study or a cautionary tale.
—
