Results for “fnd_conc_stat_groups”

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

Overview

FND_CONC_STAT_GROUPS is a configuration table owned by the APPLSYS schema within the FND — Application Object Library product of Oracle E-Business Suite. It stores the definition of concurrent program status groups, which are the named groupings used by the Concurrent Manager to classify and organize concurrent requests into logical status categories. These status groups determine how request states are presented to end users, how the Concurrent Managers prioritize and report work, and how status-driven filtering behaves across the concurrent processing infrastructure. In EBS 12.1.1 and 12.2.2, the physical definition remains stable: seven documented columns, a primary key named FND_CONC_STAT_GROUPS_PK on GROUP_CODE, and a unique index FND_CONC_STAT_GROUPS_U1 also on GROUP_CODE.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as a standalone Data Vault component. Under a Data Vault model, that constitutes a hub recommendation: the table carries a stable, unique business key (GROUP_CODE) with system-maintained descriptive attributes rather than dependent transactional detail. It is best treated as a reference or dimension-style hub for status group identity.

Key Information Stored

The table holds a small, configuration-oriented column set. The documented columns are:

• GROUP_CODE — the business key and primary key. It uniquely identifies each status group and is the value referenced by dependent concurrent processing objects.
• ENABLED — a flag controlling whether the status group is active. Disabled groups are ignored by the Concurrent Manager when classifying requests.
• CREATION_DATE — the date the group definition was created.
• CREATED_BY — the user identifier that created the record.
• LAST_UPDATE_DATE — the timestamp of the most recent modification; critical for audit and delta extraction.
• LAST_UPDATED_BY — the user identifier responsible for the last change.
• LAST_UPDATE_LOGIN — the login session under which the last update occurred.

GROUP_CODE serves simultaneously as the surrogate primary key (FND_CONC_STAT_GROUPS_PK) and as the unique business-key candidate (FND_CONC_STAT_GROUPS_U1). The remaining six columns are standard Oracle Applications audit and control attributes, following the WHO column convention used across APPLSYS.

Common Use Cases and Queries

Typical use cases center on auditing, concurrent manager troubleshooting, and integration. A DBA or developer may enumerate active status groups to diagnose why requests are not being picked up by a manager, or to validate that a customization expects a specific group code.

A simple listing of enabled groups:

• SELECT GROUP_CODE, ENABLED, LAST_UPDATE_DATE FROM APPLSYS.FND_CONC_STAT_GROUPS WHERE ENABLED = 'Y';

An audit query identifying recent configuration changes relies on the WHO columns:

• SELECT GROUP_CODE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN FROM APPLSYS.FND_CONC_STAT_GROUPS ORDER BY LAST_UPDATE_DATE DESC;

Because GROUP_CODE is the sole key, joins to dependent concurrent processing tables are performed on that column. Reporting scenarios frequently combine this table with concurrent request and status tables to summarize request volumes by status group and manager.

Related Objects

The ETRM metadata records no foreign-key relationships for FND_CONC_STAT_GROUPS; the heuristic classification is standalone. In practice, the GROUP_CODE value participates in the broader concurrent processing data model. Significant related objects include:

• FND_CONCURRENT_PROGRAMS — concurrent program definitions that may be associated with status grouping logic.
• FND_CONCURRENT_REQUESTS — the request records whose status values are categorized through the group definitions.
• FND_CONCURRENT_QUEUES — the managers that process requests organized under status groups.
• FND_CONCURRENT_PROCESSES — runtime process records tied to the concurrent pipeline.
• FND_CONC_STAT_GROUPS_TL — the translatable attributes variant, where present, sharing GROUP_CODE as the join key.
• FND_RUN_REQUESTS or equivalent request-run views that surface status information to end users.

Joins in all cases should be validated against the local ETRM or data dictionary, since the documented relationship set for this table is limited to its own primary and unique key constraints.