Skip to main content
FromNine
Menu

Enterprise platform · SAP

SAP S/4HANA, with a core that stays clean.

We plan and run S/4HANA programmes, keep custom logic out of the core by building it on SAP BTP, and connect SAP with data platforms, AI and neighbouring systems. Upgrades stay possible while the business carries on as usual.

For Malaysian groups running SAP at home and in Europe, from the group close to e-Invoice and budgets in statutory bodies.

Arrange a discussionPlatform comparison
  • SAPGold PartnerPartner status · SAP
  • ISO/IEC 27001 certified
  • 600+ European government projects
S/4HANA as a clean core, with the systems around it. SAP S/4HANA forms the clean core in the middle. Three extension layers sit over it: extensions by key users inside the application, ABAP Cloud extensions by developers on the stack, and separate applications running beside it on SAP BTP. From the core, six lines lead to Joule with custom AI, to the data platform, to identity, to Salesforce or a different CRM, to Odoo used by subsidiaries, and to MyInvois, Peppol and other government and market platforms.

When SAP is the right choice, and when it is not

A good fit when

  • One consistent record is needed for finance, purchasing, logistics and production across several companies, countries and currencies, for example a Malaysian parent with companies in the EU.
  • Your business still runs on SAP ECC and needs a credible plan for S/4HANA while mainstream maintenance lasts.
  • Statutory reporting, segregation of duties and complete audit trails are firm requirements.
  • A statutory body wants its budgets, commitments and grants recorded in one ledger with its accounts.
  • Your organisation is ready to follow SAP standard processes rather than recreate its legacy procedures in the core.

Look elsewhere when

  • A smaller subsidiary wants a lighter ERP that its own team can manage. Odoo beside the SAP group core, as a two-tier set-up, is often cheaper over time.

    Alternative: Odoo

  • Your real challenge lies in customer contact, cases or portals and not in the ledger. Salesforce usually serves better at the front, with SAP in the background.

    Alternative: Salesforce

  • The process is unique to your business and fits no standard SAP model. A custom application beside SAP protects the core from being bent out of shape.

    Alternative: Enterprise Software & SaaS

Our SAP work

Five types of work, normally combined in a single programme. They also serve as column headings in the capability matrix further down.

  1. 01

    Implement

    S/4HANA implementation

    Workshops that fit your processes to the standard, then configuration and master data for finance, logistics and public sector work, including e-Invoice output for MyInvois. Each release comes with its test evidence.

    Deliverables

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

    Extend

    Clean-core extensions

    Extensions by key users come first, then on-stack ABAP Cloud development where logic must stay near the data, and separate BTP applications built on the Cloud Application Programming Model. Upgrades remain routine.

    Deliverables

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

    Integrate

    Integration and events

    Interfaces between SAP and the rest of your systems on SAP Integration Suite, using APIs and business events, including the migration of existing interfaces away from SAP Process Orchestration.

    Deliverables

    • Interface catalogue
    • Monitored integration flows
  4. 04

    Migrate

    ECC to S/4HANA

    A new implementation, a conversion or a selective data transition, picked on the basis of your custom code, your data and your appetite for process change. Includes readiness checks, remediation of code, trial migrations and the cut-over itself.

    Deliverables

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

    Operate

    Managed evolution

    Once live, the system keeps improving: monitoring, preparation for upgrades, a ranked list of improvements, and new SAP capabilities taken up when they have shown their value.

    Deliverables

    • Release calendar
    • Run book
    • Improvement backlog

Capability matrix

Product areas we cover and the kinds of work we take on in each, shown row by row.

  • S/4HANA Finance

    Universal Journal, group close, controlling and the tax localisations of each country where you have companies.

    • Implement
    • Extend
    • Migrate
    • Operate

  • Procurement, logistics and production

    Procure to pay, stock, production planning and the execution of logistics.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Public Sector Management

    Funds and grantor management with budget availability checks for statutory bodies.

    • Implement
    • Extend
    • Migrate
    • Operate

  • Clean core and custom code

    Custom code analysed and remediated, and modifications moved onto extension points SAP supports.

    • Extend
    • Migrate
    • Operate

  • SAP BTP applications

    Applications beside the core using SAP Build or CAP, plus event-driven extensions.

    • Implement
    • Extend
    • Integrate
    • Operate

  • SAP Integration Suite

    Cloud integration, API management, e-Invoice exchange with MyInvois and the move of SAP Process Orchestration interfaces.

    • Implement
    • Integrate
    • Migrate
    • Operate

  • Business Data Cloud and SAP Datasphere

    SAP data prepared for analytics and AI with its business meaning kept intact.

    • Implement
    • Integrate
    • Operate

  • SAP Business AI and Joule

    Assessing, switching on and governing the AI scenarios included in your licence.

    • Implement
    • Extend
    • Operate

  • Identity and authorisations

    Roles, segregation of duties and SAP Cloud Identity Services.

    • Implement
    • Integrate
    • Operate

AI with SAP

Built into the platform

Under the SAP Business AI label, SAP builds AI into its cloud applications. Joule, its copilot, works in supported applications: it answers questions on SAP data, guides users to the right screen and can complete transactions. Agents for specific business processes are being added.

For scenarios of your own, SAP AI Core includes the generative AI hub: governed access to a range of large language models, with SAP controls over grounding, prompts and spend. Availability depends on product, deployment model and licence, so we confirm what you are entitled to before a plan relies on any feature.

Built alongside the platform

Much of the value lies between SAP and other systems: comparing supplier invoices with contracts kept elsewhere, preparing replies from SAP data and policy documents, or flagging unusual patterns across SAP and other sources. We run these as BTP services or in your own cloud. They reach SAP only through released APIs and events and never write to its tables.

Every AI component is limited to the SAP authorisations your team assigns, records each step and asks for approval before a posting that has consequences. We set quality criteria with you, test against them before and after go-live, and route doubtful cases to people.

Choosing the route

  1. 01

    Is the scenario already part of the standard SAP products you license?

    If yes

    Switch on and govern the standard capability first. It follows the SAP release cycle and leaves no code to maintain.

    If no

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

  2. 02

    Will the scenario draw on data from systems other than SAP?

    If yes

    Build alongside the platform; SAP becomes one of several governed sources.

    If no

    Keep it within SAP, where standard features and existing authorisations cover it.

  3. 03

    Is the AI going to create or alter business documents?

    If yes

    Settle the approval step and audit trail first, before go-live.

    If no

    Start with read-only access, check quality against the criteria you agreed, then decide.

Moving from ECC to S/4HANA in six steps

  1. Step 01

    Discover

    Readiness check, analysis of custom code, review of processes and data, and a list of every interface.

    • Readiness report
    • Custom code inventory
    • Interface list

  2. Step 02

    Decide the route

    The choice between greenfield, brownfield and selective data transition, between RISE with SAP and other deployment models, and the clean-core rules extensions must follow.

    • Transition strategy
    • Target architecture

  3. Step 03

    Prepare

    Data cleansing, remediation of custom code, redesign of interfaces, including MyInvois, and automated regression tests.

    • Cleansed data
    • Remediated code
    • Test suite

  4. Step 04

    Build and rehearse

    Configuration, extensions on BTP and interfaces, rehearsed through several full trial migrations.

    • Release candidates
    • Rehearsal reports
    • Cutover runbook

  5. Step 05

    Cut over

    Downtime agreed in advance, balances and open items reconciled, then close support for the business.

    • Reconciliation sign-off
    • Hypercare log

  6. Step 06

    Evolve

    Regular upgrades, then automation and AI when the core has settled.

    • Release plan
    • Operating model
Illustrative example

One template for a Malaysian parent and its EU sales company

01Situation
An electronics exporter could be running SAP ECC at its Malaysian parent and a separate package at its sales company in the EU. ECC mainstream maintenance ends on 31 December 2027, the parent issues e-Invoices through MyInvois, and the EU company has e-invoicing rules of its own.
02What we would deliver
S/4HANA on one group template for both companies by selective data transition, e-Invoice submission and validation results through the MyInvois API, invoices for the EU company in the format its country requires, and intercompany flows carried on SAP Integration Suite.
03Decisions that stay with people
Group finance controllers sign off intercompany postings over an agreed amount and check every rejected e-Invoice before resubmission; each automated posting keeps its source document and a log entry.
04How results would be tracked
Working days needed for the group close, share of e-Invoices accepted at first submission, share of intercompany items matched automatically, and the effort each upgrade takes.

SAP among your other systems

SAP usually holds the books and the material record, but it seldom stands alone. We link it using SAP Integration Suite or your current integration platform, with released APIs, business events and well-specified file exchanges. Front offices, subsidiaries, data platforms, MyInvois and other government services each get what they need, without a web of direct links.

Plenty of SAP landscapes still rely on SAP Process Orchestration for their interfaces. Mainstream maintenance for its current release also ends at the close of 2027, so moving those interfaces is part of the same plan as S/4HANA. Our integration specialists design the two together.

Illustrative example

People and channels

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

SAP S/4HANA

Integration Suite · APIs · events

Systems and data

  • Data platform and Datasphere
  • Odoo subsidiaries
  • Identity provider
  • MyInvois, Peppol and tax services
How SAP connects to the systems it serves
Read the diagram as text

Left side, people and channels: SAP users working in Fiori and Joule, the Salesforce front office, and portals used by suppliers and the public.

Centre, SAP S/4HANA, which reaches every other system through one integration layer built on SAP Integration Suite, APIs and business events.

Right side, systems and data: the data platform including SAP Datasphere, Odoo at subsidiaries, the identity provider, and MyInvois, Peppol and tax services.

SAP by sector

Public sector

Public Sector & Government

Statutory bodies can run funds, budgets and grants in S/4HANA with links to government systems. Those still on ECC lose mainstream maintenance on the same date as private companies, and must fit the move into procurement rules and annual budget cycles.

600+

European government projects

  • Manufacturing & Industry

    For electronics, chemicals and metals producers: production planning, quality management and plant maintenance in S/4HANA, while shop-floor data and planning support from AI stay outside the core.

  • Financial Services

    Financial and regulatory reporting with duties kept separate and every change traceable, designed with the Risk Management in Technology (RMiT) policy document of Bank Negara Malaysia (BNM) in view, and with DORA where EU financial entities are your customers.

  • Healthcare & Life Sciences

    Purchasing, stock and finance for private hospitals, pharmaceutical manufacturers and medical device makers, with every batch traceable and every change controlled.

Malaysia

SAP for groups in Malaysia and the EU

A Malaysian group with companies in the EU meets two sets of invoicing rules in one SAP landscape. At home, the Inland Revenue Board of Malaysia (IRBM) phased in mandatory e-Invoice from 1 August 2024 to 1 January 2026, and each invoice is validated through MyInvois. Malaysia Digital Economy Corporation (MDEC) is the Peppol Authority for Malaysia, with Malaysia PINT as the national specification. In the EU, each Member State where the group has a company brings its own e-invoicing requirements.

We set up localisation, output management and the integration layer so that each new country extends a single template rather than forcing changes to the core.

The same care applies to data. For the European companies, the EU Data Act affects how SAP data may be shared with other systems, and NIS2 affects how the integration layer must be protected.

Common questions about SAP

When does SAP stop mainstream maintenance for ECC?

For SAP ECC 6.0, part of SAP Business Suite 7, SAP has committed to mainstream maintenance up to 31 December 2027. Extended maintenance is available for an additional fee up to the end of 2030, and SAP has announced transition options for certain customers moving to RISE with SAP.

Because these terms shift and vary by contract, we check the position with you and with SAP before any plan rests on it.

How do we choose between a new system, a conversion and a selective transition?

A brownfield conversion keeps your current system, with its history and custom code, and is the fastest route when processes are in good shape. A greenfield implementation starts again and fits organisations that want to rethink how they work. Selective data transition is the middle way: a new system carrying over only the history and organisational units you pick.

The choice rests on evidence: the volume and quality of custom code, the state of the data, the distance between your processes and the standard, and the amount of change your people can take on in one go.

What does a clean core mean in day-to-day terms?

Nobody modifies SAP code. Extensions rely only on released APIs and extension points, and each piece of custom logic goes to the right layer: key-user tools for simple adjustments, on-stack ABAP Cloud development where logic must stay near the data, and SAP BTP for applications that have their own life cycle.

The pay-off is upgrades measured in weeks, not in projects. We write the rules into extension guidelines and review all new work against them.

Is Joule available in our SAP landscape?

It depends on your SAP products, their deployment and the scope of your licence. Joule is offered mostly in SAP cloud applications.

We start by listing your entitlements, then advise on standard features, a custom BTP service, or a mix of the two.

Can our custom code come with us to S/4HANA?

Part of it can. When we analyse custom code, a large portion usually turns out to be unused, some of it is covered by standard S/4HANA functions, and what remains is either remediated or rebuilt as a clean extension. Measurement comes first; decisions follow object by object.

Do you deliver SAP for the public sector?

Yes. SAP work in the public sector brings together funds management, grants, procurement rules, accessibility and links to government services. Our experience comes from Europe: 600+ government projects for public authorities in EU Member States, some completed and others still running. For a Malaysian statutory body, that means documentation and audit trails built for procurement and review. Our public sector page explains more.

Talk through your next SAP move

Whether you are picking a route to S/4HANA, tidying an overloaded core or bringing AI to SAP, the first step is a discussion of your landscape and the dates you must meet.

Arrange a discussionDocument intelligence