Results for “xdo_font_mapping_sets_vl”

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

Overview

The XDO_FONT_MAPPING_SETS_VL view is an Oracle XML Publisher (XDO) dictionary object owned by the APPS schema. XML Publisher, also marketed as Oracle BI Publisher, is the template-based publishing engine embedded within Oracle E-Business Suite. It relies on RTF, XSL-FO, and PDF templates to render concurrent program output, and it must resolve font selection deterministically across heterogeneous platforms. Font mapping sets are the configuration mechanism through which BI Publisher translates a logical font requested by a template, such as Arial or Times New Roman, into a physically available font on the target rendering server.

This view is the multilingual (VL) interface to that configuration. Its role is to present font mapping set definitions with the mapping name resolved to the language of the current session, so that forms, list-of-values queries, and diagnostic reports display a user-readable name rather than an internal code. Because it carries a translated name alongside the immutable code, it is the correct object for any reporting or integration layer that must show font mapping sets to an end user. The view is present and valid in both Oracle EBS 12.1.1 and 12.2.2, with an identical structure in each release.

Underlying Base Objects

The view joins two documented base objects, both referenced through APPS synonyms: XDO_FONT_MAPPING_SETS_B, the base table holding language-independent attributes, and XDO_FONT_MAPPING_SETS_TL, the translation table holding language-dependent attributes. The join predicate links the two on MAPPING_CODE, and the translation row is filtered by TL.LANGUAGE = USERENV('LANG'). Consequently, exactly one row is returned per mapping code for the session language, provided a translation exists at that language. The view is defined with no WHERE clause other than the language restriction and no hints, so it behaves as a conventional equijoin. Because the definition is a database view rather than a table, it exposes no independent DML; inserts and updates must be directed at the underlying base and translation tables.

Key Columns

• MAPPING_CODE — The language-independent primary key of the font mapping set and the join key between the base and translation tables. This is the value typically supplied as a parameter to font mapping logic.
• MAPPING_NAME — The translated, user-facing name of the mapping set, sourced from the translation table for the session language. This is the column returned by the user's search term "mapping_name".
• MAPPING_TYPE — Classifies the mapping set, distinguishing the type of font resolution the set performs.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard EBS "WHO" audit columns, inherited from the base table, identifying the user and timestamp of initial creation and the most recent modification.

Common Use Cases and Queries

A frequent requirement is to list all font mapping sets with their display names for a configuration or support report:

SELECT mapping_code, mapping_name, mapping_type
FROM   apps.xdo_font_mapping_sets_vl
ORDER BY mapping_name;

To locate a specific set by its friendly name, or by a partial match:

SELECT mapping_code, mapping_name, mapping_type
FROM   apps.xdo_font_mapping_sets_vl
WHERE  mapping_name LIKE '%ARIAL%';

To audit recently modified mapping sets, the WHO columns support change tracking:

SELECT mapping_code, mapping_name, last_updated_by, last_update_date
FROM   apps.xdo_font_mapping_sets_vl
WHERE  last_update_date > SYSDATE - 30
ORDER BY last_update_date DESC;

Because MAPPING_NAME is resolved through USERENV('LANG'), results depend on the session language; a concurrent program or integration that requires a fixed language should set the session locale explicitly or join to the _TL table directly, rather than relying on the view. This view is read-only and is best treated as a query surface for display and validation; all maintenance of font mapping sets should be performed through the XML Publisher administration pages or against the base tables.