Results for “per_business_groups”

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

Overview

PER_BUSINESS_GROUPS is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER (Human Resources) product family. It is validated in both release 12.1.1 and 12.2.2. The view exposes a single, denormalized row for each Business Group defined in the enterprise, consolidating descriptive attributes from the organization entity, its translated name, and the flexfield segments that carry Business Group configuration. A Business Group is the highest-level organizational unit in Oracle HRMS and acts as the partitioning boundary for employees, assignments, grades, jobs, positions, payrolls and other HR entities. Because so many downstream objects reference the Business Group, this view is widely used in reporting, data extraction, and integration layers that need Business Group context without joining the raw HR organization and flexfield tables manually.

Underlying Base Objects

The view text joins four aliases derived from the documented base objects. HR_ALL_ORGANIZATION_UNITS (aliased O) supplies the core organization record, including ORGANIZATION_ID, dates, address line and location. HR_ALL_ORGANIZATION_UNITS_TL (aliased OTL) provides the language-specific NAME, joined on ORGANIZATION_ID and filtered by OTL.LANGUAGE = USERENV('LANG'). HR_ORGANIZATION_INFORMATION appears three times to resolve distinct descriptive flexfield contexts: O2 carries the WORK DAY INFORMATION context (outer-joined), O3 carries the BUSINESS GROUP INFORMATION context (mandatory), and O4 carries the CLASS context. The join to O4 requires ORG_INFORMATION1 = 'HR_BG' and ORG_INFORMATION2 = 'Y', which restricts the result set to organizations classified as Business Groups. The mandatory joins on O3 and O4 mean that only organizations with valid Business Group information and a class flag of Y are returned.

Key Columns

The view exposes two identifiers — BUSINESS_GROUP_ID and ORGANIZATION_ID — both mapped to the underlying organization identifier and functionally equivalent for this entity. NAME holds the translated Business Group name. DATE_FROM and DATE_TO define the effective date range of the organization; INTERNAL_ADDRESS_LINE, LOCATION_ID and COMMENTS capture address and free-text detail. WORK DAY INFORMATION columns include DEFAULT_START_TIME, DEFAULT_END_TIME, WORKING_HOURS and FREQUENCY. The BUSINESS GROUP INFORMATION context contributes SHORT_NAME, METHOD_OF_GENERATION_EMP_NUM, GRADE_STRUCTURE, PEOPLE_GROUP_STRUCTURE, JOB_STRUCTURE, COST_ALLOCATION_STRUCTURE, POSITION_STRUCTURE, COMPETENCE_STRUCTURE, LEGISLATION_CODE, CURRENCY_CODE and additional method-of-generation columns. SECURITY_GROUP_ID and ENABLED_FLAG support row-level security and activation status.

Common Use Cases and Queries

Typical scenarios include driving Business Group LOVs, joining seeded HR tables back to a Business Group name, and validating configuration such as legislation and currency during data loads. A representative query is:

• List all Business Groups: SELECT business_group_id, name, short_name, legislation_code, currency_code FROM per_business_groups WHERE enabled_flag = 'Y';
• Resolve a Business Group for a known ID: SELECT name, default_start_time, default_end_time FROM per_business_groups WHERE business_group_id = :p_bg_id;
• Reporting join: join PER_BUSINESS_GROUPS to PER_ALL_PEOPLE_F on BUSINESS_GROUP_ID to segment headcount by Business Group.
• Integration extraction: SELECT business_group_id, name, short_name, legislation_code FROM per_business_groups for staging into external systems.

Because the view already applies the CLASS = HR_BG and BUSINESS GROUP INFORMATION filters, callers should treat it as a pre-qualified source and not re-apply those predicates.