Search Results bic_party_status_summ_v




Overview
Explore in AI Chat

Overview

The view BIC_PARTY_STATUS_SUMM_V belongs to the Oracle E-Business Suite product family BIC — Customer Intelligence, a component that is documented in the ETRM repository as obsolete in release 12.1.1 and 12.2.2. Customer Intelligence was an analytical layer built on top of the trading community model, intended to expose customer lifecycle and party-status metrics for reporting and downstream integration. This view presents a consolidated, denormalized snapshot of party status summarization data joined to party master attributes and a time dimension. Its role is analytical rather than transactional: it flattens the party status summary fact records into a wide, query-friendly structure that reporting tools and custom concurrent programs could consume directly without additional joins.

Because the product is flagged obsolete, the view should be treated as a legacy artifact. It remains useful for understanding historical data models and for maintaining backward compatibility in customizations that still reference it.

Underlying Base Objects

The documented view text defines the object over three sources:

  • BIC_PARTY_STATUS_SUMM S — the primary fact table containing period-based status measures (acquisition, activation, retention, life cycle) keyed by PERIOD_START_DATE and PARTY_ID.
  • HZ_PARTIES P — the trading community party master, supplying party name, category code, address, and contact attributes.
  • BIC_DIMV_TIME T — the Customer Intelligence time dimension, providing accounting and calendar period attributes.

The join is driven by two equality predicates: S.PERIOD_START_DATE = T.START_DATE and S.PARTY_ID = P.PARTY_ID. The ETRM metadata records no referenced base objects for the 12.2.2 documentation set and reports the view as not implemented in the reference database, so it may be absent from a given installation even though the definition exists in the data dictionary.

Key Columns

The view exposes thirty-one columns, which fall into three functional groups:

Common Use Cases and Queries

Typical uses include customer acquisition trending by fiscal period, retention analysis by market segment, and lifecycle distribution reporting for a party population. A representative query aggregates acquisition counts by accounting period:

SELECT ACT_YEAR, ACT_PERIOD_NUM, ACT_PERIOD_NAME, SUM(ACQUISITION) ACQ
FROM BIC_PARTY_STATUS_SUMM_V
GROUP BY ACT_YEAR, ACT_PERIOD_NUM, ACT_PERIOD_NAME
ORDER BY ACT_YEAR, ACT_PERIOD_NUM;

A second pattern filters a single party to review its status history across periods:

SELECT PERIOD_START_DATE, ACQUISITION, ACTIVATION, RETENTION, LIFE_CYCLE
FROM BIC_PARTY_STATUS_SUMM_V
WHERE PARTY_ID = :p_party_id
ORDER BY PERIOD_START_DATE;

Because the object is documented as obsolete and not implemented in the reference database, any query should be preceded by a data dictionary check confirming that the view exists in the target instance.