Search Results cpg_ship_to_location_number

Overview

AR_TA_PAYMENTS_INTERFACE_REM_V is a Receivables (AR) view that exposes a filtered, single-record-type slice of the Oracle EBS Automatic Receipts payment interface. Its name indicates a "Payments Interface" view scoped for remittance ("REM") transmission processing. The view is defined with a hard-coded predicate of RECORD_TYPE = 6 against AR_PAYMENTS_INTERFACE_ALL, and it is entity-org (operating unit) secured through the USERENV('CLIENT_INFO') mechanism that resolves to ORG_ID. The ETRM metadata notes that the view is "Not implemented in this database," meaning the object may exist in the data dictionary of the E-Business Suite release but is not formally instantiated or populated in the environment documented. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a reporting and diagnostic surface for payment records that carry transmission/remittance identifiers, allowing Receivables and remittance-processing logic to read interface rows together with their transmission and transmission-request context.

Underlying Base Objects

The documented base object is AR_PAYMENTS_INTERFACE_ALL, the core Automatic Receipts interface table that stages records before they are formatted and transmitted to a bank, lockbox processor, or remittance partner. The view is a projection over that table, restricted to RECORD_TYPE=6 and constrained by the entity-org isolation predicate. No additional referenced base objects are documented in the ETRM metadata for this view. Functionally, the view leans on the transmission-related columns of AR_PAYMENTS_INTERFACE_ALL—specifically TRANSMISSION_ID, TRANSMISSION_REQUEST_ID, TRANSMISSION_RECORD_ID, STATUS, and OVERFLOW_SEQUENCE/OVERFLOW_INDICATOR—to present a coherent view of payment interface rows that belong to a given remittance/transmission request. Because the view filters on RECORD_TYPE=6, only rows of that specific record type are surfaced, which is consistent with a dedicated payment/remittance record class within the interface.

Key Columns

• TRANSMISSION_RECORD_ID / TRANSMISSION_ID / TRANSMISSION_REQUEST_ID — Identifiers that tie an interface row to its transmission record and the parent transmission request. These are the columns most relevant to the user's search for "transmission_id."
• RECORD_TYPE — Fixed at 6 by the view definition, distinguishing this record class from other interface rows.
• STATUS — Lifecycle status of the interface row (e.g., staged, formatted, transmitted).
• BATCH_NAME / CPG_ORIG_BATCH_NAME — Current and original batch identification for reconciliation.
• CHECK_NUMBER / CPG_REASSOCIATION_TRACE_NUM — Payment instrument and trace reference.
• ITEM_NUMBER / INVOICE1 / AMOUNT_APPLIED1 / INVOICE1_INSTALLMENT — The receipt or invoice line being applied, with amount and installment detail.
• CURRENCY_CODE / GL_DATE / CPG_TRANSACTION_DATE — Currency and accounting/transaction dates.
• LOCKBOX_NUMBER / CPG_ORIG_LOCKBOX_NUMBER — Current and originating lockbox references.
• CPG_PURCHASE_ORDER_NUMBER / CPG_CUSTOMER_REF_NUMBER / CPG_SHIP_TO_LOCATION_NUMBER / CPG_ORIGINAL_TRX_NUMBER — CPG (customer payment group) reference attributes carried from the source transaction.
• CPG_ASSOCIATION_FLAG / CPG_TRX_HANDLING_CODE / CPG_CUST_DEDUCTION_REASON_CODE — Flags and codes governing association and deduction handling.
• OVERFLOW_SEQUENCE / OVERFLOW_INDICATOR — Support for records exceeding segment limits in fixed-format remittance output.
• ORG_ID — Operating unit identifier used for the entity-org security predicate.

Common Use Cases and Queries

This view is typically queried to locate interface payment rows associated with a specific transmission or to reconcile remittance staging. A representative query retrieving rows for a known transmission id is:

SELECT TRANSMISSION_ID, TRANSMISSION_REQUEST_ID, TRANSMISSION_RECORD_ID, STATUS, CHECK_NUMBER, AMOUNT_APPLIED1, CURRENCY_CODE FROM AR_TA_PAYMENTS_INTERFACE_REM_V WHERE TRANSMISSION_ID = :transmission_id;

Other common patterns include grouping by transmission request to count staged records, joining to receipt and remittance metadata using TRANSMISSION_RECORD_ID, and inspecting overflow handling via OVERFLOW_SEQUENCE and OVERFLOW_INDICATOR. Because the view is org-secured, queries executed through the standard Receivables responsibility automatically restrict returned rows to the current operating unit, which makes it suitable for operational reporting without additional ORG_ID filtering—though explicit ORG_ID predicates are advisable in cross-org diagnostic scripts. The fixed RECORD_TYPE=6 filter should be treated as authoritative: the view will not return other interface record types, so it must not be used as a general-purpose substitute for querying AR_PAYMENTS_INTERFACE_ALL.