Search Results okl_ae_lines_all




Overview
Explore in AI Chat

Overview

The OKL_AE_LINES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It functions as the detailed transaction repository for accounting entry lines. In the context of Oracle EBS 12.1.1 and 12.2.2, this table is integral to the financial accounting engine for leasing and financing operations, storing the individual debit and credit line items that comprise a complete accounting journal entry. Each record in this table represents a specific accounting line that, when aggregated under a common header, forms a balanced journal entry ready for posting to the General Ledger. Its role is to persist the granular financial details generated from lease contracts, invoices, payments, and other financial events processed within the OKL module.

Key Information Stored

The table's primary purpose is to hold the attributes of an accounting line item. The metadata identifies the primary key as AE_LINE_ID, a unique system-generated identifier for each line. A critical foreign key column is AE_HEADER_ID, which links each line to its parent journal entry batcheader in the OKL_AE_HEADERS_ALL table. While the full column list is not detailed in the provided excerpt, based on its function, the table typically stores data such as the accounting code combination (e.g., CODE_COMBINATION_ID), the line's entered and accounted monetary amounts (e.g., ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR), the line type, and descriptive information about the transaction source. This structure allows for the detailed audit and reconstruction of every financial posting originating from the leasing subsystem.

Common Use Cases and Queries

This table is central to financial reporting, reconciliation, and troubleshooting within OKL. Common use cases include tracing the accounting impact of a specific lease contract event, reconciling subledger transactions to the General Ledger, and analyzing accounting distributions for a period. A typical query pattern involves joining to the header table to retrieve complete journal entries. For example, to find all accounting lines for a specific lease contract number, one might query:

  • SELECT hl.ae_line_id, hl.ae_header_id, hl.code_combination_id, hl.accounted_dr, hl.accounted_cr FROM okl_ae_lines_all hl JOIN okl_ae_headers_all hh ON hl.ae_header_id = hh.ae_header_id WHERE hh.source_id = :p_lease_id AND hh.source_table = 'OKL_K_HEADERS';

Reporting use cases often aggregate data from this table by account, cost center, or product to produce subledger trial balances or detailed transaction listings.

Related Objects

The OKL_AE_LINES_ALL table has defined relationships with several key objects in the OKL schema, as indicated by the metadata. Its most critical relationship is via the foreign key to the OKL_AE_HEADERS_ALL table, which contains the batch-level control information for journal entries. This table is also a likely source for key OKL reporting views and is accessed by standard Oracle Subledger Accounting (SLA) and OKL-specific APIs for journal creation and posting processes. While not listed in the excerpt, it is commonly referenced by data migration and interface programs (e.g., OKL_ACCOUNTING_PUB) that handle the flow of accounting data from the leasing subledger to the General Ledger (GL_INTERFACE, GL_JE_LINES).