Results for “fnd_req_set_stages_form_v”

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

Overview

The view APPS.FND_REQ_SET_STAGES_FORM_V is a denormalized, form-oriented database object within the Oracle E-Business Suite Application Object Library (FND). It exposes the stage definitions that comprise a request set, joining transactional stage records to their translatable attribute values, lookup meanings, and linked executable metadata. Because a request set in Oracle EBS is executed as an ordered pipeline of stages, each stage controls the flow of processing through success, warning, and error links to subsequently executed stages. This view consolidates those relationships into a single queryable surface.

The view is classified as a form view, meaning it is primarily intended to support the Oracle Forms-based user interface for maintaining request set stages. Its denormalized structure also makes it convenient for reporting and integration queries, particularly when a developer or DBA must resolve the details of a request set given a known request_set_id. It is owned by the APPS schema and is marked VALID in the ETRM 12.2.2 metadata.

Underlying Base Objects

The view is defined over the following documented base objects: FND_REQUEST_SET_STAGES (synonym), FND_REQUEST_SET_STAGES_TL (synonym), FND_LOOKUPS (view), FND_APPLICATION_VL (view), FND_EXECUTABLES_VL (view), and the FND_GLOBAL package, which supplies the runtime language binding used to restrict translation joins.

The primary driving table is FND_REQUEST_SET_STAGES, alias B, which holds the physical stage rows keyed by SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID. The translated table FND_REQUEST_SET_STAGES_TL is joined multiple times: alias T retrieves the primary stage name and description for the user's language, while aliases T3, T4, and T5 resolve the user-friendly names of the success, warning, and error link targets respectively through outer joins. FND_LOOKUPS populates the outcome meaning from the CP_SET_OUTCOME lookup type. FND_APPLICATION_VL identifies the owning application, and FND_EXECUTABLES_VL resolves the concurrent program executable name associated with the stage function. FND_GLOBAL provides USERENV('LANG') so that only translation rows matching the session language are returned.

Key Columns

• ROW_ID — the ROWID of the underlying FND_REQUEST_SET_STAGES row, used by Oracle Forms for row identification.
• SET_APPLICATION_ID — the application owning the request set.
• REQUEST_SET_ID — the unique identifier of the parent request set; this is the column most commonly supplied in user searches.
• REQUEST_SET_STAGE_ID — the unique identifier of the individual stage within the set.
• STAGE_NAME / USER_STAGE_NAME — the internal and translated display names of the stage.
• SUCCESS_LINK, WARNING_LINK, ERROR_LINK — stage IDs to which processing branches based on outcome, with corresponding RESOLVED names exposed as SUCCESS_LINK_NAME, WARNING_LINK_NAME, and ERROR_LINK_NAME.
• OUTCOME and OUTCOME_MEANING — the outcome code and its interpreted meaning from FND_LOOKUPS.
• CRITICAL — indicates whether the stage is critical to set completion.
• ALLOW_CONSTRAINTS_FLAG — controls whether constraints may be applied at this stage.
• CONCURRENT_PROGRAM_ID, FUNCTION_ID, FUNCTION_APPLICATION_ID — the executable invoked by the stage, with USER_EXECUTABLE_NAME and APPLICATION_NAME resolving these identifiers.
• DISPLAY_SEQUENCE — the ordering used when rendering stages on the form.

Common Use Cases and Queries

The most frequent scenario is retrieving all stages belonging to a known request set. A typical query is:

SELECT request_set_id, request_set_stage_id, user_stage_name, outcome_meaning, critical, user_executable_name FROM fnd_req_set_stages_form_v WHERE request_set_id = :p_request_set_id ORDER BY display_sequence;

Analysts also use the view to visualize stage flow, substituting SUCCESS_LINK_NAME, WARNING_LINK_NAME, and ERROR_LINK_NAME to reconstruct branching logic. Integration developers query it to determine which concurrent program (USER_EXECUTABLE_NAME) executes at each stage, while support personnel use OUTCOME_MEANING to diagnose failed stages. Because the view honors the session language through FND_GLOBAL, it returns localized stage names without additional translation joins, making it suitable for multilingual reporting against request set definitions.