Results for “fnd_request_sets”

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

Overview

FND_REQUEST_SETS is a core configuration table in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. It stores the definition of report sets (request sets), which are user-defined groupings of concurrent programs and reports that can be submitted, sequenced, and — under controlled conditions — executed together as a single logical unit. Each row represents one request set header, capturing its identity, ownership, presentation attributes, and the constraints under which its member requests are allowed to run. In Oracle EBS 12.1.1 and 12.2.2, this table is central to the standard Request Set and Report Set functionality, and it participates in the concurrent manager submission model through the Request Set Stages, Request Set Links, and Request Group Units structures.

From a Data Vault modeling perspective, the mined FK structure classifies FND_REQUEST_SETS as satellite-leaning. It carries descriptive and control attributes attached to a parent key (APPLICATION_ID plus REQUEST_SET_ID), rather than acting as a pure hub or a pure link, although it also references several other business entities through foreign keys.

Key Information Stored

The table contains 19 documented columns in the 12.2.2 physical schema. The most significant attributes are:

• APPLICATION_ID and REQUEST_SET_ID — together form the surrogate primary key FND_REQUEST_SETS_PK, identifying a request set within its owning application.
• REQUEST_SET_NAME — the user-visible name of the request set; paired with APPLICATION_ID it is a business-key candidate (FND_REQUEST_SETS_U1 / U2 in the documented indexes).
• OWNER — the FND_USER who owns the set, controlling who may modify or submit it.
• CONCURRENT_PROGRAM_ID — links the set definition to a concurrent program entry in FND_CONCURRENT_PROGRAMS.
• ALLOW_CONSTRAINTS_FLAG and PRINT_TOGETHER_FLAG — control flags governing whether constraints are enforced and whether member outputs are printed as a unit.
• START_DATE_ACTIVE, END_DATE_ACTIVE, and START_STAGE — define the effective life and the initial stage at which execution begins.
• PRINTER and PRINT_STYLE — reference FND_PRINTER and FND_PRINTER_STYLES to control output routing.
• ICON_NAME — used by the Forms interface for display in the navigator.
• Audit columns CREATED_BY, LAST_UPDATED_BY, CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track creation and modification, with the user and login columns referencing FND_USER and FND_LOGINS respectively.

Common Use Cases and Queries

Typical uses include reporting on defined request sets, auditing ownership and activation dates, and troubleshooting set submission failures. A representative query lists active sets with their owner and program:

• SELECT rs.request_set_name, rs.owner, rs.start_date_active, rs.end_date_active, cp.concurrent_program_name FROM fnd_request_sets rs JOIN fnd_concurrent_programs cp ON cp.application_id = rs.application_id AND cp.concurrent_program_id = rs.concurrent_program_id WHERE rs.end_date_active IS NULL OR rs.end_date_active > SYSDATE;
• To list the stages and member units of a set, join to fnd_request_set_stages and fnd_request_group_units on set_application_id / request_set_id and unit_application_id / request_unit_id.
• For multilingual reporting, join fnd_request_sets_tl on application_id and request_set_id to retrieve the translated request_set_name.

Related Objects

The most significant dependent and referenced objects are:

• FND_REQUEST_SET_STAGES — child table holding the stages of each set, joined on SET_APPLICATION_ID and REQUEST_SET_ID.
• FND_REQUEST_GROUP_UNITS — child table holding member units, joined on UNIT_APPLICATION_ID and REQUEST_UNIT_ID.
• FND_REQUEST_SETS_TL — translation table for request set names, joined on APPLICATION_ID and REQUEST_SET_ID.
• FND_CONCURRENT_PROGRAMS — parent of CONCURRENT_PROGRAM_ID and APPLICATION_ID.
• FND_USER — referenced by OWNER, CREATED_BY, and LAST_UPDATED_BY.
• FND_LOGINS — referenced by LAST_UPDATE_LOGIN.
• FND_PRINTER and FND_PRINTER_STYLES — referenced by PRINTER and PRINT_STYLE for output control.