Results for “fnd_data_groups”

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

Overview

FND_DATA_GROUPS is a core reference table in the Application Object Library (FND) of Oracle E-Business Suite, owned by the APPLSYS schema. It stores the master registry of data groups — logical groupings that associate a set of Oracle database objects (tables, sequences, and their synonyms) with one or more Oracle EBS applications and a specific ORACLE username. Data groups are the mechanism by which the EBS concurrent manager determines the database connectivity context under which a concurrent program executes, and they underpin Oracle Alert installations as well.

Each data group is defined by a name and a set of member object units, and it is bound to an application and a database user. This makes FND_DATA_GROUPS the central definition point for how runtime processes connect to and are scoped within the EBS database. Within a Data Vault modeling context, the mined relationship structure classifies this object as hub-leaning: it holds stable, uniquely identified business entities (the data groups themselves) that are referenced by multiple downstream tables, rather than being a transaction link or a descriptive satellite. This classification is a modeling suggestion based on the foreign-key topology and should be validated against specific integration requirements.

Key Information Stored

The table exposes 9 documented columns. Of these, the following are the most significant for identification, business meaning, and auditing:

• DATA_GROUP_ID — the surrogate primary key (FND_DATA_GROUPS_PK) and the value propagated to all dependent foreign-key tables. Because it is also the basis of the unique index FND_DATA_GROUPS_U1, it is a stable, system-generated identifier.
• DATA_GROUP_NAME — the user-facing business key, enforced by the unique index FND_DATA_GROUPS_U2. This is the name administrators and concurrent program definitions refer to.
• DEFAULT_GROUP_FLAG — indicates whether the data group is designated as a default, influencing which group is selected when an explicit assignment is absent.
• DESCRIPTION — free-form text documenting the purpose or scope of the data group.
• CREATED_BY, CREATION_DATE — standard EBS who-columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — who-columns capturing the most recent modification and its author.
• LAST_UPDATE_LOGIN — the login context associated with the last change, supporting audit and troubleshooting.

The surrogate key (DATA_GROUP_ID) and the business-key candidate (DATA_GROUP_NAME) are distinct; integrators should resolve references using the surrogate key wherever possible, while presentation layers typically present the name.

Common Use Cases and Queries

Typical scenarios include auditing data group definitions, resolving which data group a concurrent queue or alert installation uses, and reconciling data group membership. A foundational query returns the group identity and status:

• SELECT data_group_id, data_group_name, default_group_flag, description FROM fnd_data_groups ORDER BY data_group_name;
• Locating the default group: SELECT data_group_id, data_group_name FROM fnd_data_groups WHERE default_group_flag = 'Y';
• Resolving a group by name: SELECT data_group_id FROM fnd_data_groups WHERE data_group_name = :name;
• Auditing recent changes: SELECT data_group_name, last_updated_by, last_update_date FROM fnd_data_groups WHERE last_update_date > SYSDATE - 30;
• Inspecting membership: join to FND_DATA_GROUP_UNITS on DATA_GROUP_ID to list the objects belonging to each group.

Reporting use cases include validation reports confirming that every data group has at least one unit, and impact analysis before modifying a data group that is referenced by an active concurrent queue.

Related Objects

FND_DATA_GROUPS functions as a referenced parent. The documented foreign-key relationships identify the principal dependent objects, each joined on DATA_GROUP_ID:

• FND_DATA_GROUP_UNITS — child table (FND_DATA_GROUP_UNITS.DATA_GROUP_ID) defining the constituent objects of a group; the most direct dependency for membership analysis.
• FND_CONCURRENT_QUEUES — stores the data group assigned to each concurrent queue (FND_CONCURRENT_QUEUES.DATA_GROUP_ID), governing the connectivity context for concurrent processing.
• ALR_ALERT_INSTALLATIONS — records the data group tied to an Oracle Alert installation (ALR_ALERT_INSTALLATIONS.DATA_GROUP_ID).

Beyond these, administrators commonly correlate FND_DATA_GROUPS with FND_APPLICATION and FND_ORACLE_USERID, which supply the application and database user context, and with FND_CONCURRENT_PROGRAMS when tracing execution configuration. Together, these relationships establish FND_DATA_GROUPS as the anchor of the data group registration model across the Application Object Library.