You are on page 1of 523

IUT110 Introduction to the IS-U/CCS System

IUT110

Release 463 25.09.2003

IUT110 Introduction to the IS-U/CCS System..................................................................................................................1
Copyright.......................................................................................................................................................................2
SAP Utilities (IS-U/CCS)..........................................................................................................................................4
Course Prerequisites...................................................................................................................................................5
Target Group..............................................................................................................................................................6
Course Goals..............................................................................................................................................................7
Course Objectives......................................................................................................................................................8
Course Content...........................................................................................................................................................9
IS-U/CCS: Overview.....................................................................................................................................................1
IS-U/CCS Overview: Unit Objectives.......................................................................................................................2
IS-U Overview: Business Scenario............................................................................................................................3
mySAP.com: Overview.............................................................................................................................................4
Workplace Internet Business Framework..................................................................................................................5
mySAP Utilities: The Comprehensive Solution........................................................................................................6
Customer Relationship Management (CRM)............................................................................................................7
Business Information Warehouse (BW)....................................................................................................................8
Functional Scope of the IS-U System........................................................................................................................9
Integrated and Open System Landscape..................................................................................................................10
IS-U/CCS Business Processes.................................................................................................................................11
Synchronized Business Objects...............................................................................................................................12
Marketing and Sales Process...................................................................................................................................13
System Infrastructure CRM, BW and mySAP Utilities..........................................................................................14
IS-U/CCS - Integration Model.................................................................................................................................15
The Strengths of mySAP Utilities............................................................................................................................16
Solutions for the New Industry Market Model........................................................................................................17
Deregulated Market: Business Perspective..............................................................................................................18
Sales and Marketing in IS-U/CCS (1).....................................................................................................................19
Sales Processing.......................................................................................................................................................20
Sales and Marketing in IS-U/CCS (2).....................................................................................................................21
Internet Self Services: Start Page.............................................................................................................................22
What is Energy Data Management?........................................................................................................................23
Energy Data Management 1.....................................................................................................................................24
Energy Data Management 2.....................................................................................................................................25
IS-U Overview: Unit Summary...............................................................................................................................26
CIC.................................................................................................................................................................................1
CIC: Unit Objectives..................................................................................................................................................2
CIC: Business Scenario..............................................................................................................................................3
The IS-U House.........................................................................................................................................................4
Various Business Partners..........................................................................................................................................5

Roles of the Business Partner....................................................................................................................................6
Business Partner Data................................................................................................................................................7
Contract Account Data...............................................................................................................................................8
Collective Bills...........................................................................................................................................................9
Contract Data...........................................................................................................................................................10
Connection Object Data...........................................................................................................................................11
Premise Data............................................................................................................................................................12
Installation Data.......................................................................................................................................................13
Point of Delivery Data.............................................................................................................................................14
Business Objects in IS-U/CCS.................................................................................................................................15
What Is a Customer Interaction Center?..................................................................................................................16
Customer Interaction Center: Requirements............................................................................................................17
Integration with External Communication Systems................................................................................................18
The IS-U/CCS Customer Interaction Center...........................................................................................................19
Customer Interaction Center (L-Shaped).................................................................................................................20
Workflow Inbox.......................................................................................................................................................21
E-Mail and Fax in the Workflow Inbox...................................................................................................................22
Typical Uses of the CIC: Identification...................................................................................................................23
Typical Uses of the CIC: Information.....................................................................................................................24
Typical Uses of the CIC: Front Office Process.......................................................................................................25
Front Office Processes.............................................................................................................................................26
Typical Uses of the CIC: Workflow........................................................................................................................27
Using R/3 Workflow: Changing a Rate (Example).................................................................................................28
Typical Uses of the CIC: Customer Contact............................................................................................................29
Contact Management in Customer Service..............................................................................................................30
Customer Contact Data............................................................................................................................................31
CIC: Unit Summary.................................................................................................................................................32
Customer Interaction Center Exercises....................................................................................................................33
Customer Interaction Center (CIC) Solutions..........................................................................................................44
Move-In/Out..................................................................................................................................................................1
Move-In/Out: Unit Objectives...................................................................................................................................2
Move In/Out: Business Scenario...............................................................................................................................3
Move-In Definition....................................................................................................................................................4
Move-In: Prerequisites...............................................................................................................................................5
Move-In: Business Master Data.................................................................................................................................6
The Move-In Process.................................................................................................................................................7
Move-In: Options for Processing...............................................................................................................................8
Move-In: The IS-U House.........................................................................................................................................9
Move-Out: Business Scenario..................................................................................................................................10

The Move-Out Process............................................................................................................................................11
Options for Move-Out Processing...........................................................................................................................12
Move In/Out: Business Scenario.............................................................................................................................13
The Move-In/Out Process........................................................................................................................................14
Options in Move-In/Out Processing........................................................................................................................15
Move-In: Master Data..............................................................................................................................................16
No Changes to Installation Data..............................................................................................................................17
Installation History...................................................................................................................................................18
Move-In/Out: Unit Summary...................................................................................................................................19
Move-In/Out Exercises............................................................................................................................................20
Move-In/Out Solutions............................................................................................................................................28
Work Management.........................................................................................................................................................1
Work Management: Unit Objectives.........................................................................................................................2
What Areas does the Work Management System Cover?.........................................................................................3
Utility Management Services.....................................................................................................................................4
Work Management: Technical Objects.....................................................................................................................5
Overview of Technical Objects.................................................................................................................................6
Supply Grid................................................................................................................................................................7
Connection Object.....................................................................................................................................................8
Work Management: Services.....................................................................................................................................9
Installation Services.................................................................................................................................................10
Basic Structure of a Work Order.............................................................................................................................11
Sequence of Order Processing.................................................................................................................................12
Service Product: Concept.........................................................................................................................................13
Service Product: Create Service Connection...........................................................................................................14
The Installation Services Process.............................................................................................................................15
Create Service Connection.......................................................................................................................................17
Work Management: Interfaces.................................................................................................................................18
Possible Configuration of an Interface Scenario.....................................................................................................19
Technical Objects in Work Management and GIS..................................................................................................20
Device Repairs.........................................................................................................................................................21
Work Management: Unit Summary.........................................................................................................................22
Work Management Exercises..................................................................................................................................23
Work Management Solutions..................................................................................................................................24
Device Technology........................................................................................................................................................1
Device Technology: Unit Objectives.........................................................................................................................2
Demands on Device Management.............................................................................................................................3
Device Management: Business Scenario...................................................................................................................4
Device Technology: Device Category.......................................................................................................................5

The Device and the Device Category........................................................................................................................6
Modeling of Devices..................................................................................................................................................7
Integration with Logistics..........................................................................................................................................8
Definition of Device Category...................................................................................................................................9
Device Category Data..............................................................................................................................................10
Possible Elements of the Device Category..............................................................................................................11
Device Category: Device and Register....................................................................................................................12
Definition of Devices...............................................................................................................................................13
Device Data..............................................................................................................................................................14
Definition of a Register............................................................................................................................................15
Register Data............................................................................................................................................................16
Device Technology: Device Lifecycle.....................................................................................................................17
Central Data Objects - Integration in Logistics.......................................................................................................18
Device Life Cycle....................................................................................................................................................19
Documentation for the Device Lifecycle.................................................................................................................20
Device Technology: Device Inspection...................................................................................................................21
Introduction: Device Inspection and Certification...................................................................................................22
Certification Procedures Overview..........................................................................................................................23
Certification Procedure............................................................................................................................................24
Sampling Procedure.................................................................................................................................................25
Inspection Using the Sampling Procedure...............................................................................................................26
Periodic Replacement..............................................................................................................................................27
Device Technology: Unit Summary........................................................................................................................28
Device Technology Exercises..................................................................................................................................29
Device Technology Solutions..................................................................................................................................32
Device Installation.........................................................................................................................................................1
Device Installation: Unit Objectives..........................................................................................................................2
Device Installation: Business Scenario......................................................................................................................3
Installation: Installation, Removal And Replacement...............................................................................................4
Business Scenario: Replacement of Sample Devices................................................................................................5
Service Order Execution: Determining the Device Location....................................................................................6
Definition of the Device Location.............................................................................................................................7
Device Location Data................................................................................................................................................8
Relationships Between Technical Objects.................................................................................................................9
Service Order Execution: Device Replacement & Service Order Confirmation.....................................................10
Data Changes: Installation Location........................................................................................................................11
Data Changes: Device Replacement........................................................................................................................12
Technical and Billing-Related Installation..............................................................................................................14
Installation: Installation Structure............................................................................................................................15

Example of an Installation Structure........................................................................................................................16
Technical Installation Structure...............................................................................................................................17
Billing-Related Installation Structure......................................................................................................................18
Device Installation: Summary..................................................................................................................................19
Device Installation Exercises...................................................................................................................................20
Device Installation Solutions...................................................................................................................................23
Meter Reading................................................................................................................................................................1
Meter Reading: Unit Objectives................................................................................................................................2
Meter Reading: Business Scenario............................................................................................................................3
Meter Reading: Meter Reading Organization............................................................................................................4
Types of Meter Reading.............................................................................................................................................5
Regional Structure and Scheduling............................................................................................................................6
Scheduling Tasks.......................................................................................................................................................7
Portions and Meter Reading Units.............................................................................................................................8
Generation of Schedule Records................................................................................................................................9
Scheduling: Annual Billing......................................................................................................................................10
Meter Reading Organization: Street Route..............................................................................................................11
Meter Reading: Process...........................................................................................................................................12
Overview: Scheduled Meter Reading......................................................................................................................13
Creating Meter Reading Orders...............................................................................................................................14
Issuing the Meter Reading Orders...........................................................................................................................15
Types of Result Entry..............................................................................................................................................16
Result Entry Data.....................................................................................................................................................17
Checking Meter Reading Results: Overview...........................................................................................................18
Check Meter Reading Results: Process...................................................................................................................19
Monitoring Meter Readings.....................................................................................................................................20
Meter Reading: Special Functions:..........................................................................................................................21
Meter Reading by Customers over the Internet.......................................................................................................22
Meter Reading by Customer over WAP Telephone................................................................................................23
Reversing Meter Reading Orders: Process..............................................................................................................24
Meter Reading: Unit Summary................................................................................................................................25
Meter Reading: Exercises........................................................................................................................................26
Meter Reading: Solutions........................................................................................................................................27
Energy Data Management..............................................................................................................................................1
Profile Management: Unit Objectives.......................................................................................................................2
Profile Management: Business Scenario...................................................................................................................3
Profile Header............................................................................................................................................................4
Profile Allocation for Register...................................................................................................................................5
Point of Delivery........................................................................................................................................................6

Importing Profile Values............................................................................................................................................7
Profile Values.............................................................................................................................................................8
Formula Profile..........................................................................................................................................................9
Synthetic Profiles.....................................................................................................................................................10
Profile Management: Summary...............................................................................................................................11
Billing and Invoicing.....................................................................................................................................................1
Billing and Invoicing: Course Objectives..................................................................................................................2
Billing........................................................................................................................................................................3
Billing: Introduction...................................................................................................................................................4
Billing: Business Scenario.........................................................................................................................................5
IS-U/CCS: Billing......................................................................................................................................................6
Billing Procedures: Overview....................................................................................................................................7
Definition of Billing...................................................................................................................................................8
Billing Tasks..............................................................................................................................................................9
Billing Periods.........................................................................................................................................................10
Forms of Billing.......................................................................................................................................................11
Special Forms of Billing..........................................................................................................................................12
Generation of Schedule Records..............................................................................................................................13
Billing Process: Overview.......................................................................................................................................14
Universal Billing Engine..........................................................................................................................................15
General Billing Functions........................................................................................................................................16
Example: Billing Rule for Electricity......................................................................................................................17
Special Billing Functions.........................................................................................................................................18
Billing and Simulation.............................................................................................................................................19
Simulation Types.....................................................................................................................................................20
Document Types......................................................................................................................................................21
Document Information.............................................................................................................................................22
Further Processing of Documents............................................................................................................................23
Outsorting Procedure...............................................................................................................................................24
Outsorting Process...................................................................................................................................................25
Billing Reversal.......................................................................................................................................................26
Billing Reversal Process..........................................................................................................................................27
Billing: Unit Summary.............................................................................................................................................28
Invoicing: Introduction............................................................................................................................................29
Invoicing: Business Scenario...................................................................................................................................30
Definition of Invoicing............................................................................................................................................31
Invoicing: Overview................................................................................................................................................32
Tasks of Invoicing....................................................................................................................................................33
Invoicing Units.........................................................................................................................................................34

Mandatory and Optional Contracts: 1......................................................................................................................35
Mandatory and Optional Contracts: 2......................................................................................................................36
Invoicing Options.....................................................................................................................................................37
Source of Billing Documents...................................................................................................................................38
Invoicing Various Services......................................................................................................................................39
Cross-company code invoicing................................................................................................................................40
Bill Due Date...........................................................................................................................................................41
Document Flow in Invoicing...................................................................................................................................42
Settlement: Overview...............................................................................................................................................43
Bill Printout Procedure............................................................................................................................................44
Invoicing Reversal...................................................................................................................................................45
Procedure for Bill Reversal......................................................................................................................................46
Procedure for Full Reversal.....................................................................................................................................47
Invoicing: Unit Summary........................................................................................................................................48
Billing and Invoicing Exercises...............................................................................................................................49
Billing and invoicing Solutions...............................................................................................................................58
Billing Master Data........................................................................................................................................................1
Billing Master Data: Unit Objectives........................................................................................................................2
Billing Master Data: Overview..................................................................................................................................3
Billing Master Data: Introduction..............................................................................................................................4
Billing Master Data: Business Scenario....................................................................................................................5
Billing of Utility Services..........................................................................................................................................6
Business Objects: Rate Allocation.............................................................................................................................7
Rate Allocation: Overview........................................................................................................................................8
Billing Class I............................................................................................................................................................9
Rate Category I........................................................................................................................................................10
Rate Category II.......................................................................................................................................................11
Definition of Rate Type...........................................................................................................................................12
Business Objects: Rate Structure.............................................................................................................................13
Rate..........................................................................................................................................................................14
Example: Billing Rule for Electricity......................................................................................................................15
Rate Structure...........................................................................................................................................................16
Rate Data..................................................................................................................................................................17
Data for the Rate Step..............................................................................................................................................18
Structure of the Fact Group......................................................................................................................................20
Operand Data...........................................................................................................................................................21
Operand Categories/Examples.................................................................................................................................22
Rate Determination - Operands...............................................................................................................................23
Allocation of Operand Values.................................................................................................................................24

Schema 1..................................................................................................................................................................25
Schema 2..................................................................................................................................................................26
Price Categories.......................................................................................................................................................27
Price Types...............................................................................................................................................................28
Rate Determination..................................................................................................................................................29
Rate Structure...........................................................................................................................................................30
Discounts / Surcharges.............................................................................................................................................31
Billing Master Data: Unit Summary........................................................................................................................32
Exercises: Billing Master Data................................................................................................................................33
Billing Master Data Solutions..................................................................................................................................36
Real-Time-Pricing..........................................................................................................................................................1
Real-Time-Pricing: Unit Objectives..........................................................................................................................2
Real-Time-Pricing:Business Scenario.......................................................................................................................3
RTP Overview...........................................................................................................................................................4
RTP interface.............................................................................................................................................................5
RTP-Billing................................................................................................................................................................6
Example.....................................................................................................................................................................7
Data Model for Billing...............................................................................................................................................8
Interface.....................................................................................................................................................................9
Input Parameters......................................................................................................................................................10
Calculation...............................................................................................................................................................11
Result.......................................................................................................................................................................12
Transfer of Results to RTP Operand........................................................................................................................13
Real-Time-Pricing: Unit Summary..........................................................................................................................14
Budget Billings..............................................................................................................................................................1
Budget Billing: Unit Objectives.................................................................................................................................2
Budget Billing: Business Scenario.............................................................................................................................3
Budget Billing Procedure: Overview.........................................................................................................................4
Payment Plan Categories...........................................................................................................................................5
Budget Billing Plan: Overview..................................................................................................................................6
Creating / Adjusting Budget Billing Plans.................................................................................................................7
Quantity-Based Extrapolation....................................................................................................................................8
Budget Billing Amounts Due.....................................................................................................................................9
Budget Billings: Summary.......................................................................................................................................10
Contract Accounts Receivable and Payable..................................................................................................................1
Contract Accounts Receivable and Payable: Unit Objectives...................................................................................2
Contract Accounts Receivable and Payable: Overview.............................................................................................3
Contract Accounts Receivable and Payable: Business Scenario...............................................................................4
Contract Accounts Receivable and Payableand FI-CA.............................................................................................5

FI-CA Has An Open Architecture.............................................................................................................................6
Special Features of FI-CA.........................................................................................................................................7
Central Objects in FI-CA...........................................................................................................................................8
Contract Accounts Receivable and Payable: Business Transactions.........................................................................9
Contract Accounts Receivable and Payable: Posting Documents...........................................................................10
Posting Documents: Objectives...............................................................................................................................11
Posting Documents: Introduction............................................................................................................................12
Posting Documents: Business Scenario...................................................................................................................13
Documents in Contract Accounts Receivableand Payable......................................................................................14
General Document Data...........................................................................................................................................15
Document Data: Reference and Currency...............................................................................................................16
Document Data: Link to General Ledger Accounting.............................................................................................17
Document Data: Entry Control................................................................................................................................18
Data on Business Partner Item.................................................................................................................................19
Data on G/L Account Item.......................................................................................................................................20
Manual Document Entry: Items...............................................................................................................................21
Transactions in Contract Accounts Receivable and Payable...................................................................................22
Examples of Transactions........................................................................................................................................23
Transfer to General Ledger Accounting..................................................................................................................24
Summary Record.....................................................................................................................................................25
Posting Documents: Summary (1)...........................................................................................................................26
Posting Documents: Summary (2)...........................................................................................................................27
Contract Accounts Receivable and Payable: Account Display...............................................................................28
Account Display: Objectives...................................................................................................................................29
Account Display: Introduction.................................................................................................................................30
Account Display: Business Scenario.......................................................................................................................31
Account Display: Initial Screen...............................................................................................................................32
Account Display: List Category...............................................................................................................................33
Account Display: Line Layout.................................................................................................................................34
Account Display: Navigating in the Document Display..........................................................................................35
Account Display: Summary (1)...............................................................................................................................36
Account Display: Summary (2)...............................................................................................................................37
Contract Accounts Receivable and Payable: Payments...........................................................................................38
Payment Run: Objectives.........................................................................................................................................39
Payment Run: Introduction......................................................................................................................................40
Payment Run: Business Scenario.............................................................................................................................41
Automatic and Manual Payments............................................................................................................................42
Payment Lot.............................................................................................................................................................43
Payment Lot: Structure............................................................................................................................................44

..............52 Payment Lot: Post-processing..........................73 Dunning: Objectives.............................................................................48 Payment Lot: Change............................................................................................................................................................................................................................53 Payment at cash desk............................................................................................................................................................................................................64 Returns Entry..................................................82 Printing of Dunning Notice for a Business Partner..........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................70 Returns History.........................................................................................................65 Returns Lot: Change..................................79 Dunning: Factors That Can Be Influenced (Selection).......................................................................................................61 Returns: Activity Settings......................................................60 Returns: Influencing Factors.................................................................................................................62 Returns Lot: Processing Steps..........................................47 Payment Lot: Create Items..................................................................................................................................................78 Dunning Proposal for a Business Partner.........74 Dunning: Introduction.....................................................................................55 Payment: Summary............................................................................................................................................................................................................................50 Payment Lot: Post...............................................................................................................................................................................................................................................................................................................................................................................................68 Returns Lot: Posting (2)...................................................................72 Contract Accounts Receivable and Payable: Dunning........................................................56 Contract Accounts Receivable and Payable: Returns..........................................................Payment Lot: Structure....................................................................................................................................................63 Returns Lot: Create....................................................................................................................................................................................................................................................................................................................46 Payment Lot: Create............................................................................................................................................................................................................................................................................................................81 Dunning Levels...........................................................................71 Returns: Summary.76 Dunning: Dunning Proposal and Dunning Activities.....49 Payment Lot: Close.57 Returns: Objectives..................................................................................................................................................................................................................................58 Returns: Introduction.............................................................................................................................51 Automatic Clearing: Process...................................................................................................................................................................................................................................................................................................45 Payment Lot: Processing Steps.....................................................................................................................................................................................................................................................................................................80 Dunning: Determination of Dunning Levels...............................66 Returns Lot: Close.....................................................................................................................................................54 Clearing: Dialog Processing.........................................................................................................................................................77 Dunning: Influential Factors.................67 Returns Lot: Posting (1).......................................75 Dunning: Business Scenario..........................................................................................................................................................................................................................................69 Returns Lot: Post-processing...........59 Returns: Business Scenario...........................................................................................................................83 ............................................................

...................................................................................13 Interface to Route Planning System................................................................................................................89 Deferral.......................................................................................................................91 Installment Plan Category.............................................................................108 Waste Industry.......................................................................15 Process: Container Delivery / Removal...............................................................................................................................................................................................................4 mySAP Waste Industry : Involved Areas......................................................................................................................84 Dunning: Summary.......................................................6 Focus Areas of EH&S WA ..............93 Deferral and Installment Plan: Unit Summary..................................................86 Deferral and Installment Plan: Objectives...................85 Contract Accounts Receivable and Payable: Deferral and Installment Plan..................................................94 Contract Accounts Receivable and Payable Exercises..................................................................................10 Technical Master Data II...........................................3 Integration Model for mySAP Waste Industry.............12 Container Management: Integration...................87 Deferral and Installment Plan: Introduction.....................................................................................................................................................................................................................................................................................................................................................................................1 Waste Industry: Unit Objectives......................................8 Data Model – Container Service (Simplified)........................................................................................................................................................64......18 Implemented Functions II............................5 Focus Areas of IS-Waste .................................................................88 Deferral and Installment Plan: Business Scenario........................................................................................................................................................................................................................................................................21 .........................................................................................................................................................Waste Management...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................90 Installment Plan: Characteristics............................................................................................................................................17 Implemented Functions I.........................................................11 Technical Master Data III...........................................................14 Waste Disposal Orders......95 Contract Accounts Receivable and Payable Solutions.....................................................................................................................................................7 The Waste Disposal Cycle with EH&S...................................................92 Installment Plan: Item Selection.................................................................................................................................................................... Dunning: Dunning History...................................................................................................................................................................................................................................................................................................................................................................................................20 Waste Industry: Summary....................................................................9 Technical Master Data I.......................................................................................................................................................................................................................................2 Solution Map and Integration Model for the Waste Industry....19 Planned Functions for mySAP Utilities 4.....16 Fleet Management..............................................................................................Waste Industry...............

0 IUT110 Introduction to the IS-U/CCS System IUT110 Introduction to the IS-U/CCS System  SAP AG 1999  R/3 System  Release 4.63 / IS-Utilities/Customer Care Service  August 2001  5004 4795 .

 Visio ® is a registered trademark of Visio Corporation.  UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation. The information contained in this document is subject to change and supplement without prior notice. R/2. SAP EarlyWatch. RIVA. Saarbrücken  Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc. SAP ArchiveLink. WinWord ®. Inc. . SAPscript. SAPtime. R/3 Retail. OS/2 ®. InterSAP. and HTML Help ® are registered trademarks of Microsoft Corporation. NT ®. Video for Windows ®.  ADABAS ® is a registered trademark of Software AG  The following are trademarks or registered trademarks of SAP AG.  Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation.  INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated.0. SAPtronic. Inc. PowerPoint ®. SAP-EDI. Project ®. SAP (Word). SQL-Server ®. SAPfile. ABAP/4.  ORACLE ® is a registered trademark of ORACLE Corporation.  Vivo ® and VivoActive ® are registered trademarks of RealNetworks.  Indeo ® is a registered trademark of Intel Corporation.  ARIS Toolset ® is a registered Trademark of IDS Prof. Windows ®. SAPaccess. and ALE/WEB. DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation.  TouchSend Index ® is a registered trademark of TouchSend Corporation. and Netscape Communicator ® are registered trademarks of Netscape Communications.  OSF/Motif ® is a registered trademark of Open Software Foundation. SAPfind. SAPoffice. Excel ®. R/3. SAPmail.  Netscape Navigator ®. Neither this training manual nor any part thereof may be copied or reproduced in any form or by any means. without the prior consent of SAP AG. Internet Explorer ®.  SAP AG 1999  Microsoft ®. All rights reserved. SAP Business Workflow.  IBM ®. Multimedia Viewer ®. Scheer GmbH.2 Copyright Copyright 2001 SAP AG. All rights reserved. or translated into another language. California. NetShow ®. USA.

logos.  Other products. or brand names included herein are trademarks or registered trademarks of their respective owners. services. The SAP logo and all other SAP products. . logos. services. or brand names included herein are also trademarks or registered trademarks of SAP AG.

0. Basic Data/ Basic Real Time Pricing Billing and Invoicing U/CCS Functions IUT240 5 days Contract Accounts Receivable and Payable IUT250 4 days Customer Service IUT280 2 days Print Workbench  SAP AG 1999 .3 SAP Utilities (IS-U/CCS) Level 2 Level 3 IUT220 3 days IUT225 2 days Energy Data Device Management Management IUT221 3 days Work Management IUT110 5 days IUT210 3 days IUT230 5 days IUT235 2 days Introduction to the IS.

0.4 Course Prerequisites  Basic knowledge of SAP (For example. course SAP020: SAP R/3 Overview)  Knowledge of business processes in a utility company  Basic knowledge of the Windows environment  SAP AG 1999 .

0.5 Target Group  Participants  Decision makers using IS-U to support business processes  Project managers responsible for implementing IS-U  Project team modeling business processes with IS-U  Administrators optimizing processes in the IS-U environment  Consultants preparing for IS-U implementation  Duration  5 days  SAP AG 1999 .

6 Course Goals This course will prepare you to:  Recognize how IS-U is integrated in the R/3 environment  Outline business processes in IS-U  Use and efficiently implement IS-U  SAP AG 1999 .0.

0. you will be able to:  Describe the integration of IS-U in R/3  Perform the core business processes of IS-U  Explain the structure and processes of IS-U  SAP AG 1999 .7 Course Objectives At the conclusion of this course.

0.8 Course Content Preface Unit 1 IS-U/CCS Overview Unit 8 Energy Data Management Unit 2 CIC Unit 9 Billing & Invoicing Unit 3 Move-In/Out Unit 10 Billing Master Data Unit 4: Work Management Unit 11 Real-Time Pricing Unit 5 Device Technology Unit 12 Budget Billings Unit 6 Device Installation Unit 13 Contract Accounts Receivable and Payable Unit 7 Meter Reading Unit 14 Waste Disposal Industry Appendix  SAP AG 1999  CIC: Customer Interaction Center .

1 IS-U/CCS: Overview Contents:  Integration of IS-U/CCS in standard SAP components  Incorporation of IS-U/CCS into the core business processes of a utility company in regulated and deregulated markets  Overview of IS-U/CCS functions  SAP AG 1999 (C) SAP AG IUT110 1 .

you will be able to:  Present the integration of IS-U/CCS in standard SAP components  Name the most important SAP components and their roles in the utilities industry  Describe the functions of IS-U/CCS  SAP AG 1999 (C) SAP AG IUT110 2 .2 IS-U/CCS Overview: Unit Objectives At the conclusion of this unit.1.

1.  You are taking part in a 5-day training program  Your main tasks will be customer-oriented processes in the customer center  You will use typical business processes to become familiar with the IS-U/CCS structure  SAP AG 1999 (C) SAP AG IUT110 3 .3 IS-U Overview: Business Scenario  The course participants are new employees of eNRGCo.

com workplace provides personalized. (C) SAP AG IUT110 4 ."One-Step Business" (co-operation) .4 mySAP.building of business relationships (virtual communities) .role-specific .1.com concept consists of three areas:  The my area stands for easy access to all elements of mySAP.standard entry into all internal .platform for business co-operation .industry-specific .com area stands for the Internet intiative of SAP. Based on the results of the EnjoySAP initiative. role-based system access. Trade relations and business co-operation can be initiated and developed over the Internet.  The .individually adaptable . universal business processes and external services CO-OPERATIVE .integrated. the mySAP.application hosting .com: Overview PERSONAL INTEGRATED .integration of external services (content) .Internet business framework  SAP AG 1999  The mySAP.com.  The SAP area represents the availability of enterprise software over the Internet.

Knowledge Warehouse content  mySAP.com components: External systems via open Internet standards  mySAP. Reports (such as Business Information Warehouse reports in BW 2.com Marketplace  Any Internet or intranet Websites (C) SAP AG IUT110 5 .comInternetservices Other Internet services SAP SAP  SAP AG 1999  The Workplace contains links to information within and outside company limits. New Dimensions. R/2 Syst Syst.com Internet Com Com pp.com components: Classical and new Web-based R/3 transactions (standard R/3 System. Links can be made to:  Non mySAP.. Open Ext Ext.5 Workplace Internet Business Framework R/2 Le Leg g..1.. NonmySAP.. Standards R/3 R/3 4.comcomponents Pe Person rsonaalize lized d KM KM BW BW Webbrowser access D Dra ragg& &ReRelalattee CRM CRM Com within pan y lim i ts Pa Part rtnerr ne M Maark rkeett-. outside ppla lace ce mySAP.com Internet services: mySAP.6 FI FI LO LO Single HHR R Sign. m mySAP ySAP SEM SEM W Work orkpla place ce On Utilities Utilities In Ind duust stry ry-sp -speecific cific APO APO B2 B2B B IS-U IS-U/CCS /CCS Role Role-b -baase sed d mySAP.6 4.1C). industry solutions).

6 mySAP Utilities: The Comprehensive Solution Busi nesssI ntelligence Busines I ntelligence Str ategic EEnterprise Strategic nterpr ise MManagerial anager ial Financial Fina ncial Reg ulat or Regulat y ory && Manageme Management nt Accounting Accounti ng Accounti Accountingng Reporting /FERC Reporting/FERC Data Data Warehousing Warehousing Market ing M arketi ng Mar ket RResearch Market es earch Pr oduct/ Product/ Sal es Sales CCus ustomer tomer SServic ervic ee Program Program Sal es Manag Sales ement M anagem ent &&AAnal nal ysis ysis Brand BrandMark eting M arketing Chann els Cha nnels Management Management Engin eering && Engineering Product ion Plant PlantMaint M aintenanc en ancee Deco mmissi oni Decommissi ng oning Construction Constructi on Production Engin eering && Engineering M aintenance Mainte nance&& Transmi Transmiss ssi ion on && Operati Operations onsM anag ementnt Manageme Construction Constructi on Wor WorkkMan agement M anagement Dist ributio Distri n SServic bution ervicee Sales Sal esCCycle ycle&& Connecti C onnect on ion&&Inst Installati allation on Ser Servivic cee M eter Reading Meter Reading Billing Billi ng MManage ment anagement Manageme Manag ement nt Management M anage ment Pool/ Pool/ ISO ISO Ser Servic e vice Special Sp ecialCCusto mer ustomer Sal es CCycle Sales ycle&& Retail Retail Bi lling Billing Agreem Agreementent Process es Processes Energy Energ ydata Dat a Tr aders Traders Ri sk Risk Wholes Wh olesale ale Rec Recoonciliation nciliati on M anag ementnt Manageme Wor Workbenc kbenchh Manag M anagement ement Billing Billing &&SSettlement ett lement Invoici Invoicing ng Receivabl es Man Receiv ables agement Manag ement Thir Thirdd PParty arty Settl Settlem ement ent Business Network Human H umanRReso urce esource Fixed FixedAsset Asset Procureme Procurementnt Treasur Treas uryy Real Real Estat Estatee Manageme Managementnt Management M anage ment  SAP Customer Relationship  Finance & Controlling Management  Human Resource  SAP Supply Chain Management Management  Logistics  SAP Business Intelligence  SAP Business-to-Business E-Commerce  SAP AG 1999 (C) SAP AG IUT110 6 .1.

sales and distribution or marketing (telesales and telemarketing). SAP CRM is subdivided into four main business scenarios:  Mobile Sales Scenario: Enables field service employees to access to all the information necessary for their job.7 Customer Relationship Management (CRM) Mobile Sales Contact Center Internet Sales  SAP AG 1999  SAP Customer Relationship Management (CRM) provides solutions that enable companies to effectively maintain customer relationships throughout the entire life cycle.1. processing of incoming and outgoing E-mails and activity management (recording of all contacts in the contact center). and between companies and end-customers (B2C). CRM supports companies by understanding and anticipating the requirements of their customer base as well as those of potential customers. this forms one of the key components of SAP CRM.  Contact Center Scenario: Along with the Customer Interaction Center (CIC).  Business-to-Business Procurement (SAP BBP): The SAP solution for business activities taking place between companies over the World Wide Web. (C) SAP AG IUT110 7 .  Internet Sales Scenario: Enables electronic business activities to take place over the World Wide Web between companies. The CIC can be used in service (Service Interaction Center SIC). The CIC enables processing of incoming and outgoing telephone calls using the SAPphone CTI (Computer Telephony Integration) interface. The data is saved on a lap-top database and is regularly aligned with the CRM System.

 SAP BW requests application data in regular intervals from the allocated source systems (pull mechanism).com business component that is used to extract and analyze data from operative business applications (OLTP systems).central control R/3 Other  SAP AG 1999  The SAP Business Information Warehouse (BW) is the mySAP.for all types of user Extensive Business Content .1. This includes InfoSources.  The SAP Business Information Warehouse supports Online Analytical Processing (OLAP) and is especially suitable for processing large volumes of operative and historical data.information model.Metadata repository .8 Business Information Warehouse (BW) Efficient Analysis of Information . Besides OLTP Systems such as R/3 and SAP BBP (Business-to-Business Procurement: Business process in E- Commerce that enables employees to purchase goods and services directly from suppliers). other external data sources such as databases or online services can also be connected. InfoCubes and standard reports.efficient OLAP analysis functions .fully automated . transfer structures for all releases and communication structures and update rules for each InfoCube.  SAP BW contains all the necessary Metadata for current business processes.company comparison values End-to-End Data Warehousing Solutions .innovative and intuitive user interface .extraction of R/3 data and external data . (C) SAP AG IUT110 8 . OLTP stands for Online Transaction Processing. reports and extractors . These elements are part of the ready-to-go strategy that supports automatic data transfer with immediate analysis according to installation of the system and naming of the source system. The back-end systems therefore contain extractors that collect data and deliver it to the SAP Business Information Warehouse.

1.9 Functional Scope of the IS-U System Customer Generation Transmission Distribution service & billing All customer-related business processes IS-U/ CCS Customer Relationship Management Particular business processes PM MM Consumption Consumption Marketing entry billing Contract SD Invoicing & Sales A/R & A/P Installation Service billing Invoicing services FI Meter & Device Management CRM Work Management  SAP AG 1999 (C) SAP AG IUT110 9 .

10 Integrated and Open System Landscape Electronic SAP BW business (Internet) ITS Business objects such as business Tele Analyses partner. agreement. CTI business contracts. products and sales and distribution projects SAP IS-U/ Mobile CCS Appli- cations Back end Front end  SAP AG 1999 (C) SAP AG IUT110 10 .1.

distribution projects SAP IS-U/ Mobile CCS Appli- cations Back end Front end  SAP AG 1999 (C) SAP AG IUT110 11 .. . CTI business Intercompany Data Exchange contracts. Energy Data Management Energy Data Management sales and .1. products.. Intercompany Data Exchange activities...11 IS-U/CCS Business Processes Electronic SAP BW business (Internet) Device Management Device Management ITS Billing Billing Invoicing Invoicing Business objects Contract Accountssuch Receivable as business and Payable Tele Contract Accounts Receivable and Payable Analyses partner.

1. products. business Contracts CTI Contracts contracts. activities. Connection objects Connection objectssales and Pointsofofdelivery Points delivery distribution projects SAP IS-U/ Mobile CCS Appli- cations Back end Front end  SAP AG 1999 (C) SAP AG IUT110 12 .12 Synchronized Business Objects Electronic SAP BW business (Internet) ITS Business objects Businesspartners Business partners such as business Tele Analyses Contractaccounts Contract accounts partner.

1. Business partner transfer to target group selection 11) Automatic creation of contracts 12) IDE communication with prior supplier or transmission company 13) Automatic creation or change of SAP master data IS-U/ ----. Mobile CCS 14) Transfer of meter reading results Components 15) Billing and invoicing 16) Transfer of sales and transaction statistics to BW Back end Front 17) end Commission Optional:  SAP AG 1999 determination (C) SAP AG IUT110 13 . contracts CTI and products.13 Marketing and Sales Process 3) Transfer of target group to SAP CRM 2) Target group selection 4) Marketing planning Electronic 5) Campaign creation SAP BW 6) Campaign executionbusiness (Internet) 7) Activity management 8) Campaign feedback (BW) 9) Contract creation ITS synchronization 10) Contract Business objects 1(a) Import of external Telebusin such as business addresses to target Analyses Analysis ess group selection partner.

ment Prospect Service Level Mgmt mySAP Internet Marketing Replication via mySAP Billing & Invoicing Contract Accounting Owner Bill Recipient Installer Service Center CRM 3. Develop. &Brand System Customer ment Mgmt Tele. connection object and point ons Cable TV Service Order Work Internet Tele- of delivery Management GoodsService Contract s Customer Sales BW or Service Bus.14 System Infrastructure CRM. mySAP From R/3 master data mySAP top n analyses and other BW and transaction data Financials analyses in BW in accordance to target group with CRM 2. contract accounts. 4.ta ant gro a da rge W in a t om r B W to Fr aste o ta in B m ta t tion da lec se Data transfer BW extractors From selected target groups.1. Cust. m External and such a exter so o s pr n data n osp al ects  SAP AG 1999 (C) SAP AG IUT110 14 . Marketing Sales Cust.1C selection and other analyses in BW Flat f data iles fro . Manage.63 Services Device Management Water Waste Water District Heating Field Sales Meters/Devices/Connecti Waste Disposal Service contracts. Cust. Nonresid. Charges Self Taxes / Fees Sales Mgmt Collabor- ct Service Interaction n Center &Support ation t io xt e tra c ac Fr ra x ifi rans om ct e ec t an C sp d up al y R M sis d or s BW IS-U.Part.0 Field Sales CRM middleware Utilities Consumption Installation Sectors: Electricity Gas Entry Internet Of business partner. Marketing & Sales Service Cust. BW and mySAP Utilities Business Marketing Partners: Retention &Analysis Product Information Resid.

 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). CAD. purchasing and stockholding of devices are processed using MM components.MM Asset Management & SCADA Materials Management  SAP AG 1999  Central business partner model (R/3) => the customer is the central data object. further processing of debits occurs via FI-CA.1.  Material master records are managed in MM at the same time as device categories in IS-U.15 IS-U/CCS . => 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 billing CO: Allocation and settlement of costs related to service activities MM: Processing of material requirements and goods movement related to service activities  The results of service billing can be transferred to IS-U invoicing.Integration Model IS-U/CCS IS-U/CCS as as an an integrated integrated SD component component ofof the the FI Sales & SAP SAP enterprise enterprise Distribution information information system system Financial External Accounting Sales In Bill I-C + ct C A) / P vo i n Systems (F / R tr a ic g/ Customer A A on in information system g C O ST ME Plant Maintenance U & Customer SAP R Service Service Busine Business IS-U Entr ption Ins ervice E Partne rtner components S CA IC tall MM R y V External sum E & S ER atios PM/ Consumption Standard SAP CS components Co n n Entry SD Device Systems CO Management External systems AM PM GIS. (C) SAP AG IUT110 15 .

1.16 The Strengths of mySAP Utilities  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  SAP AG 1999 (C) SAP AG IUT110 16 .

billing.  SAP AG 1999 Device Management customer service (C) SAP AG IUT110 17 .1.17 Solutions for the New Industry Market Model Solution Map SAP Utilities Classic utility company Deregulation Generation Transmission & Distribution Sales & Distribution Generation Transmission Marketing. sales and Distribution distribution.

schedule and Supplier company settlement results Grid connection contract. grid usage contract Energy supply contract  SAP AG 1999 Business partner (C) SAP AG IUT110 18 .1.18 Deregulated Market: Business Perspective Settlement coordinator (= transmission company) Exchanges and bilateral contracts Energy Balance procurement Grid access regulations for comparison contracts use of the transmission grid. Distribution outline contract for smaller customers. schedule and settlement results Negotiated grid access.

transaction statistics and so on  SAP AG 1999 (C) SAP AG IUT110 19 . This includes customer overviews. displaying bills. IS- IS-U content for BW  Sales statistics. The master data generator is used to post-edit campaigns. Master data template  Product modeling on the basis of configured materials and pricing in SD. entering meter reading results. consumption statistics.19 Sales and Marketing in IS-U/CCS (1) Call- Call-center functionality  Faster and more direct access to all relevant information and transactions required during contact with customers is admissible.1.  Work items allow callbacks and outbound campaigns. account information and so on. changing master data.

20 Sales Processing Product selection Master data generation using mySAP CRM or change in channels: mySAP Utilities: Fixed Fixed product product information information Master Master data data template template mySAP mySAP CRM CRM mySAP mySAP Utilities Utilities Master Master data data mySAP product product product product generator generator Utilities Configuration Configuration Configuration Configuration Variable Variable product product information information Workflow  SAP AG 1999 (C) SAP AG IUT110 20 .1.

21 Sales and Marketing in IS-U/CCS (2) Internet Self Services  B2C (Business to Customer scenarios)  Registration/password change for Internet user  Maintain move-in data  Maintain move-out data  Maintain personal data  Display consumption history  Enter meter reading results  Display and payment of a bill  Issue collection authorization  Display account balance  The data is updated immediately or is transferred to the appropriate user for further processing.1.  SAP AG 1999 (C) SAP AG IUT110 21 .

1.22 Internet Self Services: Start Page Select service Enter user and password  SAP AG 1999 (C) SAP AG IUT110 22 .

C o ns um pt i oPrn i ceC ha r ge • Price profile 10 O n.0 0 Settlement  SAP AG 1999 Energy Data Management (EDM) enables you to manage consumption data and corresponding business processes.  EDM enables you to bill interval data such as RTP rates (real-time pricing) and time-of-use rates. 50 $ 5 0 . as well as procurement schedules and network profiles.Pe ak kWh 1 0 0 kWh $0 .01. – 06.  Settlement  deals with settlement processes.0 0 O f f -Pea k kW h 4 0 0 kWh $0 . amounts and charges. 25 $ 2 5 .01. EDM is particularly useful for managing and billing consumption data that is measured at specific intervals (for example load profiles and load shapes).0 0 profile Agreed price A mo un t Du e $ 1 15 . 10 $ 4 0 .0 0 • Forecast S p ot kW h 1 0 0 kWh $0 .1.23 What is Energy Data Management? Profile Billing Management Spot price Additional agreement: Spot John Smith EDM KW delivery 10 Park Avenue 12345 NY 60 • Historical Billing period profile 30 05. (C) SAP AG IUT110 23 .

MR Auto. wn Billing Billing loa meter d MR MR D Up en ata loa d data data try Meter mgmt mgmt reading Print document Other Data entry modules customer meter reading EDIFACT Device Device Management Management Public network network  SAP AG 1999 (C) SAP AG IUT110 24 .1.24 Energy Data Management 1 Load Load Auto. MR systems mgmt mgmt oa d systems systems Real-time Invoicing Invoicing w nl Do na l pricing sig Preliminary load profiles Interval billing Contract Contract EDM EXPORT IMPORT Derived d meter loa Point Point of of wn l na delivery delivery A/R A/R ++ A/P Do A/P sig MD Data E entr y Do Scheduling Scheduling Tradit. MR profile profile Auto.

30 min. 1hr)  Measurement using interval meters  Consumption billing for each interval in accordance with interval- specific conditions  Billing complies with the typical table calculation procedure  Low billing throughput  SAP AG 1999 (C) SAP AG IUT110 25 .1.25 Energy Data Management 2  Variant-based billing (IS-U/CCS)  Differentiation of various rate periods using registers  Consumption billing for each register (per rate period) using any complex billing rules  Construction of cost estimates from basic formulas  High billing throughput  Profile-based billing (IS-U/EDM)  Differentiation between fixed intervals of measurement (such as 15 min.

 SAP AG 1999 (C) SAP AG IUT110 26 .  IS-U/CCS can be used for billing and managing standard divisions as well as additional new services.26 IS-U Overview: Unit Summary  IS-U/CCS supports customer-oriented core business processes of utility and service companies.1.  IS-U/CCS is an integrated component of the SAP enterprise information system.

2 CIC Contents:  Master data  Objectives of the Customer Interaction Center (CIC)  Typical processing steps  Implementation and use  Most important application areas  Customer contacts  SAP AG 1999 (C) SAP AG IUT110 1 .

2 CIC: Unit Objectives At the conclusion of this unit.2. you will be able to:  Name the most important IS-U/CCS business objects  Describe the range of applications  Explain the elements of the Customer Interaction Center  Carry out some typical customer processes  Create and use customer contacts  SAP AG 1999 (C) SAP AG IUT110 2 .

2.3 CIC: Business Scenario  Customer call and identification via Front Office  Data environment  Display of business data  Changes to data  Change bank details  Change rates  Customer contact  SAP AG 1999 (C) SAP AG IUT110 3 .

4 The IS-U House Connection Object Apartment 1= Premise Hall Installation Installation 1: 1: Contract Contract 1:1: Apartment 3 Electricty Electricty Electricity Electricity meter meter Device Device location location Hall Hall Installation Installation 2: 2: Contract Contract Contract Contract 2: 2: account Gas Apartment 2 account Gas Gas Gas meter meter Business partner Contract Installation Installation 3: 3: Basement Contract 3: 3: Device Device location location Water Water Basement Basement Water Water meter meter Service Connection: Water Service Connection: Gas Service Connection: Electricity Supply Grid Street  SAP AG 1999 (C) SAP AG IUT110 4 .2.

5 Various Business Partners Existing Owners Debtor Tenants SAP Business partner Installer Interested party Employee  Individuals and companies  Business partner relationships  Flexible interfaces Nonresidential  Integration of business roles Group customer  SAP AG 1999 (C) SAP AG IUT110 5 .2.

2.... • Identification driver's license no. social security. depending on his or her role:  A customer receiving utility and maintenance services  A bill recipient  Supplier  A prospect targeted by marketing activities  The owner of an apartment or house (C) SAP AG IUT110 6 .. • Main utility company creditworthiness.. employee class) • .  A business partner is included in different business processes.. • License • .6 Roles of the Business Partner Business partner • Name • Address • Personal data • Communication Contract partner Installer Prospect • Payment • Type of company • Branch of industry transactions • Division license • Relationships • General data • Work field • Contact history (account class.  SAP AG 1999  The central business partner concept enables you to:  Define the business partner globally  Model different roles for a business partner in the system  The specific roles of the business partner in IS-U are:  Contract partner  Installer  Contact person  Prospect Other roles and data fields are dependent on Customizing settings.. • .

IS-U differentiates between:  Contract partner  Installer  Contact person  Prospect Other roles depend on Customizing  For each contract partner. which will incorporate customer-specific fields. company  Equal  Group. box address Partner  Bank details  Other addresses Communication Additional Data  Telephone.2.7 Business Partner Data General BP Relationships  Form of address.  A programmable interface. online  Register entry Cross-role data Role-specific data  SAP AG 1999  Business partners are divided into various groups. (C) SAP AG IUT110 7 . name  Hierarchical  Legal form. search terms  Marital Payment Addresses SAP Transactions  Standard address Business  P. fax  Identification numbers  Extensions  Legitimation  Internet. is currently being planned.O. E-mail. to which different attributes are allocated. the business partner can assume different roles. an SD business partner is created in the background. IS-U differentiates between:  Individuals  Organizations  Groups  Depending on the business context.

in legacy  Dunning control system  Dunning letter recipient  Terms of payment  Dunning block reason  Tolerance group Control Incoming payments Contract  Alternative bill recipient  Payment method  Paid by collective bill Bank details Account  account  Alternate payer  Additional bill Account assignment Outgoing payments  Where-used list for Ols  Payment method  Planning group  Bank details  Account determination  Alternate payee  Settlement category General data Dunning/payment data  SAP AG 1999 (C) SAP AG IUT110 8 .8 Contract Account Data General data Dunning data  Account name  Account no.2.

business) Bill cover Contract CA 2 sheet Account 2 Contract 4 Contract 100 CA 2/3 Contract (Elec.business) collective collective billing account CBACBA 1) Total : 50 UNI  SAP AG 1999 (C) SAP AG IUT110 9 .domestic) CA 1 Contract Partner Partner Account 1 Contract 2 100 (Water .2. . .business) Total : 400 UNI Account Accountforfor Total : 450 UNI UNI Collective Collective (Statistical Bill Bill Bill posting toto Contract Contract 5 CA 3 contract 50 Account 3 (Elec.9 Collective Bills Contract 1 Bill 150 Contract Contract (Elec. .domestic) Total : 250 UNI Contract 3 300 Bill (Gas .

 A business area is an organizational unit that covers a restricted area of activity/responsibility in your company. A contract can also be outsorted manually. the user must have authorization for both the activity and the authorization group.2.  The outsorting group determines which validations are to be carried out in billing. you specify a statistics group for a contract. • Statistics group Acct Assignment Data • Authorization group • Account determination ID Contract • Cost center • Business area Budget Billing Data • Budget billing Adjustment Scheduling Data • Budget billing cycle • Contract start/end date • Renewal dates • Cancellation dates Deregulation Fields General Data Move-In/Move-Out Data  SAP AG 1999  In the Statistics group field.  Data relevant to budget billing (the budget billing cycle.  Scheduling data is provided mainly for information purposes. 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). for instance) maintained in the contract overrides the default values defined in the portion or the Customizing settings.  The authorization group prevents unauthorized access to specified objects. It is used for determining data for sales statistics. To be able to carry out any activity protected in this way.10 Contract Data Data Relevant to Billing General Billing Data Contract Data • Joint Invoice • Contract account • Billing block reason • Division • Outsorting group • Company code • Plant/comp.  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. Value movements entered in Financial Accounting can be attributed to this business area for the purposes of external accounting. consum. for example. (C) SAP AG IUT110 10 . It allows you to display information on when a contract was signed or cancelled.

11 Connection Object Data Location Data General • Maintenance plant • Description • Location description • Processing status • ABC indicator • Notes Plant Maintenance Address • Structure • Maintenance planning Connection • Street.2. house number plant Object • Postal code. city • Maintenance planning • Political regional structure group Additional Data Attributes • Structure/equipment list • Regional structure group • Account assignment • Authorization group • Classification PM data IS-U data  SAP AG 1999 (C) SAP AG IUT110 11 .

2.12 Premise Data Location Data Connection Object  Forms the link between  Storey the premise and the  Room number regional structure  Location description Attributes Installation Premise type  Owners Premise  Can comprise several  installations to be billed  Number of occupants Technology Additional Data  Notes  Can be assigned to a  Update log device location General data Relationships  SAP AG 1999 (C) SAP AG IUT110 12 .

2.13 Installation Data Process Data Billing  Rate category  Current premise  Rate data for devices  Current business partner and registers  Current contract  Reference value Control Data Business Partner Supply or consumption Conclusion of the contract Installation    Definition of base period with the business partner  Meter reading control Regional Structure Additional Data  Linked via the premise  Installation type and connection object  Guarantee of supply  Override default meter  Notes reading unit  Update log General data Relationships  SAP AG 1999 (C) SAP AG IUT110 13 .

14 Point of Delivery Data Point of delivery ID Header data • Structure category • History • Description • Point of delivery type • Point of delivery role Point of delivery Deregulation Technical • Installation • Premise • Register • Service type • Grid (distributor) • Settlement unit  SAP AG 1999 (C) SAP AG IUT110 14 .2.

Contract account Integration with Logistics Contract (utility) Service Point of Connection Connection Installation Premise delivery object object Device Device Device category location Connection Meter reading  SAP AG 1999 (C) SAP AG IUT110 15 . appl.15 Business Objects in IS-U/CCS IS-U IS-U Business FI-CA FI-CA Regional partner structure SD. SD. CS. PM PM Cross Cross appl.2. CS.

16 What Is a Customer Interaction Center?  Large utility companies process several million customer- oriented business processes every year  There are usually special departments for this:  Customer center  Call center  Customer service agents  The IS-U Customer Interaction Center (CIC) supports these departments in the system  SAP AG 1999 (C) SAP AG IUT110 16 .2.

g.17 Customer Interaction Center: Requirements  Efficient user interface. Internet)  SAP AG 1999 (C) SAP AG IUT110 17 .2. 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. Computer Telephony Integration.

IS-U/CCS enables you to integrate external communication systems in your daily work.).18 Integration with External Communication Systems WWW Fax Letter Telephone Internet In person Archive Call center Internet integration integration integration IS-U/CCS Front Office Functions IS-U Customer Information System  SAP AG 1999  As a customer information system.  Integration with a call center solution via the SAPphone component. welcome letters. (C) SAP AG IUT110 18 .2. letters. and so on.  Access to IS-U functionality via the Internet or via an intranet. as well as archiving incoming (or outgoing) documents which are initially only available in paper form (faxes. and so on).  The following slides describe the three most important interfaces:  Archiving of documents created in IS-U (for example invoices to customers.

 The CIC/Front Office screen is divided into four different areas:  Clipboard (also called business data display): Used to temporarily save processed business objects. part. address or telephone number.  Identification (search criteria. The CIC with different vertical screen areas (see above) is the standard layout.2. Business partner Tel.obj. no. change and service bill and so on connection process  SAP AG 1999  The CIC is available in two different layouts. data finder): This is where you enter search criteria to locate a business object. Technical Call Description Information Processes  Display of business objects  Field representation of  Front Office processes severalbusiness objects  R/3 workflow processes  Examples: customer. media and telecommunications are available. Examples of search criteria include a name.  Information (business object display): Once the relevant business objects have been identified.19 The IS-U/CCS Customer Interaction Center Service Initiate Customer Customer Identification Information function workflow contact contact Customizing Identification Front Office: Initial Screen Front office Edit Goto System Help X Clipboard  Definable field selection  Temporary storage of  Use AND to join fields Context Processe s business objects  Generic search with *  Quick follow-up calls  Display results  Good contextual Search criteria Name: last/first Addr. PostCd/city/cntry Conn. contacts. In the L-shape layout (see next page).  Examples: customer contract account. and workflows which can be carried out for previously identified business objects. various types of information can be displayed. Front Office processes. selected sectors including utilities.  (C) SAP AG IUT110 19 .Cat. Activity date Customer Premise Install.  Processes: This is a list of change transactions. overview Street/house number Bus.

2. (C) SAP AG IUT110 20 .20 Customer Interaction Center (L-Shaped) Telephony Telephony Identification Identification functions functions Call Call status status Action Action box box Application Application area area Navigation Navigation •• Customer Customer overview overview area •• R/3 R/3 transactions transactions area •• User- User -defined HTML User-defined HTML pages pages •• Web Web pages pages  SAP AG 1999  The concept of the CIC (L-shaped) focuses on processing the business partner.

2.21 Workflow Inbox  In the application area of the CIC  List of all work items to be performed  E-mail and fax inbox  SAP AG 1999 (C) SAP AG IUT110 21 .

mail. letters letters utteess Exxeeccu E Customer Customer data data displayed displayed in in Call center agent CIC CIC  SAP AG 1999 (C) SAP AG IUT110 22 . letters letters (scanned (scanned documents) System System Business partner Confirmation Confirmation Workflow Workflow Work Work item in inbox for E- E- mail. fax.2. E-mail. fax.22 E-Mail and Fax in the Workflow Inbox E-mail.

2. even if the customer details are incomplete. such as CTI  SAP AG 1999  The CIC enables customer service agents to quickly identify customer or processes.  CTI = Computer Telephony Integration (C) SAP AG IUT110 23 .23 Typical Uses of the CIC: Identification Identification Of: Supported by:  Business partners and  Data finder associated data such as connection objects  Integration of external communication systems.

24 Typical Uses of the CIC: Information Identification Information Supported by:  Modifiable lists  Information masks  SAP AG 1999  Once the customer has been identified. (C) SAP AG IUT110 24 . his or her installations. the agent can display information on the customer.2. as well as previous and current transactions.

2.  In many cases. changes to bank details. the business process can be carried out completely using one or more of these service functions. (C) SAP AG IUT110 25 .25 Typical Uses of the CIC: Front Office Process Carry Out Front Identification Information Inform Office Processes if Required Supported by:  Predefined and company-specific business processes (for example name changes. various types of complaints)  SAP AG 1999  Standard business processes are supported by a number of service functions in IS-U/CSS that are designed for use in the Front Office of a utility company. move-in processing. interim billing.

 The lifetime of a Front Office process is limited to the lifetime of the Front Office session that initiated the process.2.26 Front Office Processes Sequence of steps that can be processed:  by an agent  in one step Example: changing bank details Change bank/payment Log customer data for a contract contact account  SAP AG 1999  A Front Office process is a sequence of steps that is specially designed for processing a particular business transaction. (C) SAP AG IUT110 26 .  All steps in a Front Office process can be carried out by a customer service agent.

administration of disconnection orders)  Customer-specific workflows (for example rate changes)  SAP AG 1999  If the business process cannot be fully processed immediately.27 Typical Uses of the CIC: Workflow Perform FrontOffice Office Initiate Identification ntifica Inform Information Processes Workflow if Required if Required Supported by the SAP Workflow Management System by means of:  Pre-defined workflows (for example service connection processing.2. These can be modified to meet individual requirements. (C) SAP AG IUT110 27 . the remaining steps of the process can be coordinated by means of a workflow.  IS-U/CCS contains a number of standard workflows.  You can also create your own workflows.

28 Using R/3 Workflow: Changing a Rate (Example) I'd like to sign up for Front Office: an off-peak enter rate.2. inquiry Customer service agent Letter of Check notification feasibility Change/create Change (programmable) contract meter Data in Sales agent Billing agent Technician  SAP AG 1999 (C) SAP AG IUT110 28 .

29 Typical Uses of the CIC: Customer Contact Carry out Customer service Initiate Initia contact Identification Informattion ion workflow orkflow function log if necessary if necessary ne IS-U/CCS Contact Management supports:   The logging of CIC contacts  Automatic creation of customer contacts as the final step in Front Office processes and workflows  Manual creation of customer contacts for logging purposes  SAP AG 1999  Customer contacts can be created. changed or displayed either directly in the Customer Interaction Center or in the menu under Utilities Industry -> Customer service -> Create/Display/Change Customer contact.2. (C) SAP AG IUT110 29 .

Internet. type and the corresponding activity. (C) SAP AG IUT110 30 . telephone calls  Correspondence.30 Contact Management in Customer Service WWWWWW Fax Letter Telephone Internet In person  Recording of contacts resulting from:  Personal customer service. e-mail  Evaluation of contacts for:  Comprehensive overview of customer service  Quality and efficiency of consulting processes Utility company  SAP AG 1999  Contact management in IS-U/CCS is designed to record all types of contact between the utility company and the customer.  Customer contacts can be classified during creation according to class. fax.2.

 Contact activity describes the type of activity between the business partner and the utility company. online company code  Incoming. E-mail.  Contact classes are used to group customer contacts according to their general subject area. account information. and budget billing. fax. such as division or Internet. billing.2. Example include information.31 Customer Contact Data General References  Business partner  Reference to any  Business partner business objects  Contact number  Permissibility can be set Process Description Notes  Date. Example include rates information. (C) SAP AG IUT110 31 . and so on. telephone. outgoing  Authorization group  SAP AG 1999  Contact classes and activities can be created according to the requirements of the utility company. time Customer Contact  User-defined text  Contact class in IS-U  Indicator for additional  Activity documents Additional Data Communication  Self-defined fields  In person.

2.  Contact management enables you evaluate the complete contact history of business partners  SAP AG 1999 (C) SAP AG IUT110 32 .32 CIC: Unit Summary  The CIC is oriented towards the needs of information- based and operational processes  The processing interface is an efficient work environment that provides quick access to critical information  The transparency and flexibility of the CIC provides an optimal link to business processes.

and correctly. 1-1 Which four units make up the CIC? What are their tasks? Unit 1: _____________________________________________ Task: _____________________________________________ Unit 2: _____________________________________________ Task: _____________________________________________ Unit 3: _____________________________________________ Task: _____________________________________________ Unit 4: _____________________________________________ Task: _____________________________________________ (C) SAP AG IUT110 33 . A sound working knowledge of the CIC will help you achieve this. completely. you will be able to: • Describe the objectives and the areas of implementation of the CIC • Use the CIC to carry out processes efficiently As an employee in the customer center. you must process customer inquiries quickly. This increases both customer satisfaction and efficiency at work.2.33Customer Interaction Center Exercises Unit: Customer Interaction Center (CIC) Topic: Using the CIC At the conclusion of these exercises.

1-2 True or false? 1-2-1 The CIC is the initial access point for users who handle both simple and complex business processes. __________________________________________________ 1-2-2 The CIC provides flexible. powerful search functions. enter the serial number in the Device data area. __________________________________________________ 1-2-5 The data finder always identifies the business partner as the result of a search. __________________________________________________ 1-2-3 The CIC dictates how the processes are handled. Enter the address of the connection object in which the device is located:___________________________________________________________ _________________________________________________________________ ____________________________________________________________ (C) SAP AG IUT110 34 . In the CIC. • To leave the data finder. __________________________________________________ 1-2-4 The CIC automates business processes. __________________________________________________ 1-3 To which business partner is the device with serial number TB010110## allocated? What is the address of the connection object? Proceed as follows: • Call up the data finder using the button • On the Technical data tab page. choose Continue. choose Continue again.

How business partners does the connection object contain? Proceed as follows: In the selection area. Enter the street and house number. Premise number Short text 1-5 End the contact. Business partner no. Confirm your entry by choosing Enter. 1-4 Which premises are contained in the connection object from task 1-3? Proceed as follows: In the navigation area (Environment tab page). Choose the Connection object environment activity using the right mouse button. (C) SAP AG IUT110 35 . 1-6 Identify all the customers using the connection object on 0## Main Street. such as Main*. select the premise. use the street of the connection object as the search criterion. You can also make a partial entry. First and last names of business partner Choose Mr Petersheim and complete the following table: Question Answer How many contract accounts are assigned to Mr Petersheim? Which types of contract does Mr Petersheim have? Which devices are assigned to Mr Petersheim? 1-7 Display the data environment of the premise to which contract TB010110## belongs.

1-9 Display the data for the devices and complete the table below: Information Electricity Gas meter Water meter meter Serial number Device category (or material) number Description of the device category or material Division Current business partners Current device location 1-10 How can you recognize that advanced search criteria have been entered? ____________________________________________________________ ____________________________________________________________ (C) SAP AG IUT110 36 . save the devices belonging to the premise to the clipboard. 1-8 From the data environment in task 1-7.

2-1-2 You provide customer TB010110## with general information which you make more specific by supplementing it with information from the object link in the customer contact. Customer Interaction Center (CIC) Exercises Unit: Customer Interaction Center (CIC) Topic: Customer contact management At the conclusion of these exercises. Insert contract TB010110## and contract account TB010110##. The link to business objects allows you to access relevant information instantly. Check the list of object links. switch to the detail display of the business object. 2-2 Display contacts 2-2-1 Display all customer contacts in the CIC for customer TB010110##. you will be able to provide a more efficient service to customers. 2-1 Create a customer contact using the following information: 2-1-1 Customer TB010110## reports a complaint by telephone. If necessary. How many contacts does the customer have? Of what type? ________________ Date Class Action Type (C) SAP AG IUT110 37 . You record the complaint in a customer contact. you will be able to: • Create various customer contacts • Evaluate and display customer contact history By completely documenting all customer contacts.

Display all customer contacts entered with contact class 8 (complaint). From the SAP Easy Access menu. 2-2-2 Use the customer overview in the CIC to display the current customer contacts for customer TB010110##. use the information system. ______________________________________________________ 2-3-2 Customer contacts are divided into contact classes and further sub-divided into contact activities. 2-2-3 Evaluate all the customer contacts. ______________________________________________________ 2-3-3 Customer contacts can only ever be displayed for one business partner at a time. ______________________________________________________ (C) SAP AG IUT110 38 . choose: Utilities Industry  Information System  Report Selection  } Customer Service  List of Customer Contacts. To do this. 2-3 True or false? 2-3-1 All customer contacts are always created automatically.

you have been assigned to telephone service today. ______________________________________________________ ______________________________________________________ ______________________________________________________ (C) SAP AG IUT110 39 . As an employee in customer services. The following exercises are based solely on his Private Account 0##. you will be able to: • Explain the central business partner model and how it is integrated in the R/3 System. display the customer overview. 3-1-1 Enter the selection criteria. Customer Interaction Center (CIC) Exercises Unit: Customer Interaction Center (CIC) Topic: Master data in IS-U/CCS At the conclusion of these exercises. The customer notifies you of new bank details that are to be used for bank collections for his private account. enter the new bank details. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 3-1-2 Switch from customer overview to the change mode for the business partner. Describe the menu paths and mouse actions you use for this procedure. 3-1 Customer TB010110## has two contract accounts. and enter the current bank details for bank collections for the customer’s private account. • Use the customer overview • Process each step from the customer overview. • Start from the CIC. You are using the CIC as your central working environment. and save your data. Describe the menu paths and mouse actions you use for this procedure. but others want to have their data changed. Some customers only wish to obtain information.

______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 3-3 Change the contract description for residential electricity contract TB010130## of the community account. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 3-2-4 Enter a remark in the customer contact and save your data. Describe the menu paths and mouse actions you use for this procedure. and enter the new bank details as the payment method for incoming payments. Return to the CIC. ______________________________________________________ _______________________________________________________ _______________________________________________________ 3-2-2 Enter the new bank details for the business partner and save your data. Describe the menu paths and mouse actions you use for this procedure. choose the private account. The customer notifies you of new bank details that are to be used for bank collections for his community account. ______________________________________________________ 3-1-3 Switch from the customer overview to change modus for the contract account. The following exercises are based solely on his Community Account 0##. select the contract account of customer TB010110## and call the Change bank data activity. Describe the menu paths and mouse actions you use for this procedure. Change the contract description of the residential electricity contract of the communal account from the old description residential electricity contract 0## to the new (C) SAP AG IUT110 40 . Save your changes. 3-2 Customer TB010110## has two contract accounts. Describe the menu paths and mouse actions you use for this procedure. Describe the menu paths and mouse actions you use for this procedure. 3-2-1 In the navigation area ( Environment tab page). ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ 3-2-3 Enter the new bank details as the payment method for incoming payments in the contract account and save your data.

______________________________________________________ 3-5-2 A contract account can be assigned to several business partners. 3-4-1 When was the last budget billing due for business partner TB110110##? ______________________________________________________ 3-4-2 How much was the budget billing amount? ______________________________________________________ 3-5 True or false? 3-5-1 Data for a business partner who is also a contract partner. List the changes for each log. ___________________________________________________________ ___________________________________________________________ ___________________________________________________________ ___________________________________________________________ End the contact. description communal electricity contract 0##. ______________________________________________________ 3-6 Name three different logs that are updated when master data is created or changed. __________________________________________________________ 2. Massachusetts Ave 0##). 1. 3-4 (For countries with budget billing procedures): Customer Constance Bishop (TB010120##. use contract TB010130##. ______________________________________________________ 3-5-3 The contract account is the contract partner’s customer account. To do this. Describe the menu paths and mouse actions you use for this procedure. • Call up the customer overview • Provide information on the budget billings. asks for information on her budget billings: • Enter the search criteria to identify the customer. __________________________________________________________ (C) SAP AG IUT110 41 . ______________________________________________________ 3-5-4 The contract contains rate data for all divisions. and contact person has to be entered more than once. installer.

__________________________________________________________ (C) SAP AG IUT110 42 . 3.

______________________________________________________ 3-7-3 The connection object is managed as a piece of equipment in the Plant Maintenance component (PM). ______________________________________________________ 3-7-7 The installation groups together the measuring devices of a division and a premise for the purpose of joint billing. ______________________________________________________ 3-7-8 The installation manages basic billing control parameters. ______________________________________________________ 3-7-2 The connection object can comprise one or more premises. ______________________________________________________ 3-7-6 The premise is managed as a functional location in PM. 3-7 True or false? 3-7-1 The connection object is always a building. ______________________________________________________ 3-7-5 Individual devices are installed in the connection object. _____________________________________________________ 3-7-4 The device location is subordinate to the connection object. ______________________________________________________ (C) SAP AG IUT110 43 .

CIC contact management. 1-2-5 False. CIC processes and workflow processes are integrated in the CIC. For example. Unit 4: Action box Task: Calls specific business processes. 1-2-4 True. 1-2-3 False. for example SAP Business Workflow. It supports the user in implementing processes. True. The CIC is very flexible and is easily adapted and integrated with process flows for different user groups. The CIC enables you to enter a variety of information in order to find the data of a business partner. Unit 3: Application area Task: Provides overview pages containing inbox for SAP business workflow. (C) SAP AG IUT110 44 .2. The data finder only identifies the business objects you were searching for. 1-2 1-2-1 True. Unit 2: Navigation area Task: Provides specific information in response to customer inquiries. you can determine a business partner by means of their name or by their device number. The CIC integrates both simple information and environment displays and workflow processes that are used to control comprehensive business processes. 1-2-2 True.34Customer Interaction Center (CIC) Solutions Unit: Customer Interaction Center (CIC) Topic: Using the CIC 1-1 Unit 1: Identification (selection area) Task: Selects data using flexible search criteria. Starts complex business processes. and so on. This means that business processes are controlled and forwarded automatically. These objects must belong to a business partner.

Enter your search criteria. Boston TB010120## 0## Massachusetts Avenue. 1-4 Select the premise in the navigation area (Environment tab page). In the Device data area. enter the serial number TB010110## in the Serial number field. Choose the End contact button. First and last names of business partner TB010110## Elmer Petersheim TB010120## Constance Bishop Choose Mr Elmer Petersheim. Premise number Short text TB010110## 0## Massachusetts Avenue. The answers are as follows: (C) SAP AG IUT110 45 . Choose Continue. 1-6 In the identification area. The Choose the Connection object environment by clicking on the right mouse button. search for the street of the connection object. 1-3 Call the CIC. the second data call confirms the search criteria. If the system finds data that meets the search criteria. Exit the data finder by choosing Choose again. Business partner no. all the business partners appear in the hit list. the system searches using the selection criteria. Activate the data finder by choosing Open the Technical Data tab page. The first time you call the data. The system then displays the data. The data environment for the business partner is displayed. All the master data belonging to the connection object is also displayed. Since this connection object contains more than one business partner. The system displays the connection object in which the device is located. Boston 1-5 Return to the CIC (F3). From the SAP Easy Access menu choose: Utilities Industry → Customer Service  Front Office/Customer Interaction Center  Customer Interaction Center.

double click on it. This selects the line. You can now answer the following questions: Information Electricity meter Gas meter Water meter Serial number TB010110## TB010180## TB010120## Device category (or material) TD-DRA-00 TD-GA-00 TD-WA-00 (C) SAP AG IUT110 46 . You have now added the object to the clipboard. Choose To clipboard or F8. contract account. and two for electricity. repeat the following procedure for each device: Click on the device. you can identify the following relationships: Four utility installations are allocated to the tree structure:. return to the CIC. This is a flat-rate installation that does not measure consumption or energy. To display a device. open the structure as far as the device level. To save all the devices in the clipboard (corresponding tab page in the navigation area). Once you have added all the devices to the clipboard. and business partner is allocated to each utility installation. gas. To confirm your actions. call the Clipboard tap page in the navigation area. Meters are allocated to all the other installations. 1-9 On the Environment tab page of the navigation area. One electricity installation contains no devices. water. Question Answer How many contract accountsMr arePetersheim has two contract accounts: assigned to Mr Private account: TB010110## Petersheim? Community account: TB010120## Which types of contract doesMr MrPetersheim has four utility contracts: Petersheim have? Electricity contract: TB010110## Gas contract: TB010180## Water contract: TB010120## Electricity contract: TB010130## Which devices are assigned Mr to Mr Petersheim has 3 devices: Petersheim? Double-rate meter: TB01011## Water meter: TB01012## Gas meter: TB01018## 1-7 Select the premise and choose Premise environment. A utility contract. 1-8 You are in the environment of premise TB010110##. From the tree structure. Repeat for all devices in the premise.

number Description of the deviceIS-U double-rate meter IS-U gas meter IS-U water meter category or material Division 01 Current business TB010110##TB010110## TB010110## partners Technical device TB010111DL0## TB010111DL0## TB010111DL0## location 1-10 Call up the data finder and select the Other search criteria tab page. The button turns green when advanced selection values have been added. (C) SAP AG IUT110 47 .

(C) SAP AG IUT110 48 . select 1 (unfriendly employee). press the Add object button. The residential electricity contract has been added to the link list. Utilities Industry → Customer Service  Front Office/Customer Interaction Center  Customer Interaction Center. Save the contact. The system calls the data finder so that you can search for a specific contract. enter 8 (complaint). Solutions Unit: Customer Interaction Center (CIC) Topic: Customer contact management 2-1 2-1-1 Call the CIC. enter 1001 Information In the Activity field. call the Create contact function (call group Customer). In the Contact class field. Enter additional text on the information in the editor lines. Enter TB010110## in the contract field and choose Enter. Choose an object role that refers to the Utility Contract object type. Carry out the same procedure to add Contract account TB010110## to the link list. 2-1-2 Choose the action box call again. Change to the Business objects tab page. Select your customer. In the editor lines at the bottom of the screen. To add a link. In the Class field. In the action box. In the Action field. enter 1001 General information provided. enter a reason for the complaint and save the contact.

you activate the detail display. (C) SAP AG IUT110 49 . This gives you a list of all customer contacts for this customer. Double-clicking on the individual lines displays detailed information on the customer contact. Return to the CIC. in the Customer overview tab page.04. 2-2 2-2-1 In the navigation area choose the Documents tab page. Enter the following search criteria: Contact class: 8 (Complaint). deactivate the contact log. 2-3 2-3-1 False. The following contacts exist: Date Class Action Type 08.98 Move-in New customer moves in 03. Choose Refresh. Choose Execute or F8.98 Move-in New customer moves in 03.10. By double-clicking on the individual customer contacts. The system creates the CIC contact automatically.04. 2-3-2 True. 2-2-3 From the SAP Easy Access menu choose: Utilities Industry  Information System  Report Selection  } Customer Service  List of Customer Contacts. Customer contacts can also be created manually. To stop the customer contact being created. All contacts relating to complaints are displayed. 2-3-3 False. You can configure the system to display customer contacts in the application area. The information system can analyze all customer contacts according to different criteria. call the Customer overview (call group Information) The most recent customer contacts are listed in the center table.98 Move-in New customer moves in Today’s date Complaint Unfriendly employee Today’s date Information General information provided 2-2-2 In the action box.

Under Incoming payments. Choose Change contract account. (C) SAP AG IUT110 50 . This brings you to the master data change screen of the contract account. 3-1-3 Position the cursor on Private Account 0##. Save your changes. The new bank details are displayed (double- clicking refreshes the screen). Double-click on the account Private Account 0##. Return to the customer overview. enter GIRO and in the Cntry field. Save your changes. You have now entered the new bank details for the business partner and have returned to the customer overview. Switch to the Payment/Taxes tab. Double- click the Bank Details ID field. This brings you to the master data display of the contract account. Return to the CIC. 3-1-2 Place the cursor in the address field of the business partner. In the Bank key field. Switch to the Payment transactions tab page. enter an account number. Solutions Unit: Customer Interaction Center (CIC) Topic: Master Data in IS-U/CCS 3-1 3-1-1 Once you have identified the customer. This brings you to the master data change screen for the business partner. You have now defined new bank details for incoming payments and have returned to the customer overview. In the data area Incoming Payments you can read the bank details for incoming payments in the field Bank details ID. Switch to the Payments/Taxes tab page. In the Bank acct field. enter GIRO in the Bank details Id field. Choose Change or F5. enter the key US . Enter the new bank details. enter a bank sort code using F4. call the Customer overview (call group Information). Enter the new bank details for incoming payments. In the ID field.

Double-click the Bank Details ID field. True. Return to customer overview. You have now entered new bank details for the business partner and are brought automatically to the previously chosen contract account. In the ID field. 3-4 3-4-1 Choose the customer overview for business partner TB110110##. However. 3-2-4 In the last step. you can define the contract account so that it can be allocated to several business partners. The new bank details are displayed (double-clicking refreshes the screen). enter a bank using F4. a business partner can have several contract accounts. the contract account is configured in such a way that it can only be allocated to a single business partner. Position the cursor on the budget billing data. In IS-U/CCS. A customer account is managed for a contract account. 3-2 3-2-1 In the navigation area. Enter the new description Community electricity contract 0## in the Text Contract field. In the Bank key field. 3-2-2 This brings you to the business partner to record the new bank details. You have now defined new bank details for incoming payments. 3-5-3 True. You can use the SAP business partner model to assign different roles to a business partner. Save your changes. Switch to the Payment Transactions tab page. 3-2-3 Switch to the Payment/Taxes tab page. Enter a comment in the editor lines at the bottom of the screen and save the changes. enter the key US. enter the key GEM . Save the changes and return to the CIC. enter the key GEM in the ID field. 3-4-2 The cumulative amount is located in the corresponding column. 3-5 3-5-1 False. 3-5-2 False. 3-3 In the navigation area. Now enter the new bank details. Call the Change bank data activity using the right mouse button. you created a customer contact. select the contract and choose the Change contract activity. The contract account is a structure which allows the billing of posting data for contracts or benefit types which have the same collections/disbursements agreements. When you customize the contract account category. select the second contract account. Only role-specific data which was not entered previously has to be added. Enter an account number in the Bank acct field. Save your changes. In the Cntry field. (C) SAP AG IUT110 51 . Double-click to display the budget billing plan. To do this.

and for managing contract accounts receivable and payable. The connection object is at the top of the hierarchy of functional locations. 3-7-3 False. The billing class and rate category are allocated to the installation. 3-7-4 True. are grouped together and assigned to a premise. Here. The contract is an agreement between a business partners and utility company which applies to a particular division. 3-7-8 True. These influence how billing runs. 3-7-5 False. the following three logs are located under the Extras menu: 1) 1) Creation data 2) Field changes 3) Contract changes 3-7 3-7-1 False. which are to be jointly billed. The premise is used exclusively in IS-U/CCS to group together installations of different divisions. Devices. Devices are installed in device locations and are therefore indirectly allocated to a connection object. 3-7-2 True. A connection object can also be a piece of property. 3-7-7 True. or a building site. 3-7-6 False. registers. A premise can contain several installations. a well. 3-5-4 False. The rate data is stored in the installation and in the installation structure. Device locations are modeled as functional locations in the PM component and the connection object is the higher-level concept. These can refer to the same or to different divisions. the generation of budget billing plans. The contract contains control data for billing. (C) SAP AG IUT110 52 . and fixed payment settlement factors. Double-click on contract TB010130## to display the master data. 3-6 Enter the business partner key in the data finder and identify the business partner data.

(C) SAP AG IUT110 1 .3 Move-In/Out Contents:  The business processes move-in. including sending the bill to the customer moving out and a welcome letter to the customer moving in. and move-in/out. and move- in/out  Effects on both the business and technical master data  SAP AG 1999  You can enter all the data required for moving in or out using the pre-defined transactions move-in. move-out. This enables you to process the whole transaction immediately. move-out.

3. move- out.2 Move-In/Out: Unit Objectives At the conclusion of this unit. and move-in/out from the CIC  Explain the changes to the master data  SAP AG 1999 (C) SAP AG IUT110 2 .  Implement the business processes move-in. and move-in/out. move- out. you will be able to  Describe the business processes move-in.

 You carry out the move-in in the CIC as follows:  Check if the customer is an existing business partner  Enter the premise and move-in date  Enter and check the personal data  Check the meter reading results  SAP AG 1999 (C) SAP AG IUT110 3 .3.3 Move In/Out: Business Scenario  A customer reports a move-in.

a contract is concluded for each Contract installation selected at one account or more premises Contract Installation  SAP AG 1999 (C) SAP AG IUT110 4 .3.4 Move-In Definition Move-in Business partner At move-in.

3.5 Move-In: Prerequisites Connection Connection  The following technical master object object data must be entered before move-in:  Connection object Premise Premise  Premise  Installation  The device can be installed Installation Installation before move-in. but this is not a prerequisite. Device  SAP AG 1999 (C) SAP AG IUT110 5 .

6 Move-In: Business Master Data  Should be re-used for existing Business Business customers partner partner Contract Contract  Can be re-used for existing account account customers Contract Contract  Is created during move-in  SAP AG 1999 (C) SAP AG IUT110 6 .3.

.  Request cash security deposit  Create budget billing plan  Create welcome letter (C) SAP AG IUT110 7 . 1 FI -CA document 3 FI -CA document Move-in complete Move-in Customer moves in Move-in July Mrs..3.7 The Move-In Process Customer Contract Validation Security Welcome visit/call letter Contract Bank details 1 1 Payment method 1 A lternative payer . as necessary  Create contract  Optional steps for move-in  Add contact data  Prepare and carry out move-in meter reading  Record results of move-in meter reading  Maintain rate data  Check the billability of the billing structure  Manually maintain creditworthiness or result of automatic creditworthiness calculation. Smith 31 BB Move-In/Out amount $250 Business Meter Budget Customer partner.. account reading billing contact plan  SAP AG 1999  Essential steps for move-in  Identify premise  Identify or create customer  Select contract account and edit or create account.

Business partner Tel.obj.3. part. no.Cat. Street/house number Bus. Activity date Processes Information Environment Change Call Description Call Description  SAP AG 1999 (C) SAP AG IUT110 8 . PostCd/city/cntry Conn.8 Move-In: Options for Processing Parameters Parameters  Premise  Premise  Business partner  Classification of new  Move-in date business partner Special feature  Move-in date  Transfer of existing contract account possible Existing New customer customer Call in CIC Front Office: Initial Screen X Front office Edit Goto System Help Context Proces ses Search Name: last/first criteria Addr.

3.9 Move-In: The IS-U House Connection object Apartment 1= Premise Hall Installation Installation 1: 1: Contract Contract 1:1: Apartment 3 Electricity Electricity Current Current meter meter Device Device location location Hall Hall Installation Installation 2: 2: Contract Contract Contract Contract 2: 2: account Gas Apartment 2 account Gas Gas Gas meter meter Business partner Contract Installation Installation 3: 3: Basement Contract 3: 3: Device Device location location Water Water Basement Basement Water Water meter meter Service conn.: Water Service connection: Gas Service connection: Electricity Supply grid Street  SAP AG 1999 (C) SAP AG IUT110 9 .

3.10 Move-Out: Business Scenario  A customer reports a move-out  You can carry out the move-out from the CIC using the following steps:  Identify the customer  Enter the move-out date  Maintain the personal data (new address)  Create a meter reading order  SAP AG 1999 (C) SAP AG IUT110 10 .

3...11 The Move-Out Process Customer reports Contract Final meter Move-out move-out reading results confirmation X Contract Bank detail s 1 Payment method Alternative payer .. FI -CA document FI -CA document 1 1 1 3 Move-out Move-out complete X Customer moves out July 31 BB amount $250 Contact data Budget Final billing billing plan  SAP AG 1999  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 (C) SAP AG IUT110 11 .

12 Options for Move-Out Processing Parameters Parameters  Business partner  Premise or  Move-out date  Business partner  Move-out date Business Move-out partner moves out Call: in CIC Front Office: Initial Screen X Front office Edit Goto System Help Context Proces ses Search Name: last/first criteria Addr. no. PostCd/city/cntry Conn.Cat. Business partner Tel. part.3.obj. Street/house number Bus. Activity date Processes Information Environment Change Call Description Call Description  SAP AG 1999 (C) SAP AG IUT110 12 .

3.13 Move In/Out: Business Scenario  A new customer reports a move-in and the move-out of the previous customer  You can carry out the move-in/out from the CIC using the following steps:  Check if the new customer is already a business partner  Enter premise and move-in/out date  Enter and check the personal data  Enter the meter reading results  SAP AG 1999 (C) SAP AG IUT110 13 .

3.14 The Move-In/Out Process Move-out Move-in Tran spor t  SAP AG 1999 (C) SAP AG IUT110 14 .

 Move-in/out for business partner. you have the following processing options:  Move-in/out for premise.Cat.You can process the move-out or move-in of two different business partners into one premise.You can process a move-out for a business partner from one premise and their move-in to another premise. Activity date Processes Information Environment Change Call Description Call Description  SAP AG 1999  In the move-in/out transaction. no.obj. (C) SAP AG IUT110 15 . part. Business partner Tel.3. Street/house number Bus.15 Options in Move-In/Out Processing Parameters Parameters  Business partner  Premise  Move-out date  Move-out date  New premise  Business partner or  Move-in date classification of new business partner  Move-in date Move-in Move- /out for in/out for business premise partner Call in CIC Front Office: Initial Screen X Front office Edit Goto System Help Context Proces ses Search Name: last/first criteria Addr. PostCd/city/cntry Conn.

16 Move-In: Master Data Business Business Connection Connection partner partner object object Contract Contract Premise Premise account account Contract Contract Installation Installation Move-in Device  SAP AG 1999 (C) SAP AG IUT110 16 .3.

Move-in Customer out 1 2 Contract Contract 11 Contract Contract 22 Nov 1st Dec 1st Jan 1st Feb 1st Mar 1st.17 No Changes to Installation Data 02/01/.2000 Move-in Customer Move.3. Apr 1st May 1st Installation  SAP AG 1999 (C) SAP AG IUT110 17 .

12/16/1996 Terminated contract 10004713 12/17/97 .18 Installation History Installation 10815 01/01/90 .08/14/1992 Terminated contract 10004711 08/15/92 .12/31/9999 Current contract 10004714 Information on the installation's data environment  SAP AG 1999 (C) SAP AG IUT110 18 .03/31/1993 No contract assigned 04/01/93 .3.

and move-in/out  Implement the business processes move-in.3. and move-in/out from the CIC  Explain the changes to the master data  SAP AG 1999 (C) SAP AG IUT110 19 . move- out. move-out.19 Move-In/Out: Unit Summary You are now able to:  Describe the business processes move-in.

choose the Technical data tab page and enter the street and house number in the connection object area. 1-1-1 Identify the customer The customer tells you that her name is Constance Bishop. Execute the Identify premise call that is located in the Identify call group (action box). At present she is living in 0## Massachusetts Avenue in Boston. In the Data Finder. If the system can determine a premise. also in Boston. A customer comes in person to the service center and informs you that she would like a utility contract for an apartment that is currently vacant. You use the CIC to perform the move-in. Enter the number of the premise here: _____________ Choose Environment  Data. 1-1-2 Identify the new premise Mrs Bishop requires utility contracts for her new apartment 0## East Side Highway. it is displayed in the navigation area on the Clipboard tab page. Select the entry and display the object (right mouse click . with today’s date as the start date. MA 02100. (Once you have done this. 1-1 A business partner moves in to a premise. and that she is moving into a new apartment. Choose Save Enter. Identify the customer in the system.20Move-In/Out Exercises Unit: Move-In/Out Topic: Move-In At the conclusion of these exercises. and answer the following question: Which installations from Mrs Bishop’s new apartment are found in this premise? Enter them in the following table: Installation number Division (C) SAP AG IUT110 20 . you should be able to access the premise from the clipboard).Display). you will be able to: • Perform the full move-in process in the system • Display the move-in document generated.3. Identify the premise into which Mrs Bishop is moving. the business partner should be available in the CIC. living in Boston. Once you have done this.

The system prompts you to maintain the move-in date in an additional step in the CIC (specify move-in parameters). To do this. • When you are asked. 1-1-3 Perform the move-in. Change the outgoing payment method accordingly. Enter today’s date. • Name/Admin. You are now in the move-in processing screen. you do not need to make any changes here. tab page In the contact data. Division Contract text 01 Electricity contract – 0## East Side Highway 02 Gas contract 03 Water contract — 0## East Side Highway (C) SAP AG IUT110 21 . Use the business objects that you saved to the clipboard. record the fact that Mrs Bishop came by in person. • Payment Data tab page Check the payment methods that have been entered. Gas and Water tab pages. • Contract Data tab page Enter the following values in the new contracts: To switch between the contracts. Return to the CIC. execute the M/in: known customer call under the Move I/O call group in the action box Perform the move-in from the CIC . Do you want to adopt an existing contract account?. answer Yes. • Perform the move-in for all the installations in the premise. Select both entries. • Bank data tab page Since Mrs Bishop has confirmed that she will continue to use the same account. activate the Electricity. Mrs Bishop has agreed that any credit may be transferred to her bank account.

______________________________________________________ 1-2-4 During move-in. In the Documents tab page of the navigation area. • Return to the CIC by pressing F3. The system displays the new data you have created. choose Refresh. 1-1-6 Customer environment Display the customer environment for Constance Bishop. Display this contact (double click on the object) and choose the Business Objects tab page. ______________________________________________________ (C) SAP AG IUT110 22 . 1-1-4 Display the current business partner data. • Save the move-in. a business partner and his/her contract accounts and contracts must already exist in the system. Here you can find the move-in document. Therefore. 1-2 True or false? 1-2-1 The move-in is a workflow process ______________________________________________________ 1-2-2 A move-in connects the contracts of a business partner to the installations of a premise. A new contact exists. Note that both premises are visible in the lower part of the screen. Choose Refresh in the navigation area (Environment tab page). the system does not automatically propose it as the meter reading at move-in. ______________________________________________________ 1-2-3 The installation contains the move-in date. use the Select All button to select all the registers and choose Estimate. • MR Data Since the meter reading at device installation was taken so long ago. Display this document and make a note of the document number: ______________________________________________________ 1-1-5 Customer overview Display the customer overview for Constance Bishop.

Identify the customer in the system. you will be able to: • Perform the full move-out process in the system • Display the move-out document generated. In addition. A customer telephones and informs you that she is moving out at the end of the month. 2-1 Business partner move-out 2-1-1 Identify customer Sarah Peterson lives in 0## Massachusetts Avenue in Boston. Perform the move-out from the CIC and enter the customer’s new address. MA 02116. Once you have executed this step. request a meter reading order. How many contract accounts does she have? ___________________________ How many utility contracts? ___________________________ Complete the following table (with the corresponding key values): Division Contract Installation Are there any outstanding receivables for Mrs Smith’s account? ______________________________________________________ (C) SAP AG IUT110 23 . choose the go to the selection area and choose either the Customer Environment or Customer Overview call. To do this. the business partner should be available in the clipboard 2-1-2 Obtain an overview of the data environment of Mrs Peterson. Exercises Unit: Move-In/Out Topic: Move-Out At the conclusion of these exercises.

(C) SAP AG IUT110 24 . Use the Business partner Sarah Peterson business object that has been saved in the clipboard. • MR Data tab page Generate a new meter reading order for the meters. 2-1-3 Perform the move-out Do this from the CIC using the Move-Out Partner call under the Move-I/O call group. return to the CIC and refresh the data. • Save the move-out. • Move-out date Last day of the current month • Address data tab page Enter Mrs Peterson’s new address: 0## Independence Avenue in Boston.

you will be able to: • Perform a move-in/out in the system • Display related documents • Understand the move-in/out data environment Harry Jones is moving into premise 0## Constitution Avenue in Boston. Mr Jones reports the move-out and his subsequent move-in. Exercises Unit: Move-In/Out Topic: Move-In/Out At the conclusion of these exercises. Harry Jones does not exist. 3-1 Move-in/move-out of a premise 3-1-1 Identify the new customer Find out if Harry Jones is already a customer. Create the business partner in the selection area. chosoe the Create button and maintain the following data: Field name Value Title Mr Category Person Sex Male Last name Jones First name Harry0## Street Independence Avenue Number 2## Post code 69120 City Boston Country US (C) SAP AG IUT110 25 . and provides the meter readings for all the registers. To do this. MA 02129 tomorrow. The previous tenant moved out of the premise today.

C. MA 02129 business objects from the clipboard. 3-1-3 Perform the move-in/out Do this from the CIC (Premise move-in/out). You can now attempt to identify Mr Jones again (press Enter twice) 3-1-2 Identify the premise and its environment • Identify the premise on the ground floor of 0## Constitution Avenue in Boston. • Move-in: MR Data tab page Check the meter reading data. • Move-in: Payment data tab page Mr Jones agrees to a direct debit and would like any credit balances to be transferred to this account. Use the Connection Object Environment call under Information call group in the action box. You can check the dates here (such as move- in or move-out date. Have the move-out meter readings been (C) SAP AG IUT110 26 . please attach your group number to the end of the first name. Business partner number: _____________________________ Name: _____________________________________________ • Select the premise and choose Copy to Clipboard or F8. • Enter the business partner’s new address: 0## Apple Tree Lane in Washington D. • Move-in: Bank data tab page Mr Jones has account number 08154711## at the Mellon Bank in Boston (under ID 1). Choose Save Enter. Use the business partner Harry 0# Jones and Premise 0## Constitution Avenue in Boston. You are now in move-in processing. • Move-out: tab page MR Data Estimate the meter reading results • Move-out: Save the move-out. You are now in move-out processing. You are on the initial move-in/out screen. • Find out who was previously registered as a business partner at that address. You should therefore subsequently search for Harry (0###) Jones. Choose Save Enter. To enable each group to carry out the exercise. MA 02129.

Note that the contracts for the premise’s installations can be displayed historically. transferred? What is the meter reading type? • Save the move-in. 3-1-4 Data environment for the premise following move-in/out Display the premise environment. Which new contracts were created? Division Contract Installation • Switch the view from today’s data to a view which comprises the data for a particular period (for example 01/01/1998 to tomorrow). (C) SAP AG IUT110 27 .

M*. • The business partner identified is now also displayed in the clipboard. or initial House number 0## or initial Post code 02100 or initial City Boston or initial • Choose Enter until the data is displayed in the navigation area. 1-1-2 Identify the new premise. • Enter the following data in the search criteria: Field name Value Street East Side Highway or Ea* House number 0## • The premise required is now in the clipboard (Clipboard tab page in the navigation area). (C) SAP AG IUT110 28 .3.21Move-In/Out Solutions Unit: Move-In/Out Topic: Move-In 1-1 Business partner moves in to a premise Utilities Industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center 1-1-1 Identify the customer • Enter the following data in the search criteria: Field name Value Last name Bishop or Bis* First name Constance or Co* Street Massachusetts Avenue.

• In the premise display. 1-1-3 Peform the move-in • The business partner line on the clipboard is selected. • Choose the M/in: known customer call under the Move I/O call group. Choose Execute or F8. Installation number Division TB060110## Electricity TB060120## Water TB060170## Gas • Return to the Customer Interaction Center (using the F3 function key). • Enter today’s date in the move-in date field. • Confirm that you want to perform the move-in for all three installations on the premise by pressing Enter or the green checkmark. • The number of the premise is TB060110##. choose the value Personal. choose Environment  Data. Using field selection (F4). B method Bank ID – outgoing 1 (C) SAP AG IUT110 29 . • Name/Administration: Contact data tab page The personal visit of Mrs Bishop to the customer center is saved under contact type. • Payment data tab page Field name Value Outgoing payment. • Select the premise line. To display the desired premise information: • Select the premise in the clipboard and choose the Display call via right mouse click. answer Yes. • When you are asked. Do you want to adopt an existing contract account?.

since all steps can by carried out by one employee at the same time and without interruption. • Proceed as described in the exercise. However. the installation is assigned to a contract after move-in. a new business partner can be added and the contracts and contract account created. 1-1-5 Customer overview • Choose Customer overview from the Information call group. 1-2-4 False. 1-2-2 True. 1-2-3 False. 1-1-4 Display the business partner data. During move-in. • Return to the Customer Interaction Center. 1-1-6 Customer environment • Choose Customer environment from the Information call group. • Return to the Customer Interaction Center. (C) SAP AG IUT110 30 . move-in and move-out dates are managed in the contract. 1-2 True or false? 1-2-1 False. • Contracts tab page Divisio Contract text n 01 Electricity contract – 0## East Side Highway 02 Gas contract – 0## East Side Highway 03 Water contract – 0## East Side Highway • Save the move-in.

of contract accounts Contract account number 1 TB010140## (C) SAP AG IUT110 31 . 2-1-2 Navigation area: Customer overview and customer environment. • The business partner identified is now also found in the clipboard. • How many contract accounts does Mrs Peterson have? No. • Choose Customer environment from the Information call group. Solutions Unit: Move-In/Out Topic: Move-Out 2-1 Business partner moves out Utilities Industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center 2-1-1 Identify the customer • Enter the following data in the search criteria: Field name Value Last name Peterson or Pe* First name Sarah Street Massachusetts Avenue or Ma* House number 3## or initial Post code 02116 or initial City Boston or initial • Choose Enter until the data is available in the navigation area. • Return to the Customer Interaction Center.

2-1-3 Perform the move-out • The business partner line on the clipboard is selected. • How many utility contracts does Mrs Peterson have? 2 Division Contract Installation Electricity TB010160## TB010160## Water TB010170## TB010170## • Are there any outstanding receivables for Mrs Smith’s account? No. • Enter the move-out date • Maintain your data on the Administration/Name and Address Data tab pages. • Return to the CIC. (C) SAP AG IUT110 32 . • Choose the Move-out partner call that is found under the Move I/O call group. Field name Values Street Independence Avenue House no. • Save the move-out. 0## Post Code 69190 City Boston. • Update the Environment and Documents tab pages in the navigation area. • MR Data tab page Activate the Service Notification/Order indicator.

Business partner Name TB000110## Ashley Smith • Return to the Customer Interaction Center. • Choose Enter until the data for the new business partner created appears in the clipboard. 3-1-2 Identify the premise and its environment • Proceed as described in the exercise. no object from category Business partner was found. Solutions Unit: Move-In/Out Topic: Move-In/Out 3-1 Move-in/out of a premise Utilities Industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center 3-1-1 Identify the new customer • Enter the following data in the search criteria: Field name Value Last name Jones First name Harry(###) • Search results: Using the specified selections. • Create the business partner. (C) SAP AG IUT110 33 .

• Select both objects from the clipboard. You can correct any data here if necessary. 0## Post Code 69190 City Washington D. method B (Outgoing paym. • Choose the Premise move-in/out call that is found under the Move I/O call group. • Save the move-out document./bank transfer) Bank ID – outgoing 1 • Move-in: MR Data tab page The meter reading type is 04 (derived meter reading). 3-1-3 Perform a move-in/out for a premise. (C) SAP AG IUT110 34 . • The system switches to process the move-in. • Save the move-in document. method D (Direct debit) Bank details ID 1 Outgoing payment. • You start move-in/out processing by pressing Enter. • Move-out: MR data tab page Select all registers Choose the Estimate button. • Move-out: Address data tab page Field name Values Street Apple Tree Lane House no.C. • Move-in: Bank data tab page Field name Values ID 1 Country US Bank key 70080010 Bank account 08154711## • Move-in: Payment data tab page Field name Values Incoming payment.

(C) SAP AG IUT110 35 . 3-1-4 The data environment of the premise after the move-in/out • New contracts Division Contract Installation 01 Internally assigned contract TB000110## number 03 Internally assigned contract TB000120## number • Data environment from 01/01/1998 – to date Press the button Period F7 and enter 01/01/1998 in the Valid from field.

IS-U uses functions which already exist in the various components of the R/3 standard system to manage these orders. (C) SAP AG IUT110 1 .g. calculated. billed to a customer in a utilities company. planned. e.4 Work Management Contents:  Technical objects in Work Management  Customer-related Work Management (Installation services)  Interfaces to external systems  SAP AG 1999  A large number of work orders are accepted. carried out and if necessary. in the online documentation and in the PM handbook under PM . These functions are merged with IS-U-specific business processes in Work Management and industry-specific functions are added.  Work Management uses a large number of functions from the Plant Maintenance (PM) and Customer Service (CS) components.The functions in detail. These functions are described extensively in the documentation for PM.

you will be able to:  Describe the tasks of Work Management  List the most important interface systems of Work Management  Define the functions of service and installation orders  Carry out simple processes in the system in the area of Work Management  SAP AG 1999 (C) SAP AG IUT110 2 .2 Work Management: Unit Objectives At the conclusion of this unit.4.

(C) SAP AG IUT110 3 . extension or removal of technical equipment  SAP AG 1999  The day to day business of a utility company includes processing a large number of work orders.  There are two different types of work orders. internal work orders and external work orders (which relate to Customer Service). planned. calculation. Internal work orders are mapped with plant maintenance orders in the Customer Service (CS) component. External work orders are mapped with service orders in the Customer Service (CS) component. executed and when necessary. calculated. billed to a customer.3 What Areas does the Work Management System Cover?  Acquisition. planning. 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. The orders must be accepted.4.

4. Generation Generation Transmission Transmission Distribution Distribution •• Power Power distribution distribution Plant Plantservicing servicing •• Installation Installation Network Network services services •• Electricity Electricity supply supply Plant Plantmanagement management •• Meter Meter reading reading  SAP AG 1999 (C) SAP AG IUT110 4 ..4 Utility Management Services Services for which Work Management can be implemented: Typical services for private / commercial customers .

4.5 Work Management: Technical Objects  Technical objects  Installation services  Interfaces  SAP AG 1999 (C) SAP AG IUT110 5 .

6 Overview of Technical Objects Description: Description: Technical objects in Technical objects with a direct transmission and distribution reference to the customer can be reproduced in IS-U. Example: Example:  Transformer substations  Connobj Plant Plant Customer  Transmission lines Maintenance Service  Premise  Transformer stations IS- IS-U  Device location PM/CS  Transformers  Devices  Switching stations  Device relationship Technical objects in the supply area  SAP AG 1999  Object links: connections between individual systems  Hierarchy between functional locations and equipment. (C) SAP AG IUT110 6 .  Classifications: Describe technical data of all object types.4.

) 571 571 Field Field Field Field Field Field Field Field 01 01 02 02 01 01 02 02 Line Line no.4.7 Supply Grid Pylons (equip. no. 186 186 Line Line no.) (func. no. (func. no. 187 187 (func.) Distribution Distribution station station STST 435 435 Distribution Distribution station station ST ST (functional (functional loc.) loc. loc. 189 189 Object connection used to connect two systems with different Field Field Field Field hierarchies 01 01 02 02 Line network with subsections Field Field 03 03 Distribution station with transformer fields Distribution Distribution station station ST ST 768 768  SAP AG 1999 (C) SAP AG IUT110 7 .) loc.) loc. 188 188 Transformer fields fields Line Line no. no.) Field Field 03 03 Transformer Line Line no. Field Field 03 03 (func. loc.

for example.) 0539802 0539802 125. 0716192 0716192 (equipment) (equipment) (func. loc.8 Connection Object Connection obj. loc.01 125. (func.  Since the technical installation is a piece of equipment.  A maximum of one technical installation can be created for each division in each premise. loc. it can be subject to regular maintenance.4.01 Devices (equipment)  SAP AG 1999  The technical installation is division-dependent. (C) SAP AG IUT110 8 . An equipment is created in PM automatically.256.256.) Premise Technical installations (equipment) Premise Transformer Connection Dev.

4.9 Work Management: Services  Technical objects  Installation services  Interfaces  SAP AG 1999 (C) SAP AG IUT110 9 .

technical measure installation.. . monitoring...10 Installation Services Premise Premise Domestic installation services Damage repairs Monitoring of domestic installations Device services (installation/removal) me te rea r no: Maintenance of appliances ding 32 : __ 4561 ___ _ Special meter readings OFF ON Reconnection/shutdown Other on-site services  SAP AG 1999  The tasks of installation services center around the connection object and the device location. External installations: heating. elevators.4. installation control.  Certification. . air conditioning. fire protection.. security. installing.. (C) SAP AG IUT110 10 . meter reading  Break-in protection.. energy consulting . Services may relate to equipment in the utility company or at the customer's installation. elevators. maintaining. extending Own installations: connection. for example:  Consulting.

activity type. several objects can be entered. the updating of key figures in the PMIS with value categories. assemblies. and/or materials with serial numbers. priority. excavator Billing rule Costs (planned/actual)  SAP AG 1999  Header data is information used to identify and administer work orders. traffic Production resources lights. the person who created the order and the person who last changed it.  Production resources (e. fire extinguisher. units of measure. wages Examples: materials. reference object. maintenance notifications. control key.  The data in the billing rule states who is usually responsible for the costs. and special heavy goods vehicles) are also needed to execute the order. This information applies to the whole order. In the object list. be changed during the first steps of the billing process for the order.g. dates.11 Basic Structure of a Work Order Examples: order type. however. availability Examples: protective clothing. Material list storage location. quantities. equipment.4.  Materials are spare parts that are needed and used to execute the order.signs. Examples of header data are the order number.  The cost data informs you of the estimated costs. crane. protective clothing. and the updating of these key figures with actual costs. dates for order execution.  Processes are used to describe the work to be carried out according to the order (the process includes the work center. item category.  The object list contains functional locations. A single object can be entered in the order header as a reference object. (C) SAP AG IUT110 11 . the relevant cost categories for the order. description Equipment (assembly) Object list Functional locations Maintenance notifications Examples: work center. but are not actually used in the order. Processes description. plant. description. Order header priority. batch. tools. order type. as well as the planned and actual costs of the order. the time required and the control key). It can. standard time. The data is taken from the master record of the reference object.

4. Availability is checked. An order can be created directly. reserving replacement parts or defining working hours.12 Sequence of Order Processing Entry/notification Planning Release Printout Execution Confirmation Technical completion For service orders only Invoicing Billing Commercial completion  SAP AG 1999  Processing starts when a customer or employee reports an outage.  Typical planning tasks include defining work processes. Other technical information is also entered to document repairs and define the status of the technical system.  Once work is complete. disruption or other request (such as a modification request).  Execution includes obtaining replacement parts from the stock and actually executing the order. or on the basis of a notification. (C) SAP AG IUT110 12 .  The order is then transferred for scheduling and control. the actual times required to complete the work are recorded. 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. capacity required is provided and the necessary shop papers are printed.

You can use configuration in the customer order or the technical object to define and analyze individual instructions.t external resources device Technical object Instructions Service Customer Service product order order Service material Configur.  You can assign a general maintenance task list to a service product. A service product is a service that is sold in SD and performed in PM. These documents are linked using a service product. Sales view Price information Characteristics Values Dependencies  SAP AG 1999  IS-U uses the customer order from the Sales & Distribution application component (SD) and the service order from the Plant Maintenance component (PM) to manage customer-related business transactions...4. Connection objec. (C) SAP AG IUT110 13 .  The system copies the general maintenance task list and the technical objects into the service order in the PM component. materials. You can also specify a technical object (such as equipment) for which the service is to be performed.13 Service Product: Concept Description of energy resources for work.

200 UNI Connection type A Type B 1.500 UNI 4.2 h per m Service Service object object Quotation.14 Service Product: Create Service Connection Service Service product product Service material Instructions Configuration 1. Secure excavation Excavation per m 150 Type of ground: Light Only for soft ground UNI Length: 10m 3. Lay cable Connection boxes Material: X m cable Type A 1. Install connection boxes Internal service Yes Time: 1h BB amount for Material: Connection box internal service 300 UNI 5.4. Dig trench Time: 0. customer customer order order Service Service order order  SAP AG 1999 (C) SAP AG IUT110 14 .5h per m Tool: Excavator Cable per m 60 UNI Chars Values 2. Quotation. Fill trench Time: 0.

(C) SAP AG IUT110 15 . If the service is not invoiced according to consumption. a billing request is created in the SD component. but on a flat rate. the invoicing procedure is based on the sales order. (5) The customer service representative generates a sales order. it is also possible to create the invoice for the service in IS-U/CCS and to offset it with consumption billing.e. if the actual costs incurred are to be billed). (8) If the service is invoiced according to consumption (i.15 The Installation Services Process Customer Document 3 4 1 IS-U/ 10 Front office CCS FI-CA UTILITY BILL P. As an alternative to invoicing in SD. 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). (6) A service order is created automatically in the background if this was not created with the quotation (3). (2) The customer service representative creates a customer quotation in the Sales & Distribution (SD) component. (9) The invoice is triggered and posted in the SD component. Order items can be automatically transferred from the quotation. #: Customer Premise Qty Shipped Price Total Description Workflow Management Qty Ordered SD 2 5 DATE SALE SPE RSON To tal S ubt otal Sales Tax 9 Invoicing: Request for Billing Quotation Order Installation quotation request services OR 8 IS-U/ 6 PM/CS CCS 7 Work Invoicing: installation order Supply services  SAP AG 1999  Management of a service connection could be performed as follows: (1) A customer requests a quotation for the installation of a service connection. (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.4. (7) The service connection is made on site.O.

 (C) SAP AG IUT110 16 . (10) The invoiced amount is then entered as a debit amount in the FI-CA component.

Trigger Confirm invoicing service order Customer Technician Agent Agent  SAP AG 1999  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.4.16 Create Service Connection Create Accept customer order quotation Create Create service order quotation Customer Agent System Agent Workflow Create Payment service conn. (C) SAP AG IUT110 17 .

4.17 Work Management: Interfaces  Technical objects  Installation services  Interfaces  SAP AG 1999 (C) SAP AG IUT110 18 .

4.18 Possible Configuration of an Interface Scenario R/3 MDI Mobile Customer Mobile Standard Service orders devices devices Completion service confirmations Work Work Service orders Decentralized Decentralized Management Management confirmations resource resource planning planning Applications Outage Outage confirmations notifications and orders Situation monitoring Outage Outage SCADA Transformer analysis analysis station Geographical outages data AM/FMGIS Connection information  SAP AG 1999  MDI: Mobile Data Interface  SCADA: Supervisory Control and Data Acquisition  GIS: Geographical Information System  AM/FM: Asset Management / Facility Management (C) SAP AG IUT110 19 .

19 Technical Objects in Work Management and GIS Object ID Transformer Transformer Connectivity Transformer Transformer station station information WMS Connection Connection Connection Connection object object Object ID Connectivity information: GIS Business Device Device Device Connector Device location location CCS GIS  SAP AG 1999 (C) SAP AG IUT110 20 .4.

 The repair order is automatically created. (C) SAP AG IUT110 21 .  You select the corresponding technical object from the displayed customer overview screen.20 Device Repairs Customer complains about a faulty device Agent selects the service object in the CIC The service order. instructions.4. tools and materials are sent to the responsible technician  SAP AG 1999  In the CIC you can trigger the generation of a repair order by first selecting the customer and starting the process.

21 Work Management: Unit Summary You are now able to:  Identify the most important tasks and interface systems in Work Management  Carry out simple processes in the system in the area of Work Management  Describe which external systemscna be used in conjunction with Work Management  SAP AG 1999 (C) SAP AG IUT110 22 .4.

Under the Environment tab page in the navigation area.4. Identify the business partner. select the dual rate meter and access the Front Office process Create repair order by means of a right mouse click. 1-1 Create a service order using the CIC. 1-1-2 Which order number has been assigned by the system? _________________________________________________________ What is the customer contact number? _________________________________________________________ 1-1-3 Which work center has been determined? (C) SAP AG IUT110 23 . you will be able to: • Perform the Front Office process “Create service order”. Massachusetts Avenue0## in Boston reports a device fault. Create a service order (repair order). using the CIC. 1-1-1 Business partner Elmer Petersheim.22Work Management Exercises Unit: Work Management Topic: Service Orders At the conclusion of these exercises. You will become familiar with a sub-area of Work Management.

Choose order display and display the Operations tab page. Customer contact number: __________ Service order number: __________ 1-1-2 You can also determine the service order from the clipboard in the navigation area or from the customer contact in the Business objects tab page (select and right mouse click on Display in each case). You can display both documents by selecting them and choosing Display (right mouse click).4. Expand the structure of Elmer Petersheim’s private account to the dual rate meter and select this. (C) SAP AG IUT110 24 . Contacts and service orders are listed under the Documents tab page in the navigation area once you have pressed Refresh. Enter the data and confirm this by pressing Enter. Utilities Industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center 1-1-1 Use the search functions in the CIC to determine your business partner. The service order is created in the background. Access the front office process by right mouse clicking and choosing Create repair order.23Work Management Solutions Unit: Work Management Topic: Service Orders 1-1 Create service order. By pressing Enter a second time. the customer data will be recorded in the Environment tab page. Save the customer contact. 1-1-3 The work center is recorded in the service order.

5 Device Technology Contents:  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  SAP AG 1999 (C) SAP AG IUT110 1 .

5. you will be able to:  Describe the function of the device category  Process device-related activities  Definition of the device category and device features  Creation and delivery of devices  Explain device inspection  Sampling procedure  Certification  Explain how the device category and the device are integrated in the standard SAP System  SAP AG 1999 (C) SAP AG IUT110 2 .2 Device Technology: Unit Objectives At the conclusion of this unit.

maintenance. integration in Materials Management and Asset Management SAP Utilities  SAP AG 1999 (C) SAP AG IUT110 3 . instrument panels)  Organization of billing-related data (such as rental prices. billing. and inspection  Controlling device stocks in terms of quantity and value. meter readings)  Recording of comprehensive device history as the basis for meter reading.3 Demands on Device Management  Technical modeling of complex devices and installation structures (such as integrated water meters.5.

4 Device Management: Business Scenario  Creation and delivery of new devices  Definition of the device category and device information  Ordering and posting the goods receipt for the new device  Inspection and certification of devices  SAP AG 1999 (C) SAP AG IUT110 4 .5.

5.5 Device Technology: Device Category  Device category as the basis for device definition  Devices and registers  Device lifecycle  Device inspection  SAP AG 1999 (C) SAP AG IUT110 5 .

07. year: 1997  Valid from 01. LGY-980701-300  Single-rate meter that is subject to certification  Manuf. one decimal place  Valid from July 1. year: 1998  Six pre-decimal places. 1. by Landis&Gyr  Plastic housing and external seal  Prod. year: 1998  Valid from Jan. by Siemens  Prod.97  Serial number AEG-980101-125  Manuf. 1998  Serial no.6 The Device and the Device Category Device category Device  Serial number Sie-970701-503  Manuf. by AEG  Prod.5. 1998  SAP AG 1999 (C) SAP AG IUT110 6 .

=> Basic functions of device categories. e.7 Modeling of Devices Basic device cat. such as:  Meters  Transformers  Pressure regulators Device category 1 => Features of similar devices  Definition of technical device data Device category 2  Recording of inspection and certification periods  The device category corresponds to the material in the MM component => Specific device data Device 1  Device number/serial number  Activity dates. (Example: electrical voltage)  ARCRs (audio frequency ripple control receivers) transmit information via the electricity grid by means of audio frequency modulation. or meter Device 2 reading  Certification and maintenance data Device 3  "Device" corresponds to "equipment" in the Plant Maintenance (PM) component  SAP AG 1999  Examples of basic device categories:  Meters measure consumption  Transformers convert. removal. such as installation. temperature sensors (C) SAP AG IUT110 7 .5.  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.g.

the input/output group.8 Integration with Logistics IS-U Device management Logistics Device category Material Device Equipment  SAP AG 1999  IS-U functions of device management include:  Technical data such as the register group. certification.  Installation. in addition to rate data  Organization and carrying out of meter readings in the service territory  Inspection: sampling procedure. and command group and so on.5. 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 (C) SAP AG IUT110 8 . as well as removal and replacement of devices  Installation structure for modeling devices and register relationships.

5.  SAP AG 1999 (C) SAP AG IUT110 9 .9 Definition of Device Category Device category The device category groups together devices with the same features (data). Device categories are managed as materials with a material number in the Materials Management application component.

5. price • Price class • Allocated documents • Notes Logistics Certification • Storage • Warehouse management Device category • Certification requirement • Transport data • Certification period • Quality management Planning Additional data dependent on basic device category • Procurement planning • Register group • Price estimate • Winding group • Forecasts • Input/output group MM data IS-U data  SAP AG 1999 (C) SAP AG IUT110 10 .10 Device Category Data Basic data General • Construction class • Description of material • Function class • Value.

An input/output group can also be maintained for information purposes (such as for service technicians).11 Possible Elements of the Device Category Function-related Informative Material MM Register group Device category IS-U Input/output group Winding group Command group  SAP AG 1999  Certain functional element groups are required. depending on the basic device category. (C) SAP AG IUT110 11 .  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). an input/output group may be assigned for technical descriptions of the available device interfaces.  Allocation of a winding group in which the billing data is recorded is obligatory for devices of the TRANSFORMERS basic device category. However. if required. Examples:  Devices of the basic device category METERS must be allocated to a register group.5. if desired.

5.12 Device Category: Device and Register  Device category as the basis for device definition  Devices and registers  Device lifecycle  Device inspection  SAP AG 1999 (C) SAP AG IUT110 12 .

Devices are managed in the Plant Maintenance (PM) application component as pieces of equipment with serial numbers.5.  SAP AG 1999 (C) SAP AG IUT110 13 . or control and protect other instruments. process data.13 Definition of Devices Device category Device A device is an instrument that is used to measure consumption.

inspection status Processes: installation. plant and location. planning plant • Ownership status • Maint. goods issue. (C) SAP AG IUT110 14 . premises Meter reading results. planner group • Certification data • Main work center PM IS-U  SAP AG 1999  The device master record is divided into various sections (tabs):  General data: technical data. year of replacement. winding group. the equipment status is updated (ESTO. year • Maintenance plant • Manufacturer. and disconnection Master data: business partners. reference data. manufacturer data  Location data: area assignment and account assignment elements  IS-U data: Technical data: register group.g. General • Equipment category • Device category. connection object. removal. AVLB.  When devices are moved (e. The status of the device informs the user that a certain business process has been performed. installation. command group (depending on the device basic category) Certification /inspection data: year of certification. device location. certification status. • Maint. goods receipt. designated plants Serialization data: allocated to material and serial number with stock information. (Example: ESTO means that the device was entered in the system via a goods receipt posting and is available in a warehouse). modification.5.desc.14 Device Data Header data • Material and serial no. prod. basic General and number category • Inventory number • Status • Lock status • Weight/volume • Change documents • Reference data • Time slices • Manufacturer data • Stock information Processes • Installation and removal Processes Device • Modification and • Maintenance orders disconnection • Service orders • Certification • Messages • Meter reading • Capacity planning Device-specific data Plant maintenance • Group data. location. INST). removal). lot. cat.

This can refer to the actual instrument or simply the display inan electronic device.5. The register is identified by a register number in the device.15 Definition of a Register Device category Device Register A device that meters consumption.  SAP AG 1999 (C) SAP AG IUT110 15 . energy. and so on.

Example: Meter reading results from two registers that are connected by a control relationship can only differ by a maximum of 1%. (C) SAP AG IUT110 16 . the meter reading result is not accepted and is assigned the status "implausible".5. meter reactive energy or active reader power • Date • Display type. If this tolerance is exceeded. such as Register • Type of reading. transformer • Status Meter reading Register relationships • Number of meter reading results per meter reading • Relationship type • Indicator: nonmetering • Relationship register register • Operation code Sample register Technical data relationship Process data  SAP AG 1999  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.16 Register Data Register General configuration Meter readings • Register category • Recorded meter reading • Register type (time zone) • Estimated meter reading • Pre-decimal places • Multiple allocation • Decimal places Technology Meter reading • Quantity unit • Reason • Register code.

5.17 Device Technology: Device Lifecycle  Device category as the basis for device definition  Devices and registers  Device lifecycle  Device inspection  SAP AG 1999 (C) SAP AG IUT110 17 .

Connection Integration Register Register MR with Logistics group service  SAP AG 1999 (C) SAP AG IUT110 18 .18 Central Data Objects . appl.Integration in Logistics Business Regional partner structure FI-CA Contract document account Billing document Contract (Utility supply) (Utility supply) Point of Premise Connection Installation delivery object IS-U IS-U FI-CA FI-CA Device Device category Device location Cross Cross appl.5.

IS-U/CCS does not provide inventory management functionality. Inventory Management (MM-IM) and Plant Maintenance (PM).5.19 Device Life Cycle Purchase Purchase MM PM requisition order Goods receipt Goods Retirement Transfer issue Inspection/ Inspection/ certification/ certification/ Installation IS- IS-U reprogramming reprogramming Removal/ Device management replacement Installation  SAP AG 1999  Devices are created in an integrated system using standard R/3 components. 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. however.  Although device installation is performed within IS-U/CCS. it is. The entire goods procurement process can be performed in an optional first step (purchase requisition ordering and so on). However.  If the Materials Management (MM) component is not implemented. (C) SAP AG IUT110 19 . based on a modified version of the PM component. it is also possible to create devices directly in IS-U/CCS. 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. such as Purchasing (MM- PUR).

5.20
Documentation for the Device Lifecycle

 Specification of the device: device category, device
IS-U  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
 Purchasing: purchase orders, inquiries/quotations, outline agreements
MM
 Warehouse logistics: transport, stocktaking, transfer posting
 Inventory management: goods movement, reservation
 Valuation, stocktaking, material requirements planning

 Maintenance of technical objects and equipment
PM  Work planning, maintenance planning
 Maintenance processing

 Service contracts: contracts, maintenance plans
CS  Service processing: notifications, orders, completion
confirmations
 Service planning: scheduling, work plans
 SAP AG 1999

(C) SAP AG IUT110 20

5.21
Device Technology: Device Inspection

 Device category as the basis for device definition
 Devices and registers
 Device lifecycle
 Device inspection

 SAP AG 1999

(C) SAP AG IUT110 21

5.22
Introduction: Device Inspection and Certification

 External certification involves a device being inspected
by a state inspection authority. If a device passes an
inspection according to the prescribed margins of error, the
SAP Utilities device is certified for the calibration validity period.

 Internal certification involves the utility company
voluntarily inspecting a device according to company
standards. When the internal certification period expires,
the device is inspected again in accordance with the
company's criteria and the certification is renewed.

 In the certification procedure, you can either inspect all
devices or a sample of devices.

 SAP AG 1999

(C) SAP AG IUT110 22

5.23
Certification Procedures Overview

4567,8
4567,8
Sieme ns

Siemens Proper ty no..

4567,8 4567,8 Prop erty no.. SIE-$/)($%)/

SIE-$/)($%) /

Siemens Sieme ns

Property no.. Property no..

SIE-$/ )($%)/ SIE-$/)($%)/

4567,8
4567,8
4567,8
4567,8 Siemens 4567,8
Sieme ns 4567,8
4567,8
Prop erty no..
Proper ty no.. 4567,8 Sie mens
Siemens SIE-$/)($%)/ Sie mens
SIE-$/)($%)/ Sie mens Property no..
Prop erty no.. Property no..
Sieme ns
Siemens Property no..
4567,8 SIE-$/)($% )/
SIE-$/)($%)/
Property no.. SIE-$/)($%)/
4567,8 SIE-$/)($%)/
Property no..
4567,8 SIE-$/) ($%)/
SIE-$/)($%)/ Siemens
Sieme ns
Si emens Property no..
Property no..
Pr operty no.. SIE-$/)($%)/
4567,8 SIE-$/)($%)/
SI E-$/)($%)/

Sieme ns 4567,8 4567,8
Property no..
4567,8 SIE-$/) ($%)/ Sie mens
Siemens
Property no.. 4567,8
4567,8 Proper ty no..
Siemens
SIE-$/)($%)/ 4567,8 SIE-$/)( $%)/
Property no.. Siemens
4567,8 SIE-$/)($%)/ Siemens
Property no.. Siemens
Property no..
Siemens
4567,8 SIE-$/)($%)/
Property no..
SIE-$/ )($%)/
Prop erty no..
SIE-$/)( $%)/ 4567,8
SIE-$/)($%)/
4567,8 Sieme ns

Property no.. Sieme ns

Si emens SIE-$/)($%)/ Property no..

Pr operty no.. SIE-$/)($%)/

SI E-$/)($%)/

Device
category Device
A category
B

Sample Periodic replacement list
4567,8 4567,8 4567,8 4567,8 4567,8
4567,8 4567,8
4567,8
Siemens Sieme ns Siemens Siemens Siemens 4567,8 4567,8
4567,8 Property no.. Si emens Sie mens
Prop erty no.. Proper ty no.. Property no.. Property no.. Sieme ns 4567,8 Pr operty no.. 4567,8 Property no..
SIE-$/)($%)/ SIE-$/)( $%)/ SIE-$/)($%)/ SIE-$/)($%)/ 4567,8 Proper tySIE-$/ )($%)/ Sie mens Siemens
4567,8 PropertySIno..

Replacement
no..
Siemens 4567,8
E-$/)($%)/ SIE-$/)($%)/
Property no..
Sieme ns
4567,8 SIE-$/)( $%)/
Property no..
Siemens
Siemens 4567,8 SIE-$/)($% )/
Property no.. 4567,8 Property SIE-$/)($%)/
no..
SIE-$/)($%)/ Siemens Sie mens
Prop erty no.. SIE-$/) ($%)/ SIE-$/)($%)/
Si emens Property no.. Pr operty no..
SIE-$/)($%)/ Siemens Sie mens

orders for sample
Pr operty no.. SIE-$/)($%)/ SIE-$/)($% )/
Property no.. Property no..
SI E-$/)($%)/

Replacement
SIE-$/)($%)/ SIE-$/)($%)/

devices and spare orders for all
sample devices devices
 SAP AG 1999

 You certify the devices in device category A individually (since, for instance, they may be particularly
prone to errors, or because the number of devices is too small to allow use of the sampling procedure).
Therefore, these devices are included in the periodic replacement list and are removed. All of the devices
are then inspected. When they pass inspection, they are certified individually.
 You certify device category B using the sampling procedure, which requires that only a certain
percentage of the devices (sample devices) have to be removed. The sample devices are determined
using the lot procedure. If the devices pass the inspection, then the internal certification periods of all
devices assigned to this lot are increased by the time period set in Customizing (for example, for 4
years). Normally, the checked devices themselves are certified individually (for example, for 16 years).

(C) SAP AG IUT110 23

5.24
Certification Procedure

Description: Description:
Only a representative sample Devices due for certification are
of devices is removed for removed completely and
inspection and replaced. replaced by identical devices.

Procedure: Periodic Procedure:
Sample
 Create lot replacement  Create periodic replacement
list list
 Compile lot
 Determine lot devices  Select device categories

 Perform first drawing  Create list in foreground or
background
 Inspection IS-U  Replacement orders created
automatically

Certification
of devices

 SAP AG 1999

(C) SAP AG IUT110 24

5.25
Sampling Procedure

 Description:
 Used for selecting and placing devices in sample lots.
 A defined number of devices are drawn for inspection from this
lot.
 The results of the inspection determine the renewal period of
the lot.
 Goals:
 Official lots:
Renewal of the calibration validity of the lot devices if the
sample devices are certified.
 Internal lots: Quality control

 SAP AG 1999

(C) SAP AG IUT110 25

5.26
Inspection Using the Sampling Procedure

Conduct
Conduct
Create
Create Compile
Compile Determine
Determine first
first
lot
lot lot
lot lot
lot devices
devices drawing
drawing

Conduct
Conduct Check
Check
second
second inspection
inspection
drawing
drawing devices
devices

no
? Inspection
passed
? yes

Certify
Certify
Break
Break up
up lot
lot inspection
inspection
devices
devices

Transfer
Transfer Renew
Renew
devices
devices to
to lot
lot
PRL
PRL

 SAP AG 1999

 The flow chart shows the typical flow of the sampling procedure. Certain steps, however, can be
omitted, depending on your settings in Customizing. (For example, a second drawing is normally not
possible).
 If required, you can use the standard R/3 Quality Management component (QM) to organize and manage
inspection data. This component contains powerful functionality for working with inspection
regulations, operations and results.

(C) SAP AG IUT110 26

5.27
Periodic Replacement

 In periodic replacement, devices
Rem

that are to be certified are
removed, and replaced by the
ova

same kind of devices.
l

 Devices that are to be replaced are
Installation

managed in the periodic
replacement list.
 Devices that are to be replaced on
a certain date are selected from the
periodic replacement list.
 A work order is then created for the
devices that are to be replaced.

 SAP AG 1999

 The periodic replacement component is optional. It is needed if:
Devices are to be certified individually
A lot does not exist for the sampling procedure, and the devices have to be certified individually

(C) SAP AG IUT110 27

5.28
Device Technology: Unit Summary

 The device category divides devices into functional
groups and specifies their features.The device
category corresponds to the material in MM.
 The device is a measuring instrument that “inherits”
the features of the device category.These “inherited”
features can be enhanced by individual
specifications, if required.
 Integration in the PM and MM application
components allows you to completely process all
service and logistics functions.
 Devices are certified and inspected for internal and
external purposes by means of periodic replacement
and sampling procedures.

 SAP AG 1999

(C) SAP AG IUT110 28

5.29Device Technology Exercises

Exercises: Device Technology
Topic: Creating and Delivering Devices

At the conclusion of these exercises, you will be able to:
• Distinguish between devices, device categories, and basic device
categories.
• Provide information on devices.
• Understand integration with the SAP PM and MM components.

Provide information on the devices installed at a customer’s location.
The creation and delivery of devices is standardized by integration in
SAP components.

1-1 Display all devices for customer TB010110## and select the water meter.
1-1-1 To which device category does this device belong?
______________________________________________________

______________________________________________________

1-1-2 When was the last meter reading result recorded and what was the result?
______________________________________________________

______________________________________________________

1-1-3 How many registers does the meter have?
______________________________________________________

______________________________________________________

(C) SAP AG IUT110 29

e. 1-2 Display all devices for customer TB010110## and select the double-rate electricity meter. 1-3-1 What is the current connection object? ______________________________________________________ ______________________________________________________ 1-3-2 What is the current device location? ______________________________________________________ ______________________________________________________ 1-3-3 Display the structure graphic and describe the procedure.. (C) SAP AG IUT110 30 . (Comment: the device category – i. 1-2-1 When is the device due for certification again? ______________________________________________________ ______________________________________________________ 1-2-2 Is the device already in a lot? ______________________________________________________ ______________________________________________________ 1-2-3 Has the device already been drawn as a sample device? ______________________________________________________ ______________________________________________________ 1-2-4 What is the calibration validity? How long is the internal certification period? _____________________________________________________ ______________________________________________________ 1-3 Specify the connection data for device TB010110##. ______________________________________________________ ______________________________________________________ 1-4 Display the material master data for device TB010110##. the material – is assigned to Plant “U003”).

______________________________________________________ 1-5-3 Device categories group together similar devices. ______________________________________________________ 1-5-2 Devices are based on a basic device category. ______________________________________________________ (C) SAP AG IUT110 31 . ______________________________________________________ 1-5-4 The device category is managed in the MM component ______________________________________________________ 1-5-5 The register group is allocated to the device category for information purposes. ______________________________________________________ 1-5-6 The device is managed in the Plant Maintenance (PM) component as a piece of equipment. ______________________________________________________ 1-5-8 Only the sampling procedure can be used when inspecting devices for internal and external purposes. 1-5 True or false? 1-5-1 Device technology is integrated into the R/3 logistics component. ______________________________________________________ 1-5-7 Devices can be allocated to more than one lot.

5. Expand the sub-tree and double-click the device TB010120##. Select the premise in the navigation area. all the readings are displayed. a lot has not yet been allocated. Possible status of sample devices: – Not sample device – Sample device from first drawing – Sample device from second drawing – Spare device from first drawing – Spare device from second drawing – Device cannot be used as a sample device (C) SAP AG IUT110 32 . 1-2 1-2-1 Double-click on Double-rate electricity meter. 1-2-3 In the view IS data  Ins. data. switch to tab page Cert/ins. Do not leave this screen.status field is empty. Return to device display. The field Next repl.dev. The master data for the register group is displayed.30Device Technology Solutions Exercises: Device Technology Topic: Creating and Delivering Devices 1-1 1-1-1 Select the customer in the Customer Interaction Center. Do not leave this screen. choose the Ins. year displays the year in which the device must next be certified. The device category is displayed on the IS data tab page. If the Samp. Otherwise. Switch to the IS data tab page. data tab. This lists all meter reading results. Return to the premise environment. the device has been allocated to a lot. Do not leave this screen. data. Double-click on the Register group field (tab page Group). 1-2-2 In the IS-data view. If the Lot field is filled. Choose Premise environment (right mouse click). On the lower set of tabs. either internally or externally. the device has not yet been drawn as a sample device. 1-1-2 After pressing the MR results button. 1-1-3 You are located in the device display for TB010120##. The data environment of the meter is displayed. Double-click on the device TB010110##. You can obtain information on the number of registers and their technical specifications and functionalities from the table entries.

field. In the Int. 1-5-3 True. PM and CS. 1-5 1-5-1 True. • Select all views and confirm the entry. choose Structure  Structure graphic or Strg F7. 1-5-4 True. 1-3-3 In the menu. the internal certification period is displayed. 1-3-1 The current connection object is TB010110##. This shows the internal period set by the company. The device category is managed in the component MM using the material number. Enter the plant key U003 and confirm it. Double-clicking the on Device category field displays the material data for the device. • Open a new session and change to logistics using the path Logistics → Materials management → Material master → Material → Display → Display current • Enter the key for the material (= device category) and choose the Data button. When a dialog box appears with the question “Expand structure upwards?” choose “Yes”. Here you can further expand the structure using the Levels above button. The calibration validity is displayed in years. • As materials are always defined for a specific plant./order data tab page. 1-5-2 False. 1-3 Choose the Mast. which in turn consists of one or more basic device categories. (C) SAP AG IUT110 33 . 1-3-2 The current device location is TB010111DL0##. data tab page. 1-4 • Determine the device category of the device TB010110## in the device master data. Devices are based on a device category. 1-2-4 The calibration validity is stored in the device category. after which a device must be re- inspected and certified. This is used to calculate the next year of replacement. IS-U device technology is integrated in the components MM. per. You are now looking at an illustration of the structure. cert. Switch to the Cert. you must also specify the plant. The current connection object is TB010110##.

1-5-7 False. Register groups are assigned to the device category. The device is managed in PM using the serial number. possible meter reading overflows or when converting results depending on the transformation relationship. For example. 1-5-5 False. but also a functional purpose and are used for processing and inspecting meter reading results. Devices can only be allocated to one lot. 1-5-6 True. the periodic replacement procedure can also be used. However. (C) SAP AG IUT110 34 . 1-5-8 False. In addition to the sample procedure. these not only have an informative purpose. validation checks for the number of premises.

6 Device Installation Contents:  Device installation/removal/replacement  Technical installation/removal  Billing-related installation/removal  Installation structure  Device allocations  Register relationships  SAP AG 1999 (C) SAP AG IUT110 1 .

you will be able to:  Describe and perform device installation.2 Device Installation: Unit Objectives At the conclusion of this unit.  Display devices of an installation and describe the installation structure. and how they are integrated in the Plant Maintenance (PM) application component. and replacement. removal.6. You will also be able to describe how these functions are integrated with the Service Management (SM) application component. and the device. the device location.  SAP AG 1999 (C) SAP AG IUT110 2 .  Explain the relationship between the connection object.

6.3 Device Installation: Business Scenario  Device installation if replaced periodically  Create and plan service orders  Execute service orders: Remove old devices and install new ones (device replacement)  SAP AG 1999 (C) SAP AG IUT110 3 .

removal and replacement  Installation structure  SAP AG 1999 (C) SAP AG IUT110 4 .4 Installation: Installation. Removal And Replacement  Device installation.6.

5 Business Scenario: Replacement of Sample Devices Generation Generation ofof work work orders orders to to replace replace Planning Planning the the devices devices the the affected affected work work orders orders Sample Sample Team leader devices devices inin aa lot Device field force lot must must be be replaced replaced forfor inspection agent certification certification Technical Technical conclusion conclusion of of the the service service order order and and triggering triggering of of the the Field force invoice invoice employee Device inspection agent On-site On-site technical technical execution execution of of the the order order and completion and completion Team leader confirmation confirmation of the of the Changes Changes to to data data field force order order in in the the system system in in the the system system ("full ("full device device replacement") replacement")  SAP AG 1999  Devices of a particular device category are due for certification.  The work orders are then scheduled for execution. the work order is executed on-site according to the process description: the old device is removed and is replaced by a new device of the same category. The work orders contain a complete description of the process. (C) SAP AG IUT110 5 .  When the completion certification has been successfully generated. the device replacement is carried out in the system and the order can be closed and invoiced. it is documented accordingly in the system by means of a completion confirmation. the corresponding work orders are automatically generated for the removal of these devices. as well as a list of materials and resources that may be needed. taking resource capacities and deadlines into account. if necessary.  In the next step.6.  As soon as the work order is executed. After the sample devices are defined using the lot procedure.

6.  SAP AG 1999 (C) SAP AG IUT110 6 . location supplement.6 Service Order Execution: Determining the Device Location Execute service Determine order device location  The device location indicates where a device is installed in the connection object. and a long text.The service order is used to forward this information together with the address data to the field force employee.  The address of the connection object links the device location to regional structure.  The device location is a functional location in the PM application component.  The location can be specified in more detail using location data.  The structure of the functional locations and the equipment (devices) installed provides a comprehensive overview of the technical systems installed.

 SAP AG 1999 (C) SAP AG IUT110 7 .7 Definition of the Device Location Execute Determine service device location order Connection object 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.6.

8 Device Location Data Execute Determine service device order location Independent of Reference to premise division • Installation location for • The device location can devices of all divisions be allocated to a • Installation location for premise if required all device categories Device location Location data Integration with PM • Exact location and • The device location is location supplement defined as a functional • Long text location below the • Link to regional structure connection object  SAP AG 1999 (C) SAP AG IUT110 8 .6.

6.9 Relationships Between Technical Objects Execute Determine service device location order Equipment Connection Higher- Higher-level Connobj Functional location Equipment Device Device Device Lower- Lower-level location Functional location IS-U objects PM objects Legend Installation of equipment Hierarchical relationship between functional locations  SAP AG 1999 (C) SAP AG IUT110 9 .

 SAP AG 1999 (C) SAP AG IUT110 10 . Since the new device has to perform the tasks and functions of the old device. it must be identical from a technical me point of view.  This concludes the technical aspect of the service order and the field force employee enters the corresponding completion confirmation in the system.  The new device is installed in the device location.6.10 Service Order Execution: Device Replacement & Service Order Confirmation Execute Perform Confirm Service service Determine device service order order device location replacement order executed  The field force employee performs an on- site meter reading for the sample device and then physically removes the device. te rea r no: ding 32 : __ 4561  A function test is performed and new meter ___ _ readings can be taken as a basis for billing.

The completion confirmation contains all the central information forany data changes required in the system.11 Data Changes: Installation Location Execute Perform Confirm Service service Determine device service order order device location replacement order executed Change data in Locate system installation  The Back Office employee responsible receives the completion confirmation for the service order in electronic or paper form.6.  The customer service representative can locate the installation affected using the device number of the device removed and startthe "Full replacement" transaction using the following data:  Device location  Installation  Activity date  Device number of the sample device  Device number of the new device  SAP AG 1999 (C) SAP AG IUT110 11 .

 Technical removal of the old device: This removes the link to the device location.  Once the data has been saved. Individual transactions. The device receives the status EEGB. a new time slice is opened for the device.  Processing steps that are performed automatically for a device replacement can also be performed separately (for instance by different customer service representatives). Data that is relevant to rates (such as the rule for determining the settlement price. All existing register relationships are terminated and the current time slice for the device is removed. and full installation (= both steps in one transaction) can be used to perform each step of the installation and removal processes separately. This ensures that there are no gaps in the consumption history. rate data at device and register level. The status in the device master record is changed from EEGB (equipment installed) to EFRE (equipment free).12 Data Changes: Device Replacement Execute Perform Confirm Service service Determine device service order order device location replacement order executed Change Perform Data data in Locate installation device change system replacement completed  The customer service representative enters the meter reading from the device removed and the meter reading at installation of thenew device.  Technical installation of the new device: The connection of the new register to the device location (and therefore the connection object) is established.  Billing-related installation of the new device: The new device is connected to the business master data (installation. business partner). the device replacement is complete. beginning on the installation date. such as technical installation.6. Any register relationships are transferred from the old device to the new meter. contract.  SAP AG 1999  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). (and therefore to the connection object). information about extrapolation of consumption values) is transferred to the new device. a new time slice begins. which provides the basis for billing. billing-related installation. At the same time. At the same time. (C) SAP AG IUT110 12 .

(C) SAP AG IUT110 13 .

a separate installation in the relevant division is created for each contract. The customer then receives only one bill for both services and has one contact person for all queries. Since one contract exists per installation. or a third company can carry out these tasks for both companies. each of which is supplied by a different service provider. Accordingly.13 Technical and Billing-Related Installation Business Business partner partner Contract Contract 11 Contract Contract Contract Contract 22 (Company (Company code code 1) 1) (Company (Company code code 2) 2) account account Generation Generation and and Distribution Distribution and and transmission transmission customer customer service service Installation Installation Premise Premise Installation Installation 11 22 Billing-related Billing-related installation installation Device Device Connection Connection Technical location location object object installation Device 1  SAP AG 1999  Devices can be allocated to several installations from a billing perspective (billing-related installation). However. The billing-relevant data in the utility installation and in the installation structure can be established individually for both contracts. This model clarifies how deregulated energy supply can be reflected in IS-U/CCS. each device can be allocated to only one device location from a technical point of view (technical installation). one of the companies can carry out billing and customer service on behalf of the other.  In the example above. (C) SAP AG IUT110 14 . any meters installed are allocated twice from the point of view of billing. The contracts for each of these basic services are managed under different company codes. When both contracts are managed in the same system.6. the utility services of the division are divided into two areas. These two basic services are "generation and transmission'" and "distribution and customer service".

6. removal and replacement  Installation structure  SAP AG 1999 (C) SAP AG IUT110 15 .14 Installation: Installation Structure  Device installation.

The consumption of the serial switching register (secondary register) is automatically deducted from the consumption of the main register during the billing run.6. (C) SAP AG IUT110 16 . At the same time.15 Example of an Installation Structure Serial switching Electricity Audio frequency ripple Electricity control receiver Supply grid Street Device allocation Register relationship  SAP AG 1999  The installation structure comprises all technical and billing-related data for a utility contract. one of the registers of the double-rate electricity meter has a serial switching relationship with another register. For information purposes.  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). this is described in the system as a device allocation of the ARCR type.

A device allocation is always composed of a controlling and a controlled device (Example: A calculation factor. (C) SAP AG IUT110 17 .  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.16 Technical Installation Structure  Device allocations  Register relationships  Audio frequency ripple  Reactive/active control receiver relationship  Transformers  Serial switching relationship  Pressure regulator  On-peak/off-peak  Customer-specific relationship allocations  Control relationship  VCF relationship  VCF calculation relationship  Customer-specific relationships  SAP AG 1999  Device allocations describe relationships between installed devices. all registers are added and the totals compared with the designated control register.g. on-peak and off-peak registers). 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. which is taken into account in consumption billing.6.  The serial switching relationship is automatically subordinate to all other relationships during meter reading and validation.  In a control relationship. is defined in the installation structure at register level for the "transformer" allocation category).  The on-peak/off-peak relationship describes the relationship between registers of different register categories (e.  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.  In a reactive/active relationship.

 Discounts can be assigned at register level for quantities and services ("register discount"). meter rental) from the rate.  Period consumption is used in the extrapolation of meter readings when no representative meter reading results are available (such as for new customers).g.  If the "relevance to billing" indicator is activated at register level. these can be changed at any time under "installation structure" in the menu. a plausible meter reading result is expected for billing.  The rate fact group is also assigned at device or register level.  The price class can be defined at the device category. However. together with the installation's rate category. or register level.6. the "relevance to settlement price" indicator determines whether a settlement price should be charged or not.  The rate type is maintained at device or register level and controls rate determination.g. price keys) that are assigned to a rate. (C) SAP AG IUT110 18 . determines the settlement price (e.  During device installation (or afterwards). constants) and/or keys (e. The price class. together with the price level. The rate fact group contains specific values (e.g. device.17 Billing-Related Installation Structure  Rate data  Extrapolation data  Relevance to  Expected period settlement price consumption  Relevance to billing  Fixed consumption  Price class values weighted linearly (absolute or relative value)  Rate type  Rate fact group  Discount  SAP AG 1999  Rate and extrapolation data are usually determined during maintenance of the installed device.

In this way. full removal of the old device and full installation of the new device is carried out in one step. technical and billing-related data is automatically transferred from the old device to the new device. Devices can also be removed or installed in one step for both billing and technical data. The device location is a functional location in the PM application component.  SAP AG 1999 (C) SAP AG IUT110 19 .18 Device Installation: Summary  The precise location of the devices is identified using device location in IS-U/CCS.6.  During device replacement.  Devices can be removed or installed in two separate steps that are distinguished in terms of billing and technical factors.

1-1-1 First. As the office-based employee responsible. you should carry out the device replacement step by step). in the Customer Interaction Center. To replace a device. (Note: this transaction can be processed quickly in one step using the transaction “device replacement”. in the data environment display in the Customer Interaction Center. 1-1-4 Finally. Use today’s date as activity date. In this transaction. (C) SAP AG IUT110 20 .19Device Installation Exercises Unit: Device Installation Topic: Installation and Removal of Devices At the conclusion of these exercises. Choose today’s date as the installation date and enter the meter reading at installation as 97. 1-2 Check the following features of the device you have just installed. log the device replacement. 1-1-3 Then carry out the full installation of the new meter TB010200## in one step. 1-1 Water meter TB010120## belonging to customer TB010110## was faulty and was replaced by a new device with the same technical features by a field force employee. in order to illustrate the individual steps in this task. However.8 m³. determine which device location and installation the device is assigned to. Assign a rate type and a fact group to the register. 1-1-2 Access the device management component in a new session and carry out the removal of device TB010120## in one step for today’s date. the following steps are performed in the system: • Billing-related removal of the faulty device from the installation and technical removal from the device location. you will first carry out the full removal of the old device and then the full installation of the new device in the system. the system carries out the full removal and installation in the background.6. • Technical and billing-related installation of the new meter. you will be able to: • Display all the devices in an installation • Install and remove devices • Describe integration with the PM component A customer’s water meter is faulty and must be replaced.

searched for and changed. 1-4 (Optional) Consumption has increased for a flat-rate installation. ______________________________________________________ (C) SAP AG IUT110 21 . the device is assigned to a device location and to an installation. Note that you must adapt the billing-relevant data for the installation to the new circumstances before the device is installed to ensure that billing and the billing-related installation of the device are correct. but device locations can. the utility installation must be extended by installing an additional meter. Only assign household rate data at register level. 1-5 True or false? 1-5-1 During technical installation. ______________________________________________________ 1-5-2 Only devices of the same division can be installed in a device location. Rate data can not be maintained. be created. To do this. “E1”) and limit the installation facts.g. however. you must assign a suitable rate category (e. Extend the flat- rate electricity installation by installing a meter using today’s date and the following details: Connection object: TB010110## Device location: TB010112DL0## Installation: TB010130## New device: TB010130## with a meter reading at installation of 250. 1-2-1 Installation date and installation reason: ______________________________________________________ 1-2-2 Meter reading at installation: ______________________________________________________ 1-2-3 Current business partner assigned: ______________________________________________________ 1-2-4 Device manufacturer: ______________________________________________________ 1-2-5 Maintenance planning plant: ______________________________________________________ 1-3 Display the structure graphic for the functional locations and their equipment for the newly installed device and complete the installation in the device location. For this reason.

______________________________________________________ (C) SAP AG IUT110 22 . ______________________________________________________ 1-5-4 The device location is managed as a functional location in PM. ______________________________________________________ 1-5-6 Device installation and removal automatically generates a time slice for the device. 1-5-3 Billing-relevant rate data must always be maintained during device installation. ______________________________________________________ 1-5-5 The device location is the highest level in the functional location hierarchy in PM.

The system displays the device master data. Utilities Industry  Device Management. press the Display time slice overview button. Choose the following for device removal: Device Installation  Removal  Full Device location: TB010111DL0## Installation: TB010120## Old device TB010120## 1-1-3 Choose the following for device installation: Device Installation  Installation  Full Device location: TB010111DL0## Installation: TB010120## New device: TB010200## 1-1-4 In the CIC. Choose: Technology  Device  Display Enter TB010200## in the Serial number field. Choose the action box Info  Customer environment Choose utility installation TB010120## by double-clicking on it. (C) SAP AG IUT110 23 . 1-2 1-2-1 Access device management or double-click on the device in the CIC.20 Device Installation Solutions Unit: Device Installation Topic: Installation and Removal of Devices 1-1G 1-1-1 Find customer TB010110## in the CIC Choose the water meter TB010120## with a right mouse click 1-1-2 Choose device management from the SAP Easy Access menu: Utilities Industry  Device Management. call up the data for business partner TB010110##. To obtain an overview of the time slices.Press Continue to confirm your entry.6. Branch to the device history of the devices assigned to the installation by pressing the Device history (DevHist) button.

Choose the time slice overview and specify today’s date as the selection date. Data 1-2-4 Choose tab page General in the upper work area. Activate the Prorate indicator and choose the newly created time slice by double-clicking on it. Since another rate has to be found for the device installed. To ensure that your billing is correct./codes. 1-2-2 Using the MR results button you can call up a list of the previous meter readings. The producer of the device is listed in the field Manufacturer. 1-3 Call up device management as follows: Utilities Industry  Device Management. you must also specify the validity of the previous rate type in the installation facts. before you can transfer the settings). choose IS data  Act. change the rate category in the current time slice to “E1”. call up the installation: Select flat-rate installation in the navigation area. On the following screen. The entire structure graphic is displayed. 1-2-3 Choose IS Data  Mast. Limit the period of validity to the day prior to the installation of the device. For this reason. a rate category which matches a rate type at device or register level must be specified. This informs you of the allocation of the device to a planning plant. Choose device display as follows: Technology  Device  Display Choose the following menu items to call up the structure graphic: Structure → Structure graphic The structure graphic screen appears: . (You may have to delete another automatically generated continuation line. 1-4 First. To check the installation date. A new time slice for the installation data relevant to billing opens automatically. Choose the following for device installation: Device Installation  Installation  Full Enter the initial data: Connection object TB010110## Device location: TB010112DL0## (C) SAP AG IUT110 24 . Choose rate maintenance (right mouse click). choose the Facts button. select the rate type by double-clicking on it. 1-2-5 Plant maintenance planning plant: Choose the tab page Organization. To do this. Transfer the settings using the Transfer button and then save the changes to the installation. The installation is now ready for billing-related device installation. The rate category entered (E4) was defined as the rate category for flat-rate installations and is only suitable for the rate types set down in the (installation) facts.

The device location can be explicitly assigned to a particular premise. if desired. 1-5-2 False. 1-5-5 False. 1-5-4 True. The billing-relevant rate data is not required during technical installation. (C) SAP AG IUT110 25 .: 0001 Residential customer Activate the indicator for payment of rental and settlement charges. Installation: TB010130## Activity date: Today’s date New device TB010130## To continue processing. 1-5-6 True. This can be added during billing-related installation or full installation. press Enter. 1-5 True or false? 1-5-1 True. Enter the Activity Date: Activity reason: 02 Installation extension Meter reading: 250 Rate type: 1002 Off-peak active energy FactGr. The device location describes the installation place in the connection object that is not dependent on a division. The connection object represents the level above the device location in the hierarchy. 1-5-3 False. Save your entries.

7 Meter Reading Contents:  Meter reading organization:  Scheduled and unscheduled meter readings  Street route  Scheduling  Meter reading procedure:  Creating the meter reading order  Options for result entry  Meter reading validations  Monitoring and correction of meter reading results  Special functions:  Meter reading by customer via the Internet and telephone  Reversal  SAP AG 1999 (C) SAP AG IUT110 1 .

you will be able to:  Describe the meter reading procedure  Scheduling and street route  Meter reading processing  Enter meter reading results by means of:  Automatic and manual payment run  Single and mass entry  Single and mass estimation  Meter reading correction  SAP AG 1999 (C) SAP AG IUT110 2 .2 Meter Reading: Unit Objectives At the conclusion of this unit.7.

followed by invoicing  SAP AG 1999 (C) SAP AG IUT110 3 .3 Meter Reading: Business Scenario  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.7.

4 Meter Reading: Meter Reading Organization  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  SAP AG 1999 (C) SAP AG IUT110 4 .7.

7.  Date and area scheduled in such as a move-in/out regional structure  Date and area cannot be  Resources can be planned scheduled  Meter reading cannot be Process planned  Create meter reading schedule Process  Specify meter reading Unscheduled  Create a single meter reading sequence Scheduled order  Create mass meter reading  Enter consumption orders  Check results  Enter results  Release for billing  Check results  Release for billing Meter reading  SAP AG 1999 (C) SAP AG IUT110 5 .5 Types of Meter Reading Indicator Indicator  Predefined meter reading  There are special reasons for strategy the meter reading request.

7.  Scheduling: Controlling and planning of the following processes: Meter reading order creation Periodic billing Budget billing collection  Scheduling is managed at the meter reading unit and billing portion levels. (C) SAP AG IUT110 6 .6 Regional Structure and Scheduling Regional structure Master data Scheduling Business partner Account Postal regional structure Portion Contract Street Street City section Meter Installation reading unit Premise Political structure Connection object  SAP AG 1999  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.

intervals  SAP AG 1999 (C) SAP AG IUT110 7 .7.7 Scheduling Tasks  Grouping together of contracts:  For joint billing Portion 1  Where budget billing options are identical Portion 2 (budget billing cycle and scheduling)  Grouping of utility installations: MR unit 1  Of the same billing class and division category MR unit 2  For joint billing MR unit 3  To control special features of meter reading. such as MDE.

 The utility company bills residential customers periodically. major customers (such as industrial and business groups) within the area concerned are allocated to a separate portion (C). such as billing conditions. (C) SAP AG IUT110 8 . Portion A is billed on June 15.1 MR unit A.1 MR unit B. Meter reading units in these portions are structured in such a way that they correspond to the daily work quota of the meter reader.1 MR unit C.2 MR unit C. This portion consists of three meter reading units that are not in close proximity to each other.5 Portion C MR unit C. They are "islands" inside portions A and B.  Example:  Portions A and B represent different city districts consisting almost entirely of households and small businesses (such as residential customers).8 Portions and Meter Reading Units Portion A Portion B MR unit A. and so on.  Non-residential customers are billed monthly. July 15.3 B MR unit B.2 A MR unit B. This means that portion C is billed on June 15. portion B is billed on July 15.2 MR unit A.3  SAP AG 1999  A portion normally contains several meter reading units.3 MR unit B. 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.4 MR unit B.7.  Since other meter reading cycles and billing conditions apply to nonresidential customers.

 Schedule records refer to specific dates. (C) SAP AG IUT110 9 .9 Generation of Schedule Records Schedule master records Schedule records MR unit A_AUG01 2000 MR unit A_AUG01 A_AUG01 2001 Generation of A_AUG01 2002 Portion schedule records P_AUG01 Portion Parameter record P_AUG01 2000 P1 P_AUG01 2001 P_AUG01 2002  SAP AG 1999  Schedule records are generated from the settings in the parameter record and schedule master records (portion and meter reading unit). which control meter reading and billing.  Schedule records must be generated for portions and meter reading units before meter reading orders can be generated.7.

It is also the date for which periodic meter readings are generated in scheduling. together with the length of the billing period (that is.10 Scheduling: Annual Billing End of Portion A Schduled billing date billing period 07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03 Meter reading period for meter reading unit 1 End of Billing period meter reading Scheduled Meter reading period for meter reading unit 2 period meter for all meter reading units reading date Meter reading period for meter reading unit 3 2001 2001 2002 2002 Portion A Portion A 07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03 07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03 Meter Meter reading Meter Meter reading reading Billing Billing Billing Billing  SAP AG 1999  End of billing period: This is the date on which the portion is to be billed for the first time. determines the date of the next billing (start of the next billing period = end of the billing period + 1 day). It forms the basis for calculating the expected consumption during meter reading order creation.  The scheduled meter reading date is the date on which the schedule specifies the register is to be read. This date.  The scheduled billing date is the date on which the contracts belonging to a portion are billed. and is used as a basis for defining dates of subsequent meter reading periods.7.  The end of the meter reading period corresponds to the end of the billing period. This takes the SAP calendar into account. it also acts as the final date for determining the budget billing amount. the period length). (C) SAP AG IUT110 10 .

2 object n loc. 1 A A Street 1 Str ee t rou Connection te Street 2 object 1 Connection Device Street n object 2 location 1 Connection Device Device 1 City distr. n City distr.11 Meter Reading Organization: Street Route MR MR unit unit City distr. n Device n  SAP AG 1999 (C) SAP AG IUT110 11 . 2 Device Device 2 loc.7.

7.12
Meter Reading: Process

 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

 SAP AG 1999

(C) SAP AG IUT110 12

7.13
Overview: Scheduled Meter Reading

Meter Create Output
reading meter reading meter reading
due orders orders

Manual MDE
meter reading meter reading
due due

Print Download
meter reading meter reading
documents data

Read meter Read meter

Enter Upload
meter reading meter reading
results results

Results
determined

Check
meter reading
results
 SAP AG 1999

(C) SAP AG IUT110 13

7.14
Creating Meter Reading Orders

Meter Create Output
reading meter reading meter reading
 Meter reading due orders orders
orders
Manual MDE
 Single meter reading orders meter reading meter reading
due due
 Mass meter reading orders
Print Download
 Single order data meter reading meter reading
documents data
 Selection via the meter reading unit,
contract, installation or device Read meter Read meter

 Additional dates for billing control
Enter Upload
 Mass order data meter reading meter reading
results results
 Selection via From meter reading unit and
To meter reading unit Results
determined
 Schedule task in task management
 Specification of meter reading reason Check
meter reading
results
 SAP AG 1999

(C) SAP AG IUT110 14

7.15
Issuing the Meter Reading Orders

Meter Create Output
Output media reading meter reading meter reading
due orders orders

Manual MDE
meter reading meter reading
due due
• Cover sheet MDE • Meter reading notification
• Meter reading • Card for meter reading Print Download
documents by customer meter reading meter reading
documents data

Read meter Read meter
Meter reading information
(selection)
Enter Upload
 Expected reading with area meter reading meter reading
results results
 Any number of previous meter
reading results
Results
 Street route determined

 Notes for the meter reader
(dynamic / static) Check
meter reading
results
 SAP AG 1999

(C) SAP AG IUT110 15

7.16
Types of Result Entry

Meter Create Output
 Automatic reading meter reading meter reading
due orders orders
 Upload interface
 Automatic estimation Manual MDE
meter reading meter reading
 Manual due due

 Fast entry Print Download
meter reading meter reading
 Fast entry without correction documents data

 Fast entry with correction
Read meter Read meter
 Single entry

Enter Upload
 Result correction meter reading meter reading
results results
 Plausible results
 Implausible results Results
determined
 Meter reading by customer
 Via the Internet
Check
 Via WAP telephone meter reading
results
 SAP AG 1999

(C) SAP AG IUT110 16

7.17
Result Entry Data

Meter Create Output
 Reference to meter reading meter reading meter reading
due orders orders
reading order (fast entry)
 Entry number Manual MDE
meter reading meter reading
 Check digit due due
 Meter reading
Print Download
data meter reading meter reading
documents data
 Recorded meter reading
 Date and time of meter reading Read meter Read meter

 Meter reader's notes
 Meter reading type (such as meter reading by the Enter Upload
meter reading meter reading
utility company, by the customer, or estimation) results results
 Meter reader number
 Date and time of maximum reading Results
determined
 Functions
 Correction and release of meter reading results Check
meter reading
 Estimation of meter reading results results
 SAP AG 1999

(C) SAP AG IUT110 17

7.18
Checking Meter Reading Results: Overview

Meter Create Output
reading meter reading meter reading
due orders orders
 Entry of meter reading results
 Manual Manual MDE
meter reading meter reading
 Automatic due due

 Types of validation Print Download
meter reading meter reading
 Fixed checks documents data
 Independent checks
Read meter Read meter
 Dependent checks
 Correction
Enter Upload
meter reading meter reading
 Correction and release of meter reading results
results results
 Estimation of meter reading results
 Correction aids Results
determined

Check
meter reading
results
 SAP AG 1999

(C) SAP AG IUT110 18

7.19
Check Meter Reading Results: Process

Implausible
result
Correction aids
Device: 4711000
Plausible
Meter
reading: 78133 result

Independent Dependent
checks checks
Examples: Examples:
• Consumption from • Cosine phi for
previous period energy/demand
• Demand from previous • Usage hours
periods • Control meters
• Demand compared with
agreed demand

 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
 SAP AG 1999

(C) SAP AG IUT110 19

7.20
Monitoring Meter Readings

 Selection of meter reading orders
via the following data objects:
 Contract
 Installation
 Device
 Portion
 MR unit
 Business partner
 Display (single or all):
 Billing order
 Meter reading orders
 Meter reading results

 SAP AG 1999

(C) SAP AG IUT110 20

7.21
Meter Reading: Special Functions:

 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

 SAP AG 1999

(C) SAP AG IUT110 21

m E Meter Meter reading reading request request Internet Internet IS- IS-U/ IS-U/ Transaction Transaction server CCS CCS server Customer Customer Read meter Entry Entry of of meter meter data data Int Inte ern rne ettcu cust stom ome err Int Inte ernett rne Ene Energ rgy ysup supp plie lierr  SAP AG 1999 (C) SAP AG IUT110 22 .22 Meter Reading by Customers over the Internet l ai .7.

23 Meter Reading by Customer over WAP Telephone IS- IS-U/ IS-U/ CCS W CCS Tr AP an sf er m et er r ea Internet Internet di Transaction ng Transaction s server server Customer Customer Read meter W Wire irele less ssAp Appplica licattion ion Int Inte erne rnettcustom custome err Protocol Protocol Ene Energ rgy ysup supp plie lierr  SAP AG 1999 (C) SAP AG IUT110 23 .7.

7.24 Reversing Meter Reading Orders: Process Incorrect mass selection Reverse Correct Restart meter reading order selection creation order Incorrect single selection Meter reading New meter order deleted reading order  SAP AG 1999  Meter reading orders can be reversed. (C) SAP AG IUT110 24 .  If meter reading results are already available when the reversal is performed. these can be deleted or retained and re-used in a new meter reading order.

25 Meter Reading: Unit Summary  Scheduled meter readings are controlled via meter reading units  In meter reading preparation.7. 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  SAP AG 1999 (C) SAP AG IUT110 25 .

1-4-4 If meter reading results are not available. and invoicing processes. 1-4-2 Meter reading orders can be output on the printer or via IDoc. For some customers. the meter reading unit cannot be billed. The customer reports the meter readings either in writing or by phone. 1-4-3 Meter reading results can be entered manually or automatically and are subject to the same validations. (C) SAP AG IUT110 26 . A customer service representative records the meter readings by customer and enters these manually in the system.7. 1-4 True or false? 1-4-1 Meter reading orders control the meter reading. the company does not carry out meter reading at all installations. 1-1 Which meter reading unit(s) is/are contained in the portion T-A-00? 1-2 Which objects can the portions be directly or indirectly allocated to? 1-3 Business partner TB090110## would like an interim billing for all his/her contracts. 1-4-5 Validations are always carried out. billing.26Meter Reading: Exercises Unit: Meter Reading Topic: Meter reading for individual customers At the conclusion of these exercises. carrying out the meter reading themselves is an efficient use of resources. Carry out the meter reading for all devices allocated to this business partner using the Customer Interaction Center. you will be able to: • Describe the organization and the process of meter reading • Carry out single entry of meter reading results With regard to periodic meter reading.

• Choose Save Enter. • By expanding the sub-tree Portion in MR units. • Enter portion T-A-00. This is valid for all meter reading units assigned to this portion. 1-2 The following relationships can exist: . (C) SAP AG IUT110 27 . The portion is entered directly in the meter reading unit. • The planned billing date is stored in the Sched BD field. • You can view the list of the meter reading units assigned by choosing the Where- used list pushbutton or CTRL+F4. you can view all the meter reading units that belong to this portion. The portion is indirectly referenced via the meter reading unit in the installation.7. . . The portion can be specified as an alternative portion directly in the contract.27Meter Reading: Solutions Exercises: Meter reading Topic: Meter reading processing 1-1 Go to the SAP Easy Access menu and choose: Utilities Industry → Scheduling → Schedule Master → Portion → Display.

collecting data and creating the meter reading documents. proceed as follows: . The meter reading order is an organizational aid for preparing for meter readings. Repeat the above steps for the other utility contracts. .  To release a meter reading. . very high or very low). Carry out this step for each utility contract • To enter the meter readings for each contract. To correct meter readings.  You return to the screen where you can enter meter readings.data fields. Choose the action Enter customer meter reading. Choose Enter until the data is displayed in the navigation area. such as implausible previous meter reading results and deviations where the installation (C) SAP AG IUT110 28 .Enter the meter readings. Confirm the entry of: . There are fixed validations which are always checked. 1-4-4 False. Meter reading reason 02 Interim reading with billing . .  From the MR data and Consump. Complete the customer contact and save it using: . even if the values are implausible (i. Choose F8 to continue or . 1-4-2 True. Meter reading type 02 Meter reading by customer. 1-4-3 True. 1-4 1-4-1 False. Save the meter readings by choosing Save: . You return to the CIC.e. . . you can read the expected values. proceed as follows:  Select a register line  Choose the Correct button. 1-4-5 True. .  The reading can be corrected in the Current MR field. 1-3 Proceed as follows: • Call the CIC and select the data for your business partner TB090110##. Missing meter reading results can be estimated by mass runs. choose Release. Select a contract.

The validations can then be carried out automatically. (C) SAP AG IUT110 29 . or where devices have not been installed. is inactive or disconnected. All other independent and dependent validations can be classified into validation groups in Customizing.

8 Energy Data Management Contents:  Profile header  Profile allocation for register  Point of delivery  Profile values  Formula profiles  Synthetic profiles  SAP AG 1999 (C) SAP AG IUT110 1 .

2 Profile Management: Unit Objectives At the conclusion of this unit. you will be able to:  Describe the components that make up profiles  Explain the connection of profiles to the master data  SAP AG 1999 (C) SAP AG IUT110 2 .8.

3 Profile Management: Business Scenario  Values determined by automated meter reading for an interval meter should be copied to the system  SAP AG 1999 (C) SAP AG IUT110 3 .8.

forecast profile. 30. demand. factor. schedule profile. other  Interval Lengths 5. quantity. 10.8. synthetic profile.4 Profile Header  Profile Type Historical profile. 15. day profile  Consistency Checking Group Determines which checks to carry out when importing profile values  Replacement Value Group Determines the calculation of plausible values that are used instead of missing or implausible actual values  Validity Period  Profile Value Category Amount. formula profile. price. 60 minutes  SAP AG 1999 (C) SAP AG IUT110 4 .

8.5 Profile Allocation for Register Business Regional partner structure  Profiles can be allocated to Contract (logical) registers of interval account meters  This allocation is historical and Contract Connection role-based object  The role determines the profile's task for this register Installation Premise  Examples of roles are measurement and forecast Device Measured Register profile  SAP AG 1999 (C) SAP AG IUT110 5 .

6 Point of Delivery Business partner  Point to which a utility service is supplied or to which a utility service can be Contract account determined for a customer  A point of delivery has one external identification number at any time (point Contract of delivery description according to metering code. for example)  The point of delivery is used for Point of Delivery Installation communication in automatic data exchange  The point of delivery is used to exchange Device meter reading results Measured Register profile  SAP AG 1999 (C) SAP AG IUT110 6 .8.

results participants system For example: EDI MSCONS SAP AG 1999 (C) SAP AG IUT110 7 .8.7 Importing Profile Values For example: Siemens metering Fröschl IS-U/EDM Görlitz Download Interval AMR Conversion meter system signal Profile Interface Point of delivery Meter Other EDI reading market sub.

8.8 Profile Values  A profile value is saved for every interval  At least one status is saved for every profile value  Multiple versions can be managed for every profile  Profile values can be displayed in table or in graphical form  Profile values can be changed individually or for certain periods of time  Profile values can be imported using BAPI orIDoc  An OLE (Excel) interface exists  Profile values can be displayed on the web  SAP AG 1999 (C) SAP AG IUT110 8 .

NL .9 Formula Profile 1/4h demand(kW ) 100 90 80 70 60 50 40 30 20 0 12:00 12:00 12:00 00:00 00:00 12:00 00:00 00:00 01. for example)  Formula profiles allow automatic calculation depending on the input parameters  The calculation is scalable  User-defined formulas can be supplemented (C) SAP AG IUT110 9 .1995 01.21.1995 01.1995 EDM RP LT total load UI NL request net losses + request + SL request street lights UI rest load RL = LT .SL .1995 01.8.MC + request UI scheduling + + MC measured customers UI + elementary load profile automatic aggregated load profile UI formula based profile  SAP AG 1999  Formula profiles are used to calculate profile values on the basis of a functional connectivity  You should use formula profiles if the relationship of input parameters to output parameters rarely changes (for the grid energy-feeding curve.19.17.18.1995 01.20.

31 Th 04.8.03 Su 04.29 Tu 03.30 We 03.10 Synthetic Profiles Residential Summer Workday customer 00:00 24:00 Weekend 00:00 24:00 Winter Workday 00:00 24:00 Weekend 00:00 24:00 Winter Summer Weekend Workday Workday Weekend Workday Su 03.02 Sa 04.04 Mo 04.06  SAP AG 1999  Profile containing values that are generated on the basis of predefined periods (defined by day and season blocks) and the corresponding day or annual profiles  Synthetic profiles are used for classifying customers or customer groups (C) SAP AG IUT110 10 .05 Tu 04.28 Mo 03.01 Fr 04.

8.11 Profile Management: Summary You are now able to:  Describe the components that make up profiles  Explain the connection of profiles to the master data  SAP AG 1999 (C) SAP AG IUT110 11 .

9 Billing and Invoicing 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  SAP AG 1999 (C) SAP AG IUT110 1 .

manual backbilling  Outsorting.2 Billing and Invoicing: Course Objectives At the conclusion of this unit. simulation  Credit memo.9. you will be able to:  Describe the billing process  Billing procedure. billing reversal  Explain the invoicing process  Invoicing tasks and procedure  Special features of invoicing  Use of invoicing documents  SAP AG 1999 (C) SAP AG IUT110 2 .

manual backbilling  Outsorting. reversal  SAP AG 1999 (C) SAP AG IUT110 3 .9.3 Billing Contents  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.

SAP Utilities  Integrated processing of both residential and non- residential customers requires several billing rules.  SAP AG 1999 (C) SAP AG IUT110 4 .  Different types of simulation enable the correct billing to be performed.  Increased competition requires the billing process to be flexible and efficient.4 Billing: Introduction  Contract billing of the supply and services provided is the most important function of a utility company.9.

9. followed by invoicing  SAP AG 1999 (C) SAP AG IUT110 5 .5 Billing: Business Scenario  Move-out processing in the customer center  Move-out date and meter readings reported by telephone  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.

Discounts. . ... adjustment adjustment surcharges surcharges duties duties fees fees  SAP AG 1999 (C) SAP AG IUT110 6 . General General Proration Proration Franchise Franchise .. . Price Price Discounts.6 IS-U/CCS: Billing Business Divisions partner Residential Water/ District customer Electricity Waste water heating Non-residential customer Cable Consumption Gas television Charges Multimedia services Energy Taxes Flat rates Duties suppliers Billing rules. variants . ..9...

period- end billing)  SAP AG 1999 (C) SAP AG IUT110 7 .9.7 Billing Procedures: Overview Billing procedures: Special functions  Interim billing  Month-based  Outsorting for bill verification  Key date  Simulation  Period  Manual backbilling  For exact number of days  Manual credit memo  Season-based  Reversal  Comparative (best rate)  Unbilled revenue reporting  For employees  Floating (backbilling.

8 Definition of Billing Meter reading Billing Invoicing Billing order processing that involves valuation of consumption and demand for each contract.  SAP AG 1999 (C) SAP AG IUT110 8 .9. and creation of billing documents for invoicing.

9.9 Billing Tasks Determination and Determination of conversion of billing periods quantities Determination of Valuation of change date and Billing quantities with proration to that prices date Determination of: Creation of billing • Rate data documents for • Price data invoicing  SAP AG 1999 (C) SAP AG IUT110 9 .

4. or 12 months  Length of period for period-end billing MO TU WE TH FR SA SU  x + x days. or 12 months 1 8 2 9 3 10 4 11 5 12 6 13 7 14 15 16 17 18 19 20 21  Billing for an exact number of days 21 28 22 29 23 30 24 31 25 26 27  based on the date of the meter reading  Month-based billing  dependent on key date  Month-based billing  dependent on intervals  SAP AG 1999 The billing period for which the utility bills the customer can be determined in a number of ways.10 Billing Periods  Length of period for periodic billing  x days. 1. 3. 2. 6. (C) SAP AG IUT110 10 .  Month-based Bills a specific number of complete months. 2. These are:  For an exact number of days Determines the exact length of the billing period in days. If the case of a move-in or move-out. for example the period between the last billed meter reading and the current day of meter reading. 4. 6. 1. the month-based procedure can be billed based on the number of days.9. 3.

service territory transfer  SAP AG 1999 (C) SAP AG IUT110 11 .9.11 Forms of Billing  Periodic billing Recurring periodic billing  Floating backbilling Special form of monthly periodic billing in which backbilling is performed for previous months using a current value. Example: monthly comparison of n peak averages  Period-end billing After completion of the billing cycle Example: 13th billing. backbilling for a year  Interim billing Unscheduled billing at any time Example: initiated by customer request  Final billing Examples: customer move-out or termination of contract.

9.  SAP AG 1999 (C) SAP AG IUT110 12 .  Demand-based rate determination The measured demand is used to determine the billing rule that applies. different billing rules for each season.12 Special Forms of Billing  Best-rate billing The most favorable rate is chosen for the customer on the basis of several billing rules.  Quantity-based rate for basic price The annual quantity consumed is used to determine the billing rule that applies.  Season-based billing Examples: Different prices for each season.

2.31.27.9.  The SAP calendar is used for this. 7.29.28. (C) SAP AG IUT110 13 . 8.30.3. 8. 7.13 Generation of Schedule Records End of Scheduled billing date scheduled Portion 1 billing 7.31. 7. Meter reading Meter Meter reading reading Billing Billing Billing  SAP AG 1999  End of the billing period: Portions should be billed for the first time on this date.  Scheduled meter reading date: Date on which all extrapolations and estimations are performed.31. 7. 7.  Scheduled billing date:  Date on which billing of contracts that belong to a particular portion should begin. minus the number of days between the end of the billing period and the scheduled billing date of the schedule master record.27. 7.3. 8. period Meter reading period for MR unit 1 Billing period End of MR Scheduled Meter reading period for MR unit 2 period MR for all MR units date Meter reading period for MR unit 3 2001 2002 Portion 1 Portion 1 7.3.28. 8. 8. 7.28.  This date is calculated as follows during generation of the schedule records: Date of the end of the billing period of the schedule record.1. 7. 8.29.1. This date may not be later than the end of the billing period for the allocated portion. 7. 7.29. 8.1. 7. The length of the scheduled billing period (period length) in conjunction with this date determine the date of the next billing. 8.30.30. 8. 7.  End of the meter reading period: Used as the baseline date for determining the schedules of the following meter reading periods.2.27.2. 7.

14 Billing Process: Overview MR MR Bill Billing Invoicing order creation entry printout Billing order Billing order Billing Bill printout document Plausible MR MR order results MR Implausible correction MR results  SAP AG 1999 (C) SAP AG IUT110 14 .9.

pr. facts/ ty 1 VarProg. . . C Rate 2 U 1 VarProg. . Inst. Values E Contract rate facts Rate 1 X 1 VarProg. structure pe Rate n Rate n Rate cat. C x4 T Installation ca te Rate 3 VarProg. A x1 E 2 VarProg. . D x5 I te . N mination . . . . . O ry . A xxx t e a Installation facts R Execution Validation Data Q uantity Qua of variant nt Generation enttry ry conversion of meter programs of billing and and reading analysis na accordingto lineitems proration results schema  SAP AG 1999 (C) SAP AG IUT110 15 . A x3 Ra Rate 1 2 VarProg. go deter. B x2 . .9. .15 Universal Billing Engine Data relating to Rate data Procedure data customer and installation Schema 1 Prices and Rate Var. .

9. 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 price Measured or calculated demand is valuated using demand prices. The demand replacement values can also be levied as a flat rate. The number of the measured demand values used for calculating the demand to be billed is variable. For example:  Comparison with minimum 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. maximum demand.16 General Billing Functions Decision variants Energy price Usage hours Demand price Billing Best-rate billing Block and scale Service price prices Season-based values and variants  SAP AG 1999  Energy price Measured or calculated consumption is valuated using energy charges.  Block and scale prices  Season-based values and variants  Decision variants (C) SAP AG IUT110 16 .

. QTY QTY Valuates * PRICE PRICE Valuates energy energy with BILLING BILLING LINE with aa price price LINE ITEMS ITEMS  SAP AG 1999 (C) SAP AG IUT110 17 ... . QUANTITY QUANTITY Difference Difference of - of two QUANTITY QUANTITY two quantities quantities QUANTITY QUANTITY Contract Contract text: text: ....5 ACT_50% ACT_50% REACT_KWH . Variant Variant pool pool . . . ..ACT_50% NUMBER NUMBER OF OF DEMAND DEMAND PEAKS PEAKS DEMAND DEMAND Calculates Calculates N N peak peak averages averages REACT_KWH ACT_50% BILL_REACT BILL_REACT DEMAND DEMAND Valuates * PRICE PRICE Valuates demand demand with BILLING BILLING LINE with aa price price LINE ITEMS ITEMS BILL_REACT * BILL_REACT UNIUNI 0.. . of of the the active active energy energy is is valuated valuated using using aa separate separate price....9... .. ACT_KWH ACT_KWH * 0. The The reactive reactive energy energy that that exceeds exceeds 50% 50% .. price.5 0.17 Example: Billing Rule for Electricity Variant Variant pool pool QUANTITY QUANTITY Calculates Calculates x% * FACTOR FACTOR x% of of aa quantity quantity QUANTITY QUANTITY . . .06 0. .06 BILLING BILLING LINE ITEMS ITEMS LINE . .

duties. and charges Consideration of Energy feeding register Billing from small power relationships producers Manual credit Billing of company memos and and plant backbilling consumption  SAP AG 1999 (C) SAP AG IUT110 18 .9.18 Special Billing Functions Determination of Billability check taxes.

9.19 Billing and Simulation reached Choose Billingdate Enter selection criteria Choose billing type billing type Billing Simulation chosen chosen Start Startsimulation billing Check billing Check documents simulation documents Billing types Billingdocuments implausible Billing documents correct Billing documents incorrect Start invoicing simulation Outsort Start invoicing Reversebilling documents Description: Description: IS- IS-U Creation of billing documents used Creation of simulation only for further processing in documents that are only used for invoicing further processing in invoicing simulation Billing Simulation Processing steps: Processing steps:  The billing order is deleted and  Billing order is retained and cannot be billed again and can still be used for  Meter reading results cannot be simulation changed again  Meter reading results can still  Billing document is created be changed  Simulation document is created  SAP AG 1999 (C) SAP AG IUT110 19 .

20 Simulation Types Billingdate Enter selection Choose billing reached criteria type Choose Billing Simulation chosen simulation chosen Start billing type Startsimulation Check billing Check documents simulation documents Simulation Billingdocuments implausible Billing documents correct Billing documents incorrect Start invoicing simulation types Outsort documents Start invoicing Reversebilling Description: Description: IS- IS-U Billing can be simulated without a Billing is simulated on the basis billing order for any group and for of a billing order that can be any period of time. Billing Simulation simulation Processing steps: Processing steps:  Simulation period can be  Period is determined by the freely defined billing order  Extrapolation that takes  Meter reading results relevant account of meter reading to billing are required results  Valuation of billing  Period can already have been billed  Billability check  SAP AG 1999 (C) SAP AG IUT110 20 . processed.9.

9.21 Document Types Billingdate Enter selection Choose billing reached criteria type Billing chosen Check Simulation chosen Start documents Startsimulation billing Check billing Check documents simulation Simulation documents Start invoicing Billingdocuments Billing documents Billing documents simulation implausible correct incorrect Outsort Start invoicing Reversebilling documents Billing Description:  Simulation produces a simulation document Simulation document  Billing produces a billing document Billing document Purpose  Documents the procedure  Saves and validates the results  Used for further processing of billing line items  SAP AG 1999 (C) SAP AG IUT110 21 .

9.22 Document Information Billingdate Enter selection Choose billing reached criteria type Billing chosen Check Simulation chosen Billing Start documents Startsimulation billing line items Check billing documents Check simulation documents Start invoicing Billingdocuments Billing documents Billing documents simulation implausible correct incorrect Internal billing Outsort Start invoicing Reversebilling Rate data documents data Documents from Account data Price data • Simulation • Billing Print data Device data Meter reading data  SAP AG 1999 (C) SAP AG IUT110 22 .

23 Further Processing of Documents Billingdate Enter selection Choose billing reached criteria type Billing Simulation chosen chosen Start Startsimulation billing Process Check billing Check documents simulation Invoicing documents documents Invoicing Start invoicing Billingdocuments Billing documents Billing documents simulation implausible correct incorrect simulation Outsort documents Start invoicing further Reversebilling Documents from • Simulation • Billing Billing Outsorting reversal  SAP AG 1999 (C) SAP AG IUT110 23 .9.

is set are not automatically processed further.24 Outsorting Procedure Billingdate Enter selection Choose billing reached criteria type Billing Simulation chosen chosen Start Startsimulation billing Check billing Check documents simulation Outsort documents Start invoicing Billingdocuments Billing documents Billing documents Outsort simulation implausible documents correct incorrect documents Outsort documents Start invoicing Reversebilling Description: Description: Billing documents which have IS- IS-U Billing documents for a contract failed validation are outsorted for which the outsorting indicator automatically.9. Possible validations: Automatic Manual Purpose  Percentage or absolute amount that the billing  Check special contract billing document exceeds or falls documents below the following:  Check new rates  Amount limit  Check consumption values in  Bill sum total complex installations  Budget billing  Check proration for different time slices  Bills with a balance of zero  SAP AG 1999 (C) SAP AG IUT110 24 .

9.25 Outsorting Process Billingdate Enter selection Choose billing reached criteria type Billing Simulation chosen chosen Bill Start Startsimulation billing Billing Invoicing Check billing Check printout documents simulation documents Start invoicing Billingdocuments Billing documents Billing documents simulation implausible incorrect Outsort correct documents Outsort Start invoicing Reversebilling documents Check documents  Outsorting reasons  Failed validation Exception Outsort  Indicator set in the contract list documents  Further processing  Reversal  Release Reverse Release documents documents  SAP AG 1999 (C) SAP AG IUT110 25 .

Selection takes place without a subsequent correction using document intervals or lists bill. This can occur with or reversed. Individual Mass reversal reversal Possible reasons: Possible reasons:  Incorrect conditions for  Incorrect settlement group nonresidential contract  Incorrect rates and prices  Incorrect meter reading result  Incorrect sales tax  Technical fault  ...  ..26 Billing Reversal Billingdate Enter selection Choose billing reached criteria type Billing Simulation chosen chosen Start Startsimulation billing Check billing Check documents simulation Reverse billing documents Reverse Start invoicing Billingdocuments Billing documents Billing documents simulation implausible correct incorrect Outsort Start invoicing documents Reversebilling documents Description: Description: IS- IS-U Only one billing document is More than one document is reversed.  SAP AG 1999 (C) SAP AG IUT110 26 .9.. of individual documents.

. . . 700 Water . . . . 900 Electricity . . . .000 Gas . . . .000 Gas .00 Reversed 2. .000 Water . 2.300 Reversal indicator set  SAP AG 1999 (C) SAP AG IUT110 27 . . . . .24. . . 700 Water . . . . . .00 Corrected 2. . . . . 600 Gas .27 Billing Reversal Process Billingdate Enter selection Choose billing reached criteria type Document Billing Simulation outsorted chosen chosen Start Startsimulation Reverse billing Correct data Restart Check billing Check billing billing documents simulation documents Reverse Start invoicing Billingdocuments Billing documents Billing documents simulation implausible correct incorrect Document Outsort Start invoicing documents Reversebilling documents implausible Billing order Incorrect 2. .600 Total .16. . . 2. . . 2. .9. . . 1. . 700 Total . .23. 1. . .00 billing document billing document billing document Jane Smith Jane Smith Jane Smith Electricity. . 900 Electricity . . . . .600 Total . . 1. . . . .

Documents must be either released or reversed. and creates billing documents for invoicing. which creates simulation documents  Billing. Reasons for outsorting:  Failed validation  Indicator set in the contract  Individual or mass reversals enable quick correction and subsequent billing.9.  SAP AG 1999 (C) SAP AG IUT110 28 .28 Billing: Unit Summary  Billing processes billing orders.valuates consumption and demand.  There are two types of billing:  Simulation. which creates billing documents  Outsorted billing documents require additional processing .

29 Invoicing: Introduction  Invoicing links contract billing to contract accounts receivable and payable. and prepares bill printout. and duties that are due.9.other credits (credit memo. and against the taxes. such as payments to open items reduce the amount of processing required. payment on account) + other receivables (backbilling.  SAP AG 1999  The bill sum total is calculated as follows: Bill sum total = Total receivables from billing . dunning charge) (C) SAP AG IUT110 29 . SAP Utilities  The bill sum total is determined after settlement of the billing documents against the budget billings already paid.  Flexible settlement options. charges.paid budget billings .

9. followed by invoicing  SAP AG 1999 (C) SAP AG IUT110 30 .  Implausible meter reading requires meter reading by the company.  Meter reading processing:  Create meter reading order  Entry or estimation of meter reading results  Start of billing and invoicing:  Final billing.30 Invoicing: Business Scenario  Move-out processing in the customer center:  Move-out date and meter readings reported by telephone.

31 Definition of Invoicing Meter reading Billing Invoicing The process that links the billing documents to contract accounts receivable and payable.  SAP AG 1999 (C) SAP AG IUT110 31 .9. and provides the basis for bill creation.

32 Invoicing: Overview Billing: Contract accounts receivable Provides the processes relevant and payable: to payment and manages the Contract Accounts Receivable and individual accounts. Invoice-relevant transactions Invoice-relevant transactions IS- IS-U FI- FI-CA Open items  Billing documents   Credit memos  Paid budget billings  Backbillings  Manual postings  Dunning charges  Payments on account Invoicing  Bill printout  Budget billing plan  Due date determination  Settlement  Use of credits  SAP AG 1999 (C) SAP AG IUT110 32 . Payable makes available items relevant for payment and manages the individual accounts.9.

 Invoicing is used for the following:  Grouping together billing documents of contracts from the same contract account into one joint bill.33 Tasks of Invoicing Settlement against first budget billing Creation of Joint invoicing budget billing plan Cross-company Due date code invoicing Invoicing determination Account Credit settlement determination Budget billing settlement  SAP AG 1999  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.  Posting documents to FI-CA (sub-ledger accounting)  Supplying bill printout documents for bill creation  Processing budget billing plans (C) SAP AG IUT110 33 .9.

34 Invoicing Units Date for Enter selection Choose invoicing criteria invoicing type reached Invoicing Invoicing chosen simulation chosen Start Start invoicing Start invoicing simulation invoicing  Creation of invoicing units Check the FI-CA document Check bill printout document Check simulation documents Invoicing Invoicing Invoicing Simulate bill documents documents documents printout Summary of the billing documents in a implausible Outsort correct Start bill incorrect Invoicing contract account can be controlled at contract level. documents printout Reversal  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  SAP AG 1999 (C) SAP AG IUT110 34 .9.

35 Mandatory and Optional Contracts: 1 Contract account Billing Invoicing Contract Contract 11 Document Mandatory Mandatory Document 11 Joint Jointinvoice invoice Mandatory Mandatory Contract Contract 22 Mandatory Mandatory Joint Jointinvoice invoice Contract Contract 33 Mandatory Mandatory Document Document 33 Joint Jointinvoice invoice Mandatory Mandatory Contract Contract ll Optional Document Document Document Document Bi Optional Joint Jointinvoice invoice Optional Optional Optional Optional Contract Contract Document Document Document Document Exclusive Exclusiveinvoice invoice Exclusive Exclusive Exclusive Exclusive ll Bi  SAP AG 1999 (C) SAP AG IUT110 35 .9.

9.36 Mandatory and Optional Contracts: 2 Contract account Billing Invoicing Contract Contract 11 Document Document 11 Mandatory Mandatory Joint Jointinvoice invoice Mandatory Mandatory Contract Contract 22 Document Document 22 Mandatory Mandatory Mandatory Document Document ll Joint Jointinvoice invoice Mandatory Bi Contract Contract 33 Document Mandatory Mandatory Document 33 Joint Jointinvoice invoice Mandatory Mandatory Contract Contract Document Document Optional Optional Joint Jointinvoice invoice Optional Optional Contract Document Document Document Document Contract ll Exclusive Exclusiveinvoice invoice Exclusive Exclusive Exclusive Exclusive Bi  SAP AG 1999 (C) SAP AG IUT110 36 .

9.37 Invoicing Options Date for Enter selection Choose invoicing criteria invoicing type reached Invoicing Invoicing chosen simulation chosen Start Start invoicing Start invoicing simulation invoicing  SAP billing documents Check the FI-CA document Check bill printout document Check simulation documents Invoicing Invoicing Invoicing Simulate bill printout IS-U billing documents documents documents documents implausible correct incorrect  Start bill Outsort Invoicing documents printout Reversal  SD billing documents  PM / SM billing documents  External billing documents via the standard IDoc interface  Heating costs billing  Telecommunications  Company code allocation  Invoicing within a company code  Cross-company code invoicing  SAP AG 1999 (C) SAP AG IUT110 37 .

38 Source of Billing Documents SAP systems: External systems: Central invoicing of all Using standard billing processes from consumption documents. . . .9. . . .500 ce Maintenan 700 . 1. Electricity . Te l. .. consumption billing results. . . 600 . . . . Invoice-relevant transactions Invoice-relevant transactions External SD  Telecommunications  IS-U consumption billing IS- IS-U  Heating costs billing  SD Sales and Distribution  CS Customer Service  Other unbundling services CS Bill Jane Smith .800 Total . sales and distribution external systems can be invoiced and service management and monitored together with simplify the transactions. com. 2. . .  SAP AG 1999 (C) SAP AG IUT110 38 . . billing results from billing. .. ..

. SAP applications without tax Billing #2 .One division for several contracts ("unbundling" electricity Billing #4711 UNI 180 rate) Single items per ....39 Invoicing Various Services Disposal service #1 Supply service #2 Energy feeding #3 Other services #4 Waste Waste water water UNI UNI 50 50 Electricity Electricity UNI UNI 15 15 Electricity Electricity Cable Cable TV TV UNI UNI 30 30 Garbage Garbage UNI UNI 40 40 Water Water UNI UNI 60 60 connection connection UNI UNI 85 85 Gas Gas UNI UNI 80 80 Sale #5 Total charges #4711 External billing Radiator Billing(#1-#7) UNI 510 document #7 Radiator UNI UNI 35 35 Servicexy UNI 70 -Budget billings paid(#1-#3)UNI 330 Bill sumtotal UNI 180 Maintenance fee #6 dueon 01/15/2000 Gas Gas heating heating UNI UNI 45 45 Billing summary IS-U Account: A....various divisions (electricity........ SD/CS and IS-U invoices ... Simplified receivable: gas. water) example Billing #1 . Smith . Also billing from external systems  SAP AG 1999 (C) SAP AG IUT110 39 ....9.

obwohl es sich um verschiedene Unternehmen handelt. 02 Waste water 500 UNI FI-CA Waste disposal 200 UNI General ledger 02 General ledger 03 Cross-company code billing (not relevant for fin. Cross-company code billing for Billing #3 (rs) ... (C) SAP AG IUT110 40 .  All dies geschieht im selben SAP-System. water Water 600 UNI Billing #1 (xy) . 01 Gas 1500 UNI Req. gas for ”xy" CoCd.  Die Stadtwerke xy versorgen ihre Kunden mit Strom. of works xy Dep. 03 Cable TV 180 UNI Waste water req.. of works xy: Contracts Consumption bill. Total charges #4711: Cross-company Third party billing Billing (#1- (#1-#3) 3980 UNI code billing . Contracts local authority zz: for "zz" Other services #2 CoCd..  Für die Kabelfernsehgesellschaft rs rechnen sie die Gebühren für Kabel-TV ab. Billing #2 (zz) . #1 Line items for each Req. Waste disposal req. Gas und Wasser.9. #4711 380 UNI Dep. electricity Electricity 1000 UNI requirement: Req.. Cable TV req. Contracts for TV company rs: Local authority zz statements) for "zz" Other Services #3 TV company "rs" CoCd.  Sie rechnen aber auch im Auftrag der Kommune zz Abwasser und Müllabfuhr ab.40 Cross-company code invoicing Total Charges #4711 Account Smith (xy (xy)) General ledger 01 Re..amount paid (#1- (#1-#3)- #3)-3600 UNI IS- IS-U amount outstanding: 380 UNI FI due on 1/15/96  SAP AG 1999  Dies ist das Beispiel einer Fakturierung für verschiedene Buchungskreise.

41 Bill Due Date Terminfür Selektions. the bill due date can be corrected to fall on a working day. document date. Artder Faktura kriterien Faktura erreicht eingeben wählen Faktura- Faktura simulation gewählt gewählt Start Start invoicing Faktura- simulation invoicing starten  The bill due date is determined from the Check the FI-CA document Check bill printout document Simulations- belege prüfen following attributes: Faktura- belege unplausibel Faktura- belege korrekt Faktura- belege fehlerhaft Rechnungs- druck simulieren Rechnungs- Terms of payment Belege Faktura aussteuern druck stornieren  starten These determine the source of the baseline date  Baseline date: Posting 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. (C) SAP AG IUT110 41 .9.  Can be specified for each company inCustomizing Baseline date + terms of payment = bill due date  SAP AG 1999  Das Rechnungsfälligkeitsdatum kann auch mit dem ersten Abschlag zusammengelegt werden.

9. Faktura.42 Document Flow in Invoicing Terminfür Selektions. Rechnungs- belege belege belege druck unplausibel korrekt fehlerhaft simulieren Billing Credit memos/ Belege Rechnungs. Artder Faktura kriterien Faktura erreicht eingeben wählen Faktura- Faktura simulation gewählt gewählt Start Start invoicing Faktura- simulation invoicing Check the FI-CA Check bill starten Simulations- printout belege document document prüfen Faktura. FI-CA Budget billing plans FI-CA documents  SAP AG 1999 (C) SAP AG IUT110 42 . Faktura aussteuern druck stornieren starten documents backbillings Print documents Start invoicing Posting docs. Faktura.

 The selected items are cleared or partially cleared on the basis of these allocations.  Settlement control is flexible and enables you to model your own clearing strategy in Customizing.9.43 Settlement: Overview Date for Enter selection Choose invoicing criteria invoicing type reached Invoicing Invoicing chosen simulation chosen Start Start invoicing Start invoicing simulation invoicing  In IS-U clearing processing. settlement Check the FI-CA document Check bill printout document Check simulation documents comprises the following activities: Invoicing documents implausible Invoicing documents correct Invoicing documents incorrect Simulate bill printout Outsort Start bill Invoicing Automatic determination of the purpose of documents printout Reversal  a payment amount when a payment transaction is entered.  SAP AG 1999 (C) SAP AG IUT110 43 .  Automatic allocation of posted open items to each other in account maintenance.

to your lette letter of 9/27.44 Bill Printout Procedure Date for Enter selection Choose invoicing criteria invoicing type reached Invoicing Invoicing chosen simulation chosen Start invoicing Start invoicing simulation Print Check the FI-CA Check bill printout Check simulation document document Select print Choose Start document documents Invoicing Invoicing Invoicing Simulate bill ready for document output type output documents implausible Start bill documents correct documents incorrect printout output Outsort documents printoutStart bill printout Invoicing Reversal SAP spool Output Print documents Raw data interface Dear Mad Dear am/S ir: Dear Mad Mad am/Sir: am/SInir:refe renc In refe e In referenc renc 9/27.. .e.to your to your lette r of 9/27 ....9. e r of Mail processing Bill date Archive  SAP AG 1999 (C) SAP AG IUT110 44 .

9. number. billing bills or partial bills are reversed by documents are also reversed by selecting using a reconciliation key selecting using a document or document number.45 Invoicing Reversal Date for Enter selection Choose invoicing criteria invoicing type reached Invoicing Invoicing chosen simulation chosen Invoicing Reversal Start invoicing Start invoicing simulation  Mass reversal Check the FI-CA document Check bill printout Check simulation document documents or Invoicing documents Invoicing documents Invoicing documents Simulate bill printout implausible correct incorrect  Single reversal Outsort Start bill printout Invoicing Invoicing documents Reversal Reversal Bill reversal: Full reversal: Bill printout and FI-CA documents for IS- IS-U In addition to the bill. Transactions Transactions  Reversal of FI-CA document  Reversal of FI-CA document  Reversal of bill printout  Reversal of bill printout document document  Possible reasons:  Reversal of billing document  Incorrect layout  Possible reasons:  Printing problems  Incorrect billing  SAP AG 1999 (C) SAP AG IUT110 45 . Full reversal does not include reversal of partial billing Bill Full reversal reversal documents.

1.. . . billings Bud. . 700 W ater . . . . Credit memo . . . . . . 900 . . . 300 ..... . . .000 Electricity . 2. W ater .900 2. . . . . . . . . . . 900 Electricity . . 700 Gas . ..46 Procedure for Bill Reversal Date for Enter selection Choose invoicing criteria invoicing type reached Invoicing Invoicing chosen simulation chosen Start invoicing Start invoicing Document simulation outsorted Check bill Check Check the FI-CA printout simulation document document documents Simulate bill Restart Invoicing Invoicing Invoicing Reverse documents implausible documents correct documents incorrect printout Correct data invoicing Reverse invoice Outsort documents Start bill printout Invoicing Reversal documents Document implausible Billing document Bill Reversed bill New bill Jane Smith Jane Smith Jane Smith . . Receivable .500 Bud. billings . W ater . .000 900 Electricity... 1. 300 100 Credit mem o . . .900 2. billings Bud... 1.  SAP AG 1999 Reversal indicator set (C) SAP AG IUT110 46 . 700 Gas .. . .000 Ga s .9. .

.2. . . 300 Credit memo . . .2. Credit me mo . . . . 700 . 900 Electricity .2. . .. 100 . . .900 Bud.. . . .. . . Electricity . Water . . . ..000 Total . . 300 . . . 2. . .. billings Bud. .9. 700 . . . . . billings . Water .900 ctricity . 1. .47 Procedure for Full Reversal Document outsorted Reverse Reverse Restart Correct data Restart billing invoicing invoice billing Document implausible Billing order 16. . .500 2. . . .2. . . . . Total  SAP AG 1999 (C) SAP AG IUT110 47 .300 Gas . . . . . .0 900 Total . .600 00 Total . .. Water .. . 700 .98 Incorrect billing document billing document billing document Jane Smith Jane Smith Jane Smith Electricity . . .000 ith Gas . .98 Corrected 24. 1. . . Jan e Smith 1. 900 Electricity . bill New 600 Gas .. Wa ter 2. . Ele 2. -Jan 700 . . .600 .ers 900 ed bill Electricity . . 1. . . bill ing s. . ..000 ith e Sm Jane Sm Water . .. . . . Bill . .700 Water . .. 1. 1. . . . . . . . 700 00 Gas . . . .0 2.900 Bud. . Gas . .000 Gas . . . Rev .98 Reversed 23.

48 Invoicing: Unit Summary  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  SAP AG 1999 (C) SAP AG IUT110 48 .9.

9. Carrying out a simulation for any billing period. You process the move-out and create the final billing. • Use the billing and simulation functions. 1-1 Business partner TB100120## with contract account TB100120## comes in to the customer center to report his/her move-out. allows you to provide specific information. by the express wish of a customer or to advise a customer. or for an actual billing period. 1-1-1 Call up the move-out process How would you proceed? ______________________________________________________ ______________________________________________________ 1-1-2 Create move-out: Initial screen Enter the last day of the previous month as the move-out date and choose the call.49Billing and Invoicing Exercises Unit: Billing and invoicing Topic: Billing a business partner At the conclusion of these exercises. Various business processes require the billing of an individual customer. How would you proceed? ___________________________________________________ ___________________________________________________ ___________________________________________________ ___________________________________________________ (C) SAP AG IUT110 49 . This may be necessary due to the move-out of a customer. without altering data. you will be able to: • Describe the billing process and tasks. Check the move-out date and the bill sum total in the customer overview. for example.

Use the correction and estimation functionality How would you proceed? ___________________________________________________ ___________________________________________________ ___________________________________________________ What values would you enter? Electricity register 1 _____________________________________________ Gas register 1 _____________________________________________ Water register 1 _____________________________________________ • Request a final bill and display this on the screen. How would you proceed? ___________________________________________________ ___________________________________________________ • Exit move-out processing How would you proceed? ___________________________________________________ ___________________________________________________ (C) SAP AG IUT110 50 . Use printer LT0Q. • Enter a plausible meter reading for each device and each register. 1-1-3 Execute move-out processing: Enter meter readings • Meter reading by customer.

1-2 Business partner TB100110## comes into the customer center and would like an interim billing. 1-2-1 Enter the meter readings for business partner TB100110## using the CIC. Display the individual simulation of the billing. • What was the bill sum total? _______________________________________________________ • Where can you read the move-out date? On which date did the move-out take place? ___________________________________________________ • End the contact. check the meter reading results and then request the actual billing. enter the meter readings supplied by the customer. How would you proceed? Which meter readings have you entered? ______________________________________________________ ______________________________________________________ ______________________________________________________ (C) SAP AG IUT110 51 . First. 1-1-4 Check the move-out in the customer overview. From the CIC.

1-2-2 Carry out the individual simulation and display the bill for business partner TB100110##. go to the SAP Easy Access menu and choose Utilities Industry  Billing  Billing Execution  Individual Processing  Individual Bill. How would you proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ 1-2-3 Process and display the individual bill for business partner TB100110##. • For the bill simulation. • For the individual bill. 1-3-1 Display the billing document. • Choose the Display bill level of processing. • The most useful means of selection is via the contract account. • The most useful means of selection is via the contract account. How would you proceed? ______________________________________________________ ______________________________________________________ ______________________________________________________ 1-3 Display the billing document for the water contract of business partner TB100110## and answer the following questions. How would you proceed? (C) SAP AG IUT110 52 . go to the SAP Easy Access menu and choose Utilities Industry  Billing  Billing Execution  Individual Processing  Individual Simulation  Billing. • Choose the Bill level of processing.

_____________________________________________________ 1-4-5 Individual billing items can be entered manually as backbilling or as a credit memo. ______________________________________________________ ______________________________________________________ ______________________________________________________ 1-3-2 What was the scheduled billing period? ______________________________________________________ 1-3-3 How many line items does the billing document contain? ______________________________________________________ ______________________________________________________ ______________________________________________________ 1-3-4 Which line categories are available and what do they mean? Line category Meaning 1-3-5 What was the total billing quantity determined? ______________________________________________________ 1-4 True or false? 1-4-1 Billing is only carried out after meter reading and before invoicing. ______________________________________________________ (C) SAP AG IUT110 53 . the billable orders are produced. _____________________________________________________ 1-4-4 The billing documents are processed further during invoicing. ______________________________________________________ 1-4-2 Billing simulation must be carried out before billing. ______________________________________________________ 1-4-3 After billing.

The bill sum total is determined in this way. • Provide information on the budget billing plan. After calculating the budget billing plan for the next period. Exercises Unit: Billing and invoicing Topic: Invoicing a business partner At the conclusion of these exercises. • Explain the budget billing procedure. • Use the invoicing and simulation functions. 2-1 Execute the invoicing simulation for business partner TB100110##. you will be able to: • Describe the invoicing process and tasks. Carry out the following steps: 2-1-1 Simulate invoicing How would you proceed? ______________________________________________________ ______________________________________________________ 2-1-2 Check the log How would you proceed? ______________________________________________________ ______________________________________________________ (C) SAP AG IUT110 54 . the bill can be printed with details of the bill due date and the new budget billing amount due date. The billing results are compared with the transactions in open item accounting.

2-1-3 Display the document How would you proceed? ______________________________________________________ ______________________________________________________ 2-1-4 Simulate the bill? How would you proceed? ______________________________________________________ ______________________________________________________ 2-2 Process the actual invoice for business partner TB100110##. How would you proceed? __________________________________________________________ __________________________________________________________ 2-3-2 How many line items does the print document contain? How would you proceed? (C) SAP AG IUT110 55 . 2-3-1 From the customer overview. display the print document for business partner TB100110##. 2-2-1 Invoice the business partner How would you proceed? ______________________________________________________ ______________________________________________________ 2-2-2 Check the log ______________________________________________________ ______________________________________________________ 2-2-3 Display bill from customer overview How would you proceed? ______________________________________________________ ______________________________________________________ 2-3 Provide information on the print document.

______________________________________________________ ______________________________________________________ 2-4-3 The invoice takes into account billing documents from other company codes. ______________________________________________________ ______________________________________________________ 2-4-2 Only one invoice is ever generated for all contracts of the contract account. ______________________________________________________ ______________________________________________________ 2-3-3 What is the bill sum total? How would you proceed? ______________________________________________________ ______________________________________________________ 2-3-4 Which rate was used in the calculation? ______________________________________________________ ______________________________________________________ 2-3-5 Enter the bill due date. ______________________________________________________ ______________________________________________________ 2-4-5 The invoice generates the print documents. ______________________________________________________ 2-4 True or false? 2-4-1 Invoicing is only carried out after billing. ______________________________________________________ (C) SAP AG IUT110 56 . ______________________________________________________ ______________________________________________________ 2-4-4 The bill due date is always derived from the posting date and the terms of payment.

______________________________________________________ 2-4-6 The invoice can be reversed separately or reversed along with the settlement. ______________________________________________________ ______________________________________________________ 2-4-7 The billing document only takes into account statistically posted documents ______________________________________________________ ______________________________________________________ (C) SAP AG IUT110 57 .

choose: (C) SAP AG IUT110 58 . In the MvOut date field. Pay attention to the column meter reading status (RS). You must enter a reconciliation key.50Billing and invoicing Solutions Unit: Billing and invoicing Topic: Billing a business partner 1-1 From the SAP Easy Access menu. 1-2-2 From the SAP Easy Access menu. Identify the business partner by entering the number TB100120## in the Business partner field and choose Enter twice. choose: Choose Utilities industry → Customer service → Front Office/Customer Interaction Center → Customer Interaction Center. 1-2 From the SAP Easy Access menu. (You will have to carry out this process three times). Check that the tabs for the contracts have been deactivated. you have entered an implausible meter reading result and can use the Correct button to enter a plausible result. Choose the End contact button. This must have a value of 1. 1-1-3 Choose the MR data tab and enter plausible meter readings. The business partner is stored on the clipboard. choose: Utilities industry → Billing → Billing Execution → Individual Processing → Individual Simulation → Billing 1-2-3 From the SAP Easy Access menu. 1-1-1 Choose the Move-out partner call that is found under the Move I/O call group. Identify the customer. If the value is different. choose: Choose Utilities industry → Customer service → Front Office/Customer Interaction Center → Customer Interaction Center. Confirm the data for printing. Choose the Final bill button. You are now in the move-out processing screen. Enter the meter reading results for each contract individually and save the entries.9. Save the move-out. 1-1-2 Enter the move-out date. Go to Info and choose Customer overview. 1-2-1 Choose the action Enter customer meter reading. 1-1-4 You return to the CIC. you can see the date on which the customer moved out. Refresh your data in the navigation area. Enter IUT110-01 and save the data. Double-click on the invoice sum total to display the print document.

1-3 Choose Utilities Industry → Billing → Billing Execution → Display Document. The billing simulation produces simulation documents that can be used only for invoice simulation purposes. (C) SAP AG IUT110 59 . 1-3-3 The Table overview button provides an overview of the billing lines. since billing processes the meter reading results and provides prices of valuated quantities for invoicing. You will receive a list of all the billing documents of the customer to choose from. 1-4-5 True. 1-4-3 False. Invoice orders are the result of billing. “Billable” status is granted when a billing-relevant meter reading becomes available. field. Contrary to the billing documents. 1-4-2 False. 1-4-6 True. 1-3-4 000001 Energy price 000004 Rental price IQUANT Quantities (meter readings) 1-3-5 The billing quantity is visible in the table overview or in the individual documents. 1-4 1-4-1 True. 1-3-1 Choose F4 for help in the Document no. The billing order results from the creation of the meter reading order. Utilities Industry → Billing → Billing Execution → Individual Processing → Individual Bill. 1-3-2 The header data of the billing document provides the most important data for billing. the billing simulation documents can only be processed further by invoicing simulation. The billing simulation is only a demonstration of how the real billing would be carried out. Enter your business partner number.

You will automatically branch to the print document display. 2-1-1 Activate the indicator for simulation runs and identify your business partner. Enter a reconciliation key (IUT110-##). 2-1-3 After the simulation you can check the log. choose: Choose Utilities industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center. Choose Customer overview from the Information call group. 2-3 2-3-1 Double click on the total amount of the bill. 2-2-2 Once the invoicing has been completed successfully. 2-1-4 Choose the Simulate bill button . 2-3-3 Go to Header data and view the bill amount. 2-3-2 The number of print document lines is displayed under Document overview. Identify the business partner by entering their number in the Business partner field. Enter a reconciliation key. 2-1-2 Begin the simulation with all the billing documents. you can display the log. Do not leave this display. 2-2 Go to the SAP Easy Access menu and choose: Utilities Industry → Invoicing → Invoice Processing → Individual Processing → Create Bill. (C) SAP AG IUT110 60 . choose: Utilities industry → Invoicing → Invoice Processing → Individual Processing → Create Bill. 2-2-3 From the SAP Easy Access menu. Choose the Display Document button or go to the SAP Easy Access menu and choose: Utilities industry → Invoicing → Invoice Processing → Display Print Document. 2-2-1 Identify the business partner. Solutions Unit: Billing and invoicing Topic: Invoicing a business partner 2-1 From the SAP Easy Access menu.

A contract account can be specified for each account. 2-4-7 False. Invoicing processes the meter reading results and the open item accounting data and. In the Rate field. Depending on the budget billing procedure. The posting date. the bill sum total is determined by calculating the statistically posted budget billings or including the outstanding partial bills. generates the bill and the new budget billing plan. document date or system date may be used as the baseline date for calculating when the bill falls due. leaf through the various line items with different line categories using F6 or F7 or 2-3-5 Choose Header data. 2-4-5 True. 2-4-6 True. 2-4-2 False. (C) SAP AG IUT110 61 . using this information. 2-4 2-4-1 True. lines. 2-4-4 False. 2-4-3 True. The Net due date field contains the bill due date. Choose Doc. regardless of whether they are to be billed together with other contracts or separately. 2-3-4 Choose Document overview. If necessary. you can read the various rates used in the calculation.

and schemas  Prices  Rate determination  Rate allocation  SAP AG 1999 (C) SAP AG IUT110 1 .10 Billing Master Data Contents:  Billing master data  Overview of billing master data  Connection to business objects  Rate structure  Rate type and rate category  Rates. operands.

10.2 Billing Master Data: Unit Objectives 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  SAP AG 1999 (C) SAP AG IUT110 2 .

10. SCADA Asset Management & Materials Management  SAP AG 1999 (C) SAP AG IUT110 3 . rate categ. prices Management Business E partner • Operands. IS-U C components R & Service SAP Busin • Rate definition. MM CAD. schemas CA IC Installation R Premise MM services E V External components PM/ & S ER • Rate Premise entry determination CS Entry Systems Device External systems SD Management CO AM GIS.3 Billing Master Data: Overview IS-U/CCS as an integrated component of the SD SD R/3 enterprise FI Sales & information system Sales & Distribution Distribution Financial External Accounting Sales Customer Contract Rate Structure Systems External Billing/ information system Invoicing • Link to master data Sales A/R + A/P Plant (FI-CA) S TOM E Systems Maintenance U • Rate type.

4 Billing Master Data: Introduction  Billing master data enables you to specify contract billing rules for both residential and non-residential customers and provides the basis for a complete SAP Utilities modeling of rates.  SAP AG 1999 (C) SAP AG IUT110 4 .  The flexible universal structuring of rates allows you to implement new and creative sales and marketing concepts.10.  An open architecture allows you to adapt and succeed in a changing environment.

5 Billing Master Data: Business Scenario  Sales and marketing requirements  Description of new products and market segments  Utilities industry  Specification. and discounts  Maintenance of agreed special conditions  SAP AG 1999 (C) SAP AG IUT110 5 . checking and release of new contracts  Customizing of billing master data  Creation of rate category and rate type  Definition of rates.10. prices.

budget.  Open to new billing procedures  Third party billing and cross-company code billing  Special features: Examples include thermal gas billing. interim and period-end billing.  SAP AG 1999 (C) SAP AG IUT110 6 . and so on.10. final billing. floating backbilling. average monthly and equalized billing. such as periodic. billing for external generators and installations without a meter.6 Billing of Utility Services  Billing of contracts for residential and non-residential customers  Supports billing procedures for international utility management.

CS. CS.10. and the register contain information relevant to the rate. the device. SD.7 Business Objects: Rate Allocation Business Regional partner structure FI-CA Contract document A/R + A/P Customer contact Billing document Contract (utility) (utility) Point of Connection Installation Premise delivery object Device Device Equipment Category Device location Connection IS-U IS-U FI- FI-CA FI-CA Rate-relevant SD.  The installation contains: Billing class Rate category  The device contains: Rate category Fact group Price class  The register also contains: Rate category Fact group Price class (C) SAP AG IUT110 7 . appl.. appl  SAP AG 1999  The installation. PM PM Register information Cross Cross appl.

or an installation using a rate type. (C) SAP AG IUT110 8 . devices. you establish the criteria for billing which govern the rates. control the period-end billing or calculation of the budget billing. for example.  Rate type You can allocate a rate to registers.8 Rate Allocation: Overview Contract per division  Installations are classified for billing Rate via the billing class category Installation Billing  The rate category influences indirect class rate determination  The rate type and the rate category determine the rate used for billing.10. Price class Fact group  The fact group contains values Rate type relevant to billing. In the rate category. These criteria can. a rate category.  Rate category Classification of an installation for billing. Device  The price class determines the rental price in conjunction with the price level. for example. The rate category is used in conjunction with the rate type to determine the rate. Price class Fact group Register Rate type  SAP AG 1999  Billing class Classification of installations. for residential customers or non-residential customers.

 Can be valid for several rate categories. For example. you can verify that a residential customer's installation has not been allocated to a nonresidential contract. for example residential/nonresidential contract.  Can be used as a statistical criteria.  As a statistical criteria.  If you change the billing class. you must also change the rate category.  Used for plausibility checks in scheduling and in the billing master data. (C) SAP AG IUT110 9 .  Enables several franchise fee groups to be defined.10.  The billing class is also used for the following purposes:  For consistency verifications between the master data and billing master data. for example in the sales statistics.9 Billing Class I  Classifies installations within a division.  SAP AG 1999  The billing class classifies installations for billing. You do not have to perform a final billing.

The rate category is used in conjunction with the rate type to determine the rate.10 Rate Category I  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  SAP AG 1999  The billing class classifies installations for billing.10. 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 (C) SAP AG IUT110 10 .

no quantities are measured. prices.10. In the case of flat rate services (such as cable services and street lights). demand. This includes any agreed quantities.11 Rate Category II Division Billing Schema Dynamic Period Control Rate Billing Class Category Outsorting Group Advance Billing Notes Backbilling/ Period-End Billing  SAP AG 1999  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. (C) SAP AG IUT110 11 . or flat rates. 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).

flat rate installations  The rate category is used in conjunction with the rate type to determine the rate. Using these. you enter the rate type in the register.  SAP AG 1999  Generally. Also used to determines rates for flat rate installations without installed devices.  Facts Used to determine rates that cannot be derived from registers.12 Definition of Rate Type  Used to classify  Registers  Devices  Flat rates  Reference values for billing  Examples: peak and off-peak rates for active energy. peak rate for active power. gas and water consumption. as well as gas and water consumption. peak rates for reactive energy.  Reference values Used to model street lights.10. peak rates for active power. peak rate for reactive energy. for example (C) SAP AG IUT110 12 .  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. Examples of rate categories are peak and off-peak rates for active energy. you can calculate a device-based settlement price.

10.  Individual rate steps apply billing rules.13 Business Objects: Rate Structure  The rate forms the basis for the billing Rate structure rule for a device. Technology  SAP AG 1999 (C) SAP AG IUT110 13 .  Billing rules have been implemented in the variant programs. or reference Rate value (facts). Operand Variant category programs  Operands are the input and output parameters of the variant programs. control account determination and the Rate steps creation of billing line items. and take Operand into account the franchise fee. register.

10.14
Rate

 Billing rule for a device, register, or reference value (facts),
that is, all billing-related steps performed during billing.
 These steps are represented by one or more variant
programs for which the execution sequence is specified in
the billing schema.
 The rate can be permissible for one of the following:
 Register
 Device
 Reference value (facts)
 Rate steps affect account determination and the creation of
billing line items.

 SAP AG 1999

(C) SAP AG IUT110 14

10.15
Example: Billing Rule for Electricity

Variant
Variant pool
pool
QUANTITY
QUANTITY
Calculates
Calculates x%
*
FACTOR
FACTOR
x% of
of aa quantity
quantity
QUANTITY
QUANTITY

.. .. .. Variant
Variant pool
pool

.. .. .. ACT_KWH
ACT_KWH
* 0.5
0.5 ACT_50%
ACT_50%

REACT_KWH - ACT_50%
NUMBER
NUMBER OF OF DEMAND
DEMAND PEAKS
PEAKS DEMAND
DEMAND
Calculates
Calculates N
N peak
peak averages
averages REACT_KWH ACT_50% BILL_REACT
BILL_REACT
DEMAND
DEMAND
Valuates *
PRICE
PRICE
Valuates demand
demand with
BILLING
BILLING LINE
with aa price
price
LINE ITEMS
ITEMS BILL_REACT
*
BILL_REACT UNIUNI 0.06
0.06 BILLING
BILLING LINE
ITEMS
ITEMS
LINE

.. .. ..
QUANTITY
QUANTITY
Difference
Difference of
-
of two
QUANTITY
QUANTITY
two quantities
quantities
QUANTITY
QUANTITY

Contract
Contract text:
text:
.. .. ..
The
The reactive
reactive energy
energy that
that exceeds
exceeds 50%
50%
.. .. .. of
of the
the active
active energy
energy is
is valuated
valuated using
using aa
separate
separate price.
price.
QTY
QTY
Valuates *
PRICE
PRICE
Valuates energy
energy with
BILLING
BILLING LINE
with aa price
price
LINE ITEMS
ITEMS

 SAP AG 1999

(C) SAP AG IUT110 15

10.16
Rate Structure

Rate

Rate step Fact group

Elementary calculation and Grouping of individual
processing step facts allocated to a rate

 SAP AG 1999

 A rate is a billing rule for a register or a reference value, that is, all billing-related steps executed during
billing.
 A rate step is represented by one or more variant programs. These are small, independent programs that
perform elementary calculation steps.
 Several rate fact groups can be allocated to one rate. In this way, if the same rate is used, the operands
can still be filled with different values.

 A rate step is determined by the variant that is being used.
 Variants are small, independent programs that perform elementary calculation steps.
 Many variants calculate values relevant to billing and therefore generate billing line items. Other
variants convert values and make the results available to subsequent variants.
 Variants usually have input and output operands which represent the parameters included in the variant.
These operands belong to a particular operand category.

In the rate, a combination of variants is used to model the billing rules.
 Example of fact group:
The rate fact group X contains the rate facts "minimum demand = 20 kW" and "discount rate = 10%".
This means that if the customer uses at least 20 kW, he/she receives a discount of 10%.

(C) SAP AG IUT110 16

10.17
Rate Data

Billing class

Permissibility Register operand

Division Rate Validation class

Usage type

Minimum time portion
required for
extrapolation

 SAP AG 1999

(C) SAP AG IUT110 17

10.18
Data for the Rate Step

Variant program

Billing debit and Fine-tuned control
credit sub- of variants
transactions (additional
parameters)

Budget billing
Rate step Franchise fee
debit and credit
group
sub-transactions

Indicator for optional Statistical rate
billing step
Input and
output operand(s)

 SAP AG 1999

 Variants are modules in the rate or in the schema that contain a billing rule.
 A sub-transaction is a key that classifies the line item for account determination and/or the way
application-specific programs are processed. Main transactions are broken down into sub-transactions.
 Indicator for optional billing step: schema steps can only be executed in billing if all input operands are
provided with values for the entire period that the step covers. If this is not the case, the optional
indicator is checked:
If the indicator is not set, billing of the contract is terminated.
If the indicator is set, the schema step is not executed. Processing then continues with the next
schema step.
 Input and output operand: symbolic name defined by the company for the allocated values that are used
as input and output parameters for variant programs.
 Statistical rate: you must specify a statistical rate for all rate steps that generate billing line items. During
billing, the statistical rate is written to the billing line item. This rate key can be used for statistical
analyses of billing documents.
 Franchise fee group: company's own grouping of business partners subject to the same franchise fee
conditions such as major customers or household customers.
 Fine-tuned control of variants: some variant programs require additional input parameters to define the
action of the variant programs. Example: according to settings, a variant that subtracts two values can
also create negative differences or suppress them.

(C) SAP AG IUT110 18

(C) SAP AG IUT110 19

10.19
Structure of the Fact Group

Fact group

Operands

Operand
values

 SAP AG 1999

 A fact group is the grouping of individual facts allocated to a rate.
 Facts are:
Specific values, for example, 100 kW, or
Keys, for example for prices that are allocated to operands and are valid for a particular period.
 Operands are allocated to the fact group.
 Operands manage the operand values.
 The operand values represent the historically managed characteristics of the operands.
 Example of a fact group:
The rate fact group X contains the following rate facts:
minimum demand = 20 kW
discount rate = 10%
This means that if the customer uses at least 20 kW, he/she receives a discount of 10%.

(C) SAP AG IUT110 20

10.20
Operand Data

Determination of the
demand peaks

Operand
category Weighting key

Division Operands Access control

Unit of measurement History management

Rounding rules

 SAP AG 1999

 The operand category classifies the operands for the variant programs.
 Rounding rules consist of:
 The place to which rounding is performed.
If you specify a positive value, rounding is performed to that number of places after the decimal
point.
If you specify a negative value, rounding is performed to that number of places before the decimal
point.
 The rounding type (the principle used to round):
+ for rounding up
- for rounding down
0 for rounding to the nearest whole number

(C) SAP AG IUT110 21

10.21
Operand Categories/Examples

Operand category Description
AMOUNT Amount
DEMAND Services (general)
FACTOR Number with decimal places
QUANT Quantity (general)
QPRICE Quantity-based price
REFVALUE Reference value
SEASON Season
TPRICE Time-based price

 SAP AG 1999

 Operands link values to be billed and variant programs.
 An operand is allocated to an operand category and a division. Operand categories determine the
functions of the operands The variant program determines which operand categories can be used as input
and output operands.
 The system contains 20 different operand categories.
 The operand categories are predefined by SAP and cannot be changed.

(C) SAP AG IUT110 22

10.22
Rate Determination - Operands

Operand Operands Operand values
categories

• Predefined • Determined • Provide operands
individually with values
• Control processing
via variant programs • Serve as the • Define actual
parameters for values
variant programs

 SAP AG 1999

 In the following objects, you can allocate values to the operands:
 rate facts
 Rate category facts
 Installation facts
 Dynamic determination at billing runtime

(C) SAP AG IUT110 23

23 Allocation of Operand Values Installation Price A facts 0. flexible allocation of operand values is possible. you can enter a replacement value instead of a fixed operand value (mandatory/optional entries are required at sub-ordinate levels). the values from the rate facts are used. a month.10. ordered demand. These specifications have preference over the rate facts. With these replacement values.  You can also historically override operand values. number of persons.  If no operand value can be determined during billing.  At rate level or rate-category-fact level. You can also define specifications for all rates in the rate category facts and the installation facts.  You define general operand values that are valid for a larger group of customers in the rate and rate category facts. (C) SAP AG IUT110 24 . and you store individual values at the installation fact level (for example. In the other months.70  SAP AG 1999  Operand values are usually stored in the rate facts and are. valid at rate level. therefore. for example. Exception: the rate step is marked in the rate as an optional rate step.60 facts Have precedence over Price C Rate facts and rate fact group group 0.55 Hierarchy Have precedence over Price B Rate category 0. floor area). billing is aborted and the error is reported in the billing log. In this way. a different price key can be allocated to a certain installation for only a certain period of time. connection loads. installed demand.

(C) SAP AG IUT110 25 .24 Schema 1  Valid for a particular division  Valid for a specific billing class  Contains one or more rates  Establishes the sequence of the billing rate steps  Indicator can be set for:  Billing line item relevant to posting  Billing line item relevant to statistics  SAP AG 1999  A schema is a structure that defines the sequence in which variant programs of the rates to be billed are executed.10.

25 Schema 2  Dependent on the rate category in the installation  Influences sorting of the billing line items on the bill form  Controls the grouping of billing line items  SAP AG 1999 (C) SAP AG IUT110 26 .10.

 The price categories are used internally to control data processing. Normally. the correct rate is proposed by the system. (C) SAP AG IUT110 27 .10.26 Price Categories  Quantity-based price for quantities and consumption  Flat rate fixed amounts per unit of time (consumption flat rates and flat-rate amounts)  Settlement price for the use of a measuring device over a certain period of time  Time-based price for demand and connection values  SAP AG 1999  The price categories are predefined by SAP and cannot be changed. In this case. you create the prices based on the rate.

higher consumption can be cheaper than lower consumption. the price for the next quantity range applies for the entire quantity. In this way.27 Price Types  Normal price Price that is not based on the quantity  Block price One or more prices that are based on the quantity  Scale price Price that is based on the quantity  SAP AG 1999  The price type specifies how the particular price is to be used. you can also use scale and block prices.10. (C) SAP AG IUT110 28 .  Certain sequential quantity areas (for demand and/or energy) are defined by price blocking for which certain prices apply. This prevents higher consumption from being cheaper than lower consumption.  Certain sequential quantity ranges (for demand and/or energy) are defined by price scaling. in other words different prices are used.  In addition to standard single prices. If one quantity range is exceeded.

10.28
Rate Determination

Rate
Rate
Rate
Rate type
type category
category

Allocates Household rate
W ater, ...
A particular rate category and ....
rate type for a particular period 3.50
1 m3 water . . 4,00
Monthly rent
to a rate. ....

 SAP AG 1999

 The rate is determined dynamically (at runtime) from the rate type of the register and the rate category of
the installation.
 Rate determination is managed historically.
 This has the advantage that rate changes can be performed easily. You are then not required to change
the rate types and rate categories in the master data. Instead, a new rate is determined starting at a new
from-date.

(C) SAP AG IUT110 29

10.29
Rate Structure

Data relating to
Rate data Procedure data
customer and
installation Schema 1
Prices and Rate Var.pr. Values E
Contract rate facts Rate 1 X
1 VarProg. A x1 E
2 VarProg. B x2
. . . C
Rate 2
U
1 VarProg. A x3
Ra Rate 1 2 VarProg. C x4 T
Installation ca te Rate 3 VarProg. D x5 I
te
go . . .
ry deter- . . . O
mination .
.
.
.
.
.
N
Inst.
Inst. structure
structure pe Rate n
ty Rate n
t e
Rate
Rate cat.
cat. facts/
facts/ Ra
1 VarProg. A xxx

Installation
Installation facts
facts

Quan tity
nt Execu tion
cut Validation
Data Generation
entry conversion of variant of
programs of billing
and and billing
analysis accordingto lineitems
proration results
schema
 SAP AG 1999

(C) SAP AG IUT110 30

10.30
Discounts / Surcharges

 The discount category defines a discount or surcharge.

 The discount type determines the calculation of:

 Absolute values

 Relative values

 The reference defines how the discount is applied:

 Quantity

 Price

 Amount

 SAP AG 1999

(C) SAP AG IUT110 31

10.31
Billing Master Data: Unit Summary

 Billing master data is classified by:
 Billing class
 Rate
category
 Rate type
 The rate consists of:
 Variants, which are provided with operands
 A schema, which determines the processing sequence
of the variants
 Prices, discounts, and surcharges
 Indirect rate determination
 Reduced maintenance of data in the case of rate
changes
 SAP AG 1999

(C) SAP AG IUT110 32

10.32Exercises: Billing Master Data

Unit: Billing master data
Topic: Rate structure

At the conclusion of these exercises, you will be able to:
• Describe the elements and the structure of a rate.
• Carry out a price change for a particular key date.
• Adjust the budget billing amount to the business partner.

Provide information to customers on rates and price calculations.

1-1 Which rate category is defined for the customer installations of business partner
TB110110##?
1-1-1 Electricity
______________________________________________________

______________________________________________________

1-1-2 Water
______________________________________________________
______________________________________________________

1-2 Which devices and registers are billed to the business partner? Enter the device
and register numbers.
1-2-1 Electricity
______________________________________________________

1-2-2 Water
______________________________________________________

1-3 Which rate types are assigned at device and register level to the business partner for the
divisions below?

(C) SAP AG IUT110 33

1-3-1 Electricity

Device level: _________________________________________

Register level: ________________________________________

1-3-2 Water

Device level: _________________________________________

Register level: ________________________________________

1-4 Determine the rate for the rate category from task 1-1 and the rate types from
task 1-3.

Division
Rate Rate type Rate determined
category
Electricity

Electricity

Water

1-5 Provide information on the electricity rate E1_1.
1-5-1 Where is the rate permissible?
__________________________________________________

1-5-2 The rate is composed of which components?
Name the variant program and describe its functions.
______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

(C) SAP AG IUT110 34

1-5-3 Which operands belong to the rate fact group? What do they mean?
______________________________________________________

______________________________________________________

______________________________________________________

1-5-4 What is the energy price?
______________________________________________________

(C) SAP AG IUT110 35

10.33Billing Master Data Solutions

Unit: Billing master data
Topic: Rate structure

1-1 Identify and display the data of business partner TB110110## in the CIC.
From the SAP Easy Access menu, choose:
Utilities Industry → Customer Service → Front Office/Customer Interaction Center
→ Customer Interaction Center
Go to Info and choose Customer overview. The rate category can be found at the
bottom of the screen.
Alternatively, you can double-click the installation(s) in the navigation area.

1-2 Display (from the customer environment, for example) the individual utility
installations for a business partner (by double-clicking). Then: Devices.

1-3 Display (from the customer environment, for example) the individual utility
installations for a business partner (by double-clicking). Then: Billing view.
You can find the rate types for the devices under Rate types.

1-4 You can find rate determination in the Implementation Guide (IMG):

Division Rate Rate type Rate determined
category
Electricity E1 1001 E1_1

Electricity E1 1002 E1_2

Water W1 3001 W1_1

(C) SAP AG IUT110 36

1-5 You can find the rates under Rates.
1-5-1 This information is located under Permissibility.
1-5-2 Choose Rate steps For a description of the variants, choose Environment →
Variant documentation.
1-5-3 To do this, click on Facts in the Display Rate screen.
You are now looking at the operands. You can display the operand values by
pressing Expand.

You can use the color legend here. To do this, choose Utilities → Color legend.
1-5-4 Double-click on the operand values. For block and scale prices, you need to
double-click again on the price.

(C) SAP AG IUT110 37

11
Real-Time-Pricing

Contents:

 Overview
 RTP interface
 Components of the RTP interface

 SAP AG 1999

(C) SAP AG IUT110 1

you will be able to:  Describe the Real-Time-Pricing interface and its components  Explain the connection of the RTP interface to IS-U billing  SAP AG 1999 (C) SAP AG IUT110 2 .2 Real-Time-Pricing: Unit Objectives At the conclusion of this unit.11.

3 Real-Time-Pricing:Business Scenario  Values determined by automated meter reading for an interval meter should be billed in the system  SAP AG 1999 (C) SAP AG IUT110 3 .11.

11.4 RTP Overview Customer/ Download AMR IS-U/ Contract data Interval Signal system CCS Device manage- ment meter EDM Point of delivery (EDIS indicator) Load shape RTP interface Invoicing Contract accounts System receivable & payable EDI / XML Billing MSCONS Scheduling Other modules  SAP AG 1999 (C) SAP AG IUT110 4 .

5 RTP interface  Allows time series. such as load shapes. to be billed  Takes the load shape data directly from IS-U-EDM  Is fully integrated with IS-U-Billing  Allows flexible modeling of special customer and major customer billing using interval measurement  Is easily extendable (customer-specific formulas and result functions)  SAP AG 1999 (C) SAP AG IUT110 5 .11.

6 RTP-Billing  Period-related billing  Time-of-day blocks (on/off-peak rates)  Day blocks (week day/weekend day)  Season blocks (summer/winter)  Use of a spot price or an index price  Determination of demand values (highest demand.11. for example)  Inclusion of other profiles for billing  Determination of consumption blocks  SAP AG 1999 (C) SAP AG IUT110 6 .

11.7 Example E01 load shape: quantity A03 over limit 2: quantity E03 limit 2: quantity A02 over limit 1: quantity A04 over limit 1: demand E02 limit 1: quantity A01 up to limit 1: quantity  SAP AG 1999 (C) SAP AG IUT110 7 .

. VarProg..25 UNI Step 2 Comparison of two demands 400kW. (C) SAP AG IUT110 8 .8 Data Model for Billing Individual IndividualRTP RTP interface interface PI RTP RTPinterface interface Rate Rate category category P1 Installation Installation Rate Rate Rates Rates determination determination VarProg. Installation Installation P2 structure structure P12 Logical Logicalregister Rate register Ratetype type Billing BillingSchema Schema Profile Rate 1 VarProg.11. . Operand values Step 1 Example: quantity x price 1000kWh. 300kW Rate n Step 1  SAP AG 1999  The billing master data to be processed and its connections is shown above. 0.

9 Interface Components In Formula Out Components Result Season Weekday x1 = Pc1 y1 -> e1 e1 <sum> x3 = Pr1 x1 y1 = min( x1. x2 ) y1 y3 -> e2 Billing period e2 <sum> x1 = Pc1 y1 -> e3 e3 <sum> x3 = Pr1 x2 y2 = max( 0.11. x1 .x2 ) y2 y3 -> e4 e4 <sum> x2 = Pf2 x3 y3 = y2 * x3 y3 y2 -> e5 e5 <sum> < value > p r o f il e p r o f il e  SAP AG 1999 (C) SAP AG IUT110 9 .

11.10 Input Parameters Components Summer Weekend On-peak Off-peak Workday On-peak Off-peak Winter Weekend On-peak Off-peak Workday On-peak Off-peak x1  SAP AG 1999 (C) SAP AG IUT110 10 .

11 Calculation Formula definition In Formula Profile Out x1 y1 = min( x1.11. x1 . x2 ) y1 Profile Profile x2 y2 = max( 0.x2 ) y2 Profile Profile x3 y3 = y2 * x3 y3 Profile Profile Function modules  SAP AG 1999 (C) SAP AG IUT110 11 .

12 Result Components y1 Summer Weekend On-peak Off-peak Workday On-peak e1 Off-peak Winter e2 Weekend On-peak Off-peak Workday Result Function Op.11. Cat. On-peak e1 sum QUANT e2 average DEMAND Off-peak e3 peak DEMAND  SAP AG 1999 (C) SAP AG IUT110 12 .

. Cat. .13 Transfer of Results to RTP Operand y1 result function Op. 007 QUANTI01 ONPEAKCON .  SAP AG 1999 (C) SAP AG IUT110 13 . Pricing for OFF Peak consumption . Pricing for ON Peak consumption 008 QUANTI01 OFFPEAKCON ..11. e1 sum QUANT e2 average DEMAND e3 peak DEMAND IS-U IS-Ubilling billingschema: schema: Rate: ON_OFF_PEAK RegOperand RTP-Interface ON_OFF_PEAK 001 .. ..............

for example)  SAP AG 1999 (C) SAP AG IUT110 14 .14 Real-Time-Pricing: Unit Summary  The Real-Time-Pricing interface is fully integrated with the IS-U billing procedure  It links energy data management (profile management) to the IS-U billing functionality  You can use the RTP interface to flexibly establish certain billing regulations (billing of interval meters with special price agreements.11.

12 Budget Billings Contents:  Budget billing procedure  Determination and requirements of budget billing  SAP AG 1999 (C) SAP AG IUT110 1 .

2 Budget Billing: Unit Objectives At the conclusion of this unit.12. you will be able to:  Explain the difference between a budget billing plan and a payment plan  Create and change budget billing plans  SAP AG 1999 (C) SAP AG IUT110 2 .

you recalculate the budget billing plan.3 Budget Billing: Business Scenario  A customer's consumption pattern has changed.  After adjusting the period consumption.  SAP AG 1999 (C) SAP AG IUT110 3 .12.

12.4 Budget Billing Procedure: Overview Budget billing procedure Budget billing Payment plan IS- IS-U A down payment. and and is recalculated for the next settlement at the end of the period. which is Monthly bills for an agreed determined from the bill sum total amount (fixed or variable). period Budget billing categories Payment plan categories  statistical posting with  fixed amounts budget billing requirements Budget Billing Plan  actual debit entry with partial  variable amounts bill Average Monthly Plan  SAP AG 1999 (C) SAP AG IUT110 4 .

The amounts due for later months are calculated using the average of the previous months plus the current bill and the accumulated difference. actual billing occurs monthly. the customer is charged an average amount based on billings over the next 12 months (orless in the case of new customers).  SAP AG 1999 (C) SAP AG IUT110 5 . and the results are shown on the bill.  Average Monthly Billing Plan /Equalized Billing Plan In Average Monthly Billing/Equalized Billing.5 Payment Plan Categories  Budget Billing Plan An average amount is determined manually or by simulation.At the end of this period.In addition. In addition. actual billing occurs monthly. simulation occurs again for the next period. The customer pays this amount for a specified period.12. The results of this billing are shown onthe bill and settled in the last month of the billing period.

6 Budget Billing Plan: Overview Settlement Printout Amount Budget billing limits cycle Budget billing Minimum Due date charge determination plan Amount Manual calculation rounding Automatic Amount adjustment determination factor ✔ Grouping of budget billings from one billing period ✔ Allocation of budget billings to individual contracts ✔ Display of the accumulated and individual budget billing amounts ✔ Display of the open budget billing amounts ✔ Automatic and manual determination of the budget billing amount  SAP AG 1999 (C) SAP AG IUT110 6 .12.

All other contracts belonging to the contract account can have an individual budget billing plan. for example). for example) Therefore. (C) SAP AG IUT110 7 .7 Creating / Adjusting Budget Billing Plans  Business processes  For move-in  For periodic billing Extrapolation Due date  For invoicing Budget billing plan Grouping of contracts  Amount determination Amount check  Manual calculation  Automatic extrapolation  Due date of budget billing amounts  Terms of payment from the contract account  SAP AG 1999  Utility companies often only bill for their services at the end of a supply period (during annual consumption billing.12.  Budget billing plans are normally created automatically (during invoicing or move-in. they can also be created manually. to maintain liquidity during the current period. However.  Contracts that must be invoiced together are assigned a joint budget billing plan. budget billings are billed by anticipating the total amount owed by the customer. The budget billing plan defines the dates and size of the budget billings and forms the basis for increases in budget billings.

The budget billing items created in this way are transferred to invoicing in the billing document... ...... . Billing simulation for this period Distribution Distribution of of total total simulated simulated amount amount over the budget billing due dates over the budget billing due dates  SAP AG 1999  Billing calculates the consumption up until the next scheduled meter reading date.12. .. . 14/01 Budget billing period Extrapolation of consumption using configured weighting procedure. Invoicing accepts these amounts and distributes them to the individual budget billing due dates. .. schedule records must already be generated for the next billing period..... (C) SAP AG IUT110 8 .  When billing....... 08/01 Billing period 2001 2001 09/01 .. Simulated billing is carried out for the budget billing period.... ..... . .8 Quantity-Based Extrapolation Actual Next scheduled meter reading meter reading date 2000 2000 from scheduling 11/01 ....... .. ...

 Sales tax posting on  Sales tax posting on payments receivables  SAP AG 1999  The scheduled budget billing dates are determined from the portion valid for the contract and the parameter record. (C) SAP AG IUT110 9 .12. Statistical Actual posting debit-entry FI-CA posting FI-CA posting  Statistical posting document  Actual debit-entry  Items per contract  Items per contract  Repetition items for each  Documents only in customer budget billing amount due account when receivable date. total owed.9 Budget Billing Amounts Due Process budget billing amounts  Due date determination using terms of payment  Scheduling using the portion Budget billing request Creation of partial bills IS- IS-U Generation of statistical posting Generation of debit-entry partial documents that are calculated bills that are calculated as down as down payments towards the payments against the bill sum bill sum total owed. meaning that the scheduled dates are at regular intervals over the period (monthly or every few months). a debit entry can be generated in Contract Accounts Receivable and Payable or a statistical posting (budget billings that do not affect the general ledger) can be carried out. Whilst changes in the budget billing plan take effect immediately. entries in the contract only become effective the next time a budget billing plan is produced.  When requesting budget billings.  The specifications for the portion can be overridden in the budget billing plan or in the contract. The following details are defined:  Length of the budget billing period (several months or one year)  Budget billing cycle.  The budget billling due date results from the budget billling dates and the terms of payment in the contract account.

12.10 Budget Billings: Summary You are now able to:  Explain the difference between a budget billing plan and a payment plan  Create and change budget billing plans  SAP AG 1999 (C) SAP AG IUT110 10 .

13 Contract Accounts Receivable and Payable Contents:  Overview  Documents  Structure  Use  Posting documents  Account display  Payments  Returns  Dunning  Deferral and installment plan  SAP AG 1999 (C) SAP AG IUT110 1 .

 SAP AG 1999 (C) SAP AG IUT110 2 .  Provide information on customer accounts.  Explain some common business transactions in Contract Accounts Receivable and Payable and perform them in the system. you will be able to:  Describe the document structure in contract accounts receivable and payable.13.2 Contract Accounts Receivable and Payable: Unit Objectives At the conclusion of this unit.

E & Service C Central R Components Management Business E AM of IS-U partner CA IC MM ContractV Installation R Premise External services E R entry Standard R/3 PM/ & SE Premise Components SM A/R + A/P Entry Entry Systems SD (FI-CA) Device Management External systems CO AM GIS. SCADA Asset Management & Materials Management  SAP AG 1999 (C) SAP AG IUT110 3 .13. MM CAD.3 Contract Accounts Receivable and Payable: Overview IS-U/CCS as an integrated SD component of the FI R/3 enterprise FI Sales & Distribution information system Financial External Accounting Sales Contract Systems Customer Billing/ FinancialA/R + A/P Invoicing information system TOM Accounting Plant Maintenance (FI-CA) U S (FI.

4 Contract Accounts Receivable and Payable: Business Scenario  Post request for energy consulting  Display account balance  Payment by check for account balance  The check was not covered: Return with charge  Dunning proposal for contract account.13. followed by dunning  Arrangement of installment plan  SAP AG 1999 (C) SAP AG IUT110 4 .

5 Contract Accounts Receivable and Payable and FI-CA  Contract Accounts Receivable and Payable is the FI-CA component: (Financial Accounting: Contract Accounts Receivable and Payable)  FI-CA is designed as a sub-ledger for customer processing.  SAP AG 1999 (C) SAP AG IUT110 5 .13.

Telecommunications (C) SAP AG IUT110 6 .6 FI-CA Has An Open Architecture IS-U IS-T FI-CA Data exchange Open items IS-IS/CD Other Posting information Information Business processes Workflows  SAP AG 1999  IS-IS-CD: Industry Specific Component .Insurance: collections/disbursements  IS-T: Industry Specific Component .13.

 Documents are assigned to business partner accounts and contract accounts (and depending on the industry.7 Special Features of FI-CA  Suitable for a large number of contract accounts and documents:  Optimal use of storage space by means of a special document structure. they are also assigned to contracts). dunning run).  Standard processes (such as posting or paying) can be changed without making any modifications.  Processing of business transactions convenient for clerks.  Summarization of general ledger information (summary records).13.  Parallel processing of mass runs (such as payment run.  SAP AG 1999 (C) SAP AG IUT110 7 .

communication data and bank details. terms of payment and dunning procedures. such as names.  Represents a natural or legal person with whom business relationships can be conducted.  Object. for which open item accounting is managed in Contract Accounts Receivable and Payable IS-CA  Usually represents a group of contracts BP (industry sector).13. Account Account  Contract (industry-specific) Contract Contract Contract  Document items IS-U  SAP AG 1999 (C) SAP AG IUT110 8 . such as payment methods. Account  Contract account  Contains control data.8 Central Objects in FI-CA  Business partner  Contains central data. addresses.

9 Contract Accounts Receivable and Payable: Business Transactions Document Payment Payment posting posting Incoming Incoming payments payments posting Account Account Document Document reversal reversal Interest maintenance maintenance Returns Returns Account Account analysis analysis Dunning Dunning processing processing Installment Installment plan plan Deferral Deferral Irrecoverable Irrecoverable debt debt  SAP AG 1999 (C) SAP AG IUT110 9 .13.

13.10 Contract Accounts Receivable and Payable: Posting Documents  Overview  Documents  Account display  Payments  Returns  Dunning  Deferral and installment plan  SAP AG 1999 (C) SAP AG IUT110 10 .

11 Posting Documents: Objectives At the conclusion of this topic.  SAP AG 1999 (C) SAP AG IUT110 11 .13. you will be able to:  Explain the document structure in contract accounts receivable and payable.  Post receivables items.

 Examples include rent receivables.13.12 Posting Documents: Introduction  If business processes are not integrated with IS-U or SD. SAP Utilities individual postings can be inserted into the system as manual documents. or automatically connected to Contract Accounts Receivable and Payable by an interface. lease receivables as well as receivables for an energy consultant.  SAP AG 1999 (C) SAP AG IUT110 12 .

13 Posting Documents: Business Scenario  Post request for energy consulting  Display account balance  Payment by check for account balance  The check was not covered: Return with charge  Dunning proposal for contract account. followed by dunning  Arrangement of installment plan  SAP AG 1999 (C) SAP AG IUT110 13 .13.

posting date. reconciliation key. (C) SAP AG IUT110 14 .13.  Business partner items (receivables lines or reconciliation lines) These contain all data relevant for payment transactions or dunning and the receivables account or reconciliation account which is debited or credited. such as document date.  G/L account item (revenue lines) This contains the data for the profit and loss statement.14 Documents in Contract Accounts Receivable and Payable Document Business partner G/L account item item  SAP AG 1999  The basis for Contract Accounts Receivable and Payable is the document with:  Document header This contains the data that is valid for all line items. as well as data for sales tax.

13. which identifies the document in the contract account receivable and payable for each client. (C) SAP AG IUT110 15 . or is entered by the user when a document is created. Whether the number is entered automatically or manually. The document number is determined during posting by the number range. You specify: A number range from which the document number is chosen.  Document types  Distinguish between business transactions  Control document storage using the number range allocated.  Document number  Key.  The type of number assignment is decided by the document type entered in the document header. FA Invoicing.  Depending on the type of number assignment.15 General Document Data General • Document date • Document type • Document number Document General data  SAP AG 1999  The document date indicates the issue date of the original document.  Are valid for a single client  Examples of document types are: AB Miscellaneous document. the document number is assigned automatically by the system when the document is posted. GB Fees.

The exchange rate is saved at the item level. This field can also be filled with other data. it is possible to copy the document number in the reference number field by entering "*". The exchange rate field can only be used by clerks who enter documents for company codes with the same local currency. If the document was generated in your company and a document number is not known for the partner. The exchange rate that is entered is proposed in the document items during entry of a document (possible entries). The reference document number is used as a search criterion for document display or change. the reference document number is sometimes printed in place of the document number.  The transaction currency is the key of the currency. This local currency must be recorded in the user settings. (C) SAP AG IUT110 16 . In correspondence.13.16 Document Data: Reference and Currency General • Document date • Document type • Document number Reference and currency • Reference Document • Currency • Conversion rules General data  SAP AG 1999  The reference document number can contain the document number for the business partner. in which the document is (or was) posted.  Exchange rate Exchange rate used for the conversion between the transaction currency and the local currency. Enter the number specified by the partner.

13. the key is assigned by the program that executes processing (such as a payment run). This means that itemization of the totals posted in the general ledger is possible. If you do not want a summary. This document is saved in the G/L document as a single document item. The key is entered as an external reference in the document header field "reference key" during transfer of the summary records to SAP R/3 general ledger accounting.  Document items belonging to one summary record are summarized. You must assign the key for manual postings. (C) SAP AG IUT110 17 . The posting date may be different to the entry date (date of entry in the system) and the document date (date on which the original document was created). you can select single document or single item in the corresponding field for each document.17 Document Data: Link to General Ledger Accounting General • Document date • Document type • Document number Reference and currency • Reference Document • Currency • Conversion rules General ledger • Posting date • Reconciliation key • Single document General data  SAP AG 1999  Posting date: The date on which the document was posted in Contract Accounts Receivable and Payable.  Reconciliation key for G/L accounting: Key. in which the summary records of Contract Accounts Receivable and Payable are written for transfer to downstream accounting. For mass processing.

18 Document Data: Entry Control General • Document date • Document type • Document number Reference and • Entry variants currency • Calculate taxes • Reference Document • Jurisdiction code • Currency • Company code • Conversion rules • Clearing reason • Screen variants General ledger • Posting date • Reconciliation key • Single document General data Entry control  SAP AG 1999  The entry variant controls which fields are to be hidden for posting.  The user settings allow you to block cross-company code posting. the default company code is added to each document line item. users must enter a company code. If you do not enter a clearing reason.13. The company code is an entry aid for documents or line items that are to be posted in the same company code. the system will ask you to enter one before posting the document. and displaying a document. If this setting has been made. you must specify a clearing reason here. you have to enter the tax lines separately. This allows you to customize screens for the business transaction (such as a down payment).  The clearing reason is saved in the cleared line items and can be displayed during analysis of the single items (such as in the account balance display). If you do not set the indicator. changing.  Default value for company code  Where no company code is entered. If you clear items using the function Post document. (C) SAP AG IUT110 18 .  The calculation of taxes means that the system automatically calculates taxes using the specifications in the business partner items during simulation or posting.

This can then be specified on all correspondence.6. The required key can be entered as an alternative to saving a long text for each item.30. To differentiate between these. Example: If a customer bill contains items from different divisions.  A grouping key can be assigned to any document items that should be depicted as one item in lists. Examples:  Q195 First quarter 1995  0195 January 1995  H195 1. a summarized list simplifies the allocation of incoming payments. correspondence and account processing. such as dunning notices and payment advice notes.1995 (C) SAP AG IUT110 19 .1. if details about the billing period that the receivable relates to are to be included in the correspondence.13. The asterisks are automatically removed when the document is printed. texts for external use must begin with "*". but only one final amount is payable by the customer. for example.1995 .  The period key can be used.19 Data on Business Partner Item Business partner Due dates: Contract account Net/Cash discount/ Contract deferral Clearing data Company code Dunning data/ Procedure Interest calculation Set automatically Amounts Payment data Additional data -Item text -Grouping -Period key Repetition Business specifications Alternative partner partner for item payments Individual transfer to general ledger Optional specifications Mandatory specifications  SAP AG 1999  Item text can be used both internally and externally.

The planning level is used for control in cash management.20 Data on G/L Account Item General ledger: Company code. bank sub-accounts). (C) SAP AG IUT110 20 . INPUT is used for input tax.  The tax transaction determines which type of tax is used. Automatic determination of tax accounts is performed using the transaction key.13. Examples: TAX is used for output tax. The value date is decisive for representation of the cash management position. The value date indicates the day on which the financial transaction actually took place in financial accounts (bank accounts. The keys are defined in the system and cannot be changed. Amounts G/L account and tax code Account assignment for subsequent accounting G/L account item  SAP AG 1999  Data on G/L account item:  Value date: Day when values are set.  A planning level is allocated in the document item of Contract Accounts Receivable and Payable for updating in cash management. The transaction key is for documenting the tax type after transfer into R/3 general ledger accounting. The value date indicates the day on which the financial transaction is expected for payment postings that are generated before payment.

 Receivables and credit memos can also be cleared either immediately or partially.21 Manual Document Entry: Items  Receivables / credit memos Business partner BP1 Contract account CA 1  Automatic determination of Amount UNI 100 general ledger accounts and tax accounts using Business partner BP2 transactions Contract account CA2  Classification using Amount UNI 150 document type  Automatic determination of Business partner BP3 due dates using terms of Contract account CA3 Amount UNI 250 payment in the contract account  Receivables or credit can be cleared immediately  SAP AG 1999  Receivables and credit memos can be entered manually.  Document line items do not all have to belong to the same business partner.13. a transaction that is defined in the system is specified for each business transaction. the general ledger accounts are automatically determined and inserted in the receivables and revenue lines.  Receivables lines can be repeated with different due dates and specification of a start date at monthly or daily intervals (for example. During posting. for budget billing or installment plans).  Classification of documents occurs with specification of a document type. The same occurs for tax accounts. In this way. (C) SAP AG IUT110 21 .  Due dates are determined automatically using the terms of payment in the contract account.

13.  SAP AG 1999  Example for:  Main transaction: periodic billing  Sub-transaction: receivable from energy charge (C) SAP AG IUT110 22 .22 Transactions in Contract Accounts Receivable and Payable Transactions explain the business transaction on which the posting of a line item is based.  A transaction is a combination of main and sub-transactions  Texts for the transactions explain the business transaction and are available for correspondence  Transactions control IS-U account determination  Transactions control IS-U determination of value-added tax  IS-U uses internal main and sub-transactions. The transactions also control these business processes. which are assigned internally by various IS-U business processes.

tax is only due for statistical budget billing receivables. if payment is not made. Similarly.23 Examples of Transactions Main transaction Sub-transaction Billing Energy charge receivable Energy charge credit Settlement price receivable Settlement price credit Service charge receivable Service charge credit Charges Statistical dunning charge Dunning charge Charge for items in installment plan  SAP AG 1999  Statistical posting simplifies the administration of doubtful receivables (items). on payment of the budget billing amount thus only when the receivables are posted to the general ledger. Dunning charges are another example of charges that tend not to be payed. as these postings are not transferred to the general ledger. Budget billing receivables are a typical example. is less likely than in cases where a bill exists. and are thus easier to reverse if they are not paid. there is no bill and the collection of payment. as in most cases.13. (C) SAP AG IUT110 23 .

13. (C) SAP AG IUT110 24 .-- C 800000 UNI 600 Generate 50 175001 96.: Amount UNI 116 Net UNI 100 Tax UNI 16 Reconciliation key: 98126ISU01 Document posting FI documents Summary Record 40 140000 696.-- C 175001 UNI 96 postings Reference key 98126ISU01 Reconciliation key Reference transaction 98126ISU01 FKKSU  SAP AG 1999  One use of the reference key is to relocate individual items in the sub-ledger (taken from the general ledger).: Amount UNI 580 Net UNI 500 Tax UNI 80 2.24 Transfer to General Ledger Accounting FI-CA documents 1. Doc.-- D 140000 UNI 696 50 800000 600. Doc.

13.25 Summary Record  Transfer unit for postings from Contract Accounts Receivable and Payable to Financial Accounting.  Single documents from Contract Accounts Receivable and Payable are grouped into summary records if:  Summarization was not prevented manually.  They have the same reconciliation key.  Examples for summarization criteria are:  Company code and date  Debit/credit indicator  General ledger account  Currency  Downstream system criteria  SAP AG 1999 (C) SAP AG IUT110 25 .  They can be grouped according to G/L accounting and subsequent application criteria.

26 Posting Documents: Summary (1)  The most important data in the document header is:  Document number  Reconciliation key  Posting date  Document date  The business partner item:  Is allocated to a business partner.  The G/L account item contains information on the corresponding G/L account.  Contains the amount to be posted. From the clerk's point of view. Receivables lines form the basis of repetition lines and can be repeated for different due dates. In this case. One example of this is a normal payment that leads to complete clearing of the affected receivables lines. only a new document header is written for the payment.  SAP AG 1999  Repetition lines also exist in the document. (C) SAP AG IUT110 26 .  A document does not have to contain all of the lines mentioned above.13. since the data relevant for the account assignment comes from the receivables lines. They make it possible to save memory space and are used for representing budget billing plans and installment plans.  Contains the account assignment for G/L accounting determined by the transaction. these lines are irrelevant since they appear in the contract account display as normal items and can be processed accordingly.

 This is possible for both receivables and credit memos.13.  An item can be entered:  Individually  In a list  SAP AG 1999 (C) SAP AG IUT110 27 . documents can be posted manually in Contract Accounts Receivable and Payable.27 Posting Documents: Summary (2)  If necessary.

28 Contract Accounts Receivable and Payable: Account Display  Overview  Documents  Account display  Payments  Returns  Dunning  Deferral and installment plan  SAP AG 1999 (C) SAP AG IUT110 28 .13.

 SAP AG 1999 (C) SAP AG IUT110 29 .  Use the navigation options in the item display.13.  Use the "Customer overview" and "Customer account” information processes.  Provide information on the items of a customer account. you will be able to:  Provide information on the balance and development of a customer account.29 Account Display: Objectives At the conclusion of this topic.

13.30 Account Display: Introduction  Utility companies often have to deal with large numbers of items due to the large number of customers and budget billing payments.  Variable displays are provided that can easily be adjusted according to the situation.  SAP AG 1999 (C) SAP AG IUT110 30 .  Information on customer accounts is given quickly SAP Utilities and comprehensively.  Different display formats can be used depending on the tasks of the clerk (accounting. for example)  Individual selection of display variants can be defined in the user parameters. dunning.

31 Account Display: Business Scenario  Post request for energy consulting  Display account balance  Payment by check for account balance  The check was not covered: Return with charge  Dunning proposal for contract account.13. followed by dunning  Arrangement of installment plan  SAP AG 1999 (C) SAP AG IUT110 31 .

13. due.32 Account Display: Initial Screen  Business partner. installment plan. or statistical items. contract account. collective bill  List category for restricting the items to be displayed according to "status": Examples: All open. contract Company code.  User-specific limitations  List representation defines the line structure  Any type of sorting is possible  SAP AG 1999 (C) SAP AG IUT110 32 .

you can select:  Standard. in order to specifically determine the selection of items. non-statistical items).  The list category makes it possible to save frequently used selections under one key. the selection can still be changed using "detail".13.  Even if a list category is used.33 Account Display: List Category  The list category determines which items are selected for the account display (such as open items or down payment requests).  As an alternative to selecting items using list categories. in order to choose the standard selection (all open.  Detail. This change is not saved and is only used for the current display.  SAP AG 1999 (C) SAP AG IUT110 33 .

13. It is also possible to totalize values using particular criteria.  Different line structure variants can be selected in the account display.  SAP AG 1999 (C) SAP AG IUT110 34 .34 Account Display: Line Layout  Determines which fields of a document are included in the account display.  The same output list can be viewed in a number of ways.

35 Account Display: Navigating in the Document Display Header Item G/L list item list Overview Detail screen Detail screen of of business G/L items partner items  SAP AG 1999  It is possible to return to the header from any screen. (C) SAP AG IUT110 35 .13.

36 Account Display: Summary (1)  Variable item selection  All items/open items/cleared items (with/without payments)  Statistical items (all/budget billing plan/charges/.13.)  User-specific selection criteria Example: By due dates  Variable display  "Free" selection of data fields  User-defined account display  SAP AG 1999 (C) SAP AG IUT110 36 ...

13.  Sort and summary functions within the account display  SAP AG 1999 (C) SAP AG IUT110 37 .37 Account Display: Summary (2)  Immediate access to environment data  Document  Business partner/contract account/contract  Payment use  Source receivable(s) for installment plan items  Dunning history  ...

38 Contract Accounts Receivable and Payable: Payments  Overview  Documents  Account display  Payments  Returns  Dunning  Deferral and installment plan  SAP AG 1999 (C) SAP AG IUT110 38 .13.

13.39 Payment Run: Objectives At the conclusion of this topic. you will be able to:  Explain the processing steps of a payment lot  Post payments using a payment lot  Post payments via payment at cash desk  SAP AG 1999 (C) SAP AG IUT110 39 .

depending on the situation.13. These include data medium exchange.40 Payment Run: Introduction  Utility companies have to deal with large numbers of incoming payments in a reliable efficient manner.  Background and dialog processes are provided for processing payments. SAP Utilities  Payment flow reaches the utility company in various ways.  SAP AG 1999 (C) SAP AG IUT110 40 . automatically read documents and other documents.

13. followed by dunning  Arrangement of installment plan  SAP AG 1999 (C) SAP AG IUT110 41 .41 Payment Run: Business Scenario  Post request for energy consulting  Display account balance  Payment by check for account balance  The check was not covered: Return with charge  Dunning proposal for contract account.

financial institutions. it is possible to post an account at contract account level.13. bank transfer or postal cash payment order and the corresponding output media are created. Manual post- processing is also possible.  Credit repaymentCredit is automatically repayed by check.  Collection procedurePayments are handled by collection or direct debit from financial institutes or credit card companies and the corresponding output media are created. as well as for returned incoming checks and postal cash payment orders that could not be delivered. Payments are automatically allocated to one or more receivables items. Credit items released for settlement are also taken into account.42 Automatic and Manual Payments  Automatic incoming  Payment lot payments  Collection procedure  Check lot  Credit repayment  Credit card lot  Returns Automatic Manual  Payment at cash desk  Returns lot  SAP AG 1999  Automatic incoming payment: Incoming payment data from previous systems. The system automatically creates a payment posting for the corresponding business partner. If an item cannot be allocated.  Returns processing Automatic returns processing with workflow link is provided for returned payments from financial institutions and credit card companies. or agencies is processed here. (C) SAP AG IUT110 42 .

 Data for a group of incoming checks is stored in a payment lot. This type of lot is called a check lot.  SAP AG 1999 (C) SAP AG IUT110 43 .43 Payment Lot  The payment lot stores data from external payments.13.  Bank transfers and/or debit memos that were received are extracted from an account statement and stored in a payment lot.  Payment data is stored in a lot if:  It has the same source  It is to be processed jointly.

44 Payment Lot: Structure  Data is saved in the payment lot header if: Header Header entry entry  It applies to the entire lot  It is used as a default value for items  SAP AG 1999  Data that applies to the entire lot:  Key  Search term  Posting date  Bank clearing account  Company code for the bank posting  Reconciliation key for general ledger accounting  Currency  Value date (C) SAP AG IUT110 44 .13.

13.45 Payment Lot: Structure  Data is saved in the payment lot header if: Header Header entry entry  It applies to the entire lot:  It is used as a default value for items  An item is a payment with: Item Item 11  An amount Item Item 22  Specifications for the selection of receivables to be cleared  SAP AG 1999 (C) SAP AG IUT110 45 .

 SAP AG 1999 (C) SAP AG IUT110 46 .46 Payment Lot: Processing Steps New Payment payment Create Close Post lot lot complete Post- Change processing  Payment lot processing includes the following steps:  Create  Change (optional)  Close (deletion and insertion of items is no longer allowed)  Post  Post-processing (for clarification and errors) Post-processing is necessary if postings were generated in an interim account. or if it was not possible to make any postings.13.

clearing reason.13. items. and business area. currency.  The document type.47 Payment Lot: Create New Payment payment Create Close Post lot lot complete  A payment lot can be created:  In dialog mode (for example a check lot)  By program (for example an incoming bank transfer lot)  The following is specified:  Reconciliation key  Header data for the payment lot  The document. (C) SAP AG IUT110 47 . and the selection categories are recorded in Customizing. and the clearing of open items  SAP AG 1999  Default values on the header screen:  The current date is defined  The last values entered (if available) are inserted automatically for the company code.

 By pressing the Additional specifications key. K for contract account. you can branch to the detail screen of the selected item.13.  On the detail screen. which are essential for choosing open items that are cleared by payment.  These include: G for business partner. (C) SAP AG IUT110 48 . You can enter additional data on the payment.  Selection categories are one character abbreviations that are defined in Customizing. Variants of the line structure can be recorded in Customizing. you can enter any additional data necessary for payment allocation or for further clarification. if required. V for contract  SAP AG 1999  Enter one line of data for each payment during list entry. You can change the entry variants using the Screen variant key.48 Payment Lot: Create Items New Payment payment Create Close Post lot lot complete  The essential entries are:  Amount  Payment use via selection category and selection value.

 Data on items that have already been entered can also be corrected.  Interrupted entry of a payment lot can be resumed using this function.49 Payment Lot: Change New Payment payment Create Close Post lot lot complete Change  Items can be deleted and added as long as the payment lot is not closed.13.  SAP AG 1999 (C) SAP AG IUT110 49 .

13.  Corrections can still be made on the payment lot items after closing.50 Payment Lot: Close New Payment payment Create Close Post lot lot complete  Closing a payment lot means that adding or deleting items is no longer possible.  Posting cannot begin until a lot is closed.  SAP AG 1999 (C) SAP AG IUT110 50 .

The document number is recorded in the associated items in the payment lot.  The payment use can consist of different components: Clearing/partial clearing of open items Postings on account Expense/revenue (payment difference) Generation of new receivables that are cleared immediately (charges. and one posting for clearing account to payment use for each check (in planning).13. interest) (C) SAP AG IUT110 51 .  Postings to customer account including payment use with:  Clearing of open items and/or  Generation of payments on account  Posting to an interim account if the payment use is unclear  A check deposit list can be printed for check lots  SAP AG 1999  The following postings are generated in a posting run:  For a check lot: One summary posting for each lot: incoming checks account to clearing account. The document number is noted in the payment lot header.  For other lots: One posting of bank sub-account to payment use or interim account.51 Payment Lot: Post New Payment payment Create Close Post lot lot complete  Postings can either be dealt with in dialog mode or in a background process (typical for mass data).

charges. down payments) caused by clearing  Posting of the clearing document and noting the clearing information in the items to be cleared  SAP AG 1999 (C) SAP AG IUT110 52 .52 Automatic Clearing: Process  Determination of the amount available for clearing  Determination of the selection criteria for open items  Open item selection  Conversion of item currency to clearing currency  Distribution of clearing amount to open items  Generation of document items (such as cash discounts.13.

 Correction of payment items (such as selection specifications) and restart of postings for selected items.  Triggering of repayment if the payment use cannot be determined.13.  SAP AG 1999 (C) SAP AG IUT110 53 .  Manual posting and clearing for selected items.53 Payment Lot: Post-processing New Payment payment Create Close Post lot lot complete Post- processing If automatic allocation was not possible:  Clarification of payment use and transfer from interim account to a contract account.

4.four hundred DM .  SAP AG 1999  Within the cash desk function.  A receipt can be printed following the posting. 2000.  A distinction is made between cash payments and payment by check or credit card. (C) SAP AG IUT110 54 .13. payments can be directly allocated to open items for a business partner.  You can use a payment proposal or assign the payment manually. Business partner Contract account Contract account Post Post Contract directly Document number Post Post in in Net due date dialog mode Payment form no. X Account no.45 UNI UNI deposit list on on April April 15. transfers and cash analysis can be carried out. 2000.400.45 123.  If an overpayment is made in cash.- Am ount in words ON Red Cross New York Or the holder City 1. withdrawals. Payment Payment posting Check Receipt You You paid paid 123. Check no.1996 Date Signature The printed ch eck text must not be alt er ed in an y way. You can display a cash desk structure and functions such as deposits. X Am ount X Sort code X Text 00000150900 12131400 67291500 11 Do not write in or stamp this field.54 Payment at cash desk Deutsche Bank Pay the bearer CurrencyAmount .  The cash journal offers further functionalities. 15. the remaining amount is used to decide whether a posting on account is to be made or whether this amount is to be paid to the customer.

The clearing amount can be overwritten (partial clearing). The screen width can be set to 80 or 120 characters (more detailed information on items). the system sets the amount that is necessary to bring the clearing to zero. Cash discount fields can be displayed or hidden.  The processing screen can be reconfigured by pressing the Presentation key. You can change the currency that is displayed.  The clearing can be posted if the difference:  Is zero (green light appears)  Is within a predefined tolerance limit (yellow light appears)  SAP AG 1999  Open item processing: By double-clicking in the Amount column. To do this. select the items in the left column and then press the desired key (active or inactive). The posting amount and clearing amount can be displayed as net or gross. Items can also be set to active and inactive in groups. (C) SAP AG IUT110 55 .  The allocated amount is the sum of the clearing amounts that is allocated to the individual items.  The difference between the clearing amount and the allocated amount is decisive here. The posting amount of the item is proposed.55 Clearing: Dialog Processing  Open items are displayed:  In a list with one line per item and  In a control block that displays the status of clearing processing. a value appears in the "Clearing amount” column. You can switch between selection mode and command mode. The line structure (information displayed on open items) can be varied.13. By double-clicking in the Clearing amount column. As soon as an item is active. inactive items become active and vice versa. The summarization of items in the display can be switched on and off.

 Payments are processed:  In payment lots  At the cash desk  Detailed rules can be defined for automatic item clearing.13.56 Payment: Summary  Payment can be handled automatically and manually in Contract Accounts Receivable and Payable.  SAP AG 1999 (C) SAP AG IUT110 56 .

57 Contract Accounts Receivable and Payable: Returns  Overview  Documents  Account display  Payments  Returns  Dunning  Deferral and installment plan  SAP AG 1999 (C) SAP AG IUT110 57 .13.

13.58 Returns: Objectives At the conclusion of this topic. you will be able to:  Describe the returns process  Post a return  SAP AG 1999 (C) SAP AG IUT110 58 .

13.  The additional workload is kept as low as possible by:  Reversing payment to the account  Passing on charges  Triggering of subsequent activities such as correspondence or new move-in  SAP AG 1999 (C) SAP AG IUT110 59 .59 Returns: Introduction  Utility companies must deal with a large number of incoming and outgoing payments. or not covered.  A certain percentage of these cannot be successfully SAP Utilities processed because the account is incorrect. closed.

13. followed by dunning  Arrangement of installment plan  SAP AG 1999 (C) SAP AG IUT110 60 .60 Returns: Business Scenario  Post request for energy consulting  Display account balance  Payment by check for account balance  The check was not covered: Return with charge  Dunning proposal for contract account.

61 Returns: Influencing Factors Customer Return reason creditworthiness and tolerance group Return category Returns Number of returns History Return amount  SAP AG 1999  Every return category is allocated to a return reason.  Maximum amount difference Maximum difference between the house bank returns amount and the original payment amount that is tolerated for automatic charges posting. Creditworthiness can also be maintained manually. Examples are check returns and bank returns.  Bank-specific returns reasons can be allocated to company-specific returns reasons. Return reasons can have the same category. The return category determines the accounts used (G/L accounts for returns charges and bank clearing account).13.  Creditworthiness is calculated via the number of business partner dunnings and returns dependent on the creditworthiness weighting according to the following formula: Creditworthiness = (number of dunnings + number of returns) * creditworthiness weighting. As long as the difference amount is within the maximum amount difference.  HistoryMaximum number of days that have passed since an event before the event can be included in the analysis of the returns history. (C) SAP AG IUT110 61 . it is interpreted as a charge by the system and posted accordingly. Manually maintained creditworthiness automatically overrides calculated creditworthiness.

the items due for dunning or the open items are not dunned when the dunning program is executed.  Recording a blocking reason for incoming/outgoing payments in the master record of Contract Accounts Receivable and Payable prevents debit memos/bank collections/payments from being initiated by the payment program.  The new due date for the receivable is calculated using the deferral days according to the following formula: New due date = document date or return + deferral days  Recording a payment block reason for open items means that the open items are blocked for automatic payment with the payment program.Items  SAP AG 1999  Pass on bank charges: Means that the bank passes on the returns charges to the business partner (accompanying contract account). these charges are paid by the utility company. If this is not the case. (C) SAP AG IUT110 62 .  By recording a dunning block reason in the master record of Contract Accounts Receivable and Payable or under open items.13.  Calculation of lot charge Means that the business partner has to pay a surcharge in addition to the bank charges.62 Returns: Activity Settings Correspondence Pass on charges Incoming with/without tax payment method Payment block Calculate lot charges Returns reasons Deferral days Post charges Return amount statistically Dunning block . The amount of the lot charge depends on the amount of the returns charge.Contract account .

 SAP AG 1999 (C) SAP AG IUT110 63 .63 Returns Lot: Processing Steps New Returns returns Create Close Post lot lot complete Post- Change processing  Returns lot processing contains the following steps:  Create  Change (optional)  Close (deletion and insertion of items is no longer allowed)  Post  Post-processing (for clarification and errors): Post-processing is necessary if postings could not be made.13.

 The document type. clearing reason. currency. (C) SAP AG IUT110 64 .  The last values entered (if available) are inserted automatically for the company code.13.64 Returns Lot: Create New Returns returns Create Close Post lot lot complete  A returns lot can be created:  Using a program (such as returns lot with DTAUS)  In dialog mode  The following must be specified:  Reconciliation key  Whether the amount contains charges  Whether the amount contains taxes  Posting type (taking back payment. and business area. new receivables)  SAP AG 1999  Default values on the header screen:  The current date is defined. and the selection categories are stored in Customizing.

you can branch to the detail screen of the selected item.  On the detail screen.65 Returns Entry New Returns returns Create Close Post lot lot complete  The essential entries are:  Amount  Returns reason  Payment document number  SAP AG 1999  Enter one line of data for each return during list entry. You can choose other line structures in Extras --> Screen variants  By pressing the Additional specifications key. if required. Variants of the line structure can be recorded in Customizing. (C) SAP AG IUT110 65 . you can enter any additional data necessary for payment allocation or for further clarification.13. You can enter additional data on the payment.

 SAP AG 1999 (C) SAP AG IUT110 66 .66 Returns Lot: Change New Returns returns Create Close Post lot lot complete Change  Items can be deleted and added if the returns lot is still open.  Data on items that have already been entered can also be corrected.  Interrupted entry of a returns lot can be resumed using this function.13.

 SAP AG 1999 (C) SAP AG IUT110 67 .  Corrections can still be made to returns lot items after closing.  Posting cannot begin until a lot is closed.67 Returns Lot: Close New Returns returns Create Close Post lot lot complete  Closing a returns lot means that adding or deleting items is no longer possible.13.

13.68 Returns Lot: Posting (1) New Returns returns Create Close Post lot lot complete  You can decide whether postings are to be managed:  In dialog mode  In a background process  For each return:  The payment document and cleared items are determined  The returns history is written  SAP AG 1999 (C) SAP AG IUT110 68 .

workflow  SAP AG 1999 (C) SAP AG IUT110 69 . correspondence.69 Returns Lot: Posting (2) New Returns returns Create Close Post lot lot complete  Reverse the clearing in the contract account  Generation of the returns document item  Triggering of postings:  Credit institute charges  Further debit charges to business partner  Own charges  Tax on charges  Setting payment and dunning blocks  Deferral of newly open items  Triggering of deferred payment.13.

13.70 Returns Lot: Post-processing New Returns returns Create Close Post lot lot complete Post- processing  Clarification of return use  Correction of returns item and restart posting for selected items  Manual posting and clearing for selected items  SAP AG 1999 (C) SAP AG IUT110 70 .

Number of returns . dependent on: including: .Amounts .Period of examination .Document numbers Returns history  SAP AG 1999 (C) SAP AG IUT110 71 .13.71 Returns History Record of business Basis for future handling management data for of the contract account returns processing.

72 Returns: Summary  The utility company can configure the many settings in such a way that detailed work is taken care of in the background.13.  Some of these activities are:  Reversing the clearing for the contract account  Passing on charges with/without tax  Deferral of receivables  Setting payment and dunning blocks  Triggering correspondence  SAP AG 1999 (C) SAP AG IUT110 72 .

73 Contract Accounts Receivable and Payable: Dunning  Overview  Documents  Account display  Payments  Returns  Dunning  Deferral and installment plan  SAP AG 1999 (C) SAP AG IUT110 73 .13.

74 Dunning: Objectives At the conclusion of this topic. you will be able to:  Describe the two-step dunning process  Display and explain the dunning history of a business partner/contract account  Name some of the influential factors in dunning  SAP AG 1999 (C) SAP AG IUT110 74 .13.

13. disconnection order)  This is a general procedure and can be adjusted to company requirements and individual customers or customer groups.  SAP AG 1999 (C) SAP AG IUT110 75 . dunning automatically:  Creates a customer letter  Triggers workflows (security requirement.75 Dunning: Introduction  Customer payments can only be reasonably controlled if they are supported by automatic processes. SAP Utilities  If payment is delayed.

followed by dunning  Arrangement of installment plan  SAP AG 1999 (C) SAP AG IUT110 76 .76 Dunning: Business Scenario  Post request for energy consulting  Display account balance  Payment by check for account balance  The check was not covered: Return with charge  Dunning proposal for contract account.13.

(C) SAP AG IUT110 77 . are carried out on the basis of the dunning proposal. in particular printing of the dunning notice.  In the second run. dunning activities.  A dunning proposal is created in the first run. Post account Generate Generate nation of interest dunning dunning Open new and proposal activities items dunning charges levels Dunning history  SAP AG 1999  The dunning program is divided into two runs.77 Dunning: Dunning Proposal and Dunning Activities Thresholds Charges schema Days in arrears Print forms Dunning interval Business partner Contract Determi.13.  The dunning proposal can be processed before you print the dunning notice.

 Indicator: Always dun dunning level. division.13. contract account. business area. or contract). Items due for dunning are dunned according to the settings in the dunning procedure and dunning data is stored in the dunning history. Items due for dunning are always grouped according to the following criteria in the dunning run: business partner. and dunning letter recipient. responsible company code. regardless of whether the days in arrears and the maximum / minimum amount have been reached. To create another dunning letter. (C) SAP AG IUT110 78 . dunning procedure. This means that a dunning letter is always triggered in this dunning level.  Another condition for creation of a dunning letter is that the dunning frequency has been reached. at least the specified number of days must have passed since the creation date of the last dunning letter. currency.  The dunning grouping key determines the criteria with which items due for dunning are additionally grouped during execution of a dunning run (for example. as soon as the dunning frequency has been reached. or whether the dunning level has been raised for any items of the same dunning grouping.  A dunning can only be triggered in a dunning level if the amount of all due items of a dunning grouping exceeds the maximum amount stored in the dunning level.78 Dunning: Influential Factors Dunning procedure Dunning grouping Minimum/maximum amounts Dunning process Creditworthiness Days in arrears Dunning frequency  SAP AG 1999  A dunning procedure can be allocated to a contract account or to individual line items in the document.  Days in arrears describes the minimum number of days in arrears that must elapse after the net due date of a receivable before a dunning letter can be created.

13. (C) SAP AG IUT110 79 .79 Dunning Proposal for a Business Partner Determine all business partner accounts Read the dunning history Calculate creditworthiness Generate a dunning proposal  The new dunning level is determined  Dunning information is not saved for items Write the dunning proposal in the dunning history  SAP AG 1999  Possible start parameters for a dunning proposal:  General selection criteria: Company code Business partner Contract account Net due date  Dynamic selection criteria (from the business partner item contract accounting document): Document number Business area Contract Division Document date Posting date Currency All other criteria from the document item can also be used.

80 Dunning: Factors That Can Be Influenced (Selection) Creditworthiness Dunning Levels weighting Dunning charges Print all items (Scale schema) Dunning process Interest Payment period Dunning activity: Customer letter Disconnection order Deactivate installment plan  SAP AG 1999  Different dunning levels can be created for each dunning procedure. only the items due for dunning are printed (items that have reached the number of days in arrears specified). (C) SAP AG IUT110 80 . Otherwise.  Payment period in days. This is calculated from the dunning issue date and used for the payment target for a dunning letter.13. and for currency-dependent minimum/maximum amounts. You can also record parameters at every dunning level for printing dunning letters. Dunning levels determine the dunning intervals.  Creditworthiness weighting is the factor used in dunning to calculate creditworthiness. the charges schema used for determining the dunning charges and the way in which interest is calculated and posted. Payment target = dunning issue date + payment period  The Print all items indicator means that all due items that meet the same criteria for the dunning grouping are printed on one dunning letter.

13.81 Dunning: Determination of Dunning Levels Where do the influential factors for dunning come from? Contract Open Dunning account items history Dunning procedure Due date Last dunning date Dunning grouping Amount Last dunning level New dunning levels  SAP AG 1999 (C) SAP AG IUT110 81 .

 More days have passed since the due date than the number recorded for the dunning frequency.  The highest dunning level of all items summarized in a dunning group determines which dunning activities are performed for the corresponding dunning group.  An item that is dunned more than once passes through the various dunning levels according to predefined rules.13.82 Dunning Levels  Items that have not yet been dunned have dunning level 0.  An open item receives the next highest dunning level if:  More than the recorded number of days in arrears have passed since the due date.  SAP AG 1999 (C) SAP AG IUT110 82 .

13.83 Printing of Dunning Notice for a Business Partner Write dunning level in the receivables items Determine and post dunning charges Determine and post interest Determine dunning activities  Print dunning letter  Inform various recipients (legal department)  Start workflow Update dunning history  SAP AG 1999 (C) SAP AG IUT110 83 .

. 2000 MS 4 150 UNI 4713 Sep.84 Dunning: Dunning History  Overview of all dunning levels for a business partner / contract account Dec. 01. 2001 1200 UNI 4711 Aug. 2001 800 UNI Identification Identification of of the the 4711 Aug. 15. 01. 16. 15. 16. 15. 01. 2000 MS 3 250 UNI Every Every item item relevant relevant to to 4713 Sep. 1996 DL 3 250 UNI . 2001 Aug. 2000 800 UNI Jan. 15. 2000 DL 4 200 UNI dunning run dunning run Jan. 2000 DL 3 250 UNI 4712 Aug. dunning dunning has has an an entry entry . 16.13. Sep. 2000 DL 4 150 UNI 4713 4711 Aug. 16.. 2000 DL 4 200 UNI 4712 Jan.. 2000UNI 4 200 DL 3 250 UNI 4712 Aug. 15... 30. 2001 DL 1 120 UNI ... 2001 MS 1 120 UNI  SAP AG 1999 (C) SAP AG IUT110 84 . 1997 DL 1 120 UNI 4729 Jan. 01. 01.. 2000 1500 UNIDL 4 150 UNI 4711 Aug. 1996 DL 4 200 UNI 4712 Aug. 15. 1999 DL 1 120 UNI . 2000 MS01. 01. 4729 Jan. 01. 1996 DL 4 150 UNI 4713 Sep. in in the the dunning dunning history history 4729 Jan. 4729 Jan. 01.

13.85 Dunning: Summary  Dunning in Contract Accounts Receivable and Payable provides flexible dunning that can be adjusted to meet the utility company's requirements.  Customer payments can be controlled efficiently. The following activities are supported:  Customer letter  Creation of disconnection orders  Charging fees and/or taxes  SAP AG 1999 (C) SAP AG IUT110 85 .

86 Contract Accounts Receivable and Payable: Deferral and Installment Plan  Overview  Documents  Account display  Payments  Returns  Dunning  Deferral and installment plan  SAP AG 1999 (C) SAP AG IUT110 86 .13.

you will be able to:  Defer items in contract accounts receivable and payable.87 Deferral and Installment Plan: Objectives At the conclusion of this topic.13.  SAP AG 1999 (C) SAP AG IUT110 87 .  Create an installment plan.

installment plans or deferrals can be arranged for one or more receivables in order to:  Accommodate the customer  Guarantee payment  SAP AG 1999 (C) SAP AG IUT110 88 .88 Deferral and Installment Plan: Introduction  Some customers are not able to keep up with payments to the utility company SAP Utilities  In this situation.13.

89 Deferral and Installment Plan: Business Scenario  Post request for energy consulting  Display account balance  Payment by check for account balance  The check was not covered: Return with charge  Dunning proposal for contract account. followed by dunning  Arrangement of installment plan  SAP AG 1999 (C) SAP AG IUT110 89 .13.

 SAP AG 1999 (C) SAP AG IUT110 90 .90 Deferral  A deferral is a document change.  Items are deferred by entering the date until which they are to be deferred in the "Deferral date" field.13.

13.91 Installment Plan: Characteristics  Any number of open items as the basis of aninstallment agreement  Interest calculation for installment plans  Installment plan charges  Letter to the customer  Change. add and delete individualinstallments  Deactivation of installment plans  SAP AG 1999 (C) SAP AG IUT110 91 .

13.92 Installment Plan Category Pre-definable installment plan categories simplify creation of new installment plans. Number of Installment installments interval Installment plan category Rounding Interval category amount  SAP AG 1999 (C) SAP AG IUT110 92 .

13.93 Installment Plan: Item Selection Selection of open items for installment plan Simplified selection Manual compilation from the list of open  All open items items  SAP AG 1999 (C) SAP AG IUT110 93 .

 Simple procedure for creating and managing installment plans. or any selection of open items.94 Deferral and Installment Plan: Unit Summary  In Contract Accounts Receivable and Payable.  SAP AG 1999 (C) SAP AG IUT110 94 .  Installment plan items are statistical document items that are saved in repetition groups.  Installment plan categories make it easier to create installment plans on the basis of an enterprise model. open items can be easily deferred by making a document change.  Either all open items. can be included.13.

You now have to post the corresponding receivable to the customer’s account. _____________________________________________________ 1-1-2 Using parameters (optional) Display the help information for the Company code field. From this help screen. 1-1 Posting receivables 1-1-1 Specify the menu path that you would use to post a document. take a look also at the technical information for the Company code field. Enter the following parameters in your user settings. you will be able to: • Manually post a document • Interpret the information contained in a FI-CA document and how to access this information You are an assistant in accounts receivable accounting in your company. What is the parameter for the Company code field? _____________________________________________________ 1-1-3 Using parameters (optional) You can simplify the posting of documents if you preassign user parameters to fields for which you (almost) always use the same values. (C) SAP AG IUT110 95 .95Contract Accounts Receivable and Payable Exercises Unit: Contract Accounts Receivable and Payable Topic: Manual document entry At the conclusion of these exercises.13. Your colleague has just completed an energy consultation.

1-1-4 Now post a receivable for today’s energy consultation. In doing so. to see which data the system determines automatically. try to make as few entries as possible. Parameters Value Meaning FWS UNI is automatically entered in the Currency field. enter a miscellaneous posting for the energy consultation. Use the following data: Data field Contents Document date Today’s date Is pre-filled Posting date Today’s date Is pre-filled Reconciliation key 01-yymmdd-## yymmdd = today’s date Currency User parameters or user entries Company code U300 User parameters or user entries Jurisdiction code Tax jurisdiction code used 1-1-5 Change to entry screen for document items. Ensure that you use capital letters. The content of the screen Post Document: Initial Screen must first be refreshed before your user profile can be entered automatically. postings Use F4 for help SubT Miscellaneous posting . Choose the Parameters tab. For your business partner. BUK U300 U300 is automatically entered in the Company code field. Data field Contents BusPartner TB130110## Misc. (C) SAP AG IUT110 96 .debit Use F4 for help Amount Do not save your entries 1-1-6 Clarify your receivable using the following text: “Energy consultation of <today’s date>”. Your user profile is located under System → User profile → Own data.

_____________________________________________________ 1-2-5 The reconciliation key can differ for each document item. SAP02. _____________________________________________________ 1-2-4 The document date and posting date always correspond to the entry date. __________________________________________________ 2. (using the Screen variant icon or the menu path Settings  Screen variant). __________________________________________________ 3. To add the text you must switch to another screen variant. (C) SAP AG IUT110 97 . _____________________________________________________ 1-2-2 Posting documents is the usual method for creating receivables in Contract Accounts Receivable and Payable. see solutions. ID 1-1-11 Name three specifications from the document or the document item that control the determination of account assignment in financial accounting. For further options. 1-1-9 Display the document item. 1-1-7 Post the document and note the document number. _____________________________________________________ 1-1-8 Display the document. 1. 1-1-10 What information does the general ledger provide? Data field Value Origin Company code G/L Account Act. _____________________________________________________ 1-2-3 A document contains all the information for posting in financial accounting. determ. __________________________________________________ Are there any other criteria for determination? 1-2 True or false? 1-2-1 A document is always assigned to just one contract account.

_____________________________________________________ (C) SAP AG IUT110 98 .

you will be able to display the exact item you want to display and in the way in which you want to view it. _____________________________________________________ 2-1-4 To display the items in a customer account in another line layout. how the lines are constructed. _____________________________________________________ 2-1-2 The line item display can be modified to display items other than those pre- configured in the standard settings. you would like to obtain a detailed picture of the recent transactions for each account. _____________________________________________________ 2-1-3 The list category determines the line layout of the item display.e. _____________________________________________________ (C) SAP AG IUT110 99 . i. you must return to the initial screen. Exercises Unit: Contract Accounts Receivable and Payable Topic: Display account balance At the conclusion of these exercises. • Provide information on the balance and development of a customer account • Provide information on the items of a customer account • Use the navigation options in the item display Two customers want to meet with you. 2-1 True or false? 2-1-1 The standard display of the items in a customer account shows all items that are posted to that account. Before you initiate the contact.e. i. you will be able to: • Handle the many options of the account display.

2-2 Line item display for a business partner 2-2-1 What is the current balance for business partner TB130110##? _____________________________________________________ 2-2-2 Which items comprise the balance? _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ 2-2-3 Have any payments already been made? _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ (C) SAP AG IUT110 100 .

_____________________________________________________ 2-4-5 Have any taxes been calculated for the energy consultation? _____________________________________________________ (C) SAP AG IUT110 101 . Tip: Choose the correct line layout variant. 2-4-2 Who posted the receivable? _____________________________________________________ 2-4-3 Which reconciliation key was used? _____________________________________________________ 2-4-4 Have any items been posted to the above document number for any other business partner? Tip: Use the Overview button. 2-3 Navigating the document display (optional) 2-3-1 Identify the receivable for the energy consultation for business partner TB130110##.

no more changes can be made to it. you will be able to: • Explain the processing steps of a payment lot • Post payments via a payment lot • Post payment at cash desk A customer comes in and would like to pay cash for an energy consultation. provided that you do not close the payment lot. _____________________________________________________ (C) SAP AG IUT110 102 . _____________________________________________________ 3-2-3 The procedures for payment lots and check lots are identical. 3-1 Payment Lot 3-1-1 Which steps must be carried out when processing a payment lot? _____________________________________________________ _____________________________________________________ _____________________________________________________ 3-2 True or false? 3-2-1 If you are interrupted while working on a payment lot. _____________________________________________________ 3-2-2 Once the payment lot is closed. Exercises Unit: Contract Accounts Receivable and Payable Topic: Payment run At the conclusion of these exercises. you can resume work on it at any time.

3-3-6 Check the status. 3-3-7 Display the postings you have just carried out in the account display for each business partner and note the effects of the posting. 3-3 Posting a payment lot 3-3-1 Create a payment lot (PL-yymmdd-##). 3-3-5 Post the payments. Use the Payment list hotspot. 3-3-3 Enter payments for three of your business partners: Amount Business partner TB130210## TB130220## 1200 TB130230## 3-3-4 Save your entries and close the payment lot. 3-3-2 Enter the search term (IUT110-##) and a bank clearing account. (C) SAP AG IUT110 103 .

make the following entries: Recon. To do this. key RB-yymmtdd-## Business partner TB130110## Amount Balance for TB130110## (C) SAP AG IUT110 104 . 3-4 Payment at cash desk 3-4-1 Display the open receivables for business partner TB130110##. 3-4-4 Post a payment for the amount of the open balance of business partner TB130110##. What is the open balance? _____________________________________________________ 3-4-2 Which items make up the total? 3-4-3 Switch to payment at cash desk.

create a second session to determine the required payment document number. which you now have to post. If necessary. _____________________________________________________ 4-1-4 Save the data and close the returns lot. 4-1-6 Check the status. 4-1-7 Switch to the account display and observe the changes. 4-1-2 Enter the search term (IUT110-##). Ensure that a “B” for “document” is entered in the selection type field. 4-2 Returns lot with charges (optional) 4-2-1 Repeat the steps of the previous task for a new returns lot (RN-yymmdd-##). 4-1-3 Enter a return for business partner TB130120##. generate a return for the payment entered for business partner TB130210## in exercise 3-3-3. (C) SAP AG IUT110 105 . you will be able to: • Post a return • Define the effects of returns on payments already made In accounts receivable accounting. Exercises Unit: Contract Accounts Receivable and Payable Topic: Returns At the conclusion of these exercises. Increase the return amount by 10 UNI. The fields Amounts contain bank charges and Calculate charges should be activated. Switch to enter items. 4-1-5 Post the returns lot. 4-1 Returns lot 4-1-1 Create a returns lot (RL-yymmdd-##). This time. some returns have just arrived in the mail from the bank.

Exercises Unit: Contract Accounts Receivable and Payable Topic: Dunning At the conclusion of these exercises. _____________________________________________________ 5-2 Dunning history 5-2-1 Display the dunning history for business partner TB130220##. 5-1 True or false? 5-1-1 The dunning process is carried out using the same procedure for all the company’s contract accounts . _____________________________________________________ 5-1-2 The days in arrears and the dunning frequency largely determine when a due open item can be dunned. you will be able to: • Display and explain the dunning history for a business partner/contract account. _____________________________________________________ (C) SAP AG IUT110 106 . • Differentiate between various influential factors for dunning and describe the resultant activities.

remember that the previous settings for the list type are still active. The business partner telephones again and would like to pay for the open items in installments. the statistical items must also be displayed. Display the customer account from the navigation area of the contract account. Use functions from the Customer Interaction Center (CIC). 6-1 Deferral 6-1-1 Defer the open receivable of business partner TB130130## until the last day of the month. Exercises Unit: Contract Accounts Receivable and Payable Topic: Deferral and installment plan At the conclusion of these exercises. When you display the customer account from Front Office. For this reason. 6-2-2 Check that the instalment plan has been created in the account display. you have to first defer the receivable and then create the installment plan. However. you will be able to: • Defer the posting of a contract account • Create an installment plan A business partner telephones and asks for a deferral of an open item. to display the installment plan. 6-1-2 Display the changes in the corresponding document resulting from the deferral. (C) SAP AG IUT110 107 . 6-2 Creation of an installment plan 6-2-1 Create an installment plan with five installments at intervals of two weeks and a rounding amount of 10 for all open receivables for business partner TB130130##.

5. Your settings have now been added to the Currency and Company code fields. From this help screen.13. Save your entries by choosing Save or F11. Enter the following parameters in your user settings. Enter the values from the table. 4.96Contract Accounts Receivable and Payable Solutions Unit: Contract Accounts Receivable and Payable Topic: Manual document entry 1-1 Posting receivables 1-1-1 Specify the menu path that you would use to post a document. If you are already in the screen Post Document: Initial Screen. Place the cursor in the Company code field and choose Help. To do this. Utilities industry → Contract Accounts Receivable and Payable → Document → Post 2. you will see the value BUK. In the Parameter ID field. 4. take a look also at the technical information for the Company code field. press F1 or the button with the yellow question mark. Choose the Parameters tab page. (C) SAP AG IUT110 108 . Utilities industry → Contract Accounts Receivable and Payable → Document → Post 1-1-2 Using parameters (optional) Display the help information for the Company code field. you must update its contents so that the user settings can be entered automatically. confirm this using Yes and start the transaction again immediately using Document Post. Choose Technical info. Leave the screen using Cancel or F12. System → User profile → Own data. What is the parameter for the Company code field? 1. 1. 3. 2. 3. 1-1-3 Using parameters (optional) You can simplify the posting of documents if you preassign user parameters to fields for which you (almost) always use the same values.

. 1. postings Use F4 for help SubT Miscellaneous posting . Or change to the detail display for your business partner (for example. Enter the following values: Data field Contents Note BusPartner TB130110## Main Misc. enter a miscellaneous posting for the energy consultation. Choose the screen variant SAP02 and enter the text in the text field (use the screen variant icon or the menu path Settings → Screen variant. by double- clicking on the current item in the list) and enter the text under Other data. try to make as few entries as possible. In the Post Document: Initial Screen. to see which data the system determines automatically. Utilities industry → Contract Accounts Receivable and Payable → Document → Post Use the following data: Data field Contents Note Document date Today’s date Is pre-filled Posting date Today’s date Is pre-filled Reconciliation key 01-yymmdd-## yymmdd = today’s date Currency UNI User parameters or user entries Company code U300 User parameters or user entries 1-1-5 Change to entry screen for document items. Do not save your entries 1-1-6 Clarify your receivable using the following text: “Energy consultation of <today’s date>”.debit Use F4 for help Amount 116 3. press Enter or the green checkmark or the button BP item (Business partner item list). 1-1-4 Now post a receivable for today’s energy consultation. In doing so. For your business partner. To enter text . Parameters Value Meaning FWS UNI UNI is automatically entered in the Currency field. BUK U300 U300 is automatically entered in the Company code field. (C) SAP AG IUT110 109 . 2.

The document number is pre-filled. Another possible solution: In the screen Display Document: Initial Screen. Choose BP item (Business partner item list). Enter the text in the text field. To post the document. 1. Change to Document Change via the menu. Company code in the document item 2. Then double-click on the summary of business partner items. 1. Sub-transaction in the document item Other criteria for determination are the account determination ID and the division. ID 01 Contract account 1-1-11 Name three specifications from the document or the document item that control the determination of account assignment in financial accounting. 3. 2. you must choose Post (CTRL S). The document number is displayed in the message line after posting. determ. choose BP item (Business partner item list) to display the document items. or select the item with the cursor and use Edit → Choose (F2) from the menu to display the business partner item. Choose the screen variant SAP02 4. 1-1-8 Display the document. If you have already saved the document. A document can have more than one document item. 2. each of which can be assigned to another contract account or business partner. From the Display Document: Initial Screen. Utilities Industry → Contract Accounts Receivable and Payable → Document → Display 1-1-9 Display the document item. 1. 1-1-7 Post the document and note the document number. 1-1-10 What information does the general ledger provide? Data field Value Origin Company code U300 Entered during “document posting” G/L Account 140520 Account determination Act. Main transaction in the document item 3. (C) SAP AG IUT110 110 . False. 1-2 True or false? 1-2-1 A document is always assigned to just one contract account. choose Enter or the green checkmark.

These three dates may be different. 1-2-2 Posting documents is the usual method for creating receivables in Contract Accounts Receivable and Payable. (C) SAP AG IUT110 111 . True. 1-2-3 A document contains all the information for posting in financial accounting. False. 1-2-5 The reconciliation key can differ for each document item. The usual method of creating receivables is by invoicing. False. It is possible. that a document is grouped together with other documents (via the reconciliation key). but each individual document contains information for posting and offsetting in financial accounting. For each document there is only one reconciliation key. False. 1-2-4 The document date and posting date always correspond to the entry date.

you can use the blue arrows (provided you have activated them in your personal settings for account balance display). i. False. 2-1-4 To display the items in a customer account in another line layout. Alternatively.e. False. you must return to the initial screen. 2-1-2 The line item display can be modified to display items other than those pre- configured in the standard settings. You can change the line layout in the item display using the Line layout (Shift + F4) pushbutton or via Settings → Line layout. Solutions Unit: Contract Accounts Receivable and Payable Topic: Display account balance 2-1 True or false? 2-1-1 The standard display of the items in a customer account shows all items that are posted to that account. (C) SAP AG IUT110 112 . you can double-click an item to display a more detailed line layout variant. The list category determines which items are displayed in the lines. True. 2-1-3 The list category determines the line layout of the item display. You define your own line item display by choosing Settings → Display/ Change (F6). False – the standard display shows all open non-statistical items. how the lines are constructed. If a totals variant is active.

Now all payments made are displayed. Choose the Totals hotspot. directly choose the Receivables hotspot. Utilities Industry → Contract Accounts Receivable and Payable → Account → Account Balance 2. Use Back (F3) to return to the screen Account Display: Initial Screen. (C) SAP AG IUT110 113 . 4. 2. 2-2 Line item display for a business partner 2-2-1 What is the current balance for business partner TB130110##? 1. Alternatively. 3. Choose either a List category which displays more than only the open items (using F4 help. field. Return to the account display. 2-2-3 Have any payments already been made? 1. Press the green checkmark (ENTER).or on the total line. Select the Cleared items field and choose ENTER (green checkmark). 3. The List category field is in standard mode and is empty and Standard line layout – acc display is displayed in the Line layout field. 2-2-2 Which items comprise the balance? Double-click on the Receivables line. for example List category All items) or press the Detail button in the List type subscreen. Enter business partner TB130110## in the Business partn. 5. The balance appears in the Total field.to return to the display of the receivables that are still open.

1. 2. Therefore. 2. Press the button Overview F7 or use Goto → Overview F7 from the menu. 2-3 Navigating the document display (optional) 2-3-1 Identify the receivable for the energy consultation for business partner TB130110##. this document only contains items for one business partner. Choose the line layout variant TBT – Account display with document text by double-clicking on it. Utilities Industry → Contract Accounts Receivable and Payable → Account → Account Balance 2. The number is one. 2-3-4 Have any items been posted to the above document number for any other business partner? 1. Choose Document header CTRL+F4. 3. 3. You are now in the screen Display Document: Item. 2-3-5 Have any taxes been calculated for the energy consultation? 1. 2-3-2 Who posted the receivable? 1. 6. 3. (C) SAP AG IUT110 114 . Tip: Choose the correct line layout variant. Choose the Taxes (CTRL+F6). Now you can see which of the open receivables is the one for the energy consultation (if you happened to have entered the text “Energy consultation” in the corresponding exercise). field. Enter business partner TB130110## in the Business partn. 2-3-3 Which reconciliation key was used? Contained in the Recon. 2. Press the button Line layout (Shift+F4). key field in the document header. Press the green checkmark (ENTER). 4. You can find the number of document items in the Summarized items subscreen. Preceding the Business partner items header is the number of business partners (<x> Business partner items). You can read the user key of the creator from the Created by field. Double-click on the receivable. 5. Here you can view the details for the tax item.

2. 3-3 Posting a payment lot 3-3-1 Create a payment lot (PL-yymmdd-##). 1. The Change step exists for this purpose. Enter UNI in the Currency field. Post 3-2 True or false? 3-2-1 If you are interrupted while working on a payment lot. 1. Search term: IUT110-##. 3-2-3 The procedures for payment lots and check lots are identical. The only difference is that a different screen variant must be chosen for the line layout. 3-3-3 Enter payments for three of your business partners: (C) SAP AG IUT110 115 . no more changes can be made to it. False. 3. True. Create 2. but this does not happen in the screen variant for the payment lot. While it is true that no new items can be added and items cannot be deleted. Utilities industry → Contract accounts receivable and payable → Payments → Payment lot. Close 3. Choose an account enter today’s date as the value date. existing items can be corrected. provided that you do not close the payment lot. Choose Create (F5). Enter PL-yymmdd-## in the Lot field. 3-2-2 Once the payment lot is closed. 3-3-2 Enter the search term (IUT110-##) and a bank clearing account. 2. as a check number must be entered for a check. Bank clearing account: selection via the possible entries for Bank clrg acct (F4 help). Solutions Unit: Contract Accounts Receivable and Payable Topic: Payment run 3-1 Payment Lot 3-1-1 Which steps must be carried out when processing a payment lot? 1. True. you can resume work on it at any time.

To enter the item. 3-3-5 Post the payments. field. 3-3-7 Display the postings you have just carried out in the account display for each business partner and note the effects of the posting. To do this. Choose Close and confirm the action. 3. Amount Business partner 500 TB130210## 800 TB130220## 1200 TB130230## 3-3-4 Save your entries and close the payment lot. The balance of open items is located in the Total field. 4. Choose the Totals hotspot. Use the skills you learned in the FI-CA2 unit “Display Account Balance”. press the New items F5 pushbutton. You now see the Payment lot Create: Default Entries and Status screen . Ensure that the screen variant SAP01 with the description Standard (one line) is activated. Tip: Use the Payment list hotspot. 2. Choose Back (F3) again. 3-3-6 Check the status. Press the green checkmark (ENTER). The status should read “Postings made”. Choose Save (CTRL+S). choose Post. 4. 2. Utilities Industry → Contract Accounts Receivable and Payable → Account → Account Balance 2. Enter business partner TB130110## in the Business partn. What is the open balance? 1. 3-4 Payment at cash desk 3-4-1 Display the open receivables for business partner TB130110##. Choose Back (F3). 1. 3. Observe the change in status during the following activities. Choose Start Online. Press the green checkmark (Continue Enter). 1. 1. 3. You have returned to the Payment lot: Initial Screen. 3-4-2 Which items make up the total? (C) SAP AG IUT110 116 . 2.

(C) SAP AG IUT110 117 . 1.00 UNI Miscellaneous posting: Hire of energy measuring device 116. Amount Item type 20.00 UNI Miscellaneous posting: Energy consultation of <dd/mm/yy> (from the “Post document” exercise). Ensure that you have chose the line layout variant TBT (Account display with document text) to display the document text column. 2. Utilities Industry → Contract Accounts Receivable and Payable → Payments → Cash Account → Payment at Cash Desk. 3-4-3 Switch to payment at cash desk. Double-click on the Receivables field in the total display.

3. Ensure that the field Incoming cash paymt is selected. (C) SAP AG IUT110 118 . key RB-yymmdd-## (Under Further posting specs) Business partner TB130110## Amount Balance for TB130110## 1. 4. 2. make the following entries: Recon. Select any output device (F4 help) and choose Enter. 3-4-4 Post a payment for the amount of the open balance of business partner TB130110##. Choose Print receipt. If you have chosen Post item online. To do this. use the save button to post the item (ctrl + S). choose Post item or Post item online. To post the payment.

4-1-3 Enter a return for business partner TB130120##. 1. Choose the green checkmark (ENTER). 1. Choose return reason 01 (Bank account overdraft). Utilities Industry → Contract Accounts Receivable and Payable → Payments → Returns Lot. field. Enter RL-yymmdd-## in the Returns lot field. 5. 4. 2. 1. If necessary. 6. Search term: IUT110-##. Switch to enter items. 2. create a second session to determine the required payment document number. The selection type should be set to B. Choose New items. if these were not already chosen. Enter business partner TB130120## in the Business partn. 8. The fields Amounts contain bank charges and Calculate charges should be activated. 7. Ensure that a “B” for “document” is entered in the selection type field. 3. In the screen Returns: Enter/Maintain Lot RL-yymmdd-##. 4-1-2 Enter the search term (IUT110-##). Note the payment document number. 3. (C) SAP AG IUT110 119 . Choose the standard list category All items and line layout Account display with text (IUT110). Close the second session: System  End session. System → Create session 2. Utilities Industry → Contract Accounts Receivable and Payable → Account → Account Balance 3. Press the button Create (F5). Solutions Unit: Contract Accounts Receivable and Payable Topic: Returns 4-1 Returns lot 4-1-1 Create a returns lot (RL-yymmdd-##). enter the payment document number in the SelectionValue field. Choose the above settings and save them using Save (CTRL+S).

3. 3. Choose Enter. The status should read “Postings made”. To do this. Choose OK. (C) SAP AG IUT110 120 . Choose Back (F3). You now see the Returns: Specifications and Status: Edit screen. you will notice that the bank charges contained in the return amount were posted together as one item with the utility company’s charges. This time. The amount and the return reason is determined automatically. 4-1-6 Check the status. You are now looking at the Returns: Request Screen. 4-1-4 Save the data and close the returns lot. 2. 1. 9. 4-2 Returns lot with charges (optional) 4-2-1 Repeat the steps of the previous task for a new returns lot (RN-yymmdd-##). 2. Solution as for 4-1. In the account display. 1. Choose Back (F3). Increase the return amount by 10 UNI. choose Post. 4-1-7 Switch to the account display and observe the changes. 4-1-5 Post the returns lot. 4. Choose Save (CTRL+S). generate a return for the payment entered for business partner TB130210## in exercise 3-3-3. Use the Payment list hotspot. Select Start online and Immediately. Choose Close and confirm the action.

1. The dunning procedure can be defined in the contract account and can be applied even to individual items. (C) SAP AG IUT110 121 . False. The days in arrears determine the minimum number of days that must have passed since the due date before dunning can occur. 2. Solutions Unit: Contract Accounts Receivable and Payable Topic: Dunning 5-1 True or false? 5-1-1 The dunning process is carried out using the same procedure for all the company’s contract accounts . 5-1-2 The days in arrears and the dunning frequency largely determine when a due open item can be dunned. 4. The dunning frequency defines the number of days that must have passed since the issue date of the dunning letter before another dunning letter can be sent. 3. Utilities Industry → Contract Accounts Receivable and Payable → Account → Other Information → Dunning History. Enter TB130220## in the Business partner field. 5-2 Dunning history 5-2-1 Display the dunning history for business partner TB130220##. Press Execute F8. The dunning history is displayed. True.

Select the contract account. 6. 3. Display the customer account from the navigation area of the contract account. 3. Double-clicking on the open receivables brings you to the detail display of the document. 2. enter the last date of the month. Solutions Unit: Contract Accounts Receivable and Payable Topic: Deferral and installment plan 6-1 Deferral 6-1-1 Defer the open receivable of business partner TB130130## until the last day of the month. Save the contact (Save or CTRL + S). Then click the right mouse button and choose the customer account. Select the contract account. Choose Enter to display the business partner’s data. Then click the right mouse button and choose Post deferral. 7. 5. Enter TB130130## in the field Business Partner (in the search criteria of the data finder). Return to the CIC by choosing Back (F3) twice. Then choose Confirm partner. 6-2 Creation of an installment plan 6-2-1 Create an installment plan with five installments at intervals of two weeks and a rounding amount of 10 for all open receivables for business partner TB130130##. 6-1-2 Display the changes in the corresponding document resulting from the deferral. Enter text relating to the customer contact. (C) SAP AG IUT110 122 . In the Deferral field. 4. 1. The deferral date you have just entered is now visible in the Deferral to field of the Basic data subscreen. Choose ENTER. 1. The business partner environment is displayed in the navigation area. Utilities Industry → Customer Service → Front Office/Customer Interaction → Customer Interaction Center. 2.

7. When you display the customer account from the CIC. to display the installment plan. Enter today’s date in the Start date field. Then click the right mouse button and choose Create Installment plan. Save the contact by pressing Save (Ctrl+S). the statistical items must also be displayed. 6. 1. Then choose Confirm partner. field. Utilities Industry  Customer Service  Front Office/Customer Interaction Center  Customer Interaction Center 2. Then click the right mouse button and choose the customer account. Enter 2 in the Interval cat. 13. Select the contract account. 4. 14. interval field. Choose Installment plan or ENTER. Choose Enter to display the business partner’s data. Choose Save (CTRL+S). The business partner environment is displayed in the navigation area. 6-2-2 Check that the instalment plan has been created in the account display. 3. Select the contract account. Choose all open items by pressing the Select all (Shift+F7)button. Check the number of installments and the intervals between them. 10. 12. However. the statistical items display is not activated under list type. You can choose another list type on the initial screen for account balance display. Enter 5 in the No. Enter TB130130## in the field Business partner (in the search criteria). Enter 2 in the Instlm. 9. remember that the previous settings for the list type are still active. Enter 10 in the Rounding amount field. (C) SAP AG IUT110 123 . If no items are selected. of instmts field. 5. 8. 11. Enter a text relating to the customer contact.

Settlement takes into account container and premise data. Logistics and billing-related business processes are supported here.  The container forms the basis for the settlement.14 Waste Industry Contents:  Solution map and integration model for the waste industry  Areas involved and their focus of activities  Technical master data for the waste industry  Functions that have been implemented  Planned functions  SAP AG 1999  The Waste Management component allows you to map and settle periodic and aperiodic waste disposal services for residential and non-residential customers. This is usually emptied periodically by a waste disposal company. (C) SAP AG IUT110 1 .

 SAP AG 1999 (C) SAP AG IUT110 2 .14. you will be able to:  Describe terms and contexts that relate to waste in the mySAP Waste Industry.2 Waste Industry: Unit Objectives At the conclusion of this unit.

14.3 Solution Map and Integration Model for the Waste Industry Enterprise Management Business Business Strategic StrategicEnterprise Enterprise Financial Financial Regulatory Regulatory Intelligence Intelligence&& Controlling Controlling Management Management Accounting Accounting Reporting Reporting Data DataWarehousing Warehousing Customer Relationship Management Customer Customer Market MarketResearch Research Product Product Marketing Marketing Sales Sales Sales Sales Service Service &&Analysis Analysis Marketing Marketing Management Management Management Management Channels Channels Installation Management Technology Technology&& Plant PlantMaintenance Maintenance&& Decommissioning Industrial IndustrialHygiene Hygiene Installation Decommissioning InstallationConstruction Construction Service ServiceManagement Management And AndSafety Safety Management of Waste Master Data Waste-Specific Waste-Specific Inventory Inventory&& Maintenance Maintenance&& RBS RBSSites Sites&& Master MasterData Data Warehouse WarehouseManagement Management Plant PlantMaintenance Maintenance Geo GeoServer Server Waste Disposal Services Container Container Bulk Bulk Residential Residential Cleaning CleaningService Service&& Special Service Special Service Waste Waste Waste Waste Winter WinterMaintenance Maintenance Services Services Waste-Specific Cross Applications Weight WeightData DataSystem System Disposal DisposalRegulations Regulations Vehicle Vehicle&&Resource Resource Routing Routing &&Daily DailyBusiness Business Confirmation Confirmation &&Dangerous DangerousGoods Goods Planning Planning Statistics Statistics Management Management Revenue Management Guarantor Guarantor Accounts AccountsReceivable Receivable Billing Billing Billing Billing Invoicing Invoicing Billing Billing &&Payable Payable External ExternalServices Services Business Support Human HumanResource Resource Fixed FixedAsset Asset Real RealEstate Estate Procurement Procurement Treasury Treasury Management Management Management Management Management Management  SAP AG 1999 (C) SAP AG IUT110 3 .

FI/CA and so on) and to external systems (such as route planning and geographical information systems) are established by the mySAP Waste Industry solution.4 Integration Model for mySAP Waste Industry Regional structure Profitability analysis Contract/ Billing Contract SAP Invoicing Accounts Front Business Contract/ Receivable Office Partner Billing & Payable Container Vehicle Driver Route Planning GIS Weighting data IS IS SD SD FI FI MM/ MM/ CO- CO. (C) SAP AG IUT110 4 . HR BC BC CSP Waste Waste CS CS CA CA PM PM PA PA  SAP AG 1999  The integration model shows which connections to other SAP modules (such as SD/SM.14.  The Billing Engine (IS-U billing master data) is used for regular services and SD billing functions are used for unusual services.

and safety.Waste EH&S WA . Health & Safety The EH&S component covers the areas environment.5 mySAP Waste Industry : Involved Areas Industry Solution . health. The Waste Management component of EH&S is planned for Release 2.Waste Management  SAP AG 1999  EH&S Environment.14.7 of EH&S. (C) SAP AG IUT110 5 .

6 Focus Areas of IS-Waste . and weighing data systems.  Invoicing and accounting  SAP AG 1999 (C) SAP AG IUT110 6 . enter completion confirmations.  Vehicle and resource planning SAP IS-W/BIL/ICA  Flat-rate and service-related billing Special billing systems that have been designed to cope with mass data. management of bulk waste and so on.  Preconfigured business processes: Create and display orders.Waste Industry SAP IS-W/LOG  Management of specific master data for waste disposal and cleaning services/winter maintenance.  Generic interfaces to the route planning system.14. geographical information systems.

Recycling and Disposal Act. Code of Federal Regulations (40CFR) (C) SAP AG IUT110 7 .7 Focus Areas of EH&S WA .14.Waste Management  Disposal of waste that requires monitoring or special monitoring in accordance with international statutory regulations. and light commercial waste  Dispatch note  Internal/external waste disposal  Administration of waste approval  Creation of waste balances and waste management concepts  Management of master data  SAP AG 1999  Waste disposal is performed in accordance with international statutory regulations:  Germany: Waste Avoidance.  USA: United States Code.

such as checking the licence for disposal of hazardous waste (C) SAP AG IUT110 8 .  Master data that has been recorded in the vendor master record is used to perform legal checks on the waste disposal company.14.8 The Waste Disposal Cycle with EH&S R/3 mail Enter disposal purchase requisition document EH&S waste generation Settlement. Regist- assessment ration Determine WD channels Check bill Inquiry/offer info record waste approval Waste disposal Choose disposer/transporter Delivery/disposal Standard source Print delivery note determination Print disposal document EH&S waste generation Outline contract Purchase order/ CO transfer Process monitoring Disposal processing scheduling (returns)delivery  SAP AG 1999 Assigned WE  Components of mySAP Waste Industry including integration of EH&S are used to represent the waste disposal cycle in individual sub-process steps from waste registration to settlement.

loc.9 Data Model – Container Service (Simplified) Business Regional partner structure Customer Waste disposal Contract object account Func. SD / PM/ FI-CA CA Waste CS MM  SAP AG 1999 (C) SAP AG IUT110 9 . loc.14. Contract Premise Object allocation Container Container Container category location Material Equipment Func. Service Route frequency IS.

It is managed as a functional location in the Plant Maintenance (PM) component. for which a utility serviceis provided. such as an apartment or factory for which a waste disposal service is to be provided. It is managed as a functional location in the Plant Maintenance (PM) component.  Premise A premise is a spatially enclosed unit where waste is generated.10 Technical Master Data I  Waste disposal object A waste disposal object is usually a building.14. but can also be a piece of property or other facility.  SAP AG 1999 (C) SAP AG IUT110 10 . The disposal object comprises one or more premises.  Container location The container location is the place in a disposal object in which the containers are installed.

The container or cleaning object is also allocated to a contract and a premise in the object allocation. It is managed as a material with a material number in the Materials Management (MM) component. It is managed as a piece of equipment with a serial number in the Plant Maintenance (PM) component.  Container category The container category groups together containers with the same characteristics (data).  SAP AG 1999 (C) SAP AG IUT110 11 .14.11 Technical Master Data II  Object allocation The billing conditions for a container or cleaning object are maintained in the object allocation.  Container The container is an item which has to be emptied.

 Container portions A container can be assigned to several customers or premises using container portions.14. such as number of persons/ m² per premise (household).12 Technical Master Data III  Service frequency Frequency with which a service is performed for a container or cleaning object. The customer is billed for their portion of the container using various criteria. The service frequency can be maintained for each container in an IS-Waste contract or SD contract or for each cleaning object or sub-object in an IS-Waste contract.  SAP AG 1999 (C) SAP AG IUT110 12 .  Route A route defines a regional combination for several containers or cleaning objects for which a service is to be performed.

maintenance. container volume. order. containers for customers Maintenance/ Check Planning. completion confirmations Classification system  SAP AG 1999 (C) SAP AG IUT110 13 . Purchase order. cleaning Container service Organization. Warehouse Management container for route. goods receipt loading information.13 Container Management: Integration Container management Logistics Container category Material Container Equipment Technical data Purchasing Container size.14. dimensions Inventory management Allocation Container category for vehicle type.

facility management.14. This planning can also be performed manually.SD/CS Route planning system Driver data Vehicle data Determination Determination of of Creation and possible possible routes routes maintenance of Container data (sorted/unsorted) (sorted/unsorted) a periodic or aperiodic service Service data Sorting Sorting an an Allocation data existing existing route route Allocation of a route according to Possible route All All routes routes service frequency fully fully optimized optimized Optimized route  SAP AG 1999  Initial situation: The geographical coordinates (x/y coordinates. (C) SAP AG IUT110 14 . A sequence number within a route can also be loaded into the system. time zone) of any object in the SAP system are determined. validated and recorded in the SAP system using a geographical coordination tool. A BAPI is then used to load the route determined by the route planning system with a specific service date into the SAP System. service dates. Planning or optimization of the route occurs in this system. Both internal and external applications can then access this data. container. Examples of this include route planning.14 Interface to Route Planning System IS-W/CCS . various allocations) to an external route planning system.  A generic interface is used to transfer all data that has been maintained in the SAP System (such as driver. container address. resource planning. vehicle.

14.  Waste disposal orders are generated on the basis of the dates in the service frequency. (C) SAP AG IUT110 15 . You can delete waste disposal orders following creation.  Once the waste disposal service has been performed.15 Waste Disposal Orders Display/ Change In Create Service frequency paper form invoice t pu ut O Create waste Conf- irmation disposal order Ou tpu Delete t In file form Route  SAP AG 1999 You can display and change the waste disposal orders that have been created.  You may want to change the date on which the service is to be performed or the standard personnel who have been maintained for a route and who are to perform the service. A waste disposal order is subdivided into one header record at route level and 1 to n object records at container level. You can also delete the service for a particular container/customer within the route. the individual who has performed it confirms that it has taken place and billing and invoicing are then performed on the basis of this confirmation. You can use a selection parameter to control whether orders that have been confirmed are to be deleted.

14. the number (and serial number if required) of the containers that have been delivered or removed and the time required to do so is confirmed.16 Process: Container Delivery / Removal  The CIC is used to notify the customer by telephone of container delivery/removal.  A service order (PM-CS) is generated automatically in the background.  Once the container delivery/removal has been performed.  SAP AG 1999 (C) SAP AG IUT110 16 .  The customer is billed and invoiced on the basis of this confirmation.  An order for delivery/removal of one or more containers is created.

average consumption and load weight  SAP AG 1999 (C) SAP AG IUT110 17 . such as the maintenance cycle.14.17 Fleet Management  A vehicle can be created as a piece of equipment of a particular equipment category and vehicle type  Fleet Management allows you to manage fleets of vehicles  Allocation of goods to a vehicle  Form transport units from several compartments  It is possible to maintain vehicle-specific data.

18 Implemented Functions I  Container management  Serialization  Container portions  Business to customer scenario  Waste disposal-specific role  Route  Difficulties  Premise  SAP AG 1999 (C) SAP AG IUT110 18 .14.

19 Implemented Functions II  Service types  Container delivery  Unique services  Cleaning services and winter maintenance  Bulk waste  Vehicle and resource planning  Container services  SAP AG 1999 (C) SAP AG IUT110 19 .14.

20 Planned Functions for mySAP Utilities 4.14.64  Service-related billing  Customer-specific prices  Integration of EH&S  Integration of IS-Waste with SAP CRM and SAP BW  SAP AG 1999 (C) SAP AG IUT110 20 .

 SAP AG 1999 (C) SAP AG IUT110 21 .21 Waste Industry: Summary You are now able to:  Describe the special terms and contexts and individual functions of waste management in IS-U/CCS.14.