Results for “okl_fe_std_rt_tmp_b”

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

Overview

OKL_FE_STD_RT_TMP_V is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the Lease and Finance Management (OKL) product family. ETRM documents the object as the "Standard Rate Template header view." Its purpose is to expose the header-level attributes of Oracle Leasing standard rate templates for reporting, inquiry, and integration use, without requiring consumers to join the underlying multilingual and base tables themselves.

Standard rate templates in Oracle Lease and Finance Management define the pricing rate structures applied during contract and lease origination, including the rate type, frequency, index reference, and optional fixed rate. The view provides a single, translatable projection of this setup data. Because it is a view rather than a table, it stores no data of its own; it is a read-only construct that resolves its rows at query time from the documented base objects. The object holds VALID status in the APPS schema, confirming that it is compiled and available for use in both referenced releases.

Underlying Base Objects

The view definition joins two documented synonyms in the APPS schema:

• OKL_FE_STD_RT_TMP_B — the base table containing the standard rate template header records, including identifiers, currency, rate type, frequency, index, dates, and the descriptive flexfield attribute columns. This is the primary source for nearly all columns exposed by the view.
• OKL_FE_STD_RT_TMP_ALL_TL — the translation (_TL) table that stores language-dependent descriptive text for the template, primarily TEMPLATE_DESC. The suffix "ALL" indicates the table holds translations for all installed languages.

The join is performed on STD_RATE_TMPL_ID, with the translation row filtered by T.LANGUAGE = USERENV('LANG'). This restricts the result to the description in the session's current language, so the same template appears with the description appropriate to the logged-in user's language setting. Consumers therefore see a single, language-resolved row per template rather than one row per translation. The underlying tables remain accessible directly for administrative or bulk operations, but the view is the recommended access path for descriptive, user-facing queries.

Key Columns

The view exposes the full header attribute set. The principal columns and their meanings are:

• STD_RATE_TMPL_ID — Primary key of the standard rate template; the join key to both base tables and the identifier used when relating templates to other OKL entities.
• TEMPLATE_NAME — The template name, sourced from the base table.
• TEMPLATE_DESC — The language-specific description, sourced from the translation table.
• ORG_ID — Operating unit identifier, enabling multi-org–restricted queries.
• CURRENCY_CODE — Currency in which the template's rate structure is expressed.
• RATE_CARD_YN, RATE_TYPE_CODE, FREQUENCY_CODE, INDEX_ID, SRT_RATE — The pricing attributes: whether the template derives from a rate card, the rate type, the payment/accrual frequency, the referenced interest index, and the fixed standard rate value.
• PRICING_ENGINE_CODE, DEFAULT_YN — The pricing engine used and whether the template is a default.
• STS_CODE — Status code governing whether the template is active or otherwise available.
• EFFECTIVE_FROM_DATE, EFFECTIVE_TO_DATE — The date range over which the template is effective.
• ORIG_STD_RATE_TMPL_ID, OBJECT_VERSION_NUMBER — The source template identifier (for copied templates) and the optimistic-locking version number.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — Descriptive flexfield segments for customer-defined extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns.

Common Use Cases and Queries

The view is typically used for reporting on rate template setup, validating effective-dated pricing configuration, and feeding rate data into downstream integrations. A representative query retrieves active templates for a given operating unit:

• SELECT std_rate_tmpl_id, template_name, template_desc, currency_code, rate_type_code, frequency_code, srt_rate
• FROM okl_fe_std_rt_tmp_v
• WHERE org_id = :p_org_id AND sts_code = 'ACTIVE'
• AND TRUNC(SYSDATE) BETWEEN effective_from_date AND NVL(effective_to_date, SYSDATE);

Other common scenarios include joining STD_RATE_TMPL_ID to contract or pricing tables to report the rate template applied to a lease, and extracting default templates (DEFAULT_YN = 'Y') for setup validation. Because the view resolves the language automatically, reports built on it respect the user's session language without additional translation handling. Queries should always be constrained by ORG_ID where multi-org access applies, and by the effective dates to avoid returning superseded template versions.