Results for “jtf_fm_fnd_printer_v”

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

Overview

JTF_FM_FND_PRINTER_V is a validity-checked database view owned by the APPS schema within the JTF – CRM Foundation product family. As documented in the ETRM repository for Oracle E-Business Suite 12.1.1 and 12.2.2, the view is defined over the FND_PRINTER table and is intended to expose printer definitions maintained by the Oracle Application Object Library in a form suitable for CRM Foundation consumers, reporting, and integration.

The object carries a status of VALID and is catalogued as a view rather than a table, which means it stores no data of its own. Its purpose is to project a stable, application-facing column list over the base printer table while normalizing a small number of columns so that downstream JTF components can treat printer data uniformly. Typical consumers include concurrent program definitions, BI Publisher report configurations, and custom CRM extensions that need to resolve a printer by name without querying the low-level FND table directly.

Because the view is owned by APPS and referenced across product boundaries, it represents the supported integration surface for printer metadata. Direct queries against FND_PRINTER remain possible for administrators, but the view isolates callers from future changes to the base table definition.

Underlying Base Objects

The documented dependent object is FND_PRINTER, accessed through a synonym in the APPS schema. FND_PRINTER is the canonical Oracle EBS repository of printer definitions registered with the concurrent manager and the Reports server. Each row describes one printer name and its associated printer type.

The view text supplied in the ETRM excerpt is:

SELECT PRINTER_NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, PRINTER_TYPE, NULL, 1 FROM FND_PRINTER

Two expressions are notable. The eighth projection emits a literal NULL aliased to F_DELETEDFLAG, and the ninth emits the constant 1 aliased to OBJECT_VERSION_NUMBER. Neither value originates in FND_PRINTER; they are synthesized to satisfy the standard WHO-style contract expected by JTF Framework consumers, which require a deletion indicator and an optimistic-locking version column. The view therefore performs no join and no aggregation; it is a pure projection with two derived columns.

Key Columns

• PRINTER_NAME – The unique identifier of the printer as registered in the EBS environment. This is the column most frequently referenced in ad hoc queries and is the natural key returned when users search for a printer by name.
• LAST_UPDATE_DATE / LAST_UPDATED_BY – Standard WHO audit columns recording when and by which application user the printer definition was last modified.
• CREATION_DATE / CREATED_BY – Standard WHO audit columns recording the original creation event.
• LAST_UPDATE_LOGIN – The login identifier associated with the most recent update, used for session auditing.
• PRINTER_TYPE – Classifies the printer entry according to the printer type stored in FND_PRINTER.
• F_DELETEDFLAG – A derived column that always returns NULL. Consumers should interpret this as "not deleted" and must not rely on it to identify removed printers; deletion is handled by physical row removal in the base table.
• OBJECT_VERSION_NUMBER – A derived column that always returns the constant 1, supplying the version token expected by JTF Framework optimistic-locking conventions.

Common Use Cases and Queries

The view is most often used to validate or display printer names in CRM Foundation screens and reports. A typical lookup filters on a partial printer name:

SELECT printer_name, printer_type, last_update_date FROM apps.jtf_fm_fnd_printer_v WHERE printer_name LIKE :search_name ORDER BY printer_name;

For a complete inventory of registered printers, a straightforward full select is sufficient:

SELECT printer_name, printer_type FROM apps.jtf_fm_fnd_printer_v ORDER BY 1;

Change-audit queries can use the WHO columns without touching FND_PRINTER directly:

SELECT printer_name, created_by, creation_date, last_updated_by, last_update_date FROM apps.jtf_fm_fnd_printer_v WHERE last_update_date >= :from_date;

Because F_DELETEDFLAG is always NULL and OBJECT_VERSION_NUMBER is always 1, these columns should not be used in filtering logic. All meaningful filtering should be performed on PRINTER_NAME and PRINTER_TYPE. The view is read-only in practice; inserts, updates, and deletes must be directed to FND_PRINTER or, preferably, to the supported Oracle forms that maintain printer definitions.