Oracle Retail Knowledge Base

Push data to AIF Apps

4 min read

Context

Runbook to push foundation dimensions and historical facts from RI (Retail Insights, RADM01) to AIF Apps (RASE01) using the RSE_MASTER_ADHOC_PROCESS standalone job in POM. It is part of AIF Initial Setup process and runs after the RI side is validated (calendar, dimensions, historical facts).

RSE_MASTER_ADHOC_PROCESS is one job that takes a string of one-character flags — each flag toggles a load step, and flags can be combined (-pldg, -xwa). Steps that extract historical data also accept --from:YYYYMMDD --to:YYYYMMDD. See Rejected records cleanup and AIF Data warehouse Cleanup before running anything — the push only reflects what is already in RI, so unresolved rejects and duplicates land in AIF Apps as-is. For how to navigate POM and edit standalone job parameters, see How to run a POM standalone job.

Quick access

RSE_MASTER_ADHOC_PROCESS flags

Flags used in this runbook (full list: Reference).

FlagStep
-pProduct Hierarchy
-lLocation Hierarchy
-dCalendar Hierarchy
-gCustomer Segment Hierarchy
-zPrice Zone ETL (only when Price Zones are used)
-NSeason Phase Item Load (required for LPO)
-xSales transaction data
-wWeekly Aggregate Sales
-aAggregate Sales processing
-TWeekly Return transactions
-eWeekly Return Aggregation
-iInventory
-CPrice and Cost
-VForecast Lifecycle Classification
-PProduct Attributes
-JRules Engine data for PRO (LPO)

Date parameters for the historical steps: --from:YYYYMMDD, --to:YYYYMMDD, --extfrom:Y and --extto:Y to extend to week start/end.

Push the foundation dimensions

Run in POM, on the AIF Apps standalone schedule.

  1. Choose the parameter bundle for your scope:
    • -pldg — core hierarchies (Oracle’s documented first-time bundle).
    • -pldgz — core + Price Zone.
    • -pldgNz — core + Price Zone + Season/Phase (typical LPO setup).
  2. Run RSE_MASTER_ADHOC_PROCESS with the bundle chosen above.
  3. Validate the load in AIF Apps: Validate AIF Apps dimensions.

Extended product hierarchy

If the implementation uses the 9-level product hierarchy (style / style-color, used by AP, IPO, LPO), confirm LOAD_EXTENDED_PROD_HIER = Y and PROD_HIER_SLSTXN_HIER_LEVEL_ID in RSE_CONFIG (in APEX, or AI FOUNDATION CLOUD SERVICE > TOP LEFT MENU > Tasks > Control and Tactical Center > Manage Configurations) before running the push. A mismatch produces an Extended Hierarchy Level mismatch error on the fact push, not here.

Push the historical facts

Only after Validate AIF Apps dimensions is clean. Push and validate one interface at a time — a bad range on Sales compounds into Receipts and Inventory if you do not catch it first.

Use --from/--to matching the min/max dates loaded into RI for each interface. Get them by querying the date range on the RI fact table of that interface:

select
	TO_CHAR(min(<date_column>), 'YYYYMMDD') AS min_dt,
	TO_CHAR(max(<date_column>), 'YYYYMMDD') AS max_dt
from <RI_fact_table>;

RI fact table and date column per interface:

InterfaceRI fact tableDate column
SalesW_RTL_SLS_TRX_IT_LC_DY_FDT_WID
ReceiptsW_RTL_INVRC_IT_LC_DY_FDT_WID
InventoryW_RTL_INV_IT_LC_DY_FDT_WID
PriceW_RTL_PRICE_IT_LC_DY_FFROM_DT_WID

For Sales example, if RI runs from 2024-01-01 to 2026-03-22:

RSE_MASTER_ADHOC_PROCESS -xwa --from:20240101 --to:20260322
  1. Sales — RSE_MASTER_ADHOC_PROCESS -xwa --from:<FROM> --to:<TO>. If it fails with TO date appears too far in the future, see Date validation errors. Validate: Sales.
  2. Receipts (when applicable, before Inventory) — RSE_MASTER_ADHOC_PROCESS -Te --from:<FROM>. Validate: Receipts.
  3. Inventory — RSE_MASTER_ADHOC_PROCESS -i --from:<FROM>. Validate: Inventory.
  4. Price and Cost — RSE_MASTER_ADHOC_PROCESS -C --from:<FROM>. Validate: Price.
  5. Additional groups for LPO — RSE_MASTER_ADHOC_PROCESS -V (Forecast Lifecycle Classification), then RSE_MASTER_ADHOC_PROCESS -PJ (Product Attributes + LPO Rules Engine). Both are prerequisites for PRO_MASTER_ADHOC_PROCESS (LPO initialization, not yet documented in this vault). Validate: Additional data groups.

Date validation errors

RSE_MASTER_ADHOC_PROCESS can fail with:

EXT_PROG_SYS_OUT:rse_master.ksh: TO date appears too far in the future.
Maximum available date is 20250331.
Passed parameter is 20260322.

If the --to you passed is correct and the RI data actually goes up to that date, rerun with --bypass_date_validation:Y:

RSE_MASTER_ADHOC_PROCESS -xwa --from:<FROM> --to:<TO> --bypass_date_validation:Y

--bypass_date_validation:Y is not in the Oracle docs

Workaround seen in practice on the Sales push. It only skips the process date check — it does not create missing data. Do not use it to mask a wrong --to or an incomplete RI load.

Reference

Graph View

Backlinks