Results for “hxc_layout_comp_definitions”

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

Overview

HXC_LAYOUT_COMP_DEFINITIONS is a configuration table owned by the HXC schema within the Oracle E-Business Suite Time and Labor Engine (HXC) module. It stores layout component definitions — the reusable metadata templates that describe the individual building blocks used to construct timecard and time-entry layouts presented to end users. Each row defines a component type together with the rendering characteristics applied when that component is displayed in a layout.

The table occupies a foundational, reference-data position in the HXC layout model. Where HXC_LAYOUT_COMPONENTS records the actual instances of components placed within a specific layout, HXC_LAYOUT_COMP_DEFINITIONS supplies the underlying definition those instances reference. The ETRM metadata classifies this object as hub-leaning under a Data Vault heuristic, i.e. it behaves as a stable, key-driven reference entity around which dependent component instances cluster. This classification is a modeling suggestion derived from the foreign-key structure, not a physical design statement in EBS.

Key Information Stored

The documented physical schema for 12.2.2 carries eleven columns. The most significant are:

• LAYOUT_COMP_DEFINITION_ID — surrogate primary key (HXC_LAYOUT_COMP_DEFINITIONS_PK). This is the value propagated to dependent component rows.
• COMPONENT_TYPE — the category of the layout component being defined. Part of the unique business key.
• RENDER_TYPE — how the component is rendered when presented. Together with COMPONENT_TYPE it forms the unique business key HXC_LAYOUT_COMP_DEFINITIONS_UK.
• COMPONENT_CLASS — the implementation class associated with the component definition.
• OBJECT_VERSION_NUMBER — optimistic-locking version column used by the Oracle Application Framework (OAF) and concurrent update protection.
• ZD_EDITION_NAME — editioning column supporting Oracle EBS 12.2 online patching; it participates in both the primary and unique keys.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS audit (WHO) columns for insert/update tracking and user accountability.

The distinction between the surrogate primary key (LAYOUT_COMP_DEFINITION_ID) and the business-key candidates (COMPONENT_TYPE + RENDER_TYPE + ZD_EDITION_NAME) is central: joins use the surrogate, while lookups and de-duplication logic typically rely on the business key.

Common Use Cases and Queries

Typical scenarios include auditing which component definitions exist for a given render type, tracing a rendered timecard element back to its definition, and validating that dependent component instances point to valid definitions.

• Listing definitions by render type:

  SELECT layout_comp_definition_id, component_type, render_type, component_class
  FROM   hxc.hxc_layout_comp_definitions
  WHERE  render_type = :p_render_type
  AND    zd_edition_name = 'SET1';

• Resolving a component instance to its definition:

  SELECT c.component_id, d.component_type, d.render_type
  FROM   hxc.hxc_layout_components c,
         hxc.hxc_layout_comp_definitions d
  WHERE  c.layout_comp_definition_id = d.layout_comp_definition_id;

• Orphan detection — component instances referencing a definition that no longer exists — is a standard data-integrity report.

Reporting against this table is frequently joined to HXC_LAYOUT_COMPONENTS to produce inventories of configured timecard layouts, and to layout/layout-set tables for administrative dashboards.

Related Objects

The most significant dependent object documented is HXC_LAYOUT_COMPONENTS, which references this table via LAYOUT_COMPONENTS.LAYOUT_COMP_DEFINITION_ID → HXC_LAYOUT_COMP_DEFINITIONS.LAYOUT_COMP_DEFINITION_ID. This is the primary foreign-key relationship defined in the metadata. Associated supporting and lookup objects in the HXC timecard layout family include the layout definition and layout set tables (e.g. HXC_LAYOUT_DEFINITIONS, HXC_LAYOUT_SETS), and the application program interfaces that create and maintain layouts. Because the metadata excerpt documents a single foreign key, that dependency should be treated as authoritative; the remaining objects are contextual members of the same HXC layout subsystem rather than documented FK children of this table.