Search Results location_extra_info_id

Overview

The HR_LOCATION_EXTRA_INFO table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically in releases 12.1.1 and 12.2.2. It functions as a flexible extension mechanism for the standard location model, enabling organizations to store supplementary, user-defined information about physical locations beyond the core attributes defined in the primary HR_LOCATIONS_ALL table. This table implements a key-value pair design, allowing for the association of multiple, varied pieces of information with a single location record. Its role is to provide a structured yet customizable repository for location-specific details that are critical for advanced HR, payroll, and legal reporting but are not part of the standard location address fields.

Key Information Stored

The table's structure is designed to support its extensible purpose. The primary and foreign key columns establish critical data integrity and relationships. The LOCATION_EXTRA_INFO_ID serves as the unique primary key identifier for each row. The LOCATION_ID is a foreign key that links each record definitively to a specific entry in the HR_LOCATIONS_ALL table, anchoring the extra information to a master location. The INFORMATION_TYPE column is a foreign key referencing the HR_LOCATION_INFO_TYPES table, which defines the category or classification of the extra information being stored (e.g., 'Tax Jurisdiction Code', 'Building Security Contact', 'Regional Code'). The actual data value for the specified information type is held in the LEI_INFORMATION column, completing the key-value model. Additional audit columns, such as LAST_UPDATE_DATE and LAST_UPDATED_BY, are typically present to track changes.

Common Use Cases and Queries

A primary use case is enhancing location data for statutory reporting, such as storing local tax jurisdiction codes required for payroll tax calculations. Another common scenario is storing operational details like facility manager contacts or health and safety officer information for internal processes. For reporting, a typical query joins this table to the master location and information type tables to produce a readable dataset. For example, to retrieve all extra information for a specific location, one might use:

• SELECT hl.location_code, hlit.type_name, hlei.lei_information
• FROM hr_locations_all hl,
• hr_location_extra_info hlei,
• hr_location_info_types hlit
• WHERE hl.location_id = hlei.location_id
• AND hlei.information_type = hlit.information_type
• AND hl.location_id = :p_location_id;

Administrators may also query this table to audit or list all custom information types currently in use across the organization's locations.

Related Objects

HR_LOCATION_EXTRA_INFO has defined dependencies on two principal tables, as indicated by its foreign keys. It is fundamentally dependent on HR_LOCATIONS_ALL, the master table for all physical location definitions within Oracle EBS. It also relies on HR_LOCATION_INFO_TYPES, which acts as a reference code table controlling the valid types of extra information that can be recorded. While not explicitly listed in the provided metadata, this table is often referenced by or integrated with various HR and payroll APIs, personalization layers, and custom reports that require enriched location data. Its design ensures that location-related extensions remain tightly integrated with the core HRMS data model.