Search Results bis_bucket_u2

Overview

The BIS.BIS_BUCKET table is a core configuration object within the Oracle E-Business Suite Business Intelligence System (BIS) schema, which underpins the Daily Business Intelligence (DBI) and Enterprise Performance Management reporting layers. This table stores the bucket information used to categorize, segment, and group numeric measures into discrete ranges, enabling trend, distribution, and comparison-style analytics across subject areas such as financials, supply chain, and order management. Each bucket defines up to ten low/high range pairs, allowing a single bucket definition to describe multi-dimensional banding or percentile-style segmentation applied to a measure.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone, meaning it does not act purely as a hub with downstream link and satellite dependencies in the mining derived from the foreign-key structure. In practice, however, BUCKET_ID functions as a business hub-like key and the descriptive attributes (ranges, flags, unit of measure) behave as attached satellite data. Designers implementing a Data Vault pattern around this object would typically model BUCKET_ID as a hub and the range and flag columns as satellite attributes.

Key Information Stored

The table contains 34 documented columns. The most significant are:

• BUCKET_ID (NUMBER) — The surrogate primary key, uniquely enforced by index BIS_BUCKET_U1.
• SHORT_NAME (VARCHAR2(30)) — The business-key candidate, uniquely enforced by index BIS_BUCKET_U2; this is the index referenced by the search term bis_bucket_u2.
• TYPE (VARCHAR2(30)) — Classifies the bucket, driving how ranges are interpreted.
• APPLICATION_ID (NUMBER) — Associates the bucket with a specific EBS application.
• RANGE1_LOW … RANGE10_HIGH — Ten low/high numeric pairs defining the segment boundaries.
• UPDATABLE, EXPANDABLE, DISCONTINUOUS, OVERLAPPING (VARCHAR2) — T/F flags controlling bucket behavior at runtime.
• UOM (VARCHAR2(10)) — Unit of measure for the range values.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include resolving a measure value to its bucket, listing all active buckets for a given application, and auditing bucket configurations prior to reporting changes.

• Lookup by short name:
  SELECT * FROM BIS.BIS_BUCKET WHERE SHORT_NAME = :p_short_name;
  This leverages the unique index BIS_BUCKET_U2.
• Buckets for a subject area:
  SELECT BUCKET_ID, SHORT_NAME, TYPE FROM BIS.BIS_BUCKET WHERE APPLICATION_ID = :app_id;
• Range inspection: Query the RANGE*_LOW/RANGE*_HIGH pairs to validate that OVERLAPPING and DISCONTINUOUS flags are consistent with the configured boundaries.
• Audit reporting: Join the audit columns to FND_USER to trace who last modified a bucket definition.

Related Objects

• BIS.BIC_MEASURE_BUCKETS — The primary dependent table; it references BIS_BUCKET.BUCKET_ID via foreign key, linking bucket definitions to specific measures.
• BIS.BIC_MEASURES_B / BIC_MEASURES_TL — Measure definitions that consume buckets through the BIC_MEASURE_BUCKETS association.
• BIS.BIS_BUCKET_U1 and BIS.BIS_BUCKET_U2 — The unique indexes supporting the primary and business keys.
• DBI subject-area views (for example, financial and supply-chain dashboard views) that resolve measure values into bucket bands at query time.

No additional child tables with foreign keys into BIS_BUCKET are documented beyond BIC_MEASURE_BUCKETS in the ETRM relationship data, and the table is classified as standalone from the FK-mining perspective.