Results for “function_application_id”

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

Overview

FND_REQUEST_SET_STAGES is a core Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the stage definitions that make up a concurrent request set. A request set is a container that groups multiple concurrent programs and executes them in a defined sequence; each stage in FND_REQUEST_SET_STAGES represents a logical grouping of programs that share execution dependencies, success rules, and outcome handling. Stages allow administrators to model serial, parallel, and conditional execution flows, including branching logic through success, warning, and error links.

From a Data Vault modeling perspective, this table is best classified as a hub. Its composite primary key (SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID) identifies each stage uniquely, and it carries multiple foreign-key references to parent and sibling stages, executables, concurrent programs, and audit tables. The hub classification reflects that this table is the anchor for stage identity and relationships rather than a descriptive satellite or a transaction link.

Key Information Stored

The table contains 23 documented columns. The most significant are:

• SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID — the surrogate composite primary key (FND_REQUEST_SET_STAGES_PK), uniquely identifying each stage.
• STAGE_NAME — a business-key candidate; with SET_APPLICATION_ID and REQUEST_SET_ID it forms unique index FND_REQUEST_SET_STAGES_U2.
• CRITICAL — flag indicating whether the stage is mandatory to the request set's success.
• OUTCOME — the evaluated result of the stage used for downstream branching.
• ALLOW_CONSTRAINTS_FLAG — controls whether link constraints are enforced.
• DISPLAY_SEQUENCE — ordering value for rendering and execution sequencing.
• SUCCESS_LINK, WARNING_LINK, ERROR_LINK — self-referencing pointers to the next stage based on outcome.
• FUNCTION_APPLICATION_ID, FUNCTION_ID — reference to an FND_EXECUTABLES entry.
• CONCURRENT_PROGRAM_ID — references FND_CONCURRENT_PROGRAMS for the program associated with the stage.
• X, Y, ICON_NAME — layout coordinates and icon used by the Request Set administrative UI.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

The unique index FND_REQUEST_SET_STAGES_U1 covers SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID, and ZD_EDITION_NAME, supporting edition-aware access in 12.2.2.

Common Use Cases and Queries

Typical usages include auditing request set definitions, generating documentation of existing setups, and diagnosing execution-order problems. Common query patterns:

• List all stages for a given request set:

  SELECT stage_name, display_sequence, critical, outcome
  FROM   applsys.fnd_request_set_stages
  WHERE  set_application_id = :app_id
  AND    request_set_id = :set_id
  ORDER  BY display_sequence;

• Resolve branching links to identify the next stage on success:

  SELECT a.stage_name, b.stage_name next_stage
  FROM   fnd_request_set_stages a, fnd_request_set_stages b
  WHERE  a.success_link = b.request_set_stage_id
  AND    a.set_application_id = b.set_application_id
  AND    a.request_set_id = b.request_set_id;

• Join to FND_REQUEST_SETS to report stage counts per request set.
• Join to FND_REQUEST_SET_PROGRAMS via (SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID) to enumerate the programs belonging to each stage.

Related Objects

• FND_REQUEST_SETS — parent; joined via SET_APPLICATION_ID and REQUEST_SET_ID.
• FND_REQUEST_SET_PROGRAMS — child; joined on SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID.
• FND_REQUEST_SET_STAGES_TL — translated stage descriptions keyed to the same composite identifier.
• FND_EXECUTABLES — joined via FUNCTION_APPLICATION_ID and FUNCTION_ID.
• FND_CONCURRENT_PROGRAMS — joined via CONCURRENT_PROGRAM_ID.
• FND_STAGE_FN_PARAMETER_VALUES — stores parameter values for functions bound to a stage.
• FND_STAGE_LINK_VERTICES — stores graphical link vertices for the stage flow diagram.
• FND_USER and FND_LOGINS — audit references for CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.