Results for “ar_ta_recv_trxset”

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

Overview

AR_TA_RECV_TRXSET is a reporting and integration view in the Oracle E-Business Suite Receivables (AR) module. Its documented description identifies it as a "SINGLE_ORG view," which is the standard Oracle Applications pattern for presenting multi-organization data as if it belonged to a single operating unit. The view is layered over the multi-org base table AR_TA_RECV_TRXSET_ALL and filters rows by the current organization context, so a session only sees the receivable transaction set definitions belonging to the operating unit it is currently operating within. The object is relevant to the searching term receivables_trx_set_id, which is the primary identifier exposed by this view.

The view is defined in the context of standard Oracle EBS 12.1.1 and 12.2.2 environments. In the documented metadata the view is flagged as "Not implemented in this database," meaning the metadata was captured from a reference repository rather than an active instance; its definition and column structure are nonetheless authoritative.

Underlying Base Objects

The view text documents a single underlying base object: AR_TA_RECV_TRXSET_ALL. AR_TA_RECV_TRXSET is a secure, filtered projection of that table. The WHERE clause compares the ORG_ID column against the organization identifier stored in the USERENV('CLIENT_INFO') session context, using the standard Oracle multi-org technique of decoding the first ten characters of CLIENT_INFO. The NVL logic collapses unknown or unset organization values to -99, while NULL ORG_ID values are treated equivalently. This guarantees that only records matching the session's operating unit are returned, and shared or global rows (with NULL ORG_ID) remain visible where applicable. No additional joins, views, or synonyms beyond AR_TA_RECV_TRXSET_ALL are documented. The base table is an _ALL table, which in Oracle EBS denotes a multi-org enabled table partitioned logically by ORG_ID.

Key Columns

• RECEIVABLES_TRX_SET_ID — Primary identifier of the receivables transaction set definition; the column users filter on when searching for a specific transaction set.
• PROFILE_ID — Reference to the transaction set profile that governs the grouping or behavior of the set.
• TRX_SET_ID — Identifier of the transaction set itself, distinct from the RECEIVABLES_TRX_SET_ID.
• RECEIVABLES_ACCOUNT_CCID — Code combination identifier (CCID) of the receivables account associated with the set.
• START_DATE / END_DATE — Effective dating window defining when the transaction set is active.
• ORG_ID — Operating unit identifier used by the single-org filter.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle flexfield descriptive columns for extensible, customer-defined data.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard concurrent-program audit tracking.

Common Use Cases and Queries

Because the view applies the operating unit security filter automatically, it is the preferred object for operational reports and integrations that must respect organization-level data segregation. Typical uses include reporting on active transaction sets, validating effective dates, and extracting the account CCID for reconciliation. A representative query retrieves the identifier and effective window for the current organization:

• SELECT receivables_trx_set_id, trx_set_id, profile_id, start_date, end_date, org_id FROM ar_ta_recv_trxset ORDER BY receivables_trx_set_id;
• SELECT receivables_trx_set_id, receivables_account_ccid FROM ar_ta_recv_trxset WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date, TRUNC(SYSDATE)) AND NVL(end_date, TRUNC(SYSDATE));

For a targeted lookup by the term the user searched, filtering on the primary key returns the single transaction set definition visible to the session, including its associated profile and accounting flexfield. When unrestricted, cross-organization analysis is required, the underlying AR_TA_RECV_TRXSET_ALL table should be queried directly with an explicit ORG_ID predicate, since the view intentionally limits visibility to the current organization context.