Results for “rct_id_details”

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

Overview

OKL_TXL_RCPT_APPS_ALL_B is a transaction-level table in the Oracle E-Business Suite Leasing and Finance Management (OKL) module, delivered and validated in releases 12.1.1 and 12.2.2. Its documented purpose is to apply cash to various OKL objects, meaning it records the allocation of receipt transactions against leases, contracts, consolidated receivables, and other financial instruments managed by the leasing application. The table serves as the central bridge between incoming cash receipts and the underlying receivable or contract structures they settle.

From a Data Vault modeling perspective, the FK structure suggests this object behaves as a link table. It connects multiple independent business entities — contracts, headers, consolidated AR lines and streams, and receipt details — through surrogate foreign keys, capturing the associative relationship that arises when a receipt is applied to an OKL object. This link classification is a heuristic observation derived from the foreign key topology, not a documented architectural directive.

Key Information Stored

The table contains 38 documented columns. The most operationally significant are:

• ID — the surrogate primary key, enforced by OKL_TXL_RCPT_APPS_ALL_B_PK and also indexed uniquely via OKL_TXL_RCPT_APPS_ALL_B_U1. This is the technical identifier for each application record.
• RCT_ID_DETAILS — foreign key tying the application back to the receipt detail. This is the principal business join to the cash receipt side of the transaction.
• CNR_ID, KHR_ID, LLN_ID, LSM_ID — foreign keys to the contract, header, consolidated AR line, and consolidated AR stream objects that the cash is applied against.
• ILE_ID — identifier linking to the related lease or instrument element, where applicable.
• AR_INVOICE_ID — reference to the associated Oracle Receivables invoice.
• STY_ID — identifier relating to the leasing stream type or supporting stream definition.
• AMOUNT — the monetary value of the cash applied in this record. This is the primary quantitative field for reporting and reconciliation.
• LINE_NUMBER — ordering or sequencing attribute for multi-line applications.
• ORG_ID — the operating unit, enabling multi-org security and filtering in R12.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program and process audit fields indicating which batch job created or last updated the record.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OKL framework to manage concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) segment columns for customer-specific data capture.

Common Use Cases and Queries

Typical scenarios centre on cash application reconciliation, receipt-to-contract traceability, and aging or allocation reporting. A common pattern is to join the application table to the receipt details and to the contract headers to produce a receipt-application register for a given period:

• Receipt application audit: query by RCT_ID_DETAILS to list all OKL objects to which a single receipt was applied, replicating the allocation view seen in the Cash Application workbench.
• Contract-level cash collection: sum AMOUNT grouped by KHR_ID or CNR_ID to measure total cash applied per contract or consolidated AR line.
• Period and batch reporting: filter on CREATION_DATE / LAST_UPDATE_DATE and REQUEST_ID to reconcile the output of a specific Cash Application concurrent program run.
• Multi-org reporting: apply ORG_ID predicates to satisfy operating-unit security in R12.
• Reconciliation to Receivables: join AR_INVOICE_ID to the AR invoice tables to verify that OKL-applied cash agrees with the Receivables subledger.

Related Objects

• OKL_K_HEADERS — referenced via KHR_ID; the contract or agreement header that the applied cash relates to.
• OKL_CNSLD_AR_LINES_B — referenced via LLN_ID; consolidated AR line receiving the cash application.
• OKL_CNSLD_AR_STRMS_B — referenced via LSM_ID; the consolidated AR stream definition.
• Receipt details (RCT_ID_DETAILS) — the receipt-side object resolved through the RCT_ID_DETAILS FK; the originating cash receipt line.
• OKL_TXL_RCPT_APPS_ALL_TL / associated views — generally the transactional views and PL/SQL APIs in the OKL Transactional (TXL) family that read and write this table during cash application processing.
• Oracle Receivables invoice tables — joined indirectly via AR_INVOICE_ID for subledger reconciliation.

Note that this object is not exposed as a public API interface; it is accessed primarily through OKL transactional APIs and concurrent cash-application programs. Direct DML should be avoided in favour of supported API calls.