Glossary

The SAP Field Service and Asset Management (formerly SAP FSM), S/4 and licensing terms used across these docs, in plain English.

FSA#

SAP Field Service and Asset Management — SAP's cloud platform for field service operations (service calls, activities, technicians, equipment). This is the product's current name.

FSM#

The previous name of the same product — SAP Field Service Management. SAP renamed it to Field Service and Asset Management (FSA); our docs use FSA throughout. Nothing technical changed with the name: the API hostnames and the `@sap/fsm-shell` SDK still carry it.

FSA Shell#

The web UI your users work in. Extensions load inside the Shell as iframes, alongside the standard screens.

Web Container#

The FSA mobile app's host for extensions. The same products run there, and can also be installed on the device as an app.

Extension#

A third-party app that plugs into the FSA Shell. Installed by an admin via Foundational Services → Extensions.

accountId#

A numeric identifier for an FSA tenant. Our license keys are bound to a specific accountId so they can't be used on a different tenant.

Cluster#

An FSA data centre region — usually `de`, `eu`, or `us`. Your tenant lives on exactly one cluster (e.g. `de.fsm.cloud.sap`; the hostname still carries the old name).

UDO (User-Defined Object)#

A custom record type your FSA admin defines to store data outside FSA's built-in objects. UDO screens turn one into a real screen — browse, create, edit, delete, sync with S/4 and import in bulk.

UDF (User-Defined Field)#

An extra field added to a standard FSA object. UDFs are offered wherever you pick a field, so your own fields appear alongside SAP's.

Outlet#

A defined spot in the FSA Shell where an extension can render — a tab on a record, a panel under a detail page, or the Shell home screen. A screen published as its own extension can target 18 of them.

Install parameter#

A value an admin provides when adding an extension — like a license key. FSA passes install parameters to the extension at runtime.

Foundational Services#

The admin section of FSA where extensions, users and account settings are managed. Find it from the main FSA landing page.

Standard Report#

A screen type that queries FSA objects (service calls, activities, business partners…) with drivers, filters and joins — and can put a live S/4 block beside them.

SAP document screen#

A screen type shaped like a document: header, items and sub-items. Optionally a live projection of an S/4 entity, with changes pushed back.

Custom screen#

A fully bespoke screen with a layout you define entirely. Entries are stored as UDO records. Available on the Complete SKU.

Smartform#

FSA's checklist/form template, filled in by technicians on a job. Checklist Manager manages the templates: versions, usage, differences between versions and translations.

OData#

The protocol SAP exposes S/4 services over. Our engine speaks both V2 (the older SEGW services) and V4 (RAP), so it works either side of SAP's own migration.

Entitlement#

A capability granted by a license — one per screen type and one per product. Your licence carries exactly the ones you bought.

Seat#

One person using a licence, counted over an activity window. One human is one seat across laptop, phone and a second browser; someone who stops using it releases theirs automatically.

Engine licence#

A separate signed licence for the connectivity engine you run on your own BTP. It renews a short lease against our service, so a contract can end without you redeploying anything.

SKU#

A specific product configuration we sell. For the studio: Single (one screen type), Dual (two), or Complete (all four).

License JWT#

A signed JSON Web Token that encodes your entitlements, accountId and contract expiry. Our backend verifies the signature server-side on every validate call.

Ed25519#

The signing algorithm we use for license keys. Modern, fast, and not subject to the RSA key-size escalation cycle.

Revocation#

Marking a license as invalid before its natural expiry. Useful after a suspected leak. Takes effect within an hour as customer caches expire.