Search Results jtf_fm_group_user_pk

Overview

JTF_FM_GROUP_FND_USER is a cross-reference (association) table owned by the JTF schema within the CRM Foundation product module of Oracle E-Business Suite. Its documented role is to store mappings between "groups" and "agents" — that is, which FND users belong to which JTF functional/resource groups. In EBS 12.1.1 and 12.2.2 the object is reported as VALID, and the documented physical schema (ETRM 12.2.2) contains ten columns.

Under the heuristic Data Vault classification provided in the metadata, this table is modeled as a link. That classification is consistent with the object's design: it holds no descriptive attributes of its own beyond audit and multi-tenancy columns, and its identity is entirely defined by the combination of two foreign keys. In a Data Vault sense it resolves a many-to-many relationship between the group hub (JTF_FM_GROUPS_ALL) and the user hub (FND_USER), rather than acting as a hub or a descriptive satellite.

Key Information Stored

The documented primary key is JTF_FM_GROUP_FND_USER_PK, composed of GROUP_ID and USER_ID. This composite key is the true business identifier of each row: a single row asserts that a given agent (USER_ID) is a member of a given group (GROUP_ID). An alternate declaration, JTF_FM_GROUP_USER_PK, is also documented over the same two columns, reinforcing that the pairing is unique and that no surrogate single-column key exists.

• GROUP_ID — foreign key to JTF_FM_GROUPS_ALL; identifies the group or resource pool.
• USER_ID — foreign key to FND_USER; identifies the assigned agent or user.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; supports multi-tenant / security-group partitioning of the membership row.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit trail columns recording when, by whom, and through which login the row was last changed.
• CREATION_DATE, CREATED_BY — standard EBS creation audit columns.
• F_DELETEDFLAG — soft-delete / logical deletion indicator used by the JTF framework to retire a membership without physically removing the row.

Notably, the table carries no start/end date or primary-flag columns in the documented schema, so effective-dating of membership is not represented here.

Common Use Cases and Queries

The most frequent use is resolving which agents belong to a group, and conversely which groups a given agent belongs to. Typical reporting patterns include:

• Listing members of a group: SELECT user_id FROM jtf.jtf_fm_group_fnd_user WHERE group_id = :p_group_id AND NVL(f_deletedflag,'N') = 'N';
• Listing groups for an agent: SELECT group_id FROM jtf.jtf_fm_group_fnd_user WHERE user_id = :p_user_id AND NVL(f_deletedflag,'N') = 'N';
• Joining to FND_USER for agent names and to JTF_FM_GROUPS_ALL for group names to produce membership rosters, workload or capacity reports, and group-based assignment analyses.
• Raising data-fix scripts to add or remove agent-to-group associations, always respecting SECURITY_GROUP_ID and the soft-delete flag rather than issuing physical deletes.

Because the table is a pure intersection link, extracting GROUP_ID and USER_ID pairs and loading them into a Data Vault link table is straightforward, and any change data capture should key on the composite primary key.

Related Objects

The FK metadata identifies the principal related objects and join columns:

• JTF_FM_GROUPS_ALL — referenced by GROUP_ID; the group/resource master.
• FND_USER — referenced by USER_ID; the application user/agent master.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; controls multi-tenant visibility of the link row.

Additional relationships are implied by the same FK definitions appearing under the two constraint names, and by the shared primary key columns GROUP_ID and USER_ID, which are the natural join predicates when this table is combined with its parent group and user tables in CRM Foundation queries.