Monitoring Communication 
Monitoring Communication
The system provides functions for monitoring communication. These functions enable you to check whether the communication was successful or whether errors occurred. If an error did occur, the type of error is indicated.
You can monitor communication both in the sending system and in the receiving system. In ALE Administration, choose Monitoring
® Display IDoc list.In the Sending System:
Execute the function, and select the IDocs of the logical message type MATMAS which you created today.
A list of IDocs grouped by status (St. column) is displayed:
Status |
Description of Status |
03, 12, 38 |
IDoc successfully transferred |
02, 04, 05, 25 26, 29 |
Processing error |
30 |
Waiting status (still processing...) |
>=50 |
Inbound IDoc (not relevant in this context) |
Other |
Not relevant in this context |
To display a list of IDocs with a particular status, double-click on a line. For detailed information on one of these IDocs, double-click on it. If an error occurs, select the pushbutton Incorrect segments to display information about the cause of the error.
In the Receiving System
Execute the function, and select the IDocs of the logical message type MATMAS which you created today.
A list of IDocs grouped by status (St. column) is displayed:
Status |
Description of Status |
53 |
IDoc successfully updated by application |
64 |
Waiting status (still processing...) |
<50 |
Outbound IDoc (not relevant in this context) |
51, 56, 60, 61, 63, 65 |
Inbound error |
Other |
Not relevant in this context |
You can look at the details here the same way as you can in the sending system.
Error Handling
If an error has occurred, use the monitoring function to resolve it. The cause of the error is likely to be a value in your material that the receiving system does not know and therefore cannot process it. Try to eliminate the cause of the error and send your material again.
If your IDoc in the sending system was successfully transferred (status 03) but does not appear in the receiving system, a technical communication error is the likely cause. You can check this in the sending system by choosing ALE
® Administration ® Communication ® Transactional RFC. If an error occurs consult your system administrator.