Search Results hxc_layouts




Overview
Explore in AI Chat

Overview

The HXC_LAYOUTS table is a core data object within the Oracle E-Business Suite Time and Labor Engine (HXC). It serves as the master definition table for timecard layouts, which are the structural templates that determine how time entry screens are presented to users. These layouts define the arrangement of fields, components, and rules governing data entry for timecards, ensuring a consistent and controlled user experience across the application. The table's integrity is critical for the proper rendering and processing of all timecard data within the system.

Key Information Stored

The table stores the fundamental metadata for each unique timecard layout. Its primary columns include the surrogate key LAYOUT_ID, which uniquely identifies each layout record. The APPLICATION_ID column associates the layout with a specific Oracle EBS application module, while LAYOUT_NAME holds the unique, user-defined identifier for the layout. The combination of APPLICATION_ID and LAYOUT_NAME is enforced as a unique constraint (HXC_LAYOUTS_UK1), ensuring no duplicate layout names exist within the same application context. This structure allows for the precise identification and retrieval of layout definitions.

Common Use Cases and Queries

This table is central to administrative setup and reporting on timecard configurations. Common use cases include auditing available layouts, troubleshooting timecard display issues, and identifying which layouts are assigned to specific responsibilities or users. A typical query retrieves all layouts for a given application or finds a specific layout by name.

  • Retrieve all layouts for the Time and Labor application (APPLICATION_ID = 800):
    SELECT layout_id, layout_name FROM hxc_layouts WHERE application_id = 800 ORDER BY layout_name;
  • Find a specific layout definition:
    SELECT * FROM hxc_layouts WHERE layout_name = 'WEEKLY_TIMECARD';
  • Join with translation table for descriptive information:
    SELECT b.layout_name, t.name FROM hxc_layouts b, hxc_layouts_tl t WHERE b.layout_id = t.layout_id AND t.language = USERENV('LANG');

Related Objects

The HXC_LAYOUTS table has key relationships with other Time and Labor objects, forming the core of the layout definition model. The HXC_LAYOUTS_TL table provides translated descriptive information (NAME) for the layouts, linked via the LAYOUT_ID foreign key. The HXC_LAYOUT_COMPONENTS table defines the specific fields, blocks, and regions that constitute a layout, also linked by LAYOUT_ID. These dependencies mean that the HXC_LAYOUTS record acts as a parent entity; its LAYOUT_ID is propagated to these child tables to define the complete, renderable structure of a timecard template.