Results for “std_value”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIC_STANDARD_VALUES is a table owned by the BIC schema, part of the Customer Intelligence (BIC) product family. In Oracle EBS 12.1.1 and 12.2.2, BIC is documented as obsolete, meaning the module is retained for backward compatibility and historical data retention rather than for active functional use. The table stores industry standard values used as benchmarks for satisfaction measurement, allowing organizations to compare internal performance metrics against externally defined or industry-derived thresholds.

From a Data Vault modeling perspective, the mined classification is satellite-leaning. Its primary key combines MEASURE_CODE and PERIOD_START_DATE, and it references BIC_MEASURE_ATTRIBS, suggesting it functions as a descriptive satellite attached to a measure hub rather than as an independent hub or a link table. The periodic key component implies time-variant descriptive attributes, consistent with satellite behavior.

Key Information Stored

The table contains 13 documented columns. The most significant are listed below.

• MEASURE_CODE — Identifier for the satisfaction measure. Part of the composite primary key and foreign key to BIC_MEASURE_ATTRIBS.
• PERIOD_START_DATE — Start date of the period to which the standard value applies. Completes the composite primary key.
• STD_VALUE — The industry standard or benchmark value itself.
• LAST_UPDATE_DATE — Timestamp of the most recent modification, used for change tracking and incremental extracts.
• LAST_UPDATED_BY — User who performed the last update.
• CREATION_DATE — Timestamp of record creation.
• CREATED_BY — User who created the record.
• LAST_UPDATE_LOGIN — Login identifier associated with the last update, useful for audit trails.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns captured when records are inserted or updated through EBS concurrent processing.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting data segregation in a multi-organization deployment.

The primary key BIC_STANDARD_VALUES_PK is defined on (MEASURE_CODE, PERIOD_START_DATE). A unique index, BIC_STANDARD_VALUES_U1, mirrors the same column pair, confirming the business key. The documented columns do not include a single-column surrogate key, so identification relies on the natural composite business key.

Common Use Cases and Queries

Because BIC is obsolete, the primary use cases are historical reporting, data migration validation, and archival extracts. The table supports benchmarking queries that compare actual satisfaction scores against the stored standard values for a given measure and period.

A typical pattern retrieves the benchmark for a measure in effect on a specific date:

• SELECT std_value FROM bic.bic_standard_values WHERE measure_code = :measure AND period_start_date = :period_start;
• SELECT s.measure_code, s.period_start_date, s.std_value FROM bic.bic_standard_values s WHERE s.period_start_date BETWEEN :from_date AND :to_date ORDER BY s.measure_code, s.period_start_date;
• SELECT s.measure_code, s.std_value, m.attribute_value FROM bic.bic_standard_values s JOIN bic.bic_measure_attribs m ON s.measure_code = m.measure_code WHERE s.period_start_date = :period_start;

Reporting use cases include trend reporting across periods, benchmarking dashboards, and reconciliation of legacy satisfaction targets prior to decommissioning BIC components.

Related Objects

The following objects are most relevant based on documented foreign key and primary key relationships.

• BIC_MEASURE_ATTRIBS — Referenced via BIC_STANDARD_VALUES.MEASURE_CODE, providing descriptive attributes for each measure.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID, controlling access to records across security groups.
• BIC_STANDARD_VALUES_PK — Primary key constraint on (MEASURE_CODE, PERIOD_START_DATE).
• BIC_STANDARD_VALUES_U1 — Unique index enforcing uniqueness on the same business-key columns.

Because BIC is obsolete, no active public APIs or views are documented for this table. Any downstream dependency should be validated against the specific implementation environment before relying on this object.