Search Results hr_ade_styles

Overview

HR_ADE_STYLES is a table registered in the Oracle E-Business Suite ETRM (E-Business Suite Tables and Relationships Model) repository under the PER — Human Resources product group. Its documented description identifies it as a "Test table for ADE," indicating it belongs to the Application Data Exchange / Application Desktop Integrator (ADE) subsystem rather than to core HR transactional processing. In the ETRM metadata the object is flagged "Not implemented in this database," meaning the definition exists in the repository but the physical table is not deployed in the reference environment.

Despite its HR product classification, the table functions as a shared style definition repository referenced by a broad set of Oracle Purchasing objects. The relationship metadata mined from the foreign key graph classifies HR_ADE_STYLES as hub-leaning in Data Vault terms: it is a candidate for modeling as a hub, holding a stable set of business keys (style definitions) that many downstream link and satellite structures depend upon. This classification should be treated as a modeling suggestion derived from FK topology, not as a prescriptive design mandate.

Key Information Stored

The documented metadata exposes a narrow column surface, anchored by the primary key:

• STYLE_ID — the surrogate primary key, enforced through the HR_ADE_STYLES_PK constraint.
• Style definition content is not carried directly on HR_ADE_STYLES in the documented model; instead, attribute-level detail is held on the child table HR_ADE_STYLE_COLUMNS, which joins back on STYLE_ID.

No unique indexes beyond the primary key constraint are documented in the provided metadata, so STYLE_ID is the only confirmed identifier. Where a natural business key (for example, a style name or code) exists, it is not exposed in the ETRM extract and should be confirmed against a live data dictionary query before being used in joins or de-duplication logic.

Common Use Cases and Queries

The most common practical requirement is resolving a style reference held on a Purchasing document back to its definition. Because eight documented foreign keys point at STYLE_ID, joins are direct:

• Document style resolution — joining PO_HEADERS_ALL to HR_ADE_STYLES on STYLE_ID to report the style applied to a purchase order.
• Sourcing and negotiation reporting — PON_NEGOTIATION_STYLES, PON_NEGOTIATION_STYLES_TL, PON_DOCTYPE_STYLES, and PON_AUCTION_HEADERS_ALL all reference STYLE_ID, supporting style-based reporting across sourcing events and auction headers.
• Interface and archive auditing — PO_HEADERS_INTERFACE and PO_HEADERS_ARCHIVE_ALL carry STYLE_ID, allowing reconciliation of staged or archived documents against the same style hub.
• Column-level detail — HR_ADE_STYLE_COLUMNS should be joined on STYLE_ID when the actual style attributes are required.

A representative pattern is a multi-table join from PO_HEADERS_ALL to HR_ADE_STYLES on STYLE_ID, with an optional left join to HR_ADE_STYLE_COLUMNS for attribute detail. Any query against HR_ADE_STYLES in an environment where the table is not implemented will return an invalid-object error; the ETRM flag should be checked first.

Related Objects

The following objects are documented as referencing or being referenced by HR_ADE_STYLES:

• HR_ADE_STYLE_COLUMNS — child table; joins on HR_ADE_STYLE_COLUMNS.STYLE_ID = HR_ADE_STYLES.STYLE_ID.
• PO_HEADERS_ALL — via STYLE_ID.
• PO_HEADERS_INTERFACE — via STYLE_ID.
• PO_HEADERS_ARCHIVE_ALL — via STYLE_ID.
• PON_DOCTYPE_STYLES — via STYLE_ID.
• PON_NEGOTIATION_STYLES — via STYLE_ID.
• PON_NEGOTIATION_STYLES_TL — via STYLE_ID.
• PON_AUCTION_HEADERS_ALL — via STYLE_ID.

The breadth of Purchasing-side dependencies, contrasted with the single HR-side child table, is the principal signal behind the hub-leaning classification in the ETRM relationship metadata.