Results for “billing_source_code”

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

Overview

MTL_BILLING_SOURCES_VL is a read-only, translation-enabled view owned by the APPS schema in Oracle E-Business Suite, belonging to the Inventory (INV) product module. It presents billing source definitions in the language of the current session, exposing the descriptive (translatable) attributes of a billing source alongside its identifying and system-audit attributes. Billing sources are the configuration records that determine how an outbound transaction — a shipment, an issue, or an RMA receipt — is translated into a receivable or revenue event in Oracle Order Management, Receivables, and Service modules. The "_VL" suffix denotes a "view with language," meaning the view joins a multilingual translation table to a base table and filters the translation rows by the session's language environment.

Because it resolves the session language automatically through USERENV('LANG'), the view is the preferred interface for reports, concurrent programs, and integrations that must render billing source names and descriptions in the user's own language. It insulates callers from the join between the base and translation tables, so external systems query a single object rather than reconstructing the join themselves.

Underlying Base Objects

The view is defined over two documented base objects:

• MTL_BILLING_SOURCES_B — the base (non-translatable) table holding the billing source primary key, its code, the procedure code, and standard audit columns. Referenced in the view text as alias B and exposed in the ETRM metadata as a synonym.
• MTL_BILLING_SOURCES_TL — the translation table holding the NAME and DESCRIPTION for each supported language. Referenced as alias TL, also documented as a synonym.

The two tables are joined on BILLING_SOURCE_ID, and the result set is restricted by the predicate TL.LANGUAGE = USERENV('LANG'), so each billing source appears exactly once, in the session language. The view also projects B.ROWID as ROW_ID.

Key Columns

• ROW_ID — the ROWID of the underlying base-table row, retained to support tools that rely on row identification.
• BILLING_SOURCE_ID — the surrogate primary key linking base and translation records; the join key used by dependent modules.
• NAME — the translated, user-facing label of the billing source, presented in the session language.
• DESCRIPTION — the translated explanatory text for the billing source.
• PROCEDURE_CODE — the identifier of the stored procedure executed to perform the billing action; this drives the logic invoked when the source is applied to a transaction.
• BILLING_SOURCE_CODE — the language-independent code used programmatically to reference the billing source.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include validating that a billing source has been configured before an integration raises a billing or receivable event, populating a List of Values or lookup in a custom form or report, and joining to transaction tables to render billing-source descriptions in the user's language. The following query lists all configured billing sources in the current session language:

SELECT billing_source_id, billing_source_code, name, procedure_code
FROM apps.mtl_billing_sources_vl
ORDER BY name;

To resolve the billing source for a specific transaction, filter on the code or ID surfaced through the dependent transaction entity and join back to this view on BILLING_SOURCE_ID. All access should be read-only, as no DML is supported against a view of this type.