FSA Shell extension

Altiwerk Studio

Four screen types, designed by your own people, running inside FSA next to everything else. No code, no deployment cycle, and no consulting round for the next small thing your team needs. It runs inside the SAP Field Service and Asset Management Shell (formerly SAP FSM), next to everything your team already uses.

Try free for 14 days Contact sales Compare options →

An equipment history as a single chronological stream: maintenance orders, installs and moves, service jobs and measuring points merged under month headings, each source a chip carrying its own count — The timeline presentation — four sources, one chronology, nothing copied anywhere

Four screen types

Pick the shape your problem already has

One install, four types. Your licence decides which appear — the ones you did not buy are simply not there.

Standard reports

A filter bar and the tables it drives — across FSA, your UDOs, and live S/4.

Answering a recurring question with parameters, where the answer spans more than one object.

12 capabilities

UDO screens

Your user-defined objects, with a real UI and two-way S/4 sync.

Data that lives in FSA as a user-defined object and needs more than the admin console gives you.

11 capabilities

SAP document screens

Header, items and sub-items — the shape a real business document has.

Anything quotation-shaped: a header with lines, optionally mirroring an S/4 document.

8 capabilities

Custom screens

A blank canvas, when none of the other three is the right shape.

A form that is entirely yours, stored as records without you designing storage.

4 capabilities

A standard report joining three sources into one result block, with a warehouse driver above it, per-column filters, and 102 rows paged fifty at a time — A standard report — one driver bar, and a result block joined across three objects

A UDO screen in table view showing 148 records, with per-column filters and a full toolbar of views, prefills, CSV, batch, compare, sync and new record — A UDO screen in table view

A SAP document screen listing service quotations with status tabs across the top, a driver filter bar, and a toolbar carrying views, prefills, CSV, batch, compare and Sync with S/4 — A SAP document screen — quotations, with status tabs and saved views

A custom screen — an equipment inspection laid out as two pages of sections, the equipment's own details answered on the first with the inspection checklist below it, each section paging through its entries, and tabs for history, timeline and export — A custom screen, laid out entirely by the team that built it

Whatever type you pick

What every screen inherits

Designing

A designer, not a code editor

Sections, pages and fields, each required, hidden, read-only or defaulted — configured by an admin, not deployed by a developer.

Rules instead of a rulebook

A field can show, hide, require or lock itself based on what somebody put in another field. The rule is a sentence you assemble — when this, then that — so the form guides people through it rather than a training document doing the work.

Caught at the keyboard, not at the write

Ranges, lengths, a pattern with your own error message, and checks that compare one field against another — all applied as somebody types. For fields bound to S/4, S/4's own validation still has the final say; this just stops the trip being wasted.

One field, three surfaces

The create form, the edit form and the viewer can each show a different set of fields, so what somebody fills in once is not what they stare at forever. Fields can also carry a default, or compute themselves from their siblings.

Search help across everything

Pick a record from an FSA object, a UDO or an S/4 value list, with partial matching done on the server so three letters is enough.

Bind any field to S/4

One field, fetched live, formatted, and with its value help scoped to the context it sits in.

Start from a verified mapping

A template gallery of starter screens, plus saved S/4 mapping templates you can reuse across screens.

Check the screen before your users do

Deterministic checks find broken bindings and missing fields; the AI layer proposes the repair.

Names are guarded at the moment you type them

FSA has no rename and no clean delete for a user-defined object, so a duplicate name is blocked and a shadowing field name warns — while changing your mind is still free.

Operating

Restrict who sees the designer

The workspace can be limited to chosen FSA policy groups or roles, so end users get screens and admins get the builder.

Downloads that reach the disk

An extension runs in a sandboxed frame that blocks downloads outright. Every export here routes around it, so the file actually arrives — a detail nobody notices until it is missing.

Looks like SAP built it

The Fiori Horizon design system, in light and dark, adapting from a full page down to a narrow record tab.

The same timeline screen rendered in the dark theme, with the light interface's spacing and colour relationships preserved — The Fiori Horizon design system, in light and in dark

Moving between tenants

Move a whole configuration between tenants

Export every screen design to one file and import it into another company. A read-only preflight shows collisions, renames, missing object references and S/4 dependencies before anything is written, then a progress panel names each step as it runs. The file carries the definitions of the objects your screens read, so the restore can create what the target company is missing.

The restore preflight — every screen in the backup listed with what would happen to it: imported as a copy so the existing screen is left untouched, which ones bring their own storage, and the S/4 services each one reads, with a note that imported screens arrive as drafts holding no records — The read-only preflight, before a restore touches the target tenant

One screen, two surfaces

The same screen, sized for where it runs

A screen has two lives: the full one in the workspace, and the cramped one inside an FSA record tab. Every piece of furniture around the data — cards, filter bar, toolbar, the buttons on it — is set independently for each, and each can be shown, collapsed or removed rather than merely switched off. Published screens start compact on their own, so this is the dial you reach for when you disagree with the default, not a form you have to fill in.

The Screen Settings dialog: each part of a screen's furniture — status cards, recent chips, toolbar, filter bar, header card, remarks — with Show, Collapse and Hide chosen independently for the standard surface and for the screen running solo inside an FSA tab, above a bulk-data section explaining why CSV upload does not apply to this screen — One screen, two surfaces — and three states per section, not a switch

Admin

Built by your power users, not us

The Admin tab lets your team create and configure screens directly in FSA. Pick a type, name it, set its status. No consulting engagement, no deployment cycle — your power users ship to your field users.

It is hidden for users whose role does not grant access, so end users only ever see the screens.

The admin screen list grouped by screen type, with a report open beside it — its driver field, and a result block whose three sources, joins and output columns are each spelled out — Every screen your team has built — and, beside it, how one of them is defined

The screen designer — header card settings beside a field table whose source column marks each field as custom or read from S/4, with AI suggestion and S/4 template actions — The designer — fields, their sources, and where each value comes from

And then

A screen your team built can become its own extension

A screen your team built is useful. A screen that appears on the equipment page, for the people who never open the studio, is a product. The factory turns one into the other — one click, one link, no second deployment.

Extension Factory

·One deployment, signed per-extension manifests — never a deployment per screen.
·Short install URLs, and 18 places a screen can appear — the Shell home screen among them.
·The screen picks up the record it is hosted on with no configuration.
·Expand into a full Shell modal from a small outlet.

Optional

Six AI tools, off until you turn them on

None of them is required, and the one people reach for most answers from a curated knowledge base before it ever calls a model.

Ask this screen

Everyone

Type what you want in your own words — “open orders in Hamburg from last month, newest first” — and the screen filters and sorts itself. What it did is shown as chips you can undo, English or German, and relative dates resolve against today.

Explain this error

Everyone

SAP errors are famously opaque. This answers from a curated knowledge base first — a verified answer, no model call — and only falls back to AI when the base has nothing. Most answers therefore work with no AI enabled at all.

What is this field?

Everyone

An explanation of any field, built from its metadata. No record data is sent.

Screen-building copilot

Admins

Proposes a mapping from your system's own metadata, so the first draft of a screen is not a blank page.

Generate a template

Admins

Drafts a new S/4 mapping template from a description of what you need.

Screen doctor

Admins

Suggests repairs on top of the deterministic checks, which always remain available.

How it is governed

·The engine decides whether AI is available at all, and which models may be used.
·The tenant turns individual tools on or off for everyone, and can pin a model per tool.
·Each screen can switch off the tools its users should not have.
·Nothing a screen enables can widen what the tenant or the engine allowed.
·Usage is counted per tool — calls, tokens and estimated cost — so spend is visible rather than discovered.

Pricing

Annual, per tenant — quoted on request

Single

One screen type

Quotedannual, per tenant

✓Choose Standard, UDO, or SAP
✓Unlimited screens within type
✓Per-tenant license
✓Email support

Contact sales

Dual

Any two screen types

Quotedannual, per tenant

✓Mix any two of Standard, UDO, SAP
✓Unlimited screens within types
✓Per-tenant license
✓Email support

Contact sales

Complete

All screen types incl. Custom

Quotedannual, per tenant

✓Standard + UDO + SAP + Custom
✓Bespoke layouts (Custom screens)
✓Per-tenant license
✓Priority email support

Contact sales

Note: the tier you buy determines what we encode in your license key. Same install regardless — screen types you did not license are hidden. The other products are licensed separately; see the family.

Entitlements at a glance

Which screen types each tier enables.

Screen type	Single	Dual	Complete
Standard reports	Optional	Optional	✓
UDO screens	Optional	Optional	✓
SAP document screens	Optional	Optional	✓
Custom screens	—	—	✓
Number of types enabled	1	2	4

Optional = your choice at purchase time. Single picks one of Standard / UDO / SAP; Dual picks any two.

Pricing FAQ

Common questions about how purchasing works.

How are licenses billed?

Annual contracts, invoiced once at the start of the term. Multi-year contracts get a discount — ask at the contact stage.

What about taxes and currency?

We quote and invoice in EUR, exclusive of VAT; reverse-charge applies inside the EU when you provide a valid VAT number.

Can we upgrade mid-term?

Yes. Upgrades are pro-rated against the remaining term. We issue a new license with the broader entitlements; you paste it in and the new screen types appear immediately.

What if we have multiple FSA tenants?

Each license is bound to a single FSA accountId. We discount additional tenants in the same contract — talk to us about volume.

Do you offer trials?

Yes — 14-day evaluation licenses on any tier. No credit card. Start a free trial.

What happens if we don't renew?

The license stops validating at the end of your term. Your data (screens, configurations) stays in your FSA tenant — we don't hold it. To resume, sign a new contract and we issue a fresh license.

Procurement / SAP Ariba support?

We work with procurement teams. Reach out and we'll fill out vendor onboarding forms, accept POs, and invoice on net-30 terms.

Get started

Ready to try Altiwerk Studio?

14-day trial license bound to your tenant. No credit card. No auto-bill.

Start a free trial Contact sales