The Buyer's Start Center: The Desk That Runs Itself Before the Backlog Buries You
🎯 Who this is for: Buyers, procurement specialists, and purchasing supervisors on go-live morning, plus the admins who deploy the buyer Tier 0 pack — anyone who will open MAS 9 to find the migration dumped three thousand requisitions and a full inbox of stale approvals.
Series: Part 6 of 10 — MAS 9 Supply-Chain Playbook | Read time: 24 minutes
🖥️ The Buyer Desk Has Its Own Tier 0
The storekeeper's first hour (Part 1) has a buyer twin, and it is exactly as decisive.
A buyer who logs into MAS 9 on go-live morning without a starter pack meets a specific kind of chaos: an empty Start Center, three thousand requisitions sitting in ENTERED status because the 7.6 queues migrated wholesale, an inbox full of stale workflow approvals nobody triaged, and a Company master with fourteen thousand vendors and no obvious way to find the active ones. That is how a MAS 9 rollout produces a PO-processing backlog that lasts a quarter.
The fix is the same shape as the storeroom's: a BUYER_HOME Tier 0 pack deployed before anyone logs in — a locked Start Center template of work-queue result sets and KPIs, backed by eighteen public saved queries scoped by buyer code, plus the inbox hygiene and cleanup routines that clear the migration mess in an afternoon. It is all out-of-the-box. It is the highest-leverage hour of the buyer's rollout.
<aside>
💡 Key insight: The buyer's Start Center is a work queue, not a dashboard. Where the storekeeper's screen answers "do I need to act?", the buyer's answers "what do I act on next?" — the oldest unsourced PR, the latest PO, the RFQ awaiting reply. Order the result sets by urgency and the buyer works top to bottom instead of hunting.
</aside>
📊 The Seven Work-Queue Result Sets
Seven result-set portlets, in a left column ordered by urgency, put a buyer's whole desk on one screen:
| Slot | Portlet | Source query (app) | Refresh |
|---|---|---|---|
| L1 | My Open PRs — Ready to Source | PR | 10 min |
| L2 | POs Past Required Date — Expedite | PO | 15 min |
| L3 | My Active RFQs | RFQ | 30 min |
| L4 | PRs Older Than 14 Days — Unsourced | PR | daily |
| L5 | Contracts Expiring in 90 Days | Contract | daily |
| L6 | POs With Invoice Mismatch | PO | 30 min |
| L7 | My POs With Partial Receipts | Receiving | 1 hour |
Each answers a buyer question: what needs sourcing now (L1), what is late and needs expediting (L2), what am I waiting on vendors for (L3), what is aging unsourced (L4), what renewals are coming (L5), what invoices are stuck (L6), and what is half-received (L7). The refresh cadence tracks how fast each moves — the ready-to-source queue every ten minutes, the ninety-day contract list once a day.
🎯 The Five KPI Tiles
Five KPI tiles, in the right column, give the buyer and the procurement manager an at-a-glance pulse of the desk:
| KPI | Measures | Metric |
|---|---|---|
| Open PR Value ($) | Unsourced commitment | SUM(totalcost) of APPR, unsourced PRs |
| Open PO Value ($) | Committed spend in flight | SUM(totalcost) of APPR/INPRG POs |
| PO Cycle Time — 30d avg | Buyer's headline metric | Avg days from PR approved to PO issued |
| Invoice Match Rate | Match-pay health | Matched / total invoices this month |
| RFQs Awaiting Reply | Sourcing pipeline | COUNT(*) of SENT RFQs |
Traffic-light thresholds
| KPI | Green | Yellow | Red |
|---|---|---|---|
| PO Cycle Time (PR approved → PO issued) | ≤ 3 days | 4–7 | > 7 |
| Open PR Value — drift from baseline | ±10% | ±10–25% | > ±25% |
| Invoice Match Rate | ≥ 95% | 85–94% | < 85% |
| RFQs Awaiting Reply | ≤ 5 | 6–15 | > 15 |
| Contracts expiring < 30 days, uncaught | 0 | 1–2 | > 2 |
PO cycle time is the one a procurement manager watches hardest — it is the buyer's single most important number, and a red here means requisitions are aging into POs too slowly.
🔑 The :BUYER and :SITEID Bind Variables
Exactly as the storeroom uses :STOREROOM, the buyer desk uses :BUYER and :SITEID so one template serves every buyer. Each query resolves :BUYER to the logged-in buyer's code and :SITEID to their purchasing site, so buyer BUYER01 sees BUYER01's PRs and buyer BUYER02 sees BUYER02's — from the same template with no per-user editing.
For the parameters to resolve, every buyer needs a buyer code and a default purchasing site on their People record. A blank buyer code is the buyer-side version of the storekeeper's blank default storeroom: the queries are fine, but the "My Buyer" filter returns nothing, and it looks like the pack failed.
<aside>
⚠️ Watch out: "My Open PRs returns nothing" after go-live is almost always a blank buyer code on the person record, not a broken query. It is the number-one buyer Tier 0 defect — verify buyer codes before you build the template.
</aside>
🗂️ The Eighteen Starter Queries
The admin creates these in Query Manager, marks them Public, and sets one Default per app. All use ANSI SQL that runs on Db2 and Oracle.
Purchase Requisitions and Purchase Orders
| Query | App | WHERE clause |
|---|---|---|
| My Open PRs — Ready to Source (Default) | PR | status = 'APPR' AND buyer = :BUYER AND ponum IS NULL AND siteid = :SITEID |
| PRs Older Than 14 Days — Unsourced | PR | status = 'APPR' AND buyer = :BUYER AND ponum IS NULL AND changedate < SYSDATE - 14 |
| PRs Requiring RFQ (high-value, no contract) | PR | status = 'APPR' AND buyer = :BUYER AND totalcost >= 5000 AND ponum IS NULL AND contractrefnum IS NULL |
| My Open POs — Awaiting Receipt (Default) | PO | status IN ('APPR','INPRG') AND buyer = :BUYER AND siteid = :SITEID |
| POs Past Required Date — Expedite | PO | status IN ('APPR','INPRG') AND EXISTS (…requireddate < SYSDATE AND receivedqty < orderqty…) AND buyer = :BUYER |
| POs With Invoice Mismatch | PO | status IN ('APPR','INPRG') AND ponum IN (SELECT ponum FROM invoice WHERE status = 'WAPPR') AND buyer = :BUYER |
RFQ, Vendors, Contracts, Receiving
| Query | App | WHERE clause |
|---|---|---|
| My Active RFQs (Default) | RFQ | status IN ('INPRG','SENT') AND buyer = :BUYER |
| RFQs Past Reply Date — No Response | RFQ | status = 'SENT' AND replyduedate < SYSDATE AND buyer = :BUYER |
| Active Vendors With Missing Tax ID | Company | disabled = 0 AND (federalidnum IS NULL OR TRIM(federalidnum) = '') AND type = 'V' |
| Duplicate Vendor Candidates (same tax ID) | Company | federalidnum IN (SELECT federalidnum FROM companies GROUP BY federalidnum HAVING COUNT(*) > 1) |
| Contracts Expiring in 90 Days | Contract | status = 'APPR' AND enddate <= SYSDATE + 90 AND buyer = :BUYER |
| My POs With Partial Receipts | Receiving | EXISTS (…receivedqty > 0 AND receivedqty < orderqty…) AND buyer = :BUYER |
That is a representative dozen of the eighteen; the full set adds PRs-awaiting-your-approval, POs-awaiting-approval, POs-closed-this-month, RFQs-due-today, active-vendors-used-in-24-months, and contracts-auto-renewing-this-quarter. Mark them all Public or they vanish from the group's Result Set picker.
📥 Inbox Hygiene: Bulk Approve, Reject Comments, Delegation
The Inbox in the top bar holds workflow approvals for PRs, POs, invoices, contract changes, and over-threshold adjustments. In 7.6 many buyers ignored it and approved by email; in MAS 9 the inbox is the sanctioned path, and it is genuinely better.
- Bulk approve. Select multiple items with the checkboxes and approve all with a single comment — ten PRs in one click.
- Required reject comments. The Comments field is required by audit on a reject; no silent rejects.
- Reassign. Hand this decision to another approver — but note the reassignment does not change the workflow route; the next step still goes where the workflow says.
Delegation — set it up Day 1
Coverage for PTO is a first-class feature, not a password-sharing hack. On Labor → your record → Delegation tab, enter a delegate with start and end dates. During the window, your inbox items also appear in the delegate's inbox. Email approvals still work for backward compatibility, but their audit trail is weaker — turn them off when the organization is ready, typically ninety days post-upgrade.
<aside>
💡 Key insight: Email approvals are audit-hostile — there is no Maximo-side trail of who clicked what. Moving buyers to inbox approvals is not a UI preference; it is the difference between an auditable approval history and a mailbox archaeology project. Make the inbox the only sanctioned path and set delegation up before the first PTO.
</aside>
🧹 The Migration Cleanup
Most 7.6 migrations arrive with a thousand-plus stale PRs, five hundred-plus open POs that should have closed, and hundreds of POs held open by a single unreceived line. The Tier 0 queries plus a few bulk actions clear it in an afternoon.
PR cleanup, worked
- Run PRs Older Than 14 Days — Unsourced.
- Triage into four buckets: still needed (source today), cancel (contact requestor), consolidate (batch to the same vendor), escalate (to the procurement manager).
- Cancel directly: select → Change Status → CAN with a comment like "Cancel — superseded by PR/PO XYZ."
PO cleanup, worked
- Run POs Past Required Date — Expedite.
- For each: contact the vendor for an ETA, short-receive and close if delivery is impossible, or cancel unshipped lines via the PO line's Cancel Line action.
- Close: Change Status → CLOSE — which requires zero open lines and all received lines matched to invoice. PO close is irreversible in the UI, so settle receipts and invoices first.
The orphan-line pattern is worth naming because it is so common: a PO received nine of ten units eleven months ago, the vendor never shipped the last one, and nobody closed the PO — so it sits open, holding the whole order in limbo and distorting your open-commitment reports. Short-receive it, close it, move on. Multiply that by a few hundred and you understand why the open-PO list arrives so long.
An admin can back this with cron tasks that auto-close fully-received-and-invoiced POs over an age threshold, and auto-cancel PR lines referencing disabled items. The goal: open PR count over thirty days under twenty, open PO count over 180 days (excluding blankets) under fifty.
📎 Attaching Sourcing Evidence the Right Way
Every purchasing object — PR, PO, Contract, Company, Invoice — has an Attachments section, and disciplined use of it is what makes an audit find zero gaps. Attach the quote to the PR, the signed contract and insurance cert to the Contract, the W-9 to the new vendor.
| Object | Required attachments (recommended policy) |
|---|---|
| Non-contract PO ≥ $5k | Original quote + RFQ scores + vendor W-9 |
| Contract | Signed contract PDF + insurance cert + SOW |
| New vendor (Company) | W-9, insurance cert, supplier qualification form |
| Invoice > $10k mismatch | Vendor copy + internal reconciliation memo |
Set a Document Type (QUOTE, CONTRACT) and a Folder so attachments are searchable by description, not just filename. One MAS 9 behavior to know: Copy PO copies attachments by default now — in 7.6 that was a toggle — so when you clone a PO, make sure you are not re-sending last year's vendor quote.
⏱️ The 60-Minute Buyer Deploy
One admin, roughly an hour, before go-live:
| Min | Step |
|---|---|
| 0–15 | Verify BUYER/BUYER_SUPV/PROCUREMENT_MGR groups; confirm every buyer has a buyer code and purchasing site |
| 15–35 | Create the eighteen starter queries in Query Manager; mark Public, set Default |
| 35–50 | Build the BUYER_HOME template — seven result sets, five KPIs, Favorites, Inbox |
| 50–57 | Assign to the buyer groups; default on first login |
| 57–60 | Log in as a test buyer; confirm queries return data and KPIs compute |
Run the two-buyer smoke test (BUYER01 and BUYER02 show different numbers) for the same reason the storeroom does — it is the only step that catches a hard-coded buyer code.
🔧 Troubleshooting the Buyer Start Center
| Symptom | Cause | Fix |
|---|---|---|
| "My Open PRs" returns nothing | Blank buyer code on person record | Populate buyer code + purchasing site |
| Result set empty for everyone | Bound query left Private | Re-mark Public |
| Inbox is blank after migration | Workflow reassignment cron didn't run | Admin re-runs workflow reassignment |
| Cloned PO re-sent an old quote | Copy PO now copies attachments by default | Review attachments before issuing |
| PO won't close | Open lines or unmatched receipts remain | Cancel/short-receive lines, match invoices |
🎓 The Commandments of the Buyer Desk
- Thou shalt pre-load BUYER_HOME before the migration backlog buries the desk.
- Thou shalt scope by `:BUYER` and `:SITEID`, and set every buyer's code.
- Thou shalt order result sets by urgency — the desk is a work queue.
- Thou shalt approve from the inbox, not from email, and set delegation Day 1.
- Thou shalt clear the migration mess with the aging queries and bulk actions.
- Thou shalt attach sourcing evidence so audits find zero gaps.
Key Takeaways
- The buyer desk has its own Tier 0 — a BUYER_HOME template plus eighteen public saved queries, deployed before the migration backlog arrives.
- Seven urgency-ordered result sets and five KPIs put the whole desk on one screen, with PO cycle time as the headline metric.
- The `:BUYER` and `:SITEID` bind variables personalize one template — provided every buyer has a code and purchasing site.
- Inbox hygiene beats email approvals on audit trail; bulk approve, require reject comments, and set delegation Day 1.
- The Tier 0 queries plus bulk actions clear the migration mess — stale PRs, open POs, orphan lines — in an afternoon, and attaching sourcing evidence keeps audits clean.
References
- IBM Maximo Application Suite Documentation
- Maximo Manage — Purchasing (IBM Documentation)
- Maximo Manage — Start Centers and Query Manager (IBM Documentation)
- Maximo Manage — Workflow inbox and delegation (IBM Documentation)
Series Navigation
| Previous: | Part 5 — Reservations & Replenishment |
|---|---|
| Next: | Part 7 — PR to PO & Approvals |
About TheMaximoGuys: We help Maximo developers and teams navigate the move to MAS 9 with practical, no-hype guidance grounded in how the platform actually behaves.
Published by TheMaximoGuys | July 2026
Posam Lakshminarayana
Venkat Achanta