Search Results fnd_request_group_units_n1




Overview

APPLSYS.FND_REQUEST_GROUP_UNITS is a seed-data table within the Oracle E-Business Suite Application Object Library (FND) schema. It stores the individual members that make up a Request Security Group — that is, the reports, report sets, and applications that have been assigned to a given report security group through the Define Report Security Group form. Each row represents one such assignment, linking a security group to exactly one request unit. Oracle Application Object Library reads this table at runtime to determine which concurrent programs and request sets a responsibility's report security group makes available to the user.

The table resides in the APPS_TS_SEED tablespace, consistent with its role as setup/seed data propagated through the FND design data layer (FND.FND_REQUEST_GROUP_UNITS). The ETRM metadata records a Data Vault classification of "link" for this object. This classification is a heuristic modeling suggestion mined from the foreign-key structure: FND_REQUEST_GROUP_UNITS behaves as an associative entity resolving a many-to-many relationship between report security groups and the request units (programs, sets, and applications) they authorize, rather than as a standalone hub or a descriptive satellite.

Key Information Stored

The table contains eleven documented columns. The most significant are the five that constitute the primary key and business key:

  • APPLICATION_ID (NUMBER) — identifies the application that owns the report security group; the first component of the composite key and foreign key to FND_REQUEST_GROUPS.
  • REQUEST_GROUP_ID (NUMBER) — the report security group identifier. Together with APPLICATION_ID it identifies the parent group.
  • REQUEST_UNIT_TYPE (VARCHAR2) — a flag indicating the nature of the included unit: "A" for an application (all its reports and sets), "P" for a report, or "S" for a set.
  • UNIT_APPLICATION_ID (NUMBER) — the application identifier of the report, report set, or application being included.
  • REQUEST_UNIT_ID (NUMBER) — the identifier of the specific report, report set, or application included in the group.

The surrogate primary key, FND_REQUEST_GROUP_UNITS_PK, is defined over all five of these columns. The unique index FND_REQUEST_GROUP_UNITS_U1 covers the same five columns plus ZD_EDITION_NAME, confirming the five-column tuple as the business-key candidate and enforcing that a given unit may appear only once per security group. The remaining documented columns are the standard WHO audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — plus ZD_EDITION_NAME, the editioning column introduced for online patching in EBS 12.2.

Common Use Cases and Queries

Typical reporting and troubleshooting scenarios involve determining which programs a responsibility can access, or which security groups contain a given concurrent program.

  • List all units in a security group: SELECT REQUEST_UNIT_TYPE, UNIT_APPLICATION_ID, REQUEST_UNIT_ID FROM FND_REQUEST_GROUP_UNITS WHERE APPLICATION_ID = :app AND REQUEST_GROUP_ID = :grp;
  • Find security groups containing a specific program: SELECT rg.REQUEST_GROUP_NAME FROM FND_REQUEST_GROUPS rg, FND_REQUEST_GROUP_UNITS rgu WHERE rgu.UNIT_APPLICATION_ID = :app AND rgu.REQUEST_UNIT_ID = :prog AND rgu.REQUEST_UNIT_TYPE = 'P' AND rg.APPLICATION_ID = rgu.APPLICATION_ID AND rg.REQUEST_GROUP_ID = rgu.REQUEST_GROUP_ID;
  • Resolve program names for display by joining FND_CONCURRENT_PROGRAMS on UNIT_APPLICATION_ID and REQUEST_UNIT_ID when REQUEST_UNIT_TYPE = 'P', and FND_REQUEST_SETS when the type is 'S'.

The nonunique index FND_REQUEST_GROUP_UNITS_N1 (REQUEST_UNIT_ID, UNIT_APPLICATION_ID, REQUEST_UNIT_TYPE) supports reverse lookups driven by the included unit rather than the group.

Related Objects

  • FND_REQUEST_GROUPS — parent table joined on APPLICATION_ID and REQUEST_GROUP_ID; supplies the security group definition.
  • FND_CONCURRENT_PROGRAMS — referenced via UNIT_APPLICATION_ID and REQUEST_UNIT_ID when REQUEST_UNIT_TYPE = 'P'; resolves the report definition.
  • FND_REQUEST_SETS — referenced via UNIT_APPLICATION_ID and REQUEST_UNIT_ID when REQUEST_UNIT_TYPE = 'S'; resolves the report set definition.
  • FND_APPLICATION — referenced via UNIT_APPLICATION_ID when REQUEST_UNIT_TYPE = 'A'; resolves the owning application of the included unit.

These relationships allow the FND concurrent manager and the Request Security Group resolution logic to expand a responsibility's group into the concrete set of programs a user may submit.