|
Measures reported by AsAbapTemSeTest
TemSe is the SAP store location for temporary sequential data. When the Temse are grows rapidly, it becomes tedious for the adminsitrators to locate what exactly caused the growth of the Temse area and which Temse object contributed to this abnormal growth? Use the AsAbapTemSeTest test to figure out the answers to such questions.
This test reports the rate at which each Temse object was created due to spool requests, background jobs and activity in the HR module. In addition, this test reports how well the data is copied to the Temse object. This way, administrators may figure out the Temse object that occupied more space and the Temse object that was created the most.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| totRate |
Indicates the rate at which this Temse object was created during the last measurement period. |
Parts/sec |
This measure is a good indicator of the rate at which the Temse data has grown. If the value of this measure is high, administrators can consider reorganizing/provisioning the TemSe data accordingly. |
| spoRate |
Indicates the rate at which this Temse object was created due to spool requests during the last measurement period. |
Parts/sec |
This measure is a good indicator of the growth in the Temse area due to spool/printing requests. |
| jobRate |
Indicates the rate at which this Temse object was created due to background jobs during the last measurement period. |
Parts/sec |
|
| hrRate |
Indicates the rate at which this Temse object was created during the last measurement period due to the activity in the HR module of the SAP ABAP instance. |
Parts/sec |
A low value is desired for this measure. |
| dataRate |
Indicates the rate at which data was copied to the Temse area of this Temse object during the last measurement period. |
MB/sec |
This measure can also be used for provisioning/reorganization of the TemSe space and also helps in detecting TemSe issues created due to causes like huge spool requests, overutilization by background jobs etc., |
|