Results for “format_currency_code”

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

Overview

AR_RECEIPTS_REP_ITF is a Receivables (AR) report exchange interface table that serves as the staging and output repository for the Receivables Receipts reports. Owned by the AR schema under Oracle E-Business Suite 12.1.1 and 12.2.2, the table is documented as VALID and contains 89 columns. Rather than storing live transaction data, it holds a denormalized, report-ready projection of receipt, application, bank, customer, and accounting information generated during report execution. Each row is tied to a concurrent request through REQUEST_ID, allowing the report exchange mechanism to materialize rows that downstream report templates and external formatting tools can consume.

Under the heuristic Data Vault classification derived from the documented foreign key structure, AR_RECEIPTS_REP_ITF is best modeled as a link table. It captures associations among receipts, batches, and customers rather than functioning as a standalone hub of a single business concept, and it is populated as a transient interface rather than serving as a system of record.

Key Information Stored

The table blends identifiers, descriptive attributes, monetary amounts, and accounting flexfield details. The following columns are the most significant for reporting and integration:

• REQUEST_ID — associates each interface row with the concurrent request that generated it, and is also the primary access path when purging or re-reading output.
• CASH_RECEIPT_ID / RECEIPT_NUMBER — the surrogate identifier of the underlying cash receipt and its user-facing document number.
• RECEIPT_AMOUNT / ACCTD_RECEIPT_AMOUNT — the entered and accounted receipt values, expressed in RECEIPT_CURRENCY_CODE and the functional currency respectively.
• BATCH_ID / BATCH_NAME / BATCH_SOURCE — the remittance batch to which the receipt belongs; BATCH_ID carries the documented foreign key to RA_BATCHES_ALL.
• CUSTOMER_ID / CUSTOMER_NAME / CUSTOMER_NUMBER — the customer identity, where CUSTOMER_ID carries the documented foreign key to HZ_CUST_ACCOUNTS.
• RECEIVABLE_APPLICATION_ID / APPLIED_CUSTOMER_TRX_ID / TRX_NUMBER — the application and its target transaction, enabling receipt-to-invoice reporting.
• AMOUNT_APPLIED_TO / AMOUNT_APPLIED_FROM — the applied amounts in entered currency, with accounted equivalents in ACCTD_AMOUNT_APPLIED_TO and ACCTD_AMOUNT_APPLIED_FROM.
• RECEIPT_DATE / GL_DATE / DEPOSIT_DATE / APPLY_DATE — the principal date dimensions used for aging, cash forecasting, and GL reconciliation.
• RECEIPT_METHOD / RECEIPT_STATUS / RECEIPT_TYPE — classification attributes for receipt mode and lifecycle state.
• ACCOUNT_CODE_COMBINATION_ID / DEBIT_ACCOUNT / ACCOUNTING_FLEXFIELD — the accounting distribution and flexfield representation.
• UNAPP_AMOUNT / ON_ACCOUNT_AMOUNT / CLAIM_AMOUNT / PREPAY_AMOUNT / TOTAL_UNRESOLVED_AMOUNT — the unresolved and unapplied balances central to cash-in-transit reporting.

The physical schema documents no standalone surrogate primary key; the table functions as an interface projection keyed in practice by REQUEST_ID and the receipt/application identifiers. Business-key candidates visible in the column set include RECEIPT_NUMBER, BATCH_NAME, and TRX_NUMBER, though uniqueness is scoped by request and application context.

Common Use Cases and Queries

Principal use cases include reproducing the standard Receipts Register, Unapplied and Unidentified Receipts, and Applied Receipts reports; extracting receipt data into external reporting or reconciliation tools; and validating report output against base AR tables. A typical access pattern filters by the generating request:

SELECT RECEIPT_NUMBER, RECEIPT_DATE, CUSTOMER_NAME,
       RECEIPT_AMOUNT, UNAPP_AMOUNT, RECEIPT_STATUS
FROM   AR.AR_RECEIPTS_REP_ITF
WHERE  REQUEST_ID = :request_id
ORDER  BY RECEIPT_DATE, RECEIPT_NUMBER;

Batch-level analysis joins the interface to RA_BATCHES_ALL on BATCH_ID, while customer-level rollups join HZ_CUST_ACCOUNTS on CUSTOMER_ID. Application-level queries group by TRX_NUMBER to reconcile applied amounts against ACCTD_AMOUNT_APPLIED_TO. Because rows are populated per request, standard practice is to select by REQUEST_ID and delete stale rows once downstream processing completes.

Related Objects

• RA_BATCHES_ALL — joined via AR_RECEIPTS_REP_ITF.BATCH_ID to RA_BATCHES_ALL.BATCH_ID, supplying batch source and control totals.
• HZ_CUST_ACCOUNTS — joined via AR_RECEIPTS_REP_ITF.CUSTOMER_ID to HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID, resolving customer identity.
• AR_CASH_RECEIPTS_ALL — base receipt entity underlying CASH_RECEIPT_ID and RECEIPT_NUMBER.
• AR_CASH_RECEIPT_HISTORY_ALL — source of CASH_RECEIPT_HISTORY_ID and RECEIPT_HISTORY_STATUS.
• AR_RECEIVABLE_APPLICATIONS_ALL — base application records mirrored by RECEIVABLE_APPLICATION_ID and APPLICATION_STATUS.
• AR_PAYMENT_SCHEDULES_ALL — transaction schedule data behind APPLIED_CUSTOMER_TRX_ID and TRX_NUMBER.
• RA_CUSTOMER_TRX_ALL — invoice header referenced through APPLIED_CUSTOMER_TRX_ID.
• FND_CONCURRENT_REQUESTS — joined via REQUEST_ID to identify report executions and output ownership.