Results for “fnd_request_sets_vl”

50+ results




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

Overview

FND_REQUEST_SETS_VL is a validated APPS-owned view within the FND (Application Object Library) product of Oracle E-Business Suite, documented for both 12.1.1 and 12.2.2. It presents the translatable, language-aware representation of concurrent request set definitions. Because it follows the standard "_VL" convention used throughout EBS, the view joins the base entity table (FND_REQUEST_SETS) with its translation table (FND_REQUEST_SETS_TL) so that consumer sessions retrieve the request set name and description already resolved into the user's current language.

In Oracle EBS, a request set groups multiple concurrent programs or sub-requests so they can be submitted and, optionally, printed together. This view is the reporting and integration surface for those definitions. It supports BI Publisher extracts, custom concurrent program lookups, and third-party scheduling tools that need to enumerate the request sets available to an application and the runtime attributes governing each set.

Underlying Base Objects

The documented ETRM metadata lists two referenced base objects, both exposed to the APPS schema as synonyms: FND_REQUEST_SETS and FND_REQUEST_SETS_TL. FND_REQUEST_SETS is the non-translatable definition table holding the identifiers, flags, date ranges, ownership, printer, and print style attributes. FND_REQUEST_SETS_TL is the translation table holding the user-facing name and description for each language.

The ETRM view text confirms the join predicate: REQUEST_SET_ID and APPLICATION_ID must match between the two tables, and the translation row is filtered by T.LANGUAGE = USERENV('LANG'). Consequently, FND_REQUEST_SETS_VL returns exactly one row per request set for the language in which the querying session executes. The view is read-only; inserts and updates are performed against the base tables through the FND concurrent manager forms and APIs.

Key Columns

  • REQUEST_SET_ID / APPLICATION_ID — the composite primary key identifying each request set. Both are required when resolving a specific set.
  • REQUEST_SET_NAME — the internal, non-translated identifier of the set as stored in FND_REQUEST_SETS.
  • USER_REQUEST_SET_NAME / DESCRIPTION — the translated, user-facing values sourced from FND_REQUEST_SETS_TL. These are the columns custom reports should display.
  • PRINT_STYLE — the print style assigned to the request set. This column is directly relevant to the print_style search term and governs the formatting applied when the set's outputs are routed to a printer or report output.
  • PRINTER — the default printer device for the set.
  • PRINT_TOGETHER_FLAG — indicates whether all reports in the set print as a single job.
  • ALLOW_CONSTRAINTS_FLAG — controls whether formatting and constraint options are offered at submission.
  • START_DATE_ACTIVE / END_DATE_ACTIVE / START_STAGE — effective-dating and initial-stage information controlling when and how the set may be run.
  • CONCURRENT_PROGRAM_ID / OWNER — the owning concurrent program and registered owner of the set.
  • ICON_NAME — the icon associated with the set in the Submit Requests interface.
  • ROW_ID — the ROWID of the underlying FND_REQUEST_SETS row, exposed for tools that require a physical row reference.

Common Use Cases and Queries

A frequent requirement is to list the request sets for an application along with their print styles. The PRINT_STYLE column on this view is precisely the attribute reported when administrators audit print behavior.

SELECT request_set_id,
       request_set_name,
       user_request_set_name,
       print_style,
       printer,
       print_together_flag
FROM   apps.fnd_request_sets_vl
WHERE  application_id = :app_id
AND    (start_date_active IS NULL OR start_date_active <= SYSDATE)
AND    (end_date_active   IS NULL OR end_date_active   >= SYSDATE);

Another common pattern retrieves the translated display name for a known set, joined to submission history such as FND_CONCURRENT_REQUESTS, so that completed runs can be grouped by their originating set and print configuration. Integrators also use the view to validate that a set exists and is currently active before programmatically submitting it through the concurrent manager APIs.

Because the view depends on USERENV('LANG'), results vary by session language. Reports intended for multilingual environments should either pin the language context or fall back to the base FND_REQUEST_SETS_TL table when all translations are required.