Show TOC

 Request Utilities Device Smart Meter Creation

 

To request the creation of smart meter utilities device.

Technical Data

Entity Type

Service Operation

Software Component Version

IS-UT 606

Release State

released

Technical Name

UtilitiesDeviceERPSmartMeterCreateRequest_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

This outbound service operation is used for replicating device information as a mass request. In the IS-U backend, more than one device can be created. The creation process triggers an outbound processing of bulk processing, which will be sent to request the creation of these devices on the AMI system.

Features

In the bulk request message, each single object (Utilities Device) should provide the following values:

  • UtilitiesDeviceID

  • StartDate

  • EndDate

  • SerialID

  • MaterialID

Furthermore, the UUID of the bulk request message should also be supplied.

Error Handling

Typical errors are:

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

Message Types

  • Utilities Device ERP Smart Meter Create 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_DEVICESMCRTRCO_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.