Search Results invalid_account

Overview

APPS.OKL_AE_LINES_UPDT_UV is a reporting and inquiry view within the Oracle Enterprise Rental Management (ETRM) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. Its purpose is to expose accounting event lines that have failed validation against the chart of accounts — specifically those carrying an accounting error code of INVALID_ACCOUNT. The view joins accounting event headers, accounting event lines, transaction contracts, contract lines, and the accounting events table, then outer-joins to the key flexfield view GL_CODE_COMBINATIONS_KFV to resolve account segment concatenations and descriptions.

The view is not a base transaction entity; it is a diagnostic and corrective query surface. It is typically consumed by the "Update Accounting" or "Accounting Errors" correction flows, where a user must review lines that could not be posted to the General Ledger because the code combination was invalid (for example, disabled, end-dated, or not defined for the ledger). Because the account column is resolved through an outer join, lines with a missing code combination still return a row with a null ACCOUNT, which is itself a signal that no valid combination exists.

Underlying Base Objects

The view is defined over the following documented objects:

• OKL_AE_LINES_ALL — the accounting event lines, the driving table of the query.
• OKL_AE_HEADERS — accounting event headers supplying the period name and accounting date.
• OKL_ACC_EVENTS_ALL — the accounting events, providing event number, event type code, and event status code.
• OKL_TXL_CNTRCT_LNS_ALL — contract lines, linked to the accounting event via SOURCE_ID where SOURCE_TABLE = 'OKL_TXL_CNTRCT_LNS'.
• OKL_TRX_CONTRACTS_ALL — the transaction contract header, providing TRX_NUMBER.
• GL_CODE_COMBINATIONS_KFV — the key flexfield concatenated view, outer-joined on CODE_COMBINATION_ID.
• OKL_ACCOUNTING_UTIL — the package supplying GET_LOOKUP_MEANING and GET_CONCATE_DESC for decoded descriptions.

The joins are driven by AE_HEADER_ID between lines and headers, ACCOUNTING_EVENT_ID between headers and events, and SOURCE_ID/SOURCE_TABLE between events and contract lines. The contract header is then joined through TCN_ID. The outer join to GL_CODE_COMBINATIONS_KFV ensures every invalid-account line is returned regardless of whether the combination resolves.

Key Columns

• AE_LINE_ID — primary identifier of the accounting event line.
• TRX_NUMBER and LINE_NUMBER — the contract and line the accounting entry originated from.
• AE_LINE_TYPE_CODE / AE_LINE_TYPE_MEANING — the line type and its decoded lookup meaning.
• ACCOUNT and ACCOUNT_DESC — concatenated segments and description from GL_CODE_COMBINATIONS_KFV; null when the combination is unresolvable.
• CODE_COMBINATION_ID — the key flexfield combination identifier being validated.
• ENTERED_DR, ENTERED_CR, ACCOUNTED_DR, ACCOUNTED_CR — entered and accounted debit/credit amounts.
• CURRENCY_CODE — the transaction currency.
• PERIOD_NAME and ACCOUNTING_DATE — the GL period and accounting date from the header.
• ACCOUNTING_ERROR_CODE — filtered to 'INVALID_ACCOUNT'.
• EVENT_NUMBER, EVENT_TYPE_CODE, EVENT_STATUS_CODE and their decoded descriptions — identifying the originating accounting event and its status.

Common Use Cases and Queries

Typical usage is to list all lines failing account validation for a given period or contract, so that the account assignable flexfield or the subledger accounting setup can be corrected and the event re-accounted.

SELECT trx_number, line_number, ae_line_type_meaning,
       account, account_desc, entered_dr, entered_cr,
       period_name, accounting_date
FROM   apps.okl_ae_lines_udt_uv
WHERE  trx_number = :p_trx_number;

To isolate unresolvable combinations (no matching GL_CODE_COMBINATIONS row):

SELECT ae_line_id, trx_number, code_combination_id
FROM   apps.okl_ae_lines_udt_uv
WHERE  account IS NULL;

Because the view embeds a hard-coded filter of ACCOUNTING_ERROR_CODE = 'INVALID_ACCOUNT', it is effectively an exception report. It should be treated as read-only for diagnosis; corrections are applied through the ETRM accounting regeneration process, not by updating rows returned by the view.