TemSe is a store for temporary sequential data; that is, objects that are not normally permanently held in the system are stored in the TemSe.
The spool system uses the TemSe to store output data temporarily. You can set whether the spool data is to be stored by TemSe in the SAP database or in the file system (for more information, see Storage Methods for Spool Objects in TemSe).
Every TemSe object consists of a header entry in table TST01 and the actual object. This can be stored in the file system (for example, job logs) or in table TST03 (for example, HR data).
There are the following TemSe objects, among others:
· Spool requests (TemSe Name: Spool....)
· Job logs (TemSe Name: JOBLG...)
· Objects from other applications, such as Human Resources (TemSe Name: HR)
· An object whose name begins with KONS; this is object is constantly used by report RSPO1043 and should never be deleted (SAP Note 98065)
With spool requests, you can decide whether the object is stored in the file system or in table TST03. By default, a spool request is stored in table TST03. You have the following options to define a storage location for spool requests:
· Using the profile parameter rspo/store_location; where you can specify file system (parameter value G) or table TST03 (parameter value db)
· In the device definition of an output device (Edit ® File Storage)
Spool requests also have entries in table TSP01 (Spool Requests) and possibly in table TSP02 (Output Requests).
· Storage of temporary objects, such as spool requests and job logs
· Administration and display of temporary objects
TemSe cannot administer objects that require more than two gigabytes of storage space, regardless of whether the objects are stored in the database or in the file system. Spool requests of a size greater than two gigabytes must therefore be split into several smaller requests.
Note that TemSe is not an archiving system. The maximum permissible number of spool requests is limited. The default value is 32000 and can be increased to 2 billion. However, this can affect performance, depending on the capacity of the database and the database host (see SAP Note 48284). You should therefore use the print list archiving option for spool requests.
You can check space usage to avoid storage space problems.