Results for “fnd_printer_tl”

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

Overview

FND_PRINTER_TL is the translation table for FND_PRINTER within the Oracle E-Business Suite Application Object Library (FND) product. It resides in the APPLSYS schema and holds language-specific descriptive text for printer definitions registered in Oracle EBS. In a multi-language or multi-org deployment, base printer records in FND_PRINTER are paired with one row per installed language in FND_PRINTER_TL, allowing printer descriptions to be presented in the end user's session language.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests FND_PRINTER_TL is best treated as a satellite table attached to the FND_PRINTER hub, carrying descriptive, language-dependent attributes rather than defining new business entities or acting as an associative link.

Key Information Stored

The table's documented structure includes ten columns. The most significant are:

• PRINTER_NAME — Core business identifier referencing FND_PRINTER.PRINTER_NAME. Together with LANGUAGE it forms the composite primary key FND_PRINTER_TL_PK.
• LANGUAGE — The NLS language code qualifying each translated row.
• DESCRIPTION — The translated printer description, the primary payload of this translation table.
• SOURCE_LANG — Indicates the language in which the source description was originally entered, supporting the translation integrity model used across FND translation tables.
• ZD_EDITION_NAME — Editioning column included in the unique index FND_PRINTER_TL_U1 (PRINTER_NAME, LANGUAGE, ZD_EDITION_NAME), which serves as the business-key candidate.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, providing standard WHO-column tracking.

The surrogate primary key is FND_PRINTER_TL_PK on (PRINTER_NAME, LANGUAGE), while the unique index FND_PRINTER_TL_U1 adds ZD_EDITION_NAME to that key, reflecting the Editioning feature introduced in EBS 12.2.

Common Use Cases and Queries

Typical usage centers on reporting printer inventories with translated descriptions, verifying that translations exist for each installed language, and troubleshooting printer setup issues. A representative query joining base and translation tables is:

• SELECT p.PRINTER_NAME, t.LANGUAGE, t.DESCRIPTION FROM FND_PRINTER p, FND_PRINTER_TL t WHERE p.PRINTER_NAME = t.PRINTER_NAME;

Filtering by LANGUAGE restricts results to the desired localization. A completeness check can use an outer join between FND_PRINTER and FND_PRINTER_TL to find printers lacking a translation for a specific language. Administrators also query this table to audit CREATED_BY and LAST_UPDATE_DATE when investigating configuration changes.

Related Objects

• FND_PRINTER — The base table; joined on PRINTER_NAME. This is the direct foreign key relationship documented in FND_PRINTER_TL.
• FND_PRINTER_TL_PK / FND_PRINTER_TL_U1 — Primary key and unique indexes enforcing the composite key and Editioning behavior.
• FND_PRINTER_STYLES, FND_PRINTER_DRIVERS — Related printer configuration tables that may participate in reporting joins.
• FND_LANGUAGES — Provides the valid language codes used in the LANGUAGE column.
• FND_PRINTER / FND_CONCURRENT_PROGRAMS — Concurrent programs and requests reference printers, enabling linkage of translation data to concurrent processing reports.

Together these relationships define FND_PRINTER_TL as the localized descriptive satellite of the printer master, essential for multi-language reporting and configuration validation in Oracle EBS 12.1.1 and 12.2.2.