Search Results mtl_billing_rule_headers_vl




Overview
Explore in AI Chat

Overview

MTL_BILLING_RULE_HEADERS_VL is a validation view owned by the APPS schema in Oracle E-Business Suite Inventory (INV). It is a multi-language (VL) view whose purpose is to expose billing rule header records together with their translated name and description, the associated service agreement (contract) context, and the authoring organization. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status, indicating it is a supported dictionary object used by forms, concurrent programs, and reporting layers that need to resolve billing rule headers for service and contract-based inventory transactions.

Because it is a VL view, it joins the base table with its translation table, filtering the translation row to the session language via USERENV('LANG'). This means callers automatically receive only the language-specific NAME and DESCRIPTION associated with the current user environment, rather than all translations. The view therefore serves as the canonical reporting surface for billing rules applied against service agreements in an Inventory context.

Underlying Base Objects

Per the documented view text and 12.2.2 metadata, the view is defined over four principal base objects plus supporting library packages:

The joins are: translation to base on BILLING_RULE_HEADER_ID, base to contract header on SERVICE_AGREEMENT_ID = OKC_K_HEADERS_B.ID, and contract header to organization view on AUTHORING_ORG_ID = ORGANIZATION_ID.

Key Columns

  • ROW_ID — the ROWID of the base record, typically used as a surrogate key for forms and updates.
  • BILLING_RULE_HEADER_ID — the unique identifier linking the translation and base records.
  • NAME / DESCRIPTION — the translated billing rule header name and description for the session language.
  • CONTRACT_NUMBER — the identifier of the associated service agreement from OKC_K_HEADERS_B.
  • SERVICE_AGREEMENT_ID — the contract header ID (OKC_K_HEADERS_B.ID).
  • ORGANIZATION_ID / ORGANIZATION_NAME — the authoring organization from ORG_ORGANIZATION_DEFINITIONS.
  • START_DATE / END_DATE — contract validity window cloned from the contract header.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns from the base table.

Common Use Cases and Queries

Typical uses include reporting on billing rules by contract, validating rule setup against service agreements, and driving LOV-style selection in custom forms and concurrent programs.

  • List all billing rules for a given service agreement.
  • Report active rules by authoring organization and contract period.
  • Resolve the translated name for a specific BILLING_RULE_HEADER_ID.

Sample SQL:

SELECT billing_rule_header_id, name, contract_number,
organization_name, start_date, end_date
FROM apps.mtl_billing_rule_headers_vl
WHERE service_agreement_id = :agreement_id
ORDER BY name;

SELECT billing_rule_header_id, name
FROM apps.mtl_billing_rule_headers_vl
WHERE organization_id = :org_id
AND SYSDATE BETWEEN start_date AND end_date;

Because language filtering is embedded, no additional translation joins are required; results reflect the run-time session language automatically.