SAP Field Service Management

On the two questions a buyer actually asks: the name is current, and yes, it is still separately marketed. SAP still uses the string SAP Field Service Management verbatim in 2026. Its iOS app, published by SAP SE, carries version 26.10.0 dated October. SAP own learning course is titled Managing SAP Field Service Management. An SAP support knowledge article documents a planning and dispatching board behaviour change in the 2602 release. It has not been folded into SAP Service Cloud or S/4HANA Service. SAP own portfolio material draws the line explicitly: Service Cloud handles interaction with end customers through the agent console and ticketing, S/4HANA is the backbone for master data, logistics, financials and order handling, and Field Service Management covers planning and dispatching plus mobile execution, with its own cloud platform, web UI, mobile apps and release stream. The one real change is that SAP marketing has shifted the URL to a broader Field Service and Asset Management umbrella path, so the product name persists under a wider banner.

The Coresystems origin could not be confirmed on any SAP page. The circumstantial evidence is strong, though: SAP FSM help and knowledge content still lives on Coresystems domains. It is recorded here as circumstantial rather than vendor-stated.

Functionally, the dispatching board supports drag-and-drop assignment and release, reservations, absences and team planning, with manual, assisted and automatic assignment and skill-based matching. Autoscheduling is customisable to business criteria. Assisted planning aims to optimise resource utilisation and travel time, and a service map shows route total travel time and distance; note that this is travel-time optimisation inside assisted planning rather than an independently documented multi-stop optimiser. There is a customer self-service portal where customers view service calls and equipment and can create a call by scanning a QR code, which is a nice touch rarely found at this tier.

• Crowd service is the genuine differentiator. SAP describes a pool of certified and trained partners and third-party vendors available to respond to service calls. Native subcontractor dispatch of that kind is uncommon.
• Offline is claimed without qualification. SAP states native apps for iOS, Android and Windows with full offline capability, and the App Store listing says full offline support when out of mobile coverage. No contradicting SAP statement was found, so this is recorded as yes, but no SAP page enumerating offline limits was readable, so the word full is the vendor unqualified claim rather than a verified specification.
• Technician map visibility depends on technicians enabling GPS services on their own phones, which SAP states plainly.

Good fit: enterprise service organisations already standardised on SAP, specifically those running S/4HANA as the backbone and Service Cloud in the front office. SAP frames FSM as one of three solutions that integrate to deliver an end-to-end service process, which is honest but also means FSM on its own is only part of the picture. It is a strong fit where a meaningful share of field work is delivered by certified partners or subcontractors rather than employees, because crowd service handles that natively instead of through workarounds. Windows tablet fleets are also better served here than by most competitors, since SAP ships a Windows app alongside iOS and Android.

Poor fit: any organisation not already invested in SAP. The value proposition is contextual by SAP own framing, and standing FSM up without S/4HANA or Service Cloud behind it discards much of the reason to choose it. Also a poor fit for buyers who need documented offline limits before signing, because no SAP page enumerating them was readable and the claim is an unqualified full offline. Third-party aggregators list an SME option SKU; no SAP page confirmed it, so small and mid-market targeting is scored zero here.

Typical use cases: manufacturer installed-base service inside an SAP landscape, high-tech and equipment service with mixed employee and partner delivery, and enterprise service operations needing customer self-service call creation tied back to equipment records. Expect a quote-based commercial conversation; nothing is published.