Search Results jtf_terr_rsc_access_all_pk




Overview

The JTF_TERR_RSC_ACCESS_ALL table is a core data object within the Oracle E-Business Suite CRM Foundation (JTF) module, specifically for Release 12.1.1 and 12.2.2. It serves as the central repository for defining the level of access a sales or service resource possesses within a specific territory. This table is integral to the territory management and resource assignment functionalities, enabling precise control over which resources can view, update, or own records associated with a given territory. Its design supports a multi-organization model, as indicated by the "_ALL" suffix, meaning it can store data across multiple operating units when properly partitioned.

Key Information Stored

The table's primary function is to map a resource's access type to a territory assignment. While the full column list is not detailed in the provided metadata, the structure is defined by its primary and foreign keys. The TERR_RSC_ACCESS_ID column is the unique primary key identifier for each access record. The TERR_RSC_ID is a critical foreign key column that links to the JTF_TERR_RSC_ALL table, which stores the base assignment of a resource to a territory. The table would logically contain at least one additional column to store the enumerated ACCESS_TYPE, which defines the specific privilege (e.g., Read, Write, Full Control) granted to the resource for that territory assignment.

Common Use Cases and Queries

This table is primarily accessed for territory security validation and reporting on resource permissions. A common operational query is to determine all access levels for a specific resource across territories, often for auditing or troubleshooting assignment issues. For reporting, it is frequently joined with territory and resource master tables to produce lists of resources and their effective privileges within a sales region. A typical SQL pattern involves joining JTF_TERR_RSC_ACCESS_ALL to JTF_TERR_RSC_ALL and then to resource (JTF_RS_RESOURCE_EXTNS) and territory (JTF_TERRITORIES_B) definition tables.

  • Sample Query: Retrieve a resource's territory access details.
    SELECT rsc.resource_id, terr.territory_id, acc.access_type
    FROM jtf_terr_rsc_access_all acc,
    jtf_terr_rsc_all rsc,
    jtf_territories_b terr
    WHERE acc.terr_rsc_id = rsc.terr_rsc_id
    AND rsc.territory_id = terr.territory_id
    AND rsc.resource_id = 1000;

Related Objects

The table has a direct and documented dependency on the JTF_TERR_RSC_ALL table, which stores the fundamental resource-to-territory assignment. The relationship is enforced by a foreign key constraint where JTF_TERR_RSC_ACCESS_ALL.TERR_RSC_ID references JTF_TERR_RSC_ALL. This design means an access record cannot exist without a corresponding base territory assignment record. Key related objects not listed in the metadata but essential for complete data context include JTF_TERRITORIES_B (territory definitions) and JTF_RS_RESOURCE_EXTNS (resource definitions), which are joined via the JTF_TERR_RSC_ALL table.

  • Primary Key Constraint: JTF_TERR_RSC_ACCESS_ALL_PK (on column TERR_RSC_ACCESS_ID)
  • Foreign Key Relationship: JTF_TERR_RSC_ACCESS_ALL.TERR_RSC_ID → JTF_TERR_RSC_ALL table