The Config Team Gives SAP Customers Three Ways to Structure AMS Support

The Config Team, an SAP supply chain specialist with nearly 30 years of implementation experience and an in-house team of more than 180 colleagues, has built its SAP Application Management Services practice around three separate commercial models rather than a single standard contract. The offering, delivered with 24/7 global availability, gives customers a choice between pre-paid hours, fixed-price managed service, and on-demand ad hoc support, a structure that lets support terms track a customer’s budget cycle and risk appetite rather than forcing every engagement into the same shape.

Three Ways to Structure SAP Support

The Hour/Ticket Bank Support model lets customers purchase hours or tickets in advance and draw on them as needed, giving full control over spend and usage while enabling rapid engagement when an issue arises. The SAP Managed Service model works differently: it sets a fixed price against clearly defined deliverables and responsibilities, a structure The Config Team positions as a low-risk, high-reliability option for ongoing structured support. Ad Hoc Support sits at the other end, offering pay-as-you-go resource augmentation for short-term staffing gaps or one-off needs.

Across all three models, SAP AMS work is organized into three pillars. Functional AMS covers logistics, planning, and finance issues, delivered by functional experts focused on long-term fixes rather than repeated patchwork. Technical AMS handles backend system work aimed at keeping SAP environments secure and scalable. Service Delivery Management adds a dedicated SDM who connects daily ticket resolution to broader account strategy. The support team also runs formal testing processes such as unit testing, user acceptance testing, and regression testing before changes reach a live environment.

Flexible AMS commercial structures of this kind reflect a wider pattern among SAP customers, who are increasingly looking to de-risk support spend as IT budgets face continued pressure. Formal testing disciplines such as UAT and regression testing have also taken on more weight industry-wide as SAP customers move toward more frequent release cycles under cloud-based SAP models, where an untested change can propagate faster than it would in a traditional on-premise environment.

Supply Chain Depth Beyond Issue Resolution

The Config Team’s AMS work sits inside a narrower specialization than general SAP support: inventory management, warehouse management, and extended warehouse management, extending to customers running greenfield EWM or S/4HANA migration projects. The specialization is reinforced by two proprietary products. PreBilt, a mobile solution used by more than 25,000 users worldwide, is built to work in network blackspots and across devices and operating systems, and can be deployed within days. CodingControl connects directly to SAP and integrates with one or multiple production lines, feeding real-time alerts and monitoring data through a central configuration cockpit.

Beyond the software, on-site consultants are available for system investigation, post-go-live support, and floor walking to handle day-to-day warehouse issues as they surface. The combination of packaged tools and embedded people reflects a broader industry pattern in distribution and manufacturing environments, where device-agnostic, mobile-first tools have become a common response to labor turnover and inconsistent network coverage on the warehouse floor. It also reflects a decision point many SAP customers face when adopting EWM or migrating to S/4HANA: whether to build internal support capacity from scratch or lean on an external team already fluent in the same modules, a choice sharpened for many organizations by the approaching end of mainstream ECC support.

What This Means for SAPinsiders

• Support contracts can now match budget cycles. SAP teams evaluating AMS vendors can select a pre-paid, fixed-price, or ad hoc commercial model based on how predictable their budget needs to be, rather than accepting one rigid contract type by default. The flexibility shifts more of the negotiation onto matching contract terms to internal finance planning.
• Formal testing steps reduce operational risk during changes. Structured UAT, regression, and load testing built into an AMS engagement lower the chance that a support fix causes problems in live warehouse or production processes. Teams relying on external AMS providers gain a documented checkpoint before changes reach the floor.
• External AMS can stand in for an unbuilt internal team. Organizations without an internal SAP function, including those that inherit systems through acquisition, can use a managed service model to gain EWM, ECC, or IBP coverage without immediate internal hiring. The option changes the timeline pressure on staffing decisions following a system handover.