Results for “cc_error_flag”

40 results




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

Overview

AR_CASH_RECEIPTS_ALL is the core Receivables table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores detailed, transactional information about every cash receipt processed within the AR module. Each row represents a single receipt—manual, automatic, miscellaneous, or refund-related—capturing its amount, currency, status, remittance details, reversal information, and the banking or customer references associated with it. The table is the authoritative source for receipt data that drives customer balance updates, payment schedule applications, accounting entries, and remittance batch processing. It resides in the AR schema and is documented with 124 columns, reflecting the breadth of financial, geographic, and integration attributes EBS attaches to receipts.

From a modeling perspective, the metadata’s heuristic Data Vault classification identifies this object as hub-leaning. AR_CASH_RECEIPTS_ALL functions as the central receipt hub, keyed on CASH_RECEIPT_ID, with surrounding descriptive and reference tables acting as satellites and links. This classification is offered as a design suggestion: the table’s stable, unique business identity and its role as the parent of numerous dependent objects make it a natural hub candidate in an analytical or integration model.

Key Information Stored

The table’s primary key is defined by AR_CASH_RECEIPTS_PK on CASH_RECEIPT_ID, the surrogate identifier that uniquely distinguishes each receipt. A second unique index, AR_CASH_RECEIPT_UK1, is defined on PAY_FROM_CUSTOMER, RECEIPT_NUMBER, and AMOUNT, representing a business-key candidate useful for deduplication and external matching.

Among the 124 columns, the most operationally significant include:

Common Use Cases and Queries

Typical reporting scenarios include receipt-level cash application analysis, unapplied and unidentified receipt tracking, bank reconciliation extracts, and remittance batch audits. A common query retrieves receipts by customer and status:

  • SELECT cash_receipt_id, receipt_number, amount, status FROM ar_cash_receipts_all WHERE pay_from_customer = :customer_id AND receipt_date BETWEEN :from_date AND :to_date;
  • Joining to AR_RECEIVABLE_APPLICATIONS_ALL on CASH_RECEIPT_ID reveals which invoices a receipt has been applied against.
  • Joining to FV_REFUNDS_VOIDS_ALL on CASH_RECEIPT_ID supports refund and void analysis, tying directly to the user’s search term.
  • Aggregating by CURRENCY_CODE and SET_OF_BOOKS_ID produces daily cash position reports.

Related Objects

The table participates in an extensive relationship network. Significant referencing objects include AR_RECEIVABLE_APPLICATIONS_ALL and AR_ADJUSTMENTS_ALL (application and adjustment linkage via CASH_RECEIPT_ID and ASSOCIATED_CASH_RECEIPT_ID), AR_PAYMENT_SCHEDULES_ALL (which references multiple cash receipt columns), AR_CASH_RECEIPT_HISTORY_ALL, AR_MISC_CASH_DISTRIBUTIONS_ALL, and the multi-currency AR_MC_CASH_RECEIPTS family. FLexFields-related tables FV_REFUNDS_VOIDS_ALL and FV_INTERAGENCY_FUNDS_ALL both join on CASH_RECEIPT_ID, as do the India localization tables JAI_CMN_DOCUMENT_TAXES and JAI_RGM_REFS_ALL. Parent lookups flow outward to AP_BANK_ACCOUNTS_ALL, IBY_EXT_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, HZ_CUST_ACCOUNTS, GL_SETS_OF_BOOKS_11I, and FV_LEGAL_ENTITIES.