SP01 — Spool Request Management and Output Monitor

SP01 lists spool requests generated anywhere in the system - print jobs, faxes, PDF exports, archived outputs - and lets a consultant inspect, reprint, forward, or delete them. The one fact that explains most of the confusion here: SAP separates the spool request, which is the formatted data sitting on the spool server, from the output request, which is the actual attempt to push that data to a printer, fax device, or archive. SP01 displays both in two separate status columns, and a spool request can show a clean 'completed' status while the output request underneath is stuck, errored, or was never triggered at all. Reading only the top-level icon and declaring the print worked is the single most common mistake made in this transaction.

SP01 is the first stop whenever someone reports a missing printout, a blank page, a garbled PDF, or output that seems to have disappeared. It sits downstream of the business transaction that requested the print - a sales order confirmation, a goods receipt slip, a payment advice - and downstream of the output determination logic that decided a print was needed in the first place. Functional consultants reach for it after confirming the output condition record actually fired; Basis reaches for it when the complaint is really about a device, a queue, or a corrupted spool object rather than about whether the document should have printed at all. On S/4HANA it is still used ahead of any Fiori monitoring app when the question is where a specific spool request went.

Open SE16 on TSP01 and filter by the requesting user and the creation date and time to locate the spool number in question. Compare the status field on the header record against what SP01 shows on screen, since the numeric status code is easy to misread outside the transaction. If no matching spool request exists in TSP01 for the expected window, the problem is upstream of spooling entirely - check NAST for the relevant output type and condition record instead of continuing to search spool tables.

SP01 is unchanged as a transaction on S/4HANA; the spool and TemSe architecture underneath it did not change with the move to HANA. Some Fiori-based output management apps exist for specific processes such as billing correspondence, but they wrap the same underlying spool request rather than replacing it. SP01 remains the direct tool for inspecting an individual spool request across any application area, on either ECC or S/4HANA.

Basis owns the spool server, TemSe consistency, device definitions, and print server connectivity. Functional consultants own why the output determination fired or failed to fire. ABAP gets involved when a Smartform or SAPscript program throws an error during rendering. A useful handover includes the spool request number, the requesting user, the timestamp, the target device, and the exact error text on the output request line, not just a description that printing is broken.

SP02 is the personal view of one's own spool requests and is usually the better tool to point an end user toward, since SP01 has broader authorization scope. SPAD covers device definition and is the next stop when the fault is device-side rather than request-side. SM50 and SM51 matter when the spool work process itself looks hung rather than one individual request being stuck. NAST, while not a transaction covered here, is the record to trace back to when a spool request that should exist was never created in the first place.