Index	Log Message	Description	Impacts	Actions	Information
0 (INFO)	Starting an instance for {0} (Technical Version Number: {1})	This instance of the SAP CC Core Server system is going to start.			See the SAP CC 5.0 Installation Guide to know how to apply for a license and how to import it in your SAP CC Core Server system.
1 (INFO)	{0} ({1}), the instance {2} is started in system {3}	This instance of the SAP CC Core Server system has successfully started.
2 (ERROR)	Cannot initialize the network interfaces of the host machine	An input/output (I/O) error occurred while initializing the network interfaces of the machine hosting this instance of the SAP CC Core Server system.	The instance communications will not work.	Troubleshoot your SAP CC system: Verify the network interfaces of this host.
3 (FATAL)	System property [{0}] is missing in the startup configuration file	A property is not set in the startup configuration file (jstart.config) of this instance of the SAP CC Core Server system. Example The system property boot.config must be present and set to the path of the boot configuration file.	This instance of the SAP CC Core Server system will not start.	Correct the startup configuration file (jstart.config) of this instance of the SAP CC Core Server system. Verify the JVM option (the javaParameters key) in this file. This key includes the declaration of various system properties. Insert or adjust the -Dboot.config= entry as stated in the log message. Save the file. Verify the other instances of the SAP CC system. Restart this instance of the SAP CC system.	Startup Configuration File (jstart.config) Each instance of the SAP CC Core Server system uses a startup configuration file (jstart.config) to start. The system instance gets the JVM options necessary for the Java runtime environment. You set up the JVM options in this startup configuration file. Consult the SAP CC 5.0 Configuration Guide to know how to administer this file.
4 (FATAL)	Cannot read the boot configuration file in [{0}]	An error occurred while trying to read the boot configuration file of this instance of the SAP CC Core Server system.	This instance of the SAP CC Core Server system will not start.	Check the previous log messages Correct the error Restart this instance of the SAP CC system
5 (FATAL)	Out of memory in thread [{0}]	The instance of the SAP CC Core Server system cannot allocate more memory.	This instance of the SAP CC Core Server system will not start.	Correct the startup configuration file (jstart.config) of the instance of the SAP CC Core Server system: Check the JVM option (the javaParameters key) in this file. This key includes the declaration of various system properties. Insert or adjust the -Xmx= entry as stated in the log message Save the file Check the other instances of the SAP CC system. Restart this instance of the SAP CC system.	Startup Configuration File (jstart.config) Each instance of the SAP CC Core Server system uses a startup configuration file (jstart.config) to start. The system instance gets the JVM options necessary for the Java runtime environment. You set up the JVM options in this startup configuration file. Consult the SAP CC 5.0 Configuration Guide to know how to administer this file.
6 (FATAL)	Launching of {0} aborted due to unknown errors	Unknown errors occurred during the launching of this instance of the SAP CC Core Server system.	This instance of the SAP CC Core Server system will not start.	Troubleshoot your SAP CC Core Server system to identify a possible cause: Analyze the technical information in the trace messages Correct the error(s) Restart this instance of the SAP CC system Otherwise: Enable and configure the generation of traces Set up the trace severity threshold to PATH Restart this instance of the system Analyze the technical information in the trace messages Correct the error(s) Restart this instance of the SAP CC system Check if other instances of the SAP CC system cannot start.
7 (FATAL)	Launching of {0} aborted due to previous errors	Errors occurred during the launching of this instance of the SAP CC Core Server system.	This instance of the SAP CC Core Server system will not start.	Troubleshoot your SAP CC system to identify a possible cause: Check the previous log messages for errors Correct the error(s) Restart this instance of the SAP CC system
8 (FATAL)	License not found or cannot be read	This instance of the SAP CC Core Server system cannot find or read the license.	This instance of the SAP CC Core Server system will not start.	Insert the license in SAP CC Core Database that is connected to SAP CC Core Server.	See the Configuration Guide and the Installation Guide to know how to apply for a license and how to install it in the SAP CC Core Server system.
9 (FATAL)	License is corrupted	The SAP Convergent Charging license has been corrupted.	This instance of the SAP CC Core Server system will not start.	Troubleshoot your SAP CC system: Try to remove and insert again your license file If the problem persists then apply for a new license file	Consult the SAP CC 5.0 Configuration Guide and the SAP CC 5.0 Installation Guide to know how to apply for a permanent or temporary license and how to install it in the SAP CC Core Server system.
10 (FATAL)	License has expired	Your SAP Convergent Charging license has expired.	This instance of the SAP CC Core Server system will not start.	Apply for a new license file Install a valid license file	Consult the SAP CC 5.0 Configuration Guide and the SAP CC 5.0 Installation Guide to know how to apply for a permanent or temporary license and how to install it in the SAP CC Core Server system.
11 (FATAL)	Not enough memory to verify the license	This instance of the SAP CC Core Server system has not enough memory to manage the license. It cannot verify the license.	This instance of the SAP CC Core Server system will not start.	Correct the startup configuration file (jstart.config) of this instance of the SAP CC Core Server system. Check the JVM option (the javaParameters key) in this file. This key includes the declaration of various system properties. Insert or adjust the -Xmx= entry Save the file Check the other instances of the SAP CC system. Restart this instance of the SAP CC system.	Startup Configuration File (jstart.config) Each instance of the SAP CC Core Server system uses a startup configuration file (jstart.config) to start. The system instance gets the JVM options necessary for the Java runtime environment. You set up the JVM options in this startup configuration file. Consult the SAP CC 5.0 Configuration Guide to know how to administer this file.
12 (FATAL)	License is not valid for this host	This instance of the system is verifying the license installed for its host but the license is not valid for this host machine.	This instance of the SAP CC Core Server system will not start. The other instances installed on this host will not start.	Check you started the instance on the expected host machine Compare the hardware key(s) of the SAP CC Core Server system to the hardware key(s) of the license file Get the hardware keys from the hardware_keys.txt file. There is a key for each host of the system. Get the hardware keys declared in the installed licenses. You can use the Setup Configuration Tool to export the licenses in a file Check that the hardware keys are correct Install a valid license for the hardware key of this host machine Restart this instance of the SAP CC system	The licenses are linked to the hardware you are running the SAP CC Core Server system on. See the SAP CC Configuration Guide and the SAP CC Installation Guide to know where to find the hardware key of your SAP CC Core Server installation, how to export the licenses, how to install licenses.
13 (ERROR)	Invalid system properties for logging and tracing settings. Degraded mode is set temporarily.	Some of the system properties set in the startup configuration file (jstart.config) are invalid for this instance of the SAP CC Core Server system to set up the logging and the tracing functions.	This instance of the SAP CC Core Server system did not apply the logging and tracing settings set in the startup configuration file. The instance will temporarily apply some degraded settings for the logging and tracing functions and continue the launching phase: It loads the final configuration settings from SAP CC Core Database.	Check the JVM option (javaParameters) in the startup configuration file (jstart.config) of the instance of the SAP CC system. Check the system properties that configure the logging and the tracing functions during the first phase of the launch. Use the SAP CC System Parameter Reference to know the correct values. Example -Dls.trc.severity=PATH Correct these system properties. Restart this instance of the SAP CC system.	You can set up the following system properties in the JVM option: ls.app.severity ls.sys.severity ls.trc.severity ls.app.destination ls.sys.destination ls.trc.destination ls.trc.domain ld.console.formatter ld.file1.enabled ld.file1.name ld.file1.size ld.file1.setsize ld.file1.formatter ld.file2.enabled ld.file2.name ld.file2.size ld.file2.setsize ld.file2.formatter ld.file3.enabled ld.file3.name ld.file3.size ld.file3.setsize ld.file3.formatter ld.file4.enabled ld.file4.name ld.file4.size ld.file4.setsize ld.file4.formatter ld.file5.enabled ld.file5.name ld.file5.size ld.file5.setsize ld.file5.formatter Note Consult the SAP CC System Parameter Reference to determine the values allowed for these system properties. The ranges of values are the same. Startup Configuration File (jstart.config) Each instance of the SAP CC Core Server system uses a startup configuration file (jstart.config) to start. The system instance gets the JVM options necessary for the Java runtime environment. You set up the JVM options in this startup configuration file. Consult the SAP CC 5.0 Configuration Guide to know how to administer this file.
14 (FATAL)	System property [{0}] is missing. Set up the JVM option with '-D{0}=<ID>' or set up the program option '-{0} = <ID>' where <ID> is the identifier of a {1} instance.	The instance ID has not been specified to the launcher.	This instance of the SAP CC Core Server system cannot start.	Correct the JVM option (javaParameters) in the startup configuration file (jstart.config) of the instance Restart this instance of the SAP CC system	The instance ID is of the form: <instanceType>#<instanceNumber> The possible values for <instanceType> are: dispatcher bulkLoader guider rater taxer updater Example Example of instance ID: dispatcher#1 Startup Configuration File (jstart.config) Each instance of the SAP CC Core Server system uses a startup configuration file (jstart.config) to start. The system instance gets the JVM options necessary for the Java runtime environment. You set up the JVM options in this startup configuration file. Consult the SAP CC 5.0 Configuration Guide to know how to administer this file.
15 (FATAL)	Invalid instance ID value [{1}] of the system property [{0}]	The value set as instance ID is wrong in the startup configuration file (jstart.config).	This instance of the SAP CC Core Server system cannot start.	Check that the property value specified to the JVM or to the launcher is correct.	The instance ID is of the form: <instanceType>#<instanceNumber> The possible values for <instanceType> are: dispatcher bulkLoader guider rater taxer updater Example Example of instance ID: dispatcher#1 Startup Configuration File (jstart.config) Each instance of the SAP CC Core Server system uses a startup configuration file (jstart.config) to start. The system instance gets the JVM options necessary for the Java runtime environment. You set up the JVM options in this startup configuration file. Consult the SAP CC 5.0 Configuration Guide to know how to administer this file.
16 (INFO)	Starting the Bulk Loading Service	This bulkloader instance started to launch its Bulk Loading Service.
17 (ERROR)	Cannot initialize the multicast service	An error occurred while initializing the multicast service.	This bulkloader instance of the SAP CC Core Server system will not start.	Troubleshoot your SAP CC system to identify a possible cause: Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Restart this instance of the SAP CC system Analyze the technical information in the traces
18 (ERROR)	Cannot configure a function of the SAP CC system	An error occurred while configuring the sources	This bulkloader instance of the SAP CC Core Server system will not start.	Troubleshoot your SAP CC system to identify a possible cause: Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Restart this instance of the SAP CC system Analyze the technical information in the traces
19 (INFO)	Bulk Loading Service started ({0} threads)	The Bulk Loading Service successfully started.
20 (WARNING)	Exception occurred while stopping the Charging output Integration Framework	At least one CIF processor raised an exception during the bulkloader instance stop sequence.	The data files may have not been closed properly. Depends on the CIF configuration of the bulkloader.	Troubleshoot your SAP CC system to identify a possible cause: Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Restart this instance of the SAP CC system Analyze the technical information in the traces during the stop sequence
21 (INFO)	Shutting down the Bulk Loading Service	This bulkloader instance of the system has started to shut down its service.
22 (INFO)	Bulk Loading Service stopped	The Bulk Loading Service is stopped.
23 (ERROR)	Cannot start the HTTP listener of the dispatcher instance	The HTTP listener of this dispatcher instance cannot start because it cannot load its XML schema configuration. This error occurs if the dispatcher instance cannot find the XML schema or because of a parsing error.	This dispatcher instance of the SAP CC Core Server system will not start.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
24 (INFO)	Starting the Dispatcher Internal Service	This dispatcher instance started to launch the internal service for the SAP CC Core Server system.
25 (INFO)	Waiting for the master dispatcher instance of the SAP CC system	This slave dispatcher instance is waiting for the connection from the master dispatcher instance of the SAP CC Core Server system.
26 (INFO)	{0} Dispatcher Internal Service started and available at the address: {1}:{2}	This dispatcher instance has started its dispatching service for the internal communications of the SAP CC Core Server system.
27 (INFO)	Internal Discovery Service started at network bindpoint {0}:{1} observing multicast address {2} for system {3}	The internal discovery service of the dispatcher instance is started.
28 (ERROR)	Cannot initialize the Internal Service	An error occurred while starting the internal service of this dispatcher instance of the SAP CC Core Server system.	This dispatcher instance of the SAP CC Core Server system will not start.
29 (INFO)	Starting the Dispatcher External Service	This dispatcher instance started to launch its external service.
30 (INFO)	{0} Dispatcher External Service started at the address: {1}:{2}	The external service of the dispatcher instance is started.
31 (INFO)	External Discovery Service started at network bindpoint {0}:{1} observing multicast address {2} for system {3}	The external discovery service of the dispatcher instance is started.
32 (ERROR)	Cannot initialize the External Service	An error occurred while starting the external service of the dispatcher instance of the SAP CC system.	This dispatcher instance of the SAP CC Core Server system will not start.
33 (INFO)	Shutting down the services of the dispatcher instance of the system	This dispatcher instance of the SAP CC system started to shut down its services.
34 (INFO)	Dispatcher services stopped	The dispatcher services are stopped.
35 (ERROR)	Cannot initialize the properties; Reason: {0}.	An error occurred during the properties initialization of the instance map.	This dispatcher instance of the SAP CC Core Server system will not start.	Export the instance map using SAP CC Setup Tool Correct the instance map Import the instance map	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
36 (ERROR)	Cannot determine the IP address of the host [{0}] specified in the parameter [{1}]	An error occurred while determining the IP address of the host machine specified in the parameter.	This dispatcher instance of the SAP CC Core Server system will not start.	Check the hostname specified can be resolved to an IP address.
37 (FATAL)	Out of memory in thread {0}	The current thread run into an out of memory error.	This instance of the SAP CC Core Server system will stop.	Adjust the -Xmx JVM option in the startup configuration file (jstart.config).
38 (FATAL)	Unexpected Java error in thread {0}: {1}	An unexpected Java error occurred in the system.	The instance of the SAP CC Core Server system will stop.	Archive the log messages and the trace messages Contact your SAP Support Team Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.	Startup Configuration File (jstart.config) Each instance of the SAP CC Core Server system uses a startup configuration file (jstart.config) to start. The system instance gets the JVM options necessary for the Java runtime environment. You set up the JVM options in this startup configuration file. Consult the SAP CC 5.0 Configuration Guide to know how to administer this file.
39 (FATAL)	Shutting down {0} due to an error encountered	This instance of the SAP CC Core Server system is shutting down due to an error. See the previous log messages.	This instance of the SAP CC Core Server system will stop.	See the previous error messages logged Correct the error(s)
40 (INFO)	Starting the Guiding Service	This guider instance of the SAP CC Core Server system is launching its Guiding Service.			Technical information: See the subcomponent of the Core Server system: Guiding Lookup Collector.
41 (FATAL)	Cannot initialize the Guiding Service	An error occurred while starting the Guiding Service.	This guider instance of the SAP CC Core Server system will not start.	See the previous error messages logged Correct the error(s)
42 (INFO)	Guiding Service started and available with {0} threads	The Guiding Service is started.
43 (INFO)	Shutting down the Guiding Service	This instance of the SAP CC system is shutting down its Guiding Service.
44 (INFO)	Guiding Service stopped	The Guiding Service is stopped.
45 (FATAL)	Cannot start the HTTP listener of the instance [{0}] of the system	The HTTP listener cannot start because the instance identifier cannot be found in the instance map.	This instance of the SAP CC Core Server system will not start.	Export the instance map Add the missing instance identifier and its settings in the instance map Import the instance map Restart this instance of the SAP CC system	The dispatcher instances and the updater instances of the system must be specified in the instance map, a line per instance ID Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
46 (INFO)	Starting the HTTP listener of this instance for HCI communications	This instance of the SAP CC Core Server system is starting its HTTP listener for HCI communications.
47 (INFO)	HTTP listener started and available at address: {0}:{1} (with {2} threads)	The HTTP listener is started in this instance of the SAP CC system.
48 (FATAL)	Cannot initialize the HTTP listener for communications via HCI	The HTTP listener dedicated to the Web Services technical interface cannot start.	This instance of the SAP CC Core Server system will not start.
49 (INFO)	Shutting down the HTTP listener	This instance of the SAP CC Core Server system is shutting down its HTTP listener.
50 (INFO)	HTTP listener stopped	The HTTP listener of this instance of the SAP CC Core Server system is now stopped. The communications via HCI technical interface are not possible anymore.
51 (FATAL)	Cannot start the HTTP listener	The HTTP listener cannot start.
52 (INFO)	Restarting the services of the instance	This instance of the SAP CC Core Server system is starting again its services.
53 (INFO)	Services restarted	This instance of the SAP CC Core Server system has successfully restarted its services.
54 (INFO)	Services stopped	This instance of the SAP CC Core Server system has stopped its services.
55 (FATAL)	Instance type [{0}] is not supported	The instance type is not supported.	This instance of the SAP CC Core Server system will not start.
56 (FATAL)	Instance map not found by the master dispatcher instance	This instance of the SAP CC Core Server system has requested the current instance map from the master dispatcher instance. The instance map has not been found during its initialization and the dispatcher instance cannot provide the map. An instance map is missing.	This instance of the SAP CC Core Server system will not start.	Check the other error log messages Define a correct instance map depending on the system landscape (host machines, instances of the SAP CC system) Import the new instance map using SAP CC Setup Tool Restart this instance of the SAP CC system	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
57 (FATAL)	Invalid instance map; Reason: {0}	The instance map is not valid. The reason is dynamically provided in the log message.		Check the reason Export the instance map of the SAP CC Core Server system using SAP CC Setup Tool Correct the instance map Import the changed instance map	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
58 (FATAL)	Information for the instance ID [{0}] not found in the instance map	This instance is not defined in the instance map of this SAP CC Core Server system.	This instance of the SAP CC Core Server system will not start.	Export the instance map using SAP CC Setup Tool Add the missing instance to the instance map Import the instance map Restart this instance of the SAP CC system	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
59 (FATAL)	Cannot detect the local host network: Cannot find the IP addresses of the network interfaces.	The IP addresses of the network interfaces of the local host cannot be detected.	This instance of the SAP CC Core Server system will not start.	Check the local host has working network interfaces Check the available IP addresses
60 (FATAL)	Cannot find a single IP address for the resolution of the hostname {0}. {1} IP addresses have been found ({2}) for the {4} service of the {3} instance. Change the instance map.	The hostname configured for this service of the instance is not resolved to a unique IP address. This service does not handle multiple IP addresses. Check the instance map.	This instance of the SAP CC Core Server system will not start.	Export the instance map of the SAP CC Core Server system using Setup Tool Check the settings for the relevant instance of the SAP CC system Change the address declared for this instance Do not set a hostname but set up a unique IP address if this hostname resolution maps to several IP addresses Import the instance map Restart this instance of the SAP CC system	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
61 (FATAL)	IP address {0} set for service {1} does not exist on any network interface	The IP address configured for this service in the instance map cannot be found on any network interface of the host machine.	This instance of the SAP CC Core Server system will not start.	Export the instance map of the SAP CC Core Server system using Setup Tool Check that the IP address (or hostname) configured in the instance map for this service is correct Check that the network interface is working correctly Change the address defined for this service in the instance map Import the instance map Restart this instance of the SAP CC system	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
62 (FATAL)	Instance {0} must not be launched on this host but on the host {1}	This instance of the SAP CC Core Server system is not launched on the host it has been configured for.	This instance of the SAP CC Core Server system will not start.	Restart this instance on the expected host machine.
63 (FATAL)	Cannot find a single IP address for the address {0}. {1} IP addresses have been resolved ({2}). Change the hostname declared for this instance {3} in the instance map.	The specified IP address resolves several addresses; This may occur when there are several loopback addresses.	This instance of the SAP CC Core Server system will not start.	Update the hostname of this instance in the instance map. Consider using an external IP address instead of a loopback IP address.	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
64 (FATAL)	Cannot resolve the hostname {0} of the instance {1} to an IP address	The hostname resolution has cannot map to an IP address.	This instance of the SAP CC Core Server system will not start.	Export the instance map check if hostname exists Hostname does not exist: operating syst	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
65 (FATAL)	Cannot initialize the instance map because the database connection was not ready	An error occurred during the initialization of the instance map: The connection to the database system is not ready to accept queries.	This instance of the SAP CC Core Server system will not start.	Check your database configuration and connection.	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
66 (FATAL)	Cannot initialize the instance map because of an SQL error	An SQL error occurred during the initialization of the instance map.	This instance of the SAP CC Core Server system will not start.	Troubleshoot your SAP CC system to identify a possible cause: Enable and configure the generation of trace messages Set up the trace severity threshold to PATH using SAP CC Admin+ Restart this instance of the SAP CC system Analyze the trace messages	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
67 (FATAL)	Cannot initialize the instance map due to previous errors	Previous error(s) stopped the initialization of the instance map.	This instance of the SAP CC Core Server system will not start.	See the previous error log messages recorded Correct the error(s)	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
68 (FATAL)	Cannot initialize the instance map because the property {0} has not been found in the boot configuration file	The initialization of the instance map cannot be completed because a mandatory property has not been found in the boot configuration file (boot.config) of this instance of the SAP CC Core Server system.	This instance of the SAP CC Core Server system will not start.	Check the boot configuration file (boot.config) of this instance Set up the missing property Restart this instance of the SAP CC system	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures. Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
69 (FATAL)	Cannot initialize the properties because the property {0} has not been found in the boot configuration file	A boot configuration property has not been found.	This instance of the SAP CC Core Server system will not start.	Add the missing property to the boot configuration file (boot.config).	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
70 (ERROR)	Cannot initialize the parameter manager function; Reason: {0}.	An error occurred during the initialization of the parameter manager in the instance of the SAP CC system.	This instance of the SAP CC Core Server system will not start.
71 (ERROR)	Cannot finalize the parameter manager function; Reason: {0}
72 (FATAL)	Invalid configuration for logging and tracing	The logging configuration cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Export the parameter configuration from the database Add or correct the logging configuration section Import the parameter configuration to the database
73 (FATAL)	Parameter {0} does not match the already configured database instances URIs	There is a difference between the expected SQLHELPER_DB_INSTANCE_COUNT and the configured SQLHELPER_JDBC_URI_DBI<n> parameters.	This instance of the SAP CC Core Server system will not start.	Export the parameter configuration from the database Correct the parameter configuration Import the parameter configuration to the database	The value of the parameter SQLHELPER_DB_INSTANCE_COUNT must reflect the number of configured SQLHELPER_JDBC_URI_DBI<n> parameters.
74 (ERROR)	Cannot warm up the cache because there is no space left	This instance cannot warm up its data cache because there is no space left.	This instance of the SAP CC Core Server system will not start.	Check your configuration.
75 (INFO)	Audit function is enabled	The User Operation Auditing feature and functions are enabled in this instance of the running SAP CC Core Server system. The SAP CC system can audit some particular user operations by recording the processing results to the back-end database system.			System configuration: Consult the AUDIT_ACTIVATION system parameter in the SAP CC 5.0 System Parameter Reference. Concept and features: Consult Features in the SAP CC 5.0 Application Help for more information and user assistance about the System and Data Auditing fundamental feature and the Master Data and User Operation Auditing technical feature and functions. Technical operations: Consult the SAP CC 5.0 Operations Guide in the SAP CC 5.0 System Parameter Reference.
76 (INFO)	Audit function is disabled	TThe User Operation Auditing feature and functions are disabled in this instance of the SAP CC Core Server system.
77 (FATAL)	Current version ({1}) of the {0} Database schema is incompatible with the expected version ({2}). Consider running the appropriate SQL patches.	The technical version number of the database schema is different from the expected version to run this instance of the system. The SAP CC Database system must be compliant with the SAP CC Core Server system.	This instance of the SAP CC Core Server system will not start.	Check the maintenance deliveries about the available support packages. Determine why the version numbers are different: If the version number of the database schema is lower than the version number of the SAP CC Core Server system: Update the database schema by running the appropriate SQL patches If the version number of the database schema is higher: Update the installation of your SAP CC Core Server system
78 (FATAL)	{0} Database schema version is missing. Consider running the appropriate SQL patches.	The technical version number of the database schema is empty in your back-end database system. This may occur if your database has not been populated: The schema has been created only. The SAP installer creates the schema and populates the SAP CC Core Database system.	This instance of the SAP CC Core Server system will not start.	Determine why the version number is empty Run the SQL patches to populate your database schema	The version of the SAP CC Core Database is identified with a version number (VERSION_ID from the VERSION table): See Database Structure Reference -> Tables -> VERSION
79 (FATAL)	Cannot determine the schema version number of the {0} Database	An error occurred while determining the version number of the database schema in the specified SAP CC Database. Several causes are possible. The SAP CC system connects to this back-end database system.	This instance of the SAP CC Core Server system will not start.	Verify the connection to the back-end database system. Otherwise troubleshoot your SAP CC system landscape to identify another possible cause: Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Restart this instance of the SAP CC system and check the trace messages
80 (INFO)	Starting the UDP discovery of the system. Now searching for instances of the system {0} on internal interface during {1} seconds maximum ({2} seconds between each look up attempt)."	This instance of the system has started to detect the dispatcher instance(s) of the same SAP CC Core Server system in the network. Several attempts will be performed.			Each instance of the system has a boot configuration file (boot.config) that includes information to connect to the system. Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
81 (INFO)	Starting the UDP discovery of the system. Now searching for instances of the system {0} on internal interface (single attempt)."	This instance of the system has started to detect the dispatcher instances of the same SAP CC Core Server system in the network.			Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
82 (INFO)	System {0} found via connected instances	This instance of the system has found another dispatcher instances of the same SAP CC Core Server system in the network.
83 (WARNING)	Cannot discover the dispatcher instances of the SAP CC system using the UDP discovery function	This instance cannot find the dispatcher instances of the SAP CC Core Server system by using the UDP discovery function.	This instance of the SAP CC system will use information from the boot configuration to determine a list of dispatcher instances of the same system.	Check the boot configuration file (boot.config) of this instance: Check if the system ID declared in this boot configuration is correct Determine if you need to disable the UDP discovery function because your landscape is not compliant with this function.	Consult the SAP CC Configuration Guide about the system configuration of the UDP discovery function.
84 (INFO)	Loading the list of dispatcher instances of the system from the boot configuration	This instance of the system is loading the list of dispatcher instances from its boot configuration file.			This occurs if the instance of the system cannot detect the dispatcher instances of the SAP CC Core Server system by using the UDP discovery function.
85 (ERROR)	Cannot load the list of dispatcher instances from the boot configuration	An error occurred while loading the dispatcher list from the boot configuration file.	This instance of the SAP CC Core Server system will not start.	Check the boot configuration file (boot.config) of this instance: Change the BOOT_DISPATCHER_LIST property with valid values	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
86 (INFO)	System {0} defined by {1}	This instance of the SAP CC system has determined the dispatcher instances to connect to.
87 (FATAL)	Database configuration: The property {0} is missing in the boot configuration file	A property has not been found while reading the database configuration from the boot configuration file.	This instance of the SAP CC Core Server system will not start.	Check the boot configuration file (boot.config) of this instance. Set up the expected property	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
88 (FATAL)	Instance map not found in the database	This instance of the SAP CC Core Server system did not find the instance map while retrieving it from the back-end database system.	This instance of the SAP CC Core Server system will not start.	Import the instance map using SAP CC Setup Tool.	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
89 (FATAL)	Invalid instance map; Reason: [{0}]	The instance map is not valid. The reason is indicated in the log message.	This instance of the SAP CC Core Server system will not start.		Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
90 (FATAL)	Cannot retrieve the instance map from the database because the database connection was not ready	The instance of the SAP CC Core Server system was unable to retrieve the instance map from the database because the database connection was not ready.	This instance of the SAP CC Core Server system will not start.		Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
91 (FATAL)	Cannot retrieve the instance map from the database because of an SQL manager error: {0}	This instance of the SAP CC Core Server system was unable to retrieve the instance map from the database because of an error encountered by its SQL Manager. The error is detailed in the log message.	This instance of the SAP CC Core Server system will not start.	Correct the error indicated in the log message.	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
92 (FATAL)	Cannot retrieve the instance map from the database because of an SQL error: {0}	This instance of the SAP CC Core Server system was unable to retrieve the instance map from the database because of an SQL error detailed in the log message.	This instance of the SAP CC Core Server system will not start.	Correct the error indicated in the log message.	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
93 (FATAL)	Cannot retrieve the instance map from the database due to previous errors	This instance of the system was unable to retrieve the instance map from the database due to previous errors.	This instance of the SAP CC Core Server system will not start.	See the previous error log messages recorded by the SAP CC system Correct the error(s)	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
94 (ERROR)	Cannot initialize the tax system in this rater instance	This rater instance of the SAP CC Core Server system cannot initialize its tax system.	This rater instance of the SAP CC Core Server system will not start.	Identify the tax system using SAP CC Admin+ Check that the necessary configuration settings are available	Consult the product documentation: SAP CC 5.0 Application Help about the tax systems, the tax function and the tax process SAP CC System Parameter Reference about the system configuration SAP CC Configuration Guide about the tax configuration
95 (ERROR)	Mandatory parameter [{0}] not found	A configuration parameter is missing to start this rater instance of the SAP CC Core Server system.	This rater instance of the SAP CC Core Server system will not start.
96 (ERROR)	CIF/RIF configuration settings not found	The CIF/RIF configurations are missing to start this rater instance of the SAP CC Core Server system.	This rater instance of the SAP CC Core Server system will not start.	Import the CIF and the RIF configurations in the SAP CC Core Database system connected to the SAP CC Core Server system.
97 (INFO)	Starting the Charging Service	This rater instance of the SAP CC Core Server system is starting its Charging Service.
98 (ERROR)	Cannot initialize the Charging Service	An error occurred during the initialization of the Charging Service in the rater instance of the SAP CC Core Server system.	This rater instance of the SAP CC Core Server system will not start.		The Charging Service is part of the SAP CC Core Server system. It manages the acquisition and collection of the chargeable items (consumption information data). It provides the Stateful Charging services.
99 (INFO)	Charging Service started (with {0} threads)	The Charging Service is started.
100 (INFO)	Shutting down the Charging Service	The Charging Service is shutting down.
101 (INFO)	Charging Service stopped	The Charging Service is stopped.
102 (FATAL)	Cannot initialize the Transaction Processor function due to previous errors	This instance of the SAP CC Core Server system cannot initialize its Transaction Processor function due to previous errors.	This instance of the SAP CC Core Server system will not start.	See the previous error log messages recorded by the SAP CC system Correct the error(s)
103 (FATAL)	Cannot initialize the Rerate Processor function due to previous errors	This instance of the SAP CC Core Server system cannot initialize its Rerate Processor function due to previous errors.	This instance of the SAP CC Core Server system will not start.	See the previous error log messages recorded by the SAP CC system Correct the error(s)
104 (INFO)	Starting the tax service	This taxer instance of the SAP CC Core Server system is starting its tax service.			Consult the SAP CC 5.0 Application Help about the tax systems, the tax function and the tax process.
105 (ERROR)	EZTax base path not found (specified by the JVM option -D{0}=<eztax base path>)	An error occurred during the initialization of the tax service: The EZTax base path cannot be found	This taxer instance of the SAP CC Core Server system will not start.	Check if the EZTax base path is the relevant repository Check if the EZTax base path is correctly set in the JVM option	Consult the SAP CC 5.0 Application Help about the tax systems, the tax function and the tax process.
106 (ERROR)	Cannot initialize the tax service in this taxer instance		This taxer instance of the SAP CC Core Server system will not start.	Identify the tax system Check that the necessary configurations are available	Consult the product documentation: SAP CC 5.0 Application Help about the tax systems, the tax function and the tax process SAP CC System Parameter Reference about the system configuration SAP CC Configuration Guide about the tax configuration
107 (ERROR)	Cannot start due to previous errors	This taxer instance of the SAP CC Core Server system cannot start due to previous errors.	This instance of the SAP CC Core Server system will not start.	See the previous error messages logged Correct the error(s)
108 (INFO)	Tax service started and available with {0} threads	The tax service of this taxer instance is started.			Consult the SAP CC 5.0 Application Help about the tax systems, the tax function and the tax process.
109 (INFO)	Shutting down the Taxer service	The taxer service is shutting down.
110 (INFO)	Taxer service stopped	The taxer service is stopped.
111 (ERROR)	Cannot initialize the Batch Rating Group Assignment Processor function	An error occurred during the initialization of the Batch Rating Group Assignment Processor function.	This updater instance of the SAP CC Core Server system will not start.	Check that the BATCH_RATING_GROUP_ASSIGNMENT_POLICY_CLASS parameter is correctly set in the SAP CC system.	Use SAP CC Admin+ to get the value of this system parameter See the System Parameter Reference to know the correct values
112 (ERROR)	Cannot initialize the tax system in this updater instance	This updater instance of the SAP CC Core Server system cannot initialize its tax system.	This updater instance of the SAP CC Core Server system will not start.	Identify the tax system Check that the necessary configurations are available	Consult the product documentation: SAP CC 5.0 Application Help about the tax systems, the tax function and the tax process SAP CC System Parameter Reference about the system configuration SAP CC Configuration Guide about the tax configuration
113 (ERROR)	Cannot initialize the Exportable Item Connector	An error occurred during the initialization of the exportable item connector in the instance of the SAP CC Core Server system.	This updater instance of the SAP CC Core Server system will not start.	See the previous error messages logged Correct the errors	EIF (Exportable item Integration Framework) Settings parameter group EIF_CONN_CLASS indicator
114 (INFO)	Starting the initialization of the external currencies	In the SAP CC Core Server system, this updater instance is starting the initialization of the external currencies automatically because of the EIF. The instance tries to synchronize some currency definitions from a reference system such as SAP S/4HANA or SAP ERP.			Synchronizing Currencies with an SAP Reference System (S/4HANA or ERP): Manual Replication Currencies and Custom Currencies SAP Convergent Charging manages ISO and non-ISO based currency definitions. SAP CC assigns a currency to each computed amount (dynamic price) with a personalized precision level. You can process prices with up to six decimal places. Currencies are part of the business data configured in the complete SAP CC system. SAP CC handles a proprietary definition for country or custom currencies. An application administrator manages this business data in close cooperation with the SAP CC pricing specialists. The data maintenance depends on various reasons. Note In an integrated SAP Solution (with SAP S/4HANA or SAP Business Suite), the currency definitions are configured in the SAP S/4HANA or SAP ERP reference system first. The reference system replicates the currency definitions with their number of decimal places to SAP Convergent Charging when requested by an SAP CC user. If your deployment scenario is not based on this SAP Solution, each SAP currency must be configured and maintained in the SAP CC system. The SAP CC Core Server system stores the currency definitions in the CURRENCY database table. In SAP Convergent Charging, you do not configure currencies to manage currency conversion for the pricing configuration. An SAP Currency is identified by an alphanumeric code (max. five digits). This identification code is a three-letter code when you configure an SAP currency that represents an original country currency and that is based on the international ISO 4217 standard. To manage amounts with more decimal places than an original currency, you define some secondary currencies. Use a four-digit code to configure some secondary currencies that are based on the original one but with some different precision. Use a personalized code to configure some non-ISO currencies such as the PNT (Point) currency for example. PNT is defined with no decimal precision. The currency is defined by: The precision, which represents the number of decimal places A legible name, which is clear enough to be read easily An ISO 4217 currency code defined by the International Standards Organization (ISO) when the currency configured in SAP CC relates to an ISO currency. Examples You configure an SAP CC system with the following currencies: SAP Currency Precision Legible Name Based on ISO Code PNT Zero decimal places Point N/A EUR Two decimal places European Euro EUR (978) EUR4 Four decimal places European Euro (4 Dec. Places) EUR6 Six decimal places European Euro (6 Dec. Places) USD Two decimal places United States Dollar USD (840) USDN Five decimal places (Internal) United States Dollar (5 Decimal Places) USD6 Six decimal places (Internal) United States Dollar (6 Decimal Places) Based on these currencies, you can model and design some pricing logic for your marketable end-customer services. For example: In pricing catalogs, reusable charge and redefine charge plans are associated to a single or multicurrency In customer master data, subscriber accounts are associated to a currency; subscriber mapping tables can include some currencies. SAP Convergent Charging manages some definitions for the IS0 4217 currency codes to facilitate the configuration of ISO-based country currencies. In SAP CC, you configure the necessary ISO currency codes (three-letter code, numeric code, minor currency unit, and ratio). The international ISO 4217 standard is the reference from the International Standards Organization (ISO). An application administrator manages this business data in close cooperation with the SAP CC pricing specialists. The data maintenance depends on various reasons. Note The SAP CC Core Server system stores the ISO currency code definitions in the ISO_4217 database table. See also: About currencies in SAP Convergent Charging Creating and Importing Some SAP Currencies and ISO Currency Codes Creating and Maintaining Some ISO 4217 Currency Codes by Importing Data Definitions from an XML File With an integrated SAP Solution (based on SAP S/4HANA or SAP Business Suite): Synchronizing Currencies with an SAP Reference System (S/4HANA or ERP): Manual Replication Handling Amounts with Increased Precision in an SAP S/4HANA System Handling Amounts with Increased Precision in an SAP ERP System
115 (INFO)	Initialization of the external currencies done. The number of defined currencies is {0}.	Initialization of the external currencies is done.			Refer to log message com.sap.SCC.core_server.000114. Synchronizing Currencies with an SAP Reference System (S/4HANA or ERP): Manual Replication SAP Convergent Charging manages some ISO and non-ISO based currency definitions to assign to computed amounts in order to form prices with personalized level for precision (decimal places). ISO 4217 currency codes are some business data that is configured in SAP Convergent Charging in order to define the necessary ISO-based country currencies that are associated to computed amounts (dynamic prices).
116 (INFO)	Instance is waiting for authorization from dispatcher	This instance of the SAP CC system is waiting for the authorization from the master dispatcher instance.
117 (INFO)	Web Services are not configured	The Web Services for this instance are either: not available or available but not enabled	This instance will not be able to handle requests through Web Services
118 (INFO)	Web Services are not configured	The Web Services for this instance are not enabled	This instance will not be able to handle requests through Web Services
119 (INFO)	Starting the Web Services	This instance of the system is starting its Web Services
120 (INFO)	Web Services published and available at: {0}://{1}:{2}/{3}	The URL of the published Web Services. This URL is required by the systems connected to the SAP CC Core Server system with this technical interface (Web Services).
121 (INFO)	Web Services started	The Web Services are started on this instance of the SAP CC Core Server system
122 (WARNING)	Cannot insert the Web security policy in the following WSDL: \n{0}	An error occurred while inserting the security policy in the WSDL		Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
123 (WARNING)	Cannot insert Web security policy reference in the following WSDL: \n{0}	An error occurred while inserting the security policy reference in the WSDL		Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
124 (INFO)	Stopping the Web Services	This instance of the SAP CC Core Server system is stopping its Web Services.
125 (INFO)	Web Services stopped	The Web Services technical interface is stopped. The relating business operations are not possible anymore.
126 (ERROR)	Cannot initialize the system parameters. Reason is: {0}	An error occurred during the initialization of the system parameters. The reason is dynamically provided in the log message.	This updater instance of the SAP CC Core Server system will not start.	Check the reason provided in the log message Fix eventual configuration error(s)
127 (INFO)	Authorization received from a dispatcher instance of the same system	This updater instance has received an authorization from a dispatcher instance of the same system
128 (WARNING)	Activation process (with subscriptions) is already running. The request is ignored.	An activation process with subscriptions is already running. It is not possible to run several activation processes at the same time.	Any new activateAll operation request sent by external systems will be ignored by the SAP CC Core Server system	If you ran consecutive subscription activation processes (activateAll), only the first one will be taken into account. If you need to run the subscription activation process again: You should either wait for the current subscription activation to complete Or terminate the current activation using the stopActivation operation (available through the stop_activation command of SAP CC Admin+)
129 (WARNING)	Cannot start the activation process (with subscriptions) because a rerating process is currently running	A rerating process is currently running. It is not possible to run an activation process concurrently with a rerating process.	The activateAll operation will be ignored.	You should wait for the rerating process to complete.
130 (ERROR)	Cannot start the activation process (with subscriptions) because it has not been possible to determine if a rerating process is running	The subscription activation process will not start because it has not been possible to determine if a rerating process is already running.	The activateAll operation will not start.	Check if the instances are able to communicate between them Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Look at the traces to get more technical information
131 (INFO)	Starting the activation process with subscriptions	This instance of the system is starting an activation process
132 (INFO)	Activation process completed	The activation process is completed by this instance of the system. Check the other instances.
133 (WARNING)	Activation process (with provider contracts) is already running. The request is ignored.	An activation process (with provider contracts) is already running. It is not possible to run several contract activation processes at the same time.	Any new chargingContractActivate operation request sent by external systems will be ignored by the SAP CC Core Server system	If you ran consecutive provider contract activation processes, only the first one will be taken into account. If you need to run the provider contract activation again: You should either wait for the current provider contract activation process to complete Or terminate the current activation using SAP CC Admin+ or by implementing the stopChargingContractActivation operation
134 (WARNING)	Cannot start the activation process (with provider contracts) because a rerating process is currently running	A rerating process is currently performed by the system. It is not possible to launch an activation process concurrently with a rerating process.	chargingContractActivate operation will be ignored.	You should wait for the rerating process to complete.
135 (ERROR)	Cannot start the activation process (with provider contracts) because it has not been possible to determine if a rerating process is running	The activation process for provider contracts will not start because it has not been possible to determine if a rerating process is already running.	The chargingContractActivate operation will not start.	Check if the instances are able to communicate between them Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Determine the next triggering date Analyze the trace messages on the next refresh triggered
136 (WARNING)	Cleanup process is already running. The operation request is refused.	A cleanup process is already running in the SAP CC Core Server system. This updater instance of the system refuses the new operation request for cleanup.	The CleanupAllOp operation requests will be ignored by the updater instances. The start_cleanup command of SAP CC Admin+ will not be usable.	If you ran consecutive cleanup processes, only the first one will be taken into account. If you need to run the cleanup process again: You should either wait for the current cleanup process to complete Or terminate the current cleanup using the stop_cleanup command of SAP CC Admin+ or by implementing the stopCleanup operation in your application interfaced with SAP Convergent Charging	Consult the SAP CC 5.0 Application Help about the: Cleanup function and the cleanup process Admin+ user interface
137 (WARNING)	Cleanup process is already running. The operation request is refused and not dispatched to the rater instances of the system	A cleanup process is already running in the SAP CC Core Server system. This dispatcher instance of the system refuses the cleanup operation request and does not dispatch it to the rater instances of the system.	The CleanupAllOp operation requests will be ignored by the dispatcher instances.	If you ran consecutive cleanup processes, only the first one will be taken into account. If you need to run the cleanup process again: you should either wait for the current cleanup process to complete or terminate the current cleanup process using the stopCleanup operation.
138 (INFO)	Cleanup process completed with status {1}. A total of {0} subscriptions/provider contracts have been cleaned up.	The cleanup process is completed in the SAP CC Core Server system. Check the final and global status to know if all the objects have been cleaned up.
139 (INFO)	Starting the mass cleanup process with reference date {0} and a maximum throughput set to {1} cleanup(s) per second per rater instance	The SAP CC Core Server system starts processing the mass cleanup of subscriptions and provider contracts
140 (WARNING)	Activation process of {0} objects is already running. The request is refused.	The activation process is already running	The operation request is refused.	Wait for the current activation process to complete Start the activation process again, if it is still needed The activation process initiated by the scheduler will be automatically triggered on the next schedule
141 (INFO)	Activation process completed with status {2}. {0} {1} have been activated.	The activation process is completed by the system. Check the final status.
142 (INFO)	Starting the activation process of {0} objects with reference date {1} and a maximum throughput set to {2} per second per rater instance	The activation process is performed by the system. See the logs of the rater instances for details.
143 (WARNING)	Expiration alert process already running. Request ignored.	The expiration alert process is already running	fireExpirationAlerts operation will be ignored.	You should wait for the running expiration alert process to complete
144 (ERROR)	Error occurred during the execution of the expiration alert process	An error occurred during the execution of the expiration alert process.	The expiration alert process ended with an error status.
145 (WARNING)	Expiration alert process already running. Request ignored.	The expiration alert process is already running.	fireExpirationAlerts operation will be ignored.	You should wait for the running expiration alert process to complete.
146 (WARNING)	Scheduler cannot refresh the instance {0} of the system	A scheduled refresh of an instance of the system cannot be processed	The instance will not be refreshed.	Check the instance is running Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Determine the next triggering date Analyze the trace messages on the next refresh triggered
147 (ERROR)	Error occurred during the refresh of the rater instances of the SAP CC system	An error occurred during the refresh of the rater instances of the SAP CC Core Server system.		Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Determine the next triggering date Analyze the trace messages on the next refresh triggered
148 (INFO)	Tax cache successfully refreshed: The data cache includes {0} VAT rates	This instance of the SAP CC Core Server system has refreshed its data cache that includes the definitions of all the tax rates for all the value added taxes (VAT) configured in the system.			Consult the SAP CC 5.0 Application Help about the tax management.
149 (INFO)	Persistent value [{0}] of the parameter [{1}] is changed from [{2}] to its default value [{3}] for {4} instances by the SAP user {5}	The persistent value of the system parameter has been reset.
150 (INFO)	Memory value of the parameter [{0}] is changed from [{1}] to its default value [{2}] by the SAP user {3}	The memory value of the parameter has been reset.
151 (INFO)	Persistent value [{0}] of the parameter [{1}] is changed from [{2}] to [{3}] for {4} instances by the SAP user {5}	The persistent value of the parameter has been changed.
152 (INFO)	Memory value of the parameter [{0}] is changed from [{1}] to [{2}] by the SAP user {3}	The memory value of the parameter has been changed.
153 (INFO)	Shutdown request received: Shutting down {0} instance {1} in {2} seconds	This instance of the SAP CC Core Server system has received a request to shut down in few seconds.	This instance will shut down.
154 (INFO)	Executing shutdown of {0} instance {1} from Admin+ (waiting for the dispatcher authorization to stop)	This instance of the SAP CC Core Server system has received a shutdown request from the Admin+ user interface. The instance waits for an authorization to stop from the master dispatcher instance.	This instance will shut down.
155 (INFO)	Shutdown operation waiting for a new authorization to stop from the dispatcher instance	This instance of the SAP CC Core Server system is still waiting for the authorization to stop.	This instance of the SAP CC system will shut down.
156 (ERROR)	Cannot load the bulk loader sources configuration due to an I/O error	Cannot load the bulk loader sources configuration due to an input/output error.
157 (ERROR)	Cannot load the bulk loader sources configuration due to an error in the parser configuration	Cannot load the bulk loader sources configuration due to an error in the parser configuration.
158 (ERROR)	Cannot load the bulk loader sources configuration due to an XML parsing error	Cannot load the bulk loader sources configuration due to an XML parsing error.		Fix the bulkLoader sources configuration.
159 (ERROR)	Cannot load the shell configuration of the charged item processor function	Cannot load the charged item processor shell configuration.		Check and correct the CIF configuration of the bulkloader.
160 (ERROR)	Cannot load the shell configuration of the transaction processor function	Cannot load the transaction processor shell configuration.		Check and correct the CIF configuration of the rater.
161 (ERROR)	Cannot load the shell configuration of the rerate processor function	Cannot load the rerate processor shell configuration.		Check and correct the RIF configuration of the rater
162 (ERROR)	Cannot load the notification policy configuration	Cannot load the notification policy configuration		Check and correct the notification policy configuration
163 (INFO)	Missing parameter [{0}] has been inserted in database for the instance type {1} with value [{2}]	A missing parameter has been inserted in the database
164 (INFO)	Sending SLD payload to the URL: {0}	The SLD payload is going to be sent by the instance of the system			The server systems of SAP Convergent Charging send information about installed hardware and software components of your SAP CC system landscape. The SAP CC systems update periodically the System Landscape Directory (SLD) of SAP NetWeaver. Consult the SAP CC 5.0 Configuration Guide and the SAP CC System Parameter Reference about the system settings dedicated to the management of System Landscape Directory (SLD).
165 (INFO)	SLD updated	The SLD payload has been sent			The server systems of SAP Convergent Charging send information about installed hardware and software components of your SAP CC system landscape. The SAP CC systems update periodically the System Landscape Directory (SLD) of SAP NetWeaver. Consult the SAP CC 5.0 Configuration Guide and the SAP CC System Parameter Reference about the system settings dedicated to the management of System Landscape Directory (SLD).
166 (ERROR)	Cannot connect to the SLD at the URL: {0}	The instance of the system cannot connect to the SLD	The SLD payload will not be sent	Troubleshoot your SAP CC system and its settings for the System Landscape Directory (SLD): Check the value of the SLD_URL parameter Check you can connect to this URL	The server systems of SAP Convergent Charging send information about installed hardware and software components of your SAP CC system landscape. The SAP CC systems update periodically the System Landscape Directory (SLD) of SAP NetWeaver. Consult the SAP CC 5.0 Configuration Guide and the SAP CC System Parameter Reference about the system settings dedicated to the management of System Landscape Directory (SLD).
167 (ERROR)	Cannot update the SLD due to an I/O error	This instance of the system cannot update the SLD due to an input/output (I/O) error		Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Determine the next sent of the SLD payload by checking the value of the SLD_SCHEDULER_RECURRENCE parameter Analyze the technical information in the traces generated on the next schedule	The server systems of SAP Convergent Charging send information about installed hardware and software components of your SAP CC system landscape. The SAP CC systems update periodically the System Landscape Directory (SLD) of SAP NetWeaver. Consult the SAP CC 5.0 Configuration Guide and the SAP CC System Parameter Reference about the system settings dedicated to the management of System Landscape Directory (SLD).
168 (ERROR)	Error occurred while sending the SLD payload	An error occurred while sending the SLD payload.		Troubleshoot your SAP CC system: Enable and configure the generation of trace messages Set up the trace severity threshold to PATH Determine the next sent of the SLD payload by checking the value of the SLD_SCHEDULER_RECURRENCE parameter Analyze the technical information in the traces generated on the next schedule	The server systems of SAP Convergent Charging send information about installed hardware and software components of your SAP CC system landscape. The SAP CC systems update periodically the System Landscape Directory (SLD) of SAP NetWeaver. Consult the SAP CC 5.0 Configuration Guide and the SAP CC System Parameter Reference about the system settings dedicated to the management of System Landscape Directory (SLD).
169 (ERROR)	Cannot read the log entries	Cannot read the log entries.	The log extractor will not return the log entries.
170 (ERROR)	Cannot load the shell configuration of the charged item processor function of the bulkloader instance	The charged item processor shell of the bulkloader instance could not be loaded.	The bulkloader instance may not be completely functional. The parameters defined in the charged item processor shell configuration may not be accessible.	Fix the charged item processor shell configuration for the bulkloader instance.
171 (ERROR)	Cannot load the charged item processor shell of the bulkloader	The charged item processor shell of the bulkloader instance could not be loaded.	The bulkloader instance may not be completely functional. The parameters defined in the charged item processor shell configuration may not be accessible.	Fix the charged item processor shell configuration for the bulkloader instance.
172 (ERROR)	Cannot load the charged item processor shell of the rater	The charged item processor shell of the rater instance could not be loaded.	This rater instance may not be completely functional. The parameters defined in the charged item processor shell configuration may not be accessible.	Fix the charged item processor shell configuration for the rater instance.
173 (ERROR)	Cannot load the charged item processor shell of the rater	The charged item processor shell of the rater instance could not be loaded.	This rater instance may not be completely functional. The parameters defined in the charged item processor shell configuration may not be accessible.	Fix the charged item processor shell configuration for the rater instance.
174 (ERROR)	Cannot update the notification policy configuration due to an SQL error	The configuration of the notification policy could not be updated in the back-end database due to an error in the communication with the database system.	The notification policy will not be updated. The modifications to the notification policy will not be saved to the database.	Check the previous traces to identify the issue linked to the database access.
175 (ERROR)	Cannot retrieve the notification policy configuration due to an SQL error	The configuration of the notification policy could not be retrieved from the back-end database due to an error in the communication with the database system.	The notification policy previously saved to the database will not be used in the current session	Check the previous traces to identify the issue linked to the database access
176 (ERROR)	Cannot retrieve the notification policy configuration due to an XML parsing error	The configuration of the notification policy could not be retrieved from the back-end database due to an error in the format of the configuration data.	The notification policy previously saved to the database will not be used in the current session.	Check the previous traces to identify the issue linked to the format of the configuration data.
177 (ERROR)	Cannot load the rerate processor shell of the rater	The rerate processor shell of the rater instance could not be loaded.	This rater instance may not be completely functional. The parameters defined in the rerate processor shell configuration may not be accessible.	Fix the rerate processor shell configuration for the rater instance.
178 (ERROR)	Cannot load the rerate processor shell of the rater	The rerate processor shell of the rater instance could not be loaded.	This rater instance may not be completely functional. The parameters defined in the rerate processor shell configuration may not be accessible.	Fix the rerate processor shell configuration for the rater instance.
179 (ERROR)	Cannot retrieve the bulkLoader sources configuration due to an I/O error	The bulkloader sources configuration could not be loaded due to an input/output (I/O) error.	The bulkLoader sources configuration previously saved to the database will not be used in the current session.	Check the previous traces to identify the issue preventing access to the configuration data.
180 (ERROR)	Cannot retrieve the bulkLoader sources configuration due to a parser configuration error	The bulkloader sources configuration could not be loaded due to an error in the configuration of its data parser.	The bulkLoader sources configuration previously saved to the database will not be used in the current session.	Check the previous traces to identify the issue linked to the data parser.
181 (ERROR)	Cannot retrieve the bulkLoader sources configuration due to an XML parsing error	The bulkloader sources configuration could not be loaded due to an error in the format of the configuration data.	The bulkLoader sources configuration previously saved to the database will not be used in the current session.	Check the previous traces to identify the issue linked to the format of the configuration data.
182 (WARNING)	Operation {0} is stopped because the connection limit is reached	The operation is stopped because the connection limit is reached. It could happen when multiple instances have been reconnected during the operation. This operation is limited to 100 connections, including lost connections.	The operation has not completed.	See the dispatcher logs to investigate on the possible unwanted reconnections Execute the operation again The operations initiated by the scheduler will be automatically triggered on the next schedule
183 (WARNING)	Admin XML Proxy received an execution request for the operation {0} which is unknown	Admin XML Proxy received an execution request for an unknown operation.	The request will be ignored.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
184 (INFO)	VAT rule cache successfully refreshed: The data cache includes {0} VAT rules	This instance of the SAP CC Core Server system has refreshed its VAT rule cache from the configuration.			Consult the SAP CC 5.0 Application Help about the tax management.
185 (ERROR)	Scheduler (triggering the expiration alerts) cannot communicate to the dispatcher instance	This dispatcher instance of the SAP CC Core Server system cannot trigger the expiration alerts from the scheduler because it is busy, not started or shutting down.	The client application is not aware of this expiration alert.	Ensure that the dispatcher instance is started. The scheduler will automatically trigger the expiration alerts on the next schedule.
186 (FATAL)	License has expired	Your SAP Convergent Charging license has expired.	This instance of the SAP CC Core Server system will not start.	Apply for a new license file Install a valid license file	Consult the SAP CC 5.0 Configuration Guide and the SAP CC 5.0 Installation Guide to know how to apply for a permanent or temporary license and how to install it in the SAP CC Core Server system.
187 (ERROR)	Error was raised in the core security module; Reason: {0}	An error occurred in the security module (com.sap.security.core.server) for license verification.	This instance of the SAP CC Core Server system will not start.	Check the reason in the log message recorded by the SAP CC system Check the log file from the com.sap.security.core.server
188 (INFO)	OFF configuration initialized with ID [{0}]	The selected operation factory has been initialized successfully.
189 (FATAL)	Parameter [{0}] is not set or is empty. Check this parameter.	The specified parameter has not been set in the configuration or its value is invalid. The operation factory cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify that the specified parameter is correctly set in the configuration Correct the configuration using SAP CC Config Tool
190 (FATAL)	Cannot find OFF class {0}. Check the parameter [{1}].	The Java class configured for the operation factory framework cannot be found. The operation factory cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify that the specified parameter is correctly set in the configuration Verify that the class is in the launcher classpath Change the configuration using SAP CC Config Tool
191 (FATAL)	Cannot initialize OFF {0} due to: {1}. Check the parameter [{2}].	An error occurred during the initialization of the operation factory connector. The operation factory cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
192 (FATAL)	Cannot instantiate OFF with class {0}, exception is: {1}. Check the parameter [{2}].	An error occurred during the initialization of the operation factory connector. The operation factory class could not be instantiated. The operation factory cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message The class must be instantiable and have a nullary constructor Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
193 (FATAL)	Cannot instantiate OFF with class {0}, exception is: {1}. Check the parameter [{2}].	An error occurred during the initialization of the operation factory connector. The operation factory class could not be accessed by the Java Virtual Machine. The operation factory cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message The class must be accessible by the JVM Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
194 (INFO)	Transaction processor with ID [{0}] has been initialized correctly	The selected transaction processor has been initialized successfully.
195 (FATAL)	Parameter [{0}] is not set or is empty. Check this parameter.	The specified parameter has not been set in the configuration or its value is invalid. The transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
196 (FATAL)	Cannot initialize transaction processor [{0}] due to: {1}. Check the parameter [{2}].	An error occurred during the initialization of the rating transaction processor function. The rating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
197 (FATAL)	Cannot initialize transaction processor [{0}] due to: {1}. Check the CIF configuration.	An error occurred during the initialization of the rating transaction processor function. The rating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message and previous error messages Verify that the CIF configuration is correctly set up Change the CIF configuration using SAP CC Setup Tool
198 (FATAL)	Cannot find transaction processor class {0}. Check the parameter [{1}].	The class configured for the rating transaction processor framework cannot be found. The rating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify that the specified parameter is correctly set in the configuration Verify that the class is in the launcher classpath Change the configuration using SAP CC Config Tool
199 (FATAL)	Cannot instantiate transaction processor with class {0}, exception is: {1}. Check the parameter [{2}].	An error occurred during the initialization of the rating transaction processor function. The rating transaction processor class could not be instantiated. The rating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message The class must be instantiable and have a nullary constructor Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
200 (FATAL)	Cannot instantiate transaction processor with class {0}, exception is: {1}. Check the parameter [{2}].	An error occurred during the initialization of the rating transaction processor function. The rating transaction processor class could not be accessed by the Java Virtual Machine. The rating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message The class must be accessible by the JVM Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
201 (INFO)	Transaction processor with ID [{0}] has been initialized correctly	The selected rerating transaction processor has been initialized successfully.
202 (FATAL)	Parameter [{0}] is not set or is empty. Check this parameter.	The specified parameter has not been set in the configuration or its value is invalid. The rerating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
203 (FATAL)	Cannot initialize transaction processor [{0}] due to: {1}. Check the parameter [{2}].	An error occurred during the initialization of the rerating transaction processor function. The rerating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
204 (FATAL)	Cannot find transaction processor class {0}. Check the parameter [{1}].	The class configured for the rerating transaction processor framework cannot be found. The rerating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify that the specified parameter is correctly set in the configuration Verify that the class is in the launcher classpath Change the configuration using SAP CC Config Tool
205 (FATAL)	Cannot instantiate transaction processor with class {0}, exception is: {1}. Check the parameter [{2}].	An error occurred during the initialization of the rerating transaction processor function. The rerating transaction processor class could not be instantiated. The rerating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message The class must be instantiable and have a nullary constructor Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
206 (FATAL)	Cannot instantiate transaction processor with class {0}, exception is: {1}. Check the parameter [{2}].	An error occurred during the initialization of the rerating transaction processor function. The rerating transaction processor class could not be accessed by the Java Virtual Machine. The rerating transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message The class must be accessible by the JVM Verify that the specified parameter is correctly set in the configuration Change the configuration using SAP CC Config Tool
207 (FATAL)	Cannot initialize the Transaction File Processor: No properties for initialization.	An error occurred during the initialization of the transaction file processor (TFP) function. No configuration could be found for this function. The transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
208 (FATAL)	Cannot initialize the Transaction File Processor: The configuration parameters {0}, {1}, {2} or {3} are missing or invalid.	An error occurred during the initialization of the transaction file processor function. The specified configuration parameters are missing or malformed. The transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message Verify the configuration of the transaction file processor Change the configuration using SAP CC Config Tool
209 (FATAL)	Cannot initialize the Transaction File Processor: Configuration parameter {0} is missing or invalid.	An error occurred during the initialization of the transaction file processor connector. The specified configuration parameter is missing or malformed. The transaction processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message Verify the configuration of the transaction file processor Change the configuration using SAP CC Config Tool
210 (INFO)	Transaction file processor with ID [{0}] has been initialized correctly	The transaction file processor has been initialized successfully
211 (ERROR)	Transaction File Processor - Writing channel ({0}) writing error. Reason: {1}.	An error occurred in the transaction file processor when trying to write transactions to file. The transaction could not be cleared.	A new attempt will be made. If multiple attempts do not succeed, some transactions may be lost.	Check the error message Verify the output file path, file access, and disk space
212 (FATAL)	Transaction File Processor - Unable to store some transactions into Writing Channels	An error occurred in the transaction file processor when trying to write transactions to file. The transaction could not be cleared.	Some transactions have been lost.	Check the previous error messages
213 (FATAL)	Cannot initialize the Data File Processor: System parameter {0} is missing or invalid. Parameter value is [{1}]	An error occurred during the initialization of the data file processor function. The configuration system parameter is missing, malformed or invalid. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify the parameter in the configuration of the data file processor Change the configuration using SAP CC Admin+	Consult the SAP CC System Parameter Reference for information about the possible values.
214 (FATAL)	Cannot initialize the Data File Processor: System parameter {0} is incorrect. Encoding [{1}] is not supported.	An error occurred during the initialization of the data file processor function. The specified configuration parameter refers to an unsupported character encoding. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify the parameter in the configuration of the data file processor Change the configuration using SAP CC Config Tool	See the SAP CC System Parameter Reference for information about the possible values.
215 (FATAL)	Cannot initialize the Data File Processor: The directory [{0}] cannot be initialized.	An error occurred during the initialization of the data file processor function. The pathname specified in the configuration is not a valid directory. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify the parameter in the configuration of the data file processor Check that the specified pathname exists and is a valid directory Create the directory or change the configuration using SAP CC Config Tool
216 (FATAL)	Cannot initialize the Data File Processor: The value of configuration parameter {0} must be greater or equal to [{1}].	An error occurred during the initialization of the data file processor function. The specified configuration parameter value is less than minimal expected value. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify the parameter in the configuration of the data file processor Change the configuration using SAP CC Config Tool	See the SAP CC Parameter Book for information on possible parameter values
217 (FATAL)	Cannot initialize the Data File Processor: The path [{0}] is not a path directory.	An error occurred during the initialization of the data file processor function. The pathname specified in the configuration is not a valid directory. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify the parameter in the configuration of the data file processor Check that the specified pathname exists and is a valid directory Create the directory or change the configuration using SAP CC Config Tool
218 (FATAL)	Cannot initialize the Data File Processor: Cannot create the directory [{0}].	An error occurred during the initialization of the data file processor function. The specified directory cannot be created on the file system. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists and is a valid directory Verify that there is enough space on the file system
219 (INFO)	{0} writing channel manager is initialized with {1} channel(s)	The data file processor has initialized the specified writing channel. Two types of writing channels may be initialized: postpaid and prepaid.
220 (FATAL)	Cannot initialize the Data File Processor: The value of DB_FILE_PROCESSOR_DIRECTORY_COUNT parameter must be greater or equal to [{0}].	An error occurred during the initialization of the data file processor function. The specified configuration parameter value is less than minimal expected value. This could happen with the postpaid or prepaid writing channels. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify the parameter in the configuration of the data file processor Change the configuration using SAP CC Config Tool	See the SAP CC System Parameter Reference for information on possible parameter values
221 (FATAL)	Cannot initialize Data File Processor: The directory [{0}] is defined twice.	An error occurred during the initialization of the data file processor function. The specified directory has been defined twice, which will cause inconsistencies in the storage. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the directory is only defined once Change the configuration using SAP CC Config Tool
222 (FATAL)	Cannot initialize the Data File Processor: The directory [{0}] cannot be initialized.	An error occurred during the initialization of the data file processor function. The pathname specified in the configuration is not a valid directory. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify the parameter in the configuration of the data file processor Check that the specified pathname exists and is a valid directory Create the directory or change the configuration using SAP CC Config Tool
223 (ERROR)	Database was not able to load some files from the directory [{0}]	Some of the files from the specified directory could not be loaded successfully by the data file processor function.	Some of the files may not be loaded immediately in the back-end database. The bulkloader instance will attempt to load those files again on the next schedule.	Verify the parameter in the configuration of the data file processor Check that the specified pathname exists and is a valid directory Create the directory or change the configuration using SAP CC Config Tool
224 (WARNING)	Directory [{0}] has not been loaded by the database	The specified directory has not yet been processed. It still contains files that need to be loaded to the database.	The bulkloader instance will try again to load those files on the next schedule.	Verify the parameter in the configuration of the data file processor Check that the specified pathname exists and corresponds to a valid directory Create the directory or change the configuration using SAP CC Config Tool
225 (INFO)	Directory [{0}] is initialized for the {1} Writing Channel Manager	The specified directory is ready to be processed by the bulkloader instance. Its files will be loaded to the database.
226 (FATAL)	Cannot initialize the Database File Encoding Processor: Encoding [{0}] is not supported.	An error occurred during the initialization of the data file processor function. The configuration of character encoding for output files is not supported and cannot be used. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Verify the encoding parameters in the configuration of the data file processor Change the configuration using SAP CC Config Tool	See the SAP CC System Parameter Reference for more information about the possible parameter values.
227 (FATAL)	Cannot initialize the Data File Processor: The lock file {0} cannot be initialized.	An error occurred during the initialization of the data file processor function. The lock file cannot be created. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists, is a valid directory and has the correct permissions Check that the specified filename is not an existing file Check that the file can be created on the file system Check that the file system has enough free space
228 (FATAL)	Cannot initialize the Data File Processor: The lock file {0} cannot be read.	An error occurred during the initialization of the data file processor function. The lock file cannot be read. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists, is a valid directory and has the correct permissions Check that the file has the correct read permissions
229 (FATAL)	Cannot initialize the Data File Processor: The lock file {0} cannot be modified.	An error occurred during the initialization of the data file processor function. The lock file cannot be modified. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists, is a valid directory and has the correct permissions Check that the file has the correct write permissions
230 (FATAL)	Cannot initialize the Data File Processor: The lock file {0} is not a valid file.	An error occurred during the initialization of the data file processor function. The lock file is not a valid file. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists, is a valid directory and has the correct permissions Check that the file exists
231 (FATAL)	Cannot initialize the Data File Processor: The lock file {0} is not a valid file; Reason: {1}	An error occurred during the initialization of the data file processor function. An unexpected input/output (I/O) error occurred during the creation of the data file. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message Check that the parent directory exists, is a valid directory and has the correct permissions Check that the file exists and has the required permissions
232 (FATAL)	Cannot initialize the Data File Processor: The data file {0} cannot be initialized.	An error occurred during the initialization of the data file processor function. The data file cannot be created. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists, is a valid directory and has the correct permissions Check that the specified filename is not an existing file Check that the file can be created on the file system Check that the file system has enough free space
233 (FATAL)	Cannot initialize the Data File Processor: The data file {0} cannot be read.	An error occurred during the initialization of the data file processor function. The data file cannot be read. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists, is a valid directory and has the correct permissions Check that the file has the correct read permissions
234 (FATAL)	Cannot initialize the Data File Processor: The data file {0} cannot be modified.	An error occurred during the initialization of the data file processor function. The data file cannot be modified. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists, is a valid directory and has the correct permissions Check that the file has the correct write permissions
235 (FATAL)	Cannot initialize the Data File Processor: The data file {0} is not a valid file.	An error occurred during the initialization of the data file processor function. The data file is not a valid file. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check that the parent directory exists, is a valid directory and has the correct permissions Check that the file exists
236 (FATAL)	Cannot initialize the Data File Processor: The data file {0} is not a valid file; Reason: {1}.	An error occurred during the initialization of the data file processor function. An unexpected input/output (I/O) error occurred during the creation of the data file. The data file processor cannot be initialized.	This instance of the SAP CC Core Server system will not start.	Check the error message Check that the parent directory exists, is a valid directory and has the correct permissions Check that the file exists and has the required permissions
237 (WARNING)	Invalid ISO 3166 file; Reason: {0}.	The resource file containing country tax policies has been tampered with and is not a valid file.	This instance of the SAP CC Core Server system will not start.	Application files are inconsistent or have been tampered with. Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
238 (ERROR)	Country tax policy file not found in database	The country tax policies file has not been imported in the database.	This instance of the SAP CC Core Server system will not start.	Import the country tax policies in the database
239 (INFO)	Registering country tax policies	The country tax policies file is being loaded. The tax policies are being registered in the system.
240 (INFO)	Country tax policies registered	The country tax policies file has been loaded. Tax policies have been registered successfully in the system.
241 (ERROR)	Cannot read tax policy file; Error: {0}.	The country tax policies file cannot be read.	This instance of the SAP CC Core Server system will not start.	Application files are inconsistent or have been tampered with. Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
242 (FATAL)	Cannot recover major runtime error when populating country tax policies; Error: {0}.	SAP CC Setup Tool records this log message because an unexpected runtime error occurred while loading the country tax policies file.	The import of the country tax policies is canceled. The country tax policies are not changed and previous data remains available.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
243 (FATAL)	Cannot recover major SQL error when populating country tax policies; Error: {0}.	An unexpected SQL error occurred while loading the country tax policies file.	This instance of the SAP CC Core Server system will not start.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
244 (ERROR)	EU taxes file not found in database	The European tax rates file has not been imported in the back-end database.	This instance of the SAP CC Core Server system will not start.	Import the European tax rates in the database
245 (INFO)	Registering European tax rates	The European tax rates file is being loaded. European tax rates are being registered in the system.
246 (INFO)	European tax rates registered	The VAT rates file has been loaded. VAT rates have been registered successfully in the SAP CC system.
247 (WARNING)	Incompatibility between tax rate and tax code for tax {0}, ignoring this tax code	An issue occurred while importing the European tax rates file. There is an incompatibility between the tax rate type and the tax code. The specified tax code is not valid and will be ignored.	The tax rate for the tax code will not be available in the system	Check the validity of the tax rate Fix the potential errors Import the modified VAT rates file using SAP CC Setup Tool
248 (WARNING)	Invalid tax rate for tax {0}, ignoring this tax code	An issue occurred while importing the European tax rates file. The tax rate type is not valid.	The tax rate for the tax code will not be available in the system	Check the validity of the tax rate Fix the potential errors on the rate type Import the modified VAT rates file using SAP CC Setup Tool
249 (WARNING)	Bad effective date {0} for tax {1}, ignoring this tax code	An issue occurred while importing the European tax rates file. The tax effective date is not valid.	The tax rate for the tax code will not be available in the system	Check the validity of the tax rate Fix the potential errors on the tax rate effective date Import the modified VAT rates file using SAP CC Setup Tool
250 (ERROR)	Cannot read European tax rates file; Error: {0}.	The European tax rates file cannot be read.	This instance of the SAP CC Core Server system will not start.	Application files are inconsistent or have been tampered with. Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
251 (FATAL)	Cannot recover major runtime error when populating European tax rates; Error: {0}.	An unexpected runtime error occurred while loading the European tax rates file.	This instance of the SAP CC Core Server system will not start.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
252 (FATAL)	Cannot recover major SQL error when populating European tax rates; Error: {0}.	An unexpected SQL error occurred while loading the European tax rates file.	This instance of the SAP CC Core Server system will not start.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
253 (ERROR)	Cannot parse VAT rules file; Error: {0}.	The VAT rules policies file cannot be loaded and read correctly.	This instance of the SAP CC Core Server system will not start.	Application files are inconsistent or have been tampered with. Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
254 (ERROR)	Cannot parse VAT rules file. Not enough fields in rule definition: {0}	The VAT rules file cannot interpret the VAT rule. The rule is malformed as it does not contain enough fields or it contains too many fields.	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Fix the eventual errors Import the modified VAT rules file using SAP CC Setup Tool
255 (ERROR)	VAT rule ID [{0}] already exists	The specified VAT rule identifier has been defined twice in the VAT rules file. It is not possible to determine which one is the correct rule.	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Fix the eventual errors Import the modified VAT rules file using SAP CC Setup Tool
256 (ERROR)	VAT rule ID is empty in VAT rule definition: {0}.	The VAT rule identifier is missing in the VAT rules file. The identifier is a mandatory field of the VAT rule.	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add an identifier to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
257 (ERROR)	Description is empty in VAT rule [{0}]	The VAT rule description is missing in the VAT rules file. The description is a mandatory field of the VAT rule.	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a description to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
258 (ERROR)	Supplier country code is empty or invalid in VAT rule [{0}]	The supplier country code of the VAT rule is missing or invalid in the VAT rules file. The supplier country code is a mandatory field of the VAT rule.	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid supplier country code to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
259 (ERROR)	B2B taxation place is out of range in VAT rule [{0}]	The value of the B2B taxation place of the VAT rule does have a correct value in the VAT rules file. The B2B taxation place is a mandatory field of the VAT rule. The B2B taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid B2B taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
260 (ERROR)	B2B taxation place is not a number in VAT rule [{0}]	The value of the B2B taxation place of the VAT rule does have a correct value in the VAT rules file. The B2B taxation place is a mandatory field of the VAT rule. The B2B taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid B2B taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
261 (ERROR)	B2C taxation place is out of range in VAT rule [{0}]	The value of the B2C taxation place of the VAT rule does have a correct value in the VAT rules file. The B2C taxation place is a mandatory field of the VAT rule. The B2C taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid B2C taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
262 (ERROR)	B2C taxation place is not a number in VAT rule [{0}]	The value of the B2C taxation place of the VAT rule does have a correct value in the VAT rules file. The B2C taxation place is a mandatory field of the VAT rule. The B2C taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid B2C taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
263 (ERROR)	Default B2B taxation place is out of range in VAT rule [{0}]	The value of the default B2B taxation place of the VAT rule does have a correct value in the VAT rules file. The default B2B taxation place is a mandatory field of the VAT rule. The default B2B taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid default B2B taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
264 (ERROR)	Default B2B taxation place is not a number in VAT rule [{0}]	The value of the default B2B taxation place of the VAT rule does have a correct value in the VAT rules file. The default B2B taxation place is a mandatory field of the VAT rule. The default B2B taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid default B2B taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
265 (ERROR)	Default B2B taxation place is empty in VAT rule [{0}]	The value of the default B2B taxation place of the VAT rule is not set in the VAT rules file. The default B2B taxation place is a mandatory field of the VAT rule. The default B2B taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid default B2B taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
266 (ERROR)	Default B2C taxation place is out of range in VAT rule [{0}]	The value of the default B2C taxation place of the VAT rule does have a correct value in the VAT rules file. The default B2C taxation place is a mandatory field of the VAT rule. The default B2C taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid default B2C taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
267 (ERROR)	Default B2C taxation place is not a number in VAT rule [{0}]	The value of the default B2C taxation place of the VAT rule does have a correct value in the VAT rules file. The default B2C taxation place is a mandatory field of the VAT rule. The default B2C taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid default B2C taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
268 (ERROR)	Default B2C taxation place is empty in VAT rule [{0}]	The value of the default B2C taxation place of the VAT rule is not set in the VAT rules file. The default B2C taxation place is a mandatory field of the VAT rule. The default B2C taxation place can be one of: 0: supplier country 1: customer country 2: user defined	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rule Add a valid default B2C taxation place to the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
269 (FATAL)	No VAT rule has been loaded	No VAT rule was loaded in the system. Either the VAT rules file was empty or incorrect, or none of the VAT rules was valid.	This instance of the SAP CC Core Server system will not start.	Check the validity of the VAT rules file Verify that the VAT rules are all valid Import the modified VAT rules file using SAP CC Setup Tool
270 (ERROR)	EZTax output path not found (specified by the JVM option -D{0}=<eztax output path>)	An error occurred during the initialization of the tax service: The EZTax output path cannot be found.	This taxer instance of the SAP CC Core Server system will not start.	Check if the EZTax output path is correctly set in the JVM option Create the EZTax output directory	Consult the SAP CC 5.0 Application Help about the tax systems, the tax function and the tax process.
271 (INFO)	EZTax library version {0}, database version {1}	The taxer instance uses the specified EZTax library and database versions.
272 (INFO)	EZTax could not initialize:\n 1. Make sure that BillSoft's EZTax software is properly installed.\n\t- Make sure that the EZTax library or shared object is present in the Taxer 'jars' directory.\n\t- Make sure that the EZTax database files are present in the Taxer 'eztaxBasePath' directory.\n2. Your EZTax database files may have expired.\n3. Refer to the status files (.sta) in the Taxer directory for error information.	An error occurred during the initialization of the tax service. This error may be linked to the EZTax installation or the EZTax configuration.	This taxer instance of the SAP CC Core Server system will not start.	Make sure that BillSoft's EZTax software is properly installed Make sure that the EZTax library or shared object is present in the Taxer 'jars' directory Make sure that the EZTax database files are present in the Taxer 'eztaxBasePath' directory Your EZTax database files may have expired Refer to the status files (.sta) in the Taxer directory for error information	Consult the SAP CC 5.0 Application Help about the tax systems, the tax function and the tax process.
273 (WARNING)	Forbidden entity resolution request for publicId=[{0}] and serviceId=[{1}] from [{2}]:[{3}] - could be an XXE attack	An instance of the SAP CC Core Server received a message on the XML over HTTP communication channel (HCI) that could not be interpreted. The included object could not be resolved for the public ID and system ID. This warning message could indicate a possible XXE (Xml eXternal Entity) Attack and should be investigated by the administrator.	The message on the XML over HTTP communication channel (HCI) is ignored by the SAP CC system.	Check that the host identified by its address and port is allowed to query the system and that its queries are valid.
274 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the login or password is incorrect	An SAP CC user tried to log on to the SAP CC system, however the attempt was refused because the logon or password is incorrect. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Check the user roles and authorizations.
275 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the SAP CC user is locked	An SAP CC user tried to log on to the system, however the attempt was refused because the user is locked. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Check the user roles and authorizations.
276 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the password has expired	An SAP CC user tried to log on to the system, however the attempt was refused because the password has expired. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Check the user roles and authorizations.
277 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused. Reason: {2}	An SAP CC user tried to log on to the system, however the attempt was refused. The reason is not known or unexpected. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Check the user roles and authorizations Contact your SAP Support Team to investigate on this specific reason code Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
278 (INFO)	Advanced password management is enabled	The Advanced Password Management feature is enabled in this SAP CC system landscape.
279 (INFO)	User session management enabled	The User Session Management feature is enabled in this SAP CC system landscape.
280 (INFO)	No validity period defined for user session	The User Session Management feature is enabled without session validity period.	The user sessions will not expire in this SAP CC system landscape.		Consult the SAP CC System Parameter Reference to find more information on user session configuration.
281 (INFO)	User session management is enabled and validity period is set to [{0}] seconds	The User Session Management feature is enabled with the displayed validity period on each user session. This validity period is expressed in seconds.			User Session A working session for an SAP CC individual user User Session Management Features, Concepts Refer to the SAP CC 5.0 Application Help for more information and user assistance about this technical feature. Implementation As an IT administrator or IT consultant, determine if SAP CC must manage some user sessions for the SAP CC users. Configuration (System) To configure the SAP CC Core Server system, see the USER_SESSION_ENABLED system parameter and the User Management Settings parameter group. Consult the SAP CC 5.0 System Parameter Reference to find more information about the system configuration settings that relate to SAP user management and user session management. Technical Operations Audit: View the list of user sessions currently open with the SAP CC Admin+ user interface Troubleshooting: Delete a user session with SAP CC Admin+
282 (INFO)	No limit per SAP CC user and user interface defined for user sessions	The User Session Management feature is not configured to limit the number of sessions per SAP CC user and per user interface or client application that implements this feature in SAP CC.			Consult the SAP CC System Parameter Reference to find more information on user session configuration.
283 (INFO)	User session management: Limit per SAP CC user and user interface is set to [{0}].	The User Session Management feature is configured to limit the number of sessions per user and per tool.			Consult the SAP CC System Parameter Reference to find more information on user session configuration.
284 (ERROR)	{0} request(s) were received late. Maximum delay recorded since {1}: {2} ms. Invalid configuration: increase client-side timeout or update parameter COLLECTOR_RTT to decrease server-side round-trip time according to your network average latency.	The configuration of the internal communication between system instances is not valid.	The SAP CC Core Server system may have finished processing the request(s) but the remote client application did not receive the answer(s) because of the client-side timeout.	Increase client-side timeout or update the COLLECTOR_RTT system parameter to decrease server-side estimated round-trip time according to your network average latency.	Consult the SAP CC System Parameter Reference to find more information on the configuration parameter.
285 (WARNING)	{0} timeout(s) occurred. Maximum allocated handling time recorded since {1}: {2} ms.	Timeout(s) occurred during internal communication between system instances.	The SAP CC Core Server system may have finished processing the request(s) but the remote client did not receive the answer(s) because of a client-side timeout.	Check the client-side timeout and the server-side parameter (COLLECTOR_RTT) for the estimated network round trip time explained in milliseconds	Consult the SAP CC System Parameter Reference to find more information on the configuration parameter.
286 (INFO)	Instance [{0}] ([{1}]) is not allowed to start because the instance [{2}] ([{3}]) is registered and the connection is alive	The instance of the SAP CC Core Server system cannot start because another instance is already registered.
287 (INFO)	Instance [{0}] ([{1}]) is allowed to replace the connection ([{2}])	The instance of the SAP CC Core Server system has been allowed to replace the existing connection.
288 (INFO)	Waiting for instance [{0}] ([{1}]) is stopped	The instance of the SAP CC Core Server system is actually stopped.
289 (INFO)	Instance [{0}] ([{1}]) is unregistered	The instance of the SAP CC Core Server system is not a registered instance.
290 (INFO)	Instance [{0}] ([{1}]) is registered	The instance of the SAP CC Core Server system has been registered.
291 (WARNING)	Instance [{0}] ([{1}]) is re-registered. Previous register connection is [{2}].	The instance of the SAP CC Core Server system has been registered once again, even though it already had a previously registered connection.	The connection was down between this instance and the instance that has just been re-registered.	Check the connection between this instance and the instance that has just been re-registered.
292 (INFO)	Instance [{0}] ([{1}]) is not authorized to be registered because this dispatcher is the master dispatcher of the system	The instance of the SAP CC Core Server system is the master dispatcher of the SAP CC system; it cannot be registered.
293 (WARNING)	Concurrent master dispatcher detected: dispatcher [{0}] ([{1}]) will restart	The instance of the SAP CC Core Server system has been declared as master dispatcher while another master dispatcher instance is already running. This instance will restart as a slave dispatcher.	This instance will not be available during the restart sequence.	This instance will restart automatically.
294 (INFO)	Client [{0}] is registered	The specified client has been registered with the SAP CC Core Server system.
295 (INFO)	Client [{0}] is unregistered	The specified client has been unregistered from the SAP CC Core Server system.
296 (INFO)	Instance [{0}] ([{1}]) is waiting for authorization to start	The instance of the SAP CC Core Server system is waiting for its authorization to start.
297 (INFO)	Instance [{0}] ([{1}]) is not allowed to be registered because an updater is already registered	The instance of the SAP CC Core Server system is not allowed to be registered because another updater instance is already registered.
298 (INFO)	Instance [{0}] ([{1}]) is not allowed to be registered because the updater is not the authorize updater	The instance of the SAP CC Core Server system is not allowed to be registered in the system. This updater is not the authorization updater.
299 (INFO)	Instance [{0}] ([{1}]) is not allowed to be registered because a authorize updater is already registered	The instance of the SAP CC Core Server system is not allowed to be registered in the system. An authorization updater has already been registered in the system.
300 (ERROR)	Cannot reply to the remote client. Error code: [{0}], reason: {1}	An internal communication error has occurred in the message protocol. The instance of the SAP CC Core Server system cannot reply to the remote client.	The remote client may not receive the answer.	Verify the error message to determine the cause
301 (ERROR)	Cannot commit the request in database. Error code: [{0}], reason: {1}	Cannot commit the request in database during the processing of an operation. An error will be returned to the remote client.	All or a part of the operation has not been recorded.	Verify the error message to determine the cause
302 (WARNING)	All rater instances received the order to stop the Activation process. However, some of these rater instances could not comply with the order.	An internal message was sent to all rater instances for stopping the execution of the Activation process. These rater instances correctly received the order, but some of them could not comply with it.	Some rater instances may not have stopped the execution of the Activation process.	Check the logs of the rater instances that could not stop the Activation process.
303 (ERROR)	Some rater instances did not receive the order to stop the Activation process for subscriptions before the timeout expiration with the following reason: [{0}]	An internal message was sent to all rater instances for stopping the execution of the Activation process for subscriptions. Some of these rater instances did not receive this order.	Some rater instances may not have stopped the execution of the Activation process for subscriptions.	Check the network connections between the dispatcher instance and the rater instances that did not answer.
304 (ERROR)	Some rater instances did not receive the order to stop the Activation process for provider contracts before the timeout expiration with the following reason: [{0}]	An internal message was sent to all rater instances for stopping the execution of the Activation process for provider contracts. Some of these rater instances did not receive this order.	Some rater instances may not have stopped the execution of the Activation process for subscriptions.	Check the network connections between the dispatcher instance and the rater instances that did not answer.
305 (WARNING)	All rater instances received the order to start the Cleanup process. However, some of these rater instances could not comply with the order.	An internal message was sent to all rater instances for starting the execution of the Cleanup process. These rater instances correctly received the order, but some of them could not comply with it.	Some rater instances may not have started the execution of the Cleanup process.	Check the logs of the rater instances that could not start the Cleanup process.
306 (ERROR)	Some rater instances did not receive the order to start the Cleanup process before the timeout expiration with the following reason: [{0}]	An internal message was sent to all rater instances for starting the execution of the Cleanup process. Some of these rater instances did not receive this order.	Some rater instances may not have started the execution of the Cleanup process.	Check the network connections between the dispatcher instance and the rater instances that did not answer.
307 (WARNING)	All rater instances received the order to stop the Cleanup process. However, some of these rater instances could not comply with the order.	An internal message was sent to all rater instances for stopping the execution of the Cleanup process. These rater instances correctly received the order, but some of them could not comply with it.	Some rater instances may not have stopped the execution of the Cleanup process.	Check the logs of the rater instances that could not stop the Cleanup process.
308 (ERROR)	Some rater instances did not receive the order to stop the Cleanup process before the timeout expiration with the following reason: [{0}]	An internal message was sent to all rater instances for stopping the execution of the Cleanup process. Some of these rater instances did not receive this order.	Some rater instances may not have stopped the execution of the Cleanup process.	Check the network connections between the dispatcher instance and the rater instances that did not answer.
309 (ERROR)	Some reachable servers did not acknowledge the fire expiration alerts order before timeout expiration with following reason: [{0}]	An internal message to run the process triggering the expiration alerts was sent to all rater instances. However not all running rater instances acknowledged the request.	Some rater instances may not trigger the expiration alerts process.	Verify the error message to determine the cause
310 (INFO)	Activation process with subscriptions starts with the reference date {0}	This rater instance of the SAP CC Core Server system is launching the subscription activation process.	The activation process uses system resources and may take some time depending on the overall number of subscriptions.
311 (INFO)	Rater instance must activate {0} subscription(s) for the partition {1} ({2}/{3} partitions)	This rater instance of the SAP CC Core Server system is about to start the activation process for the identified number of subscriptions. This message displays additional information for activation process tracking.
312 (INFO)	Activation process: {0}% of subscription(s) activation done for the partition {1} ({2}/{3} partitions)	This rater instance of the SAP CC Core Server system will activate the specified number of subscriptions. This message displays additional information for activation process tracking.
313 (INFO)	Subscription activation stopped by user	An SAP CC user has stopped the subscription activation process in this rater instance of the SAP CC system.
314 (WARNING)	Connection to the master dispatcher is down: Activation is stopped	The connection to the master dispatcher instance in the SAP CC Core Server system has been lost. This rater instance cannot perform the subscription activation process and will stop the process execution.	Some subscriptions may not have been activated in customer master data.	Check the network connections between this rater instance and the dispatcher instances of the SAP CC system.
315 (INFO)	Rater instance has visited {0} subscription(s) and {1} subscription(s) cannot be activated	This rater instance of the SAP CC Core Server system has finished the subscription activation process.	Some subscriptions may not have been activated. The number of subscriptions that could not be activated is specified in the message.	If some subscriptions could not be activated, it is mandatory to check that the previous error messages to determine the cause.
316 (ERROR)	Activation process cannot activate [{0}] due to error: {1}	This rater instance of the SAP CC Core Server system cannot activate the contract identified by its internal object identifier.	The contract may not have been activated, recurring and non-recurring fees may not have been all generated.	Verify the error message to determine the cause
317 (INFO)	Activation process with provider contracts starts with the reference date {0}	This rater instance of the SAP CC Core Server system is launching the activation process with provider contracts.	The activation process uses system resources and may take some time depending on the overall number of provider contracts.
318 (INFO)	Rater instance must activate {0} provider contract(s) for the partition {1} ({2}/{3} partitions)	This rater instance of the SAP CC Core Server system is about to start the activation process with the specified number of provider contracts. This message displays additional information for activation process tracking.
319 (INFO)	Activation process: {0}% of provider contract(s) activation done for the partition {1} ({2}/{3} partitions)	This rater instance of the SAP CC Core Server system will activate the specified number of provider contracts. This message displays additional information for activation process tracking.
320 (INFO)	Activation process of provider contracts stopped by user	An SAP CC user has stopped the activation process with provider contracts in this rater instance of the SAP CC Core Server system.
321 (WARNING)	Connection to the master dispatcher instance is down: Activation process is stopped	The connection to the master dispatcher instance of the SAP CC Core Server system has been lost. This rater instance cannot perform the provider contract activation process and will stop the process execution.	Some provider contracts may not have been activated in customer master data.	Check the network connections between this rater instance and the dispatcher instances of the SAP CC system.
322 (INFO)	Rater instance has visited {0} provider contract(s) and {1} provider contract(s) cannot be activated	This rater instance of the SAP CC Core Server system has finished the activation process with provider contracts.	Some provider contracts may not have been activated in customer master data. The number of provider contracts that could not be activated is specified in the log message.	If some provider contracts could not be activated, it is mandatory to check that the previous error messages to determine the cause.
323 (INFO)	Cleanup process starts with the reference date {0}	This rater instance of the SAP CC Core Server system is launching the cleanup process.
324 (INFO)	Rater must cleanup subscriber account(s) for the partition {0} ({1}/{2} partitions)	This rater instance of the SAP CC Core Server system is about to start the cleanup process for the specified partition of subscriber accounts. This message displays additional information for cleanup process tracking.
325 (INFO)	Cleanup process: {0}% of subscriber account(s) cleanup done for the partition {1} ({2}/{3} partitions)	This rater instance of the SAP CC Core Server system will cleanup the identified number of subscriber account. This message displays additional information for cleanup process tracking.
326 (INFO)	Subscriber account cleanup stopped by user	An SAP CC user has stopped the cleanup process in this rater instance.
327 (WARNING)	Connection to the master dispatcher instance is down: Cleanup operation is stopped	The connection to the master dispatcher instance of the SAP CC Core Server system has been lost. In this rater instance, the cleanup process cannot proceed and will be stopped.	Some subscriber accounts may not have been cleaned.	Check the network connections between this rater instance and the dispatcher instances.
328 (INFO)	Rater has visited {0} subscriber account(s)	This rater instance of the SAP CC Core Server system has finished the cleanup process.
329 (ERROR)	Cleanup process cannot clean [{0}] due to error: {1}	This rater instance of the SAP CC Core Server system cannot cleanup the sessions for the subscriber account identified by its internal object identifier.	The sessions for this subscriber account cannot be removed from database. Further ratings on this subscriber account will be refused.	Verify the configuration of the price plan. Verify the error message to determine the cause. Archive the log messages and the trace messages. Contact your SAP Support Team.
330 (ERROR)	VAT rule ID [{0}] is too long	The VAT rule identifier length is too long. The VAT rule identifier can contain a maximum of 256 characters.	The VAT rules are not imported in the SAP CC Core Server system.	Change the identifier of the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
331 (ERROR)	Description is too long in VAT rule [{0}]	The VAT rule description is too long. The VAT rule description can contain a maximum of 2,000 characters.	The VAT rules are not imported in the SAP CC Core Server system.	Change the description of the VAT rule Import the modified VAT rules file using SAP CC Setup Tool
332 (ERROR)	Description of the existing VAT rule [{0}] has changed	The description in the VAT rules file differs from the back-end database system. The description should not be changed.	The new VAT rules are not imported in the SAP CC Core Server system.	Change the description to the one in database for this VAT rule Import the modified VAT rules file using SAP CC Setup Tool
333 (ERROR)	Supplier zone of the existing VAT rule [{0}] has changed	The supplier zone in the VAT rules file differs from the back-end database system. The supplier zone should not be changed.	The new VAT rules are not imported in the SAP CC Core Server system.	Change the supplier zone to the one in database for this VAT rule Import the modified VAT rules file using SAP CC Setup Tool
334 (ERROR)	B2B taxation place of the existing VAT rule [{0}] has changed	The B2B taxation place in the VAT rules file differs from the back-end database system. The B2B taxation place should not be changed.	The new VAT rules are not imported in the SAP CC Core Server system.	Change the B2B taxation place to the one in database for this VAT rule Import the modified VAT rules file using SAP CC Setup Tool
335 (ERROR)	B2C taxation place of the existing VAT rule [{0}] has changed	The B2C taxation place in the VAT rules file differs from the back-end database system. The B2C taxation place should not be changed.	The new VAT rules are not imported in the SAP CC Core Server system.	Change the B2C taxation place to the one in database for this VAT rule Import the modified VAT rules file using SAP CC Setup Tool
336 (ERROR)	Default B2B taxation place of the existing VAT rule [{0}] has changed	The default B2B taxation place in the VAT rules file differs from the back-end database system. The default B2B taxation place should not be changed.	The new VAT rules are not imported in the SAP CC Core Server system.	Change the default B2B taxation place to the one in database for this VAT rule Import the modified VAT rules file using SAP CC Setup Tool
337 (ERROR)	Default B2C taxation place of the existing VAT rule [{0}] has changed	The default B2C taxation place in the VAT rules file differs from the back-end database system. The default B2C taxation place should not be changed.	The new VAT rules are not imported in the SAP CC Core Server system.	Change the default B2C taxation place to the one in database for this VAT rule Import the modified VAT rules file using SAP CC Setup Tool
338 (ERROR)	Existing VAT rule [{0}] is missing	The VAT rule exists in the back-end database system but is missing in the VAT rules file. The VAT rule should not be removed.	The new VAT rules are not imported in the SAP CC Core Server system.	Add the missing VAT rule Import the modified VAT rules file using SAP CC Setup Tool
339 (INFO)	Checking license key for system "{0}", hardware key "{1}", product "{2}"	The license of an SAP CC instance is going to be checked.
340 (ERROR)	Rater instance cannot send the expiration alert response because the connection to the client is down	An expiration alert has been triggered by an SAP CC user or by the scheduler of the updater instance in the SAP CC Core Server system. The rater instance, which handles this operation, cannot send the response to the client application or system due to a communication error.	The client application (or system) is not informed about the result of the expiration alert.	Verify that: the network is available the dispatcher instance is started
341 (ERROR)	Rater instance cannot send the expiration alert response because the connection to the client has been interrupted	An expiration alert has been triggered by a user or by the scheduler of the updater instance in the SAP CC Core Server system. The rater instance, which handles this operation, cannot send the response to the client application or system due to a connection timeout.	The client application (or system) is not informed about the result of the expiration alert.	Verify that: the network is available the dispatcher instance is started
342 (ERROR)	Unable to check if the activation process is running before launching the rerating process	The rerateBulk operation has not been able to check if the activation process was running. The connection to the dispatcher instance is down.	The rerateBulk operation will not be performed.	Verify that: the network is available the dispatcher instance is started
343 (INFO)	Synchronizing of {0} bulk loader files	The rerating external system used is BART Server of SAP CC. Bulk loader files created before the synchronization with bulkloader instances.
344 (INFO)	Bulk loader files synchronized	The rerating external system used is BART Server of SAP CC. The synchronization with bulkloader instances concerning the bulk loader files.
345 (ERROR)	Cannot contact the BART server to open the rerating session	The rerating external system is BART Server of SAP CC. Cannot open the rerating session due to a communication error with the BART Server system.	The operations performed by BART are unavailable.	Verify that: the BART Server system is started the status of the network
346 (ERROR)	Cannot contact the BART server to start the rerating session	The rerating external system is BART Server of SAP CC. Cannot start the rerating session due to a communication error with BART.	The operations performed by BART are unavailable.	Verify that: the BART Server system is started the status of the network
347 (ERROR)	Cannot stop the opened rerating session	The rerating external system is BART. Cannot stop the rerating session due to a communication error with BART.	The operations performed by BART are unavailable.	Verify that: the BART Server system is started the status of the network
348 (INFO)	Starting the taxer client	A network client is registering with instance managing taxes
349 (INFO)	Taxer client started	A network client is registered with instance managing taxes
350 (INFO)	Shutting down the taxer client	A network client is not registering with instance managing taxes
351 (INFO)	Taxer client stopped	A network client is not longer registered with instance managing taxes
352 (ERROR)	Cannot initialize the Transaction File Processor: Cannot open the writing channel in [{0}].	Cannot initialize the Transaction File Processor (TFP) because the directory of the writing channel cannot be created.	The TFP is not initialized.	Verify the path/file access rights.
353 (ERROR)	Cannot initialize the Transaction File Processor: Several files found for current transaction in [{0}].	The TFP expects to find only one file for the writing channel but it found several.	The TFP is not initialized.	Rename the older file by removing '_' prefix.
354 (ERROR)	Cannot initialize the Transaction File Processor: The current file name [{0}] in [{1}] is malformed, its expected length is [{2}] characters.	The writing channel file name is malformed.	The TFP is not initialized.	Rename the current file by removing the '_' prefix.
355 (ERROR)	Cannot initialize the Transaction File Processor: I/O exception in [{0}]. The reason is {1}	During the launch of the rater instance, the TFP cannot be initialized because it cannot write, read or rename files due to an input/output (I/O) system error.	The TFP is not initialized. The launching of the rater is aborted.	Verify that: the disk has enough space to create or fill files the access rights And restart the rater instance.
356 (ERROR)	Cannot initialize the Transaction File Processor: The current file name [{0}] in [{1}] is malformed.	The writing channel file name is malformed.	The TFP is not initialized.	Rename the current file by removing the '_' prefix.
357 (ERROR)	Writing Channel [{0}] fell down and has been discarded. Available writing channel count: [{1}]	A writing channel did not work and got discarded.	A writing channel has been lost.	Analyze the previous log messages or trace messages.
358 (ERROR)	Writing channel cannot be updated; Reason: {0}.	Cannot update the writing channel. It happened at the initialization of the TFP or during an operation.	It can occurred during: the launch of the rater: The launching is aborted an operation: The writing channel is discarded	Verify that: the disk has enough space to create or fill files the access rights And following the circumstance of the error: restart the rater instance re-perform the operation
359 (INFO)	{0} ({1}) cannot be authorized to pre-register because the dispatcher is not ready
360 (INFO)	{0} ({1}) does not exist
361 (WARNING)	{0} is not authorized to register because the timeout of {1}ms has been reached due to a concurrent operation		The services provided by the specified instance are not available.	Restart the specified instance.
362 (WARNING)	{0} is not authorized to unregister because the timeout of {1}ms has been reached due to a concurrent operation	The	The services provided by the specified instance might be unavailable.	See the logs of the dispatcher instances for details. Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
363 (WARNING)	Dispatcher instance cannot stop because a timeout has been reached due to a concurrent operation		The services provided by the dispatcher instance might be unavailable.	See the logs of the dispatcher instances for details. Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
364 (INFO)	Waiting for the end of the administration operations
365 (INFO)	Waiting for the end of the administration operations
366 (INFO)	Waiting for the master dispatcher end of communication, {0} message(s) remaining
367 (INFO)	Waiting for dispatcher(s) connection(s) to be closed: {0}.
368 (INFO)	Waiting for rater(s) connection(s) to be closed: {0}.
369 (INFO)	Concurrent modification of the raters partitions map, the process will restart with the new map
370 (INFO)	Concurrent modification of the guiders partitions map, the process will restart with the new map
371 (WARNING)	Master dispatcher emptied the raters map	The master dispatcher instance is not connected to any rater instance.	The rating service is not available.	Restart the rater instances or check that the logs of rater instances if they do not start
372 (INFO)	Raters map is updated by the master dispatcher to {0} instance(s): {1}.
373 (WARNING)	Master dispatcher emptied the guiders map	This master dispatcher instance is not connected to any guider instance in the SAP CC Core Server system.	The Guiding Service is not available.	Restart the guider instances or check that the logs of guider instances if they do not start.
374 (INFO)	Guiders map is updated by the master dispatcher to {0} instance(s): {1}.
375 (WARNING)	{0}s map is empty after a down connection		The services provided by the specified instance type are not available.	The possible reasons are: All the instances of the specified type are stopped. Start all these instances to solve the problem. A connection problem occurs between this dispatcher instance and all the instances of the specified type. Investigate the connection issue to solve the problem.
376 (INFO)	{0}s map is updated after a down connection to {1} instance(s): {2}
377 (WARNING)	No more {0} instance in the map	There is no instance of the specified type connected to this master dispatcher instance in the SAP CC Core Server system.	The business and technical services of the instances of the specified type are not provided.	Check the next log messages. If another log message (378) indicates that the map of the specified instance is updated, the problem does not occur anymore. Otherwise this means either: All the instances of the specified type are stopped. The correction action is to start all these instances to solve the problem. A connection problem occurs between this dispatcher instance and all the instances of the specified type. The correction action is to investigate the connection issue.
378 (INFO)	{0}s map is updated to {1} instance(s): {2}
379 (WARNING)	{0} is not authorized to start because a timeout has been reached due to a concurrent operation	A "register" or "unregister" operation is in progress on the same instance type than the one which is starting.	The new instance is not started.	Restart the new instance.
380 (WARNING)	Cannot send unregistration request to dispatcher instances	One or multiple slave dispatcher instances have not received the new guiders map and raters map.	The quality of Charging and Guiding Services is degraded until the issue resolution.	See the logs of the dispatcher instances for details. Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
381 (INFO)	Starting the Data File Processor function
382 (INFO)	Data File Processor started
383 (INFO)	Tax cache has been refreshed: It contains {0} taxes.	The tax cache has been refreshed.
384 (INFO)	Subscription/contract counter snapshot maximum size is {0} bytes	Indicates the maximum size.
385 (WARNING)	Counter snapshot count is not the same for all subscriptions/contracts
386 (INFO)	Counter snapshot count initialized to {0} from the database
387 (INFO)	Counter snapshot count initialized to {0} from the instance configuration
388 (WARNING)	Counter snapshot is set to {0} in the database. Value {1} from the instance configuration will be ignored.		For instance: If the counter snapshot count in the database is greater than the value of the COUNTER_SNAPSHOT_COUNT system parameter, then it will not be possible to rerate from this extra counter snapshot that exists in the system. If the counter snapshot count in the database is lower than the value of the COUNTER_SNAPSHOT_COUNT system parameter, then the system will propose a rerating of more days than what exists in the system.	Set the COUNTER_SNAPSHOT_COUNT system parameter to a value that is equal to the counter snapshot count in the database.
389 (WARNING)	Threshold of {0} bytes reached during the counter snapshot insertion for subscription/contract [{1}]: snapshot size is {2}/{3} bytes.	This warning is fired to prevent problem of counter snapshot insertion in database (ie: log message 390). The size of this counter snapshot has just reached 75% of the maximum size of a counter snapshot.	If nothing is done, a following counter snapshot will reach the maximum size of a counter snapshot and the rerating service will be compromised.	Increase the size of the counter snapshot value. Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
390 (WARNING)	Maximum size of {0} bytes reached during the counter snapshot insertion for subscription/contract [{1}]: {2} snapshot(s) between {3} and {4} have not been inserted into the database.		The counter snapshot(s) for this subscription/contract are stored as erroneous in the database between the 2 dates specified in the log message.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
391 (INFO)	Cache invalidation timeout set to {0}ms
392 (INFO)	Starting the Data File Processor function
393 (INFO)	Data File Processor started
394 (INFO)	Cache warmed ({0} {1} in cache)
395 (INFO)	Starting to warm up the data cache	The warm-up of the data cache is starting.
396 (INFO)	Cache warmed	The warm-up of the data cache successfully ended.
397 (INFO)	Starting to warm up the data cache	The warm-up of the data cache is starting.
398 (INFO)	Cache warmed	The warm-up of the data cache successfully ended.
399 (INFO)	Starting to warm up the data cache	The warm-up of the data cache is starting.
400 (INFO)	Cache warmed	The warm-up of the data cache successfully ended.
401 (INFO)	Provisioning cache initialized with a size of {0} bytes	The provisioning cache has been initialized according to the size specified in the SUBSCRIPTION_CACHE_SIZE system parameter.
402 (INFO)	Starting the warm-up of the {0} cache for the partition {1}	The specified cache will be warmed up for the specified partition ID.
403 (WARNING)	Warm-up of the {0} data cache stopped because the cache is too small	The warm-up of the data cache is stopped because the size of the data cache is too small.	All the objects will not be stored in the cache. If one of the missing objects is required, it will be fetched from the back-end database. This will have an impact on performance.	Increase the size of the data cache by changing the value of the related system parameter: SUBSCRIPTION_CACHE_SIZE: for the storage of provisioning data in each rater instance and updater instance GUIDING_CACHE_SIZE: for the storage of guiding information in each guider instance SESSION_MEMORY_SIZE: for the storage of rating sessions in each rater instance Refer to the SAP CC System Parameter Reference for the description of these parameters.
404 (INFO)	Warm-up of the {0} data cache for the partition {1} stopped ({2} {3} in cache)	The specified cache has been warmed.
405 (INFO)	Guiding cache initialized with a size of {0} bytes	The provisioning cache has been initialized according to the size specified in the GUIDING_CACHE_SIZE system parameter.
406 (INFO)	License will expire on {0}	Indicates the expiration date of the license.
407 (INFO)	CI operation factory connected to host {0} on client {1} using user {2}	This dispatcher instance of the SAP CC system is connected to SAP Convergent Invoicing (SAP CI) in the SAP ERP/FI-CA system.
408 (INFO)	{0} scheduler paused	The scheduler is in pause.
409 (INFO)	{0} scheduler resumed	The scheduler is resumed.
410 (INFO)	{0} scheduler will wake up on {1}	The scheduler is sleeping and will wake up on the specified date.
411 (INFO)	{0} scheduler started	The scheduler is started.
412 (INFO)	Starting the {0} scheduler	The scheduler is starting.
413 (INFO)	{0} scheduler stopped	The scheduler stopped.
414 (INFO)	Stopping the {0} scheduler	The scheduler is stopping.
415 (WARNING)	Invalidation of the cache has been performed after the re-connection to the master dispatcher	The cache has been invalidated before replying to a request because the master dispatcher has changed.	There will be an impact on performance while the cache is being reloaded from the back-end database.	Check if this temporary loss of connection was expected or not.
416 (WARNING)	Invalidation of the cache has been performed after a down connection to the master dispatcher	The cache has been invalidated because the dispatcher connection has been lost.	There will be an impact on performance while the cache is being reloaded from the back-end database.	Check if this temporary loss of connection was expected or not.
417 (INFO)	Master dispatcher has been replaced by {0}	The connection to the known master dispatcher has been replaced by this new connection.
418 (INFO)	{0} ({1}) cannot be authorized to pre-register because the connection for {0} is already used	A server with the specified instance ID is already connected to this server instance.
419 (INFO)	{0} {1} ({2}) is not authorized to register because the dispatcher is reorganizing its connections	This instance of the SAP CC system cannot be authorized to register during the reorganization of the connections of the dispatcher instance.
420 (INFO)	{0} ({1})) cannot be authorized to register because the connection for {0} is already used	A server with the specified instance ID is already connected to this server instance.
421 (INFO)	{0} ({1}) is not authorized to be unregistered because the dispatcher is reorganizing its connections	A server with the specified instance ID is already connected to this server instance.
422 (WARNING)	Instance {0} is still associated with a partition	A connection associated to a partition has been lost but the dispatcher is still referencing the instance in charge of this partition. This reveal a network problem, previous log entries should help solving it.	Some requests may not be answered.	Check the network configuration.
423 (WARNING)	{0} is not an instance of the system ID {1} but an instance of system ID {2}	The instance has not been authorized to connect to the current instance because their system ID are different.	The requesting instance will not start.	Check the boot configuration file (boot.config) of the requesting instance Change the value of the SYSTEM_ID property Restart the requesting instance	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures. Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
424 (INFO)	Instance is registered to the master dispatcher [{0}]	This instance of the SAP CC Core Server system is registered to the master dispatcher instance specified in the log message. The connection information identifies the IP address and communication port.
425 (INFO)	Instance is registered to the slave dispatcher [{0}]	The instance of the SAP CC Core Server system is registered to the slave dispatcher instance specified in the log message. The connection information identifies the IP address and communication port.
426 (WARNING)	{0} is not an instance of the system ID {1} but an instance of system ID {2}	The instance has not been authorized to connect to the current instance because their system IDs are different.	The requesting instance will not start.	Check the boot configuration file (boot.config) of the requesting instance Change the value of the SYSTEM_ID property Restart the requesting instance	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures. Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
427 (INFO)	Instance {0} has been unregistered	The specified instance in the SAP CC system is no longer connected to this running instance. The connection information identifies the IP address and communication port.
428 (INFO)	Instance has not been authorized to stop	This instance has not been authorized to stop.
429 (INFO)	Connection to the master dispatcher is down: {0}	This instance is no longer connected to the master dispatcher instance of the SAP CC Core Server system.
430 (INFO)	Connection to a slave dispatcher is down: {0}	This instance is no longer connected to the specified slave dispatcher instance of the SAP CC Core Server system.
431 (WARNING)	"Unregister" operation has been interrupted due to a timeout	The unregister operation has been interrupted due to a timeout.	The unregister operation will be retried until it can be completed.	Verify the connection of this running instance to the master dispatcher instance in the SAP CC system.
432 (INFO)	Directory [{0}] created	The specified directory has been created by a file processor in this instance of the SAP CC system.
433 (ERROR)	File [{0}] cannot be processed completely because it is corrupted. Processed lines: {1}.	No line of the file has been processed. The file will be marked in error.	No line of the file has been processed.	Check the content of the control file related to the corrupted file for error information. Consult the "Data Files Bulk Loading Process" chapter of the SAP CC 5.0 Application Help for more details.
434 (INFO)	File [{0}] processed. Processed lines: {1}.	The file has been processed.
435 (WARNING)	Request handler queue is full for {0}	The message queue is full and cannot handle more requests. This message will not be rewritten in the following 10 seconds.	The requests will be rejected while the queue is full.	The queue size is specified by a parameter for each service. The related parameters are: BATCH_SERVICE_QUEUE_SIZE DISPATCHER_SERVER_QUEUE_SIZE MULTICAST_SERVER_QUEUE_SIZE STATEFUL_SERVICE_QUEUE_SIZE STATELESS_SERVICE_QUEUE_SIZE	Use SAP CC Admin+ to get the value of this system parameter See the System Parameter Reference to know the correct values
436 (WARNING)	Invalid recurrence [{0}] for {1} scheduler	The recurrence has an invalid format and cannot be used.	The recurrence for the scheduler was not changed.	Set a valid value for the recurrence of the scheduler. Check the syntax in the documentation of the related system parameter.
437 (WARNING)	Cannot unmarshall operations with the NOP OFF framework, check your configuration	A request related to the integration with SAP Convergent Invoicing was sent to a dispatcher instance, but the configuration of the dispatcher instance(s) did not allow it.	The requested operation will not be executed.	Change the value of the system parameter OFF_CLASS to "com.highdeal.off.ci.CIOperationFactory", then restart the dispatcher instance(s).
438 (WARNING)	Invalid notification {0} for the JCo publisher	The JCo publisher had to publish a notification, which it does not handle. The JCo publisher can handle AMOUNT_ALERT and EXPIRATION_ALERT notification types.	The notification will be published through the error channel configured for the JCo publisher.	Consult the notification in the error channel of the JCo publisher.
439 (WARNING)	Instance {0} is not authorized to start because its system ID {1} is invalid	An instance with a different system ID than the one of the current dispatcher requires to start but the request is rejected.	The requesting instance will not start.	Check the boot configuration file (boot.config) of the requesting instance Change the value of the SYSTEM_ID property Restart the requesting instance	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
440 (WARNING)	Connection ({0}) with an unknown system ID requests to start	An instance which does not declare a system ID requests to start.	The requesting instance will start.	Check the boot configuration file (boot.config) of the requesting instance Set the value of the SYSTEM_ID property Restart the requesting instance	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
441 (WARNING)	Connection ({0}) with old protocol requests to start	An instance which does not use the latest protocol version requests to start. This occurs because the requesting instance was not updated to the latest version.	The version declared by the requesting instance will be used.	Configure the requesting instance to use the latest protocol version.
442 (WARNING)	Instance {0} is not authorized to register because its system ID {1} is invalid	An instance with a different system ID than the one of the current dispatcher requires to register but the request is rejected.	The requesting instance will not start.	Check the boot configuration file (boot.config) of the requesting instance Change the value of the SYSTEM_ID property Restart the requesting instance	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
443 (WARNING)	Connection ({0}) with an unknown system ID requests to register	An instance which does not declare a system ID requests to register.	The requesting instance will start.	Check the boot configuration file (boot.config) of the requesting instance Set the value of the SYSTEM_ID property Restart the requesting instance	Boot Configuration File (boot.config) Each instance of the SAP CC Core Server system has a boot configuration file (boot.config) that includes information to connect to its SAP CC system. Consult the SAP CC 5.0 Configuration Guide for more information about the available procedures.
444 (WARNING)	Connection ({0}) with old protocol requests to register	An instance which does not use the latest protocol version requests to register. This occurs because the requesting instance was not updated to the latest version.	The version declared by the requesting instance will be used.	Configure the requesting instance to use the latest protocol version.
445 (WARNING)	Audit field OPERATION_NAME with the value [{0}] has been truncated to [{1}]	The value of the operation name is too large to be inserted into the database and has been truncated.	Some audit data will be lost.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
446 (WARNING)	Audit field OPERATOR_NAME with the value [{0}] has been truncated to [{1}]	The value of the operator name is too large to be inserted into the database and has been truncated.	Some audit data will be lost.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
447 (WARNING)	Audit field OPERAND_REFERENCE with the value [{0}] has been truncated to [{1}]	The value of the operand reference is too large to be inserted into the database and has been truncated.	Some audit data will be lost.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
448 (WARNING)	Audit field MESSAGE with the value [{0}] has been truncated to [{1}]	The value of the audit message is too large to be inserted into the database and has been truncated.	Some audit data will be lost.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
449 (INFO)	Modification of subscription(s) ignoring pending sessions: {0}.	Some subscriptions have been modified while pending sessions were running.	The results generated by the pending sessions may be impacted by the modifications performed on the subscriptions.
450 (INFO)	Deletion of subscription(s) ignoring pending sessions: {0}.	Some subscriptions have been deleted while pending sessions were running.	The pending sessions have been deleted.
451 (WARNING)	Cannot put the data in the cache because it is larger than the cache	The data is larger than the cache, it will not be cached.	The data will not be stored in the cache. If it is required, it will be fetched from the back-end database. This will have an impact on performance.	Increase the size of the provisioning cache by changing the value of the SUBSCRIPTION_CACHE_SIZE system parameter.
452 (WARNING)	Cannot put the subscription in the cache because it is larger than the cache	The subscription is larger than the data cache, it will not be cached in this instance of the SAP CC Core Server system.	The subscription will not be stored in the cache. If it is required, it will be fetched from the back-end database system. This will have an impact on performance.	Increase the size of the provisioning cache by changing the value of the SUBSCRIPTION_CACHE_SIZE system parameter.
453 (INFO)	Tax cache successfully refreshed: The data cache includes {0} VAT rules	This instance of the SAP CC Core Server system has refreshed its data cache that includes the definitions of all the tax rules for all the value added taxes (VAT) configured in the system.			Consult the SAP CC 5.0 Application Help about the tax management.
454 (WARNING)	Cannot put the provider contract in the data cache because it is larger than the cache	The provider contract is larger than the data cache, it will not be cached.	The provider contract will not be stored in the cache. If it is required, it will be fetched from the back-end database system. This will have an impact on performance.	Increase the size of the provisioning cache by changing the value of the SUBSCRIPTION_CACHE_SIZE system parameter.
455 (WARNING)	Cannot put the rating data in the cache because it is larger than the cache	The rating data is larger than the cache, it will not be cached.	The rating data will not be stored in the cache. If it is required, it will be fetched from the back-end database system. This will have an impact on performance.	Increase the size of the rating data cache by changing the value of the SESSION_MEMORY_SIZE system parameter.
456 (FATAL)	Cannot read the private key and certificate for service {0} from the database	An error occurred while reading the private key and the certificate from the database for the specified service.	This instance of the SAP CC Core Server system will not start.	Import a valid private key and a valid certificate in the database for the specified service using the 'keyentry' target of SAP CC Setup Tool.
457 (FATAL)	Cannot read the list of trusted certificates of type {0} from the database	An error occurred while reading the list of trusted certificates from the database for the specified type.	This instance of the SAP CC Core Server system will not start.	Import a valid list of trusted certificates in the database for the specified type using the 'certentry' target of SAP CC Setup Tool.
458 (FATAL)	Cannot initialize the SSL protocol for communications via the Web Services	An error occurred while configuring SSL for the Web Services (WS) technical interface of SAP Convergent Charging.	This instance of the SAP CC Core Server system will not start.	Use the SAP CC Setup Tool user interface to: Verify the validity of the private key and certificate used for the security of the Web Services technical interface. Import new ones if needed using the 'keyentry import' command of Setup Tool. Verify the validity of the trusted certificates configured for the Web Services technical interface. Import new ones if needed using the 'certentry import' command.	Consult the: SAP CC 5.0 Security Guide Refer to the certentry import command and the management of the client certificate entries for secured services.
459 (FATAL)	Cannot initialize the HTTP listener for communications via the Web Services	An error occurred while initializing the HTTP listener dedicated to the Web Services technical interface.	This instance of the SAP CC Core Server system will not start.	Check that the hostname specified in the instance map for the Web Services technical interface belongs to the local host. Change it if needed using the 'instancemap' target of SAP CC Setup Tool. Check that the port number specified in the instance map for the Web Services technical interface is not already in use. Change it if needed using the 'instancemap' target of SAP CC Setup Tool.
460 (FATAL)	Cannot initialize the service [{0}] in the Web Services technical interface	An error occurred while publishing a service (service component) of the Web Services (WS) technical interface.	This instance of the SAP CC Core Server system will not start.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
461 (WARNING)	Authentication attempt with login [{0}] from [{1}] using the Web Services and Single Sign-On was refused because the login is incorrect	An SAP CC user tried to log onto the system using the Web Services technical interface and Single Sign-On (SSO), however the attempt was refused because the login is incorrect. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request will be rejected by the SAP CC system.	Check the user roles and authorizations.
462 (WARNING)	Authentication attempt from [{0}] using the Web Services was refused because the authentication data is invalid	An SAP CC user tried to log onto the system using the Web Services technical interface, however the attempt was refused because the authentication data is invalid. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request will be rejected by the SAP CC system.	Check the configuration of the web services client.
463 (WARNING)	Authentication request was received from address {0} with a client version ({1}) different from the SAP CC system version ({2})	An authentication request was received from a client application whose version differs from the version of the connected SAP CC Core Server system.	Some features of the client application might not work correctly.	Check the versions of the SAP CC Java libraries implemented in the client application. Update the client application or its Customizing to the same version than the server one.
464 (WARNING)	Authentication request was received from address {0} corresponding to a client application whose version is unknown	An authentication request was received from a client application whose version is unknown.	Some features of the client application might not work correctly.	Update the client application to the same version than the server one.
465 (FATAL)	No {1} address found for the hostname {0}	The host name configured in the instance map cannot be resolved as an IP address. The version of the resolved IP addresses, IP v4 or IP v6, does not correspond to the expected IP address version. For example, the configured IP address version is "FORCE_IPV4" but only IPV6 addresses have been resolved.	This instance of the SAP CC Core Server system will not start.	Export the parameter configuration from the database Change the value of the parameter 'IP_ADDRESS_VERSION' according to your network configuration Import the parameter configuration to the database	Instance Map The instance map lists all the instances of an SAP CC system deployed in your system landscape. It is managed by the master dispatcher instance. View the current instance map with the SAP CC Admin+ user interface Export the instance map with the SAP CC Setup Tool user interface
466 (INFO)	Initializing the resend subfunction of the reservation renewal function (session-based charging services)	At startup time, this rater instance of the SAP CC system started the initialization of the resend subfunction of the reservation renewal function available in the session-based charging services for registered client applications or systems.
467 (INFO)	Resend subfunction of the reservation renewal function is paused by an administrator	The resend subfunction of the reservation renewal function is now disabled by an administrator in this instance of the SAP CC system. This instance of the SAP CC system no longer resends any renew reservation notifications.
468 (INFO)	Stopping the resend subfunction of the reservation renewal function	This rater instance of the SAP CC system is stopping the resend subfunction of the reservation renewal function.
469 (INFO)	Resend subfunction of the reservation renewal function is enabled and initialized	The resend subfunction of the reservation renewal function is now enabled and initialized in this rater instance of the SAP CC system. According to the system settings (attempts, interval), the instance will regularly resend the renew reservation notifications as long as an acknowledgment has not been received from a registered client application (or system).
470 (INFO)	Resend subfunction of the reservation renewal function is stopped	This instance of the SAP CC system has stopped the resend subfunction of the reservation renewal function. It will no longer resend renew reservation notifications.
471 (ERROR)	Cannot resend a renew reservation notification. Reason is: {0}	An unexpected error occurred in the system. This rater instance of the SAP CC system cannot resend a renew reservation notification due to this unexpected error when trying to send one or several renew reservation notifications.	The client application (or system) will not receive the renew reservation notification and will not be able to manage properly the session-based charging services for certain end customers.	This error must not occur. Check the reason indicated in your log entry; The reason is based on Java Technology. Archive the log messages and the trace messages Contact your SAP Support Team
472 (INFO)	Pausing the resend subfunction of the reservation renewal function	This instance of the SAP CC system is pausing its resend subfunction after a system configuration change. An administrator has requested to disable the subfunction to resend renew reservation notifications. The instance will complete its current tasks and resend the last renew reservation notifications.
473 (INFO)	Resuming the resend subfunction of the reservation renewal function	This instance of the SAP CC system is resuming its resend subfunction of the reservation renewal function after a system configuration change. An administrator has requested to re-enable the subfunction of the reservation renewal function in the session-based charging services.
474 (INFO)	Resend subfunction of the reservation renewal function is resumed by an administrator	The resend subfunction of the reservation renewal function is now enabled by an administrator in this rater instance of the SAP CC system. According to the system settings (attempts, interval), the instance will regularly resend the renew reservation notifications as long as an acknowledgment has not been received from a registered client application (or system).
475 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the SAP CC user credentials are not valid	An SAP CC user tried to log onto the system, however the attempt was refused because the provided user credentials are not valid. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Use the SAP CC Core Tool user interface to check that the user roles and authorizations.
476 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the SAP CC user is not allowed to perform the operation	An SAP CC user tried to log onto the system, however the attempt was refused because the user has not be configured to be allowed to perform the operation. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Use the SAP CC Core Tool user interface to check that the user roles and authorizations.
477 (INFO)	Authentication attempt with login [{0}] from [{1}] was refused because the SAP CC user credentials have expired	A known SAP CC user tried to log onto the system, however the attempt was refused because the user credentials are no longer valid.	The operation request is rejected by the SAP CC system.	Use the SAP CC Core Tool user interface to check that the user roles and authorizations.
478 (INFO)	Authentication attempt with login [{0}] from [{1}] was refused because the SAP CC user password must be changed	A known SAP CC user tried to log on to the SAP CC Core Server system. However the attempt was refused because the user password must be changed due to the configured password management policy.	The operation request is rejected by the SAP CC system.	Use the SAP CC Core Tool user interface to verify the user roles and authorizations. In your running Core Server system, verify the values of the PASSWORD_MANAGEMENT_EXPIRATION_DELAY system parameter.	SAP CC 5.0 Core Tool Manage SAP CC System Parameters in SAP CC 5.0 Cockpit SAP CC 5.0 System Parameter Reference
479 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the user session [{2}] does not belong to the SAP CC user	An SAP CC user tried to log onto an SAP CC system, however the attempt was refused because the session does not belong to the user. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Use the SAP CC Admin+ user interface to check that the user sessions.
480 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the provided session [{2}] is unknown	An SAP CC user tried to log onto the system, however the attempt was refused because the provided session identifier is unknown for this user. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Check the user sessions.
481 (INFO)	SAP CC user [{0}] (from [{1}]) is not allowed to request the WS operation because this user is not assigned to a catalog	This operation via the Web Services can only be requested by an SAP CC user, which is assigned to a pricing catalog in master data.	The operation request is rejected by the SAP CC system.	Verify that the SAP CC user has a default catalog assigned.
501 (INFO)	Allowances Purge mechanism starts with the reference date {0}	This rater instance of the SAP CC Core Server system is launching the allowance purge mechanism.	The allowance purge mechanism uses system resources and may take some time depending on the overall number of charging contracts and allowances.
502 (INFO)	Rater instance must purge {0} charging contract(s) for the partition {1} ({2}/{3} partitions)	This rater instance of the SAP CC Core Server system is about to start the allowance purge mechanism for the specified number of allowances. This message displays additional information for tracking the allowance purge mechanism.
503 (INFO)	Allowances Purge mechanism: {0}% of charging contract(s) are purged for the partition {1} ({2}/{3} partitions)	This rater instance of the SAP CC Core Server system will purge the specified number of allowances. This message displays additional information for tracking the Allowances Purge mechanism.
504 (INFO)	Allowances Purge mechanism is stopped by a user	A user has stopped the Allowances Purge mechanism of the rating engine of SAP CC Core Server
505 (WARNING)	Connection to the master dispatcher is down: the Allowances Purge mechanism is stopped	The connection to the master dispatcher instance of the SAP CC Core Server system has been lost. The Allowances Purge mechanism cannot proceed and will be stopped.	All expired allowances will not be purged from the system.	Run the Allowances Purge mechanism again after the connection to the master dispatcher is restored to complete the purge of the expired allowances.
506 (INFO)	Rater instance has visited {0} charging contract(s), {1} allowance(s) is/are visited, {2} allowance(s) is/are purged and {3} charging contract visit(s) cannot be purged	This rater instance of the SAP CC Core Server system has finished the Allowances Purge mechanism.	Some charging contracts may not have been purged. The number of charging contracts that could not be purged is specified in the message.	If some charging contract could not be purged, it is mandatory to check that the previous error messages to determine the cause.
507 (WARNING)	Allowances Purge mechanism is already running. The request is refused.	The Allowances Purge mechanism is already running.	The request will be refused.	Wait for the current execution of the Allowances Purge mechanism to complete before trying to execute it again.
508 (INFO)	Allowances Purge mechanism is completed with the status {1}. {0} charging contract(s) have been visited to purge the allowances.	The Allowances Purge mechanism is completed by the system. Check the final status.
509 (INFO)	Allowances Purge mechanism is starting with the reference date {0} and a maximum throughput set to {1} per second per rater instance	The execution of the Allowances Purge mechanism is starting. See the logs of the rater instances for details.
510 (WARNING)	All rater instances received the order to stop the Allowances Purge mechanism. However, some of these rater instances could not comply with the order.	An internal message was sent to all rater instances for stopping the execution of the Allowances Purge mechanism. These rater instances correctly received the order, but some of them could not comply with it.	Some rater instances may not have stopped the execution of the Allowances Purge mechanism.	Check the logs of the rater instances which could not stop the Allowances Purge mechanism.
511 (ERROR)	Some rater instances did not receive the order to stop the Allowances Purge mechanism before the timeout expiration with the following reason: [{0}]	An internal message was sent to all rater instances for stopping the execution of the Allowances Purge mechanism. Some of these rater instances did not receive this order.	Some rater instances may not have stopped the Allowances Purge mechanism.	Check the network connections between the dispatcher instance and the rater instances which did not answer.
512 (INFO)	Next conditions for triggering the Activation scheduler and the Allowances Purge scheduler are synchronized. The provider contracts will not be activated by the Activation process.	Because the Activation scheduler and the Allowances Purge scheduler are triggered at the same time, the Activation process will not activate the provider contracts to improve performance.
513 (INFO)	Next conditions for triggering the Activation scheduler and the Allowances Purge scheduler are synchronized. The provider contracts will be activated by the Allowances Purge mechanism.	Because the Activation scheduler and the Allowances Purge scheduler are triggered at the same time, the Allowances Purge mechanism will activate the provider contracts to improve performance.
514 (INFO)	Activation process of the provider contracts is running. The provider contracts will not be activated by the Allowances Purge mechanism.	Because the Activation process is already running, the Allowances Purge mechanism will not activate the provider contracts.
515 (WARNING)	Retention period for rerating ({0} days) is greater than the retention period for expired allowances ({1} days)	The retention period for rerating (parameter COUNTER_SNAPSHOT_COUNT) is greater than the retention period for allowances (parameter ALLOWANCES_PURGE_RETENTION_PERIOD).	Expired allowances may be deleted by the Allowances Purge mechanism while they are still usable by the chargeable items rerating process. This could result in invalid results during the execution of the chargeable items rerating process.	If allowances are used by the rerating process, increase the retention period for expired allowances.
526 (INFO)	Initializing the resend subfunction of the spending status function	At startup time, this rater instance of the SAP CC system started the initialization of the resend subfunction of the spending status function available for registered client applications or systems.
527 (INFO)	Resend subfunction of the spending status function is paused by an administrator	The resend subfunction of the spending status function is now disabled by an administrator in this instance of the SAP CC system. This instance of the SAP CC system no longer resends any spending status reports.
528 (INFO)	Stopping the resend subfunction of the spending status monitoring	This rater instance of the SAP CC system is stopping the resend subfunction of the spending status monitoring.
529 (INFO)	Resend subfunction of the spending status monitoring is enabled and initialized	The resend subfunction of the spending status monitoring is now enabled and initialized in this rater instance of the SAP CC system. According to the system settings (attempts, interval), the instance will regularly resend the spending status reports as long as an acknowledgment has not been received from a registered client application (or system).
530 (INFO)	Resend subfunction of the spending status monitoring is stopped	This instance of the SAP CC system has stopped the resend subfunction of the spending status monitoring. It will no longer resend spending status reports.
531 (ERROR)	Cannot resend a spending status report. Reason is: {0}	An unexpected error occurred in the SAP CC Core Server system. This rater instance of the SAP CC system cannot resend a spending status report due to this unexpected error when trying to send one or several spending status reports.	The client application (or system) will not receive the spending status report and will not be able to manage properly the spending status monitoring services for certain end customers.	This error must not occur. Check the reason information recorded in your log entry; The reason is based on Java Technology. Archive the log messages and the trace messages Contact your SAP Support Team
532 (INFO)	Pausing the resend subfunction of the spending status monitoring	This instance of the SAP CC system is pausing its resend subfunction after a system configuration change. An administrator has requested to disable the subfunction to resend spending status reports. The instance will complete its current tasks and resend the last spending status reports.
533 (INFO)	Resuming the resend subfunction of the spending status monitoring	This instance of the SAP CC system is resuming its resend subfunction of the spending status monitoring after a system configuration change. An administrator has requested to re-enable the report resend subfunction of the spending status monitoring.
534 (INFO)	Resend subfunction of the spending status monitoring is resumed by an administrator	The resend subfunction of the spending status monitoring is now enabled by an administrator in this rater instance of the SAP CC system. According to the system settings (attempts, interval), the instance will regularly resend the spending status reports as long as an acknowledgment has not been received from a registered client application (or system).
552 (INFO)	List of transport destinations is empty	No transport destination is currently defined in the SAP system.
553 (INFO)	List of transport destinations contains the following aliases: [{0}].	A modification of these destinations only concerns the transport requests which reference them.
554 (INFO)	SAP CC user [{0}] (from [{1}]) is not allowed to request the WS operation because this user is assigned to a catalog	This operation via the Web Services (WS) technical interface, can only be requested by an SAP CC user, which is not assigned to a pricing catalog in master data.	The operation request is rejected by the SAP CC system.	Unassign the catalog from the user or execute the operation with a user with no catalog assigned.
555 (WARNING)	Transport requests execution already running. Request ignored.	The transport requests execution operation is already running.	The execution of transport requests will be ignored.	You should wait for the current operation of transport requests execution to complete.
556 (WARNING)	Transport scheduler execution error	The execution of the transport scheduler encountered an error.	The transport requests execution has not been performed.	Troubleshoot your SAP CC Core Server system to identify a possible cause: Enable and configure the generation of traces Set up the trace severity threshold to PATH Wait for the next transport scheduler execution Analyze the technical information in the trace messages Correct the error(s)
557 (WARNING)	Error occurred while receiving an asynchronous response for the transport web service: {0}	An error occurred while receiving an asynchronous response for the transport web service. Some parameters of the response are missing or invalid.	No transport request will be updated.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
558 (INFO)	Waiting for {0}(s) connection(s) to be closed: {1}.	The dispatcher instance is waiting for client connections to be closed before shutting down.
559 (WARNING)	Allowances Purge mechanism is already running. The request is ignored.	The Allowances Purge mechanism is already running. It is not possible to execute the Allowances Purge mechanism more than once at the same time.	Any new execution of the Allowances Purge mechanism will be ignored by the SAP CC Core Server system.	If you need to run the Allowances Purge mechanism again: You should either wait for the current execution of the Allowances Purge mechanism to complete Or terminate the current Allowances Purge mechanism using SAP CC Admin+ or by implementing the stopPurgeAllowances operation
571 (WARNING)	Data file [{0}] cannot be cleaned because the cleaning queue is full	The data file cannot be cleaned before its archiving because there is too much data files to clean.	The data file is not archived and will not be available for the bulkloader instance or for the third-party system.	The data file will be cleaned again when the rater instance will be restarted.
572 (ERROR)	Data file [{0}] cannot be archived due to an error during cleaning	An error occurred during the cleaning of the data file before its archiving. The possible errors are (but not restricted to): I/O error (e.g. there is not enough space in the file system) File format error (e.g. when a crash occurs during data file compression)	The data file is set in error ("cleanErr" file extension) and will not be available for the bulkloader instance or for the third-party system.	If the data file is not corrupted (e.g. when the error is due to insufficient space in the file system): Rename the erroneous file to remove the cleaning error extension (".cleanErr") Restart the rater instance, to make the data file be cleaned again when the associated channel will be used You could disable the compression of the data files in the bulkWriter CIF processors. Set the deflate parameters to false (XXX_DEFLATE) for the rater bulkWriter CIF processors Restart your system to activate this configuration You could elevate the trace level to have detailed information when this error occurs. Enable and configure the generation of traces Set up the trace severity threshold to PATH Ensure that the tracing domain for the bulk loading mechanism (BLK) is enabled After the error occurs, analyze the technical information in the trace messages Correct the error(s)
573 (INFO)	Instance is registered to the dispatcher [{0}]	This instance of the SAP CC Core Server system is registered to the specified dispatcher instance. The connection information identifies the IP address and communication port. Note This running instance in the SAP CC system does not know if the dispatcher instance is master or slave.
574 (INFO)	Connection to a dispatcher instance is down: {0}	This instance of the SAP CC Core Server system is no longer connected to the specified dispatcher instance.
575 (INFO)	Applying change list on destination [{0}]	Call of the changeListApply operation of the transport webservice for the specified destination.
576 (WARNING)	Cannot send the change list to current destination due to error: {0}.	The change list cannot be sent on the destination.	The change list is not applied on the configured destination(s).	Check the dispatcher URL of the transport destination Check the user credentials within the transport destination Check that the system which is referenced by the transport destination is started Check that the Web Services are available in the SAP CC system referenced by the transport destination Check the imported certificates if a secured connection is configured
577 (INFO)	Execution of transport request [{0}] is ended	The transport request was executed on its associated transport destination(s).
578 (INFO)	Execution of transport request [{0}] relating to the change list [{1}] is starting	The SAP CC Core Server system executes a transport request.
579 (WARNING)	Transport request cannot be executed due to error: {0}.	The change list cannot be transported to the configured destination(s).		Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
580 (WARNING)	Guider instance is not configured to store the unique identifier of subscriber accounts in the guiding cache	This guider instance is not configured to store the unique identifier of subscriber accounts related to accessible charges in the guiding cache and cannot thus provide it in responses to guiding requests.	The vertical scalability of the rater instances will not be optimal.	Execute the procedure "Enhancement of the vertical scalability of rater instances" described in the SAP CC Upgrade Guide.
581 (WARNING)	Rater instance is not configured to use the unique identifier of subscriber accounts for workload distribution	This rater instance is not configured to use the unique identifier of subscriber accounts of the accessible charges and cannot thus use it to distribute the workload between the threads of the stateful service.	The vertical scalability of the rater instances will not be optimal.	Execute the procedure "Enhancement of the vertical scalability of rater instances" described in the SAP CC Upgrade Guide.
582 (WARNING)	Invalid CIF configuration: inconsistent number of channels between bulkWriter "{0}" ({1} channels) and bulkReader "{2}" ({3} channels)	The number of writing channels allocated to the specified bulkWriter function in the rater instances differs from the number of reading channels allocated to the specified bulkReader function in the bulkloader instances. For each type of output data, the SAP CC system instances handle several channels to manage multiple files The mechanisms provide mass parallel processing and a high level of performance. Each channel handles a unique file. Example The POSTPAID_CIT_WRITER function in the rater instances must have the same number of channels as the POSTPAID_CIT_READER function in the bulkloader instances.	Some output data files generated by the specified bulkWriter function in the rater instances will not be processed by the corresponding bulkReader function in the bulkloader instances.	Update the CIF configuration so that the number of writing channels for the specified bulkWriter in the rater instances is equal to the number of reading channels for specified bulkReader in the bulkloader instances. Use the SAP CC Setup Tool user interface and the cif export command Edit the exported text file and change the relevant value Import the changed configuration file with Setup Tool and the cif import command This change may impact the global performance of the SAP CC system.
583 (WARNING)	Instance stopping and starting again for an internal reason	This instance of the SAP CC Core Server system is stopping for an internal reason. The startup framework will start the SAP CC system instance again. The current state of this instance is not consistent with the complete SAP CC system. There are several reasons that explain this issue: Concurrence between two master dispatcher instances (see message ID com.sap.SCC.core_server.000293) Concurrence between two active updater instances Instance reconnecting to the master dispatcher instance, and then not authorized by the master dispatcher instance, for some reason Try to determine the reason that is relevant for you and your SAP system landscape.	This instance will not be available during the restart sequence.	This instance restarts automatically. Determine the preventive actions to perform. To troubleshoot this potential anomaly, you analyze the cause of this stop and restart sequence: Verify the previous log messages of this instance Verify the previous trace messages of this instance Verify the previous log messages of all dispatcher instances
584 (INFO)	Loading and initializing the CIF configuration	The bulkloader is loading and initializing the CIF configuration. The CIF configuration defines the way the bulkloaders must process the charged items and chargeable items generated by raters.
585 (INFO)	CIF configuration loaded and initialized	The bulkloader has successfully loaded and initialized the CIF configuration. The CIF configuration defines the way the bulkloaders must process the charged items and chargeable items generated by raters.
586 (INFO)	Loading and initializing the CIF configuration	The rater is loading and initializing the CIF configuration. The CIF configuration defines the way the raters must output charged items and chargeable items.
587 (INFO)	CIF configuration loaded and initialized	The rater has successfully loaded and initialized the CIF configuration. The CIF configuration defines the way the raters must output charged items and chargeable items.
588 (INFO)	Loading and initializing the RIF configuration	The rater is loading and initializing the RIF configuration. The RIF configuration defines the way the raters must handle rerating orders from the BART Server.
589 (INFO)	RIF configuration loaded and initialized	The rater has successfully loaded and initialized the RIF configuration. The RIF configuration defines the way the raters must handle rerating orders from the BART Server.
590 (INFO)	Loading the notification policy	The rater or bulkloader is loading the notification policy. The notification policy defines the way the raters or bulkloaders must handle the notifications. On raters side, the notifications are generated during the charging operations On bulkloaders side, the notifications are retrieved from the locations defined in the bulkloader policy
591 (INFO)	Notification policy loaded	The rater or bulkloader has successfully loaded the notification policy. The notification policy defines the way the raters or bulkloaders must handle the notifications. On raters side, the notifications are generated during the charging operations On bulkloaders side, the notifications are retrieved from the locations defined in the bulkloader policy
592 (INFO)	Initializing the notification policy	The rater or bulkloader is initializing the notification policy. The notification policy defines the way the raters or bulkloaders must handle the notifications. On raters side, the notifications are generated during the charging operations On bulkloaders side, the notifications are retrieved from the locations defined in the bulkloader policy
593 (INFO)	Notification policy initialized	The rater or bulkloader has successfully initialized the notification policy. The notification policy defines the way the raters or bulkloaders must handle the notifications. On raters side, the notifications are generated during the charging operations On bulkloaders side, the notifications are retrieved from the locations defined in the bulkloader policy
594 (INFO)	Loading the bulkloader policy	The bulkloader is loading the bulkloader policy. The bulkloader policy defines the locations that the bulkloder must use to read notifications generated by raters.
595 (INFO)	Bulkloader policy loaded	The bulkloader has successfully loaded the bulkloader policy. The bulkloader policy defines the locations that the bulkloder must use to read notifications generated by raters.
596 (INFO)	Initializing the bulkloader policy	The bulkloader is initializing the bulkloader policy. The bulkloader policy defines the locations that the bulkloder must use to read notifications generated by raters.
597 (INFO)	Bulkloader policy initialized	The bulkloader has successfully initialized the bulkloader policy. The bulkloader policy defines the locations that the bulkloder must use to read notifications generated by raters.
598 (INFO)	Initializing OFF configuration	The instance is initializing the OFF configuration.
599 (INFO)	Instance is registering to the dispatcher [{0}]	The instance of the SAP CC Core Server system is registering to the dispatcher instance specified in the log message. The connection information identifies the IP address and communication port.
600 (INFO)	Instance is connecting to the dispatcher [{0}]	The instance of the SAP CC Core Server system is connecting to the dispatcher instance specified in the log message. The connection information identifies the IP address and communication port.
601 (INFO)	Instance is connected to the dispatcher [{0}]	This instance of the SAP CC Core Server system is connected to the dispatcher instance specified in the log message. The connection information identifies the IP address and communication port.
602 (INFO)	Connecting to the JCo destination {0} on host {1} using client {2} and user {3} with version {4} of the JCo library.	SAP Convergent Charging is connecting to a JCo destination.
603 (INFO)	Connected to the JCo destination {0}.	SAP Convergent Charging is connected to a JCo destination.
604 (INFO)	Logging and tracing successfully configured with system parameters.	Both the logging and tracing functions are configured now in the corresponding SAP CC system instance. The functions use the system parameters such as the LDF1_ENABLED system parameter and LDF2_ENABLED system parameter. See the Logging and Tracing Settings parameter group in the SAP CC 5.0 System Parameter Reference.			Configuration (System) To configure some SAP CC system parameters in the SAP CC Core Server system, see the app Manage SAP CC System Parameters in the SAP CC 5.0 Cockpit user interface or see the SAP CC Admin+ user interface. For more information and user assistance, consult the SAP CC 5.0 System Parameter Reference. Features, Concepts SAP CC 5.0 Application Help
611 (WARNING)	SAP CC user [{0}] (from [{1}]) is not allowed to use the technical interface	An SAP CC user tried to log on to the system, however the attempt was refused because the security profile of the user (service user or individual user) does not allow it to use the technical interface. This security message is intended to warn of a possible attack and should be investigated by the administrator.	The operation request is rejected by the SAP CC system.	Check the security profile of the user.
612 (INFO)	Starting the cleanup service for processing unclosed data files.	The cleanup service is starting in order to process the data files that have not been properly released by the associated Rater, and which must thus be archived for further bulk loading operations.
613 (INFO)	Cleanup service executed. {0} data files archived and {1} data files failed to be processed.	The execution of the cleanup service ended for targeted data files. The data files that failed to be processed will not be available for further bulk loading operations.
614 (INFO)	Thread dump generated in file {0} for the following reason: {1}	A thread dump file has been generated because a triggering condition has been reached within an instance of the Core Server system.
615 (ERROR)	An error occurred during the generation of a thread dump file: {0}	The generation of a thread dump file failed due to an internal error. The thread dump file could not be generated.	The thread dump file will not be generated, and no information will thus be available for the execution context of the related thread.	Troubleshoot your SAP CC system by analyzing the description of the internal error that is provided as an argument of this log message.
616 (INFO)	{0} file(s) deleted during the cleanup operation related to thread dump files	The execution of the cleanup operation ended for targeted thread dump files. For further information about the recurrence of this operation, refer to the description of the THREAD_DUMP_RETENTION_PERIOD system parameter available in the SAP CC System Parameter Reference documentation.
617 (INFO)	List of thread dump files whose generation aborted due to the generation interval condition: {0}	The automated generation of thread dump files is enabled in this instance of the running SAP CC Core Server system. The THREAD_DUMP_MINIMUM_INTERVAL system parameter gives the possibility to define the minimum number of seconds between two generations of a thread dump file relating to the same triggering reason. In rare case multiple thread dump files must be generated for the same reason within this defined interval, corresponding generation operations are aborted but listed for information purpose. For more information about the definition of the minimum interval, refer to the THREAD_DUMP_MINIMUM_INTERVAL system parameter in the SAP CC 5.0 System Parameter Reference.		Verify the abort reasons and contact your SAP Support Team.	Thread dump files provide your SAP Support Team with some advanced supportability tools. Consult the SAP CC 5.0 Operations Guide and contact a support specialist from your SAP Support Team to know how to work with thread dump files of SAP Convergent Charging. System configuration: THREAD_DUMP_ENABLED system parameter Thread Dump File Generation Troubleshooting Settings parameter group Technical operations: Troubleshooting: see Troubleshooting of SAP CC Monitoring: see the Thread Dump metric node See also: SAP CC 5.0 System Parameter Reference SAP CC 5.0 Operations Guide SAP CC 5.0 Metric Reference and Performance Troubleshooting
618 (INFO)	File [{0}] was not processed completely because the instance is shutting down.	This bulkloader instance is shutting down. It did not process the identified file completely. The instance automatically resumes processing the file after its restart.
619 (INFO)	Starting the service in charge of creating data files.	Raters and bulkloaders use the Charging output Integration Framework to generate data files. The pre-creation service is used to create these data files before they are really used, in order to increase performances regarding contention and latency during writing operations.
620 (INFO)	The service in charge of creating data files is stopped	The pre-creation service is stopped.
621 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the login or the password is incorrect	A client application tried to log on to the SAP CC system, but the attempt was refused because the login or the password is incorrect. This security message warns of a possible attack that the administrator should investigate.	The operation request is rejected by the SAP CC system.	Check the user login or the password.
622 (WARNING)	Authentication attempt with login [{0}] from [{1}] was refused because the user does not have the Message Charging Client role	A client application tried to log on to the SAP CC system, but the attempt was refused because the user does not have the Message Charging Client role. This security message warns of a possible attack that the administrator should investigate.	The operation request is rejected by the SAP CC system.	Check the user roles.
623 (WARNING)	Authentication attempt without credential from [{0}] was refused because authentication is required	A client application tried to log on to the SAP CC system, but the attempt was refused because credentials are needed. This security message warns of a possible attack that the administrator should investigate.	The operation request is rejected by the SAP CC system.	Check the credentials.
624 (INFO)	{0} remaining partitions to release before completing the shutdown of this instance of the SAP CC Core Server system. List of remaining partitions: {1}	This instance of the SAP CC Core Server system has received a shutdown request. This instance must release the set of handled partitions to give the master dispatcher the possibility to distribute this set among the other running instances of the same type. For further information, refer to the "Partitions mapping reorganization" section of the SAP CC Application Help documentation.
625 (INFO)	Executing hard shutdown of {0} instance {1} with a configured timeout of {2} seconds (waiting for the dispatcher authorization to stop)	This instance of the SAP CC Core Server system has received a hard shutdown request from the startup framework. For further information, refer to the "Starting and stopping the servers" procedure available in the SAP CC Installation Guide documentation. The instance waits for an authorization to stop from the master dispatcher instance.	This instance will shut down.
626 (INFO)	Executing soft shutdown of {0} instance {1} (waiting for the dispatcher authorization to stop)	This instance of the SAP CC Core Server system has received a soft shutdown request from the startup framework. For further information, refer to the "Starting and stopping the servers" procedure available in the SAP CC Installation Guide documentation. The instance waits for an authorization to stop from the master dispatcher instance.	This instance will shut down.
627 (INFO)	Shared Allowance cache initialized with a size of {0} bytes	The shared allowance cache has been initialized according to the size specified in the SHARED_ALLOWANCE_CACHE_SIZE system parameter.
628 (INFO)	{0} shared Allowances were victimized due to the update of the shared Allowance cache	The number of shared Allowances victimized due to the update of the shared Allowance cache
629 (INFO)	Refreshing the shared allowance cache	The refreshing operation of the cached structure containing shared allowances is starting.
630 (INFO)	The shared allowance cache has been refreshed	The refreshing operation of the cached structure containing shared allowances successfully ended. The shared allowances cache is now up-to-date.
631 (ERROR)	The shared allowances cache could not be refreshed.	An error occurred during the refreshing operation of the cached structure containing shared allowances. The shared allowances cache has not been refreshed and is thus not up-to-date.
632 (INFO)	The recharging feature is deactivated	The Chargeable Items Recharging feature is deactivated within your SAP CC landscape.	Recharging operations cannot be performed anymore.
633 (INFO)	Starting the recording service for file metadata	This instance is starting the service in charge of recording metadata about data files generated by SAP CC during the execution of the different processes.
634 (INFO)	Recording service for file metadata successfully started	This instance has successfully started the service in charge of recording metadata about data files generated by SAP CC during the execution of the different processes.
635 (INFO)	Stopping the recording service for file metadata	This instance is stopping the service in charge of recording metadata about data files generated by SAP CC during the execution of the different processes.
636 (INFO)	Recording service for file metadata successfully stopped	This instance has successfully stopped the service in charge of recording metadata about data files generated by SAP CC during the execution of the different processes.
637 (ERROR)	An error occurred while recording file metadata in the Core database. {0} files could not be recorded. Reason is: {1}.	An error occurred while recording file metadata in the Core database.	Metadata will not be recorded for the impacted data files. The data available in the "Analyze Item Files" web application will not be consistent for these data files.	Verify the reason provided in the log message Verify for additional traces about the error
638 (INFO)	Starting the purge of file metadata with the reference date {0}	This updater instance of the SAP CC Core Server system is executing a purge operation of file metadata.	The purge of file metadata uses system resources and may take some time depending on the overall number of file metadata that exist in the Core database.
639 (INFO)	Purge of file metadata ended. {0} file metadata purged.	This updater instance of the SAP CC Core Server system has finished a purge operation of file metadata.	Some file metadata may not have been purged. Verify the previous log message to get information about the reason of the possible errors.
640 (ERROR)	An error occurred while purging file metadata from the Core database. Reason is: {0}.	An error occurred while purging file metadata from the Core database.	Some metadata will not be purged.	Verify the reason provided in the log message. Verify for additional traces about the error. Perform the purge of file metadata again.
650 (INFO)	Cleanup service still running for {0} data files containing uncommitted items that must be removed	The execution of the cleanup service is still running asynchronously for data files containing uncommitted items that must be removed. The related data files will be available for further bulk loading operations once the cleanup ends.
651 (INFO)	Shutdown request received: closing opened data files	This instance of the SAP CC Core Server system has received a request to shut down. Opened data files will be closed if possible to ensure that a maximum of these data files are closed properly for further bulk loading operations.
652 (WARNING)	The SLD server was not recognized	The SLD registration request was sent to an HTTP server that could not be identified. This security message warns of a possible error in the configuration of the System Landscape Directory (SLD) or of your SAP CC Core Server system.	The SAP CC system cannot confirm that the SLD registration has been taken into account.	Verify whether the SAP CC system has been properly registered in the SLD. Verify that the SLD system is correctly running. Verify that the SLD_URL system parameter points to the Data Supplier service of the SLD.
653 (WARNING)	Audit field INSTANCE_ID with the value [{0}] has been truncated to [{1}]	The value of the audit instance identifier is too large to be inserted into the database and has been truncated.	Some audit data will be lost.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
654 (WARNING)	{0} session start operation(s) refused because the subscriber account has already more than {1} started session(s).	Some session start operations have been refused because the limit of started sessions per subscriber account has been reached. For further information, refer to the description of the RATING_SESSION_PER_SUBSCRIBER_ACCOUNT_LIMIT system parameter.	The operation is refused.	The configured limit has been reached. The operations are refused to limit the potential impact on the system stability. You should investigate the reason why the subscriber account(s) have reached the configured limit.	Consult the SAP CC System Parameter Reference to find more information on the configuration parameter RATING_SESSION_PER_SUBSCRIBER_ACCOUNT_LIMIT.
701 (ERROR)	Cleanup operation fails on subscriber account {0} for session {1} and reservation {2} due to error: {3}	The cleanup operation failed. The expired charging session cannot be cleanup and removed.	The operation is refused, it may be a cleanup operation or the operation that triggered the cleanup. The expired session is still attached to the subscriber account in the session history and may lead to other failures.	Verify the error message and the expired session for the subscriber account in error to determine the cause and an action plan. Possible solutions are: Try to cleanup again this subscriber account in case of a temporary failure. Correct the customer data of the subscriber account, such as its prepaid accounts, subscriber mapping tables, counters or allowances. Cancel the subscriber account expired charging session in error. Correct the pricing catalog that cause the error, such as mapping tables, price plan or charging plan.
702 (INFO)	Publish the list of available dispatchers to the internal clients	Publish the list of available dispatchers to the internal clients
703 (WARNING)	Retry to publish the list of available dispatchers to the internal clients	Retry to publish the list of available dispatchers to the internal clients
704 (INFO)	The list of available dispatchers to the internal clients has been published	The list of available dispatchers to the internal clients has been published
705 (WARNING)	Cannot publish the list of available dispatchers to the internal clients	Cannot publish the list of available dispatchers to the internal clients
706 (WARNING)	The connection to the {0} cannot be close because {1} has not be unregistered (Process has started at {2})	The connection of one dispatcher instance cannot be close because it has not be unregistered. It will be retried.
707 (WARNING)	Stop to check the status of the {0} (the timeout is reached, process has started at {1})	The timeout of 45 seconds has been expired. This stops the check of the status of the dispatcher instance.
708 (WARNING)	The connection to the {0} can be closed, the {1} is already unregistered (Process has started at {2})	The connection to the dispatcher instance can be closed, it is already unregistered.
709 (WARNING)	Stopping to waiting for {0} connection(s) to be closed due to timeout: {1}.	Stopping to waiting for {instanceType}(s) connection(s) to be closed due to timeout: {connection}.
710 (INFO)	The maintenance mode has been enabled.	Due to maintenance operations, the Core Server system now runs in maintenance mode.
711 (INFO)	The maintenance mode has been disabled.	The maintenance mode has been disabled for the Core Server system.
712 (INFO)	The standby status of some instances has changed. Current status is: {0}	The standby status of some instances has changed.
713 (INFO)	Warm-up of the {0} data cache for the partition {1} stopped ({2} {3} in cache, {4} warmed using network data transfer)	The specified cached structure has been warmed using network data transfer operations.
714 (INFO)	Starting to update the instance map	The dispatcher is starting the reorganization of the instance map.
715 (INFO)	Cache warm-up configuration: \n- Network data transfer: {0}\n- Instances incompatible with network data transfer: {1}
716 (INFO)	No new partition to assign to the following instances: {0}	The specified instances are not concerned by the instance map reorganization and will not receive any new partition.
717 (INFO)	New partition to assign to the following instances: {0}	The specified instances are concerned by the instance map reorganization and will receive the specified set of partitions.
718 (INFO)	Assigned new partition(s) to the following instances: {0}	The specified set of partitions have been assigned to the specified instances.
719 (INFO)	No more partition assigned to {0}. {0} is authorized to stop	The specified instance does not handle any partition and does not take part anymore of any process. This instance can thus stop.
720 (INFO)	No more data transfer activity on the network for {0}. {0} is authorized to stop	Data transfer operations ended for the specified instance. This instance does not handle any partition and does not take part anymore of any process. This instance can thus stop.
721 (INFO)	The update of the instance map has stopped due to a new reorganization	The status of some instances has changed in parallel, which leads to a new reorganization of the currently computed instance map. As a consequence, the dispatcher needs to stop the current reorganization operation to perform a new one.
722 (INFO)	Waiting for the end of partitions warm-up operations	All partitions have been distributed to the running instances. The dispatcher is waiting for the end of the related warm-up operations.
723 (INFO)	All warm-up operations ended	All warm-up operations performed by all the running instances ended. The reorganization of the instance map is thus finished.
724 (INFO)	Starting the warm-up of the {0} cache for the partition {1} from the database	The specified cached structure will be warmed up from the database using data related to the specified partition ID.
725 (WARNING)	Unable to send {0} object(s) due to exceeded message size ({1})	The size of the data sent over the network exceeded the value defined in the CONNECTION_MESSAGE_MAX_SIZE system parameter. This warning message will not be displayed in the following 10 seconds.	The requesting instance will not receive the data and may have to load this data from the database.
726 (WARNING)	Unable to receive {0} {1} due to exceeded message size during warm-up of the partition {2}	The size of the data sent over the network exceeded the value defined in the CONNECTION_MESSAGE_MAX_SIZE system parameter.	The requested data will not be warmed up and the instance may have to load this data from the database.
727 (WARNING)	Prefix for parameter names is missing in the CIF configuration for the {0} CIF processor. Change the system settings.	The CIF configuration for the specified CIF processor is incorrect. A prefix for the parameter names is missing in these system settings. The CIF configuration is an XML structure. It must include the attribute adminParameterPrefixName in the XML elements that are specified in your log message. Note that the CIF configuration depends on the type of the instances in the SAP CC Core Server system.	In the SAP CC Core Server system, this instance will start but the system parameters for this CIF processor will not be available when using the SAP CC Admin+ and the SAP CC Cockpit user interfaces or the SAP CC APIs.	Correct the CIF configuration of your SAP CC Core Server system: Determine the type of instances in the system that generated the log message. Export the CIF configuration for this type of instances using the SAP CC Setup Tool user interface. Verify that the CIF configuration is correctly set. Add some missing mandatory XML attributes adminParameterPrefixName to define the system parameters properly. Refer to the SAP Note 2470720 for more information and user assistance. Import the modified CIF configuration.	SAP CC 5.0 Setup Tool SAP Note 2470720
728 (INFO)	The Prepaid Accounts Management feature is disabled	The Prepaid Accounts Management feature is disabled. This means that master data related to prepaid accounts are no more available in both user interfaces and operations from the Web Services and HCI technical interfaces: Prepaid Account in Subscriber Account Refill Item Class Refill Record Class Refill Logic Refill Plan
729 (INFO)	Loading the instance configuration from the boot configuration file	This instance is loading the settings related to its communication channels from its boot configuration file.
730 (INFO)	SCIM REST API is enabled	The SCIM 2.0 Web Service (REST) feature and functions are enabled in this instance of the running SAP CC Core Server system.
731 (WARNING)	SCIM REST API cannot be enabled because the Web Services are not secured	To enable the SCIM REST API feature, the Web Services must be secured.
732 (FATAL)	Cannot initialize the rest application [{0}] in the Web Services technical interface	An error occurred while publishing an application (service component) of the Web Services (RS) technical interface.	This instance of the SAP CC Core Server system will not start.	Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
733 (INFO)	Rest application published and available at: {0}://{1}:{2}/{3}	The URL of the published Rest application. This URL is required by the systems connected to the SAP CC Core Server system with this technical interface (Web Services).