Results for “group_name”

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

Overview

GL_APPLICATION_GROUPS is a General Ledger reference table in the GL schema that identifies the application product groups authorized to use Oracle General Ledger accounting periods. Each row associates an Oracle E-Business Suite application (registered in FND_APPLICATION) with a named group, allowing the accounting calendar and period status logic of GL to be shared across multiple products. The table therefore acts as a bridge between the application registry and the GL period control framework, and it is referenced whenever EBS determines which applications participate in the open/close cycle of an accounting period.

The object is owned by the GL schema and is marked VALID in the ETRM 12.2.2 documentation. Under the heuristic Data Vault classification mined from its foreign key structure, the table is assessed as satellite-leaning: it primarily stores descriptive attributes (the group name) that qualify a parent application entity, rather than serving as a pure hub or a many-to-many link. This classification is a modeling suggestion only; functionally the table behaves as a lightweight association between applications and GL period-sharing groups.

Key Information Stored

The documented physical schema lists four columns, of which the following are significant:

• APPLICATION_ID — The numeric identifier of the Oracle EBS application, foreign-keyed to FND_APPLICATION.APPLICATION_ID. It establishes which product owns or participates in the group.
• GROUP_NAME — The textual name of the application product group. Combined with APPLICATION_ID, it forms the business key of the record.
• LAST_UPDATED_BY — Audit column recording the user who last modified the row.
• LAST_UPDATE_DATE — Audit column recording the timestamp of the last modification.

The primary key is GL_APPLICATION_GROUPS_PK, defined on the composite of (APPLICATION_ID, GROUP_NAME). A unique index, GL_APPLICATION_GROUPS_U1, is documented on the same column pair, confirming that (APPLICATION_ID, GROUP_NAME) is the business-key candidate enforcing uniqueness. Because the table has no single-column surrogate key, the composite pair serves both as primary key and as the natural business identifier.

Common Use Cases and Queries

Typical scenarios involve auditing which applications share GL accounting periods and resolving application names for period-close reporting. A common query joins the table to FND_APPLICATION to translate APPLICATION_ID into an application short name:

• Listing all groups for an application: SELECT group_name FROM gl_application_groups WHERE application_id = :app_id;
• Resolving application names: SELECT g.group_name, a.application_short_name FROM gl_application_groups g, fnd_application a WHERE g.application_id = a.application_id;
• Reporting recently changed assignments using LAST_UPDATE_DATE and LAST_UPDATED_BY for audit trails.

These queries support period-close validation, security reviews of which products touch GL calendars, and reconciliation of application registration data after upgrades or clones.

Related Objects

• FND_APPLICATION — Referenced via GL_APPLICATION_GROUPS.APPLICATION_ID = FND_APPLICATION.APPLICATION_ID; the principal parent of this table.
• GL_PERIODS — The GL accounting period definitions whose usage is scoped by these application groups.
• GL_PERIOD_STATUSES — Period open/close status records governed by the participating applications.
• GL_LEDGERS — Ledger definitions that depend on GL period control for the assigned applications.
• FND_APPLICATION_TL — Translation table supplying application display names for reporting joins.

Together these objects form the period-management chain: FND_APPLICATION identifies the products, GL_APPLICATION_GROUPS groups them, and GL_PERIODS and GL_PERIOD_STATUSES apply calendar and status rules to the resulting set.