Results for “btc_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_TXL_CNTRCT_LNS_ALL is the lease transaction line table within the Oracle E-Business Suite (EBS) OKL product family — Leasing and Finance Management. It resides in the OKL schema and is classified as VALID in both EBS 12.1.1 and 12.2.2. The table records the individual transaction lines that make up a lease contract, capturing cash flows, receipts, disbursements, tax lines, stream assignments, and rule-based accrual activity associated with a lease. It is one of the central transactional stores used by the OKL sub-ledger to translate contract terms into accounting events.

Under a heuristic Data Vault classification derived from its foreign key structure, this table is best modeled as a link. It does not act as a standalone hub because it primarily stitches together references to headers (OKL_K_HEADERS), cash batches, receipts, stream types, buckets, accrual templates, and tax lines through its numerous foreign keys. This suggests it resolves many-to-many relationships between those parent dimensions and acts as the connective transactional fact table of the contract line domain.

Key Information Stored

The table documents 58 columns. The surrogate primary key is ID, enforced by the unique index OKL_TXL_CNTRCT_LNS_ALL_PK and mirrored by OKL_TXL_CNTRCT_LNS_ALL_U1, which represents the closest documented business-key candidate. The most operationally significant columns include:

• ID — Surrogate primary key for the transaction line.
• LINE_NUMBER — Human-readable sequencing of lines within a contract.
• KHR_ID — Foreign key to OKL_K_HEADERS, identifying the owning lease contract header.
• TCN_ID — Contract identifier linking the line to its broader contract context.
• RCT_ID — Reference to OKL_TRX_CSH_RCPT_ALL_B (receipts).
• BTC_ID — Reference to OKL_TRX_CSH_BATCH_ALL_B (cash batches).
• STY_ID — Reference to OKL_STRM_TYPE_B, identifying the stream type applied to the line.
• AVL_ID and BKT_ID — References to accrual templates and buckets respectively.
• TCL_TYPE — Classifies the transaction line type (e.g., cash, tax, accrual).
• AMOUNT and CURRENCY_CODE — Monetary value and currency of the line.
• TAX_LINE_ID — Foreign key into ZX_LINES for the associated tax detail.
• GL_REVERSAL_YN, ACCRUAL_RULE_YN, BEFORE_TRANSFER_YN — Flags controlling accounting behavior.
• ORG_ID — Multi-org operating unit context.
• The ATTRIBUTE1–15 flexfield columns and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include reconstructing lease cash flow schedules, tracing accrued versus cash-based lines, isolating tax lines for tax reporting, and auditing GL-reversal lines. A common pattern joins the line table to the header to resolve contract numbers:

SELECT l.LINE_NUMBER, l.AMOUNT, l.CURRENCY_CODE, h.CONTRACT_NUMBER
FROM   OKL_TXL_CNTRCT_LNS_ALL l
JOIN   OKL_K_HEADERS h ON h.ID = l.KHR_ID
WHERE  l.ORG_ID = :org_id
AND    l.CREATION_DATE >= :start_date;

Tax-focused queries join to ZX_LINES on TAX_LINE_ID, while stream analysis joins to OKL_STRM_TYPE_B on STY_ID. Extracts filtered by TCL_TYPE support sub-ledger to GL reconciliation, and the ACCRUAL_RULE_YN and GL_REVERSAL_YN flags are commonly combined to identify accrued versus immediate cash lines.

Related Objects

The most significant related objects are driven by the documented foreign keys:

• OKL_K_HEADERS — Linked via KHR_ID; the parent contract header.
• OKL_TRX_CSH_RCPT_ALL_B — Linked via RCT_ID; receipts applied to lines.
• OKL_TRX_CSH_BATCH_ALL_B — Linked via BTC_ID; cash batches.
• OKL_STRM_TYPE_B — Linked via STY_ID; stream type definitions.
• OKL_BUCKETS — Linked via BKT_ID; bucket groupings used for aging/accounting.
• OKL_AE_TEMPLATES_ALL — Linked via AVL_ID; accounting/accrual templates.
• ZX_LINES — Linked via TAX_LINE_ID; tax calculation detail.
• OKL_TXL_CNTRCT_LNS_ALL — Self-referencing via TCN_ID, indicating hierarchical or parent-child line relationships.

These dependencies position the table as a key integration point between OKL contract setup, cash processing, tax, and the general ledger.