Results for “fnd_printer”

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

Overview

WSH_REPORT_PRINTERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Shipping Execution (WSH) product family. It exposes configuration data that governs how shipping-related concurrent programs and reports are routed to physical printers. The view is classified as VALID in both ETRM 12.1.1 and 12.2.2, indicating that its definition and dependencies remain consistent across those releases.

The view's principal role is to present printer-assignment rules in a form suitable for reporting, integration, and administrative inquiry. By combining the WSH configuration table with the FND_PRINTER foundation table, it ensures that only printers currently defined and recognized by the Oracle Applications printer framework are surfaced. This makes the view a reliable source for validating print routing logic, particularly where a shipping report must be directed to a specific device based on organizational or program-level criteria.

For users researching the equipment_instance term, this view is significant because it carries an EQUIPMENT_INSTANCE column, linking a printer assignment to a defined equipment instance. This supports environments where physical print devices are modelled as equipment assets and where routing must respect asset-level identity.

Underlying Base Objects

The documented definition of the view joins two referenced base objects:

• WSH_REPORT_PRINTERS (SYNONYM) — the Shipping Execution configuration table holding report-to-printer assignment records, including program, level, organization, subinventory, formatting, and equipment-instance attributes.
• FND_PRINTER (SYNONYM) — the Applications foundation table that registers printers known to the concurrent manager infrastructure.

The join predicate is WRP.PRINTER_NAME = FPR.PRINTER_NAME. Because the view selects only columns from WSH_REPORT_PRINTERS, the FND_PRINTER join functions as a validation filter rather than a data source. The practical consequence is that any report-printer assignment whose PRINTER_NAME does not exist in FND_PRINTER is excluded from the view. Assignments created against unregistered or subsequently removed printers therefore become invisible, which is a common cause of "missing configuration" investigations.

Key Columns

• APPLICATION_ID / CONCURRENT_PROGRAM_ID — Identify the concurrent program whose output is routed to the printer, scoping the assignment to a specific report.
• LEVEL_TYPE_ID / LEVEL_VALUE_ID — Define the routing granularity, allowing assignments to be resolved at different levels of the shipping hierarchy.
• PRINTER_NAME — The printer identifier, matched against FND_PRINTER; the effective routing target.
• ENABLED_FLAG — Indicates whether the assignment is active; only enabled rows should be considered during runtime resolution.
• EQUIPMENT_INSTANCE — Associates the printer configuration with a defined equipment instance, tying print routing to asset identity.
• ORGANIZATION_ID / SUBINVENTORY — Constrain the assignment to a specific inventory organization and subinventory context.
• FORMAT_TYPE and LABEL_ID — Describe the output format and, where applicable, the label definition used.
• DEFAULT_PRINTER_FLAG — Marks the assignment as the default device for its scope.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield segments for customer-specific extensions.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID / PROGRAM_UPDATE_DATE — Standard audit and concurrent-program context columns.

Common Use Cases and Queries

The view is typically queried to audit printer routing, to verify that expected assignments are visible after the FND_PRINTER filter, and to reconcile equipment-instance-based routing. A basic listing is:

• SELECT concurrent_program_id, printer_name, organization_id, subinventory, equipment_instance, default_printer_flag FROM wsh_report_printers_v WHERE enabled_flag = 'Y';
• To locate assignments tied to a specific equipment instance: SELECT * FROM wsh_report_printers_v WHERE equipment_instance = :p_instance;
• To find default printers per organization: SELECT organization_id, printer_name FROM wsh_report_printers_v WHERE default_printer_flag = 'Y';
• To diagnose invisible configuration, compare row counts between WSH_REPORT_PRINTERS and the view to detect assignments whose PRINTER_NAME is absent from FND_PRINTER.

Because the view applies an inner join to FND_PRINTER, all diagnostic queries should account for that filter before concluding that a configuration record does not exist.