New articleSAP IS-U to S/4HANA Utilities: choosing between conversion, greenfield and selective transition

Clean Core

Keep billing custom code off the S/4 core

Clean core means fewer modifications in S/4HANA Utilities, and extensions that survive upgrades. For utilities, that starts with an honest view of IS-U billing and FI-CA custom code.
S/4 readinessABAP Cloud

The challenge

Why utilities feel stuck with custom code

  • Custom billing code sticks to the core

    Years of IS-U exits, enhancements and reports sit next to SAP code. That slows upgrades and makes an S/4HANA Utilities move harder to scope.

  • New needs still land in-core by habit

    Rate experiments, portal rules and partner interfaces often get built where the team already knows the debugger, not where upgrades stay cheap.

  • Leadership hears clean core without a plan

    Clean core is easy to say and hard to operationalize: what stays on-stack, what moves to BTP, and what gets retired.

Approach

How we advise on a cleaner core

  1. 01

    Keep the digital core thin

    Prefer released APIs, key-user extensibility and configuration for standard meter-to-cash processes. Put lasting custom logic on released extension points or beside the core.

  2. 02

    Extend on SAP BTP when it fits

    Side-by-side apps, Integration Suite flows and event-driven services keep partner and channel logic off the upgrade path when the process does not need to live inside S/4.

  3. 03

    Use ABAP Cloud for on-stack work that must stay close

    When logic must run next to billing or FI-CA, build with RAP, CDS and released APIs so the extension stays lifecycle-stable.

  4. 04

    Review IS-U custom code with S/4 in mind

    Inventory what billing and FI-CA custom code still does, what blocks a move, and what can be rebuilt, wrapped or dropped before a conversion or selective transition.

When to choose what

Side-by-side, on-stack, or stay careful

  • Side-by-side on BTP

    Channel apps, partner integrations, analytics hand-offs and non-core workflows that consume released APIs or events.

  • On-stack ABAP Cloud

    Process steps that must run inside S/4HANA Utilities with transactional consistency next to billing or FI-CA.

  • Stay in-core (carefully)

    Only when SAP provides no released path yet. Isolate with wrappers so the custom piece can be replaced when APIs appear.

Related reading: SAP BTP integration, ABAP Cloud, and the S/4 readiness assessment, which reviews custom billing code as part of path planning. Accelerators such as Bill Comparison are examples of capability that can sit beside the core where the process allows.

Talk through your custom code

Bring a list of billing exits and enhancements. We will help you sort what to keep, rebuild or retire before an S/4 move.

Book a scoping callS/4 readiness

Looking for BTP integration detail? SAP BTP integration →