Search Results acctd_earned_discount_taken




Overview
Explore in AI Chat

Overview

AR_MC_RECEIVABLE_APPS is an Oracle Receivables (AR) transaction table that stores cash and credit memo applications for each reporting set of books. The "MC" prefix denotes a multiple-currency or multi-organization reporting construct, and the table exists to record application activity — the matching of receipts and credit memos against open receivables — in a form partitioned by SET_OF_BOOKS_ID. In Oracle EBS 12.1.1 and 12.2.2, this table sits alongside the primary applications table, AR_RECEIVABLE_APPLICATIONS_ALL, and provides the set-of-books-specific view of how much of a given receivable has been settled by each cash receipt or credit memo.

Under the heuristic Data Vault classification derived from the foreign-key structure, AR_MC_RECEIVABLE_APPS is best modeled as a link table. It connects a receivable application, a payment schedule, a cash receipt, a cash receipt history record, and a posting control record, with the set of books acting as the effective context key. This link classification reflects its role as a resolver of many-to-many relationships among receipts, receivables, and accounting books rather than a standalone descriptive entity.

Key Information Stored

The table is defined with 21 documented columns. Its primary key is AR_MC_RECEIVABLE_APPS_PK, composed of RECEIVABLE_APPLICATION_ID and SET_OF_BOOKS_ID. A unique index, AR_MC_RECEIVABLE_APPS_U1, is defined on the same two columns, making this pair the business-key candidate that guarantees one application record per set of books.

Common Use Cases and Queries

Typical reporting scenarios include reconciling applied amounts by ledger, tracing unapplied or on-account cash, and auditing discount activity. A common query pattern aggregates applications per set of books:

  • SELECT SET_OF_BOOKS_ID, SUM(AMOUNT_APPLIED) FROM AR_MC_RECEIVABLE_APPS GROUP BY SET_OF_BOOKS_ID;
  • Joining to AR_CASH_RECEIPTS_ALL on CASH_RECEIPT_ID to report receipt-to-invoice matching.
  • Joining to AR_PAYMENT_SCHEDULES_ALL on PAYMENT_SCHEDULE_ID to determine remaining balances on installments.
  • Filtering on REVERSAL_CREATED or ADJUSTMENT_CREATED for audit and exception reports.
  • Reconciling GL_POSTED_DATE against posting control records to identify unposted applications.

Related Objects

  • AR_RECEIVABLE_APPLICATIONS_ALL — Parent transaction table; joined on RECEIVABLE_APPLICATION_ID.
  • GL_SETS_OF_BOOKS — Ledger definition; joined on SET_OF_BOOKS_ID.
  • AR_PAYMENT_SCHEDULES_ALL — Installment records; joined on PAYMENT_SCHEDULE_ID.
  • AR_CASH_RECEIPTS_ALL — Receipt headers; joined on CASH_RECEIPT_ID.
  • AR_CASH_RECEIPT_HISTORY_ALL — Receipt history; joined on CASH_RECEIPT_HISTORY_ID.
  • AR_POSTING_CONTROL — Posting rules; joined on POSTING_CONTROL_ID.