Search Results customer_category_fk




Overview
Explore in AI Chat

Overview

BIC_SUMV_LOYALTY is a read-only database view belonging to the BIC – Customer Intelligence module of Oracle E-Business Suite. In ETRM 12.2.2 metadata the object is flagged as obsolete and documented as "Not implemented in this database," meaning it is a legacy artifact that may not be installed or populated in a given environment. Within the Customer Intelligence (BIC) reporting layer, the view presents a summarized, party-level loyalty fact set, exposing loyalty value measurements alongside the customer category, market segment, organization, and geographic attributes needed for dimensional analysis. Its role is to support loyalty-oriented reporting and downstream integration, such as extracting loyalty summaries for a data warehouse or a customer analytics dashboard, without requiring the caller to join the full underlying summary table.

Underlying Base Objects

The view text is defined entirely over a single source object: BIC_PARTY_SUMM_V, a customer intelligence party summary view. No additional base tables are documented for BIC_SUMV_LOYALTY, and the ETRM metadata records no referenced base objects beyond this parent view. The definition projects a selected set of columns from BIC_PARTY_SUMM_V and constrains the result set with WITH READ ONLY, so the view cannot be used for DML. Because it is a view over another view, its effective lineage depends on the columns materialized in BIC_PARTY_SUMM_V, and it inherits the access and security characteristics of that parent object.

Key Columns

The projection exposes the measures and dimensional keys required for loyalty analysis:

Common Use Cases and Queries

The typical scenario is loyalty value aggregation and comparison across customer categories, market segments, geographies, and accounting periods. The CUSTOMER_CATEGORY_FK column allows analysts to group loyalty value by category, while ACT_QUARTER and ACT_HALF_YEAR support period-over-period trending. Because the object is obsolete and may not exist, scripts should verify presence before execution.

A representative query by customer category:

SELECT customer_category_fk, org_id, act_quarter, SUM(value) loyalty_value
FROM bic_sumv_loyalty
WHERE act_year = :p_year
GROUP BY customer_category_fk, org_id, act_quarter
ORDER BY customer_category_fk, act_quarter;

A comparable query grouping by market segment and geography:

SELECT market_segment_fk, country, state, SUM(value) loyalty_value
FROM bic_sumv_loyalty
WHERE org_id = :p_org_id
GROUP BY market_segment_fk, country, state;

To confirm installation, query the data dictionary before relying on the view:

SELECT view_name, status FROM all_views WHERE view_name = 'BIC_SUMV_LOYALTY';

Where the view is absent, equivalent logic should be reimplemented against BIC_PARTY_SUMM_V or the current customer intelligence summary objects supported in the release.