Search Results bic_measures_u1

Overview

BIC.BIC_MEASURES_ALL is a seeded reference table within the Oracle E-Business Suite BIC (Business Intelligence Center / Customer Intelligence) schema. Its purpose is to store the master list of measures — quantifiable business metrics such as revenue, order counts, or satisfaction scores — that the Customer Intelligence application makes available to users. The table is created in the APPS_TS_SEED tablespace, confirming its role as a controlled, seed-managed object. Measures are pre-seeded for each operating unit; end users cannot insert or delete rows, but they may selectively disable measures and assign weights, thereby influencing aggregation and scoring behavior. In Oracle EBS 12.1.1 and 12.2.2 the table is registered as FND Design Data with owner BIC, status VALID.

From a Data Vault modeling standpoint, the metadata classifies BIC_MEASURES_ALL as satellite-leaning. It carries descriptive, relatively static reference attributes rather than functioning as a pure hub or transaction link. This classification is a heuristic suggestion derived from the foreign-key structure, not an EBS-imposed constraint.

Key Information Stored

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

• MEASURE_ID — Surrogate primary key (BIC_MEASURES_ALL_PK) and unique business identifier via index BIC_MEASURES_U1. Links to BIC_MEASURE_BUCKETS.MEASURE_ID.
• MEASURE_CODE — Internal code (VARCHAR2(30)); part of unique index BIC_MEASURES_U2.
• ORG_ID — Operating unit identifier; also part of BIC_MEASURES_U2, enabling measure configuration per operating unit.
• NAME — Display name of the measure (VARCHAR2(60)).
• DESCRIPTION — Descriptive text (VARCHAR2(240)).
• ENABLED_FLAG — Controls whether a measure is active; set to 'N' to suppress use.
• WEIGHT — User-definable numeric weight for each measure.
• TIME_UNIT_CODE — Period grain (month, quarter, etc.) sourced from CS_LOOKUPS where lookup_type='BIC_TIME_CODE'.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS for row-level security.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• ZD_EDITION_NAME — Editioning column present in 12.2.2 for online patching; included in both unique indexes.

Common Use Cases and Queries

Typical uses include validating measure configuration, reporting on enabled measures, and driving weighting logic in customer intelligence scoring. A representative query for enabled measures for a given operating unit:

• SELECT MEASURE_CODE, NAME, WEIGHT, TIME_UNIT_CODE FROM BIC.BIC_MEASURES_ALL WHERE ORG_ID = :org_id AND ENABLED_FLAG = 'Y';
• Join to buckets: SELECT M.NAME, B.* FROM BIC.BIC_MEASURES_ALL M, BIC.BIC_MEASURE_BUCKETS B WHERE M.MEASURE_ID = B.MEASURE_ID AND M.ORG_ID = :org_id;
• Obtain time-unit lookup meaning: join TIME_UNIT_CODE to CS_LOOKUPS using lookup_type='BIC_TIME_CODE'.
• Audit configuration changes using CREATION_DATE, LAST_UPDATE_DATE and the Who columns.

Related Objects

The most significant related objects include:

• BIC.BIC_MEASURE_BUCKETS — References BIC_MEASURES_ALL.MEASURE_ID; defines value ranges per measure.
• BIC.BIC_MEASURE_ATTRIBS — Joined on MEASURE_CODE; holds attribute definitions.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID.
• FND_USER — Implicit reference via CREATED_BY / LAST_UPDATED_BY.
• FND_LOGINS — Implicit reference via LAST_UPDATE_LOGIN.
• CS_LOOKUPS — Supplies TIME_UNIT_CODE values under lookup_type 'BIC_TIME_CODE'.