Results for “ar_ta_int_invoice_number_v”

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

Overview

AR_TA_INT_INVOICE_NUMBER_V is a Receivables (AR) view that exposes a single column, INVOICE_NUMBER, representing transaction numbers drawn from the AR_TA_REMIT_HIST remittance history table. The view belongs to the Oracle E-Business Suite Trade Accounting / Receivables integration layer and is deployed across EBS 12.1.1 and 12.2.2. Its purpose is to surface the set of receivable invoice (transaction) numbers that have been associated with remittance advice processing, so downstream report, concurrent program, or interface logic can resolve invoice identifiers without embedding the full self-join against the remittance history table.

Because the view returns DISTINCT values, it acts as a lightweight lookup list of invoice numbers encountered in the remittance history rather than a transactional detail view. In the context of a user search on "invoice_number," this object is relevant because INVOICE_NUMBER is its only projected column and is derived from TRX_NUMBER on the underlying remittance history rows. It does not carry customer, amount, currency, or date attributes, so it is typically joined back to AR_TA_REMIT_HIST or RA_CUSTOMER_TRX_ALL when additional context is required.

Underlying Base Objects

The view is defined solely over AR_TA_REMIT_HIST, referenced twice through the aliases RH1 and RH2:

• RH1 — filtered to rows where RECORD_TYPE = 6, supplying the TRX_NUMBER projected as INVOICE_NUMBER.
• RH2 — filtered to rows where RECORD_TYPE = 7, and correlated to RH1 through the condition RH2.PARENT_HISTORY_LINE_ID = RH1.HISTORY_LINE_ID.

The join establishes a parent/child relationship within the remittance history hierarchy: record type 6 rows act as the parent carrying the transaction number, and record type 7 rows are the related child records. Only parent rows that have at least one matching child are returned, which is why DISTINCT is applied — a single parent may have multiple qualifying children. The ETRM metadata documents no additional referenced base objects, and the view is listed as "not implemented in this database," meaning it exists in the shipped product definition but is not necessarily present in every environment.

Key Columns

• INVOICE_NUMBER — The transaction number (TRX_NUMBER) of the receivable invoice associated with a remittance history parent record (RECORD_TYPE = 6) that has child records (RECORD_TYPE = 7). This is the transaction number commonly displayed on invoices and used to identify a receivable transaction in AR and in downstream general ledger or reconciliation reporting. Values are returned once per distinct invoice number regardless of how many child history lines exist.

Common Use Cases and Queries

Typical uses include identifying which invoices have remittance activity, driving reconciliation or reporting that must enumerate invoice numbers with associated remittance children, and providing a lookup domain for validation in custom concurrent programs or interfaces.

Selecting all exposed invoice numbers:

• SELECT invoice_number FROM ar_ta_int_invoice_number_v;

Joining back to remittance history to obtain the underlying history line identifiers:

• SELECT v.invoice_number, rh.history_line_id, rh.record_type FROM ar_ta_int_invoice_number_v v, ar_ta_remit_hist rh WHERE rh.trx_number = v.invoice_number;

Checking whether a specific invoice appears in remittance history:

• SELECT invoice_number FROM ar_ta_int_invoice_number_v WHERE invoice_number = :p_trx_number;

Because the view exposes only INVOICE_NUMBER and performs no filtering beyond the RECORD_TYPE and parent-child conditions, queries requiring amounts, dates, or customer data must join to AR_TA_REMIT_HIST or the core AR transaction tables. Review the view text in each environment, since the ETRM notes it is not implemented in all databases and its definition may be customized.