Search Results fnd_request_group_units_pk




Overview
Explore in AI Chat

Overview

FND_REQUEST_GROUP_UNITS is a core Oracle Application Object Library (FND) table in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the constituent members of a request security group, storing the individual concurrent programs and request sets that belong to each request group. Request groups are the primary mechanism by which Oracle EBS administrators control which concurrent programs and request sets a given responsibility, user, or application can submit. This table is therefore foundational to concurrency security and access provisioning across the entire EBS instance.

The table resides in the APPLSYS schema and is owned by the FND product. Based on the foreign key topology—where the table resolves many-to-many relationships between request groups and their member units—the heuristic Data Vault classification is link. This classification is a modeling suggestion derived from the FK structure; it indicates that the object primarily records associations between parent entities rather than describing an entity itself.

Key Information Stored

The table contains 11 documented columns and is governed by the primary key constraint FND_REQUEST_GROUP_UNITS_PK, defined over APPLICATION_ID, REQUEST_GROUP_ID, REQUEST_UNIT_TYPE, UNIT_APPLICATION_ID, and REQUEST_UNIT_ID. A secondary unique index, FND_REQUEST_GROUP_UNITS_U1, extends the business key with ZD_EDITION_NAME. The most significant columns are:

  • APPLICATION_ID — Identifies the application owning the request group; forms part of the FK to FND_REQUEST_GROUPS.
  • REQUEST_GROUP_ID — The parent request group to which a unit is assigned.
  • REQUEST_UNIT_TYPE — Distinguishes whether the member is a concurrent program or a request set.
  • UNIT_APPLICATION_ID — The application owning the member unit (program or set); participates in FKs to FND_CONCURRENT_PROGRAMS, FND_REQUEST_SETS, and FND_APPLICATION.
  • REQUEST_UNIT_ID — The identifier of the specific concurrent program or request set included in the group.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit (WHO) columns tracking creation and modification.
  • ZD_EDITION_NAME — Editioning column supporting EBS online patching (12.2.x), allowing multiple editions of the same logical row.

The five-column primary key serves as the surrogate/business identifier, while the U1 unique index represents the fully qualified business-key candidate when the edition is considered.

Common Use Cases and Queries

Typical use cases include auditing which concurrent programs are exposed through a given request group, validating security configurations after a patch or upgrade, and reporting on the programs and request sets available to a responsibility. A representative query listing all programs in a group is:

  • SELECT rgu.request_unit_id, rgu.request_unit_type, cp.concurrent_program_name, cp.user_concurrent_program_name FROM fnd_request_group_units rgu, fnd_concurrent_programs_vl cp WHERE rgu.request_group_id = :group_id AND rgu.request_unit_type = 'P' AND rgu.unit_application_id = cp.application_id AND rgu.request_unit_id = cp.concurrent_program_id;
  • Joining to FND_REQUEST_GROUPS to resolve group names for a named group: ... WHERE rgu.application_id = rg.application_id AND rgu.request_group_id = rg.request_group_id AND rg.request_group_name = :name;
  • Detecting duplicate or orphaned memberships by grouping on the composite key and comparing against FND_REQUEST_SETS for request-set units.

These patterns support security reviews, responsibility-to-program traceability, and impact analysis before applying changes to request groups.

Related Objects

  • FND_REQUEST_GROUPS — Parent table keyed on APPLICATION_ID and REQUEST_GROUP_ID; defines the group itself.
  • FND_CONCURRENT_PROGRAMS — Referenced via UNIT_APPLICATION_ID and REQUEST_UNIT_ID when the unit is a concurrent program.
  • FND_REQUEST_SETS — Referenced via UNIT_APPLICATION_ID and REQUEST_UNIT_ID when the unit is a request set.
  • FND_APPLICATION — Resolves UNIT_APPLICATION_ID to the owning application for reporting.
  • FND_REQUEST_GROUP_UNITS_U1 — Unique index supporting the extended business key including ZD_EDITION_NAME.

Together these objects form the relational fabric that governs concurrent program security in Oracle EBS.