Search Results jtf_rs_srp_groups




Overview
Explore in AI Chat

Overview

JTF_RS_SRP_GROUPS is a CRM Foundation (JTF) table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas that stores the primary resource group identifier associated with each salesperson. Its documented purpose is to persist the mapping between a sales resource and the group that is treated as that resource's primary sales group. The table is not maintained through online forms; it is populated by the concurrent program "Update Primary Sales Groups for Salespersons," which derives and refreshes the primary group designation on a scheduled or administrative basis.

The ETRM metadata records a heuristic Data Vault classification of standalone for this object. In dimensional modeling terms this suggests the table behaves primarily as a satellite-like record attached to the resource rather than as a true hub or link. Modelers should treat that classification as a modeling suggestion only, since the only documented outbound foreign key is SECURITY_GROUP_ID to FND_SECURITY_GROUPS, a standard multi-tenancy column rather than a business relationship.

Key Information Stored

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

  • SRP_GROUPS_ID — the surrogate primary key, enforced by the JTF_RS_SRP_GROUPS_PK constraint. It uniquely identifies each primary-group assignment row.
  • RESOURCE_ID — the JTF resource identifier for the salesperson; the principal business-key candidate when combined with GROUP_ID and the effective dates.
  • SALESREP_ID — the salesrep identifier, providing the sales-facing business key for the same person.
  • GROUP_ID — the group being designated as the resource's primary sales group.
  • ORG_ID — the operating unit, supporting multi-org data security and reporting.
  • USER_ID — the application user associated with the resource assignment.
  • START_DATE and END_DATE — the effective-dating window for which the group is considered primary.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns populated by the concurrent program and by user activity.

There is no second unique index documented beyond the surrogate primary key, so RESOURCE_ID, SALESREP_ID, and GROUP_ID function as business-key candidates rather than enforced uniqueness constraints.

Common Use Cases and Queries

Typical usage centres on reporting which sales group a resource currently belongs to, validating that the concurrent program has run successfully, and resolving group membership in CRM and Territory Manager integrations.

  • Current primary group per salesperson: SELECT resource_id, salesrep_id, group_id FROM jtf_rs_srp_groups WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);
  • Freshness check on the concurrent program: SELECT MAX(last_update_date) FROM jtf_rs_srp_groups;
  • Multi-org scoping: filter by ORG_ID to enforce operating unit security in custom reports.
  • Historical effective-dating: query against START_DATE/END_DATE to reconstruct prior group assignments for auditing.

Any custom SQL should join to JTF_RS_RESOURCE_EXTNS or PER_ALL_PEOPLE_F to translate RESOURCE_ID and SALESREP_ID into recognizable names.

Related Objects

  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.
  • JTF_RS_GROUPS_VL / JTF_RS_GROUPS_B — resolve GROUP_ID to a group name.
  • JTF_RS_RESOURCE_EXTNS — resource-level attributes for RESOURCE_ID.
  • JTF_RS_SALESREPS — salesperson master for SALESREP_ID.
  • PER_ALL_PEOPLE_F — HR person details behind the resource.
  • JTF_RS_GROUP_MEMBERS — broader group membership, useful alongside primary-group data.
  • Concurrent program "Update Primary Sales Groups for Salespersons" — the sole documented population mechanism.