Show TOC

 Request Smart Meter Utilities Connection Status Change Request Creation


To request the creation of a smart meter utilities connection status change request.

Technical Data

Entity Type

Service Operation

Software Component Version

IS-UT 606

Release State


Technical Name



Application Component









not applicable

Change/Update Behavior

not applicable

P2P Communication Enabled


Business Context and Use

This outbound service operation is used to handle disconnection and reconnection processes in the AMI (Advanced Meter Infrastructure) environment. This service operation allows communication between SAP for Utilities and a meter data unification and synchronization system (MDUS) regarding a disconnection or reconnection request.

The key reasons for disconnection are:

  • Lack of customer payment (credit or collection cause)

  • Confirmed customer request (explicit request)

The key reasons for reconnection are:

  • Customer completes the payment (dunning lock removed: credit or collection cause)

  • Confirmed customer request (explicit request)

Within this process, a disconnection or reconnection is triggered by the manual processing of the disconnection or reconnection request for a specific AMI device (smart meter) using the function ‘Trigger Immediate Disconnection or Reconnection’ or ‘Trigger Remote Disconnection or Reconnection’ in transaction 'Change Disconnection Document’ (transaction EC86) or by using the mass activity ‘Send Disconnection/Reconnection Orders’ via transaction EAMIDISCSEND01. A message is sent from SAP for Utilities to the MDUS. Within the MDUS, a corresponding disconnection or reconnection request is created and is processed. As a result of the creation of the request, or in the case of error, a confirmation is sent from the MDUS to SAP for Utilities.

You can trigger the disconnection or reconnection request (Trigger  Immediate Disconnection/Reconnection) in one of two ways:

  • Option 1: Using the dialog functionality 'Change Disconnection Document' (transaction EC86) in the ERP System

  • Option 2: From the SAP CRM system

Once this outbound service operation is triggered successfully, the confirmation status for the disconnection or reconnection is:

  • Remote Disconnection Requested

  • Remote Reconnection Requested

The previous status of the disconnection or reconnection order must be:

  • Remote Disconnection to be Requested

  • Remote Reconnection to be Requested

These order statuses are necessary for the successful execution of this outbound service operation.


The outbound service Request Smart Meter Utilities Connection Status Change Request Creation requests the disconnection or reconnection of a specific smart meter. The request is sent from the SAP system to an external system (Meter Data Unification and Synchronization).

This service operation is used by SAP for Utilities, transaction EC85 ‘Create Disconnection Document’, and is used  to update the status of a utilities smart meter. The operation can only be triggered if the device in question is an AMI (Advanced Metering Infrastructure) device. To trigger the operation, the user must choose the ‘Trigger Remote Disconnection" or "Trigger Remote Reconnection" button. The operation then sends the current status of the AMI device to the MDUS external system.

The Request Smart Meter Utilities Connection Status Change Request Creation operation requires the ID of the Utilities Connection Status Change Request message combined with the device that the service wishes to update.

Message Types

  • Smart Meter Utilities Connection Status Change Request ERP Create Request

Notes on SAP Implementation

To use this service operation, the application component Utilities (IS-U) should be implemented and the Utilities business function set must be activated.


The ISU_SE_CONNSTSREQSMCRTRCO_ASYN Business Add-In (BAdI) is available for this operation. This BAdI definition is found in the enhancement spot: ISU_SPOT_SE_CONNSTSREQ.

You can use this BAdI to create a customer-specific logic for the outbound mapping of application data. The implementations are sorted according to the field layer of a BAdI implementation, for example, SAP standard, partner, or customer.