Search Results fnd_stage_fn_parameter_values




Overview
Explore in AI Chat

Overview

The FND_STAGE_FN_PARAMETER_VALUES table is a core data object within the Application Object Library (FND) module of Oracle E-Business Suite (EBS). It functions as a staging or configuration table within the Request Set subsystem. Specifically, it stores the parameter values that are defined for executable functions associated with stages in a request set. A request set is a collection of concurrent programs and other functions that can be submitted as a single job, and its stages define the execution flow. This table holds the runtime or default parameter configurations for functions within those stages, enabling the parameterization and customization of complex, multi-step business processes.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies a specific parameter value for a function within a request set stage. The key columns, as documented, are: SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID, FUNCTION_APPLICATION_ID, FUNCTION_ID, and PARAMETER_ID. The FUNCTION_APPLICATION_ID and FUNCTION_ID columns, which the user specifically searched for, are critical as they identify the executable function (often a concurrent program) to which the parameter belongs. Other important columns include the PARAMETER_VALUE itself, and standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for tracking data changes.

Common Use Cases and Queries

This table is primarily accessed for auditing, troubleshooting, and administrative reporting of request set configurations. A common scenario involves identifying all parameter values set for functions within a specific request set stage. For example, to audit the parameters for a stage in a request set, a technical consultant might use a query joining to FND_REQUEST_SET_STAGES and FND_CONCURRENT_PROGRAMS (where FUNCTION_ID maps to CONCURRENT_PROGRAM_ID). Another use case is to compare parameter values across different environments during a migration. A sample query pattern to extract parameter details for a given request set would be:

  • SELECT s.user_stage_name, cp.user_concurrent_program_name, pv.parameter_id, pv.parameter_value
  • FROM fnd_stage_fn_parameter_values pv,
  • fnd_request_set_stages_vl s,
  • fnd_concurrent_programs_vl cp
  • WHERE pv.set_application_id = s.application_id
  • AND pv.request_set_id = s.request_set_id
  • AND pv.request_set_stage_id = s.request_set_stage_id
  • AND pv.function_application_id = cp.application_id
  • AND pv.function_id = cp.concurrent_program_id
  • AND s.request_set_id = :p_request_set_id;

Related Objects

As indicated by the foreign key relationships in the provided metadata, FND_STAGE_FN_PARAMETER_VALUES has strong dependencies on several other core FND tables. Its primary relationship is with FND_REQUEST_SET_STAGES, linking via the composite key (SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID). This enforces that every parameter value record must belong to a valid request set stage. For WHO column integrity, it references FND_USER (for CREATED_BY and LAST_UPDATED_BY) and FND_LOGINS (for LAST_UPDATE_LOGIN). While not explicitly listed in the provided excerpt, the FUNCTION_APPLICATION_ID and FUNCTION_ID columns typically relate to objects like FND_CONCURRENT_PROGRAMS or other executable functions defined in FND_FORM_FUNCTIONS, forming the link between a parameter value and the actual program or function it configures.