The same products, in the technician's hand.
5 of our products run inside the SAP Field Service and Asset Management (formerly SAP FSM) mobile Web Container, and install on the device as an app of their own. Not a cut-down sibling — the same code, the same licence, laid out for a phone.
What a technician gets
Exactly the products their licence carries — no more, and nothing they have to configure.
Warranty Checker
Is this repair covered? Equipment and a date give a verdict before the work starts.
Stock Checker
Live S/4 material availability, per plant and storage location — before anyone drives out.
Service Report Compiler
One activity becomes a branded PDF — and goes back onto the record as an attachment.
S/4 Live
Browse any live S/4 entity from inside FSA — no screen to build first.
Attachment Renamer
Rename attachments in bulk by pattern — with a history you can actually undo.
And screens you published
A screen turned into its own extension can target mobile, web, or both — so a report your team built in EasyScreenViewer reaches the phone too.
How that works →Three ways to point it at your people
Everything they own
Configure the Web Container with no product pinned and each technician sees a tab per product their licence covers. One configuration for the whole workforce.
One product, locked
Pin the container to a single product and it opens straight into it, with no navigation at all. This is what you want for a crew who only ever check stock.
A curated subset
Name the handful that team needs and the navigation shows exactly those. The licence still decides what is actually allowed — the list only narrows it.
It knows which record you came from
Set the container's object types and the host record travels with the technician: opening the checker from an equipment or an activity arrives already filled in and answered, rather than asking them to find the record again on a phone keyboard.
Honest about the session
Mobile sessions expire. When one does, the app says so and tells the technician to reopen it from FSA — rather than showing an empty list that looks like missing data. On a phone, in the field, that distinction matters more than it does at a desk.
Questions people actually ask
No. It runs inside the FSA mobile app's Web Container, so there is nothing to push through an app store or an MDM. It can also be installed to the home screen as an app in its own right, which is a browser feature, not a distribution channel.
Mobile is its own entitlement — the same products and screens inside the FSA mobile Web Container, as an installable app. You are not re-buying the products.
Yes — renaming attachments and attaching a finished report back onto the record both work on-device, and they are the flows most worth having there.
Products that read live S/4 data need a connection, by design — a cached warranty verdict is a wrong warranty verdict. Where an offline copy genuinely helps, the studio's snapshot pattern pulls the record into FSA first, and FSA's own offline behaviour takes it from there.
Put it on a phone this week.
A 14-day licence covers mobile too. Configure one Web Container and hand it to a technician.