One fictional manufacturer, Meridian Components, Inc., running one purchase-to-pay cycle across three company codes, four plants and four currencies. Each card is one finished object: the report that totals the orders, the interface that posts the invoices against them, the conversion that brought them in, the check before release, the printed order, and the approval that releases it. Open any of them and work the screens.
The six apps open on a Fiori launchpad in a new page of this site. The data is synthetic and the numbers below are read from it.
Monthly view of committed, invoiced and open spend by vendor and plant, in one reporting currency, with aging of open orders and drill-down to the order.
48 vendors, 12 months, 576 vendor-period rows: 9.81M USD committed, 3.12M USD open, 1.41M USD open over 90 days. Four currencies at month-end rates; a blocked invoice shows as blocked, not as paid.
Nightly invoice files from three vendors in three layouts (IDoc INVOIC, CSV, Excel), posted against the purchase order with a three-way match; exceptions go to a work queue, the run never stops.
3 runs, 340 invoices: 313 posted, 27 held with the reason on the row: duplicate invoice, price variance above the 2% tolerance, quantity above goods receipt, unknown order, currency mismatch. Case-to-each conversion applied on 8.
Bring 1,250 open purchase orders from two acquired plants' legacy systems into SAP: vendor and material cross-reference, unit of measure mapping, open quantity = ordered minus received, closed lines excluded.
1,250 records in, 1,203 posted, 21 held (unmapped vendors, the same order in both legacy systems), 26 closed lines excluded. 7.96M USD in, 7.85M USD posted, and every record shows its vendor, material and unit mapping.
Before a purchase order is released, check it against the cost-center budget and the outline agreement price; flag and route, do not block; no custom ABAP in SAP.
160 orders, 492 checks: 107 passed, 43 flagged, 10 routed as capital items. Each order page shows the rule, the result and the detail, with the items, the approval trail and the printed order beside them.
The purchase order document sent to the vendor: branding, terms, item table with delivery schedule, multi-page, in the vendor's language (English or Spanish), as an accessible (tagged) PDF.
12 documents in 4 currencies, 2 in Spanish, one 42-line order over 5 pages. Every PDF is tagged and opens from the order page or from the document list.
Route by value and category: under $10K the manager; under $100K add finance; $100K and above add the procurement director; capital items always the director; escalate after two business days; a rejection returns to the buyer with comments.
420 work items on 160 orders: 300 approved, 50 rejected and resubmitted, 58 escalated after two business days, 19 decided by a delegate. The decision history is on every work item.