Results for “jtf_rs_groups_b”

50+ results




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

Overview

JTF_RS_GROUPS_B is the base table in the JTF (CRM Foundation) schema that stores general information about a given group. In Oracle E-Business Suite 12.1.1 and 12.2.2, a "group" is a named collection of resources—sales groups, collector groups, approver groups, territory resource groups, and similar role-oriented groupings used throughout the CRM and Financials product families. Because resources in EBS are modeled in the JTF resource schema, JTF_RS_GROUPS_B is the central registry that defines each group's identity, active date range, and classification attributes.

The table is very widely referenced. Its GROUP_ID is consumed as a foreign key by over forty child tables spanning Oracle Sales (AS, ASO), Receivables (AR), Collections (AMS), Service (CS, CSS), Contracts (OKC), and the JTF resource tables themselves. In the specific context of the user's search term ra_cust_trx_line_salesreps_all, both REVENUE_SALESGROUP_ID and NON_REVENUE_SALESGROUP_ID on that table resolve to JTF_RS_GROUPS_B.GROUP_ID, meaning every sales-credit line assigned to a sales group points here.

From a heuristic Data Vault perspective (mined from the foreign-key structure), JTF_RS_GROUPS_B is hub-leaning: it holds a stable business key (GROUP_NUMBER), a surrogate primary key (GROUP_ID), and is referenced by numerous dependent tables. A Data Vault modeler would treat it as a hub, with descriptive attributes such as EXCLUSIVE_FLAG, START_DATE_ACTIVE, and END_DATE_ACTIVE residing in an associated satellite.

Key Information Stored

The table contains 31 documented columns. The most significant are:

The distinction between the surrogate key and the business key matters: GROUP_ID is system-generated and used for all foreign-key joins, while GROUP_NUMBER is the value normally presented to users and searched in queries.

Common Use Cases and Queries

The most frequent scenario involving this table is resolving sales-credit assignments on Receivables transactions. A typical query joins the sales-credit line table to the group registry:

SELECT t.trx_number, g.group_number, g.group_id
FROM ra_cust_trx_line_salesreps_all s, ra_customer_trx_all t, jtf_rs_groups_b g
WHERE s.revenue_salesgroup_id = g.group_id
AND s.customer_trx_id = t.customer_trx_id;

Other common uses include listing all active sales groups for territory assignment, auditing group membership via JTF_RS_GROUP_MEMBERS, and reporting on group-owner relationships in the AS/ASO modules. Because start and end dates gate usability, queries should test ACTIVE status using SYSDATE against START_DATE_ACTIVE and END_DATE_ACTIVE. Reporting on group-level credit splits in AR, collector assignments in AMS, and territory resource listing in JTF_TERR_RSC_ALL all originate from this base table.

Related Objects

Together these objects form the group-management backbone that supports sales crediting, collections, approvals, and territory assignment across Oracle EBS.