Results for “jtf_rs_groups_b_u1”

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

Overview

JTF.JTF_RS_GROUPS_B is the base table within the Oracle E-Business Suite Resource Manager (JTF_RS) schema that stores general information about a given group. In EBS 12.1.1 and 12.2.2, a "group" is a logical container for resources — sales groups, service teams, approver groups, territory groups, and task owners — and the table acts as the master header record from which memberships, translations, denormalized rollups, and audit rows are derived. The _B suffix denotes the base (language-independent) table of a translated entity; the corresponding JTF_RS_GROUPS_TL table carries the language-dependent group name and description.

Physically, the table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its indexes reside in APPS_TS_TX_IDX. The ETRM data-vault classification heuristic marks this object as hub-leaning: it holds a stable, non-repeating business key (GROUP_ID) that many dependent objects reference, which is characteristic of a hub entity in a Data Vault model. It should be treated as the durable identity anchor for group resources rather than as a transactional or descriptive satellite.

Key Information Stored

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

• GROUP_ID (NUMBER) — the surrogate primary key, enforced by the unique index JTF_RS_GROUPS_B_U1 and the constraint JTF_RS_GROUPS_B_PK. This is the column referenced by virtually every dependent table and is the identifier returned by Resource Manager APIs.
• GROUP_NUMBER (VARCHAR2(30)) — the user-facing business identifier for the group, indexed non-uniquely by JTF_RS_GROUPS_B_N1. Because the ETRM documentation does not declare it unique, GROUP_NUMBER is a reporting key rather than a strict business-key candidate; GROUP_ID remains the only documented unique key.
• EXCLUSIVE_FLAG — indicates whether the group is exclusive, controlling whether a resource may belong to more than one instance of the group type.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective-dating window; each is indexed (JTF_RS_GROUPS_B_N2 and N3) to support "active as of date" queries.
• ACCOUNTING_CODE (VARCHAR2(80)) — accounting code used by Sales for revenue and credit assignment.
• EMAIL_ADDRESS — the group's e-mail address, indexed by the function-based index JTF_RS_GROUPS_B_FN1 on UPPER("EMAIL_ADDRESS") to support case-insensitive lookup.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group data isolation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the underlying ADF/BC4J entity objects.
• TIME_ZONE — default time zone associated with the group.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 (VARCHAR2(150) each) — the Descriptive Flexfield (DFF) segments for customer-defined extensions.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on resolving a group to its identifier, listing currently active groups, and joining group headers to membership or translation tables.

• Resolving a group by business number or e-mail:

  SELECT group_id, group_number, exclusive_flag FROM jtf.jtf_rs_groups_b WHERE group_number = :p_number;

• Listing active groups as of a given date:

  SELECT g.group_id, g.group_number FROM jtf.jtf_rs_groups_b g WHERE :as_of BETWEEN NVL(g.start_date_active, :as_of) AND NVL(g.end_date_active, :as_of);

• Displaying the language-specific name by joining to the translation table:

  SELECT b.group_id, t.name FROM jtf.jtf_rs_groups_b b, jtf.jtf_rs_groups_tl t WHERE b.group_id = t.group_id AND t.language = USERENV('LANG');

• Counting members per group for a team-sizing report via JTF_RS_GROUP_MEMBERS.
• Sales credit and revenue reporting through columns such as AS_SALES_CREDITS.SALESGROUP_ID or RA_CUST_TRX_LINE_SALESREPS_ALL.NON_REVENUE_SALESGROUP_ID.

Related Objects

The table is heavily referenced across JTF, CRM, Order Management, Receivables, and Service modules. The most significant dependent and related objects include:

• JTF.JTF_RS_GROUPS_TL — joined on GROUP_ID; provides translated name and description.
• JTF.JTF_RS_GROUP_MEMBERS — joined on GROUP_ID; the membership link defining which resources belong to the group.
• JTF.JTF_RS_GROUPS_DENORM — joined on GROUP_ID and PARENT_GROUP_ID; a denormalized rollup used for faster hierarchy traversal.
• JTF.JTF_RS_GRP_RELATIONS — joined on GROUP_ID and RELATED_GROUP_ID; models parent/child group relationships.
• JTF.JTF_RS_GROUPS_AUD_B — joined on GROUP_ID; the audit table capturing change history.
• AS.AS_SALES_CREDITS and AS.AS_ACCESSES_ALL_ALL — joined on SALESGROUP_ID; drive sales credit and territory access reporting.
• RA.RA_CUST_TRX_LINE_SALESREPS_ALL — joined on REVENUE_SALESGROUP_ID and NON_REVENUE_SALESGROUP_ID; links receivables sales credits to revenue and non-revenue groups.
• ASO.ASO_APR_RULE_APPROVERS and ASO_APR_APPROVAL_DET_B — joined on JTF_RS_APPROVER_GROUP_ID; define approval routing groups.

Because these relationships flow outward from GROUP_ID, any data purge, merge, or rekeying of JTF_RS_GROUPS_B must account for the many downstream foreign keys that depend on its primary key value.