# Printer Not Working in SAP: Troubleshooting Spool Requests with SP01 and SPAD > Source: https://netray.co/erp-help/sap-printer-not-working-spad-sp01-spool-errors > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer When SAP does not print, the answer is in the spool request. Open SP01 (or SP02 for your own), read the status and error text, then check the output device in SPAD: device type, access method, host printer name and whether the spool server and a spool work process are available. Most cases are a wrong device definition, a stopped spool work process or a missing user default. ## Kind error ## System sap ## Erp SAP ECC / S/4HANA ## Module Basis / Spool and Output Management ## Query printer not working in sap ## Alternate Queries - sap spool request error - sap print stuck in waiting - sap spad output device check - sap sp01 spool request failed ## Applies To SAP ECC 6.0 and S/4HANA on-premise, SAP GUI and Fiori printing through the SAP spool. Access method names are consistent across releases. ## Steps ### How to troubleshoot SAP printing step by step **Items:** - Open SP02 (your spool requests) or SP01 (all, with authorization). Find the request and note its status and the output request status. - Read the error text on the output request. Double click the request, then look at the output request details for messages from the print system. - Open SPAD, go to Output Devices and check the device: device type, spool server, access method and host printer. - Run a test print from SPAD (Output Device > Test). If the test works but the application does not, the issue is in the application setup or user defaults. - Check user defaults in SU3 (Defaults > Output Device) and that Output immediately or Delete after output are set as intended. - Check spool processes in SM50 or SM51: at least one spool work process must be available on the spool server. Check SM21 for system log entries. - For Windows printing through SAPSprint, confirm the SAPSprint service is running and the host printer name matches exactly. - Fix, then resend the request from SP01 (Print Again) instead of re-running the transaction. ## Sections ### Reading spool statuses **Body:** A spool request has its own status (for example Waiting, Processing, Printing, Completed or Error) and each output request has one too. A request stuck in Waiting often means output is not set to immediate or no spool work process is free. In Error, the output request text names the cause, such as a printer that cannot be reached. Distinguish between the spool request (the document held in SAP) and the output request (the attempt to send it to a device). You can resend an output request without regenerating the document. ### Checking the output device in SPAD **Body:** Each device in SPAD has a device type (the language the printer understands), a spool server, and an access method that says how SAP reaches the printer: local (L), UNIX (U), the SAP protocol used with SAPSprint (S), front end (F) or direct (C), among others. A mismatch between device type and printer language leads to garbled output or blank pages. For host spooler methods, the printer name must exist on the host exactly as entered. For front-end printing, the user's SAP GUI must be active and the local printer available, so it cannot work for background jobs. **Code:** - SP01 / SP02 Spool requests (all / own) - SPAD Spool administration, output devices - SU3 User defaults: output device - SM50 / SM51 Work processes (spool WP) - SM21 System log - SP12 TemSe administration (consistency check) ### Frequent root causes **Body:** The common ones are: no default printer for the user; a device with the wrong access method; the host print service stopped; a firewall or DNS change that hides the print server; no free spool work process; and a full or inconsistent TemSe store. Background jobs fail when the device uses front-end printing. If a single application prints nothing but others do, check its output determination or print parameters in the transaction, since the document may never have reached the spool. ## Pitfalls - Re-running the transaction instead of resending the spool request, which creates duplicate documents. - Using front-end printing for background jobs, which cannot work. - Wrong device type for label or PDF printers, causing garbled output. - Ignoring SM50 and assuming the printer is the problem when no spool work process is free. - Typing the host printer name with different case or spacing than the host defines. ## Ai Angle Helpdesks spend hours on print tickets. A grounded assistant can look up the spool request, summarize its error text, compare the device definition against known-good ones and suggest the likely fix, leaving any change to Basis. Netray builds assistants like this as private layers, read-only by default, which can run inside your network. ## Faq ### Why is my SAP spool request stuck in Waiting? **Answer:** Usually either output is not set to print immediately, or no spool work process is available on the spool server. Check the user defaults in SU3, then SM50 or SM51 for a free spool work process, and resend the request from SP01. ### What is SPAD used for? **Answer:** SPAD is spool administration. Basis uses it to define output devices, device types, spool servers and access methods, and to run test prints. It is the first place to look when a device itself is misconfigured. ### How do I resend a print job without re-running the transaction? **Answer:** Find the spool request in SP02 or SP01, select it and use the print again function, choosing the right output device. The stored document is reused, so no new document is created. ### Why does printing work in SAP GUI but not in background jobs? **Answer:** Front-end printing sends output through the user's SAP GUI session, which does not exist for a background job. Use a device with a host spooler or SAPSprint access method for scheduled jobs. ## Search terms printer not working in sap, sap spool request error, sap spad output device, sp01 spool, sap print stuck waiting, sap sapsprint, sap output device not found, sap front end printing --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json