Search Results hr_bg




Overview

APPS.HR_H2PI_BG_AND_GRE_V is a reporting and integration view within the Oracle E-Business Suite Human Resources (HR) module. Its purpose is to expose a consolidated list of organizations that function as business groups or legal entities (gre, in Oracle terminology "GRE" refers to "Government Reporting Entity"). The view filters the organization master data so that only those organizations carrying the appropriate classification and the qualifying attribute flag are returned.

The view is typically consumed by downstream interfaces, extracts, and third-party integrations — the "H2PI" prefix suggests a component of an HR-to-External/Payroll interface flow — where a clean list of business groups and legal entities is required without the caller needing to understand the internal classification model of HR organizations. Because the view is owned by APPS and defined over public synonyms, it can be referenced directly by concurrent programs, PL/SQL packages, and ad hoc reporting tools operating within the EBS schema.

Underlying Base Objects

The view is defined over two documented base objects, both exposed as synonyms in the APPS schema:

  • HR_ALL_ORGANIZATION_UNITS — the master table of organization units, aliased as ORG. It supplies the organization identifier, business group identifier, name, effective dates, location, and the auditing column last_update_date.
  • HR_ORGANIZATION_INFORMATION — the flexible information table that stores additional descriptive attributes about an organization, aliased as OGI. It is joined to HR_ALL_ORGANIZATION_UNITS on organization_id.

The join is constrained by OGI.ORG_INFORMATION_CONTEXT = 'CLASS', meaning only classification-type information rows are considered, and OGI.ORG_INFORMATION1 IN ('HR_BG','HR_LEGAL'), restricting the result to organizations classified as a business group or a legal entity. A final predicate, ORG.ATTRIBUTE20 = 'Y', applies a DFF-style attribute flag to further qualify the organizations returned.

Key Columns

  • ORGANIZATION_ID — unique primary key of the organization unit; the primary join and lookup key.
  • BUSINESS_GROUP_ID — identifies the business group to which the organization belongs, enabling multi-organization filtering.
  • NAME — the organization name as held on the organization unit record.
  • DATE_FROM / DATE_TO — the effective date range of the organization, supporting date-effective queries.
  • LOCATION_ID — reference to the location (address) associated with the organization.
  • LAST_UPDATE_DATE — timestamp of the most recent change, used for incremental extracts and high-water-mark processing.

Common Use Cases and Queries

The view is most frequently used to populate LOVs, drive extracts, or validate business group and legal entity references in integration code. A typical query to list all qualifying organizations is:

  • SELECT organization_id, name, business_group_id, date_from, date_to FROM apps.hr_h2pi_bg_and_gre_v WHERE TRUNC(SYSDATE) BETWEEN date_from AND NVL(date_to, TRUNC(SYSDATE));

For incremental interfaces, the LAST_UPDATE_DATE column supports delta extraction, for example ... WHERE last_update_date >= :p_last_run_date. Analysts commonly filter by BUSINESS_GROUP_ID when scoping results to a single business group, and join ORGANIZATION_ID back to HR_ALL_ORGANIZATION_UNITS or HR_LOCATIONS for additional address detail. Because the view encapsulates the CLASS information and ATTRIBUTE20 logic, it removes the need for consumers to replicate those predicates.