Automate IFS report printing without duplicate output
Documentation-based guide draft · Reviewed against sources on 2026-09-27 · Not executed in an IFS environment. IFS references use 26R1 unless stated otherwise. Confirm available APIs, components, and permissions in your installed release.
Schedule one report to a logical printer and trace it from report execution to physical output. This procedure avoids direct inserts into report/print tables and does not rely on a person’s browser printer.
Before you start
Section titled “Before you start”Use a development report, a dedicated test logical printer, a functioning Print Agent, and a small fictional data selection that produces one page. Confirm that the account running the schedule can execute the report. Agree a test window with anyone sharing the printer.
1. Prove a manual print first
Section titled “1. Prove a manual print first”Order the report interactively with the exact parameters you intend to schedule. Preview it and record the report ID, layout, language, and result/archive key. Print one copy to the intended logical printer and confirm the physical output.
If this fails, fix the report/layout/printer before adding a schedule. A scheduled run will not repair a broken manual print path.
2. Check the logical-to-physical mapping
Section titled “2. Check the logical-to-physical mapping”Open Logical Printers and confirm the test printer’s ID and description. With the Print Agent administrator, verify that this logical ID maps to the intended physical queue on the agent machine and that the agent is healthy.
Do not map special electronic printers such as SEND_PDF_TO_CONNECT to a physical device. They trigger electronic processing, and they are not supported uniformly by all layout engines. Use the selected report engine’s documented capabilities.
3. Create a one-time scheduled report
Section titled “3. Create a one-time scheduled report”- Open New Database Task Schedule and select the report task offered by the installed system.
- Set a distinctive Schedule Name, such as Lab single report print.
- In Set Parameters, enter the same narrow report selections proven in step 1.
- Select the intended layout, report language, logical printer, and one copy wherever exposed by that report’s scheduling flow.
- In Set Schedule, choose Date and a time a few minutes ahead, checking the environment’s displayed time zone.
- Review options and save the schedule initially inactive if you still need printer defaults configured.
Some reports expose scheduling through their order dialog rather than a generic report choice. Use that report’s supported scheduling action; do not invent a database task that calls undocumented internal print methods.
4. Make printer selection explicit
Section titled “4. Make printer selection explicit”If the scheduling flow does not supply a printer, configure a narrowly scoped default using Report User Printers for the report/user/language combination. Record the previous value. Use Report Printers or User Printers only when their broader scope is intended.
Where a report rule is needed, distinguish Preselect Property from Set Property: a preselection is a default, while Set Property forces the value during printing. Avoid Also Print To in the first test because it creates an additional print destination/job.
Activate the one-time schedule after all destinations are reviewed.
5. Follow the execution evidence
Section titled “5. Follow the execution evidence”After the scheduled time:
- Open the schedule and use View Background Jobs.
- Inspect the associated job state and error details.
- Find the generated item in Report Archive and verify its parameters/result.
- Open Print Manager and match the print job to the archive result and logical printer.
- Check Print Agent/spooler evidence and count physical pages.
Expected result: one scheduled execution, one intended report result, and one physical copy. Report generation success alone does not prove printing.
6. Diagnose without creating duplicates
Section titled “6. Diagnose without creating duplicates”| State | Next action |
|---|---|
| No background job | Check schedule active flag, next run time, and owner |
| Job error before archive result | Inspect report parameters and execution permissions |
| Archive exists, no print job | Check scheduled delivery/printer selection |
| Print job waiting/error | Check Print Agent mapping, connection, and physical queue |
| Output exists but status uncertain | Reconcile agent/spooler first; do not generate another report blindly |
Record archive and print-job identifiers before retrying. Retry the failed stage using its supported recovery action rather than rerunning the entire business transaction.
7. Convert to recurrence only after acceptance
Section titled “7. Convert to recurrence only after acceptance”After the one-time test, choose Daily/Weekly or the required schedule and recheck the next run time. Confirm how long a run takes and prevent overlapping work in the underlying task where necessary.
For cleanup, deactivate the schedule, confirm no job is still pending, and restore printer defaults/rules changed for the lab. Retain the test evidence without leaving a recurring paper-producing job behind.
Scheduling reference: Scheduled Database Tasks.
Sources and scope
Section titled “Sources and scope”Older IFS Applications examples are historical context, not evidence of Cloud compatibility. No third-party code, screenshots, or downloadable workflows are reproduced.