Search Results hr_ade_style_columns

Overview

HR_ADE_STYLE_COLUMNS is a table within the PER (Human Resources) product family of Oracle E-Business Suite, documented in the ETRM repository with the description "Test table for ADE." ADE (Application Data Entry) is the framework that renders configurable, style-driven user interfaces across Oracle HRMS and related modules. In that framework, a "style" defines a reusable presentation layout, and the individual columns or fields belonging to that layout are described as rows in this table. HR_ADE_STYLE_COLUMNS therefore serves as the definition table that maps discrete field-level entries to a parent style definition, allowing ADE to determine which data elements are displayed, in what order, and with what presentation attributes.

The ETRM metadata explicitly notes that the object is "Not implemented in this database," which is significant for practitioners. This status indicates that the table is part of the shipped Oracle schema dictionary but is not instantiated in the particular environment from which the ETRM extract was taken. In Oracle EBS 12.1.1 and 12.2.2, such objects are typically created only when the corresponding product feature is licensed, configured, or patched. Reference material for this table is nonetheless useful for understanding the ADE metadata model, for interpreting ADE-related support queries, and for anticipating what will appear in environments where the table is present.

The provided metadata classifies the object, heuristically, as satellite-leaning within a Data Vault modeling suggestion. This is consistent with the documented structure: the table carries a surrogate primary key and a foreign key to a parent definition table, and its rows are best understood as descriptive attributes that hang off the parent style entity rather than as an independent hub or a link resolving many-to-many relationships between hubs.

Key Information Stored

The ETRM documentation for HR_ADE_STYLE_COLUMNS identifies a deliberately narrow set of structural elements rather than a full column listing. The documented elements are as follows.

• STYLE_COLUMN_ID — the surrogate primary key column, governed by the constraint HR_ADE_STYLE_COLUMNS_PK. As an ADE-generated numeric identifier, it is an internal key with no business meaning; it exists to give each field-level row within a style a stable, unique handle for joins and referential integrity.
• STYLE_ID — the foreign key column pointing to HR_ADE_STYLES. This is the business-significant relationship in the table. STYLE_ID identifies which parent style definition the row belongs to, and it is the column on which the ADE engine and most reporting queries will filter, sort, and group.

Because the metadata documents only these two columns, STYLE_COLUMN_ID should be treated as the surrogate key and STYLE_ID as the principal business-key candidate for the parent relationship. Any additional descriptive columns — for example, field name, display sequence, visibility, or prompt text — are not enumerated in the supplied metadata and should be confirmed against the actual database dictionary (ALL_TAB_COLUMNS) in an environment where the table is implemented before they are relied upon in code or documentation.

Common Use Cases and Queries

The practical uses of this table center on diagnosing and validating ADE style configuration. Typical scenarios include confirming that a style has the expected number of field definitions, auditing which styles reference a given set of columns, and investigating display problems reported by end users.

A simple pattern to count field definitions per style, joining to the parent table on the documented relationship, is:

• SELECT s.style_id, COUNT(*) FROM hr_ade_style_columns c, hr_ade_styles s WHERE c.style_id = s.style_id GROUP BY s.style_id;
• SELECT * FROM hr_ade_style_columns WHERE style_id = :style_id; to retrieve all field rows for a specific style.
• SELECT * FROM hr_ade_style_columns WHERE style_column_id = :id; to resolve a single row by its surrogate key.

Because the table is documented as not implemented in the ETRM source database, DBAs and support analysts should first verify its existence before executing such queries: SELECT table_name FROM all_tables WHERE table_name = 'HR_ADE_STYLE_COLUMNS';. Reporting on ADE configuration is typically performed directly against these underlying metadata tables rather than through a public HRMS view, so understanding the STYLE_ID linkage is the essential prerequisite for any such query.

Related Objects

The documented relationship data is precise but limited: HR_ADE_STYLE_COLUMNS holds a foreign key, STYLE_ID, referencing HR_ADE_STYLES. HR_ADE_STYLES is therefore the single most significant related object and the parent in the association. Beyond this documented join, the following objects are commonly encountered when working with ADE metadata in Oracle EBS and are worth reviewing alongside this table:

• HR_ADE_STYLES — the parent style definition table; join on HR_ADE_STYLE_COLUMNS.STYLE_ID = HR_ADE_STYLES.STYLE_ID.
• HR_ADE_STYLE_COLUMNS_PK — the primary key constraint on STYLE_COLUMN_ID that enforces row uniqueness.
• ADE configuration tables and views — sibling metadata objects under the HR_ADE_ prefix that describe blocks, fields, and layout attributes for the ADE framework.
• PER and HRMS application forms — the runtime consumers that read ADE style metadata to render data-entry pages for HR users.
• ALL_TAB_COLUMNS / ALL_CONSTRAINTS — the data dictionary views used to confirm whether the table is implemented and to retrieve its complete column list.

Where the documented metadata is silent on additional columns and dependencies, verification against the live data dictionary remains the recommended approach before any integration or customization work is undertaken.