Results for “fnd_request_set_stages_vl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The FND_REQUEST_SET_STAGES_VL view is a translated (VL) view owned by the APPS schema within the FND – Application Object Library product of Oracle E-Business Suite. It is documented in ETRM for both release 12.1.1 and 12.2.2 and carries a VALID status. The view exposes the stages that make up a request set — the ordered list of concurrent programs and sub-requests that Oracle Concurrent Manager executes when a request set is submitted — together with their translatable descriptive attributes. Because Concurrent Manager, the Submit Request Set form, and the Request Set definition UI all depend on this view, it is a foundational reporting object for anyone auditing or migrating request set definitions.
Underlying Base Objects
The view is defined, per the documented view text, as a join between two base objects: FND_REQUEST_SET_STAGES (the non-translatable "B" alias base of stage definitions) and FND_REQUEST_SET_STAGES_TL (the translatable "T" alias holding language-specific text). The join is performed on the composite key of SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID, filtered by T.LANGUAGE = USERENV('LANG') so that only the rows matched to the session's current language are returned. Consequently the "_VL" suffix signifies that the view merges the transactional configuration rows with the corresponding translated rows, presenting a single denormalized result set. In ETRM these two sources are referenced as synonyms over the underlying FND tables.
Key Columns
- ROW_ID — the ROWID of the base stage row, useful for direct base-table DML.
- SET_APPLICATION_ID / REQUEST_SET_ID / REQUEST_SET_STAGE_ID — the composite primary key identifying the stage and its parent request set.
- STAGE_NAME / USER_STAGE_NAME / DESCRIPTION — the internal stage name plus the translated user-facing name and description sourced from the TL table.
- ALLOW_CONSTRAINTS_FLAG — the flag controlling whether run-time constraints are permitted for the stage; this is the column most relevant to users searching for "allow_constraints_flag."
- CRITICAL / OUTCOME — indicates whether failure of the stage is critical and defines the resulting outcome behavior.
- DISPLAY_SEQUENCE — controls stage ordering in the UI and execution.
- FUNCTION_APPLICATION_ID / FUNCTION_ID / CONCURRENT_PROGRAM_ID — identify the executable invoked by the stage.
- SUCCESS_LINK / WARNING_LINK / ERROR_LINK — define the branching flow based on stage completion status.
- X / Y / ICON_NAME — presentation attributes for the graphical request set designer.
- Standard WHO columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
Common Use Cases and Queries
Typical uses include auditing request set composition, extracting stage sequences for documentation, and diagnosing constraint-related behavior. A representative query listing stages in execution order for a given request set is:
SELECT rs.request_set_id, rs.display_sequence, rs.stage_name,
rs.user_stage_name, rs.allow_constraints_flag, rs.critical, rs.outcome
FROM apps.fnd_request_set_stages_vl rs
WHERE rs.set_application_id = :app_id
AND rs.request_set_id = :set_id
ORDER BY rs.display_sequence;
A second scenario filters on the flag itself to find every stage where run-time constraints are allowed:
SELECT request_set_id, set_application_id, stage_name,
allow_constraints_flag
FROM apps.fnd_request_set_stages_vl
WHERE allow_constraints_flag = 'Y'
ORDER BY set_application_id, request_set_id, display_sequence;
Because the view resolves the session language automatically, it is the preferred interface for reporting request set stages in a user's native language without manually joining the TL table.
-
- Retrofitted
APPS.FND_REQUEST_SET_STAGES_VL·↳ FND_REQUEST_SET_STAGES·↳ FND_REQUEST_SET_STAGES_TL·Explore FND module →
-
- Retrofitted
APPS.FND_REQUEST_SET_STAGES_VL·↳ FND_REQUEST_SET_STAGES·↳ FND_REQUEST_SET_STAGES_TL·Explore FND module →
-
APPS.BIS_RS_RUN_ALL_STAGES_V·↳ BIS_RS_RUN_HISTORY·↳ BIS_RS_STAGE_RUN_HISTORY·↳ FND_REQUEST_SET_STAGES_VL·Explore BIS module →
-
View: FND_REQ_SET_RUN_FORM_V 12.2.2
- Retrofitted
APPS.FND_REQ_SET_RUN_FORM_V·↳ FND_APPLICATION_VL·↳ FND_CONCURRENT_PROGRAMS_VL·↳ FND_LANGUAGES·Explore FND module →
-
View: FND_REQ_SET_RUN_FORM_V 12.1.1
- Retrofitted
APPS.FND_REQ_SET_RUN_FORM_V·↳ FND_APPLICATION_VL·↳ FND_CONCURRENT_PROGRAMS_VL·↳ FND_LANGUAGES·Explore FND module →
-
Not implemented in this database·Explore BIS module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2