|
Measures reported by AsAbapUpdReqTest
An update request, or update record, describes the data changes determined in an SAP LUW. These changes should be made completely, or not all (this means, in a database LUW). This refers only to V1 updates. V2 updates are triggered once the V1 update is complete, and are processed in a separate database LUW.
An update request is identified by its update key.
When the dialog transaction ends (COMMIT WORK), and the update process is called, an update header is created. Then the update record is created. The update data is contained in the update modules that was created using the ABAP command CALL FUNCTION '…' IN UPDATE TASK. The function module type is defined in the transaction for maintaining function modules (transaction SE37). Whenever there are too many data changes in the target environment, then it indicates that so many update requests will be created to effect those changes. With an increase in the volume of data changes, administrators may need to check the volume of the update requests too. The time taken for an update request to complete processing depends on the changes that were made to the target environment. Therefore, when too many update requests are created in the environment, administrators need to identify the update requests that are taking too long to process, update requests that are stopped and are stuck for a longer duration. This is exactly where the AsAbapUpdReqTest test helps!
Using this test, you can figure out how many update requests were created and how many were actually stopped/stuck in the target environment. In addition, administrators can figure out the update requests that encountered errors.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| noOfUpdates |
Indicates the number of update requests that were created during the last measurement period. |
Requests |
|
| updateRate |
Indicates the rate at which update requests were created during the last measurement period. |
Requests/sec |
This measure is a good indicator of the load on the system. |
| stoppedUpdates |
Indicates the total number of update requests that were stopped since the start of the server. |
Requests |
The update requests may be stopped due to various reasons such as database issues, longer wait period to connect to the server, the update server being inactive for a longer time etc. |
| stoppedUpdateRate |
Indicates the rate at which update requests were stopped during the last measurement period. |
Percent |
|
| errorUpdates |
Indicates the total number of errors encountered in the update request since the start of the server. |
Number |
Ideally, the value of this measure should be zero. |
| errorUpdateRate |
Indicates the rate at which errors were encountered in the update requests during the last measurement period. |
Requests/sec |
An increasing trend for this measure indicates an error with the update system. If so, update system can be deactivated to prevent issues relating to the abnormally terminated updates and reactivated once the issue has been resolved. |
| stuckUpdates |
Indicates the total number of update requests that were stuck while processing since the start of the server. |
Requests |
Stuck updates are hanging updates that have not been marked as error updates. Stuck updates may need to be manually processed depending upon their actual status. |
| stuckUpdatesRate |
Indicates the rate at which update requests were stuck while processing during the last measurement period. |
Requests/sec |
|
| newStoppedUpdates |
Indicates the number of update requests that were stopped during the last measurement period. |
Number |
|
| newErrorUpdates |
Indicates the number of errors encountered in the update requests during the last measurement period. |
Number |
Ideally, the value of this measure should be zero. |
| newStuckUpdates |
Indicates the number of updates that were stuck while processing during the last measurement period. |
Number |
|
|