Results for “okl_ae_tmpt_sets”

50+ results




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

Overview

OKL_AE_TMPT_SETS is a reference and header table within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). It stores accounting template sets — logical groupings that associate accounting template definitions with contract transactions and lease contracts so that the correct set of accounting generation rules is applied during accounting event processing. Each template set acts as a reusable container that can be assigned to contracts and consumed by the Accounting Engine (AE) when generating journal entries for a lease or loan transaction.

Under the heuristic Data Vault classification derived from its foreign-key topology, OKL_AE_TMPT_SETS is described as hub-leaning. In Data Vault modeling terms, this suggests the table behaves primarily as a business entity hub — a stable, uniquely identified business concept keyed by a durable business identifier — rather than as a transactional link or a descriptive satellite. In practice, referenced objects such as OKL_AE_TEMPLATES and OKL_TRX_CONTRACTS point toward this table via shared AES_ID values, reinforcing its role as a parent entity from which dependent records hang.

Note that the implementation metadata records this table as "Not implemented in this database," indicating it may be present in some deployments or release levels of OKL while remaining inactive or uninstantiated in others. In Oracle EBS 12.1.1 and 12.2.2, the OKL schema is a shared product family, so the table's presence depends on the specific OKL configuration and applied patches.

Key Information Stored

The documented metadata identifies a small but critical set of columns and keys:

  • ID — the surrogate primary key column defined by the constraint OKL_AE_TMPT_SETS_PK. This is the system-generated unique identifier referenced by child tables.
  • NAME — a business descriptor for the accounting template set; part of the unique business key.
  • VERSION — the version indicator paired with NAME, forming the alternate unique key AES_AES_UK (NAME, VERSION). This allows multiple versions of the same named template set to coexist.
  • AES_ID — although the metadata lists it as the foreign key column on the child tables, it corresponds directly to the parent identifier used in join relationships (OKL_AE_TEMPLATES.AES_ID and OKL_TRX_CONTRACTS.AES_ID both reference OKL_AE_TMPT_SETS).

The distinction is significant: ID is the surrogate key generated by the system, whereas NAME and VERSION together constitute the natural business key enforced by the unique constraint AES_AES_UK. Business users typically identify a template set by name and version rather than by internal ID.

Common Use Cases and Queries

Report developers and functional consultants query this table to determine which accounting template sets are configured, to trace how contracts and templates reference a given set, and to troubleshoot accounting generation failures. Representative patterns include:

  • Listing all defined template sets by name and version: SELECT id, name, version FROM okl_ae_tmpt_sets ORDER BY name, version;
  • Identifying templates belonging to a set: SELECT t.* FROM okl_ae_templates t, okl_ae_tmpt_sets s WHERE t.aes_id = s.id;
  • Finding contracts assigned to a particular template set: SELECT c.* FROM okl_trx_contracts c, okl_ae_tmpt_sets s WHERE c.aes_id = s.id;
  • Resolving a business key to its surrogate ID for integration or data-load purposes.

These queries support accounting setup validation, contract-accounting audits, and reconciliation of generated journal entries against their originating templates.

Related Objects

  • OKL_AE_TEMPLATES — child table; joins via OKL_AE_TEMPLATES.AES_ID → OKL_AE_TMPT_SETS.ID. Stores individual accounting template definitions grouped into a set.
  • OKL_TRX_CONTRACTS — dependent table; joins via OKL_TRX_CONTRACTS.AES_ID → OKL_AE_TMPT_SETS.ID. Assigns a template set to lease or loan contracts.
  • OKL_AE_TMPT_SETS_PK — primary key constraint on ID.
  • AES_AES_UK — unique constraint on (NAME, VERSION), enforcing the business key.
  • The broader OKL Accounting Engine objects that consume template sets during accounting event generation, though these are not enumerated in the supplied metadata.

Together these relationships confirm OKL_AE_TMPT_SETS as a parent entity anchoring template and contract associations within the OKL accounting framework.