Results for “amount_applied”

50+ results




Overview
Explore in AI Chat

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

Overview

The AR_AR_PMTS_INTERFACE_HEADER_GT table (commonly referenced as AR_PMTS_INTERFACE_HEADER_GT) is an Oracle Receivables interface table that resides in the AR schema. It serves as a staging and processing structure for manipulating payment application data prior to, or as an alternative to, the standard AR_PAYMENTS_INTERFACE_ALL inbound interface. The "_GT" suffix indicates a global temporary table, meaning its rows are session-scoped and typically purged automatically at transaction commit or session termination, making it well suited for high-volume batch processing without persistent storage overhead.

In the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this table is commonly used by AutoInvoice and receipt application programs, particularly when reconciling cash receipts against open transactions. Its structure supports the transmission framework via the AR_TRANSMISSIONS_ALL table, which tracks outbound and inbound communications such as those from bank lockbox transmissions.

Based on the heuristic Data Vault classification mined from its foreign-key structure, the table is described as a standalone entity. In Data Vault modeling terms, this suggests it behaves as a staging or link-like structure rather than a deeply normalized hub-and-satellite hierarchy, carrying transactional attributes directly for a short-lived processing window.

Key Information Stored

The table contains 13 documented columns. The most significant, grouped by function, are:

  • TRANSMISSION_REQUEST_ID and TRANSMISSION_RECORD_ID — Foreign keys linking each staged row to AR_TRANSMISSIONS_ALL and AR_PAYMENTS_INTERFACE_ALL respectively. These establish the lineage between the staging record and the underlying payment interface and transmission batch.
  • INVOICE_NUMBER — The business identifier of the invoice or transaction being applied against, used to resolve the target CUSTOMER_TRX_ID.
  • CUSTOMER_TRX_ID — The surrogate identifier of the customer transaction once resolved by AutoInvoice or receipt application.
  • AMOUNT_APPLIED and AMOUNT_APPLIED_FROM — The monetary value of the application, with the "_FROM" variant denoting the source-currency or original amount before conversion.
  • TRANS_TO_RECEIPT_RATE — The exchange rate used to convert between the transaction currency and the receipt currency.
  • CURRENCY_CODE and INVOICE_CURRENCY_CODE — The receipt currency and invoice currency respectively, ensuring cross-currency applications are validated.
  • PRECISION, INV_PRECISION, and DEFAULT_BY — Precision and rounding-control attributes governing how amounts are extended or defaulted.
  • RECORD_STATUS — A processing flag indicating whether the staged row is pending, validated, or in error.

The surrogate identity for each row is the composite of its transmission identifiers, while INVOICE_NUMBER combined with the transmission context functions as the business key candidate.

Common Use Cases and Queries

This table is used primarily during receipt application batch runs, particularly for lockbox and electronic payment processing. A typical reconciliation query joins staged records to the payment interface to detect unprocessed applications:

  • Identifying rows in error by querying on RECORD_STATUS to isolate failed applications.
  • Reconciling applied amounts by aggregating AMOUNT_APPLIED grouped by TRANSMISSION_REQUEST_ID.
  • Auditing currency conversion by comparing AMOUNT_APPLIED_FROM against AMOUNT_APPLIED and validating TRANS_TO_RECEIPT_RATE.
  • Joining to AR_TRANSMISSIONS_ALL via TRANSMISSION_REQUEST_ID to trace the originating lockbox batch.

Because it is a global temporary table, queries should be scoped to the active session; historical trending requires extracting data to a persistent staging table before commit.

Related Objects

  • AR_PAYMENTS_INTERFACE_ALL — Referenced via TRANSMISSION_RECORD_ID; the persistent interface that ultimately consumes staged payment data.
  • AR_TRANSMISSIONS_ALL — Referenced via TRANSMISSION_REQUEST_ID; tracks the transmission request driving the batch.
  • AR_CASH_RECEIPTS_ALL — The target receipt table populated after successful application.
  • RA_CUSTOMER_TRX_ALL — Resolved through CUSTOMER_TRX_ID for the invoice being applied.
  • AR_RECEIPT_METHODS — Validates the payment method used for the application.
  • AutoInvoice (RAXTRX) concurrent program — Consumes interface rows during import.