Results for “component_value”

4 results




Overview
Explore in AI Chat

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

Overview

HXC_LAYOUT_COMPONENTS is a core configuration table in the Oracle E-Business Suite Time and Labor Engine (HXC) schema. It stores the individual building blocks that make up timecard layouts—the reusable UI and data-entry elements that define how a timecard is rendered and how its fields behave. Each row represents a single component (such as a field, prompt, region, or container) that belongs to a parent layout defined in HXC_LAYOUTS. Layered on top of these components are prompts and qualifiers, held in HXC_LAYOUT_COMP_PROMPTS and HXC_LAYOUT_COMP_QUALIFIERS respectively.

From a Data Vault modeling perspective, the documented foreign key structure is heuristic satellite-leaning. The table carries a surrogate primary key, references several parent entities, and includes descriptive attributes such as COMPONENT_NAME, COMPONENT_VALUE, and SEQUENCE, which are characteristic of satellite data that describes a business key rather than acting as a standalone hub or a pure associative link. The self-referencing PARENT_COMPONENT_ID indicates a hierarchical structure that a Data Vault model would typically split into a link.

Key Information Stored

The table contains 26 documented columns. The surrogate primary key is LAYOUT_COMPONENT_ID, enforced by HXC_LAYOUT_COMPONENTS_PK. The unique business-key candidate is expressed through HXC_LAYOUT_COMPONENTS_UK1 on COMPONENT_NAME, and the 12.2.2 editioned PK includes ZD_EDITION_NAME for multi-tenant or edition-aware partitioning.

  • LAYOUT_COMPONENT_ID – surrogate primary key; the unique identifier for each layout component.
  • LAYOUT_ID – foreign key to HXC_LAYOUTS; identifies the layout to which the component belongs.
  • LAYOUT_COMP_DEFINITION_ID – foreign key to HXC_LAYOUT_COMP_DEFINITIONS; points to the template or definition that governs the component's type and behavior.
  • PARENT_COMPONENT_ID – self-referencing foreign key establishing the parent-child hierarchy of components; enables nested or container-style layouts.
  • COMPONENT_NAME – the business identifier for the component and the basis of the unique key.
  • COMPONENT_VALUE – the value or default content carried by the component.
  • COMPONENT_ALIAS and PARENT_BEAN – aliasing and parent-bean references used by the rendering layer.
  • SEQUENCE – controls ordering of components within a layout.
  • NAME_VALUE_STRING – a name/value serialization used for dynamic component content.
  • REGION_CODE and REGION_CODE_APP_ID – identify the associated application region and its owning application.
  • ATTRIBUTE_CODE and ATTRIBUTE_CODE_APP_ID – identify the underlying attribute and application context.
  • ATTRIBUTE1–ATTRIBUTE5 – descriptive flexfield extension columns for customer-specific data.
  • Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER provide standard who-columns and optimistic locking.

Common Use Cases and Queries

The most frequent operational need is to reconstruct the full component hierarchy of a given timecard layout. A typical query walks the self-referencing relationship starting from a specific LAYOUT_ID, joining each component to its parent and to the definition:

  • Retrieve all components for a layout: SELECT * FROM hxc_layout_components WHERE layout_id = :layout_id ORDER BY sequence;
  • Resolve the parent chain: SELECT child.component_name, parent.component_name AS parent_name FROM hxc_layout_components child LEFT JOIN hxc_layout_components parent ON child.parent_component_id = parent.layout_component_id;
  • Identify the template driving a component: join LAYOUT_COMP_DEFINITION_ID to HXC_LAYOUT_COMP_DEFINITIONS to understand available behavior.
  • Audit prompts and qualifiers by joining LAYOUT_COMPONENT_ID to HXC_LAYOUT_COMP_PROMPTS and HXC_LAYOUT_COMP_QUALIFIERS.
  • Reporting on customizations via the ATTRIBUTE1–ATTRIBUTE5 flexfields and tracking changes through the audit columns.

Because COMPONENT_NAME is unique, it serves as a reliable lookup key for administrators investigating timecard rendering issues, and the SEQUENCE column supports display-order reporting.

Related Objects

The most significant related objects, based on the documented foreign key and referencing relationships, are the following:

  • HXC_LAYOUTS – referenced via LAYOUT_COMPONENTS.LAYOUT_ID; the parent layout.
  • HXC_LAYOUT_COMP_DEFINITIONS – referenced via LAYOUT_COMPONENTS.LAYOUT_COMP_DEFINITION_ID; provides the component template.
  • HXC_LAYOUT_COMPONENTS (self) – via PARENT_COMPONENT_ID; supports hierarchical nesting.
  • HXC_LAYOUT_COMP_PROMPTS – references LAYOUT_COMPONENTS.LAYOUT_COMPONENT_ID; defines prompts attached to a component.
  • HXC_LAYOUT_COMP_QUALIFIERS – references LAYOUT_COMPONENTS.LAYOUT_COMPONENT_ID; defines qualifiers that filter or constrain component behavior.

Together these tables form the metadata backbone of the Time and Labor timecard layout engine, and any modification to HXC_LAYOUT_COMPONENTS should be validated against all of the above dependents.