Tracks every part of a new product through the readiness gates each function owns, reading the material, BOM, routing, source, inspection and price records live until launch.
Today launch readiness is a weekly meeting around a spreadsheet of part numbers, and each function reports its status from memory. The first sign that a plant view is incomplete is a planning run that skips the part 2 weeks before launch.
The launch lead registers the product with its target date and the list of new part numbers. The app opens a readiness gate per part for each function and reads the live records behind each gate: basic data, bill of materials (BOM) and routing for engineering; approved source, price and lead time for sourcing and planning; inspection settings and the first-article decision for quality; the price condition and sales view for sales. A gate turns complete the moment the fields it needs are present in the ERP, and an owner is named for every field still open. Each function's second level signs its gates, and the sales director signs the launch when every gate is complete.
| Function | Level | Does |
|---|---|---|
| Engineering | Level 1: design engineer | completes basic data, BOM and routing for every new part |
| Engineering | Level 2: engineering manager | releases the structure and signs the engineering gate |
| Supply chain | Level 1: buyer and material planner | name an approved source and price per purchased part and fill the plant views with lead times and planning settings |
| Supply chain | Level 2: supply chain manager | signs sources above 250,000 of annual spend and the supply gate |
| Quality | Level 1: quality engineer | sets inspection settings and records the first-article decision |
| Quality | Level 2: quality manager | signs the quality gate |
| Sales | Level 1: product manager | sets the price condition and the sales view |
| Sales | Level 2: sales director | signs the launch |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Launch register | product name, target launch date, plant, new part numbers picked from the material master or uploaded, launch lead; submit |
| S02 Readiness board | matrix of parts by gate with a tick or the open field named; count complete per function; days to launch; filter by function |
| S03 Part checklist | for one part: every field each view needs, read live from the ERP, with owner and due date per open field; assign and done buttons |
| S04 Supply gate | purchased parts with approved vendor, price, lead time and vendor block status; sign button for the supply chain manager |
| S05 Quality gate | inspection settings per part, first-article lot and its usage decision; sign button |
| S06 Launch sign-off | state of every gate, open items with owner and date, launch date; sign or hold with a note |
| S07 Tracker | all launches with gates complete per function, items overdue, days to each launch |
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 |
|---|---|---|
| Material master | the new part numbers with basic data, plant views, status and lead time | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Bill of materials | the product structure with its valid-from | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Routing | operations and work centers for made parts | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Supplier master | approved sources and their block status | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Inspection lot | the first-article inspection lot and its usage decision | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Price condition | the sales price condition and its validity | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Material master | plant status set to active for the launch plant when the launch is signed |
| Bill of materials | the released structure's valid-from aligned to the launch date |
Start: The launch lead registers a new product with its target launch date and part numbers on S01.
| Step | Moves when |
|---|---|
| Launch registered | parts read from the material master; a gate per part and function opened with its owner from the plant's role map |
| Engineering complete | basic data present; BOM and routing released with a valid-from on or before the launch date |
| Supply ready | every purchased part has an approved source, a price and a lead time; plant views complete |
| Quality ready | inspection settings set; first-article lot carries an accepted usage decision |
| Sales ready | price condition valid from the launch date; sales view complete |
| Launch signed | sales director signs; material status set to active for the plant; launch closed |
| Component | Trigger → action → outcome |
|---|---|
| btn_register | on click → read the listed part numbers from the material master → open the gates, assign owners, set each gate's due date from the launch date |
| grd_readiness | on refresh → reread the live material, BOM, routing, vendor, lot and price rows → mark a gate complete when every field it needs is present |
| btn_sign_gate | on click → record the signature against the gate → notify the next function's owner and update S07 |
| btn_release_launch | on click → set the material status to active for the plant through the material interface → store the confirmation, close the launch |
| Step | Time limit and escalation |
|---|---|
| Each gate | due 20 working days before launch; an overdue gate escalates to the function's second level |
| Open field | 5 working days after assignment, then the launch lead is reminded and the field is flagged on S02 |
Names, places and figures are illustrative; the pattern is the catalogue's.
Lena, the launch lead in Eindhoven, registered a new sensor module with 38 part numbers at 09:05 on a Tuesday, 11 weeks before launch. The readiness board showed 19 parts with a released BOM and 7 purchased parts still awaiting a source; by 14:00 the buyer had sources for 5 of them and the supply chain manager signed the sixth, a 300,000 connector contract, on Wednesday morning. The first-article lot for the housing was accepted in week 8, the price condition went live in week 9, and the sales director signed the launch on the Friday with 0 open items. The tracker showed 6 other launches and the gate each one waited on.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Material master read from MARA · MARC · MAKT; also on SAP ECC.
Open the S/4HANA page →Material master read from Product Hub REST: itemsV2; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Material master read from CONFORMED.MATERIAL; lakehouse.
Open the Snowflake page →Material master read from silver.material; 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 8 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.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
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.