Index of com.sap.SCC.core_client (SAP CC 5.0 Log Messages)

Index of com.sap.SCC.core_client

Index Log Message Description Impacts Actions Information

0 (WARNING) Could not encrypt data of the configuration file located at {0}: The file cannot be read or written.
The configuration data cannot be encrypted because the configuration file could not be read or written.

Critical data will stay human readable in the file.

Fix the file permissions to allow read/write operations by the SAP CC system.

1 (FATAL) Cannot initialize the VAT tax system because the currency book cannot be initialized
The tax system for VAT cannot be initialized properly because the currency book could not be initialized in the SAP CC system.

The tax system will not be initialized.

Troubleshoot your SAP CC system to identify a possible cause:

Check the previous log messages for errors

Correct the error(s)

Technical information: See taxation module

2 (WARNING) Cannot calculate taxes of a transaction with tax code {0}
The SAP CC system cannot calculate taxes for the transaction during a charging operation.

The transaction amounts will not include taxes.

The transaction which could not be taxed properly can be identified by its taxStatus field which is set to tsTaxMissedForInfo.

3 (WARNING) Cannot load the ISO 3166 file {0}: An I/O error occurred while reading the file.
The resource file containing the country codes was not completely loaded.

Some or all country codes and names may not appear where a list of countries is used.

Check the ISO 3166 file access and permissions.

4 (ERROR) Cannot initialize the tax system: The parameter {0} is missing.
The tax system cannot be initialized due to a missing parameter.

The tax system will not be initialized.

Use SAP CC Admin+ to verify that the missing system parameter (TAX_PRECISION) is set and has a valid value.

Consult the SAP CC Application Help for more information about the tax functions and processes in SAP Convergent Charging.

5 (ERROR) Cannot initialize the tax system: The value [{0}] is not valid for the parameter {1}, it must be an integer.
The tax system cannot be initialized due to an invalid value.

The tax system will not be initialized.

Verify that the given parameter (TAX_PRECISION) has a valid value.

See the SAP CC Admin+ documentation to set up a parameter.

6 (INFO) Initializing the {0} tax system...
The taxation module selected in the configuration is being initialized.

7 (INFO) {0} tax system initialized>
The taxation module selected in the configuration has been initialized.

8 (ERROR) Cannot found the Java class {0} of the tax system
A required Java class cannot be found.

The tax system will not be initialized.

Check the expected Java class is present in the CLASSPATH of the application.

9 (ERROR) Cannot instantiate the Java class {0} of the tax system
The application cannot instantiate the Java class for the taxation module.

The tax system will not be initialized.

The class should be instantiable

The class should have nullary constructor

Technical information: See taxation module

10 (ERROR) Cannot access the Java class {0} of the tax system
The application does not have access to the definition of the Java class for the taxation module.

The tax system will not be initialized.

The Java class should be accessible (in the Java class semantic).

11 (WARNING) Cannot find a counter during the recharging process. The counter is identified by: Key:{0}, Subscriber Account ID:{1}, Holder ID:{2}, Partition ID:{3}.
An expected counter is missing during the execution of the recharging process.

The recharging operation could not be performed.

Check the counter identifiers.

Check previous log messages for errors

Correct the error(s)

12 (WARNING) Partition {0} is switched to a new connection without unregistered procedure. There are {1} operation(s) on-going on the connection {2}.
A partition is being switched while there are ongoing operations on the connection.

An instance of the SAP CC Core Server system has been disconnected.

Troubleshoot your SAP CC system to identify a possible cause:

Check the previous log messages for errors

Correct the error(s)

Restart the instance(s) of the SAP CC system

13 (WARNING) Memory accessor {0} manages the following unknown parameters: {1}
The memory accessor manages parameters that are unknown.

The unknown parameters cannot be accessed.

This may be an implementation issue.

14 (WARNING) Persistent accessor {0} manages the following unknown parameters: {1}
The persistent accessor manages parameters which are unknown.

The unknown parameters cannot be accessed.

This may be an implementation issue.

15 (WARNING) Could not publish the notification because of an invalid message. The notification was: {0}.
The notification could not be published

External systems may not have received the notification.

Increase the trace severity to PATH to see the related exception

Check your notification configuration

16 (WARNING) Could not publish the notification because of a communication error. The notification was: {0}.
The notification could not be published.

External systems may not have received the notification.

Increase the trace severity to PATH to see the related exception

Check your notification configuration

17 (WARNING) Could not publish the notification because the acknowledgment time expired. The notification was: {0}.
The notification could not be published.

External systems may not have received the notification.

Check your notification configuration.

Check the external systems.

18 (ERROR) Cannot initialize the EIF connector class: The EIF configuration parameters are invalid.
The configuration parameters relating to the EIF are invalid.

The EIF Connector functions will not be initialized.

Correct the erroneous values of the EIF configuration parameters.

SAP Convergent Charging provides the Exportable item Integration Framework (EIF) feature to implement either a custom EIF Connector or a delivered connector in the SAP CC Core Server system.

In an integrated SAP Solution, a specialized connector is used and configured when SAP Convergent Invoicing is the target destination.

It is the CI Connector. The corresponding Java class is: com.highdeal.eif.ci.CIConnector

See also: EIF_CONN_CLASS indicator in SAP CC 5.0 System Parameter Reference

19 (INFO) EIF configuration initialized with ID [{0}]
The EIF Connector is initialized. Its functions implement the Exportable item Integration Framework (EIF) of SAP Convergent Charging.

SAP Convergent Charging provides the Exportable item Integration Framework (EIF) feature to implement either a custom EIF Connector or a delivered connector in the SAP CC Core Server system.

In an integrated SAP Solution, a specialized connector is used and configured when SAP Convergent Invoicing is the target destination.

It is the CI Connector. The corresponding Java class is: com.highdeal.eif.ci.CIConnector

See also: EIF_CONN_CLASS indicator in SAP CC 5.0 System Parameter Reference

21 (ERROR) Cannot initialize the EIF connector class: Cannot instantiate EIF connector with class {0}.
The application cannot instantiate the Java class for the EIF Connector.

The EIF Connector functions will not be initialized.

The Java class name can be specified by using the EIF_CONN_CLASS indicator to identify the EIF Connector function that is based on the Exportable item Integration Framework (EIF) of SAP Convergent Charging.

Verify that this parameter is correctly set.

Verify that the signaled Java class is present in the classpath of the Java Virtual Machine (JVM) that runs the application.

The Java class must be instantiable and have a nullary constructor.

SAP Convergent Charging provides the Exportable item Integration Framework (EIF) feature to implement either a custom EIF Connector or a delivered connector in the SAP CC Core Server system.

In an integrated SAP Solution, a specialized connector is used and configured when SAP Convergent Invoicing is the target destination.

It is the CI Connector. The corresponding Java class is: com.highdeal.eif.ci.CIConnector

See also: EIF_CONN_CLASS indicator in SAP CC 5.0 System Parameter Reference

22 (ERROR) Cannot initialize the EIF connector class: The Java class {0} cannot be accessed.
The application does not have access to the definition of the Java class for the EIF Connector.

The EIF Connector functions will not be initialized.

The Java class name can be specified by using the EIF_CONN_CLASS indicator to identify the EIF Connector function that is based on the Exportable item Integration Framework (EIF) of SAP Convergent Charging.

Verify that this parameter is correctly set.

Verify that the signaled Java class is present in the classpath of the Java Virtual Machine (JVM) that runs the application.

The Java class must be accessible.

SAP Convergent Charging provides the Exportable item Integration Framework (EIF) feature to implement either a custom EIF Connector or a delivered connector in the SAP CC Core Server system.

In an integrated SAP Solution, a specialized connector is used and configured when SAP Convergent Invoicing is the target destination.

It is the CI Connector. The corresponding Java class is: com.highdeal.eif.ci.CIConnector

See also: EIF_CONN_CLASS indicator in SAP CC 5.0 System Parameter Reference

23 (WARNING) Could not find a request handler. Unknown topic {0} for the request {1}.
The remote client may not receive the answer.

The client waits indefinitely for the answer. It may be blocked.

24 (ERROR) Could not find a request handler. Unknown topic {0} for the request {1} and the client cannot be informed because a timeout has expired.
The remote client may not receive the answer.

The client waits indefinitely for the answer. It may be blocked.

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.

25 (ERROR) Could not find a request handler. Unknown topic {0} for the request {1} and the client cannot be informed because of a communication error.
The remote client may not receive the answer.

The client waits indefinitely for the answer. It may be blocked.

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.

26 (WARNING) Cannot put the session(s) in the cache because the size is bigger than the cache
The session(s) is/are bigger than the cache, it will not be cached.

Performances.

The size of the session subcaches and the session history sub caches are computed by the parameter SESSION_MEMORY_INSTANCES and the parameter SESSION_MEMORY_SIZE.

Check these parameters are correctly set.

27 (INFO) Initializing EIF configuration
The instance is initializing the EIF configuration.

34 (WARNING) The validity period of the newly created allowance is postponed by the system for the allowance plan [{2}] with the subscriber account [{0}] and the provider contract [{1}] because an allowance cannot be renewed more than once per day.
The system postpones the validity period of the new allowance to the validity start date of the expired allowance plus 1 day (Gregorian Calendar).

If the validity period of the expired allowance is lower than 1 day, a time interval can separate the 2 allowances.

To avoid discontinuities in the allowance chronology, modify the allowance logic to ensure that the validity period is greater than or equal to 1 day.

Archive the log and trace messages.

Index	Log Message	Description	Impacts	Actions	Information
0 (WARNING)	Could not encrypt data of the configuration file located at {0}: The file cannot be read or written.	The configuration data cannot be encrypted because the configuration file could not be read or written.	Critical data will stay human readable in the file.	Fix the file permissions to allow read/write operations by the SAP CC system.
1 (FATAL)	Cannot initialize the VAT tax system because the currency book cannot be initialized	The tax system for VAT cannot be initialized properly because the currency book could not be initialized in the SAP CC system.	The tax system will not be initialized.	Troubleshoot your SAP CC system to identify a possible cause: Check the previous log messages for errors Correct the error(s)	Technical information: See `taxation module`
2 (WARNING)	Cannot calculate taxes of a transaction with tax code {0}	The SAP CC system cannot calculate taxes for the transaction during a charging operation.	The transaction amounts will not include taxes.	The transaction which could not be taxed properly can be identified by its taxStatus field which is set to `tsTaxMissedForInfo`.
3 (WARNING)	Cannot load the ISO 3166 file {0}: An I/O error occurred while reading the file.	The resource file containing the country codes was not completely loaded.	Some or all country codes and names may not appear where a list of countries is used.	Check the ISO 3166 file access and permissions.
4 (ERROR)	Cannot initialize the tax system: The parameter {0} is missing.	The tax system cannot be initialized due to a missing parameter.	The tax system will not be initialized.	Use SAP CC Admin+ to verify that the missing system parameter (`TAX_PRECISION`) is set and has a valid value.	Consult the SAP CC Application Help for more information about the tax functions and processes in SAP Convergent Charging.
5 (ERROR)	Cannot initialize the tax system: The value [{0}] is not valid for the parameter {1}, it must be an integer.	The tax system cannot be initialized due to an invalid value.	The tax system will not be initialized.	Verify that the given parameter (`TAX_PRECISION`) has a valid value.	See the SAP CC Admin+ documentation to set up a parameter.
6 (INFO)	Initializing the {0} tax system...	The taxation module selected in the configuration is being initialized.
7 (INFO)	{0} tax system initialized>	The taxation module selected in the configuration has been initialized.
8 (ERROR)	Cannot found the Java class {0} of the tax system	A required Java class cannot be found.	The tax system will not be initialized.	Check the expected Java class is present in the `CLASSPATH` of the application.
9 (ERROR)	Cannot instantiate the Java class {0} of the tax system	The application cannot instantiate the Java class for the taxation module.	The tax system will not be initialized.	The class should be instantiable The class should have nullary constructor	Technical information: See `taxation module`
10 (ERROR)	Cannot access the Java class {0} of the tax system	The application does not have access to the definition of the Java class for the taxation module.	The tax system will not be initialized.	The Java class should be accessible (in the Java class semantic).
11 (WARNING)	Cannot find a counter during the recharging process. The counter is identified by: Key:{0}, Subscriber Account ID:{1}, Holder ID:{2}, Partition ID:{3}.	An expected counter is missing during the execution of the recharging process.	The recharging operation could not be performed.	Check the counter identifiers. Check previous log messages for errors Correct the error(s)
12 (WARNING)	Partition {0} is switched to a new connection without unregistered procedure. There are {1} operation(s) on-going on the connection {2}.	A partition is being switched while there are ongoing operations on the connection.	An instance of the SAP CC Core Server system has been disconnected.	Troubleshoot your SAP CC system to identify a possible cause: Check the previous log messages for errors Correct the error(s) Restart the instance(s) of the SAP CC system
13 (WARNING)	Memory accessor {0} manages the following unknown parameters: {1}	The memory accessor manages parameters that are unknown.	The unknown parameters cannot be accessed.	This may be an implementation issue.
14 (WARNING)	Persistent accessor {0} manages the following unknown parameters: {1}	The persistent accessor manages parameters which are unknown.	The unknown parameters cannot be accessed.	This may be an implementation issue.
15 (WARNING)	Could not publish the notification because of an invalid message. The notification was: {0}.	The notification could not be published	External systems may not have received the notification.	Increase the trace severity to PATH to see the related exception Check your notification configuration
16 (WARNING)	Could not publish the notification because of a communication error. The notification was: {0}.	The notification could not be published.	External systems may not have received the notification.	Increase the trace severity to PATH to see the related exception Check your notification configuration
17 (WARNING)	Could not publish the notification because the acknowledgment time expired. The notification was: {0}.	The notification could not be published.	External systems may not have received the notification.	Check your notification configuration. Check the external systems.
18 (ERROR)	Cannot initialize the EIF connector class: The EIF configuration parameters are invalid.	The configuration parameters relating to the EIF are invalid.	The EIF Connector functions will not be initialized.	Correct the erroneous values of the EIF configuration parameters.	SAP Convergent Charging provides the Exportable item Integration Framework (EIF) feature to implement either a custom EIF Connector or a delivered connector in the SAP CC Core Server system. In an integrated SAP Solution, a specialized connector is used and configured when SAP Convergent Invoicing is the target destination. It is the CI Connector. The corresponding `Java class` is: `com.highdeal.eif.ci.CIConnector` See also: EIF_CONN_CLASS indicator in SAP CC 5.0 System Parameter Reference
19 (INFO)	EIF configuration initialized with ID [{0}]	The EIF Connector is initialized. Its functions implement the Exportable item Integration Framework (EIF) of SAP Convergent Charging.			SAP Convergent Charging provides the Exportable item Integration Framework (EIF) feature to implement either a custom EIF Connector or a delivered connector in the SAP CC Core Server system. In an integrated SAP Solution, a specialized connector is used and configured when SAP Convergent Invoicing is the target destination. It is the CI Connector. The corresponding `Java class` is: `com.highdeal.eif.ci.CIConnector` See also: EIF_CONN_CLASS indicator in SAP CC 5.0 System Parameter Reference
21 (ERROR)	Cannot initialize the EIF connector class: Cannot instantiate EIF connector with class {0}.	The application cannot instantiate the `Java class` for the EIF Connector.	The EIF Connector functions will not be initialized.	The `Java class name` can be specified by using the EIF_CONN_CLASS indicator to identify the EIF Connector function that is based on the Exportable item Integration Framework (EIF) of SAP Convergent Charging. Verify that this parameter is correctly set. Verify that the signaled `Java class` is present in the classpath of the Java Virtual Machine (JVM) that runs the application. The `Java class` must be instantiable and have a nullary constructor.	SAP Convergent Charging provides the Exportable item Integration Framework (EIF) feature to implement either a custom EIF Connector or a delivered connector in the SAP CC Core Server system. In an integrated SAP Solution, a specialized connector is used and configured when SAP Convergent Invoicing is the target destination. It is the CI Connector. The corresponding `Java class` is: `com.highdeal.eif.ci.CIConnector` See also: EIF_CONN_CLASS indicator in SAP CC 5.0 System Parameter Reference
22 (ERROR)	Cannot initialize the EIF connector class: The Java class {0} cannot be accessed.	The application does not have access to the definition of the `Java class` for the EIF Connector.	The EIF Connector functions will not be initialized.	The `Java class name` can be specified by using the EIF_CONN_CLASS indicator to identify the EIF Connector function that is based on the Exportable item Integration Framework (EIF) of SAP Convergent Charging. Verify that this parameter is correctly set. Verify that the signaled `Java class` is present in the classpath of the Java Virtual Machine (JVM) that runs the application. The `Java class` must be accessible.	SAP Convergent Charging provides the Exportable item Integration Framework (EIF) feature to implement either a custom EIF Connector or a delivered connector in the SAP CC Core Server system. In an integrated SAP Solution, a specialized connector is used and configured when SAP Convergent Invoicing is the target destination. It is the CI Connector. The corresponding `Java class` is: `com.highdeal.eif.ci.CIConnector` See also: EIF_CONN_CLASS indicator in SAP CC 5.0 System Parameter Reference
23 (WARNING)	Could not find a request handler. Unknown topic {0} for the request {1}.	The remote client may not receive the answer.		The client waits indefinitely for the answer. It may be blocked.
24 (ERROR)	Could not find a request handler. Unknown topic {0} for the request {1} and the client cannot be informed because a timeout has expired.	The remote client may not receive the answer.	The client waits indefinitely for the answer. It may be blocked.	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.
25 (ERROR)	Could not find a request handler. Unknown topic {0} for the request {1} and the client cannot be informed because of a communication error.	The remote client may not receive the answer.	The client waits indefinitely for the answer. It may be blocked.	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.
26 (WARNING)	Cannot put the session(s) in the cache because the size is bigger than the cache	The session(s) is/are bigger than the cache, it will not be cached.	Performances.	The size of the session subcaches and the session history sub caches are computed by the parameter `SESSION_MEMORY_INSTANCES` and the parameter `SESSION_MEMORY_SIZE`. Check these parameters are correctly set.
27 (INFO)	Initializing EIF configuration	The instance is initializing the EIF configuration.
34 (WARNING)	The validity period of the newly created allowance is postponed by the system for the allowance plan [{2}] with the subscriber account [{0}] and the provider contract [{1}] because an allowance cannot be renewed more than once per day.	The system postpones the validity period of the new allowance to the validity start date of the expired allowance plus 1 day (Gregorian Calendar).	If the validity period of the expired allowance is lower than 1 day, a time interval can separate the 2 allowances.	To avoid discontinuities in the allowance chronology, modify the allowance logic to ensure that the validity period is greater than or equal to 1 day. Archive the log and trace messages.