Results for “okl_ae_templates”

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

Overview

The OKL_AE_TEMPLATES table is a core configuration object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It stores accounting templates — the reusable rules that determine how accounting entries are generated for lease and finance transactions. Each row defines a template that maps a transaction, stream type, and accounting template set combination to a set of distribution and formula definitions, effectively governing how the OKL subledger creates its accounting events and journal lines.

Based on the documented foreign-key topology, the table can be modeled heuristically as a satellite-leaning entity. It carries a highly composite business key and holds descriptive/definitional attributes that qualify and extend the parent transactional and setup entities it references (transaction types, stream types, formula sets, and accounting template sets). In a Data Vault design, the natural business key would form the hub, while the template-specific descriptive columns would sit in a satellite.

The table is documented as "Not implemented in this database," meaning it may be absent or unpopulated in certain 12.1.1 / 12.2.2 environments, which is important when writing queries that assume its existence.

Key Information Stored

The primary surrogate key is ID, enforced via the OKL_AE_TEMPLATES_PK constraint. A second unique constraint, AVL_AVL_UK, defines the composite business-key candidate: TRY_ID, SET_OF_BOOKS_ID, STY_ID, AES_ID, NAME, and VERSION. The most significant columns are:

• ID — surrogate primary key identifying the accounting template row.
• TRY_ID — foreign key to OKL_TRX_TYPES_B, the lease transaction type.
• SET_OF_BOOKS_ID — the ledger/set of books the template applies to.
• STY_ID — foreign key to OKL_STRM_TYPE_B, the stream (cash flow) type.
• AES_ID — foreign key to OKL_AE_TMPT_SETS, the accounting template set.
• NAME — the template name (business-key component).
• VERSION — the template version (business-key component, supporting revisions).
• AVL_ID — referenced by OKL_TXL_CNTRCT_LNS.AVL_ID, linking templates to contract lines.
• FMA_ID — foreign key to OKL_FORMULAE_B, the associated accounting formula.

The composite business key is notable: a given combination of transaction type, ledger, stream type, template set, name, and version must be unique, which supports controlled refinement of accounting rules across versions.

Common Use Cases and Queries

Typical use cases include auditing which accounting templates are configured for a given transaction type and ledger, tracing how a contract line's accounting was derived, and reporting on template-versus-version history. A representative query joining the setup parents follows:

• Resolve a template's full context: join OKL_AE_TEMPLATES to OKL_TRX_TYPES_B on TRY_ID, to OKL_STRM_TYPE_B on STY_ID, and to OKL_AE_TMPT_SETS on AES_ID.
• Trace generated distributions: join OKL_TRNS_ACC_DSTRS on TEMPLATE_ID = OKL_AE_TEMPLATES.ID.
• Link templates to lease contract lines via OKL_TXL_CNTRCT_LNS.AVL_ID = OKL_AE_TEMPLATES.AVL_ID.
• Filter by SET_OF_BOOKS_ID to report templates per ledger; order by VERSION to view revision history.

Related Objects

The table participates in a rich relationship graph. It references four parent setup tables and is referenced by two downstream tables:

• OKL_AE_TMPT_SETS — joined on AES_ID; the accounting template set.
• OKL_STRM_TYPE_B — joined on STY_ID; the stream type.
• OKL_TRX_TYPES_B — joined on TRY_ID; the transaction type.
• OKL_FORMULAE_B — joined on FMA_ID; accounting formulas.
• OKL_TRNS_ACC_DSTRS — references this table via TEMPLATE_ID; holds generated accounting distributions.
• OKL_TXL_CNTRCT_LNS — references this table via AVL_ID; contract line linkage.