Search Results variation_number

Overview

The HZ_STYLE_FMT_VARIATIONS table is a core data object within the Oracle E-Business Suite (EBS) Receivables (AR) module, specifically version 12.1.1 and 12.2.2. It functions as a child table in the Trading Community Architecture (TCA) data model, which underpins party and customer information. Its primary role is to define and store the distinct layout variations available for a given style format. A style format, defined in the parent table HZ_STYLE_FORMATS_B, represents a template for formatting data, such as an address or a name. This table enables the system to support multiple presentation layouts (variations) for a single logical format, providing flexibility in how formatted data is rendered across different documents, reports, or user interfaces within the Receivables context.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies each variation. The key columns are STYLE_FORMAT_CODE and VARIATION_NUMBER. The STYLE_FORMAT_CODE is a foreign key that links the variation to its parent style format definition in HZ_STYLE_FORMATS_B. The VARIATION_NUMBER is a numeric identifier that distinguishes one layout variation from another within the same style format. While the provided ETRM metadata does not list non-key columns, typical columns in such a table could include descriptive fields like VARIATION_NAME or DESCRIPTION, creation and last update dates (CREATION_DATE, LAST_UPDATE_DATE), and the user IDs responsible for those actions (CREATED_BY, LAST_UPDATED_BY). The table's existence is fundamentally to catalog the available variations for a format.

Common Use Cases and Queries

The primary use case for this table is to query the list of available layout variations for a specific style format, which is essential for configuration and reporting. For instance, an implementation consultant may need to identify all variations for an address format to map them correctly to output templates. A common reporting need is to join this table with its parent and child tables to understand the complete formatting hierarchy. A typical SQL pattern would be a join to retrieve format and variation details:

• SELECT s.STYLE_FORMAT_CODE, s.NAME, v.VARIATION_NUMBER FROM HZ_STYLE_FORMATS_B s, HZ_STYLE_FMT_VARIATIONS v WHERE s.STYLE_FORMAT_CODE = v.STYLE_FORMAT_CODE ORDER BY 1, 3;

This data is critical when the application logic must select a specific variation (e.g., a short vs. a long address format) for rendering customer information on an invoice or statement generated by the Receivables module.

Related Objects

HZ_STYLE_FMT_VARIATIONS sits at the center of a key relationship chain within the TCA style format model. Its documented foreign key relationships are as follows:

• Parent Table (Referenced): HZ_STYLE_FORMATS_B. The column HZ_STYLE_FMT_VARIATIONS.STYLE_FORMAT_CODE is a foreign key to this table. This establishes that every variation must belong to a defined style format.
• Child Table (Referencing): HZ_STYLE_FMT_LAYOUTS_B. This table references HZ_STYLE_FMT_VARIATIONS via a composite foreign key on the columns (STYLE_FORMAT_CODE, VARIATION_NUMBER). This relationship indicates that the HZ_STYLE_FMT_LAYOUTS_B table stores the specific layout components (e.g., sequence, element type) for each variation defined in HZ_STYLE_FMT_VARIATIONS.

Therefore, the complete hierarchy is: HZ_STYLE_FORMATS_B (Master Format) → HZ_STYLE_FMT_VARIATIONS (Layout Variations) → HZ_STYLE_FMT_LAYOUTS_B (Detailed Layout Elements).