Results for “okl_xtl_csh_apps_b”

50+ results




Overview
Explore in AI Chat

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

Overview

The table OKL_XTL_CSH_APPS_B is a transactional data object within the Oracle E-Business Suite (EBS) module OKL — Leasing and Finance Management. Its documented description states that it represents a "receipt application specifying amount applied to Receivables invoices." In practical terms, this table stores the linkage between cash receipts captured in the leasing subsystem and the specific Receivables invoices against which those receipts are applied, together with the applied amount. It therefore sits at the intersection of cash management, receipt processing, and receivables settlement within the leasing and finance management flow.

Under the heuristic Data Vault classification mined from its foreign key structure, the table is characterized as a link. This modeling suggestion reflects the fact that OKL_XTL_CSH_APPS_B primarily resolves and records relationships between several other business entities — cash allocation rules, consolidated AR streams, receipt application records, and external cash receipts — rather than acting as a standalone hub of a single business key or a descriptive satellite. The official ETRM metadata indicates that the table is not implemented in the reference database, meaning its presence and population depend on the specific configuration and modules licensed in a given environment.

Key Information Stored

The primary key of the table is defined by the constraint OKL_XTL_CSH_APPS_B_PK, which is enforced on the column ID. This ID is the surrogate primary key and serves as the unique technical identifier for each receipt-application row; it is not itself a business key.

The most significant columns documented in the metadata are the foreign key columns that define the table's relationships:

These columns collectively describe which receipt was applied, the amount applied to invoice balances, and the allocation and stream context in which the application occurred. The metadata does not document a separate unique business-key index beyond the PK, so the business key is effectively composed from the combination of referenced foreign keys.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include tracing applied amounts from external cash receipts through to Receivables invoices, verifying cash allocation rule usage, and auditing consolidated AR streams. A representative query joins the link to its referenced parents:

  • Join OKL_XTL_CSH_APPS_B to OKL_EXT_CSH_RCPTS_B on XCR_ID_DETAILS to retrieve receipt details.
  • Join to OKL_TXL_RCPT_APPS_B on RCA_ID to obtain the receipt application context.
  • Join to OKL_CNSLD_AR_STRMS_B on LSM_ID for consolidated AR stream reporting.
  • Join to OKL_CASH_ALLCTN_RLS on CAT_ID to analyze allocation rule behavior.

A sample SQL pattern follows: SELECT a.ID, a.CAT_ID, a.LSM_ID, a.RCA_ID, a.XCR_ID_DETAILS FROM OKL_XTL_CSH_APPS_B a WHERE a.XCR_ID_DETAILS = :receipt_id;. Such queries support cash application reconciliation, aging analysis, and audit of applied versus unapplied receipts within the leasing module.

Related Objects

The following objects are the most significant references and dependencies based on the documented foreign key relationships:

  • OKL_CASH_ALLCTN_RLS — joined via OKL_XTL_CSH_APPS_B.CAT_ID; defines the cash allocation rule.
  • OKL_CNSLD_AR_STRMS_B — joined via OKL_XTL_CSH_APPS_B.LSM_ID; consolidated AR streams.
  • OKL_TXL_RCPT_APPS_B — joined via OKL_XTL_CSH_APPS_B.RCA_ID; transactional receipt applications.
  • OKL_EXT_CSH_RCPTS_B — joined via OKL_XTL_CSH_APPS_B.XCR_ID_DETAILS; external cash receipt details.

These relationships confirm the table's role as a link that bridges external receipt data, transactional receipt applications, allocation rules, and consolidated receivables streams within Oracle Leasing and Finance Management.