Every order, including the deleted ones

A deletion flag removes an order line from the screen and leaves it in the table. May’s register holds 57 orders for 1,378,900.00 across three buying lanes, flags shown, birth dates beside invoice dates, nothing tidied away.

RuleBuild the order register from the raw lines, deletion flags included, so the register shows every order that existed, not every order still convenient.

Neveraudit purchasing from the list transaction. Flagged lines vanish from the screen and stay in the table; the screen is the version history forgot.

The register is purchasing’s ledger. Built from the raw lines it remembers everything, including what was flagged away.

◆ May orders, by buying lanethree lanes, one register.

Buying lane	Orders	Ordered value
Raw materials	24	812,400.00
Services and indirect	19	342,100.00
Capital equipment	14	224,400.00
Orders placed, May	57	1,378,900.00

Ordered value is commitment at birth; the open book tracks what remains of it as the receipts land. The register keeps every line ever placed, which is the property the next drill is about. Sample values are illustrative, never client data.

◆ Where the transaction lies by omissionflagged lines leave the screen, not the table.

A deletion flag removes a line from the list transactions and leaves it in the table, so a register built from screens understates what was ordered and by whom. The honest register reads the raw lines, shows the flag as a column, and lets the flagged-after-approval pattern surface.

◆ Orders born after their invoicesthe maverick measure.

Compare order dates to first invoice dates and a plant’s real approval culture appears: orders created after the spend existed are approvals in reverse. The pair of dates is on the landed lines; the delivered screens never put them side by side.

Use case

Problem

Purchasing audits read list screens, flagged lines disappear from history, and retro-created orders pass as process compliance.

What we build

The register from raw order lines: deletion flags visible, birth and invoice dates side by side, buying lanes and approvers trended.

What you get

Purchasing history that cannot be tidied after the fact: every line that existed, the flags that hid them, and the retro pattern measured.

How many of your orders were born after their invoices?

We build the register that puts the two dates together.

Talk to us

Terms on this page

SAP: The vendor. Systems, Applications, and Products in data processing.
HANA: SAP’s in-memory database, the platform S/4 runs on.
MM: Materials Management, the purchasing and inventory module.
EKKO: The purchase order header table.
EKPO: The purchase order line table the register reads raw.
LOEKZ: The deletion flag field; hides lines from screens, not from tables.
maverick spend: Buying first, papering later; measured by date pairs.