Context
LPO optimizes against forecast demand parameters, so the forecast has to be trained, approved and mapped to LPO before any optimization run produces recommendations. Done in the AIF UI, as part of Build the LPO application.
Navigate Strategy & Policy Management > Manage Forecast Configurations.
Check the configuration flags before aggregating
RSE_INV_WHSE_ACTIVITY_USE_FLGmust beNbefore starting aggregation — leaving itYincreases aggregation time dramatically, and it can be turned on later once batches are running. Also confirmPMO_PROD_HIER_TYPE(3 for extended hierarchy) andPMO_AGGR_INVENTORY_DATA_FLGinRSE_CONFIG, reachable fromAI FOUNDATION CLOUD SERVICE>TOP LEFT MENU>Tasks>Control and Tactical Center>Manage Configurations.
Set up the forecast
- Create a forecast run type at the recommendation level you want, for example Style-Color, Price Zone, Week.
- Click Start Data Aggregation. Populates
PMO_ACTIVITIESandPMO_CUM_SLS. - Create the forecast run under that run type and Submit to train the model.
- Review the resulting demand parameters.
- Approve in order: Approve Demand Parameters, Approve Base Demand, Approve Forecast.
- Activate the forecast run type and map it to LPO.
Validate
select * from PMO_ACTIVITIES;
select * from PMO_CUM_SLS;Both empty after step 2 means the aggregation found no data — check that the historical facts landed, in Validate AIF Apps historical facts.
Related
- AIF Apps implementation
- Build the LPO application
- Build the LPO business rules
- Validate AIF Apps historical facts