Results for “trx_line_amount”

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

Overview

OKS_BILL_TXN_LINES_V is an APPS-owned database view in the Oracle E-Business Suite Service Contracts (OKS) module. It exposes billing transaction line detail originating from the OKS_BILL_TXN_LINES base table and is delivered in both release 12.1.1 and 12.2.2. The view presents the transactional charging lines generated when service contracts are billed, tying together the billing instance, the transaction header, the transaction line amount, and the associated tax amount for each billed line.

In the context of the user search term "trx_line_amount," this view is the canonical presentation layer for the TRX_LINE_AMOUNT column. That column represents the extended amount charged for an individual billing transaction line before the associated tax component. The view is defined as a simple, non-joining projection over its synonym, so it preserves row cardinality one-to-one with the underlying table and applies no filtering, deduplication, or aggregation. Its primary role is to provide a stable, named, and DBA-documented interface for reporting, concurrent program extract logic, integration feeds, and ad hoc querying of contract billing amounts.

Underlying Base Objects

The view is defined directly over the object OKS_BILL_TXN_LINES, which is referenced through an APPS synonym. The documented view text performs a straightforward SELECT of the base table columns using the alias BTLB. Because the synonym resolves to the single base table, the view introduces no joins and no business-rule predicates; all rows present in OKS_BILL_TXN_LINES are visible through the view.

The view surfaces the base table's primary key column ID, along with the ROWID projected as ROW_ID and the OBJECT_VERSION_NUMBER used for optimistic locking in the underlying entity. The transactional linkage columns BTN_ID (billing transaction), BSL_ID (billing transaction line context), and BCL_ID (billing context line) are carried forward unchanged, allowing consumers to navigate from the view to parent billing constructs. Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are also exposed.

Key Columns

• TRX_LINE_AMOUNT — The billed amount for the transaction line; the primary measure referenced by the search term "trx_line_amount."
• TRX_LINE_TAX_AMOUNT — The tax component associated with the same billing transaction line, reported separately from the line amount.
• ID — Primary identifier of the billing transaction line record.
• BTN_ID — Foreign reference to the parent billing transaction header.
• BSL_ID / BCL_ID — Identifiers linking the line to its billing line and billing context line structures.
• BILL_INSTANCE_NUMBER — The billing instance against which the transaction was generated.
• TRX_NUMBER, TRX_DATE, TRX_CLASS — Transaction number, accounting/transaction date, and transaction class for the billing line.
• MANUAL_CREDIT — Flag indicating a manually entered credit on the billing line.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield context and segment values.
• OBJECT_VERSION_NUMBER — Version token supporting concurrent update control.

Common Use Cases and Queries

Typical reporting usage reconciles billed contract revenue by transaction and period, aggregates line amounts and tax, or extracts detail for downstream financial systems. Because the view performs no transformation, query performance mirrors the base table, and predicates on BTN_ID or TRX_DATE should be pushed to the driving query.

A representative query retrieves line-level billing amounts for a given billing transaction:

• SELECT trx_number, trx_line_amount, trx_line_tax_amount, trx_class, trx_date FROM apps.oks_bill_txn_lines_v WHERE btn_id = :p_btn_id;
• SELECT TRUNC(trx_date,'MM') period, SUM(trx_line_amount) net_amount, SUM(trx_line_tax_amount) tax_amount FROM apps.oks_bill_txn_lines_v GROUP BY TRUNC(trx_date,'MM') ORDER BY 1;
• SELECT bill_instance_number, manual_credit, trx_line_amount FROM apps.oks_bill_txn_lines_v WHERE manual_credit = 'Y';

This view is a read-only reporting artifact and should not be used for direct DML; maintenance of billing transaction lines belongs to the Service Contracts billing programs that operate against the underlying base table.