Search Results okl_txl_adjsts_lns_all_b




Overview
Explore in AI Chat

Overview

The OKL_TXL_ADJSTS_LNS_ALL_B table is a core transactional entity within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. It serves as the detailed line-level repository for recording the application of write-offs or adjustments from the leasing system to specific Accounts Receivable (AR) invoices. This table is fundamental to the financial reconciliation process between the leasing contracts managed in OKL and the corresponding receivables tracked in the AR module, ensuring that credit actions initiated in the lease portfolio are accurately reflected in the general ledger.

Key Information Stored

The table's primary function is to link an adjustment transaction to its associated invoice line and accounting distribution. Its key columns, as indicated by its foreign key relationships, include the unique identifier (ID), which serves as the primary key. The ADJ_ID column references the parent adjustment header in OKL_TRX_AR_ADJSTS_ALL_B. The TIL_ID and TLD_ID columns link to the specific invoice line (OKL_TXL_AR_INV_LNS_B) and its associated detail (OKL_TXD_AR_LN_DTLS_B) being adjusted. The PSL_ID connects the entry to the AR payment schedule (AR_PAYMENT_SCHEDULES_ALL) for the invoice. Finally, the CODE_COMBINATION_ID points to the specific general ledger account (GL_CODE_COMBINATIONS) impacted by the adjustment, defining its accounting treatment.

Common Use Cases and Queries

This table is central to audit trails, reconciliation reports, and financial inquiries related to lease write-offs. A common reporting requirement is to trace the full impact of an adjustment. A typical query would join this table to its related entities to retrieve a comprehensive view of an adjustment's application.

  • Reconciliation Report: To verify all write-offs applied to a specific lease invoice, one would query this table filtered by the associated TIL_ID or PSL_ID, joining to the adjustment header and GL accounts to report amounts and accounting codes.
  • Audit Trail: For a given adjustment header (ADJ_ID), a query can list all invoice lines and amounts affected, providing a detailed audit trail of the transaction.

Sample SQL Pattern:

SELECT adjln.id, adjln.adj_id, invln.line_number, ps.customer_trx_id, gcc.segment1
FROM okl_txl_adjsts_lns_all_b adjln,
     okl_txl_ar_inv_lns_b invln,
     ar_payment_schedules_all ps,
     gl_code_combinations gcc
WHERE adjln.til_id = invln.id
AND adjln.psl_id = ps.payment_schedule_id
AND adjln.code_combination_id = gcc.code_combination_id
AND adjln.adj_id = :p_adj_id;

Related Objects

The table is a central hub in the OKL-to-AR integration, with documented foreign key relationships to several critical tables. These relationships define its role in the data model:

  • OKL_TRX_AR_ADJSTS_ALL_B: Linked via ADJ_ID. This is the parent adjustment header table.
  • OKL_TXL_AR_INV_LNS_B: Linked via TIL_ID. This references the specific lease invoice line being adjusted.
  • OKL_TXD_AR_LN_DTLS_B: Linked via TLD_ID. This provides further detail for the invoice line.
  • AR_PAYMENT_SCHEDULES_ALL: Linked via PSL_ID. This ties the adjustment to the core AR transaction schedule.
  • GL_CODE_COMBINATIONS: Linked via CODE_COMBINATION_ID. This defines the accounting entry for the adjustment amount.