App catalogue Procurement

Supplier scorecard and corrective action

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 ScorecardscreenS02 Supplier detailscreenS03 Corrective actionscreenS04 Plan reviewscreenS05 Progressscreendh_vendorSupplier masterdh_poPurchase order linedh_grGoods receiptdh_qnQuality notificationdh_invoiceSupplier invoiceS/4HANALFA1 · LFB1 · LFM1S/4HANAEKKO · EKPO · EKET · EKBES/4HANAMATDOCS/4HANAQMEL · QMFE · QMMAS/4HANARBKP · RSEGrows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
5 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
5
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Data-driven app: starts from the records a criterion selects; each record launches its own flow

LaneDoes
Buyerreviews the score, opens the action and agrees the plan
Suppliersubmits root cause and actions on the portal screen and reports progress
Supplier quality engineerassesses quality causes and verifies the actions
Category leaddecides a new-business hold or an exit
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Scorecardgrid 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 detailchart of the score by month; late lines with days late; quality notifications by defect; invoices above the order price; open-action button
S03 Corrective actionportal screen: the facts behind the score; root cause field; actions with owner and date; submit
S04 Plan reviewbuyer and supplier quality engineer accept or return the plan with a note; verification months set
S05 Progressactions with status and evidence uploaded by the supplier; the following months' scores beside them; close or escalate buttons
S06 Boardsuppliers below 70, actions open by age, score recovered after action, suppliers on a new-business hold
Data handlers

5 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Supplier masterthe supplier record, contacts and purchasing blockS/4HANA · Oracle Fusion · Snowflake · Databricks
Purchase order lineorder lines with delivery dates and buyersS/4HANA · Oracle Fusion · Snowflake · Databricks
Goods receiptreceipts with their dates and quantitiesS/4HANA · Oracle Fusion · Snowflake · Databricks
Quality notificationquality notifications raised against the supplierS/4HANA · Oracle Fusion · Snowflake · Databricks
Supplier invoiceinvoiced amounts against order valuesS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Quality notificationa corrective action notification created with the supplier's actions as tasks with owners and due dates
Supplier masterpurchasing block set when the category lead places the supplier on hold
The flow

From the trigger to the last write

THE FLOW · SUPPLIER SCORECARD AND CORRECTIVE ACTION1Score computedfirst working day:score per supplierfrom the receipts,notifications andinvoices of the last3 months2Case openedscore below 70 opensa case for the buyerwith the late lines,defects and invoicesbehind it3Plan receivedsupplier submits rootcause and actions onthe portal within 10working days4Plan agreedbuyer and supplierquality engineeraccept; actions anddates fixed as taskson the notification5Verified2 monthly scores ator above 70 close thecase; a third monthbelow 70 sends it tothe category lead6Escalatedcategory lead sets apurchasing block onthe vendor record orstarts a supplierexit
Each step and the criterion that moves it.

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

StepMoves when
Score computedfirst working day: score per supplier from the receipts, notifications and invoices of the last 3 months
Case openedscore below 70 opens a case for the buyer with the late lines, defects and invoices behind it
Plan receivedsupplier submits root cause and actions on the portal within 10 working days
Plan agreedbuyer and supplier quality engineer accept; actions and dates fixed as tasks on the notification
Verified2 monthly scores at or above 70 close the case; a third month below 70 sends it to the category lead
Escalatedcategory lead sets a purchasing block on the vendor record or starts a supplier exit
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
btn_open_actionon click → create a corrective action notification with the facts from S02 → invite the supplier contact to the portal, start the 10-day clock
frm_planon submit → attach the root cause and actions to the notification as tasks → notify the buyer and the supplier quality engineer
btn_agreeon click → fix the task dates on the notification → start the verification watch over the next 2 monthly scores
btn_holdon click → set the purchasing block on the vendor record through the ERP vendor interface → notify buyers with open orders, refresh S06

Clocks

StepTime limit and escalation
Supplier plan10 working days, then the buyer is reminded and the supplier's account manager is copied
Plan review5 working days, then the procurement lead is reminded
Verification2 monthly scores; a score still below 70 after the second month escalates to the category lead

Measures

suppliers below 70share of receipts on timenotifications per 100 receiptsscore recovery after an actionactions closed on time
A day with the app

Illustrative

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.

illustrative scenario · Supplier scorecard and corrective action
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

ScorecardA monthly score per supplier made of on-time delivery, quality and price.
Corrective actionA plan the supplier commits to for removing the cause of a problem, with owners and dates.
Purchasing blockA mark on the vendor record that stops new purchase orders until it is removed.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.