Search Results okl_acc_events_all




Overview
Explore in AI Chat

Overview

The OKL_ACC_EVENTS_ALL table is a core data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It serves as the master repository for accounting events, which are critical triggers for the generation of accounting entries in the leasing lifecycle. Every financial transaction, such as a lease booking, invoice, payment, or adjustment, creates a record in this table to signify that an accounting activity has occurred and requires processing. Its role is foundational to the OKL accounting engine, acting as the primary source for downstream processes that create journal entries in the General Ledger. The '_ALL' suffix indicates it is a multi-organization structure, storing data partitioned by operating unit.

Key Information Stored

The table's primary purpose is to catalog and track the status of accounting events. While the provided metadata specifies the primary key column, the logical data model implies the storage of several key attributes. The central column is ACCOUNTING_EVENT_ID, the unique sequence-generated identifier for each event. Other critical columns typically include EVENT_TYPE_CODE, which classifies the nature of the financial transaction (e.g., 'BOOKING', 'INVOICE'), and EVENT_STATUS_CODE, indicating the processing state (e.g., 'UNPROCESSED', 'PROCESSED', 'ERROR'). The table also stores references to the source transaction, such as a contract or invoice ID, the date of the event, and the associated operating unit (ORG_ID). These fields collectively enable the system to manage the flow of accounting data from source transaction to final journal entry.

Common Use Cases and Queries

This table is central for troubleshooting accounting issues, auditing transaction flows, and generating custom operational reports. A common use case involves identifying unprocessed or errored events that are preventing journal creation. A typical query would filter on EVENT_STATUS_CODE. For auditing, one might join to source transaction tables to trace the accounting history of a specific lease contract. Reporting on accounting event volumes by type or organizational unit is another frequent requirement. Sample SQL to find pending events for a specific operating unit might resemble:

  • SELECT accounting_event_id, event_type_code, event_date
  • FROM okl_acc_events_all
  • WHERE org_id = 123
  • AND event_status_code = 'UNPROCESSED';

Direct data manipulation (DML) on this table is strongly discouraged; interaction should occur via standard OKL public APIs to maintain data integrity.

Related Objects

As indicated by the foreign key relationships in the metadata, OKL_ACC_EVENTS_ALL is integrally linked to other key OKL accounting tables. The OKL_AE_HEADERS_ALL table, which stores the summarized accounting entries (journal headers) generated from an event, references it via ACCOUNTING_EVENT_ID. Similarly, the OKL_TRNS_ACC_DSTRS_ALL table, which holds detailed accounting distributions (journal lines), references it via the AET_ID (Accounting Event ID) column. This establishes a clear hierarchy: an Accounting Event (OKL_ACC_EVENTS_ALL) drives the creation of an Accounting Entry Header (OKL_AE_HEADERS_ALL), which in turn contains multiple Accounting Distributions (OKL_TRNS_ACC_DSTRS_ALL). Understanding this relationship chain is essential for tracing the complete accounting lifecycle of any leasing transaction.