Results for “trx_set_id”

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

Overview

AR_TA_TRX_SETS is a single-organization (SINGLE_ORG) reporting view in the Oracle E-Business Suite Receivables (AR) module. It exposes transaction set definitions — logical groupings of transactions used by Receivables for grouping, batch processing, and reporting purposes — while enforcing Oracle's multi-organization access security model at query time. The view is classified under AR - Receivables in the ETRM metadata, and its primary identifier is TRX_SET_ID, the column users most frequently reference when tracing transaction set membership.

In Oracle EBS 12.1.1 and 12.2.2, the SINGLE_ORG designation means the view filters rows to the organization (operating unit) associated with the current session, rather than returning data across all organizations. The view exists to provide a secured, operating-unit-scoped projection of the underlying transaction sets table so that concurrent requests, forms, and integrations only see data relevant to the active organization context. This is consistent with the Multi-Org architecture used throughout Receivables, where an _ALL base table holds rows for every operating unit and a corresponding single-org view applies the ORG_ID predicate.

The ETRM record notes "Not implemented in this database" for the implementation/DBA data section, and documents no referenced base objects. This indicates the view definition is captured in metadata but was not instantiated in the specific environment sampled. The view text supplied in the ETRM documentation, however, defines the structure unambiguously.

Underlying Base Objects

The view is defined over a single base object, AR_TA_TRX_SETS_ALL, as shown in the view text: SELECT ... FROM AR_TA_TRX_SETS_ALL WHERE NVL(ORG_ID, ...) = NVL(TO_NUMBER(DECODE(SUBSTR(USERENV('CLIENT_INFO'), 1, 1), ' ', NULL, SUBSTR(USERENV('CLIENT_INFO'), 1, 10))), -99). The _ALL suffix confirms that AR_TA_TRX_SETS_ALL stores transaction set definitions across all operating units, and AR_TA_TRX_SETS is the secured single-org projection of that table.

The predicate derives the current organization from USERENV('CLIENT_INFO'), Oracle's traditional mechanism for passing multi-org context. The first character of CLIENT_INFO is inspected; if it is a space, the decode returns NULL (no organization context), otherwise the first ten characters are interpreted as the numeric ORG_ID. Both the column expression and the bind expression are wrapped in NVL(..., -99), so rows and the session context are normalized to a sentinel value of -99 when no organization is available. This design ensures the view returns rows only when the stored ORG_ID matches the active organization context, including the "no org" case.

Key Columns

• TRX_SET_ID — Primary identifier for the transaction set; the key searched for by users and the join column to related transaction-set associations.
• ORG_ID — Operating unit that owns the transaction set; drives the single-org security filter applied by the view.
• NAME — User-defined name of the transaction set.
• DESCRIPTION — Free-text description of the transaction set.
• START_DATE / END_DATE — Effective date range during which the transaction set is valid.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns tracking the most recent modification.
• CREATION_DATE, CREATED_BY — Standard audit columns capturing row creation.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield (DFF) columns supporting client-specific extension of transaction set definitions.

Common Use Cases and Queries

The view is used in reporting and integration scenarios requiring transaction set data scoped to the current operating unit, such as resolving a TRX_SET_ID to its name and validity dates, or listing active transaction sets for a given organization.

Basic lookup by identifier:

SELECT trx_set_id, name, description, start_date, end_date, org_id
FROM   ar_ta_trx_sets
WHERE  trx_set_id = :trx_set_id;

Listing currently effective transaction sets:

SELECT trx_set_id, name, start_date, end_date
FROM   ar_ta_trx_sets
WHERE  TRUNC(SYSDATE) BETWEEN NVL(start_date, SYSDATE)
                          AND NVL(end_date, SYSDATE);

When a report must span all operating units, query AR_TA_TRX_SETS_ALL rather than this view, since AR_TA_TRX_SETS restricts output to the organization established in USERENV('CLIENT_INFO'). Integration code that sets multi-org context with FND_GLOBAL / MO_GLOBAL before querying will see the appropriately filtered rows; code that omits context may receive only the -99 (no-org) rows, which is an important behavioral consideration when troubleshooting missing results.