User Assistance for Technical Operations
| Logs | Perf. Metrics | ||
| Cockpit | |||
| Param. | Admin+ | Setup Tool | |
| Monitoring | Troubleshooting | ||
| Software Maintenance | Purging and Archiving | ||
| Java | WS | ERR | Notif. |
This SAP product documentation is a complete reference of the log message IDs available in SAP Convergent Charging 5.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.
Recommendation
Use your favorite search engine to find the information that relates to a log entry of SAP CC quickly. Simply type the log message ID in your web browser.
Important Notes
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 and Definition | 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 |
|
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 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. |
The log messages relate to the following areas. Choose your area to view its log message IDs.
| Prefix | Definition |
|---|---|
| com.sap.SCC.chargingplan |
Log messages from the SAP CC charging components |
| 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.infra |
Log messages from the SAP CC Core Server technical infrastructure |
This section provides a starting point for troubleshooting investigations and problem solving when the symptoms are signaled by a log entry of SAP Convergent Charging. SAP CC is part of a multitechnology system landscape with distributed systems. The root cause may be difficult to identify.
When working with a specific error log message, you can use this documentation reference to empower your investigations. You quickly navigate to the relevant troubleshooting page by selecting the appropriate prefix of your log message. The page contains some useful details.
In SAP Convergent Charging, each log message has a unique identifier in order to facilitate the troubleshooting work. Most of the log messages recorded by your system include detailed runtime information such as identifiers and dates/times.
| Core Server System | Core Tool (User Interface) | Other Custom Client Application (or System) |
|---|---|---|
This technical operation is triggered by:
To provide a complete solution, the objective is to identify:
To troubleshoot a problem signaled by a log entry:
log message IDYou can get the log messages generated by the systems of SAP Convergent Charging by using the following procedures:
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.
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.
To view the logs (and traces) in your SAP Management Console:
For more information about the real-time monitoring of SAP Convergent Charging and its concepts, see the SAP CC 5.0 Operations Guide.
Recommendation
Based on log automated analysis, the log monitoring and alerting functions provided in SAP Solution Manager 7.1 SP13 identify potential problems in your SAP system landscape.
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.
Recommendation
For offline consultation, you can download this document on SAP Help Portal.
Consult the documentation set of SAP CC for more information.
For more information about working with SAP Convergent Charging, see these SAP product documents:
| User Assistance | About |
|---|---|
| SAP CC 5.0 Operations Guide | |
| SAP CC 5.0 Configuration Guide | Configuration and Implementation Information |
| SAP CC 5.0 Installation Guide | Installation or Upgrade Information |
| SAP CC 5.0 Application Help | Logging and tracing functions |
For more information, see the product documentation set of SAP Convergent Charging 5.0 in SAP Help Portal: