Runs the monthly sales and operations planning cycle as one app: demand review, supply review, reconciliation and the executive meeting, on the live plan.
Today the cycle runs on slide decks assembled from planning exports, and the decisions taken in each meeting are typed into the planning system days later.
The app defines the four functions in the cycle and their levels: demand planners and their director, supply planners and their director, finance, and the executive team. Each level has its own screen on the live forecast, capacity and inventory figures. The flow moves from demand review to supply review to reconciliation to the executive meeting on fixed dates, and each decision is recorded against the plan version and returned to the planning system.
| Function | Level | Does |
|---|---|---|
| Demand | Level 1: demand planners | review and adjust the forecast by family |
| Demand | Level 2: demand director | signs the demand plan |
| Supply | Level 1: supply planners | check capacity and inventory against the demand plan |
| Supply | Level 2: supply director | signs the supply plan |
| Finance | Level 1: FP&A | values the gap between plans and budget |
| Executive | Level 1: executive team | decides the open trade-offs |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Demand review | forecast by family and region for 18 months, last cycle's plan, actuals; override field with reason |
| S02 Supply review | capacity by line, planned production, projected inventory, shortfalls; scenario toggle |
| S03 Reconciliation | gaps between demand and supply, valued; proposed resolutions; owner and due date |
| S04 Executive meeting | the 5 open decisions with options and values; decision and note |
| S05 Cycle tracker | stage, dates, sign-offs, decisions recorded to the plan |
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 |
|---|---|---|
| Forecast | the demand plan by family and period | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Planned order | the supply plan | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Stock position | projected inventory | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Sales order line | open orders as demand signal | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Budget line | the budget the plans are compared with | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Forecast | agreed forecast version written to the planning system |
| Planned order | firmed supply decisions written back |
Start: The cycle starts on the first working day of each month, or when the demand director starts it early.
| Step | Moves when |
|---|---|
| Demand review | every family reviewed; overrides carry a reason |
| Demand signed | demand director signs by working day 5 |
| Supply review | supply planners resolve or list each shortfall |
| Reconciliation | finance values the gaps; open decisions listed |
| Executive meeting | decisions recorded; plan version agreed and written back |
| Component | Trigger → action → outcome |
|---|---|
| grd_forecast | on edit → check the override against the last 3 months of actuals → require a reason when the change is above 20 percent |
| btn_sign_demand | on click → lock the demand version → open S02 for the supply level, notify the supply planners |
| btn_record_decision | on click → write the decision to the plan version → update S05, notify the owners |
| Step | Time limit and escalation |
|---|---|
| Each stage | the working-day deadline of the cycle calendar; a late stage escalates to the function's director |
| Open decision | 5 working days after the executive meeting, then it returns to the next cycle with a flag |
Names, places and figures are illustrative; the pattern is the catalogue's.
On working day 3 Aisha, a demand planner in Dubai, raised the beverages forecast for Ramadan by 24 percent and wrote the reason beside it. The supply screen showed a bottling shortfall in week 12 the same afternoon, and the supply planner listed two options with their cost. Finance valued both by day 7, the executive team chose the overtime option on day 9, and the agreed plan version reached the planning system before the meeting ended.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Forecast read from PBIM · PBED (planned independent requirements); also on SAP ECC.
Open the S/4HANA page →Forecast read from Demand Management: forecast measures (REST / planning data extract); also on Oracle E-Business Suite.
Open the Oracle Fusion page →Forecast read from CONFORMED.FORECAST · HISTORY.FORECAST_VERSIONS; lakehouse.
Open the Snowflake page →Forecast read from silver.forecast · gold.forecast_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 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.