Results for “oke_billing_methods_tl_u2”

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

Overview

OKE.OKE_BILLING_METHODS_TL is the translation (language-specific) table for Oracle E-Business Suite billing methods within the Oracle ETRM (Enterprise Trade and Contracts) module. In Oracle EBS 12.1.1 and 12.2.2, the "TL" suffix denotes a translation table that stores the multilingual, display-facing attributes of a logical entity, while a corresponding base table would hold the language-independent "code" values. This table stores language-specific information for billing methods, meaning the descriptive labels and descriptions used to present a billing method to users in their session language.

The object resides in the OKE schema, is enabled as FND Design Data (OKE.OKE_BILLING_METHODS_TL), and has a status of VALID. It is stored in the APPS_TS_SEED tablespace, reflecting its role as reference and setup (seed) data rather than transactional data. From a heuristic Data Vault modeling perspective, the metadata classification is standalone; this is best interpreted as a suggested classification only, since the object functions conceptually as a satellite carrying the descriptive, language-dependent attributes keyed by the natural business key. It neither references other database objects nor acts as a hub or link in this documentation.

Key Information Stored

The table's primary key is documented as OKE_BILLING_METHODS_TL_PK, defined over the composite columns BILLING_METHOD_CODE and LANGUAGE. Two business-key candidates are documented as unique indexes:

• OKE_BILLING_METHODS_TL_U1 — unique on (BILLING_METHOD_CODE, LANGUAGE). This is the key most commonly referenced in ETRM naming conventions and by the user's search term "oke_billing_methods_tl_u1."
• OKE_BILLING_METHODS_TL_U2 — unique on (BILLING_METHOD_NAME, LANGUAGE), ensuring a billing method name is not duplicated within a language.

The most important columns are:

• BILLING_METHOD_CODE (VARCHAR2, 30) — the language-independent code identifying the billing method; the business key that joins to the underlying base table.
• LANGUAGE (VARCHAR2) — the language code of the current row, part of both the primary key and the unique indexes.
• BILLING_METHOD_NAME (VARCHAR2, 80) — the translated, user-visible billing method name.
• DESCRIPTION (VARCHAR2, 240) — the translated description of the billing method.
• SOURCE_LANG (VARCHAR2) — the source language code of the current data, used for translation synchronization.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard "Who" columns that record insert and update audit information.

Common Use Cases and Queries

The primary use case is retrieving the correct localized label and description for a billing method when rendering ETRM setup and transaction screens, and in multilingual reporting. A typical query retrieves the display name for the user's language:

• SELECT billing_method_code, billing_method_name, description FROM oke.oke_billing_methods_tl WHERE language = USERENV('LANG');
• To confirm the documented key, querying by the unique index columns validates a code/name combination: WHERE billing_method_code = :code AND language = :lang;
• Translation audit reports compare SOURCE_LANG against LANGUAGE to identify rows still pending translation or missing a localized name.
• Joining to the base billing method table on BILLING_METHOD_CODE (with a language predicate) produces a complete view of method metadata together with its translations.

Related Objects

The documentation states that OKE.OKE_BILLING_METHODS_TL is referenced by APPS.OKE_BILLING_METHODS_TL (the APPS synonym/access path). The natural relationship implied by the composite key is to the base billing methods table, joined on BILLING_METHOD_CODE, since the TL table supplies the language-specific name and description. Reporting views and concurrent programs that expose billing method setup typically consume this table through that synonym. Additional significant dependencies include the FND language and translation infrastructure used through SOURCE_LANG and LANGUAGE, and the standard ETRM setup forms and lookup mechanisms that resolve BILLING_METHOD_CODE into a user-facing name. Because the documented dependency list is limited (the object references no other database object), joins to sibling setup tables should be validated against the physical schema before use in production queries.