Results for “bis_business_groups_v”

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

Overview

BIS_BUSINESS_GROUPS_V is a dictionary-style view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the BIS (Applications BIS) product family and exposes the mapping between an operating unit (business group) organization, its translated name, and the responsibility under which that business group is made available. The view is a convenience wrapper around the profile option machinery that governs the Business Group (PER_BUSINESS_GROUP_ID) context: it resolves the profile option definition, its assigned values at different hierarchy levels, and joins those values back to the human resources organization tables.

For reporting and integration purposes, the view answers a recurring functional question: "Which business group does a given responsibility see, and which responsibilities are associated with a given business group?" This is particularly relevant where users search using the internal key profile_option_id, since the view's definition is driven almost entirely by FND_PROFILE_OPTIONS.PROFILE_OPTION_ID. The view is read-only, VALID, and is typically consumed in custom reports, concurrent programs, and diagnostic queries rather than being updated.

Underlying Base Objects

The ETRM metadata lists no separately documented base objects, but the embedded view text explicitly references the following APPS/FND and HR tables:

• FND_PROFILE_OPTIONS — supplies the profile option definition where PROFILE_OPTION_NAME = 'PER_BUSINESS_GROUP_ID'. Its PROFILE_OPTION_ID is the join key to the value tables, which is the column most closely related to a user's profile_option_id search.
• FND_PROFILE_OPTION_VALUES — holds the actual assigned values, split by LEVEL_ID. LEVEL_ID = 10001 represents the responsibility level, while LEVEL_ID = 10003 is used in the exclusion logic (with LEVEL_VALUE matching RESPONSIBILITY_ID).
• FND_RESPONSIBILITY — provides RESPONSIBILITY_ID for the responsibility-level branch of the union.
• HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL — provide the organization identifier and its translated name, filtered on USERENV('LANG') for the session language.

Structurally, the view is a UNION of two branches: one that derives business groups via responsibility-level profile assignments (excluding those explicitly overridden at level 10003), and one that derives business groups directly from level 10003 assignments.

Key Columns

• ID — the organization identifier (operating unit / business group), returned as a character string via TO_CHAR(O.ORGANIZATION_ID). This is the value compared against the numeric profile option value.
• VALUE — the translated organization name from HR_ALL_ORGANIZATION_UNITS_TL.
• RESPONSIBILITY_ID — the responsibility through which the business group is exposed; in the second branch of the union this is populated from the profile level value rather than FND_RESPONSIBILITY.

Although the view does not project PROFILE_OPTION_ID directly, that identifier is the internal pivot of the definition and is the key a user typically researches when troubleshooting why a business group is or is not appearing for a responsibility.

Common Use Cases and Queries

Typical scenarios include auditing business-group/responsibility assignments, validating security setup after a clone or patch, and driving custom reporting that must be scoped to an operating unit.

• List all responsibilities and their associated business groups: SELECT id, value, responsibility_id FROM apps.bis_business_groups_v ORDER BY value;
• Find the business group for a specific responsibility: SELECT id, value FROM apps.bis_business_groups_v WHERE responsibility_id = :resp_id;
• Cross-check against the profile option itself: SELECT profile_option_id, profile_option_name FROM fnd_profile_options WHERE profile_option_name = 'PER_BUSINESS_GROUP_ID';

Because the view relies on session language and profile value hierarchy, results can vary by user and responsibility context; testing under the target profile_option_id setup is recommended before embedding the view in production reporting.