Search Results interface_line_attribute15

Overview

The OKX_CUST_TRX_LINES_V view is a Contracts Integration (OKX) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes customer transaction line data for invoices, debit memos, chargebacks, credit memos, and commitments, presenting a focused projection of receivable line attributes intended for integration and reporting consumption. The view is registered as VALID in the ETRM metadata and carries a single documented base object reference.

Because the OKX product handles the flow of contract-related transactions into Oracle Receivables, this view serves as a read-only interface for extracting transaction line information in a form that is stable relative to the underlying wide Receivables table. It is documented as "Oracle Proprietary, Confidential Information" with a legal flag of "N."

Underlying Base Objects

The view is defined over a single base object: RA_CUSTOMER_TRX_LINES_ALL, referenced in the view text through the synonym and aliased as CTL. In the ETRM metadata the referenced base object is recorded with the type SYNONYM, which in a standard EBS installation resolves to the APPS synonym for the Receivables transaction lines table.

The SELECT list maps columns directly from the base table without joins, aggregations, or filters, so the view is a straight projection. This means row cardinality and uniqueness characteristics of the view mirror those of RA_CUSTOMER_TRX_LINES_ALL: one row per customer transaction line, keyed by CUSTOMER_TRX_LINE_ID. No WHERE clause is present, so no implicit filtering by line type, org, or status is applied by the view itself.

Key Columns

• ORG_ID — Operating unit identifier, the multi-org partitioning key for the transaction line.
• SET_OF_BOOKS_ID — Ledger (set of books) associated with the transaction line.
• CUSTOMER_TRX_LINE_ID — Primary key of the customer transaction line.
• CUSTOMER_TRX_ID — Foreign key to the parent transaction header (invoice, debit memo, chargeback, credit memo, or commitment).
• LINE_TYPE — Classification of the line, distinguishing line categories such as line, tax, freight, and charges.
• EXTENDED_AMOUNT — The extended amount for the line, the field most directly relevant to the "extended_amount" search. It represents the line-level monetary value carried from the Receivables base table.
• LINK_TO_CUST_TRX_LINE_ID — Self-referencing link to another customer transaction line, used to associate a line with a related line (for example, a charge line linked to a base line).
• INTERFACE_LINE_CONTEXT — Descriptive flexfield context that determines which interface line attributes are meaningful for the line.
• INTERFACE_LINE_ATTRIBUTE1 – INTERFACE_LINE_ATTRIBUTE15 — The descriptive flexfield segment columns. Note that ATTRIBUTE9 is positioned after ATTRIBUTE15 in the documented SELECT list, though the logical set covers ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

The view is typically used to report or extract line-level receivable amounts tied to contracts integration. A common query retrieves extended amounts for all lines of a given transaction:

• SELECT customer_trx_id, customer_trx_line_id, line_type, extended_amount FROM okx_cust_trx_lines_v WHERE customer_trx_id = :p_trx_id;
• SELECT org_id, line_type, SUM(extended_amount) FROM okx_cust_trx_lines_v WHERE org_id = :p_org_id GROUP BY org_id, line_type;
• SELECT customer_trx_line_id, link_to_cust_trx_line_id, extended_amount FROM okx_cust_trx_lines_v WHERE link_to_cust_trx_line_id IS NOT NULL;

Because the view is a direct projection of RA_CUSTOMER_TRX_LINES_ALL, queries filter by ORG_ID and SET_OF_BOOKS_ID for multi-org and ledger scope, and join to transaction headers via CUSTOMER_TRX_ID when header context is required. Interface flexfield queries should first constrain on INTERFACE_LINE_CONTEXT to interpret the attribute segments correctly.