Search Results bic_party_summ_v




Overview
Explore in AI Chat

Overview

BIC_PARTY_SUMM_V is a reporting view delivered within the Oracle E-Business Suite Customer Intelligence (BIC) product family. BIC is oriented toward customer analytics, delivering summarized party-level metrics for use in dashboards, data warehousing extracts, and business intelligence reporting. The view presents a denormalized, ready-to-consume result set that joins customer summary facts to party master attributes and to a time dimension, producing a single row per party per accounting period.

In the EBS 12.1.1 and 12.2.2 documentation sets, the BIC module is explicitly marked Obsolete, and the ETRM metadata records this view as "Not implemented in this database." This means the view is documented for historical and reference purposes only; it is not created in supported instances and cannot be queried directly in a standard installation. Understanding its structure remains useful for legacy migration analysis, for interpreting pre-existing BI extracts, and for reconstructing equivalent logic from supported source tables.

Underlying Base Objects

The view text defines a three-way join over the following objects:

  • BIC_DIMV_TIME (T) — the time dimension view, supplying the accounting calendar attributes used to slice the summary measures. This is the object the user searched for under the term "bic_dimv_time."
  • HZ_PARTIES (P) — the trading community party master, supplying names, addresses, category codes, and creation dates.
  • BIC_PARTY_SUMM (S) — the party summary fact object, supplying loyalty, satisfaction, sales, cost of goods sold, and profitability measures keyed by period and party.

The join predicates are S.PERIOD_START_DATE = T.START_DATE and S.PARTY_ID = P.PARTY_ID. The ETRM metadata lists no separately documented base tables, so the base-object relationship is established entirely through the view text above.

Key Columns

The projected columns fall into three logical groups.

Common Use Cases and Queries

Typical usage patterns include customer profitability reporting by period and calendar roll-up, loyalty and satisfaction trending, and party-level segmentation extracts for downstream BI tools. The denormalized time attributes eliminate the need for a separate date-dimension join in most reports.

The following example returns annual profitability totals for a single operating unit:

  • SELECT ACT_YEAR, PARTY_NAME, SUM(SALES) SALES, SUM(PROFITABILITY) PROFIT FROM BIC_PARTY_SUMM_V WHERE ORG_ID = :p_org_id GROUP BY ACT_YEAR, PARTY_NAME ORDER BY ACT_YEAR, PROFIT DESC;

A second pattern examines loyalty and satisfaction by market segment and quarter:

  • SELECT ACT_YEAR, ACT_QUARTER, MARKET_SEGMENT_FK, AVG(LOYALTY) AVG_LOYALTY, AVG(SATISFACTION) AVG_SATISFACTION FROM BIC_PARTY_SUMM_V GROUP BY ACT_YEAR, ACT_QUARTER, MARKET_SEGMENT_FK;

Because the view is obsolete and undocumented against a live schema, these statements are illustrative. Equivalent results in supported releases must be assembled directly from HZ_PARTIES and the surviving summary and time-dimension objects.