Search Results group_resolver

Overview

BNE_PARAM_GROUPS_VL is a standard multilingual (translation) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the BNE product family — Web Applications Desktop Integrator (Web ADI) — which underpins the desktop integration framework used for uploading journals, budgets, and other spreadsheet-driven data into EBS. The "_VL" suffix is the conventional Oracle naming pattern for a view that joins a "_B" (base) table to a "_TL" (translation) table and filters on the session language.

The view exposes parameter group definitions used by the BNE parameter resolution engine. Parameter groups map a given parameter list and sequence position to a resolver, which determines how the runtime value for that parameter is derived. In this context the GROUP_RESOLVER column (the term underlying the user's search) is a core attribute: it identifies the resolution logic applied to the parameter group entry. Reporting and diagnostic queries rely on this view to present resolver configuration in the user's own language.

Underlying Base Objects

The view is defined over two synonym-backed base tables:

• BNE_PARAM_GROUPS_B — the base table holding the language-independent attributes of each parameter group record, including APPLICATION_ID, PARAM_LIST_CODE, SEQUENCE_NUM, ATTRIBUTE_APP_ID, ATTRIBUTE_CODE, and GROUP_RESOLVER.
• BNE_PARAM_GROUPS_TL — the translation table holding the USER_NAME column (and other translatable attributes) per language.

The join is performed on the three-part composite key (APPLICATION_ID, PARAM_LIST_CODE, SEQUENCE_NUM), and the translation side is restricted by T.LANGUAGE = USERENV('LANG') so that only rows matching the current session language are returned. The view additionally synthesizes a ROW_ID column from the base table's ROWID.

Key Columns

• ROW_ID — pseudo-key derived from the base table ROWID.
• APPLICATION_ID — the application owning the parameter list.
• PARAM_LIST_CODE — identifier of the parameter list to which the group belongs.
• SEQUENCE_NUM — ordering position of the parameter within the list.
• ATTRIBUTE_APP_ID / ATTRIBUTE_CODE — the attribute against which the group is defined.
• GROUP_RESOLVER — the resolver identifier/expression that determines how the parameter value is resolved at runtime; central to parameter resolution configuration.
• USER_NAME — the user-facing (translated) name of the parameter group.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include troubleshooting parameter resolution, auditing resolver assignments, and generating language-specific configuration reports. The following examples are grounded in the documented column list.

-- List all parameter groups and their resolvers for a given list
SELECT param_list_code, sequence_num, attribute_code, group_resolver, user_name
FROM   apps.bne_param_groups_vl
WHERE  application_id = :app_id
AND    param_list_code = :list_code
ORDER BY sequence_num;

-- Find all entries using a specific group resolver
SELECT application_id, param_list_code, sequence_num, group_resolver
FROM   apps.bne_param_groups_vl
WHERE  group_resolver = :resolver
ORDER BY application_id, param_list_code, sequence_num;

Because the view automatically restricts to the session language, it is the preferred source for user-facing reports and configuration screens, whereas the underlying BNE_PARAM_GROUPS_B table should be used when language-independent, full-population extraction is required. Querying the view directly avoids the need to re-implement the language join logic in custom code.