Output & Spool Management

How are old spool requests cleaned up, and what does the standard job leave behind?

What does a device type describe about a printer?

What does the Printing Assistant for Landscapes (PAL) centralize, and how does it distribute definitions?

What's the difference between Transaction SP01 and SP02 for spool requests?

What do spool access methods L, C, S, U, and G mean?

Why is SAP printing split into a spool request and an output request?

What happens if the maximum number of spool requests is reached, and which parameter sets it?

What are spool server classes for, and what are the five of them?

A user's printer is down when they print — why don't they have to recreate the document once it's fixed?

What makes an application server a 'physical' spool server?

When defining an output device in Transaction SPAD, what three things do you specify?

What is SAPSprint, and which access method uses it?

How do you avoid redefining output devices in every system of the landscape?

What do spool work processes do, what's the system minimum, and where are spool requests stored?

Which parameter sets where the TemSe stores data, and what do the options db/G/L/T mean?

What does a logical spool server add over a physical one?

If none of SAP's predefined device types fits your printer, what can you fall back to?

Why can't background jobs or mass printing use frontend printing?

A system migrated from SAP ERP — why should you check its printers for access method F?

What does the spool consistency check compare, and where do you fix inconsistencies?