Results for “access_type”

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

Overview

JTF_TERR_RSC_ACCESS_V is a documented Oracle E-Business Suite view owned by the APPS schema and delivered as part of the JTF – CRM Foundation product family. Its stated purpose is to expose the access types that a resource holds to a territory, providing a denormalized, human-readable representation of the territory-resource access model used throughout Territory Manager and related CRM modules. The view is catalogued as VALID in the ETRM metadata for both EBS 12.1.1 and 12.2.2, and it is routinely referenced by reporting, integration, and personalization logic that must determine why a given resource appears, or fails to appear, in a territory.

Because it is a view rather than a table, no data is stored at this layer. It is a read-only projection over the underlying territory-resource access table, joined to a qualification-type lookup so that a descriptive meaning is returned alongside the raw access type code. This makes the view particularly useful in environments where external systems consume territory assignments and require a decoded value rather than an internal lookup name.

Underlying Base Objects

The documented definition of the view selects from two physical sources and is documented in ETRM as referencing FND_GLOBAL (PACKAGE), JTF_QUAL_TYPES (VIEW), and JTF_TERR_RSC_ACCESS (SYNONYM). The JTF_TERR_RSC_ACCESS synonym resolves to the underlying base table that stores the territory-resource access rows, and it supplies the primary key, audit, and descriptive columns of the view. The join to JTF_QUAL_TYPES resolves the ACCESS_TYPE value to a descriptive MEANING, converting the internal lookup name into a presentation-ready label.

The view text shown in the ETRM documentation joins J1 (JTF_TERR_RSC_ACCESS) to J2 (JTF_QUAL_TYPES) on J1.ACCESS_TYPE = J2.NAME. The presence of FND_GLOBAL in the documented metadata is consistent with multi-org security enforcement applied at the view or underlying object level, ensuring that territory access records are filtered by the operating unit context of the querying session.

Key Columns

The view exposes a compact but complete column set. The important columns are:

• ROW_ID — the ROWID of the underlying JTF_TERR_RSC_ACCESS row, used as a unique row identifier.
• TERR_RSC_ACCESS_ID — primary key of the territory-resource access record.
• TERR_RSC_ID — the territory-resource identifier linking the access record to its resource assignment within a territory.
• ACCESS_TYPE — the internal code denoting the access level (for example, the qualification type name) the resource holds.
• MEANING — the decoded description obtained from JTF_QUAL_TYPES, providing the display value for ACCESS_TYPE.
• ORG_ID — the operating unit identifier supporting multi-org access control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table for change tracking and reconciliation.

Common Use Cases and Queries

Typical scenarios include auditing which resources hold a particular level of access to a territory, diagnosing why a sales representative is or is not receiving territory-qualified leads, and feeding external CRM or analytics platforms with decoded access data. A straightforward listing of all decoded access records is:

SELECT terr_rsc_access_id, terr_rsc_id, access_type, meaning, org_id
FROM apps.jtf_terr_rsc_access_v
WHERE org_id = :p_org_id;

To isolate resources holding a specific access level, filter on the descriptive MEANING rather than the raw code:

SELECT terr_rsc_id, access_type, meaning
FROM apps.jtf_terr_rsc_access_v
WHERE meaning = :p_access_meaning;

Because the view resolves ACCESS_TYPE through JTF_QUAL_TYPES, it should always be preferred over querying JTF_TERR_RSC_ACCESS directly when a decoded value is required, reducing dependency on internal lookup name conventions maintained by the application.