You use this activity to define and configure attributes of the Transaction Log Report (see Transaction Log Report).
Caution
The transaction logging impacts performance of SAP ME. Turn off the transaction logging when complete.
The following table describes fields requiring explanation:
Field |
Description |
---|---|
Log Transaction |
Enables logging for the category (deselected by default). |
Details |
Displays the Transaction Log Maintenance Details screen |
SQL Log Threshold |
The first five SQL queries executed within the transaction that exceed the threshold value (milliseconds) will be logged with the transaction and made available in the Transaction Log Report. |
Field |
Description |
---|---|
Auto Disable on Logging Error |
If selected, the system automatically disables transaction logging when an error is detected. Note Only errors triggered by transaction log processing itself are considered with this setting. Errors that occur during SAP ME business processing are not considered as transaction log processing errors and are logged along with transactions that complete successfully. End of the note. |
Log Payload |
If selected, the payload of the transaction is recorded in the log. The payload contains the content of the client request, such as the XML message in the case of Data Exchange and Production XML, or a human readable form of a Web service parameter. |
Maximum Payload Size |
If Log Payload is selected, the size of the payload is limited to the specified number of characters. Any content that exceeds the maximum size will be truncated. |
Log Result |
If selected, the transaction result (response) is recorded in the log. |
Maximum Result Size |
If Log Result is selected, the size of the result is limited to the specified number of characters. Any content that exceeds the maximum size will be truncated. |
Query Elapsed Time Offset |
The offset (in milliseconds) that when added to the base threshold value indicates the minimum time an SQL query must execute before it is logged with the transaction. The purpose of this setting is to correlate long transaction times with long running SQL queries. The number of queries that may be logged for a single transaction is limited to five. This limitation helps guard against excessive query logging if the system becomes unduly stressed due to heavy load conditions or when system resources are drastically limited. |
Log Cleanup Aging Period |
The number of days that a log message may remain in the database before it is deleted. |
In Activity Maintenance, retrieve the TRANS_LOG_CONFIG activity.
On the Activity Groups tab page, move System Configuration to the Assigned Activity Groups list.
Save the record.
Clear the record.
Retrieve the TRANS_LOG_REPORT activity.
On the Activity Groups tab page, move System Reports to the Assigned Activity Groups list.
Save the record.
In User Group Maintenance, retrieve the ADMINISTRATORS group (we recommend that only users with administrative privileges are granted access).
On the Permissions tab page, find the Transaction Log Maintenance and Transaction Log Report activities and enable Execute permissions for them (we recommend that only users with administrative privileges are granted access).
Save the record.
Log off and log on to your site. You should now see Transaction Log Report under the System Reports group and Transaction Log Maintenance under the System Configuration group.