Search Results act_period_start_date




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. Customer Intelligence was a customer analytics product introduced in earlier EBS releases to support segmentation, profiling, and loyalty-oriented reporting against trading partners and customers. In EBS 12.1.1 and 12.2.2 the module is classified as obsolete, meaning it is retained only for backward compatibility and is no longer delivered or supported as part of new implementations. The ETRM metadata confirms this status and further documents that the view is "not implemented in this database" in the reference environment, so its presence in a given instance depends on whether legacy BIC objects were ever installed or subsequently dropped.

The view exposes a period-based snapshot of loyalty measures at the party level, enriched with calendar and fiscal roll-up attributes. Its principal role is analytical rather than transactional: it supplies pre-aggregated loyalty values that can be joined to customer, organization, and geography dimensions for dashboard, ad hoc, or extract reporting. Because the object is a view with a WITH READ ONLY clause, it cannot be used as a DML target.

Underlying Base Objects

According to the documented view text, BIC_SUMV_LOYALTY is defined over a single underlying object, BIC_PARTY_SUMM_V, and simply projects a subset of that view's columns. The ETRM metadata lists no separate base tables, so the lineage terminates at BIC_PARTY_SUMM_V, which in turn derives from the customer intelligence summary tables (typically BIC_PARTY_SUMMARY and its dimension joins) in a standard BIC installation. No valid base objects are documented for the reference database, consistent with the obsolete classification. All column names and datatypes are inherited from BIC_PARTY_SUMM_V; the view adds no expressions, filters, or joins of its own.

Key Columns

Common Use Cases and Queries

The view is typically consumed for quarterly loyalty trending, segment comparison, and geography-based roll-ups. A representative quarterly aggregation is:

SELECT act_year, act_quarter, org_id, SUM(value) loyalty_total
FROM   bic_sumv_loyalty
WHERE  act_year = :year
GROUP  BY act_year, act_quarter, org_id
ORDER  BY act_quarter;

Segment-level analysis adds the market segment key:

SELECT act_quarter, market_segment_fk, AVG(value) avg_loyalty
FROM   bic_sumv_loyalty
WHERE  act_period_start_date BETWEEN :from_date AND :to_date
GROUP  BY act_quarter, market_segment_fk;

Before writing new reports, verify availability with SELECT * FROM all_views WHERE view_name = 'BIC_SUMV_LOYALTY', since the object is obsolete and may be absent or invalid. Where present, it remains a convenient read-only source for period and quarter loyalty analytics without direct access to the underlying BIC summary tables.