Results for “xdo_font_mappings”

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

Overview

XDO_FONT_MAPPINGS is a configuration table in the XDO schema, the database schema owned by Oracle XML Publisher (BI Publisher) within Oracle E-Business Suite. It stores the mapping rules that resolve a logical, generic font specification into a concrete physical font reference at report-rendering time. When a report template, RTF layout, or XSL-FO style declares a base font (for example, a standard corporate sans-serif), the XML Publisher formatting engine consults XDO_FONT_MAPPINGS to determine which actual TrueType or TrueType Collection (TTC) font should be used for a given language, territory, style, and weight combination. This makes the table the runtime translation layer between template-defined typography and the fonts physically available on the middle-tier or concurrent manager node that performs the rendering.

In Data Vault modeling terms, the heuristic classification for this object is standalone. It exhibits no foreign-key dependency on other documented tables and is keyed entirely by descriptive attributes rather than by a generated surrogate. A modeling exercise would therefore treat it as a reference or lookup structure rather than as a hub, link, or satellite, since its rows represent stable mapping facts rather than transactional events or relationships between business entities.

Key Information Stored

The table contains 14 columns, which together define the resolution rules for font substitution. The primary key, XDO_FONT_MAPPINGS_PK, is a composite business key spanning BASE_FONT, LANGUAGE, MAPPING_CODE, STYLE, TERRITORY, and WEIGHT. There is no single-column surrogate identifier; uniqueness is enforced through this six-column combination.

• BASE_FONT — The logical or template-declared font name to be resolved.
• MAPPING_CODE — The mapping context or rule set under which the substitution applies.
• STYLE — The typographic style (for example, normal or italic) of the base font specification.
• WEIGHT — The font weight (for example, normal or bold) qualifying the base font.
• LANGUAGE — The language context for which the mapping is valid, enabling locale-aware font selection.
• TERRITORY — The territory or regional context narrowing the mapping.
• TARGET_FONT — The physical font that the engine substitutes for the base font.
• TARGET_FONT_TYPE — The type classification of the target font (for example, TrueType).
• TTC_NUMBER — The index within a TrueType Collection file identifying the specific member font.
• CREATED_BY, CREATION_DATE — Standard audit columns capturing row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the session that performed it.

The audit columns follow the conventional Oracle EBS WHO-column pattern and support change tracking and diagnostics.

Common Use Cases and Queries

The primary operational use case is troubleshooting font substitution failures in XML Publisher output. When a rendered report displays incorrect glyphs, missing characters, or unexpected typography, administrators query this table to confirm which TARGET_FONT will be selected for a given BASE_FONT and language/territory combination. A representative query would filter on base font and language:

SELECT base_font, style, weight, language, territory, target_font, target_font_type, ttc_number FROM xdo.xdo_font_mappings WHERE base_font = :p_font AND language = :p_lang;

Reporting use cases include auditing the complete set of substitutions configured for a language or territory, validating that every base font referenced by production templates has a corresponding mapping row, and identifying duplicate or conflicting mapping rules. A coverage query might left-join the distinct base fonts observed in report metadata against this table to surface unmapped fonts. Administrative review of MAPPING_CODE values helps determine which rule set governs a particular class of output. Because the table is relatively small and configuration-oriented, queries are typically unindexed beyond the primary key and are run infrequently by administrators or support personnel rather than by high-volume application logic.

Related Objects

The documented relationship data classifies this table as standalone, with no foreign keys to other database objects. Consequently, its dependencies are logical rather than referential. The most significant related objects are:

• XDO_FONT_MAPPINGS_PK — The composite primary key constraint enforcing uniqueness across BASE_FONT, LANGUAGE, MAPPING_CODE, STYLE, TERRITORY, and WEIGHT.
• XML Publisher runtime font-resolution services in the XDO schema, which read this table during template rendering to select the physical font.
• Other XDO configuration and template metadata tables that store the base font names consumed as input by these mappings.
• The XML Publisher administration user interface, which provides the supported maintenance path for these rows in preference to direct DML.

Direct manipulation of XDO_FONT_MAPPINGS should be avoided in favor of the supported XML Publisher configuration interfaces, since incorrect mappings propagate immediately to all affected report output. Administrators should back up existing rows before any corrective changes and validate results by regenerating affected reports.