Results for “jtf_tty_terr_grp_roles”

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

Overview

The table JTF.JTF_TTY_TERR_GRP_ROLES is a CRM Foundation (JTF) data object that stores the assignment of roles to territory groups within Oracle E-Business Suite. It resides in the JTF schema and is marked VALID in both the 12.1.1 and 12.2.2 releases. Territory groups are the containers used by Oracle Territory Manager to organize territories, and this table records which role codes apply to each territory group. The information held here drives eligibility behavior in downstream territory processing, including how role-based product and resource access is scoped to a given group.

From a dimensional modeling perspective, the ETRM heuristic classifies this object as satellite-leaning. This is a modeling suggestion rather than a physical designation: the table carries a surrogate primary key plus descriptive and audit attributes, and it depends on a parent hub-like entity through a foreign key. It should therefore be treated as descriptive context attached to a parent territory-group entity rather than as an independent business entity or an associative link between two hubs.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

• TERR_GROUP_ROLE_ID — the surrogate primary key, backed by JTF_TTY_TERR_GRP_ROLES_PK and also carried by the unique index JTF_TTY_TERR_GRP_ROLES_U1. This is the identifier referenced by child objects.
• TERR_GROUP_ID — foreign key to JTF_TTY_TERR_GROUPS, identifying the territory group to which the role assignment belongs.
• ROLE_CODE — the role being associated with the territory group; this is the core business value of the row.
• OBJECT_VERSION_NUMBER — the standard Oracle Applications optimistic locking column used by the framework during concurrent updates.
• CREATED_BY, CREATION_DATE — standard audit columns capturing row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent update, its timestamp, and the login session responsible.

The surrogate key TERR_GROUP_ROLE_ID is the documented uniqueness anchor; TERR_GROUP_ID combined with ROLE_CODE functions as the practical business-key candidate, since it defines the logical role-to-group assignment.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing the roles configured for each territory group, auditing role assignments by creation or update date, and joining through to product integration for role-based access scoping. A representative query:

• SELECT r.TERR_GROUP_ROLE_ID, r.TERR_GROUP_ID, r.ROLE_CODE FROM JTF.JTF_TTY_TERR_GRP_ROLES r WHERE r.TERR_GROUP_ID = :group_id;
• SELECT g.TERR_GROUP_ID, r.ROLE_CODE FROM JTF_TTY_TERR_GROUPS g, JTF_TTY_TERR_GRP_ROLES r WHERE g.TERR_GROUP_ID = r.TERR_GROUP_ID;
• Audit pattern: filter or order by LAST_UPDATE_DATE and LAST_UPDATED_BY to track recent configuration changes.

Because the table is satellite-leaning, reports should join it to its parent group table rather than treating it as a standalone dimension.

Related Objects

• JTF_TTY_TERR_GROUPS — parent of this table via TERR_GROUP_ID.
• JTF_TTY_ROLE_PROD_INT — references this table through TERR_GROUP_ROLE_ID.
• JTF_TTY_ROLE_ACCESS — also references this table through TERR_GROUP_ROLE_ID.
• JTF_TTY_TERR_GRP_ROLES_PK — primary key constraint on TERR_GROUP_ROLE_ID.
• JTF_TTY_TERR_GRP_ROLES_U1 — unique index on TERR_GROUP_ROLE_ID.

Together these relationships establish the table as the central role-assignment record linking territory groups to role-based product and access definitions.