Warnings of com.sap.SCC.core_client

Warnings

The SAP CC system or a subcomponent can recover from anomaly, and fulfill the desired task, but needs later follow-up activity by a system administrator or an SAP CC SAP CC application administrator to avoid erroneous terminations in the future.

Resolution Plan and Troubleshooting

Preventive Actions

The administrators plan a follow-up activity to take into account the anomaly and to determine the appropriate timeframe to perform preventive actions.

Recommendation

In a production system landscape, contact your SAP Support Team at support.sap.com/incident.

Warning Messages

The administrators of the SAP CC systems may perform troubleshooting operations relating to the following warning log messages:

Warning Log Message Possible Impacts
Cannot calculate taxes of a transaction with tax code {0}

The transaction amounts will not include taxes.

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}.

The recharging operation could not be performed.

Cannot load the ISO 3166 file {0}: An I/O error occurred while reading the file.

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

Cannot put the session(s) in the cache because the size is bigger than the cache

Performances.

Could not encrypt data of the configuration file located at {0}: The file cannot be read or written.

Critical data will stay human readable in the file.

Could not find a request handler. Unknown topic {0} for the request {1}.
Could not publish the notification because of a communication error. The notification was: {0}.

External systems may not have received the notification.

Could not publish the notification because of an invalid message. The notification was: {0}.

External systems may not have received the notification.

Could not publish the notification because the acknowledgment time expired. The notification was: {0}.

External systems may not have received the notification.

Memory accessor {0} manages the following unknown parameters: {1}

The unknown parameters cannot be accessed.

Partition {0} is switched to a new connection without unregistered procedure. There are {1} operation(s) on-going on the connection {2}.

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

Persistent accessor {0} manages the following unknown parameters: {1}

The unknown parameters cannot be accessed.

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.

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

See Also