Results for “page_instance_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The object IBW_PAGE_SA_TIME_MV is a materialized view owned by the APPS schema and registered under the FND — Application Object Library product family in Oracle E-Business Suite. Despite its categorization under FND, its name and column composition clearly tie it to the iStore/Interactive Business Warehouse (IBW) web-analytics stack, where page-level clickstream data is aggregated along time dimensions. The _MV suffix confirms it is a materialized view rather than a base table; ETRM documentation for 12.1.1 records the object as "Not implemented in this database," meaning the definition ships with the product but the container is created only when the corresponding analytics feature is licensed and enabled.

The view exposes 20 columns and carries a single documented unique index, I_SNAP$_IBW_PAGE_SA_TIME_M, built over SYS_OP_MAP_NONNULL expressions of thirteen grouping keys. That construction is typical of materialized-view snapshots with refresh-on-commit aggregation, where null-tolerant uniqueness is required for the refresh engine. From a Data Vault modeling perspective, the heuristic classification is satellite. The index keys (VISIT_ID, PAGE_INSTANCE_ID, VISITANT_ID, SITE_ID, TRANSACTION_DATE) form a composite parent key, while the measures PAGE_VIEWS, PAGE_VIEW_DURATION, D_PAGE_VIEWS, and D_PAGE_VIEW_DURATION_CNT are descriptive, time-variant attributes — the classic hub/link-plus-satellite pattern flattened into one denormalized analytic structure.

Key Information Stored

• Grain identifiers — SITE_ID, SITE_AREA_ID, PAGE_INSTANCE_ID, VISITANT_ID, VISIT_ID, and GROUPING_SETS_ID jointly define the additive grain of a single snapshot row.
• Time dimensions — TRANSACTION_DATE, TIME_ID, PERIOD_TYPE_ID, ENT_YEAR_ID, ENT_QTR_ID, ENT_PERIOD_ID, WEEK_ID, and REPORT_DATE_JULIAN provide the enterprise calendar and Julian reporting axes used for period-over-period trending.
• Measures — PAGE_VIEWS and PAGE_VIEW_DURATION hold raw counts; D_PAGE_VIEWS and D_PAGE_VIEW_DURATION_CNT hold distinct or derived counters consumed by dashboard queries.
• Foreign key — VISIT_ID references AHL_VISITS_B, anchoring each snapshot row to a physical or logical visit record.
• Surrogate key — no single-column surrogate primary key is documented; uniqueness is enforced by the composite expression index I_SNAP$_IBW_PAGE_SA_TIME_M.

Common Use Cases and Queries

Typical consumption is through IBW dashboard and iStore analytics reports that trend page popularity and dwell time by site, area, and period. A representative aggregation pattern is:

• SELECT site_id, ent_period_id, SUM(page_views), SUM(page_view_duration) FROM ibw_page_sa_time_mv WHERE transaction_date BETWEEN :f AND :t GROUP BY site_id, ent_period_id
• Joining to AHL_VISITS_B on VISIT_ID to correlate page activity with visit attribution.
• Refreshing the snapshot on demand with DBMS_MVIEW.REFRESH('IBW_PAGE_SA_TIME_MV','C') following iStore transaction loads.

Related Objects

• AHL_VISITS_B — joined on IBW_PAGE_SA_TIME_MV.VISIT_ID = AHL_VISITS_B.VISIT_ID.
• IBW_PAGE_SA_TIME — the presumed base fact source from which the _MV snapshot is refreshed.
• FND_LOOKUP_VALUES — supplies PERIOD_TYPE_ID and grouping-set definitions.
• FND_FLEX_VALUES / GL calendars — resolve ENT_YEAR_ID, ENT_QTR_ID, and ENT_PERIOD_ID labels.
• DBMS_MVIEW — administrative package governing refresh scheduling for the snapshot.