Search Results multi_org_category

Overview

The FND_REQ_SET_RUN_FORM_V view is a reporting and integration construct owned by the APPS schema in Oracle E-Business Suite Application Object Library (FND). It exposes the composition of request sets—the ordered stages and concurrent programs that make up a runnable request set—joined to descriptive concurrent program attributes, application short names, and NLS (National Language Support) language descriptions. The view is classified as "Retrofitted" in the ETRM metadata, indicating it was carried forward across release boundaries (12.1.1 and 12.2.2) to preserve existing form and integration behavior. In practice it supports the Request Set Run form, providing the rows necessary to enumerate each program within a stage, along with the flags and attributes that determine how each program is submitted at runtime. It is a read-only view and is not intended for direct DML.

Underlying Base Objects

The ETRM 12.2.2 documentation lists the following base objects referenced by the view:

• FND_REQUEST_SET_PROGRAMS (synonym) — the primary source of request set program rows, keyed by set application, request set, stage, and program.
• FND_REQUEST_SET_STAGES_VL (view) — the translated stage definitions, supplying user stage names and display sequence.
• FND_CONCURRENT_PROGRAMS_VL (view) — the translated concurrent program definitions, supplying user/conc program names, execution method, print style, save output flag, and the NLS_COMPLIANT indicator.
• FND_APPLICATION_VL (view) — the application short name for the owning application.
• FND_LANGUAGES (synonym) and FND_LANGUAGES_TL (synonym) — language and translated language description lookups used to resolve NLS language values.

The joins link each request set program row to its stage, its concurrent program, and its owning application, with outer joins ((+)) applied to the language tables so that rows without an NLS language assignment are still returned.

Key Columns

The view exposes identifying and control columns from the request set program definition, including SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID, REQUEST_SET_PROGRAM_ID, SEQUENCE, PROGRAM_APPLICATION_ID, and CONCURRENT_PROGRAM_ID. Runtime control attributes include NUMBER_OF_COPIES, PRINTER, PRINT_STYLE, SAVE_OUTPUT_FLAG, NLS_LANGUAGE, NLS_TERRITORY, and CRITICAL. Descriptive columns sourced from the concurrent program include USER_CONCURRENT_PROGRAM_NAME, CONCURRENT_PROGRAM_NAME, APPLICATION_SHORT_NAME, EXECUTION_METHOD_CODE, SRS_FLAG, MULTI_ORG_CATEGORY, and the NLS_COMPLIANT flag, which indicates whether the program supports NLS. The column DESCRIPTIVE_FLEXFIELD_NAME is generated as '$SRS$.'||CONCURRENT_PROGRAM_NAME. Standard audit columns (ROW_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present. User-facing translated values include USER_STAGE_NAME, DISPLAY_SEQUENCE, and LANGUAGE.

Common Use Cases and Queries

Typical scenarios include auditing the contents of request sets, generating reports of program membership by stage, and identifying programs that are NLS compliant or bound to particular language/territory combinations. A representative query is shown below.

SELECT frsv.request_set_id,
       frsv.user_stage_name,
       frsv.display_sequence,
       frsv.user_concurrent_program_name,
       frsv.application_short_name,
       frsv.nls_compliant,
       frsv.critical,
       frsv.number_of_copies,
       frsv.nls_language,
       frsv.nls_territory
FROM   apps.fnd_req_set_run_form_v frsv
WHERE  frsv.request_set_id = :request_set_id
ORDER  BY frsv.display_sequence, frsv.sequence;

Because the view is a form-supporting construct, it is most reliably used for read-only reporting and integration rather than as a persistence target.