An SAP S/4HANA Cloud implementation is a different kind of project from the ERP projects most Malaysian finance teams have seen before. With older systems, the question was "how do we make the software do what we do today?" With S/4HANA Cloud, the question flips: "SAP already has a proven way to run this process, so where do we really need to be different?" Companies that accept that early tend to go live faster and with fewer surprises.
This guide explains how a typical project runs, phase by phase, how long each part takes, who you need on your side, and the mistakes we see most often. It is written for CFOs, finance managers and IT heads at mid-sized and growing Malaysian companies who are planning or budgeting a move.
How S/4HANA Cloud Projects Are Run
SAP S/4HANA Cloud projects follow SAP Activate, SAP's implementation methodology. It has six phases: Discover, Prepare, Explore, Realize, Deploy and Run. The heart of it is the fit to standard approach. Instead of writing long requirement documents, your team is shown SAP's preconfigured best practice processes in a working system, and you agree where they fit and where a real gap exists.
That matters because S/4HANA Cloud, especially the public edition, is built to stay close to standard. SAP updates the public edition for all customers twice a year. Heavy customisation makes every update harder, so changes are made through approved extensions rather than by modifying the core.
The Six Phases, Step by Step
1. Discover
You confirm the business case and rough scope: which companies, which processes, which edition. Many companies use a trial or demo system here to see the product before committing. For help with the edition and product choice, see our companion post on SAP Business One vs SAP S/4HANA Cloud.
2. Prepare
The project is planned and staffed. Your system is provisioned, the project team is onboarded and governance is agreed: who signs off decisions, how often the steering committee meets, and how issues are escalated.
3. Explore
This is where the fit to standard workshops happen. Finance, procurement, sales, warehouse and production leads walk through SAP's standard processes with the consultants. Each gap is logged and decided: adopt the standard, change the business process, or build an extension. Data migration and integration needs are also defined here.
4. Realize
The system is configured in short iterations, extensions and integrations are built, and data is loaded into test systems several times. Key users test real scenarios end to end, such as order to cash, procure to pay and record to report.
5. Deploy
Final testing, user training, cutover planning and go live. Opening balances and open documents are migrated, old systems are frozen, and the new system goes into production, usually at a month end.
6. Run
After go live the focus moves to support, stabilising the first month end closes, and preparing for SAP's regular updates. Many companies also start phase two scope here, such as additional entities or modules.
A Typical Timeline
The table below shows a common shape for a public edition project at a mid-sized Malaysian company with a few entities. These are typical ranges from our experience and published partner benchmarks, not fixed quotes.
| Phase | Typical duration | Main output |
|---|---|---|
| Discover and Prepare | 3 to 6 weeks | Scope, plan, team, provisioned system |
| Explore | 4 to 8 weeks | Fit to standard decisions, gap list, data and integration design |
| Realize | 8 to 16 weeks | Configured system, extensions, test data loads, user testing |
| Deploy | 3 to 6 weeks | Training, cutover, go live |
| Hypercare | 4 to 8 weeks after go live | Stable operations and first month end closes |
Put together, that is roughly four to nine months from kick off to go live. Private edition programmes and moves from older SAP ERP systems usually take longer because there is more to configure, convert and test.
Who You Need on Your Side
The single biggest predictor of a smooth project is not the software or the partner. It is whether the customer puts the right people on the project and gives them time to do it.
- Executive sponsor. Usually the CEO or CFO. Makes the hard calls when departments disagree.
- Project manager. Your own, working alongside the partner's project manager.
- Key users. One per main process area: finance, procurement, sales, inventory, production. They attend workshops, test and train others.
- Data owner. Someone responsible for cleaning customers, suppliers, items and balances.
- IT lead. Handles integrations, security, single sign on and the systems around the ERP.
Expect key users to spend a large share of their week on the project during Explore and Realize. If they are also expected to run their full day job, timelines slip. Some companies backfill routine work, or bring in support through IT outsourcing for the systems around the ERP.
Data Migration: Where Time Really Goes
S/4HANA Cloud projects in Malaysia rarely run late because of configuration. They run late because the data is not ready. A typical migration covers:
- Customer and supplier masters, including TINs and registration numbers for e-invoice.
- Item masters, units of measure, bills of materials and prices.
- Open sales orders, purchase orders and stock balances by location.
- Open receivables and payables, general ledger balances and fixed assets.
Historical transactions usually stay in the old system for reference. Start cleaning data in the Explore phase, not in the last month. Duplicate customers, inactive items and wrong tax details all have to be fixed before the first test load.
E-Invoice and Malaysian Requirements
E-invoice should be in scope from day one, not added after go live. S/4HANA Cloud uses SAP's own compliance tools or a partner connector to submit e-invoices to MyInvois, and the test cycle should include real scenarios such as credit notes, self billed e-invoices and consolidated e-invoices. The rules themselves are set out in the LHDN e-invoice guidelines. Our posts on MyInvois API integration and e-invoice setup mistakes cover what to test.
Also confirm early how SST, withholding tax and local statutory reports will be handled, and agree the plan for payroll. Payroll is usually run in a separate payroll system with postings to finance, so the interface needs to be designed and tested like any other.
What Drives Implementation Cost
| Cost driver | Lower effort | Higher effort |
|---|---|---|
| Entities and countries | One or two Malaysian companies | Many entities across several countries |
| Process fit | Mostly standard processes adopted | Many gaps needing extensions |
| Integrations | Bank and e-invoice only | E-commerce, warehouse, CRM, group reporting |
| Data | One clean source system | Several systems with years of messy data |
| Edition | Public edition | Private edition or conversion from older SAP |
Subscription fees are separate from implementation services and depend on users and scope. Ask any partner to separate the two clearly in their proposal, and to state what is excluded.
Common Mistakes We See
- Recreating the old system. Asking for every old report and screen defeats the point of moving to standard processes.
- Under staffing key users. Workshops without the people who do the work lead to wrong decisions and rework.
- Leaving data to the end. Data cleaning is the longest task on most projects.
- Treating training as a one day event. Users need practice in a test system with their own scenarios.
- Ignoring the update cycle. Plan who will test each SAP release before it reaches production.
After Go Live: Living With Regular Updates
On the public edition, go live is not the end of change. SAP releases updates on a fixed schedule, and every customer moves together. That is good news, because you get new features and fixes without running an upgrade project every few years. It does mean your team needs a simple routine.
- Read the release notes. Someone in finance and someone in operations should skim what is changing in their areas before each update.
- Test in the test system first. Run a short set of critical scenarios, such as creating a sales order, posting a goods receipt, issuing an e-invoice and closing a period.
- Check extensions and integrations. Anything built on top of the standard system, including the e-invoice connector, should be retested.
- Brief users. A short note or a fifteen minute session on screen or process changes saves a lot of support calls.
Many mid-sized companies ask their partner to run this cycle as part of an ongoing support arrangement. Whoever does it, put it in the plan before go live so it does not become an afterthought.
Questions to Ask Any Implementation Partner
Before you sign, ask each partner the same questions so you can compare answers fairly.
- Which edition do you recommend for us, and why not the other one?
- How many key user days will you need from us in each phase?
- Which of our requirements do you already see as gaps, and how would you handle them?
- Who on your team will run the fit to standard workshops, and have they done a Malaysian project with e-invoice in scope?
- What is excluded from the proposal, such as data cleaning, integrations or post go live support?
- How will you support us through the first SAP update after go live?
A partner who answers these clearly, including telling you what will be hard, is usually a safer choice than one who promises everything.
Is S/4HANA Cloud the Right Move?
For a single SME company, SAP Business One is often the more sensible choice; our SAP Business One implementation guide covers that path, and our SAP Business One page shows what it includes. For groups with several entities, regional operations or heavy reporting needs, S/4HANA Cloud is built for the job. You can read more on our SAP S/4HANA Cloud page, about Aspert's authorisation for SAP S/4HANA Cloud, and about the hosting choice in cloud vs on premise ERP.
Frequently Asked Questions
How long does an SAP S/4HANA Cloud implementation take in Malaysia?
For a mid-sized company on the public edition, a typical project runs around four to nine months from kick off to go live, plus a few weeks of hypercare. Private edition programmes and conversions from older SAP systems usually take longer. Data quality, scope and the availability of key users are the biggest factors.
What is SAP Activate?
SAP Activate is SAP's implementation methodology for S/4HANA Cloud. It has six phases: Discover, Prepare, Explore, Realize, Deploy and Run. It relies on preconfigured best practice processes and fit to standard workshops, where the business confirms how SAP's standard processes fit and decides how to handle real gaps.
What is a fit to standard workshop?
It is a session in the Explore phase where consultants walk your key users through SAP's preconfigured processes in a working system. Together you decide where the standard fits, where your process should change, and where a genuine gap needs an extension. It replaces long requirement documents and keeps the system close to standard.
Can S/4HANA Cloud handle LHDN e-invoicing?
Yes. S/4HANA Cloud submits e-invoices to MyInvois through SAP's compliance tools or a certified partner connector. E-invoice should be in scope from the start, with buyer TINs, registration numbers and classification codes cleaned during data migration, and credit notes, self billed and consolidated e-invoices included in testing.
How much customisation is allowed in S/4HANA Cloud?
The public edition stays close to standard. Changes are made through approved extensions and configuration, not by modifying the core, because SAP updates all public edition customers twice a year. The private edition allows more flexibility. In both cases, adopting standard processes where possible keeps projects shorter and upgrades easier.
What does our company need to provide for the project?
An executive sponsor, an internal project manager, key users for each main process area, a data owner and an IT lead. Key users need real time for workshops and testing, especially during the Explore and Realize phases. Projects without enough internal time are the ones that most often slip.
Planning an SAP S/4HANA Cloud project? We can review your scope, entities and data and give you a realistic timeline and team plan before you commit.
Plan Your S/4HANA Project