Results for “service_agreement_line_id”

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

Overview

MTL_BILLING_RULE_LINES is an Inventory (INV) module table that stores the detail lines of billing rules used by the third-party logistics (3PL) Billing feature in Oracle E-Business Suite. It is owned by the INV schema and is valid in both 12.1.1 and 12.2.2. The table functions as the child entity of MTL_BILLING_RULE_HEADERS_B, capturing the individual service, client, and source-level components that make up a billing rule header.

In a Data Vault modeling sense, the heuristic classification derived from the foreign-key structure is a link table. This is a suggested modeling pattern rather than a physical design fact: the table associates a billing rule header with a client, a billing source, and a service agreement line, and therefore behaves as a relationship/association entity between those business hubs.

Key Information Stored

The documented physical schema for 12.2.2 contains 12 columns. The most significant are summarized below.

• BILLING_RULE_LINE_ID — the surrogate primary key, enforced by the unique index MTL_BILLING_RULE_LINES_PK. This is the only documented unique index, making it the sole business-key candidate on the table.
• BILLING_RULE_HEADER_ID — foreign key to MTL_BILLING_RULE_HEADERS_B, tying each line to its parent rule.
• CLIENT_CODE — foreign key to MTL_CLIENT_PARAMETERS, identifying the 3PL client to whom the rule line applies.
• CLIENT_NUMBER — the client reference value carried on the line.
• SERVICE_AGREEMENT_LINE_ID — the service agreement line against which the billing rule line is evaluated.
• BILLING_SOURCE_ID — foreign key to MTL_BILLING_SOURCES_B, identifying the billing source that supplies the charge or activity data.
• INVENTORY_ITEM_ID — the inventory item associated with the billing rule line.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns recording insert and update context.

Common Use Cases and Queries

Typical uses include configuring 3PL billing rules, verifying which clients, items, and sources a rule covers, and driving charge calculation and reconciliation reports. A straightforward query joins the table to its parent header to list the lines of a given rule:

SELECT l.billing_rule_line_id,
       l.billing_rule_header_id,
       l.client_code,
       l.billing_source_id,
       l.inventory_item_id
FROM   mtl_billing_rule_lines l
WHERE  l.billing_rule_header_id = :header_id;

Joining to MTL_CLIENT_PARAMETERS resolves the client identity, while joining to MTL_BILLING_SOURCES_B resolves the source definition. Reporting scenarios commonly group lines by client or source to summarize rule coverage, and reconciliation scenarios compare the item and service agreement line on each rule line against the transactions being billed.

Related Objects

The following objects are the most significant references or dependents documented for this table:

• MTL_BILLING_RULE_HEADERS_B — parent table; joined on MTL_BILLING_RULE_LINES.BILLING_RULE_HEADER_ID = MTL_BILLING_RULE_HEADERS_B.BILLING_RULE_HEADER_ID.
• MTL_CLIENT_PARAMETERS — referenced on CLIENT_CODE, providing the 3PL client definition.
• MTL_BILLING_SOURCES_B — referenced on BILLING_SOURCE_ID, defining the billing source.
• MTL_BILLING_RULE_LINES_PK — the primary key index enforcing uniqueness of BILLING_RULE_LINE_ID.

Together these relationships define the 3PL Billing rule configuration model, with MTL_BILLING_RULE_LINES acting as the associative detail table beneath the rule header.