Results for “bis_rsg_option”

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

Overview

BIS_REQUEST_SET_OPTIONS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BIS (Applications BIS / Business Intelligence System) product family. Its purpose is to present a fully resolved, presentation-ready listing of request set options, combining the raw configuration stored in the BIS option table with user-facing lookup descriptions and request set names. This makes the view particularly suitable for reporting on concurrent processing behavior defined within the BIS request-set generation framework, where options such as refresh mode and other yes/no flags drive how BI/FSG request sets behave.

The view translates internal codes and identifiers into human-readable values. It resolves the request set name, the option's internal name (for example REFRESH_MODE), and the option value, converting coded values into lookup meanings using two helper functions. This design removes the need for report authors to join to FND_COMMON_LOOKUPS or decode raw codes themselves, and it supports Oracle EBS reporting and integration by exposing a stable, descriptive interface over the underlying BIS configuration tables.

Underlying Base Objects

The view is defined over three documented base objects:

• FND_REQUEST_SETS_VL — the request set definition view, aliased as F. It supplies the user-visible REQUEST_SET_NAME and is joined to BIS_REQUEST_SET_OPTIONS on REQUEST_SET_NAME with an outer join, so options are retained even if the request set name cannot be resolved.
• BIS_REQUEST_SET_OPTIONS — the BIS configuration table, aliased as B, which stores the request set name, set application ID, option name, and option value.
• FND_COMMON_LOOKUPS — the common lookups table, aliased as FLK, joined where LOOKUP_TYPE = 'BIS_RSG_OPTION' and ENABLED_FLAG = 'Y', matching LOOKUP_CODE to B.OPTION_NAME to obtain the user-friendly lookup meaning.

The option value is further resolved through two functions in the BIS_REQUESTSET_VIEWHISTORY package: GET_BIS_LOOKUP_MEANING for REFRESH_MODE values (lookup type BIS_REFRESH_MODE) and GET_SYS_LOOKUP_MEANING for YES_NO values. The view therefore sits directly on top of the BIS request-set option store rather than any runtime or history table.

Key Columns

• USER_REQUEST_SET_NAME — the resolved request set name. A DECODE returns the user request set name from FND_REQUEST_SETS_VL when available; otherwise it returns the base request set name suffixed with '(DELETED)', flagging orphaned configuration.
• REQUEST_SET_NAME — the raw request set name stored in BIS_REQUEST_SET_OPTIONS.
• SET_APP_ID — the application ID owning the request set, used to disambiguate request sets with identical names across applications.
• OPTION_NAME — the internal option code (for example REFRESH_MODE).
• USER_OPTION_NAME — the meaning of the option as defined in the BIS_RSG_OPTION lookup.
• OPTION_VALUE — the stored, coded option value.
• USER_OPTION_VALUE — the decoded option value: REFRESH_MODE values are translated via the BIS_REFRESH_MODE lookup, while all other options are translated through the YES_NO lookup by way of a DECODE on OPTION_NAME.

Common Use Cases and Queries

Typical scenarios include auditing request set configuration before a BI Publisher or FSG run, confirming whether refresh mode options are set as expected, and producing administrative listings of request set options with descriptive labels rather than codes. The following query lists all enabled options for a given request set:

• SELECT user_request_set_name, user_option_name, user_option_value FROM apps.bis_request_set_options_v WHERE request_set_name = :p_request_set_name;

To identify configuration whose request set has been deleted, filter on the decorative suffix:

• SELECT request_set_name, option_name, option_value FROM apps.bis_request_set_options_v WHERE user_request_set_name LIKE '%(DELETED)';

Because the view already resolves lookup meanings, no additional joins to FND_COMMON_LOOKUPS are required, and it can be queried directly from BI Publisher, Discoverer, or ad hoc SQL against the APPS schema.