App catalogue Supply chain and planning

Supplier collaboration portal

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.

HIERARCHY · SUPPLIER COLLABORATION PORTALSupplierL1: supplier plannerscreen · usersL2: supplier accountmanagerscreen · usersProcurementL1: buyerscreen · usersL2: category leadscreen · usersPlanningL1: material plannerscreen · usersa person created at a level is assigned their parent-level and child-level users at the same timeTrigger and flow criteriaAn open order line for the supplier's parts that is still awaiting a supplier confirmation, or whose confirmed…
The hierarchy: functions, levels, and the criterion that starts the flow. Each level carries a screen and its people.
7 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 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.

Who takes part

Collaborative app: levels first, then screens per level, then people, then the flow and trigger criteria

FunctionLevelDoes
SupplierLevel 1: supplier plannercommits a date and quantity per schedule line and acknowledges the forecast
SupplierLevel 2: supplier account managersigns commitments below 90 percent of the request and answers challenges
ProcurementLevel 1: buyeraccepts matching commitments and challenges gaps
ProcurementLevel 2: category leaddecides gaps above 100,000 or beyond 2 weeks, including a second source
PlanningLevel 1: material plannerconfirms whether a committed date still covers production and customer demand
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 Supplier homeportal screen: open order lines by week, forecast by part, lines awaiting commitment counted, messages from the buyer; filter by plant
S02 Commit linesportal 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 viewportal 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 reviewcommitments received with the gap against the request and against demand; accept and challenge buttons; thread per line
S05 Category decisiongaps above the threshold with value, weeks short and the second source on file; options: accept, split to a second source, escalate; note
S06 Boardcommitment coverage by supplier, forecast weeks acknowledged, open challenges by age, commitments met at goods receipt
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
Purchase order lineopen order lines, schedule lines and supplier confirmationsS/4HANA · Oracle Fusion · Snowflake · Databricks
Forecastthe 26-week requirement per part and plant the supplier seesS/4HANA · Oracle Fusion · Snowflake · Databricks
Supplier mastersupplier contacts, purchasing organisation and block statusS/4HANA · Oracle Fusion · Snowflake · Databricks
Goods receiptreceipts posted, so the supplier sees what has arrivedS/4HANA · Oracle Fusion · Snowflake · Databricks
Material masterpart description and planned lead timeS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Purchase order linesupplier confirmation written to the schedule line: committed date, committed quantity and reason
The flow

From the trigger to the last write

THE FLOW · SUPPLIER COLLABORATION PORTAL1Lines releasedeach Monday at 06:00the forecast and theopen lines refresh;lines awaitingcommitment appear onS022Suppliercommitssupplier plannerenters a date andquantity per scheduleline within 2 workingdays; a shortfallcarries a reason3Shortfallsigneda commitment below 90percent of therequest goes to thesupplier accountmanager, who signs it4Buyer reviewbuyer accepts acommitment thatmatches; a gap goesto the planner, whoconfirms cover orflags the shortfall5Categorydecisiona gap above 100,000or beyond 2 weeksgoes to the categorylead, who accepts orsplits to a secondsource6Line confirmedconfirmation writtento the schedule linein the ERP;acknowledgementstored; coverage onS06 updated
Each step and the criterion that moves it.

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})

StepMoves when
Lines releasedeach Monday at 06:00 the forecast and the open lines refresh; lines awaiting commitment appear on S02
Supplier commitssupplier planner enters a date and quantity per schedule line within 2 working days; a shortfall carries a reason
Shortfall signeda commitment below 90 percent of the request goes to the supplier account manager, who signs it
Buyer reviewbuyer accepts a commitment that matches; a gap goes to the planner, who confirms cover or flags the shortfall
Category decisiona gap above 100,000 or beyond 2 weeks goes to the category lead, who accepts or splits to a second source
Line confirmedconfirmation written to the schedule line in the ERP; acknowledgement stored; coverage on S06 updated
Actions, clocks and measures

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

ComponentTrigger → action → outcome
grd_commiton 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_allon click → validate every edited row → write the confirmations to the schedule lines through the ERP order interface, notify the buyer
btn_challengeon click → open a thread on the line with the buyer's question → start the 8-hour reply clock, copy the supplier account manager
btn_spliton click → create the request for the second source with the short quantity → record the decision, refresh S04 and S06

Clocks

StepTime limit and escalation
Supplier commitment2 working days after release, then the supplier account manager is reminded and the line is flagged for the buyer
Challenge reply8 working hours, then the category lead is copied
Category decision2 working days, then the case goes to the head of procurement

Measures

schedule lines committed within 2 dayscommitted quantity as a share of the requestforecast weeks acknowledged per supplieropen challenges by agecommitments met at goods receipt
A day with the app

Illustrative

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.

illustrative scenario · Supplier collaboration portal
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

Supplier confirmationThe date and quantity a supplier commits against a schedule line; the ERP stores it beside the requested date.
Forecast releaseThe weekly copy of planned requirements per part that a plant shares with its suppliers.
Commitment coverageThe share of the requested quantity that suppliers have committed for the coming weeks.
Questions

How long does it take to have this running?

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.

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.