Search Results bis_bucket_tl




Overview
Explore in AI Chat

Overview

BIS_BUCKET_TL is a translation table in the BIS (Applications BIS) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores language-specific, translated display values for the range labels that define the individual buckets of a balance or measure bucket set. The suffix "_TL" identifies the table as a translation layer that accompanies the base BIS_BUCKET entity, enabling the same bucket definition to be presented with localized descriptive text in each installed language.

In this model each physical row represents the translation of one bucket into one supported language. The table includes a LANGUAGE column and the standard MLS-style translation control columns (TRANSLATED, SOURCE_LANG), which together determine whether a given language row is the source-language row or a derived translation. From a heuristic Data Vault modeling perspective, this table is best classified as a satellite: it hangs off the bucket identity and carries descriptive, language-qualified, time-stamped attributes rather than new business entities or relationships.

Because the table is a translation table, it is not intended to be the primary source of bucket logic. Business rules and numeric boundaries continue to reside on the base bucket object; BIS_BUCKET_TL adds the human-readable naming layer used in forms, reports, and analytics that must display bucket labels to end users.

Key Information Stored

The documented physical schema contains 21 columns. The columns with the greatest functional significance are:

  • BUCKET_ID — the foreign key to the parent bucket definition (BIC_MEASURE_BUCKETS). It is the identity column that links each translation row to a specific bucket, and it is the dominant join key for all accesses to this table.
  • LANGUAGE — the language code for the translated row. Together with BUCKET_ID it forms the effective unique business key of a translation row.
  • NAME — the translated bucket (or bucket set) name shown to users in the selected language.
  • RANGE1_NAME through RANGE10_NAME — ten translated labels for the individual bucket ranges. These allow each segment of a bucket range to carry its own localized description, which is essential for producing readable bucket-based reports.
  • DESCRIPTION — the translated long description of the bucket definition.
  • TRANSLATED and SOURCE_LANG — MLS translation control columns. TRANSLATED flags whether the row has been translated; SOURCE_LANG records the language of the original entry, enabling detection of untranslated content.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns that record who created and last modified each translation row and when.

The surrogate identity of the table is the combination of BUCKET_ID and LANGUAGE. BUCKET_ID is also the documented business-key candidate expressed through the foreign key relationship to BIC_MEASURE_BUCKETS. No additional unique index is documented beyond this pairing.

Common Use Cases and Queries

The most frequent use of BIS_BUCKET_TL is joining translation rows to the base bucket definition to render bucket labels for a specified language. A typical query restricts the LANGUAGE value and projects the range labels:

SELECT t.NAME, t.RANGE1_NAME, t.RANGE2_NAME, t.DESCRIPTION
FROM BIS.BIS_BUCKET_TL t
WHERE t.BUCKET_ID = :bucket_id
AND t.LANGUAGE = USERENV('LANG');

Reporting scenarios include bucket aging analysis, cash-flow or receivable maturity banding, and any dashboard where bucket ranges must be displayed in the user's language. Analysts frequently join this table to BIC_MEASURE_BUCKETS to correlate translated labels with the numeric boundaries of each range. Data-quality queries can detect missing translations by selecting rows where TRANSLATED is not set or where SOURCE_LANG differs from LANGUAGE.

Because the table is protected, all access should be read-only. Insertion and maintenance of translation rows are typically performed through the BIS application's translation facilities or a controlled MLS maintenance process rather than by direct DML.

Related Objects

The following objects are most relevant to BIS_BUCKET_TL:

  • BIC_MEASURE_BUCKETS — the parent bucket definition table. The documented foreign key is BIS_BUCKET_TL.BUCKET_ID → BIC_MEASURE_BUCKETS, making this the primary join path and the authoritative source of bucket structure.
  • BIS_BUCKET (base entity) — the non-translation counterpart that holds the language-independent bucket definition.
  • FND_LANGUAGES — the language reference table used to validate and interpret the LANGUAGE column.
  • FND_TERRITORIES and related NLS views — supporting objects for locale-aware display.
  • BIS product views and concurrent programs that consume bucket definitions for measure and balance reporting.
  • BIC_MEASURE_* tables and their translation counterparts, which share the same MLS pattern and are commonly queried alongside this table.

Any object that reports on measure buckets should resolve labels through BIS_BUCKET_TL to ensure correct, language-specific presentation.