Results for “okl_trns_acc_dstrs”

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

Overview

OKL_TRNS_ACC_DSTRS is a table within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. Its documented description is "Accounting distributions," indicating that it stores the account distribution lines generated during accounting event processing for lease and finance transactions. In the context of Oracle EBS 12.1.1 and 12.2.2, this table participates in the accounting engine flow that translates business events into general ledger distributions, working alongside the accounting events and accounting event template infrastructure.

The ETRM metadata indicates that this object is "Not implemented in this database," which means the table may not be physically present or populated in the specific environment from which the metadata was mined, but its definition and relationships remain valid. Based on the foreign key structure, the heuristic Data Vault classification for this table is link. This classification suggests the table behaves as an associative entity connecting accounting events to accounting templates and their resulting distribution lines, rather than acting as an independent hub or a pure descriptive satellite.

Key Information Stored

The table is organized around a surrogate primary key and a set of foreign key columns that establish its relationships. The most significant columns documented in the metadata include:

• ID — The surrogate primary key, defined by the constraint OKL_TRNS_ACC_DSTRS_PK. This uniquely identifies each accounting distribution row.
• AET_ID — Foreign key to OKL_ACCOUNTING_EVENTS, linking the distribution to the accounting event that generated it.
• TEMPLATE_ID — Foreign key to OKL_AE_TEMPLATES, identifying the accounting event template applied to produce the distribution.

Beyond these documented columns, the table in a typical implementation holds distribution detail attributes such as the account code combination, debit and credit amounts, distribution line number, and status flags. The surrogate key ID distinguishes technical row identity from business-key candidates; the pair or combination of AET_ID and TEMPLATE_ID, together with line-level attributes, often functions as the effective business key for a distribution line. Because the metadata does not document a unique business index beyond the primary key, AET_ID and TEMPLATE_ID should be treated as the principal relational identifiers.

Common Use Cases and Queries

Typical use cases center on accounting event reconciliation, distribution reporting, and GL transfer validation. Analysts commonly query this table to confirm that each accounting event produced the expected distribution lines and to trace how a template drove the resulting accounts.

A representative query joins the distribution table to its parent accounting event:

• SELECT d.id, d.aet_id, d.template_id FROM okl_trns_acc_dstrs d WHERE d.aet_id = :event_id;

Reporting scenarios include auditing distributions by template, summarizing debit and credit activity per event, and validating that no event is missing its expected distribution rows. A join to OKL_AE_TEMPLATES allows analysts to group distributions by template to detect configuration issues. Because the object may be unpopulated in some environments, queries should be guarded with existence checks or executed against the environment where the accounting engine is active.

Related Objects

The most significant related objects are those directly connected through documented foreign keys:

• OKL_ACCOUNTING_EVENTS — referenced by OKL_TRNS_ACC_DSTRS.AET_ID; represents the accounting event that owns each distribution.
• OKL_AE_TEMPLATES — referenced by OKL_TRNS_ACC_DSTRS.TEMPLATE_ID; defines the template that generated the distribution.

In practice, these two parents are complemented by GL interface and accounting program objects that consume the distributions, but the ETRM metadata explicitly documents only the two foreign key relationships above. Any extension beyond these relationships should be validated against the specific EBS 12.1.1 or 12.2.2 instance before reliance.