Results for “ar_ta_asgn_to_int”

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

Overview

AR_TA_ASGN_TO_INT is a reporting and integration view in the Oracle E-Business Suite Receivables (AR) module, delivered as part of the ETRM (E-Business Tax and Transaction Management) object set. The view is documented with the description "SINGLE_ORG view," which identifies its primary architectural role: it exposes organization-scoped data from a multi-organization table while transparently enforcing the operating unit (ORG_ID) security context of the current session. In Oracle EBS 12.1.1 and 12.2.2, single-org views are the standard mechanism by which multi-org tables are surfaced to forms, reports, concurrent programs, and integration interfaces without requiring the calling application to embed operating unit predicates explicitly.

The view centers on "assigned-to" records — entities (parties, resources, or personnel) to whom transactions, tasks, or receivables activities are assigned. The presence of the ASSIGNED_TO_ID and ASSIGNED_TO_NUMBER columns, together with NAME, TYPE, START_DATE, END_DATE, and STATUS, indicates that the view describes assignments with effective-dating and lifecycle state. The user search term "assigned_to_number" corresponds directly to the ASSIGNED_TO_NUMBER column exposed by this view.

Underlying Base Objects

The view is defined exclusively over a single underlying table, AR_TA_ASGN_TO_INT_ALL. The _ALL suffix follows the Oracle multi-organization naming convention, indicating that the base table stores rows for all operating units, discriminated by the ORG_ID column.

The view applies a restrictive WHERE clause that filters AR_TA_ASGN_TO_INT_ALL down to the current operating unit. The predicate extracts the organization identifier from the USERENV('CLIENT_INFO') session value, decoding the first ten characters when the first character is not a space, and compares it against ORG_ID. Both sides of the comparison use NVL(..., -99), which means rows with a null ORG_ID, and sessions with no resolvable client information, are evaluated consistently against the sentinel value -99. This is the classic single-org view pattern used throughout Receivables and other Oracle EBS modules.

The ETRM metadata records no other documented referenced base objects and states the view is "Not implemented in this database" in the source datasource, meaning the definition is a shipped reference rather than an installed object in that particular environment. No documentation confirms the existence of an accompanying _S or _TL variant, so it should be assumed that name and type information is stored directly on the _ALL table.

Key Columns

• ASSIGNED_TO_ID — Primary identifier of the assigned-to record; the foreign key used in joins to related transaction or assignment tables.
• ASSIGNED_TO_NUMBER — The business-facing number or reference for the assigned-to entity, and the column most commonly used for lookups and cross-referencing.
• NAME — Descriptive name of the assigned-to entity.
• TYPE — Classification of the assigned-to entity (for example, distinguishing entity categories).
• START_DATE / END_DATE — Effective-dating bounds governing when the assignment record is valid.
• STATUS — Lifecycle state of the assignment record.
• ORG_ID — Operating unit discriminator; the column on which the single-org filter operates.
• REQUEST_ID — Identifier of the concurrent request that created or last processed the row.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide audit lineage.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle flexfield (descriptive) columns for extensibility.

Common Use Cases and Queries

Because the view enforces operating unit context automatically, it is the preferred access point for reports, concurrent programs, and integration extracts that must respect multi-org security. Typical scenarios include listing active assignments for the current operating unit, resolving an assigned-to number to its identifier for downstream processing, and extracting assignment records within a date range for reconciliation or interface loading.

Sample query returning assignments active on the current date:

• SELECT ASSIGNED_TO_ID, ASSIGNED_TO_NUMBER, NAME, TYPE, STATUS, START_DATE, END_DATE FROM AR_TA_ASGN_TO_INT WHERE STATUS = 'ACTIVE' AND TRUNC(SYSDATE) BETWEEN START_DATE AND NVL(END_DATE, TRUNC(SYSDATE));

Sample query resolving a specific assigned-to number:

• SELECT ASSIGNED_TO_ID, ASSIGNED_TO_NUMBER, NAME, ORG_ID FROM AR_TA_ASGN_TO_INT WHERE ASSIGNED_TO_NUMBER = :p_assigned_to_number;

For cross-operating-unit reporting, query AR_TA_ASGN_TO_INT_ALL directly with an explicit ORG_ID predicate, since the single-org view restricts results to the session organization. Note that the view text is documented as "Not implemented in this database" in the source ETRM extract, so object availability should be verified against the target environment before relying on it in production code.