Results for “mtl_billing_sources_tl”

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

Overview

MTL_BILLING_SOURCES_TL is the translation (language) table for billing sources within the Oracle Inventory (INV) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. A billing source in Oracle EBS represents a predefined source that can be assigned to a transaction or accounting line to indicate the origin of a billing or cost event; it is commonly referenced when configuring intercompany invoicing, internal order flows, and cost-to-charge mappings. Because Oracle EBS supports multiple installed languages, descriptive attributes for billing sources are stored in a base table (MTL_BILLING_SOURCES_B) and their translated equivalents are stored in this _TL table. Each row in MTL_BILLING_SOURCES_TL contains the language-specific name and description of a single billing source, keyed by the combination of the billing source identifier and the language code.

From a Data Vault modeling perspective, the mined relationship metadata classifies MTL_BILLING_SOURCES_TL as satellite-leaning. This heuristic reflects that the table carries descriptive, language-dependent attributes attached to a business key defined elsewhere (MTL_BILLING_SOURCES_B), rather than serving as a hub or a link between independent business entities. The translation row therefore behaves much like a descriptive satellite keyed by (BILLING_SOURCE_ID, LANGUAGE).

Key Information Stored

The documented physical schema for this object in ETRM 12.2.2 lists ten columns owned by the INV schema. The most significant of these are:

• BILLING_SOURCE_ID — Surrogate identifier for the billing source. Together with LANGUAGE it forms the primary key (MTL_BILLING_SOURCES_TL_PK). It is also the foreign key column referencing MTL_BILLING_SOURCES_B, linking each translated row to its base record.
• LANGUAGE — The language code identifying the translation locale for the row. This is the second component of the composite primary key and the discriminator that makes this a translation table.
• NAME — The translated display name of the billing source, used in forms, list of values, and reports when the session language matches LANGUAGE.
• DESCRIPTION — The translated free-text description of the billing source, providing contextual detail beyond the short name.
• SOURCE_LANG — The language in which the source record was originally created; used by the translation framework to track derivation of translated content.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified the translated row, when, and from which login session. These support audit trails and are populated automatically by the application.

The surrogate key of the table is the composite (BILLING_SOURCE_ID, LANGUAGE); the unique index MTL_BILLING_SOURCES_TL_PK is the business-key candidate, guaranteeing that a given billing source has at most one translation per language.

Common Use Cases and Queries

The primary reporting use case is to retrieve language-appropriate billing source values for display in multilingual environments. A typical query joins the translation table to the base table and restricts to the desired language:

• SELECT b.billing_source_id, t.name, t.description FROM mtl_billing_sources_b b, mtl_billing_sources_tl t WHERE b.billing_source_id = t.billing_source_id AND t.language = USERENV('LANG');
• Listing all available billing sources in a specific installed language, for configuration review or migration validation.
• Detecting missing translations by comparing base rows against translation rows for a given language, which is useful during implementation and post-patch validation.
• Auditing changes to billing source names or descriptions by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Feeding localized billing source values into custom reports, OBIEE/BI Publisher datasets, or interfaces that populate downstream billing or intercompany documentation.

Related Objects

The following objects are the most significant in relation to MTL_BILLING_SOURCES_TL, based on the documented foreign-key relationship and the standard Oracle Inventory translation architecture:

• MTL_BILLING_SOURCES_B — Base table for billing sources. Joined on BILLING_SOURCE_ID. This is the only foreign key documented in the metadata and is the mandatory parent of every translation row.
• MTL_BILLING_SOURCES_TL_PK — The unique index enforcing uniqueness of (BILLING_SOURCE_ID, LANGUAGE).
• MTL_BILLING_SOURCES_VL — The standard Oracle translation view that unions the base and translated columns, exposing a single language-aware row per billing source.
• MTL_TRANSACTIONS / MTL_MATERIAL_TRANSACTIONS — Transaction tables that reference billing sources during cost and intercompany processing.
• MTL_CST_TXN_COST_DETAILS — Cost detail records that may carry billing source values for charge attribution.
• FND_LANGUAGES — The language definition table providing valid values for the LANGUAGE column.
• ORG_ORGANIZATION_DEFINITIONS — Accessed alongside billing sources when configuring inventory and intercompany rules per organization.

Because the table is maintained by the Inventory application, direct DML is not recommended; changes should be made through the supported Oracle EBS configuration and translation screens.