A purchasing manager at a two-plant manufacturer clears the queue of requisitions waiting on their signature.
Direction
Floorplan. List Report → Object Page, held together by a Flexible Column Layout. Fiori's default pairing, and the one floorplans.md says to reach for first.
Archetype. Split. Both halves stay live, so the queue never disappears behind whichever record the manager is deciding.
Data stance. Table-first. The queue is the product; the object page answers the one question a row raises.
Density. Cozy, at a 36px control and a 44px row. Not Condensed.
The one bold thing. The text/element split, shown side by side: a budget bar in --sapNegativeElementColor with its label beside it in --sapNegativeTextColor.
Generator
sap_tokens.py --both # produced tokens.css
sap_tokens.py --density
sap_tokens.py --semantic
sap_tokens.py --grep Duration
tokens.css is unedited: re-running --both reproduces it byte for byte (diff -q clean).
Why Cozy
--density reports Condensed at 22px control / 24px row and exits 1 while that stands, against SC 2.5.8's 24×24 floor. 2.5.8's Spacing exception wants a 24px-diameter circle on each undersized target's bounding box to clear its neighbours; in a packed queue with a checkbox in the first cell, it does not. Cozy clears the floor outright and serves touch as well as a mouse.
Measured in Chromium at 1440×900: control 36px, the single-line Items rows 44px, the queue's two-line item 52px (Cozy's two-line ceiling is 80px). Every target passes wcag_check.py --target at AA.
The two states
- The queue. Nine requisitions, with the first one open in the object page.
- A bulk approval that only partly lands. Check every row → Approve → a confirmation naming the count and the total → "6 of 9 requisitions approved. 3 need a second approver", each of the three named with what to do about it, the three remaining rows marked Held, and the object page switched to the first of them carrying its own reason and a changed primary action. This is the state
patterns.mdsays an enterprise bulk action owes the user, and the one a split floorplan makes hardest, because both halves have to agree afterwards. - The queue empty. Each held row's primary action names its own destination (the CFO office, 4712-FAC, Legal) routes it there and takes it off this desk, so three more clicks reach nothing. The list says Queue clear rather than reusing the search's copy, and the object column empties with it: a split whose right half keeps a live Approve on a record that has left the queue is telling the manager two different things at once.
Reject and Ask for information are real on both the toolbar and the object page; nothing on the page is an inert control.
The uplift pass
What the page does now that it did not:
- A dynamic page header. The object page's title bar is sticky. The expanded header (total value, needed-by, status, cost centres, a bullet chart) scrolls away under it; past it the bar snaps to a one-line title and subtitle, with hysteresis and a scroll-position compensation so nothing jumps. An anchor bar with Items, Budget and Approval chain tracks the section being read.
- Variant management. The filter bar's saved views (My queue, Everything open, Ingolstadt over 50.000 EUR) carry a
*when changed, with Save, Save as and a duplicate-name refusal. Filters sit in a collapsible bar; a chart over the queue plots each requisition by the day it is needed. - A responsive table in three tiers, by container width: every column, then needed-by folded under the title, then status folded in as well on a phone. The phone gets the floorplan's own phone variant: one column, a footer action bar and popovers as bottom sheets.
- Every record has its own object page. Line items, a budget meter per cost centre and the approval chain are computed from the data, not static.
- A posting that is checked before it is committed. Approve (one or many) runs a pre-flight against the signature limit, Legal's rule on multi-year commitments and each cost centre's remaining budget, in screen order with the budget already used by the rows above. The confirmation lists what will post and what will not, and why, and the single Approve uses the same function so the two cannot disagree.
- German locale. Amounts, quantities and dates follow the plants' locale: a point between thousands, a comma before the cents, day first, 24-hour clock. Money is integer cents throughout; "today" is fixed at 14.09.2026. All twelve requisition totals and the 439.220,50 queue total reconcile with their lines.
Deviations from CONTRACT.md §1
- No web font. SAP licenses the 72 typeface and Google Fonts does not serve it. The page takes
--sapFontFamilyas published, which falls through to Arial and Helvetica. - No icon font. SAP licenses that one too; every icon is inline SVG at
--sapContent_IconHeight. - This page authors its motion. Horizon's 1,537 parameters carry no duration, easing or transition (
--grep Durationprints an empty rule; Transition, Animation and Easing do the same). 100ms for a pointer state, 160ms enter, 120ms exit; reduced motion shortens all three to 1ms rather than deleting them. - This page authors its spacing on a 0.25rem grid, which Horizon does not tokenize either.
- Two attributes carry a hex because neither can hold a
var(): the favicon'sdata:URI (mirrors--sapBrandColor) and the initialtheme-color(mirrors--sapShell_Background, and script rewrites it from the live token on every appearance change).
Round two: the first screen
- The object page header is the focal moment. The open requisition's total is set at 1.5 times Horizon's Header1 (4.5rem), with the verdict beside it (a bar in the element red, its words in the text red). Under it the four items are stacked end to end on one scale, the 100.000 signature limit crosses them, and the 18.400 past it is drawn in
--sapNegativeElementColor. 29.100 + 19.650 + 41.650 + 28.000 = 118.400 is visible as shape. - Decisions in the header and the page footer. The footer says what Approve will do, from the same
check()Approve runs, and follows the button's label (Send to CFO once held). Phones keep the fixed bar. - Object status carries semantic colour. Waiting on you is information blue text and icon; Overdue, Held are inverted chips on the Horizon semantic grounds (
sapWarning/ErrorBackgroundand border). An over-limit row flags itself in the value column. - Contrast, measured. Overdue text (
sapCriticalTextColor) was 4.48:1 on the open row's selected ground and the neutral icon 2.89:1; both now sit on their own chip ground (4.84:1 and 6.67:1 light, 11.0 and 6.03 dark) or are plain information-blue text (4.75:1 worst case, light). - The queue chart is labelled. Taller, a dashed limit line, the overdue bar named, the open bar valued, and a bar's part past the limit in the mark red.
Round four
- Object page: the over-limit message keeps its red mark bar and red words but loses its pink fill and drops to body size, so the red budget bar is the one loud thing beside the title. The bar's labels sit on two lines (item, then amount) at body size, with room between segments.
- List: "Waiting on you" is the ordinary state and is no longer printed on nine rows; the column is "Exception" and a row shows a status only for Overdue, Held, Waiting on the requester or routed. The object page still states the status.
- Mini chart: the three in-plot labels on three baselines are one key under the chart (swatch in the mark colour, words in the text colour, one baseline): Overdue, the open requisition, Your limit.
Round nine: the approver's pass
Driven as the approver (select, approve under the limit, over the 100.000,00 EUR limit, reject, ask, multi-select, every popover and dialog, the three sections, expand and close), then at 360 and 390 on an emulated phone, at 200% zoom, in both themes and at 1920. Arithmetic re-checked from the data: nine rows sum to 439.220,50; items 29.100,00 + 19.650,00 + 41.650,00 + 28.000,00 = 118.400,00, 18.400,00 over; quantities times unit prices agree; 14.09.2026 is a Monday and no due date falls on a weekend.
- Reject and Ask for information carry words. Both used to commit on one click with nothing said to the requester and no way back. A dialog now asks for a reason or a question (required, with three one-click phrasings, a counter, an inline error, Escape and Cancel), for one requisition or a checked set. The reason shows in the confirmation strip; an asked requisition shows the question on its object page and reads "Awaiting reply" in the list.
- The section tabs no longer move the window. Items, Budget and Approval chain used
scrollIntoView, which also scrolled the page and slid the whole app up under the shell. They now scroll the column that owns the sections. - Focus stays somewhere. After a bulk approval, a reject or the last decision, focus went to the page body; it now lands on the open requisition's title, or the first row.
- The phone's fixed action bars leave when the design notes come up, so Approve and Reject no longer float over a section that is not the app.
- The smallest phones. At 360 the shell title broke inside a word and the list bar wrapped its filters onto a second row; the avatar steps aside below 400px. The shell icons keep 36px. The bullet bar's item labels drop the word "Item" before they clip. At 320 the readability swatches and the dialog's cost-centre table no longer overflow, and the contrast table stacks on a phone instead of hiding three of its four columns behind a sideways scroll.
- The wide screen. The object page's container query was declared on the element it styled, so it never applied; Budget and Approval chain now sit side by side once the column is wide enough (1920). With the object page closed, the queue splits requester and plant into their own columns.
- Quieter details. A held requisition's footer no longer repeats the strip above it; numbers and units in item names hold together on a non-breaking space.
Scores, ten heuristics 0 to 4: before 26, after 30. Below 3 after: help and documentation (2), because the page explains states only where they happen.
Boson
boson.mjs copies index.html alone into its run folder, so the linked tokens.css goes missing: run on the file as it stands it reports Times New Roman on 99.6% of the text, 21px-high buttons and "no focus indicator" on every control, none of which is the page. Run on a scratch copy with the tokens inlined, it reports the keyboard probe at 0 findings and no contrast or target findings. What remains is deliberate or out of scope: sticky bars inside the two column scrollers (that is the floorplan), four fixed leadings kept in rem for alignment, and launch checks (privacy policy, share image, 404 page) that belong to a site, not a specimen.
Round ten: help, and a way back
Scored first, ten heuristics 0 to 4, then driven as the approver at 1440, 390 and 360 (emulated phone), in both schemes. Round nine's one score below 3 was help and documentation (2): the page explained a state only where it happened. Fiori's own answer is a Help entry in the shell, an info button with a popover beside the term that needs it, a tooltip on every icon-only button, and keyboard paths for the decision.
- Help in the shell. A Help button (and
?) opens a popover that says how the queue works: what the limit, the Held mark and Undo mean, and the keys. Info buttons sit beside the three terms people ask about: the Waiting-on-you figure, the signature limit and the Budget section. - Undo after a decision. Every approve, reject, ask and bulk approval leaves a message strip with Undo that restores the queue as it was, until the next decision. On a phone the strip is scrolled into view, and its Undo drops under the text so the words keep the full width.
- Strips name what they hold. The partial bulk result lists each held requisition by title, number and amount. Approving a requisition that fails the pre-flight no longer errors: it routes it to its destination, says so, and moves on.
- Keys. Arrow keys move through the queue, Ctrl+Enter takes the primary action, and the primary button's label says what it will do before it is pressed. Icon-only buttons carry a styled tooltip on hover and on keyboard focus.
- Queue clear ends with a tally of what was approved, rejected, asked and routed.
Scores: help and documentation 2 then 3; the other nine held, so the total goes from 30 to 31 and nothing remains below 3.
Left: the Horizon semibold family falls back to Arial for visitors, so the weight-600 titles render at regular weight in the shell and the list. SAP licenses 72, so this is the page's stated deviation, not a defect to patch.
Round eleven (2026-11-10)
An independent reviewer scored 34/40 and found two severity-2 defects and one severity-1, all reproduced before editing.
- D1, a double press commits an unread requisition. At 1440, Approve on Calibration auto-opened the next requisition (Vacuum feedthroughs) with its Approve in the same spot and focus still on that button; a second press (Enter, Ctrl+Enter or a click) committed it unread. The same held for Send to CFO. Fix: every decision (approve, route, reject) now returns to the queue on every width, as the phone already did. The next row is marked and holds focus, the requisition column is closed and inert, and opening it is a deliberate act. The strip with its Undo sits beside the figure. A second Ctrl+Enter now changes nothing. No new rule: the one-column layout and the focus fallback were already in the page.
- Side effect found and fixed. Layout "one" on a wide screen left the page 36px wider than the window (the closed column's contents, which are zero wide and inert); it was latent behind the close button.
.fcl[data-layout="one"] .col--objectnow hascontain: paint; overflow is 0 at 1440 and 1920. - D2, the changed figure hides behind the sticky header on a phone. After a decision the window was scrolled to the strip (scrollY 311), leaving "Waiting on you" and the chart above the header. It is now scrolled to the figure, just under the list bar (scrollY 40), so 439.220,50 becoming 320.820,50, the chart and the strip with Undo are on one screen at 360 and 390. The same call serves Undo, reject, ask and bulk approval.
- Help popover reads as cut off (severity 1). The panel scrolls (about 1260px of text in 704px) and the thin scrollbar is easy to miss. Edge fades in
--sapContent_ForegroundBorderColornow show on whichever side has more to read and go when that end is reached. The three action buttons wrapping at 360 was noted and left.
Invented: nothing in the product. One layout rule (a decision returns to the queue), named above.
Round thirteen (2026-11-10)
An independent reviewer scored 35/40 and said it would ship, with one gap: "the split does not hold the next record after a decision." Reproduced at 1440 light: open Vacuum, Approve, and the object column closed, nothing was selected and the next record needed a click.
- The detail column follows the queue. Approve, Send to CFO / Legal / Controlling and Reject (one record, with the reason dialog) now move the open column to the record that followed the decided one. It stays marked (aria-current) and in view in the list, the strip with Undo sits beside the figure, and focus lands on the next record title, never on a button. Last record in the list: the one before it opens. Queue empty: the column closes and the list says Queue clear, as before. A decision made from the toolbar with the column closed leaves it closed and puts focus on the next row. A bulk reject that leaves the open record in the queue does not move it.
- Phone. Master and detail are one column, so after a decision the column shows the next record, with the strip and its Undo above it (the same strip is in the list behind Back). Undo from there restores the record in place instead of throwing the reader to the list. When the last record is decided, the list shows the figure and the strip as in round eleven.
- Round eleven stays true. The hazard it closed (a second press committing an unread record) returns the moment the next record opens under the same button, so a decision opens a 700 ms pause in which Approve, Reject and Ask for information (button, footer, Enter, Ctrl+Enter, tap) do nothing. Focus on the title, not on the button, is the other half.
- Reject, focus. The dialog used to hand focus back to the Reject button, which is now the next record button; a reject lands on the title instead.
Invented: nothing in the product. Two small rules, named above: the 700 ms pause after a decision, and the previous record opens when the last one was decided. Not changed: Ask for information keeps the requisition in the queue, so it stays open; a partly landing bulk approval still switches to the first held record.
Round fifteen (2026-11-10)
An independent reviewer found one severity-2 defect and four severity-1 notes. The severity 2 reproduced as reported before editing.
- D1, a slow second press signs an unread requisition. Round thirteen opened the next requisition under the same Approve and guarded it with a 700 ms pause; at 1440 light, Approve on Calibration, a wait of 700 ms and a second press at the same spot approved Vacuum feedthroughs (417.075,00 to 402.815,00 EUR, 8 requisitions to 7), and the phone did the same with Laser marking head. A clock cannot tell a second press from a deliberate one. Fix: a requisition that a decision opened is unread, and its Approve, Reject and Ask for information (header, footer, Ctrl+Enter, tap) are dimmed with aria-disabled and do nothing until the approver has had it in front of them, which is a scroll of the record, a wheel, touch or click inside it, or focus moving to a control in it that is not a decision button. The footer says why ("Not read yet. Scroll it or open a section, then decide."); on a phone, where the footer is not shown, the same line sits at the top of the action bar. A record opened from the queue is ready at once. The 700 ms pause is gone. Ctrl+Enter takes the same path as the button, so it is refused while the record is unread. Chosen over leaving the next record selected but closed: it keeps round thirteen's decision (the split holds the next record, which was the earlier reviewer's gap) and puts the reading, not the clock, between the two presses. Fiori has no approve-and-next rule of its own for this, so it is a page rule. The first record a partly landing bulk approval switches to is unread in the same way.
- Touch targets at 390 (sev 1). The row checkboxes stay 24px but their tap area is 44px square on a touch screen: the label is 44px and the box carries a 44px hit area; the check column is 44px wide at phone width.
- Reject and Ask wording chips (sev 1) were bare blue text; they are Default buttons with a border now.
- Not changed. The short budget bar labels only the item number at phone width (round nine's decision to drop the word before it clips); the header and footer repeating the three decisions is the floorplan's, and the footer is not shown on a phone.
Invented: nothing in the product. One page rule, named above: a requisition a decision opens is unread until the approver scrolls it, touches it or moves focus into it, and its decision buttons wait until then. The hint line is the one new string.
Round seventeen (2026-11-10)
An independent reviewer scored 36/40 and found one severity-2 defect and one remaining severity-1.
- D1, the empty object column after a bulk approve says the queue is decided. Reproduced at 1440 light, with a condition the report left out: the requisition that is open must be one of the ticked ones (open Laser marking head, tick it and Conveyor drive units, Approve, "Approve 2"). The column read "Nothing open. You have decided every requisition in this view." with seven requisitions still on the left. Fix: the column's text is now written from the queue. After a bulk decision it says how many that decision settled and how many remain ("2 requisitions decided just now. 7 requisitions are still waiting on you."), and offers a button to open the next one, the requisition that followed the open one in the list before the decision (Laser marking head, then Antistatic flooring, Bay 7, because Conveyor drive units was decided too). What the button opens is unread by round fifteen's rule: Approve, Reject and Ask for information are dimmed with the same footer line until the record is scrolled, touched or entered, and focus lands on its title. "You have decided every requisition in this view" now shows only when the queue is empty; with a search that hides every waiting record it says so ("None of them matches what you typed"). Checked against the queue count after single approve, bulk approve, reject, undo, a bulk approve of the last two, a bulk approve under a search, and the last record: the list's "Queue clear" and "Nothing matches that search" were already derived from the queue and agree.
- Severity 1, header and footer repeat the three decisions. Beside the page (above 900px) the decisions live once, in the footer bar, where Fiori puts them; the header copies are not shown. On a phone the footer is not shown, so the header bar stays the one set. The header buttons stay in the page as the handlers' target (the footer buttons click them), and
aria-keyshortcuts="Control+Enter"moved to the footer Approve. - Not changed, seen on the way. At 390 dark, after ticking two rows the bulk bar's Approve sits above the viewport (y -131 at scroll 548); identical on the committed file, so it is not from this round.
Invented: nothing in the product. Two small rules, named above: "decided just now" counts what the last undoable decision settled, and the next record offered is the one that followed the open one.
- Phone bulk bar out of reach (found in round seventeen, fixed after). At 390 dark and 360 light the selection bar was bottom-sticky, which holds only while its own place is below the screen; with rows ticked and the list scrolled past it, Approve and Reject sat at y -132 and could not be tapped (reproduced on the previous file at scroll 548, 800 and 1200). It is now the same sticky bar as on a wide screen, parked under the list bar, so Approve, Reject and Ask for information stay in view and tappable (rects in view and hit-tested at scroll 0, 300, 548, 700 and 800 at both widths); the table header parks under it (the list now measures the bar's height on a phone too). It had also been hidden whenever the design notes came into view, which is wrong for a bar that is no longer fixed. 1440 and 1920 are unchanged: bar at y 326 to 379, header at 379, same as before. Cost: about 97px of a phone screen while rows are ticked. No product change.
- Ticking a row moved the window (found in round seventeen, fixed after). Reproduced at 390 and 360 on a touch screen: at scroll 250 the selection bar appeared above the table and pushed the ticked row down 97px (y 319 to 416); at scroll 650 the redraw of the rows sent the window to scroll 88 and the row to y 1039, 659px away, so the second tap missed. At 1440 the bar is always in place and nothing moved. The cause is two things together: the bar changes the height above the rows, and every tick draws all the rows again, which removes the node the browser was anchoring on and the one that had focus. A tick, an untick and the select-all box now hold the touched row (for select-all, the row nearest the top of the screen) at the same viewport y by scrolling the difference back, on the page on a phone and on the list column beside the page, and the ticked box keeps focus. Measured with taps at scroll 250, 450 and 650 at 390 and 360, and at three depths at 1440 (the list there scrolls only 97px): the row is at the same y after tick and after untick, 0px off in every case.
Round nineteen (2026-11-10)
- Defect, reproduced (1440, 390, 360, 1920). In the header chart (value by item), a stretch under 3.5% of the 150.000,00 scale drops its label: the Class II biosafety cabinet showed only "10" under the bar and nothing for item 20 (1.500,00). The same held for seven other requisitions seen under "Everything open": Vacuum feedthroughs (three thin stretches, no label at all), Cable ties (three), Safety glasses, Antistatic flooring item 20 and 30, and the number-only labels on Calibration, Nitrogen and HEPA filters.
- Fix. A legend under the bar, in bar order, one entry per item: "Item 20" in the label colour and the amount in the semibold text colour (
#mcLegend,.mc__legend, filled byrenderMc). It lists every item whose stretch is under 13% of the scale, the same threshold at which the axis stops printing the amount, so each item has its amount either on the axis or in the legend, never twice and never neither. Where the column is narrower than 34rem the axis already drops the amounts, so the legend then names every item. A record with no thin item shows no legend above that width. Entries wrap onto a second row rather than overlap; the legend isaria-hiddenlike the rest of the chart, since the Items table carries the same values. When the axis has no labels at all, its 2.75rem row collapses (.mc__axis:empty). - Measured after the edit at 1440 light, 390 dark, 360 light and 1920 dark, for all eleven requisitions: no overlap between axis labels, legend entries and limit flags, every legend entry inside the viewport and below the bar, no horizontal overflow, no page errors.
- Invention. None in the product: item numbers and amounts are the ones already in the table. One display rule, named above: items under 13% of the scale go in the legend.
Round twenty-one (2026-11-10)
- Defect, reproduced (390x844, 360x800, 360x740). On a phone the decision bar of a record that a decision opened was 126px tall (15% of 844, 16% of 800, 17% of 740) against 57px for a record opened from the queue. Cause: the hint line took a row of its own, and a primary that names its destination (Send to CFO, Move to 4712-FAC, Send to Controlling) pushed Reject and Ask for information onto a second row. The same long primary also made a read record 101px at 360 wide.
- Fix, Fiori's footer-toolbar shape: one row. (1) An unread record's bar is the reason on the left, in words ("Not read yet. Scroll it, then decide."), and the dimmed primary on the right; Reject and Ask for information are not drawn while it waits, since they do nothing then, and come back the moment the record is read. (2) On a phone the Ask button reads "Ask" and keeps its full name for a screen reader (the rest of the words are visually hidden), so three buttons fit in one row beside the longest primary. Measured: bar 57px read and unread at 390x844, 360x800 and 360x740, with Send to Controlling and Move to 4712-FAC as the primary. 1440 and 1920 are unchanged (footer 57px, three buttons, full label); the footer message there is still the longer "Not read yet. Scroll it or open a section, then decide."
- Undo is a stack, not one slot (round twenty reviewer, sev 1). A second decision used to replace the first one's Undo, so the bulk approval could not be taken back after routing one held record. Each decision now keeps its own snapshot; Undo takes back the last, and the strip then says "Undone. ... Undo again to take back the one before." while earlier decisions remain. Checked: bulk approve of 9 (6 post, 3 held), route two, then Undo three times returns 3, 2, 9 requisitions and 439.220,50 EUR, at 1440, 390, 360 and 1920. The Help line for Undo says the same.
- Not changed. The Cozy 36px control size (the brief fixes it). The thin-segment tick labels on the bar.
- Invention. None in the product. Two page strings: the shorter unread line on the phone bar, and "Undo again to take back the one before."
- Clipped tick labels on the value bar (seen at 360 in round twenty-one). Reproduced on the committed file at 320, 360 and 390 for Calibration ("1 | 2( 3": item numbers cut by their own thin stretch, 20 overlapping 10) and four more records (a number cut by 2 to 13px). Cause: a label is boxed to its segment and clipped, and 3.5% of the scale is narrower than "Item 10" with its tick. Fix: after drawing, the axis measures each label against its stretch (the function fitMc, run again when the axis resizes). A label that does not fit drops its amount first, then is not drawn, and its item goes in the legend, so every item still has its number or its amount somewhere whole. When no label fits the empty axis row collapses. Measured text rects against their label boxes, each other and the limit flags, for all 12 requisitions under Everything open at 320, 360, 390, 1440 and 1920: 0 cut, 0 overlapping, 0 horizontal overflow, 0 page errors (the committed file showed 13 cut or overlapping cases). Phones now show the bar with the legend under it and no tick labels where the stretch is thin; 1440 and 1920 keep the ticks. No invention.