Results for “jtf_fm_groups_all”

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

Overview

JTF_FM_GROUPS_ALL is a CRM Foundation (JTF) table that stores information about fulfillment groups. Fulfillment groups define the destinations and delivery channels used by Oracle's fulfillment middleware when a CRM or EBS application dispatches outbound documents, notifications, messages, or interactive reports. Each row represents a fulfillment group header, recording its name, optional descriptive text, owning server, and audit/security context.

The table resides in the JTF schema and is classified as a hub-leaning object under the heuristic Data Vault classification mined from its foreign key structure. Interpreted as a modeling suggestion, this classification indicates that JTF_FM_GROUPS_ALL acts as a central reference or master entity (hub) around which several dependent detail tables cluster. The child tables JTF_FM_EMAIL_JTF_FM_GROUPS, JTF_FM_FAX_JTF_FM_GROUPS, JTF_FM_FILE_JTF_FM_GROUPS, JTF_FM_PRINTER_JTF_FM_GROUPS, and JTF_FM_GROUP_FND_USER all reference this table through GROUP_ID, confirming its role as the parent in the fulfillment group configuration hierarchy.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are:

• GROUP_ID — the surrogate primary key, enforced by JTF_FM_GROUPS_ALL_PK and uniquely indexed by JTF_FM_GROUPS_ALL_U1. This is also the join key consumed by all dependent fulfillment channel tables.
• GROUP_NAME — business-key candidate that holds the user-visible name of the fulfillment group.
• GROUP_DESC — free-text description of the group's purpose.
• SERVER_ID — reference to the server context associated with the group.
• ORG_ID — Multi-Org operating unit identifier, enabling the table to be partitioned by organization in a multi-org implementation.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing CRM security group scoping. This is the only documented outbound foreign key from the table.
• F_DELETEDFLAG — soft-delete indicator, allowing rows to be logically retired without physical deletion.
• OBJECT_VERSION_NUMBER — optimistic locking column, used by the OAF framework to detect concurrent updates.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture WHO/WHEN information required by EBS audit conventions.

Common Use Cases and Queries

Because JTF_FM_GROUPS_ALL is the header table for fulfillment configuration, typical queries retrieve group names and descriptions and then drill into the specific channels (email, fax, file, printer, or FND user) that are linked via GROUP_ID. A common reporting pattern joins the header to each child table to display the complete delivery definition for a group.

For example, to list active email fulfillment groups:

SELECT g.group_id, g.group_name, g.group_desc
FROM   jtf_fm_groups_all g,
       jtf_fm_email_jtf_fm_groups e
WHERE  g.group_id = e.group_id
AND    NVL(g.f_deletedflag,'N') = 'N';

Administrators also query the table when troubleshooting why a notification was routed incorrectly, verifying the SERVER_ID and ORG_ID combination, or auditing SECURITY_GROUP_ID assignments across operating units. Because the table carries ORG_ID, queries in a Multi-Org environment must be executed with the appropriate org context (or filtered explicitly) to avoid cross-organization data leakage.

Related Objects

The following objects are most significant in relation to JTF_FM_GROUPS_ALL:

• JTF_FM_EMAIL_JTF_FM_GROUPS — email channel configuration; joined on GROUP_ID.
• JTF_FM_FAX_JTF_FM_GROUPS — fax channel configuration; joined on GROUP_ID.
• JTF_FM_FILE_JTF_FM_GROUPS — file destination configuration; joined on GROUP_ID.
• JTF_FM_PRINTER_JTF_FM_GROUPS — printer destination configuration; joined on GROUP_ID.
• JTF_FM_GROUP_FND_USER — maps fulfillment groups to FND users; joined on GROUP_ID.
• FND_SECURITY_GROUPS — the parent security group referenced by SECURITY_GROUP_ID, defining the CRM security context in which the fulfillment group is visible.

Together these objects form the fulfillment group configuration model used by CRM Foundation to drive outbound delivery routing.