Brief IS-U

SAP AG 1999

Customerservice &

billingGenerationGeneration TransmissionTransmission DistributionDistribution

Consumptionentry

Consumptionentry

InvoicingInvoicingContractA/R & A/PContractA/R & A/P

Meter & Device Management

Work Management

Servicebilling

Consumptionbilling

Consumptionbilling

Installationservices

All customer-related business processes

InvoicingInvoicing

MarketingMarketing& Sales& Sales

Particular business processesParticular business processesCustomer Relationship ManagementCustomer Relationship Management

IS-U/CCS

PMMM

SD

FIFI

CRM

Functional Scope of the IS-U System

SAP AG 1999

FIFISDSD

AMAMMMMM

GIS,CAD,SCADA

GIS,CAD,SCADA

MMMMPM/PM/CSCS

SDSDCOCO

Sales & Distribution


Contra

ct

A/R +

A/P

(FI-C

A)Contra

ct

A/R +

A/P

(FI-C

A)

Billing/Invoicing

Billing/Invoicing

Installation

ServicesInstallation

Services

Cons

umpt

ion

Entry

Cons

umpt

ion

Entry External

ConsumptionEntry

Systems

ExternalConsumption

EntrySystems

ExternalSales

Systems

ExternalSales

Systems

SAPBusinessPartner

SAPBusinessPartner

Customerinformation system

IS-U components

Standard SAP components

External systems

FinancialAccountingFinancial

Accounting

DeviceManagement

DeviceManagement

CCUUSS TTOOMM EERRPlant Maintenance& Customer

Service

Plant Maintenance& Customer

Service

Asset Management &Materials ManagementAsset Management &Materials Management

CCAARR EE && SS EE RR VV

II CCEE

IS-U/CCS as an integratedcomponent of the

SAP enterpriseinformation system


SAP enterpriseinformation system

PMPM

IS-U/CCS - Integration Model

Central business partner model (R/3) => the customer is the central data object. Cross-application component FI-CA for Contract Accounts Receivable and Payable

Designed for processing a large volume of postings from sales and collection activities for a large number of customers

Industry-specific enhancements for the utilities industry enable the use of the standard R/3 component PM/CS (Plant Maintenance/Customer Service).=> ideal prerequisites for processing service activities

PM/CS is integrated with the following components:SD: Management of customer quotations and orders, and also execution of billingCO: Allocation and settlement of costs related to service activitiesMM: Processing of material requirements and goods movement related to service activities

The results of service billing can be transferred to IS-U invoicing; further processing of debits occurs via FI-CA.

Material master records are managed in MM at the same time as device categories in IS-U; purchasing and stockholding of devices are processed using MM components.

SAP AG 1999

Deregulation-enabled functionality Integration of application areas

Homogeneous interaction between accounting and core logistics processes

Business processes for all areas Shorter lead times for business processes

Flexibility Can be adapted to local deregulation rules Can be implemented in all types of companies Supports all types of service Enables development of individual business strategy

Customer-orientation User friendly Oriented to business processes Competition-oriented Informative Communicative

Open architecture

The Strengths of mySAP Utilities

SAP AG 1999

CallCall--center functionalitycenter functionality Faster and more direct access to all relevant information and

transactions required during contact with customers is admissible. This includes customer overviews, changing master data, displaying bills, entering meter reading results, account information and so on.

Work items allow callbacks and outbound campaigns.

Master data templateMaster data template Product modeling on the basis of configured materials and

pricing in SD. The master data generator is used to post-edit campaigns.

ISIS--U content for BWU content for BW Sales statistics, consumption statistics, transaction statistics

and so on

Sales and Marketing in IS-U/CCS (1)

SAP AG 1999

IS-U/CCS supports customer-oriented core business processes of utility and service companies.

IS-U/CCS is an integrated component of the SAP enterprise information system.

IS-U/CCS can be used for billing and managing standard divisions as well as additional new services.

IS-U Overview: Unit Summary

SAP AG 1999

Basement

Apartment 2

Apartment 3

Apartment 1 Hall

Service Connection: ElectricityService Connection: GasService Connection: WaterSupplyGrid

Street

Connection Object

= Premise

Device locationBasement

Device locationBasement

Device locationHall

Device locationHall

Businesspartner

Contract 1:Electricity

Contract 1:Electricity

Contract 2:Gas

Contract 2:Gas

Contract 3:Water

Contract 3:Water

Installation 1: Electricty

meter

Installation 1: Electricty

meter

Installation 2:

Gas meter

Installation 2:

Gas meter

Installation 3:

Water meter

Installation 3:

Water meter

Contractaccount

Contractaccount

The IS-U House

SAP AG 1999

• Name• Address• Personal data• Communication

• Name• Address• Personal data• Communication

• Payment transactions• General data (account class,social security,creditworthiness,driver's license no.,employee class)• ...

Prospect

• Type of company• Division license• Work field• License• Main utility company• Identification• ...

Installer

• Branch of industry• Relationships• Contact history• ...

Business partnerBusiness partner

Contract partner

Roles of the Business Partner

SAP AG 1999

General data Dunning/payment data

Contract

Account

Dunning data Dunning control Dunning letter recipient Dunning block reason

Outgoing payments

Payment method Bank details Alternate payee

Account assignment

Where-used list for Ols Planning group Account determination Settlement category

Incoming payments Payment method Bank details Alternate payer

Control Alternative bill recipient Paid by collective bill

account Additional bill

General data Account name Account no. in legacy

system Terms of payment Tolerance group

Contract Account Data

SAP AG 1999

General Data Move-In/Move-Out Data

ContractContract

Billing Data• Joint Invoice• Billing block reason• Outsorting group

Budget BillingData

• Budget billingAdjustment

• Budget billing cycle

Acct Assignment Data• Account determination ID• Cost center• Business area

GeneralContract Data• Contract account• Division• Company code• Plant/comp. consum.• Statistics group• Authorization group

Scheduling Data• Contract start/end date• Renewal dates• Cancellation dates

Data Relevant to Billing

Deregulation Fields

Contract Data

In the Statistics group field, you specify a statistics group for a contract. It is used for determining data for sales statistics.

The authorization group prevents unauthorized access to specified objects. To be able to carry out any activity protected in this way, the user must have authorization for both the activity and the authorization group.

Data relevant to budget billing (the budget billing cycle, for instance) maintained in the contract overrides the default values defined in the portion or the Customizing settings.

The outsorting group determines which validations are to be carried out in billing. A contract can also be outsorted manually.

The meter reading block reason specifies why the contract has been blocked for meter readings. If you make an entry in this field then the contract can no longer be billed. The contract will not be released again for billing until you enter a billing release reason (the billing release reason overrides the billing block reason).

A business area is an organizational unit that covers a restricted area of activity/responsibility in your company. Value movements entered in Financial Accounting can be attributed to this business area for the purposes of external accounting.

Scheduling data is provided mainly for information purposes. It allows you to display information on when a contract was signed or cancelled, for example.

SAP AG 1999

PM data IS-U data

ConnectionObject

Additional Data• Structure/equipment list• Account assignment• Classification

Plant Maintenance• Structure• Maintenance planning

plant• Maintenance planning

group

Location Data

• Maintenance plant• Location description• ABC indicator

General

• Description• Processing status• Notes

Attributes• Regional structure group• Authorization group

Address• Street, house number• Postal code, city• Political regional structure

Connection Object Data

SAP AG 1999

General data Relationships

Premise

Additional Data

Notes Update log

Attributes Premise type Owners Number of occupants

Location Data

Storey Room number Location description

Connection Object Forms the link between

the premise and theregional structure

Technology

Can be assigned to adevice location

Installation

Can comprise severalinstallations to be billed

Premise Data

SAP AG 1999

General data Relationships

Additional Data Installation type Guarantee of supply Notes Update log

Control Data Supply or consumption Definition of base period Meter reading control

Process Data Current premise Current business partner Current contract

Installation

Billing Rate category Rate data for devices

and registers Reference value

Regional Structure Linked via the premise

and connection object Override default meter

reading unit

Business Partner

Conclusion of the contractwith the business partner

Installation Data

SAP AG 1999

Point of delivery

Technical• Register

Header data• Structure category• History

Point of delivery ID

• Description• Point of delivery type• Point of delivery role

Deregulation• Installation• Premise• Service type• Grid (distributor)• Settlement unit

Point of Delivery Data

SAP AG 1999

IS-UIS-U

FI-CAFI-CA

SD, CS, PMSD, CS, PM

Cross appl.Cross appl. Contractaccount

Businesspartner Regional

structure

Connectionobject

Connectionobject

Connection

Device location

Premise

Contract(utility)

Installation

Device

Meter reading

Integration withLogistics

Device category

Point of delivery

Business Objects in IS-U/CCS

Service

SAP AG 1999

Efficient user interface, short training period

All common service functions directly accessible

Entry with incomplete data and comprehensive search help

User-specific adjustment of the interface and of the available business processes

Connection to external communication systems (e.g. Computer Telephony Integration, Internet)

Customer Interaction Center: Requirements

SAP AG 1999

Carry OutFront

Office Processesif Required

IdentificationIdentification InformationInformation

Supported by:

Predefined and company-specific business processes (for example name changes, changes to bank details, move-in processing, interim billing, various types of complaints)

Typical Uses of the CIC: Front Office Process

Unit 1: Identification (selection area)Task: Selects data using flexible search criteria.

Unit 2: Navigation areaTask: Provides specific information in response to customer inquiries. Starts complex business processes, for example SAP Business Workflow.

Unit 3: Application areaTask: Provides overview pages containing inbox for SAP business workflow, CIC contact management, and so on.

Unit 4: Action boxTask: Calls specific business processes.

SAP AG 1999

Move-in

Installation

Contract

Contractaccount

Businesspartner At move-in, a contract is

concluded for each installation selected at one or more premises

Move-In Definition

SAP AG 1999

Connection object

Connection object

PremisePremise

InstallationInstallation

DeviceDevice

The following technical master data must be entered before move-in:

Connection object

Premise

Installation

The device can be installed before move-in, but this is not a prerequisite.

Move-In: Prerequisites

0.2

SAP AG 1999

Move-out Move-outcomplete

Customer reportsmove-out

Contact data

Contract Final meterreading results

Final billing

Budgetbillingplan

Move-outconfirmation

Customermoves out

ContractBank details 1

Payment method 1Alternative payer 1....FI -CA document 1FI -CA document 3

31July

BB amount$250

X

X

The Move-Out Process

Essential steps for move-out: Identify and choose customer and contract Enter move-out date Enter final meter reading results

Optional steps for move-out: Add contact data Edit the customer moving out and the contract account Prepare and carry out final meter reading Carry out final billing immediately and print and issue final invoice Create move-out confirmation

IS-U will do the following for you: Terminate the contract Stop any budget billing collection Suspend any current dunning procedure Change any dunning procedures that may affect open items

In the move-in/out transaction, you have the following processing options: Move-in/out for premise.You can process the move-out or move-in of two different business

partners into one premise. Move-in/out for business partner.You can process a move-out for a business partner from

one premise and their move-in to another premise.

SAP AG 1999

Business partner

Business partner

Contract account

Contract account

ContractContractContract

Connection object

Connection object

PremisePremise

InstallationInstallation

DeviceDevice

Move-in

Move-In: Master Data

SAP AG 1999

Acquisition, planning, calculation, execution of internal and external work orders

Creation of bills for customers

Examples: Creation and extension of service connections

Energy consulting

Unscheduled meter reading

Disconnection and reconnection

Maintenance

Repairs

Installation, extension or removalof technical equipment

What Areas does the Work Management System Cover?

The day to day business of a utility company includes processing a large number of work orders. The orders must be accepted, planned, calculated, executed and when necessary, billed to a customer.

There are two different types of work orders; internal work orders and external work orders (which relate to Customer Service). External work orders are mapped with service orders in the Customer Service (CS) component. Internal work orders are mapped with plant maintenance orders in the Customer Service (CS) component.

0.3

SAP AG 1999

Technical installations(equipment)

0539802

125.256.01

0716192

0539802

125.256.01

0716192

Connection obj.(func. loc.)

Premise

Connection (equipment)

Premise

Devices (equipment)

Dev. loc.(func. loc.)

Transformer(equipment)

Connection Object

The technical installation is division-dependent. A maximum of one technical installation can be created for each division in each

premise. An equipment is created in PM automatically. Since the technical installation is a piece of equipment, it can be subject to regular

maintenance, for example.

0.4

SAP AG 1999

For service orders only

Entry/notification

Planning

Release

Printout

ConfirmationConfirmation

Technical completionTechnical completion

InvoicingInvoicing

Billing Billing

CommercialCommercialcompletioncompletion

Execution

Sequence of Order Processing

Processing starts when a customer or employee reports an outage, disruption or other request (such as a modification request). An order can be created directly, or on the basis of a notification.

Typical planning tasks include defining work processes, reserving replacement parts or defining working hours.

The order is then transferred for scheduling and control. Availability is checked, capacity required is provided and the necessary shop papers are printed.

Execution includes obtaining replacement parts from the stock and actually executing the order.

Once work is complete, the actual times required to complete the work are recorded. Other technical information is also entered to document repairs and define the status of the technical system. The order is then billed in Controlling.

Billing is performed prior to invoicing for a service order and a bill is created for the customer.

0.5

SAP AG 1999

IS-U/CCSIS-U/CCS

SD

PM/CS

FI-CAFI-CAFront officeFront office

OR

IS-U/CCSIS-U/CCS

W o r k f l o w M a n a g e m e n tW o r k f l o w M a n a g e m e n t

Workorder

Invoicing:installation

Supplyservices

Request forquotation

Quotation Order Billingrequest

Invoicing:Installation

services

Document

1

2

4

5

6

7

8

9

10

Qty Ordered

TotalSALESPERSONDATE

Sales Tax

Subt otal

TotalPriceDescriptionQty Shipped

P.O. #:

PremiseCustomer

UTILITY BILL

CustomerCustomer

3

The Installation Services Process

Management of a service connection could be performed as follows:(1) A customer requests a quotation for the installation of a service connection. The customer

service representative identifies the customer in the CIC or creates the corresponding customer master record (if the customer is not already defined in the system).

(2) The customer service representative creates a customer quotation in the Sales & Distribution (SD) component.

(3) A quotation notification is created and sent to the customer. A service order can be generated automatically in the background in the CS component (6).

(4) The customer accepts the quotation.(5) The customer service representative generates a sales order. Order items can be

automatically transferred from the quotation.(6) A service order is created automatically in the background if this was not created with the

quotation (3).(7) The service connection is made on site.(8) If the service is invoiced according to consumption (i.e. if the actual costs incurred are to

be billed), a billing request is created in the SD component. (9) The invoice is triggered and posted in the SD component. If the service is not invoiced

according to consumption, but on a flat rate, the invoicing procedure is based on the sales order. As an alternative to invoicing in SD, it is also possible to create the invoice for the service in IS-U/CCS and to offset it with consumption billing.

(10) The invoiced amount is then entered as a debit amount in the FI-CA component.

0.6

S A P A G 1 9 9 9

A c c e p tq u o t a t i o n

C r e a t e q u o t a t i o n

C r e a t e s e r v i c e o r d e r

C r e a t e s e r v i c e c o n n .

C u s t o m e r

A g e n t

A g e n t

A g e n t

A g e n t

C u s t o m e r

S y s t e m

T e c h n i c i a n

C r e a t e c u s t o m e r o r d e r

C o n f i r m s e r v i c e o r d e r

P a y m e n t T r i g g e r i n v o i c i n g

W o r k f l o wW o r k f l o w

C r e a t e S e r v i c e C o n n e c t i o n

The "service connection" business process (such as new installation of a service connection or extension of an existing service connection) can be further divided into three subprocesses: Management of quotations Order processing Order completion and invoicing

The order processing subprocess includes the external customer order and the internal service order.

0.7Interfaces

0.8

SAP AG 1999

SCADASCADA

AM/FMGISAM/FMGIS

Decentralized resource planning

Decentralized resource planning

Outage analysisOutage analysis

WorkManagement

WorkManagement

R/3Standard

Applications

Service orders confirmations

Outagenotificationsand orders

Outageconfirmations

Transformer stationoutages

Connection information

Situation monitoring

Geographical data

Service ordersCompletion confirmations

MDI Mobile devicesMobile devicesCustomer

service

Customer

service

Possible Configuration of an Interface Scenario

MDI: Mobile Data Interface SCADA: Supervisory Control and Data Acquisition GIS: Geographical Information System AM/FM: Asset Management / Facility Management

Device Management

SAP AG 1999

Device category as the basis for device definition Device category data and attributes Integration in the standard R/3 System

Devices and registers Device data Integration in the standard R/3 System Register data

Device lifecycle Device inspection

Sample lot Certification

Contents:

Device Technology

0.9

SAP AG 1999

=> Specific device data Device number/serial number Activity dates, such as installation, removal, or meter

reading Certification and maintenance data "Device" corresponds to "equipment" in the Plant

Maintenance (PM) component

=> Features of similar devices Definition of technical device data Recording of inspection and certification periods The device category corresponds to the material in

the MM component

=> Basic functions of device categories, such as: Meters Transformers Pressure regulators

Basic device cat.Basic device cat.

Device category 1Device category 1

Device category 2Device category 2

Device 1Device 1

Device 2Device 2

Device 3Device 3

Modeling of Devices

Examples of basic device categories: Meters measure consumption Transformers convert. (Example: electrical voltage) ARCRs (audio frequency ripple control receivers) transmit information via the electricity

grid by means of audio frequency modulation. Remote meters measure consumption from a distance Counters calculate heat quantities generated in district heating Correctors calculate standard cubic meters from gas values Pressure regulators adjust gas pressure Sensors act as pulse generators, e.g. temperature sensors

0.10

SAP AG 1999

IS-UDevice management

IS-UDevice management

Device categoryDevice category

DeviceDevice

LogisticsLogistics

MaterialMaterial

EquipmentEquipment

Integration with Logistics

IS-U functions of device management include: Technical data such as the register group, the input/output group, and command group and

so on. Installation, as well as removal and replacement of devices Installation structure for modeling devices and register relationships, in addition to rate data Organization and carrying out of meter readings in the service territory Inspection: sampling procedure, certification, periodic replacement

Integration of IS-U/CCS Device Management with the standard R/3 Logistics component makes it possible to use the following: Inventory Managment (MM-IM component) Purchasing (MM-PUR component) Warehouse Managment (MM-IM and MM-WM components) Plant Maintenance (PM component) Classification system

0.11

SAP AG 1999

MaterialMM

Device categoryIS-U

Input/output group

Register groupRegister group

Winding groupWinding group

Command group

Informative

Possible Elements of the Device Category

Function-relatedFunction-related

Certain functional element groups are required, depending on the basic device category. Examples: Devices of the basic device category METERS must be allocated to a register group.

However, an input/output group may be assigned for technical descriptions of the available device interfaces, if desired.

Allocation of a winding group in which the billing data is recorded is obligatory for devices of the TRANSFORMERS basic device category. An input/output group can also be maintained for information purposes (such as for service technicians), if required.

Data on device category elements can be arranged according to division category (the reactive current/active current indicator can for instance only be maintained in the register group of the electrical division).

0.12

SAP AG 1999

A device is an instrument that is used to measure consumption, process data, or control and protect other instruments.

Devices are managed in the Plant Maintenance (PM) application component as pieces of equipment with serial numbers.

Device

Device category

Definition of Devices

0.13

SAP AG 1999

PM IS-U

Plant maintenance• Maintenance plant• Maint. planning plant• Maint. planner group• Main work center

Processes• Maintenance orders• Service orders• Messages• Capacity planning

General• Inventory number• Weight/volume• Reference data• Manufacturer data• Stock information

General• Device category, basiccategory

• Lock status• Change documents• Time slices

Device-specific data• Group data, prod. year• Manufacturer, cat.desc.• Ownership status• Certification data

Processes• Installation and removal• Modification and disconnection

• Certification• Meter reading

Device

• Material and serial no.• Equipment category and number

• Status

Header data

Device Data

The device master record is divided into various sections (tabs): General data: technical data, reference data, manufacturer data Location data: area assignment and account assignment elements IS-U data:

Technical data: register group, winding group, command group (depending on the device basic category)Certification /inspection data: year of certification, certification status, lot, year of replacement, inspection statusProcesses: installation, removal, modification, and disconnectionMaster data: business partners, connection object, device location, location, premisesMeter reading results, designated plantsSerialization data: allocated to material and serial number with stock information, plant and location.

When devices are moved (e.g. goods receipt, goods issue, installation, removal), the equipment status is updated (ESTO, AVLB, INST). The status of the device informs the user that a certain business process has been performed. (Example: ESTO means that the device was entered in the system via a goods receipt posting and is available in a warehouse).

0.14

SAP AG 1999

Technical data Process data

General• Register category• Register type (time zone)• Pre-decimal places• Decimal places

Technology• Quantity unit• Register code, such asreactive energy or active power

• Display type, transformer

Meter reading• Number of meter readingresults per meter reading

• Indicator: nonmetering register

Register relationships• Relationship type• Relationship register• Operation code

Meter readings

• Recorded meter reading • Estimated meter reading• Multiple allocation

Meter reading• Reason• Type of reading, meterreader

• Date• Status

RegisterRegister

Registerconfiguration

Sample registerrelationship

Register Data

Examples of register relationships: Active/reactive relationship Serial switching relationship On-peak/off-peak

relationship Control relationship VCF relationship (thermal gas billing) VCF calculation relationship (thermal gas billing)

You can assign individual validations to each register relationship to check the meter reading results.Example: Meter reading results from two registers that are connected by a control relationship can only differ by a maximum of 1%. If this tolerance is exceeded, the meter reading result is not accepted and is assigned the status "implausible".

0.15

SAP AG 1999

Billingdocument

(Utility supply)

FI-CAdocument

FI-CAdocument

IS-UIS-U

FI-CAFI-CA

Cross appl.Cross appl.

ContractaccountContractaccount

Businesspartner Regional

structure

Connectionobject

Connection

Device location

Premise

Contract(Utility supply)

Installation

Device

RegisterIntegrationwith Logistics

Devicecategory

MRservice

Register group

Point of delivery

Central Data Objects - Integration in Logistics

0.16

SAP AG 1999

MMMM

ISIS--UU

Device managementInstallation

PurchaseorderPurchaseorder

GoodsreceiptGoodsreceipt

Goodsissue

GoodsissueTransferTransfer

InstallationInstallationInspection/

certification/reprogramming

Inspection/Inspection/certification/certification/

reprogrammingreprogramming

Removal/replacement

Removal/replacement

RetirementRetirement

PMPMPurchase

requisitionPurchase

requisition

Device Life Cycle

Devices are created in an integrated system using standard R/3 components, such as Purchasing (MM-PUR), Inventory Management (MM-IM) and Plant Maintenance (PM). Devices are created as pieces of equipment in the system by posting a goods receipt for any number of devices of a particular device category. The entire goods procurement process can be performed in an optional first step (purchase requisition ordering and so on). A prerequisite is that the device category has already been created and therefore exists as a material master in the MM component. The serial number profile of the material master (in Customizing) ensures that the device in question is supplied with the necessary IS-U data.

If the Materials Management (MM) component is not implemented, it is also possible to create devices directly in IS-U/CCS. However, IS-U/CCS does not provide inventory management functionality.

Although device installation is performed within IS-U/CCS, it is, however, based on a modified version of the PM component.

0.17

SAP AG 1999

MMMM

Purchasing: purchase orders, inquiries/quotations, outline agreements Warehouse logistics: transport, stocktaking, transfer posting Inventory management: goods movement, reservation Valuation, stocktaking, material requirements planning

PMPM Maintenance of technical objects and equipment Work planning, maintenance planning Maintenance processing

CSCS Service contracts: contracts, maintenance plans Service processing: notifications, orders, completion

confirmations Service planning: scheduling, work plans

Specification of the device: device category, device Installation: installation, removal, replacement, installation structure Meter reading: organization, meter reading orders, entry of meter

reading results Inspection and certification: internal or external periodic replacement

procedure or sampling procedure

IS-UIS-U

Documentation for the Device Lifecycle

0.18

SAP AG 1999

Connectionobject

Device location

Device

The device location is the location in the connection object that is independent of a division and in which any number of devices can technically be installed.

Executeserviceorder

Determinedevice location

Definition of the Device Location

0.19

SAP AG 1999

Device location

Reference to premise

• The device location can be allocated to a premise if required

Integration with PM• The device location is

defined as a functional location below the connection object

Independent of division

• Installation location fordevices of all divisions

• Installation location forall device categories

Location data• Exact location and

location supplement• Long text• Link to regional structure

Device Location Data

Executeserviceorder

Determinedevice

location

The following steps are performed automatically in the background for a device replacement: Billing-related removal of the old device: This terminates the business relationship between

the device and the business partner's installation (and therefore the contract). Technical removal of the old device: This removes the link to the device location, (and

therefore to the connection object). All existing register relationships are terminated and the current time slice for the device is removed. At the same time, a new time slice begins. The status in the device master record is changed from EEGB (equipment installed) to EFRE (equipment free).

Technical installation of the new device: The connection of the new register to the device location (and therefore the connection object) is established. The device receives the status EEGB. At the same time, a new time slice is opened for the device, beginning on the installation date. Any register relationships are transferred from the old device to the new meter.

Billing-related installation of the new device: The new device is connected to the business master data (installation, contract, business partner). Data that is relevant to rates (such as the rule for determining the settlement price, rate data at device and register level, information about extrapolation of consumption values) is transferred to the new device.

Processing steps that are performed automatically for a device replacement can also be performed separately (for instance by different customer service representatives). Individual transactions, such as technical installation, billing-related installation, and full installation (= both steps in one transaction) can be used to perform each step of the installation and removal processes separately.

0.20

SAP AG 1999

Businesspartner

Businesspartner

ContractaccountContractaccount

Installation1

Installation1

Installation2

Installation2

Contract 2(Company code 2)

Distribution and customer service


Distribution and customer service


Generation andtransmission


Generation andtransmission

PremisePremise

DevicelocationDevice

locationConnection

objectConnection

objectDevice 1

Billing-relatedinstallation

Technicalinstallation

Billing-relatedinstallation

Technical and Billing-Related Installation

Devices can be allocated to several installations from a billing perspective (billing-related installation). However, each device can be allocated to only one device location from a technical point of view (technical installation).

In the example above, the utility services of the division are divided into two areas, each of which is supplied by a different service provider. These two basic services are "generation and transmission'" and "distribution and customer service". The contracts for each of these basic services are managed under different company codes. This model clarifies how deregulated energy supply can be reflected in IS-U/CCS. The billing-relevant data in the utility installation and in the installation structure can be established individually for both contracts. Since one contract exists per installation, a separate installation in the relevant division is created for each contract. Accordingly, any meters installed are allocated twice from the point of view of billing. When both contracts are managed in the same system, one of the companies can carry out billing and customer service on behalf of the other, or a third company can carry out these tasks for both companies. The customer then receives only one bill for both services and has one contact person for all queries.

0.21

SAP AG 1999

Supplygrid

Street

Electricity

Audio frequency ripplecontrol receiver

Device allocationRegister relationship

Electricity

Serial switching

Example of an Installation Structure

The installation structure comprises all technical and billing-related data for a utility contract. In the example above, switching between the two rates of the double-rate electricity meter is

controlled by an ARCR (audio frequency ripple control receiver). For information purposes, this is described in the system as a device allocation of the ARCR type. At the same time, one of the registers of the double-rate electricity meter has a serial switching relationship with another register. The consumption of the serial switching register (secondary register) is automatically deducted from the consumption of the main register during the billing run.

0.22

SAP AG 1999

Device allocations Register relationships

Reactive/activerelationship

Serial switchingrelationship

On-peak/off-peakrelationship

Control relationship

VCF relationship

VCF calculationrelationship

Customer-specific relationships

Audio frequency ripplecontrol receiver

Transformers

Pressure regulator

Customer-specificallocations

Technical Installation Structure

Device allocations describe relationships between installed devices. A device allocation is always composed of a controlling and a controlled device (Example: A calculation factor, which is taken into account in consumption billing, is defined in the installation structure at register level for the "transformer" allocation category).

In a reactive/active relationship, all active registers of a register category and all reactive registers of the same register category are added and the total is used to perform the cosine phi examination.

The serial switching relationship is automatically subordinate to all other relationships during meter reading and validation.

The on-peak/off-peak relationship describes the relationship between registers of different register categories (e.g. on-peak and off-peak registers).

In a control relationship, all registers are added and the totals compared with the designated control register.

The VCF relationship (gas division only) is needed for billing difference quantities that result from different meter readings for the operating volume meter of the corrector and another external operating volume meter.

The VCF calculation relationship (gas division only) is needed for billing difference quantities that result from different meter readings for the operating cubic meter meter of the corrector and another external operating cubic meter meter.

0.23

SAP AG 1999

Rate data

Relevance tosettlement price

Relevance to billing Price class Rate type Rate fact group Discount

Extrapolation data

Expected periodconsumption

Fixed consumptionvalues weighted linearly(absolute or relative value)

Billing-Related Installation Structure

Rate and extrapolation data are usually determined during maintenance of the installed device. However, these can be changed at any time under "installation structure" in the menu. During device installation (or afterwards), the "relevance to settlement price" indicator

determines whether a settlement price should be charged or not. If the "relevance to billing" indicator is activated at register level, a plausible meter reading

result is expected for billing. The price class can be defined at the device category, device, or register level. The price

class, together with the price level, determines the settlement price (e.g. meter rental) from the rate.

The rate type is maintained at device or register level and controls rate determination, together with the installation's rate category.

The rate fact group is also assigned at device or register level. The rate fact group contains specific values (e.g. constants) and/or keys (e.g. price keys) that are assigned to a rate.

Discounts can be assigned at register level for quantities and services ("register discount").

Period consumption is used in the extrapolation of meter readings when no representative meter reading results are available (such as for new customers).

0.24

SAP AG 1999

A customer telephones the customer call center to report his/her move-out The customer service agent enters the move-out

date and the meter readings

An implausible reading means that the utility company has to carry out a control reading

Meter reading processing Creation of meter reading order

Entry or estimation of meter reading results

Start of billing and invoicing Final billing, followed by invoicing

Meter Reading: Business Scenario

0.25

SAP AG 1999

Meter reading

UnscheduledScheduled

Indicator Predefined meter reading

strategy Date and area scheduled in

regional structure Resources can be planned

Process Create meter reading

schedule Specify meter reading

sequence Create mass meter reading

orders Enter results Check results Release for billing

Indicator There are special reasons for

the meter reading request, such as a move-in/out

Date and area cannot be scheduled

Meter reading cannot be planned

Process Create a single meter reading

order Enter consumption Check results Release for billing

Types of Meter Reading

0.26

SAP AG 1999

Regional structure SchedulingMaster data

Meterreading

unit

Businesspartner

Connection object

Premise

Account

Installation

Contract

CityCity StreetStreet Street sectionStreet section

Political structure

PortionPostal regional structure

Regional Structure and Scheduling

Portioning: Grouping of contracts that are to be billed together. You allocate a contract to a portion either directly in the contract or indirectly via the meter reading units entered in the installations.

Scheduling: Controlling and planning of the following processes:Meter reading order creationPeriodic billingBudget billing collection

Scheduling is managed at the meter reading unit and billing portion levels.

0.27

SAP AG 1999

MR unit A.3

Portion A

MR unit A.2

MR unit B.1

MR unit B.3

Portion B

MR unit B.2

MR unit B.4B

Portion C

MR unit B.5

MR unit C.3

AMR unit A.1

MR unit C.2

MR unit C.1

Portions and Meter Reading Units

A portion normally contains several meter reading units, which are structured according to location and/or scheduling requirements.

Meter reading units in a portion do not have to be located near one another; their grouping can also depend on other factors, such as billing conditions.

Example: Portions A and B represent different city districts consisting almost entirely of households

and small businesses (such as residential customers). Meter reading units in these portions are structured in such a way that they correspond to the daily work quota of the meter reader.

Since other meter reading cycles and billing conditions apply to nonresidential customers, major customers (such as industrial and business groups) within the area concerned are allocated to a separate portion (C). This portion consists of three meter reading units that are not in close proximity to each other. They are "islands" inside portions A and B.

The utility company bills residential customers periodically. Portion A is billed on June 15; portion B is billed on July 15.

Non-residential customers are billed monthly. This means that portion C is billed on June 15, July 15, and so on.

0.28

SAP AG 1999

PortionP_AUG01PortionP_AUG01

MR unitA_AUG01MR unitA_AUG01

P1P1Parameter recordParameter record

Schedule master records

A_AUG01 2002A_AUG01 2002

A_AUG01 2001A_AUG01 2001

A_AUG01 2000A_AUG01 2000

MR unitMR unitSchedule records

P_AUG01 2002P_AUG01 2002

P_AUG01 2001P_AUG01 2001

P_AUG01 2000P_AUG01 2000

PortionPortion

Generation ofschedule records

Generation of Schedule Records

Schedule records are generated from the settings in the parameter record and schedule master records (portion and meter reading unit).

Schedule records refer to specific dates, which control meter reading and billing. Schedule records must be generated for portions and meter reading units before meter reading

orders can be generated.

0.29

SAP AG 1999

20012001Portion A07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03

Portion A07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03

20022002

Portion A07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03

Scheduledmeterreadingdate

Billing period Billing period

Meter reading period for meter reading unit 1Meter reading period for meter reading unit 1



for all meter reading units for all meter reading units

End ofmeterreadingperiod

End ofbillingperiod

Meter readingMeter readingBillingBilling

Meter readingMeter readingBillingBilling

Scheduling: Annual Billing

Schduled billing date

End of billing period: This is the date on which the portion is to be billed for the first time. This date, together with the length of the billing period (that is, the period length), determines the date of the next billing (start of the next billing period = end of the billing period + 1 day).

The scheduled billing date is the date on which the contracts belonging to a portion are billed. This takes the SAP calendar into account.

The end of the meter reading period corresponds to the end of the billing period, and is used as a basis for defining dates of subsequent meter reading periods.

The scheduled meter reading date is the date on which the schedule specifies the register is to be read. It is also the date for which periodic meter readings are generated in scheduling. It forms the basis for calculating the expected consumption during meter reading order creation; it also acts as the final date for determining the budget billing amount.

0.30

SAP AG 1999

Street route

MRunit

A

MRunit

A

Meter Reading Organization: Street Route

City distr. 1

Street 1

Street 2

Street n

City distr. 2

City distr. n

Device 1

Device 2

Device n

Device location

1

Device loc. n

Device loc. 2

Connectionobject 1

Connectionobject 2

Connectionobject n

0.31

SAP AG 1999

Meter reading organization: Scheduling

Street route

Meter reading procedure Processing the meter reading

Checking of meter reading results

Extrapolation of meter reading results

Special functions Meter reading by customer via the Internet

Reversal function

Meter Reading: Process

0.32

SAP AG 1999

Meterreading

due

Createmeter reading

orders

Outputmeter reading

orders

Printmeter reading

documents

Downloadmeter reading

data

Read meter Read meter

Entermeter reading

results

Uploadmeter reading

results

Check meter reading

results

Manual meter reading

due

MDEmeter reading

due

Resultsdetermined

Overview: Scheduled Meter Reading

0.33

SAP AG 1999

Meterreading

due

Createmeter reading

orders

Outputmeter reading

orders

Printmeter reading

documents


data


Entermeter reading

results

Uploadmeter reading

results

Check meter reading

results


due

MDEmeter reading

due

Resultsdetermined

Meter reading orders Single meter reading orders

Mass meter reading orders

Single order data Selection via the meter reading unit,

contract, installation or device

Additional dates for billing control

Mass order data Selection via From meter reading unit and

To meter reading unit

Schedule task in task management

Specification of meter reading reason

Creating Meter Reading Orders

0.34

SAP AG 1999

• Cover sheet• Meter reading

documents

MDE • Meter reading notification• Card for meter reading

by customer

Output media

Meter reading information (selection)

Expected reading with area

Any number of previous meter reading results

Street route

Notes for the meter reader(dynamic / static)

Issuing the Meter Reading Orders

Meterreading

due

Createmeter reading

orders

Outputmeter reading

orders

Printmeter reading

documents


data


Entermeter reading

results

Uploadmeter reading

results

Check meter reading

results


due

MDEmeter reading

due

Resultsdetermined

0.35

SAP AG 1999

Automatic Upload interface

Automatic estimation

Manual Fast entry

Fast entry without correction

Fast entry with correction

Single entry

Result correction

Plausible results

Implausible results

Meter reading by customer Via the Internet

Via WAP telephone

Types of Result Entry

Meterreading

due

Createmeter reading

orders

Outputmeter reading

orders

Printmeter reading

documents


data


Entermeter reading

results

Uploadmeter reading

results

Check meter reading

results


due

MDEmeter reading

due

Resultsdetermined

0.36

SAP AG 1999

Reference to meter reading order (fast entry)

Entry number Check digit

Meter readingdata

Recorded meter reading Date and time of meter reading Meter reader's notes Meter reading type (such as meter reading by the

utility company, by the customer, or estimation) Meter reader number Date and time of maximum reading

Functions Correction and release of meter reading results Estimation of meter reading results

Result Entry Data

Meterreading

due

Createmeter reading

orders

Outputmeter reading

orders

Printmeter reading

documents


data


Entermeter reading

results

Uploadmeter reading

results

Check meter reading

results


due

MDEmeter reading

due

Resultsdetermined

0.37

SAP AG 1999

Entry of meter reading results Manual

Automatic

Types of validation Fixed checks

Independent checks

Dependent checks

Correction Correction and release of meter reading results

Estimation of meter reading results

Correction aids

Checking Meter Reading Results: Overview

Meterreading

due

Createmeter reading

orders

Outputmeter reading

orders

Printmeter reading

documents


data


Uploadmeter reading

results

Check meter reading

results


due

MDEmeter reading

due

Resultsdetermined

Entermeter reading

results

0.38

SAP AG 1999

Checks can be configured for individual customers and customer groups

Permitted deviations between measured values and target values can be configured using tables

Return control/monitoring of implausible results

Examples:• Consumption from

previous period• Demand from previous

periods• Demand compared with

agreed demand

Examples:• Consumption from

previous period• Demand from previous

periods• Demand compared with

agreed demand

Examples:• Cosine phi for

energy/demand• Usage hours• Control meters

Examples:• Cosine phi for

energy/demand• Usage hours• Control meters

Device: 4711000Meter reading: 78133

PlausiblePlausibleresultresult

ImplausibleImplausibleresultresult

Correction aidsCorrection aids

IndependentIndependentcheckschecks

DependentDependentcheckschecks

Check Meter Reading Results: Process

0.39

SAP AG 1999

Selection of meter reading ordersvia the following data objects: Contract

Installation

Device

Portion

MR unit

Business partner

Display (single or all): Billing order

Meter reading orders

Meter reading results

Monitoring Meter Readings

0.40

SAP AG 1999

InternetTransaction

server

InternetTransaction

server

EE--mail

mail

CustomerCustomer

Meter reading request

Meter reading request

Read meter

Entry of meter data

Entry of meter data

IS-U/CCSISIS--U/U/CCSCCS

InternetInternet Energy supplierEnergy supplierInternet customerInternet customer

Meter Reading by Customers over the Internet

0.41

SAP AG 1999

CustomerCustomer

Read meter

IS-U/CCSISIS--U/U/CCSCCS

Wireless Application Protocol

Wireless Application Protocol Energy supplierEnergy supplierInternet customerInternet customer

WAP

Transfer meter readings

Meter Reading by Customer over WAP Telephone

InternetTransaction

server

InternetTransaction

server

0.42

SAP AG 1999

New meterreading order

Incorrectmass

selection

Incorrectsingle

selection

Reverse meter reading

order

Correctselection

Restart order

creation

Meter reading order deleted

Reversing Meter Reading Orders: Process

0.43

SAP AG 1999

Scheduled meter readings are controlled via meter reading units

In meter reading preparation, documents are created for:

Meter reading by the company via meter reading lists

Meter reading by the company via MDE

Meter reading by customer via meter reading cards

Meter reading by customers via the Internet

Meter reading processing includes:

Automatic upload of data from external systems

Manual fast entry with and without correction

Manual single entry and meter reading estimation

Configurable validations reduce the potential for error

Meter Reading: Unit Summary

1

SAP AG 1999

Contents:

Billing Overview

Basic components of billing

Special functions

Invoicing Overview

Invoicing functions

Creation of contract accounts receivable and payable (FI-CA) and print documents

Billing and Invoicing

1.2

SAP AG 1999

At the conclusion of this unit, you will be able to:

Describe the billing process Billing procedure, simulation

Credit memo, manual backbilling

Outsorting, billing reversal

Explain the invoicing process Invoicing tasks and procedure

Special features of invoicing

Use of invoicing documents

Billing and Invoicing: Course Objectives

1.3

SAP AG 1999

Overview: Billing procedures and special functions

Billing and simulation procedures

Design of billing rules

Basic components of billing: Scheduled dates and periods

Billing procedures

Billing and simulation

Document display

Special billing functions: Credit memo, manual backbilling

Outsorting, reversal

Contents

Billing

1.4

SAP AG 1999

Contract billing of the supply and services provided is the most important function of a utility company.

Integrated processing of both residential and non-residential customers requires several billing rules.

Increased competition requires the billing process to be flexible and efficient.

Different types of simulation enable the correctbilling to be performed.

Billing: Introduction

SAP Utilities

1.5

SAP AG 1999

Move-out processing in the customer center

Move-out date and meter readings reported bytelephone

Implausible meter reading requires meter reading by the company

Meter reading processing

Create meter reading order

Enter or estimate meter reading results

Start of billing and invoicing

Final billing, followed by invoicing

Billing: Business Scenario

1.6

SAP AG 1999

Discounts,surchargesDiscounts,surcharges

Generalduties

Generalduties

ProrationProration Franchisefees

Franchisefees

Priceadjustment

Priceadjustment

. . .. . . . . .. . .

Electricity

Gas

Water/Waste water

Districtheating

Cabletelevision

MultimediaCharges TaxesDuties

Divisions

Residentialcustomer

Non-residentialcustomer

Energysuppliers

Businesspartner

ConsumptionservicesFlat rates

Billing rules, variantsBilling rules, variants

IS-U/CCS: Billing

1.7

SAP AG 1999

Billing procedures:

Month-based

Key date

Period

For exact number of days

Season-based

Comparative (best rate)

For employees

Floating (backbilling, period-

end billing)

Special functions Interim billing

Outsorting for bill verification

Simulation

Manual backbilling

Manual credit memo

Reversal

Unbilled revenue reporting

Billing Procedures: Overview

1.8

SAP AG 1999

Meter reading

Billing

Invoicing

Billing order processing that involves valuation of consumption and demand for each contract, and creation of billing documents for invoicing.

Definition of Billing

1.9

SAP AG 1999

Billing

Determination of billing periods

Determination and conversion of quantities

Creation of billing documents for invoicing

Determination of:•Rate data•Price data

Determination of change date andproration to that date

Valuation of quantities with prices

Billing Tasks

1.10

SAP AG 1999

MO TU WE TH FR SA SU18152128

29162229

310172330

411182431

5121925

6132026

7142127

Length of period for periodic billing x days; 1, 2, 3, 4, 6, or 12 months

Length of period for period-end billing x + x days; 1, 2, 3, 4, 6, or 12 months

Billing for an exact number of days based on the date of the meter reading

Month-based billing dependent on key date

Month-based billing dependent on intervals

Billing Periods

The billing period for which the utility bills the customer can be determined in a number of ways. These are:

For an exact number of daysDetermines the exact length of the billing period in days, for example the period between the last billed meter reading and the current day of meter reading.

Month-basedBills a specific number of complete months. If the case of a move-in or move-out, the month-based procedure can be billed based on the number of days.

SAP AG 1999

Periodic billingRecurring periodic billing

Floating backbillingSpecial form of monthly periodic billing in which backbilling is performed for previous monthsusing a current value.Example: monthly comparison of n peak averages

Period-end billingAfter completion of the billing cycleExample: 13th billing, backbilling for a year

Interim billingUnscheduled billing at any timeExample: initiated by customer request

Final billingExamples: customer move-out or termination of contract; service territory transfer

Forms of Billing

1.11

SAP AG 1999

Best-rate billingThe most favorable rate is chosen for the customer on the basis of several billing rules.

Quantity-based rate for basic priceThe annual quantity consumed is used to determinethe billing rule that applies.

Demand-based rate determinationThe measured demand is used to determine the billing rule that applies.

Season-based billingExamples: Different prices for each season, different billing rules for each season.

Special Forms of Billing

1.12

SAP AG 1999

2001Portion 17.27. 7.28. 7.29. 7.30. 7.31. 8.1. 8.2. 8.3.

Portion 17.27. 7.28. 7.29. 7.30. 7.31. 8.1. 8.2. 8.3.

2002

Portion 17.27. 7.28. 7.29. 7.30. 7.31. 8.1. 8.2. 8.3.

ScheduledMRdate

Billing periodBilling period

Meter reading period for MR unit 1Meter reading period for MR unit 1



for all MR unitsfor all MR units

End ofMRperiod

End ofscheduledbillingperiod

Meter readingMeter readingBilling Billing

Meter readingMeter readingBilling Billing

Generation of Schedule Records

Scheduled billing date

End of the billing period: Portions should be billed for the first time on this date. The length of the scheduled billing period (period length) in conjunction with this date determine the date of the next billing.

Scheduled billing date: Date on which billing of contracts that belong to a particular portion should begin. This date is calculated as follows during generation of the schedule records: Date of the end

of the billing period of the schedule record, minus the number of days between the end of the billing period and the scheduled billing date of the schedule master record.

The SAP calendar is used for this. End of the meter reading period: Used as the baseline date for determining the schedules of

the following meter reading periods. This date may not be later than the end of the billing period for the allocated portion.

Scheduled meter reading date: Date on which all extrapolations and estimations are performed.

SAP AG 1999

ImplausibleMR

results

ImplausibleMR

results

PlausibleMR

results

PlausibleMR

resultsMR

orderMR

order

Billing orderBilling order Billing orderBilling order Billing document

Billing document

MRorder creation

MRentry Billing Invoicing

MRcorrection

Billing Process: Overview

Bill printoutBill printout

Billprintout

1.13

SAP AG 1999

Generationof billingline items

Generationof billingline items

Validationof meterreadingresults

Validationof meterreadingresults

Executionof variantprograms

according to schema

Executionof variantprograms

according to schema

Quantityconversion

andproration

Quantityconversion

andproration

Dataentryand

analysis

Dataentryand

analysis

Data relating tocustomer and

installationRate data Procedure data

Contract

Ratedeter-

mination . . .

Schema 1Rate Var.pr. ValuesRate 11 VarProg. A x12 VarProg. B x2

. . .Rate 2

1 VarProg. A x32 VarProg. C x43 VarProg. D x5

. . .

. . .

. . .

Rate n1 VarProg. A xxx

EXECUTION

Installation Ratecategory

Rate type

Prices andrate facts

Rate 1

Rate n

Universal Billing Engine

Inst. structureRate cat. facts/

Installation facts

1.14

SAP AG 1999

Energy price

Demand price

Service price

Season-based values and variants

Block and scale prices

Usage hours

Best-rate billing

Decision variants

Billing

General Billing Functions

Energy priceMeasured or calculated consumption is valuated using energy charges. For example: Adjustment of calculated consumption over the course of the billing period Comparison with maximum/minimum purchase quantities and further processing of

difference quantities Breakdown/valuation of energy quantities using different percentage rates or time criteria

Demand priceMeasured or calculated demand is valuated using demand prices. The number of the measured demand values used for calculating the demand to be billed is variable. For example: Comparison with minimum demand, maximum demand, or other demand established in the

contract, and further processing of the difference demand (such as excess demand) Breakdown and valuation of demand using different percentage rates

Service price Any number of demand replacement values can be valuated with time-based prices for the supplying of energy. The demand replacement values can also be levied as a flat rate.

Block and scale prices Season-based values and variants Decision variants

1.15

SAP AG 1999

Billing

Billability check

Consideration of register relationships

Manual credit memos andbackbilling

Billing of company and plant consumption

Determination of taxes, duties, and charges

Energy feeding from small power producers

Special Billing Functions

1.16

SAP AG 1999

SimulationBilling

ISIS--UU

Billing typesReverse billing

Billing date reached

Enter selection criteria

Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation

Check billing documents

Check simulationdocuments

Start invoicing simulationBilling documents

implausibleBilling documents

correctBilling documents

incorrect

Outsortdocuments

Start invoicing

Choose billing type

Description:Creation of billing documents used only for further processing in invoicing

Description:Creation of simulation documents that are only used for further processing in invoicing simulation

Processing steps: Billing order is retained and

and can still be used for simulation

Meter reading results can still be changed

Simulation document is created

Processing steps: The billing order is deleted and

cannot be billed again

Meter reading results cannot be changed again

Billing document is created

Billing and Simulation

1.17

SAP AG 1999

Reverse billing



Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation






incorrect

Outsortdocuments

Start invoicing

Choose simulation

type

ISIS--UU

Simulation types

SimulationBilling

simulation

Description:Billing can be simulated without a billing order for any group and for any period of time.

Processing steps: Simulation period can be

freely defined

Extrapolation that takes account of meter reading results

Period can already have been billed

Description:Billing is simulated on the basis of a billing order that can be processed.

Processing steps: Period is determined by the

billing order

Meter reading results relevantto billing are required

Valuation of billing

Billability check

Simulation Types

1.18

SAP AG 1999

Reverse billing



Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation






incorrect

Outsortdocuments

Start invoicing

Check documents

Simulationdocument

Simulation

Billingdocument

BillingDescription:

Simulation produces a simulation document

Billing produces a billing document

Purpose Documents the procedure

Saves and validates the results

Used for further processing ofbilling line items

Document Types

1.19

SAP AG 1999

Internal billingdata

Account data

Print data

Meter readingdata

Device data

Price data

Billing line items

Documents from

• Simulation

• Billing

Reverse billing



Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation






incorrect

Outsortdocuments

Start invoicing

Check documents

Rate data

Document Information

1.20

SAP AG 1999

Documents from

• Simulation

• Billing

Reverse billing



Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation






incorrect

Outsortdocuments

Start invoicing

Processdocuments

further

Billingreversal

Outsorting

InvoicingInvoicing simulation

Further Processing of Documents

1.21

SAP AG 1999

Outsortdocuments

Automatic

ISIS--UU

Manual

Reverse billing



Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation






incorrect

Outsortdocuments

Start invoicing

Outsortdocuments

Description:Billing documents which have failed validation are outsortedautomatically.

Possible validations: Percentage or absolute

amount that the billing document exceeds or falls below the following:

Amount limit Bill sum total Budget billing

Bills with a balance of zero

Description:Billing documents for a contract for which the outsorting indicator is set are not automatically processed further.

Purpose Check special contract billing

documents Check new rates Check consumption values in

complex installations Check proration for different

time slices

Outsorting Procedure

1.22

SAP AG 1999

BillprintoutBilling Invoicing

Outsortdocuments

Check documents

Exception list

Reverse billing



Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation






incorrect

Outsortdocuments

Start invoicing

Outsortdocuments

Release documents

Reversedocuments

Outsorting reasons Failed validation

Indicator set in the contract

Further processing Reversal

Release

Outsorting Process

1.23

SAP AG 1999

Reverse billing

Individual reversal

ISIS--UU

Massreversal

Reverse billing



Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation






incorrect

Outsortdocuments

Start invoicing

Reversedocuments

Description:Only one billing document is reversed. This can occur with or without a subsequent correction bill.

Possible reasons: Incorrect conditions for

nonresidential contract Incorrect meter reading result Technical fault ...

Description:More than one document is reversed. Selection takes place using document intervals or listsof individual documents.

Possible reasons: Incorrect settlement group Incorrect rates and prices Incorrect sales tax ...

Billing Reversal

1.24

SAP AG 1999

2.16.00Incorrectbilling document

Jane Smith

Electricity. . . . . 900Gas . . . . . . 1.000Water . . . . . . 700Total . . . . . 2.600

Documentoutsorted

Document implausible

Reverse billing

Correct data Restart billing

2.23.00Reversedbilling document

Billing order

2.24.00Correctedbilling document

Jane Smith

Electricity . . . . 600Gas . . . . . 1.000Water . . . . . . 700Total . . . . . 2.300

Reversal indicator set

Jane Smith

Electricity . . . . 900Gas . . . . . 1.000Water . . . . . . 700Total . . . . . 2.600

Reverse billing



Choose billing type

Billingchosen

Simulationchosen

Startbilling

Start simulation






incorrect

Outsortdocuments

Start invoicing

Reversedocuments

Billing Reversal Process

1.25

SAP AG 1999

Billing processes billing orders, valuates consumption and demand, and creates billing documents for invoicing.

There are two types of billing: Simulation, which creates simulation documents

Billing, which creates billing documents

Outsorted billing documents require additional processing - Documents must be either released or reversed. Reasons for outsorting:

Failed validation

Indicator set in the contract

Individual or mass reversals enable quick correction and subsequent billing.

Billing: Unit Summary

1.26

SAP AG 1999

Invoicing links contract billing to contract accounts receivable and payable, and prepares bill printout.

The bill sum total is determined after settlement of the billing documents against the budget billings already paid, and against the taxes, charges, and duties that are due.

Flexible settlement options, such as payments to open items reduce the amount of processing required.

SAP Utilities

Invoicing: Introduction

The bill sum total is calculated as follows:Bill sum total = Total receivables from billing

- paid budget billings- other credits (credit memo, payment on account)+ other receivables (backbilling, dunning charge)

1.27

SAP AG 1999

Meter reading

Billing

Invoicing

The process that links the billing documents to contract accounts receivable and payable, and provides the basis for bill creation.

Definition of Invoicing

1.28

SAP AG 1999

FIFI--CACAISIS--UU

Billing:Provides the processes relevant to payment and manages the individual accounts.

Invoice-relevant transactions Billing documents Credit memos Backbillings

Contract accounts receivable and payable:

Contract Accounts Receivable and Payable makes available items relevant for payment and manages the individual accounts.

Invoice-relevant transactions Open items Paid budget billings Manual postings Dunning charges Payments on account

Invoicing Bill printout Budget billing plan Due date determination Settlement Use of credits

Invoicing: Overview

1.29

SAP AG 1999

Invoicing

Joint invoicing

Cross-company code invoicing

Account determination

Budget billing settlement

Credit settlement

Creation of budget billing

plan

Due datedetermination

Settlement against first budget billing

Tasks of Invoicing

Invoicing is the process that ingrates contract billing with the Contract Accounts Receivable and Payable (FI-CA) component. It also forms the basis for bill creation.

Invoicing is used for the following: Grouping together billing documents of contracts from the same contract account into one

joint bill. Posting documents to FI-CA (sub-ledger accounting) Supplying bill printout documents for bill creation Processing budget billing plans

1.30

SAP AG 1999

Invoicing Reversal

Date for invoicing reached


Choose invoicing type

Invoicing chosenInvoicing simulation

chosen

Start invoicing Start invoicing simulation


Simulate bill printout

Invoicingdocuments implausible

Invoicingdocuments

correct

Invoicingdocuments incorrect

Outsortdocuments

Start bill printout

Check bill printout

document

Check the FI-CA document

Start invoicing Creation of invoicing units

Summary of the billing documents in acontract account can be controlled at contract level.

Mandatory Contracts for which the documents must be invoiced together

Optional Contracts for which the documents can be invoiced together

Exclusive Contracts for which the documents must be invoiced separately

Invoicing Units

1.31

SAP AG 1999

Baseline date + terms of payment = bill due date

Fakturastornieren

Termin fürFakturaerreicht

Selektions-kriterieneingeben

Art der Fakturawählen

Fakturagewählt

Faktura-simulation

gewählt

Start invoicing Faktura-simulation

starten

Simulations-belegeprüfen

Rechnungs-druck

simulieren

Faktura-belege

unplausibel

Faktura-belegekorrekt

Faktura-belege

fehlerhaft

Belegeaussteuern

Rechnungs-druck

starten

Check bill printout

document


Start invoicing The bill due date is determined from the

following attributes: Terms of payment

These determine the source of the baseline date Baseline date:

Posting date, document date, or system date

Terms of payment Allocated to the contract account centrally Can be differentiated for incoming and outgoing payment If a bill falls due on a holiday, the bill due date can be

corrected to fall on a working day. Can be specified for each company in Customizing

Bill Due Date

1.32

SAP AG 1999

Credit memos/backbillings

Credit memos/backbillings

Billingdocuments

Billingdocuments

FI-CA documentsFI-CA documentsBudget billing plansBudget billing plans

Posting docs. FI-CA

Print documents

Fakturastornieren

Termin fürFakturaerreicht

Selektions-kriterieneingeben

Art der Fakturawählen

Fakturagewählt

Faktura-simulation

gewählt

Start invoicing Faktura-simulation

starten

Simulations-belegeprüfen

Rechnungs-druck

simulieren

Faktura-belege

unplausibel

Faktura-belegekorrekt

Faktura-belege

fehlerhaft

Belegeaussteuern

Rechnungs-druck

starten

Check bill printout

document


Start invoicing

Start invoicing

Document Flow in Invoicing

1.33

SAP AG 1999

Invoicing Reversal





chosen





Invoicingdocuments

correct


Outsortdocuments

Start bill printout

Check bill printout

document


Start invoicing In IS-U clearing processing, settlement

comprises the following activities: Automatic determination of the purpose of

a payment amount when a payment transactionis entered.

Automatic allocation of posted open items to eachother in account maintenance.

The selected items are cleared or partially cleared on the basis of these allocations.

Settlement control is flexible and enables you tomodel your own clearing strategy in Customizing.

Settlement: Overview

1.34

SAP AG 1999

Billreversal

ISIS--UU

Fullreversal

Invoicing Reversal





chosen





Invoicingdocuments

correct


Outsortdocuments

Start bill printout

Check bill printout

document


Invoicing Reversal

Transactions Reversal of FI-CA document Reversal of bill printout

document Possible reasons:

Incorrect layout Printing problems

Invoicing Reversal Mass reversalor Single reversal

Bill reversal:Bill printout and FI-CA documents for bills or partial bills are reversed by selecting using a reconciliation key or document number.

Full reversal:In addition to the bill, billing documents are also reversed by selecting using a document number. Full reversal does not include reversal of partial billing documents.Transactions

Reversal of FI-CA document Reversal of bill printout

document Reversal of billing document Possible reasons:

Incorrect billing

Invoicing Reversal

1.35

SAP AG 1999

Documentoutsorted


Reverse invoice Correct data

Restart invoicing

Billing document

New billJane Smith....

Electricity. . . 900Gas . . . . . . 1.000Water . . . . . 700

Bud. billings 2.500

Receivable . . 100

BillJane Smith....

Electricity . . . . 900Gas . . . . . 1.000Water . . . . . . 700

Bud. billings 2.900

Credit memo . . 300

Reversal indicator set

Reversed bill

Jane Smith....

Electricity . . . . 900Gas . . . . . 1.000Water . . . . . . 700

Bud. billings 2.900

Credit memo . . 300

Invoicing Reversal





chosen





Invoicingdocuments

correct


Outsortdocuments

Start bill printout

Check bill printout

document


Reversedocuments

Procedure for Bill Reversal

1.36

SAP AG 1999

24.2.98Correctedbilling document

Jane Smith

Electricity . . . . . 600Gas . . . . . 1.000

Water . . . . . . 700Total . . . . . 2.300

New billJane Smith

....

Electricity . . . 900Gas . . . . . 1.000

Water . . . . . 700

Bud. billings 2.500

Total . . . . . 100

Billing order

Incorrectbilling document

Jane Smith

Electricity . . . . . 900Gas . . . . . . 1.000Water . . . . . . 700Total . . . . . 2.600

BillJane Smith

....

Electricity . . . .900Gas . . . . . . 1.000

Water . . . . . . 700

Bud. billings 2.900

Credit memo . 300

16.2.98 23.2.98Reversedbilling document

Jane Smith

Electricity . . . . 900Gas . . . . . 1.000Water . . . . - 700

Total . . . . - 2.600

Reversed bill

Jane Smith....

Electricity . . . . 900Gas . . . . . 1.000Water . . . . . 700

Bud. billings. 2.900

Credit memo . . 300

Reverse invoice

Documentoutsorted


Reverse billing Correct data Restart billing

Restart invoicing

Procedure for Full Reversal

1.37

SAP AG 1999

The invoicing procedure includes: Invoicing and printing of the bill

Requests for budget billings or creation of partial bills

Different reversal procedures

Flexible settlement control

Budget billing procedure Budget billing: statistical posting or debit entry

Payment plan: fixed amounts or variable amounts

Output Printout on R/3 printer using spool

Raw data interface for external mail processing

Archiving

Invoicing: Unit Summary

2

SAP AG 1999

Contents:

Billing master data Overview of billing master data

Connection to business objects

Rate structure Rate type and rate category

Rates, operands, and schemas

Prices

Rate determination

Rate allocation

Billing Master Data

2.2

SAP AG 1999

At the conclusion of this unit, you will be able to:

Explain the function of rate master data: Billing class Operands and operand values Rate type and rate category Prices

Define the rate structure: Components of the rate Variant programs in the schema Rate determination

Describe rate allocation

Billing Master Data: Unit Objectives

2.3

SAP AG 1999

FIFISDSD

AMAMMMMM

GIS,CAD,SCADA

GIS,CAD,SCADA

MMMMPM/PM/CSCS

Customerinformation system

IS-U components

components

External systems


R/3 enterpriseinformation system

SDSDCOCO

Sales & DistributionSales & Distribution

Contract

A/R + A/P(FI-CA)

Contract

A/R + A/P(FI-CA)

Billing/InvoicingBilling/

Invoicing

Installationservices

Installationservices Premise

entryPremise

entryExternalExternalPremisePremise

EntryEntrySystemsSystems

ExternalExternalSalesSales

SystemsSystems

FinancialAccountingFinancial

Accounting

DeviceManagement

DeviceManagement

Plant Maintenance

& ServiceManagement

Plant Maintenance

& ServiceManagement

Asset Management & Materials Management

Asset Management & Materials Management

SAPBusinesspartner

SAPBusinesspartner

CCUUSS TTOOMM EERR

CCAARR EE && SS EE RR VV

II CCEE

SDSD

ExternalSales

Systems

ExternalSales

Systems



Rate StructureRate Structure• Link to master data• Rate type, rate categ.• Rate definition, prices• Operands, schemas• Rate determination

• Link to master data• Rate type, rate categ.• Rate definition, prices• Operands, schemas• Rate determination

Billing Master Data: Overview

2.4

SAP AG 1999

SAP Utilities

Billing master data enables you to specify contract billing rules for both residential and non-residential customers and provides the basis for a complete modeling of rates.

The flexible universal structuring of rates allows you to implement new and creative sales and marketing concepts.

An open architecture allows you to adapt and succeed in a changing environment.

Billing Master Data: Introduction

2.5

SAP AG 1999

Sales and marketing requirements

Description of new products and market segments

Utilities industry

Specification, checking and release of new contracts

Customizing of billing master data

Creation of rate category and rate type

Definition of rates, prices, and discounts

Maintenance of agreed special conditions

Billing Master Data: Business Scenario

2.6

SAP AG 1999

Billing of contracts for residential and non-residential customers

Supports billing procedures for international utility management, such as periodic, interim and period-end billing, floating backbilling, final billing, budget, average monthly and equalized billing, and so on.

Open to new billing procedures

Third party billing and cross-company code billing

Special features: Examples include thermal gas billing, billing for external generators and installations without a meter.

Billing of Utility Services

2.7

SAP AG 1999

IS-UIS-U

FI-CAFIFI--CACA

SD, CS, PMSD, CS, PM

Cross appl.CrossCross applappl..

FI-CAdocument

FI-CAdocument

Billingdocument

(utility)

Businesspartner

ContractA/R + A/PContractA/R + A/P

Contract(utility)

Regionalstructure

Premise

EquipmentConnection

DeviceCategory

Register

Device location

Customercontact

Connectionobject

Rate-relevant information

Device

InstallationPoint of delivery

Business Objects: Rate Allocation

The installation, the device, and the register contain information relevant to the rate. The installation contains:

Billing classRate category

The device contains:Rate categoryFact groupPrice class

The register also contains:Rate categoryFact groupPrice class

2.8

SAP AG 1999

Contractper division

Installation

Device

Register

Billingclass

Ratecategory

Rate type

Rate type

Fact group

Price class

Price class

Fact group

Installations are classified for billing via the billing class

The rate category influences indirect rate determination

The rate type and the rate category determine the rate used for billing.

The fact group contains values relevant to billing.

The price class determines the rental price in conjunction with the price level.

Rate Allocation: Overview

Billing classClassification of installations, for example, for residential customers or non-residential customers.

Rate categoryClassification of an installation for billing. The rate category is used in conjunction with the rate type to determine the rate. In the rate category, you establish the criteria for billing which govern the rates. These criteria can, for example, control the period-end billing or calculation of the budget billing.

Rate typeYou can allocate a rate to registers, devices, a rate category, or an installation using a rate type.

2.9

SAP AG 1999

Classifies installations within a division, for example residential/nonresidential contract.

Can be valid for several rate categories.

Used for plausibility checks in scheduling and in the billing master data.

Enables several franchise fee groups to be defined.

Can be used as a statistical criteria.

If you change the billing class, you must also change the rate category. You do not have to perform a final billing.

Billing Class I

The billing class classifies installations for billing. The billing class is also used for the following purposes:

For consistency verifications between the master data and billing master data. For example, you can verify that a residential customer's installation has not been allocated to a nonresidential contract.

As a statistical criteria, for example in the sales statistics.

2.10

SAP AG 1999

Valid for one division only

Belongs to a single billing class

Contains one valid billing schema

Controls billing - used to determine the rate in conjunction with the rate type

Determines which outsorting checks occur during billing

Controls floating backbilling and period-end billing for nonresidential customers

Controls advance billing and dynamic period control

Rate Category I

The billing class classifies installations for billing. The rate category is used in conjunction with the rate type to determine the rate. Examples of rates are: Household rate Commercial rate Commercial rate with demand measurement Industrial rate Minimal consumption rate Basic price rate 1 Basic price rate 2 Domestic water Reserve wasser Water for fire fighting

Rate determination:rate type + rate category = rate

2.11

SAP AG 1999

RateCategoryBilling Class

OutsortingGroup

Division

Notes Backbilling/Period-End Billing

DynamicPeriod Control

Billing Schema

Advance Billing

Rate Category II

The rate category contains data that controls the processing of billing data. This includes: Billing Schema Control of period-end billing and accompanying backbilling Outsorting checks

Any other billing-relevant data is also saved in the rate category. This includes any agreed quantities, demand, prices, or flat rates. In the case of flat rate services (such as cable services and street lights), no quantities are measured. You must therefore define replacement values that the system can use for evaluation (for example number of cable connections or number of street lights with a specific connection value).

2.12

SAP AG 1999

Used to classify Registers

Devices

Flat rates

Reference values

for billing

Examples: peak and off-peak rates for active energy; peak rate for reactive energy; peak rate for active power; gas and water consumption; flat rate installations

The rate category is used in conjunction with the rate type to determine the rate.

Definition of Rate Type

Generally, you enter the rate type in the register. Examples of rate categories are peak and off-peak rates for active energy, peak rates for reactive energy, peak rates for active power, as well as gas and water consumption.

In exceptional cases you can allocate the rate type to the following objects: Device

For devices without registers (such as ripple control receivers) you can use the rate type to find special rates. Using these, you can calculate a device-based settlement price.

FactsUsed to determine rates that cannot be derived from registers.Also used to determines rates for flat rate installations without installed devices.

Reference valuesUsed to model street lights, for example