Results for “jtf_tty_role_access”

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

Overview

The JTF.JTF_TTY_ROLE_ACCESS table is a CRM Foundation data object in Oracle E-Business Suite, residing in the JTF schema and validated across both 12.1.1 and 12.2.2 releases. Its documented purpose is to store role access for territory groups. In the Territory Management model, territories are organised into territory groups, and each territory group is associated with one or more CRM roles. This table captures the additional access rules that determine how those roles may interact with the territory group — for example, granting transaction-level visibility or restricting access by an access code.

From a Data Vault modelling perspective, the mined foreign-key structure classifies this table heuristically as standalone. It carries its own surrogate key and does not exhibit the multi-parent dependency pattern typical of a link table; it can therefore be treated as a hub-like or satellite-like entity anchoring access definitions. Note that the vault classification is heuristic and derived from FK topology rather than an explicit design declaration.

Key Information Stored

The table is documented with eleven columns. The most significant are:

• TERR_GROUP_ROLE_ACCESS_ID — the surrogate primary key and the column backing the unique index JTF_TTY_ROLE_ACCESS_U1, making it the business-key candidate for row-level identification.
• TERR_GROUP_ROLE_ID — foreign key referencing JTF_TTY_TERR_GRP_ROLES, linking each access rule to a specific territory group / role combination.
• ACCESS_TYPE — classifies the nature of the access grant applied to the territory group role.
• ACCESS_CODE — the specific access code value associated with the rule.
• TRANS_ACCESS_CODE — a transaction-oriented access code, typically governing access at the transactional level within the territory.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns recording row provenance and last modification context.

Common Use Cases and Queries

Typical usage centres on auditing and reporting which roles hold access to which territory groups, and how that access is typed. A representative query joins the access table to its parent role assignment:

• Access inventory by territory group: join JTF_TTY_ROLE_ACCESS to JTF_TTY_TERR_GRP_ROLES on TERR_GROUP_ROLE_ID to list every access rule per group role.
• Security audit: filter on ACCESS_TYPE or ACCESS_CODE to identify roles granted broad or transaction-level access.
• Change tracking: use LAST_UPDATED_BY and LAST_UPDATE_DATE to report recently modified access definitions.
• Concurrency diagnostics: inspect OBJECT_VERSION_NUMBER where OAF screens raise stale-row errors during territory administration.

A simple pattern is: SELECT ra.TERR_GROUP_ROLE_ACCESS_ID, ra.TERR_GROUP_ROLE_ID, ra.ACCESS_TYPE, ra.ACCESS_CODE FROM JTF.JTF_TTY_ROLE_ACCESS ra WHERE ra.TERR_GROUP_ROLE_ID = :role_id;

Related Objects

The principal related objects are:

• JTF_TTY_TERR_GRP_ROLES — parent table referenced by TERR_GROUP_ROLE_ID; the mandatory join target.
• JTF_TTY_TERR_GRPS — territory group definitions, reached indirectly through the group-roles table.
• JTF_TTY_TERRITORIES — territory definitions participating in group assignments.
• JTF_TTY_TERR_GRP_ROLE_ACCESS views or dependent access screens that surface this data in the Territory Management UI.
• FND_USER / FND_RESPONSIBILITY — CRM roles resolved through the role model, providing the identity context for granted access.

Together these objects support territory administration, access provisioning, and security reporting within CRM Foundation.