Results for “remittance_bank_name”

46 results




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

Overview

OKL_EXT_CSH_RCPTS_V is a VALID Oracle E-Business Suite view owned by the APPS schema and belonging to the OKL (Leasing and Finance Management) product family. It exposes external cash receipts that have been received from a customer and are destined for the Receivables lockbox interface. In practice, the view serves as a staging read model over the OKL external cash receipt entities, allowing receipts captured or imported within Oracle Leasing and Finance Management to be inspected, validated, and subsequently pushed into Oracle Receivables. Because it flattens the header and translation information into a single relational projection, it is well suited for reporting, diagnostic queries, and integration extracts that must present customer remittance data in a format compatible with the Receivables lockbox processing conventions.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

  • OKL_EXT_CSH_RCPTS_B (SYNONYM) — the base table that stores the receipt-level attributes of each external cash receipt, including remittance amount, receipt date and method, customer and bank information, exchange rate details, descriptive flexfield attributes, and standard WHO/audit columns.
  • OKL_EXT_CSH_RCPTS_TL (SYNONYM) — the translation table, which supplies language-dependent descriptive content such as COMMENTS.

The view joins these two objects, with the _B table supplying the bulk of the columns and the _TL table contributing the translation-dependent comment text and the SFWT_FLAG. Because both bases are referenced through synonyms in APPS, the view remains independent of the physical table owner and is available to any APPS-connected session with the appropriate privileges.

Key Columns

The view projects a broad set of columns that mirror the Receivables lockbox interface requirements. The most significant include:

Common Use Cases and Queries

Typical scenarios include reconciling external receipts before lockbox submission, investigating remittance failures, and building extracts for Receivables. The BILL_TO_LOCATION column is frequently used to trace a remittance to a specific customer site.

  • Listing pending receipts by bill-to location:
    SELECT id, customer_number, bill_to_location,
           remittance_amount, currency_code, receipt_date
    FROM   apps.okl_ext_csh_rcpts_v
    WHERE  bill_to_location = :p_location
    ORDER  BY receipt_date DESC;
  • Identifying unapplied or expired receipts:
    SELECT id, customer_number, remittance_amount,
           fully_applied_flag, expired_flag
    FROM   apps.okl_ext_csh_rcpts_v
    WHERE  NVL(fully_applied_flag,'N') = 'N'
       OR  NVL(expired_flag,'N') = 'Y';
  • Reviewing foreign-currency remittances:
    SELECT id, currency_code, exchange_rate_type,
           exchange_rate, exchange_rate_date, gl_date
    FROM   apps.okl_ext_csh_rcpts_v
    WHERE  currency_code <> functional_currency;

Each query should restrict on ORG_ID where multi-organization security applies, and access requires the OKL responsibility or equivalent APPS privileges.