Search Results batch_sequence

Overview

AR_TA_REMIT_HIST is a reporting view in the Oracle Receivables (AR) module, classified in the ETRM documentation as a SINGLE_ORG view. Its name indicates that it exposes the remittance history generated by Oracle Receivables' AutoRemittance and bank transmission processing. Each row represents a historical line item associated with a transmission request — typically the record of a receipt, transaction, or adjustment that was packaged into a remittance batch and transmitted to a bank or lockbox processor.

The view is not stored as a standalone database object with independent data. As documented, it is "Not implemented in this database," meaning it is defined only as a view template at the ETRM level and is created at runtime in customer instances by the underlying product installation or patching mechanism. Because it is a SINGLE_ORG view, it presents a filtered subset of the multi-org AR_TA_REMIT_HIST_ALL table, restricting rows to the operating unit currently established in the user's session. This makes it suitable for reports and concurrent programs that must run in the context of a single operating unit without exposing cross-organization data.

In Oracle EBS 12.1.1 and 12.2.2, views of this type serve both operational reporting (for example, reviewing remittance activity for a given lockbox or transmission request) and integration/audit purposes, since the remittance history captures what was sent, matched, applied, or adjusted during the transmission lifecycle.

Underlying Base Objects

The ETRM metadata identifies a single referenced base object: AR_TA_REMIT_HIST_ALL. The view is defined as a straightforward projection — every column in the view maps one-to-one to a column in AR_TA_REMIT_HIST_ALL, with no joins, aggregations, or derived expressions in the SELECT list. The only logic applied is the WHERE clause, which implements the single-org security filter.

The filtering predicate relies on the session environment variable USERENV('CLIENT_INFO'). The view compares the ORG_ID column of the base table against a numeric value parsed from the first ten characters of CLIENT_INFO. When the first character of CLIENT_INFO is a space, the value is treated as NULL. The comparison uses NVL(..., -99) on both sides, so rows with a null ORG_ID are matched to a session with a null org context (both resolving to -99). This is the standard multi-org "SINGLE_ORG" view pattern used throughout Oracle EBS.

No other base tables are documented as referenced by this view. Because the metadata lists no additional objects, the view should be treated as a direct, filtered reflection of the _ALL table rather than as a joined reporting construct.

Key Columns

The view exposes an extensive column set that mirrors the transmission and remittance lifecycle. The most significant columns include:

• HISTORY_LINE_ID — Primary identifier for each remittance history line.
• TRANSMISSION_REQUEST_ID — Links the history line to the transmission request that produced it.
• ORG_ID — Operating unit identifier used by the SINGLE_ORG filter.
• CUSTOMER_ID, CHECK_NUMBER, TRX_NUMBER, TRX_AMOUNT, REMITTANCE_AMOUNT — Identify the customer, payment instrument, transaction, and the amounts remitted.
• MATCHED_TRX_NUMBER, MATCHED_TRX_ID, MATCHED_TRX_TYPE, AMOUNT_APPLIED, DISCOUNT_AMT — Describe how the remittance line was matched and applied, including discount taken.
• NEW_TRX_ID, NEW_TRX_TYPE, AMOUNT — Capture the resulting transaction created or adjusted by the auto-remittance rule.
• CASH_RECEIPT_ID — Reference to the cash receipt associated with the line.
• ADJUSTMENT_ID, ADJUSTMENT_NUMBER, ADJUSTMENT_STATUS, ADJUSTMENT_ACTIVITY_ID — Details of any adjustment generated, along with its status.
• RULE_ID, RULE_SET_ID, RULE_PROCEDURE, RULE_PROCESS, PROFILE_ID — Identify the auto-remittance rule, rule set, and processing logic that determined the outcome.
• CURRENCY_CODE, PAYMENT_TYPE, EVENT_TYPE, RECORD_TYPE — Classify the financial and event characteristics of the line.
• RECEIPT_DATE, APPLY_DATE, DEPOSIT_DATE, POSTMARK_DATE — Key dates for reconciliation and aging.
• EDI_REASS_TRACE_NUMBER, EDI_TRX_HANDLING_CODE, EDI_ASSOCIATION_FLAG — EDI-related identifiers relevant to electronic remittance processing.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

Common Use Cases and Queries

Typical uses include auditing what an auto-remittance transmission contained, reconciling applied versus remitted amounts, reviewing adjustments produced by auto-remittance rules, and tracing EDI remittance handling. Because the view is session-org filtered, it is well suited to concurrent programs and Oracle Reports that run in a single operating unit context.

Example: list recent remittance history lines for a transmission request.

SELECT h.history_line_id,
       h.transmission_request_id,
       h.customer_id,
       h.check_number,
       h.remittance_amount,
       h.amount_applied,
       h.adjustment_number,
       h.receipt_date
FROM   ar_ta_remit_hist h
WHERE  h.transmission_request_id = :p_request_id
ORDER  BY h.history_line_id;

Example: summarize remitted versus applied amounts by currency.

SELECT h.currency_code,
       COUNT(*)                line_count,
       SUM(h.remittance_amount) total_remitted,
       SUM(h.amount_applied)    total_applied
FROM   ar_ta_remit_hist h
WHERE  h.receipt_date BETWEEN :p_start AND :p_end
GROUP  BY h.currency_code;

Example: locate adjustment activity from auto-remittance rules.

SELECT h.adjustment_number,
       h.adjustment_id,
       h.adjustment_status,
       h.rule_id,
       h.rule_set_id,
       h.trx_number
FROM   ar_ta_remit_hist h
WHERE  h.adjustment_id IS NOT NULL
AND    h.adjustment_status = 'A';

Because the view is a filtered projection of AR_TA_REMIT_HIST_ALL, queries should always run under a properly initialized operating unit context; otherwise the USERENV('CLIENT_INFO') filter may return no rows. For cross-organization reporting, query the underlying _ALL table directly and apply an explicit ORG_ID predicate.