Results for “ar_ta_int_batch_name_v”

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

Overview

The view AR_TA_INT_BATCH_NAME_V belongs to the Oracle Receivables (AR) module and forms part of the AutoInvoice / tax and remittance integration infrastructure within Oracle E-Business Suite 12.1.1 and 12.2.2. Its name follows Oracle's convention for integration views: AR (Receivables), TA (Transaction/Tax area), INT (integration), and _V (view). The view exposes a single column, BATCH_NAME, and is designed to surface the set of distinct remittance batch names that satisfy a specific pair of record-type conditions against the remittance history table.

In practical terms, the view acts as a lightweight lookup or validation helper for processes and reports that must enumerate valid remittance batch names without directly querying the underlying history table. It decouples consuming code from the physical structure of AR_TA_REMIT_HIST and returns only the batch name attribute, which is useful when building concurrent program parameters (such as an LOV driven by a value set), interface validation routines, or reconciliation queries that need to iterate across batches.

Underlying Base Objects

The view is defined exclusively over AR_TA_REMIT_HIST, referenced twice with the aliases RH1 and RH2 — a self-join. The ETRM metadata lists no other referenced base objects. The documented view text is:

• SELECT DISTINCT RH1.BATCH_NAME BATCH_NAME FROM AR_TA_REMIT_HIST RH1, AR_TA_REMIT_HIST RH2 WHERE RH1.RECORD_TYPE=6 AND RH2.RECORD_TYPE=7 AND RH2.PARENT_HISTORY_LINE_ID=RH1.HISTORY_LINE_ID

The join condition links RH2 to RH1 through PARENT_HISTORY_LINE_ID = HISTORY_LINE_ID. The filter restricts RH1 rows to RECORD_TYPE = 6 and RH2 rows to RECORD_TYPE = 7. Consequently, only batch names whose history contains a record of type 6 that is the parent of a record of type 7 are returned. In the tax/remittance context, RECORD_TYPE distinguishes the nature of each history line (for example, header versus detail, or a controlling record versus its associated distribution), and PARENT_HISTORY_LINE_ID establishes the hierarchical linkage between them. The DISTINCT keyword removes duplicate batch names so each valid batch appears once.

Key Columns

The view exposes a single documented column:

• BATCH_NAME — The identifier of a remittance batch as recorded in AR_TA_REMIT_HIST.BATCH_NAME. It corresponds to the user- or process-assigned batch label used to group remittance history records. Because the query applies DISTINCT and the type 6/type 7 join filter, the value represents only those batches that contain a completed parent/child relationship between the two record types.

No other columns are projected. Any column present in AR_TA_REMIT_HIST — such as HISTORY_LINE_ID, PARENT_HISTORY_LINE_ID, or RECORD_TYPE — is used internally in the view definition but is not exposed to consumers.

Common Use Cases and Queries

Typical scenarios include populating a parameter list of valid batch names, validating a batch supplied by an interface, and auditing which batches carry paired remittance records. A representative query is:

• SELECT BATCH_NAME FROM AR_TA_INT_BATCH_NAME_V ORDER BY BATCH_NAME;
• SELECT COUNT(*) FROM AR_TA_INT_BATCH_NAME_V; — to count distinct qualifying batches.
• SELECT BATCH_NAME FROM AR_TA_INT_BATCH_NAME_V WHERE BATCH_NAME LIKE :p_prefix; — to restrict by a naming pattern for a value-set LOV.

Because the view performs a self-join over a potentially large history table, queries that return all rows should be used judiciously; applying filters on BATCH_NAME where the value set permits helps constrain the result. The view is read-only and intended for query access only. Note that the ETRM metadata records the object as "Not implemented in this database" for the documented environment, indicating that availability depends on whether the relevant Receivables tax/remittance patch level has installed the underlying objects.