Results for “bgh_id”

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

Overview

OKL_TXD_AR_LN_DTLS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the OKL (Leasing and Finance Management) product family. Its documented purpose is to present the transaction line details that are staged for inclusion on Receivables invoices. In effect, the view flattens the transactional detail records created by the OKL tax and disbursement processing engine into a single, invoice-oriented row shape that can be consumed by the Receivables integration, by concurrent programs, and by downstream reporting.

The view is a union of the base detail records and their translated descriptive attributes, so that a line detail carries both its operational values (amount, links to the originating batch, stream, and contract identifiers) and its user-facing descriptive text. Because it is a view rather than a table, it inherits the security, multi-org behavior, and row-level access of its underlying tables, and it should be treated as read-only reference data. The presence of columns such as INVOICE_FORMAT_TYPE, INVOICE_FORMAT_LINE_TYPE, TXL_AR_LINE_NUMBER, and INVESTOR_DISB_STATUS confirms that the view is the interface through which invoice formatting decisions and investor disbursement state are surfaced to the Receivables side of the flow.

Underlying Base Objects

Per the ETRM metadata, the view is defined over two referenced base objects, both exposed as synonyms in the APPS schema:

• OKL_TXD_AR_LN_DTLS_B — the base detail table holding the transaction line detail rows, including amounts, identifiers, audit columns, and the descriptive flexfield ATTRIBUTE1 through ATTRIBUTE15 columns.
• OKL_TXD_AR_LN_DTLS_TL — the translation table supplying language-dependent descriptive text, joined to the base rows to supply DESCRIPTION, ERROR_MESSAGE, and the translated header/detail attributes such as SFWT_FLAG.

The view text shows the join rooted on OKL_TXD_AR_LN_DTLS_B (aliased TLDB) with OKL_TXD_AR_LN_DTLS_TL (aliased TLDT), keying on the shared identifier. This mirrors the standard EBS multilingual pattern in which the _B table stores language-independent columns and the _TL table stores translated columns addressed by language and source language.

Key Columns

• ID, ROW_ID, OBJECT_VERSION_NUMBER — surrogate key, rowid, and optimistic locking token for the underlying detail row.
• RECEIVABLES_INVOICE_ID — the invoice the line detail is destined for; the principal link into Receivables.
• AMOUNT, AMOUNT_APPLIED — the transaction line amount and how much has been applied.
• INVOICE_FORMAT_TYPE, INVOICE_FORMAT_LINE_TYPE — classification controlling how the line is formatted on the invoice.
• TXL_AR_LINE_NUMBER — the line ordering number used on the Receivables invoice.
• LINE_DETAIL_NUMBER — the sequential identifier of the detail within its transaction line.
• STY_ID, SEL_ID, TIL_ID_DETAILS, BCL_ID, BSL_ID — keys to the stream type, stream element, transaction line details, billing cycle, and billing schedule structures.
• BCH_ID, BGH_ID, IDX_ID, TLD_ID_REVERSES — batch, batch group, index, and reversal linkage for the originating transaction.
• LATE_CHARGE_YN, LATE_CHARGE_ASS_YN, LATE_INT_ASS_YN, LATE_CHARGE_ASSESS_DATE, LATE_INT_ASSESS_DATE — late-charge and late-interest assessment flags and dates.
• INVESTOR_DISB_STATUS — investor disbursement status.
• DATE_CALCULATION, FIXED_RATE_YN, INVENTORY_ITEM_ID, INVENTORY_ORG_ID — calculation date, rate basis, and inventory linkage.
• ORG_ID — operating unit, enabling multi-org filtering.
• DESCRIPTION, ERROR_MESSAGE, SFWT_FLAG — translated/working text exposed from the translation table.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments for client-specific extensions.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE identifying the concurrent program that produced the row.

Common Use Cases and Queries

Typical uses include validating invoice-ready line details before the Receivables interface runs, investigating outbound invoice discrepancies, and building custom reports over transaction line details. Because INVOICE_FORMAT_TYPE is often the search term of interest, the following query isolates the formatting attributes together with the invoice and amount:

• SELECT txl_ar_line_number, invoice_format_type, invoice_format_line_type, receivables_invoice_id, amount, amount_applied FROM apps.okl_txd_ar_ln_dtls_v WHERE org_id = :p_org_id AND invoice_format_type = :p_format_type ORDER BY receivables_invoice_id, txl_ar_line_number;
• SELECT receivables_invoice_id, COUNT(*) line_count, SUM(amount) total_amount FROM apps.okl_txd_ar_ln_dtls_v GROUP BY receivables_invoice_id HAVING SUM(amount) <> 0;
• SELECT id, line_detail_number, description, error_message FROM apps.okl_txd_ar_ln_dtls_v WHERE error_message IS NOT NULL;

Joins to OKL_TXD_AR_LN_DTLS_B, OKL_TXD_AR_LN_DTLS_TL, or to Receivables (RA_CUSTOMER_TRX_ALL) via RECEIVABLES_INVOICE_ID are common for reconciliation. As with all reporting against large OKL tables, filters on ORG_ID and the standard audit or date columns are advisable, and direct DML against the view is neither supported nor recommended; corrections belong in the base tables or through the OKL application processes that own them.