|
Measures reported by AsAbapTrfcTest
Transactional RFC (tRFC) and qRFC are variants of the Remote Function Call that make the data transfer between different systems more reliable and more secure. For each type of tRFC call, this test reports the number of calls that were receorded, the number of calls that were executed. Using this test, administrators may figure out how many calls were in states such as CPICERR, SYSFAIL, other states etc.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| NumRecorded |
Indicates the number of tRFC calls of this type that were recorded during the last measurement period. |
Number |
A sudden/gradual increase in the value of this measure could indicate issues such as insufficient configuration of connection resources for transactions. |
| NumExeced |
Indicates the number of tRFC calls of this type that were executed during the last measurement period. |
Number |
|
| NumWithCPICERR |
Indicates the number of tRFC calls of this type with communication errors i.e., the number of tRFC calls in CPICERR state during the last measurement period. |
Number |
CPICERR error arises due to connection of communication issues with the target system or external component. CPICERR calls may be retried.
The detailed diagnosis of this measure if enabled, lists the details about these calls such as the host, process ID, timestamp, destination, function, user, retries, Tcode and error message. |
| NumWithSYSFAIL |
Indicates the number of tRFC calls of this type that were in SYSFAIL state during the last measurement period. |
Number |
SYSFAIL error arises due to error in execution of tRFC call in target system or external component.
The detailed diagnosis of this measure if enabled lists the details about these calls such as the host, process ID, timestamp, destination, function, user, retries, Tcode and error message. |
| NumMailed |
Indicates the number of tRFC calls of this type for which CMC (protocol X400) connection was initiated during the last measurement period. |
Number |
|
| NumExecedInTarget |
Indicates the total number of tRFC calls of this type that were executed in the target SAP system during the last measurement period. |
Number |
|
| NumOtherStates |
Indicates the number of tRFC calls of this type that were in intermediary states such as HOLD, WCONFIRM, SYSLOAD etc during the last measurement period. |
Number |
Tracking these calls become important when typical tRFC issues are encountered.
The detailed diagnosis of this emasure if enabled lists the details for these calls using which you can figure out any abnormal/error states. |
| longWaitingCalls |
Indicates the number of tRFC calls of this type that were stuck in any state beyond the time specified against the longwaitingCutOff parameter while configuring this test. |
Number |
tRFC calls can get stuck in certain states due to various reasons such as insufficient errors or intermediate errors, communication issues etc. Such calls need to be either manually processed or an appropriate report can be configured to process any known issues.
Use the detailed diagnosis of this measure for further analysis of such calls. |
|