Results for “icr_id”

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

Overview

The OKL_EXT_CSH_RCPTS_ALL_B table is a core staging and interface table within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. It stores cash receipts received from customers that are destined for the Receivables lockbox interface. In practical terms, this table acts as an inbound staging area: external or internal processes populate it with customer receipt data, which is subsequently transmitted to Oracle Receivables via the lockbox interface for application against open transactions. The table resides in the OKL schema and is marked as VALID in both the 12.1.1 and 12.2.2 releases.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is a link table. This suggestion reflects the fact that OKL_EXT_CSH_RCPTS_ALL_B primarily captures relationships and transactional events — receipts flowing between customers, banks, and Receivables — rather than serving as a stable business entity hub or a descriptive satellite. Its structure, which emphasizes event attributes alongside foreign key references to upstream and downstream entities, is consistent with a link construct.

Key Information Stored

The table contains 52 documented columns. The most significant are summarized below:

• ID — The surrogate primary key, enforced by OKL_EXT_CSH_RCPTS_ALL_B_PK and backed by the unique index OKL_EXT_CSH_RCPTS_ALL_B_U1. This is the sole documented business-key candidate.
• ICR_ID — Foreign key referencing AR_CASH_RECEIPTS_ALL, linking the staged receipt to the Receivables cash receipt once interface processing completes.
• RCT_ID — A receipt identifier used for linking within the OKL receipt framework.
• XCB_ID — An additional reference column supporting the OKL receipt processing context.
• REMITTANCE_AMOUNT — The monetary value of the customer remittance.
• CURRENCY_CODE and EXCHANGE_RATE — Currency and conversion data required for multi-currency receipt processing.
• RECEIPT_DATE, GL_DATE, and EXCHANGE_RATE_DATE — Accounting and transaction dates governing period and rate determination.
• RECEIPT_METHOD and RECEIPT_TYPE — Classify how the receipt was tendered.
• CHECK_NUMBER — Instrument identifier for check-based receipts.
• CUSTOMER_NUMBER and BILL_TO_LOCATION — Identify the paying customer and the relevant billing location.
• ITEM_NUMBER — Reference to the item or contract associated with the receipt.
• ORG_ID — Operating unit context, essential for multi-org security.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE — Standard concurrent program audit columns.
• FULLY_APPLIED_FLAG and EXPIRED_FLAG — Status indicators reflecting receipt application and expiration.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard EBS descriptive flexfield columns.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER complete the audit and concurrency framework.

Common Use Cases and Queries

Typical usage centers on reconciling staged receipts against their final Receivables counterparts and reporting on unprocessed or failed interface records.

• Identifying receipts not yet interfaced to Receivables:
  SELECT id, remittance_amount, customer_number FROM okl.okl_ext_csh_rcpts_all_b WHERE icr_id IS NULL;
• Reconciling staged receipts to applied cash receipts via ICR_ID.
• Auditing a specific concurrent program run using REQUEST_ID.
• Reporting on receipts by operating unit through ORG_ID, or by currency and method.

Related Objects

The most significant related objects, based on the documented foreign key relationships, are:

• AR_CASH_RECEIPTS_ALL — Referenced by ICR_ID; the authoritative Receivables cash receipt table.
• OKL_EXT_CSH_RCPTS_ALL_B self-referencing relationship via RCT_ID, used for internal linkage.
• Receivables lockbox interface tables, which consume staged rows.
• Concurrent program and request objects referenced by REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID.
• Operating unit (ORG) and FND flexfield definition objects supporting ORG_ID and the attribute columns.