Results for “okl_ae_tmpt_sets_all”

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

Overview

OKL_AE_TMPT_SETS_ALL is a core configuration table within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. The table stores accounting template sets, which are named, versioned groupings of accounting generation rules. In OKL, accounting templates determine how lease and loan transactions are translated into accounting entries — defining debit and credit line generation, accrual schedules, and revenue or interest recognition patterns. A template set binds one or more such templates together so they can be assigned consistently to a product or a contract.

The table is owned by the OKL schema and is documented as VALID. Its heuristic Data Vault classification is hub-leaning. In Data Vault modeling terms, this suggests treating ID as a durable business hub key, with descriptive and versioning attributes (NAME, VERSION, GTS_ID, dates) carried as satellite information. Because the table is referenced by foreign keys from products and contracts, it behaves as a stable reference point rather than a transactional or associative (link) entity.

Key Information Stored

The physical schema documented for ETRM 12.2.2 contains 14 columns. The most significant are:

• ID — Surrogate primary key, enforced by OKL_AE_TMPT_SETS_ALL_PK and also exposed as unique index OKL_AE_TMPT_SETS_ALL_U1. This is the value propagated to foreign keys in dependent tables.
• NAME — The user-facing name of the accounting template set. Part of the business-key candidate OKL_AE_TMPT_SETS_ALL_U2 along with VERSION and ORG_ID.
• VERSION — Version number that allows a template set to be revised over time without overwriting its prior definition; also part of the business-key candidate U2 and the alternate unique index OKL_AE_TMPT_SETS_ALL_UK1.
• ORG_ID — Operating unit (multi-org) discriminator, ensuring template sets are isolated per operating unit; part of the U2 business-key candidate.
• START_DATE / END_DATE — Effective dating window that governs when a template set version is active.
• DESCRIPTION — Free-text description of the template set's purpose.
• GTS_ID — Identifier that links the template set to its associated generation/grouping template configuration.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and user context.

The surrogate key ID is distinct from the business key composed of NAME, VERSION, and ORG_ID. This separation allows the same template set name to coexist across operating units and evolve through versions while retaining a single stable row identity referenced by downstream tables.

Common Use Cases and Queries

Typical scenarios include verifying which template set is assigned to a product or contract, auditing effective-dated versions, and reporting on template configuration by operating unit.

• Retrieve the active template set for an operating unit:

  SELECT id, name, version, start_date, end_date FROM okl.okl_ae_tmpt_sets_all WHERE org_id = :p_org_id AND SYSDATE BETWEEN start_date AND end_date AND (end_date IS NULL OR end_date > SYSDATE);

• List all versions of a named template set:

  SELECT id, name, version, start_date, end_date FROM okl.okl_ae_tmpt_sets_all WHERE name = :p_name AND org_id = :p_org_id ORDER BY version;

• Find contracts referencing a template set through OKL_TRX_CONTRACTS_ALL:

  SELECT c.id, c.contract_number FROM okl.okl_trx_contracts_all c WHERE c.aes_id = :p_aes_id;

• Identify products bound to a template set via OKL_PRODUCTS.AES_ID for impact analysis before retiring a version.

Because effective dates are stored directly, reports should always filter on the date range and ORG_ID to avoid returning superseded versions.

Related Objects

The following objects are the most significant consumers or dependents of OKL_AE_TMPT_SETS_ALL, per the documented foreign-key relationships:

• OKL_PRODUCTS — References OKL_AE_TMPT_SETS_ALL through OKL_PRODUCTS.AES_ID, associating a lease product with its accounting template set.
• OKL_TRX_CONTRACTS_ALL — References the table through OKL_TRX_CONTRACTS_ALL.AES_ID, linking individual lease/loan contracts to the template set that governs their accounting.
• OKL_AE_TMPT_SETS_ALL_PK / _U1 / _U2 / _UK1 — Primary, unique, and business-key indexes enforcing ID and (NAME, VERSION, ORG_ID) integrity.
• Associated template and generation configuration tables referenced through GTS_ID, which complete the accounting rule definition.

Together these relationships establish OKL_AE_TMPT_SETS_ALL as a central reference table in the OKL accounting engine, bridging product setup and contract-level accounting generation.