If a profile has been changed, you can perform extensive checks for it. You can check the semantics, syntax, and the parameter names of the profile. The system displays the result of the profile checks as a log that contains either warnings or error messages.
The profile parameters in a profile are divided into classes. For each class, there is a separate check rule. The table below shows these rules and includes an example for each:
Parameter Class |
Check Rule |
Example |
---|---|---|
Integer value |
Value smaller than default value: Error Value larger than default by a factor of 10: Warning |
rdisp/TRACE |
Time |
Valid characters are:
Value smaller than 0 or an invalid character: Error |
rdisp/btctime |
Boolean true value. |
Legal values:
Other values: Error |
gw/accept_remote_trace_level |
File Directory |
Directory does not exist: Warning No write authorization: Warning |
rdisp/workdir |
File name |
File does not exist: Error |
abap/rsyn |
TCP computer name |
Host is not known to TCP: Error |
rdisp/mshost |
TCP service name |
Service name is not known to TCP: Error |
rdisp/msserv |
SAP server name |
Server name is not known to SAP system: Error |
rdisp/vbname |
File mask |
Check is not possible |
enque/log_file |
Character string |
Check is not possible |
abap/locale_ctype |
Cannot be changed by customer |
If particular parameters are changed by the customer: Error |
transport/systemtype |
Special parameters |
If value does not contain a particular character string: Error |
rdisp/bufrefmode |
Start Parameters |
If at least one program is not started: Error |