Results for “uppercase_flag”

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

Overview

HZ_STYLE_FMT_LAYOUTS_B is a Receivables (AR) base table that stores the layout definition of individual style format variation components. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model, it defines how the constituent parts of a style format variation are physically and visually arranged — the ordering, positioning, delimiters, and transformation rules applied to each attribute that makes up a formatted output. This table is part of the Trading Community Architecture (TCA) formatting framework used to control how party, account, and address data is rendered on documents and reports.

The table carries the _B suffix, indicating it is the base (non-translated) table of a translatable entity pair. Its translated counterpart, HZ_STYLE_FMT_LAYOUTS_TL, holds language-specific descriptive text and references this table by primary key. The object is owned by the AR schema and is marked VALID.

From a warehousing and modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. This should be treated as a heuristic suggestion rather than a documented fact: the table hangs off the HZ_STYLE_FMT_VARIATIONS parent and primarily contributes descriptive attributes rather than defining new business relationships.

Key Information Stored

The table is defined with 25 physical columns. The functionally significant columns include:

• STYLE_FMT_LAYOUT_ID — the surrogate primary key, enforced by HZ_STYLE_FMT_LAYOUTS_B_PK. It uniquely identifies each layout component row and is the column referenced by the translation table.
• STYLE_FORMAT_CODE and VARIATION_NUMBER — together they form the foreign key to HZ_STYLE_FMT_VARIATIONS, anchoring each layout line to a specific style format variation.
• ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID — the foreign key to AK_ATTRIBUTES, identifying the attribute whose value is rendered by this component.
• COMP_STYLE_CODE — the component style applied to this layout element.
• LINE_NUMBER and POSITION — control sequencing and horizontal placement of the component within the formatted output.
• MANDATORY_FLAG, USE_INITIAL_FLAG, and UPPERCASE_FLAG — rendering behavior flags governing whether the element is required, whether initials are used, and whether the value is uppercased.
• TRANSFORM_FUNCTION — the name of the function applied to transform the attribute value before display.
• DELIMITER_BEFORE, DELIMITER_AFTER, BLANK_LINES_BEFORE, BLANK_LINES_AFTER — presentation delimiters and spacing.
• START_DATE_ACTIVE and END_DATE_ACTIVE — date-effective range controlling when the layout component is active.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications framework.

The business-key candidate documented is the unique index HZ_STYLE_FMT_LAYOUTS_B_U1 on (STYLE_FMT_LAYOUT_ID, ZD_EDITION_NAME), reflecting the editioning construct in 12.2.2. The remaining columns are standard audit and editioning fields (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, ZD_EDITION_NAME).

Common Use Cases and Queries

This table is most often queried when diagnosing or customizing how formatted party or account information is rendered. Typical reporting patterns retrieve all layout components for a given variation, ordered by line and position, and join to AK_ATTRIBUTES to resolve the attribute description.

• Inspecting the layout of a variation: join HZ_STYLE_FMT_LAYOUTS_B to HZ_STYLE_FMT_VARIATIONS on STYLE_FORMAT_CODE and VARIATION_NUMBER, ordering results by LINE_NUMBER and POSITION.
• Resolving attribute meaning: join to AK_ATTRIBUTES on ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
• Retrieving display text: join to HZ_STYLE_FMT_LAYOUTS_TL on STYLE_FMT_LAYOUT_ID for the description in the user's language.
• Date-effectiveness filtering: restrict rows where START_DATE_ACTIVE and END_DATE_ACTIVE bracket the report date.

Related Objects

• HZ_STYLE_FMT_VARIATIONS — parent table; joined via STYLE_FORMAT_CODE and VARIATION_NUMBER.
• AK_ATTRIBUTES — defines the attribute rendered; joined via ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
• HZ_STYLE_FMT_LAYOUTS_TL — translation table; references this table via STYLE_FMT_LAYOUT_ID.

These relationships form the core of the style format layout framework within Receivables and TCA.