Parameter
rsts/filename
Short text
Rule for creation of TemSe directory and file name
Parameter Description
This parameter contains the rule for generating the TemSe object name in the file system. This can also be a combination of a directory and file name (relative path name).
Application Area
TemSe
Default Value
5.5n/.15n
Are other parameters affected or dependent?
rsts/filename , rspo/store_location rsts/files/root/G , rsts/files/root/L , rsts/files/root/T .
Values allowed
The rule is interpreted as follows:
• &c is the three-digit client name with leading zeros
• &p is the part number for the object (should comprise four characters)
• &n is the TemSe object name as it appears in R/3 (a maximum of 20 characters for the TemSe object)
• / creates a directory from the preceding string. The numbers are length specifications (minimum and maximum length). 5.5 means min. 5 and max. 5 : exactly 5 characters. 15 means a maximum of 15 characters with no minimum length.
Example
TemSe object name SPOOL1234567890 part 1 and client 066 with creation rule: 5.5n/.15n
Result: 066 SPOOL / 0001 1234567890
The relative path name is: 066SPOOL/0011234567890
The “relative” file name created in this way is then prefixed with the value from parameter rsts/files/root/G, rsts/files/root/L, or rsts/files/root/T. This results in an absolute file name for the TemSe object in question.
Parameter rspo/store_location specifies whether
• rsts/files/root/G, rsts/files/root/L, or
• rsts/files/root/T is used:
• rspo/store_location =G –> rsts/files/root/G
• rspo/store_location =L –> rsts/files/root/L
• rspo/store_location =T –> rsts/files/root/T
Example with rspo/store_location=G (and standard assumptions):
/usr/sap/[SID]/SYS/global/066SPOOL/00011234567890
You should not change this creation rule. If you change the rule, this results in an incompatible change to the file names created, which means that “old spool requests” can no longer be processed. It is not possible to manage “old” and “new” spool requests in the same R/3 system. This inevitably leads to inconsistencies and errors in the spool/TemSe system.
