Context
First section of AIF Apps implementation (DR02 task 5.1). Review the RSE_CONFIG values the applications depend on, then push hierarchies, attributes and historical facts from RI (RADM01) to AIF Apps (RASE01) with RSE_MASTER_ADHOC_PROCESS, and validate what landed.
The push procedure itself — flag syntax, --from/--to, date validation errors — is in Push data to AIF Apps. This note records the order and flag groups used at P&C so the run can be repeated as executed.
Quick access
- Review RSE_CONFIG — configuration check before anything is pushed.
- Run RSE_MASTER_ADHOC_PROCESS — the flag groups, in the order they were run.
- Monitor the run —
RSE_LOG_MSG.- Validate — where the checks live.
Review RSE_CONFIG
The plan labels this “Review system configurations for IPO-IO — see AIF Implementation Guide”. Every value reviewed, with the P&C setting, is in RSE_CONFIG parameters. Do it in APEX, or in AI FOUNDATION CLOUD SERVICE > Tasks > Control and Tactical Center > Manage Configurations.
Two of them decide whether the fact push succeeds at all: LOAD_EXTENDED_PROD_HIER and PROD_HIER_SLSTXN_HIER_LEVEL_ID — see Extended product hierarchy check.
Run RSE_MASTER_ADHOC_PROCESS
POM > Tasks > Batch Monitoring > AIF APPS > Standalone > RSE_MASTER_ADHOC_PROCESS > job RSE_MASTER_ADHOC_JOB. Navigation in How to run a POM standalone job; edit the job parameter to each group below and run them one at a time, in this order.
| Group | Parameter | Loads |
|---|---|---|
| Hierarchies | -pldgNz | -p Product, -l Location, -d Calendar, -g Customer Segment hierarchies, -N Season Phase Item, -z Price Zone |
| Attributes | -PLGmu | -P Product attributes, -L Location attributes, -G Customer Segment attributes, -m Customer Engagement attribute, -u UDA |
| Orders | -HO | -H Buyer, Allocation, Purchase Order, Transfer loads; -O Order Cost |
| Supplier | -U | Supplier, Supplier Item, Daily Supplier Cost, Supplier Inv Mgmt |
| Sales | -xwa | -x Sales transactions, -w Weekly Aggregate Sales, -a Aggregate Sales processing |
| Inventory | -i | Inventory |
| Returns | -Te | -T Weekly Return transactions, -e Weekly Return Aggregation |
| Price | -C | Price and Cost |
| Consumer segments | -s | Consumer segment data (about 1 min) |
| Forecast lifecycle | -V | Forecast Lifecycle Classification (about 1 min) |
| Baseline | -B | Baseline Sales and SKU/Store Ranging calculations |
The Sales, Inventory, Returns and Price groups take --from:YYYYMMDD --to:YYYYMMDD matching the range loaded into RI — how to find it, and what to do on TO date appears too far in the future, is in Push the historical facts.
-Bwas skipped at DR02 but LPO needs itThe plan lists the Baseline group as “not executed but is required”. It is a prerequisite for
PRO_MASTER_ADHOC_PROCESS— its-bBaseline step reads what-Bproduces — so run it before Build the LPO application. See Push the historical facts, step 5.
Monitor the run
Each step writes to RSE_LOG_MSG. Newest first:
select * from RSE_LOG_MSG order by MSG_TS DESC;Validate
Run the checks after the corresponding group, before starting the next:
- Hierarchies and Price Zone → Validate AIF Apps dimensions.
- Sales, Inventory, Returns, Price → Validate AIF Apps historical facts.
Next section: Send data to PDS tables.
Related
- AIF Apps implementation
- RSE_CONFIG parameters
- Push data to AIF Apps
- How to run a POM standalone job
- Validate AIF Apps dimensions
- Validate AIF Apps historical facts