7. Run the January 2027 Demand Plan¶
In the previous chapters, you loaded the data, created the clusters, defined the monthly profile, and validated the statistical models. You will now consolidate those decisions into a versioned Demand Plan with January 2027 as its reference period.
What this chapter creates¶
| Field | Tutorial value |
|---|---|
| Description | Demand Plan — January 2027 — East collaboration |
| Profile | DP_MONTHLY_TUTORIAL |
| Month | January |
| Year | 2027 |
| Resulting horizon | January through December 2027 |
1. Open Process Execution¶
Hover over Processes in the side menu and open Operations > Process Execution.
Action to perform
Under Macro Selection, choose Demand Planning. Under Sub-selection, keep Plan Generation and select Execute Demand Plan.
2. Fill in the execution fields¶
Enter the description, select the monthly profile, and explicitly set the month and year. The blue outline identifies every field that must be checked before submission.
Action to perform
- Under Description, enter
Demand Plan — January 2027 — East collaboration. - Under Demand-planning execution profile, select
DP_MONTHLY_TUTORIAL. - Under Reference period, select
Januaryand2027. - Click Submit.
3. Understand Running and Completed¶
Community Edition generates the plan synchronously: the button remains in the Submitting... state while the request is running. This is the operational equivalent of Running at this step.
When it finishes, the screen displays Demand Planning executed successfully. In an installation with the process-history endpoint updated, the same execution also appears as Completed under Processes > Process Status.
How to read the status
Do not close the page while it shows Submitting.... Continue only after the success message. An error does not create a valid scenario and must be investigated before running the plan again.
4. Confirm the persisted scenario¶
Hover over Demand Planning and open Planning > Demand Plans.
The functional scenario is listed with ID 2, user demand.planner, the
January 1, 2027 reference date, and profile DP_MONTHLY_TUTORIAL.
Action to perform
Check Description, Execution Profile ID, Time Bucket, Reference Period, and Generated By. Together, these fields are the minimum evidence that the intended scenario was run and persisted.
Completion criterion¶
You have completed this chapter when the scenario appears under Demand Plans with the correct functional user and reference period.
Continue with the commercial collaboration view, or revisit the execution profile if the scenario parameters do not match.