Introduction

A public utility (usually just utility) is an organization that maintains theinfrastructure for a public service.
State provision of utility services (like electricity, gas, water, district heating, waste management etc.) often resulted in inefficiency andpoor service quality.
Trend towards liberalization, deregulation and privatization of public utilities encouraging competition among private players.

Business benefits of SAP for Utilities
Enhances Efficiency of business processes
o mass processing of consumption and customer-related financial data
o efficient and automated exchange of data (deregulation processes) with market participants, enabling supplier switching as well as payment and settlement processes
o Increased Asset Usage and Reliability
o integrates information and processes from finance, procurement, maintenance, operational safety, and workforce management
o integrates SAP solutions, legacy systems, plant and geographic information systems, outage management systems, and automated meter-reading systems
o Optimized procurement – reduced material inventory and efficientcollaboration with contractors and suppliers
o Improved Customer Relationship Management
o delivers personalized services
o effective tools for designing and executing marketing campaigns
Useful Transactions

EASY – Searches Transaction Codes in IS-U.
EC20 – Front Office
EC25 – Data Environment
EPRODCUST – Master Data Template
ECRMREPL – IS-U Contract Error Monitor
EMMACL – Clarification Case List (EMMA Case)
EMIGALL – IS-U Migration: Workbench (Data Migration Tool; Conversion)
EQ81 – IS-U Migration Workbench: User Handbook

Master Data – remains unchanged over a long period of time

Business Master Data

Business Partner: Business Partner can be a person, group or organisation with whom the utility company has a business relationship.
Useful T-codes:
BP – Maintain Business Partner
FPP1/2/3 – Create/Change/Display Contract Partner
Tables:BUT000
Fields:PARTNER(10)

Contract Account: A contract account groups together all of a business partner’s contracts to which the same payment and dunning data applies. It is an account through which the financial transactions between a customer and a utility company are managed (stores payment transaction data).
Useful T-codes:
CAA1/2/3 – Create/Change/Display
Tables:FKKVK, FKKVKP
Fields:VKONT(12)

Contract: A contract is an agreement between a utility company and a business partner relating to a utility service. It forms the basis for billing. Created during move-in process. It is specific to one Division.
Useful T-codes:
ES20/21/22 – Create/Change/Display
ES27/8 – Change/Display Contracts for Contract Account
Tables:EVER
Fields:VERTRAG(10)

Move-in: A contract is created and allocated to an installation
Useful T-codes:EC50/1/2E (Create, Change, Display), EC53E (Reverse)
Tables:EEIN (Cont. Acc.), EEINV (Contract)

Move-out: A contract with a customer is terminated
Useful T-codes:EC55/6/7E (Create, Change, Display), EC58E (Reverse)
Tables:EAUS (Cont. Acc.), EAUSV (Contract)

Technical Master Data

Connection Object: Connection Object is a building, piece of property or other facility that is connected to the supply grid.
A connection object is allocated an address. It links premises, device locations etc. to a postal regional structure.
Useful T-codes:ES55/6/7 – Create/Change/Display
Tables:EHAUISU
Fields:HAUS(30)

Premise: A premise is an enclosed spatial unit (such as an apartment or a factory) to which a utility service is supplied. It is allocated to a Connection Object.
Useful T-codes:ES60/1/2 – Create/Change/Display
Tables:EVBS
Fields:VSTELLE(10)

Installation: The connection between premise, devices, and contract is referred to as an installation.
An installation is allocated to a single contract.
Used to group together all devices that are allocated to same premise, belong to same division and are to be billed together.
Several utility installations can be allocated to one premise (for different divisions, for example). The premise is therefore not related to one specific division. A deregulated scenario exists if more than one utility installation of the same division is allocated to a premise.
The installation stores the billing properties for one or more devices at a premise

Useful T-codes:
ES30/1/2 – Create/Change/Display
Tables:EANLH(time slice), EANL
Fields:ANLAGE(10)

Device Location: Device Location is a location in a Connection Object where any number of
devices (across divisions) is installed. The device location provides information on the physical location of the device
Usefu T-codes:
ES65/6/7 – Create/Change/Display
Tables:EGPLT, EGPLTX
Fields:DEVLOC(30)

Device: Devices are physical objects. E.g. Counting Device (meter), controlling device (ripple control receiver), data processing device (converter), device with protective or adjustive functions (pressure controller) etc.
Useful T-codes:
EG41,2/3/4 – Device Modification/Display /Create
Tables:EGERS
Fields:GERAET(18)

Point of Delivery:
useful T-codes:
EEDM09/10/11 – Point of Delivery Create/Change/Display
Tables:EUITRANS, EUIINSTLN
Fields:INT_UI(22), EXT_UI(50) – POD ID
Intercompany Data Exchange (IDE):

T-codes:
EEDMIDESERVPROV01/2/3 – Service Provider Create/Change/Display
IW52/3/4 – Service Notification Change/Display/Create
EDATEXMON01 – Monitoring of Data Exchange Tasks
ESWTMON01 – Monitoring of Switch Documents
WEDI – SAP Easy Access IDoc and EDI Basis