Results for “split_flag”

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

Overview

OKS_BILL_TXN_LINES is a Service Contracts (OKS) module table that stores the actual transaction amount and tax information returned from Oracle Receivables after a billing event has been processed. In the Oracle E-Business Suite 12.1.1 and 12.2.2 architecture, the Service Contracts billing flow generates invoice requests that are passed to Receivables; the inbound receipt of transaction numbers, transaction classes, line amounts, and tax amounts is persisted in this table. It therefore acts as the reconciliation bridge between the Service Contracts billing engine and the Receivables invoice that is ultimately created for a contract.

The table is narrow in scope but central to the billing confirmation process. Every billing transaction line generated for a contract is reflected here, allowing the application to report on billed amounts, tax collected, and transaction references without querying Receivables directly. The ETRM metadata classifies this object heuristically as a link table in Data Vault terms, since it resolves relationships between contract lines, sub-lines, and billing transactions while carrying descriptive measures. This is a modeling suggestion rather than a normative statement; in practice the table functions as both a join artifact and a satellite of billing amounts.

Key Information Stored

The physical schema documents 37 columns. The most significant are:

• ID — the surrogate primary key, enforced by OKS_BILL_TXN_LINES_PK. It uniquely identifies each transaction line record.
• BTN_ID — foreign key to OKS_BILL_TRANSACTIONS, tying the line to its parent billing transaction header.
• BCL_ID — foreign key to OKS_BILL_CONT_LINES, identifying the originating contract line.
• BSL_ID — foreign key to OKS_BILL_SUB_LINES, identifying the originating contract sub-line.
• BILL_INSTANCE_NUMBER — the billing instance reference generated during the billing cycle.
• TRX_NUMBER and TRX_CLASS — the Receivables transaction number and class returned from AR.
• TRX_LINE_AMOUNT and TRX_LINE_TAX_AMOUNT — the actual billed amount and tax amount as confirmed by Receivables.
• TRX_AMOUNT — the aggregate transaction amount associated with the line.
• TRX_DATE — the transaction date recorded in Receivables.
• MANUAL_CREDIT and SPLIT_FLAG — indicators for manual credit handling and line splitting.
• CYCLE_REFRENCE — a reference to the billing cycle (note the documented spelling).
• OBJECT_VERSION_NUMBER plus the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) — audit and optimistic locking.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting Multi-Org Access Control.
• The ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 columns provide the standard extensibility (DFF) mechanism.

The unique index OKS_BILL_TXN_LINES_U1 covers ID, while OKS_BILL_TXN_LINES_U3 covers (BSL_ID, BCL_ID), indicating the business-key candidate combining sub-line and contract line.

Common Use Cases and Queries

Typical scenarios include billing reconciliation reports, invoice-to-contract tracing, and tax analysis. A common pattern joins the table to its parent billing transaction and up to contract lines:

SELECT t.TRX_NUMBER,
       t.TRX_CLASS,
       l.TRX_LINE_AMOUNT,
       l.TRX_LINE_TAX_AMOUNT,
       l.TRX_DATE
FROM   OKS.OKS_BILL_TXN_LINES l,
       OKS.OKS_BILL_TRANSACTIONS t
WHERE  l.BTN_ID = t.ID
AND    l.BILL_INSTANCE_NUMBER = :instance;

To trace a billed line back to the contract, join OKS_BILL_CONT_LINES on BCL_ID and OKS_BILL_SUB_LINES on BSL_ID. Reporting users frequently aggregate TRX_LINE_AMOUNT and TRX_LINE_TAX_AMOUNT by TRX_CLASS or CYCLE_REFRENCE to produce billing summaries. Tax reconciliation reports filter on TRX_LINE_TAX_AMOUNT to verify tax returned from Receivables. Because SECURITY_GROUP_ID is present, queries executed through Multi-Org-enabled responsibilities must respect operating unit security.

Related Objects

• OKS_BILL_TRANSACTIONS — parent table; join on OKS_BILL_TXN_LINES.BTN_ID = OKS_BILL_TRANSACTIONS.ID.
• OKS_BILL_CONT_LINES — contract line detail; join on OKS_BILL_TXN_LINES.BCL_ID = OKS_BILL_CONT_LINES.ID.
• OKS_BILL_SUB_LINES — contract sub-line detail; join on OKS_BILL_TXN_LINES.BSL_ID = OKS_BILL_SUB_LINES.ID.
• FND_SECURITY_GROUPS — security group reference via SECURITY_GROUP_ID.
• OKS_BILL_TXN_LINES_PK / U1 / U3 — indexes enforcing uniqueness on ID and (BSL_ID, BCL_ID).

The table is populated and read through the Service Contracts billing concurrent programs and the public OKS billing APIs rather than through direct DML, so referencing applications should treat it as a dependent child of the OKS billing transaction hierarchy.