Results for “transmission_request_id”

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

Overview

AR_PMTS_INTERFACE_LINES_GT is a global temporary table (GT suffix) in the Oracle Receivables (AR) schema. It serves as an intermediate staging structure used by the AutoLockbox and Post QuickCash processes to hold the distribution lines of payment interface records prior to application against open transactions in the Receivables sub-ledger. Each row represents a single candidate application line — an amount to be applied against a specific transaction — before the feathered allocation logic, discount handling, and accounting creation in the payments interface are finalized.

The table is transient by design. Rows exist only for the duration of a posting or import session and are scoped to that session; no permanent transactional history is retained. It is populated from payment batch import flows and consumed by the same concurrent program session that created the rows. From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone. That classification is a heuristic suggestion: although the table carries foreign keys to AR_TRANSMISSIONS_ALL and AR_PAYMENTS_INTERFACE_ALL, it functions primarily as a staging satellite referencing an interface transaction rather than a reusable hub or link in the Data Vault sense.

Key Information Stored

The documented physical schema for 12.2.2 exposes 12 columns. The most significant are:

• TRANSMISSION_REQUEST_ID — FK to AR_TRANSMISSIONS_ALL; identifies the transmission request (import run) that produced the line.
• TRANSMISSION_RECORD_ID — FK to AR_PAYMENTS_INTERFACE_ALL; the parent payment interface record this line detail belongs to.
• INVOICE_NUMBER — the customer transaction number in textual form, used to resolve the target transaction.
• CUSTOMER_TRX_ID — the resolved internal identifier of the transaction being applied to.
• APPLY_TO — classification of the application target (e.g., invoice, debit memo, chargeback, on-account).
• CURRENCY_CODE — currency of the payment/interface line.
• INVOICE_CURRENCY_CODE — currency of the target transaction, enabling cross-currency application handling.
• TRANS_TO_RECEIPT_RATE — exchange rate conversions applied when transaction and receipt currencies differ.
• LINE_AMT_REMAINING — the remaining amount available on the line for application.
• FREIGHT_REMAINING, CHARGES_REMAINING, TAX_REMAINING — component-level remaining balances that allow the application program to split amounts across freight, charges, and tax for revenue and accounting accuracy.

No surrogate primary key or unique index is documented; uniqueness is enforced functionally by the combination of TRANSMISSION_REQUEST_ID plus TRANSMISSION_RECORD_ID plus target application attributes within a session. The two foreign key columns form the strongest business-key candidates for lineage tracing back to the transmission and interface record.

Common Use Cases and Queries

Because the table is session-scoped, queries are typically executed inside the originating session or by joining to the persistent interface table. A representative diagnostic pattern identifies interface lines that could not be applied:

• Reconciliation of import versus application — join AR_PMTS_INTERFACE_LINES_GT to AR_PAYMENTS_INTERFACE_ALL on TRANSMISSION_RECORD_ID to compare staged line amounts against the header payment amount.
• Tracing a failed Lockbox run — filter by TRANSMISSION_REQUEST_ID and join to AR_TRANSMISSIONS_ALL to inspect the parent transmission status.
• Identifying unresolved transactions — where CUSTOMER_TRX_ID is null despite a populated INVOICE_NUMBER, the target transaction could not be matched.
• Component-level exposure analysis — aggregate FREIGHT_REMAINING, CHARGES_REMAINING, and TAX_REMAINING to report unapplied components.

Typical SQL: SELECT g.TRANSMISSION_RECORD_ID, g.INVOICE_NUMBER, g.CUSTOMER_TRX_ID, g.LINE_AMT_REMAINING FROM AR.AR_PMTS_INTERFACE_LINES_GT g WHERE g.TRANSMISSION_REQUEST_ID = :req_id;

Related Objects

• AR_PAYMENTS_INTERFACE_ALL — parent interface record; joined via TRANSMISSION_RECORD_ID.
• AR_TRANSMISSIONS_ALL — transmission request header; joined via TRANSMISSION_REQUEST_ID.
• AR_PAYMENTS_INTERFACE — view exposing interface records to concurrent programs.
• AR_RECEIVABLE_APPLICATIONS_ALL — final application records created once staging lines are successfully applied.
• RA_CUSTOMER_TRX_ALL — transaction header resolved via CUSTOMER_TRX_ID.
• AR_CASH_RECEIPTS_ALL — receipt created from a fully applied interface line.