Table name: /USI/BAL_SL_BEHA
Maintained via: SM30

Generally, the API prevents log fragmentation to simplify support. The underlying concept is explained here.

Log fragmentation can be prevented in different ways:

• Reuse: A log writer, once created, can be reused everywhere so that all API consumers write to the same log.
• Linking: Each consumer creates its own log writer, and the logs are linked via trace messages that allow navigation between them.

The desired behavior for each log object and sub-object can be configured in this table.

The settings are evaluated whenever a new log writer is requested from the factory.

The structure of all customizing tables has been documented in a unified format.

General Information explains how this documentation is to be read.

Fieldname	Fieldtype	Filter-Priority	Description
LOG_OBJECT	Filter	1	Log object
SUB_OBJECT	Filter	2	Sub object
BEHAVIOR	Data		Desired behavior

Currently four different behaviors are available.

Technical value	Short Description	Creates new logger, if
0	Create new logger	ALWAYS
3	Reuse existing logger, if Log Object & Subobject match	No logger existed before or the previously created logger has a different combination of Log-Object and Subobject
6	Reuse existing logger, if Log Object matches	No logger existed before or the previously created logger has a different Log-Object
9	Reuse existing logger	No logger existed before

Linking logs via trace messages will only work, if the data containers /USI/CL_BAL_DC_PARENT_LOG and /USI/CL_BAL_DC_CHILD_LOG are relevant on log level 1!

A description of that customizing can be found here:
Customizing -> Log Levels -> Relevant Data containers

The recommended settings can be taken from the installation guide.
Installation Guide -> Maintain Basic Customizing

If no suitable customizing can be found, the following default values will be applied.

Fieldname	Default
BEHAVIOR	0 (Create new logger)