Parameter: LS_TRC_SEVERITY
Definition
Description
This system parameter defines the severity threshold for generating trace messages to the configured destinations (see the LS_TRC_DESTINATION parameter).
The main thresholds are:
- Error information (Default): To use in a productive landscape
- Additional information: To use in a development landscape Informational text, mostly for echoing what has been performed; This level is interesting for a development SAP CC system during the implementation phase of the integration project
- Path information: To use for advanced troubleshooting operations only by a support specialist in the SAP Support Team
See the Syntax section for more information.
Recommendation
SAP SE recommends that you use the default settings in a productive system:
- The SAP CC system generates the traces to the destination fileset #2
- The generation severity threshold is set to ERROR
- No tracing domain is filtered
Caution
Do not change the value of this SAP CC system parameter in a productive landscape, except under the direct supervision of a support specialist from your SAP Support Team, or under specific recommendation provided within the SAP CC documentation.
Before changing the value of this system parameter, check the tracing domains that are enabled in your SAP CC system.
Note
Similar parameters ( LS_APP_SEVERITY and LS_SYS_SEVERITY ) are available to set up the severity thresholds used for the generation of the log messages.
Syntax
Recommendation
Before changing the value of this system parameter, check the tracing domains that are enabled .
The possible threshold values are:
-
DEBUG(**) : For debugging purpose by SAP labs, with extensive and low level information -
PATH(**) : For tracing the execution flow, e.g. used in the context of entering and leaving a method, looping and branching operations -
INFO: Informational text, mostly for echoing what has been performed; This level is interesting for a development SAP CC system during the implementation phase of the integration project -
WARNING: Application can recover from anomaly, and fulfill the desired task, but need attention from developer/operator -
ERROR(Default): Application can recover from error, but cannot fulfill desired task due to the error -
FATAL: Application cannot recover from error, and the severe situation causes fatal termination
Caution (**)
Once set to
DEBUG
or
PATH
level, the SAP CC system generates a high stream of several MB per minute.
Check
before if the file rotation mechanism is available or if you have
only one single file in
the destination
fileset
for traces
or if you have customized the file naming by setting special values.
See Also
- Destination(s) of the trace messages related to the system level: LS_TRC_DESTINATION
Detailed Information
| Name | LS_TRC_SEVERITY
|
|||||||||||||
| Category | Parameter | |||||||||||||
| Type | String | |||||||||||||
| Access (RO/RW) |
RW(-): Dynamic Read / Static Write An immediate change is not possible.
For a deferred and permanent change, use the |
|||||||||||||
| Group(s) | System: Log and Trace Settings | |||||||||||||
| System Instances | This system parameter is available in the following types of instances in a running SAP CC system: rater, updater, guider, bulkloader, taxer, dispatcher | |||||||||||||
| Default Values (Factory Settings) |
|
|||||||||||||
Additional Information
For more information, consult the product documentation of SAP Convergent Charging:
- SAP CC Library (Application Help) about the logging and the tracing functions
- SAP CC Log Message Reference about detailed information for each log message, possible reasons, and follow-up activities
- SAP CC Operations Guide about monitoring and troubleshooting