Results for “cp_set_outcome”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.FND_REQ_SET_STAGES_FORM_V is a supplementary Oracle EBS view owned by the APPS schema. Its status is VALID in both 12.1.1 and 12.2.2. The view exists to simplify Oracle Forms coding for the Request Set Stages setup form, presenting stage definitions in a single denormalized result set that the form layer can bind directly. Oracle explicitly warns that this view is not intended to be queried or altered by customers and that its definition may change dramatically in subsequent minor or major releases. It should therefore be treated as an internal forms-supplement view rather than a supported integration or reporting interface. The FND Design Data entry is FND.FND_REQ_SET_STAGES_FORM_V.
Underlying Base Objects
The documented dependencies for this view are the following: FND_APPLICATION_VL (VIEW), FND_EXECUTABLES_VL (VIEW), FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), FND_REQUEST_SET_STAGES (SYNONYM), and FND_REQUEST_SET_STAGES_TL (SYNONYM). The primary transactional data source is FND_REQUEST_SET_STAGES, which stores one row per stage within a request set, keyed by SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID. The FND_REQUEST_SET_STAGES_TL synonym supplies translated, user-facing text such as the stage name and description. FND_APPLICATION_VL resolves the owning application name, while FND_EXECUTABLES_VL resolves the user-executable name associated with CONCURRENT_PROGRAM_ID. FND_LOOKUPS provides the decoded meaning for the OUTCOME lookup value. FND_GLOBAL supplies session context such as the current application and login identifiers used during forms invocation. Because several dependencies are _VL views and one is a package, the view reflects translated and session-aware data at query time.
Key Columns
The view exposes identifiers, descriptive attributes, and link-related flags. ROW_ID carries the ROWID of the underlying stage row. SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID identify the parent request set and the individual stage. STAGE_NAME is the raw stage name, while USER_STAGE_NAME and DESCRIPTION provide the translated forms-facing values. SUCCESS_LINK, WARNING_LINK, and ERROR_LINK are numeric link identifiers; the corresponding decoded names are exposed as SUCCESS_LINK_NAME, WARNING_LINK_NAME, and ERROR_LINK_NAME. The WARNING_LINK_NAME column is the decoded text associated with WARNING_LINK and is the field typically surfaced in the stage definition form. OUTCOME holds the stage outcome code, decoded through the lookup view as OUTCOME_MEANING. CRITICAL, ALLOW_CONSTRAINTS_FLAG, ICON_NAME, DISPLAY_SEQUENCE, FUNCTION_ID, and FUNCTION_APPLICATION_ID govern behavior and presentation. CONCURRENT_PROGRAM_ID, USER_EXECUTABLE_NAME, and APPLICATION_NAME tie the stage to a concurrent program. Standard WHO columns are included: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. X and Y hold positional coordinates used by the form layout.
Common Use Cases and Queries
Legitimate use is largely diagnostic: inspecting how a request set stage is defined when the form displays unexpected warning behavior, or tracing which concurrent program and outcome a stage maps to. The warning_link_name term in the search indicates a user inspecting the decoded warning link label for a stage. A representative query is:
- SELECT REQUEST_SET_ID, REQUEST_SET_STAGE_ID, USER_STAGE_NAME, WARNING_LINK, WARNING_LINK_NAME, OUTCOME_MEANING, CRITICAL, USER_EXECUTABLE_NAME FROM APPS.FND_REQ_SET_STAGES_FORM_V WHERE REQUEST_SET_ID = :p_request_set_id ORDER BY DISPLAY_SEQUENCE;
- SELECT REQUEST_SET_STAGE_ID, USER_STAGE_NAME, SUCCESS_LINK_NAME, WARNING_LINK_NAME, ERROR_LINK_NAME FROM APPS.FND_REQ_SET_STAGES_FORM_V WHERE REQUEST_SET_ID = :p_request_set_id;
- SELECT s.USER_STAGE_NAME, s.WARNING_LINK_NAME, a.APPLICATION_NAME FROM APPS.FND_REQ_SET_STAGES_FORM_V s, APPS.FND_APPLICATION_VL a WHERE s.FUNCTION_APPLICATION_ID = a.APPLICATION_ID AND s.REQUEST_SET_ID = :p_request_set_id;
Because the view is documented as forms-only and subject to change, production integrations should be built against the base table FND_REQUEST_SET_STAGES and its _TL companion directly, using FND_APPLICATION_VL and FND_EXECUTABLES_VL for the join columns the view performs internally.
-
Lookup Type: CP_SET_OUTCOME 12.2.2
Set and Stage Outcomes
-
Lookup Type: CP_SET_OUTCOME 12.1.1
Set and Stage Outcomes
-
APPS.FND_REQ_SET_STAGES_FORM_V·↳ FND_APPLICATION_VL·↳ FND_EXECUTABLES_VL·↳ FND_GLOBAL·Explore FND module →
-
APPS.FND_REQ_SET_STAGES_FORM_V·↳ FND_APPLICATION_VL·↳ FND_EXECUTABLES_VL·↳ FND_GLOBAL·Explore FND module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2