Results for “ar_receivable_applications_all”

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

Overview

AR_RECEIVABLE_APPLICATIONS_ALL is the core Receivables table that stores the accounting information for cash and credit memo applications within Oracle E-Business Suite 12.1.1 and 12.2.2. Every time a receipt, credit memo, on-account credit, or adjustment is applied against a customer transaction or an open payment schedule, a corresponding row is written to this table. As such, it acts as the transactional bridge that links incoming cash (AR_CASH_RECEIPTS_ALL) to the receivable it settles (RA_CUSTOMER_TRX_ALL), carrying the amounts, dates, discount amounts, and general ledger account references required for subledger accounting and posting to the general ledger.

From a dimensional modeling perspective, the mined foreign-key structure suggests this table is satellite-leaning in nature. It behaves as a transactional fact table representing an application event, with its surrogate primary key rooted in AR_RECEIVABLE_APPLICATIONS_PK (RECEIVABLE_APPLICATION_ID). Because the table fans out to multiple descriptive dimension tables, it should be treated as a central transactional entity that derives its meaning through its relationships.

Key Information Stored

The table contains 136 documented columns. The most operationally significant are the following:

• RECEIVABLE_APPLICATION_ID — the surrogate primary key, unique per application event and enforced by AR_RECEIVABLE_APPLICATIONS_PK and the unique index AR_RECEIVABLE_APPLICATIONS_U1.
• AMOUNT_APPLIED and AMOUNT_APPLIED_FROM — the amount applied against the target transaction and the source amount drawn (for example, the receipt amount).
• APPLICATION_TYPE and STATUS — classify the nature of the application (cash, credit memo, on-account, adjustment) and its workflow state (for example, applied, unapplied, unidentified).
• CASH_RECEIPT_ID — links the application to the source receipt.
• CUSTOMER_TRX_ID and APPLIED_CUSTOMER_TRX_ID — identify the transaction being applied and the transaction receiving the application.
• PAYMENT_SCHEDULE_ID and APPLIED_PAYMENT_SCHEDULE_ID — tie the application to the open balances on the payment schedules.
• GL_DATE, GL_POSTED_DATE, and REVERSAL_GL_DATE — drive the accounting date of the application and its subsequent reversal.
• CODE_COMBINATION_ID, SET_OF_BOOKS_ID, EARNED_DISCOUNT_CCID, and UNEARNED_DISCOUNT_CCID — provide the general ledger account context for accounting.
• EARNED_DISCOUNT_TAKEN, UNEARNED_DISCOUNT_TAKEN, LINE_APPLIED, TAX_APPLIED, FREIGHT_APPLIED, and RECEIVABLES_CHARGES_APPLIED — decompose the application across receipt discount and transaction line components.
• ACCTD_AMOUNT_APPLIED_FROM, ACCTD_AMOUNT_APPLIED_TO, and ACCTD_EARNED_DISCOUNT_TAKEN — hold the accounted amounts translated to the ledger currency.
• ORG_ID — supports multi-org security and partitioning of application data.
• APPLIED_REC_APP_ID and CHARGEBACK_CUSTOMER_TRX_ID — capture chargeback and re-application relationships.
• CONFIRMED_FLAG, POSTABLE, and POSTING_CONTROL_ID — govern whether and when the application is eligible for posting.

Common Use Cases and Queries

This table is central to cash application reporting, reconciliation, unapplied and on-account analysis, and discount tracking. A typical query joins it to receipts and transactions to report how much cash settled which invoice:

• Retrieving applications for a given receipt: SELECT * FROM ar_receivable_applications_all WHERE cash_receipt_id = :p_receipt_id;
• Listing all applications against a transaction: SELECT * FROM ar_receivable_applications_all WHERE applied_customer_trx_id = :p_trx_id;
• Analyzing applications by ledger and GL period using SET_OF_BOOKS_ID and GL_DATE.
• Reconciling subledger accounting entries through AR_DISTRIBUTIONS_ALL, which references this table via SOURCE_ID.
• Reporting earned and unearned discounts taken across a date range.
• Identifying chargebacks by querying rows where CHARGEBACK_CUSTOMER_TRX_ID is populated.
• Confirming postability with POSTABLE, POSTING_CONTROL_ID, and CONFIRMED_FLAG before GL transfer.

Because the table is partitioned by ORG_ID in multi-org deployments, reporting queries should filter on ORG_ID to satisfy security and performance expectations.

Related Objects

AR_RECEIVABLE_APPLICATIONS_ALL participates in a dense web of relationships. The most significant associated objects include:

• AR_CASH_RECEIPTS_ALL — joined via CASH_RECEIPT_ID; the source receipt.
• RA_CUSTOMER_TRX_ALL — joined via CUSTOMER_TRX_ID and APPLIED_CUSTOMER_TRX_ID; the transactions involved in the application.
• AR_PAYMENT_SCHEDULES_ALL — joined via PAYMENT_SCHEDULE_ID and APPLIED_PAYMENT_SCHEDULE_ID; maintains open balance state and references CASH_APPLIED_ID_LAST back to this table.
• AR_DISTRIBUTIONS_ALL — references this table via SOURCE_ID and holds the accounting distributions generated for each application.
• AR_ADJUSTMENTS_ALL — references this table via ASSOCIATED_APPLICATION_ID for adjustment-related applications.
• AR_CASH_BASIS_DISTS_ALL — references RECEIVABLE_APPLICATION_ID and RECEIVABLE_APPLICATION_ID_CASH for cash-basis accounting.
• AR_TRANSACTION_HISTORY_ALL — joined via LINK_TO_TRX_HIST_ID to trace the lifecycle of the application.
• AR_CASH_RECEIPT_HISTORY_ALL — joined via CASH_RECEIPT_HISTORY_ID for receipt activity history.
• GL_CODE_COMBINATIONS and GL_SETS_OF_BOOKS_11I — provide ledger and account context.
• AR_RECEIVABLES_TRX_ALL and AR_APP_RULE_SETS — joined via RECEIVABLES_TRX_ID and RULE_SET_ID to control application rules.