Results for “fnd_stage_fn_parameter_values”

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

Overview

FND_STAGE_FN_PARAMETER_VALUES is a table owned by the APPLSYS schema in Oracle E-Business Suite, belonging to the FND — Application Object Library product. It stores the parameter values that are bound to individual functions at each stage of a concurrent request set. In other words, when a request set is defined with multiple stages, each stage executes a function, and that function may accept parameters (such as a period name, an organization identifier, or a date range). This table records the concrete value supplied for each such parameter, keyed by the request set, the stage within that set, and the function definition.

The ETRM description marks the object as "Retrofitted," indicating it was incorporated into the documentation set after initial publication. The table exists in both 12.1.1 and 12.2.2 with the same documented APPLSYS owner and a column count of twelve.

From a heuristic Data Vault modelling perspective, the mined FK structure suggests this object behaves as a link table. Its composite unique key ties together several independent business entities — request set, stage, function, and parameter — and it carries a descriptive attribute (VALUE). It is best understood as an associative table resolving the many-to-many relationships among those entities rather than as a standalone hub or a pure satellite.

Key Information Stored

The primary key constraint FND_STAGE_FN_PARAM_VAL_PK is defined across six columns: SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID, FUNCTION_APPLICATION_ID, FUNCTION_ID, and PARAMETER_ID. A redundant unique index, FND_STAGE_FN_PARAMETER_VAL_U1, enforces the same six-column combination, confirming this tuple as the business key candidate.

• SET_APPLICATION_ID — Application owning the request set; part of the FK to FND_REQUEST_SET_STAGES.
• REQUEST_SET_ID — Identifier of the parent request set.
• REQUEST_SET_STAGE_ID — Identifier of the specific stage within the request set.
• FUNCTION_APPLICATION_ID — Application owning the function executed at the stage.
• FUNCTION_ID — Identifier of the function whose parameter is being valued.
• PARAMETER_ID — Identifier of the parameter definition being assigned a value.
• VALUE — The actual parameter value stored for that function/stage/parameter combination.
• CREATION_DATE, CREATED_BY — Standard audit columns recording insertion.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.

Common Use Cases and Queries

Typical usage centers on auditing and migrating request set definitions. Administrators inspecting why a request set behaves a certain way can join this table to stage and function metadata to reveal which values are hard-coded per stage.

• Parameter audit for a request set: SELECT REQUEST_SET_ID, REQUEST_SET_STAGE_ID, FUNCTION_ID, PARAMETER_ID, VALUE FROM FND_STAGE_FN_PARAMETER_VALUES WHERE REQUEST_SET_ID = :set_id.
• Identify who last changed a parameter value: join LAST_UPDATED_BY to FND_USER.USER_NAME.
• Migration or cloning: extract rows for a set of request sets to reproduce them in another environment.
• Data quality checks: find duplicate business keys or null VALUE entries that may cause a concurrent program to fail.

Related Objects

• FND_REQUEST_SET_STAGES — Parent of this table; joined on SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID.
• FND_USER — Referenced via CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FND_LOGINS — Referenced via LAST_UPDATE_LOGIN to identify the login session of the last change.
• FND_REQUEST_SETS — The parent request set definition governing the stages.
• FND_FORM_FUNCTIONS / FND_CONCURRENT_PROGRAMS — Provide the function and parameter metadata used when resolving the stored values.