Search Results fnd_request_set_stages




Overview
Explore in AI Chat

Overview

The FND_REQUEST_SET_STAGES table is a core Application Object Library (FND) table within the Oracle E-Business Suite (EBS) architecture, specifically for releases 12.1.1 and 12.2.2. It functions as the master repository for defining the stages within a request set. A request set is a logical grouping of concurrent programs that can be submitted as a single job. This table stores the definition of each stage, which acts as a container for one or more programs (stored in FND_REQUEST_SET_PROGRAMS) and controls the execution flow based on the completion status of the stage. The integrity of request set definitions is maintained through its primary and foreign key relationships with other fundamental FND tables.

Key Information Stored

The table's structure captures the metadata necessary to define a stage's identity, behavior, and navigation logic. The primary key is a composite of SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID, ensuring uniqueness within the EBS instance. A unique key also exists on SET_APPLICATION_ID, REQUEST_SET_ID, and STAGE_NAME to prevent duplicate stage names within a set. Critical columns include STAGE_NAME for identification, and FUNCTION_APPLICATION_ID with FUNCTION_ID, which link to an executable function (FND_EXECUTABLES) that may be associated with the stage. The table also defines conditional navigation through the SUCCESS_LINK, WARNING_LINK, and ERROR_LINK columns, which store the REQUEST_SET_STAGE_ID of the next stage to execute based on the current stage's completion status, creating a self-referential relationship.

Common Use Cases and Queries

This table is central to administrative and reporting activities concerning request sets. Common use cases include auditing the structure of request sets, diagnosing execution flow issues, and generating documentation. A typical query retrieves all stages for a specific request set to understand its workflow.

  • Listing Stages for a Request Set: SELECT stage_name, request_set_stage_id, success_link, warning_link, error_link FROM apps.fnd_request_set_stages WHERE request_set_id = &request_set_id AND set_application_id = &application_id ORDER BY stage_name;
  • Analyzing Stage Dependencies: Joining the table to itself on the link columns can map the complete execution path. Reports often join this table with FND_REQUEST_SETS for set details and FND_REQUEST_SET_PROGRAMS to list programs within each stage.
  • Impact Analysis: Before modifying or deleting a request set definition, queries against this table and its dependent FND_REQUEST_SET_PROGRAMS are essential for understanding the scope of changes.

Related Objects

The FND_REQUEST_SET_STAGES table is a nexus within the request set subsystem, with documented relationships to several key tables.

  • FND_REQUEST_SETS: Foreign key (SET_APPLICATION_ID, REQUEST_SET_ID). A request set must exist before stages can be defined for it.
  • FND_REQUEST_SET_PROGRAMS: Foreign key (SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID). This is a critical parent-child relationship where programs are assigned to a specific stage.
  • FND_EXECUTABLES: Foreign key (FUNCTION_APPLICATION_ID, FUNCTION_ID). Links the stage to an executable function.
  • FND_CONCURRENT_PROGRAMS: Foreign key (SET_APPLICATION_ID, CONCURRENT_PROGRAM_ID). Associates a stage with a specific concurrent program.
  • Self-Referential Links: Foreign keys on SUCCESS_LINK, WARNING_LINK, and ERROR_LINK to the table's own primary key. This defines the conditional workflow between stages.
  • Audit Columns: Standard Foreign keys to FND_USER (CREATED_BY, LAST_UPDATED_BY) and FND_LOGINS (LAST_UPDATE_LOGIN) for tracking changes.