Results for “mtl_billing_sources_b”

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

Overview

MTL_BILLING_SOURCES_B is an Inventory (INV) module base table that stores the master definition of billing sources used by the Oracle E-Business Suite Third-Party Logistics (3PL) Billing functionality. It holds the language-independent attributes of each billing source and serves as the primary anchor record for the billing source entity. Billing sources describe the categories or origins of chargeable activity that the 3PL billing engine evaluates when applying billing rules to billable transactions. The table is owned by the INV schema and is documented as VALID in ETRM for Oracle EBS 12.1.1 and 12.2.2.

Applying Data Vault modeling heuristics to the foreign key structure, MTL_BILLING_SOURCES_B is classified as hub-leaning. This designation is a modeling suggestion only: the table functions as a durable business entity anchor referenced by dependent tables, which is characteristic of a hub. Its companion translation table, MTL_BILLING_SOURCES_TL, and the billing rule line table, MTL_BILLING_RULE_LINES, both reference it via BILLING_SOURCE_ID, reinforcing its role as a shared reference point rather than a transactional detail record.

Key Information Stored

The table contains eight documented columns. The most significant are:

• BILLING_SOURCE_ID — the surrogate primary key, defined by the unique index MTL_BILLING_SOURCES_B_PK. This identifier is the sole documented unique business-key candidate and is the column propagated to all dependent tables.
• BILLING_SOURCE_CODE — the user-visible or internal code that identifies the billing source, providing a meaningful business reference.
• PROCEDURE_CODE — the code identifying the procedure or logic associated with the billing source, used to link the source to its processing behavior.
• CREATION_DATE, CREATED_BY — standard Oracle EBS audit columns capturing when and by whom the billing source was first created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification, the user making it, and the login session context.

The distinction between the surrogate key and the business key is important: BILLING_SOURCE_ID is an internally generated, stable identifier, whereas BILLING_SOURCE_CODE carries the semantic meaning relied on by users and integrations. The descriptive, language-dependent names are stored in the associated _TL table rather than in this base table.

Common Use Cases and Queries

Typical usage centers on retrieving billing source definitions and resolving them to their translations and rule lines. A basic lookup of all active billing sources follows this pattern:

• SELECT billing_source_id, billing_source_code, procedure_code FROM mtl_billing_sources_b;
• SELECT b.billing_source_id, t.billing_source_name 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');
• SELECT l.billing_source_id, l.rule_line_id FROM mtl_billing_rule_lines l WHERE l.billing_source_id = :source_id;

Reporting scenarios include enumerating billing sources referenced by billing rules, auditing creation and update activity through the standard audit columns, and validating referential integrity between billing rules and their sources. Because the table is small and reference-oriented, joins to the translation table are generally required to present human-readable names.

Related Objects

• MTL_BILLING_SOURCES_TL — the translation table, joined on BILLING_SOURCE_ID, holding language-specific descriptive text. Note that the FK metadata inverts the parent/child direction for this pair.
• MTL_BILLING_RULE_LINES — references BILLING_SOURCE_ID, associating each billing rule line with the billing source it evaluates.
• MTL_BILLING_SOURCES_B_PK — the primary key constraint/index enforcing uniqueness of BILLING_SOURCE_ID.

These relationships define the billing source as a controlled reference entity consumed by both the translation layer and the billing rule engine within the 3PL Billing project.