Search Results bic_party_summary




Overview
Explore in AI Chat

Overview

The BIC_PARTY_SUMMARY table resides in the BIC schema, which is the physical owner of the Customer Intelligence (BIC) product in Oracle E-Business Suite releases 12.1.1 and 12.2.2. BIC is documented as an obsolete module, and this table exists primarily to hold pre-aggregated, non-organization-striped customer measures produced by the concurrent program "Extract Customer Summary." Rather than computing customer metrics on demand from transactional tables, BIC materializes summary values here on a periodic basis, keyed by party, measure, and accounting period. The table is populated as part of the Customer Intelligence extraction cycle and is intended for reporting and downstream intelligence consumption.

From a Data Vault modeling perspective, a heuristic classification derived from the foreign-key structure suggests that BIC_PARTY_SUMMARY behaves as a satellite-leaning table. Its grain is described by the combination of a party (business key) plus a measure and period, while descriptive and numeric payload columns (VALUE, SCORE) attach context to that business key. It is not a pure hub or link, but its design is consistent with a satellite that hangs off the HZ_PARTIES hub.

Key Information Stored

The table contains 18 documented columns. The most significant include:

The documented business-key candidate is the unique index BIC_PARTY_SUMMARY_U1, defined over (PERIOD_START_DATE, PARTY_ID, MEASURE_ID), which confirms the intended grain of one row per party, per measure, per period.

Common Use Cases and Queries

Because BIC is obsolete, the primary uses of this table are historical reporting, data migration, and auditing of prior customer intelligence extracts. Typical queries join to HZ_PARTIES to resolve party names and to BIC_MEASURE_BUCKETS to obtain bucket definitions.

A representative query retrieves the current-period measure value for a specific customer:

  • SELECT p.party_name, s.measure_code, s.value, s.score FROM bic.bic_party_summary s JOIN hz_parties p ON p.party_id = s.party_id WHERE s.party_id = :party_id AND s.period_start_date = :period AND s.security_group_id = :sgid;

Other common patterns include aggregating VALUE by MEASURE_CODE across all parties for a given PERIOD_START_DATE, tracing rows back to their originating concurrent request via REQUEST_ID, and filtering rows by SECURITY_GROUP_ID to honor data-security policies in reporting tools.

Related Objects

  • HZ_PARTIES — joined via BIC_PARTY_SUMMARY.PARTY_ID; the master party/customer definition.
  • BIC_MEASURE_BUCKETS — joined via BIC_PARTY_SUMMARY.BUCKET_ID; provides bucket or banding definitions for measure values.
  • FND_SECURITY_GROUPS — joined via BIC_PARTY_SUMMARY.SECURITY_GROUP_ID; enforces EBS security group access.
  • "Extract Customer Summary" concurrent program — the population process registered as PROGRAM_ID/REQUEST_ID references that fills this table.
  • BIC measure definition tables — referenced through MEASURE_ID and MEASURE_CODE, providing measure metadata.

Together these relationships make BIC_PARTY_SUMMARY a dependent satellite of the party dimension, used for reporting and scoring workflows within an obsolete BIC deployment.