Search Results okl_fe_std_rt_tmp_all_b_pk




Overview

The OKL_FE_STD_RT_TMP_ALL_B table is a core data object within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, specifically for the OKL (Leasing and Finance Management) product module. It serves as the header table for Standard Rate Templates. These templates are foundational structures used to define and manage the standard interest or pricing rates applied to financial instruments, such as leases and loans, within the system. The table's role is to store the master definition and key attributes of a rate template, which can then be versioned and applied to specific contracts. Its "ALL_B" suffix indicates it is the base table for a multi-language support (MLS) setup, storing language-independent data, with translated descriptions typically held in a corresponding "_TL" table.

Key Information Stored

While the provided metadata does not list specific columns, the documented primary and foreign key relationships reveal the critical data points stored. The primary identifier is the STD_RATE_TMPL_ID, a unique system-generated key for each template. A significant structural column is ORIG_STD_RATE_TMPL_ID, which creates a self-referential foreign key relationship. This allows templates to be linked to an original or parent template, supporting scenarios like template revisions or inheritance. The INDEX_ID column establishes a foreign key relationship to the OKL_INDEX_VALUES table, indicating that a standard rate template can be associated with a specific financial index (e.g., LIBOR, Prime Rate). Other typical header information would include template name, description, effective dates (FROM_DATE, TO_DATE), status, and audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER).

Common Use Cases and Queries

This table is central to configuring and querying the standard rate structures used across leasing operations. Common use cases include the setup of new base rate templates for product offerings, the modification of existing templates to create new versions, and reporting on all active rate templates. A frequent reporting requirement is to list templates along with their associated financial index. A sample SQL pattern for this would join OKL_FE_STD_RT_TMP_ALL_B to OKL_INDEX_VALUES.

  • Sample Query: SELECT tmpl.STD_RATE_TMPL_ID, tmpl.TEMPLATE_NAME, idx.INDEX_NAME FROM OKL.OKL_FE_STD_RT_TMP_ALL_B tmpl LEFT JOIN OKL.OKL_INDEX_VALUES idx ON tmpl.INDEX_ID = idx.INDEX_ID WHERE tmpl.TO_DATE IS NULL OR tmpl.TO_DATE > SYSDATE;
  • Template Lineage: The self-referential foreign key enables queries to trace the version history or derivation chain of a template by joining the table to itself on ORIG_STD_RATE_TMPL_ID = STD_RATE_TMPL_ID.

Related Objects

The table is integral to the rate template data model, with documented relationships to other key OKL objects.

  • Primary Key: OKL_FE_STD_RT_TMP_ALL_B_PK on column STD_RATE_TMPL_ID.
  • Foreign Keys (Referenced By This Table):
    • OKL_FE_STD_RT_TMP_ALL_B.ORIG_STD_RATE_TMPL_ID references OKL_FE_STD_RT_TMP_ALL_B.STD_RATE_TMPL_ID (Self-referential for template lineage).
    • OKL_FE_STD_RT_TMP_ALL_B.INDEX_ID references OKL_INDEX_VALUES (Links template to a financial index).
  • Foreign Keys (Referencing This Table):
    • OKL_FE_STD_RT_TMP_ALL_B.ORIG_STD_RATE_TMPL_ID is referenced by OKL_FE_STD_RT_TMP_ALL_B (The reciprocal of the self-reference).
    • OKL_FE_STD_RT_TMP_VERS.STD_RATE_TMPL_ID references OKL_FE_STD_RT_TMP_ALL_B.STD_RATE_TMPL_ID. This is a critical relationship, as the OKL_FE_STD_RT_TMP_VERS table stores the detailed rate schedules and values for each version of a header template.