Altiwerk
Screen type

UDO screens

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

LicenceUDO screensUnlimited screens of this type
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
Reach for it when

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

What it does

  • Table or card view, with a filter bar, per-column filters, sort, drag-to-reorder and hidden columns.
  • Create, edit and delete records without leaving FSA.
  • Sync with FSA: refresh the values this screen copied from other objects when they change.
  • Sync with S/4: pull records in — newest N or all — creating what is missing and refreshing what drifted, deleting nothing.
  • Records S/4 does not know are listed rather than silently dropped.
  • Push back to S/4 with live progress, one row per write, and inline conflict resolution.
  • A rejected write is re-planned into atomic units, so one bad field does not lose the rest.
  • Bulk CSV import: fill a spreadsheet, review what will change before anything is written, then undo the whole import if it was wrong.
  • Excel-proof files — semicolon-separated exports, umlauts, leading zeros, and no cell that can execute as a formula.
  • Batch delete that asks once, shows progress, can be stopped cleanly, groups the failures by reason and retries just those.
  • Screens scope themselves to the record whose tab they are opened in.

What people build with it

  • An inspection register kept in FSA but reconciled against S/4
  • Per-site equipment attributes your team maintains
  • A parts-used log that pushes back into the order
In the app

What that looks like

The same UDO screen in card view, one card per record
…and the same screen in cards, which suits a narrow record tab better
The Sync with S/4 dialog, offering the latest N records or all of them, and stating that S/4 wins and nothing is deleted
Pulling from S/4 says what it will do before it does it
The bulk CSV preflight, counting six new rows, three updates, three unchanged and no errors before anything is written
Bulk CSV — what will change, counted, before a single row is written
The result of a CSV import — six created and three updated — with an Undo this import action
…and the whole import can be walked back afterwards
A batch delete confirmation listing the record ids it is about to remove and warning that forty deletions cannot be undone
Batch delete asks once, and shows you exactly what it holds
A batch delete in progress — seven of forty records at eighteen percent, with elapsed time, an estimate of the time left, and a Stop button
…runs with real progress and an honest estimate, and can be stopped
The tally after a batch delete: forty records deleted in 12.3 seconds, about 0.3 seconds each
…and ends with a tally rather than a silent refresh
Get started

Build a udo screen this week.

A 14-day licence covers every screen type, so you can find out which of the four your problem actually is.