Search Results act_quarter_start_date




Overview
Explore in AI Chat

Overview

BIC_SUMV_LOYALTY is a reporting view historically shipped with the Oracle E-Business Suite Customer Intelligence (BIC) module. Customer Intelligence was an analytical layer built on top of Oracle Marketing and Oracle Trade Management data, designed to surface customer-level summaries for segmentation, campaign targeting, and loyalty analysis. The SUMV prefix in the view name indicates a summary view, while the LOYALTY suffix identifies its subject area.

The view is documented as obsolete and is explicitly recorded as not implemented in the reference database. In EBS 12.1.1 and 12.2.2 environments where the BIC product family was never licensed or deployed, the view will not exist at all. Where remnants persist, it exists only as a read-only projection over a single underlying summary table. Its role in reporting and integration is therefore limited to legacy environments that were originally provisioned with Customer Intelligence.

Underlying Base Objects

The view text is a straightforward projection defined entirely over one base object:

  • BIC_PARTY_SUMM_V — a party-level summary view supplying all columns exposed by BIC_SUMV_LOYALTY.

The view is declared WITH READ ONLY, so no DML is permitted against it; it is a query-only construct. The ETRM metadata records no additional referenced base objects, and no separate owner or synonym chain is documented. Because BIC_SUMV_LOYALTY adds no joins, filters, or expressions, it is a column-slicing convenience view rather than a transformation layer. Any change to BIC_PARTY_SUMM_V propagates directly.

Key Columns

The projection exposes nineteen columns, which fall into four logical groups.

The column of interest to users searching on act_quarter_start_date is ACT_QUARTER_START_DATE, which returns the first day of the accounting quarter to which the row's summary period belongs. It is the correct field for quarter-bucketing loyalty values without deriving the boundary in SQL.

Common Use Cases and Queries

The primary use case is period-over-period loyalty reporting grouped by customer, segment, or region, using the accounting calendar columns to align with financial reporting cycles.

Quarter-level loyalty by market segment:

SELECT act_year,
       act_quarter,
       act_quarter_start_date,
       market_segment_fk,
       SUM(value) AS loyalty_value
FROM   bic_sumv_loyalty
WHERE  org_id = :p_org_id
GROUP  BY act_year, act_quarter, act_quarter_start_date, market_segment_fk
ORDER  BY act_quarter_start_date;

Party-level detail for a single accounting period:

SELECT party_id, country, city, state, value
FROM   bic_sumv_loyalty
WHERE  act_period_name = :p_period
AND    org_id = :p_org_id;

Because the object is documented as obsolete and not implemented, developers should confirm its existence before use and treat it as read-only legacy reporting infrastructure. New development should target supported Customer Intelligence or Marketing Analytics alternatives rather than this view.