Search Results ar_pmts_interface_lines_n1

Overview

AR.AR_PMTS_INTERFACE_LINES_GT is a global temporary table in the Oracle Receivables (AR) schema that serves as a transient staging structure for Automatic Receipts payment interface processing in Oracle E-Business Suite 12.1.1 and 12.2.2. It holds the payment line detail generated during the receipt creation and remittance workflow, before or during the load into the persistent payments interface tables. Because it is a global temporary table defined with SYS$TRANSACTION duration, each session sees only the rows it inserted, and those rows are purged at transaction commit or rollback, making the object safe for concurrent, multi-session receipt processing.

Modeled through a heuristic Data Vault lens, this object is best classified as a link: it associates a transmission request to an interface record and a customer transaction, driven by foreign keys to AR_TRANSMISSIONS_ALL and AR_PAYMENTS_INTERFACE_ALL. The applied amounts behave like satellite-style attributes riding along that linkage, though the table itself is a functional staging object rather than a formal warehouse construct.

Key Information Stored

The table contains 12 columns. The most significant for functional and diagnostic purposes are:

• TRANSMISSION_REQUEST_ID – reference to AR_TRANSMISSIONS_ALL; identifies the remittance or transmission batch.
• TRANSMISSION_RECORD_ID – reference to AR_PAYMENTS_INTERFACE_ALL; the interface record being staged.
• INVOICE_NUMBER – the transaction or invoice number against which the payment line is applied.
• APPLY_TO – the application target (e.g., invoice, credit memo) for the receipt.
• LINE_AMT_REMAINING – remaining line amount available for application.
• FREIGHT_REMAINING – the remaining freight amount on the transaction line; central to freight distribution during receipt application.
• CHARGES_REMAINING – remaining charges (e.g., handling) amount.
• TAX_REMAINING – remaining tax amount.
• CUSTOMER_TRX_ID – surrogate identifier of the customer transaction; key component of the N1 index.
• CURRENCY_CODE, INVOICE_CURRENCY_CODE – transaction and invoice currencies, with TRANS_TO_RECEIPT_RATE providing conversion between them.

The documented non-unique index AR_PMTS_INTERFACE_LINES_N1 covers (CUSTOMER_TRX_ID, APPLY_TO). No documented unique index or surrogate primary key exists; CUSTOMER_TRX_ID and APPLY_TO together function as the principal business-key candidates within this object.

Common Use Cases and Queries

A frequent reason this table is queried is to inspect remaining balances on a receipt line — particularly FREIGHT_REMAINING — when freight, charges, or tax are not applying as expected. Analysts commonly join back to customer transactions to correlate remaining amounts with invoice headers:

• Reconciling receipt application failures due to residual freight or tax balances.
• Diagnosing Automatic Receipts batch discrepancies by TRANSMISSION_REQUEST_ID.
• Reporting on currency and exchange-rate translation (TRANS_TO_RECEIPT_RATE, INVOICE_CURRENCY_CODE).

A representative query pattern:

SELECT TRANSMISSION_REQUEST_ID, INVOICE_NUMBER, LINE_AMT_REMAINING, FREIGHT_REMAINING, CHARGES_REMAINING, TAX_REMAINING FROM AR.AR_PMTS_INTERFACE_LINES_GT WHERE CUSTOMER_TRX_ID = :trx_id;

Because data is session-scoped and transaction-duration, queries must run in the same session that populated the table; it is not a suitable target for scheduled standalone reports.

Related Objects

The following parent and companion objects are most significant:

• AR.AR_PAYMENTS_INTERFACE_ALL – referenced through TRANSMISSION_RECORD_ID; the persistent interface record for payments.
• AR.AR_TRANSMISSIONS_ALL – referenced through TRANSMISSION_REQUEST_ID; the remittance transmission header.
• AR.AR_CUSTOMER_TRX_ALL – related through CUSTOMER_TRX_ID; source of invoice, freight, tax, and charge amounts.
• AR.AR_PMTS_INTERFACE_LINES_GT – referenced as APPS.AR_PMTS_INTERFACE_LINES_GT in dependency listings.
• Automatic Receipts APIs (AR_RECEIPT_API_PUB) – the programmatic layer that populates and consumes this staging object during receipt creation.

Together these objects form the Automatic Receipts and remittance pipeline in Oracle Receivables, with this temporary table acting as the session-local workbench for line-level amounts including FREIGHT_REMAINING.