Search Results ar_mc_receivable_apps




Overview
Explore in AI Chat

Overview

The AR_MC_RECEIVABLE_APPS table is a core data object within the Oracle E-Business Suite (EBS) Receivables (AR) module, specifically designed to support the Multi-Currency (MC) and Multi-Organization Accounting (MOAC) features in versions 12.1.1 and 12.2.2. Its primary role is to store detailed transactional records for cash and credit memo applications, replicated for each reporting set of books. This structure is essential for organizations operating with multiple accounting ledgers, as it enables the maintenance of complete application history and financial reporting integrity across each distinct ledger without duplicating the core transactional data in the primary application table (AR_RECEIVABLE_APPLICATIONS_ALL). It acts as a critical junction table linking application details to specific ledgers.

Key Information Stored

The table's structure centers on linking a single receivable application event to one or more sets of books. Its primary key is a composite of RECEIVABLE_APPLICATION_ID and SET_OF_BOOKS_ID, ensuring a unique record per application per ledger. Key foreign key columns establish critical relationships: RECEIVABLE_APPLICATION_ID links to the source transaction in AR_RECEIVABLE_APPLICATIONS_ALL, and SET_OF_BOOKS_ID links to the ledger definition in GL_SETS_OF_BOOKS. Other essential foreign keys include PAYMENT_SCHEDULE_ID (linking to AR_PAYMENT_SCHEDULES_ALL), CASH_RECEIPT_ID (linking to AR_CASH_RECEIPTS_ALL), and POSTING_CONTROL_ID (linking to AR_POSTING_CONTROL for accounting event status). This design stores the ledger-specific context for each application.

Common Use Cases and Queries

This table is fundamental for ledger-specific reporting and reconciliation in multi-ledger environments. A common use case is generating a detailed report of all cash applications for a specific set of books during a period, which is crucial for period-end close and audit trails. Another key scenario is tracing the accounting impact of a single transaction across different reporting ledgers. A typical query pattern involves joining this table to its related transaction tables to fetch a comprehensive view.

Sample SQL Pattern:
SELECT mc.*, apps.apply_date, ps.amount_due_original
FROM ar_mc_receivable_apps mc,
     ar_receivable_applications_all apps,
     ar_payment_schedules_all ps
WHERE mc.receivable_application_id = apps.receivable_application_id
AND mc.payment_schedule_id = ps.payment_schedule_id
AND mc.set_of_books_id = :ledger_id
AND apps.apply_date BETWEEN :start_date AND :end_date;

Related Objects

The AR_MC_RECEIVABLE_APPS table is a central hub with documented foreign key relationships to several core Receivables and General Ledger tables. These relationships are essential for data integrity and constructing accurate joins in queries and reports.

  • AR_RECEIVABLE_APPLICATIONS_ALL: Linked via RECEIVABLE_APPLICATION_ID. This is the source transaction table containing the core application data (amounts, dates, types).
  • GL_SETS_OF_BOOKS: Linked via SET_OF_BOOKS_ID. This provides the ledger definition (name, currency, chart of accounts) for the reporting context.
  • AR_PAYMENT_SCHEDULES_ALL: Linked via PAYMENT_SCHEDULE_ID. This provides details of the invoice or charge being paid or adjusted.
  • AR_CASH_RECEIPTS_ALL: Linked via CASH_RECEIPT_ID. This provides details of the cash receipt involved in the application.
  • AR_POSTING_CONTROL: Linked via POSTING_CONTROL_ID. This indicates the posting status of the related accounting events.
  • AR_CASH_RECEIPT_HISTORY_ALL: Linked via CASH_RECEIPT_HISTORY_ID. This provides remittance and accounting history for the cash receipt.