Skip to main content
FromNine
Menu

Enterprise platform · SAP

SAP, from S/4HANA to a clean core.

We plan and deliver S/4HANA transformations, keep the core clean with extensions on SAP BTP, and connect SAP to the data, AI and systems around it. The core stays upgradeable while the business keeps moving.

For groups and public bodies running SAP in several European countries, from group close to public budgets.

Discuss your platform needsCompare the platforms
  • SAPGold PartnerPartner status · SAP
  • ISO/IEC 27001 certified
  • 600+ European government projects
A clean SAP core and the systems around it. At the centre sits SAP S/4HANA as the clean core. Three extension layers sit above it: key-user extensions in the application, developer extensions with ABAP Cloud on the stack, and side-by-side applications on SAP BTP. Six connections lead out from the core: Joule and custom AI, the data platform, identity, Salesforce or another CRM, Odoo in subsidiaries, and government and market platforms such as Peppol.

Where SAP fits, and where it does not

Fits well when

  • Finance, procurement, supply chain and manufacturing run across several entities, countries and currencies and need one consistent record.
  • You run SAP ECC today and need a credible route to S/4HANA before mainstream maintenance ends.
  • Statutory reporting, audit trails and segregation of duties are non-negotiable.
  • A public body needs budget control, commitments and grants in the same ledger as its accounts.
  • You are prepared to adopt standard processes rather than rebuild your old ones inside the core.

Consider alternatives when

  • A subsidiary or smaller entity needs a lighter ERP that it can run itself. Odoo in a two-tier model next to the SAP group core is often cheaper to own.

    Alternative: Odoo

  • The real problem is customer engagement, case handling or portals rather than the ledger. Salesforce usually makes the better front office, with SAP behind it.

    Alternative: Salesforce

  • The process is unique to you and no standard model fits it. Custom software next to SAP keeps the core clean instead of bending it.

    Alternative: Enterprise Software & SaaS

What we deliver on SAP

Five kinds of work, usually combined in one programme. They also label the columns of the capability matrix below.

  1. 01

    Implement

    S/4HANA implementation

    Fit-to-standard workshops, configuration and master data design for finance, logistics and public sector processes, delivered in releases with test evidence.

    Outputs

    • Fit-to-standard backlog
    • Configured releases
    • Test evidence
  2. 02

    Extend

    Clean-core extensions

    Key-user extensions first, ABAP Cloud on the stack where logic belongs close to the data, and side-by-side applications on SAP BTP with the Cloud Application Programming Model. Upgrades stay routine.

    Outputs

    • Extension guidelines
    • BTP applications
    • Released-API usage only
  3. 03

    Integrate

    Integration and events

    SAP Integration Suite, APIs and business events between SAP and the rest of your estate, including the move of existing interfaces off SAP Process Orchestration.

    Outputs

    • Interface catalogue
    • Monitored integration flows
  4. 04

    Migrate

    ECC to S/4HANA

    Greenfield, brownfield or selective data transition, chosen on your custom code, data quality and appetite for process change. Readiness checks, code remediation, migration rehearsals and cut-over.

    Outputs

    • Transition strategy
    • Custom code inventory
    • Cutover runbook
  5. 05

    Operate

    Managed evolution

    After go-live we keep the system moving: monitoring, upgrade preparation, a prioritised improvement backlog and adoption of new SAP capabilities when they earn their place.

    Outputs

    • Release calendar
    • Run book
    • Improvement backlog

Capability matrix

Product areas we work in, and the kind of work we do in each. Read a row from left to right.

  • S/4HANA Finance

    Universal Journal, group close, controlling and country tax localisations across entities.

    • Implement
    • Extend
    • Migrate
    • Operate

  • Sourcing, supply chain and manufacturing

    Procure-to-pay, inventory, production planning and logistics execution.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Public Sector Management

    Funds management, budget availability control and grantor management for public bodies.

    • Implement
    • Extend
    • Migrate
    • Operate

  • Custom code and clean core

    Custom code analysis and remediation, and moving modifications to supported extension points.

    • Extend
    • Migrate
    • Operate

  • SAP BTP applications

    Side-by-side applications with CAP and SAP Build, and event-driven extensions.

    • Implement
    • Extend
    • Integrate
    • Operate

  • SAP Integration Suite

    Cloud integration, API management and migration of SAP Process Orchestration interfaces.

    • Implement
    • Integrate
    • Migrate
    • Operate

  • SAP Datasphere and Business Data Cloud

    SAP data made usable for analytics and AI without losing its business meaning.

    • Implement
    • Integrate
    • Operate

  • Joule and SAP Business AI

    Assessment, activation and governance of the AI scenarios your licence includes.

    • Implement
    • Extend
    • Operate

  • Identity and authorisations

    SAP Cloud Identity Services, role design and segregation of duties.

    • Implement
    • Integrate
    • Operate

AI with SAP

Native on the platform

SAP builds AI into its cloud applications under the SAP Business AI name. Joule is its AI copilot: in supported applications it answers questions about SAP data, helps users navigate and can carry out transactions, and SAP is adding agents for specific business processes.

For custom scenarios, SAP offers the generative AI hub in SAP AI Core: governed access to a choice of large language models, with SAP controls for grounding, prompts and cost. What is available depends on product, deployment model and licence, so we confirm your entitlements before anyone plans around a feature.

Built around the platform

Many useful scenarios sit between SAP and other systems: matching supplier invoices against contracts held elsewhere, drafting answers from SAP data and policy documents, flagging anomalies across SAP and non-SAP sources. We build these as services on SAP BTP or your own cloud, calling SAP through released APIs and events, never by writing to tables.

Every AI component acts within the SAP authorisations you define, logs each step and asks for approval before consequential postings. We agree quality criteria and test output against them before and after release, and route uncertain cases to people.

Which route fits

  1. 01

    Is the scenario delivered as standard in your SAP products and licence?

    If yes

    Activate and govern the native capability first. It follows SAP’s release cycle with no code to maintain.

    If no

    Assess a custom service on SAP BTP using the generative AI hub, or your own model platform.

  2. 02

    Does the use case need data from outside SAP?

    If yes

    Build around the platform, with SAP as one governed source among several.

    If no

    Keep it inside SAP, where native features and authorisations already apply.

  3. 03

    Will the AI create or change business documents?

    If yes

    Design the approval step and the audit trail before anything goes live.

    If no

    Start read-only, measure quality against agreed criteria, then decide.

The path from ECC to a clean S/4HANA core

  1. Step 01

    Discover

    Readiness check, custom code analysis, process and data assessment, interface inventory.

    • Readiness report
    • Custom code inventory
    • Interface list

  2. Step 02

    Decide the route

    Greenfield, brownfield or selective data transition; RISE with SAP or another deployment; clean-core rules for extensions.

    • Transition strategy
    • Target architecture

  3. Step 03

    Prepare

    Data cleansing, custom code remediation, interface redesign and automated regression tests.

    • Cleansed data
    • Remediated code
    • Test suite

  4. Step 04

    Build and rehearse

    Configuration, BTP extensions and integration, with repeated full migration rehearsals.

    • Release candidates
    • Rehearsal reports
    • Cutover runbook

  5. Step 05

    Cut over

    Agreed downtime window, reconciliation of balances and open items, hypercare with the business.

    • Reconciliation sign-off
    • Hypercare log

  6. Step 06

    Evolve

    A steady upgrade rhythm, then automation and AI once the core is stable.

    • Release plan
    • Operating model
Illustrative example

A group core with lighter subsidiaries

01Situation
A manufacturing group runs SAP ECC at headquarters and a mix of local systems in subsidiaries in three EU countries. ECC maintenance is ending and every country has its own e-invoicing rules.
02What we build
S/4HANA for group finance and production by selective data transition, Odoo in the smaller subsidiaries, and one integration layer on SAP Integration Suite carrying intercompany flows and country e-invoicing.
03Human control
Finance controllers approve intercompany postings above an agreed threshold; every automated posting carries its source document and is logged.
04What we would measure
Days to group close, share of intercompany items matched without manual work, and effort per upgrade.

SAP in the wider landscape

SAP is usually the system of record for money and materials, and almost never the only system. We connect it through SAP Integration Suite or your existing integration platform, using released APIs, business events and well-defined file interfaces. Front offices, subsidiaries, data platforms and government services each get what they need without point-to-point sprawl.

Many estates still run their interfaces on SAP Process Orchestration, whose current release reaches the end of mainstream maintenance at the end of 2027 as well. Interface migration belongs in the same plan as the S/4HANA move. Our integration and API practice designs both together.

Illustrative example

People and channels

  • SAP Fiori and Joule
  • Salesforce front office
  • Supplier and citizen portals

SAP S/4HANA

Integration Suite · APIs · events

Systems and data

  • Data platform and Datasphere
  • Odoo subsidiaries
  • Identity provider
  • Peppol, tax and government services
SAP among the systems it serves
Read the diagram as text

On the left, people and channels: SAP Fiori and Joule for SAP users, a Salesforce front office, and supplier and citizen portals.

In the middle, SAP S/4HANA, connected to everything else through one integration layer: SAP Integration Suite with APIs and business events.

On the right, systems and data: the data platform with SAP Datasphere, Odoo in subsidiaries, the identity provider, and Peppol, tax and government services.

SAP in your sector

Public sector

Public Sector & Government

Funds management, budget control and grantor management in S/4HANA, connected to government platforms and e-invoicing networks. Public bodies on ECC face the same end of mainstream maintenance as industry, and have to plan the move inside procurement rules and budget cycles.

600+

European government projects

  • Manufacturing & Industry

    Production planning, quality and plant maintenance on S/4HANA, with shop-floor data and AI-assisted planning kept outside the core.

  • Financial Services

    Finance and regulatory reporting with segregation of duties, complete audit trails and the operational resilience DORA expects.

  • Healthcare & Life Sciences

    Procurement, inventory and finance for hospitals and life sciences, with batch traceability and controlled change.

International

SAP across European markets

An SAP programme that spans several countries meets several sets of rules at once. E-invoicing is the clearest example: Belgium made Peppol e-invoicing mandatory between businesses in 2026, Germany requires companies to receive structured e-invoices and is phasing in issuing, and France is rolling out its own reform through approved platforms. We design the S/4HANA localisation, the output management and the integration layer so each country can be added without reopening the core.

The same discipline applies to data: the EU Data Act and NIS2 shape how SAP data is shared with other systems and how the integration layer is secured.

SAP questions we hear often

When does mainstream maintenance for SAP ECC end?

SAP has committed to mainstream maintenance for SAP ECC 6.0 (SAP Business Suite 7) until 31 December 2027, with optional extended maintenance at extra cost until the end of 2030. SAP has also announced transition options for some customers who move to RISE with SAP.

Terms change and depend on your contract, so we check the current position with you and SAP before building a plan on it.

Greenfield, brownfield or selective data transition: which is right for us?

Brownfield converts your existing system and keeps history and custom code, which is fastest when processes are sound. Greenfield starts clean and suits organisations that want to redesign processes. Selective data transition sits between the two: a new system with the history and organisational units you choose to bring along.

We decide on evidence: custom code volume and quality, data quality, how far processes have drifted from standard, and how much change the business can absorb at once.

What does clean core mean in practice?

No modifications to SAP code, extensions only through released APIs and extension points, and custom logic placed in the right layer: key-user tools for simple changes, ABAP Cloud on the stack when logic must sit close to the data, SAP BTP for applications with their own life cycle.

The pay-off is upgrades that take weeks rather than projects. We write the rules down as extension guidelines and check new work against them.

Can we use Joule in our SAP landscape?

It depends on which SAP products you run, how they are deployed and what your licence includes. Joule is primarily available in SAP cloud applications.

We start with an inventory of what you are entitled to, then advise whether to activate native features, build a custom service on SAP BTP, or both.

Can we move to S/4HANA and keep our custom code?

Some of it. A custom code analysis usually shows that a large share is no longer used, some is replaced by standard S/4HANA functions, and the rest needs remediation or a new home as a clean extension. We measure first, then decide object by object.

Do you work with public bodies on SAP?

Yes. Public sector SAP work combines funds management and grants with procurement rules, accessibility requirements and links to government services. Our experience spans 600+ European government projects, delivered and ongoing, and we bring it to SAP programmes. See our public sector work.

Plan your next SAP step with us

Whether you are choosing an S/4HANA route, cleaning up a core or connecting SAP to AI, start with a conversation about your landscape and your deadlines.

Discuss your platform needsSee document intelligence