App catalogue Supply chain and planning

New product introduction readiness

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.

HIERARCHY · NEW PRODUCT INTRODUCTION READINESSEngineeringL1: design engineerscreen · usersL2: engineering managerscreen · usersSupply chainL1: buyer and materialplannerscreen · usersL2: supply chain managerscreen · usersQualityL1: quality engineerscreen · usersL2: quality managerscreen · usersSalesL1: product managerscreen · usersL2: sales directorscreen · usersa person created at a level is assigned their parent-level and child-level users at the same timeTrigger and flow criteriaThe launch lead registers a new product with its target launch date and part numbers on S01.
The hierarchy: functions, levels, and the criterion that starts the flow. Each level carries a screen and its people.
8 days
of configuration to a production-grade version
estimate
7
screens, desktop and mobile
catalogue
6
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
2
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

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

FunctionLevelDoes
EngineeringLevel 1: design engineercompletes basic data, BOM and routing for every new part
EngineeringLevel 2: engineering managerreleases the structure and signs the engineering gate
Supply chainLevel 1: buyer and material plannername an approved source and price per purchased part and fill the plant views with lead times and planning settings
Supply chainLevel 2: supply chain managersigns sources above 250,000 of annual spend and the supply gate
QualityLevel 1: quality engineersets inspection settings and records the first-article decision
QualityLevel 2: quality managersigns the quality gate
SalesLevel 1: product managersets the price condition and the sales view
SalesLevel 2: sales directorsigns the launch
Screens

7 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 Launch registerproduct name, target launch date, plant, new part numbers picked from the material master or uploaded, launch lead; submit
S02 Readiness boardmatrix of parts by gate with a tick or the open field named; count complete per function; days to launch; filter by function
S03 Part checklistfor 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 gatepurchased parts with approved vendor, price, lead time and vendor block status; sign button for the supply chain manager
S05 Quality gateinspection settings per part, first-article lot and its usage decision; sign button
S06 Launch sign-offstate of every gate, open items with owner and date, launch date; sign or hold with a note
S07 Trackerall launches with gates complete per function, items overdue, days to each launch
Data handlers

6 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
Material masterthe new part numbers with basic data, plant views, status and lead timeS/4HANA · Oracle Fusion · Snowflake · Databricks
Bill of materialsthe product structure with its valid-fromS/4HANA · Oracle Fusion · Snowflake · Databricks
Routingoperations and work centers for made partsS/4HANA · Oracle Fusion · Snowflake · Databricks
Supplier masterapproved sources and their block statusS/4HANA · Oracle Fusion · Snowflake · Databricks
Inspection lotthe first-article inspection lot and its usage decisionS/4HANA · Oracle Fusion · Snowflake · Databricks
Price conditionthe sales price condition and its validityS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Material masterplant status set to active for the launch plant when the launch is signed
Bill of materialsthe released structure's valid-from aligned to the launch date
The flow

From the trigger to the last write

THE FLOW · NEW PRODUCT INTRODUCTION READINESS1Launchregisteredparts read from thematerial master; agate per part andfunction opened withits owner from theplant's role map2Engineeringcompletebasic data present;BOM and routingreleased with avalid-from on orbefore the launchdate3Supply readyevery purchased parthas an approvedsource, a price and alead time; plantviews complete4Quality readyinspection settingsset; first-articlelot carries anaccepted usagedecision5Sales readyprice condition validfrom the launch date;sales view complete6Launch signedsales director signs;material status setto active for theplant; launch closed
Each step and the criterion that moves it.

Start: The launch lead registers a new product with its target launch date and part numbers on S01.

StepMoves when
Launch registeredparts read from the material master; a gate per part and function opened with its owner from the plant's role map
Engineering completebasic data present; BOM and routing released with a valid-from on or before the launch date
Supply readyevery purchased part has an approved source, a price and a lead time; plant views complete
Quality readyinspection settings set; first-article lot carries an accepted usage decision
Sales readyprice condition valid from the launch date; sales view complete
Launch signedsales director signs; material status set to active for the plant; launch closed
Actions, clocks and measures

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

ComponentTrigger → action → outcome
btn_registeron 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_readinesson 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_gateon click → record the signature against the gate → notify the next function's owner and update S07
btn_release_launchon click → set the material status to active for the plant through the material interface → store the confirmation, close the launch

Clocks

StepTime limit and escalation
Each gatedue 20 working days before launch; an overdue gate escalates to the function's second level
Open field5 working days after assignment, then the launch lead is reminded and the field is flagged on S02

Measures

gates complete on timeopen fields per part 20 days before launchlaunches signed by the target datedays from register to sign-off
A day with the app

Illustrative

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.

illustrative scenario · New product introduction readiness
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

Plant viewThe part of a material record that holds planning, purchasing and storage settings for one plant.
Usage decisionThe quality verdict recorded on an inspection lot: accepted, rejected or accepted with conditions.
First articleThe first pieces made or delivered of a new part, inspected in full before series production.
Questions

How long does it take to have this running?

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.

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?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

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.