Search Results hr_layouts




Overview
Explore in AI Chat

Overview

The HR_LAYOUTS table is a core repository for Self-Service User Interface (UI) configuration metadata within Oracle E-Business Suite Human Resources (PER). It stores information about each distinct UI layout instance, which defines the structure and presentation of self-service pages for employees and managers. These layouts are integral to the personalization and configuration of Oracle HRMS Self-Service modules, enabling administrators to tailor the user experience without direct code modification. The table's existence is fundamental to the declarative, component-based architecture of the E-Business Suite self-service framework.

Key Information Stored

The table's primary function is to uniquely identify and name each layout configuration. Its structure, as indicated by the primary and unique keys, centers on two critical identifiers. The LAYOUT_ID column serves as the primary technical key (HR_LAYOUTS_PK), a unique numeric identifier for each layout record. The LAYOUT_NAME column, combined with APPLICATION_ID, forms a unique logical key (HR_LAYOUTS_UK1). This combination ensures that layout names are unique within the context of a specific EBS application module (e.g., core HR, iRecruitment). Other columns, though not detailed in the excerpt, typically store metadata such as creation date, last update date, and descriptive notes about the layout's purpose.

Common Use Cases and Queries

The primary use case involves querying and managing self-service UI configurations for support, upgrade, or customization projects. A frequent query pattern, directly relevant to the user's search for "layout_name", is to retrieve all layouts for a specific application or to find a layout by its logical name. For example, to audit all layouts in the system, one might execute: SELECT layout_id, layout_name, application_id FROM hr_layouts ORDER BY application_id, layout_name;. To investigate components associated with a specific layout, a join is used: SELECT hlc.component_name FROM hr_layouts hl, hr_layout_components hlc WHERE hl.layout_id = hlc.layout_id AND hl.layout_name = 'MY_CUSTOM_LAYOUT';. Such queries are essential for troubleshooting page rendering issues or replicating configurations across instances.

Related Objects

HR_LAYOUTS sits at the center of a small hierarchy of configuration tables. As per the foreign key metadata, it has two key dependent objects. The HR_LAYOUTS_TL table provides translated descriptions for the layout, linked via LAYOUT_ID, supporting multilingual implementations. The HR_LAYOUT_COMPONENTS table stores the specific UI components (e.g., regions, items, buttons) that constitute a given layout, also linked by LAYOUT_ID. This relationship means that the HR_LAYOUTS table must be populated before its associated translated data or component definitions can be created, establishing a clear dependency chain for data migration and setup scripts.