Search Results gl_application_groups_u1
Overview
GL.GL_APPLICATION_GROUPS is a small control table in the Oracle General Ledger schema that registers, per application, which application groups are enabled for that application. In practice the table is effectively a single-purpose configuration register: the GROUP_NAME column is documented as always holding the literal value 'PERIOD_STATUS', meaning the table exists to record that a given Oracle E-Business Suite application participates in General Ledger period status validation and the associated open/close period controls. It is classified as an Oracle internal object, owned by the GL schema, and delivered under FND design data SQLGL.GL_APPLICATION_GROUPS, so it is not supported for direct customer-level data manipulation outside standard Oracle Applications programs.
From a Data Vault modeling perspective, the mined metadata classifies this object as satellite-leaning. Its two-column key consists of a foreign reference to another application plus a low-cardinality descriptive attribute, which is the classic shape of a satellite table hanging off an application reference, rather than a true independent hub or a link between two distinct business entities. This is offered as a modeling suggestion only; the object itself is a normal, non-versioned transactional control table in APPS_TS_TX_DATA.
The physical definition is deliberately minimal. Only four columns are documented, with PCTFREE 10 and no PCTUSED specification, and a single unique index (GL_APPLICATION_GROUPS_U1) in the APPS_TS_TX_IDX tablespace. Because the row count is typically tiny, the table contributes almost nothing to overall database size but is frequently joined in period-close and setup diagnostics.
Key Information Stored
- APPLICATION_ID (NUMBER(15), mandatory) — the application defining column and foreign key to FND_APPLICATION. It identifies the registered application for the row.
- GROUP_NAME (VARCHAR2(30), mandatory) — the application group name; documented as always 'PERIOD_STATUS'.
- LAST_UPDATED_BY (NUMBER(15)) — standard Who column recording the user who last modified the row.
- LAST_UPDATE_DATE (DATE) — standard Who column recording the last modification timestamp.
The documented primary key is GL_APPLICATION_GROUPS_PK over (APPLICATION_ID, GROUP_NAME). The unique index GL_APPLICATION_GROUPS_U1 covers the same two columns and therefore represents the same business-key candidate set rather than a separate surrogate key; there is no independent surrogate identifier in this table. Because GROUP_NAME is effectively a constant, the practical uniqueness of a row is driven by APPLICATION_ID.
Common Use Cases and Queries
The dominant use case is setup validation: confirming whether a specific application is registered for period status processing before troubleshooting period open/close behavior, posting failures, or cross-application period synchronization. Because the row count is small, full-table queries are inexpensive and are common in diagnostics and extract-based reporting.
- Listing all registered applications:
SELECT APPLICATION_ID, GROUP_NAME FROM GL.GL_APPLICATION_GROUPS; - Resolving the application name for a given row by joining to FND_APPLICATION on APPLICATION_ID.
- Filtering to period-status participants:
WHERE GROUP_NAME = 'PERIOD_STATUS'. - Audit changes using LAST_UPDATED_BY and LAST_UPDATE_DATE.
The published query text is: SELECT APPLICATION_ID, GROUP_NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM GL.GL_APPLICATION_GROUPS;
Related Objects
- FND_APPLICATION — referenced by GL_APPLICATION_GROUPS.APPLICATION_ID; the principal join for application name and application short name.
- APPS.GL_APPLICATION_GROUPS — the APPS synonym through which EBS code and reports typically access the table.
- GL.GL_APPLICATION_GROUPS_PK / GL_APPLICATION_GROUPS_U1 — primary and unique indexes enforcing row identity.
- GL_PERIOD_STATUSES — the period status data whose processing depends on the applications registered here.
- FND_APPLICATION_TL — translated application names for reporting joins.
-
INDEX: GL.GL_APPLICATION_GROUPS_U1
12.2.2
owner:GL, object_type:INDEX, object_name:GL_APPLICATION_GROUPS_U1, status:VALID,
-
INDEX: GL.GL_APPLICATION_GROUPS_U1
12.1.1
owner:GL, object_type:INDEX, object_name:GL_APPLICATION_GROUPS_U1, status:VALID,
-
TABLE: GL.GL_APPLICATION_GROUPS
12.1.1
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_APPLICATION_GROUPS, object_name:GL_APPLICATION_GROUPS, status:VALID,
-
TABLE: GL.GL_APPLICATION_GROUPS
12.2.2
owner:GL, object_type:TABLE, fnd_design_data:SQLGL.GL_APPLICATION_GROUPS, object_name:GL_APPLICATION_GROUPS, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
eTRM - SQLGL Tables and Views
12.2.2
description: This table contains the tracking information that Golden Gate will use to launch Journal Import. ,
-
eTRM - SQLGL Tables and Views
12.1.1
description: USSGL transaction codes ,