Results for “okl_ae_templates_v”

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

Overview

OKL_AE_TEMPLATES_V is a reporting view within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL), exposed in releases 12.1.1 and 12.2.2. The view presents accounting templates — the configurable rule sets that determine how lease and finance transactions are translated into accounting events and ultimately into general ledger postings. Accounting templates in OKL drive the derivation of debit and credit distributions for contract events such as bookings, accruals, billings, and terminations, and are therefore central to the financial integrity of the leasing subledger.

The view is a thin projection over the base table OKL_AE_TEMPLATES, applying an organization-level (Multi-Org / MOAC) security predicate rather than aggregating or joining additional objects. As such, it functions as a secure, read-optimized access layer that reports and integrations can query to retrieve template definitions without exposing raw table access or bypassing operating unit filtering. Because it carries the full attribute-column set (ATTRIBUTE1 through ATTRIBUTE15) plus descriptive and effective-dating fields, it is equally suited to configuration auditing and to downstream programmatic consumption.

Underlying Base Objects

The view is defined as a SELECT over the single base object OKL_AE_TEMPLATES (aliased AVLB), exposing all columns and the ROWID. No joins to lookup or reference tables are performed inside the view, so enrichment with template type, accounting source, or event descriptions must be performed by the caller. The WHERE clause enforces operating unit security by comparing the row's ORG_ID — via NVL(ORG_ID, ...) — against the ORG_ID derived from the USERENV('CLIENT_INFO') session context. Note that the metadata records "Not implemented in this database," meaning the view exists in the documented schema but is not instantiated in every environment; the referenced base objects are also listed as "none documented" in the ETRM repository. Callers should therefore confirm object existence with ALL_VIEWS or DBA_OBJECTS before relying on it in concurrent programs or BI Publisher data models.

Key Columns

• ID / ROW_ID — Primary identifier and physical row locator for each accounting template.
• POST_TO_GL — Flag indicating whether the template's generated accounting entries are transferred to the General Ledger; this is the column directly relevant to users searching for post_to_gl behavior.
• TRY_ID / AES_ID / STY_ID / FMA_ID / SET_OF_BOOKS_ID — Foreign keys linking the template to its transaction type, accounting event source, source type, formula/accounting rule, and ledger.
• FAC_CODE / SYT_CODE — Code values identifying the accounting source and source type driving the template.
• ADVANCE_ARREARS — Distinguishes advance versus arrears accounting treatment.
• MEMO_YN / PRIOR_YEAR_YN / ACCRUAL_YN — Control flags for memo entries, prior-year processing, and accrual accounting.
• FACTORING_SYND_FLAG — Indicates applicability to factoring or syndication scenarios.
• START_DATE / END_DATE and NAME / DESCRIPTION / VERSION — Effective dating and descriptive metadata for template identification and audit.
• ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 — Descriptive flexfield segments reserved for client extensions.
• ORG_ID — Operating unit driving MOAC security.

Common Use Cases and Queries

A frequent requirement is to identify which accounting templates actually post to the ledger, or which are configured not to. The following query lists templates in the current operating unit that are marked for GL posting:

SELECT id, name, set_of_books_id, post_to_gl, advance_arrears, accrual_yn, start_date, end_date FROM okl_ae_templates_v WHERE post_to_gl = 'Y' ORDER BY name;

To audit versioning and recently modified templates, order by LAST_UPDATE_DATE and filter by the ATTRIBUTE1 extensibility column where localizations are stored. A further scenario joins the view to OKL_AE_SOURCES or OKL transaction type lookup tables on SYT_CODE and FAC_CODE to reconstruct human-readable template definitions for documentation or migration. Because none of these lookups are embedded in the view, integrators should treat OKL_AE_TEMPLATES_V strictly as a secured, single-table projection and perform all enrichment in the surrounding query.