Shows each supplier the forecast and open order lines for its parts, collects committed dates and quantities, and writes the confirmations onto the schedule lines in the ERP.
Today the forecast goes to suppliers as a spreadsheet attached to an email each Monday, and their commitments come back in replies that a buyer keys into the ERP by hand. A supplier learns about a changed order line when the buyer remembers to call.
The app gives each supplier a portal screen with the forecast for the coming 26 weeks and every open order line for its parts, refreshed from the ERP each Monday morning and whenever a line changes. The supplier planner commits a date and a quantity per schedule line, and a commitment that falls short of the request carries a reason and goes to the supplier's account manager for a signature. The buyer sees every commitment beside the demand it covers, accepts the ones that match and challenges the ones that leave a gap, and the category lead decides the large gaps. Each accepted commitment is written to the schedule line in the ERP as the supplier confirmation.
| Function | Level | Does |
|---|---|---|
| Supplier | Level 1: supplier planner | commits a date and quantity per schedule line and acknowledges the forecast |
| Supplier | Level 2: supplier account manager | signs commitments below 90 percent of the request and answers challenges |
| Procurement | Level 1: buyer | accepts matching commitments and challenges gaps |
| Procurement | Level 2: category lead | decides gaps above 100,000 or beyond 2 weeks, including a second source |
| Planning | Level 1: material planner | confirms whether a committed date still covers production and customer demand |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Supplier home | portal screen: open order lines by week, forecast by part, lines awaiting commitment counted, messages from the buyer; filter by plant |
| S02 Commit lines | portal grid of schedule lines with requested date and quantity; fields for committed date and quantity, reason code when they differ; commit-all button |
| S03 Forecast view | portal chart and grid of the 26-week forecast by part beside last week's version; changes above 20 percent marked; acknowledge button and a capacity flag per week |
| S04 Buyer review | commitments received with the gap against the request and against demand; accept and challenge buttons; thread per line |
| S05 Category decision | gaps above the threshold with value, weeks short and the second source on file; options: accept, split to a second source, escalate; note |
| S06 Board | commitment coverage by supplier, forecast weeks acknowledged, open challenges by age, commitments met at goods receipt |
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 |
|---|---|---|
| Purchase order line | open order lines, schedule lines and supplier confirmations | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Forecast | the 26-week requirement per part and plant the supplier sees | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Supplier master | supplier contacts, purchasing organisation and block status | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Goods receipt | receipts posted, so the supplier sees what has arrived | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Material master | part description and planned lead time | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Purchase order line | supplier confirmation written to the schedule line: committed date, committed quantity and reason |
Start: An open order line for the supplier's parts that is still awaiting a supplier confirmation, or whose confirmed date falls after the requested date; the Monday forecast release refreshes every part as well.
# start criterion, in canonical fields; each system page shows it in that system's fields
{po.received_qty} < {po.qty} and ({po.confirmed_date} is blank or {po.confirmed_date} > {po.delivery_date})| Step | Moves when |
|---|---|
| Lines released | each Monday at 06:00 the forecast and the open lines refresh; lines awaiting commitment appear on S02 |
| Supplier commits | supplier planner enters a date and quantity per schedule line within 2 working days; a shortfall carries a reason |
| Shortfall signed | a commitment below 90 percent of the request goes to the supplier account manager, who signs it |
| Buyer review | buyer accepts a commitment that matches; a gap goes to the planner, who confirms cover or flags the shortfall |
| Category decision | a gap above 100,000 or beyond 2 weeks goes to the category lead, who accepts or splits to a second source |
| Line confirmed | confirmation written to the schedule line in the ERP; acknowledgement stored; coverage on S06 updated |
| Component | Trigger → action → outcome |
|---|---|
| grd_commit | on edit → compare the committed date and quantity with the schedule line → require a reason code when the date slips or the quantity falls short |
| btn_commit_all | on click → validate every edited row → write the confirmations to the schedule lines through the ERP order interface, notify the buyer |
| btn_challenge | on click → open a thread on the line with the buyer's question → start the 8-hour reply clock, copy the supplier account manager |
| btn_split | on click → create the request for the second source with the short quantity → record the decision, refresh S04 and S06 |
| Step | Time limit and escalation |
|---|---|
| Supplier commitment | 2 working days after release, then the supplier account manager is reminded and the line is flagged for the buyer |
| Challenge reply | 8 working hours, then the category lead is copied |
| Category decision | 2 working days, then the case goes to the head of procurement |
Names, places and figures are illustrative; the pattern is the catalogue's.
At 06:00 on Monday the forecast release reached 140 suppliers of the Guadalajara plant. Marta, the planner at a wire harness supplier in Querétaro, opened her portal screen at 08:30, saw 46 schedule lines awaiting commitment and committed 41 of them by 10:15; 5 slipped by a week because of a copper delivery, each with a reason, and her account manager signed the shortfall before lunch. The buyer in Guadalajara challenged 2 of the 5 at 13:40, and by 16:00 the material planner had confirmed that stock covered the gap. The confirmations sat on the schedule lines in the ERP that evening, and the board showed 93 percent of lines committed within 2 days.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Purchase order line read from EKKO · EKPO · EKET · EKBE; also on SAP ECC.
Open the S/4HANA page →Purchase order line read from Procurement REST: purchaseOrders · lines · schedules; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Purchase order line read from CONFORMED.PURCHASE_ORDER_LINE · HISTORY.PO_LINE_VERSIONS; lakehouse.
Open the Snowflake page →Purchase order line read from silver.purchase_order_line · gold.po_line_versions; 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 7 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.