Search Results bis_bucket




Overview
Explore in AI Chat

Overview

The BIS_BUCKET table is a configuration and metadata object within the BIS (Applications BIS) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It defines the bucket structures used by the BIS measurement and analytics framework to categorize numeric values into discrete ranges. Each row describes a named bucket definition together with a set of up to ten lower and upper boundary pairs, allowing a single definition to express complex multi-range segmentation logic for a measured quantity. This makes BIS_BUCKET a foundational reference table for any reporting, scoring, or threshold-driven process that relies on standardized bucketing rather than ad hoc CASE expressions.

The documented heuristic Data Vault classification for this object is standalone, with a single foreign key to BIC_MEASURE_BUCKETS. In Data Vault modeling terms this suggests the table behaves primarily as a hub-like reference entity rather than a transactional satellite or link, since it carries its own natural business keys (BUCKET_ID and SHORT_NAME) and does not depend on a parent transaction to exist.

Key Information Stored

The table contains 34 columns. The most significant are described below.

  • BUCKET_ID — Surrogate primary key for the bucket definition, enforced by unique index BIS_BUCKET_U1. It is also the column participating in the foreign key to BIC_MEASURE_BUCKETS.
  • SHORT_NAME — The user-facing business key, enforced by unique index BIS_BUCKET_U2. Used to identify the bucket definition in configuration screens and queries.
  • TYPE — Classifies the kind of bucket (for example, range-based versus discrete) and drives how the boundary columns are interpreted.
  • APPLICATION_ID — Identifies the Oracle application context to which the bucket definition belongs, enabling multi-application coexistence within the BIS schema.
  • RANGE1_LOW through RANGE10_HIGH — Ten pairs of lower and upper boundary values that collectively define the bucket segments. A definition may use only a subset of the available pairs.
  • UPDATABLE, EXPANDABLE, DISCONTINUOUS, OVERLAPPING — Boolean-style flags describing the behavioral characteristics of the bucket set, such as whether ranges may overlap, whether gaps are permitted, and whether the definition can be extended.
  • UOM — Unit of measure associated with the boundary values, ensuring range comparisons are dimensionally consistent.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns providing audit lineage.

The surrogate key is BUCKET_ID; SHORT_NAME is the alternate business-key candidate for external reference.

Common Use Cases and Queries

Typical usage centers on resolving a measured value into its bucket label, or enumerating all definitions available to a given application.

  • Retrieving all bucket definitions for an application: SELECT BUCKET_ID, SHORT_NAME, TYPE FROM BIS.BIS_BUCKET WHERE APPLICATION_ID = :app_id;
  • Locating a definition by business key: SELECT * FROM BIS.BIS_BUCKET WHERE SHORT_NAME = :name;
  • Resolving a value into a segment by comparing against RANGE1_LOW/RANGE1_HIGH pairs in order until a match is found.
  • Reporting on definitions that permit overlap or discontinuity, using the OVERLAPPING and DISCONTINUOUS flags, to audit data quality of configuration.

Related Objects

  • BIC_MEASURE_BUCKETS — Referenced by the foreign key BIS_BUCKET.BUCKET_ID, linking bucket definitions to the measure bucketing assignments.
  • BIS_BUCKET_U1 / BIS_BUCKET_U2 — Unique indexes enforcing the surrogate and business-key candidates.
  • Other BIS measurement configuration tables in the BIS schema that consume bucket definitions for metric evaluation.