SAP Printing issues
Printing problems, output not appearing, going to the wrong device, or garbled, are common user complaints. This page covers diagnosing SAP output issues.
When SAP output does not print, prints to the wrong printer or comes out garbled, first check SP01 for the spool request and its status, then SPAD for the output device's access method, host printer and device type. That separates output not generated from output not delivered. If no spool exists, output determination never triggered.
- Watch out: the spool request and the output request are different objects, and only one reached the printer.
Symptom
A document does not print, prints to the wrong printer, or comes out garbled.
Start here: read the evidence
Check the spool request in SP01 (was output created? what is its status?) and the output device configuration in SPAD (access method, host printer, device type). This separates "output not generated" from "output not delivered".
Likely causes, in order
- Output device misconfigured (wrong access method/host queue).
- Wrong device type, garbled output/formatting.
- Spool/host connectivity, output stuck in the queue.
- Output determination, the document did not trigger output at all.
How to fix it
- Check SP01 for the spool/output request and its status.
- Verify the device in SPAD (access method, host printer, device type).
- Fix the device config or clear the stuck request.
- For "no output", check output determination/condition records.
Preventing recurrence
Configure output devices correctly (access method, device type), monitor stuck output requests, and keep the spool cleaned up. For business documents, verify output determination so the right output triggers automatically.
Common pitfalls
- Guessing instead of reading the log/dump.
- Fixing the symptom, not the root cause.
- Changing several things at once.