Custom Code or Clean Core? How Leading SAP S/4HANA Teams Decide What Belongs Where

Introduction

Do your SAP project calls in India suddenly stretch on when someone suggests a “quick custom change”?

If you own or sponsor an SAP S/4HANA program, you already know that small changes rarely stay small. Every extra field, workflow, or report adds effort in testing, upgrades, and future cloud moves. At the same time, your business teams want systems that stay close to how they actually work in plants, branches, and shared services.

This blog gives you a clear, technical, but simple way to decide what belongs inside the core of the platform and what should sit outside as an extension.

Why this decision matters for Indian enterprises

Across Indian enterprises, SAP S/4HANA is becoming the central system for finance, supply chain, and manufacturing. The choice between custom code and a clean core affects:

• Rollout and upgrade timelines
• How quickly you respond to GST and e-invoice changes
• Data quality for analytics, AI, and planning
• Confidence that your ERP landscape can support new business plans

A recent Indian ERP pricing analysis for 2026 explains that entry-level ERP plans may start around ₹20,000 per year, while large, complex deployments can reach far higher levels once licenses, infrastructure, and services are added. 

This range shows how strongly your implementation cost depends on scope, complexity, and the volume of custom work you allow.

Start with Best Practice SAP S/4HANA, then allow exceptions

A practical way to protect the core is to treat Best Practice SAP S/4HANA as your starting point. You first explore what standard processes can cover, then you discuss where true gaps exist.

You can use a simple three-step rhythm:

1. Run focused fit-to-standard sessions

In these sessions, you map core flows such as order to cash, procure to pay, and record to report against Best Practice SAP S/4HANA. You keep the discussion on outcomes: faster collections, better inventory turns, safer compliance.

2. Classify every gap with a short checklist

For each request, ask:

• Does this come from a statutory or regulatory rule in India?
• Does this protect a clear competitive edge for your organisation?
• Does this meaningfully reduce risk around quality, safety, or cash flow?

3. Choose an extension-first path

Many needs can sit in Fiori adaptations, configuration, low-code apps, or BTP-based services instead of core code. When you always start with Best Practice SAP S/4HANA, the number of items that really touch the core falls sharply.

With this rhythm in place, the system stays flexible for India-specific needs while still supporting a stable, upgrade-ready core.

Reading the real cost of implementing SAP S/4HANA

Most budgets focus on what you spend up to go-live. In reality, the cost of implementing SAP S/4HANA stretches across the full life of the platform.

A global ERP software outlook expects Enterprise Resource Planning software revenue to grow from about USD 92.6 billion in 2025 to nearly USD 229.79 billion by 2032. This growth points to sustained demand for ERP skills and consulting capacity.

For Indian SAP leaders, this has a direct impact. Deep custom work becomes more expensive over time because you pay for it repeatedly through:

• Impact analysis before every upgrade
• Extra regression testing rounds
• Performance tuning and incident handling
• Knowledge transfer when team members move on

Leaders who think ahead look at the cost of implementing SAP S/4HANA as a lifecycle curve, not just a one-year budget. That view makes discussions with CFOs and business heads in India far more concrete.

Comparing SAP S/4HANA on-premises, private cloud, and subscription paths

Deployment choice also shapes the clean core story. Indian organisations now evaluate SAP S/4HANA on-premises, private cloud, and subscription models simultaneously, instead of reacting to them as separate worlds.

A cloud ERP market forecast projects global cloud ERP growth at a 14.5 percent CAGR between 2024 and 2029. Such growth puts pressure on talent, partner capacity, and support models.

Here is how Indian leaders commonly compare options:

This table helps Indian steering groups explain why SAP S/4HANA on-premises can still serve legacy-heavy entities while subscription paths with RISE with SAP benefits support faster, cloud-friendly parts of the enterprise.

Pressure points while migrating to SAP S/4HANA

The most sensitive stage for many Indian organisations comes when they are migrating to SAP S/4HANA from ECC or a mixed ERP landscape. Years of local modifications, custom reports, and point-to-point interfaces have built up a lot of weight.

You may recognise patterns like:

• Z programs that only a few users still run, but that add test effort
• Tax and discount rules are buried inside custom code instead of configuration
• Interfaces built quickly for older go-lives are now hard to support
• Shadow reporting in spreadsheets that bypasses the core system

A 2025 migration benchmark report found that roughly one-third of surveyed organisations had already completed their move, with many more in implementation or pilot stages. That signal matters for Indian companies because it confirms that migrating to SAP S/4HANA is an active, global shift, not a future experiment.

During migration to SAP S/4HANA, disciplined teams in India usually:

• Build a clear inventory of custom code and interfaces
• Tag items as retire, keep, refactor, or move to an extension
• Use usage and incident data to support those decisions
• Run pilots with a leaner core to prove that the platform still supports local needs

This makes each phase of the journey lighter and more predictable.

Where custom code genuinely belongs

Clean core does not mean you avoid custom work. It means custom work needs a stronger case.

In Indian SAP landscapes, custom code usually earns its place when:

• Statutory or regulatory needs demand logic that configuration alone cannot cover
• Industry-specific flows or pricing models directly support margin or growth
• Automated checks can materially reduce quality or safety risk
• Critical legacy systems and plant equipment need specialised integration

In most other areas, extension patterns are strong enough. This way, the heart of SAP S/4HANA stays stable while your teams can still respond to change.

Lifecycle governance that protects your core

After go-live, requests increase. Plants, branches, and group functions see what the system can do and start asking for more. Without guardrails, your clean core can slowly fill up again.

Simple governance habits help you stay in control:

• Every change request links to measurable outcomes such as revenue, margin, cash, or compliance
• Core modifications are treated as a last option after extension choices are evaluated
• The custom portfolio is reviewed regularly, so low-value items can be retired
• The same rules apply across on-premises and cloud systems
• Integration standards favour APIs and loose coupling instead of tight, fragile links

These habits stop “custom creep” and keep your landscape closer to the clean core model you agreed on.

How Geschäft Formulae India supports your SAP journey

You do not need to balance all these decisions alone. At Geschäft Formulae  India, the SAP services team works with organisations that want a stable core and practical innovation on top.

Through our SAP services, you can:

• Build an IT roadmap that links SAP S/4HANA to clear business goals in India
• Plan and deliver SAP S/4HANA on-premises, private cloud, or subscription programs
• Structure projects around migrating to SAP S/4HANA with a strong focus on core health
• Improve integration so the system becomes a reliable data source for decision-making
• Use consulting and managed services to explore the RISE with SAP benefits while keeping operations predictable

This support lets your internal teams focus on process change and user adoption while specialists handle architecture and governance.

Final perspective

Each custom change shapes the future of your ERP. With a clean core mindset grounded in Best Practice SAP S/4HANA, clear rules for extension-first development, an honest view of the cost of implementing SAP S/4HANA, and a structured approach to migrating to SAP S/4HANA, your organisation gains a far more predictable path to growth.

If you want to review your landscape or plan the next phase of your SAP S/4HANA program, the team at Geschäft Formulae India can help you build a clean core strategy suited for Indian operations and long-term goals.

Connect with our team today!