Results for “fnd_request_groups”

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

Overview

FND_REQUEST_GROUPS is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of report security groups, which are the logical containers used by the Concurrent Manager and Oracle Reports to partition concurrent programs and request sets into access-controlled groupings. Each row represents one request group, identified within an application, and serves as the parent definition to which individual concurrent programs, request sets, and other executable units are attached. Responsibility-level security then determines which request groups a given user can run, thereby controlling which concurrent programs are visible and executable.

From a dimensional modeling perspective, the ETRM relationship metadata classifies this object as hub-leaning. This heuristic suggests that FND_REQUEST_GROUPS functions as a hub entity in a Data Vault model: it holds the durable business key of a request group, and other structures (such as assignment or membership tables) act as links or satellites referencing it. The table is not a transactional or event table; it is reference and setup data whose attributes change infrequently.

Key Information Stored

The table contains 11 documented columns. The most significant of these are described below.

• APPLICATION_ID — The owning application (foreign key to FND_APPLICATION). Part of every key on the table; a request group is always scoped to a single application.
• REQUEST_GROUP_ID — The internal numeric identifier for the request group. Together with APPLICATION_ID, forms the surrogate primary key FND_REQUEST_GROUPS_PK and is the value carried by dependent tables.
• REQUEST_GROUP_NAME — The user-facing name of the report security group, unique within an application. This is the primary business-key candidate, reflected in unique index FND_REQUEST_GROUPS_U2 (APPLICATION_ID, REQUEST_GROUP_NAME, ZD_EDITION_NAME).
• REQUEST_GROUP_CODE — A short code associated with the group, used for programmatic identification and reference in concurrent program definitions.
• DESCRIPTION — Free-text description of the group's purpose and content, used in setup and administrative reporting.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard FND audit columns capturing who created or last modified the row and when. These support change tracking, auditing, and incremental extraction in data warehouse loads.
• ZD_EDITION_NAME — The editioning column introduced for Online Patching in EBS 12.2.x, allowing multiple editions of the same logical row to coexist during patching cycles. It forms part of both unique indexes FND_REQUEST_GROUPS_U1 and FND_REQUEST_GROUPS_U2.

The two documented unique indexes distinguish the surrogate key path (U1: APPLICATION_ID, REQUEST_GROUP_ID, ZD_EDITION_NAME) from the business-key path (U2: APPLICATION_ID, REQUEST_GROUP_NAME, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical uses of this table center on security audits, responsibility configuration reporting, and concurrent program assignment analysis.

• Listing all request groups for a given application:
  SELECT request_group_id, request_group_name, description FROM fnd_request_groups WHERE application_id = :app_id ORDER BY request_group_name;
• Resolving the request group assigned to a responsibility, joining through FND_RESPONSIBILITY on GROUP_APPLICATION_ID and REQUEST_GROUP_ID.
• Identifying stale or unused groups by checking for the absence of child rows in FND_REQUEST_GROUP_UNITS.
• Audit reporting on recent setup changes using LAST_UPDATE_DATE and LAST_UPDATED_BY, typically joined to FND_USER for the modifier's name.
• Data warehouse extraction keyed on the APPLICATION_ID and REQUEST_GROUP_ID hub key, with descriptive attributes loaded as a satellite.

Related Objects

The following objects participate in the documented relationships:

• FND_APPLICATION — Referenced by FND_REQUEST_GROUPS.APPLICATION_ID; provides the application name and short name for the owning product.
• FND_REQUEST_GROUP_UNITS — The child assignment table linking FND_REQUEST_GROUPS.APPLICATION_ID and REQUEST_GROUP_ID to individual units (concurrent programs, request sets). This is the principal link structure in a Data Vault sense.
• FND_RESPONSIBILITY — References this table via GROUP_APPLICATION_ID and REQUEST_GROUP_ID, binding a responsibility to its request group and thus driving user-level menu and program access.
• FND_CONCURRENT_PROGRAMS — Concurrent program definitions that are surfaced to users only when their containing units are attached to a request group available to the user's responsibility.
• FND_USER — Joined via CREATED_BY or LAST_UPDATED_BY for audit and setup reporting.

Together these objects form the request security chain: application → request group → group units → concurrent programs, with responsibilities acting as the access grant point.