Calling the Trace Monitor 
Use
You call the Middleware Trace Monitor to track program flows, record events from this and provide information for evaluation.
Prerequisites
To use the Middleware Trace Monitor you have to make the relevant settings.
Procedure
...
1. To call up the Middleware Trace Monitor choose Architecture and Technology ® Middleware ® Monitoring ® Message Flow ® Display Middleware Trace. The Middleware Trace screen appears.
2. Enter the following values, if required, in the Middleware Trace screen.
Optional Entries for the Middleware Trace Monitor:
|
Field |
Value |
|
R/3 client |
R/3 client |
|
Trace Environment |
Internal trace environment |
|
Trace Object ID |
Identification of trace object |
|
Component |
Middleware component |
|
GUID1 |
Globally Unique Identifier of trace object |
|
GUID2 |
GUID of an alternative trace object |
|
User name |
Name of your SAP user |
|
Time from/to |
Start/end times |
|
Date from/to |
Start/end dates |
3. Choose Execute.
A table with following information is displayed:
|
Column |
Entry |
|
Exception |
Note on errors (red) or warnings (yellow) |
|
Date |
Date on which the entry was written |
|
Time |
Time at which the entry was written |
|
Trace Object ID |
Identification of trace object |
|
Trace Environment |
Internal trace environment |
|
Trace Component |
Middleware component |
|
Trace Subcomponent |
Sub-component, for example, function module |
|
Trace Program Name |
ABAP program name |
|
User name |
Name of SAP user |
4. Select an entry in the displayed table and choose Choose detail to display further information.
The following information is also displayed:
|
Column |
Entry |
|
Timestamp UTC |
UTC time stamp |
|
Text Field |
Text (maximum 250 characters) of trace message |
|
Hex GUID between transactions |
GUID to differentiate between entries with the same time stamp from different application servers. |
|
Trace Line Number |
ABAP program line |
5. Double-click on an entry in the table to see more details.
Following information will be displayed (in alphabetical order):
|
Column |
Entry |
|
Additional info |
Column that specifies whether the additional trace information is to be saved If it should, the column contains an X. By double-clicking on the line, you activate the function module in the Trace Format column, which reads this data. |
|
Date |
Date on which the entry was written |
|
Hex GUID between transactions |
GUID to differentiate between entries with the same time stamp from different application servers. |
|
Timestamp UTC |
UTC time stamp |
|
Trace Component |
Middleware component |
|
Trace counter |
Counter for entries with the same time stamp from the same application server |
|
Trace Environment |
Internal trace environment |
|
Trace Format |
Function module to access more saved trace details |
|
Trace GUID |
Globally Unique Identifier of trace object |
|
Trace GUID |
Globally Unique Identifier of an alternative trace object |
|
Trace Level |
Required trace level |
|
Trace Line Number |
ABAP program line |
|
Trace Program Name |
ABAP program name |
|
Trace Subcomponent |
Sub-component, for example, function module |
|
Text Field |
Text (maximum 250 characters) of trace message |
|
Time |
Time at which the entry was written |
|
Trace Object ID |
Identification of trace object |
|
User name |
Name of SAP user |
You can change this alphabetical display of all the available columns in any way you like using the function Change layout.