Show TOC

 Notify of Smart Meter Utilities Connection Status Change Request as Bulk

 

To send a notification about the utilities connection status change request as bulk.

Technical Data

Entity Type

Service Operation

Software Component Version

IS-UT 605

Release State

Released

Technical Name

SmartMeterUtilitiesConnectionStatusChangeRequestERPBulkNotification_Out

Namespace

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

Application Component

IS-U

Category

SAP A2A

Direction

outbound

Mode

asynchronous

Idempotency

not applicable

Change/Update Behavior

not applicable

P2P Communication Enabled

true

Business Context and Use

The Utilities Connection Status Change Request business object is used to manage disconnection and reconnection activities for an advanced meter in the utilities industry. In the advanced metering infrastructure (AMI), the services connected to the business object are used to inform a meter data unification and synchronization (MDUS) system about disconnection, reconnection, or cancellation of such disconnection and reconnection activities.

The SmartMeterUtilitiesConnectionStatusChangeRequestERPBulkNotification_Out outbound service operation is used to send a notification about disconnection or reconnection as bulk.

The possible use cases are the following:

  • Installation of a device at a disconnected installation

    When you try to install a new device into an installation that contains disconnected devices, a popup is displayed, asking you to decide whether the device that is being installed at a disconnected installation should also be disconnected. If you choose yes, a disconnection notification service is sent to MDUS.

  • Replacement of a device at a disconnected installation

    When you try to replace a device in an installation that contains disconnected devices, a disconnected device is automatically replaced with a disconnected device and a reconnection notification service is sent to MDUS.

  • Removal of a device from a disconnected installation

    In this case, a reconnection notification service is sent to MDUS. The status in the disconnection document is set to removed and disconnected.

Features

The following graphic illustrates both the interface, the fields and cardinality of this service operation. You can use the Utilities data type catalog at http://service.sap.com/~sapidb/011000358700001049282012EInformation published on SAP site (Start of the navigation path service.sap.com/utilities Next navigation step SAP for Utilities Next navigation step SAP for Utilities - Product Information Next navigation step IS-U/CCS Next navigation step General Next navigation step Cookbook&Guidelines Next navigation step Utilities Data Type Catalog End of the navigation path) to search for information about specific fields.

The UtilitiesConnectionStatusChangeRequest should provide the following values:

  • UtilitiesConnectionStatusChangeRequestID

  • UtilitiesConnectionStatusChangeRequestCategoryCode

    The following category codes are available:

    • 1 = Disconnection request for the disconnection of a utilities device

    • 2 = Reconnection request for the reconnection of a utilities device

  • UtilitiesServiceDisconnectionReasonCode

    The following disconnection reason codes are available:

    • 00 = Any reason not matching the reasons in the disconnection reason code list

    • 01 = Service disconnection triggered by dunning with level disconnection

    • 02 = Service disconnection because a house or an apartment is unoccupied

    • 03 = Service disconnection upon customer request

    • 04 = Service disconnection because of technical reasons, e.g. prior to maintenance

    • 05 = Service disconnection because the reason for service activation became obsolete

  • GLOBAL DateTime (date and time at which the service technician disconnects or reconnects an advanced meter)

  • UtilitiesDeviceID

  • UtilitiesAdvancedMeteringSystemID

In the SAP system, the sending of notifications from SAP for Utilities to the external system is triggered using the transactions Create / Change Disconnection Document (EC85 and EC86).

Error Handling

Typical general processing and/or mapping errors are:

  • UtilitiesDeviceID not provided

  • Message UUID not provided

For more information about monitoring your process integration, see the SAP Process Integration (PI) Handbook.

Integration

This service operation belongs to the Notify Utilities Connection Status Change Request Out service interface.

Notes on SAP Implementation
Switch Framework

The Utilities business function set must be activated.

Configuration

This operation is suitable for the Utilities Industry Solutions sector. However, it is only available to customers who are running the IS-U application component.

Enhancements

The Business Add-In (BAdI) ISU_SE_CNSTSRQSMBLKNOO_ASYN 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 inbound and outbound mapping of application data. The BAdI can be implemented several times. The implementations are sorted according to the field layer of a BAdI implementation, for example, SAP standard, partner, customer, and so on.