Search Results bic_party_summary_u1

Overview

BIC.BIC_PARTY_SUMMARY is a summary (aggregate) table in the Customer Intelligence (BIC) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores pre-computed Customer Intelligence measures at the party (customer) and period level. The table is owned by the BIC schema, resides in the APPS_TS_SUMMARY tablespace, and is described in FND Design Data as BIC.BIC_PARTY_SUMMARY. Its documented purpose is to hold Customer Intelligence summary information populated by the concurrent program Extract Customer Summary, specifically for non-Org striped measures.

Because the table is fed exclusively by a concurrent extraction process and carries the full set of concurrent-program WHO columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) as well as standard WHO auditing columns, it functions as a derived reporting store rather than a transactional entry point. Under the heuristic Data Vault classification mined from its foreign-key structure, the table is satellite-leaning: it holds descriptive, periodically refreshed measure values keyed to a party hub (HZ_PARTIES) and a bucket reference, rather than acting as a hub or a many-to-many link. This classification is offered as a modeling suggestion only.

Key Information Stored

The documented physical schema contains 18 columns. The most significant are:

• MEASURE_ID (NUMBER) — identifier of the Customer Intelligence measure being summarized; part of the unique business key.
• PERIOD_START_DATE (DATE) — the start of the reporting period the row covers; part of the unique business key.
• PARTY_ID (NUMBER) — foreign key to HZ_PARTIES, identifying the customer to whom the measure applies; part of the unique business key.
• BUCKET_ID (NUMBER) — foreign key to BIC_MEASURE_BUCKETS, defining the bucketing/range applied to the measure value.
• VALUE (NUMBER) — the computed numeric measure value for the party, period, measure, and bucket combination.
• SCORE (NUMBER) — a scored or derived value associated with the measure.
• MEASURE_CODE — a code form of the measure; note that it is indexed by the non-unique index BIC_PARTY_SUMMARY_N1.
• SECURITY_GROUP_ID (NUMBER) — foreign key to FND_SECURITY_GROUPS, supporting multi-org/security-group partitioning of rows.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — capture row audit history.
• Concurrent Program WHO columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — record which concurrent request last populated the row.

The documented unique index BIC_PARTY_SUMMARY_U1 is defined on (PERIOD_START_DATE, PARTY_ID, MEASURE_ID) in the APPS_TS_SUMMARY tablespace, making this triple the business-key candidate that enforces one row per party, measure, and period. The non-unique index BIC_PARTY_SUMMARY_N1 on MEASURE_CODE supports measure-oriented filtering.

Common Use Cases and Queries

Typical usage centers on Customer Intelligence dashboards, customer scoring reports, and analytical extracts that need summarized measure values without scanning transactional data.

• Retrieve all measures for a given customer in a period, joining to HZ_PARTIES for the party name.
• Report measure values by MEASURE_CODE or MEASURE_ID across a date range, aggregating VALUE or averaging SCORE.
• Audit which concurrent request populated a set of rows by filtering on REQUEST_ID or PROGRAM_ID.

A representative query pattern:

• SELECT ps.party_id, ps.period_start_date, ps.measure_id, ps.measure_code, ps.value, ps.score
• FROM bic.bic_party_summary ps
• WHERE ps.party_id = :party_id
• AND ps.period_start_date BETWEEN :start_date AND :end_date
• ORDER BY ps.period_start_date, ps.measure_id;

Because the unique key begins with PERIOD_START_DATE, date-bounded queries exploit BIC_PARTY_SUMMARY_U1 efficiently; measure-code filters benefit from BIC_PARTY_SUMMARY_N1.

Related Objects

• HZ_PARTIES — referenced by BIC_PARTY_SUMMARY.PARTY_ID; supplies the customer definition behind each summarized row.
• BIC_MEASURE_BUCKETS — referenced by BIC_PARTY_SUMMARY.BUCKET_ID; defines bucket/range metadata for measure values.
• FND_SECURITY_GROUPS — referenced by BIC_PARTY_SUMMARY.SECURITY_GROUP_ID; governs row-level security partitioning.
• FND_USER — implied foreign key target for LAST_UPDATED_BY and CREATED_BY.
• FND_CONCURRENT_REQUESTS — implied foreign key target for REQUEST_ID, identifying the extraction run.
• FND_CONCURRENT_PROGRAM — implied foreign key target for PROGRAM_ID; the Extract Customer Summary concurrent program is the documented populator of this table.
• FND_APPLICATION — implied foreign key target for PROGRAM_APPLICATION_ID.

These relationships confirm the table's role as a satellite-style aggregate anchored to the party hub and refreshed by the Extract Customer Summary concurrent program.