Results for “ar_mc_payment_schedules_u1”

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

Overview

AR.AR_MC_PAYMENT_SCHEDULES is a Multiple Reporting Currencies (MRC) subtable of AR_PAYMENT_SCHEDULES_ALL within the Oracle Receivables (AR) module. It stores currency-related information for all transactions except adjustments and miscellaneous cash receipts, maintained separately for each reporting set of books associated with the parent record in AR_PAYMENT_SCHEDULES_ALL. Oracle Receivables writes to this table whenever a transaction occurs against an invoice, debit memo, chargeback, credit memo, on-account credit, or receipt. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is registered under FND Design Data as AR.AR_MC_PAYMENT_SCHEDULES with a VALID status.

From a Data Vault modeling perspective, the table is best classified heuristically as a satellite: it carries descriptive, currency-conversion attributes (exchange rate type, exchange date, exchange rate, and converted amounts) that qualify a parent business key rather than introducing new relationships. It does not behave as a hub, and while it links to AR_PAYMENT_SCHEDULES_ALL, GL_SETS_OF_BOOKS, and RA_CUSTOMER_TRX_ALL, those references are inherited through the parent rather than being native link semantics.

Key Information Stored

The table is uniquely identified by the composite primary key AR_MC_PAYMENT_SCHEDULES_PK, defined on SET_OF_BOOKS_ID and PAYMENT_SCHEDULE_ID. The same two columns form the unique business-key candidate indexed by AR_MC_PAYMENT_SCHEDULES_U1, the index referenced in the user's search. The most important columns include:

• SET_OF_BOOKS_ID — Part of the surrogate/composite primary key; identifies the reporting set of books for which the MRC row is maintained.
• PAYMENT_SCHEDULE_ID — Part of the composite primary key; foreign key to the parent AR_PAYMENT_SCHEDULES_ALL record.
• CUSTOMER_TRX_ID — Invoice identifier and foreign key to RA_CUSTOMER_TRX_ALL; also indexed non-uniquely via AR_MC_PAYMENT_SCHEDULES_N1.
• EXCHANGE_RATE_TYPE — The conversion type used to translate foreign-currency transactions into reporting currency.
• EXCHANGE_DATE — The date on which the transactional amount was converted to the reporting currency.
• EXCHANGE_RATE — The rate applied during that conversion.
• ACCTD_AMOUNT_DUE_REMAINING — The amount due remaining expressed in the functional (accounted) currency.
• AMOUNT_DUE_REMAINING — The current amount due remaining, stored in the transactional currency.

Common Use Cases and Queries

The predominant use case is MRC reporting: reconciling transactional balances against reporting-currency balances across multiple sets of books, and validating that exchange rate, exchange date, and exchange rate type were captured consistently. A typical report joins the MRC subtable to its parent and to the transaction header:

SELECT m.SET_OF_BOOKS_ID, m.PAYMENT_SCHEDULE_ID, m.CUSTOMER_TRX_ID,
  m.EXCHANGE_RATE_TYPE, m.EXCHANGE_DATE, m.EXCHANGE_RATE,
  m.AMOUNT_DUE_REMAINING, m.ACCTD_AMOUNT_DUE_REMAINING
FROM AR.AR_MC_PAYMENT_SCHEDULES m
WHERE m.SET_OF_BOOKS_ID = :p_sob_id;

Additional patterns include comparing AMOUNT_DUE_REMAINING to the parent AR_PAYMENT_SCHEDULES_ALL value to detect rate-driven variances, retrieving all MRC rows for a given invoice using the CUSTOMER_TRX_ID-driven index AR_MC_PAYMENT_SCHEDULES_N1, and auditing exchange rate information for a specific reporting book during period close.

Related Objects

The following objects are the most significant references and dependencies for this table:

• AR.AR_PAYMENT_SCHEDULES_ALL — The parent table; joined on PAYMENT_SCHEDULE_ID and shares transaction/currency context.
• AR.RA_CUSTOMER_TRX_ALL — Transaction header; joined on CUSTOMER_TRX_ID.
• GL.GL_SETS_OF_BOOKS — Joined on SET_OF_BOOKS_ID to resolve the reporting book name and currency.
• AR.AR_MC_PAYMENT_SCHEDULES_U1 / _N1 — The unique and non-unique indexes supporting primary key and invoice lookups respectively.
• AR.AR_PAYMENT_SCHEDULES — The reporting-set-of-books view layered over the parent and MRC subtable.
• AR Receivables transaction and receipt APIs — Logic within AR that inserts and maintains MRC rows as transactions are processed.