Troubleshooting Tools

Note Note

This section is part of the technical documentation of the ABAP statistics data reporting scenario. This data is used in Interactive Reporting, Root Cause Analysis and SAP EarlyWatch Alert.

End of the note.

There are various tools available to check the data provision and processing for the ABAP statistics data reporting scenario.

Problem Message Display Report

You can display the problem messages from the following areas of ABAP statistics data reporting:

Data Loader (writing the data into BW data store objects)
Further processing in BW (write DSO data into InfoCubes)

Use the report SMBI_PN_SHOW_MESSAGES in transaction se38.

If problems occur in BW-based ABAP statistics data reporting, this report is the first check to perform.

Note Note

These messages are also in the self-check messages which are shown in the Self-Monitoring of BW-Based Reporting.

End of the note.

It checks ABAP statistics data saving and processing in BW steps in the software component ST_BCO (BI Content for SAP Solution Manager). If your BW is in its own system, call SMBI_PN_SHOW_MESSAGES in that system.

You can restrict the problem messages to be displayed, to a date range (DAT_FROM to DAT_TO). A good initial value is the last 30 days.

The problem messages in the specified date range are displayed, with the following data:

Column Title	Meaning
PROBLEM_ID	Technical ID of problem message. If you cannot resolve the problem from its description, search for notes with this ID, to get SAP troubleshooting information. If there is no appropriate note, report an incident in the component SV-SMG-MON-REP.
DESCRIPTION	Short problem description
PROGRAM_OCCUR	Methods, programs, function modules or form routines in which the problem occurred.
TIME_LAST_OCCUR	Timestamp of last occurrence of problem
COUNT_TOTAL	Number of times the problem has occurred
COUNT_24H COUNT_7D COUNT_30D	Number of times the problem has occurred in the last 24 hours (COUNT_24H), last 7 days (COUNT_7D) and the last 30 days (COUNT_30D)
COUNT_CONF	How often you have already confirmed the problem in the BW-Based Reporting Self-Monitoring

If no problem messages are listed, BW-based reporting based on ABAP statistics data is usually running well. If problems occur nevertheless, it is due to the provision of statistics data by EFWK (see Getting ABAP Statistics Data for Reporting Applications).

Tracing BW-Based Reporting

SAP Solution Manager BW-based reporting has a trace which you can analyze extractors and data loaders. This section describes how to use this trace.

Note Note

Writing traces requires authorization for the RFC call of the function group E2EREP_TOOLS (authorization object S_RRC, activity 16).

End of the note.

To start or end trace recording, proceed as follows:

Depending on the software component to be traced, start the following program in transaction se38:

Program

Software Component

Run in System

E2EREP_ACTIVATE_TRACE

ST

SAP Solution Manager

E2EREP_ACTIVATE_TRACE_BI_CONT

ST_BCO

Associated BW System

Program	Software Component	Run in System
E2EREP_ACTIVATE_TRACE	ST	SAP Solution Manager
E2EREP_ACTIVATE_TRACE_BI_CONT	ST_BCO	Associated BW System

Enter the trace ID for which the trace is to be activated. This specifies the extractor which is to write the trace information. For the analysis of ABAP statistics data, there are the following trace IDs:

Trace ID	Meaning of extractor	Comments
E2E_LUW_ME_CORE_SSR	Main extractor for getting ABAP statistics data.	You can restrict the trace to a managed system, by entering the system ID in the Filter field. You can use regular expressions.
ASR_READ	Statistics data extractor
GENERIC_DATALOADER	Generic data loader (used for ABAP statistics data, etc.)	To only analyze writing of ABAP statistics data, in the Filter field; enter `ASR`.

Set the trace status by choosing Activate, Deactivate or Reorganize.

Note
You can check the current status for the trace ID with Check Trace Status.

End of the note.
Save your settings.

Note Note

The traces are saved in the table CPH_TRACE. Two days after a trace is activated, it is automatically deactivated, and its status set to Reorganize. Trace entries which are older than 30 days are deleted.

You can also reorganize the table manually, by choosing Reorganize in the group box Reorganize Now. All entrie for the trace are deleted from the table.

End of the note.

To evaluate an existing trace, proceed as follows:

Display the contents of the table CPH_TRACE in transaction se16.
START_DATE and START_TIME show the same date and time for all records of the trace of a program (e.g. an extractor). The first entry for a run contains the following entry in the MESSAGE column
-----------> Start of trace: < Trace ID>

The ID2 column contains the trace ID.
Sort the table by ascending key value, to show the trace chronologically.

Other Tools

Also use the following tools to search for errors:

Application log (transaction slg1)

Use the following objects to display the application log:

Object	Meaning	Run in System
ASR_EXTRACT	Extract the data in the Extractor Framework (EFWK) from the managed system into the SAP Solution Manager system	SAP Solution Manager
ASR_DATALOAD	Data processing in the generic data loader	Associated BW System

Extractor Framework
In the Extractor Framework management, you can display the run time, status and log entries of main extractors and primary and secondary extractors.

Call the Extractor Framework management in the SAP Solution Manager Administration work center, with Infrastructure Framework Extractor Framework .
Job Selection (transaction sm37)
Check the Job Log for the job CCMS_ASR_AGGR_DATA_UPDATE:
ABAP Run-Time Errors (transaction st22)