SAP Implementation
A greenfield SAP build is decided in the fit-to-standard workshops, long before anyone configures a company code.
Why It Matters
SAP ships preconfigured standard scope items. We load them into a sandbox before the workshops start, so your process owners look at working screens instead of slides.
Modifying SAP objects is the reason older landscapes became impossible to patch. We keep the core untouched. Small logic goes in key user extensibility inside S/4HANA.
Value case, process scope, and a decision between public edition, private edition under RISE with SAP, or on-premise.
Several weeks of workshops on a loaded sandbox, producing a signed backlog of real gaps.
Configuration, BTP extensions, Fiori roles and integrations delivered in sprints with a demo at the end of each.
Unit, integration and user acceptance cycles, then at least two full mock cutovers on migrated data.
Cutover on a rehearsed plan, then daily support through your first month-end close in S/4HANA.
Every workshop decision recorded as a scope item accepted, adjusted or rejected, with the reason attached.
Company codes, plants, sales areas, purchasing organisations and the full module configuration behind them.
Masters and open items loaded with the SAP Migration Cockpit, reconciled against your legacy trial balance.
Business roles, catalogues and spaces built per job, so a warehouse operator sees six tiles and not six hundred.
Integration Suite interfaces to banks and third-party systems, and BTP extensions on released APIs.
Daily on-site or remote support through cutover and the first full month-end close, with a formal exit.
Quality gates at the end of every phase, and we will tell you when a gate should not be passed.
A deviation has to earn its place in front of your steering group, with a build cost attached.
No modifications to SAP objects. Extensions sit on BTP or in key user tooling, and they are registered.
If the public edition fits your processes, we say so, even though a private edition project bills more.
Launchpad roles built around what a person does in a day, which is what decides adoption.
A focused single-country, single-entity build usually runs 9 to 12 months. Multiple legal entities, several plants or heavy integration work push it towards 18 months. The Explore phase alone accounts for several weeks of fit-to-standard workshops, and we will not compress that part, because every week skipped there turns into a change request later.
It means you start from a working system rather than a blank one. SAP ships preconfigured standard processes, we load them into a sandbox in the Prepare phase, and in Explore your process owners sit in front of the real screens and confirm or reject each step. Your job is to attend those workshops and make decisions. Activate fails when the business sends delegates who cannot sign anything off.
Public edition gives you a two-release-per-year upgrade cadence, a lower running cost and a hard limit on how far you can customise. Private edition, usually bought through RISE with SAP, keeps classic ABAP access and a slower upgrade schedule. If your processes are close to standard, the public edition constraint is doing you a favour, because it stops the modifications that make upgrades expensive. If you have genuinely differentiating manufacturing or industry logic, private edition is the honest answer.
Most of them, yes, and that is usually a win. In fit-to-standard we walk your process against the SAP standard and you justify every deviation in front of the group. Typically 80 to 90 percent of what looks custom is habit inherited from an older system. The remainder is real, and that is where the build effort and the extension budget should go.
It means they stop modifying SAP objects and start building against released APIs instead. Extensions live on SAP BTP, in CAP or ABAP environment services, or as in-app key user extensions inside S/4HANA. The skills carry over, RAP and CDS are still ABAP, but the habit of changing standard code has to go. That single discipline is what decides whether your next upgrade costs two weeks or two quarters.
We run hypercare through your first full month-end close in S/4HANA, because that is when the gaps in the chart of accounts, the tax setup and the reconciliation reports actually show up. Our team sits with finance and operations daily during that period. After the close is signed off, you move onto a support contract or take it in-house with the documentation we hand over.
Related
The other services in this section, and related pages from TCB Infotech.
No commitment. A practical first look at your S/4HANA programme.
