Search Results fnd_request_group_units




The FND_REQUEST_GROUP_UNITS table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository table that stores information about request groups and their associated units, which define the accessibility of concurrent programs, reports, and other executable functions within the application. This table plays a pivotal role in the security and functional setup of Oracle EBS by linking request groups to specific application modules, responsibilities, and executable components. Below is a detailed breakdown of its structure, purpose, and usage in Oracle EBS.

Purpose and Context

The FND_REQUEST_GROUP_UNITS table is part of the Oracle Application Object Library (FND) and serves as a junction table that associates request groups (FND_REQUEST_GROUPS) with executable units such as concurrent programs, request sets, or other functional components. Request groups are collections of executable items that determine what tasks a user can perform under a specific responsibility. This table ensures that only authorized users can access designated programs or reports based on their assigned responsibilities.

Key Columns and Structure

The table consists of several important columns, including:
  • REQUEST_GROUP_ID: A foreign key referencing the FND_REQUEST_GROUPS table, identifying the request group to which the unit belongs.
  • REQUEST_UNIT_ID: The unique identifier of the executable unit (e.g., a concurrent program or request set).
  • REQUEST_UNIT_TYPE: Specifies the type of unit (e.g., 'P' for concurrent program, 'S' for request set).
  • APPLICATION_ID: The application module to which the unit belongs, linking to FND_APPLICATION.
  • START_DATE and END_DATE: Define the active period for the unit within the request group.

Functional Role in Oracle EBS

This table is integral to the security model of Oracle EBS. When a user navigates to the "Submit Requests" or "Run Reports" screens, the system queries FND_REQUEST_GROUP_UNITS to determine which programs or sets are available under their current responsibility. This ensures that users only see and execute programs relevant to their roles, adhering to the principle of least privilege.

Integration with Other Tables

FND_REQUEST_GROUP_UNITS interacts with several other key tables:
  • FND_REQUEST_GROUPS: Defines the request groups themselves.
  • FND_CONCURRENT_PROGRAMS: Stores details of concurrent programs referenced by REQUEST_UNIT_ID when the unit type is 'P'.
  • FND_REQUEST_SETS: Contains request set definitions for unit type 'S'.

Usage in Customizations and Upgrades

During implementations or upgrades, administrators often modify this table to:
  • Add or remove programs from request groups to reflect changing business needs.
  • Audit and troubleshoot access issues by verifying unit assignments.
  • Migrate request group configurations between environments using scripts or Oracle's standard tools.

Best Practices

To maintain data integrity:
  • Use Oracle's standard APIs (e.g., FND_PROGRAM.ADD_TO_GROUP) for modifications instead of direct DML.
  • Document changes to request group assignments for audit purposes.
  • Leverage Oracle's security console or responsibility definitions screens for most administrative tasks.
In summary, FND_REQUEST_GROUP_UNITS is a foundational table in Oracle EBS that bridges request groups with executable units, enabling granular control over program accessibility. Its proper configuration is essential for maintaining a secure and functional EBS environment.