Search Results fnd_request_set_programs




Overview
Explore in AI Chat

Overview

The FND_REQUEST_SET_PROGRAMS table is a core data object within the Oracle E-Business Suite Application Object Library (FND). It functions as the master definition table for individual concurrent programs that are linked to a request set. A request set is a grouping of related concurrent programs that can be submitted as a single job. This table stores the metadata that defines each program's membership, execution order, and specific runtime parameters within the context of its parent request set and stage. It is a critical component for the request set submission and execution engine in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure captures the relationship between a request set and its constituent programs. Its primary keys enforce uniqueness: one on the program identifier (REQUEST_SET_PROGRAM_ID) and another on its logical position (SEQUENCE) within a stage. Key columns include SET_APPLICATION_ID and REQUEST_SET_ID, which link to the parent request set definition (FND_REQUEST_SETS). REQUEST_SET_STAGE_ID links to the containing stage (FND_REQUEST_SET_STAGES). PROGRAM_APPLICATION_ID and CONCURRENT_PROGRAM_ID form a foreign key to FND_CONCURRENT_PROGRAMS, identifying the specific executable program. Other significant columns control execution behavior, such as SEQUENCE (execution order), PRINT_STYLE, PRINTER, and columns for standard WHO audit information (CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

This table is central to administrative reporting and troubleshooting of request set configurations. Common use cases include auditing all programs within a specific request set, identifying programs that use a particular concurrent program definition, or analyzing the execution sequence. A typical query to list all programs in a request set would join to FND_REQUEST_SETS and FND_CONCURRENT_PROGRAMS_TL for descriptions.

  • Sample Query: SELECT rspt.user_request_set_name, cp_tl.user_concurrent_program_name, rsp.sequence FROM fnd_request_set_programs rsp JOIN fnd_request_sets_tl rspt ON rsp.request_set_id = rspt.request_set_id AND rsp.set_application_id = rspt.application_id JOIN fnd_concurrent_programs_tl cp_tl ON rsp.concurrent_program_id = cp_tl.concurrent_program_id AND rsp.program_application_id = cp_tl.application_id WHERE rspt.user_request_set_name = 'My Request Set' ORDER BY rsp.sequence;
  • Data in this table is primarily maintained via the Oracle Applications Manager or the "Define Request Set" form (Submit Requests -> Set -> Define), not via direct DML.

Related Objects

As indicated by the foreign key metadata, FND_REQUEST_SET_PROGRAMS sits at the center of a relational model for request set execution. Key dependencies include:

  • Parent Objects: FND_REQUEST_SET_STAGES (defines the containing stage), FND_CONCURRENT_PROGRAMS (defines the executable program), FND_PRINTER, and FND_PRINTER_STYLES.
  • Child Objects: FND_REQUEST_SET_PROGRAM_ARGS stores the runtime argument values for each program in the set. FND_RUN_REQUESTS and FND_RUN_REQ_PP_ACTIONS reference it to track the runtime instances and post-processing actions of submitted set programs.
  • Key Relationships: The table is essential for the request set submission workflow, linking the static definition (FND_REQUEST_SETS) to the dynamic execution instances (FND_RUN_REQUESTS).