Results for “xdo_font_mapping_sets_b”

44 results




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

Overview

XDO.XDO_FONT_MAPPING_SETS_B is an XML Publisher (XDO) base table that stores font mapping set definitions used by the BI Publisher rendering engine within Oracle E-Business Suite 12.1.1 and 12.2.2. Font mapping sets allow administrators to define how logical or missing fonts referenced in an RTF or XSL-FO template are translated into concrete physical fonts available on the target rendering server. This is particularly important for multilingual deployments and for PDF output where certain glyphs, such as non-Latin characters, currency symbols, or barcode fonts, must be resolved through an explicit substitution rule. The table holds the header-level definition of each mapping set, while the associated translation table supplies locale-specific descriptions.

The object resides in the XDO schema alongside other XML Publisher repository tables. From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as standalone, suggesting it behaves as an independent reference entity with no inbound foreign key dependencies on other XDO repository tables. It therefore functions conceptually as a reference hub for font mapping set definitions, referenced by configuration and runtime components rather than acting as a transactional link or satellite.

Key Information Stored

The documented physical schema for release 12.2.2 comprises seven columns. The central column is MAPPING_CODE, which serves as the primary key through the constraint XDO_FONT_MAPPING_SETS_B_PK. This code is the business identifier used throughout the application to select a font mapping set at runtime; it is the value administrators and developers reference in profile options, template configuration, and concurrent program parameters. Because the primary key is defined on the natural business code rather than a generated surrogate sequence, MAPPING_CODE is simultaneously the surrogate and business-key candidate in this schema.

MAPPING_TYPE distinguishes the category or scope of the mapping set, determining how the font substitution rules attached to the set are interpreted by the rendering engine. The remaining columns are standard Oracle EBS audit attributes: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These track who defined or last modified the mapping set and when, supporting auditability and troubleshooting. No descriptive or translated name column is present in the _B table, confirming that the design follows the standard EBS pattern in which user-facing text resides in a companion _TL table keyed by MAPPING_CODE and language.

Common Use Cases and Queries

Typical usage involves inventorying configured font mapping sets, verifying which definition is referenced by a given template, and auditing recent changes. A representative query lists the defined mapping sets with their type and audit information:

  • SELECT mapping_code, mapping_type, created_by, creation_date, last_updated_by, last_update_date FROM xdo.xdo_font_mapping_sets_b ORDER BY mapping_code;
  • Filtering by type to isolate a specific category of mapping, for example WHERE mapping_type = :p_type.
  • Change auditing by restricting on last_update_date to identify mapping sets modified since a given date.
  • Joining to the translation table to obtain descriptions for a chosen language, and to detail tables to reconstruct the complete set of font substitution rules.

Reporting scenarios include migration validation, where the list of mapping codes in a source instance is compared with the target instance before and after cloning, and customization reviews, where DBAs confirm that only approved font mapping sets exist in production.

Related Objects

Because the mined relationship data classifies the table as standalone, there are no documented inbound foreign keys. The most significant related objects are therefore those sharing the MAPPING_CODE key or participating in the same rendering configuration:

  • XDO_FONT_MAPPING_SETS_TL — translation table joined on MAPPING_CODE and LANGUAGE.
  • Font mapping detail tables in the XDO schema, joined on MAPPING_CODE, holding individual source-to-target font rules.
  • XDO_TEMPLATES_B / XDO_TEMPLATES_TL — templates that reference a mapping set during rendering.
  • XDO configuration and profile option definitions that supply the active mapping code at runtime.
  • Concurrent program and BI Publisher runtime components that consume the definition when generating PDF or other styled output.