Results for “bic_customer_summary”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIC_CUSTOMER_SUMMARY is a reporting view associated with the BIC – Customer Intelligence product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Customer Intelligence was an analytical layer designed to surface customer-level metrics, scoring, and historical trending for use by downstream reporting tools and dashboards. The view presents a denormalized, consumption-ready projection of customer summary data, exposing measure values segmented by time period and by "bucket" — a symbolic grouping identifier used to categorize or band the underlying measure.
In Oracle EBS 12.2.2, the BIC module is documented as obsolete. The ETRM metadata explicitly records the view as "Not implemented in this database," meaning no runtime object exists in the delivered 12.2.2 environment. It persists in the reference documentation as a legacy artifact for upgrade and migration analysis. Reporting and integration teams should therefore treat the object as informational rather than operational, and any ETL or BI asset that references it must be re-pointed to a supported equivalent. The presence of ORG_ID and SECURITY_GROUP_ID confirms that the object was designed as a multi-org, multi-tenant-aware summary structure, consistent with the wider EBS data model.
Underlying Base Objects
The view is defined entirely over a single base object:
- BIC_CUSTOMER_SUMMARY_ALL — the _ALL suffixed table that holds the actual rows. The view is a thin projection over this table, selecting the full column list without joins, filters, or aggregation.
No other referenced base objects are documented in the ETRM metadata; there are no joins to customer, period, or measure dimension tables within the view text itself. Because the definition is a straightforward SELECT over the _ALL table, the view essentially provides a naming convention alias to the multi-org base table. In EBS, _ALL tables typically carry rows across operating units, with the corresponding non-_ALL view applying an ORG_ID restriction — in this case the view does not apply such a filter, so ORG_ID remains an exposed column requiring explicit qualification by the consumer.
Key Columns
The view exposes eighteen columns. The most significant are:
- MEASURE_ID — identifies the specific customer intelligence metric being summarized (for example, revenue, order count, or a score component).
- PERIOD_START_DATE — the effective start of the summary period, establishing the time dimension for trending and period-over-period comparisons.
- CUSTOMER_ID — the customer or party identifier to which the measure applies.
- BUCKET_ID — the bucket into which the measure value falls or by which it is categorized. This is the column most frequently referenced in ad hoc queries, particularly for searches using the term "bucket_id," and it enables banding, distribution, or segmentation analysis.
- VALUE — the numeric measure amount for the given customer, period, and bucket combination.
- SCORE — a derived scoring value, typically used in ranking or customer prioritization.
- ORG_ID — the operating unit owning the row, central to multi-org security and query filtering.
- SECURITY_GROUP_ID — the security group context for the row.
- Audit and concurrent program columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — supporting lineage, audit, and re-run tracing of the concurrent process that populated the row.
Common Use Cases and Queries
The intended consumption pattern is straightforward summarization by customer, measure, period, and bucket. A typical historical query, still valid against 12.1.1 installations where the object exists, retrieves bucket-level breakdowns for a given measure:
- SELECT customer_id, period_start_date, bucket_id, value, score FROM bic_customer_summary WHERE measure_id = :measure_id AND org_id = :org_id ORDER BY customer_id, period_start_date, bucket_id;
- Aggregating VALUE by BUCKET_ID to produce distribution or banding reports across the customer base.
- Filtering on SCORE to isolate high-value or high-priority customers for targeted follow-up.
- Joining CUSTOMER_ID to customer master views to render human-readable names in BI Publisher or OBIEE output.
- Driving period-over-period comparisons via PERIOD_START_DATE for trend reporting.
Before adopting any of these patterns in 12.2.2, confirm object existence with a data dictionary query against ALL_VIEWS. Where the object is absent, the analytical capability must be sourced from a supported alternative, and the upgrade impact of the obsolete BIC layer should be assessed in parallel with any customization or extension that referenced it.
-
View: BIC_CUSTOMER_SUMMARY 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_CUSTOMER_SUMMARY 12.1.1
Not implemented in this database·Explore BIC module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2