Search Results event_type_code_desc

Overview

OKL_AE_LINES_UPDT_UV is a reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family (Oracle Lease and Finance Management) and exposes accounting entry lines generated by the OKL Accounting Engine (AE) that have failed validation against the chart of accounts. The view is registered as VALID in the ETRM data dictionary and serves as a diagnostic and correction aid for the Accounting Engine's subledger accounting process.

The view presents one row per accounting line whose ACCOUNTING_ERROR_CODE equals 'INVALID_ACCOUNT', joined to its parent accounting header, accounting event, lease contract line, lease contract, and the concatenated accounting flexfield value. Because the view is prefixed "UPDT", it is intended to support the workflow by which finance and accounting teams review posting failures and update the accounting flexfield or account derivation rules so that the affected lines can be re-validated and transferred to the General Ledger. The user search term "ae_line_id" corresponds to the primary key column exposed by the view, which uniquely identifies each accounting entry line in OKL_AE_LINES_ALL.

Underlying Base Objects

The view is defined over seven documented referenced objects. The core transactional table is OKL_AE_LINES_ALL (aliased AEL), which stores the individual debit and credit lines produced by the Accounting Engine; AE_LINE_ID is the primary key of this table. OKL_AE_HEADERS (aliased AEH) supplies the header-level accounting context: period name, accounting date, and the header-to-line relationship via AE_HEADER_ID. OKL_ACC_EVENTS_ALL (aliased AET) provides the accounting event that triggered the entry, including the event number, event type, and event status, and links to its source transaction through SOURCE_TABLE and SOURCE_ID.

The source transaction for these lines is a lease contract line, resolved through OKL_TXL_CNTRCT_LNS_ALL (aliased TCL), where the join is restricted to AET.SOURCE_TABLE = 'OKL_TXL_CNTRCT_LNS'. OKL_TRX_CONTRACTS_ALL (aliased TCN) supplies the lease transaction number. GL_CODE_COMBINATIONS_KFV (aliased GCCK) supplies the concatenated accounting flexfield segments and is joined with an outer join (+) on CODE_COMBINATION_ID, so lines with a null or invalid code combination still appear. The OKL_ACCOUNTING_UTIL package is called three times to translate lookup codes into human-readable meanings and to derive the account description, making it an object dependency of the view.

Key Columns

• AE_LINE_ID — Primary key of the accounting entry line; the join key back to OKL_AE_LINES_ALL for any correction.
• TRX_NUMBER, LINE_NUMBER — Lease transaction number and contract line number, identifying the source transaction in business terms.
• AE_LINE_TYPE_CODE, AE_LINE_TYPE_MEANING — Line type code and its decoded meaning from the OKL_AE_LINE_TYPE lookup.
• ACCOUNT, ACCOUNT_DESC, CODE_COMBINATION_ID — Concatenated accounting flexfield segments, descriptive account text, and the underlying code combination identifier. The search term "ae_line_id" pairs most often with these columns when diagnosing posting errors.
• ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR, CURRENCY_CODE — Entered and accounted debit/credit amounts and the transaction currency.
• PERIOD_NAME, ACCOUNTING_DATE — Accounting period and date from the header, used to scope remediation work.
• ACCOUNTING_ERROR_CODE — Always 'INVALID_ACCOUNT' in this view, the condition that defines its population.
• EVENT_NUMBER, EVENT_TYPE_CODE, EVENT_TYPE_CODE_DESC, EVENT_STATUS_CODE, EVENT_STATUS_CODE_DESC — Accounting event identity, decoded event type, and decoded event status.
• SOURCE_TABLE, SOURCE_ID — The originating transaction table and identifier behind the accounting event.

Common Use Cases and Queries

The principal use case is the resolution of invalid-account posting failures. Accounting staff query the view to list every accounting line that the Accounting Engine could not post because the derived code combination was invalid, then correct the account derivation setup or manually assign a valid code combination and re-run accounting for the associated event.

A typical query retrieves failed lines for a period:

• SELECT ae_line_id, trx_number, line_number, ae_line_type_meaning, account, account_desc, entered_dr, entered_cr, currency_code, period_name, accounting_date, event_number, event_type_code_desc FROM okl_ae_lines_updt_uv WHERE period_name = :p_period ORDER BY trx_number, line_number;

Because AE_LINE_ID is selective and indexed in the base table, a second common pattern targets a single line for investigation or correction:

• SELECT ae_line_id, trx_number, line_number, code_combination_id, account, accounting_error_code, event_status_code_desc FROM okl_ae_lines_updt_uv WHERE ae_line_id = :p_ae_line_id;

A third pattern aggregates impact by event type and currency to size the remediation effort:

• SELECT event_type_code_desc, currency_code, COUNT(*) line_count, SUM(entered_dr) total_dr, SUM(entered_cr) total_cr FROM okl_ae_lines_updt_uv GROUP BY event_type_code_desc, currency_code;

Each returned AE_LINE_ID can be used to locate the corresponding row in OKL_AE_LINES_ALL, update the CODE_COMBINATION_ID to a valid account, and clear the accounting error so the line is re-validated and transferred to Oracle General Ledger.