Skip to main content
FromNine
Menu

Enterprise platform · SAP

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

We plan and carry out the move to S/4HANA, keep modifications out of the core by extending on SAP BTP, and link SAP to your data, your AI and the systems around it. Upgrades stay possible while operations carry on as normal.

For Maltese plants that belong to European groups, MFSA licence holders and public entities running SAP, whether for a group close or a public budget.

Start a conversationCompare Salesforce, SAP and Odoo
  • SAPGold PartnerPartner status · SAP
  • ISO/IEC 27001 certified
  • 600+ European government projects
S/4HANA as a clean core, with its surrounding systems. S/4HANA occupies the centre and is free of modifications. Extensions are placed in three tiers above it: small changes made by key users in the application itself, ABAP Cloud code running on the S/4HANA stack, and stand-alone apps hosted on SAP BTP. Six lines run out from S/4HANA, one each to Joule and bespoke AI, the data platform, identity, Salesforce or a different CRM, Odoo used by subsidiaries, and Government and trading networks, Peppol among them.

Is SAP the right platform for you?

A good fit when

  • Your finance, purchasing, supply chain and production cover more than one company, country or currency, and the group needs a single reliable record.
  • SAP ECC is your system today, and you need a workable plan for reaching S/4HANA while mainstream maintenance still runs.
  • Auditors and regulators expect statutory reports, complete audit trails and strict segregation of duties, with no exceptions.
  • A ministry or public entity wants to keep budgets, commitments and grants in the ledger where it keeps its accounts.
  • Your management accepts SAP’s standard processes, and has no wish to recreate past habits in the core.

Look at alternatives when

  • A smaller company in the group, such as a Maltese sales office, wants an ERP its own staff can run. A two-tier model with Odoo locally and SAP at group level is often cheaper over the years.

    Alternative: Odoo

  • Your pain lies in dealing with clients, cases or portals rather than in accounting. In that situation Salesforce usually serves better at the front, with SAP behind it.

    Alternative: Salesforce

  • Nothing standard matches a process that is unique to you. Building that piece as bespoke software beside SAP protects the core from being bent to fit.

    Alternative: Enterprise Software & SaaS

Our SAP services

Our SAP work falls into five types, normally mixed within one programme. The capability matrix lower down uses the same five as its columns.

  1. 01

    Implement

    S/4HANA implementation

    Workshops that test your needs against SAP standard, followed by configuration and master data design for finance, logistics and public administration, delivered release by release with test results you can show.

    Outputs

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

    Extend

    Clean-core extensions

    Key-user extensions as the first choice, ABAP Cloud on the stack when logic has to stay close to the data, and separate applications on SAP BTP using the Cloud Application Programming Model. Upgrades remain routine work.

    Outputs

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

    Integrate

    Integration and events

    Connections between SAP and your other systems through SAP Integration Suite, APIs and business events, and the transfer of existing interfaces off SAP Process Orchestration.

    Outputs

    • Interface catalogue
    • Monitored integration flows
  4. 04

    Migrate

    ECC to S/4HANA

    We pick greenfield, brownfield or selective data transition after looking at your custom code, your data and how much your processes may change. Then come readiness checks, code repair, rehearsals of the migration and the cut-over.

    Outputs

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

    Operate

    Managed evolution

    Once the system is live we keep it moving: monitoring, preparing upgrades, a ranked backlog of improvements and taking up new SAP features when they prove their value.

    Outputs

    • Release calendar
    • Run book
    • Improvement backlog

Capability matrix

The SAP areas we work in and the type of work we do in each. Each row reads from left to right.

  • S/4HANA Finance

    Universal Journal, group closing, controlling and tax localisations for each country and entity.

    • Implement
    • Extend
    • Migrate
    • Operate

  • Sourcing, supply chain and manufacturing

    Purchasing through to payment, stock, production planning and logistics.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Public Sector Management

    Funds management, checks on budget availability and grantor management for the public sector.

    • Implement
    • Extend
    • Migrate
    • Operate

  • Custom code and clean core

    Analysis and remediation of custom code, and relocating modifications to supported extension points.

    • Extend
    • Migrate
    • Operate

  • SAP BTP applications

    Stand-alone apps using CAP and SAP Build, plus event-based extensions.

    • Implement
    • Extend
    • Integrate
    • Operate

  • SAP Integration Suite

    Cloud integration and API management, and the migration of interfaces still running on SAP Process Orchestration.

    • Implement
    • Integrate
    • Migrate
    • Operate

  • SAP Datasphere and Business Data Cloud

    Making SAP data available for analysis and AI while it keeps its business meaning.

    • Implement
    • Integrate
    • Operate

  • Joule and SAP Business AI

    We assess which AI scenarios your licence covers, activate them and set rules for their use.

    • Implement
    • Extend
    • Operate

  • Identity and authorisations

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

    • Implement
    • Integrate
    • Operate

AI in and around SAP

Built into the platform

SAP Business AI is the label SAP uses for the AI it builds into its cloud applications. Its copilot, Joule, works inside supported applications: it answers questions about SAP data, guides users to the right screen and can complete transactions, while SAP keeps adding agents for particular business processes.

Where you need something SAP does not ship, the generative AI hub in SAP AI Core gives governed access to a range of large language models, and SAP controls grounding, prompts and costs. What you can use varies by product, deployment model and licence, so we confirm your entitlements before a plan counts on any feature.

Built next to the platform

Much of the value sits where SAP meets other systems. Think of supplier invoices compared with contracts kept in a document system, draft replies built from SAP figures and internal policies, or unusual patterns found only when SAP and non-SAP data are read side by side. We deliver these as services on SAP BTP or in your own cloud. They talk to SAP solely through released APIs and events and never write directly to its tables.

Each AI component stays within the SAP authorisations you set, records every step and waits for approval before it makes a posting that matters. Quality criteria are agreed with you, output is tested against them before and after go-live, and doubtful cases are passed to staff.

Choosing a route

  1. 01

    Is this scenario already part of standard SAP under your licence?

    If yes

    Use the SAP feature first, with rules around it. SAP updates it in each release and there is no code for you to look after.

    If no

    Look at a bespoke service on SAP BTP using the generative AI hub, or at your own model platform.

  2. 02

    Does the scenario rely on data held outside SAP?

    If yes

    Build it next to the platform, treating SAP as one controlled source among others.

    If no

    Keep it within SAP, where the built-in features and authorisations already apply.

  3. 03

    Is the AI going to draft or amend business documents?

    If yes

    Settle who approves and how the audit trail is kept before going live.

    If no

    Give it read-only rights at first, compare its output with the agreed criteria, and only then take a decision.

From SAP ECC to S/4HANA in six stages

  1. Step 01

    Discover

    We check readiness, analyse the custom code, assess processes and data quality, and list every interface.

    • Readiness report
    • Custom code inventory
    • Interface list

  2. Step 02

    Decide the route

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

    • Transition strategy
    • Target architecture

  3. Step 03

    Prepare

    Data is cleansed, custom code repaired, interfaces redesigned and regression tests automated.

    • Cleansed data
    • Remediated code
    • Test suite

  4. Step 04

    Build and rehearse

    Configuration, BTP extensions and interfaces, with several complete rehearsals of the migration.

    • Release candidates
    • Rehearsal reports
    • Cutover runbook

  5. Step 05

    Cut over

    A downtime window agreed in advance, balances and open items reconciled, and close support for the business afterwards.

    • Reconciliation sign-off
    • Hypercare log

  6. Step 06

    Evolve

    Upgrades on a fixed rhythm; automation and AI follow when the core is stable.

    • Release plan
    • Operating model
Illustrative example

A Maltese plant on the group’s S/4HANA core

01Starting point
A European pharmaceutical group runs SAP ECC at its head office, while its plant in Malta keeps production, batches and local finance in an older separate system. ECC maintenance is coming to an end, and the group reports to its EU customers and regulators from one set of figures.
02What we put in place
S/4HANA for group finance and production through selective data transition, the Maltese plant brought onto the group template with batch management, and one layer on SAP Integration Suite carrying intercompany flows and e-invoices, including EN 16931 invoices to Maltese Government buyers over Peppol.
03Where people decide
Batch release stays with the plant’s quality staff. Group controllers approve intercompany postings above an agreed amount, and each automated posting keeps a link to its source document and is logged.
04How we judge success
Days needed for the group close, the share of intercompany items matched with no manual work, time to trace a batch from the plant to the customer, and the effort each upgrade takes.

How SAP connects to your other systems

SAP tends to hold the books and the materials, but it never works alone. Our link between SAP and everything else is SAP Integration Suite or the integration platform you already run, built on released APIs, business events and well-documented file exchanges. The client-facing layer, the subsidiaries, the data platform and Government services, e-invoicing over Peppol included, all get the data they need, without dozens of one-to-one connections.

If your interfaces still run on SAP Process Orchestration, note that its current release also loses mainstream maintenance at the end of 2027. The S/4HANA plan should therefore cover the interface migration too, and our integrations and API team plans both as one piece of work.

Illustrative example

People and channels

  • Fiori and Joule
  • Client-facing Salesforce
  • Supplier and resident portals

SAP S/4HANA

Integration Suite · APIs · events

Systems and data

  • Datasphere and data platform
  • Odoo at subsidiaries
  • Identity provider
  • Peppol, tax, Government
SAP among the systems that depend on it
Read the diagram as text

Left side, the people and channels: SAP users in Fiori and Joule, client staff working in Salesforce, and portals used by suppliers and residents.

Centre, S/4HANA, with every connection passing through SAP Integration Suite, its APIs and its business events.

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

SAP for your sector

Government & Public Entities

Government & Public Entities

Funds management, budget control and grantor management in S/4HANA for ministries and public entities, linked to Government platforms and to e-invoicing over Peppol. A public entity still on ECC faces the same maintenance deadline as a company, and must plan its move within the Public Procurement Regulations and its budget cycle.

600+

European government projects

  • Manufacturing & Industry

    Production planning, quality and maintenance on S/4HANA for Maltese plants of European groups, including pharmaceutical manufacturers, with shop-floor data and AI-supported planning kept out of the core.

  • Financial Services

    Accounting and supervisory reporting for credit institutions, insurers and investment services firms licensed by the MFSA, with duties kept apart, every change traceable and the ICT resilience expected under DORA.

  • Healthcare & Life Sciences

    Purchasing, stock and finance for private healthcare providers and life sciences firms, with batch traceability and controlled change management.

Malta

SAP in Malta

When SAP runs in a Maltese plant or company that belongs to a European group, the local system has to fit the group core and still follow Maltese rules. E-invoicing shows this most clearly. Government has chosen the Peppol network and must accept EN 16931 e-invoices, in the Peppol BIS Billing 3.0 format, on contracts above the EU thresholds; suppliers are not legally required to send them, although some calls for tenders do require it. The other countries in which the group trades each have e-invoicing rules of their own.

Our S/4HANA localisation, output management and integration layer are designed so that Malta, and any country added later, slots in without the core being reopened. Data is treated with equal care: the EU Data Act governs how SAP data is shared with other systems, the NIS2 Order (Legal Notice 71 of 2025) sets security duties for operators within its scope, and DORA, supervised by the MFSA, applies to licence holders that run SAP.

Questions about SAP

Until when does SAP provide mainstream maintenance for ECC?

SAP’s commitment covers mainstream maintenance of SAP ECC 6.0, part of SAP Business Suite 7, until 31 December 2027. After that, extended maintenance is available at an additional fee until the end of 2030, and SAP has announced transition options for some customers moving to RISE with SAP.

Such terms shift over time and vary from contract to contract. We therefore verify the position that applies to you, together with SAP, before any plan depends on it.

Greenfield, brownfield or selective data transition: which route suits us?

Brownfield converts the system you have, keeping its history and its custom code, and is the quickest route if your processes work well. Greenfield means a fresh system, which suits an organisation that wants to redesign how it works. Selective data transition is the middle way: a new system loaded with only the history and organisational units you decide to keep.

The evidence decides: the volume and quality of custom code, the state of your data, the distance between your processes and the SAP standard, and the amount of change your staff can absorb in one go.

In practice, what is a clean core?

Nobody modifies SAP’s own code. Extensions rely only on released APIs and extension points, and each piece of custom logic lives in the layer that suits it: key-user tools for simple adjustments, ABAP Cloud on the stack if the logic has to be close to the data, and SAP BTP for apps that follow their own life cycle.

The reward is an upgrade measured in weeks instead of a full project. We set the rules out as extension guidelines and check every new development against them.

Could we use Joule with the SAP products we have?

The answer hangs on which SAP products you have, how they are deployed and what your contract includes. For now, Joule is offered mainly within SAP cloud applications.

Our first step is a list of your entitlements. From there we recommend activating SAP’s own features, a bespoke service on SAP BTP, or a mix.

Will our custom code survive the move to S/4HANA?

Only some of it. When we analyse custom code, a good part usually turns out to be unused, another part is replaced by standard S/4HANA functions, and what is left is either repaired or rebuilt as a clean extension. Measurement comes first, then a decision for each object.

Do you work on SAP for Government ministries and public entities?

We do. SAP in the public sector brings together funds management and grants with procurement rules, accessibility duties and links to Government services. In Malta that means calls for tenders on ePPS under S.L. 601.03 and, where Government is invoiced, EN 16931 e-invoices over Peppol. We bring the experience of 600+ public-sector projects across the EU, completed or still running, to every SAP programme. More on our work in Government & Public Entities.

Let us plan your next step on SAP

Whether you are choosing a route to S/4HANA, tidying up a core or linking SAP to AI, the first step is a conversation about your landscape and the dates you have to meet.

Start a conversationSee our document intelligence work