Results for “fnd_printer”

50+ results




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

Overview

FND_PRINTER is a registration table in the Oracle Application Object Library (product FND) that stores printers known to the E-Business Suite concurrent processing environment. It is owned by the APPLSYS schema and is documented as VALID for EBS 12.1.1 and 12.2.2. Every printer definition available to the Report Manager, concurrent managers, and reporting tools is rooted in a row in this table; the printer name stored here becomes the reference key that concurrent programs, requests, request sets, run requests, distribution lists, and shipping report printers use to designate a destination device.

In Data Vault terms, the heuristic classification of FND_PRINTER is hub-leaning. It carries a single-column business key, PRINTER_NAME, which is referenced by many dependent tables, and it does not itself accumulate transaction-like measures. This suggests modeling the object as a hub for printers, with the dependent tables treated as links or satellites that resolve to this hub through the printer name.

Key Information Stored

The table comprises eight documented columns in the APPLSYS schema. The most significant are:

  • PRINTER_NAME — The business identifier of the printer. It is the primary key component of FND_PRINTER_PK and the column carried as a foreign key into dependent tables.
  • PRINTER_TYPE — Classifies the printer and references FND_PRINTER_TYPES, linking each registration to a defined printer type.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns identifying when and by whom the record was last maintained.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording initial creation of the printer registration.
  • ZD_EDITION_NAME — The editioning column used by the 12.2 online patching architecture; it participates with PRINTER_NAME in the unique index FND_PRINTER_U1 (PRINTER_NAME, ZD_EDITION_NAME).

The surrogate primary key is defined by FND_PRINTER_PK on PRINTER_NAME. The unique index FND_PRINTER_U1 (PRINTER_NAME, ZD_EDITION_NAME) is the strongest business-key candidate, because it combines the semantic printer identifier with the edition qualifier required in 12.2.2.

Common Use Cases and Queries

Typical scenarios include identifying all printers available to a concurrent program, auditing which targets are referenced by outstanding or historical requests, and reconciling printer usage across request sets. The following patterns are representative:

  • List printers and their types: SELECT p.printer_name, p.printer_type, p.last_update_date FROM fnd_printer p ORDER BY p.printer_name;
  • Find requests directed to a specific printer: SELECT r.request_id, r.printer FROM fnd_concurrent_requests r WHERE r.printer = :printer_name;
  • Locate programs defaulting to a printer: SELECT c.concurrent_program_name, c.printer_name FROM fnd_concurrent_programs c WHERE c.printer_name IS NOT NULL;
  • Report distribution lists referencing a printer: SELECT d.distribution_list_name, d.printer FROM alr_distribution_lists d WHERE d.printer = :printer_name;

These queries support operational reporting, printer decommissioning analysis, and migration checks when printers are renamed or removed.

Related Objects

FND_PRINTER functions as a referenced hub. The most significant dependent tables, resolved through PRINTER_NAME, include: