Search Results fnd_request_sets




Overview
Explore in AI Chat

Overview

The FND_REQUEST_SETS table is a core data object within the Application Object Library (FND) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master definition table for report sets, which are collections of individual concurrent programs or other request sets that can be submitted as a single job. These sets enable the automation of multi-step business processes, allowing for sequential or parallel execution, conditional logic based on prior program outcomes, and consolidated output. As a foundational table in the concurrent processing architecture, it is owned by the APPLSYS schema and is integral to defining and managing batch workflows.

Key Information Stored

The table stores the structural and control metadata for each request set. Its primary key is a composite of APPLICATION_ID and REQUEST_SET_ID, ensuring uniqueness within the application. A unique key also exists on APPLICATION_ID and REQUEST_SET_NAME. Critical columns include REQUEST_SET_ID (the internal identifier), REQUEST_SET_NAME (the internal name), and CONCURRENT_PROGRAM_ID (linking to the concurrent program definition that represents the set as a runnable entity). Other significant columns manage descriptive attributes, printing preferences (PRINTER, PRINT_STYLE), and standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN). The OWNER column references the user responsible for the set definition.

Common Use Cases and Queries

This table is central to administrative and reporting activities concerning batch workflows. Common use cases include auditing the configuration of all request sets within an application, identifying sets owned by a specific user, or diagnosing submission issues by verifying base definitions. A typical query retrieves a set's core details by its internal name:

  • SELECT request_set_id, concurrent_program_id, printer, print_style FROM apps.fnd_request_sets WHERE application_id = 123 AND request_set_name = 'XX_CUSTOM_SET';

For reporting purposes, it is frequently joined with the FND_CONCURRENT_PROGRAMS table to get executable details and with FND_REQUEST_SETS_TL for translated user-facing names. Developers may query this table to find the program ID associated with a set for use in programmatic submissions via the FND_REQUEST.SUBMIT_REQUEST API.

Related Objects

FND_REQUEST_SETS has defined relationships with several key EBS objects, primarily through foreign key constraints. The documented relationships are:

  • FND_CONCURRENT_PROGRAMS: Joined via APPLICATION_ID and CONCURRENT_PROGRAM_ID. This links the set definition to its executable program entity.
  • FND_REQUEST_SETS_TL: Joined via APPLICATION_ID and REQUEST_SET_ID. This table holds the translated set names and descriptions for multiple languages.
  • FND_REQUEST_SET_STAGES: Joined via SET_APPLICATION_ID and REQUEST_SET_ID. This child table defines the stages within the request set.
  • FND_REQUEST_GROUP_UNITS: Joined via UNIT_APPLICATION_ID and REQUEST_UNIT_ID (where the unit is the request set). This registers the set as a securable unit within a request group.
  • FND_USER: Joined for the CREATED_BY, LAST_UPDATED_BY, and OWNER columns.
  • FND_LOGINS: Joined for the LAST_UPDATE_LOGIN column.
  • FND_PRINTER / FND_PRINTER_STYLES: Joined for the PRINTER and PRINT_STYLE columns, managing output device preferences.