Results for “fnd_printer_drivers”

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

Overview

FND_PRINTER_DRIVERS is a foundational configuration table in the Oracle E-Business Suite Application Object Library (FND) product, owned by the APPLSYS schema. It stores the definitions of printer drivers that Oracle EBS uses when generating and formatting concurrent program output for delivery to physical or logical printers. Each row describes a named driver tied to a specific operating platform, along with the command syntax, arguments, initialization and reset strings, and behavioral flags required to route and format a print job correctly. The table is present and valid in both EBS 12.1.1 and 12.2.2, with 12.2.2 exposing 35 documented columns, including the editioning column ZD_EDITION_NAME introduced by the online patching (ADOP) architecture.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone, meaning it is neither a hub, link, nor satellite. This is consistent with its role as a reference or lookup configuration table: it has no outbound foreign keys to other business entities and is referenced by name and platform rather than by a meaningless surrogate identifier. Its composite business key (PRINTER_DRIVER_NAME, PLATFORM_CODE) functions as the natural identifier.

Key Information Stored

The most significant columns fall into identification, platform mapping, and command execution categories.

• PRINTER_DRIVER_NAME — the internal driver identifier, part of the primary key FND_PRINTER_DRIVERS_PK and the unique key FND_PRINTER_DRIVERS_U1.
• PLATFORM_CODE — the target operating platform for the driver, also part of the primary and unique keys. It distinguishes drivers that share a name across heterogeneous hosts.
• USER_PRINTER_DRIVER_NAME — the user-facing display name, forming the business-key candidate FND_PRINTER_DRIVERS_U2 together with PLATFORM_CODE.
• PRINTER_DRIVER_METHOD_CODE — indicates the printing method or mechanism employed by the driver.
• COMMAND_NAME — the executable or spooler command invoked when the driver is used.
• ARGUMENTS — the argument string passed to the command for a given print request.
• INITIALIZATION and RESET — control sequences emitted before and after the print stream.
• SPOOL_FLAG and STDIN_FLAG — flags controlling whether output is spooled and whether input is piped via standard input.
• SRW_DRIVER and HEADER_FLAG — driver typing and header suppression behavior.
• DESCRIPTION and ATTR_CATEGORY — descriptive text and descriptive flexfield context.
• ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments available for site-specific extension.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide the standard audit trail.
• ZD_EDITION_NAME — the edition identifier supporting 12.2 online patching.

No surrogate primary key column is documented; the primary key is composed entirely of the two natural business columns named above.

Common Use Cases and Queries

Administrators and developers query this table to audit printer driver configuration, troubleshoot concurrent output that fails to print, or migrate driver definitions between environments.

• Listing all drivers for a platform: SELECT printer_driver_name, user_printer_driver_name, printer_driver_method_code FROM fnd_printer_drivers WHERE platform_code = :platform;
• Retrieving full command syntax for a specific driver: SELECT command_name, arguments, initialization, reset FROM fnd_printer_drivers WHERE printer_driver_name = :name AND platform_code = :platform;
• Identifying recently modified drivers via the audit columns.
• Reporting on drivers that pipe through standard input using STDIN_FLAG.
• Verifying edition-scoped rows in 12.2 by filtering on ZD_EDITION_NAME.

These queries underpin printer setup validation and post-clone configuration reviews.

Related Objects

Although the metadata classifies this object as standalone, printer driver definitions participate in the FND printer configuration model. Significant related objects include:

• FND_PRINTERS — printer definitions that reference a driver by PRINTER_DRIVER_NAME and PLATFORM_CODE.
• FND_PRINTER_STYLES — print styles linked to drivers for output formatting.
• FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS — concurrent programs and their runtime requests that select a printer and driver during output delivery.
• FND_PRINTER_DRIVER_METHODS — lookup values referenced by PRINTER_DRIVER_METHOD_CODE.
• FND_DESCR_FLEX_COLUMN_USAGES — descriptive flexfield definitions mapped to ATTR_CATEGORY.

The primary join path to dependent tables is PRINTER_DRIVER_NAME combined with PLATFORM_CODE.