Results for “jtf_terr_rsc_access”

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

Overview

JTF_TERR_RSC_ACCESS is a reporting view in the Oracle E-Business Suite CRM Foundation (JTF) product family, introduced to expose territory resource access assignments across the EBS instance. It is documented in the E-Business Suite Technical Reference Manual (ETRM) for releases 12.1.1 and 12.2.2 and is functionally equivalent to the JTF_TERR_RSC_ALL table from which it draws its data. The view surfaces the intersection of a territory resource (the person, group, or organization assigned to a territory) with the access rights granted to that resource, filtered by operating unit through the ORG_ID column.

The distinguishing characteristic of this view is its use of a standard multi-org access pattern rather than a strict filter. In earlier and some non-multi-org implementations, the base table JTF_TERR_RSC_ACCESS_ALL holds all rows regardless of operating unit. The _ACCESS view is intended to return only those rows that the querying session is entitled to see, based on the MO: Operating Unit or MO: Security Profile profile option. The ETRM notes that in some databases the view is "Not implemented" — meaning no database synonym or view object exists at that site — so availability should be confirmed before use in customizations or reports.

Because it presents resource-to-access-type mappings in a single, denormalized form, the view is well suited for CRM territory administration reporting, security reviews, and integration extracts that need a clean list of who can access which territory resource under which operating unit.

Underlying Base Objects

The view is defined as a simple SELECT against JTF_TERR_RSC_ACCESS_ALL. No joins, unions, or aggregations are present. The view text is:

• SELECT TERR_RSC_ACCESS_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, TERR_RSC_ID, ACCESS_TYPE, ORG_ID FROM JTF_TERR_RSC_ACCESS_ALL

The ETRM metadata records no explicitly documented owner or referenced base tables beyond this ALL table, and the view is described as identical in structure to JTF_TERR_RSC_ALL. Functionally, therefore, JTF_TERR_RSC_ACCESS is a thin projection over the multi-org base table, applying the security policies that constrain ORG_ID visibility. In practice, the row count returned by the view is typically a subset of the row count in the ALL table.

Key Columns

The view exposes nine columns. Their meanings are as follows:

• TERR_RSC_ACCESS_ID — Primary key of the access assignment record, uniquely identifying each row.
• LAST_UPDATE_DATE — Date of the most recent change to the row.
• LAST_UPDATED_BY — User ID of the last updater.
• CREATION_DATE — Date the record was created.
• CREATED_BY — User ID that created the record.
• LAST_UPDATE_LOGIN — Login ID associated with the last update, useful for audit.
• TERR_RSC_ID — Foreign key to the territory resource definition; identifies the resource receiving access.
• ACCESS_TYPE — Code indicating the level or nature of access granted to the resource.
• ORG_ID — Operating unit identifier used by the multi-org access mechanism to filter visible rows.

Common Use Cases and Queries

The view supports territory administration auditing, security validation, and data migration. A typical query lists all access assignments visible to the current operating unit:

• SELECT TERR_RSC_ACCESS_ID, TERR_RSC_ID, ACCESS_TYPE, ORG_ID FROM JTF_TERR_RSC_ACCESS ORDER BY TERR_RSC_ID;

To inspect assignments for a specific operating unit, add a predicate on ORG_ID, for example WHERE ORG_ID = :p_org_id. To reconcile the view against its base table and detect rows hidden by multi-org security, compare counts between JTF_TERR_RSC_ACCESS and JTF_TERR_RSC_ACCESS_ALL. Because the view is not implemented in every database, scripts should verify existence via ALL_VIEWS before referencing it.