Results for “fnd_data_group_units”

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

Overview

FND_DATA_GROUP_UNITS is an Application Object Library (FND) configuration table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It records the Oracle database accounts (schemas) that are assigned to each data group defined in the EBS environment. A data group represents a logical grouping of Oracle Applications that share a common APPS database account context; FND_DATA_GROUP_UNITS is the association table that resolves which Oracle user ID maps to which application within a given data group. Responsibilities reference data groups through this structure to determine the runtime APPS schema context for concurrent programs, forms sessions, and database connectivity.

Because the table stores the intersection between data groups, applications, and Oracle schema accounts, the metadata suggests a satellite-leaning Data Vault classification. The primary key is composite and consists of a foreign reference plus a business discriminator, and the ORACLE_ID and DESCRIPTION attributes are classic descriptive payload rather than structural hub keys. In practice, FND_DATA_GROUP_UNITS behaves as a detail or cross-reference table that hangs off FND_DATA_GROUPS.

Key Information Stored

The documented table contains nine columns. The most consequential are:

• APPLICATION_ID — Identifies the Oracle Application assigned to the data group. Part of the composite primary key and of the unique index FND_DATA_GROUP_UNITS_U1.
• DATA_GROUP_ID — Identifies the parent data group. The other component of the composite primary key and the leading column of the unique index.
• ORACLE_ID — The Oracle user/schema account associated with the application within the data group. This is the column joined to FND_ORACLE_USERID.
• DESCRIPTION — Free-text description of the unit record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and concurrency information for each row.

The primary key FND_DATA_GROUP_UNITS_PK is defined on (APPLICATION_ID, DATA_GROUP_ID). A separate unique index, FND_DATA_GROUP_UNITS_U1, is defined on (DATA_GROUP_ID, APPLICATION_ID) and is the documented business-key candidate — the order reversed relative to the PK but logically equivalent. There is no single-column surrogate key; the pair of foreign references forms the natural identifier.

Common Use Cases and Queries

Administrators and DBAs interrogate this table when diagnosing APPS schema connectivity, verifying which Oracle account is used for a given application in a data group, or troubleshooting responsibility access issues. A typical query resolves the Oracle schema name for a data group:

• Join FND_DATA_GROUP_UNITS to FND_ORACLE_USERID on ORACLE_ID to obtain the ORACLE_USERNAME associated with an APPLICATION_ID.
• Join to FND_DATA_GROUPS on DATA_GROUP_ID to retrieve the data group name for reporting by group.
• Trace from FND_RESPONSIBILITY via DATA_GROUP_APPLICATION_ID and DATA_GROUP_ID to enumerate the units active for a responsibility's data group.
• Audit configuration drift in cloned or multi-node environments by comparing unit rows across instances.

Because the table is configuration metadata rather than transactional data, row volume is small and query performance is rarely a concern; standard WHERE predicates on DATA_GROUP_ID or APPLICATION_ID suffice.

Related Objects

• FND_DATA_GROUPS — Parent definition of data groups; joined on FND_DATA_GROUP_UNITS.DATA_GROUP_ID.
• FND_ORACLE_USERID — Defines the Oracle schema accounts; joined on FND_DATA_GROUP_UNITS.ORACLE_ID.
• FND_RESPONSIBILITY — References this table through DATA_GROUP_APPLICATION_ID and DATA_GROUP_ID, linking responsibilities to data group unit context.
• FND_APPLICATION — Source of APPLICATION_ID values used in the primary key.
• FND_DATA_GROUP_UNITS_PK / FND_DATA_GROUP_UNITS_U1 — Primary and unique indexes enforcing row identity and business uniqueness.

Together these objects form the data group and Oracle account model that underpins EBS application connectivity and responsibility-based access control.