Search Results fnd_data_groups_standard_view

Overview

FND_DATA_GROUPS_STANDARD_VIEW is a read-only database view owned by the APPS schema in Oracle E-Business Suite, residing in the FND (Application Object Library) product. Its purpose is to expose the set of Oracle EBS data groups that are classified as "Standard" data groups — that is, the predefined, Oracle-delivered data groups rather than customer-defined or custom ones. In Oracle EBS terminology, a data group is a logical grouping of Oracle Applications database objects (tables, views, sequences) that can be assigned to an application and associated with responsibilities and menus for security and access control.

In both 12.1.1 and 12.2.2, the view serves primarily as a reporting and integration convenience. It provides a normalized, ready-to-query representation of standard data groups without requiring the calling code or report to implement the DECODE logic and lookup join itself. The view's status is VALID, indicating it is a supported, compilable object in the ETRM catalog, and it is broadly used across AOL-related diagnostics, security review queries, and upgrade/integration scripts.

Underlying Base Objects

The view is defined over two primary objects: FND_DATA_GROUPS and FND_LOOKUPS. Per the documented ETRM 12.2.2 metadata, the referenced base objects are FND_DATA_GROUPS (accessed via a synonym), FND_LOOKUPS (which itself is a view in the APPS schema), and the FND_GLOBAL package. FND_DATA_GROUPS is the master table that stores every data group definition, including both Oracle-seeded entries and any customer-created groups. FND_LOOKUPS supplies the lookup meaning for the special code 'STANDARD' under the lookup type 'FND_STANDARD'.

The join between these two objects is effectively a filter-and-translate operation: rows from FND_DATA_GROUPS are retained, and the lookup is used to substitute a human-readable meaning for the data group name when the record represents the zero-ID standard group. Because FND_LOOKUPS is referenced without a direct keyed join to DATA_GROUP_ID, the view relies on the WHERE clause constant comparison to restrict the lookup side to the single 'STANDARD' code.

Key Columns

• DATA_GROUP_ID — The numeric primary identifier for the data group. A value of 0 is significant: it denotes the built-in "Standard" data group, which is the default grouping used when no other data group is explicitly designated.
• DEFAULT_GROUP_FLAG — A flag indicating whether the data group is the default group for its application. This helps reports determine which group applies automatically when a responsibility or application does not specify one.
• DESCRIPTION — The free-text description of the data group as maintained in FND_DATA_GROUPS.
• DATA_GROUP_NAME — The name of the data group. Importantly, this column is derived: for DATA_GROUP_ID = 0, the view substitutes the lookup meaning retrieved from FND_LOOKUPS (LOOKUP_TYPE = 'FND_STANDARD', LOOKUP_CODE = 'STANDARD') rather than the raw DG.DATA_GROUP_NAME. For all other rows, the stored data group name is returned unchanged.

Common Use Cases and Queries

The view is commonly used to enumerate standard data groups for security audits, to resolve the display name of the default group, and to cross-check data group assignments against applications and responsibilities. A representative query retrieving all standard data groups is:

SELECT data_group_id, data_group_name, description, default_group_flag FROM apps.fnd_data_groups_standard_view;

To isolate the default data group for a given context, a filter on DEFAULT_GROUP_FLAG is typical:

SELECT data_group_id, data_group_name FROM apps.fnd_data_groups_standard_view WHERE default_group_flag = 'Y';

Because the view resolves the zero-ID group name through the FND_STANDARD lookup, it is also useful when validating that the 'FND_STANDARD' lookup entry exists and is correctly configured — a missing or inactive lookup may result in an unexpected or null meaning for the standard row. When combining the view with responsibility or application metadata, join on DATA_GROUP_ID against the corresponding FND assignment tables to produce a complete access-control report. As with all APPS views, query it through the APPS schema or an appropriately privileged account, and treat the output as read-only reference data.