Show TOC

 Request Utilities Connection Status Change Request

 

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

Technical Data

Entity Type

Service Operation

Software Component Version

IS-UT 606

Release State

deprecated

Notes on Release State

This service operation has been released as of ECC 6.0 EhP2 (IS-U 602). A new version of this service is available as of ECC 6.0 EhP5 ( (IS-U 605). SAP strongly recommends using the new service operation Request Smart Meter Utilities Connection Status Change Request Creation, instead.

Technical Name

UtilitiesConnectionStatusChangeRequestRequest_Out

Namespace

http://sap.com/xi/IS-U

Application Component

IS-U

Category

SAP A2A

Direction

outbound

Mode

asynchronous

Idempotency

not applicable

Change/Update Behavior

not applicable

P2P Communication Enabled

no

Business Context and Use

The Request Utilities Connection Status Change Request outbound service operation is related to the business object Utilities Connection Status Change Request business object that enables the exchange of messages requesting a status change for Utilities connections, for example, meters.

The process starts with the creation of a disconnection document that refers to different utilities master data objects (for example, business partner, contract account, contract, premise, device, and so on) and can contain multiple disconnection orders and reconnection orders for the master data object referenced.

When, for instance, a device has to be disconnected due to technical reasons or a customer request, a disconnection document is created in the SAP for Utilities backend system, which refers to different utilities master data objects (for example, business partner, contract account, contract, premise, device, and so on) and can contain multiple disconnection orders and reconnection orders for the master data object referenced. The disconnection order represents an order for disconnection that can either be executed automatically using AMI (Advanced Metering Infrastructure) or physically, by field service employees, which is the traditional way of disconnection.

Once the disconnection document has been created, the back-office employee creates a disconnection order, an outbound request message is sent from the SAP for Utilities backend system to a remote system (AMI) asking for the disconnection of that particular device.

This service operation can be used subsequently to request a reconnection of a disconnected device.

Features

The outbound service is an asynchronous service which is triggered from the SAP for Utilities backend system. In the signature of the service operation, the following GDT (Global Data Type) is provided with the following corresponding values:

  • Message Header - Used data type BusinessDocumentMessageHeader

  • ID - Unique identifier for a Utilities connection status change request data type: UtilitiesConnectionStatusChangeRequestID

  • Device Activity ID - Unique identifier for an item of a Utilities connection status change request data type: UtilitiesConnectionStatusChangeRquestActivityID

  • Device Activity Category Code - Coded representation of the category of a Utilities connection status change. Data type: UtilitiesConnectionStatusChangeRequestActivityCategoryCode

Error Handling

Since this is an outbound asynchronous service, Forward Error Handling is not used.

Message Types

  • UtilitiesConnectionStatusChangeRequestRequest

Prerequisites

To trigger the outbound request message, a disconnection or reconnection order should be created in the SAP for Utilities backend system.

Constraints

Typically, disconnection is triggered by the dunning of open items, which is part of the Contract Accounting (CA) module. An event is raised in the SAP for Utilities backend system to trigger the disconnection of a device. Alternatively, a disconnection can be triggered manually, for example, upon receiving an end customer request or for technical reasons such as maintenance. A reconnection is triggered by posting incoming payments that are going to be used to settle dunning items. Alternatively, reconnection can be triggered manually upon request from a utilities end customer (for example, the reconnection of a vacation home).

The disconnection outbound service performs a request to create a new disconnection/reconnection of a specific meter. The operation is sent from the SAP system to an external system (for example, an Advanced Metering System (AMS)).

In the SAP for Utilities system, the transaction EC85 ‘Create Disconnection Document’ can be used to update the status of a Utilities device. The operation then sends the current status of the device to an external system (AMS), which can remotely control smart meters when requests are received from Utilities Connection Processing.

The service is consumed in asynchronous interaction patterns and in conjunction with the SAP exchange Infrastructure (XI) acting as a service consumption intermediary. In this case, the service consumer (AMS) does not interact directly with the SAP for Utilities backend system. XI itself interacts with the backend system through XI service proxies. The interaction in the other direction works in a similar way. So XI mediates the entire message traffic between SAP for Utilities and the AMS.

Notes on SAP Implementation

B2B and A2A related information

The service operation is defined and implemented as an A2A service: the interaction between service provider (SAP for Utilities) and an external system (AMI) is completely asynchronous. The service integration model requires the following parties to be involved:

  • An SAP for Utilities system Release 2005 or higher

  • An SAP XI system Release 3.0 Release 7.0 or higher

  • A non-SAP (for example, AMI system) or an SAP application other than SAP for Utilities Release ERP2005 or higher.

Processing

To use this service operation, the Utilities (IS-U) application component should be implemented.

Enhancements

The Business Add-In (BAdI) BADI_ISU_DISCON_REQU_OUT is available for this operation. The BAdI definition is found in the enhancement spot SPOT_ISU_CONNECTION_IN. 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.

Switch Framework

The Utilities business function set must be activated.