Scores every supplier each month from receipts, quality notifications and invoices, and opens a corrective action with the supplier when the score falls below the threshold.
Today the scorecard is a quarterly spreadsheet built from 3 extracts, and the supplier hears about a poor score at the next business review. The corrective action lives in a slide and its due dates in someone's calendar.
On the first working day of each month the app scores every supplier with at least 5 receipts in the last 3 months: on-time delivery from goods receipt dates against the order dates, quality from notifications per 100 receipts, and price from invoice amounts against order values. A score below 70 opens a case for the buyer with the late lines, the defects and the invoices behind it. The supplier submits a root cause and an action plan on the portal screen, the buyer and the supplier quality engineer agree the plan, and the next 2 monthly scores verify it. A supplier that stays below 70 goes to the category lead, who can set a purchasing block on the vendor record.
| Lane | Does |
|---|---|
| Buyer | reviews the score, opens the action and agrees the plan |
| Supplier | submits root cause and actions on the portal screen and reports progress |
| Supplier quality engineer | assesses quality causes and verifies the actions |
| Category lead | decides a new-business hold or an exit |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Scorecard | grid of suppliers with the total score and its 3 parts, trend over 6 months, receipts counted; filter by category and plant; open button |
| S02 Supplier detail | chart of the score by month; late lines with days late; quality notifications by defect; invoices above the order price; open-action button |
| S03 Corrective action | portal screen: the facts behind the score; root cause field; actions with owner and date; submit |
| S04 Plan review | buyer and supplier quality engineer accept or return the plan with a note; verification months set |
| S05 Progress | actions with status and evidence uploaded by the supplier; the following months' scores beside them; close or escalate buttons |
| S06 Board | suppliers below 70, actions open by age, score recovered after action, suppliers on a new-business hold |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Supplier master | the supplier record, contacts and purchasing block | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Purchase order line | order lines with delivery dates and buyers | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Goods receipt | receipts with their dates and quantities | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Quality notification | quality notifications raised against the supplier | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Supplier invoice | invoiced amounts against order values | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Quality notification | a corrective action notification created with the supplier's actions as tasks with owners and due dates |
| Supplier master | purchasing block set when the category lead places the supplier on hold |
Start: On the first working day of each month, a supplier with at least 5 receipts in the last 3 months whose score from on-time delivery, quality and price is below 70.
# start criterion, in canonical fields; each system page shows it in that system's fields
score({gr.date} against {po.delivery_date}, {qn.number} per 100 receipts, {invoice.amount} against {po.value}) < 70 over the last 3 months| Step | Moves when |
|---|---|
| Score computed | first working day: score per supplier from the receipts, notifications and invoices of the last 3 months |
| Case opened | score below 70 opens a case for the buyer with the late lines, defects and invoices behind it |
| Plan received | supplier submits root cause and actions on the portal within 10 working days |
| Plan agreed | buyer and supplier quality engineer accept; actions and dates fixed as tasks on the notification |
| Verified | 2 monthly scores at or above 70 close the case; a third month below 70 sends it to the category lead |
| Escalated | category lead sets a purchasing block on the vendor record or starts a supplier exit |
| Component | Trigger → action → outcome |
|---|---|
| btn_open_action | on click → create a corrective action notification with the facts from S02 → invite the supplier contact to the portal, start the 10-day clock |
| frm_plan | on submit → attach the root cause and actions to the notification as tasks → notify the buyer and the supplier quality engineer |
| btn_agree | on click → fix the task dates on the notification → start the verification watch over the next 2 monthly scores |
| btn_hold | on click → set the purchasing block on the vendor record through the ERP vendor interface → notify buyers with open orders, refresh S06 |
| Step | Time limit and escalation |
|---|---|
| Supplier plan | 10 working days, then the buyer is reminded and the supplier's account manager is copied |
| Plan review | 5 working days, then the procurement lead is reminded |
| Verification | 2 monthly scores; a score still below 70 after the second month escalates to the category lead |
Names, places and figures are illustrative; the pattern is the catalogue's.
On 1 April the scores reached the buyers of the Pune plant at 07:30; a fastener supplier had fallen to 62 after 2 months of late lines and 4 notifications for thread defects. Ravi, the buyer, opened the action at 09:00 with the 17 late lines and the defect photos attached, and the supplier's quality lead submitted a root cause on the portal on 8 April, a worn tap on one machine, with 3 actions. The supplier quality engineer accepted the plan the next morning, May's score came in at 74 and June's at 81, and the case closed with the record beside the vendor number. The board showed the category lead 9 suppliers below 70 and 2 on hold.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Supplier master read from LFA1 · LFB1 · LFM1 (business partner in S/4); also on SAP ECC.
Open the S/4HANA page →Supplier master read from Procurement REST: suppliers · supplierSites; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Supplier master read from CONFORMED.VENDOR; lakehouse.
Open the Snowflake page →Supplier master read from silver.vendor; lakehouse.
Open the Databricks page →Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 5 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of SAP S/4HANA, Oracle Fusion Cloud, Snowflake, Databricks, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.