Show TOC

 Request Utilities Device Smart Meter Register Change

 

To request the change of smart meter utilities device register.

Technical Data

Entity Type

Service Operation

Software Component Version

IS-UT 605

Release State

released

Technical Name

UtilitiesDeviceERPSmartMeterRegisterChangeRequest_Out

Namespace

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

Application Component

IS-U

Category

SAP A2A

Direction

outbound

Mode

asynchronous

Idempotency

not applicable

Change/Update Behavior

not applicable

P2P Communication Enabled

yes

Business Context and Use

The Request Utilities Device Smart Meter Register Change outbound service operation is used for changing measurement task assignment data. Once measurement task assignments within a device have been changed in the IS-U back-end system, an outbound request message is sent to request the changes of this single device in the AMI system.

Features

The following values have to be provided:

  • UtilitiesDeviceID

  • StartDate

  • EndDate

  • UtilitiesMeasurementTaskID

  • StartDate of the node Specifications

  • EndDate of the node Specifications

  • MeasureUnitCode

  • DecimalValuePrecision

  • UtilitiesAdvancedMeteringSystemID

Error Handling

Typical errors are:

General processing and/or mapping errors: UtilitiesDeviceID is initial; Message UUID not provided.

Message Types

  • Utilities Device ERP Smart Meter Register Change Request

Prerequisites

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

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. It is necessary that the customer runs the IS-U application component in order to use it.

Enhancements

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

You can use this BAdI to create a customer-specific logic for the 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, or customer.