SAP Note 20176 - Where is the spool request saved?

Symptom

How should profile parameter "rspo/store_location" be used?

Reason and Prerequisites

The documentation is unclear.

Solution

For all releases:

Profile parameter "rspo/store_location" controls where TemSe stores the spooler data.

Possible values:

db
(lower case):
TemSe saves the spooler data in the database. Table TST03 is used for this.
Advantages:
Data will be backed up.

G
(upper case):
TemSe saves the data in global files. To do this, TemSe creates subdirectories in the "global" directory. Details of the path name are controlled by profile parameter "rsts/files/root/G". Do NOT change these details.
Advantages:
It is generally much faster.
Disadvantages:
Data is not regularly backed up.

L
T
(upper case):
TemSe saves the data in local files. Because these files can then only be accessed from the same application server, this setting is a special case, and should not be used. (For more information, see: profile parameters "rsts/files/root/L" and "rsts/files/root/T".)
Advantages:
It is much faster.
Disadvantages:
Data is not backed up.
Generating, processing, and spool work process (among others) must all run on the same application server.


As of Release 4.0A:
As of Release 4.0A, you can individually override the value of the profile parameter mentioned above for each output device.
Menu path:
SPAD -> Change output device -> Edit -> Data storage.
If you choose the option file system (local), the system issues a message stating that the data is saved in the local file system (see above) only when possible. The conditions are:

1. Flag "Immediate output" is set.

2. Flag "Delete after output" is set.

3. The function that generates the spool request (the dialog work process) is located on the same server as the output formatter (the spool work process).

Other terms

rspo/store_location, data storage, spool request