Results for “cart_id”

2 results




Overview
Explore in AI Chat

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

Overview

IBW_PRODUCT_MV is a materialized-view-backed table in the Oracle E-Business Suite Application Object Library (FND) product family. The _MV suffix and the presence of a GROUPING_SETS_ID column indicate that this object is a pre-aggregated summary structure populated by an Oracle Materialized View refresh process rather than a transactional base table. It serves reporting and analytical workloads — typically Oracle Marketing/iStore analytics (the "IBW" prefix) — by collapsing large volumes of visit, page-view, cart, quote and order activity into denormalized aggregates keyed by product, visit, site and time.

The ETRM metadata explicitly states that this object is not implemented in this database, which confirms it is an optional or install-specific summary object that appears only where the relevant analytics or Marketing Online components have been licensed and configured. In EBS 12.1.1 the documented physical schema shows an owner of APPS with 24 columns; the same definition carries forward into 12.2.2. The metadata assigns a heuristic Data Vault classification of standalone. In Data Vault modeling terms this suggests the structure behaves more like a self-contained snapshot or aggregate than a classical hub, link, or satellite, though the presence of foreign keys to FND_DM_PRODUCTS and AHL_VISITS_B means a Hub (Product, Visit) plus Satellite interpretation is also defensible for integration projects.

Key Information Stored

The table captures per-row aggregates over visit activity. The most significant columns are:

  • PRODUCT_ID and VISIT_ID — the two documented foreign keys; each references FND_DM_PRODUCTS and AHL_VISITS_B respectively, and together they form the natural business key of each aggregate row.
  • VISITANT_ID — identifies the visitor/party associated with the visit.
  • SITE_ID and LEAF_CATEG_ID — the iStore site and leaf product category context for the aggregate.
  • TRANSACTION_DATE — the time dimension used for period-based rollup.
  • NO_VISITS / D_NO_VISITS — visit count and its delta (change since prior refresh).
  • PAGE_VIEWS / D_PAGE_VIEWS — page-view totals and deltas.
  • ORDERS_SITE_VISITS — count of visits that converted to orders.
  • ORDER_ID, QOT_ORDER_ID, CART_ID — the transactional identifiers for the resulting order, quote and cart.
  • BOOKED_AMT_F, BOOKED_AMT_G, BOOKED_AMT_G1 — booked revenue expressed in the functional, global and secondary global currencies, with corresponding D_ delta columns.
  • GROUPING_SETS_ID — identifies the grouping-set definition governing the aggregation.
  • UMARKER — the standard EBS concurrency/refresh marker column.

The surrogate identifiers used for row uniqueness are not explicitly documented in the ETRM extract; in practice the primary key is a system-generated sequence value (often reflected via GROUPING_SETS_ID plus the FK pair).

Common Use Cases and Queries

The primary use case is marketing and e-commerce funnel analysis: tracking product-level traffic-to-order conversion, page views per product, and booked revenue by period and site. A representative query pattern is:

SELECT p.product_name,
       SUM(v.no_visits)       AS visits,
       SUM(v.page_views)      AS views,
       SUM(v.booked_amt_g)    AS booked
FROM   ibw_product_mv v,
       fnd_dm_products p
WHERE  v.product_id = p.product_id
AND    v.transaction_date BETWEEN :start_date AND :end_date
GROUP  BY p.product_name;

Because deltas (D_NO_VISITS, D_BOOKED_AMT_*) are materialized, incremental reporting can read only changed rows between refreshes, and currency analytics can compare BOOKED_AMT_G against BOOKED_AMT_G1 for reporting-currency reconciliation. Callers should never INSERT directly; the object is refreshed by its owning concurrent program.

Related Objects

  • FND_DM_PRODUCTS — joined on PRODUCT_ID; supplies product dimension attributes.
  • AHL_VISITS_B — joined on VISIT_ID; the base visit entity that anchors the aggregate.
  • AHL_VISITANTS — resolves VISITANT_ID to visitor identity.
  • IBW_ORDER_MV and related IBW aggregate materialized views — sibling summary objects sharing the same refresh program.
  • FND_MV_REFRESH / DBMS_MVIEW — the refresh mechanism that rebuilds these aggregates.
  • IBY_TRXN_SUMMARIES — frequently correlated for payment/revenue reconciliation against BOOKED_AMT_*.