erp2005_ehp_07_en_43

(1)

SAP Utilities

PDF download from SAP Help Portal:

http://help.sap.com/erp2005_ehp_07/helpdata/en/43/6dce53118d4308e10000000a174cb4/frameset.htm Created on October 12, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help

Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You can manually download the missing subtopics.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

(2)

Table of content

1 SAP Utilities

1.1 Basic Functions

1.2 Master Data

1.3 Device Management

1.4 Energy Data Management

1.5 Contract Billing

1.6 Invoicing

1.7 Contract Accts Receivable and Payable for the Utilities Industry

1.8 Customer Service

1.9 Work Management

1.10 Information System

1.11 Intercompany Data Exchange

1.12 Advanced Metering Infrastructure

1.13 SAP Utilities Enterprise Services Documentation (EN only)

1.13.1 Business Partner Data Management

1.13.1.1 Business Partner

1.13.1.1.1 Business Partner Replication In

1.13.1.1.1.1 Replicate Business Partner as Bulk

1.13.1.1.2 Business Partner Replication Out

1.13.1.1.2.1 Confirm Business Partner Replication as Bulk

1.13.1.1.3 Business Partner Replication Requesting In

1.13.1.1.3.1 Change Business Partner Replication Status as Bulk

1.13.1.1.4 Business Partner Replication Requesting Out

1.13.1.1.4.1 Request Business Partner Replication as Bulk

1.13.1.2 Payment Card

1.13.1.2.1 Payment Card Processing In

1.13.1.2.1.1 Change Payment Card

1.13.1.2.1.2 Create Payment Card

1.13.1.2.1.3 Read Payment Card

1.13.2 Utilities Business Partner Data Management

1.13.2.1 Utilities Service Provider

1.13.2.1.1 Manage Utilities Service Provider In

1.13.2.1.1.1 Read Utilities Service Provider Basic Data

1.13.2.1.2 Query Utilities Service Provider In

1.13.2.1.2.1 Find Utilities Service Provider by Identification

1.13.3 Measurement Processing

1.13.3.1 Measurement Reading

1.13.3.1.1 Manage Measurement Reading In

1.13.3.1.1.1 Cancel Measurement Reading

1.13.3.1.1.2 Check Measurement Reading Creation

1.13.3.1.1.3 Create Measurement Reading

1.13.3.1.1.4 Read Measurement Reading

1.13.3.1.2 Measurement Reading In

1.13.3.1.2.1 Create Measurement Reading as Bulk

1.13.3.1.3 Query Measurement Reading In

1.13.3.1.3.1 Find Latest Measurement Reading

1.13.3.1.3.2 Find Measurement Reading ERP by Measuring Device

1.13.3.1.3.3 Find Measurement Reading by Elements

1.13.3.2 Meter Reading Card

1.13.3.2.1 Manage Meter Reading Card

1.13.3.2.1.1 Change Meter Reading Card

1.13.3.3 Meter Reading Document

1.13.3.3.1 Manage Meter Reading Document In

1.13.3.3.1.1 Cancel Meter Reading Document

1.13.3.3.1.2 Cancel Meter Reading Document Result

1.13.3.3.1.3 Create Meter Reading Document Result

1.13.3.3.1.4 Create Meter Reading Document With Reference To Utilities Device

1.13.3.3.1.5 Read Meter Reading Document Basic Data

1.13.3.3.2 Meter Reading Document In

1.13.3.3.2.1 Change Meter Reading Document Result as Bulk

(3)

1.13.3.3.2.2 Change Based on Smart Meter Meter Reading Document Result Creati

1.13.3.3.2.3 Change Based on Smart Meter Meter Reading Document Result Creati

1.13.3.3.2.4 Change Based on Smart Meter Meter Reading Document Creation Conf

1.13.3.3.2.5 Change Based on Smart Meter Meter Reading Document Creation Conf

1.13.3.3.2.6 Change Based on Smart Meter Meter Reading Document Result Change

1.13.3.3.2.7 Change Based on Smart Meter Meter Reading Document Result Change

1.13.3.3.2.8 Change Based on Smart Meter Meter Reading Document Cancellation

1.13.3.3.2.9 Change Based on Smart Meter Meter Reading Document Cancellation

1.13.3.3.2.10 Create Meter Reading Document Result

1.13.3.3.2.11 Create Meter Reading Document Result as Bulk

1.13.3.3.3 Meter Reading Document Out

1.13.3.3.3.1 Notify Meter Reading Document Out

1.13.3.3.3.1.1 Notify of Meter Reading Document Result as Bulk

1.13.3.3.3.2 Confirm Meter Reading Document Result Creation

1.13.3.3.3.3 Confirm Meter Reading Document Result Creation as Bulk

1.13.3.3.3.4 Confirm Meter Reading Document Result Change as Bulk

1.13.3.3.3.5 Request Smart Meter Meter Reading Document Creation

1.13.3.3.3.6 Request Smart Meter Meter Reading Document Creation as Bulk

1.13.3.3.3.7 Request Smart Meter Meter Reading Document Cancellation

1.13.3.3.3.8 Request Smart Meter Meter Reading Document Cancellation as Bulk

1.13.3.3.3.9 Request Smart Meter Meter Reading Document Result Creation

1.13.3.3.3.10 Request Smart Meter Meter Reading Document Result Creation as Bu

1.13.3.3.3.11 Request Smart Meter Meter Reading Document Result Change

1.13.3.3.3.12 Request Smart Meter Meter Reading Document Result Change as Bulk

1.13.3.3.4 Query Meter Reading Document In

1.13.3.3.4.1 Find Meter Reading Document Result by Utilities Device

1.13.3.3.4.2 Find Meter Reading Document by Utilities Device

1.13.3.4 Utilities Measurement Task

1.13.3.4.1 Manage Utilities Measurement Task In

1.13.3.4.1.1 Read Utilities Measurement Task Basic Data

1.13.3.4.2 Notify Utilities Measurement Task Out

1.13.3.4.2.1 Notify of Smart Meter Measurement Task Point Of Delivery Assigne

1.13.3.4.2.2 Notify of Smart Meter Utilities Measurement Task Device Assignme

1.13.3.4.2.3 Notify of Smart Meter Utilities Measurement Task Point Of Delive

1.13.3.4.3 Query Utilities Measurement Task In

1.13.3.4.3.1 Find Utilities Measurement Task by Utilities Point Of Delivery I

1.13.3.4.4 Utilities Measurement Task In

1.13.3.4.4.1 Change Based on Smart Meter Measurement Task Change Confirmation

1.13.3.4.4.2 Change Based on Smart Meter Utilities Measurement Task Change Co

1.13.3.4.5 Utilities Measurement Task Out

1.13.3.4.5.1 Request Smart Meter Utilities Measurement Task Change

1.13.3.4.5.2 Request Smart Meter Utilities Measurement Task Change as Bulk

1.13.4 Service Contract Processing

1.13.5 Utilities Connection Processing

1.13.5.1 Utilities Connection Status Change Request

1.13.5.1.1 Utilities Connection Status Change Request In

1.13.5.1.1.1 Change Based on Smart Meter Connection Status Change Request Bul

1.13.5.1.1.2 Change Based on Smart Meter Connection Status Change Request Can

1.13.5.1.1.3 Change Based on Smart Meter Connection Status Change Request Cre

1.13.5.1.2 Utilities Connection Status Change Request Out

1.13.5.1.2.1 Request Smart Meter Utilities Connection Status Change Request C

1.13.5.1.2.2 Request Smart Meter Utilities Connection Status Change Request C

1.13.5.1.2.3 Request Smart Meter Utilities Connection Status Change Request C

1.13.5.1.2.4 Notify Utilities Connection Status Change Request Out

1.13.5.1.2.4.1 Notify of Smart Meter Utilities Connection Status Change Request

1.13.5.1.2.4.2 Notify Cancellation of Smart Meter Utilities Connection Status C

1.13.5.1.3 Utilities Connection Status Management In

1.13.5.1.3.1 Change Utilities Connection Status Change Request Based on Confi

1.13.5.1.4 Utilities Connection Status Management Out

1.13.5.1.4.1 Request Utilities Connection Status Change Request

1.13.5.1.4.2 Request Utilities Connection Status Change Request Cancellation

1.13.6 Utilities Contract Processing

(4)

1.13.7 Utilities Device Management

1.13.7.1 Utilities Device

1.13.7.1.1 Manage Utilities Device In

1.13.7.1.1.1 Read Utilities Device Basic Data

1.13.7.1.2 Notify Utilities Device In

1.13.7.1.2.1 Change Based on Utilities Device Smart Meter Registered Notifica

1.13.7.1.2.2 Change Based On Utilities Device Smart Meter Registered Notifica

1.13.7.1.3 Notify Utilities Device Out

1.13.7.1.3.1 Notify of Utilities Device Smart Meter Location

1.13.7.1.3.2 Notify of Utilities Device Smart Meter Location as Bulk

1.13.7.1.3.3 Notify of Utilities Device Smart Meter Relationship

1.13.7.1.3.4 Notify of Utilities Device Smart Meter Text as Bulk

1.13.7.1.4 Query Utilities Device In

1.13.7.1.4.1 Change Based on Utilities Device Smart Meter Operational State b

1.13.7.1.5 Query Utilities Device In

1.13.7.1.5.1 Find Utilities Device by Utilities Measurement Task

1.13.7.1.6 Query Utilities Device Out

1.13.7.1.6.1 Query Utilities Device Smart Meter Operational State by ID

1.13.7.1.7 Utilities Device In

1.13.7.1.7.1 Change Based on Device Smart Meter Register Creation Confirmatio

1.13.7.1.7.2 Change Based on Utilities Device Smart Meter Cancellation Confir

1.13.7.1.7.3 Change Based on Utilities Device Smart Meter Change Confirmation

1.13.7.1.7.4 Change Based on Utilities Device Smart Meter Change Confirmation

1.13.7.1.7.5 Change Based on Utilities Device Smart Meter Creation Confirmati

1.13.7.1.7.6 Change Based on Utilities Device Smart Meter Creation Confirmati

1.13.7.1.7.7 Change Based on Utilities Device Smart Meter Register Change Con

1.13.7.1.7.8 Change Based on Utilities Device Smart Meter Register Change Con

1.13.7.1.7.9 Change Based on Utilities Device Smart Meter Register Creation C

(5)

SAPUtilities

Purpose

SAP Utilities is a process-oriented sales and information system that supports all services provided by utility and waste disposal companies. You can use SAP Utilities to manage and bill residential, commercial and industrial, and prospective customers.

In times of deregulated markets and increasing competition, it is vital that you provide the bet possible response to your customers’ requirements, use operational information tailored to their specific requirements, and maximize revenue potential. As an integrated component in SAP ERP , SAP Utilities provides you with all the benefits of a comprehensive and effective Enterprise Resource Planning (ERP) System.

SAP Utilities helps you to keep you business processes as streamlined and as efficient as possible. As a single software solution, SAP Utilities eliminates incompatible and isolated information in the back office.With SAP Utilities , you can access data at any time from diverse business areas, providing you with the information you need to make the right decisions.

Integration

Solution Portfolio SAPfor Utilities

SAP Utilities is part of the solution portfolio SAP for Utilities and includes the SAP Utilities (IS-U) industry-specific component. SAPforUtilities can be integrated with the following applications:

Application Documentation

SAP Customer Relationship Management SAP Help Portal (help.sap.com):

SAP Business Suite SAP Customer Relationship Mgmt.

SAP NetWeaver Business Intelligence SAP Help Portal (help.sap.com):

SAP NetWeaver (or other release) German SAP NetWeaver by Key Capability{ BI Content Industry Solutions Utilities

SAP NetWeaver Portal SAP Help Portal (help.sap.com):

SAP NetWeaver Portal Content

SAP Utilities Customer E-Services SAP Solution Manager

You can use the Plant Maintenance (PM), Customer Service (CS) and Sales and Distribution (SD) SAP ECC application components to bill service orders, service contracts, services, and the sale of goods. Due to the large number of postings from billing and budget billing requests, these are posted in a subledger in Contract Accounts Receivable and Payable (FI-CA) .

SAP Utilities uses SAP Business Workflow to automate the processing of its many business processes. Common workflows include initial creation of a service connection and the disconnection of devices.

Features

SAPUtilities

You can use Basic Functions to manage addresses and regional structures. You can generate schedules for meter reading, budget billing, and billing. You can use Master Data to manage data that remains fixed for long periods of time. In IS-U, this data includes the business partners, contracts and contract accounts, connection objects (buildings and real estate) and the premises, installations, and device locations contained therein.

You can use Device Management to manage the installations, meter reading, and the certification of all devices for a utility company. The Billing component is used to bill the standard divisions: Electricity, gas, water/waste water, district heating, and multimedia services (for example, cable TV).

You can use Invoicing to group services and invoice them on one bill. You can also use Invoicing to calculate and charge duty, fees, and taxes. In Customer Service you can use the Customer Interaction Center (CIC) or Front Office to display all data and start specific business processes. In Internet-Self-Services your customers can send you new data or changes to their existing data via the Internet. For example, they can grant you collection authorization or register a move-in.

Energy Data Management (EDM) is a solution that meets the requirements of interval reading, schedule management, and the billing of interval energy consumption. EDM includes the following functions:

(6)

Central database for energy data (Energy Data Repository)

Settlement and schedule management using the settlement workbench Billing of profiles using real-time-pricing billing (RTP billing)

Intercompany Data Exchange (IDE) fulfills the requirements of the deregulated market. IDE includes the following functions: Infrastructure for processing deregulated business processes

Unbundling

Data exchange processes Change of supplier processes

Bill and payment processing in the deregulated environment

Work Management combines various SAP components and enhances them to include industry-specific functions for planning, calculating, executing, and billing work orders.

SAP Waste and Recycling (IS-U-WA) is a comprehensive logistics, billing, service, and customer service system that covers all the business processes required by a waste disposal company.

Note

If you have any comments or suggestions regarding this documentation, we are always grateful for Feedback .

1.1 Basic Functions

Purpose

This component contains the following basic functions of the Utilities Industry (IS-U) component: Central management of address data arranged according to postal and political regional structure Scheduling at the meter reading unit and portion levels

1.2 Master Data

Purpose

This component contains data for the Utilities Industry (IS-U) component that remains unchanged over a long period of time. The graphic below illustrates the master data and shows how the various objects are related to each other.

Master Data in IS-U

There are 2 different types of master data: technical and business. These are shown in the graphic below:

1.3 Device Management

Purpose

This component manages technical data, installations, meter readings, and the inspection of devices.

If you have activated the Advanced Metering Infrastructure business function ((ISU_AMI_1)) and you are in an advanced metering infrastructure, you can find more information under Advanced Metering Infrastructure.

Integration

The following table lists the standard application components that must be integrated into device management before you can manage devices. The device, device category, and device number in the Utilities Industry (IS-U) component correspond to equipment, material, and the serial number in the standard system:

Name in IS-U From Component Name in Standard System

Device Plant Maintenance (PM) Equipment

Device Category Logistics Basic Data (LO-MD) Material

Device Number Logistics Basic Data (LO-MD) Serial Number

The device number is created in MM with the Goods Receipt function and transferred to the device. It can also be generated when you create a device in IS-U. The device is identified by a unique material and serial number combination to distinguish it from other pieces of material that may have the same serial number. The equipment number is the same throughout the system.

(7)

MM is also used for the following functions in device flow:

Function Component

Procurement Purchase Requisition and Purchase Order from Purchasing (MM-PUR)

Delivery Goods Receipt from Inventory Management (MM-IM)

Outward Movement (such as scrapping or sales) Goods Issue and Return Delivery from MM-IM

Stock Transfer Goods Issue and Return Delivery from MM-IM

Equipment records are created automatically at goods receipt . Therefore, functions of the PM application component are used, including standard ordering functions and creation of maintenance plans or task lists. Billing is then carried out with the Sales and Distribution (SD) component.

More Information

PM: Equipment LO-MD: Material Master

MM-PUR: Purchase Requisitions, Purchase Orders

MM-IM: Planning Goods Receipts, Goods Receipts for Purchase Orders, Goods Receipts for Orders, Other Goods Receipts, Goods Issues.

1.4 Energy Data Management

Purpose

Energy Data Management is a solution that fulfills requirements by offering interval reading, settlement of energy quantities, scheduling, and billing of interval energy consumption.

Integration

The Energy Data Management (SAP IS-U-EDM) component is fully integrated into the SAP IS-U system and can be installed in an existing SAP IS-U system as a new component. SAP IS-U-EDM is also integrated into Intercompany Data Exchange (SAP IS-U-IDE). This component allows for data exchange in standardized formats and enables the integration of cross-company business processes. SAP IS-U-EDM allows you to bill profiles in SAP IS-U. Profiles are prepared in SAP IS-U-EDM and transferred to SAP IS-U billing via an internal interface. This allows you to bill new types of contracts, such as spot purchases.

SAP IS-U-EDM also interfaces with automated meter reading systems.

Features

Energy Data Management covers the following areas: Central database for energy data (Energy Data Repository) Settlement and scheduling using the settlement workbench Billing profiles using Real-Time-Pricing Billing

(8)

Profile Management

For further information see Profile Management

Import of Profile Values

You can import and monitor profile values using a standard interface.

Replacement Value Creation

For more information see Replacement Value Creation

Profile Display and Editing

Microsoft® Excel has been integrated into IS-U-EDM via an OLE (object linking and embedding) interface. This interface allows you to: Display profile values in Microsoft® Excel.

Change profile values in Excel and save the changes in an Excel file.

Export profile values (including status) from SAP IS-U-EDM to an Excel file and edit them at your workstation. Import elementary profile values (including status) from an Excel file into SAP IS-U-EDM.

The system performs predefined consistency checks during the import process.

Displaying Profiles on the Internet

You can use an Internet Application Component to display profile values on the Internet.

Settlement

For more information see Settlement

Calculating Profiles

For more information see Profile Calculation

Sending Profiles

You can send profiles to communication partners and display a list of sent profiles.

To send profiles, see Energy Data Management → Send Profiles in the Utilities Industry menu.

Profile Billing

For more information, see Real-Time-Pricing Billing .

1.5 Contract Billing

The supply and services provided by a utility company are billed using this component. It offers a range of billing procedures with a variety of selection and control options. For example, the component enables the following:

Billing of residential and commercial and industrial customers Annual consumption billing and periodic monthly billing cycles Billing for different divisions

Numerous bill forms Billing simulation

Validation of billing documents and bills

Integration

Billing can process discrete measured data from the Meter Reading component (IS-U-DM-MR) as well as interval data from the Energy Data Management component (IS-U-EDM).

If you have activated the business function Utilities, Quantity Determination (ISU_QD_1) and you use the quantity determination procedure Quantity Determination During Meter Reading , the system determines a consumption value during meter reading result entry. The value is saved to the database. In this case, billing processes the consumption quantity and not the meter reading results.

For more information, see:

Quantity Determination During Meter Reading

The billing results are processed in the Invoicing component (IS-U-IN).

In addition to the standard services, utility companies also offer their customers other services. Some important additional services are, for example: Installation of a service connection

Maintenance and repairs Sales

These additional services are either billed and invoiced in the Sales and Distribution (SD) component, or externally.

(9)

1.6 Invoicing

Use

This component:

Creates FI-CA documents for: IS-U consumption billing External billing

SD billing (sales, installation)

Clears bill receivables with posting items, in particular with budget billing payments that have been made Creates and prints bills

Supports reversal processes

Manages the budget billing plans and provides functions for processing the budget billing amounts Supports the determination and levying of taxes, charges and duties

Supports additional functions such as: Interest Calculation

Dunning Locks

Clearing control, account maintenance, and so on The following figure shows the uses and additional functions of invoicing:

Integration

The Contract Billing (IS-U-BI) component sends billing documents, credit memos, backbillings, and the basis for the budget billing plans to invoicing. The budget billing plan is formed on the basis of the budget billing extrapolation lines, which are created automatically in periodic billing.

Invoicing links the Utilities Industry (IS-U) component with the Contract Accounts Receivable and Payable (FI-CA) component. Posting documents and budget billing plans are created in FI-CA and are taken into account by invoicing during account maintenance.

The Print Workbench (IS-U-TO-PW) component is used for creating the bill form.

The following graphic shows the connection between billing, invoicing and contract accounts receivable and payable:

1.7 Contract Accts Receivable and Payable for the Utilities

(10)

1.7 Contract Accts Receivable and Payable for the Utilities

Industry

Use

Contract Accounts Receivable and Payable is a subledger developed for industries with a large customer base and a correspondingly high volume of documents to post, such as utility companies.

Features

This component provides standard accounts receivable and accounts payable functions including dunning, posting documents, and making payments. Contract accounts receivable and payable currently consists of the following detailed components:

Basic Functions Business Transactions Integration Closing Operations Information System Job Controls

European Monetary Union and Contract Accounts Receivable and Payable Archiving

Interfaces The EVENT Concept Data Processing in Mass Runs Enhanced Message Management

1.8 Customer Service

Purpose

This component is used to efficiently manage services and business transactions in IS-U/CCS. It supports you in: Customer information (for example, for account inquiries, meter reading results, and budget billings) Executing processes and workflows:

Invoicing costs that arise from service provision Logging and managing customer contacts

Integration

Depending on your Customizing settings, you can integrate all components of the Utilities Industry (IS-U) component and components of the standard system, for example the component Service Processing (CS-SE).

Features

The data finder , a high-performance search function, helps you identify customers. Depending on the data you are given, you can search by the following criteria:

Name and address of the customer Address of the connection object Customer number

Social security number You can also:

Combine search criteria any way you like

Search with incomplete criteria (for example, all names starting with Ma). Restrict the search according to objects (for example, the division electricity).

Example

You can search for customers who inhabit the same property.

You can integrate external communication systems in IS-U/CCS. You can, for example, display documents stored in the optical archive (such as bills and welcome letters), store in or outbounf documents (such as letters or faxes), integrate a call center solution using the SAPPhone component or send E-mails via the SAPConnect component.

1.9 Work Management

Purpose

(11)

You use this component for accepting, planning, calculating and carrying out work orders and, if applicable, for billing work orders to a customer. For this process, a distinction is made between two types of work order as follows:

External work orders relating to the customer ("services")

Examples of external work orders are:

Creation and amplification of service connections Energy consulting

Unplanned meter readings

Disconnection and reconnection (electricity, gas)

Internal work orders

Examples of internal work orders are: Maintenance

Repairs

Installation, modification or removal of technical equipment

To create a work order efficiently, the Utilities Industry (IS-U) component uses references ("compatible units"). Using a small number of parameters defined by the user, the system can generate the appropriate order.

After the order has been created, the system monitors the provision of resources and schedules the order. Geographical conditions play an important role here, especially in the utilities industry.

1.10 Information System

Purpose

You use this component to manage the statistics for the master data and the most important transactions in the Utilities Industry component ( IS-U ). This gives you fast and effective access to all of the data in your company. You can not only view the data, but can also evaluate, analyze, and display it.

Integration

IS-U manages data required for evaluating statistics in separate files. You analyze stock statistics, transaction statistics, and sales statistics using the Logistics Information System (LO-LIS) component, which is integrated with the Open Information Warehouse (CA-OIW) component. This allows you to use the analysis tools from CA-OIW to evaluate, analyze and present statistics.

You can also use external programs, such as Microsoft Excel , to analyze the statistics. User Exits also allow you to add information from other applications to the statistics.

1.11 Intercompany Data Exchange

Unbundling utility companies has changed the bilateral relationship of customers with a local provider in a regulated market to a multilateral relationship involving different contract and service relationships. A customer has a contractual relationship with their energy supplier, and a service relationship and in some cases also a contractual relationship with their local distributor. Since the customer can change their energy supplier according to current market offerings, additional contractual relationships may also exist over time. Commercial and industrial customers can obtain energy from several suppliers in parallel.

So that services from the supplier, distributor and possibly from other service providers to a customer can be coordinated, managed and billed, processes must be executed and information exchanged between these parties. Data exchange includes information about the customer, location and technology used by the service location, measurement values, contract content, billing information and payment transactions. This involves bilateral communication between the customer information systems used by the utility companies involved. These types of collaborative business process scenarios include for example informing the distributor that a customer has switched to a different supplier. This also involves reporting meter reading results from the distributor or meter operation service company to the supplier or exchanging billing results between service providers to ensure that a collective consolidated bill can be sent to the customer.

Modern information technology must support an enormous volume of transactions that are generated in the deregulated utilities industry: If a customer switches to a different supplier, in the energy market or when managing an extensive number of different service providers. It has become more important than ever before to keep process costs in check. World class IT support can play a decisive role here. Effective customer and cost management are also core requirements of an integrated IT system landscape.

You can use Intercompany Data Exchange (SAP IS-U/IDE) in conjunction with Energy Data Management (SAP IS-U/EDM) and additional SAP for Utilities applications to meet the deregulation requirements of energy markets.

Integration

To represent certain processes, you also require additional SAP for Utilities applications that are seamlessly integrated with Intercompany Data Exchange. Representing the processes for Energy Quantity Settlement involves both Energy Data Management and Intercompany Data Exchange. Representing the processes for Managing Grid Usage involves the following applications in addition to Intercompany Data Exchange:

Billing

Energy Data Management Invoicing

FI-CA

Features

(12)

Intercompany data exchange provides the infrastructure and functions required to implement unbundling requirements and to represent the resulting scenario Change of Supplier and Managing Grid Usage and also to process data exchange in deregulated markets.

Note

For more information about this scenario, see SAP Solution Manager. The documentation for Intercompany Data Exchange is structured as follows:

Deregulation Data

This section describes the master data objects that are required to use the SAP IS-U System in deregulated markets. This deregulation data is used by the deregulation functions.

Deregulation Functions

The Deregulation Settings section describes the basic settings that you make to configure your system for use in a deregulated environment. These deregulation settings are the basis for using the deregulation functions.

The Deregulation Infrastructure section describes the functions that make up the infrastructure used to represent deregulated processes. The Unbundling section describes the options for implementing unbundling of information.

The Processing Data Exchange section describes the functions and processes that are used to perform data exchange in the deregulated environment.

Data exchange is performed for all deregulation processes. During the change of supplier process, information about the registration or

deregistration of grid usage and the cancellation of supply service relationships is exchanged. During bill processing and payment handling, market participants communicate with each other to exchange bills, complaints, payments, and payment advice notes. The data exchanged refers to the customers for which the various service providers perform services or with whom they have contractual agreements.

The Change of Supplier section describes the functions and processes that are used to manage the change of supplier processes. The Bill Processing and Payment Handling section describes the functions and processes that are used to manage the various individual processes.

The Technical Reference to Deregulation Functions contains information about the architecture and project-specific enhancement options for the deregulation functions described previously.

Migration

This section describes migration objects for the deregulation data.

1.12 Advanced Metering Infrastructure

An advanced metering infrastructure is a communication network consisting of measurement devices and systems. An infrastructure of this nature is characterized by intensive interaction between the different market participants. These market participants can occupy different roles in the market. They exchange information according to these roles. The related information and data exchange processes virtually take place in real time.

Companies in the energy industry, associations, and government organizations choose an advanced metering infrastructure with the aim of increasing efficiency and optimizing grid usage as a result of improved evaluation options on the consumer side.

You can use SAP Utilities as a customer information and billing system together with other SAP applications as part of an advanced metering infrastructure. The SAP system can communicate with other systems and exchange data.

The following diagram illustrates how the SAP applications are integrated in an advanced metering infrastructure.

AMI System Landscape

The AMI system landscape illustrated is subdivided into three large areas:

(13)

On the left hand side, the AMI systems, on the right hand side, the SAP system as a back-office system, and in the middle, the MDUS system as an interface between the two.

The AMI systems on the left hand side include devices with advanced metering capabilities, advanced metering systems (AMS), and other devices and systems, such as data concentrators. Advanced metering systems measure, gather, and analyze energy consumption data from AMI devices and transmit commands and data to these devices.

MDUS in the middle stands for Meter Data Unification & Synchronization and describes systems that unite the interfaces between different advanced

metering systems and synchronize the data and processes in these systems with those in the back-office systems.

You can use the SAP system on the right hand side to run the usual back-office processes, as well as processes and functions specific to an advanced metering infrastructure. Communication between the SAP applications and the MDUS system takes place using enterprise services.

Processes can only run fully if all the devices and systems in the advanced metering infrastructure meet the technical requirements and support the required capabilities. For this reason, the SAP Utilities processes are only possible if the required capabilities are supported both by the advanced metering system and by the device.

Example

The advanced metering system supports the Remote Disconnection capability but the device does not. This means the remote disconnection process cannot take place.

Integration

The AMI capabilities in the SAP system are based on existing functions in the following areas: Device Management

Meter Reading Contract Billing Customer Service

The remaining documentation focuses on the capabilities and processes that are specific to an advanced metering infrastructure, or that are processed differently in this context than is the case in an infrastructure that is not based on advanced metering technology. For this reason, the descriptions contain a number of references to the documentation for the above areas.

More Information

For more information about enterprise services (English language), see SAP Library at SAP for Utilities Enterprise Services Documentation and help.sap.com/ecc SAP ERP 6.0 Enterprise Services Documentation

1.13 SAP Utilities Enterprise Services Documentation (EN only)

Features

Enterprise services are web services defined by SAP that enable companies to implement and adapt automated business processes with unprecedented speed and ease. They can also be used to break processes into smaller process steps to create reusable enterprise services that can easily be adapted to changing business needs.

The documentation that follows describes the enterprise services that are available to you in SAP for Utilities. This documentation provides technical descriptions of specific enterprise service objects and is divided into bundles in the following schema:

1. Process Component 2. Business Object 3. Service Interface

4. Enterprise Service Operation.

Enterprise service bundles provide an ideal starting point to explore the impact of service-oriented architecture (SOA) on your business processes. They create a comprehensive portfolio of business scenario descriptions that are SOA-enabled by solutions and enterprise services currently shipped by SAP. Enterprise service bundles documentation provides you with information about the impact of SOA on your business processes without requiring detailed knowledge of SAP solutions or technology. Each enterprise service bundle refers to a set of enterprise services that support a particular business process and are made available as part of the SAP Enhancement Packages for SAP Business Suite solutions.

Note

To search for information about specific enterprise service fields, you can use the Utilities data type catalog at

http://service.sap.com/~sapidb/011000358700001049282012E ( service.sap.com/utilities SAP for Utilities SAP for Utilities - Product Information IS-U/CCS General Cookbook&Guidelines Utilities Data Type Catalog ).

Specific use cases for service operations in the SAP for Utilities area can be found in the following enterprise service WIKIs (registration required): Advanced Meter Infrastructure WIKI at https://wiki.sdn.sap.com/wiki/display/ESpackages/Advanced+Meter+Infrastructure

Market Communication WIKI at https://wiki.sdn.sap.com/wiki/display/ESpackages/Market+Communication

For general information about the installation and prerequisites for using enterprise services, see the following information sources: SCN Community in the SAP Network at https://scn.sap.com/community/soa (registration required)

SAP Note 1359215: Technical prerequisites for using enterprise services (relevant for ERP only)

1.13.1 Business Partner Data Management

(14)

Business Partner Data Processing enables a company to manage all Business Partner data that is relevant to control its business processes, such as sales, purchasing and accounting processes.

Technical Data

Entity Type Process Component

Software Component Version ESM BS FOUND 731

Technical Name BusinessPartnerDataManagement

Namespace http://sap.com/xi/ESM/SUITE

1.13.1.1 Business Partner

A carrier of unstructured information and additional control and monitoring information.

Technical Data

Entity Type Business Object

Technical Name BusinessPartner

Object Category Master Data Object

1.13.1.1.1 Business Partner Replication In

Technical Data

Entity Type Service Interface

Category SAP A2A

Direction inbound

1.13.1.1.1.1 Replicate Business Partner as Bulk

Request to create or update Business Partners in a target system, using master data from a source system or file.

Technical Data

Entity Type Service Operation

Software Component Version SAP_BS_FOUNDATION 731

Release State released with restrictions

Technical Name BusinessPartnerSUITEBulkReplicateRequest_In

Namespace http://sap.com/xi/SAP_BS_FND/MDG/Global2

Application Component CA-MDG-APP-BP

Web Service Definition (Back End) BUSINESSPARTNERSUITEBULKREPLIC

Category SAP A2A

Direction inbound

Mode asynchronous

Idempotency not applicable

P2P Communication Enabled yes

Message Types

Business Partner SUITE Bulk Replicate Request

(15)

Notes on SAP Implementation

The MDG_SE_BP_BULK_REPLRQ_IN Business Add-In (BAdI) is available for this operation.

1.13.1.1.2 Business Partner Replication Out

Technical Data

Category SAP A2A

Direction outbound

1.13.1.1.2.1 Confirm Business Partner Replication as Bulk

Confirmation of the replication of business partners as bulk.

Technical Data

Technical Name BusinessPartnerSUITEBulkReplicateConfirmation_Out

Category SAP A2A

Direction outbound

Mode asynchronous

Message Types

Business Partner SUITE Bulk Replicate Confirmation

1.13.1.1.3 Business Partner Replication Requesting In

Inbound Interface for receiving Business Partner Replication Notification.

Technical Data

Category SAP A2A

Direction inbound

1.13.1.1.3.1 Change Business Partner Replication Status as Bulk

A mass confirmation of the replication of Business Partners.

Technical Data

Technical Name BusinessPartnerSUITEBulkReplicateConfirmation_In

(16)

Web Service Definition (Back End) BUSINESSPARTNERSUITEBULKREPLI1

Category SAP A2A

Direction inbound

Mode asynchronous

Message Types

Business Partner SUITE Bulk Replicate Confirmation

Notes on SAP Implementation

The MDG_SE_BP_BULK_REPLCNF_IN Business Add-In (BAdI) is available for this operation.

1.13.1.1.4 Business Partner Replication Requesting Out

Outbound Interface for Sending Business Partner Replication Notification.

Technical Data

Category SAP A2A

Direction outbound

1.13.1.1.4.1 Request Business Partner Replication as Bulk

A mass request to replicate Business Partners.

Technical Data

Technical Name BusinessPartnerSUITEBulkReplicateRequest_Out

Category SAP A2A

Direction outbound

Mode asynchronous

Message Types

Business Partner SUITE Bulk Replicate Request

Notes on SAP Implementation

The MDG_SE_BP_BULK_REPLRQ_OUT Business Add-In (BAdI) is available for this operation.

1.13.1.2 Payment Card

(17)

Payment Cards, such as credit cards, debit cards, or charge cards, are payment instruments issued by banks, financial institutions and businesses to individuals (card holders). The card holder can present the card to make cashless payments for goods and services at a merchant, who has an agreement with the issuer to accept the payment.

Technical Data

Technical Name PaymentCard

Features

Payment Card consists of the card data (root) and information regarding blocks (node: Block).The business and technical purpose that applies to all service interfaces of this business object is the processing of payment card master records.Customer and business partner payment card master data are stored at two different storages in the SAP back-end system.The related semantic name of this object in the SAP SUITE back-end system is payment card master record.

Constraints

You cannot delete a payment card master record from the SAP SUITE back-end system because this may result in inconsistencies, such as, if a payment card which has already been used for payment transactions will be physically removed from the system.

1.13.1.2.1 Payment Card Processing In

Technical Data

Category SAP A2A

Direction inbound

Business Context and Use

The Manage Payment Card inbound service interface comprises operations that enable a payment card to be read, created or changed.

1.13.1.2.1.1 Change Payment Card

To change a payment card master record.

Technical Data

Release State released

Technical Name PaymentCardSUITEChangeRequestConfirmation_In

Namespace http://sap.com/xi/SAP_BS_FND/Global2

Application Component CA-EPT

Web Service Definition (Back End) BS_PAYTCARDSUITECHGRC

Category A2X

Direction inbound

Mode synchronous

Idempotency yes

Change/Update Behavior not applicable

P2P Communication Enabled true

Business Context and Use

(18)

The Change Payment Card inbound operation changes a payment card.

Features

To change a Payment Card, the following data is needed:

Input

All mandatory fields have to be filled. ID (ID of the payment card)

blockListCompleteTransmissionIndicator (If this indicator is set, all block items will be deleted, which are not part of the block payload.) CategoryCode (not supported; should therefore not be filled)

TypeCode (type of payment card)

ValidityStartDate (date from which the payment card is valid) ExpirationDate (date up to which the payment card is valid) IssueDate (date the payment card was issued)

HolderName (name of the person or company to whom the payment card was issued) IssuerName (bank that issued the payment card)

Block

PaymentCardBlockingReasonCode (ndicates whether a payment card is blocked and for what reason)

ActionCode (If the ActionCode is empty the default 01 = create is used automatically; only ActionCodes 01 (Create) and 03 (Delete) are supported.)

ValidityPeriod

StartDate (date as of which the payment card block is valid) EndDate (date up to which the payment card block is valid) Duration (not supported; should therefore not be filled) Output

Output

For security reasons, the payment card ID which corresponds to the payment card number in the SAP Business Suite back-end system is not displayed. Instead the Payment Card MaskedID of the payment card master record is displayed, which has been created by the current service operation. The security level can be adjusted in Customizing of the SAP Business Suite backend system underCross Application Components > Payment Cards > Basic Settings -> Maintain Security Settings for Payment Cards.If the Customizing is not maintained only the first five and the last two digits of the card number are displayed (for example 99341*********77).

For security reasons, the payment card ID which corresponds to the payment card number in the SAP Business Suite back-end system is not displayed. Instead the Payment Card MaskedID of the payment card master record is displayed, which has been created by the current service operation. The security level can be adjusted in Customizing of the SAP Business Suite back-end system under Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Security Settings for Payment Cards. If the Customizing is not maintained only the first five and the last two digits of the card number are displayed (for example 99341*********77).

Error Handling

If errors occur, tThe system issues an error log.

Message Types

PaymentCardSUITEChangeConfirmation_sync PaymentCardSUITEChangeRequest_sync

Prerequisites

You have created a payment card master record.

Constraints

ActionCode 02 used to change the block of a payment card is not supported. As an alternative you can delete the block and then create a new block

Notes on SAP Implementation

Configuration

You must run the application component Payment Card (AP-MD-PCA). You have defined at least one payment card type in Customizing under Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Payment Card Type .

Depending on the Customizing settings you have made for the security level, the system: Encrypts payment card numbers when they are saved

Masks payment card numbers in the service confirmation message

(19)

You set the security level in Customizing under Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Security Settings for Payment Cards .

In addition, to ensure secure handling of payment card information in the SAP Business Suite, you must deactivate the recording of service calls in the PI monitor (also see SAP note 1032588).

Enhancements

There are three Business Add-Ins available to enhance the current operation:

Change Payment Card ( PYCD _ESOA_PAYTCARDCHGRC), e nhancement spot PYCD_SPOT_ESOA_PAYT_CARDMethod

INBOUND_PROCESSING of this BAdI is processed at the beginning of the operation. Using this method you can run checks and modify the input data. Method OUTBOUND_PROCESSING is processed at the end of the operation. Using this method you can modify the values in the response message before they are sent to the consumer.

Mapping for Blocking Reason Code ( PYCD_ESOAMAP_PAYTCARDBLCKREAS), e nhancement spot PYCD_SPOT_ESOA_PAYT_CARD Using Method MAP_EXT2INT, you can implement your own value mapping for the external field PaymentCardBlockingReasonCode to the payment card block (data element CC_LOCK ) in the SAP Buisness Suite back-end system. Using Method MAP_INT2EXT, you can implement your own value mapping for the payment card block (data element CC_LOCK ) in the SAP Business Suite back-end system to the external field

PaymentCardBlockingReasonCode.

Mapping of Payment Card Type (BSBP_ESAMAP_PAYMNTCRDTYPE), e nhancement spot BSBP_ESAMAP_PAYMNTCRDTYPE Met hod: MAP_EXT2INT Using Method MAP_EXT2INT, you can implement your own value mapping for the external field TypeCode to the payment card type (data element CC_INSTITUTE) in the SAP Buisness Suite back-end system. Using Method MAP_INT2EXT, you can implement your own value mapping for the payment card type in the SAP Business Suite back-end system to the to the external field TypeCode.

1.13.1.2.1.2 Create Payment Card

To create a payment card master record.

Technical Data

Technical Name PaymentCardSUITECreateRequestConfirmation_In

Web Service Definition (Back End) BS_PAYTCARDSUITECRTRC

Category A2X

Direction inbound

Mode synchronous

Idempotency yes

Business Context and Use

The Create Payment Card inbound operation creates payment card master records in the SAP Business Suite back-end system.

Features

To create a Payment Card, the following data is needed:

Input

All mandatory elements have to be filled: PaymentCardID (number of the payment card) TypeCode (type of payment card)

ValidityStartDate (date from which the payment card is valid)

IssueDate (date the payment card was issued)If the IssueDate is not specified in the inbound service the IssueDate will be initial. ExpirationDate (date up to which the payment card is valid)If the ExpirationDate is not specified in the inbound service the ExpirationDate will automatically be set to December 31, 9999.

HolderName (name of the person or company to whom the payment card was issued) IssuerName (bank that issued the payment card)

Output

(20)

Payment Card MaskedID

In order to avoid errors when making entries, you can assign checking rules for payment card numbers (ID) to payment card types. The checking rules check whether certain conditions for the payment card type are met. You maintain checking rules for payment card types in Customizing of the SAP SUITE back-end system under Cross Application Components -> Payment Cards -> Basic Settings -> Assign Checking Rules .

Error Handling

In case errors occur the system issues an error log.

Message Types

PaymentCardSUITECreateConfirmation_sync PaymentCardSUITECreateRequest_sync

Constraints

CategoryCode is not supported and should therefore not be filled.

Notes on SAP Implementation

Configuration You must run the application component Payment Card (AP-MD-PCA). You have defined at least one payment card type in Customizing under

Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Payment Card Type . Depending on the Customizing settings you have made for the security level, the system:

Encrypts payment card numbers when they are saved

You set the security level in Customizing under Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Security Settings for Payment Cards .

Enhancements There are two Business Add-Ins available to enhance the current operation:

Create Payment Card (PYCD_ESOA_PAYTCARDCRTRC), enhancement spot PYCD_SPOT_ESOA_PAYT_CARDMethod INBOUND_PROCESSING of this BAdI is processed at the beginning of the operation. Using this method you can run checks and modify the input data.Method

OUTBOUND_PROCESSING is processed at the end of the operation. Using this method you can modify the values in the response message before they are sent to the consumer.

Mapping of Payment Card Type (BSBP_ESAMAP_PAYMNTCRDTYPE), enhancement spot BSBP_ESAMAP_PAYMNTCRDTYPE)Using Method MAP_EXT2INT, you can implement your own value mapping for the external field TypeCode to the payment card type (data element CC_INSTITUTE) in the SAP Buisness Suite back-end system.Using Method MAP_INT2EXT, you can implement your own value mapping for the payment card type (data element CC_INSTITUTE) in the SAP Business Suite back-end system to the external field TypeCode.

1.13.1.2.1.3 Read Payment Card

To read details of a payment card master record.

Technical Data

Technical Name PaymentCardSUITEByIdQueryResponse_In

Web Service Definition (Back End) BS_PAYTCARDSUITEBYIDQR

Category A2X

Direction inbound

Mode synchronous

Idempotency no

(21)

Business Context and Use

The Read Payment Card inbound operation returns all attributes of a payment card master record.

Features

The Create Payment Card inbound operation reads detail information of payment card master records in the SAP Business Suite back-end system. To read a Payment Card, the following data is needed:

Input

All mandatory elements have to be filled: PaymentCardID (number of the payment card) TypeCode (type of payment card)

Output

Payment Card MaskedID

Error Handling

If errors occur, the system issues an error log.

Message Types

PaymentCardSUITEByIDQuery_sync PaymentCardSUITEByIDResponse_sync

Prerequisites

You have created a payment card master record.

Notes on SAP Implementation

Configuration

You must run the application component Payment Card (AP-MD-PCA).

Depending on the Customizing settings you have made for the security level, the system: Encrypts payment card numbers when they are saved

You make the settings for encryption and masking in Customizing of the SAP Business Suite back-end system under Cross Application Components -> Payment Cards -> Basic Settings -> Maintain Security Settings for Payment Cards .

Enhancements There are two Business Add-Ins available to enhance the current operation:

Read Payment Card (PYCD_ESOA_PAYTCARDBYIDQR), enhancement spot PYCD_SPOT_ESOA_PAYT_CARD Method INBOUND_PROCESSING of this BAdI is processed at the beginning of the operation. Using this method you can run checks and modify the input data.Method

OUTBOUND_PROCESSING is processed at the end of the operation. Using this method you can modify the values in the response message before they are sent to the consumer.

Mapping of Payment Card Type (BSBP_ESAMAP_PAYMNTCRDTYPE), enhancement spot BSBP_ESAMAP_PAYMNTCRDTYPEUsing Method MAP_EXT2INT, you can implement your own value mapping for the external field TypeCode to the payment card type (data element CC_INSTITUTE) in the SAP Buisness Suite back-end system.Using Method MAP_INT2EXT, you can implement your own value mapping for the payment card type (data element CC_INSTITUTE) in the SAP Business Suite back-end system to the external field TypeCode.

1.13.2 Utilities Business Partner Data Management

Utilities Business Partner Data Management allows a company to manage all data for market participants in the Utilities sector that is required to control its business processes, such as grid usage requests, invoicing, payment processes, and so on.

(22)

Technical Data

Entity Type Process Component

Software Component Version ESM ERP 606

Technical Name UtilitiesBusinessPartnerDataManagement

Namespace http://sap.com/xi/ESM/ERP

Business Context and Use

The Utilities Business Partner Data Management process component is used for applications in the Utilities industry to support divisions such as electricity, gas, and water. Market participants in both regulated energy markets and liberalized energy markets can use this process component. In liberalized markets, the market participant distributor performing the metering point administrator role, as well as the market participant supplier performing the roles of balance supplier and customer service responsible, need to operate on the basis of data for the Utilities business partner.

The process component content can be applied by front end or back end users working with data in the Utilities business partner environment. Utilities business partner data consists of the address, communication identification and role-specific data for the service provider – distinguished in more detail by market roles - offering market services. The content of this process component enables you to search for and identify the Utilities business partner, and respectively, the service provider data.

The process component is applied when a balance supplier registers with the metering point administrator (performed by the distributor) for grid usage to supply the newly acquired or moved-in customer (see process component Utilities Grid Usage Processing). It can also be used in a situation where a new meter administrator takes over the administration and operation services for a customer's meter.

Notes on SAP Implementation

The target group must run the IS-U back-end application component to use the operations found in Utilities Business Partner Data Management .

1.13.2.1 Utilities Service Provider

A Utilities Service Provider is a market participant in the utilities sector which offers services at a Utilities Point Of Delivery.

Technical Data

Software Component Version ESM ERP 606

Technical Name UtilitiesServiceProvider

Business Context and Use

A Utilities Service Provider can be represented by various market participants in the utilities industry supporting divisions such as electricity, gas and water. Examples of these market participants are a distributor, supplier, meter operator or metered data responsible at distribution grid level or a transmission system operator, and wholesaler/ shipper at transmission grid level. These market participants offer specific market services such as grid usage, energy supply, meter installation & maintenance and measurement data provision. These market services are represented in the application as services at the Utilities Point Of Delivery.

The business object Utilities Service Provider contains master data to be applied for inbound and outbound communication, address data and identification data required to identify the market participant in market communication.

Notes on SAP Implementation

All service interfaces for this business object can only be used if the business function set Utilities is activated.

1.13.2.1.1 Manage Utilities Service Provider In

An interface used to manage data for a utilities service provider.

Technical Data

Category A2X

Direction inbound

(23)

Business Context and Use

The Manage Utilities Service Provider In inbound service interface contains an operation that reads the basic data from the business object Utilities Service Provider, such as address or communication data using the service provider external identification.

1.13.2.1.1.1 Read Utilities Service Provider Basic Data

To read utilities service provider basic data by ID.

Technical Data

Software Component Version IS-UT 606

Technical Name UtilitiesServiceProviderERPBasicDataByIDQueryResponse_In

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

Application Component IS-U

Web Service Definition (Back End) ISU_SERVPROVBDIDQR

Category A2X

Direction inbound

Mode synchronous

Idempotency no

Business Context and Use

In liberalized energy markets, different market parties query master data to handle end customer processes.

This service operation provides the master data for a service provider. This master data is relevant for communication in liberalized energy markets and can be used in different processes, for example, inbound validation of the service provider, determination of information for outbound processing, providing information for portal applications, and so on.

Related Operations

The Find Utilities Service Provider by Identification inbound operation allows you to find the list of roles and identifications for a service provider.

Features

The query returns the information related to the service provider, such as a list of roles and a list of identification with the code list agency if this has been defined. It also provides master data such as person name or organization name, address information and address and dependent communication data for the business partner assigned to the service provider. The query status is added to the log to indicate the success or failure of the operation.

Error Handling

The operation returns an error message in the log if no input is provided or this input is incorrect.

Message Types

UtilitiesServiceProviderERPBasicDataByIDQuery_sync UtilitiesServiceProviderERPBasicDataByIDResponse_sync

Notes on SAP Implementation

Enhancements

The new kernel-based BAdI definition ISU_SE_SERVPROVBDIDQR is available in the enhancement spot ISU_SPOT_SE_SERVPROV for this inbound operation, and is used to extend the customer-specific logic used to map the application data.

1.13.2.1.2 Query Utilities Service Provider In

(24)

1.13.2.1.2 Query Utilities Service Provider In

An interface used to find data for a utilities service provider.

Technical Data

Category A2X

Direction inbound

Business Context and Use

The Query Utilities Service Provider In inbound service interface contains an operation that is required to query for the Utilities Service Provider business object using its external identification.

1.13.2.1.2.1 Find Utilities Service Provider by Identification

To find a utilities service provider by identification.

Technical Data

Software Component Version IS-UT 606

Technical Name UtilitiesServiceProviderERPSimpleByIdentificationQueryResponse_In

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

Application Component IS-U

Web Service Definition (Back End) ISU_SERVPROV001QR

Category A2X

Direction inbound

Mode synchronous

Idempotency no

Business Context and Use

The Find Utilities Service Provider by Identification service operation is used in the liberalized utilities markets where different market participants collaborate with each other.

This service operation can be used to verify a market participant (service provider) using their external identification in a market message.

Related Operations

The Read Utilities Service Provider Basic Data inbound operation is used to read the master data for the business partner assigned to the service provider using its internal ID.

Features

This inbound operation performs a query to find the Utilities Service Provider by providing its external Identification (mandatory) and service type (optional). If the code list agency is defined for the requested external identification, it should also be provided.

The query returns the information related to the service provider: Service provider ID, list of role and list of identification. The query result is also recorded in the log, for example, ‘Successful processing’, when the service provider is found.

Error Handling

The operation returns error messages in the log if no input is provided or the input is incorrect.