- Problems We Solve
Stanislas Berteloot
-
What SAP Clean Core Actually Requires From Your Business, Not Just Your IT Team
Clean core means keeping the SAP core close to its standard, vendor-provided state, with differentiation handled through APIs and SAP BTP rather than changes to the core itself, per SAP’s own definition. Achieving that state is not merely an IT decision; while technology teams can establish the guardrails, only business leaders can distinguish between genuine…
-
Why Does Continuous Improvement Stop After an SAP Go-Live?
One of the most powerful drivers of value is a good Center of Expertise with a mandate and budget for measurable continuous improvement. Yet it is seldom seen. Go-live is a clear target and goal, and so it gets all the budget. Yet Going Live doesn’t necessarily mean Getting Value. In fact, often Go-Live is…
-
The two findings auditors cite most are two controls an SAP build suspends
Published ITGC guidance describes controls in steady state. This report covers the build period, when the implementation suspends them and the auditor still arrives. No form.
-
Why are so few ERP Transformations on time and on budget? Or worse, need to be reset?
Five outside studies on how SAP ECC and S/4HANA transformations actually finish, with every source printed and linked. No form.
-
From Gut Feel to Signal: How AI Is Changing the Way SAP Programs Are Run
AI is changing what “testing early” actually means for SAP programs. When early results are clear, validated, and stakeholder-backed, it fosters confidence and trust in the process, which is essential for project success. Early visibility only works if the early data is real. A design-phase issue is cheap to fix. The same issue found during…
-
SAP S/4HANA Global Rollout Challenges: Why the Global Template Often Breaks
The standard approach to rollout is a global template that is derived from an initial implementation. (Rather than independent of a first implementation and then piloted) A team builds the SAP system at headquarters first, then copies the template to each subsidiary and adjusts it for local tax rules, languages, and reporting requirements. That…
-
Why SAP Program Teams Stop Trusting the Documentation
SAP program directors describe the same complaint in different words: the documentation says one thing, and reality says another. So people stop reading the documentation. They ask someone else who has been around for a while, or they start exploring the systems by themselves. That behavior is rational. A document that has been wrong three…
-
How to Build or Retrofit an SAP S/4HANA Center Of Excellence
An SAP S/4HANA Center of Excellence (COE) is a permanent governance, planning, and continuous improvement function, not a temporary support desk. It is responsible for change control, release management, architecture oversight, and continuous improvement across the SAP landscape. We have seen companies gain tremendous value from well-organized and well-supported SAP CoEs. Conversely, we have…
-
How AI Is Reshaping What Good SAP Governance Looks Like
SAP governance used to mean a quarterly access review, an annual segregation of duties check, and a scramble to prepare evidence before an audit. AI is replacing that cadence with continuous monitoring: systems that watch role changes, configuration drift, and policy violations as they happen, not months later. That shift is showing up in two…
-
SAP Business Cases Usually Expire Right After They Are Approved
The SAP business case gets approved, saved to a shared drive, and left there until the program runs into trouble and someone needs to prove who promised what. On a large S/4HANA program, the space between that approved document and the running program is what quickly puts a CIO on the defensive in front of…
See your ERP in just one week.
Ready to get started? Have a few questions? Schedule a call and begin your LeapGreat journey.