Results for “jtf_fm_printer_lookups_v”

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

Overview

The JTF_FM_PRINTER_LOOKUPS_V view resides in the APPS schema within the JTF - CRM Foundation product family. It is documented in the E-Business Suite Electronic Technical Reference Manual (ETRM) with the concise description "View to lookup printers." Its purpose is to consolidate printer and print-server information into a single denormalized result set, joining four JTF Foundation (FM) tables so that callers do not need to assemble the relationships themselves. In Oracle EBS 12.1.1 and 12.2.2 the object carries a VALID status and is the type VIEW, meaning it contains no data of its own; it derives every row from its underlying tables at query time.

In practice the view serves reporting, diagnostic, and integration scenarios where an application or administrator must resolve which printers are reachable through which print servers, and what API values those printers expose to the runtime. It is characteristic of the JTF CRM Foundation "FM" (Foundation Management) family, which centralizes shared infrastructure services such as print server registration used across CRM and related modules.

Underlying Base Objects

The ETRM metadata lists four referenced base objects, each exposed through APPS synonyms: JTF_FM_PRINTER, JTF_FM_PRINTERS, JTF_FM_PRINT_SERVERS, and JTF_FM_SERVICE_ALL. The view text joins them with an equi-join chain:

• JTF_FM_SERVICE_ALL A is joined to JTF_FM_PRINTER B on A.SERVER_ID = B.SERVER_ID.
• JTF_FM_PRINTER B is joined to JTF_FM_PRINT_SERVERS C on B.PRINT_SERVER_ID = C.PRINT_SERVER_ID.
• JTF_FM_PRINTER B is also joined to JTF_FM_PRINTERS D on B.PRINT_SERVER_ID = D.PRINT_SERVER_ID.

Consequently JTF_FM_PRINTER acts as the central bridge table, linking a registered server to its print server and to the individual printers defined for that print server. JTF_FM_SERVICE_ALL supplies the top-level server identity, while JTF_FM_PRINT_SERVERS contributes physical naming and server type, and JTF_FM_PRINTERS contributes printer naming and API values. Because the joins are ordinary equi-joins with no outer-join syntax, a printer or print server record without a matching bridge row will not appear in the result set.

Key Columns

The view exposes six columns, drawn from different base objects:

• SERVER_ID — from JTF_FM_SERVICE_ALL; identifies the registered service/server in the foundation model.
• PRINT_SERVER_ID — the print server identifier, present in the bridge and reused for the joins to print servers and printers; it is the key correlation column in the view.
• PHYSICAL_NAME — from JTF_FM_PRINT_SERVERS; the physical (host or node) name associated with the print server.
• PRINT_SERVER_TYPE — from JTF_FM_PRINT_SERVERS; classifies the print server implementation.
• PRINTER_NAME — from JTF_FM_PRINTERS; the printer's descriptive name as exposed by the view.
• PRINTER_API_VALUE — from JTF_FM_PRINTERS; the value passed to the print API when the printer is selected at runtime.

Note that the fourth column of the PRINT_SERVER_ID join target, JTF_FM_PRINTERS, is keyed on PRINT_SERVER_ID in the documented join expression, so a single print server may resolve to multiple printer rows through D.

Common Use Cases and Queries

Typical scenarios include verifying printer-to-print-server mappings during setup or troubleshooting, auditing which physical names and server types back a given printer name, and populating integration or reporting extracts that require the PRINTER_API_VALUE for a named printer. The view is useful for support diagnostics where a user reports that a printer is unavailable, since it exposes both the physical print server name and the printer API value in one pass.

A basic listing of all printer lookups is:

• SELECT server_id, print_server_id, physical_name, print_server_type, printer_name, printer_api_value FROM apps.jtf_fm_printer_lookups_v ORDER BY physical_name, printer_name;

To locate the API value used for a specific printer, or to search by physical server name, the same view can be filtered:

• SELECT printer_name, printer_api_value, physical_name FROM apps.jtf_fm_printer_lookups_v WHERE printer_name LIKE :printer_pattern;
• SELECT printer_name, physical_name, print_server_type FROM apps.jtf_fm_printer_lookups_v WHERE physical_name = :server_host;

Because the object is a view over synonyms owned in APPS, access should be granted through the APPS schema or an appropriate custom synonym and privileges; direct DML is not applicable. Performance depends on the indexes on SERVER_ID and PRINT_SERVER_ID in the underlying JTF_FM tables.