Context

Read-only checks to confirm that the foundation dimensions pushed from RI to AIF Apps landed correctly. Run right after the dimension push and before the historical fact push. None of these queries modify data.

Two checks:

  • rows — every dimension table populated by the push has data.
  • extended hierarchy config — when the 9-level product hierarchy is used (AP, IPO, LPO), confirm RSE_CONFIG matches the transaction data before pushing facts.

Quick access

Hierarchy tables

Run after RSE_MASTER_ADHOC_PROCESS -pldg (or the bundle used in the push).

select * from RSE_PROD_HIER;
select * from RSE_LOC_HIER;
select * from RSE_CAL_HIER;
select * from RSE_CUSTSEG_HIER;

Confirm each table is populated and hierarchy names and levels look right for the client.

Price Zone tables

Applies only when Price Zones are part of the implementation (-z in the dimension push).

select * from RSE_PRICE_ZONE;
select * from RSE_PRICE_ZONE_GRP;
select * from RSE_PRICE_ZONE_LOC;

Extended product hierarchy check

Applies only when the implementation uses the 9-level product hierarchy (style / style-color, used by AP, IPO, LPO).

In RSE_CONFIG (in APEX, or AI FOUNDATION CLOUD SERVICE > TOP LEFT MENU > Tasks > Control and Tactical Center > Manage Configurations), confirm:

  • LOAD_EXTENDED_PROD_HIER = Y
  • PROD_HIER_SLSTXN_HIER_LEVEL_ID matches the leaf level of the transaction data (7-Style, 8-Style/Color, or 9-Style/Color/Size).

A mismatch produces an Extended Hierarchy Level mismatch error on the fact push, not here — confirming these values now avoids a failure later.

To find every table belonging to a given RSE family — useful when validating something outside the tables listed above:

SELECT * FROM RSE_DATA_MODEL_SUPPORT_UTIL.GET_TABLE_LIST('RSE_<INTERFACE_PREFIX>%');

Reference