Log Message Reference

Target Audience

• IT System administrator (SAP CC systems)
• Application administrator (SAP CC)
• Operations team (during the production operations phase)
• Technology consultant (during the implementation phase)
• Support specialist

Getting Started

This SAP product documentation is a complete reference of the log message IDs available in SAP Convergent Charging 4.0. It provides you with the necessary resolution plans (troubleshooting investigations, immediate correction actions, or preventive actions) for each log message ID.

This user assistance is intended for troubleshooting problems and planning the necessary follow-up activities to administer the SAP CC systems.

Troubleshooting and Resolution Plans

When monitoring the logs of an SAP CC system or system landscape, you get a log message associated to a unique identifier. You use this ID to plan further actions depending on the severity level of the log:

Log Severity	Action Plan
Fatal error level: The SAP CC system or a subcomponent cannot recover from error, and the severe situation causes its fatal termination. The SAP CC system is not usable anymore and cannot be started without corrective actions by experts (administrators, support specialists).	Immediate correction actions: After a fatal error, the administrators do an immediate follow-up activity to analyze the logs and traces to determine further investigations before being able to identify the correction actions to be performed. Example See the fatal errors in the SAP CC Core Server system.
Error level: The SAP CC system or a subcomponent can recover from error, but cannot complete the desired task due to the error. The SAP CC system is still usable, but corrective actions need to be performed by administrators.	Immediate correction actions: After an error, the administrators do an immediate follow-up activity to determine the resolution and the corrective actions needed to be performed to avoid another erroneous termination in the future.
Warning level: 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.	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. You can start a root cause analysis.

Prefixes

The log messages relate to the following areas. Choose your area to view its log message IDs.

Prefix	Definition
com.sap.SCC.core_client	Log messages from the SAP CC Core client modules, including public Java APIs and XML APIs
com.sap.SCC.core_server	Log messages from the instances of the SAP CC Core Server system
com.sap.SCC.ct	Log messages from the SAP CC Communications Taxing Server system
com.sap.SCC.infra	Log messages from the SAP CC Core Server technical infrastructure

Tasks

This section provides a starting point for troubleshooting investigations and problem solving when the symptoms are signaled by a log entry. SAP CC is part of a multitechnology system landscape with distributed systems. The root cause may be difficult to identify.

Viewing the Information That Relates to a Log Message

When working with an error log message, you navigate to the relevant troubleshooting page by selecting the appropriate prefix of this log message.

Troubleshooting Problems With Logs

This technical operation is triggered by:

• an alert raised by system monitoring
• a log message discovered during log inspection

To provide a complete solution, the objective is to identify:

• the causes in a complex environment
• immediate corrective actions to restore service operations as quickly as possible with minimal disruption to end customers (digital service consumers) by isolating the area of concern

To troubleshoot a problem signaled by a log entry:

• View the log entry
• Find the corresponding troubleshooting information:
  • in your favorite search engine, search for the unique log message ID
  • access to this document and use the appropriate prefix of the log message
• Perform the recommended troubleshooting investigations
• Plan later actions

Related Tasks

Getting and Viewing Logs of the SAP CC Systems

You can get the log messages generated by the systems of SAP Convergent Charging by using the following procedures:

• To view all the logs and traces in SAP Solution Manager
• To view all the logs and traces in SAP Management Console
• To view the SAP CC system logs and traces in Admin+
• To view the SAP CC system logs and traces in BART+

By default, the file extensions are *.log and *.trc. The logs and traces are not mixed. These settings may be customized in your running SAP CC system.

Viewing the Logs (and Traces) in SAP Solution Manager

In the Root Cause Analysis Work Center of SAP Solution Manager, use the System Analysis report to display the logs and traces of SAP Convergent Charging.

• Starting a system analysis: choose the System Analysis report in the navigation area.
• Select the system cluster that corresponds to your SAP CC platform.
• Click Log Viewer. A window displays all the host machines available in this cluster, the status of the Diagnostic agents, and the declared log stores.
• Select the host and the log (or trace) files to analyze.

Viewing the Logs (and Traces) in SAP Management Console (SAP MC, SAP MMC)

To view the logs (and traces) in your SAP Management Console:

• Select the SAP CC system by its SID (SAP System Identifier) that is unique in the SAP system landscape
• Select the host you want to work with; Right-click and choose the All Tasks menu.
• Then select the View Developer Traces... submenu
• Select the log (or trace) files to analyze.

About Monitoring

For more information about the real-time monitoring of SAP Convergent Charging and its concepts, see the SAP CC Operations Guide.

This Documentation

This product documentation provides you with user assistance about the SAP Convergent Charging software product when operating the SAP CC systems in your SAP system landscape.

Consult the documentation set of SAP CC for more information.

Related Documentation

For more information about working with SAP Convergent Charging, see these SAP product documents:

User Assistance	About
SAP CC Operations Guide	Managing SAP CC Monitoring Troubleshooting
SAP CC Configuration Guide	Configuration and Deployment Information
SAP CC Installation Guide	Installation and Upgrade Information
SAP CC Library (Application Help)	Logging and tracing functions

More Documentation

For more information, see the product documentation of SAP Convergent Charging 4.0 in SAP Help Portal:

Primary Help	Secondary Help
SAP CC Admin+ SAP CC BART+ SAP CC BART Setup Tool SAP CC BART Tool SAP CC CAT Tool SAP CC Config Tool SAP CC Core Tool SAP CC HTTP Client SAP CC Message Client SAP CC Import/Export Connector (IEC) SAP CC Setup Tool SAP CC Simulation Tool	SAP CC Library (Application Help) Features Architecture Master Data Customer Master Data Processes and Functions SAP CC Database References SAP CC System Parameter Reference SAP CC Log Message Reference
Guides	Extensibilty
SAP CC Master Guide Integration Guides With SAP hybris Billing SAP CC Sizing Guide and SAP CC Sizing Guidelines SAP CC Security Guide SAP CC Installation Guide SAP CC Configuration Guide SAP CC Operations Guide SAP CC Upgrade Guide SAP CC Transition Guide (Offline Charging in SAP CI)	SAP CC Web Services Documentation SAP CC Error Code Reference SAP CC Java and XML API References SAP CC Core API Reference (Java and XML) SAP CC BART API Reference (Java and XML) SAP CC IEC Java API Reference SAP CC Notification Reference