Results for “oke_billing_methods_tl”

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

Overview

OKE_BILLING_METHODS_TL is the multi-lingual (translation) table for contract billing methods within the Oracle Project Contracts (OKE) module. In Oracle EBS 12.1.1 and 12.2.2, the OKE schema stores the setup and transactional data that governs project contract lifecycle processing, and this table supplies the language-specific display text for each billing method code defined in the application. Billing methods describe how a contract is invoiced — for example, by rate, by amount, or by periodic schedule — and their descriptions appear on contract entry forms, billing plan setup, and printed contract documents. Because Oracle EBS supports multiple installed languages, each billing method requires one row per installed language, which is why the translation table is separated from the base definition table rather than storing display names directly in the base table.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. From a modeling perspective, this object can therefore be treated as an independent reference or lookup structure rather than a hub, link, or satellite within a Data Vault model. It is a purely descriptive, low-volatility configuration table, typically populated during implementation and modified only when a new billing method is introduced or an existing description is corrected.

Key Information Stored

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

• BILLING_METHOD_CODE — the non-translatable business identifier for the billing method. This column participates in both the primary key and the primary unique index, and it is the value users typically search for when they enter "billing_method_code" in a query, report, or form personalization.
• LANGUAGE — the NLS language code (for example, US for American English) in which the billing method name and description are stored. It combines with BILLING_METHOD_CODE to form the primary key.
• BILLING_METHOD_NAME — the translated, user-visible name of the billing method for the given language. It forms the business-key candidate captured by unique index OKE_BILLING_METHODS_TL_U2 (BILLING_METHOD_NAME, LANGUAGE), which enforces that no two billing methods share the same display name within a language.
• DESCRIPTION — a longer, language-specific explanation of the billing method, used in setup windows and reference reporting.
• SOURCE_LANG — identifies the language of the source row from which a translation was derived, supporting the standard Oracle translation maintenance model.

The remaining audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — record who created and last changed each row and when, and are populated automatically by the Oracle Forms and concurrent processing infrastructure.

The surrogate primary key is defined by OKE_BILLING_METHODS_TL_PK over (BILLING_METHOD_CODE, LANGUAGE). The unique indexes OKE_BILLING_METHODS_TL_U1 (BILLING_METHOD_CODE, LANGUAGE) and OKE_BILLING_METHODS_TL_U2 (BILLING_METHOD_NAME, LANGUAGE) are the documented business-key candidates.

Common Use Cases and Queries

The most frequent requirement is resolving a billing method code to a readable name for a specific session language. A typical lookup joins the translation table to a transactional source and filters on the current NLS language:

• SELECT b.billing_method_code, t.billing_method_name, t.description FROM oke_billing_methods_b b, oke_billing_methods_tl t WHERE b.billing_method_code = t.billing_method_code AND t.language = USERENV('LANG')
• Reverse lookup from a user-entered name: SELECT billing_method_code FROM oke_billing_methods_tl WHERE billing_method_name = :name AND language = USERENV('LANG')
• Translation completeness audit: SELECT billing_method_code, COUNT(*) FROM oke_billing_methods_tl GROUP BY billing_method_code HAVING COUNT(*) < (SELECT COUNT(*) FROM fnd_languages WHERE installed_flag = 'I')

Reporting use cases include billing method listings for setup documentation, validation of contract billing plans against configured methods, and extracts that feed downstream invoicing or revenue systems. Because the table is keyed by language, reports should always constrain LANGUAGE explicitly; omitting the predicate returns duplicate rows per code and inflates result sets.

Related Objects

The table depends on and is referenced by the following significant objects:

• OKE_BILLING_METHODS_B — the base table holding language-independent billing method attributes; joined on BILLING_METHOD_CODE.
• OKE_BILLING_METHODS_VL — the MLS view that exposes the base and translation columns as a single logical row for forms and reports.
• OKE_BILLING_METHODS_TL_PK / U1 / U2 — the primary key and unique index constraints enforcing code uniqueness and name uniqueness per language.
• FND_LANGUAGES — validates the LANGUAGE column against installed languages.
• OKE_CONTRACTS_ALL / OKE_CONTRACT_BILLING_* — contract and billing plan tables that store BILLING_METHOD_CODE and resolve their display text through this translation table.

Together these objects form the billing method lookup layer used throughout Project Contracts setup and contract processing.