Portfolio

Requisition approvals Purchasing for the Ingolstadt and Neckarsulm plants

Stefan Aigner, purchasing

Requisitions

9 waiting on you
Status Waiting on me Value Over €10,000 Plant Ingolstadt Plant Neckarsulm

No rows checked

Requisitions waiting for your approval
Requisition Value Status

Cleanroom filtration retrofit, Hall 3

4500019827 · raised by Marija Novak on 8 September

Total value
€118,400.00
Status
Waiting on you
Cost centre
4711-PROD · Production hall 3
Needed by
24 September 2026

Items

The four line items on requisition 4500019827
Material or service Qty Unit price Net
HEPA filter bank H14, 610 × 6106 EA4,850.0029,100.00
Fan filter unit, EC motor, 1,200 m³/h6 EA3,275.0019,650.00
Ducting and plenum modification1 LOT41,650.0041,650.00
Commissioning and airflow validation1 LOT28,000.0028,000.00
Net total, EUR118,400.00

Budget

4711-PROD Production hall 3
Annual budget
€520,000
Committed with this one
€581,400
€61,400 over
€0Budget €520,000
4712-FAC Facilities
Annual budget
€310,000
Committed
€188,600
€121,400 left
€0Budget €310,000

Approval chain

  1. Marija Novak · raised it 8 September, 09:14
  2. Dr Elke Brandt · plant engineering Approved 9 September, 16:02
  3. Stefan Aigner · purchasing Waiting since 9 September
  4. CFO office Every requisition over €100,000 goes here

Approve 9 requisitions?

This commits €439,220.50 against the cost centres named on each one. Approvals post to the ledger and cannot be withdrawn here.

Anything over your €100,000 signature limit stays open and goes to the CFO office.

Design notes

Shape of the page
A split: the queue of requisitions beside the one somebody has opened. This is SAP's own default pairing, and both halves stay live, so deciding about one requisition never hides the queue behind it.
What it leads with
The queue. That is the product; the panel beside it exists to answer the one question a row raises.
Spacing
SAP's comfortable setting rather than its compact one. Compact fits about a third more rows, which is tempting on a queue, but its rows are too close together for a reliable tap or click, especially where the first cell holds a checkbox.
The comfortable setting clears the accessibility floor for target size outright, and serves a touch screen as well as a mouse.
The one bold decision
Two reds, side by side under Budget. SAP publishes one red for a drawn mark and a darker one for words, and the difference matters: use the mark red for the label and it falls short of the readable floor. Most screens use whichever one they measured first.

Where the colour comes from

Every colour on this page is SAP's own published Horizon set, taken from the system rather than sampled by eye. Nobody wrote a colour by hand.

Readability, measured

Every pair measured against the exact published values, in both themes. Higher is easier to read.
What sits on whatThemeRatioFloor
The words beside the budget barlight7.64:14.5, passes
The words beside the budget bardark5.24:14.5, passes
The budget bar itselflight3.90:13, passes as a mark
The budget bar itselfdark5.24:13, passes as a mark
The title of the open row, on the hardest surface it lands ondark6.23:14.5, passes
Every field label and row subtitlelight5.51:14.5, passes
Every field label and row subtitledark5.20:14.5, passes

Two findings worth keeping. In the dark theme SAP's two reds are the same colour, so a screen that confuses them looks perfectly fine there and fails in the light theme. And a row title measured only against a plain row passes, while the same title on a selected row does not, because the dark theme makes a selected row lighter rather than darker. A text colour has to be measured against every surface it lands on, not the usual one.

What we changed

  • SAP licenses its own typeface and its own icons to its own customers, so this page loads neither. It takes the fallback stack SAP publishes, and every icon is drawn rather than set in a font.
  • SAP publishes no timings for its animation, so the page sets three of its own: a fast one for hover, and slightly different ones for something arriving and something leaving. A reader who has asked their computer for less movement gets all three shortened rather than removed, which keeps the interface behaving normally.
  • SAP publishes no spacing scale either, so the page sets one on a regular grid.