Results for “ar_dms_to_ta_request_id_v”

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

Overview

AR_DMS_TO_TA_REQUEST_ID_V is a reporting view within the Oracle E-Business Suite Receivables (AR) module. Its name reflects a bridging role between the DMS (Document Management System / deduction management) side of Receivables and the TA (Trade/Transaction Accounting or Transfer Authority) layer: the view exposes the set of distinct REQUEST_ID values that have been recorded in the Receivables deductions interface. In effect, it is a thin projection that reduces the AR_TA_DEDN_INT table to a single column of request identifiers, providing a clean, de-duplicated list of concurrent request runs that have touched the deduction interface.

As documented in the ETRM (12.2.2) metadata, the view is characterized as "not implemented in this database" in the source system from which the metadata was harvested. This is an important caveat: the definition and columns are documented, but the object is not guaranteed to be present in every EBS instance. In practice, the presence of AR_DMS_TO_TA_REQUEST_ID_V depends on the deployment of the Receivables deduction/trade accounting integration features. Where it exists, it serves primarily as a lightweight lookup or validation source for integrations and reports that need to enumerate the request IDs associated with deduction interface activity, without scanning the much wider AR_TA_DEDN_INT table.

Underlying Base Objects

The view is defined over a single base object, AR_TA_DEDN_INT. It is a simple aggregation view: the defining query is SELECT REQUEST_ID FROM AR_TA_DEDN_INT GROUP BY REQUEST_ID. The GROUP BY clause is what gives the view its distinctive purpose — it collapses the potentially large, row-per-transaction content of the interface table down to one row per concurrent request.

ETRM documentation records no referenced base objects beyond the implied dependency on AR_TA_DEDN_INT, and no additional joins, lookups, or outer tables are defined. This makes the view's lineage straightforward and predictable: every value returned maps back to at least one row in AR_TA_DEDN_INT, and no value can exist in the view that is absent from the interface table. There are no synonyms, no joins to FND_CONCURRENT_REQUESTS, and no translation or decode logic embedded in the view itself.

Key Columns

• REQUEST_ID — The sole column exposed by the view. It is the Oracle Applications concurrent program request identifier (REQUEST_ID), the key that ties a processing run to the Concurrent Manager. Because the view applies GROUP BY REQUEST_ID, each request ID appears exactly once, regardless of how many deduction interface rows were produced by that run.

This single-column signature is deliberate. The view is not intended to carry deduction detail, amounts, customer data, or status codes; those remain in the underlying interface table. Instead, it answers one narrow question: "which request IDs have populated the deduction interface?"

Common Use Cases and Queries

The view is most frequently used to enumerate or validate concurrent request runs associated with deduction processing. A typical query is:

• SELECT REQUEST_ID FROM AR_DMS_TO_TA_REQUEST_ID_V ORDER BY REQUEST_ID; — returns the distinct set of request IDs present in the deduction interface.
• SELECT REQUEST_ID FROM AR_DMS_TO_TA_REQUEST_ID_V WHERE REQUEST_ID = :req_id; — confirms whether a specific concurrent request populated the interface, useful in reconciliation and support diagnostics.
• A join back to FND_CONCURRENT_REQUESTS on REQUEST_ID allows analysts to attach program name, start time, and completion status to each identifier, though that join is implemented outside the view.

The user search term "dmt invoice tracker" suggests interest in tracking invoice-related or deduction-related processing runs. This view supports that need indirectly: it isolates the request IDs behind deduction interface activity so that an external tracker or report can correlate them with invoice and deduction outcomes. Because the view is documented as not implemented in the harvested database, implementers should verify its existence in their target environment before relying on it, and otherwise reproduce its logic directly against AR_TA_DEDN_INT using the same GROUP BY REQUEST_ID construct.