Infor LN Print Management: Complete Configuration Guide
Print management in Infor LN controls how every document in the system—from purchase orders to shipping labels to financial statements—is routed to its destination. The print management system encompasses device configuration (printers, email, file, archive), output routing rules (which document goes where based on business context), and the Document Output Management (DOM) layer that orchestrates multi-channel delivery. Proper configuration is critical because manufacturing operations depend on timely, accurate document delivery to the shop floor, suppliers, customers, and regulatory bodies.
Device Configuration and Printer Setup
LN uses a logical device abstraction layer that maps logical device codes to physical output destinations. A logical device can point to a network printer, an email address, a file directory, or an archive system. Every report session in LN sends output to a logical device, and the device configuration determines the final delivery. This abstraction allows administrators to change the physical printer for an entire department by updating a single device record, without modifying any session configurations.
- Define logical devices: navigate to Device Management (ttadv3500m000); create a device code (e.g., DEV-SHOP-FLOOR-1) with device type (Printer, File, Email, Archive); for printer devices, specify the print queue name as configured in the operating system's print server
- Printer driver configuration: LN supports PostScript, PCL, ZPL (Zebra), and PDF as output formats; set the output format in Device Properties > Driver tab; for barcode label printers, select ZPL and configure the label dimensions and DPI in the device's format settings
- Network printer connectivity: LN connects to network printers via the operating system print spooler; ensure the LN application server's service account has 'Print' permission on each network printer; test connectivity with a manual test print from the Device Management form
- PDF output: configure a PDF device for electronic document distribution; set Device Type = File, Output Format = PDF, and the target directory path; LN generates a PDF file with the report name and timestamp; combine with DOM rules for automatic email delivery
- Default device assignment: in User Preferences (ttaad4100m000), assign a default output device for each user; this device is pre-selected when the user prints from any session; users can override the default for individual print jobs
Output Routing Rules and Conditional Printing
Output routing rules determine which device receives a document based on business context. For example, a Purchase Order for a domestic supplier routes to email delivery, while a PO for an international supplier routes to printed hardcopy with a faxed copy. Routing rules are evaluated in priority order, and the first matching rule determines the output destination. This eliminates the need for users to manually select the correct printer or delivery method for each document.
- Define routing rules: navigate to Output Routing (ttadv3600m000); create rules with conditions: Document Type = 'Purchase Order' AND Supplier Country = 'US' → Device = DEV-EMAIL-PDF; Document Type = 'Purchase Order' AND Supplier Country != 'US' → Device = DEV-PRINTER-INTL
- Multi-destination routing: a single document can be routed to multiple devices simultaneously; for example, route a Sales Invoice to (1) email to customer, (2) print to AR department, and (3) archive to DMS; create three routing rules with the same condition but different target devices
- User-overridable routing: set the Override flag on routing rules to allow users to change the destination at print time; set Override = No for compliance documents (tax invoices, regulatory reports) that must always route to the designated archive
- Conditional copy count: routing rules can specify the number of copies; for packing slips, route 1 copy to the shipping desk and 2 copies to the packing area based on the warehouse field in the shipment record
- Rule testing: use the Routing Simulation tool (ttadv3610m000) to test which rules match a given document/context combination without actually printing; enter the document type and context fields to see the matched rules and destinations
Troubleshooting Print Failures in LN
Print failures in LN manifest as silent drops (the document never appears at the printer), error messages ("Device [code] is not available"), or garbled output (wrong format, missing fonts, incorrect character encoding). Silent drops are the most dangerous because users do not know the document was not delivered until a customer or supplier reports the missing paperwork. Systematic troubleshooting requires checking each layer: the LN output queue, the operating system spooler, and the physical printer.
- Error: "Device is not available" — verify the device exists in Device Management (ttadv3500m000) and its status is Active; check that the mapped printer queue is online in the operating system print server; restart the Windows Print Spooler service if the queue is stuck
- Silent print drops: check the LN output queue (ttadv3700m000) for entries with status 'Queued' or 'Error'; queued items indicate the LN print service is not processing the queue (restart it); error items show a specific error message in the detail record
- Garbled output: wrong character encoding — verify the device's codepage setting matches the printer's configured codepage; for international installations, use UTF-8 encoding in the device configuration and ensure the printer firmware supports the required character set
- Performance: print queue backlog — if the LN output queue has thousands of pending items during peak hours, increase the number of print service threads in System Parameters (ttadv0100m000) > Print Settings > Max Concurrent Print Jobs from the default 3 to 8-10
- Monitor print health: create a BShell monitoring session that runs every 15 minutes, checks the LN output queue for items older than 30 minutes, and sends an alert email to the IT team; this catches print failures before users report them
Optimize your Infor LN document workflows with Netray's AI-powered print management analysis—ensure zero document delivery failures.
Related Resources
Infor LN Report Development Guide
Create and customize Infor LN reports using BShell report sessions, Crystal Reports integration, and Infor Document Output Management for BAAN/LN systems.
Infor LNInfor LN Batch Jobs and Scheduling Guide
Optimize Infor LN batch job scheduling including MRP runs, GL posting, data replication, and job queue management for maximum throughput and reliability.
Infor LNInfor LN Workflow Automation Setup Guide
Configure Infor LN workflow engine for approval routing, escalation rules, and automated business process orchestration with step-by-step setup instructions.