Results for “bis_bucket_customizations”

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

Overview

BIS_BUCKET_CUSTOMIZATIONS is a table owned by the BIS schema (Applications BIS) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its status is VALID. The name and the column set indicate that it stores user-defined customization of "measure buckets" — threshold ranges applied to bucketized metrics defined in the related BIC_MEASURE_BUCKETS table. Where the base bucket definition fixes default numeric boundaries, BIS_BUCKET_CUSTOMIZATIONS lets a specific context (user, responsibility, operating unit, application, site, page, or function) override those boundaries with up to ten customized low/high ranges.

From a heuristic Data Vault perspective mined from the foreign-key structure, this object is best modeled as a standalone structure rather than a classic hub, link, or satellite. It carries its own unique business-key index and a natural parent relationship, so it functions as a context-specific configuration artifact rather than a transactional fact.

Key Information Stored

All 35 documented columns are present; the most significant are summarized below.

• ID — the surrogate primary key for each customization row.
• BUCKET_ID — foreign key to BIS_BUCKET_CUSTOMIZATIONS.BUCKET_ID → BIC_MEASURE_BUCKETS, identifying which measure bucket is being customized.
• USER_ID, RESPONSIBILITY_ID, ORG_ID, APPLICATION_ID, SITE_ID, PAGE_ID, FUNCTION_ID — the context dimensions that scope the customization. Together these determine for whom, in which responsibility/organization, and on which application page or function the override applies.
• RANGE1_LOW … RANGE10_HIGH — ten pairs of low/high boundaries defining the customized numeric ranges for the bucket.
• CUSTOMIZED — a flag indicating whether user customization is active for the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns for audit and concurrency.

The unique index BIS_BUCKET_CUSTOMIZATIONS_U1 spans (BUCKET_ID, USER_ID, RESPONSIBILITY_ID, ORG_ID, APPLICATION_ID, SITE_ID, PAGE_ID, FUNCTION_ID), confirming that no duplicate customization may exist for the same bucket within the same context combination. This composite is the business-key candidate, distinct from the ID surrogate key.

Common Use Cases and Queries

Typical scenarios include resolving which range boundaries should be applied when rendering a bucketized metric for a given user and responsibility, auditing where custom thresholds diverge from defaults, and reporting on customized versus standard bucket definitions.

Sample query to find active customizations for a bucket and responsibility:

SELECT c.ID, c.BUCKET_ID, c.USER_ID, c.RESPONSIBILITY_ID,
       c.RANGE1_LOW, c.RANGE1_HIGH, c.CUSTOMIZED
  FROM BIS.BIS_BUCKET_CUSTOMIZATIONS c
 WHERE c.BUCKET_ID = :bucket_id
   AND c.RESPONSIBILITY_ID = :resp_id
   AND c.ORG_ID = :org_id
   AND c.CUSTOMIZED = 'Y';

A reporting pattern joins to the parent bucket table to list customized metrics:

SELECT b.NAME, c.RANGE1_LOW, c.RANGE1_HIGH
  FROM BIS.BIS_BUCKET_CUSTOMIZATIONS c,
       BIS.BIC_MEASURE_BUCKETS b
 WHERE c.BUCKET_ID = b.BUCKET_ID;

Audit queries against LAST_UPDATED_BY and LAST_UPDATE_DATE support change tracking, while exclusion of NULL context columns supports default-scope determination.

Related Objects

• BIC_MEASURE_BUCKETS — parent table referenced via BUCKET_ID; supplies the default bucket definition that this table overrides.
• BIS_BUCKET_CUSTOMIZATIONS_U1 — unique index enforcing business-key uniqueness across the context columns.
• FND_USER — logical reference for USER_ID values.
• FND_RESPONSIBILITY / FND_RESPONSIBILITY_TL — source of RESPONSIBILITY_ID context.
• FND_APPLICATION / FND_APPLICATION_TL — source of APPLICATION_ID context.
• HR_OPERATING_UNITS / ORG tables — source of ORG_ID context.
• FND_FORM_FUNCTIONS — source of FUNCTION_ID context.

These references define the dependency and lookup surface around the customization table; the sole documented foreign-key constraint remains BUCKET_ID to BIC_MEASURE_BUCKETS.