Results for “service_agreement_id”

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

Overview

MTL_BILLING_RULE_HEADERS_B is the base table in the Oracle Inventory (INV) schema that stores the header-level definitions of Third-Party Logistics (3PL) billing rules. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table anchors the billing rule framework used by warehouse operators and logistics providers to define how charges are calculated for services rendered on behalf of client organizations. Each row represents a single billing rule header, which serves as the parent container for one or more detailed billing rule lines that implement the actual charge logic.

From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning. The single-column primary key BILLING_RULE_HEADER_ID functions as a durable surrogate business key, and the table is referenced by dependent child tables rather than acting as a transactional satellite itself. This suggests it is best treated as a hub entity when designing a warehouse or integration layer around ETRM data.

Key Information Stored

The documented physical schema for MTL_BILLING_RULE_HEADERS_B in ETRM 12.2.2 consists of seven columns:

• BILLING_RULE_HEADER_ID — The surrogate primary key (MTL_BILLING_RULE_HEADERS_B_PK) that uniquely identifies each billing rule header and is the join key for all dependent child records.
• SERVICE_AGREEMENT_ID — The foreign key linking the billing rule header to the service agreement that governs the commercial relationship under which the rule is applied. This is the principal business-context attribute of the row.
• CREATION_DATE — Timestamp when the billing rule header record was created.
• CREATED_BY — The application user ID that created the record.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the header record.
• LAST_UPDATED_BY — The application user ID that performed the last update.
• LAST_UPDATE_LOGIN — The login session identifier associated with the last update, used for audit and concurrent-program traceability.

The only unique index documented is the primary key on BILLING_RULE_HEADER_ID; no separate business-key unique index is published, so BILLING_RULE_HEADER_ID doubles as both the surrogate and the effective business identifier within the INV schema. The four WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, plus LAST_UPDATE_LOGIN) provide the standard EBS auditing footprint.

Common Use Cases and Queries

Typical usage centers on reporting and integration around 3PL billing configurations. Analysts commonly list all billing rules for a given service agreement, reconcile billing rule headers against their associated lines, or extract rule headers for loading into corporate data warehouses.

A representative query joining headers to their service agreement context:

• SELECT h.billing_rule_header_id, h.service_agreement_id, h.creation_date FROM mtl_billing_rule_headers_b h WHERE h.service_agreement_id = :agreement_id;

To enumerate the child lines for each header:

• SELECT h.billing_rule_header_id, l.billing_rule_line_id FROM mtl_billing_rule_headers_b h, mtl_billing_rule_lines l WHERE h.billing_rule_header_id = l.billing_rule_header_id;

Reporting use cases include auditing how many distinct billing rules exist per service agreement, tracking recently created or modified rules using LAST_UPDATE_DATE for change-data-capture feeds, and validating that every active billing rule header has at least one associated line before a billing run.

Related Objects

The FK metadata documents the following dependency relationship, which is the single most significant related object:

• MTL_BILLING_RULE_LINES — The child table holding the individual rule lines. Its BILLING_RULE_HEADER_ID column references MTL_BILLING_RULE_HEADERS_B.BILLING_RULE_HEADER_ID. Any header record without at least one line is effectively incomplete for billing calculation purposes.
• Service Agreement tables — Through SERVICE_AGREEMENT_ID, the header is linked to the service agreement definition (in the Service Contracts / OKS realm), providing the commercial context for each rule.
• MTL_BILLING_RULE_HEADERS_TL — In multi-language installations, the translated/descriptive attributes of the header are typically stored in a companion _TL table keyed by BILLING_RULE_HEADER_ID and LANGUAGE.
• 3PL Billing concurrent programs and open interfaces — EBS billing and warehouse management programs consume these headers together with their lines when generating billing transactions.

Because MTL_BILLING_RULE_HEADERS_B is a hub-leaning parent, its principal role is to anchor referential integrity for MTL_BILLING_RULE_LINES and to carry the service agreement association; queries should generally traverse to the lines table for the detail needed in most billing reports.