Monitoring of AMI Communication

 

You can monitor data that is exchanged between SAP Utilities and the MDUS system using enterprise services.

You can use the Monitoring of AMI Communication transaction to display the formatted data from the Log for Service Communication in AMI Environment and Messages for Service Communication tables and confirm incorrect entries.

You can access the transaction in the Utilities Industry menu under Start of the navigation path Advanced Metering Infrastructure Next navigation step Utilities Next navigation step Monitoring of AMI Communication End of the navigation path.

Authorizations

You can use the authorization object for monitoring AMI communication (E_AMI_MON) to limit the use of the transaction to specific users.

Selection Criteria

If you do not make an entry in the field Object Type, the system displays log entries for all object types. Alternatively, you can restrict the display of log entries to a specific object type. You define the additional selection criteria that the system is to read for a corresponding object key in Customizing for SAP Utilities under Start of the navigation path Advanced Metering Infrastructure Next navigation step Utilities Next navigation step Define Selection Criteria for Monitoring End of the navigation path

If he object type Point of Delivery is involved, the system can determine the external point of delivery ID for an internal object key and display this in the hitlist for AMI monitoring.

Note Note

To display the object key description, you must use the Business Add-In (BAdI) ISU_AMI_LOG_MONITORING_DISP2 (Display Object Key Description) with the method DETERMINE_OBJKEY_DESCRIPTION (Determine Object Key Description) and copy the column Object Key Description to the hits displayed using the function Change Layout. This BAdI has a default implementation and is executed automatically for the object type Point of Delivery. You can record your own implementations for other object types.

End of the note.

If you select a bulk type during the selection, the system displays the bulk header message and the corresponding status in monitoring. You can navigate to the individual messages from the field Bulk Header. The system also displays the status of the individual messages: Individual messages that do not contain errors are listed as Action Completed Successfully. Action with Errors describes messages for which an error has occurred.

If an individual message has the status Action with Errors, the system also assigns the Action with Errors status to the bulk header message. If every individual message has the status Action Completed Successfully, but an error has occurred in the bulk header message, the system displays the status Action with Errors for the bulk header message.

Archiving

You can archive both service logging and the messages for service-based AMI communication using the archiving object IS-U Archiving: Service Communication (ISU_AMILOG).

For more information, see Archiving Service Communication.