Results for “bic_sumv_lifecycle”

4 results




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

Overview

BIC_SUMV_LIFECYCLE is a read-only database view belonging to the BIC (Customer Intelligence) product family within Oracle E-Business Suite. In releases 12.1.1 and 12.2.2, the BIC module is documented as obsolete, meaning the object is retained for backward compatibility and historical reference rather than active functional use. The view presents customer lifecycle stage data aggregated by period, exposing the lifecycle value assigned to parties (customers) across defined time periods. Its purpose is to support analytical reporting on customer lifecycle progression, market segments, and customer categories.

The view is defined WITH READ ONLY, preventing DML operations and reinforcing its role as a reporting-only construct. The ETRM documentation explicitly notes that BIC_SUMV_LIFECYCLE is "Not implemented in this database," indicating that in the captured environment the view was not instantiated, though its definition remains catalogued.

Underlying Base Objects

BIC_SUMV_LIFECYCLE is defined over a single documented base object: BIC_PARTY_STATUS_SUMM_V. The view is a filtered projection of that source, restricting rows to those where the LIFE_CYCLE column is not null. The ETRM metadata records no additional referenced base tables, and the parent object BIC_PARTY_STATUS_SUMM_V is itself a view (indicated by the "_V" suffix), meaning the lineage ultimately resolves to underlying party status summary tables within the BIC schema.

All columns exposed by BIC_SUMV_LIFECYCLE are inherited from the parent view; only one column, LIFE_CYCLE, is renamed to VALUE, and LIFE_CYCLE itself is used solely as the filter predicate. This aliasing indicates the view is purpose-built to present lifecycle as the primary measure of interest, suppressing rows without a defined lifecycle stage.

Key Columns

Common Use Cases and Queries

Because the BIC module is obsolete, this view is typically encountered during upgrades, custom report reviews, or data lineage audits rather than in new development. Nonetheless, its structure suits standard customer-lifecycle reporting: distribution of parties by lifecycle stage, lifecycle movement across periods, and segmentation by geography or market segment.

A representative query counts parties per lifecycle value within a given accounting year:

  • SELECT ACT_YEAR, VALUE, COUNT(DISTINCT PARTY_ID) AS PARTY_COUNT FROM BIC_SUMV_LIFECYCLE GROUP BY ACT_YEAR, VALUE ORDER BY ACT_YEAR, VALUE;

To profile lifecycle stages by market segment and country:

  • SELECT MARKET_SEGMENT_FK, COUNTRY, VALUE, COUNT(*) AS CNT FROM BIC_SUMV_LIFECYCLE GROUP BY MARKET_SEGMENT_FK, COUNTRY, VALUE;

For time-series tracking of a single party:

  • SELECT PERIOD_START_DATE, VALUE FROM BIC_SUMV_LIFECYCLE WHERE PARTY_ID = :party_id ORDER BY PERIOD_START_DATE;

Queries should confirm the view exists in the target instance, since the ETRM record states it is not implemented in the documented database. Where absent, equivalent analysis may be reconstructed directly from BIC_PARTY_STATUS_SUMM_V by applying the same non-null lifecycle filter.