Results for “internal_address”

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

Overview

HRFV_OPERATING_UNITS is an APPS-owned business view template in Oracle E-Business Suite, documented under the PER (Human Resources) product. Its stated purpose is to serve as the business view template from which the flexfield view is generated, meaning it conforms the underlying HR organization tables into a flattened, reporting-friendly shape that exposes descriptive flexfield context information for operating units. The view is VALID in both 12.1.1 and 12.2.2 and is defined in the APPS schema with the READ ONLY clause, so it can be queried for reporting and integration purposes but cannot be used as a DML target.

In the context of searching for "internal_address," this view is relevant because it surfaces the INTERNAL_ADDRESS column, derived from ORG.INTERNAL_ADDRESS_LINE on the operating unit organization record. This makes HRFV_OPERATING_UNITS a convenient single source for operating unit name, internal address, legal entity, and location attributes without requiring the caller to join the HR organization tables manually.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, HR_ORGANIZATION_INFORMATION, HR_ORGANIZATION_UNITS (itself a view), and the packages HR_BIS, HR_GENERAL, and HR_SECURITY. The synonyms HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, and HR_ORGANIZATION_INFORMATION are joined to build the result set.

The driving table is HR_ORGANIZATION_UNITS (aliased ORG), which supplies the operating unit identity, dates, internal address line, comments, and location and business group references. HR_ORGANIZATION_INFORMATION is joined twice: OI2 with ORG_INFORMATION_CONTEXT = 'OPERATING UNIT INFORMATION' supplies the legal entity reference through ORG_INFORMATION2, while OI3 with ORG_INFORMATION_CONTEXT = 'CLASS' and ORG_INFORMATION1 = 'OPERATING_UNIT' restricts output to true operating units. The _TL tables provide translated names for the operating unit, business group, legal entity, and location, each constrained to the session language via USERENV('LANG'). Security is enforced through HR_BIS.GET_SEC_PROFILE_BG_ID, which restricts results to the business group of the current security profile.

Key Columns

• BUSINESS_GROUP_NAME – translated name of the business group organization.
• OPERATING_UNIT_NAME – translated name of the operating unit.
• DATE_FROM / DATE_TO – effective dates of the organization record.
• ORGANIZATION_TYPE – decoded organization type via HR_BIS.BIS_DECODE_LOOKUP('ORG_TYPE', ORG.TYPE).
• INTERNAL_ADDRESS – the internal address line of the operating unit, sourced from ORG.INTERNAL_ADDRESS_LINE.
• COMMENTS – free-text comments on the organization.
• LEGAL_ENTITY_NAME – translated legal entity name.
• LOCATION_NAME – location code from HR_LOCATIONS_ALL_TL.
• BUSINESS_GROUP_ID, LEGAL_ENTITY_ID, LOCATION_ID, OPERATING_UNITS_ID – key identifiers for joining and for integration payloads.
• _DF – the flexfield placeholder column carrying the token '_DF:PER:PER_ORGANIZATION_UNITS:ORG'.

Common Use Cases and Queries

Typical uses include reporting on operating units by business group, populating LOVs and integration extracts, and retrieving internal address details for an operating unit or legal entity. A basic query returning the internal address alongside identifying attributes:

SELECT operating_unit_name, internal_address, legal_entity_name, location_name FROM apps.hrfv_operating_units WHERE business_group_id = :p_bg_id;

To resolve a legal entity for a given operating unit:

SELECT operating_unit_name, legal_entity_name, internal_address FROM apps.hrfv_operating_units WHERE operating_units_id = :p_org_id;

Because security filtering is applied inside the view through HR_BIS.GET_SEC_PROFILE_BG_ID, results are automatically limited to the business group of the querying user's security profile, eliminating the need for additional predicates in most reporting scenarios.