What SAP AMS is — and why a ‘support contract’ is not enough
AMS is not a ticket queue. It is carrying live SAP with the close and the gazette. An SLA alone does not write culture.
Atilla Kuruüzüm · April 2, 2026 · 7 min read
AMS (Application Management Services) inflates in proposals as ‘24/7 support’. 24/7 is a phone ringing. AMS names who picks up, who sits the close, and how the same incident does not arrive a third time. This is a definition, not a magic SLA table.
The project ends; the system stays
When a transformation or rollout ends, hypercare is a few weeks. Then operations: period-end, bank files, an e-invoice communiqué, bad master, authorizations. If the project team says ‘yours now’, the knowledge leaves too. AMS binds that knowledge to a named team. The contract writes scope and priority. If it does not, everything is urgent and nothing finishes.
What an SLA measures — and what it does not
Response time is measured. Close quality is not — until reversals and repeat tickets are counted. Good AMS turns a repeating incident into a runbook or a fix. Bad AMS ‘solves’ the same Fiori dump every month. We do not invent a scoreboard; queue and repeat counts are enough.
The invisible half of AMS in Türkiye
The GİB calendar, an e-document outage, the inflation-run window, a DBS reject code. These are not ABAP dumps; they are calendar work. If the support contract only writes Priority-1 dumps, you are alone on close day. Write regulation and the close window into scope.
When is it AMS, when is it a project?
A new country, a new ledger, a new payment factory — project. A new approver, a new tax code, an index update — AMS. Mix them and every care item becomes a change request, or every project pretends to be ‘just support’ and hides risk. The line is drawn in discovery.
At Conforcus we call AMS a partnership because we do not sell ‘support’ we will not close with. The free analysis is to talk about where scope sits — not to mint a magic health score.
Frequently asked questions
How does AMS differ from regular consulting?
Consulting is project-based; it starts and ends. AMS is continuous: a named team that knows your system supports daily operations and period-end close against SLA targets, while also removing the root cause of recurring issues.
Do we need AMS if we already have an in-house team?
In most companies AMS is set up next to the in-house team, not instead of it. The in-house team carries business knowledge; AMS adds depth (module expertise, regulation, ABAP) and continuity (leave, attrition, period-end peaks).
How is AMS pricing determined?
Module scope, ticket volume, SLA tier and the extent of close support drive it. A sound proposal starts from a few months of real ticket data and the close calendar; a price quoted before scope is clear usually hurts one side or the other.