Results for “okl_cure_payments_tl”

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

Overview

OKL_CURE_PAYMENTS_TL is a translatable (MLS) table within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 Leasing and Finance Management (OKL) module. Under Oracle's Multi-Lingual Support (MLS) architecture, each base table in a translatable entity is paired with a "_TL" table that stores the language-dependent descriptive columns, while the companion "_B" table retains language-independent attributes. In this case, the metadata explicitly states that OKL_CURE_PAYMENTS_TL holds the "OBSELETE-Translatable columns from OKL_CURE_PAYMENTS_B, per MLS standards." The object is therefore the translation repository for the cured-payment entity used in lease curing processes.

The document further states "Not implemented in this database." This indicates that in the specific environment referenced, the physical table does not exist — a common situation where a seeded object has been superseded, dropped, or never deployed. Where the table is present, its heuristic Data Vault classification is standalone, meaning it does not participate in a hub-link-satellite dependency chain derived from foreign-key structure. It can be modeled as a standalone reference/satellite-like construct, functionally paired to its base table rather than connected to other hubs.

Key Information Stored

As a translation table, the column set is deliberately narrow. The most important columns documented for this object are:

• CURE_PAYMENT_ID — the surrogate/foreign key linking back to the base entity OKL_CURE_PAYMENTS_B; identifies which cured payment the translation row describes.
• LANGUAGE — the MLS language code identifying the locale of the translatable text.

The documented Primary Key is OKL_CURE_PAYMENT_TL_PK, defined on the composite of (CURE_PAYMENT_ID, LANGUAGE). This composite effectively serves as the unique business key candidate for the translation row, because the combination guarantees one translated description per payment per language. CURE_PAYMENT_ID is the surrogate identifier inherited from the base table; LANGUAGE, paired with it, forms the only documented uniqueness constraint. Translatable text columns (typically names or descriptions) are implied by the MLS standard but are not enumerated in the provided metadata.

Common Use Cases and Queries

The principal use case is retrieving the correct localized description for a cured-payment record. Reporting queries join the base table to the _TL table filtered by the session language. A typical pattern is:

• SELECT b.cure_payment_id, t.description FROM okl_cure_payments_b b, okl_cure_payments_tl t WHERE b.cure_payment_id = t.cure_payment_id AND t.language = USERENV('LANG');
• Multi-language audit queries that list all translations for a given payment across LANGUAGE values.
• Data-cleansing checks identifying base rows that lack a translation for the active language.

Given the OBSELETE designation and the "Not implemented" note, analysts should verify table existence in the target schema before relying on these queries in 12.1.1 or 12.2.2 environments.

Related Objects

The most significant related object is the base table OKL_CURE_PAYMENTS_B, joined on CURE_PAYMENT_ID. Other relevant objects include the primary-key constraint OKL_CURE_PAYMENT_TL_PK and the associated MLS index structures. Where deployed, functional relationships extend to the cured-payment seeding and lease-curing APIs that populate the base table, from which translations are derived.