iut110_en
TRANSCRIPT
IUT110 Introduction to the IS-U/CCS SystemIUT110
Release 463 25.09.2003
IUT110 Introduction to the IS-U/CCS System..............................................................................................................0-1
Copyright....................................................................................................................................................................0-2
SAP Utilities (IS-U/CCS).......................................................................................................................................0-3
Course Prerequisites...............................................................................................................................................0-4
Target Group..........................................................................................................................................................0-5
Course Goals..........................................................................................................................................................0-6
Course Objectives...................................................................................................................................................0-7
Course Content.......................................................................................................................................................0-8
IS-U/CCS: Overview..................................................................................................................................................1-1
IS-U/CCS Overview: Unit Objectives...................................................................................................................1-2
IS-U Overview: Business Scenario........................................................................................................................1-3
mySAP.com: Overview..........................................................................................................................................1-4
Workplace Internet Business Framework..............................................................................................................1-5
mySAP Utilities: The Comprehensive Solution.....................................................................................................1-6
Customer Relationship Management (CRM).........................................................................................................1-7
Business Information Warehouse (BW).................................................................................................................1-8
Functional Scope of the IS-U System....................................................................................................................1-9
Integrated and Open System Landscape...............................................................................................................1-10
IS-U/CCS Business Processes..............................................................................................................................1-11
Synchronized Business Objects............................................................................................................................1-12
Marketing and Sales Process................................................................................................................................1-13
System Infrastructure CRM, BW and mySAP Utilities......................................................................................1-14
IS-U/CCS - Integration Model.............................................................................................................................1-15
The Strengths of mySAP Utilities........................................................................................................................1-16
Solutions for the New Industry Market Model....................................................................................................1-17
Deregulated Market: Business Perspective..........................................................................................................1-18
Sales and Marketing in IS-U/CCS (1)..................................................................................................................1-19
Sales Processing...................................................................................................................................................1-20
Sales and Marketing in IS-U/CCS (2)..................................................................................................................1-21
Internet Self Services: Start Page.........................................................................................................................1-22
What is Energy Data Management?.....................................................................................................................1-23
Energy Data Management 1.................................................................................................................................1-24
Energy Data Management 2.................................................................................................................................1-25
IS-U Overview: Unit Summary............................................................................................................................1-26
CIC.............................................................................................................................................................................2-1
CIC: Unit Objectives..............................................................................................................................................2-2
CIC: Business Scenario..........................................................................................................................................2-3
The IS-U House......................................................................................................................................................2-4
Various Business Partners......................................................................................................................................2-5
Roles of the Business Partner.................................................................................................................................2-6
Business Partner Data.............................................................................................................................................2-7
Contract Account Data...........................................................................................................................................2-8
Collective Bills.......................................................................................................................................................2-9
Contract Data........................................................................................................................................................2-10
Connection Object Data.......................................................................................................................................2-11
Premise Data.........................................................................................................................................................2-12
Installation Data....................................................................................................................................................2-13
Point of Delivery Data..........................................................................................................................................2-14
Business Objects in IS-U/CCS.............................................................................................................................2-15
What Is a Customer Interaction Center?..............................................................................................................2-16
Customer Interaction Center: Requirements........................................................................................................2-17
Integration with External Communication Systems.............................................................................................2-18
The IS-U/CCS Customer Interaction Center........................................................................................................2-19
Customer Interaction Center (L-Shaped).............................................................................................................2-20
Workflow Inbox...................................................................................................................................................2-21
E-Mail and Fax in the Workflow Inbox...............................................................................................................2-22
Typical Uses of the CIC: Identification................................................................................................................2-23
Typical Uses of the CIC: Information..................................................................................................................2-24
Typical Uses of the CIC: Front Office Process....................................................................................................2-25
Front Office Processes..........................................................................................................................................2-26
Typical Uses of the CIC: Workflow.....................................................................................................................2-27
Using R/3 Workflow: Changing a Rate (Example)..............................................................................................2-28
Typical Uses of the CIC: Customer Contact........................................................................................................2-29
Contact Management in Customer Service..........................................................................................................2-30
Customer Contact Data.........................................................................................................................................2-31
CIC: Unit Summary..............................................................................................................................................2-32
Customer Interaction Center Exercises................................................................................................................2-33
Customer Interaction Center (CIC) Solutions......................................................................................................2-46
Move-In/Out...............................................................................................................................................................3-1
Move-In/Out: Unit Objectives................................................................................................................................3-2
Move In/Out: Business Scenario............................................................................................................................3-3
Move-In Definition.................................................................................................................................................3-4
Move-In: Prerequisites...........................................................................................................................................3-5
Move-In: Business Master Data.............................................................................................................................3-6
The Move-In Process..............................................................................................................................................3-7
Move-In: Options for Processing...........................................................................................................................3-8
Move-In: The IS-U House......................................................................................................................................3-9
Move-Out: Business Scenario..............................................................................................................................3-10
The Move-Out Process.........................................................................................................................................3-11
Options for Move-Out Processing........................................................................................................................3-12
Move In/Out: Business Scenario..........................................................................................................................3-13
The Move-In/Out Process....................................................................................................................................3-14
Options in Move-In/Out Processing.....................................................................................................................3-15
Move-In: Master Data..........................................................................................................................................3-16
No Changes to Installation Data...........................................................................................................................3-17
Installation History...............................................................................................................................................3-18
Move-In/Out: Unit Summary...............................................................................................................................3-19
Move-In/Out Exercises.........................................................................................................................................3-20
Move-In/Out Solutions.........................................................................................................................................3-30
Work Management.....................................................................................................................................................4-1
Work Management: Unit Objectives......................................................................................................................4-2
What Areas does the Work Management System Cover?......................................................................................4-3
Utility Management Services.................................................................................................................................4-4
Work Management: Technical Objects..................................................................................................................4-5
Overview of Technical Objects..............................................................................................................................4-6
Supply Grid............................................................................................................................................................4-7
Connection Object..................................................................................................................................................4-8
Work Management: Services.................................................................................................................................4-9
Installation Services..............................................................................................................................................4-10
Basic Structure of a Work Order..........................................................................................................................4-11
Sequence of Order Processing..............................................................................................................................4-12
Service Product: Concept.....................................................................................................................................4-13
Service Product: Create Service Connection........................................................................................................4-14
The Installation Services Process.........................................................................................................................4-15
Create Service Connection...................................................................................................................................4-16
Work Management: Interfaces.............................................................................................................................4-17
Possible Configuration of an Interface Scenario..................................................................................................4-18
Technical Objects in Work Management and GIS...............................................................................................4-19
Device Repairs.....................................................................................................................................................4-20
Work Management: Unit Summary.....................................................................................................................4-21
Work Management Exercises...............................................................................................................................4-22
Work Management Solutions...............................................................................................................................4-23
Device Technology.....................................................................................................................................................5-1
Device Technology: Unit Objectives.....................................................................................................................5-2
Demands on Device Management..........................................................................................................................5-3
Device Management: Business Scenario................................................................................................................5-4
Device Technology: Device Category....................................................................................................................5-5
The Device and the Device Category.....................................................................................................................5-6
Modeling of Devices..............................................................................................................................................5-7
Integration with Logistics.......................................................................................................................................5-8
Definition of Device Category...............................................................................................................................5-9
Device Category Data...........................................................................................................................................5-10
Possible Elements of the Device Category...........................................................................................................5-11
Device Category: Device and Register.................................................................................................................5-12
Definition of Devices...........................................................................................................................................5-13
Device Data..........................................................................................................................................................5-14
Definition of a Register........................................................................................................................................5-15
Register Data........................................................................................................................................................5-16
Device Technology: Device Lifecycle.................................................................................................................5-17
Central Data Objects - Integration in Logistics....................................................................................................5-18
Device Life Cycle.................................................................................................................................................5-19
Documentation for the Device Lifecycle.............................................................................................................5-20
Device Technology: Device Inspection................................................................................................................5-21
Introduction: Device Inspection and Certification...............................................................................................5-22
Certification Procedures Overview......................................................................................................................5-23
Certification Procedure.........................................................................................................................................5-24
Sampling Procedure.............................................................................................................................................5-25
Inspection Using the Sampling Procedure...........................................................................................................5-26
Periodic Replacement...........................................................................................................................................5-27
Device Technology: Unit Summary.....................................................................................................................5-28
Device Technology Exercises..............................................................................................................................5-29
Device Technology Solutions...............................................................................................................................5-32
Device Installation......................................................................................................................................................6-1
Device Installation: Unit Objectives......................................................................................................................6-2
Device Installation: Business Scenario..................................................................................................................6-3
Installation: Installation, Removal And Replacement............................................................................................6-4
Business Scenario: Replacement of Sample Devices.............................................................................................6-5
Service Order Execution: Determining the Device Location.................................................................................6-6
Definition of the Device Location..........................................................................................................................6-7
Device Location Data.............................................................................................................................................6-8
Relationships Between Technical Objects.............................................................................................................6-9
Service Order Execution: Device Replacement & Service Order Confirmation.................................................6-10
Data Changes: Installation Location....................................................................................................................6-11
Data Changes: Device Replacement....................................................................................................................6-12
Technical and Billing-Related Installation...........................................................................................................6-13
Installation: Installation Structure........................................................................................................................6-14
Example of an Installation Structure....................................................................................................................6-15
Technical Installation Structure............................................................................................................................6-16
Billing-Related Installation Structure...................................................................................................................6-17
Device Installation: Summary..............................................................................................................................6-18
Device Installation Exercises...............................................................................................................................6-19
Device Installation Solutions................................................................................................................................6-22
Meter Reading............................................................................................................................................................7-1
Meter Reading: Unit Objectives.............................................................................................................................7-2
Meter Reading: Business Scenario.........................................................................................................................7-3
Meter Reading: Meter Reading Organization........................................................................................................7-4
Types of Meter Reading.........................................................................................................................................7-5
Regional Structure and Scheduling........................................................................................................................7-6
Scheduling Tasks....................................................................................................................................................7-7
Portions and Meter Reading Units.........................................................................................................................7-8
Generation of Schedule Records............................................................................................................................7-9
Scheduling: Annual Billing..................................................................................................................................7-10
Meter Reading Organization: Street Route..........................................................................................................7-11
Meter Reading: Process........................................................................................................................................7-12
Overview: Scheduled Meter Reading...................................................................................................................7-13
Creating Meter Reading Orders............................................................................................................................7-14
Issuing the Meter Reading Orders........................................................................................................................7-15
Types of Result Entry...........................................................................................................................................7-16
Result Entry Data.................................................................................................................................................7-17
Checking Meter Reading Results: Overview.......................................................................................................7-18
Check Meter Reading Results: Process................................................................................................................7-19
Monitoring Meter Readings.................................................................................................................................7-20
Meter Reading: Special Functions:......................................................................................................................7-21
Meter Reading by Customers over the Internet....................................................................................................7-22
Meter Reading by Customer over WAP Telephone.............................................................................................7-23
Reversing Meter Reading Orders: Process...........................................................................................................7-24
Meter Reading: Unit Summary............................................................................................................................7-25
Meter Reading: Exercises.....................................................................................................................................7-26
Meter Reading: Solutions.....................................................................................................................................7-27
Energy Data Management..........................................................................................................................................8-1
Profile Management: Unit Objectives....................................................................................................................8-2
Profile Management: Business Scenario................................................................................................................8-3
Profile Header.........................................................................................................................................................8-4
Profile Allocation for Register...............................................................................................................................8-5
Point of Delivery....................................................................................................................................................8-6
Importing Profile Values........................................................................................................................................8-7
Profile Values.........................................................................................................................................................8-8
Formula Profile.......................................................................................................................................................8-9
Synthetic Profiles.................................................................................................................................................8-10
Profile Management: Summary............................................................................................................................8-11
Billing and Invoicing..................................................................................................................................................9-1
Billing and Invoicing: Course Objectives..............................................................................................................9-2
Billing.....................................................................................................................................................................9-3
Billing: Introduction...............................................................................................................................................9-4
Billing: Business Scenario......................................................................................................................................9-5
IS-U/CCS: Billing..................................................................................................................................................9-6
Billing Procedures: Overview................................................................................................................................9-7
Definition of Billing...............................................................................................................................................9-8
Billing Tasks...........................................................................................................................................................9-9
Billing Periods......................................................................................................................................................9-10
Forms of Billing...................................................................................................................................................9-11
Special Forms of Billing.......................................................................................................................................9-12
Generation of Schedule Records..........................................................................................................................9-13
Billing Process: Overview....................................................................................................................................9-14
Universal Billing Engine......................................................................................................................................9-15
General Billing Functions.....................................................................................................................................9-16
Example: Billing Rule for Electricity...................................................................................................................9-17
Special Billing Functions.....................................................................................................................................9-18
Billing and Simulation..........................................................................................................................................9-19
Simulation Types..................................................................................................................................................9-20
Document Types...................................................................................................................................................9-21
Document Information.........................................................................................................................................9-22
Further Processing of Documents........................................................................................................................9-23
Outsorting Procedure............................................................................................................................................9-24
Outsorting Process................................................................................................................................................9-25
Billing Reversal....................................................................................................................................................9-26
Billing Reversal Process.......................................................................................................................................9-27
Billing: Unit Summary.........................................................................................................................................9-28
Invoicing: Introduction.........................................................................................................................................9-29
Invoicing: Business Scenario...............................................................................................................................9-30
Definition of Invoicing.........................................................................................................................................9-31
Invoicing: Overview.............................................................................................................................................9-32
Tasks of Invoicing................................................................................................................................................9-33
Invoicing Units.....................................................................................................................................................9-34
Mandatory and Optional Contracts: 1..................................................................................................................9-35
Mandatory and Optional Contracts: 2..................................................................................................................9-36
Invoicing Options.................................................................................................................................................9-37
Source of Billing Documents...............................................................................................................................9-38
Invoicing Various Services..................................................................................................................................9-39
Cross-company code invoicing............................................................................................................................9-40
Bill Due Date........................................................................................................................................................9-41
Document Flow in Invoicing................................................................................................................................9-42
Settlement: Overview...........................................................................................................................................9-43
Bill Printout Procedure.........................................................................................................................................9-44
Invoicing Reversal................................................................................................................................................9-45
Procedure for Bill Reversal..................................................................................................................................9-46
Procedure for Full Reversal..................................................................................................................................9-47
Invoicing: Unit Summary.....................................................................................................................................9-48
Billing and Invoicing Exercises............................................................................................................................9-49
Billing and invoicing Solutions............................................................................................................................9-58
Billing Master Data..................................................................................................................................................10-1
Billing Master Data: Unit Objectives...................................................................................................................10-2
Billing Master Data: Overview............................................................................................................................10-3
Billing Master Data: Introduction........................................................................................................................10-4
Billing Master Data: Business Scenario...............................................................................................................10-5
Billing of Utility Services.....................................................................................................................................10-6
Business Objects: Rate Allocation.......................................................................................................................10-7
Rate Allocation: Overview...................................................................................................................................10-8
Billing Class I.......................................................................................................................................................10-9
Rate Category I...................................................................................................................................................10-10
Rate Category II.................................................................................................................................................10-11
Definition of Rate Type......................................................................................................................................10-12
Business Objects: Rate Structure........................................................................................................................10-13
Rate.....................................................................................................................................................................10-14
Example: Billing Rule for Electricity.................................................................................................................10-15
Rate Structure.....................................................................................................................................................10-16
Rate Data............................................................................................................................................................10-17
Data for the Rate Step.........................................................................................................................................10-18
Structure of the Fact Group................................................................................................................................10-19
Operand Data......................................................................................................................................................10-20
Operand Categories/Examples...........................................................................................................................10-21
Rate Determination - Operands..........................................................................................................................10-22
Allocation of Operand Values............................................................................................................................10-23
Schema 1............................................................................................................................................................10-24
Schema 2............................................................................................................................................................10-25
Price Categories..................................................................................................................................................10-26
Price Types.........................................................................................................................................................10-27
Rate Determination.............................................................................................................................................10-28
Rate Structure.....................................................................................................................................................10-29
Discounts / Surcharges.......................................................................................................................................10-30
Billing Master Data: Unit Summary...................................................................................................................10-31
Exercises: Billing Master Data...........................................................................................................................10-32
Billing Master Data Solutions............................................................................................................................10-35
Real-Time-Pricing....................................................................................................................................................11-1
Real-Time-Pricing: Unit Objectives.....................................................................................................................11-2
Real-Time-Pricing:Business Scenario..................................................................................................................11-3
RTP Overview......................................................................................................................................................11-4
RTP interface........................................................................................................................................................11-5
RTP-Billing..........................................................................................................................................................11-6
Example................................................................................................................................................................11-7
Data Model for Billing.........................................................................................................................................11-8
Interface................................................................................................................................................................11-9
Input Parameters.................................................................................................................................................11-10
Calculation..........................................................................................................................................................11-11
Result..................................................................................................................................................................11-12
Transfer of Results to RTP Operand..................................................................................................................11-13
Real-Time-Pricing: Unit Summary....................................................................................................................11-14
Budget Billings.........................................................................................................................................................12-1
Budget Billing: Unit Objectives...........................................................................................................................12-2
Budget Billing: Business Scenario.......................................................................................................................12-3
Budget Billing Procedure: Overview...................................................................................................................12-4
Payment Plan Categories......................................................................................................................................12-5
Budget Billing Plan: Overview............................................................................................................................12-6
Creating / Adjusting Budget Billing Plans...........................................................................................................12-7
Quantity-Based Extrapolation..............................................................................................................................12-8
Budget Billing Amounts Due...............................................................................................................................12-9
Budget Billings: Summary.................................................................................................................................12-10
Contract Accounts Receivable and Payable.............................................................................................................13-1
Contract Accounts Receivable and Payable: Unit Objectives..............................................................................13-2
Contract Accounts Receivable and Payable: Overview.......................................................................................13-3
Contract Accounts Receivable and Payable: Business Scenario..........................................................................13-4
Contract Accounts Receivable and Payableand FI-CA........................................................................................13-5
FI-CA Has An Open Architecture........................................................................................................................13-6
Special Features of FI-CA....................................................................................................................................13-7
Central Objects in FI-CA.....................................................................................................................................13-8
Contract Accounts Receivable and Payable: Business Transactions...................................................................13-9
Contract Accounts Receivable and Payable: Posting Documents......................................................................13-10
Posting Documents: Objectives..........................................................................................................................13-11
Posting Documents: Introduction.......................................................................................................................13-12
Posting Documents: Business Scenario.............................................................................................................13-13
Documents in Contract Accounts Receivableand Payable.................................................................................13-14
General Document Data.....................................................................................................................................13-15
Document Data: Reference and Currency..........................................................................................................13-16
Document Data: Link to General Ledger Accounting.......................................................................................13-17
Document Data: Entry Control...........................................................................................................................13-18
Data on Business Partner Item...........................................................................................................................13-19
Data on G/L Account Item.................................................................................................................................13-20
Manual Document Entry: Items.........................................................................................................................13-21
Transactions in Contract Accounts Receivable and Payable.............................................................................13-22
Examples of Transactions...................................................................................................................................13-23
Transfer to General Ledger Accounting.............................................................................................................13-24
Summary Record................................................................................................................................................13-25
Posting Documents: Summary (1).....................................................................................................................13-26
Posting Documents: Summary (2).....................................................................................................................13-27
Contract Accounts Receivable and Payable: Account Display..........................................................................13-28
Account Display: Objectives..............................................................................................................................13-29
Account Display: Introduction...........................................................................................................................13-30
Account Display: Business Scenario..................................................................................................................13-31
Account Display: Initial Screen..........................................................................................................................13-32
Account Display: List Category.........................................................................................................................13-33
Account Display: Line Layout...........................................................................................................................13-34
Account Display: Navigating in the Document Display....................................................................................13-35
Account Display: Summary (1)..........................................................................................................................13-36
Account Display: Summary (2)..........................................................................................................................13-37
Contract Accounts Receivable and Payable: Payments.....................................................................................13-38
Payment Run: Objectives...................................................................................................................................13-39
Payment Run: Introduction.................................................................................................................................13-40
Payment Run: Business Scenario.......................................................................................................................13-41
Automatic and Manual Payments.......................................................................................................................13-42
Payment Lot.......................................................................................................................................................13-43
Payment Lot: Structure.......................................................................................................................................13-44
Payment Lot: Structure.......................................................................................................................................13-45
Payment Lot: Processing Steps..........................................................................................................................13-46
Payment Lot: Create...........................................................................................................................................13-47
Payment Lot: Create Items.................................................................................................................................13-48
Payment Lot: Change.........................................................................................................................................13-49
Payment Lot: Close............................................................................................................................................13-50
Payment Lot: Post..............................................................................................................................................13-51
Automatic Clearing: Process..............................................................................................................................13-52
Payment Lot: Post-processing............................................................................................................................13-53
Payment at cash desk..........................................................................................................................................13-54
Clearing: Dialog Processing...............................................................................................................................13-55
Payment: Summary............................................................................................................................................13-56
Contract Accounts Receivable and Payable: Returns........................................................................................13-57
Returns: Objectives............................................................................................................................................13-58
Returns: Introduction..........................................................................................................................................13-59
Returns: Business Scenario................................................................................................................................13-60
Returns: Influencing Factors..............................................................................................................................13-61
Returns: Activity Settings...................................................................................................................................13-62
Returns Lot: Processing Steps............................................................................................................................13-63
Returns Lot: Create.............................................................................................................................................13-64
Returns Entry......................................................................................................................................................13-65
Returns Lot: Change...........................................................................................................................................13-66
Returns Lot: Close..............................................................................................................................................13-67
Returns Lot: Posting (1).....................................................................................................................................13-68
Returns Lot: Posting (2).....................................................................................................................................13-69
Returns Lot: Post-processing..............................................................................................................................13-70
Returns History...................................................................................................................................................13-71
Returns: Summary..............................................................................................................................................13-72
Contract Accounts Receivable and Payable: Dunning.......................................................................................13-73
Dunning: Objectives...........................................................................................................................................13-74
Dunning: Introduction........................................................................................................................................13-75
Dunning: Business Scenario...............................................................................................................................13-76
Dunning: Dunning Proposal and Dunning Activities.........................................................................................13-77
Dunning: Influential Factors...............................................................................................................................13-78
Dunning Proposal for a Business Partner...........................................................................................................13-79
Dunning: Factors That Can Be Influenced (Selection)......................................................................................13-80
Dunning: Determination of Dunning Levels......................................................................................................13-81
Dunning Levels..................................................................................................................................................13-82
Printing of Dunning Notice for a Business Partner............................................................................................13-83
Dunning: Dunning History.................................................................................................................................13-84
Dunning: Summary............................................................................................................................................13-85
Contract Accounts Receivable and Payable: Deferral and Installment Plan......................................................13-86
Deferral and Installment Plan: Objectives..........................................................................................................13-87
Deferral and Installment Plan: Introduction.......................................................................................................13-88
Deferral and Installment Plan: Business Scenario..............................................................................................13-89
Deferral...............................................................................................................................................................13-90
Installment Plan: Characteristics........................................................................................................................13-91
Installment Plan Category..................................................................................................................................13-92
Installment Plan: Item Selection.........................................................................................................................13-93
Deferral and Installment Plan: Unit Summary...................................................................................................13-94
Contract Accounts Receivable and Payable Exercises.......................................................................................13-95
Contract Accounts Receivable and Payable Solutions.....................................................................................13-108
Waste Industry..........................................................................................................................................................14-1
Waste Industry: Unit Objectives..........................................................................................................................14-2
Solution Map and Integration Model for the Waste Industry...............................................................................14-3
Integration Model for mySAP Waste Industry.....................................................................................................14-4
mySAP Waste Industry : Involved Areas.............................................................................................................14-5
Focus Areas of IS-Waste - Waste Industry..........................................................................................................14-6
Focus Areas of EH&S WA - Waste Management...............................................................................................14-7
The Waste Disposal Cycle with EH&S................................................................................................................14-8
Data Model – Container Service (Simplified)......................................................................................................14-9
Technical Master Data I.....................................................................................................................................14-10
Technical Master Data II....................................................................................................................................14-11
Technical Master Data III...................................................................................................................................14-12
Container Management: Integration..................................................................................................................14-13
Interface to Route Planning System...................................................................................................................14-14
Waste Disposal Orders.......................................................................................................................................14-15
Process: Container Delivery / Removal.............................................................................................................14-16
Fleet Management..............................................................................................................................................14-17
Implemented Functions I....................................................................................................................................14-18
Implemented Functions II...................................................................................................................................14-19
Planned Functions for mySAP Utilities 4.64.....................................................................................................14-20
Waste Industry: Summary..................................................................................................................................14-21
0
SAP AG 1999
IUT110 Introduction to the IS-U/CCS System
Introduction to the IS-U/CCS SystemIntroduction to the IS-U/CCS System
IUT110IUT110
R/3 System Release 4.63 / IS-Utilities/Customer Care Service August 2001 5004 4795
0.2
SAP AG 1999
Copyright 2001 SAP AG. All rights reserved.
Neither this training manual nor any part thereof maybe copied or reproduced in any form or by any means,or translated into another language, without the priorconsent of SAP AG. The information contained in thisdocument is subject to change and supplement without prior notice.
All rights reserved.
Copyright
Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft Corporation.
Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation. Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc. ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc. TouchSend Index ® is a registered trademark of TouchSend Corporation. Visio ® is a registered trademark of Visio Corporation. IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation. Indeo ® is a registered trademark of Intel Corporation. Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape
Communications, Inc. OSF/Motif ® is a registered trademark of Open Software Foundation. ORACLE ® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated. UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation. ADABAS ® is a registered trademark of Software AG The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3,
R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime,
SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG.
Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.
0.3
SAP AG 1999
SAP Utilities (IS-U/CCS)
Introduction to the IS-U/CCS
IUT110 5 days
Level 2 Level 3
Work Management
IUT221 3 days
Customer Service
IUT250 4 days
Contract Accounts Receivable and Payable
IUT240 5 days
Print Workbench
IUT280 2 days
Device Management
IUT220 3 days
Billing and Invoicing
IUT230 5 days
Basic Data/ BasicFunctions
IUT210 3 days
Real Time Pricing
IUT235 2 days
Energy DataManagement
IUT225 2 days
0.4
SAP AG 1999
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
0.5
SAP AG 1999
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
0.6
SAP AG 1999
This course will prepare you to:
Course Goals
Recognize how IS-U is integrated in the R/3 environment
Outline business processes in IS-U
Use and efficiently implement IS-U
0.7
SAP AG 1999
Course Objectives
At the conclusion of this course, 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
0.8
SAP AG 1999
Course Content
Unit 8 Energy Data Management
Unit 9 Billing & Invoicing
Unit 10 Billing Master Data
Unit 11 Real-Time Pricing
Unit 12 Budget Billings
Unit 13 Contract Accounts Receivable and Payable
Unit 14 Waste Disposal Industry
Unit 1 IS-U/CCS Overview
Unit 2 CIC
Unit 3 Move-In/Out
Unit 4: Work Management
Unit 5 Device Technology
Unit 6 Device Installation
Unit 7 Meter Reading
Preface
Appendix
CIC: Customer Interaction Center
1
SAP AG 1999
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
IS-U/CCS: Overview
(C) SAP AG IUT110 1
1.2
SAP AG 1999
At the conclusion of this unit, 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
IS-U/CCS Overview: Unit Objectives
(C) SAP AG IUT110 2
1.3
SAP AG 1999
The course participants are new employees ofeNRGCo.
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
IS-U Overview: Business Scenario
(C) SAP AG IUT110 3
1.4
SAP AG 1999
INTEGRATEDPERSONAL
CO-OPERATIVE
- platform for business co-operation
- industry-specific
- integrated, universal business processes
- building of business relationships (virtual communities)
- integration of external services (content)
- "One-Step Business" (co-operation)- application hosting
- Internet business framework
- individually adaptable
- role-specific
- standard entry into all internal and external services
mySAP.com: Overview
The mySAP.com concept consists of three areas: The my area stands for easy access to all elements of mySAP.com. Based on the results of the
EnjoySAP initiative, the mySAP.com workplace provides personalized, role-based system access. The SAP area represents the availability of enterprise software over the Internet. The .com area stands for the Internet intiative of SAP. Trade relations and business co-operation can
be initiated and developed over the Internet.
(C) SAP AG IUT110 4
1.5
SAP AG 1999
Company limits
Web browser access
Market-place
Market-place
Single Sign-On
R/3 4.6R/3 4.6FIFI LOLO
HRHR
CRMCRMKMKM
B2BB2B
SEMSEM
APOAPO
BW BW
mySAPUtilities
IS-U/CCS
mySAPUtilities
IS-U/CCSmySAP.com components
OpenInternet
Standards
R/2R/2
Non mySAP.comExt.Comp.Ext.
Comp.
Leg. Syst.Leg. Syst.
PartnerPartner
SAPSAP
within
outside
mySAP.com Internet services
Other Internet services
WorkplaceIndustry-specific
Role-basedPersonalizedDrag & Relate
WorkplaceIndustry-specific
Role-basedPersonalizedDrag & Relate
Workplace Internet Business Framework
The Workplace contains links to information within and outside company limits. Links can be made to: Non mySAP.com components: External systems via open Internet standards mySAP.com components: Classical and new Web-based R/3 transactions (standard R/3 System, New
Dimensions, industry solutions), Reports (such as Business Information Warehouse reports in BW 2.1C), Knowledge Warehouse content
mySAP.com Internet services: mySAP.com Marketplace Any Internet or intranet Websites
(C) SAP AG IUT110 5
1.6
SAP AG 1999
mySAP Utilities: The Comprehensive Solution
SAP Customer Relationship Management
SAP Supply Chain Management
SAP Business Intelligence
SAP Business-to-Business E-Commerce
Finance & Controlling
Human Resource Management
Logistics
Business Network
Strategic EnterpriseManagement
Strategic EnterpriseManagement
Busi ness Intelligence&
Data Warehousing
Busi ness Intelligence&
Data Warehousing
ManagerialAccounti ng
ManagerialAccounti ng
FinancialAccounti ng
FinancialAccounti ng
RegulatoryReporting/FERC
RegulatoryReporting/FERC
Invoici ngInvoici ng Recei vabl es ManagementRecei vabl es Management Third Party Settl ementThird Party Settl ement
Sal es C ycle &Sal es C ycle & Ser viceAgreement
Ser viceAgreement
Special C ustomerProcesses
Special C ustomerProcesses Retail BillingRetail Billing
Engineering &Constructi on
Engineering &Constructi on ProductionProduction Plant MaintenancePlant Maintenance Decommissi oni ngDecommissi oni ng
Customer ServiceCustomer Service Market R esearch& Anal ysis
Market R esearch& Anal ysis
Product/Brand Marketing
Product/Brand Marketing
Marketi ngProgram
Management
Marketi ngProgram
Management Sal es ManagementSal es Management Sal es
Channels
Sal esChannels
Engineering &Constructi on
Engineering &Constructi on Operati ons ManagementOperati ons Management Maintenance &
Wor k Management
Maintenance &Wor k Management
Transmissi on &Distribution Service
Transmissi on &Distribution Service
Sal es C ycle &Billing
Sal es C ycle &Billing
Connecti on & Installati onManagement
Connecti on & Installati onManagement
Ser viceManagement
Ser viceManagement
Meter ReadingManagement
Meter ReadingManagement
Energy DataManagement
Energy dataManagement
TradersWor kbench
TradersWor kbench
RiskManagement
RiskManagement
WholesaleBilling
WholesaleBilling
Reconciliati on& Settlement
Reconciliati on& Settlement
Pool/ISO
Pool/ISO
Human R esourceManagement
Human R esourceManagement ProcurementProcurement Treasur yTreasur y Fixed Asset
Management
Fixed AssetManagement Real EstateReal Estate
(C) SAP AG IUT110 6
1.7
SAP AG 1999
Internet SalesInternet Sales
ContactContact CenterCenter
Mobile SalesMobile Sales
Customer Relationship Management (CRM)
SAP Customer Relationship Management (CRM) provides solutions that enable companies to effectively maintain customer relationships throughout the entire life cycle. CRM supports companies by understanding and anticipating the requirements of their customer base as well as those of potential customers. 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. The data is saved on a lap-top database and is regularly aligned with the CRM System. Contact Center Scenario: Along with the Customer Interaction Center (CIC), this forms one of the
key components of SAP CRM. The CIC enables processing of incoming and outgoing telephone calls using the SAPphone CTI (Computer Telephony Integration) interface, processing of incoming and outgoing E-mails and activity management (recording of all contacts in the contact center). The CIC can be used in service (Service Interaction Center SIC), sales and distribution or marketing (telesales and telemarketing).
Internet Sales Scenario: Enables electronic business activities to take place over the World Wide Web between companies, and between companies and end-customers (B2C).
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
1.8
SAP AG 1999
R/3 Other
Efficient Analysis of Information- innovative and intuitive user interface- efficient OLAP analysis functions- for all types of user
Extensive Business Content- information model, reports and
extractors- Metadata repository- company comparison values
End-to-End Data Warehousing Solutions- extraction of R/3 data and external data- fully automated- central control
Business Information Warehouse (BW)
The SAP Business Information Warehouse (BW) is the mySAP.com business component that is used to extract and analyze data from operative business applications (OLTP systems). 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. OLTP stands for Online Transaction Processing.
The SAP Business Information Warehouse supports Online Analytical Processing (OLAP) and is especially suitable for processing large volumes of operative and historical data.
SAP BW contains all the necessary Metadata for current business processes. This includes InfoSources, InfoCubes and standard reports, transfer structures for all releases and communication structures and update rules for each InfoCube. 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.
SAP BW requests application data in regular intervals from the allocated source systems (pull mechanism). The back-end systems therefore contain extractors that collect data and deliver it to the SAP Business Information Warehouse.
(C) SAP AG IUT110 8
1.9
SAP AG 1999
Customerservice &
billingGenerationGeneration TransmissionTransmission DistributionDistribution
Consumptionentry
Consumptionentry
InvoicingInvoicingContractA/R & A/PContractA/R & A/P
Meter & Device Management
Work Management
Servicebilling
Consumptionbilling
Consumptionbilling
Installationservices
All customer-related business processes
InvoicingInvoicing
MarketingMarketing& Sales& Sales
Particular business processesParticular business processesCustomer Relationship ManagementCustomer Relationship Management
IS-U/CCS
PMMM
SD
FIFI
CRM
Functional Scope of the IS-U System
(C) SAP AG IUT110 9
1.10
SAP AG 1999
Integrated and Open System Landscape
ITSITS
CTICTIAnalyses
Back end Front end
Telebusiness
MobileAppli-
cations
SAPIS-U/CCS
SAP BW
Business objects such as business
partner, agreement, contracts, products
and sales and distribution
projects
Electronic business (Internet)
(C) SAP AG IUT110 10
1.11
SAP AG 1999
ITSITS
CTICTI
Business objects such as business partner, activities,
contracts, products, sales and
distribution projects
Telebusiness
Electronic business (Internet)
MobileAppli-
cations
SAPIS-U/CCS
SAP BW
IS-U/CCS Business Processes
Device ManagementBilling InvoicingContract Accounts Receivable and PayableIntercompany Data ExchangeEnergy Data Management...
Device ManagementBilling InvoicingContract Accounts Receivable and PayableIntercompany Data ExchangeEnergy Data Management...
Analyses
Back end Front end
(C) SAP AG IUT110 11
1.12
SAP AG 1999
ITS
CTI
Business objects such as business partner, activities,
contracts, products, sales and
distribution projects
Telebusiness
Electronic business (Internet)
MobileAppli-
cations
SAPIS-U/CCS
SAP BW
Business partnersContract accountsContractsConnection objectsPoints of delivery
Business partnersContract accountsContractsConnection objectsPoints of delivery
Synchronized Business Objects
Analyses
Back end Front end
(C) SAP AG IUT110 12
1.13
SAP AG 1999
Analyses
Back end Front end
ITS
CTICTIAnalysis
Business objects such as business partner, contracts
and products.
Telebusiness
Electronic business (Internet)
Mobile Components
SAPIS-U/CCS
SAP BW
Business partner transfer to target group selection
2) Target group selection
3) Transfer of target group to SAP CRM
4) Marketing planning5) Campaign creation6) Campaign execution7) Activity management8) Campaign feedback (BW)9) Contract creation10) Contract synchronization
11) Automatic creation of contracts12) IDE communication with prior
supplier or transmission company13) Automatic creation or change of
master data-----14) Transfer of meter reading results15) Billing and invoicing16) Transfer of sales and transaction
statistics to BW17) Optional: Commission
determination
1(a) Import of external addresses to target group selection
Marketing and Sales Process
(C) SAP AG IUT110 13
1.14
SAP AG 1999
Marketing& Analysis
ServiceCenter
Tele-Sales
FieldService
ServiceLevelMgmt
Product & Brand
Mgmt Tele-Marketing
InternetMarketing
FieldSales
InternetSales
Bus.Part.Collabor-
ation
CustomerDevelop-
ment
RetentionManage-
ment
mySAP CRM 3.0
Marketing & Sales
ContractAccounting
ConsumptionEntry
InstallationServices
Device ManagementMeters/Devices/Connecti
ons
InformationSystem
Work Management
BusinessPartners:
Resid. Cust.Nonresid. Cust.
Sales Cust.
OwnerBill Recipient
Installer
Sectors:Electricity
GasWater
Waste WaterDistrict Heating
Cable TV
Service ContractGoods
ChargesTaxes / Fees
Prospect
Waste Disposal
Service Order
Billing & Invoicing
Service Cust.
mySAPUtilities
4.63
mySAPBW 2.1C
Replication viaCRM middleware
BW extra
ctors
From IS
-U-specific
master data and tr
ansaction
data to ta
rget g
roup
selection in
BW
From selected target groups,top n analyses and otheranalyses in BW in accordance with CRM
BW extractors
From CRM data to
analysis in BW
Data transfer
Of business partner, contract accounts,contracts, connection object and pointof delivery
mySAP Financials
BW extractorsFrom R/3 master data and transaction data to target group selection and other analyses in BW
External data
Flat files from external
data, such as prospects
and so on
ServiceInteraction
Center
InternetCustomer
SelfService
Sales Mgmt & Support
System Infrastructure CRM, BW and mySAPUtilities
(C) SAP AG IUT110 14
1.15
SAP AG 1999
FIFISDSD
AMAMMMMM
GIS,CAD,SCADA
GIS,CAD,SCADA
MMMMPM/PM/CSCS
SDSDCOCO
Sales & Distribution
Sales & Distribution
Contra
ct
A/R +
A/P
(FI-C
A)
Contra
ct
A/R +
A/P
(FI-C
A)Billing/
Invoicing
Billing/
Invoicing
Installation
Services
Installation
Services
Co
nsu
mp
tio
nE
ntr
y
Co
nsu
mp
tio
nE
ntr
yExternal
ConsumptionEntry
Systems
ExternalConsumption
EntrySystems
ExternalSales
Systems
ExternalSales
Systems
SAPBusinessPartner
SAPBusinessPartner
Customerinformation system
IS-U components
Standard SAP components
External systems
FinancialAccountingFinancial
Accounting
DeviceManagement
DeviceManagement
CCUUSS TTOOMM EE
RR
Plant Maintenance& Customer
Service
Plant Maintenance& Customer
Service
Asset Management &Materials ManagementAsset Management &Materials Management
CCAA
RREE && SS EE RR VV
II CCEE
IS-U/CCS as an integratedcomponent of the
SAP enterpriseinformation system
IS-U/CCS as an integratedcomponent of the
SAP enterpriseinformation system
PMPM
IS-U/CCS - Integration Model
Central business partner model (R/3) => the customer is the central data object. Cross-application component FI-CA for Contract Accounts Receivable and Payable
Designed for processing a large volume of postings from sales and collection activities for a large number of customers
Industry-specific enhancements for the utilities industry enable the use of the standard R/3 component PM/CS (Plant Maintenance/Customer Service).=> ideal prerequisites for processing service activities
PM/CS is integrated with the following components:SD: Management of customer quotations and orders, and also execution of billingCO: Allocation and settlement of costs related to service activitiesMM: Processing of material requirements and goods movement related to service activities
The results of service billing can be transferred to IS-U invoicing; further processing of debits occurs via FI-CA.
Material master records are managed in MM at the same time as device categories in IS-U; purchasing and stockholding of devices are processed using MM components.
(C) SAP AG IUT110 15
1.16
SAP AG 1999
Deregulation-enabled functionality
Integration of application areas
Homogeneous interaction between accounting and core logistics processes
Business processes for all areas Shorter lead times for business processes
Flexibility
Can be adapted to local deregulation rules Can be implemented in all types of companies Supports all types of service Enables development of individual business strategy
Customer-orientation
User friendly Oriented to business processes Competition-oriented Informative Communicative
Open architecture
The Strengths of mySAP Utilities
(C) SAP AG IUT110 16
1.17
SAP AG 1999
Solution Map SAP Utilities
Classic utility company
Generation Transmission & Distribution Sales & Distribution
Deregulation
Generation TransmissionDistribution
Device Management
Marketing, sales and distribution, billing, customer service
Solutions for the New Industry Market Model
(C) SAP AG IUT110 17
1.18
SAP AG 1999
Distribution company
Settlement coordinator
(= transmission company)
Supplier
Exchanges and bilateral contracts
Grid access regulations for use of the transmission grid,
schedule and settlement results
Grid connection contract, grid usage contract
Negotiated grid access, outline contract for smaller customers, schedule and
settlement results
Energy procurement
contracts
Energy supply contract
Business partner
Balance comparison
Deregulated Market: Business Perspective
(C) SAP AG IUT110 18
1.19
SAP AG 1999
CallCall--center functionalitycenter functionality
Faster and more direct access to all relevant information and transactions required during contact with customers is admissible. This includes customer overviews, changing master data, displaying bills, entering meter reading results, account information and so on.
Work items allow callbacks and outbound campaigns.
Master data templateMaster data template
Product modeling on the basis of configured materials and pricing in SD. The master data generator is used to post-edit campaigns.
ISIS--U content for BWU content for BW
Sales statistics, consumption statistics, transaction statisticsand so on
Sales and Marketing in IS-U/CCS (1)
(C) SAP AG IUT110 19
1.20
SAP AG 1999
Workflow
mySAP Utilities
Master datatemplate
Master datatemplate
Master datagenerator
Master datagenerator
Product selectionusing mySAP CRMchannels:
mySAP CRMproduct
mySAP CRMproduct
ConfigurationConfiguration
Variable product informationVariable product information
Fixed product informationFixed product information
mySAP Utilitiesproduct
mySAP Utilitiesproduct
ConfigurationConfiguration
Master data generationor change inmySAP Utilities:
Sales Processing
(C) SAP AG IUT110 20
1.21
SAP AG 1999
Internet Self ServicesInternet 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.
Sales and Marketing in IS-U/CCS (2)
(C) SAP AG IUT110 21
1.22
SAP AG 1999
EnterEnteruser and user and passwordpassword
SelectSelectserviceservice
Internet Self Services: Start Page
(C) SAP AG IUT110 22
1.23
S A P A G 1 9 9 9
S e t t l e m e n t
C o ns um pti on Pr i ce C ha r ge
O n-Pe ak kWh 1 0 0 kWh $0 . 25 $ 2 5 .0 0
O f f -Pea k kW h 4 0 0 kWh $0 . 10 $ 4 0 .0 0
S p ot kW h 1 0 0 kWh $0 . 50 $ 5 0 .0 0
A mo un t Du e $ 1 15 .0 0
J o h n S m i t h
1 0 P a r k A v e n u e
1 2 3 4 5 N Y
K W
6 0
3 0
1 0
A d d i t i o n a l A d d i t i o n a l a g r e e m e n t : S p o t a g r e e m e n t : S p o t
d e l i v e r yd e l i v e r y
A g r e e d p r i c e
S p o t p r i c eS p o t p r i c e
E D M• H i s t o r i c a l
p r o f i l e
• P r i c e p r o f i l e
• F o r e c a s t p r o f i l e
B i l l i n g p e r i o d0 5 . 0 1 . – 0 6 . 0 1 .
P r o f i l eM a n a g e m e n t
W h a t i s E n e r g y D a t a M a n a g e m e n t ?
B i l l i n g
Energy Data Management (EDM) enables you to manage consumption data and corresponding business processes. EDM is particularly useful for managing and billing consumption data that is measured at specific intervals (for example load profiles and load shapes).
EDM enables you to bill interval data such as RTP rates (real-time pricing) and time-of-use rates. Settlement
deals with settlement processes, amounts and charges, as well as procurement schedules and network profiles.
(C) SAP AG IUT110 23
1.24
SAP AG 1999
Auto. MR systems
Auto. MR systems
Interval meter
Auto. MR systems
Meterreading
document
customer meter
reading
MDE
Point ofdeliveryPoint ofdelivery
Der
ived
load
pro
file
s
signalDownload
sign
al
Data
entry DownloadUpload
Data entry
MRdata
mgmt
MRMRdatadata
mgmtmgmt
ED
ME
DM
Public networkPublic network
EDIFACT
IMP
OR
T
EX
PO
RT
Tradit.meter
Real-timepricing
Preliminarybilling
Billing Billing Billing
DeviceManagement
DeviceDeviceManagementManagement
Othermodules
Dow
nloa
d
Dataentry
InvoicingInvoicingInvoicing
Contract
A/R + A/P
ContractContract
A/R + A/PA/R + A/P
SchedulingSchedulingScheduling
Loadprofilemgmt
Loadprofilemgmt
Energy Data Management 1
(C) SAP AG IUT110 24
1.25
SAP AG 1999
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, 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
Energy Data Management 2
(C) SAP AG IUT110 25
1.26
SAP AG 1999
IS-U/CCS supports customer-oriented core business processes of utility and service companies.
IS-U/CCS is an integrated component of the SAP enterprise information system.
IS-U/CCS can be used for billing and managing standard divisions as well as additional new services.
IS-U Overview: Unit Summary
(C) SAP AG IUT110 26
2
SAP AG 1999
Contents:
Master data
Objectives of the Customer Interaction Center (CIC)
Typical processing steps
Implementation and use
Most important application areas
Customer contacts
CIC
(C) SAP AG IUT110 1
2.2
SAP AG 1999
At the conclusion of this unit, 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
CIC: Unit Objectives
(C) SAP AG IUT110 2
2.3
SAP AG 1999
Customer call and identification via Front Office
Data environment
Display of business data
Changes to data
Change bank details
Change rates
Customer contact
CIC: Business Scenario
(C) SAP AG IUT110 3
2.4
SAP AG 1999
Basement
Apartment 2
Apartment 3
Apartment 1 Hall
Service Connection: ElectricityService Connection: GasService Connection: Water
SupplyGrid
Street
Connection Object
= Premise
Device locationBasement
Device locationBasement
Device locationHall
Device locationHall
Businesspartner
Contract 1:Electricity
Contract 1:Electricity
Contract 2:Gas
Contract 2:Gas
Contract 3:Water
Contract 3:Water
Installation 1: Electricty
meter
Installation 1: Electricty
meter
Installation 2:
Gas meter
Installation 2:
Gas meter
Installation 3:
Water meter
Installation 3:
Water meter
Contractaccount
Contractaccount
The IS-U House
(C) SAP AG IUT110 4
2.5
SAP AG 1999
SAPBusiness partner
SAPBusiness partner
Owners
Interested party
Tenants
Existing
Debtor
Employee
Installer
Individuals and companies Business partner
relationships Flexible interfaces Integration of business roles GroupNonresidential
customer
Various Business Partners
(C) SAP AG IUT110 5
2.6
SAP AG 1999
• Name• Address• Personal data• Communication
• Name• Address• Personal data• Communication
• Payment transactions• General data (account class,social security,creditworthiness,driver's license no.,employee class)• ...
Prospect
• Type of company• Division license• Work field• License• Main utility company• Identification• ...
Installer
• Branch of industry• Relationships• Contact history• ...
Business partnerBusiness partner
Contract partner
Roles of the Business Partner
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 ProspectOther roles and data fields are dependent on Customizing settings.
A business partner is included in different business processes, 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
2.7
SAP AG 1999
Cross-role data Role-specific data
General
Form of address, nameLegal form, companyGroup, search terms
Addresses
Standard addressP.O. box addressOther addresses
Communication
Telephone, faxExtensionsInternet, E-mail, online
SAPBusinessPartner
SAPBusinessPartner
Payment Transactions
Bank details
Additional Data
Identification numbersLegitimationRegister entry
Business Partner Data
BP Relationships
HierarchicalEqualMarital
Business partners are divided into various groups, to which different attributes are allocated. IS-U differentiates between: Individuals Organizations Groups
Depending on the business context, the business partner can assume different roles. IS-U differentiates between: Contract partner Installer Contact person ProspectOther roles depend on Customizing
For each contract partner, an SD business partner is created in the background. A programmable interface, which will incorporate customer-specific fields, is currently being planned.
(C) SAP AG IUT110 7
2.8
SAP AG 1999
General data Dunning/payment data
Contract
Account
Dunning data
Dunning control Dunning letter recipient Dunning block reason
Outgoing payments
Payment method Bank details Alternate payee
Account assignment
Where-used list for Ols Planning group Account determination Settlement category
Incoming payments
Payment method Bank details Alternate payer
Control Alternative bill recipient Paid by collective bill
account Additional bill
General data Account name Account no. in legacy
system Terms of payment Tolerance group
Contract Account Data
(C) SAP AG IUT110 8
2.9
SAP AG 1999
ContractPartner
ContractPartner
ContractAccount 1
ContractAccount 2
ContractAccount 3
Contract 1(Elec. - domestic)
Contract 2(Water - domestic)
Contract 3(Gas - business)
Contract 4(Elec. - business)
Contract 5(Elec. - business)
150
100
300
100
50
Bill coversheetCA 2/3
Bill coversheetCA 2/3
Total : 450 UNI
(Statisticalposting tocontractcollective billingaccount CBA 1)
Total : 450 UNI
(Statisticalposting tocontractcollective billingaccount CBA 1)
BillCA 1
Total : 250 UNI
BillCA 2
Total : 400 UNI
BillCA 3
Total : 50 UNI
ContractAccount forCollective
Bill
ContractAccount forCollective
Bill
Collective Bills
(C) SAP AG IUT110 9
2.10
SAP AG 1999
General Data Move-In/Move-Out Data
ContractContract
Billing Data
• Joint Invoice• Billing block reason• Outsorting group
Budget BillingData
• Budget billingAdjustment
• Budget billing cycle
Acct Assignment Data• Account determination ID• Cost center• Business area
GeneralContract Data
• Contract account• Division• Company code• Plant/comp. consum.• Statistics group• Authorization group
Scheduling Data• Contract start/end date• Renewal dates• Cancellation dates
Data Relevant to Billing
Deregulation Fields
Contract Data
In the Statistics group field, you specify a statistics group for a contract. It is used for determining data for sales statistics.
The authorization group prevents unauthorized access to specified objects. To be able to carry out any activity protected in this way, the user must have authorization for both the activity and the authorization group.
Data relevant to budget billing (the budget billing cycle, for instance) maintained in the contract overrides the default values defined in the portion or the Customizing settings.
The outsorting group determines which validations are to be carried out in billing. A contract can also be outsorted manually.
The meter reading block reason specifies why the contract has been blocked for meter readings. If you make an entry in this field then the contract can no longer be billed. The contract will not be released again for billing until you enter a billing release reason (the billing release reason overrides the billing block reason).
A business area is an organizational unit that covers a restricted area of activity/responsibility in your company. Value movements entered in Financial Accounting can be attributed to this business area for the purposes of external accounting.
Scheduling data is provided mainly for information purposes. It allows you to display information on when a contract was signed or cancelled, for example.
(C) SAP AG IUT110 10
2.11
SAP AG 1999
PM data IS-U data
ConnectionObject
Additional Data
• Structure/equipment list• Account assignment• Classification
Plant Maintenance• Structure• Maintenance planning
plant• Maintenance planning
group
Location Data
• Maintenance plant• Location description• ABC indicator
General
• Description• Processing status• Notes
Attributes
• Regional structure group• Authorization group
Address
• Street, house number• Postal code, city• Political regional structure
Connection Object Data
(C) SAP AG IUT110 11
2.12
SAP AG 1999
General data Relationships
Premise
Additional Data
Notes Update log
Attributes
Premise type Owners Number of occupants
Location Data
Storey Room number Location description
Connection Object
Forms the link betweenthe premise and theregional structure
Technology
Can be assigned to adevice location
Installation
Can comprise severalinstallations to be billed
Premise Data
(C) SAP AG IUT110 12
2.13
SAP AG 1999
General data Relationships
Additional Data Installation type Guarantee of supply Notes Update log
Control Data
Supply or consumption Definition of base period Meter reading control
Process Data
Current premise Current business partner Current contract
Installation
Billing Rate category Rate data for devices
and registers Reference value
Regional Structure Linked via the premise
and connection object Override default meter
reading unit
Business Partner
Conclusion of the contractwith the business partner
Installation Data
(C) SAP AG IUT110 13
2.14
SAP AG 1999
Point of delivery
Technical
• Register
Header data• Structure category• History
Point of delivery ID
• Description• Point of delivery type• Point of delivery role
Deregulation• Installation• Premise• Service type• Grid (distributor)• Settlement unit
Point of Delivery Data
(C) SAP AG IUT110 14
2.15
SAP AG 1999
IS-UIS-U
FI-CAFI-CA
SD, CS, PMSD, CS, PM
Cross appl.Cross appl. Contractaccount
Businesspartner
Regionalstructure
Connectionobject
Connectionobject
Connection
Device location
Premise
Contract(utility)
Installation
Device
Meter reading
Integration withLogistics
Device category
Point of delivery
Business Objects in IS-U/CCS
Service
(C) SAP AG IUT110 15
2.16
SAP AG 1999
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
What Is a Customer Interaction Center?
(C) SAP AG IUT110 16
2.17
SAP AG 1999
Efficient user interface, short training period
All common service functions directly accessible
Entry with incomplete data and comprehensive search help
User-specific adjustment of the interface and of the available business processes
Connection to external communication systems (e.g. Computer Telephony Integration, Internet)
Customer Interaction Center: Requirements
(C) SAP AG IUT110 17
2.18
SAP AG 1999
IS-U/CCS Front Office Functions
WWW
Fax Letter Telephone Internet In person
IS-UCustomer Information System
Archiveintegration
Archiveintegration
Call centerintegrationCall centerintegration
Internetintegration
Internetintegration
Integration with External Communication Systems
As a customer information system, IS-U/CCS enables you to integrate external communication systems in your daily work.
The following slides describe the three most important interfaces: Archiving of documents created in IS-U (for example invoices to customers, welcome letters, and so
on.), as well as archiving incoming (or outgoing) documents which are initially only available in paper form (faxes, letters, and so on).
Integration with a call center solution via the SAPphone component. Access to IS-U functionality via the Internet or via an intranet.
(C) SAP AG IUT110 18
2.19
SAP AG 1999
Identification InformationService function
Initiate workflow
Customer contactCustomer contact
Customizing
Front Office: Initial Screen X
Front office Edit Goto System Help
Search criteriaName: last/firstStreet/house numberPostCd/city/cntry
Business partnerActivity date
Tel. no.
Addr.Cat.Bus. part.Conn.obj.
Customer Premise
Call Description
Context Processes
Install. Technical
Identification Definable field selection Use AND to join fields Generic search with * Display results
Information Display of business objects Field representation of
severalbusiness objects Examples: customer,
contract account, contacts, bill and so on
Clipboard Temporary storage of
business objects Quick follow-up calls Good contextual
overview
Processes
Front Office processes R/3 workflow processes Examples: customer
change and service connection process
The IS-U/CCS Customer Interaction Center
The CIC is available in two different layouts. The CIC with different vertical screen areas (see above) is the standard layout. In the L-shape layout (see next page), selected sectors including utilities, media and telecommunications are available.
The CIC/Front Office screen is divided into four different areas: Clipboard (also called business data display):
Used to temporarily save processed business objects. Identification (search criteria, data finder):
This is where you enter search criteria to locate a business object. Examples of search criteria include a name, address or telephone number.
Information (business object display):Once the relevant business objects have been identified, various types of information can be displayed.
Processes: This is a list of change transactions, Front Office processes, and workflows which can be carried out for previously identified business objects.
(C) SAP AG IUT110 19
2.20
SAP AG 1999
IdentificationIdentificationIdentificationTelephonyfunctions
TelephonyTelephonyfunctionsfunctions Call
statusCall Call
statusstatus
Action boxAction boxAction box
Application area• Customer overview• R/3 transactions• User-defined HTML pages• Web pages
Application areaApplication area•• Customer overviewCustomer overview•• R/3 transactionsR/3 transactions•• UserUser--defined HTML pagesdefined HTML pages•• Web pagesWeb pages
Navigationarea
NavigationNavigationareaarea
Customer Interaction Center (L-Shaped)
The concept of the CIC (L-shaped) focuses on processing the business partner.
(C) SAP AG IUT110 20
2.21
SAP AG 1999
In the application area of the CIC
List of all work items to be performed
E-mail and fax inbox
Workflow Inbox
(C) SAP AG IUT110 21
2.22
SAP AG 1999
E-mail, fax, letters (scanned documents)E-mail, fax, letters (scanned documents)
WorkflowWorkflow
System System
Business partner
Work item in inbox for E-mail, fax, lettersWork item in inbox for E-mail, fax, letters
ConfirmationConfirmation
Call center agent
ExecutesExecutes
Customer data displayed in CICCustomer data displayed in CIC
E-Mail and Fax in the Workflow Inbox
(C) SAP AG IUT110 22
2.23
SAP AG 1999
Identification
Of:
Business partners and associated data such as connection objects
Supported by:
Data finder
Integration of external communication systems, such as CTI
Typical Uses of the CIC: Identification
The CIC enables customer service agents to quickly identify customer or processes, even if the customer details are incomplete.
CTI = Computer Telephony Integration
(C) SAP AG IUT110 23
2.24
SAP AG 1999
IdentificationIdentification Information
Supported by:
Modifiable lists
Information masks
Typical Uses of the CIC: Information
Once the customer has been identified, the agent can display information on the customer, his or her installations, as well as previous and current transactions.
(C) SAP AG IUT110 24
2.25
SAP AG 1999
Carry OutFront
Office Processesif Required
IdentificationIdentification InformationInformation
Supported by:
Predefined and company-specific business processes (for example name changes, changes to bank details, move-in processing, interim billing, various types of complaints)
Typical Uses of the CIC: Front Office Process
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.
In many cases, the business process can be carried out completely using one or more of these service functions.
(C) SAP AG IUT110 25
2.26
SAP AG 1999
Example: changing bank detailsExample: changing bank details
Changebank/paymentdata for a contractaccount
Changebank/paymentdata for a contractaccount
Log customercontactLog customercontact
Sequence of steps that can be processed:
by an agent
in one step
Front Office Processes
A Front Office process is a sequence of steps that is specially designed for processing a particular business transaction.
The lifetime of a Front Office process is limited to the lifetime of the Front Office session that initiated the process.
All steps in a Front Office process can be carried out by a customer service agent.
(C) SAP AG IUT110 26
2.27
SAP AG 1999
InitiateWorkflow
if RequiredIdentification Identification InformationInformation
Pre-defined workflows (for example service connection processing, administration of disconnection orders)
Customer-specific workflows (for example rate changes)
Typical Uses of the CIC: Workflow
PerformFront Office Processesif Required
PerformFront Office Processesif Required
Supported by the SAP Workflow Management System by means of:
If the business process cannot be fully processed immediately, the remaining steps of the process can be coordinated by means of a workflow.
IS-U/CCS contains a number of standard workflows. These can be modified to meet individual requirements.
You can also create your own workflows.
(C) SAP AG IUT110 27
2.28
SAP AG 1999
Billing agentBilling agent
Sales agentSales agentData in Data in
TechnicianTechnician
Letter ofnotification
I'd like tosign up for an off-peakrate.
Changecontract
Change/create(programmable)
meter
Checkfeasibility
Customer service agent
Customer service agent
Front Office:enter
inquiry
Using R/3 Workflow: Changing a Rate (Example)
(C) SAP AG IUT110 28
2.29
SAP AG 1999
Customercontact
log
Initiateworkflow
if necessary
Initiateworkflow
if necessary
Carry out servicefunction
if necessary
Carry out servicefunction
if necessary
IdentificationIdentification InformationInformation
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
Typical Uses of the CIC: Customer Contact
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.
(C) SAP AG IUT110 29
2.30
SAP AG 1999
Fax Letter Telephone
WWW
Internet In person
UtilitycompanyUtilitycompany
WWW
Recording of contacts resulting from:
Personal customer service, telephone calls
Correspondence, fax, Internet, e-mail
Evaluation of contacts for:
Comprehensive overview of customer service
Quality and efficiency of consulting processes
Contact Management in Customer Service
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, type and the corresponding activity.
(C) SAP AG IUT110 30
2.31
SAP AG 1999
Customer Contactin IS-U
General
Business partner Business partner Contact number
Communication
In person, telephone, fax, Internet, E-mail, online
Incoming, outgoing
References Reference to any
business objects Permissibility can be set
Notes
User-defined text Indicator for additional
documents
Additional Data Self-defined fields
such as division or company code
Authorization group
Customer Contact Data
Process Description
Date, time Contact class Activity
Contact classes and activities can be created according to the requirements of the utility company. Contact classes are used to group customer contacts according to their general subject area.
Example include information, billing, and budget billing. Contact activity describes the type of activity between the business partner and the utility company.
Example include rates information, account information, and so on.
(C) SAP AG IUT110 31
2.32
SAP AG 1999
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.
Contact management enables you evaluate the complete contact history of business partners
CIC: Unit Summary
(C) SAP AG IUT110 32
2.33Customer Interaction Center Exercises
Unit: Customer Interaction Center (CIC)
Topic: Using the CIC
At the conclusion of these exercises, 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, completely, and correctly. This increases both customer satisfaction and efficiency at work. A sound working knowledge of the CIC will help you achieve this.
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
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.__________________________________________________
1-2-3 The CIC dictates how the processes are handled.__________________________________________________
1-2-4 The CIC automates business processes.__________________________________________________
1-2-5 The data finder always identifies the business partner as the result of a search.__________________________________________________
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, enter the serial number in the Device data area.
To leave the data finder, choose Continue.
In the CIC, choose Continue again.
Enter the address of the connection object in which the device is located:________________________________________________________________________________________________________________________________________________________________________________________
(C) SAP AG IUT110 34
1-4 Which premises are contained in the connection object from task 1-3?
Proceed as follows:
In the navigation area (Environment tab page), select the premise. Choose the Connection object environment activity using the right mouse button.
Premise number Short text
1-5 End the contact.
1-6 Identify all the customers using the connection object on 0## Main Street. How business partners does the connection object contain?
Proceed as follows:
In the selection area, use the street of the connection object as the search criterion. Enter the street and house number. You can also make a partial entry, such as Main*. Confirm your entry by choosing Enter.
Business partner no. 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.
(C) SAP AG IUT110 35
1-8 From the data environment in task 1-7, save the devices belonging to the premise to the clipboard.
1-9 Display the data for the devices and complete the table below:
Information Electricity meter
Gas meter Water 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
Customer Interaction Center (CIC) Exercises
Unit: Customer Interaction Center (CIC)
Topic: Customer contact management
At the conclusion of these exercises, you will be able to:
Create various customer contacts
Evaluate and display customer contact history
By completely documenting all customer contacts, you will be able to provide a more efficient service to customers. The link to business objects allows you to access relevant information instantly.
2-1 Create a customer contact using the following information:
2-1-1 Customer TB010110## reports a complaint by telephone. You record the complaint in a customer contact.
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. Insert contract TB010110## and contract account TB010110##.
2-2 Display contacts
2-2-1 Display all customer contacts in the CIC for customer TB010110##. Check the list of object links. If necessary, switch to the detail display of the business object.How many contacts does the customer have? Of what type? ________________
Date Class Action Type
(C) SAP AG IUT110 37
2-2-2 Use the customer overview in the CIC to display the current customer contacts for customer TB010110##.
2-2-3 Evaluate all the customer contacts. Display all customer contacts entered with contact class 8 (complaint).
To do this, use the information system. From the SAP Easy Access menu, choose:
Utilities Industry Information System Report Selection } Customer Service List of Customer Contacts.
2-3 True or false?
2-3-1 All customer contacts are always created automatically.______________________________________________________
2-3-2 Customer contacts are divided into contact classes and further sub-divided into contact activities.______________________________________________________
2-3-3 Customer contacts can only ever be displayed for one business partner at a time.______________________________________________________
(C) SAP AG IUT110 38
Customer Interaction Center (CIC) Exercises
Unit: Customer Interaction Center (CIC)
Topic: Master data in IS-U/CCS
At the conclusion of these exercises, you will be able to:
Explain the central business partner model and how it is integrated in the R/3 System.
As an employee in customer services, you have been assigned to telephone service today. Some customers only wish to obtain information, but others want to have their data changed. You are using the CIC as your central working environment.
3-1 Customer TB010110## has two contract accounts. The following exercises are based solely on his Private Account 0##.The customer notifies you of new bank details that are to be used for bank collections for his private account.
Start from the CIC.
Use the customer overview
Process each step from the customer overview.
3-1-1 Enter the selection criteria, display the customer overview, and enter the current bank details for bank collections for the customer’s private account. Describe the menu paths and mouse actions you use for this procedure.________________________________________________________________________________________________________________________________________________________________________________________________________________________
3-1-2 Switch from customer overview to the change mode for the business partner, enter the new bank details, and save your data.Describe the menu paths and mouse actions you use for this procedure.__________________________________________________________________________________________________________________________________________________________________
(C) SAP AG IUT110 39
______________________________________________________
3-1-3 Switch from the customer overview to change modus for the contract account, choose the private account, and enter the new bank details as the payment method for incoming payments. Save your changes. Describe the menu paths and mouse actions you use for this procedure.Return to the CIC.
3-2 Customer TB010110## has two contract accounts. The following exercises are based solely on his Community Account 0##. The customer notifies you of new bank details that are to be used for bank collections for his community account.
3-2-1 In the navigation area ( Environment tab page), 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.____________________________________________________________________________________________________________________________________________________________________
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.________________________________________________________________________________________________________________________________________________________________________________________________________________________
3-2-3 Enter the new bank details as the payment method for incoming payments in the contract account and save your data. Describe the menu paths and mouse actions you use for this procedure.________________________________________________________________________________________________________________________________________________________________________________________________________________________
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.________________________________________________________________________________________________________________________________________________________________________________________________________________________
3-3 Change the contract description for residential electricity contract TB010130## of the community account.
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
description communal electricity contract 0##. Describe the menu paths and mouse actions you use for this procedure.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
End the contact.
3-4 (For countries with budget billing procedures): Customer Constance Bishop (TB010120##, Massachusetts Ave 0##), asks for information on her budget billings:
Enter the search criteria to identify the customer.
Call up the customer overview
Provide information on the budget billings.
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, installer, and contact person has to be entered more than once.______________________________________________________
3-5-2 A contract account can be assigned to several business partners.______________________________________________________
3-5-3 The contract account is the contract partner’s customer account.______________________________________________________
3-5-4 The contract contains rate data for all divisions.______________________________________________________
3-6 Name three different logs that are updated when master data is created or changed. List the changes for each log. To do this, use contract TB010130##.
1. __________________________________________________________
2. __________________________________________________________
(C) SAP AG IUT110 41
3. __________________________________________________________
(C) SAP AG IUT110 42
3-7 True or false?
3-7-1 The connection object is always a building.______________________________________________________
3-7-2 The connection object can comprise one or more premises.______________________________________________________
3-7-3 The connection object is managed as a piece of equipment in the Plant Maintenance component (PM)._____________________________________________________
3-7-4 The device location is subordinate to the connection object.______________________________________________________
3-7-5 Individual devices are installed in the connection object.______________________________________________________
3-7-6 The premise is managed as a functional location in 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.______________________________________________________
(C) SAP AG IUT110 43
2.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.
Unit 2: Navigation areaTask: Provides specific information in response to customer inquiries. Starts complex business processes, for example SAP Business Workflow.
Unit 3: Application areaTask: Provides overview pages containing inbox for SAP business workflow, CIC contact management, and so on.
Unit 4: Action boxTask: Calls specific business processes.
1-2
1-2-1 True. The CIC integrates both simple information and environment displays and workflow processes that are used to control comprehensive business processes.
1-2-2 True. The CIC enables you to enter a variety of information in order to find the data of a business partner. For example, you can determine a business partner by means of their name or by their device number.
1-2-3 False. The CIC is very flexible and is easily adapted and integrated with process flows for different user groups.
True. It supports the user in implementing processes.
1-2-4 True. CIC processes and workflow processes are integrated in the CIC. This means that business processes are controlled and forwarded automatically.
1-2-5 False. The data finder only identifies the business objects you were searching for. These objects must belong to a business partner.
(C) SAP AG IUT110 44
1-3 Call the CIC. From the SAP Easy Access menu choose:
Utilities Industry Customer Service Front Office/Customer Interaction Center Customer Interaction Center.
Activate the data finder by choosing
Open the Technical Data tab page.In the Device data area, enter the serial number TB010110## in the Serial number field.
Exit the data finder by choosing
Choose again. The first time you call the data, the system searches using the selection criteria. If the system finds data that meets the search criteria, the second data call confirms the search criteria. The system then displays the data. The system displays the connection object in which the device is located.All the master data belonging to the connection object is also displayed.
1-4 Select the premise in the navigation area (Environment tab page). The Choose the Connection object environment by clicking on the right mouse button. Choose Continue.
Premise number Short text
TB010110## 0## Massachusetts Avenue, Boston
TB010120## 0## Massachusetts Avenue, Boston
1-5 Return to the CIC (F3). Choose the End contact button.
1-6 In the identification area, search for the street of the connection object. Enter your search criteria. Since this connection object contains more than one business partner, all the business partners appear in the hit list.
Business partner no. First and last names of business partner
TB010110## Elmer Petersheim
TB010120## Constance Bishop
Choose Mr Elmer Petersheim. The data environment for the business partner is displayed. The answers are as follows:
(C) SAP AG IUT110 45
Question Answer
How many contract accounts are assigned to Mr Petersheim?
Mr Petersheim has two contract accounts:
Private account: TB010110##
Community account: TB010120##
Which types of contract does Mr Petersheim have?
Mr Petersheim has four utility contracts:
Electricity contract: TB010110##
Gas contract: TB010180##
Water contract: TB010120##
Electricity contract: TB010130##
Which devices are assigned to Mr Petersheim?
Mr Petersheim has 3 devices:
Double-rate meter: TB01011##
Water meter: TB01012##
Gas meter: TB01018##
1-7 Select the premise and choose Premise environment.
From the tree structure, you can identify the following relationships:
Four utility installations are allocated to the tree structure:, gas, water, and two for electricity. A utility contract, contract account, and business partner is allocated to each utility installation.
One electricity installation contains no devices. This is a flat-rate installation that does not measure consumption or energy. Meters are allocated to all the other installations.
1-8 You are in the environment of premise TB010110##. To save all the devices in the clipboard (corresponding tab page in the navigation area), repeat the following procedure for each device:
Click on the device. This selects the line. Choose To clipboard or F8. You have now added the object to the clipboard. Repeat for all devices in the premise. Once you have added all the devices to the clipboard, return to the CIC. To confirm your actions, call the Clipboard tap page in the navigation area.
1-9 On the Environment tab page of the navigation area, open the structure as far as the device level. To display a device, double click on it. You can now answer the following questions:
Information Electricity meter Gas meter Water meter
Serial number TB010110## TB010180## TB010120##
(C) SAP AG IUT110 46
Device category (or material) number
TD-DRA-00 TD-GA-00 TD-WA-00
Description of the device category or material
IS-U double-rate meterIS-U gas meter IS-U water meter
Division 01
Current business partners
TB010110##TB010110## TB010110##
Technical device location
TB010111DL0## TB010111DL0## TB010111DL0##
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
Solutions
Unit: Customer Interaction Center (CIC)
Topic: Customer contact management
2-1
2-1-1 Call the CIC.
Utilities Industry Customer Service Front Office/Customer Interaction Center Customer Interaction Center.
Select your customer. In the action box, call the Create contact function (call group Customer).
In the Class field, enter 8 (complaint).In the Action field, select 1 (unfriendly employee).
In the editor lines at the bottom of the screen, enter a reason for the complaint and save the contact.
2-1-2 Choose the action box call again.
In the Contact class field, enter 1001 InformationIn the Activity field, enter 1001 General information provided.Enter additional text on the information in the editor lines.
Change to the Business objects tab page. To add a link, press the Add object button. Choose an object role that refers to the Utility Contract object type. The system calls the data finder so that you can search for a specific contract.
Enter TB010110## in the contract field and choose Enter. The residential electricity contract has been added to the link list. Carry out the same procedure to add Contract account TB010110## to the link list. Save the contact.
(C) SAP AG IUT110 48
2-2
2-2-1 In the navigation area choose the Documents tab page. Choose Refresh. 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.
You can configure the system to display customer contacts in the application area; in the Customer overview tab page. The following contacts exist:
Date Class Action Type
08.10.98 Move-in New customer moves in
03.04.98 Move-in New customer moves in
03.04.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, call the Customer overview (call group Information) The most recent customer contacts are listed in the center table. By double-clicking on the individual customer contacts, you activate the detail display.
2-2-3 From the SAP Easy Access menu choose:
Utilities Industry Information System Report Selection } Customer Service List of Customer Contacts.
Enter the following search criteria: Contact class: 8 (Complaint). Choose Execute or F8. All contacts relating to complaints are displayed. Return to the CIC.
2-3
2-3-1 False. Customer contacts can also be created manually. The system creates the CIC contact automatically. To stop the customer contact being created, deactivate the contact log.
2-3-2 True.
2-3-3 False. The information system can analyze all customer contacts according to different criteria.
(C) SAP AG IUT110 49
Solutions
Unit: Customer Interaction Center (CIC)
Topic: Master Data in IS-U/CCS
3-1
3-1-1 Once you have identified the customer, call the Customer overview (call group Information).
Double-click on the account Private Account 0##. This brings you to the master data display of the contract account. Switch to the Payments/Taxes tab page.
In the data area Incoming Payments you can read the bank details for incoming payments in the field Bank details ID. Return to the customer overview.
3-1-2 Place the cursor in the address field of the business partner. Choose Change or F5. This brings you to the master data change screen for the business partner.
Switch to the Payment transactions tab page. Enter the new bank details.
In the ID field, enter GIRO and in the Cntry field, enter the key US . In the Bank key field, enter a bank sort code using F4. In the Bank acct field, enter an account number. Save your changes. You have now entered the new bank details for the business partner and have returned to the customer overview.
3-1-3 Position the cursor on Private Account 0##. Choose Change contract account. This brings you to the master data change screen of the contract account. Switch to the Payment/Taxes tab. Enter the new bank details for incoming payments.
Under Incoming payments, enter GIRO in the Bank details Id field. Double-click the Bank Details ID field. The new bank details are displayed (double-clicking refreshes the screen).
Save your changes. You have now defined new bank details for incoming payments and have returned to the customer overview. Return to the CIC.
(C) SAP AG IUT110 50
3-2
3-2-1 In the navigation area, select the second contract account. Call the Change bank data activity using the right mouse button.
3-2-2 This brings you to the business partner to record the new bank details. Switch to the Payment Transactions tab page. Now enter the new bank details. To do this, enter the key GEM in the ID field.
In the Cntry field, enter the key US. In the Bank key field, enter a bank using F4. Enter an account number in the Bank acct field. Save your changes. You have now entered new bank details for the business partner and are brought automatically to the previously chosen contract account.
3-2-3 Switch to the Payment/Taxes tab page. In the ID field, enter the key GEM . Double-click the Bank Details ID field. The new bank details are displayed (double-clicking refreshes the screen). Save your changes. You have now defined new bank details for incoming payments.
3-2-4 In the last step, you created a customer contact. Enter a comment in the editor lines at the bottom of the screen and save the changes.
3-3 In the navigation area, select the contract and choose the Change contract activity. Enter the new description Community electricity contract 0## in the Text Contract field. Save the changes and return to the CIC.
3-4
3-4-1 Choose the customer overview for business partner TB110110##. Position the cursor on the budget billing data. Double-click to display the budget billing plan.
3-4-2 The cumulative amount is located in the corresponding column. Return to customer overview.
3-5
3-5-1 False. You can use the SAP business partner model to assign different roles to a business partner. Only role-specific data which was not entered previously has to be added.
3-5-2 False. In IS-U/CCS, the contract account is configured in such a way that it can only be allocated to a single business partner. However, a business partner can have several contract accounts.
True. When you customize the contract account category, you can define the contract account so that it can be allocated to several business partners.
3-5-3 True. 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. A customer account is managed for a contract account.
(C) SAP AG IUT110 51
3-5-4 False. The contract is an agreement between a business partners and utility company which applies to a particular division. The contract contains control data for billing, the generation of budget billing plans, and for managing contract accounts receivable and payable. The rate data is stored in the installation and in the installation structure.
3-6 Enter the business partner key in the data finder and identify the business partner data. Double-click on contract TB010130## to display the master data. Here, 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. A connection object can also be a piece of property, a well, or a building site.
3-7-2 True.
3-7-3 False. The connection object is at the top of the hierarchy of functional locations.
3-7-4 True. Device locations are modeled as functional locations in the PM component and the connection object is the higher-level concept.
3-7-5 False. Devices are installed in device locations and are therefore indirectly allocated to a connection object.
3-7-6 False. The premise is used exclusively in IS-U/CCS to group together installations of different divisions.
3-7-7 True. Devices, registers, and fixed payment settlement factors, which are to be jointly billed, are grouped together and assigned to a premise. A premise can contain several installations. These can refer to the same or to different divisions.
3-7-8 True. The billing class and rate category are allocated to the installation. These influence how billing runs.
(C) SAP AG IUT110 52
3
SAP AG 1999
The business processes move-in, move-out, and move-in/out
Effects on both the business and technical master data
Contents:
Move-In/Out
You can enter all the data required for moving in or out using the pre-defined transactions move-in, move-out, and move-in/out. This enables you to process the whole transaction immediately, including sending the bill to the customer moving out and a welcome letter to the customer moving in.
(C) SAP AG IUT110 1
3.2
SAP AG 1999
At the conclusion of this unit, you will be able to
Describe the business processes move-in, move-out, and move-in/out.
Implement the business processes move-in, move-out, and move-in/out from the CIC
Explain the changes to the master data
Move-In/Out: Unit Objectives
(C) SAP AG IUT110 2
3.3
SAP AG 1999
A customer reports a 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
Move In/Out: Business Scenario
(C) SAP AG IUT110 3
3.4
SAP AG 1999
Move-in
Installation
Contract
Contractaccount
Businesspartner At move-in, a contract is
concluded for each installation selected at one or more premises
Move-In Definition
(C) SAP AG IUT110 4
3.5
SAP AG 1999
Connection object
Connection object
PremisePremise
InstallationInstallation
DeviceDevice
The following technical master
data must be entered before
move-in:
Connection object
Premise
Installation
The device can be installed
before move-in, but this is not
a prerequisite.
Move-In: Prerequisites
(C) SAP AG IUT110 5
3.6
SAP AG 1999
Business partner
Business partner
Contract account
Contract account
ContractContract
Should be re-used for existing customers
Can be re-used for existing customers
Is created during move-in
Move-In: Business Master Data
(C) SAP AG IUT110 6
3.7
SAP AG 1999
Customermoves in
Contract
Businesspartner, account
Welcomeletter
Meterreading
Customercontact
Customervisit/call
Validation
Budgetbillingplan
Move-incomplete
Security
Contract
Bank details 1
Payment method 1
Alternative payer 1
....FI-CA document 1
FI-CA document 3
31July
BB amount$250
Move-in
Mrs. Smith
Move-In/Out
Move-in
The Move-In Process
Essential steps for move-in Identify premise Identify or create customer Select contract account and edit or create account, 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.
Request cash security deposit
Create budget billing plan
Create welcome letter
(C) SAP AG IUT110 7
3.8
SAP AG 1999
Newcustomer
Newcustomer
CallCallinin
CICCIC
ExistingcustomerExistingcustomer
Front Office: Initial Screen X
Front office Edit Goto System Help
Search criteriaName: last/firstStreet/house numberPostCd/city/cntryBusiness partnerActivity date
Tel. no.
Addr.Cat.Bus. part.Conn.obj.
InformationEnvironment
Call Description
ChangeProcesses
Call Description
Context Processes
Parameters
Premise
Business partner
Move-in date
Special feature
Transfer of existing contract account possible
Parameters
Premise
Classification of new business partner
Move-in date
Move-In: Options for Processing
(C) SAP AG IUT110 8
3.9
SAP AG 1999
Basement
Apartment 2
Apartment 3
Apartment 1 Hall
Service connection: ElectricityService connection: GasService conn.: Water
Supplygrid
Street
Connection object
= Premise
Device locationBasement
Device locationBasement
Device locationHall
Device locationHall
Businesspartner
Installation 1:
Current meter
Installation 1:
Current meter
Installation 2:
Gas meter
Installation 2:
Gas meter
Installation 3:
Water meter
Installation 3:
Water meter
Contractaccount
Contractaccount
Contract 1:Electricity
Contract 1:Electricity
Contract 2:Gas
Contract 2:Gas
Contract 3:Water
Contract 3:Water
Move-In: The IS-U House
(C) SAP AG IUT110 9
3.10
SAP AG 1999
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
Move-Out: Business Scenario
(C) SAP AG IUT110 10
3.11
SAP AG 1999
Move-out Move-outcomplete
Customer reportsmove-out
Contact data
Contract Final meterreading results
Final billing
Budgetbillingplan
Move-outconfirmation
Customermoves out
Contract
Bank details 1
Payment method 1
Alternative payer 1
....FI-CA document 1
FI-CA document 3
31July
BB amount$250
X
X
The Move-Out Process
Essential steps for move-out: Identify and choose customer and contract Enter move-out date Enter final meter reading results
Optional steps for move-out: Add contact data Edit the customer moving out and the contract account Prepare and carry out final meter reading Carry out final billing immediately and print and issue final invoice Create move-out confirmation
IS-U will do the following for you: Terminate the contract Stop any budget billing collection Suspend any current dunning procedure Change any dunning procedures that may affect open items
(C) SAP AG IUT110 11
3.12
SAP AG 1999
Move-outMove-out
Call:Call:inin
CICCIC
Businesspartnermoves out
Businesspartnermoves out
Front Office: Initial Screen X
Front office Edit Goto System Help
Search criteriaName: last/firstStreet/house numberPostCd/city/cntry
Business partnerActivity date
Tel. no.
Addr.Cat.Bus. part.Conn.obj.
InformationEnvironment
Call Description
ChangeProcesses
Call Description
Context Processes
Parameters
Business partner
Move-out date
Parameters
Premise or
Business partner
Move-out date
Options for Move-Out Processing
(C) SAP AG IUT110 12
3.13
SAP AG 1999
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
Move In/Out: Business Scenario
(C) SAP AG IUT110 13
3.14
SAP AG 1999
Move-out Move-in
Transport
The Move-In/Out Process
(C) SAP AG IUT110 14
3.15
SAP AG 1999
Move-in/out forpremise
Move-in/out forpremise
CallCallinin
CICCIC
Move-in/out for business partner
Move-in/out for business partner
Front Office: Initial Screen X
Front office Edit Goto System Help
Search criteriaName: last/firstStreet/house numberPostCd/city/cntryBusiness partnerActivity date
Tel. no.
Addr.Cat.Bus. part.Conn.obj.
InformationEnvironment
Call Description
ChangeProcesses
Call Description
Context Processes
Options in Move-In/Out Processing
Parameters
Business partner
Move-out date
New premise
Move-in date
Parameters
Premise
Move-out date
Business partner or classification of new business partner
Move-in date
In the move-in/out transaction, you have the following processing options: Move-in/out for premise.You can process the move-out or move-in of two different business partners
into one premise. Move-in/out for business partner.You can process a move-out for a business partner from one premise
and their move-in to another premise.
(C) SAP AG IUT110 15
3.16
SAP AG 1999
Business partner
Business partner
Contract account
Contract account
ContractContractContract
Connection object
Connection object
PremisePremise
InstallationInstallation
DeviceDevice
Move-in
Move-In: Master Data
(C) SAP AG IUT110 16
3.17
SAP AG 1999
Move-out
Contract 2Contract 2Contract 2
02/01/.2000
Move-inMove-in
Nov 1st Dec 1st Jan 1st Mar 1st. Apr 1st May 1st Feb 1st
Customer1
Customer2
Customer2
Installation
Move-in
Contract 1Contract 1
No Changes to Installation Data
(C) SAP AG IUT110 17
3.18
SAP AG 1999
Current contract 10004714Current contract 10004714
No contract assignedNo contract assigned
Terminated contract 10004713Terminated contract 10004713
Terminated contract 10004711Terminated contract 10004711
Installation10815
Installation10815
01/01/90 - 08/14/1992
08/15/92 - 03/31/1993
04/01/93 - 12/16/1996
12/17/97 - 12/31/9999
01/01/90 - 08/14/1992
08/15/92 - 03/31/1993
04/01/93 - 12/16/1996
12/17/97 - 12/31/9999
Information on theinstallation's dataenvironment
Information on theinstallation's dataenvironment
Installation History
(C) SAP AG IUT110 18
3.19
SAP AG 1999
You are now able to:
Describe the business processes move-in, move-out, and move-in/out
Implement the business processes move-in, move-out, and move-in/out from the CIC
Explain the changes to the master data
Move-In/Out: Unit Summary
(C) SAP AG IUT110 19
3.20Move-In/Out Exercises
Unit: Move-In/Out
Topic: Move-In
At the conclusion of these exercises, you will be able to:
Perform the full move-in process in the system
Display the move-in document generated.
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, with today’s date as the start date.
1-1 A business partner moves in to a premise.
1-1-1 Identify the customerThe customer tells you that her name is Constance Bishop, living in Boston, and that she is moving into a new apartment, also in Boston. At present she is living in 0## Massachusetts Avenue in Boston, MA 02100. Identify the customer in the system. Once you have done this, the business partner should be available in the CIC.
1-1-2 Identify the new premiseMrs Bishop requires utility contracts for her new apartment 0## East Side Highway.Identify the premise into which Mrs Bishop is moving. (Once you have done this, you should be able to access the premise from the clipboard). Execute the Identify premise call that is located in the Identify call group (action box). In the Data Finder, choose the Technical data tab page and enter the street and house number in the connection object area. Choose Save Enter. If the system can determine a premise, it is displayed in the navigation area on the Clipboard tab page. Select the entry and display the object (right mouse click - Display).Enter the number of the premise here: _____________
Choose Environment Data, 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
Return to the CIC.
1-1-3 Perform the move-in. To do this, execute the M/in: known customer call under the Move I/O call group in the action boxPerform the move-in from the CIC . Use the business objects that you saved to the clipboard. Select both entries.
The system prompts you to maintain the move-in date in an additional step in the CIC (specify move-in parameters). Enter today’s date.
When you are asked, Do you want to adopt an existing contract account?, answer Yes.
Perform the move-in for all the installations in the premise.
You are now in the move-in processing screen.
Name/Admin. tab pageIn the contact data, record the fact that Mrs Bishop came by in person.
Bank data tab pageSince Mrs Bishop has confirmed that she will continue to use the same account, you do not need to make any changes here.
Payment Data tab pageCheck the payment methods that have been entered. Mrs Bishop has agreed that any credit may be transferred to her bank account. Change the outgoing payment method accordingly.
Contract Data tab pageEnter the following values in the new contracts:
To switch between the contracts, activate the Electricity, Gas and Water tab pages.
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
MR DataSince the meter reading at device installation was taken so long ago, the system does not automatically propose it as the meter reading at move-in. Therefore, use the Select All button to select all the registers and choose Estimate.
Save the move-in.
Return to the CIC by pressing F3.
1-1-4 Display the current business partner data.Choose Refresh in the navigation area (Environment tab page). The system displays the new data you have created. In the Documents tab page of the navigation area, choose Refresh. A new contact exists. Display this contact (double click on the object) and choose the Business Objects tab page. Here you can find the move-in document. Display this document and make a note of the document number:______________________________________________________
1-1-5 Customer overviewDisplay the customer overview for Constance Bishop. Note that both premises are visible in the lower part of the screen.
1-1-6 Customer environmentDisplay the customer environment for Constance Bishop.
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.______________________________________________________
1-2-3 The installation contains the move-in date.______________________________________________________
1-2-4 During move-in, a business partner and his/her contract accounts and contracts must already exist in the system. ______________________________________________________
(C) SAP AG IUT110 22
Exercises
Unit: Move-In/Out
Topic: Move-Out
At the conclusion of these exercises, you will be able to:
Perform the full move-out process in the system
Display the move-out document generated.
A customer telephones and informs you that she is moving out at the end of the month.
Perform the move-out from the CIC and enter the customer’s new address.
In addition, request a meter reading order.
2-1 Business partner move-out
2-1-1 Identify customerSarah Peterson lives in 0## Massachusetts Avenue in Boston, MA 02116.Identify the customer in the system. Once you have executed this step, the business partner should be available in the clipboard
2-1-2 Obtain an overview of the data environment of Mrs Peterson. To do this, choose the go to the selection area and choose either the Customer Environment or Customer Overview call.
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
2-1-3 Perform the move-outDo this from the CIC using the Move-Out Partner call under the Move-I/O call group. Use the Business partner Sarah Peterson business object that has been saved in the clipboard.
Move-out date
Last day of the current month
Address data tab pageEnter Mrs Peterson’s new address:
0## Independence Avenue in Boston.
MR Data tab pageGenerate a new meter reading order for the meters.
Save the move-out, return to the CIC and refresh the data.
(C) SAP AG IUT110 24
Exercises
Unit: Move-In/Out
Topic: Move-In/Out
At the conclusion of these exercises, 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, MA 02129 tomorrow.
The previous tenant moved out of the premise today.
Mr Jones reports the move-out and his subsequent move-in, and provides the meter readings for all the registers.
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.Harry Jones does not exist. Create the business partner in the selection area. To do this, 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
To enable each group to carry out the exercise, please attach your group number to the end of the first name. You should therefore subsequently search for Harry (0###) Jones.
Choose Save Enter. 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, MA 02129. Use the Connection Object Environment call under Information call group in the action box.
Find out who was previously registered as a business partner at that address.
Business partner number: _____________________________
Name: _____________________________________________
Select the premise and choose Copy to Clipboard or F8.
3-1-3 Perform the move-in/out
Do this from the CIC (Premise move-in/out). Use the business partner Harry 0# Jones and Premise 0## Constitution Avenue in Boston, MA 02129 business objects from the clipboard.
You are on the initial move-in/out screen. You can check the dates here (such as move-in or move-out date. Choose Save Enter.
You are now in move-out processing.
Enter the business partner’s new address:0## Apple Tree Lane in Washington D.C.
Move-out: tab page MR DataEstimate the meter reading results
Move-out: Save the move-out.
You are now in move-in processing.
Move-in: Bank data tab pageMr Jones has account number 08154711## at the Mellon Bank in Boston (under ID 1).
Move-in: Payment data tab pageMr Jones agrees to a direct debit and would like any credit balances to be transferred to this account.
Move-in: MR Data tab pageCheck the meter reading data. Have the move-out meter readings been
(C) SAP AG IUT110 26
transferred?What is the meter reading type?
Save the move-in.
3-1-4 Data environment for the premise following move-in/outDisplay 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).
Note that the contracts for the premise’s installations can be displayed historically.
(C) SAP AG IUT110 27
3.21Move-In/Out Solutions
Unit: Move-In/Out
Topic: Move-In
1-1 Business partner moves in to a premiseUtilities 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, M*, 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.
The business partner identified is now also displayed in the clipboard.
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
To display the desired premise information:
Select the premise in the clipboard and choose the Display call via right mouse click.
In the premise display, choose Environment Data.
The number of the premise is TB060110##.
Installation number Division
TB060110## Electricity
TB060120## Water
TB060170## Gas
Return to the Customer Interaction Center (using the F3 function key).
1-1-3 Peform the move-in
The business partner line on the clipboard is selected.
Select the premise line.
Choose the M/in: known customer call under the Move I/O call group.
Enter today’s date in the move-in date field. Choose Execute or F8.
When you are asked, Do you want to adopt an existing contract account?, answer Yes.
Confirm that you want to perform the move-in for all three installations on the premise by pressing Enter or the green checkmark.
Name/Administration: Contact data tab pageThe personal visit of Mrs Bishop to the customer center is saved under contact type. Using field selection (F4), choose the value Personal.
Payment data tab page
Field name Value
Outgoing payment. method
B
Bank ID – outgoing 1
(C) SAP AG IUT110 29
Contracts tab page
Division
Contract text
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.
1-1-4 Display the business partner data.
Proceed as described in the exercise.
1-1-5 Customer overview
Choose Customer overview from the Information call group.
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.
1-2 True or false?
1-2-1 False, since all steps can by carried out by one employee at the same time and without interruption.
1-2-2 True.
1-2-3 False, move-in and move-out dates are managed in the contract. However, the installation is assigned to a contract after move-in.
1-2-4 False. During move-in, a new business partner can be added and the contracts and contract account created.
(C) SAP AG IUT110 30
Solutions
Unit: Move-In/Out
Topic: Move-Out
2-1 Business partner moves outUtilities 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.
The business partner identified is now also found in the clipboard.
2-1-2 Navigation area: Customer overview and customer environment.
Choose Customer environment from the Information call group.
Return to the Customer Interaction Center.
How many contract accounts does Mrs Peterson have?
No. of contract accounts Contract account number
1 TB010140##
(C) SAP AG IUT110 31
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.
2-1-3 Perform the move-out
The business partner line on the clipboard is selected.
Choose the Move-out partner call that is found under the Move I/O call group.
Enter the move-out date
Maintain your data on the Administration/Name and Address Data tab pages.
Field name Values
Street Independence Avenue
House no. 0##
Post Code 69190
City Boston.
MR Data tab pageActivate the Service Notification/Order indicator.
Save the move-out.
Return to the CIC.
Update the Environment and Documents tab pages in the navigation area.
(C) SAP AG IUT110 32
Solutions
Unit: Move-In/Out
Topic: Move-In/Out
3-1 Move-in/out of a premiseUtilities 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, no object from category Business partner was found.
Create the business partner.
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.
Business partner Name
TB000110## Ashley Smith
Return to the Customer Interaction Center.
(C) SAP AG IUT110 33
3-1-3 Perform a move-in/out for a premise.
Select both objects from the clipboard.
Choose the Premise move-in/out call that is found under the Move I/O call group. You can correct any data here if necessary.
You start move-in/out processing by pressing Enter.
Move-out: Address data tab page
Field name Values
Street Apple Tree Lane
House no. 0##
Post Code 69190
City Washington D.C.
Move-out: MR data tab page
Select all registers
Choose the Estimate button.
Save the move-out document.
The system switches to process the move-in.
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. method D (Direct debit)
Bank details ID 1
Outgoing payment. method B (Outgoing paym./bank transfer)
Bank ID – outgoing 1
Move-in: MR Data tab pageThe meter reading type is 04 (derived meter reading).
Save the move-in document.
(C) SAP AG IUT110 34
3-1-4 The data environment of the premise after the move-in/out
New contracts
Division Contract Installation
01 Internally assigned contract number
TB000110##
03 Internally assigned contract number
TB000120##
Data environment from 01/01/1998 – to date
Press the button Period F7 and enter 01/01/1998 in the Valid from field.
(C) SAP AG IUT110 35
4
SAP AG 1999
Technical objects in Work Management
Customer-related Work Management(Installation services)
Interfaces to external systems
Contents:
Work Management
A large number of work orders are accepted, planned, calculated, carried out and if necessary, billed to a customer in a utilities company. IS-U uses functions which already exist in the various components of the R/3 standard system to manage these orders. 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. These functions are described extensively in the documentation for PM, e.g. in the online documentation and in the PM handbook under PM - The functions in detail.
(C) SAP AG IUT110 1
4.2
SAP AG 1999
At the conclusion of this unit, 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
Work Management: Unit Objectives
(C) SAP AG IUT110 2
4.3
SAP AG 1999
Acquisition, planning, calculation, execution of internal and external work orders
Creation of bills for customers
Examples:
Creation and extension of service connections
Energy consulting
Unscheduled meter reading
Disconnection and reconnection
Maintenance
Repairs
Installation, extension or removalof technical equipment
What Areas does the Work Management System Cover?
The day to day business of a utility company includes processing a large number of work orders. The orders must be accepted, planned, calculated, executed and when necessary, billed to a customer.
There are two different types of work orders; internal work orders and external work orders (which relate to Customer Service). External work orders are mapped with service orders in the Customer Service (CS) component. Internal work orders are mapped with plant maintenance orders in the Customer Service (CS) component.
(C) SAP AG IUT110 3
4.4
SAP AG 1999
Plant servicing
Plant management
Plant servicing
Plant management
Services for which Work Management can be implemented:
Typical services for private / commercial customers. .
Network servicesNetwork servicesNetwork services
• Power distribution• Installation• Electricity supply• Meter reading
•• Power distributionPower distribution•• InstallationInstallation•• Electricity supplyElectricity supply•• Meter readingMeter reading
GenerationGeneration TransmissionTransmissionTransmission DistributionDistributionDistribution
Utility Management Services
(C) SAP AG IUT110 4
4.5
SAP AG 1999
Technical objects
Installation services
Interfaces
Work Management: Technical Objects
(C) SAP AG IUT110 5
4.6
SAP AG 1999
Technical objects in the
supply area
PM/CSPM/CS
ISIS--UU
CustomerService
CustomerService
PlantMaintenance
PlantMaintenance
Description:
Technical objects in transmission and distribution
Example:
Transformer substations
Transmission lines
Transformer stations
Transformers
Switching stations
Description:
Technical objects with a direct reference to the customer can be reproduced in IS-U.
Example:
Connobj
Premise
Device location
Devices
Device relationship
Overview of Technical Objects
Object links: connections between individual systems Hierarchy between functional locations and equipment. Classifications: Describe technical data of all object types.
(C) SAP AG IUT110 6
4.7
SAP AG 1999
Field01
Field01
Field 02
Field 02
Field 03Field 03
Field 01
Field 01
Field 02
Field 02
Field 03Field 03
Field 01
Field 01
Field 02
Field 02
Field 03Field 03
Distribution station ST 435
(functional loc.)
Distribution station ST 435
(functional loc.)Distribution station ST
571Distribution station ST
571
Distribution station ST 768
Distribution station ST 768
Line no. 187(func. loc.)
Line no. 187(func. loc.)
Line no. 189Line no. 189
Line no. 186(func. loc.)
Line no. 186(func. loc.)
Line no. 188Line no. 188
Line network with subsections
Object connection used to connect two systems with different hierarchies
Distribution station with transformer fields
Supply Grid
Transformerfields
Transformerfields
Pylons(equip.)
(C) SAP AG IUT110 7
4.8
SAP AG 1999
Technical installations(equipment)
0539802
125.256.01
0716192
0539802
125.256.01
0716192
Connection obj.(func. loc.)
Premise
Connection (equipment)
Premise
Devices (equipment)
Dev. loc.(func. loc.)
Transformer(equipment)
Connection Object
The technical installation is division-dependent. A maximum of one technical installation can be created for each division in each premise. An
equipment is created in PM automatically. Since the technical installation is a piece of equipment, it can be subject to regular maintenance,
for example.
(C) SAP AG IUT110 8
4.9
SAP AG 1999
Technical objects
Installation services
Interfaces
Work Management: Services
(C) SAP AG IUT110 9
4.10
SAP AG 1999
PremisePremise
OFFOFF
ONON
meter no: 324561
meter no: 324561
reading : ______
reading : ______
Domestic installation services
Damage repairs
Monitoring of domestic installations
Device services (installation/removal)
Maintenance of appliances
Special meter readings
Reconnection/shutdown
Other on-site services
Installation Services
The tasks of installation services center around the connection object and the device location. Services may relate to equipment in the utility company or at the customer's installation, for example: Consulting, installing, maintaining, monitoring, extending
Own installations: connection, technical measure installation, ...External installations: heating, air conditioning, elevators, ...
Certification, meter reading Break-in protection, security, fire protection, elevators, installation control, energy consulting ...
(C) SAP AG IUT110 10
4.11
SAP AG 1999
Basic Structure of a Work Order
Examples: materials, quantities, units of measure,storage location, batch, item category, availability
Examples: work center, control key,description, standard time,activity type, wages
Equipment (assembly)Functional locationsMaintenance notifications
Processes
Examples: order type, dates, plant, reference object,priority, descriptionOrder headerOrder header
Object list
Material list
Billing rule
Costs (planned/actual)
Examples: protective clothing, crane, trafficlights, fire extinguisher,signs, excavatorProduction resources
Header data is information used to identify and administer work orders. This information applies to the whole order. Examples of header data are the order number, description, order type, dates for order execution, priority, the person who created the order and the person who last changed it.
The object list contains functional locations, equipment, assemblies, maintenance notifications, and/or materials with serial numbers. A single object can be entered in the order header as a reference object. In the object list, several objects can be entered.
Processes are used to describe the work to be carried out according to the order (the process includes the work center, the time required and the control key).
Materials are spare parts that are needed and used to execute the order. Production resources (e.g. tools, protective clothing, and special heavy goods vehicles) are also needed
to execute the order, but are not actually used in the order. The data in the billing rule states who is usually responsible for the costs. The data is taken from the
master record of the reference object. It can, however, be changed during the first steps of the billing process for the order.
The cost data informs you of the estimated costs, as well as the planned and actual costs of the order, the relevant cost categories for the order, the updating of key figures in the PMIS with value categories, and the updating of these key figures with actual costs.
(C) SAP AG IUT110 11
(C) SAP AG IUT110 12
4.12
SAP AG 1999
For service orders only
Entry/notification
Planning
Release
Printout
ConfirmationConfirmation
Technical completionTechnical completion
InvoicingInvoicing
Billing Billing
CommercialCommercialcompletioncompletion
Execution
Sequence of Order Processing
Processing starts when a customer or employee reports an outage, disruption or other request (such as a modification request). An order can be created directly, or on the basis of a notification.
Typical planning tasks include defining work processes, reserving replacement parts or defining working hours.
The order is then transferred for scheduling and control. Availability is checked, capacity required is provided and the necessary shop papers are printed.
Execution includes obtaining replacement parts from the stock and actually executing the order. Once work is complete, the actual times required to complete the work are recorded. Other
technical information is also entered to document repairs and define the status of the technical system. The order is then billed in Controlling.
Billing is performed prior to invoicing for a service order and a bill is created for the customer.
(C) SAP AG IUT110 13
4.13
SAP AG 1999
Sales viewPrice information
Description of energyresources for work, materials...
external resources
CharacteristicsValues
Dependencies
Connection objec,tdevice
Technicalobject
Configur.
Service order
Service product
Customerorder
Instructions
Service material
Service Product: Concept
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. These documents are linked using a service product. A service product is a service that is sold in SD and performed in PM.
You can assign a general maintenance task list to a service product. You can also specify a technical object (such as equipment) for which the service is to be performed.
The system copies the general maintenance task list and the technical objects into the service order in the PM component. You can use configuration in the customer order or the technical object to define and analyze individual instructions.
(C) SAP AG IUT110 14
4.14
SAP AG 1999
Instructions
1. Dig trenchTime: 0.5h per mTool: Excavator
2. Secure excavationOnly for soft ground
3. Lay cableMaterial: X m cable
4. Install connection boxesTime: 1hMaterial: Connection box
5. Fill trenchTime: 0.2 h per m
Configuration
Chars Values
Type of ground: Light
Length: 10m
Connection type A
Internal service Yes
Service material
Cable per m 60 UNI
Excavation per m 150UNI
Connection boxesType A 1,200 UNIType B 1,500 UNI
BB amount forinternal service 300
UNI
Service objectService object
Service orderService orderQuotation, customer orderQuotation, customer order
Service productService product
Service Product: Create Service Connection
(C) SAP AG IUT110 15
4.15
SAP AG 1999
IS-U/CCSIS-U/CCS
SD
PM/CS
FI-CAFI-CAFront officeFront office
OR
IS-U/CCSIS-U/CCS
W o r k f l o w M a n a g e m e n tW o r k f l o w M a n a g e m e n t
Workorder
Invoicing:installation
Supplyservices
Request forquotation
Quotation Order Billingrequest
Invoicing:Installation
services
Document
1
2
4
5
6
7
8
9
10
Qty Ordered
TotalSALESPERSONDATE
Sales Tax
Subt otal
TotalPrice
DescriptionQty Shipped
P.O. #:
PremiseCustomer
UTILITY BILL
CustomerCustomer
3
The Installation Services Process
Management of a service connection could be performed as follows:(1) A customer requests a quotation for the installation of a service connection. The customer service
representative identifies the customer in the CIC or creates the corresponding customer master record (if the customer is not already defined in the system).
(2) The customer service representative creates a customer quotation in the Sales & Distribution (SD) component.
(3) A quotation notification is created and sent to the customer. A service order can be generated automatically in the background in the CS component (6).
(4) The customer accepts the quotation.(5) The customer service representative generates a sales order. Order items can be automatically
transferred from the quotation.(6) A service order is created automatically in the background if this was not created with the quotation
(3).(7) The service connection is made on site.(8) If the service is invoiced according to consumption (i.e. if the actual costs incurred are to be billed), a
billing request is created in the SD component. (9) The invoice is triggered and posted in the SD component. If the service is not invoiced according to
consumption, but on a flat rate, the invoicing procedure is based on the sales order. As an alternative
(C) SAP AG IUT110 16
to invoicing in SD, it is also possible to create the invoice for the service in IS-U/CCS and to offset it with consumption billing.
(10) The invoiced amount is then entered as a debit amount in the FI-CA component.
(C) SAP AG IUT110 17
4.16
S A P A G 1 9 9 9
A c c e p tq u o t a t i o n
C r e a t e q u o t a t i o n
C r e a t e s e r v i c e o r d e r
C r e a t e s e r v i c e c o n n .
C u s t o m e r
A g e n t
A g e n t
A g e n t
A g e n t
C u s t o m e r
S y s t e m
T e c h n i c i a n
C r e a t e c u s t o m e r o r d e r
C o n f i r m s e r v i c e o r d e r
P a y m e n tT r i g g e r
i n v o i c i n g
W o r k f l o wW o r k f l o w
C r e a t e S e r v i c e C o n n e c t i o n
The "service connection" business process (such as new installation of a service connection or extension of an existing service connection) can be further divided into three subprocesses: Management of quotations Order processing Order completion and invoicing
The order processing subprocess includes the external customer order and the internal service order.
(C) SAP AG IUT110 18
4.17
SAP AG 1999
Technical objects
Installation services
Interfaces
Work Management: Interfaces
(C) SAP AG IUT110 19
4.18
SAP AG 1999
SCADASCADA
AM/FMGISAM/FMGIS
Decentralized resource planning
Decentralized resource planning
Outage analysisOutage analysis
WorkManagement
WorkManagement
R/3Standard
Applications
Service orders confirmations
Outagenotificationsand orders
Outageconfirmations
Transformer stationoutages
Connection information
Situation monitoring
Geographical data
Service ordersCompletion confirmations
MDI Mobile devicesMobile devices
Customer
service
Customer
service
Possible Configuration of an Interface Scenario
MDI: Mobile Data Interface SCADA: Supervisory Control and Data Acquisition GIS: Geographical Information System AM/FM: Asset Management / Facility Management
(C) SAP AG IUT110 20
4.19
SAP AG 1999
Transformerstation
Transformerstation TransformerTransformer
WMS
GIS
ConnectionConnection
DeviceDevice
Connection object
Connection object
Device locationDevice location
CCS
Object ID
Connectivityinformation
Object ID
Connectivity information:GIS BusinessConnector
Technical Objects in Work Management and GIS
(C) SAP AG IUT110 21
4.20
SAP AG 1999
Customer complains about a faulty device
Agent selects the service objectin the CIC
The service order, instructions, toolsand materials are sent to the responsible technician
Device Repairs
In the CIC you can trigger the generation of a repair order by first selecting the customer and starting the process.
You select the corresponding technical object from the displayed customer overview screen. The repair order is automatically created.
(C) SAP AG IUT110 22
4.21
SAP AG 1999
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 systems cna be used in
conjunction with Work Management
Work Management: Unit Summary
(C) SAP AG IUT110 23
4.22Work Management Exercises
Unit: Work Management
Topic: Service Orders
At the conclusion of these exercises, you will be able to:
Perform the Front Office process “Create service order”.
You will become familiar with a sub-area of Work Management.
1-1 Create a service order using the CIC.
1-1-1 Business partner Elmer Petersheim, Massachusetts Avenue0## in Boston reports a device fault. Create a service order (repair order). using the CIC.
Identify the business partner.
Under the Environment tab page in the navigation area, select the dual rate meter and access the Front Office process Create repair order by means of a right mouse click.
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 24
4.23Work Management Solutions
Unit: Work Management
Topic: Service Orders
1-1 Create service order.
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. Enter the data and confirm this by pressing Enter. By pressing Enter a second time, the customer data will be recorded in the Environment tab page. Expand the structure of Elmer Petersheim’s private account to the dual rate meter and select this. Access the front office process by right mouse clicking and choosing Create repair order.The service order is created in the background. Save the customer contact.Contacts and service orders are listed under the Documents tab page in the navigation area once you have pressed Refresh. You can display both documents by selecting them and choosing Display (right mouse click).
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).
1-1-3 The work center is recorded in the service order. Choose order display and display the Operations tab page.
(C) SAP AG IUT110 25
5
SAP AG 1999
Device category as the basis for device definition
Device category data and attributes
Integration in the standard R/3 System
Devices and registers
Device data
Integration in the standard R/3 System
Register data
Device lifecycle
Device inspection
Sample lot
Certification
Contents:
Device Technology
(C) SAP AG IUT110 1
5.2
SAP AG 1999
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
Device Technology: Unit Objectives
At the conclusion of this unit, you will be able to:
(C) SAP AG IUT110 2
5.3
SAP AG 1999
SAP Utilities
Technical modeling of complex devices and installation structures (such as integrated water meters, instrument panels)
Organization of billing-related data (such as rental prices, meter readings)
Recording of comprehensive device history as the basis for meter reading, billing, maintenance, and inspection
Controlling device stocks in terms of quantity and value, integration in Materials Management and Asset Management
Demands on Device Management
(C) SAP AG IUT110 3
5.4
SAP AG 1999
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
Device Management: Business Scenario
(C) SAP AG IUT110 4
5.5
SAP AG 1999
Device category as the basis for device definition
Devices and registers
Device lifecycle
Device inspection
Device Technology: Device Category
(C) SAP AG IUT110 5
5.6
SAP AG 1999
Single-rate meter that is subject to certification
Plastic housing and external seal
Six pre-decimal places, one decimal place
Serial numberSie-970701-503
Manuf. by Siemens
Prod. year: 1997
Valid from 01.07.97
Serial numberAEG-980101-125
Manuf. by AEG
Prod. year: 1998
Valid from Jan. 1, 1998
Serial no.LGY-980701-300
Manuf. by Landis&Gyr
Prod. year: 1998
Valid from July 1, 1998
Device category Device
The Device and the Device Category
(C) SAP AG IUT110 6
5.7
SAP AG 1999
=> Specific device data Device number/serial number Activity dates, such as installation, removal, or meter
reading Certification and maintenance data "Device" corresponds to "equipment" in the Plant
Maintenance (PM) component
=> Features of similar devices Definition of technical device data Recording of inspection and certification periods The device category corresponds to the material in
the MM component
=> Basic functions of device categories, such as: Meters Transformers Pressure regulators
Basic device cat.Basic device cat.
Device category 1Device category 1
Device category 2Device category 2
Device 1Device 1
Device 2Device 2
Device 3Device 3
Modeling of Devices
Examples of basic device categories: Meters measure consumption Transformers convert. (Example: electrical voltage) ARCRs (audio frequency ripple control receivers) transmit information via the electricity grid by
means of audio frequency modulation. Remote meters measure consumption from a distance Counters calculate heat quantities generated in district heating Correctors calculate standard cubic meters from gas values Pressure regulators adjust gas pressure Sensors act as pulse generators, e.g. temperature sensors
(C) SAP AG IUT110 7
5.8
SAP AG 1999
IS-UDevice management
IS-UDevice management
Device categoryDevice category
DeviceDevice
LogisticsLogistics
MaterialMaterial
EquipmentEquipment
Integration with Logistics
IS-U functions of device management include: Technical data such as the register group, the input/output group, and command group and so on. Installation, as well as removal and replacement of devices Installation structure for modeling devices and register relationships, in addition to rate data Organization and carrying out of meter readings in the service territory Inspection: sampling procedure, certification, periodic replacement
Integration of IS-U/CCS Device Management with the standard R/3 Logistics component makes it possible to use the following: Inventory Managment (MM-IM component) Purchasing (MM-PUR component) Warehouse Managment (MM-IM and MM-WM components) Plant Maintenance (PM component) Classification system
(C) SAP AG IUT110 8
5.9
SAP AG 1999
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.
Definition of Device Category
(C) SAP AG IUT110 9
5.10
SAP AG 1999
MM data IS-U data
Device category
Planning
• Procurement planning• Price estimate• Forecasts
Logistics• Storage• Warehouse management• Transport data• Quality management
Basic data
• Description of material• Value, price• Allocated documents
General• Construction class• Function class• Price class• Notes
Additional datadependent on basic device category
• Register group• Winding group• Input/output group
Certification
• Certification requirement• Certification period
Device Category Data
(C) SAP AG IUT110 10
5.11
SAP AG 1999
MaterialMM
Device categoryIS-U
Input/output group
Register groupRegister group
Winding groupWinding group
Command group
Informative
Possible Elements of the Device Category
Function-relatedFunction-related
Certain functional element groups are required, depending on the basic device category. Examples: Devices of the basic device category METERS must be allocated to a register group. However, an
input/output group may be assigned for technical descriptions of the available device interfaces, if desired.
Allocation of a winding group in which the billing data is recorded is obligatory for devices of the TRANSFORMERS basic device category. An input/output group can also be maintained for information purposes (such as for service technicians), if required.
Data on device category elements can be arranged according to division category (the reactive current/active current indicator can for instance only be maintained in the register group of the electrical division).
(C) SAP AG IUT110 11
5.12
SAP AG 1999
Device category as the basis for device definition
Devices and registers
Device lifecycle
Device inspection
Device Category: Device and Register
(C) SAP AG IUT110 12
5.13
SAP AG 1999
A device is an instrument that is used to measure consumption, process data, or control and protect other instruments.
Devices are managed in the Plant Maintenance (PM) application component as pieces of equipment with serial numbers.
Device
Device category
Definition of Devices
(C) SAP AG IUT110 13
5.14
SAP AG 1999
PM IS-U
Plant maintenance• Maintenance plant• Maint. planning plant• Maint. planner group• Main work center
Processes• Maintenance orders• Service orders• Messages• Capacity planning
General• Inventory number• Weight/volume• Reference data• Manufacturer data• Stock information
General• Device category, basiccategory
• Lock status• Change documents• Time slices
Device-specific data• Group data, prod. year• Manufacturer, cat.desc.• Ownership status• Certification data
Processes• Installation and removal• Modification and disconnection
• Certification• Meter reading
Device
• Material and serial no.• Equipment category and number
• Status
Header data
Device Data
The device master record is divided into various sections (tabs): General data: technical data, reference data, manufacturer data Location data: area assignment and account assignment elements IS-U data:
Technical data: register group, winding group, command group (depending on the device basic category)Certification /inspection data: year of certification, certification status, lot, year of replacement, inspection statusProcesses: installation, removal, modification, and disconnectionMaster data: business partners, connection object, device location, location, premisesMeter reading results, designated plantsSerialization data: allocated to material and serial number with stock information, plant and location.
When devices are moved (e.g. goods receipt, goods issue, installation, removal), the equipment status is updated (ESTO, AVLB, INST). The status of the device informs the user that a certain business process has been performed. (Example: ESTO means that the device was entered in the system via a goods receipt posting and is available in a warehouse).
(C) SAP AG IUT110 14
5.15
SAP AG 1999
A device that meters consumption, energy, and so on.
This can refer to the actual instrument or simply the display in an electronic device.
The register is identified by a register number in the device.
Device
Register
Device category
Definition of a Register
(C) SAP AG IUT110 15
5.16
SAP AG 1999
Technical data Process data
General• Register category• Register type (time zone)• Pre-decimal places• Decimal places
Technology• Quantity unit• Register code, such asreactive energy or active power
• Display type, transformer
Meter reading
• Number of meter readingresults per meter reading
• Indicator: nonmetering register
Register relationships
• Relationship type• Relationship register• Operation code
Meter readings
• Recorded meter reading • Estimated meter reading• Multiple allocation
Meter reading• Reason• Type of reading, meterreader
• Date• Status
RegisterRegister
Registerconfiguration
Sample registerrelationship
Register Data
Examples of register relationships: Active/reactive relationship Serial switching relationship On-peak/off-peak
relationship Control relationship VCF relationship (thermal gas billing) VCF calculation relationship (thermal gas billing)
You can assign individual validations to each register relationship to check the meter reading results.Example: Meter reading results from two registers that are connected by a control relationship can only differ by a maximum of 1%. If this tolerance is exceeded, the meter reading result is not accepted and is assigned the status "implausible".
(C) SAP AG IUT110 16
5.17
SAP AG 1999
Device category as the basis for device definition
Devices and registers
Device lifecycle
Device inspection
Device Technology: Device Lifecycle
(C) SAP AG IUT110 17
5.18
SAP AG 1999
Billingdocument
(Utility supply)
FI-CAdocument
FI-CAdocument
IS-UIS-U
FI-CAFI-CA
Cross appl.Cross appl.
ContractaccountContractaccount
Businesspartner
Regionalstructure
Connectionobject
Connection
Device location
Premise
Contract(Utility supply)
Installation
Device
RegisterIntegrationwith Logistics
Devicecategory
MRservice
Register group
Point of delivery
Central Data Objects - Integration in Logistics
(C) SAP AG IUT110 18
5.19
SAP AG 1999
MMMM
ISIS--UU
Device managementInstallation
PurchaseorderPurchaseorder
GoodsreceiptGoodsreceipt
Goodsissue
Goodsissue
TransferTransfer
InstallationInstallationInspection/
certification/reprogramming
Inspection/Inspection/certification/certification/
reprogrammingreprogramming
Removal/replacement
Removal/replacement
RetirementRetirement
PMPMPurchase
requisitionPurchase
requisition
Device Life Cycle
Devices are created in an integrated system using standard R/3 components, such as Purchasing (MM-PUR), Inventory Management (MM-IM) and Plant Maintenance (PM). Devices are created as pieces of equipment in the system by posting a goods receipt for any number of devices of a particular device category. The entire goods procurement process can be performed in an optional first step (purchase requisition ordering and so on). A prerequisite is that the device category has already been created and therefore exists as a material master in the MM component. The serial number profile of the material master (in Customizing) ensures that the device in question is supplied with the necessary IS-U data.
If the Materials Management (MM) component is not implemented, it is also possible to create devices directly in IS-U/CCS. However, IS-U/CCS does not provide inventory management functionality.
Although device installation is performed within IS-U/CCS, it is, however, based on a modified version of the PM component.
(C) SAP AG IUT110 19
5.20
SAP AG 1999
MMMM
Purchasing: purchase orders, inquiries/quotations, outline agreements Warehouse logistics: transport, stocktaking, transfer posting Inventory management: goods movement, reservation Valuation, stocktaking, material requirements planning
PMPM
Maintenance of technical objects and equipment Work planning, maintenance planning Maintenance processing
CSCS
Service contracts: contracts, maintenance plans Service processing: notifications, orders, completion
confirmations Service planning: scheduling, work plans
Specification of the device: device category, device Installation: installation, removal, replacement, installation structure Meter reading: organization, meter reading orders, entry of meter
reading results Inspection and certification: internal or external periodic replacement
procedure or sampling procedure
IS-UIS-U
Documentation for the Device Lifecycle
(C) SAP AG IUT110 20
5.21
SAP AG 1999
Device category as the basis for device definition
Devices and registers
Device lifecycle
Device inspection
Device Technology: Device Inspection
(C) SAP AG IUT110 21
5.22
SAP AG 1999
SAP Utilities
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 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 alldevices or a sample of devices.
Introduction: Device Inspection and Certification
(C) SAP AG IUT110 22
5.23
SAP AG 1999
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
Siemens
Property no..
SIE-$/)($%)/
Siemens
Property no..
SIE-$/)($%)/
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
Periodic replacement list4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
Replacement orders for all devices
Replacement orders for sample devices and spare sample devices
4567,8
4567,8
4567,8
Sample4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
4567,8
Siemens
Property no..
SIE-$/)($%)/
Devicecategory
B
Devicecategory
A
Certification Procedures Overview
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
SAP AG 1999
Certificationof devices
Periodicreplacement
list
IS-U
Sample
Certification Procedure
Description:
Only a representative sample of devices is removed for inspection and replaced.
Procedure:
Create lot
Compile lot
Determine lot devices
Perform first drawing
Inspection
Description:
Devices due for certification are removed completely and replaced by identical devices.
Procedure:
Create periodic replacement list
Select device categories
Create list in foreground or background
Replacement orders created automatically
(C) SAP AG IUT110 24
5.25
SAP AG 1999
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
Sampling Procedure
(C) SAP AG IUT110 25
5.26
SAP AG 1999
Createlot
Createlot
Compilelot
Compilelot
Determinelot devicesDeterminelot devices
Conductfirst
drawing
Conductfirst
drawing
Certifyinspection
devices
Certifyinspection
devicesBreak up lotBreak up lot
Transferdevices to
PRL
Transferdevices to
PRL
Check inspection
devices
Check inspection
devices
Conductseconddrawing
Conductseconddrawing
Renewlot
Renewlot
yesno Inspectionpassed?? ??
Inspection Using the Sampling Procedure
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
SAP AG 1999
Rem
oval
Ins
talla
tion
In periodic replacement, devices that are to be certified are removed, and replaced by the same kind of devices.
Devices that are to be replaced are 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.
Periodic Replacement
The periodic replacement component is optional. It is needed if:Devices are to be certified individuallyA lot does not exist for the sampling procedure, and the devices have to be certified individually
(C) SAP AG IUT110 27
5.28
SAP AG 1999
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.
Device Technology: Unit Summary
(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
1-2 Display all devices for customer TB010110## and select the double-rate electricity meter.
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-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. ______________________________________________________
______________________________________________________
1-4 Display the material master data for device TB010110##. (Comment: the device category – i.e., the material – is assigned to Plant “U003”).
(C) SAP AG IUT110 30
1-5 True or false?
1-5-1 Device technology is integrated into the R/3 logistics component.______________________________________________________
1-5-2 Devices are based on a basic device category.______________________________________________________
1-5-3 Device categories group together similar devices.______________________________________________________
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-7 Devices can be allocated to more than one lot.______________________________________________________
1-5-8 Only the sampling procedure can be used when inspecting devices for internal and external purposes.______________________________________________________
(C) SAP AG IUT110 31
5.30Device Technology Solutions
Exercises: Device Technology
Topic: Creating and Delivering Devices
1-1
1-1-1 Select the customer in the Customer Interaction Center. Select the premise in the navigation area. Choose Premise environment (right mouse click). Expand the sub-tree and double-click the device TB010120##. The device category is displayed on the IS data tab page. Do not leave this screen.
1-1-2 After pressing the MR results button, all the readings are displayed.
This lists all meter reading results. Return to device display.
1-1-3 You are located in the device display for TB010120##. Double-click on the Register group field (tab page Group). The master data for the register group is displayed. You can obtain information on the number of registers and their technical specifications and functionalities from the table entries. Return to the premise environment.
1-2
1-2-1 Double-click on Double-rate electricity meter.The data environment of the meter is displayed.Double-click on the device TB010110##.Switch to the IS data tab page.On the lower set of tabs, switch to tab page Cert/ins. data. The field Next repl. year displays the year in which the device must next be certified, either internally or externally. Do not leave this screen.
1-2-2 In the IS-data view, choose the Ins. data tab.If the Lot field is filled, the device has been allocated to a lot. Otherwise, a lot has not yet been allocated.Do not leave this screen.
1-2-3 In the view IS data Ins. data.If the Samp.dev.status field is empty, the device has not yet been drawn as a sample device.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-4 The calibration validity is stored in the device category.Double-clicking the on Device category field displays the material data for the device.Switch to the Cert./order data tab page. The calibration validity is displayed in years. This is used to calculate the next year of replacement.In the Int. cert. per. field, the internal certification period is displayed. This shows the internal period set by the company, after which a device must be re-inspected and certified.
1-3 Choose the Mast. data tab page.
1-3-1 The current connection object is TB010110##.
1-3-2 The current device location is TB010111DL0##.
1-3-3 In the menu, choose Structure Structure graphic or Strg F7.
When a dialog box appears with the question “Expand structure upwards?” choose “Yes”.You are now looking at an illustration of the structure. Here you can further expand the structure using the Levels above button.The current connection object is TB010110##.
1-4
Determine the device category of the device TB010110## in the device master data.
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.
Select all views and confirm the entry.
As materials are always defined for a specific plant, you must also specify the plant. Enter the plant key U003 and confirm it.
1-5
1-5-1 True. IS-U device technology is integrated in the components MM, PM and CS.
1-5-2 False. Devices are based on a device category, which in turn consists of one or more basic device categories.
1-5-3 True.
1-5-4 True. The device category is managed in the component MM using the material number.
(C) SAP AG IUT110 33
1-5-5 False. Register groups are assigned to the device category. However, these not only have an informative purpose, but also a functional purpose and are used for processing and inspecting meter reading results. For example, validation checks for the number of premises, possible meter reading overflows or when converting results depending on the transformation relationship.
1-5-6 True. The device is managed in PM using the serial number.
1-5-7 False. Devices can only be allocated to one lot.
1-5-8 False. In addition to the sample procedure, the periodic replacement procedure can also be used.
(C) SAP AG IUT110 34
6
SAP AG 1999
Device installation/removal/replacement
Technical installation/removal
Billing-related installation/removal
Installation structure
Device allocations
Register relationships
Contents:
Device Installation
(C) SAP AG IUT110 1
6.2
SAP AG 1999
At the conclusion of this unit, you will be able to:
Describe and perform device installation, removal, and replacement. You will also be able to describe how these functions are integrated with the Service Management (SM) application component.
Explain the relationship between the connection object, the device location, and the device, and how they are integrated in the Plant Maintenance (PM) application component.
Display devices of an installation and describe the installation structure.
Device Installation: Unit Objectives
(C) SAP AG IUT110 2
6.3
SAP AG 1999
Device installation if replaced periodically
Create and plan service orders
Execute service orders: Remove old devices and install new ones (device replacement)
Device Installation: Business Scenario
(C) SAP AG IUT110 3
6.4
SAP AG 1999
Device installation, removal and replacement
Installation structure
Installation: Installation, Removal And Replacement
(C) SAP AG IUT110 4
6.5
SAP AG 1999
Generation ofwork ordersto replace
the devicesaffected
Generation ofwork ordersto replace
the devicesaffected
Team leaderfield force
Team leaderfield force
Deviceinspection agent
Deviceinspection agent
Field forceemployee
Field forceemployee
On-site technical execution of the order
and completion confirmation of the order in the system
On-site technical execution of the order
and completion confirmation of the order in the system
Team leaderfield force
Team leaderfield force
Changes to datain the system("full device
replacement")
Changes to datain the system("full device
replacement")
Deviceinspection agent
Deviceinspection agent
Technical conclusion of the service order and triggering of the
invoice
Technical conclusion of the service order and triggering of the
invoice
Sample devices in a lot must be replaced for certification
Sample Sample devices in a devices in a lot must be lot must be replaced for replaced for certificationcertification
Planningthe
work orders
Planningthe
work orders
Business Scenario: Replacement of Sample Devices
Devices of a particular device category are due for certification. After the sample devices are defined using the lot procedure, the corresponding work orders are automatically generated for the removal of these devices. The work orders contain a complete description of the process, as well as a list of materials and resources that may be needed.
The work orders are then scheduled for execution, taking resource capacities and deadlines into account. In the next step, 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. As soon as the work order is executed, it is documented accordingly in the system by means of a
completion confirmation. 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, if necessary.
(C) SAP AG IUT110 5
6.6
SAP AG 1999
Executeserviceorder
Determinedevice location
The device location indicates where a device is installed in the
connection object.
The address of the connection object links the device location to
regional structure.
The location can be specified in more detail using location data,
location supplement, and a long text. The service order is used to
forward this information together with the address data to the field
force employee.
The device location is a functional location in the PM application
component.
The structure of the functional locations and the equipment (devices)
installed provides a comprehensive overview of the technical
systems installed.
Service Order Execution: Determining the Device Location
(C) SAP AG IUT110 6
6.7
SAP AG 1999
Connectionobject
Device location
Device
The device location is the location in the connection object that is independent of a division and in which any number of devices can technically be installed.
Executeserviceorder
Determinedevice location
Definition of the Device Location
(C) SAP AG IUT110 7
6.8
SAP AG 1999
Device location
Reference to premise
• The device location can be allocated to a premise if required
Integration with PM• The device location is
defined as a functional location below the connection object
Independent of division
• Installation location fordevices of all divisions
• Installation location forall device categories
Location data
• Exact location and location supplement
• Long text• Link to regional structure
Device Location Data
Executeserviceorder
Determinedevice
location
(C) SAP AG IUT110 8
6.9
SAP AG 1999
PM objectsIS-U objects
Device Device locationlocation
LowerLower--levellevel
Functional locationFunctional location
DeviceDeviceEquipmentEquipment
DeviceDevice
ConnobjConnobjHigherHigher--levellevel
Functional locationFunctional location
EquipmentEquipment
ConnectionConnection
Legend
Installation of equipment Hierarchical relationship between functional locations
Relationships Between Technical Objects
Executeserviceorder
Determinedevice location
(C) SAP AG IUT110 9
6.10
SAP AG 1999
meter no: 324561
meter no: 324561
reading : ______
reading : ______
Executeserviceorder
Performdevice
replacement
Determinedevice location
Confirmserviceorder
Serviceorder
executed
The field force employee performs an on-site meter reading for the sample device and then physically removes the device.
The new device is installed in the device location. Since the new device has to perform the tasks and functions of the old device, it must be identical from a technical point of view.
A function test is performed and new meter readings can be taken as a basis for billing.
This concludes the technical aspect of the service order and the field force employee enters the corresponding completion confirmation in the system.
Service Order Execution: Device Replacement & Service Order Confirmation
(C) SAP AG IUT110 10
6.11
SAP AG 1999
Executeserviceorder
Determinedevice location
Serviceorder
executed
Changedata in system
Locateinstallation
Performdevice
replacement
Confirmserviceorder
The Back Office employee responsible receives the completion confirmation for the service order in electronic or paper form. The completion confirmation contains all the central information for any data changes required in the system.
The customer service representative can locate the installation affected using the device number of the device removed and start the "Full replacement" transaction using the following data:
Device location
Installation
Activity date
Device number of the sample device
Device number of the new device
Data Changes: Installation Location
(C) SAP AG IUT110 11
6.12
SAP AG 1999
Executeserviceorder
Determinedevice location
Serviceorder
executed
Changedata in system
Locateinstallation
Performdevice
replacement
Datachange
completed
Performdevice
replacement
Confirmserviceorder
The customer service representative enters the meter reading from the device removed and the meter reading at installation of the new device. This ensures that there are no gaps in the consumption history, which provides the basis for billing.
Once the data has been saved, the device replacement is complete.
Data Changes: Device Replacement
The following steps are performed automatically in the background for a device replacement: Billing-related removal of the old device: This terminates the business relationship between the device
and the business partner's installation (and therefore the contract). Technical removal of the old device: This removes the link to the device location, (and therefore to the
connection object). All existing register relationships are terminated and the current time slice for the device is removed. At the same time, a new time slice begins. The status in the device master record is changed from EEGB (equipment installed) to EFRE (equipment free).
Technical installation of the new device: The connection of the new register to the device location (and therefore the connection object) is established. The device receives the status EEGB. At the same time, a new time slice is opened for the device, beginning on the installation date. Any register relationships are transferred from the old device to the new meter.
Billing-related installation of the new device: The new device is connected to the business master data (installation, contract, business partner). Data that is relevant to rates (such as the rule for determining the settlement price, rate data at device and register level, information about extrapolation of consumption values) is transferred to the new device.
Processing steps that are performed automatically for a device replacement can also be performed separately (for instance by different customer service representatives). Individual transactions, such as technical installation, billing-related installation, and full installation (= both steps in one transaction) can be used to perform each step of the installation and removal processes separately.
(C) SAP AG IUT110 12
(C) SAP AG IUT110 13
6.13
SAP AG 1999
Businesspartner
Businesspartner
ContractaccountContractaccount
Installation1
Installation1
Installation2
Installation2
Contract 2(Company code 2)
Distribution and customer service
Contract 2(Company code 2)
Distribution and customer service
Contract 1(Company code 1)
Generation andtransmission
Contract 1(Company code 1)
Generation andtransmission
PremisePremise
DevicelocationDevice
locationConnection
objectConnection
objectDevice 1
Billing-relatedinstallation
Technicalinstallation
Billing-relatedinstallation
Technical and Billing-Related Installation
Devices can be allocated to several installations from a billing perspective (billing-related installation). However, each device can be allocated to only one device location from a technical point of view (technical installation).
In the example above, the utility services of the division are divided into two areas, each of which is supplied by a different service provider. These two basic services are "generation and transmission'" and "distribution and customer service". The contracts for each of these basic services are managed under different company codes. This model clarifies how deregulated energy supply can be reflected in IS-U/CCS. The billing-relevant data in the utility installation and in the installation structure can be established individually for both contracts. Since one contract exists per installation, a separate installation in the relevant division is created for each contract. Accordingly, any meters installed are allocated twice from the point of view of billing. When both contracts are managed in the same system, one of the companies can carry out billing and customer service on behalf of the other, or a third company can carry out these tasks for both companies. The customer then receives only one bill for both services and has one contact person for all queries.
(C) SAP AG IUT110 14
6.14
SAP AG 1999
Device installation, removal and replacement
Installation structure
Installation: Installation Structure
(C) SAP AG IUT110 15
6.15
SAP AG 1999
Supplygrid
Street
Electricity
Audio frequency ripplecontrol receiver
Device allocationRegister relationship
Electricity
Serial switching
Example of an Installation Structure
The installation structure comprises all technical and billing-related data for a utility contract. In the example above, switching between the two rates of the double-rate electricity meter is controlled
by an ARCR (audio frequency ripple control receiver). For information purposes, this is described in the system as a device allocation of the ARCR type. At the same time, one of the registers of the double-rate electricity meter has a serial switching relationship with another register. The consumption of the serial switching register (secondary register) is automatically deducted from the consumption of the main register during the billing run.
(C) SAP AG IUT110 16
6.16
SAP AG 1999
Device allocations Register relationships
Reactive/activerelationship
Serial switchingrelationship
On-peak/off-peakrelationship
Control relationship
VCF relationship
VCF calculationrelationship
Customer-specific relationships
Audio frequency ripplecontrol receiver
Transformers
Pressure regulator
Customer-specificallocations
Technical Installation Structure
Device allocations describe relationships between installed devices. A device allocation is always composed of a controlling and a controlled device (Example: A calculation factor, which is taken into account in consumption billing, is defined in the installation structure at register level for the "transformer" allocation category).
In a reactive/active relationship, all active registers of a register category and all reactive registers of the same register category are added and the total is used to perform the cosine phi examination.
The serial switching relationship is automatically subordinate to all other relationships during meter reading and validation.
The on-peak/off-peak relationship describes the relationship between registers of different register categories (e.g. on-peak and off-peak registers).
In a control relationship, all registers are added and the totals compared with the designated control register.
The VCF relationship (gas division only) is needed for billing difference quantities that result from different meter readings for the operating volume meter of the corrector and another external operating volume meter.
The VCF calculation relationship (gas division only) is needed for billing difference quantities that result from different meter readings for the operating cubic meter meter of the corrector and another external operating cubic meter meter.
(C) SAP AG IUT110 17
6.17
SAP AG 1999
Rate data
Relevance to
settlement price
Relevance to billing
Price class
Rate type
Rate fact group
Discount
Extrapolation data
Expected period
consumption
Fixed consumption
values weighted linearly
(absolute or relative value)
Billing-Related Installation Structure
Rate and extrapolation data are usually determined during maintenance of the installed device. However, these can be changed at any time under "installation structure" in the menu. During device installation (or afterwards), the "relevance to settlement price" indicator determines
whether a settlement price should be charged or not. If the "relevance to billing" indicator is activated at register level, a plausible meter reading result is
expected for billing. The price class can be defined at the device category, device, or register level. The price class,
together with the price level, determines the settlement price (e.g. meter rental) from the rate. The rate type is maintained at device or register level and controls rate determination, together with
the installation's rate category. The rate fact group is also assigned at device or register level. The rate fact group contains specific
values (e.g. constants) and/or keys (e.g. price keys) that are assigned to a rate. Discounts can be assigned at register level for quantities and services ("register discount").
Period consumption is used in the extrapolation of meter readings when no representative meter reading results are available (such as for new customers).
(C) SAP AG IUT110 18
6.18
SAP AG 1999
The precise location of the devices is identified using device location in IS-U/CCS. The device location is a functional location in the PM application component.
Devices can be removed or installed in two separate steps that are distinguished in terms of billing and technical factors. Devices can also be removed or installed in one step for both billing and technical data.
During device replacement, full removal of the old device and full installation of the new device is carried out in one step.In this way, technical and billing-related data is automatically transferred from the old device to the new device.
Device Installation: Summary
(C) SAP AG IUT110 19
6.19Device Installation Exercises
Unit: Device Installation
Topic: Installation and Removal of Devices
At the conclusion of these exercises, 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. To replace a device, 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.
Technical and billing-related installation of the new meter.
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.As the office-based employee responsible, you will first carry out the full removal of the old device and then the full installation of the new device in the system.
(Note: this transaction can be processed quickly in one step using the transaction “device replacement”. In this transaction, the system carries out the full removal and installation in the background. However, in order to illustrate the individual steps in this task, you should carry out the device replacement step by step).
1-1-1 First, in the Customer Interaction Center, determine which device location and installation the device is assigned to. Use today’s date as activity date.
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.
1-1-3 Then carry out the full installation of the new meter TB010200## in one step. Choose today’s date as the installation date and enter the meter reading at installation as 97.8 m³. Assign a rate type and a fact group to the register.
1-1-4 Finally, in the data environment display in the Customer Interaction Center, log the device replacement.
1-2 Check the following features of the device you have just installed.
(C) SAP AG IUT110 20
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.
1-4 (Optional) Consumption has increased for a flat-rate installation. For this reason, the utility installation must be extended by installing an additional meter. 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.Only assign household rate data at register level.
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. To do this, you must assign a suitable rate category (e.g. “E1”) and limit the installation facts.
1-5 True or false?
1-5-1 During technical installation, the device is assigned to a device location and to an installation. Rate data can not be maintained, but device locations can, however, be created, searched for and changed.______________________________________________________
1-5-2 Only devices of the same division can be installed in a device location.______________________________________________________
(C) SAP AG IUT110 21
1-5-3 Billing-relevant rate data must always be maintained during device installation.______________________________________________________
1-5-4 The device location is managed as a functional location in PM.______________________________________________________
1-5-5 The device location is the highest level in the functional location hierarchy in PM. ______________________________________________________
1-5-6 Device installation and removal automatically generates a time slice for the device. ______________________________________________________
(C) SAP AG IUT110 22
6.20 Device Installation Solutions
Unit: Device Installation
Topic: Installation and Removal of Devices
1-1G
1-1-1 Find customer TB010110## in the CICChoose 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.
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, call up the data for business partner TB010110##.
Choose the action box Info Customer environment
Choose utility installation TB010120## by double-clicking on it. Branch to the device history of the devices assigned to the installation by pressing the Device history (DevHist) button.
1-2
1-2-1 Access device management or double-click on the device in the CIC.
Utilities Industry Device Management.
Choose:
Technology Device Display
Enter TB010200## in the Serial number field.Press Continue to confirm your entry.The system displays the device master data.
To obtain an overview of the time slices, press the Display time slice overview button.
(C) SAP AG IUT110 23
To check the installation date, choose IS data Act./codes.
1-2-2 Using the MR results button you can call up a list of the previous meter readings.
1-2-3 Choose IS Data Mast. Data
1-2-4 Choose tab page General in the upper work area.The producer of the device is listed in the field Manufacturer.
1-2-5 Plant maintenance planning plant: Choose the tab page Organization. This informs you of the allocation of the device to a planning plant.
1-3 Call up device management as follows:
Utilities Industry Device Management.
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:
- The entire structure graphic is displayed.
1-4 First, call up the installation: Select flat-rate installation in the navigation area. Choose rate maintenance (right mouse click). Choose the time slice overview and specify today’s date as the selection date. Activate the Prorate indicator and choose the newly created time slice by double-clicking on it. A new time slice for the installation data relevant to billing opens automatically.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. Since another rate has to be found for the device installed, a rate category which matches a rate type at device or register level must be specified. For this reason, change the rate category in the current time slice to “E1”.To ensure that your billing is correct, you must also specify the validity of the previous rate type in the installation facts. To do this, choose the Facts button. On the following screen, select the rate type by double-clicking on it. Limit the period of validity to the day prior to the installation of the device. (You may have to delete another automatically generated continuation line, before you can transfer the settings).
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.
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
Installation: TB010130##Activity date: Today’s dateNew device TB010130##
To continue processing, press Enter.
Enter the Activity Date:Activity reason: 02 Installation extensionMeter reading: 250Rate type: 1002 Off-peak active energyFactGr.: 0001 Residential customer
Activate the indicator for payment of rental and settlement charges.
Save your entries.
1-5 True or false?
1-5-1 True.
1-5-2 False. The device location describes the installation place in the connection object that is not dependent on a division. The device location can be explicitly assigned to a particular premise, if desired.
1-5-3 False. The billing-relevant rate data is not required during technical installation. This can be added during billing-related installation or full installation.
1-5-4 True.
1-5-5 False. The connection object represents the level above the device location in the hierarchy.
1-5-6 True.
(C) SAP AG IUT110 25
7
SAP AG 1999
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
Contents:
Meter Reading
(C) SAP AG IUT110 1
7.2
SAP AG 1999
At the conclusion of this unit, 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
Meter Reading: Unit Objectives
(C) SAP AG IUT110 2
7.3
SAP AG 1999
A customer telephones the customer call center to report his/her move-out
The customer service agent enters the move-out date and the meter readings
An implausible reading means that the utility company has to carry out a control reading
Meter reading processing
Creation of meter reading order
Entry or estimation of meter reading results
Start of billing and invoicing
Final billing, followed by invoicing
Meter Reading: Business Scenario
(C) SAP AG IUT110 3
7.4
SAP AG 1999
Meter reading organization:
Scheduling
Street route
Meter reading procedure
Processing the meter reading
Checking of meter reading results
Extrapolation of meter reading results
Special functions
Meter reading by customer via the Internet
Reversal function
Meter Reading: Meter Reading Organization
(C) SAP AG IUT110 4
7.5
SAP AG 1999
Meter reading
UnscheduledScheduled
Indicator
Predefined meter reading strategy
Date and area scheduled in regional structure
Resources can be planned
Process
Create meter reading schedule
Specify meter reading sequence
Create mass meter reading orders
Enter results
Check results
Release for billing
Indicator
There are special reasons for the meter reading request, such as a move-in/out
Date and area cannot be scheduled
Meter reading cannot be planned
Process
Create a single meter reading order
Enter consumption
Check results
Release for billing
Types of Meter Reading
(C) SAP AG IUT110 5
7.6
SAP AG 1999
Regional structure SchedulingMaster data
Meterreading
unit
Businesspartner
Connection object
Premise
Account
Installation
Contract
CityCity StreetStreet Street sectionStreet section
Political structure
PortionPostal regional structure
Regional Structure and Scheduling
Portioning: Grouping of contracts that are to be billed together. You allocate a contract to a portion either directly in the contract or indirectly via the meter reading units entered in the installations.
Scheduling: Controlling and planning of the following processes:Meter reading order creationPeriodic billingBudget billing collection
Scheduling is managed at the meter reading unit and billing portion levels.
(C) SAP AG IUT110 6
7.7
SAP AG 1999
Portion 1Portion 1
Portion 2Portion 2
MR unit 1MR unit 1
MR unit 2MR unit 2
MR unit 3MR unit 3
Grouping together of contracts:
For joint billing
Where budget billing options are identical(budget billing cycle and scheduling)
Grouping of utility installations:
Of the same billing class and division category
For joint billing
To control special features of meter reading, such as MDE, intervals
Scheduling Tasks
(C) SAP AG IUT110 7
7.8
SAP AG 1999
MR unit A.3
Portion A
MR unit A.2
MR unit B.1
MR unit B.3
Portion B
MR unit B.2
MR unit B.4B
Portion C
MR unit B.5
MR unit C.3
AMR unit A.1
MR unit C.2
MR unit C.1
Portions and Meter Reading Units
A portion normally contains several meter reading units, which are structured according to location and/or scheduling requirements.
Meter reading units in a portion do not have to be located near one another; their grouping can also depend on other factors, such as billing conditions.
Example: Portions A and B represent different city districts consisting almost entirely of households and small
businesses (such as residential customers). Meter reading units in these portions are structured in such a way that they correspond to the daily work quota of the meter reader.
Since other meter reading cycles and billing conditions apply to nonresidential customers, major customers (such as industrial and business groups) within the area concerned are allocated to a separate portion (C). This portion consists of three meter reading units that are not in close proximity to each other. They are "islands" inside portions A and B.
The utility company bills residential customers periodically. Portion A is billed on June 15; portion B is billed on July 15.
Non-residential customers are billed monthly. This means that portion C is billed on June 15, July 15, and so on.
(C) SAP AG IUT110 8
7.9
SAP AG 1999
PortionP_AUG01PortionP_AUG01
MR unitA_AUG01MR unitA_AUG01
P1P1
Parameter recordParameter record
Schedule master records
A_AUG01 2002A_AUG01 2002
A_AUG01 2001A_AUG01 2001
A_AUG01 2000A_AUG01 2000
MR unitMR unit
Schedule records
P_AUG01 2002P_AUG01 2002
P_AUG01 2001P_AUG01 2001
P_AUG01 2000P_AUG01 2000
PortionPortion
Generation ofschedule records
Generation of Schedule Records
Schedule records are generated from the settings in the parameter record and schedule master records (portion and meter reading unit).
Schedule records refer to specific dates, which control meter reading and billing. Schedule records must be generated for portions and meter reading units before meter reading orders can
be generated.
(C) SAP AG IUT110 9
7.10
SAP AG 1999
20012001
Portion A07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03
Portion A07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03
20022002
Portion A
07/27 07/28 07/29 07/30 07/31 08/01 08/02 08/03
Scheduledmeterreadingdate
Billing period Billing period
Meter reading period for meter reading unit 1Meter reading period for meter reading unit 1
Meter reading period for meter reading unit 2Meter reading period for meter reading unit 2
Meter reading period for meter reading unit 3Meter reading period for meter reading unit 3
for all meter reading units for all meter reading units
End ofmeterreadingperiod
End ofbillingperiod
Meter readingMeter readingBillingBilling
Meter readingMeter readingBillingBilling
Scheduling: Annual Billing
Schduled billing date
End of billing period: This is the date on which the portion is to be billed for the first time. This date, together with the length of the billing period (that is, the period length), determines the date of the next billing (start of the next billing period = end of the billing period + 1 day).
The scheduled billing date is the date on which the contracts belonging to a portion are billed. This takes the SAP calendar into account.
The end of the meter reading period corresponds to the end of the billing period, and is used as a basis for defining dates of subsequent meter reading periods.
The scheduled meter reading date is the date on which the schedule specifies the register is to be read. It is also the date for which periodic meter readings are generated in scheduling. It forms the basis for calculating the expected consumption during meter reading order creation; it also acts as the final date for determining the budget billing amount.
(C) SAP AG IUT110 10
7.11
SAP AG 1999
Street route
MRunit
A
MRunit
A
Meter Reading Organization: Street Route
City distr. 1
Street 1
Street 2
Street n
City distr. 2
City distr. n
Device 1
Device 2
Device n
Device location
1
Device loc. n
Device loc. 2
Connectionobject 1
Connectionobject 2
Connectionobject n
(C) SAP AG IUT110 11
7.12
SAP AG 1999
Meter reading organization:
Scheduling
Street route
Meter reading procedure
Processing the meter reading
Checking of meter reading results
Extrapolation of meter reading results
Special functions
Meter reading by customer via the Internet
Reversal function
Meter Reading: Process
(C) SAP AG IUT110 12
7.13
SAP AG 1999
Meterreading
due
Createmeter reading
orders
Outputmeter reading
orders
Printmeter reading
documents
Downloadmeter reading
data
Read meter Read meter
Entermeter reading
results
Uploadmeter reading
results
Check meter reading
results
Manual meter reading
due
MDEmeter reading
due
Resultsdetermined
Overview: Scheduled Meter Reading
(C) SAP AG IUT110 13
7.14
SAP AG 1999
Meterreading
due
Createmeter reading
orders
Outputmeter reading
orders
Printmeter reading
documents
Downloadmeter reading
data
Read meter Read meter
Entermeter reading
results
Uploadmeter reading
results
Check meter reading
results
Manual meter reading
due
MDEmeter reading
due
Resultsdetermined
Meter reading orders
Single meter reading orders
Mass meter reading orders
Single order data
Selection via the meter reading unit, contract, installation or device
Additional dates for billing control
Mass order data
Selection via From meter reading unit and To meter reading unit
Schedule task in task management
Specification of meter reading reason
Creating Meter Reading Orders
(C) SAP AG IUT110 14
7.15
SAP AG 1999
• Cover sheet• Meter readingdocuments
MDE • Meter reading notification• Card for meter readingby customer
Output media
Meter reading information (selection)
Expected reading with area
Any number of previous meter reading results
Street route
Notes for the meter reader(dynamic / static)
Issuing the Meter Reading Orders
Meterreading
due
Createmeter reading
orders
Outputmeter reading
orders
Printmeter reading
documents
Downloadmeter reading
data
Read meter Read meter
Entermeter reading
results
Uploadmeter reading
results
Check meter reading
results
Manual meter reading
due
MDEmeter reading
due
Resultsdetermined
(C) SAP AG IUT110 15
7.16
SAP AG 1999
Automatic
Upload interface
Automatic estimation
Manual
Fast entry
Fast entry without correction
Fast entry with correction
Single entry
Result correction
Plausible results
Implausible results
Meter reading by customer
Via the Internet
Via WAP telephone
Types of Result Entry
Meterreading
due
Createmeter reading
orders
Outputmeter reading
orders
Printmeter reading
documents
Downloadmeter reading
data
Read meter Read meter
Entermeter reading
results
Uploadmeter reading
results
Check meter reading
results
Manual meter reading
due
MDEmeter reading
due
Resultsdetermined
(C) SAP AG IUT110 16
7.17
SAP AG 1999
Reference to meter reading order (fast entry)
Entry number
Check digit
Meter readingdata
Recorded meter reading
Date and time of meter reading
Meter reader's notes
Meter reading type (such as meter reading by the utility company, by the customer, or estimation)
Meter reader number
Date and time of maximum reading
Functions
Correction and release of meter reading results
Estimation of meter reading results
Result Entry Data
Meterreading
due
Createmeter reading
orders
Outputmeter reading
orders
Printmeter reading
documents
Downloadmeter reading
data
Read meter Read meter
Entermeter reading
results
Uploadmeter reading
results
Check meter reading
results
Manual meter reading
due
MDEmeter reading
due
Resultsdetermined
(C) SAP AG IUT110 17
7.18
SAP AG 1999
Entry of meter reading results
Manual
Automatic
Types of validation
Fixed checks
Independent checks
Dependent checks
Correction
Correction and release of meter reading results
Estimation of meter reading results
Correction aids
Checking Meter Reading Results: Overview
Meterreading
due
Createmeter reading
orders
Outputmeter reading
orders
Printmeter reading
documents
Downloadmeter reading
data
Read meter Read meter
Uploadmeter reading
results
Check meter reading
results
Manual meter reading
due
MDEmeter reading
due
Resultsdetermined
Entermeter reading
results
(C) SAP AG IUT110 18
7.19
SAP AG 1999
Checks can be configured for individual customers and customer groups
Permitted deviations between measured values and target values can be configured using tables
Return control/monitoring of implausible results
Examples:• Consumption from
previous period• Demand from previous
periods• Demand compared with
agreed demand
Examples:• Consumption from
previous period• Demand from previous
periods• Demand compared with
agreed demand
Examples:• Cosine phi for
energy/demand• Usage hours• Control meters
Examples:• Cosine phi for
energy/demand• Usage hours• Control meters
Device: 4711000Meter reading: 78133
PlausiblePlausibleresultresult
ImplausibleImplausibleresultresult
Correction aidsCorrection aids
IndependentIndependentcheckschecks
DependentDependentcheckschecks
Check Meter Reading Results: Process
(C) SAP AG IUT110 19
7.20
SAP AG 1999
Selection of meter reading ordersvia the following data objects:
Contract
Installation
Device
Portion
MR unit
Business partner
Display (single or all):
Billing order
Meter reading orders
Meter reading results
Monitoring Meter Readings
(C) SAP AG IUT110 20
7.21
SAP AG 1999
Meter reading organization:
Scheduling
Street route
Meter reading procedure
Processing the meter reading
Checking of meter reading results
Extrapolation of meter reading results
Special functions
Meter reading by customer via the Internet
Reversal function
Meter Reading: Special Functions:
(C) SAP AG IUT110 21
7.22
SAP AG 1999
InternetTransaction
server
InternetTransaction
server
EE--mail
CustomerCustomer
Meter reading request
Meter reading request
Read meter
Entry of meter data
Entry of meter data
IS-U/CCSISIS--U/U/CCSCCS
InternetInternet Energy supplierEnergy supplierInternet customerInternet customer
Meter Reading by Customers over the Internet
(C) SAP AG IUT110 22
7.23
SAP AG 1999
CustomerCustomer
Read meter
IS-U/CCSISIS--U/U/CCSCCS
Wireless Application Protocol
Wireless Application Protocol Energy supplierEnergy supplierInternet customerInternet customer
WA
P
Transfer meter readings
Meter Reading by Customer over WAP Telephone
InternetTransaction
server
InternetTransaction
server
(C) SAP AG IUT110 23
7.24
SAP AG 1999
New meterreading order
Incorrectmass
selection
Incorrectsingle
selection
Reverse meter reading
order
Correctselection
Restart order
creation
Meter reading order deleted
Reversing Meter Reading Orders: Process
Meter reading orders can be reversed. 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.
(C) SAP AG IUT110 24
7.25
SAP AG 1999
Scheduled meter readings are controlled via meter reading units
In meter reading preparation, documents are created for:
Meter reading by the company via meter reading lists
Meter reading by the company via MDE
Meter reading by customer via meter reading cards
Meter reading by customers via the Internet
Meter reading processing includes:
Automatic upload of data from external systems
Manual fast entry with and without correction
Manual single entry and meter reading estimation
Configurable validations reduce the potential for error
Meter Reading: Unit Summary
(C) SAP AG IUT110 25
7.26Meter Reading: Exercises
Unit: Meter Reading
Topic: Meter reading for individual customers
At the conclusion of these exercises, 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, the company does not carry out meter reading at all installations. For some customers, carrying out the meter reading themselves is an efficient use of resources.
The customer reports the meter readings either in writing or by phone. A customer service representative records the meter readings by customer and enters these manually in the system.
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. Carry out the meter reading for all devices allocated to this business partner using the Customer Interaction Center.
1-4 True or false?
1-4-1 Meter reading orders control the meter reading, billing, and invoicing processes.
1-4-2 Meter reading orders can be output on the printer or via IDoc.
1-4-3 Meter reading results can be entered manually or automatically and are subject to the same validations.
1-4-4 If meter reading results are not available, the meter reading unit cannot be billed.
1-4-5 Validations are always carried out.
(C) SAP AG IUT110 26
7.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.
Enter portion T-A-00.
Choose Save Enter.
The planned billing date is stored in the Sched BD field. This is valid for all meter reading units assigned to this portion.
You can view the list of the meter reading units assigned by choosing the Where-used list pushbutton or CTRL+F4.
By expanding the sub-tree Portion in MR units, you can view all the meter reading units that belong to this portion.
1-2
The following relationships can exist:
- The portion is entered directly in the meter reading unit.
- The portion can be specified as an alternative portion directly in the contract.
- The portion is indirectly referenced via the meter reading unit in the installation.
(C) SAP AG IUT110 27
1-3 Proceed as follows:
Call the CIC and select the data for your business partner TB090110##. Choose Enter until the data is displayed in the navigation area. Carry out this step for each utility contract
To enter the meter readings for each contract, proceed as follows:
- Select a contract.
- Choose the action Enter customer meter reading.
- Confirm the entry of:
- Meter reading reason 02 Interim reading with billing
- Meter reading type 02 Meter reading by customer.
- Choose F8 to continue or
- Enter the meter readings, even if the values are implausible (i.e. very high or very low).
- To correct meter readings, proceed as follows:
Select a register line
Choose the Correct button.
From the MR data and Consump.data fields, you can read the expected values.
The reading can be corrected in the Current MR field.
To release a meter reading, choose Release.
You return to the screen where you can enter meter readings.
- Save the meter readings by choosing Save:
- Complete the customer contact and save it using:
- You return to the CIC.
- Repeat the above steps for the other utility contracts.
1-4
1-4-1 False. The meter reading order is an organizational aid for preparing for meter readings, collecting data and creating the meter reading documents.
1-4-2 True.
1-4-3 True.
1-4-4 False. Missing meter reading results can be estimated by mass runs.
1-4-5 True. There are fixed validations which are always checked, such as implausible previous meter reading results and deviations where the installation is inactive or disconnected, or where devices have not been installed. All other independent and dependent validations can be classified into validation groups in Customizing. The validations can then be carried out automatically.
(C) SAP AG IUT110 28
8
SAP AG 1999
Contents:
Energy Data Management
Profile header
Profile allocation for register
Point of delivery
Profile values
Formula profiles
Synthetic profiles
(C) SAP AG IUT110 1
8.2
SAP AG 1999
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
Profile Management: Unit Objectives
(C) SAP AG IUT110 2
8.3
SAP AG 1999
Values determined by automated meter reading for
an interval meter should be copied to the system
Profile Management: Business Scenario
(C) SAP AG IUT110 3
8.4
SAP AG 1999
Profile TypeHistorical profile, schedule profile, formula profile, forecast profile, synthetic profile, day profile
Consistency Checking GroupDetermines which checks to carry out when importing profile values
Replacement Value GroupDetermines the calculation of plausible values that are used instead of missing or implausible actual values
Validity Period
Profile Value CategoryAmount, factor, quantity, demand, price, other
Interval Lengths5, 10, 15, 30, 60 minutes
Profile Header
(C) SAP AG IUT110 4
8.5
SAP AG 1999
Profile Allocation for Register
Measuredprofile
Regional structure
Contractaccount
Businesspartner
Installation
Contract
Register
Device
Premise
Connectionobject
Profiles can be allocated to (logical) registers of interval meters
This allocation is historical and role-based
The role determines the profile's task for this register
Examples of roles are measurement and forecast
(C) SAP AG IUT110 5
8.6
SAP AG 1999
Point of Delivery
Measuredprofile
Contractaccount
Businesspartner
Installation
Contract
Register
Device
Point of Delivery
Point to which a utility service is supplied or to which a utility service can be determined for a customer
A point of delivery has one external identification number at any time (point of delivery description according to metering code, for example)
The point of delivery is used for communication in automatic data exchange
The point of delivery is used to exchange meter reading results
(C) SAP AG IUT110 6
8.7
S A P A G 1 9 9 9
I m p o r t i n g P r o f i l e V a l u e s
P r o f i l e
Inte
rfac
e
M e t e rM e t e rr e a d i n gr e a d i n gr e s u l t sr e s u l t s
E D I
P o i n t o f d e l i v e r yP o i n t o f d e l i v e r y
O t h e rm a r k e t
p a r t i c i p a n t s
I n t e r v a l m e t e r
s i g n a l
D o w n l o a d
F o r e x a m p l e : S i e m e n s m e t e r i n gF r ö s c h lG ö r l i t z
F o r e x a m p l e :M S C O N S
I S - U / E D M
E D Is u b -s y s t e m
C o n v e r s i o nA M Rs y s t e m
(C) SAP AG IUT110 7
8.8
SAP AG 1999
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 or IDoc
An OLE (Excel) interface exists
Profile values can be displayed on the web
(C) SAP AG IUT110 8
8.9
SAP AG 1999
Formula Profile
100
0
20
30
40
50
60
70
80
90
1/4
h d
em
an
d(k
W)
01.18.1995 01.19.1995 01.20.1995 01.21.199501.17.19950
0:0
0
12
:00
12
:00
12
:00
12
:00
00
:00
00
:00
00
:00
EDM
+
+
+
request
request
UI
UI
UI
UIrest loadRL = LT - NL - SL - MC
elementary load profile
aggregated load profile
formula based profile
scheduling
automatic
+
LTtotal load
NLnet losses
SLstreet lights
MCmeasured customers
RP
UI
+
+
request
request
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, 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
8.10
SAP AG 1999
Synthetic Profiles
ResidentialResidentialcustomercustomer
WorkdaySummer00:00 24:00
Weekend
WorkdayWinter
Weekend
00:00 24:00
00:00 24:00
00:00 24:00
Su 03.28 Mo 03.29 Tu 03.30 We 03.31 Th 04.01 Fr 04.02 Sa 04.03 Su 04.04 Mo 04.05 Tu 04.06
Weekend
Winter Summer
Workday Workday WorkdayWeekend
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
8.11
SAP AG 1999
You are now able to:
Describe the components that make up profiles
Explain the connection of profiles to the master data
Profile Management: Summary
(C) SAP AG IUT110 11
9
SAP AG 1999
Contents:
Billing
Overview
Basic components of billing
Special functions
Invoicing
Overview
Invoicing functions
Creation of contract accounts receivable and payable (FI-CA) and print documents
Billing and Invoicing
(C) SAP AG IUT110 1
9.2
SAP AG 1999
At the conclusion of this unit, you will be able to:
Describe the billing process
Billing procedure, simulation
Credit memo, manual backbilling
Outsorting, billing reversal
Explain the invoicing process
Invoicing tasks and procedure
Special features of invoicing
Use of invoicing documents
Billing and Invoicing: Course Objectives
(C) SAP AG IUT110 2
9.3
SAP AG 1999
Overview:
Billing procedures and special functions
Billing and simulation procedures
Design of billing rules
Basic components of billing:
Scheduled dates and periods
Billing procedures
Billing and simulation
Document display
Special billing functions:
Credit memo, manual backbilling
Outsorting, reversal
Contents
Billing
(C) SAP AG IUT110 3
9.4
SAP AG 1999
Contract billing of the supply and services provided is the most important function of a utility company.
Integrated processing of both residential and non-residential customers requires several billing rules.
Increased competition requires the billing process to be flexible and efficient.
Different types of simulation enable the correctbilling to be performed.
Billing: Introduction
SAP Utilities
(C) SAP AG IUT110 4
9.5
SAP AG 1999
Move-out processing in the customer center
Move-out date and meter readings reported bytelephone
Implausible meter reading requires meter reading by the company
Meter reading processing
Create meter reading order
Enter or estimate meter reading results
Start of billing and invoicing
Final billing, followed by invoicing
Billing: Business Scenario
(C) SAP AG IUT110 5
9.6
SAP AG 1999
Discounts,surchargesDiscounts,surcharges
Generalduties
Generalduties
ProrationProration Franchisefees
Franchisefees
Priceadjustment
Priceadjustment
. . .. . . . . .. . .
Electricity
Gas
Water/Waste water
Districtheating
Cabletelevision
MultimediaCharges TaxesDuties
Divisions
Residentialcustomer
Non-residentialcustomer
Energysuppliers
Businesspartner
ConsumptionservicesFlat rates
Billing rules, variantsBilling rules, variants
IS-U/CCS: Billing
(C) SAP AG IUT110 6
9.7
SAP AG 1999
Billing procedures:
Month-based
Key date
Period
For exact number of days
Season-based
Comparative (best rate)
For employees
Floating (backbilling, period-
end billing)
Special functions
Interim billing
Outsorting for bill verification
Simulation
Manual backbilling
Manual credit memo
Reversal
Unbilled revenue reporting
Billing Procedures: Overview
(C) SAP AG IUT110 7
9.8
SAP AG 1999
Meter reading
Billing
Invoicing
Billing order processing that involves valuation of consumption and demand for each contract, and creation of billing documents for invoicing.
Definition of Billing
(C) SAP AG IUT110 8
9.9
SAP AG 1999
Billing
Determination of billing periods
Determination and conversion of quantities
Creation of billing documents for invoicing
Determination of:•Rate data•Price data
Determination of change date andproration to that date
Valuation of quantities with prices
Billing Tasks
(C) SAP AG IUT110 9
9.10
SAP AG 1999
MO TU WE TH FR SA SU
18152128
29162229
310172330
411182431
5121925
6132026
7142127
Length of period for periodic billing
x days; 1, 2, 3, 4, 6, or 12 months
Length of period for period-end billing
x + x days; 1, 2, 3, 4, 6, or 12 months
Billing for an exact number of days
based on the date of the meter reading
Month-based billing
dependent on key date
Month-based billing
dependent on intervals
Billing Periods
The billing period for which the utility bills the customer can be determined in a number of ways. These are:
For an exact number of daysDetermines the exact length of the billing period in days, for example the period between the last billed meter reading and the current day of meter reading.
Month-basedBills a specific number of complete months. If the case of a move-in or move-out, the month-based procedure can be billed based on the number of days.
(C) SAP AG IUT110 10
9.11
SAP AG 1999
Periodic billingRecurring periodic billing
Floating backbillingSpecial form of monthly periodic billing in which backbilling is performed for previous monthsusing a current value.Example: monthly comparison of n peak averages
Period-end billingAfter completion of the billing cycleExample: 13th billing, backbilling for a year
Interim billingUnscheduled billing at any timeExample: initiated by customer request
Final billingExamples: customer move-out or termination of contract; service territory transfer
Forms of Billing
(C) SAP AG IUT110 11
9.12
SAP AG 1999
Best-rate billingThe most favorable rate is chosen for the customer on the basis of several billing rules.
Quantity-based rate for basic priceThe annual quantity consumed is used to determinethe billing rule that applies.
Demand-based rate determinationThe measured demand is used to determine the billing rule that applies.
Season-based billingExamples: Different prices for each season, different billing rules for each season.
Special Forms of Billing
(C) SAP AG IUT110 12
9.13
SAP AG 1999
2001
Portion 17.27. 7.28. 7.29. 7.30. 7.31. 8.1. 8.2. 8.3.
Portion 17.27. 7.28. 7.29. 7.30. 7.31. 8.1. 8.2. 8.3.
2002
Portion 1
7.27. 7.28. 7.29. 7.30. 7.31. 8.1. 8.2. 8.3.
ScheduledMRdate
Billing periodBilling period
Meter reading period for MR unit 1Meter reading period for MR unit 1
Meter reading period for MR unit 2Meter reading period for MR unit 2
Meter reading period for MR unit 3Meter reading period for MR unit 3
for all MR unitsfor all MR units
End ofMRperiod
End ofscheduledbillingperiod
Meter readingMeter reading
Billing Billing Meter readingMeter reading
Billing Billing
Generation of Schedule Records
Scheduled billing date
End of the billing period: Portions should be billed for the first time on this date. The length of the scheduled billing period (period length) in conjunction with this date determine the date of the next billing.
Scheduled billing date: Date on which billing of contracts that belong to a particular portion should begin. This date is calculated as follows during generation of the schedule records: Date of the end of the
billing period of the schedule record, minus the number of days between the end of the billing period and the scheduled billing date of the schedule master record.
The SAP calendar is used for this. End of the meter reading period: Used as the baseline date for determining the schedules of the
following meter reading periods. This date may not be later than the end of the billing period for the allocated portion.
Scheduled meter reading date: Date on which all extrapolations and estimations are performed.
(C) SAP AG IUT110 13
9.14
SAP AG 1999
ImplausibleMR
results
ImplausibleMR
results
PlausibleMR
results
PlausibleMR
results
MRorderMR
order
Billing orderBilling order Billing orderBilling order Billing document
Billing document
MRorder creation
MRentry Billing Invoicing
MRcorrection
Billing Process: Overview
Bill printoutBill printout
Billprintout
(C) SAP AG IUT110 14
9.15
SAP AG 1999
Generationof billingline items
Generationof billingline items
Validationof meterreadingresults
Validationof meterreadingresults
Executionof variantprograms
according to schema
Executionof variantprograms
according to schema
Quantityconversion
andproration
Quantityconversion
andproration
Dataentryand
analysis
Dataentryand
analysis
Data relating tocustomer and
installation
Rate data Procedure data
Contract
Ratedeter-
mination . . .
Schema 1Rate Var.pr. ValuesRate 1
1 VarProg. A x12 VarProg. B x2
. . .Rate 2
1 VarProg. A x32 VarProg. C x43 VarProg. D x5
. . .
. . .
. . .
Rate n1 VarProg. A xxx
EXECUTION
Installation Ratecategory
Rate type
Prices andrate facts
Rate 1
Rate n
Universal Billing Engine
Inst. structureRate cat. facts/
Installation facts
(C) SAP AG IUT110 15
9.16
SAP AG 1999
Energy price
Demand price
Service price
Season-based values and variants
Block and scale prices
Usage hours
Best-rate billing
Decision variants
Billing
General Billing Functions
Energy priceMeasured or calculated consumption is valuated using energy charges. For example: Adjustment of calculated consumption over the course of the billing period Comparison with maximum/minimum purchase quantities and further processing of difference
quantities Breakdown/valuation of energy quantities using different percentage rates or time criteria
Demand priceMeasured or calculated demand is valuated using demand prices. The number of the measured demand values used for calculating the demand to be billed is variable. For example: Comparison with minimum demand, maximum demand, or other demand established in the contract,
and further processing of the difference demand (such as excess demand) Breakdown and valuation of demand using different percentage rates
Service price Any number of demand replacement values can be valuated with time-based prices for the supplying of energy. The demand replacement values can also be levied as a flat rate.
Block and scale prices Season-based values and variants Decision variants
(C) SAP AG IUT110 16
9.17
SAP AG 1999
QUANTITY FACTOR QUANTITYCalculates x% of a quantity
QUANTITY FACTOR QUANTITYCalculates x% of a quantity
. . . . . .
. . . . . .
NUMBER OF DEMAND PEAKS DEMANDCalculates N peak averages
NUMBER OF DEMAND PEAKS DEMANDCalculates N peak averages
DEMAND PRICE BILLING LINE ITEMSValuates demand with a price
DEMAND PRICE BILLING LINE ITEMSValuates demand with a price
. . . . . .
QUANTITY QUANTITY QUANTITYDifference of two quantitiesQUANTITY QUANTITY QUANTITYDifference of two quantities
. . . . . .
. . . . . .
QTY PRICE BILLING LINE ITEMSValuates energy with a price
QTY PRICE BILLING LINE ITEMSValuates energy with a price
ACT_KWH 0.5 ACT_50%ACT_KWH 0.5 ACT_50%
REACT_KWH - ACT_50% BILL_REACTREACT_KWH - ACT_50% BILL_REACT
BILL_REACT UNI 0.06 BILLING LINEITEMS
BILL_REACT UNI 0.06 BILLING LINEITEMS
Variant poolVariant pool
Variant poolVariant pool
Contract text:
The reactive energy that exceeds 50% of the active energy is valuated using a separate price.
Contract text:
The reactive energy that exceeds 50% of the active energy is valuated using a separate price.
*
*
* *
*
-
Example: Billing Rule for Electricity
(C) SAP AG IUT110 17
9.18
SAP AG 1999
Billing
Billability check
Consideration of register relationships
Manual credit memos andbackbilling
Billing of company and plant consumption
Determination of taxes, duties, and charges
Energy feeding from small power producers
Special Billing Functions
(C) SAP AG IUT110 18
9.19
SAP AG 1999
SimulationBilling
ISIS--UU
Billing typesReverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Choose billing type
Description:
Creation of billing documents used only for further processing in invoicing
Description:
Creation of simulation documents that are only used for further processing in invoicing simulation
Processing steps:
Billing order is retained and and can still be used for simulation
Meter reading results can still be changed
Simulation document is created
Processing steps:
The billing order is deleted and cannot be billed again
Meter reading results cannot be changed again
Billing document is created
Billing and Simulation
(C) SAP AG IUT110 19
9.20
SAP AG 1999
Reverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Choose simulation
type
ISIS--UU
Simulation types
SimulationBilling
simulation
Description:
Billing can be simulated without a billing order for any group and for any period of time.
Processing steps:
Simulation period can be freely defined
Extrapolation that takes account of meter reading results
Period can already have been billed
Description:
Billing is simulated on the basis of a billing order that can be processed.
Processing steps:
Period is determined by the billing order
Meter reading results relevantto billing are required
Valuation of billing
Billability check
Simulation Types
(C) SAP AG IUT110 20
9.21
SAP AG 1999
Reverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Check documents
Simulationdocument
Simulation
Billingdocument
BillingDescription:
Simulation produces a simulation document
Billing produces a billing document
Purpose
Documents the procedure
Saves and validates the results
Used for further processing ofbilling line items
Document Types
(C) SAP AG IUT110 21
9.22
SAP AG 1999
Internal billingdata
Account data
Print data
Meter readingdata
Device data
Price data
Billing line items
Documents from
• Simulation
• Billing
Reverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Check documents
Rate data
Document Information
(C) SAP AG IUT110 22
9.23
SAP AG 1999
Documents from
• Simulation
• Billing
Reverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Processdocuments
further
Billingreversal
Outsorting
InvoicingInvoicing
simulation
Further Processing of Documents
(C) SAP AG IUT110 23
9.24
SAP AG 1999
Outsortdocuments
Automatic
ISIS--UU
Manual
Reverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Outsortdocuments
Description:
Billing documents which have failed validation are outsortedautomatically.
Possible validations: Percentage or absolute
amount that the billing document exceeds or falls below the following:
Amount limit
Bill sum total
Budget billing
Bills with a balance of zero
Description:
Billing documents for a contract for which the outsorting indicator is set are not automatically processed further.
Purpose
Check special contract billing documents
Check new rates
Check consumption values in complex installations
Check proration for different time slices
Outsorting Procedure
(C) SAP AG IUT110 24
9.25
SAP AG 1999
Billprintout
Billing Invoicing
Outsortdocuments
Check documents
Exception list
Reverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Outsortdocuments
Release documents
Reversedocuments
Outsorting reasons
Failed validation
Indicator set in the contract
Further processing
Reversal
Release
Outsorting Process
(C) SAP AG IUT110 25
9.26
SAP AG 1999
Reverse billing
Individual reversal
ISIS--UU
Massreversal
Reverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Reversedocuments
Description:
Only one billing document is reversed. This can occur with or without a subsequent correction bill.
Possible reasons:
Incorrect conditions for nonresidential contract
Incorrect meter reading result
Technical fault
...
Description:
More than one document is reversed. Selection takes place using document intervals or listsof individual documents.
Possible reasons:
Incorrect settlement group
Incorrect rates and prices
Incorrect sales tax
...
Billing Reversal
(C) SAP AG IUT110 26
9.27
SAP AG 1999
2.16.00Incorrectbilling document
Jane Smith
Electricity. . . . . 900Gas . . . . . . 1.000Water . . . . . . 700
Total . . . . . 2.600
Documentoutsorted
Document implausible
Reverse billing
Correct data Restart billing
2.23.00Reversedbilling document
Billing order
2.24.00Correctedbilling document
Jane Smith
Electricity . . . . 600Gas . . . . . 1.000Water . . . . . . 700
Total . . . . . 2.300
Reversal indicator set
Jane Smith
Electricity . . . . 900Gas . . . . . 1.000Water . . . . . . 700
Total . . . . . 2.600
Reverse billing
Billing date reached
Enter selection criteria
Choose billing type
Billingchosen
Simulationchosen
Startbilling
Start simulation
Check billing documents
Check simulationdocuments
Start invoicing simulationBilling documents
implausibleBilling documents
correctBilling documents
incorrect
Outsortdocuments
Start invoicing
Reversedocuments
Billing Reversal Process
(C) SAP AG IUT110 27
9.28
SAP AG 1999
Billing processes billing orders, valuates consumption and demand, and creates billing documents for invoicing.
There are two types of billing:
Simulation, which creates simulation documents
Billing, which creates billing documents
Outsorted billing documents require additional processing - Documents must be either released or reversed. Reasons for outsorting:
Failed validation
Indicator set in the contract
Individual or mass reversals enable quick correction and subsequent billing.
Billing: Unit Summary
(C) SAP AG IUT110 28
9.29
SAP AG 1999
Invoicing links contract billing to contract accounts receivable and payable, and prepares bill printout.
The bill sum total is determined after settlement of the billing documents against the budget billings already paid, and against the taxes, charges, and duties that are due.
Flexible settlement options, such as payments to open items reduce the amount of processing required.
SAP Utilities
Invoicing: Introduction
The bill sum total is calculated as follows:Bill sum total = Total receivables from billing
- paid budget billings- other credits (credit memo, payment on account)+ other receivables (backbilling, dunning charge)
(C) SAP AG IUT110 29
9.30
SAP AG 1999
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
Entry or estimation of meter reading results
Start of billing and invoicing:
Final billing, followed by invoicing
Invoicing: Business Scenario
(C) SAP AG IUT110 30
9.31
SAP AG 1999
Meter reading
Billing
Invoicing
The process that links the billing documents to contract accounts receivable and payable, and provides the basis for bill creation.
Definition of Invoicing
(C) SAP AG IUT110 31
9.32
SAP AG 1999
FIFI--CACAISIS--UU
Billing:
Provides the processes relevant to payment and manages the individual accounts.
Invoice-relevant transactions
Billing documents
Credit memos
Backbillings
Contract accounts receivable and payable:
Contract Accounts Receivable and Payable makes available items relevant for payment and manages the individual accounts.
Invoice-relevant transactions
Open items
Paid budget billings
Manual postings
Dunning charges
Payments on account
Invoicing
Bill printout
Budget billing plan
Due date determination
Settlement
Use of credits
Invoicing: Overview
(C) SAP AG IUT110 32
9.33
SAP AG 1999
Invoicing
Joint invoicing
Cross-company code invoicing
Account determination
Budget billing settlement
Credit settlement
Creation of budget billing
plan
Due datedetermination
Settlement against first budget billing
Tasks of Invoicing
Invoicing is the process that ingrates contract billing with the Contract Accounts Receivable and Payable (FI-CA) component. It also forms the basis for bill creation.
Invoicing is used for the following: Grouping together billing documents of contracts from the same contract account into one joint bill. Posting documents to FI-CA (sub-ledger accounting) Supplying bill printout documents for bill creation Processing budget billing plans
(C) SAP AG IUT110 33
9.34
SAP AG 1999
Invoicing Reversal
Date for invoicing reached
Enter selection criteria
Choose invoicing type
Invoicing chosenInvoicing
simulationchosen
Start invoicing Start invoicing simulation
Check simulationdocuments
Simulate bill printout
Invoicingdocuments implausible
Invoicingdocuments
correct
Invoicingdocuments incorrect
Outsortdocuments
Start bill printout
Check bill printout
document
Check the FI-CA document
Start invoicing Creation of invoicing units
Summary of the billing documents in acontract account can be controlled at contract level.
Mandatory Contracts for which the documents must be invoiced together
Optional Contracts for which the documents can be invoiced together
Exclusive Contracts for which the documents must be invoiced separately
Invoicing Units
(C) SAP AG IUT110 34
9.35
SAP AG 1999
Contract 1Mandatory
Joint invoice
Contract 1Mandatory
Joint invoice
Contract 2Mandatory
Joint invoice
Contract 2Mandatory
Joint invoice
Contract 3Mandatory
Joint invoice
Contract 3Mandatory
Joint invoice
ContractOptional
Joint invoice
ContractOptional
Joint invoice
DocumentOptional
DocumentOptional
Document 3Mandatory
Document 3Mandatory
Document 1Mandatory
Document 1Mandatory
DocumentOptional
DocumentOptional
Billing
ContractExclusive invoice
ContractExclusive invoice
DocumentExclusive
DocumentExclusive
DocumentExclusive
DocumentExclusive
InvoicingContract account
Bill
Bill
Mandatory and Optional Contracts: 1
(C) SAP AG IUT110 35
9.36
SAP AG 1999
Contract 1Mandatory
Joint invoice
Contract 1Mandatory
Joint invoice
Contract 2Mandatory
Joint invoice
Contract 2Mandatory
Joint invoice
Contract 3Mandatory
Joint invoice
Contract 3Mandatory
Joint invoice
ContractOptional
Joint invoice
ContractOptional
Joint invoice
DocumentOptional
DocumentOptional
Document 3Mandatory
Document 3Mandatory
Document 1Mandatory
Document 1Mandatory
DocumentDocument
ContractExclusive invoice
ContractExclusive invoice
DocumentExclusive
DocumentExclusive
DocumentExclusive
DocumentExclusive
Document 2Mandatory
Document 2Mandatory Bill
Bill
Billing InvoicingContract account
Mandatory and Optional Contracts: 2
(C) SAP AG IUT110 36
9.37
SAP AG 1999
Invoicing Reversal
Date for invoicing reached
Enter selection criteria
Choose invoicing type
Invoicing chosenInvoicing
simulationchosen
Start invoicing Start invoicing simulation
Check simulationdocuments
Simulate bill printout
Invoicingdocuments implausible
Invoicingdocuments
correct
Invoicingdocuments incorrect
Outsortdocuments
Start bill printout
Check bill printout
document
Check the FI-CA document
Start invoicing SAP billing documents
IS-U billing documents
SD billing documents
PM / SM billing documents
External billing documents via the standardIDoc interface
Heating costs billing
Telecommunications
Company code allocation
Invoicing within a company code
Cross-company code invoicing
Invoicing Options
(C) SAP AG IUT110 37
9.38
SAP AG 1999
External External
ISIS--UU
SDSD
CSCS
Bill
Jane Smith
....
Electricity . . . . . . 600
Maintenance . . . . 1.500
Tel. com. . . . . . . 700
Total . . . . . 2.800
SAP systems:
Central invoicing of all processes from consumption billing, sales and distribution and service management simplify the transactions.
Invoice-relevant transactions
IS-U consumption billing
SD Sales and Distribution
CS Customer Service
External systems:
Using standard billing documents, billing results from external systems can be invoiced and monitored together with consumption billing results.
Source of Billing Documents
Invoice-relevant transactions
Telecommunications
Heating costs billing
Other unbundling services
(C) SAP AG IUT110 38
9.39
SAP AG 1999
Radiator UNI 35Radiator UNI 35
Waste water UNI 50Garbage UNI 40Waste water UNI 50Garbage UNI 40 Electricity UNI 15
Water UNI 60Gas UNI 80
Electricity UNI 15Water UNI 60Gas UNI 80
Electricityconnection UNI 85Electricityconnection UNI 85
Gas heating UNI 45Gas heating UNI 45
Simplifiedexample
without tax
Cable TV UNI 30Cable TV UNI 30
Account: A. SmithBilling #4711 UNI 180
Single items per receivable:Billing #1 ...
Billing #2 ...................
External billing document #7
Service xy UNI 70
Billingsummary
IS-U- One division for several
contracts ("unbundling" electricity rate)
- various divisions (electricity, gas, water)SAP applications
SD/CS and IS-U invoicesAlso billing from external systems
Disposal service #1 Supply service #2 Energy feeding #3 Other services #4
Total charges #4711
Billing (#1-#7) UNI 510 - Budget billings paid (#1-#3) UNI 330
Bill sum total UNI 180
due on 01/15/2000
Sale #5
Maintenance fee #6
Invoicing Various Services
(C) SAP AG IUT110 39
9.40
SAP AG 1999
Consumption bill. #1
Other Services #3Cable TV 180 UNI
Other services #2Waste water 500 UNIWaste disposal 200 UNI
Total charges #4711:Total charges #4711:
BillingBilling (#1(#1--#3)#3) 3980 UNI3980 UNI
-- amount paid (#1amount paid (#1--#3)#3)--3600 UNI3600 UNI
amount outstanding: amount outstanding: 380 UNI380 UNI
due on 1/15/96due on 1/15/96
Account Smith (Account Smith (xyxy))
Re.Re. #4711 380 UNI#4711 380 UNI
Line items for each requirement:
Billing #1 (xy) ...Billing #2 (zz) ...
Billing #3 (rs) ...
General ledger 02Local authority zz
General ledger 01 Dep. of works xy
General ledger 03(not relevant for fin. statements)TV company "rs"
Req. electricityReq. gasReq. water
Waste water req.Waste disposal req.
Cable TV req.
Contracts for ”xy"CoCd. 01
Contracts for "zz"CoCd. 02
Contracts for "zz"CoCd. 03
FI-CA
Total Charges #4711
Dep. of works xy:
Cross-company code billing for local authority zz:
Cross-company code billing for TV company rs:
Cross-companycode billing
Third party billing
ISIS--UU FIFI
Cross-company code invoicing
Electricity 1000 UNIGas 1500 UNIWater 600 UNI
Dies ist das Beispiel einer Fakturierung für verschiedene Buchungskreise. Die Stadtwerke xy versorgen ihre Kunden mit Strom, Gas und Wasser. Sie rechnen aber auch im Auftrag der Kommune zz Abwasser und Müllabfuhr ab. Für die Kabelfernsehgesellschaft rs rechnen sie die Gebühren für Kabel-TV ab. All dies geschieht im selben SAP-System, obwohl es sich um verschiedene Unternehmen handelt.
(C) SAP AG IUT110 40
9.41
SAP AG 1999
Baseline date + terms of payment = bill due date
Fakturastornieren
Termin fürFakturaerreicht
Selektions-kriterieneingeben
Art der Fakturawählen
Fakturagewählt
Faktura-simulation
gewählt
Start invoicing Faktura-simulation
starten
Simulations-belegeprüfen
Rechnungs-druck
simulieren
Faktura-belege
unplausibel
Faktura-belegekorrekt
Faktura-belege
fehlerhaft
Belegeaussteuern
Rechnungs-druck
starten
Check bill printout
document
Check the FI-CA document
Start invoicing The bill due date is determined from the
following attributes:
Terms of payment These determine the source of the baseline date
Baseline date:Posting date, document date, or system date
Terms of payment
Allocated to the contract account centrally
Can be differentiated for incoming and outgoing payment
If a bill falls due on a holiday, the bill due date can be corrected to fall on a working day.
Can be specified for each company in Customizing
Bill Due Date
Das Rechnungsfälligkeitsdatum kann auch mit dem ersten Abschlag zusammengelegt werden.
(C) SAP AG IUT110 41
9.42
SAP AG 1999
Credit memos/backbillings
Credit memos/backbillings
Billingdocuments
Billingdocuments
FI-CA documentsFI-CA documentsBudget billing plansBudget billing plans
Posting docs. FI-CA
Print documents
Fakturastornieren
Termin fürFakturaerreicht
Selektions-kriterieneingeben
Art der Fakturawählen
Fakturagewählt
Faktura-simulation
gewählt
Start invoicing Faktura-simulation
starten
Simulations-belegeprüfen
Rechnungs-druck
simulieren
Faktura-belege
unplausibel
Faktura-belegekorrekt
Faktura-belege
fehlerhaft
Belegeaussteuern
Rechnungs-druck
starten
Check bill printout
document
Check the FI-CA document
Start invoicing
Start invoicing
Document Flow in Invoicing
(C) SAP AG IUT110 42
9.43
SAP AG 1999
Invoicing Reversal
Date for invoicing reached
Enter selection criteria
Choose invoicing type
Invoicing chosenInvoicing
simulationchosen
Start invoicing Start invoicing simulation
Check simulationdocuments
Simulate bill printout
Invoicingdocuments implausible
Invoicingdocuments
correct
Invoicingdocuments incorrect
Outsortdocuments
Start bill printout
Check bill printout
document
Check the FI-CA document
Start invoicing In IS-U clearing processing, settlement
comprises the following activities:
Automatic determination of the purpose ofa payment amount when a payment transactionis entered.
Automatic allocation of posted open items to eachother in account maintenance.
The selected items are cleared or partially cleared on the basis of these allocations.
Settlement control is flexible and enables you tomodel your own clearing strategy in Customizing.
Settlement: Overview
(C) SAP AG IUT110 43
9.44
SAP AG 1999
Print documents
SAP spoolOutput
Raw data interface
Archive
Dear Madam/Sir: In reference to your letter of 9/27...
Dear Madam/Sir: In reference to your letter of 9/27...
Dear Madam/Sir: In reference to your letter of 9/27...
Bill date
Invoicing Reversal
Date for invoicing reached
Enter selection criteria
Choose invoicing type
Invoicing chosenInvoicing
simulationchosen
Start invoicing Start invoicing simulation
Check simulationdocuments
Simulate bill printout
Invoicingdocuments implausible
Invoicingdocuments
correct
Invoicingdocuments incorrect
Outsortdocuments
Start bill printout
Check bill printout
document
Check the FI-CA document
Start bill printout
Print document ready for
output
Select print document
Choose output type
Start output
Mail processing
Bill Printout Procedure
(C) SAP AG IUT110 44
9.45
SAP AG 1999
Billreversal
ISIS--UU
Fullreversal
Invoicing Reversal
Date for invoicing reached
Enter selection criteria
Choose invoicing type
Invoicing chosenInvoicing
simulationchosen
Start invoicing Start invoicing simulation
Check simulationdocuments
Simulate bill printout
Invoicingdocuments implausible
Invoicingdocuments
correct
Invoicingdocuments incorrect
Outsortdocuments
Start bill printout
Check bill printout
document
Check the FI-CA document
Invoicing Reversal
Transactions
Reversal of FI-CA document
Reversal of bill printout document
Possible reasons:
Incorrect layout Printing problems
Invoicing Reversal
Mass reversal
or
Single reversal
Bill reversal:Bill printout and FI-CA documents for bills or partial bills are reversed by selecting using a reconciliation key or document number.
Full reversal:
In addition to the bill, billing documents are also reversed by selecting using a document number. Full reversal does not include reversal of partial billing documents.
Transactions
Reversal of FI-CA document
Reversal of bill printout document
Reversal of billing document
Possible reasons:
Incorrect billing
Invoicing Reversal
(C) SAP AG IUT110 45
9.46
SAP AG 1999
Documentoutsorted
Document implausible
Reverse invoice Correct data
Restart invoicing
Billing document
New bill
Jane Smith....
Electricity. . . 900
Gas . . . . . . 1.000
Water . . . . . 700
Bud. billings 2.500
Receivable . . 100
Bill
Jane Smith....
Electricity . . . . 900
Gas . . . . . 1.000
Water . . . . . . 700
Bud. billings 2.900
Credit memo . . 300
Reversal indicator set
Reversed bill
Jane Smith....
Electricity . . . . 900
Gas . . . . . 1.000
Water . . . . . . 700
Bud. billings 2.900
Credit memo . . 300
Invoicing Reversal
Date for invoicing reached
Enter selection criteria
Choose invoicing type
Invoicing chosenInvoicing
simulationchosen
Start invoicing Start invoicing simulation
Check simulationdocuments
Simulate bill printout
Invoicingdocuments implausible
Invoicingdocuments
correct
Invoicingdocuments incorrect
Outsortdocuments
Start bill printout
Check bill printout
document
Check the FI-CA document
Reversedocuments
Procedure for Bill Reversal
(C) SAP AG IUT110 46
9.47
SAP AG 1999
24.2.98Correctedbilling document
Jane Smith
Electricity . . . . . 600Gas . . . . . 1.000
Water . . . . . . 700
Total . . . . . 2.300
New bill
Jane Smith....
Electricity . . . 900
Gas . . . . . 1.000
Water . . . . . 700
Bud. billings 2.500
Total . . . . . 100
Billing order
Incorrectbilling document
Jane Smith
Electricity . . . . . 900Gas . . . . . . 1.000Water . . . . . . 700
Total . . . . . 2.600
Bill
Jane Smith....
Electricity . . . .900
Gas . . . . . . 1.000
Water . . . . . . 700
Bud. billings 2.900
Credit memo . 300
16.2.98 23.2.98Reversedbilling document
Jane Smith
Electricity . . . . 900Gas . . . . . 1.000Water . . . . - 700
Total . . . . - 2.600
Reversed bill
Jane Smith....
Electricity . . . . 900
Gas . . . . . 1.000
Water . . . . . 700
Bud. billings. 2.900
Credit memo . . 300
Reverse invoice
Documentoutsorted
Document implausible
Reverse billing
Correct data Restart billingRestart
invoicing
Procedure for Full Reversal
(C) SAP AG IUT110 47
9.48
SAP AG 1999
The invoicing procedure includes:
Invoicing and printing of the bill
Requests for budget billings or creation of partial bills
Different reversal procedures
Flexible settlement control
Budget billing procedure
Budget billing: statistical posting or debit entry
Payment plan: fixed amounts or variable amounts
Output
Printout on R/3 printer using spool
Raw data interface for external mail processing
Archiving
Invoicing: Unit Summary
(C) SAP AG IUT110 48
9.49Billing and Invoicing Exercises
Unit: Billing and invoicing
Topic: Billing a business partner
At the conclusion of these exercises, you will be able to:
Describe the billing process and tasks.
Use the billing and simulation functions.
Various business processes require the billing of an individual customer. This may be necessary due to the move-out of a customer, by the express wish of a customer or to advise a customer, for example.
Carrying out a simulation for any billing period, or for an actual billing period, allows you to provide specific information, without altering data.
1-1 Business partner TB100120## with contract account TB100120## comes in to the customer center to report his/her move-out. You process the move-out and create the final billing. Check the move-out date and the bill sum total in the customer overview.
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.How would you proceed?___________________________________________________
___________________________________________________
___________________________________________________
___________________________________________________
(C) SAP AG IUT110 49
1-1-3 Execute move-out processing: Enter meter readings
Meter reading by customer.
Enter a plausible meter reading for each device and each register. 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. Use printer LT0Q.
How would you proceed?___________________________________________________
___________________________________________________
Exit move-out processing
How would you proceed?___________________________________________________
___________________________________________________
(C) SAP AG IUT110 50
1-1-4 Check the move-out in the customer overview.
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.
1-2 Business partner TB100110## comes into the customer center and would like an interim billing. From the CIC, enter the meter readings supplied by the customer. Display the individual simulation of the billing. First, check the meter reading results and then request the actual billing.
1-2-1 Enter the meter readings for business partner TB100110## using the CIC.
How would you proceed?Which meter readings have you entered?______________________________________________________
______________________________________________________
______________________________________________________
(C) SAP AG IUT110 51
1-2-2 Carry out the individual simulation and display the bill for business partner TB100110##.
For the bill simulation, go to the SAP Easy Access menu and choose Utilities Industry Billing Billing Execution Individual Processing Individual Simulation Billing.
The most useful means of selection is via the contract account.
Choose the Display bill level of processing.
How would you proceed?______________________________________________________
______________________________________________________
______________________________________________________
1-2-3 Process and display the individual bill for business partner TB100110##.
For the individual bill, go to the SAP Easy Access menu and choose Utilities Industry Billing Billing Execution Individual Processing Individual Bill.
The most useful means of selection is via the contract account.
Choose the Bill level of processing.
How would you proceed?______________________________________________________
______________________________________________________
______________________________________________________
1-3 Display the billing document for the water contract of business partner TB100110## and answer the following questions.
1-3-1 Display the billing document.
How would you proceed?______________________________________________________
(C) SAP AG IUT110 52
______________________________________________________
______________________________________________________
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.______________________________________________________
1-4-2 Billing simulation must be carried out before billing. ______________________________________________________
1-4-3 After billing, the billable orders are produced._____________________________________________________
1-4-4 The billing documents are processed further during invoicing._____________________________________________________
1-4-5 Individual billing items can be entered manually as backbilling or as a credit memo.______________________________________________________
(C) SAP AG IUT110 53
Exercises
Unit: Billing and invoicing
Topic: Invoicing a business partner
At the conclusion of these exercises, you will be able to:
Describe the invoicing process and tasks.
Use the invoicing and simulation functions.
Explain the budget billing procedure.
Provide information on the budget billing plan.
The billing results are compared with the transactions in open item accounting. The bill sum total is determined in this way.
After calculating the budget billing plan for the next period, the bill can be printed with details of the bill due date and the new budget billing amount due date.
2-1 Execute the invoicing simulation for business partner TB100110##. 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
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##.
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-3-1 From the customer overview, display the print document for business partner TB100110##.How would you proceed?__________________________________________________________
__________________________________________________________
(C) SAP AG IUT110 55
2-3-2 How many line items does the print document contain?How would you proceed?______________________________________________________
______________________________________________________
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 True or false?
2-4-1 Invoicing is only carried out after billing.______________________________________________________
______________________________________________________
2-4-2 Only one invoice is ever generated for all contracts of the contract account.______________________________________________________
______________________________________________________
2-4-3 The invoice takes into account billing documents from other company codes.______________________________________________________
______________________________________________________
2-4-4 The bill due date is always derived from the posting date and the terms of payment. ______________________________________________________
______________________________________________________
(C) SAP AG IUT110 56
2-4-5 The invoice generates the print documents.______________________________________________________
______________________________________________________
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
9.50Billing and invoicing Solutions
Unit: Billing and invoicing
Topic: Billing a business partner
1-1 From the SAP Easy Access menu, choose:
Choose Utilities industry Customer service Front Office/Customer Interaction Center Customer Interaction Center.
Identify the business partner by entering the number TB100120## in the Business partner field and choose Enter twice. The business partner is stored on the clipboard.
1-1-1 Choose the Move-out partner call that is found under the Move I/O call group.
1-1-2 Enter the move-out date. You are now in the move-out processing screen.
1-1-3 Choose the MR data tab and enter plausible meter readings. Pay attention to the column meter reading status (RS). This must have a value of 1. If the value is different, you have entered an implausible meter reading result and can use the Correct button to enter a plausible result. Choose the Final bill button. You must enter a reconciliation key. Enter IUT110-01 and save the data.Confirm the data for printing.Save the move-out.
1-1-4 You return to the CIC. Refresh your data in the navigation area. Go to Info and choose Customer overview. Check that the tabs for the contracts have been deactivated. In the MvOut date field, you can see the date on which the customer moved out. Double-click on the invoice sum total to display the print document.Choose the End contact button.
1-2 From the SAP Easy Access menu, choose:
Choose Utilities industry Customer service Front Office/Customer Interaction Center Customer Interaction Center.
Identify the customer.
1-2-1 Choose the action Enter customer meter reading. Enter the meter reading results for each contract individually and save the entries. (You will have to carry out this process three times).
1-2-2 From the SAP Easy Access menu, choose:
Utilities industry Billing Billing Execution Individual Processing Individual Simulation Billing
1-2-3 From the SAP Easy Access menu, choose:
(C) SAP AG IUT110 58
Utilities Industry Billing Billing Execution Individual Processing Individual Bill.
1-3 Choose Utilities Industry Billing Billing Execution Display Document.
1-3-1 Choose F4 for help in the Document no. field. Enter your business partner number. You will receive a list of all the billing documents of the customer to choose from.
1-3-2 The header data of the billing document provides the most important data for billing.
1-3-3 The Table overview button provides an overview of the billing lines.
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, since billing processes the meter reading results and provides prices of valuated quantities for invoicing.
1-4-2 False. The billing simulation is only a demonstration of how the real billing would be carried out. The billing simulation produces simulation documents that can be used only for invoice simulation purposes.
1-4-3 False. The billing order results from the creation of the meter reading order. “Billable” status is granted when a billing-relevant meter reading becomes available. Invoice orders are the result of billing.
1-4-5 True. Contrary to the billing documents, the billing simulation documents can only be processed further by invoicing simulation.
1-4-6 True.
(C) SAP AG IUT110 59
Solutions
Unit: Billing and invoicing
Topic: Invoicing a business partner
2-1 From the SAP Easy Access menu, choose:
Utilities industry Invoicing Invoice Processing Individual Processing Create Bill.
2-1-1 Activate the indicator for simulation runs and identify your business partner. Enter a reconciliation key (IUT110-##).
2-1-2 Begin the simulation with all the billing documents.
2-1-3 After the simulation you can check the log. Choose the Display Document button or go to the SAP Easy Access menu and choose:
Utilities industry Invoicing Invoice Processing Display Print Document.
2-1-4 Choose the Simulate bill button .
2-2 Go to the SAP Easy Access menu and choose:
Utilities Industry Invoicing Invoice Processing Individual Processing Create Bill.
2-2-1 Identify the business partner. Enter a reconciliation key.
2-2-2 Once the invoicing has been completed successfully, you can display the log.
2-2-3 From the SAP Easy Access menu, choose:
Choose Utilities industry Customer Service Front Office/Customer Interaction Center Customer Interaction Center.
Identify the business partner by entering their number in the Business partner field. Choose Customer overview from the Information call group. Do not leave this display.
2-3
2-3-1 Double click on the total amount of the bill. You will automatically branch to the print document display.
2-3-2 The number of print document lines is displayed under Document overview.
2-3-3 Go to Header data and view the bill amount.
(C) SAP AG IUT110 60
2-3-4 Choose Document overview.
In the Rate field, you can read the various rates used in the calculation. Choose Doc. lines.
If necessary, leaf through the various line items with different line categories using F6 or F7 or
2-3-5 Choose Header data.
The Net due date field contains the bill due date.
2-4
2-4-1 True. Invoicing processes the meter reading results and the open item accounting data and, using this information, generates the bill and the new budget billing plan.
2-4-2 False. A contract account can be specified for each account, regardless of whether they are to be billed together with other contracts or separately.
2-4-3 True.
2-4-4 False. The posting date, document date or system date may be used as the baseline date for calculating when the bill falls due.
2-4-5 True.
2-4-6 True.
2-4-7 False. Depending on the budget billing procedure, the bill sum total is determined by calculating the statistically posted budget billings or including the outstanding partial bills.
(C) SAP AG IUT110 61
10
SAP AG 1999
Contents:
Billing master data
Overview of billing master data
Connection to business objects
Rate structure
Rate type and rate category
Rates, operands, and schemas
Prices
Rate determination
Rate allocation
Billing Master Data
(C) SAP AG IUT110 1
10.2
SAP AG 1999
At the conclusion of this unit, you will be able to:
Explain the function of rate master data:
Billing class
Operands and operand values
Rate type and rate category
Prices
Define the rate structure:
Components of the rate
Variant programs in the schema
Rate determination
Describe rate allocation
Billing Master Data: Unit Objectives
(C) SAP AG IUT110 2
10.3
SAP AG 1999
FIFISDSD
AMAMMMMM
GIS,CAD,SCADA
GIS,CAD,SCADA
MMMMPM/PM/CSCS
Customerinformation system
IS-U components
components
External systems
IS-U/CCS as an integratedcomponent of the
R/3 enterpriseinformation system
SDSDCOCO
Sales & DistributionSales & Distribution
Contract
A/R + A/P(FI-CA)
Contract
A/R + A/P(FI-CA)
Billing/InvoicingBilling/
Invoicing
Installationservices
Installationservices
Premiseentry
Premiseentry
ExternalExternalPremisePremise
EntryEntrySystemsSystems
ExternalExternalSalesSales
SystemsSystems
FinancialAccountingFinancial
Accounting
DeviceManagement
DeviceManagement
Plant Maintenance
& ServiceManagement
Plant Maintenance
& ServiceManagement
Asset Management & Materials Management
Asset Management & Materials Management
SAPBusinesspartner
SAPBusinesspartner
CCUUSS TTOOMM EE
RR
CCAA
RREE && SS EE RR VV
II CCEE
SDSD
ExternalSales
Systems
ExternalSales
Systems
Sales & Distribution
Sales & Distribution
Rate StructureRate Structure
• Link to master data
• Rate type, rate categ.
• Rate definition, prices
• Operands, schemas
• Rate determination
• Link to master data
• Rate type, rate categ.
• Rate definition, prices
• Operands, schemas
• Rate determination
Billing Master Data: Overview
(C) SAP AG IUT110 3
10.4
SAP AG 1999
SAP Utilities
Billing master data enables you to specify contract billing rules for both residential and non-residential customers and provides the basis for a complete modeling of rates.
The flexible universal structuring of rates allows you to implement new and creative sales and marketing concepts.
An open architecture allows you to adapt and succeed in a changing environment.
Billing Master Data: Introduction
(C) SAP AG IUT110 4
10.5
SAP AG 1999
Sales and marketing requirements
Description of new products and market segments
Utilities industry
Specification, checking and release of new contracts
Customizing of billing master data
Creation of rate category and rate type
Definition of rates, prices, and discounts
Maintenance of agreed special conditions
Billing Master Data: Business Scenario
(C) SAP AG IUT110 5
10.6
SAP AG 1999
Billing of contracts for residential and non-residential customers
Supports billing procedures for international utility management, such as periodic, interim and period-end billing, floating backbilling, final billing, budget, average monthly and equalized billing, and so on.
Open to new billing procedures
Third party billing and cross-company code billing
Special features: Examples include thermal gas billing, billing for external generators and installations without a meter.
Billing of Utility Services
(C) SAP AG IUT110 6
10.7
SAP AG 1999
IS-UIS-U
FI-CAFIFI--CACA
SD, CS, PMSD, CS, PM
Cross appl.CrossCross applappl..
FI-CAdocument
FI-CAdocument
Billingdocument
(utility)
Businesspartner
ContractA/R + A/PContractA/R + A/P
Contract(utility)
Regionalstructure
Premise
EquipmentConnection
DeviceCategory
Register
Device location
Customercontact
Connectionobject
Rate-relevant
information
Device
InstallationPoint of delivery
Business Objects: Rate Allocation
The installation, the device, and the register contain information relevant to the rate. The installation contains:
Billing classRate category
The device contains:Rate categoryFact groupPrice class
The register also contains:Rate categoryFact groupPrice class
(C) SAP AG IUT110 7
10.8
SAP AG 1999
Contractper division
Installation
Device
Register
Billingclass
Ratecategory
Rate type
Rate type
Fact group
Price class
Price class
Fact group
Installations are classified for billing via the billing class
The rate category influences indirect rate determination
The rate type and the rate category determine the rate used for billing.
The fact group contains values relevant to billing.
The price class determines the rental price in conjunction with the price level.
Rate Allocation: Overview
Billing classClassification of installations, for example, for residential customers or non-residential customers.
Rate categoryClassification of an installation for billing. The rate category is used in conjunction with the rate type to determine the rate. In the rate category, you establish the criteria for billing which govern the rates. These criteria can, for example, control the period-end billing or calculation of the budget billing.
Rate typeYou can allocate a rate to registers, devices, a rate category, or an installation using a rate type.
(C) SAP AG IUT110 8
10.9
SAP AG 1999
Classifies installations within a division, for example residential/nonresidential contract.
Can be valid for several rate categories.
Used for plausibility checks in scheduling and in the billing master data.
Enables several franchise fee groups to be defined.
Can be used as a statistical criteria.
If you change the billing class, you must also change the rate category. You do not have to perform a final billing.
Billing Class I
The billing class classifies installations for billing. The billing class is also used for the following purposes:
For consistency verifications between the master data and billing master data. For example, you can verify that a residential customer's installation has not been allocated to a nonresidential contract.
As a statistical criteria, for example in the sales statistics.
(C) SAP AG IUT110 9
10.10
SAP AG 1999
Valid for one division only
Belongs to a single billing class
Contains one valid billing schema
Controls billing - used to determine the rate in conjunction with the rate type
Determines which outsorting checks occur during billing
Controls floating backbilling and period-end billing for nonresidential customers
Controls advance billing and dynamic period control
Rate Category I
The billing class classifies installations for billing. The rate category is used in conjunction with the rate type to determine the rate. Examples of rates are: Household rate Commercial rate Commercial rate with demand measurement Industrial rate Minimal consumption rate Basic price rate 1 Basic price rate 2 Domestic water Reserve wasser Water for fire fighting
Rate determination:rate type + rate category = rate
(C) SAP AG IUT110 10
10.11
SAP AG 1999
RateCategoryBilling Class
OutsortingGroup
Division
Notes Backbilling/Period-End Billing
DynamicPeriod Control
Billing Schema
Advance Billing
Rate Category II
The rate category contains data that controls the processing of billing data. This includes: Billing Schema Control of period-end billing and accompanying backbilling Outsorting checks
Any other billing-relevant data is also saved in the rate category. This includes any agreed quantities, demand, prices, or flat rates. In the case of flat rate services (such as cable services and street lights), no quantities are measured. You must therefore define replacement values that the system can use for evaluation (for example number of cable connections or number of street lights with a specific connection value).
(C) SAP AG IUT110 11
10.12
SAP AG 1999
Used to classify
Registers
Devices
Flat rates
Reference values
for billing
Examples: peak and off-peak rates for active energy; peak rate for reactive energy; peak rate for active power; gas and water consumption; flat rate installations
The rate category is used in conjunction with the rate type to determine the rate.
Definition of Rate Type
Generally, you enter the rate type in the register. Examples of rate categories are peak and off-peak rates for active energy, peak rates for reactive energy, peak rates for active power, as well as gas and water consumption.
In exceptional cases you can allocate the rate type to the following objects: Device
For devices without registers (such as ripple control receivers) you can use the rate type to find special rates. Using these, you can calculate a device-based settlement price.
FactsUsed to determine rates that cannot be derived from registers.Also used to determines rates for flat rate installations without installed devices.
Reference valuesUsed to model street lights, for example
(C) SAP AG IUT110 12
10.13
SAP AG 1999
Rate structure
Technology
Rate
Rate steps
Variantprograms
Operandcategory
Operand
The rate forms the basis for the billing rule for a device, register, or reference value (facts).
Individual rate steps apply billing rules, control account determination and the creation of billing line items, and take into account the franchise fee.
Billing rules have been implemented in the variant programs.
Operands are the input and output parameters of the variant programs.
Business Objects: Rate Structure
(C) SAP AG IUT110 13
10.14
SAP AG 1999
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.
Rate
(C) SAP AG IUT110 14
10.15
SAP AG 1999
QUANTITY FACTOR QUANTITYCalculates x% of a quantity
QUANTITY FACTOR QUANTITYCalculates x% of a quantity
. . . . . .
. . . . . .
NUMBER OF DEMAND PEAKS DEMANDCalculates N peak averages
NUMBER OF DEMAND PEAKS DEMANDCalculates N peak averages
DEMAND PRICE BILLING LINE ITEMSValuates demand with a price
DEMAND PRICE BILLING LINE ITEMSValuates demand with a price
. . . . . .
QUANTITY QUANTITY QUANTITYDifference of two quantitiesQUANTITY QUANTITY QUANTITYDifference of two quantities
. . . . . .
. . . . . .
QTY PRICE BILLING LINE ITEMSValuates energy with a price
QTY PRICE BILLING LINE ITEMSValuates energy with a price
ACT_KWH 0.5 ACT_50%ACT_KWH 0.5 ACT_50%
REACT_KWH - ACT_50% BILL_REACTREACT_KWH - ACT_50% BILL_REACT
BILL_REACT UNI 0.06 BILLING LINEITEMS
BILL_REACT UNI 0.06 BILLING LINEITEMS
Variant poolVariant pool
Variant poolVariant pool
Contract text:
The reactive energy that exceeds 50% of the active energy is valuated using a separate price.
Contract text:
The reactive energy that exceeds 50% of the active energy is valuated using a separate price.
*
*
* *
*
-
Example: Billing Rule for Electricity
(C) SAP AG IUT110 15
10.16
SAP AG 1999
Rate step Fact group
Grouping of individual facts allocated to a rate
Elementary calculation and processing step
Rate
Rate Structure
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
SAP AG 1999
Rate
Permissibility
Division
Usage type
Register operand
Validation class
Minimum time portion required for
extrapolation
Billing class
Rate Data
(C) SAP AG IUT110 17
10.18
SAP AG 1999
Rate stepBudget billing
debit and credit sub-transactions
Statistical rate
Fine-tuned control of variants(additional
parameters)
Franchise fee group
Input andoutput operand(s)
Variant program
Indicator for optional billing step
Billing debit and credit sub-
transactions
Data for the Rate Step
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
SAP AG 1999
Fact group
Operands
Operandvalues
Structure of the Fact Group
A fact group is the grouping of individual facts allocated to a rate. Facts are:
Specific values, for example, 100 kW, orKeys, 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 kWdiscount 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
SAP AG 1999
Operands
Operandcategory
Division
Unit of measurement History management
Weighting key
Access control
Rounding rules
Determination of the demand peaks
Operand Data
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 down0 for rounding to the nearest whole number
(C) SAP AG IUT110 21
10.21
SAP AG 1999
Operand category Description
AMOUNT AmountDEMAND Services (general)
FACTOR Number with decimal places
QUANT Quantity (general)
QPRICE Quantity-based price
REFVALUE Reference value
SEASON Season
TPRICE Time-based price
Operand Categories/Examples
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
SAP AG 1999
Operandcategories
Operands Operand values
• Predefined
• Control processingvia variant programs
• Determined individually
• Serve as the parameters for variant programs
• Provide operandswith values
• Define actualvalues
Rate Determination - Operands
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
10.23
SAP AG 1999
Price C0.70
Price C0.70
Price B0.60
Price B0.60Rate category
factsRate categoryRate category
factsfacts
Rate facts and rate fact groupRate facts and rate fact groupRate facts and rate fact group
Have precedence over
Have precedence over
Price A0.55
Price A0.55
H i
e r
a r
c h
yAllocation of Operand Values
Installation facts
Installation facts
Operand values are usually stored in the rate facts and are, therefore, valid at rate level. You can also define specifications for all rates in the rate category facts and the installation facts. These specifications have preference over the rate facts.
At rate level or rate-category-fact level, you can enter a replacement value instead of a fixed operand value (mandatory/optional entries are required at sub-ordinate levels). With these replacement values, flexible allocation of operand values is possible.
You can also historically override operand values. In this way, a different price key can be allocated to a certain installation for only a certain period of time, for example, a month. In the other months, the values from the rate facts are used.
If no operand value can be determined during billing, billing is aborted and the error is reported in the billing log. Exception: the rate step is marked in the rate as an optional rate step.
You define general operand values that are valid for a larger group of customers in the rate and rate category facts, and you store individual values at the installation fact level (for example, installed demand, connection loads, ordered demand, number of persons, floor area).
(C) SAP AG IUT110 24
10.24
SAP AG 1999
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
Schema 1
A schema is a structure that defines the sequence in which variant programs of the rates to be billed are executed.
(C) SAP AG IUT110 25
10.25
SAP AG 1999
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
Schema 2
(C) SAP AG IUT110 26
10.26
SAP AG 1999
Quantity-based price for quantities and consumption
Flat ratefixed 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 pricefor demand and connection values
Price Categories
The price categories are predefined by SAP and cannot be changed. The price categories are used internally to control data processing. Normally, you create the prices based
on the rate. In this case, the correct rate is proposed by the system.
(C) SAP AG IUT110 27
10.27
SAP AG 1999
Normal pricePrice that is not based on the quantity
Block priceOne or more prices that are based on the quantity
Scale pricePrice that is based on the quantity
Price Types
The price type specifies how the particular price is to be used. In addition to standard single prices, you can also use scale and block prices. Certain sequential quantity ranges (for demand and/or energy) are defined by price scaling. If one
quantity range is exceeded, the price for the next quantity range applies for the entire quantity. In this way, higher consumption can be cheaper than lower consumption.
Certain sequential quantity areas (for demand and/or energy) are defined by price blocking for which certain prices apply, in other words different prices are used. This prevents higher consumption from being cheaper than lower consumption.
(C) SAP AG IUT110 28
10.28
SAP AG 1999
Rate typeRate type Ratecategory
Ratecategory
Household rate
Water, ...
....
1 m3 water . . 3.50
Monthly rent 4,00
....
Allocates
A particular rate category and rate type for a particular period
to a rate.
Rate Determination
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
SAP AG 1999
Generationof billingline items
Generationof billingline items
Validationof
billingresults
Validationof
billingresults
Executionof variantprograms
according to schema
Executionof variantprograms
according to schema
Quantityconversion
andproration
Quantityconversion
andproration
Dataentryand
analysis
Dataentryand
analysis
Data relating tocustomer and
installation
Rate data Procedure data
Contract
Ratedeter-
mination. . .
Schema 1Rate Var.pr. ValuesRate 1
1 VarProg. A x12 VarProg. B x2
. . .Rate 2
1 VarProg. A x32 VarProg. C x43 VarProg. D x5
. . .
. . .
. . .
Rate n1 VarProg. A xxx
EXECUTION
Inst. structureRate cat. facts/
Installation facts
Inst. structureRate cat. facts/
Installation facts
InstallationRatecategory
Rate type
Prices andrate facts
Rate 1
Rate n
Rate Structure
(C) SAP AG IUT110 30
10.30
SAP AG 1999
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
Discounts / Surcharges
(C) SAP AG IUT110 31
10.31
SAP AG 1999
Billing master data is classified by:
Billing class
Ratecategory
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
Billing Master Data: Unit Summary
(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.
DivisionRatecategory
Rate type Rate determined
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 Ratecategory
Rate type Rate determined
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
SAP AG 1999
Contents:
Overview
RTP interface
Components of the RTP interface
Real-Time-Pricing
(C) SAP AG IUT110 1
11.2
SAP AG 1999
At the conclusion of this unit, 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
Real-Time-Pricing: Unit Objectives
(C) SAP AG IUT110 2
11.3
SAP AG 1999
Values determined by automated meter reading for
an interval meter should be billed in the system
Real-Time-Pricing:Business Scenario
(C) SAP AG IUT110 3
11.4
S A P A G 1 9 9 9
E D I / X M L
L o a d s h a p eP o i n t o f d e l i v e r y
( E D I S i n d i c a t o r )
S y s t e m
I n t e r v a lm e t e r
A M Rs y s t e m
S i g n a l
D o w n l o a d
M S C O N S
E D M R T P i n t e r f a c e
B i l l i n g
O t h e rm o d u l e s
S c h e d u l i n g
C o n t r a c ta c c o u n t s r e c e i v a b l e& p a y a b l e
I n v o i c i n g
D e v i c em a n a g e -
m e n t
C u s t o m e r /C o n t r a c t
d a t aI S - U /C C S
R T P O v e r v i e w
(C) SAP AG IUT110 4
11.5
SAP AG 1999
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)
RTP interface
(C) SAP AG IUT110 5
11.6
SAP AG 1999
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, for example)
Inclusion of other profiles for billing
Determination of consumption blocks
RTP-Billing
(C) SAP AG IUT110 6
11.7
SAP AG 1999
E01 load shape: quantity
E03 limit 2: quantity
E02 limit 1: quantity
A01 up to limit 1: quantity
A02 over limit 1: quantity
A03 over limit 2: quantity
A04 over limit 1: demand
Example
(C) SAP AG IUT110 7
11.8
SAP AG 1999
RTP interfaceRTP interface
Installation structure
Logical register
Installation structure
Logical register
InstallationInstallation
Ratecategory
Ratecategory
Rate typeRate type
Rate determination
Rate determination
RatesVarProg.
RatesVarProg.
Billing SchemaBilling Schema
Rate 1Step 1Step 2
Rate nStep 1
VarProg.Example: quantity x price
Comparison of two demands
Operand values1000kWh, 0.25 UNI
400kW, 300kW
Profile
...
P1
P2
P12
Individual RTP interface
Individual RTP interface
PI
Data Model for Billing
The billing master data to be processed and its connections is shown above.
(C) SAP AG IUT110 8
11.9
SAP AG 1999
Result
e1 <sum>
e3 <sum>
e2 <sum>
e4 <sum>
e5 <sum>
y1 = min( x1, x2 )
y2 = max( 0, x1 - x2 )
y3 = y2 * x3
x1
x2
x3
In OutFormula
y1
y2
y3
x1 = Pc1x3 = Pr1
x1 = Pc1x3 = Pr1
x2 = Pf2
Components
y1 -> e1y3 -> e2
y1 -> e3 y3 -> e4
y2 -> e5
Components
pr of ile pr of ile
< value >
Season
Billing period
Weekday
Interface
(C) SAP AG IUT110 9
11.10
SAP AG 1999
Components
Summer
On-peak
Weekend
Off-peak
On-peak
Workday
Off-peak
Winter
On-peak
Weekend
Off-peak
On-peak
Workday
Off-peak
x1
Input Parameters
(C) SAP AG IUT110 10
11.11
SAP AG 1999
Profile
y1 = min( x1, x2 )
y2 = max( 0, x1 - x2 )
y3 = y2 * x3
x1
x2
x3
In OutFormula Profile
y1
y2
y3
Function modules
Formula definition
Profile
Profile
Profile
Profile
Profile
Calculation
(C) SAP AG IUT110 11
11.12
SAP AG 1999
y1
e1
e2
e1 sum QUANTe2 average DEMANDe3 peak DEMAND
Components
Summer
On-peak
Weekend
Off-peak
On-peak
Workday
Off-peak
Winter
On-peak
Weekend
Off-peak
On-peak
Workday
Off-peak
Result Function Op. Cat.
Result
(C) SAP AG IUT110 12
11.13
SAP AG 1999
IS-U billing schema: IS-U billing schema:
y1
result function Op. Cat.
e1 sum QUANTe2 average DEMAND
e3 peak DEMAND
Rate: ON_OFF_PEAK
RegOperand
RTP-Interface ON_OFF_PEAK
001 ....
... ...
007 QUANTI01 ONPEAKCON ... Pricing for ON Peak consumption
008 QUANTI01 OFFPEAKCON ... Pricing for OFF Peak consumption
... ...
Transfer of Results to RTP Operand
(C) SAP AG IUT110 13
11.14
SAP AG 1999
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, for example)
Real-Time-Pricing: Unit Summary
(C) SAP AG IUT110 14
12
SAP AG 1999
Contents:
Budget billing procedure
Determination and requirements of budget billing
Budget Billings
(C) SAP AG IUT110 1
12.2
SAP AG 1999
At the conclusion of this unit, you will be able to:
Explain the difference between a budget billing plan and a payment plan
Create and change budget billing plans
Budget Billing: Unit Objectives
(C) SAP AG IUT110 2
12.3
SAP AG 1999
A customer's consumption pattern has changed.
After adjusting the period consumption, you
recalculate the budget billing plan.
Budget Billing: Business Scenario
(C) SAP AG IUT110 3
12.4
SAP AG 1999
ISIS--UU
Budget billing procedure
Budget billing
A down payment, which is determined from the bill sum total and is recalculated for the next period.
Payment plan
Monthly bills for an agreed amount (fixed or variable), and settlement at the end of the period
Payment plan categories
fixed amountsBudget Billing Plan
variable amountsAverage Monthly Plan
Budget Billing Procedure: Overview
Budget billing categories
statistical posting with budget billing requirements
actual debit entry with partial bill
(C) SAP AG IUT110 4
12.5
SAP AG 1999
Budget Billing Plan
An average amount is determined manually or by simulation. The customer pays this amount for a specified period. At the end of this period, simulation occurs again for the next period. In addition, actual billing occurs monthly. The results of this billing are shown on the bill and settled in the last month of the billing period.
Average Monthly Billing Plan / Equalized Billing Plan
In Average Monthly Billing/Equalized Billing, the customer is charged an average amount based on billings over the next 12 months (or less in the case of new customers). In addition, actual billing occurs monthly, and the results are shown on the bill. The amounts due for later months are calculated using the average of the previous months plus the current bill and the accumulated difference.
Payment Plan Categories
(C) SAP AG IUT110 5
12.6
SAP AG 1999
Manual calculation
Settlement
Budget billing plan
Budget billingcycle
Amountlimits
Amountrounding
Amount adjustmentfactor
Due datedetermination
Automatic determination
Minimumcharge
Printout
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
Budget Billing Plan: Overview
(C) SAP AG IUT110 6
12.7
SAP AG 1999
Business processes
For move-in
For periodic billing Extrapolation
For invoicing Budget billing plan
Amount determination
Manual calculation
Automatic extrapolation
Due date of budget billing amounts
Terms of payment from the contract account
Due date
Grouping of contracts
Amount check
Creating / Adjusting Budget Billing Plans
Utility companies often only bill for their services at the end of a supply period (during annual consumption billing, for example) Therefore, to maintain liquidity during the current period, 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.
Budget billing plans are normally created automatically (during invoicing or move-in, for example). However, they can also be created manually.
Contracts that must be invoiced together are assigned a joint budget billing plan. All other contracts belonging to the contract account can have an individual budget billing plan.
(C) SAP AG IUT110 7
12.8
SAP AG 1999
20002000
11/01 .... .... .... .... .... .... 08/01
Billing period20012001
09/01 .... .... .... .... .... .... 14/01
Budget billing period
Actualmeter reading
Extrapolation of consumption using configured weighting procedure; Billing simulation for this period
Next scheduledmeter reading date from scheduling
Distribution of total simulated amountover the budget billing due dates
Distribution of total simulated amountover the budget billing due dates
Quantity-Based Extrapolation
Billing calculates the consumption up until the next scheduled meter reading date. Simulated billing is carried out for the budget billing period. The budget billing items created in this way are transferred to invoicing in the billing document. Invoicing accepts these amounts and distributes them to the individual budget billing due dates.
When billing, schedule records must already be generated for the next billing period.
(C) SAP AG IUT110 8
12.9
SAP AG 1999
Statistical posting
ISIS--UU
Actual debit-entry
Process budget billing amounts
Due date determination using terms of payment
Scheduling using the portion
Budget billing request
Generation of statistical posting documents that are calculated as down payments towards the bill sum total owed.
FI-CA posting
Statistical posting document
Items per contract
Repetition items for each budget billing amount due date.
Sales tax posting on payments
Creation of partial bills
Generation of debit-entry partial bills that are calculated as down payments against the bill sum total owed.
FI-CA posting
Actual debit-entry
Items per contract
Documents only in customer account when receivable
Sales tax posting on receivables
Budget Billing Amounts Due
The scheduled budget billing dates are determined from the portion valid for the contract and the parameter record. The following details are defined:
Length of the budget billing period (several months or one year)
Budget billing cycle, meaning that the scheduled dates are at regular intervals over the period (monthly or every few months).
The specifications for the portion can be overridden in the budget billing plan or in the contract. 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.
The budget billling due date results from the budget billling dates and the terms of payment in the contract account.
When requesting budget billings, 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.
(C) SAP AG IUT110 9
12.10
SAP AG 1999
You are now able to:
Explain the difference between a budget billing plan and a payment plan
Create and change budget billing plans
Budget Billings: Summary
(C) SAP AG IUT110 10
13
SAP AG 1999
Overview
Documents
Structure
Use
Posting documents
Account display
Payments
Returns
Dunning
Deferral and installment plan
Contents:
Contract Accounts Receivable and Payable
(C) SAP AG IUT110 1
13.2
SAP AG 1999
At the conclusion of this unit, you will be able to:
Describe the document structure in contract accounts receivable and payable.
Provide information on customer accounts.
Explain some common business transactions in Contract Accounts Receivable and Payable and perform them in the system.
Contract Accounts Receivable and Payable: Unit Objectives
(C) SAP AG IUT110 2
13.3
SAP AG 1999
FIFISDSD
AMAMMMMM
GIS,CAD,SCADA
GIS,CAD,SCADA
MMMMPM/PM/SMSM
SDSDCOCO
Sales & DistributionSales & Distribution
ContractContract
A/R + A/PA/R + A/P(FI(FI--CA)CA)
Billing/InvoicingBilling/
Invoicing
InstallationInstallationservicesservices
Premiseentry
Premiseentry
ExternalPremise
EntrySystems
ExternalPremise
EntrySystems
ExternalSales
Systems
ExternalSales
Systems
CentralCentralBusinessBusinesspartnerpartner
Customerinformation system
Componentsof IS-U
Standard R/3Components
FinancialFinancialAccountingAccounting
DeviceDeviceManagementManagement
CCUUSS TTOOMM EE
RR
Plant MaintenancePlant Maintenance& Service& Service
Management Management
Asset Management &Materials ManagementAsset Management &Materials Management
CCAA
RREE && SS EE RR VV
II CCEE
IS-U/CCS as an integratedcomponent of the
R/3 enterpriseinformation system
Customerinformation system
External systems
AMAM
FIFI
FinancialAccountingFinancial
Accounting
Contract
A/R + A/P(FI-CA)
Contract
A/R + A/P(FI-CA)
Contract Accounts Receivable and Payable: Overview
(C) SAP AG IUT110 3
13.4
SAP AG 1999
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
Contract Accounts Receivable and Payable: Business Scenario
(C) SAP AG IUT110 4
13.5
SAP AG 1999
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.
Contract Accounts Receivable and Payableand FI-CA
(C) SAP AG IUT110 5
13.6
SAP AG 1999
FIFI--CACA
Open itemsPosting information
InformationBusiness processesWorkflows
Data exchange
IS-UIS-U IS-TIS-T
IS-IS/CDIS-IS/CD OtherOther
FI-CA Has An Open Architecture
IS-IS-CD: Industry Specific Component - Insurance: collections/disbursements IS-T: Industry Specific Component - Telecommunications
(C) SAP AG IUT110 6
13.7
SAP AG 1999
Suitable for a large number of contract accounts and documents:
Optimal use of storage space by means of a special document structure.
Parallel processing of mass runs (such as payment run, dunning run).
Summarization of general ledger information (summary records).
Processing of business transactions convenient for clerks.
Documents are assigned to business partner accounts and contract accounts (and depending on the industry, they are also assigned to contracts).
Standard processes (such as posting or paying) can be changed without making any modifications.
Special Features of FI-CA
(C) SAP AG IUT110 7
13.8
SAP AG 1999
Business partner
Contains central data, such as names, addresses, communication data and bank details.
Represents a natural or legal person with whom business relationships can be conducted.
Contract account
Contains control data, such as payment methods, terms of payment and dunning procedures.
Object, for which open item accounting is managed in Contract Accounts Receivable and Payable
Usually represents a group of contracts (industry sector).
Contract (industry-specific)
Document items
BP
Account Account
ContractContractContract
IS-U
IS-CA
Account
Central Objects in FI-CA
(C) SAP AG IUT110 8
13.9
SAP AG 1999
Documentposting
Documentposting Payment postingPayment posting
Document reversalDocument reversalAccount
maintenanceAccount
maintenance
Account analysisAccount analysis DunningDunning
Incoming paymentsIncoming payments
InterestInterestInterest
Returnsprocessing
ReturnsReturnsprocessingprocessing
Installment planInstallment plan DeferralDeferral Irrecoverable debtIrrecoverable debt
Contract Accounts Receivable and Payable: Business Transactions
(C) SAP AG IUT110 9
13.10
SAP AG 1999
Overview
Documents
Account display
Payments
Returns
Dunning
Deferral and installment plan
Contract Accounts Receivable and Payable: Posting Documents
(C) SAP AG IUT110 10
13.11
SAP AG 1999
At the conclusion of this topic, you will be able to:
Explain the document structure in contract accounts receivable and payable.
Post receivables items.
Posting Documents: Objectives
(C) SAP AG IUT110 11
13.12
SAP AG 1999
SAP Utilities
If business processes are not integrated with IS-U or SD, or automatically connected to Contract Accounts Receivable and Payable by an interface, individual postings can be inserted into the system as manual documents.
Examples include rent receivables, lease receivables as well as receivables for an energy consultant.
Posting Documents: Introduction
(C) SAP AG IUT110 12
13.13
SAP AG 1999
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
Posting Documents: Business Scenario
(C) SAP AG IUT110 13
13.14
SAP AG 1999
G/L account itemBusinesspartner
item
Document
Documents in Contract Accounts Receivableand Payable
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, such as document date, posting date, reconciliation key.
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.
G/L account item (revenue lines)This contains the data for the profit and loss statement, as well as data for sales tax.
(C) SAP AG IUT110 14
13.15
SAP AG 1999
General data
General
• Document date• Document type• Document number
Document
General Document Data
The document date indicates the issue date of the original document. Document types
Distinguish between business transactions Control document storage using the number range allocated. The document number is determined
during posting by the number range. Are valid for a single client Examples of document types are: AB Miscellaneous document, GB Fees, FA Invoicing.
Document number Key, which identifies the document in the contract account receivable and payable for each client. Depending on the type of number assignment, the document number is assigned automatically by the
system when the document is posted, or is entered by the user when a document is created. The type of number assignment is decided by the document type entered in the document header. You
specify:A number range from which the document number is chosen.Whether the number is entered automatically or manually.
(C) SAP AG IUT110 15
13.16
SAP AG 1999
General
• Document date• Document type• Document number
Document
Reference andcurrency• Reference• Currency• Conversion rules
General data
Document Data: Reference and Currency
The reference document number can contain the document number for the business partner. This field can also be filled with other data.The reference document number is used as a search criterion for document display or change. In correspondence, the reference document number is sometimes printed in place of the document number. Enter the number specified by the partner. If the document was generated in your company and a document number is not known for the partner, it is possible to copy the document number in the reference number field by entering "*".
The transaction currency is the key of the currency, in which the document is (or was) posted. Exchange rate
Exchange rate used for the conversion between the transaction currency and the local currency. The exchange rate is saved at the item level. The exchange rate that is entered is proposed in the document items during entry of a document (possible entries). The exchange rate field can only be used by clerks who enter documents for company codes with the same local currency. This local currency must be recorded in the user settings.
(C) SAP AG IUT110 16
13.17
SAP AG 1999
General data
General
• Document date• Document type• Document number
Reference andcurrency• Reference• Currency• Conversion rules
General ledger
• Posting date• Reconciliation key• Single document
Document
Document Data: Link to General Ledger Accounting
Posting date: The date on which the document was posted in Contract Accounts Receivable and Payable. 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).
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.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. This means that itemization of the totals posted in the general ledger is possible.You must assign the key for manual postings. For mass processing, the key is assigned by the program that executes processing (such as a payment run).
Document items belonging to one summary record are summarized. If you do not want a summary, you can select single document or single item in the corresponding field for each document. This document is saved in the G/L document as a single document item.
(C) SAP AG IUT110 17
13.18
SAP AG 1999
General data Entry control
General
• Document date• Document type• Document number
Reference andcurrency• Reference• Currency• Conversion rules
General ledger
• Posting date• Reconciliation key• Single document
Document
• Entry variants• Calculate taxes• Jurisdiction code• Company code• Clearing reason• Screen variants
Document Data: Entry Control
The entry variant controls which fields are to be hidden for posting, changing, and displaying a document. This allows you to customize screens for the business transaction (such as a down payment).
The calculation of taxes means that the system automatically calculates taxes using the specifications in the business partner items during simulation or posting. If you do not set the indicator, you have to enter the tax lines separately.
Default value for company code Where no company code is entered, the default company code is added to each document line item.
The company code is an entry aid for documents or line items that are to be posted in the same company code.
The user settings allow you to block cross-company code posting. If this setting has been made, users must enter a company code.
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 clear items using the function Post document, you must specify a clearing reason here. If you do not enter a clearing reason, the system will ask you to enter one before posting the document.
(C) SAP AG IUT110 18
13.19
SAP AG 1999
Additional data-Item text-Grouping-Period key
Businesspartner
item
Clearing data
Due dates: Net/Cash discount/
deferral
Alternative partner for payments
Dunning data/Interest
calculation
Payment data
Repetitionspecifications
Business partner Contract account
Contract
Company codeProcedure
Amounts
Mandatory specifications Optional specifications
Individual transfer to
general ledger
Set automatically
Data on Business Partner Item
Item text can be used both internally and externally. To differentiate between these, texts for external use must begin with "*". This can then be specified on all correspondence, such as dunning notices and payment advice notes. The asterisks are automatically removed when the document is printed.
A grouping key can be assigned to any document items that should be depicted as one item in lists, correspondence and account processing.Example: If a customer bill contains items from different divisions, but only one final amount is payable by the customer, a summarized list simplifies the allocation of incoming payments.
The period key can be used, for example, if details about the billing period that the receivable relates to are to be included in the correspondence. The required key can be entered as an alternative to saving a long text for each item.Examples: Q195 First quarter 1995 0195 January 1995 H195 1.1.1995 - 6.30.1995
(C) SAP AG IUT110 19
13.20
SAP AG 1999
Amounts and tax code
Amounts and tax code
Account assignment for subsequent accounting
Account assignment for subsequent accounting G/L account item
General ledger:Company code,G/L account
General ledger:Company code,G/L account
Data on G/L Account Item
Data on G/L account item: Value date: Day when values are set.
The value date indicates the day on which the financial transaction actually took place in financial accounts (bank accounts, bank sub-accounts). The value date indicates the day on which the financial transaction is expected for payment postings that are generated before payment. The value date is decisive for representation of the cash management position.
A planning level is allocated in the document item of Contract Accounts Receivable and Payable for updating in cash management. The planning level is used for control in cash management.
The tax transaction determines which type of tax is used. The keys are defined in the system and cannot be changed. The transaction key is for documenting the tax type after transfer into R/3 general ledger accounting. Automatic determination of tax accounts is performed using the transaction key. Examples:
TAX is used for output tax.INPUT is used for input tax.
(C) SAP AG IUT110 20
13.21
SAP AG 1999
Receivables / credit memos
Automatic determination of general ledger accounts and tax accounts using transactions
Classification using document type
Automatic determination of due dates using terms of payment in the contract account
Receivables or credit can be cleared immediately
Business partner BP1Contract account CA 1Amount UNI 100
Business partner BP2Contract account CA2Amount UNI 150
Business partner BP3Contract account CA3Amount UNI 250
Manual Document Entry: Items
Receivables and credit memos can be entered manually. During posting, a transaction that is defined in the system is specified for each business transaction. In this way, the general ledger accounts are automatically determined and inserted in the receivables and revenue lines. The same occurs for tax accounts.
Classification of documents occurs with specification of a document type. Due dates are determined automatically using the terms of payment in the contract account. Receivables and credit memos can also be cleared either immediately or partially. Receivables lines can be repeated with different due dates and specification of a start date at monthly or
daily intervals (for example, for budget billing or installment plans). Document line items do not all have to belong to the same business partner.
(C) SAP AG IUT110 21
13.22
SAP AG 1999
Transactions explain the business transactionon 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, which are assigned internally by various IS-U business processes. The transactions also control these business processes.
Transactions in Contract Accounts Receivable and Payable
Example for: Main transaction: periodic billing Sub-transaction: receivable from energy charge
(C) SAP AG IUT110 22
13.23
SAP AG 1999
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
Examples of Transactions
Statistical posting simplifies the administration of doubtful receivables (items), as these postings are not transferred to the general ledger, and are thus easier to reverse if they are not paid.Budget billing receivables are a typical example, as in most cases, there is no bill and the collection of payment, if payment is not made, is less likely than in cases where a bill exists. Similarly, tax is only due for statistical budget billing receivables, 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.
(C) SAP AG IUT110 23
13.24
SAP AG 1999
1. Doc.: Amount UNI 580Net UNI 500Tax UNI 80
2. Doc.: Amount UNI 116Net UNI 100Tax UNI 16
Reconciliation key: 98126ISU01
Documentposting
FI-CA documents
D 140000 UNI 696C 800000 UNI 600C 175001 UNI 96
Reconciliation key98126ISU01
Summary Record
Generatepostings
FI documents
40 140000 696,--50 800000 600,--50 175001 96,--Reference key
98126ISU01Reference transaction
FKKSU
Transfer to General Ledger Accounting
One use of the reference key is to relocate individual items in the sub-ledger (taken from the general ledger).
(C) SAP AG IUT110 24
13.25
SAP AG 1999
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.
They can be grouped according to G/L accounting and subsequent application criteria.
Examples for summarization criteria are:
Company code and date
Debit/credit indicator
General ledger account
Currency
Downstream system criteria
Summary Record
(C) SAP AG IUT110 25
13.26
SAP AG 1999
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.
Contains the amount to be posted.
Contains the account assignment for G/L accounting determined by the transaction.
The G/L account item contains information on the corresponding G/L account.
Posting Documents: Summary (1)
Repetition lines also exist in the document.They make it possible to save memory space and are used for representing budget billing plans and installment plans. Receivables lines form the basis of repetition lines and can be repeated for different due dates. From the clerk's point of view, these lines are irrelevant since they appear in the contract account display as normal items and can be processed accordingly.
A document does not have to contain all of the lines mentioned above. One example of this is a normal payment that leads to complete clearing of the affected receivables lines. In this case, only a new document header is written for the payment, since the data relevant for the account assignment comes from the receivables lines.
(C) SAP AG IUT110 26
13.27
SAP AG 1999
If necessary, documents can be posted manually in Contract Accounts Receivable and Payable.
This is possible for both receivables and credit memos.
An item can be entered:
Individually
In a list
Posting Documents: Summary (2)
(C) SAP AG IUT110 27
13.28
SAP AG 1999
Overview
Documents
Account display
Payments
Returns
Dunning
Deferral and installment plan
Contract Accounts Receivable and Payable: Account Display
(C) SAP AG IUT110 28
13.29
SAP AG 1999
At the conclusion of this topic, you will be able to:
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.
Use the "Customer overview" and "Customer account” information processes.
Account Display: Objectives
(C) SAP AG IUT110 29
13.30
SAP AG 1999
SAP Utilities
Utility companies often have to deal with large numbers of items due to the large number of customers and budget billing payments.
Information on customer accounts is given quickly and comprehensively.
Variable displays are provided that can easily be adjusted according to the situation.
Different display formats can be used depending on the tasks of the clerk (accounting, dunning, for example)
Individual selection of display variants can be defined in the user parameters.
Account Display: Introduction
(C) SAP AG IUT110 30
13.31
SAP AG 1999
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
Account Display: Business Scenario
(C) SAP AG IUT110 31
13.32
SAP AG 1999
Business partner, contract account, contractCompany code, installment plan, collective bill
List category for restricting the items to be displayed according to "status":Examples: All open, due, or statistical items.
User-specific limitations
List representation defines the line structure
Any type of sorting is possible
Account Display: Initial Screen
(C) SAP AG IUT110 32
13.33
SAP AG 1999
The list category determines which items are selected for the account display (such as open items or down payment requests).
The list category makes it possible to save frequently used selections under one key.
As an alternative to selecting items using list categories, you can select:
Standard, in order to choose the standard selection (all open, non-statistical items).
Detail, in order to specifically determine the selection of items.
Even if a list category is used, the selection can still be changed using "detail". This change is not saved and is only used for the current display.
Account Display: List Category
(C) SAP AG IUT110 33
13.34
SAP AG 1999
Determines which fields of a document are included in the
account display.
Different line structure variants can be selected in the
account display. It is also possible to totalize values using
particular criteria.
The same output list can be viewed in a number of ways.
Account Display: Line Layout
(C) SAP AG IUT110 34
13.35
SAP AG 1999
OverviewOverview
HeaderHeader
G/Litemlist
G/Litemlist
Itemlist
Itemlist
Detail screenof
business partner items
Detail screenof
business partner items
Detail screen of
G/L items
Detail screen of
G/L items
Account Display: Navigating in the Document Display
It is possible to return to the header from any screen.
(C) SAP AG IUT110 35
13.36
SAP AG 1999
Variable item selection
All items/open items/cleared items (with/without payments)
Statistical items (all/budget billing plan/charges/...)
User-specific selection criteria Example: By due dates
Variable display
"Free" selection of data fields
User-defined account display
Account Display: Summary (1)
(C) SAP AG IUT110 36
13.37
SAP AG 1999
Immediate access to environment data
Document
Business partner/contract account/contract
Payment use
Source receivable(s) for installment plan items
Dunning history
...
Sort and summary functions within the account display
Account Display: Summary (2)
(C) SAP AG IUT110 37
13.38
SAP AG 1999
Overview
Documents
Account display
Payments
Returns
Dunning
Deferral and installment plan
Contract Accounts Receivable and Payable: Payments
(C) SAP AG IUT110 38
13.39
SAP AG 1999
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
Payment Run: Objectives
(C) SAP AG IUT110 39
13.40
SAP AG 1999
SAP Utilities
Utility companies have to deal with large numbers of
incoming payments in a reliable efficient manner.
Payment flow reaches the utility company in various
ways. These include data medium exchange,
automatically read documents and other documents.
Background and dialog processes are provided for
processing payments, depending on the situation.
Payment Run: Introduction
(C) SAP AG IUT110 40
13.41
SAP AG 1999
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
Payment Run: Business Scenario
(C) SAP AG IUT110 41
13.42
SAP AG 1999
ManualManualAutomaticAutomatic
Automatic and Manual Payments
Automatic incoming payments
Collection procedure
Credit repayment
Returns
Payment lot
Check lot
Credit card lot
Payment at cash desk
Returns lot
Automatic incoming payment: Incoming payment data from previous systems, financial institutions, or agencies is processed here. The system automatically creates a payment posting for the corresponding business partner. Payments are automatically allocated to one or more receivables items. Credit items released for settlement are also taken into account.If an item cannot be allocated, it is possible to post an account at contract account level. Manual post-processing is also possible.
Collection procedurePayments are handled by collection or direct debit from financial institutes or credit card companies and the corresponding output media are created.
Credit repaymentCredit is automatically repayed by check, bank transfer or postal cash payment order and the corresponding output media are created.
Returns processingAutomatic returns processing with workflow link is provided for returned payments from financial institutions and credit card companies, as well as for returned incoming checks and postal cash payment orders that could not be delivered.
(C) SAP AG IUT110 42
13.43
SAP AG 1999
The payment lot stores data from external payments.
Payment data is stored in a lot if:
It has the same source
It is to be processed jointly.
Data for a group of incoming checks is stored in a payment lot. This type of lot is called a check lot.
Bank transfers and/or debit memos that were received are extracted from an account statement and stored in a payment lot.
Payment Lot
(C) SAP AG IUT110 43
13.44
SAP AG 1999
Header entryHeader entryHeader entry Data is saved in the payment lot header if:
It applies to the entire lot
It is used as a default value for items
Payment Lot: Structure
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.45
SAP AG 1999
Item 2Item 2Item 2
Item 1Item 1Item 1
Header entryHeader entryHeader entry Data is saved in the payment lot header if:
It applies to the entire lot:
It is used as a default value for items
An item is a payment with:
An amount
Specifications for the selection of receivables to be cleared
Payment Lot: Structure
(C) SAP AG IUT110 45
13.46
SAP AG 1999
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.
New payment
lotCreate Close Post
Paymentlot
complete
ChangePost-
processing
Payment Lot: Processing Steps
(C) SAP AG IUT110 46
13.47
SAP AG 1999
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, items, and the clearing of open items
New payment
lotCreate Close Post
Paymentlot
complete
Payment Lot: Create
Default values on the header screen: The current date is defined The last values entered (if available) are inserted automatically for the company code, currency, and
business area. The document type, clearing reason, and the selection categories are recorded in Customizing.
(C) SAP AG IUT110 47
13.48
SAP AG 1999
The essential entries are:
Amount
Payment use via selection category and selection value, which are essential for choosing open items that are cleared by payment.
Selection categories are one character abbreviations that are defined in Customizing.
These include: G for business partner, K for contract account, V for contract
New payment
lotCreate Close Post
Payment lot
complete
Payment Lot: Create Items
Enter one line of data for each payment during list entry. Variants of the line structure can be recorded in Customizing. You can change the entry variants using the Screen variant key.
By pressing the Additional specifications key, you can branch to the detail screen of the selected item. You can enter additional data on the payment, if required.
On the detail screen, you can enter any additional data necessary for payment allocation or for further clarification.
(C) SAP AG IUT110 48
13.49
SAP AG 1999
Items can be deleted and added as long as the payment lot is not closed.
Data on items that have already been entered can also be corrected.
Interrupted entry of a payment lot can be resumed using this function.
New payment
lotCreate Close Post
Paymentlot
complete
Change
Payment Lot: Change
(C) SAP AG IUT110 49
13.50
SAP AG 1999
Closing a payment lot means that adding or deleting items is no longer possible.
Corrections can still be made on the payment lot items after closing.
Posting cannot begin until a lot is closed.
New payment
lotCreate Close Post
Payment lot
complete
Payment Lot: Close
(C) SAP AG IUT110 50
13.51
SAP AG 1999
Postings can either be dealt with in dialog mode or in a background process (typical for mass data).
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
New payment
lotCreate Close Post
Paymentlot
complete
Payment Lot: Post
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, and one posting for clearing account to payment use for each check (in planning). 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. 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 itemsPostings on accountExpense/revenue (payment difference)Generation of new receivables that are cleared immediately (charges, interest)
(C) SAP AG IUT110 51
13.52
SAP AG 1999
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, charges, down payments) caused by clearing
Posting of the clearing document and noting the clearing information in the items to be cleared
Automatic Clearing: Process
(C) SAP AG IUT110 52
13.53
SAP AG 1999
If automatic allocation was not possible:
Clarification of payment use and transfer from interim account to a contract account.
Correction of payment items (such as selection specifications) and restart of postings for selected items.
Manual posting and clearing for selected items.
Triggering of repayment if the payment use cannot be determined.
New payment
lotCreate Close Post
Paymentlot
complete
Post-processing
Payment Lot: Post-processing
(C) SAP AG IUT110 53
13.54
SAP AG 1999
00000150900 12131400 67291500 11Do not write in or stamp this field.
Deutsche Bank
CurrencyAmountPay the bearer
Amount in words
Or the holderON
City
Date
Signature
The printed ch eck text must not be altered in an y way.
Check no. Account no.X X Amount X Sort code X Text
New York1.4.1996
DM - 400,-- four hundred
Red Cross
ReceiptYou paid 123.45 UNIon April 15, 2000.
ReceiptYou paid 123.45 UNIon April 15, 2000.
Checkdeposit listCheckdeposit list
PostdirectlyPostdirectly
Post in dialog mode
Post in dialog mode
PaymentpostingPaymentposting
Contract accountBusiness partner
Contract account
Contract
Document number
Net due date
Payment form no.
Payment at cash desk
Within the cash desk function, payments can be directly allocated to open items for a business partner. You can use a payment proposal or assign the payment manually. A distinction is made between cash payments and payment by check or credit card. A receipt can be printed following the posting. If an overpayment is made in cash, 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 cash journal offers further functionalities. You can display a cash desk structure and functions such
as deposits, withdrawals, transfers and cash analysis can be carried out.
(C) SAP AG IUT110 54
13.55
SAP AG 1999
Open items are displayed:
In a list with one line per item and
In a control block that displays the status of clearing processing.
The difference between the clearing amount and the allocated amount is decisive here.
The allocated amount is the sum of the clearing amounts that is allocated to the individual items.
The clearing can be posted if the difference:
Is zero (green light appears)
Is within a predefined tolerance limit (yellow light appears)
Clearing: Dialog Processing
Open item processing:By double-clicking in the Amount column, inactive items become active and vice versa. As soon as an item is active, a value appears in the "Clearing amount” column. The posting amount of the item is proposed.The clearing amount can be overwritten (partial clearing). By double-clicking in the Clearing amount column, the system sets the amount that is necessary to bring the clearing to zero.Items can also be set to active and inactive in groups. To do this, select the items in the left column and then press the desired key (active or inactive).
The processing screen can be reconfigured by pressing the Presentation key.You can switch between selection mode and command mode. The screen width can be set to 80 or 120 characters (more detailed information on items). The summarization of items in the display can be switched on and off.The line structure (information displayed on open items) can be varied.Cash discount fields can be displayed or hidden. The posting amount and clearing amount can be displayed as net or gross. You can change the currency that is displayed.
(C) SAP AG IUT110 55
13.56
SAP AG 1999
Payment can be handled automatically and manually
in Contract Accounts Receivable and Payable.
Payments are processed:
In payment lots
At the cash desk
Detailed rules can be defined for automatic item
clearing.
Payment: Summary
(C) SAP AG IUT110 56
13.57
SAP AG 1999
Overview
Documents
Account display
Payments
Returns
Dunning
Deferral and installment plan
Contract Accounts Receivable and Payable: Returns
(C) SAP AG IUT110 57
13.58
SAP AG 1999
At the conclusion of this topic, you will be able to:
Describe the returns process
Post a return
Returns: Objectives
(C) SAP AG IUT110 58
13.59
SAP AG 1999
SAP Utilities
Utility companies must deal with a large number of incoming and outgoing payments.
A certain percentage of these cannot be successfully processed because the account is incorrect, closed, or not covered.
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
Returns: Introduction
(C) SAP AG IUT110 59
13.60
SAP AG 1999
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
Returns: Business Scenario
(C) SAP AG IUT110 60
13.61
SAP AG 1999
Returns
Return reason
Customercreditworthiness
and tolerance group
Return amountHistory
Return category Number of returns
Returns: Influencing Factors
Every return category is allocated to a return reason. Return reasons can have the same category. The return category determines the accounts used (G/L accounts for returns charges and bank clearing account). Examples are check returns and bank returns.
Bank-specific returns reasons can be allocated to company-specific returns reasons.
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.Creditworthiness can also be maintained manually. Manually maintained creditworthiness automatically overrides calculated creditworthiness.
HistoryMaximum number of days that have passed since an event before the event can be included in the analysis of the returns history.
Maximum amount differenceMaximum difference between the house bank returns amount and the original payment amount that is tolerated for automatic charges posting. As long as the difference amount is within the maximum amount difference, it is interpreted as a charge by the system and posted accordingly.
(C) SAP AG IUT110 61
13.62
SAP AG 1999
ReturnsCalculate lot charges
Correspondence
Incoming payment method
Payment block reasons
Deferral days
Return amount
Dunning block- Contract account
- Items
Post charges statistically
Pass on charges with/without tax
Returns: Activity Settings
Pass on bank charges:Means that the bank passes on the returns charges to the business partner (accompanying contract account). If this is not the case, these charges are paid by the utility company.
Calculation of lot chargeMeans that the business partner has to pay a surcharge in addition to the bank charges. The amount of the lot charge depends on the amount of the returns charge.
By recording a dunning block reason in the master record of Contract Accounts Receivable and Payable or under open items, the items due for dunning or the open items are not dunned when the dunning program is executed.
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.
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.
(C) SAP AG IUT110 62
13.63
SAP AG 1999
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.
New returns
lotCreate Close Post
Returnslot
complete
ChangePost-
processing
Returns Lot: Processing Steps
(C) SAP AG IUT110 63
13.64
SAP AG 1999
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, new receivables)
New returns
lotCreate Close Post
Returns lot
complete
Returns Lot: Create
Default values on the header screen: The current date is defined. The last values entered (if available) are inserted automatically for the company code, currency, and
business area. The document type, clearing reason, and the selection categories are stored in Customizing.
(C) SAP AG IUT110 64
13.65
SAP AG 1999
The essential entries are:
Amount
Returns reason
Payment document number
New returns
lotCreate Close Post
Returns lot
complete
Returns Entry
Enter one line of data for each return during list entry. Variants of the line structure can be recorded in Customizing. You can choose other line structures in Extras --> Screen variants
By pressing the Additional specifications key, you can branch to the detail screen of the selected item. You can enter additional data on the payment, if required.
On the detail screen, you can enter any additional data necessary for payment allocation or for further clarification.
(C) SAP AG IUT110 65
13.66
SAP AG 1999
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.
New returns
lotCreate Close Post
Returnslot
complete
Change
Returns Lot: Change
(C) SAP AG IUT110 66
13.67
SAP AG 1999
Closing a returns lot means that adding or deleting items is no longer possible.
Corrections can still be made to returns lot items after closing.
Posting cannot begin until a lot is closed.
New returns
lotCreate Close Post
Returnslot
complete
Returns Lot: Close
(C) SAP AG IUT110 67
13.68
SAP AG 1999
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
New returns
lotCreate Close Post
Returnslot
complete
Returns Lot: Posting (1)
(C) SAP AG IUT110 68
13.69
SAP AG 1999
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, correspondence, workflow
New returns
lotCreate Close Post
Returnslot
complete
Returns Lot: Posting (2)
(C) SAP AG IUT110 69
13.70
SAP AG 1999
Clarification of return use
Correction of returns item and restart posting for selected items
Manual posting and clearing for selected items
New returns
lotCreate Close Post
Returnslot
complete
Post-processing
Returns Lot: Post-processing
(C) SAP AG IUT110 70
13.71
SAP AG 1999
Basis for future handling of the contract account dependent on:- Period of examination- Number of returns
Record of business management data for returns processing, including: - Amounts- Document numbers
Returns historyReturns history
Returns History
(C) SAP AG IUT110 71
13.72
SAP AG 1999
The utility company can configure the many settings in such a way that detailed work is taken care of in the background.
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
Returns: Summary
(C) SAP AG IUT110 72
13.73
SAP AG 1999
Overview
Documents
Account display
Payments
Returns
Dunning
Deferral and installment plan
Contract Accounts Receivable and Payable: Dunning
(C) SAP AG IUT110 73
13.74
SAP AG 1999
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
Dunning: Objectives
(C) SAP AG IUT110 74
13.75
SAP AG 1999
SAP Utilities
Customer payments can only be reasonably controlled if they are supported by automatic processes.
If payment is delayed, dunning automatically:
Creates a customer letter
Triggers workflows (security requirement, disconnection order)
This is a general procedure and can be adjusted to company requirements and individual customers or customer groups.
Dunning: Introduction
(C) SAP AG IUT110 75
13.76
SAP AG 1999
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
Dunning: Business Scenario
(C) SAP AG IUT110 76
13.77
SAP AG 1999
Businesspartner
Contractaccount
Openitems
Dunninghistory
Determi-nation of
newdunning
levels
Generate dunningproposal
Generate dunning activities
Postinterest
andcharges
Charges schemaPrint forms
ThresholdsDays in arrears
Dunning interval
Dunning: Dunning Proposal and Dunning Activities
The dunning program is divided into two runs. A dunning proposal is created in the first run. In the second run, dunning activities, in particular printing of the dunning notice, are carried out on the
basis of the dunning proposal. The dunning proposal can be processed before you print the dunning notice.
(C) SAP AG IUT110 77
13.78
SAP AG 1999
Dunning process
Dunning procedure Dunning grouping
Dunning frequencyDays in arrears
Minimum/maximum amounts
Creditworthiness
Dunning: Influential Factors
A dunning procedure can be allocated to a contract account or to individual line items in the document. Items due for dunning are dunned according to the settings in the dunning procedure and dunning data is stored in the dunning history.
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.
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.
Another condition for creation of a dunning letter is that the dunning frequency has been reached. To create another dunning letter, at least the specified number of days must have passed since the creation date of the last dunning letter.
Indicator: Always dun dunning level. This means that a dunning letter is always triggered in this dunning level, as soon as the dunning frequency has been reached, regardless of whether the days in arrears and the maximum / minimum amount have been reached, or whether the dunning level has been raised for any items of the same dunning grouping.
The dunning grouping key determines the criteria with which items due for dunning are additionally grouped during execution of a dunning run (for example, business area, contract account, division, or contract). Items due for dunning are always grouped according to the following criteria in the dunning run: business partner, dunning procedure, currency, responsible company code, and dunning letter recipient.
(C) SAP AG IUT110 78
13.79
SAP AG 1999
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
Dunning Proposal for a Business Partner
Possible start parameters for a dunning proposal: General selection criteria:
Company codeBusiness partnerContract accountNet due date
Dynamic selection criteria (from the business partner item contract accounting document):Document numberBusiness areaContractDivisionDocument datePosting dateCurrencyAll other criteria from the document item can also be used.
(C) SAP AG IUT110 79
13.80
SAP AG 1999
Dunning activity:Customer letterDisconnection orderDeactivate installment plan
Dunning charges(Scale schema)
Dunningprocess
Creditworthiness weighting
Print all items
Payment periodInterest
Dunning Levels
Dunning: Factors That Can Be Influenced (Selection)
Different dunning levels can be created for each dunning procedure. Dunning levels determine the dunning intervals, the charges schema used for determining the dunning charges and the way in which interest is calculated and posted. You can also record parameters at every dunning level for printing dunning letters, and for currency-dependent minimum/maximum amounts.
Payment period in days. This is calculated from the dunning issue date and used for the payment target for a dunning letter. 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. Otherwise, only the items due for dunning are printed (items that have reached the number of days in arrears specified).
Creditworthiness weighting is the factor used in dunning to calculate creditworthiness.
(C) SAP AG IUT110 80
13.81
SAP AG 1999
ContractaccountContractaccount
New dunning levelsNew dunning levels
Dunninghistory
Dunninghistory
OpenitemsOpenitems
Dunning procedureDunning grouping
Due dateAmount
Last dunning dateLast dunning level
Where do the influential factors for dunning come from?
Dunning: Determination of Dunning Levels
(C) SAP AG IUT110 81
13.82
SAP AG 1999
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.
More days have passed since the due date than the number recorded for the dunning frequency.
An item that is dunned more than once passes through the various dunning levels according to predefined rules.
The highest dunning level of all items summarized in a dunning group determines which dunning activities are performed for the corresponding dunning group.
Dunning Levels
(C) SAP AG IUT110 82
13.83
SAP AG 1999
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
Printing of Dunning Notice for a Business Partner
(C) SAP AG IUT110 83
13.84
SAP AG 1999
4711 Aug. 01, 2000 DL 4 200 UNI
4712 Aug. 15, 2000 DL 4 150 UNI
4713 Sep. 01, 2000 DL 3 250 UNI
...
4729 Jan. 16, 2001 DL 1 120 UNI
4711 Aug. 01, 2000 DL 4 200 UNI
4712 Aug. 15, 2000 DL 4 150 UNI
4713 Sep. 01, 2000 DL 3 250 UNI
...
4729 Jan. 16, 2001 DL 1 120 UNI
4711 Aug. 01, 2000 DL 4 200 UNI
4712 Aug. 15, 2000 DL 4 150 UNI
4713 Sep. 01, 2000 DL 3 250 UNI
...
4729 Jan. 16, 1999 DL 1 120 UNI
4711 Aug. 01, 2000 DL 4 200 UNI
4712 Aug. 15, 2000 DL 4 150 UNI
4713 Sep. 01, 2000 DL 3 250 UNI
...
4729 Jan. 16, 1999 DL 1 120 UNI
4711 Aug. 01, 1996 DL 4 200 UNI
4712 Aug. 15, 1996 DL 4 150 UNI
4713 Sep. 01, 1996 DL 3 250 UNI
...
4729 Jan. 16, 1997 DL 1 120 UNI
4711 Aug. 01, 1996 DL 4 200 UNI
4712 Aug. 15, 1996 DL 4 150 UNI
4713 Sep. 01, 1996 DL 3 250 UNI
...
4729 Jan. 16, 1997 DL 1 120 UNI
4711 Aug. 01, 2000 MS 4 200 UNI
4712 Aug. 15, 2000 MS 4 150 UNI
4713 Sep. 01, 2000 MS 3 250 UNI
...
4729 Jan. 16, 2001 MS 1 120 UNI
4711 Aug. 01, 2000 MS 4 200 UNI
4712 Aug. 15, 2000 MS 4 150 UNI
4713 Sep. 01, 2000 MS 3 250 UNI
...
4729 Jan. 16, 2001 MS 1 120 UNI
Identification of thedunning run
Identification of thedunning run
Every item relevant todunning has an entryin the dunning history
Every item relevant todunning has an entryin the dunning history
Jan. 30, 2001 1500 UNIJan. 30, 2001 1500 UNI
Jan. 15, 2001 1200 UNIJan. 15, 2001 1200 UNI
Jan. 01, 2001 800 UNIJan. 01, 2001 800 UNI
Dec. 15, 2000 800 UNIDec. 15, 2000 800 UNI
Overview of all dunning levels for a business partner / contract account
Dunning: Dunning History
(C) SAP AG IUT110 84
13.85
SAP AG 1999
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
Dunning: Summary
(C) SAP AG IUT110 85
13.86
SAP AG 1999
Overview
Documents
Account display
Payments
Returns
Dunning
Deferral and installment plan
Contract Accounts Receivable and Payable: Deferral and Installment Plan
(C) SAP AG IUT110 86
13.87
SAP AG 1999
At the conclusion of this topic, you will be able to:
Defer items in contract accounts receivable and payable.
Create an installment plan.
Deferral and Installment Plan: Objectives
(C) SAP AG IUT110 87
13.88
SAP AG 1999
SAP Utilities
Some customers are not able to keep up with
payments to the utility company
In this situation, installment plans or deferrals can be
arranged for one or more receivables in order to:
Accommodate the customer
Guarantee payment
Deferral and Installment Plan: Introduction
(C) SAP AG IUT110 88
13.89
SAP AG 1999
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
Deferral and Installment Plan: Business Scenario
(C) SAP AG IUT110 89
13.90
SAP AG 1999
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.
Deferral
(C) SAP AG IUT110 90
13.91
SAP AG 1999
Any number of open items as the basis of an installmentagreement
Interest calculation for installment plans
Installment plan charges
Letter to the customer
Change, add and delete individual installments
Deactivation of installment plans
Installment Plan: Characteristics
(C) SAP AG IUT110 91
13.92
SAP AG 1999
Installment plancategory
Number of installments
Installment interval
Interval categoryRounding amount
Pre-definable installment plan categories simplify creation ofnew installment plans.
Installment Plan Category
(C) SAP AG IUT110 92
13.93
SAP AG 1999
Simplified selection
All open items
Selection of open items
forinstallment
plan
Manual compilation from the list of open items
Installment Plan: Item Selection
(C) SAP AG IUT110 93
13.94
SAP AG 1999
In Contract Accounts Receivable and Payable, open items can be easily deferred by making a document change.
Simple procedure for creating and managing installment plans.
Installment plan categories make it easier to create installment plans on the basis of an enterprise model.
Either all open items, or any selection of open items, can be included.
Installment plan items are statistical document items that are saved in repetition groups.
Deferral and Installment Plan: Unit Summary
(C) SAP AG IUT110 94
13.95Contract Accounts Receivable and Payable Exercises
Unit: Contract Accounts Receivable and Payable
Topic: Manual document entry
At the conclusion of these exercises, 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.
Your colleague has just completed an energy consultation. You now have to post the corresponding receivable to the customer’s account.
1-1 Posting receivables
1-1-1 Specify the menu path that you would use to post a document.
_____________________________________________________
1-1-2 Using parameters (optional)
Display the help information for the Company code field.
From this help screen, take a look also at the technical information for the Company code field.
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.
Enter the following parameters in your user settings.
(C) SAP AG IUT110 95
Parameters Value Meaning
FWS UNI is automatically entered in the Currency field.
BUK U300 U300 is automatically entered in the Company code field.
Your user profile is located under System User profile Own data. Choose the Parameters tab.
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.
1-1-4 Now post a receivable for today’s 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. For your business partner, enter a miscellaneous posting for the energy consultation. In doing so, try to make as few entries as possible, to see which data the system determines automatically.
Data field Contents
BusPartner TB130110##
Misc. postings Use F4 for help
SubT Miscellaneous posting - debit Use F4 for help
Amount
Do not save your entries
(C) SAP AG IUT110 96
1-1-6 Clarify your receivable using the following text: “Energy consultation of <today’s date>”.
To add the text you must switch to another screen variant, SAP02, (using the Screen variant icon or the menu path Settings Screen variant). For further options, see solutions.
1-1-7 Post the document and note the document number.
_____________________________________________________
1-1-8 Display the document.
1-1-9 Display the document item.
1-1-10 What information does the general ledger provide?
Data field Value Origin
Company code
G/L Account
Act. determ. ID
1-1-11 Name three specifications from the document or the document item that control the determination of account assignment in financial accounting.
1. __________________________________________________
2. __________________________________________________
3. __________________________________________________
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.
_____________________________________________________
1-2-2 Posting documents is the usual method for creating receivables in Contract Accounts Receivable and Payable.
_____________________________________________________
1-2-3 A document contains all the information for posting in financial accounting.
_____________________________________________________
1-2-4 The document date and posting date always correspond to the entry date.
(C) SAP AG IUT110 97
_____________________________________________________
1-2-5 The reconciliation key can differ for each document item.
_____________________________________________________
(C) SAP AG IUT110 98
Exercises
Unit: Contract Accounts Receivable and Payable
Topic: Display account balance
At the conclusion of these exercises, you will be able to:
Handle the many options of the account display, i.e. you will be able to display the exact item you want to display and in the way in which you want to view it.
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. Before you initiate the contact, you would like to obtain a detailed picture of the recent transactions for each account.
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.
_____________________________________________________
2-1-2 The line item display can be modified to display items other than those pre-configured in the standard settings.
_____________________________________________________
2-1-3 The list category determines the line layout of the item display, i.e. how the lines are constructed.
_____________________________________________________
2-1-4 To display the items in a customer account in another line layout, you must return to the initial screen.
_____________________________________________________
(C) SAP AG IUT110 99
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-3 Navigating the document display (optional)
2-3-1 Identify the receivable for the energy consultation for business partner TB130110##.
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-4-5 Have any taxes been calculated for the energy consultation?
_____________________________________________________
(C) SAP AG IUT110 101
Exercises
Unit: Contract Accounts Receivable and Payable
Topic: Payment run
At the conclusion of these exercises, 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.
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, you can resume work on it at any time, provided that you do not close the payment lot.
_____________________________________________________
3-2-2 Once the payment lot is closed, no more changes can be made to it.
_____________________________________________________
3-2-3 The procedures for payment lots and check lots are identical.
_____________________________________________________
(C) SAP AG IUT110 102
3-3 Posting a payment lot
3-3-1 Create a payment lot (PL-yymmdd-##).
3-3-2 Enter the search term (IUT110-##) and a bank clearing account.
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-5 Post the payments.
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.
Use the Payment list hotspot.
(C) SAP AG IUT110 103
3-4 Payment at cash desk
3-4-1 Display the open receivables for 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.
3-4-4 Post a payment for the amount of the open balance of business partner TB130110##. To do this, make the following entries:
Recon. key RB-yymmtdd-##
Business partner TB130110##
Amount Balance for TB130110##
(C) SAP AG IUT110 104
Exercises
Unit: Contract Accounts Receivable and Payable
Topic: Returns
At the conclusion of these exercises, you will be able to:
Post a return
Define the effects of returns on payments already made
In accounts receivable accounting, some returns have just arrived in the mail from the bank, which you now have to post.
4-1 Returns lot
4-1-1 Create a returns lot (RL-yymmdd-##).
4-1-2 Enter the search term (IUT110-##). Ensure that a “B” for “document” is entered in the selection type field. The fields Amounts contain bank charges and Calculate charges should be activated. Switch to enter items.
4-1-3 Enter a return for business partner TB130120##.
If necessary, create a second session to determine the required payment document number.
_____________________________________________________
4-1-4 Save the data and close the returns lot.
4-1-5 Post the returns lot.
4-1-6 Check the status.
4-1-7 Switch to the account display and observe the changes.
4-2 Returns lot with charges (optional)
4-2-1 Repeat the steps of the previous task for a new returns lot (RN-yymmdd-##). Increase the return amount by 10 UNI.
This time, generate a return for the payment entered for business partner TB130210## in exercise 3-3-3.
(C) SAP AG IUT110 105
Exercises
Unit: Contract Accounts Receivable and Payable
Topic: Dunning
At the conclusion of these exercises, you will be able to:
Display and explain the dunning history for a business partner/contract account.
Differentiate between various influential factors for dunning and describe the resultant activities.
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.
_____________________________________________________
5-2 Dunning history
5-2-1 Display the dunning history for business partner TB130220##.
_____________________________________________________
(C) SAP AG IUT110 106
Exercises
Unit: Contract Accounts Receivable and Payable
Topic: Deferral and installment plan
At the conclusion of these exercises, 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. The business partner telephones again and would like to pay for the open items in installments.
For this reason, you have to first defer the receivable and then create the installment plan.
6-1 Deferral
6-1-1 Defer the open receivable of business partner TB130130## until the last day of the month. Use functions from the Customer Interaction Center (CIC).
6-1-2 Display the changes in the corresponding document resulting from the deferral.
Display the customer account from the navigation area of the contract account.
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-2-2 Check that the instalment plan has been created in the account display.
When you display the customer account from Front Office, remember that the previous settings for the list type are still active. However, to display the installment plan, the statistical items must also be displayed.
(C) SAP AG IUT110 107
13.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.
Utilities industry Contract Accounts Receivable and Payable Document Post
1-1-2 Using parameters (optional)
Display the help information for the Company code field.
From this help screen, take a look also at the technical information for the Company code field.
What is the parameter for the Company code field?
1. Utilities industry Contract Accounts Receivable and Payable Document Post
2. Place the cursor in the Company code field and choose Help. To do this, press F1 or the button with the yellow question mark.
3. Choose Technical info.
4. In the Parameter ID field, you will see the value BUK.
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.
Enter the following parameters in your user settings.
1. System User profile Own data.
2. Choose the Parameters tab page.
3. Enter the values from the table.
4. Save your entries by choosing Save or F11.
5. If you are already in the screen Post Document: Initial Screen, you must update its contents so that the user settings can be entered automatically.Leave the screen using Cancel or F12, confirm this using Yes and start the transaction again immediately using Document Post. Your settings have now been added to the Currency and Company code fields.
(C) SAP AG IUT110 108
Parameters Value Meaning
FWS UNI UNI is automatically entered in the Currency field.
BUK U300 U300 is automatically entered in the Company code field.
1-1-4 Now post a receivable for today’s energy consultation.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. For your business partner, enter a miscellaneous posting for the energy consultation. In doing so, try to make as few entries as possible, to see which data the system determines automatically.
1. In the Post Document: Initial Screen, press Enter or the green checkmark or the button BP item (Business partner item list).
2. Enter the following values:
Data field Contents Note
BusPartner TB130110##
Main Misc. postings Use F4 for help
SubT Miscellaneous posting - debit Use F4 for help
Amount 116
3. Do not save your entries
1-1-6 Clarify your receivable using the following text: “Energy consultation of <today’s date>”.
To enter text
- 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.
- Or change to the detail display for your business partner (for example. by double-clicking on the current item in the list) and enter the text under Other data.
(C) SAP AG IUT110 109
If you have already saved the document,
1. Change to Document Change via the menu.
The document number is pre-filled.
2. Choose BP item (Business partner item list).
3. Choose the screen variant SAP02
4. Enter the text in the text field.
1-1-7 Post the document and note the document number.
1. To post the document, you must choose Post (CTRL S).
2. The document number is displayed in the message line after posting.
1-1-8 Display the document.
Utilities Industry Contract Accounts Receivable and Payable Document Display
1-1-9 Display the document item.
From the Display Document: Initial Screen, choose BP item (Business partner item list) to display the document items. Another possible solution:
In the screen Display Document: Initial Screen, choose Enter or the green checkmark. Then double-click on the summary of business partner items, or select the item with the cursor and use Edit Choose (F2) from the menu to display the business partner item.
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. determ. 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.
1. Company code in the document item
2. Main transaction in the document item
3. Sub-transaction in the document item
Other criteria for determination are the account determination ID and the division.
1-2 True or false?
1-2-1 A document is always assigned to just one contract account.
False. A document can have more than one document item, each of which can be assigned to another contract account or business partner.
(C) SAP AG IUT110 110
1-2-2 Posting documents is the usual method for creating receivables in Contract Accounts Receivable and Payable.
False. The usual method of creating receivables is by invoicing.
1-2-3 A document contains all the information for posting in financial accounting.
True. 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.
1-2-4 The document date and posting date always correspond to the entry date.
False. These three dates may be different.
1-2-5 The reconciliation key can differ for each document item.
False. For each document there is only one reconciliation key.
(C) SAP AG IUT110 111
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.
False – the standard display shows all open non-statistical items.
2-1-2 The line item display can be modified to display items other than those pre-configured in the standard settings.
True. You define your own line item display by choosing Settings Display/ Change (F6).
2-1-3 The list category determines the line layout of the item display, i.e. how the lines are constructed.
False. The list category determines which items are displayed in the lines.
2-1-4 To display the items in a customer account in another line layout, you must return to the initial screen.
False. You can change the line layout in the item display using the Line layout (Shift + F4) pushbutton or via Settings Line layout.
If a totals variant is active, you can double-click an item to display a more detailed line layout variant. Alternatively, you can use the blue arrows (provided you have activated them in your personal settings for account balance display).
(C) SAP AG IUT110 112
2-2 Line item display for a business partner
2-2-1 What is the current balance for business partner TB130110##?
1. Utilities Industry Contract Accounts Receivable and Payable Account Account Balance
2. Enter business partner TB130110## in the Business partn. field. The List category field is in standard mode and is empty and Standard line layout – acc display is displayed in the Line layout field.
3. Press the green checkmark (ENTER).
4. Choose the Totals hotspot.
5. The balance appears in the Total field.
2-2-2 Which items comprise the balance?
Double-click on the Receivables line- or on the total line- to return to the display of the receivables that are still open. Alternatively, directly choose the Receivables hotspot.
2-2-3 Have any payments already been made?
1. Use Back (F3) to return to the screen Account Display: Initial Screen.
2. Choose either a List category which displays more than only the open items (using F4 help, for example List category All items) or press the Detail button in the List type subscreen. Select the Cleared items field and choose ENTER (green checkmark).
3. Return to the account display. Now all payments made are displayed.
(C) SAP AG IUT110 113
2-3 Navigating the document display (optional)
2-3-1 Identify the receivable for the energy consultation for business partner TB130110##.
Tip: Choose the correct line layout variant.
1. Utilities Industry Contract Accounts Receivable and Payable Account Account Balance
2. Enter business partner TB130110## in the Business partn. field.
3. Press the green checkmark (ENTER).
4. Press the button Line layout (Shift+F4).
5. Choose the line layout variant TBT – Account display with document text by double-clicking on it.
6. 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).
2-3-2 Who posted the receivable?
1. Double-click on the receivable.You are now in the screen Display Document: Item.
2. Choose Document header CTRL+F4.
3. You can read the user key of the creator from the Created by field.
2-3-3 Which reconciliation key was used?
Contained in the Recon. key field in the document header.
2-3-4 Have any items been posted to the above document number for any other business partner?
1. Press the button Overview F7 or use Goto Overview F7 from the menu.
2. 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).
3. The number is one. Therefore, this document only contains items for one business partner.
2-3-5 Have any taxes been calculated for the energy consultation?
1. Choose the Taxes (CTRL+F6).
2. Here you can view the details for the tax item.
(C) SAP AG IUT110 114
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. Create
2. Close
3. Post
3-2 True or false?
3-2-1 If you are interrupted while working on a payment lot, you can resume work on it at any time, provided that you do not close the payment lot.
True. The Change step exists for this purpose.
3-2-2 Once the payment lot is closed, no more changes can be made to it.
False. While it is true that no new items can be added and items cannot be deleted, existing items can be corrected.
3-2-3 The procedures for payment lots and check lots are identical.
True. The only difference is that a different screen variant must be chosen for the line layout, as a check number must be entered for a check, but this does not happen in the screen variant for the payment lot.
3-3 Posting a payment lot
3-3-1 Create a payment lot (PL-yymmdd-##).
1. Utilities industry Contract accounts receivable and payable Payments Payment lot.
2. Enter PL-yymmdd-## in the Lot field.
3. Choose Create (F5).
3-3-2 Enter the search term (IUT110-##) and a bank clearing account.
1. Search term: IUT110-##.
2. Bank clearing account: selection via the possible entries for Bank clrg acct (F4 help). Choose an account enter today’s date as the value date. Enter UNI in the Currency field.
3-3-3 Enter payments for three of your business partners:
(C) SAP AG IUT110 115
1. To enter the item, press the New items F5 pushbutton.
2. Ensure that the screen variant SAP01 with the description Standard (one line) is activated.
Amount Business partner
500 TB130210##
800 TB130220##
1200 TB130230##
3-3-4 Save your entries and close the payment lot.
1. Choose Save (CTRL+S).
2. Choose Back (F3). You now see the Payment lot Create: Default Entries and Status screen .
3. Choose Back (F3) again. You have returned to the Payment lot: Initial Screen. Observe the change in status during the following activities.
4. Choose Close and confirm the action.
3-3-5 Post the payments.
1. To do this, choose Post.
2. Choose Start Online.
3. Press the green checkmark (Continue Enter).
3-3-6 Check the status.
The status should read “Postings made”.
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.
Use the skills you learned in the FI-CA2 unit “Display Account Balance”. Tip: Use the Payment list hotspot.
3-4 Payment at cash desk
3-4-1 Display the open receivables for business partner TB130110##. What is the open balance?
1. Utilities Industry Contract Accounts Receivable and Payable Account Account Balance
2. Enter business partner TB130110## in the Business partn. field.
3. Press the green checkmark (ENTER).
4. Choose the Totals hotspot. The balance of open items is located in the Total field.
3-4-2 Which items make up the total?
(C) SAP AG IUT110 116
1. Double-click on the Receivables field in the total display.
2. Ensure that you have chose the line layout variant TBT (Account display with document text) to display the document text column.
Amount Item type
20.00 UNI Miscellaneous posting:
Hire of energy measuring device
116.00 UNI Miscellaneous posting:
Energy consultation of <dd/mm/yy>
(from the “Post document” exercise).
3-4-3 Switch to payment at cash desk.
Utilities Industry Contract Accounts Receivable and Payable Payments Cash Account Payment at Cash Desk.
(C) SAP AG IUT110 117
3-4-4 Post a payment for the amount of the open balance of business partner TB130110##. To do this, make the following entries:
Recon. key RB-yymmdd-## (Under Further posting specs)
Business partner TB130110##
Amount Balance for TB130110##
1. Ensure that the field Incoming cash paymt is selected.
2. To post the payment, choose Post item or Post item online. If you have chosen Post item online, use the save button to post the item (ctrl + S).
3. Choose Print receipt.
4. Select any output device (F4 help) and choose Enter.
(C) SAP AG IUT110 118
Solutions
Unit: Contract Accounts Receivable and Payable
Topic: Returns
4-1 Returns lot
4-1-1 Create a returns lot (RL-yymmdd-##).
1. Utilities Industry Contract Accounts Receivable and Payable Payments Returns Lot.
2. Enter RL-yymmdd-## in the Returns lot field.
3. Press the button Create (F5).
4-1-2 Enter the search term (IUT110-##). Ensure that a “B” for “document” is entered in the selection type field. The fields Amounts contain bank charges and Calculate charges should be activated. Switch to enter items.
1. Search term: IUT110-##.
2. Choose the above settings and save them using Save (CTRL+S), if these were not already chosen.
3. Choose New items.
4-1-3 Enter a return for business partner TB130120##.
If necessary, create a second session to determine the required payment document number.
1. System Create session
2. Utilities Industry Contract Accounts Receivable and Payable Account Account Balance
3. Enter business partner TB130120## in the Business partn. field.
4. Choose the standard list category All items and line layout Account display with text (IUT110).
5. Choose the green checkmark (ENTER).
6. Note the payment document number.
7. Close the second session: System End session.
8. In the screen Returns: Enter/Maintain Lot RL-yymmdd-##, enter the payment document number in the SelectionValue field. The selection type should be set to B. Choose return reason 01 (Bank account overdraft).
(C) SAP AG IUT110 119
9. Choose Enter. The amount and the return reason is determined automatically.
4-1-4 Save the data and close the returns lot.
1. Choose Save (CTRL+S).
2. Choose Back (F3). You now see the Returns: Specifications and Status: Edit screen.
3. Choose Back (F3). You are now looking at the Returns: Request Screen.
4. Choose Close and confirm the action.
4-1-5 Post the returns lot.
1. To do this, choose Post.
2. Select Start online and Immediately.
3. Choose OK.
4-1-6 Check the status.
The status should read “Postings made”.
4-1-7 Switch to the account display and observe the changes.
Use the Payment list hotspot.
4-2 Returns lot with charges (optional)
4-2-1 Repeat the steps of the previous task for a new returns lot (RN-yymmdd-##). Increase the return amount by 10 UNI.
This time, generate a return for the payment entered for business partner TB130210## in exercise 3-3-3.
Solution as for 4-1. In the account display, you will notice that the bank charges contained in the return amount were posted together as one item with the utility company’s charges.
(C) SAP AG IUT110 120
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 .
False. The dunning procedure can be defined in the contract account and can be applied even to individual items.
5-1-2 The days in arrears and the dunning frequency largely determine when a due open item can be dunned.
True. The days in arrears determine the minimum number of days that must have passed since the due date before dunning can occur. 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.
5-2 Dunning history
5-2-1 Display the dunning history for business partner TB130220##.
1. Utilities Industry Contract Accounts Receivable and Payable Account Other Information Dunning History.
2. Enter TB130220## in the Business partner field.
3. Press Execute F8.
4. The dunning history is displayed.
(C) SAP AG IUT110 121
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.
1. Utilities Industry Customer Service Front Office/Customer Interaction Customer Interaction Center.
2. Enter TB130130## in the field Business Partner (in the search criteria of the data finder). Choose Enter to display the business partner’s data. Then choose Confirm partner.
3. The business partner environment is displayed in the navigation area. Select the contract account. Then click the right mouse button and choose Post deferral.
4. In the Deferral field, enter the last date of the month.
5. Choose ENTER.
6. Enter text relating to the customer contact.
7. Save the contact (Save or CTRL + S).
6-1-2 Display the changes in the corresponding document resulting from the deferral.
Display the customer account from the navigation area of the contract account.
1. Select the contract account. Then click the right mouse button and choose the customer account. Double-clicking on the open receivables brings you to the detail display of the document.
2. The deferral date you have just entered is now visible in the Deferral to field of the Basic data subscreen.
3. Return to the CIC by choosing Back (F3) twice.
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##.
(C) SAP AG IUT110 122
1. Utilities Industry Customer Service Front Office/Customer Interaction Center Customer Interaction Center
2. Enter TB130130## in the field Business partner (in the search criteria). Choose Enter to display the business partner’s data. Then choose Confirm partner.
3. The business partner environment is displayed in the navigation area. Select the contract account. Then click the right mouse button and choose Create Installment plan.
4. Choose all open items by pressing the Select all (Shift+F7)button.
5. Enter today’s date in the Start date field.
6. Enter 10 in the Rounding amount field.
7. Enter 5 in the No. of instmts field.
8. Enter 2 in the Instlm. interval field.
9. Enter 2 in the Interval cat. field.
10. Choose Installment plan or ENTER.
11. Check the number of installments and the intervals between them.
12. Choose Save (CTRL+S).
13. Enter a text relating to the customer contact.
14. Save the contact by pressing Save (Ctrl+S).
6-2-2 Check that the instalment plan has been created in the account display.
When you display the customer account from the CIC, remember that the previous settings for the list type are still active. However, to display the installment plan, the statistical items must also be displayed.
Select the contract account. Then click the right mouse button and choose the customer account. If no items are selected, the statistical items display is not activated under list type. You can choose another list type on the initial screen for account balance display.
(C) SAP AG IUT110 123
14
SAP AG 1999
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
Contents:
Waste Industry
The Waste Management component allows you to map and settle periodic and aperiodic waste disposal services for residential and non-residential customers. Logistics and billing-related business processes are supported here.
The container forms the basis for the settlement. This is usually emptied periodically by a waste disposal company. Settlement takes into account container and premise data.
(C) SAP AG IUT110 1
14.2
SAP AG 1999
At the conclusion of this unit, you will be able to:
Describe terms and contexts that relate to waste in the mySAP Waste Industry.
Waste Industry: Unit Objectives
(C) SAP AG IUT110 2
14.3
SAP AG 1999
Solution Map and Integration Model for the Waste Industry
Enterprise Management Strategic Enterprise Management
Strategic Enterprise Management
Business Intelligence &
Data Warehousing
Business Intelligence &
Data Warehousing ControllingControlling Financial
Accounting
FinancialAccounting
RegulatoryReporting
RegulatoryReporting
Revenue ManagementInvoicingInvoicing Accounts Receivable
& Payable
Accounts Receivable& Payable
Billing External Services
Billing External Services
Customer Relationship Management Customer
Service
Customer Service
Market Research & Analysis
Market Research & Analysis
ProductMarketing
ProductMarketing
Marketing Management
Marketing Management
Sales Management
Sales Management
SalesChannels
SalesChannels
Business Support Human ResourceManagement
Human ResourceManagement ProcurementProcurement TreasuryTreasury Fixed Asset
Management
Fixed Asset Management
Real EstateManagement
Real EstateManagement
Installation Management Technology &
Installation Construction
Technology &Installation Construction
Plant Maintenance &Service Management
Plant Maintenance &Service Management DecommissioningDecommissioning
Billing Billing GuarantorBilling
GuarantorBilling
Industrial HygieneAnd Safety
Industrial HygieneAnd Safety
Waste Disposal Services ContainerService
ContainerService
BulkWaste
BulkWaste
ResidentialWaste
ResidentialWaste
Management of Waste Master Data Waste-Specific
Master Data
Waste-SpecificMaster Data
Inventory &Warehouse Management
Inventory &Warehouse Management
RBS Sites &Geo Server
RBS Sites &Geo Server
Cleaning Service & Winter Maintenance
Cleaning Service & Winter Maintenance
Maintenance &Plant Maintenance
Maintenance &Plant Maintenance
Waste-Specific CrossApplications Weight Data System
& Daily BusinessStatistics
Weight Data System& Daily Business
StatisticsConfirmationConfirmation
Disposal Regulations& Dangerous Goods
Management
Disposal Regulations& Dangerous Goods
Management
Vehicle & ResourcePlanning
Vehicle & ResourcePlanning RoutingRouting
SpecialServices
SpecialServices
(C) SAP AG IUT110 3
14.4
SAP AG 1999
Integration Model for mySAP Waste Industry
ISWaste
ISWaste
CO-PA
CO-PA
HR
Route Planning
Container
Regional structure
Front Office
SAPBusinessPartner
Contract/Billing
Contract/Billing
InvoicingContract
AccountsReceivable
& Payable
FICAFIFICACA
SDCSSDCS
MM/PM
MM/PM
Profitability analysis
GIS
BCBC
Weighting data
Driver
CSP
Vehicle
The integration model shows which connections to other SAP modules (such as SD/SM, 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.
The Billing Engine (IS-U billing master data) is used for regular services and SD billing functions are used for unusual services.
(C) SAP AG IUT110 4
14.5
SAP AG 1999
EH&S WA - Waste ManagementEH&S WA - Waste Management
Industry Solution - WasteIndustry Solution - Waste
mySAP Waste Industry : Involved Areas
EH&S Environment, Health & SafetyThe EH&S component covers the areas environment, health, and safety.The Waste Management component of EH&S is planned for Release 2.7 of EH&S.
(C) SAP AG IUT110 5
14.6
SAP AG 1999
Focus Areas of IS-Waste - Waste Industry
SAP IS-W/LOG
Management of specific master data for waste disposal and cleaning services/winter maintenance.
Preconfigured business processes: Create and display orders, enter completion confirmations, management of bulk waste and so on.
Generic interfaces to the route planning system, geographical information systems, and weighing data systems.
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.
Invoicing and accounting
(C) SAP AG IUT110 6
14.7
SAP AG 1999
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
Focus Areas of EH&S WA - Waste Management
Waste disposal is performed in accordance with international statutory regulations: Germany: Waste Avoidance, Recycling and Disposal Act. USA: United States Code, Code of Federal Regulations (40CFR)
(C) SAP AG IUT110 7
14.8
SAP AG 1999
The Waste Disposal Cycle with EH&S
R/3 mail purchase requisition EH&S waste generation
Outline contractPurchase order/ scheduling(returns)deliveryAssigned WE
Print delivery notePrint disposal document
Standard sourcedetermination EH&S waste generation
Inquiry/offerinfo record waste approval
CO transfer
Enter disposal document
Regist-ration
Determine WD channels
Choose disposer/transporter
Disposal processingProcess monitoring
Delivery/disposal
Check bill
Settlement,assessment
Waste disposal
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.
Master data that has been recorded in the vendor master record is used to perform legal checks on the waste disposal company. such as checking the licence for disposal of hazardous waste
(C) SAP AG IUT110 8
14.9
SAP AG 1999
Data Model – Container Service (Simplified)
Contractaccount
Contract
Regionalstructure
Waste disposalobject
Func. loc.
Premise
Container
Equipment
Containercategory
Material
Servicefrequency
ContainerlocationFunc. loc.
Route
IS-Waste
SD /CS
FI-CAPM/MM CA
Businesspartner
Customer
Objectallocation
(C) SAP AG IUT110 9
14.10
SAP AG 1999
Technical Master Data I
Waste disposal object
A waste disposal object is usually a building, but can also be apiece of property or other facility, for which a utility service is 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,such as an apartment or factory for which a waste disposal service is to be provided. 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.It is managed as a functional location in the Plant Maintenance (PM) component.
(C) SAP AG IUT110 10
14.11
SAP AG 1999
Technical Master Data II
Object allocationThe billing conditions for a container or cleaning object are maintained in the object allocation. The container or cleaning object is also allocated to a contract and a premise in the object allocation.
Container categoryThe container category groups together containers with the same characteristics (data).It is managed as a material with a material number in the Materials Management (MM) component.
ContainerThe container is an item which has to be emptied.It is managed as a piece of equipment with a serial number in the Plant Maintenance (PM) component.
(C) SAP AG IUT110 11
14.12
SAP AG 1999
Technical Master Data III
Service frequencyFrequency with which a service is performed for a container or cleaning object. 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.
RouteA route defines a regional combination for several containers orcleaning objects for which a service is to be performed.
Container portionsA container can be assigned to several customers or premises using container portions. The customer is billed for their portion of the container using various criteria, such as number of persons/ m² per premise (household).
(C) SAP AG IUT110 12
14.13
SAP AG 1999
Container Management: Integration
ContainerContainer
Container Container categorycategory
Container managementContainer management
EquipmentEquipment
MaterialMaterial
LogisticsLogistics
Technical data
Allocation
Container service
Container size, container volume,loading information, dimensions
Container category for vehicle type, container for
route, containers for customers
Organization, order, completion confirmations
Inventory management
PurchasingPurchase order, goods receipt
Warehouse Management
Classification system
Maintenance/ Check
Planning, maintenance, cleaning
(C) SAP AG IUT110 13
14.14
SAP AG 1999
Possible route
Determination of possible routes
(sorted/unsorted)
Sorting anexisting route
All routesfully optimized
Determination of possible routes
(sorted/unsorted)
Sorting anexisting route
All routesfully optimized
Creation and maintenance of
a periodic oraperiodic service
Allocation of a route according toservice frequency
Optimized route
Driver data
Vehicle data
Container data
Service data
IS-W/CCS - SD/CS Route planning system
Allocation data
Interface to Route Planning System
Initial situation: The geographical coordinates (x/y coordinates, time zone) of any object in the SAP system are determined, validated and recorded in the SAP system using a geographical coordination tool.Both internal and external applications can then access this data. Examples of this include route planning, resource planning, facility management.
A generic interface is used to transfer all data that has been maintained in the SAP System (such as driver, vehicle, container, container address, service dates, various allocations) to an external route planning system. Planning or optimization of the route occurs in this system. A BAPI is then used to load the route determined by the route planning system with a specific service date into the SAP System. A sequence number within a route can also be loaded into the system. This planning can also be performed manually.
(C) SAP AG IUT110 14
14.15
SAP AG 1999
Waste Disposal Orders
Display/ Change
Delete
Output
Output
Create wastedisposal
order
Route
Service frequency
In paperform
In file form
Conf-irmation
Createinvoice
You can display and change the waste disposal orders that have been created. Waste disposal orders are generated on the basis of the dates in the service frequency. A waste disposal
order is subdivided into one header record at route level and 1 to n object records at container level. You can delete waste disposal orders following creation. You can use a selection parameter to control whether orders that have been confirmed are to be deleted.
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. You can also delete the service for a particular container/customer within the route.
Once the waste disposal service has been performed, 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.
(C) SAP AG IUT110 15
14.16
SAP AG 1999
Process: Container Delivery / Removal
The CIC is used to notify the customer by telephone of containerdelivery/removal.
An order for delivery/removal of one or more containers is created.
A service order (PM-CS) is generated automatically in the background.
Once the container delivery/removal has been performed, the number (and serial number if required) of the containers that have beendelivered or removed and the time required to do so is confirmed.
The customer is billed and invoiced on the basis of this confirmation.
(C) SAP AG IUT110 16
14.17
SAP AG 1999
Fleet ManagementFleet 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, such as the maintenance cycle, average consumption and load weight
(C) SAP AG IUT110 17
14.18
SAP AG 1999
Implemented Functions I
Container management
Serialization
Container portions
Business to customer scenario
Waste disposal-specific role
Route
Difficulties
Premise
(C) SAP AG IUT110 18
14.19
SAP AG 1999
Implemented Functions II
Service types
Container delivery
Unique services
Cleaning services and winter maintenance
Bulk waste
Vehicle and resource planning
Container services
(C) SAP AG IUT110 19
14.20
SAP AG 1999
Service-related billing
Customer-specific prices
Integration of EH&S
Integration of IS-Waste with SAP CRM and SAP BW
Planned Functions for mySAP Utilities 4.64
(C) SAP AG IUT110 20
14.21
SAP AG 1999
You are now able to:
Describe the special terms and contexts and individual functions of waste management in IS-U/CCS.
Waste Industry: Summary
(C) SAP AG IUT110 21