Show TOC

Read Utilities Point Of Delivery Premise Data Locate this document in the navigation structure

 

To read premise data information for the Utilities Point Of Delivery.

Technical Data

Entity Type

Service Operation

Software Component Version

IS-UT 606

Release State

released

Technical Name

UtilitiesPointOfDeliveryERPPremiseDataByIDQueryResponse_In

Namespace

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

Application Component

IS-U

Web Service Definition (Back End)

ISU_PODPREMISEIDQR

Category

A2X

Direction

inbound

Mode

synchronous

Idempotency

no

Change/Update Behavior

not applicable

P2P Communication Enabled

true

Business Context and Use

The Read Utilities Point Of Delivery Premise Data service operation allows you to use the internal ID and key date to obtain the premise data for a Utilities Point Of Delivery.

This includes the following:

  • External ID for the utilities point of delivery

  • Premise data address information

  • Premise data address supplement

Features

You must provide a value for the UtilitiesPointOfDeliveryInternalID element. The key date is optional. When the operation is executed for the key date, the premise data for the Utilities Point Of Delivery is retrieved. If the key date is not entered, the service uses the current date for the selection.

Message Types

  • UtilitiesPointOfDeliveryERPPremiseDataByIDQuery_sync

  • UtilitiesPointOfDeliveryERPPremiseDataByIDResponse_sync

Prerequisites

Users must have the required authorization to display the utilities point of delivery and the premise (authorization object: E_POD and E_PREMISE).

Notes on SAP Implementation

Processing

This operation is suitable for the Utilities Industry Solutions sector. To use this service operation, you must:

  • Run the application component Utilities (IS-U).

  • Activate the Utilities business function set.

Enhancements

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

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