IUT110 Introduction to the SAP Utilities System
IUT110
Introduction to the SAP Utilities System
THE BEST-RUN BUSINESSES RUN SAP SAP AG 2009 ¤ SAP AG©2009
ERP2005 SAP for Utilities ECC 6.0
Version 94
Material number: 50099965
Copyright
Copyright 2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
¤ SAP AG 2009
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Prerequisites
z Basic knowledge of the SAP system (SAP01 SAP Overview) z Knowledge and experience of the business processes in a utility company z Knowledge and experience of the Windows operating system environment
¤ SAP AG 2009
Target Group
z Participants
Decision makers who use SAP Utilities to support their business processes
Project managers responsible for implementing SAP Utilities
A project team implementing business processes with SAP Utilities
Administrators who optimize processes in the SAP Utilities environment
Consultants preparing to implement SAP Utilities
z Duration
¤ SAP AG 2009
5 days
Course Objectives
This course will teach you: z The concept of integrating SAP Utilities in SAP ERP z About the business processes in the utilities industry z How to use SAP Utilities in SAP ERP and implement it efficiently
¤ SAP AG 2009
Objectives
After completing this course, you will be able to: z Describe how SAP Utilities is integrated in the SAP ERP environment z Perform the core business processes z Explain the structure and function of processes
¤ SAP AG 2008
Table of Contents
Preface Unit 1
Overview
Unit 8
Billing Master Data
Unit 2
IC and Master Data
Unit 9
Billing and Invoicing
Unit 3
Move-In/Out
Unit 10
Energy Data Management
Unit 4
Work Management
Unit 11
Real-Time Pricing
Unit 5
Device Technology
Unit 12
Budget Billing Plan
Unit 6
Device Installation
Unit 13
Contract Accounting
Unit 7
Meter Reading
¤ SAP AG 2009
IC: Customer Interaction Center
Overview
Contents: z Interaction between SAP Utilities and SAP CRM z Interaction between SAP Utilities and the classic SAP ERP components z Incorporation of SAP Utilities into the core business processes of a utility company in regulated and deregulated markets z Business process overview of SAP Utilities
¤ SAP AG 2009
(©) SAP AG
IUT110
1-1
Overview: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe the integration of SAP Utilities in SAP ERP 6.0 z Name the most important SAP ERP components and their roles in the utilities industry z Describe the functions of SAP Utilities
¤ SAP AG 2009
(©) SAP AG
IUT110
1-2
Overview: Business Scenario
z The course participants are new employees of ENRG AG z You are taking part in a 5-day training program z Your main tasks are customer-oriented processes in the customer center and customer care for corporate customers z Using standard business processes, you will learn about the structure of SAP Utilities and how it operates
¤ SAP AG 2009
(©) SAP AG
IUT110
1-3
Organizational Requirements
SAP ERP Overview
SAP R/2
SAP R/3
SAP ERP Service-Oriented Architecture
Use
Ï
Integrated Processes
Replace
X
Strategic Value
Client/Server Architecture
Efficiency and Control
Centralized Computing
Automation Technological Progress ¤ SAP AG 2009
Enterprise service-oriented architecture (enterprise SOA) drives business innovation by using the existing IT structure, maximizing agility, and reducing the total cost of ownership (TCO).
SAP NetWeaver is the application and integration platform that uses Web service technology to provide the optimum support for enterprise SOA.
There have been a number of milestones in information technology: The transition from mainframe to client/server architecture, and now from client/server technology to service-oriented architecture.
In 1992, SAP brought the product SAP R/3 (the successor to SAP R/1 and SAP R/2) on to the market, and with it, a two-level architecture (technology and application).
With the introduction of SAP ERP in March 2003, SAP provided a solution portfolio to support ERP business processes.
In the past, such changes called for complete replacement of the IT infrastructure. However, this does not apply to the switch from SAP R/3 to SAP ERP.
SAP protects and uses the investments made in SAP R/3 and offers its customers an evolutionary transition to a Web service-based architecture.
(©) SAP AG
IUT110
1-4
Application
SAP ERP Architecture
Additional components Self-Service Procurement Internet Sales
SAP R/3
SAP R/3 Enterprise
Additional components
Self Services
Self Services
Strategic Enterprise Management
Self-Service Procurement
... and more
Internet Sales
Composite Applications
Strategic Enterprise Management ... and more
up to 4.6C
SAP R/3 Enterprise 2.0 IS-U 4.72 SAP NetWeaver™
SAP NetWeaver™ 7.0 Composite Application Framework
SAP Web Application Server
PEOPLE INTEGRATION Multi Channel Access Collaboration
Master Data Management PROCESS INTEGRATION Integration Business Broker Process Management APPLICATION PLATFORM J2EE ABAP DB and OS Abstraction
PEOPLE INTEGRATION Multi Channel Access Portal
Collaboration
INFORMATION INTEGRATION Business Intelligence Knowledge Manag. Master Data Management PROCESS INTEGRATION Integration Business Broker Process Management APPLICATION PLATFORM J2EE ABAP
Life Cycle Management
Portal
INFORMATION INTEGRATION Business Intelligence Knowledge Manag.
Life Cycle Management
Technology
SAP Basis
SAP ERP 6.0
Composite Application Framework
SAP R/3 < IS-U 4.64 Enterprise 1.0 IS-U 4.71
DB and OS Abstraction
¤ SAP AG 2009
SAP ERP is the next step in this development. The figure shows the elements that are contained in SAP ERP.
In SAP NetWeaver you can see the elements that are technically integrated into SAP ERP (for example, Business Intelligence).
(©) SAP AG
IUT110
1-5
SAP ERP and SAP NetWeaver SAP ERP is the successor to SAP R/3. z SAP ERP contains the full scope of functions of SAP R/3 Enterprise.
SAP ERP Analytics Financials Human Capital Management Operations Corporate Services
A large number of additional business processes Integrated and personalized functions
z SAP ERP is based on SAP NetWeaver.
SAP NetWeaver™
… Financial Supply Chain Management, Self Service Procurement … …Self Services, Adobe Print Forms …
Portal
INFORMATION INTEGRATION Business Intelligence Knowledge Manag.
Master Data Management PROCESS INTEGRATION Integration Broker
…
Collaboration
Business Process Management
Life Cycle Management
… Strategic Enterprise Management, Manager Self Services …
PEOPLE INTEGRATION Multi Channel Access Composite Application Framework
… Self services, shared folders and joint projects ...
APPLICATION PLATFORM J2EE ABAP DB and OS Abstraction
Some examples of functions that use NetWeaver technology ¤ SAP AG 2008
SAP ERP is based on SAP NetWeaver.
This slide shows a number of examples. Many self-services are delivered along with SAP ERP.
Other functions such as self-service procurement use the Integration Broker (SAP Exchange Infrastructure).
(©) SAP AG
IUT110
1-6
SAP ERP and SAP Utilities
SAP Switch Framework Extension Industry Business
Function Sets
SAP ECC SAP ERP Central Component 6.0
SAP Discrete Industries Mill Products SAP Utilities < SAP Telecommunications
Only one industry can be activated using Business Function Sets
SAP Oil and Gas …..
Core
Generic Business Functions Financial Services Global Trade ….. …..
< <
Multiple generic business functions can be activated
¤ SAP AG 2009
SAP Business Suite is industry-independent. However, many industries require special functions and processes. To fulfill these requirements, SAP provides industry-specific solutions.
These industry solutions result partly from working closely with strategic development partners. Industry-specific functions are developed for these solutions and the solutions are offered as SAP solutions.
The industries are activated using the SAP Switch Framework and the corresponding Business Function Sets.
(©) SAP AG
IUT110
1-7
SAP Business Suite SAP Business Suite SAP PLM
Purchase Requisition
SAP SRM
SAP ERP 6.0 SAP for Utilities
Sales Order Management Contract Management
Lifecycle Data Management, Project Management, Quality Management and Asset Management
SAP CRM
Inventory and Facilities Management Production and Shipment
SAP SCM
SAP NetWeaver ¤ SAP AG 2009
SAP ERP is a solution in SAP Business Suite. It is based on the requests and requirements of customers and user groups as well as on information from analysts and leading experts. This is to ensure that the challenges that current and future customers have to face in the marketplace are always met.
The core functions and solutions from SAP ERP are extended and enhanced by the following solutions of SAP Business Suite: • SAP Customer Relationship Management - SAP CRM is a solution that puts the customer first. The customer can use a variety of channels to contact the company. • SAP Product Lifecycle Management - This solution provides functions for product development, product safety, quality assurance, and plant maintenance. • SAP Supply Chain Management - The supply chain does not end at the warehouse door. You can use SAP SCM to plan and optimize supply chains across the entire company. • SAP Supplier Relationship Management - Buying on the Internet or on the marketplace is just one possibility for optimizing procurement. Employees can use this solution to notify the purchasing department of their requirements quickly and effectively.
(©) SAP AG
IUT110
1-8
SAP Business Suite Integration
SAP BCM Corpor ate C ommu nicat ion Services
Channels
Soluti on Cap abilities
Customer
SAP CRM Interaction Center
Outb Per s Mobil Unified Cont act Routing e ound onal Cont Tel e Cont Cont IVR and Vo icemail Servi ces act phon act act y Cent Cent Cent Online Monit oring , R eport ing and An alysis ers ers ers
Sales and Distribution
Logistics
Marketing
Accounting
Service
…
Inbo und
Interaction and Communication
and Centr aliz ed Manag ement an d Administr ation Tel ep Director y and Pr esen ce Servi ces hon y Voice Log ging
SAP CRM
SAP ERP
SAP Business Suite
SAP BI /Analytics
¤ SAP AG 2009
SAP CRM Interaction Center is an integral component of SAP CRM.
SAP Business Communication Management (BCM) is a multi-channel platform for bi-directional contact.
(©) SAP AG
IUT110
1-9
Developing Customer Interaction
IC WebClient • since 2004 • SAP CRM 2007 • SAP ERP 6.0
IC WinClient L Shape CIC • 2000 • IS-U/CCS 4.61
• 2002 • CRM 3.0 • IS-U/CCS 4.71
Front Office • 1998 • IS-U/CCS 1.2 ¤ SAP AG 2009
(©) SAP AG
IUT110
1-10
SAP Utilities is ... SIMPLE
COMPREHENSIVE
FLEXIBLE
Intuitive Web-based
Business processes
Individual processes can
user interface Role-based profiles Simple adjustment by configuration
for the utilities industry For residential, commercial and industrial customers Numerous communication channels: Telephone, e-mail,
be included and integrated easily in the existing landscape Seamless integration of services
interactive forms, Internet selfservices, voice self-services, Web shop, meter, …
¤ SAP AG 2009
(©) SAP AG
IUT110
1-11
SAP Utilities Strong Points ; Supports deregulation scenarios ; Integration of application areas
Homogenous interaction between accounting and core logistics processes Business processes across all areas Shorter lead times for business processes
; Flexibility
Can be adapted to local deregulation rules Can be implemented in every type of company Supports all types of service Enables development of an individual business strategy
; Customer orientation
User-friendly Business process-oriented Competition-oriented Informative Communicative
; Open architecture ¤ SAP AG 2009
(©) SAP AG
IUT110
1-12
SAP Utilities and Business Intelligence (BI)
Efficient Analysis of Information - Innovative and intuitive user interface - Efficient OLAP analysis functions - For all types of user
Extensive Business Content - Information models, reports and extractors - Metadata repository - Company comparison values
End-to-End Data Warehousing Solutions
ERP Other
- Extraction of SAP ERP data and external data - Fully automated - Central control
¤ SAP AG 2009
SAP Business Intelligence (SAP BI) is the SAP business component that is used to extract and analyze data from operative business applications (OLTP systems). In addition to OLTP systems such as ERP and SAP BBP (Business-to-Business Procurement: E-commerce business process used by employees to purchase goods and services directly from other suppliers), other external data sources such as databases or online services can also be integrated. OLTP stands for online transaction processing.
SAP Business Intelligence supports online analytical processing (OLAP) and is designed to process large volumes of operational and historical data.
SAP BI contains all of the metadata required for common business processes. This includes InfoSources, InfoObjects, InfoCubes, and standard reports, transfer structures for all releases, and communication structures and update rules for each InfoCube. These elements are part of a "readyto-go" strategy that supports automatic data transfer with immediate analysis once the system has been installed and the source system defined.
SAP BI requests application data at regular intervals from the assigned source systems (pullmechanism). For this reason the backend systems contain extractors that collect data and deliver it to SAP Business Intelligence.
(©) SAP AG
IUT110
1-13
SAP Utilities Deregulation Consumption values, grid usage bills, customer data, and technical data
Electronic Data Exchange Distributor
Supplier Customer change, changes to customer data, grid usage payment, service requests
Provides the supply grid and accompanying services
¤ SAP AG 2009
(©) SAP AG
Creates utility contract, bill, makes collections
Customer/ point of delivery
IUT110
1-14
SAP Utilities Customer E-Services UCES = SAP Utilities Customer E-Services 6.02 Move-in
Move-out
Move-in/out
Enter meter readings
Display BB plan
Change BB plan
General contact
Overview of open invoices
Meter overview
Master data change
Credit memo overview
User creation
Contract details
Contact history
Overview of paid invoices
Payment details
Bank data maintenance
Credit memo clearing
Password change
Meter reading history
Rate comparison
Bill display
Partial payment
Credit card data maintenance
E-mail notification
FAQ
Consumption history
Interim bill
Bill payment
Direct debit mandate
Confirmation
Complaint
Anonymous Documentation of Meter reading dates meter reading user activities entry
IS-U/CCS 4.64 UCES 6.0 UCES 6.02
IS-U/CCS 4.72
(4.64 downgrade as project solution)
SAP ERP 6.0
(4.64 downgrade as project solution)
SAP Enhancement Package 2 for SAP ERP 6.0
¤ SAP AG 2009
(©) SAP AG
IUT110
1-15
SAP Service Marketplace
Î
SAP ERP
Î
http://service.sap.com/erp
Î
http://service.sap.com/Utilities
SAP NetWeaver
Î
http://service.sap.com/netweaver Î
New Release Strategy http://service.sap.com/releasestrategy
Development News
Î
http://service.sap.com/developmentnews Î
SAP for Utilities
Upgrade Information Center
Release Notes http://service.sap.com/releasenotes
Î
http://service.sap.com/upgrade-erp
Online Help http://help.sap.com
¤ SAP AG 2009
(©) SAP AG
IUT110
1-16
Overview: Summary
z SAP Utilities supports all the customer-oriented core business processes of utility, waste disposal, and service companies. z SAP Utilities is an integral part of the SAP ERP component. z SAP Utilities is designed for billing and managing standard divisions as well as for offering additional new services.
¤ SAP AG 2009
(©) SAP AG
IUT110
1-17
(©) SAP AG
IUT110
1-18
IC and Master Data
Contents: z Interaction Center Objectives z Deploying and Working with the Interaction Center z Interaction Center Processing Steps z Interaction Center Application Areas z Master Data z Customer Contacts and Interaction Records
¤ SAP AG 2009
(©) SAP AG
IUT110
2-1
IC and Master Data: Unit Objectives
At the conclusion of this unit, you will be able to: z Name the most important SAP Utilities objects z Describe the range of applications z Explain how to use the Interaction Center z Execute some standard customer processes z Create and utilize Customer contacts z Create and utilize Interaction Records
¤ SAP AG 2009
(©) SAP AG
IUT110
2-2
IC and Master Data: Business Scenario
z Customer Call and Identification z Data Environment
Business master data display
Technical master data display
z Changes to Data
Changes to bank details
Changes to budget billing amount
z Record Customer Interaction
¤ SAP AG 2009
(©) SAP AG
IUT110
2-3
IC Process Billing Correction
Identify customer in Interaction center
Execute
Select
Correct
Simulate
Billing
and display
the Meter
bill or
Correction
Print
Reading
process
Process
Document
Result
rebill
¤ SAP AG 2009
To process the billing correction directly, the agent can chose between two options: •
Process Full Reversal – the original bill is fully reversed and the rebill is processed as new
•
Process Adjustment Reversal – the net difference between the original and new bills is sent to the customer
The agent can directly enter the new reading results or can utilize standard estimation functionality to obtain an estimated result
(©) SAP AG
IUT110
2-4
IC Process Create Installment Plan
Identify customer in Interaction center
Execute
Select
Create Installment
and display
Plan
Open Items for Account
Accept or adjust proposed plan details
Save Installment Plan
Process
¤ SAP AG 2009
To create the installment plan, the agent can chose between two procedures: •
Enter the installment amount - The installment amount is determined from the sum of original items and the installment amount
•
Enter the rounding amount and the number of installments - The installment amount is determined from the sum of the original receivables, the rounding amount, and the number of installments
The system uses the parameters to create an installment plan proposal
The agent can still make changes to the proposed installment plan (such as add/delete installments, calculate interest, create fees for the creation of the installment plan).
(©) SAP AG
IUT110
2-5
IC Process Customer Overview
z Business Partner z Contract Account z Account Balance z Budget Billing Amounts z Invoices z Historical Consumption Values z Contract Overview z and much more
¤ SAP AG 2009
(©) SAP AG
IUT110
2-6
Requirements for IC
z Efficient user interface z Short training period z All normal business processes must be preconfigured and accessed directly z Entry with incomplete data and comprehensive search help z User-specific modifications to the interface and the available business processes z Connection to communication management systems (SAP BCM)
¤ SAP AG 2009
(©) SAP AG
IUT110
2-7
IC WebClient Layout Scratch pad
Account
Alerts
Communication information
info
[email protected]
Sandra Turner
Toolbar
System messages Interaction Record 5009874
Navigation bar
Hello, I have problems with the XY-Interface of my notebook HT-1010. Sandra Turner
Follow-up and Actions
Activity Clipboard e-mail Customer Solution e-mail Service
Broadcast messages
In: Notebook: Problem Sandra Turner, Denver, Colorado Check ZP-Installation file Out: Notebook: Solution Service Order
Work space
Last Interactions
Status
¤ SAP AG 2009
(©) SAP AG
IUT110
2-8
IC Inbox and Connection to SAP BCM e-mail, fax, letters (scanned documents) ...
Business Partner
Confirmation
tes Execu
System
Workflow
Work item in inbox for email, fax, letters ...
Displays customer data in interaction center
Call Center Agent ¤ SAP AG 2009
Business Communication Management (BCM) is complementary software which provides a flexible multi-channel all-IP business communications platform. It enables telephony integration, supports chat, e-mail, voice and SMS.
An all-IP, browser-based solution which is designed to work with SAP CRM out of the box.
(©) SAP AG
IUT110
2-9
SAP Utilities Data Model – House
Connection Object
Apartment 1= Premise Utility installation 1: Electric meter
Contract 1: Electricity
Entrance Hall
Apartment 3
Device loc.: Corridor Contract account Business partner
Contract 2: Gas
Utility installation 2: Gas meter
Contract 3: Water
Utility installation 3: Water meter
Service connection water Service connection gas
Apartment 2
Device loc.: Basement
Basement
Service connection electricity
Supply grid
Street ¤ SAP AG 2009
Relations: •
1 Business Partner : n Contract Accounts
•
1 Contract Account : n Contracts
•
1 Contract : 1 Installation (time-dependent)
•
1 Connection Object : n Premises
•
1 Connection Object : n Device Locations
•
1 Premise : n Installations
•
Device relations depend on scenario
(©) SAP AG
IUT110
2-10
Various Business Partners
Owners Customer
Debitors
SAP Business partner Installer
Tenants
Prospect z
Employee
z z z
Individuals and companies Business partner relationships Flexible interfaces Integration of business roles
Commercial and industrial customer
Groups
¤ SAP AG 2009
The SAP Utilities Industry solution is flexible enough to support all types of business partners.
The Business Partner concept is used in many functional areas of the solution:
•
Employees in HR
•
Installers in PM
•
Prospects in CRM and Marketing
The same entity can be represented only once in the system, regardless of the application areas which use it for processing.
(©) SAP AG
IUT110
2-11
Roles of the Business Partner
• Name • Address • Personal Data • Communication
Business Partner
Contract Partner
• Payment • General data (Account class, Social insurance, Creditworthiness...)
Installer
• Type of company • Division license • Field of work • License • Identity card • ...
Prospect
• Branch of industry • Relationships • Contact history • ...
¤ SAP AG 2009
Role definition: Roles are defined specifications for a business partner.
The central business partner concept enables you to:
•
Define the business partner globally
•
Model different business partner roles in the system
The specific roles of the business partner in SAP Utilities are: •
Contract partner
•
Installer
•
Contact person
•
Prospective customer
•
Other 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
•
Bill recipient
•
Suppliers
•
A prospective customer targeted by marketing activities
•
The owner of an apartment or house
(©) SAP AG
IUT110
2-12
Business Partner Data
BP Relationships General
• Hierarchical • Equal • Connected
• Form of address, name • Legal form, company • Group, search terms
Payment transactions • Bank details
Addresses • Standard address • P.O. box address • Other addresses
SAP Business partner
Biller Direct
Communication
Additional data
• Telephone, fax • Extension • Internet, e-mail, online
• • • •
Data for all roles
Status Identification numbers Legitimization Register entry
Data for specific roles
¤ SAP AG 2009
Business partners are divided into various groups, to which different attributes are allocated. SAP Utilities differentiates between: •
Individuals
•
Organizations
•
Groups
Depending on the business context, the business partner can assume different roles. SAP Utilities differentiates between: •
Contract partner
•
Installer
•
Contact person
•
Prospect
Other roles depend on Customizing
A sales and distribution (SD) business partner is created in the background for each contract partner.
(©) SAP AG
IUT110
2-13
Contract Account Data
General data z z
z z
Dunning data
Account name Account no. in legacy system Terms of payment Tolerance group
z z z
Dunning control Dunning letter recipient Dunning block reason
Incoming payments Control z z
z
Alternative bill recipient Paid by collective bill account Additional bill
z
Contract
z z
account Outgoing payments z
Account assignment
z z
z z z z
Where-used list for Ols Planning group Account determination Clearing category
Payment method Bank details Alternate payer
Payment method Bank details Alternate payee
Biller Direct
General data
Dunning/payment data
¤ SAP AG 2003
A contract account groups together all of a business partner's contracts that have the same payment and dunning data. Contracts that are created with the business partner are allocated to the contract account. As a result, any number of contracts can be allocated to a contract account.
(©) SAP AG
IUT110
2-14
Collective Bills
Contract Contract partner partner
Contract account 1
Contract 1 (Elec. - domestic)
Contract 2 (Water - domestic)
Contract account 2
Contract Contract account account collective collective bill bill
Contract 3 (Gas - business)
Contract 4 (Elec. - business)
Bill CA 1
150.--
100.--
300.--
Total : 250.--
Collective bill
100.-Total : 450.--
Contract account 3
Contract 5 (Elec. - business)
50.--
(Statistical posting to contract collective billing account CBA 1)
Optional Bill CA 2 Total : 400.--
Bill CA 3 Total : 50.--
¤ SAP AG 2009
The collective bill account is a contract account that is created in the business master data of the utilities industry and is marked as a collective bill account. Several contract accounts can refer to the same collective bill account.
The collective bill account groups together items that are posted to the individual accounts and that refer to the collective bill account under one or more collective bills. Only items with the same due date and origin can be grouped together in a collective bill.
(©) SAP AG
IUT110
2-15
Contract Data General Contract Data • • • • • •
Account assignment data
Contract account Division Company code Individual/operation consumption Statistics group Authorization groups
• Account determination ID • Cost center • Business area
Sales data Move-in/Move-out data • Installation • Move-in date • Move-out date
• Sales partner •Representative • Sales document
Contract (Billable service)
Deregulation data • Service Provider • Service provider invoicing • External contract number • Payment class
Scheduling data • Contract start/end date • Renewal dates • Cancellation dates
Data Relevant to Budget Billing
Data Relevant to Billing • Joint invoice • Billing Blocking Reason • Outsorting group
• Budget billing adjustment • Budget billing cycle
¤ SAP AG 2006
In the field 'Statistics Group', you specify the statistics group for a contract. This is used for determining data for sales statistics.
The Authorization Group prevents unauthorized access to specific 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.
If you maintain data relevant to budget billing (for example the budget billing cycle) in the contract, the data you enter overrides the default values defined in the portion or in 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, 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 billing 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.
Schedule data is provided mainly for information purposes. It allows you to display information on when a contract was signed or cancelled, for example.
(©) SAP AG
IUT110
2-16
Connection Object Data
Location Data
General
• Maintenance plant • Location description • ABC indicator
• Text • Processing status • Notes
Address
Plant Maintenance • Structure • Planning plant • Planner group
Connection Object
• Street, house number • Postal code, city • Political ?regional structure
Other Data
Properties
• Structure/equipment list • Account determ
• Regional structure group • Authorization group
PM Data
Data Specific to SAP Utilities
¤ SAP AG 2008
A connection object is normally a building. However, it can be a plot of land or other structure such as a fountain or a building site. The connection object corresponds to the functional location in the Plant Maintenance (PM) component and has the same key.
(©) SAP AG
IUT110
2-17
Premise Data
Connection object
Location data z z z
z
Floor Room number Location description
Installation
Attributes z z z
Premise type Owners Number of occupants
Premise
z
z
Can comprise several installations to be billed
Technical
Additional data z
Forms the link between the premise and the regional structure
Notes Update log
z
Can be assigned to a device location
General data
Relationships
¤ SAP AG 2009
The premise is a spatially enclosed unit (such as an apartment, factory floor) that has to be supplied.
The premise is allocated to a connection object.
Owner attribute enables Landlord Automatic Turn on/Move-in process.
(©) SAP AG
IUT110
2-18
Installation Data
Billing
Process Data z z z
z
Current premise Current business partner Current contract
z
z
Business Partner
Control Data z z z
Supply or consumption Definition of base period Meter reading control
Rate category Rate data for device and registers Reference value
z
Installation
Linked to the conclusion of contract with the business partner
Regional Structure Other Data z z z z
z
Installation type Guarantee of supply Notes Change log
z
Linked via the premise and connection object Overriding of default meter" reading unit
General Data
Relationships
¤ SAP AG 2009
The installation is the most important technical master data object in SAP Utilities.
The installation contains the important control data for meter reading and billing.
The installation groups together division-specific devices, registers and, where applicable, reference values that are allocated to a premise and, as a result, are billed jointly.
The installation is allocated to a specific contract. Only in exceptional cases is it not allocated to a contract (for example, the installation is under construction, there is no owner for the installation).
The installation contains the meter reading unit with the scheduling data.
The installation contains the rate category with the billing rule data.
The installation contains information about the service (for example, grid usage or supply).
The installation references the point of delivery.
The installation references the synthetic load profile for SLP customers (Load Profile button).
The installation references the installation structure (Devices button).
The installation references the meter reading, billing, and print documents (Billing View button).
(©) SAP AG
IUT110
2-19
Point of Delivery Data
Point of Delivery ID
Header Data
• Structure category • History
• Description • Point of delivery type • Point of delivery role
Point of Delivery Deregulation
Technical
• Installation • Premise • Service type • Grid (grid operator) • Settlement unit
• Register
¤ SAP AG 2009
The point of delivery is the point to which a utility service is supplied for a customer.
The point of delivery is identified by a unique key, the point of delivery ID. This is used for communicating with external systems. The unique ID ensures that registered data and information about a utility service that is rendered at a point of delivery is not incorrectly allocated, even when a customer switches his or her utility company.
The deregulation point of delivery is used to communicate between different utility companies in a deregulated energy market. An example of this could be the exchange of consumption information between a distributor and a supplier.
The technical point of delivery is used to communicate with a remote meter reading system. This type of communication is used in the Energy Data Management (EDM) component for importing profile values.
(©) SAP AG
IUT110
2-20
SAP Utilities Data Model IS-U Business Partner
FI-CA
Regional Structure
SD CS PM
Cross-Appl.
Contract Account
Integration with Logistics Contract (Supply) Service PoD
Device Category
Installation
Premise
Device
Device Location
Connection Object
Connection Meter Reading ¤ SAP AG 2009
(©) SAP AG
IUT110
2-21
SAP Utilities and SAP CRM Data Model
SAP ERP / SAP Utilities
SAP CRM
Business Partner
Account
Contract Account
Bill
Business Agreement
Contract
Billing
Contract
Installation
Premise
Connection Object
PoD & Premise
Connection Object IBASE
PoD
Profile
Profile
¤ SAP AG 2009
The mapping of master data objects is displayed here based on the data models of both systems. •
1:1 - Mapping of the business partner and the contract accounts
•
Parts of the SAP IS-U contract and the installation together represent the utility contract in SAP CRM.
•
The technical data is mapped in a leaner hierarchy in SAP CRM. This means that only the connection object and the points of delivery beneath it exist in the SAP CRM system. The point of delivery in SAP CRM also contains data from the SAP IS-U premise (for example, the floor).
•
The billing and invoicing data is only known in SAP IS-U.
•
Profiles in CRM: Historical profile, forecast profile, and schedule profile
•
IS-U customer contacts are replicated to CRM interaction records.
(©) SAP AG
IUT110
2-22
Contract Management with SAP CRM and SAP ERP SAP CRM
SAP for Utilities
CRM Contract 2
1 Point of Delivery SAP CRM Product
Switch Document
Beginning of Market Communication
Configuration
…
3 Status
4
SAP Utilities Master Data Template
Master Data Generator
SAP for Utilities
Configuration
¤ SAP AG 2009
(1) The contract is created in CRM – by allocating a product to a service location (IBASE) and customer (account).
(3) The replication process creates the necessary objects in the backend IS-U system. The product allocates to an MDT configuration which controls the replication.
(2) If IDE is required, then the market communication is also triggered by the CRM contact creation.
(©) SAP AG
IUT110
2-23
Contact Management in Customer Service
WWWWWW
Fax
Letter
Telephone
Internet
In person
z Recording of contacts resulting from:
Personal customer service, telephone calls
Correspondence, fax, Internet, e-mail
z Evaluation of contacts for:
Comprehensive overview of customer service
Quality and efficiency of consulting processes Utility Company
¤ SAP AG 2009
Customer contact management in SAP Utilities is designed to record all types of customer contact between the utilities company and the customer.
Customer contacts can be classified during creation according to class, type and the corresponding activity.
Interaction records can be automatically saved during customer interaction process.
Business transaction details can be attached to interactions.
IS-U Customer contacts are replicated into CRM Interaction Records providing IC users with a full picture of all customer interactions.
(©) SAP AG
IUT110
2-24
Customer Contact Data
General z z z
References
Business partner Contact partner Contact number
z
z
Notes
Process Description z z z
Date, time Contact class Contact activity
Customer Contact
z
z z
User-defined text Indicator for additional documents
Other Data
Communication z
Reference to any business objects Permissibilities can be set
z
In person, telephone, fax, Internet, mail, online Incoming, outgoing
z
User-defined fields for example, division, company code Authorization group
¤ SAP AG 2008
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: Information, billing, budget billing amount, ...
The contact activity describes the type of activity between the business partner and the utility company.
Example: Rate information, account information, ...
(©) SAP AG
IUT110
2-25
IC and Master Data: Summary
z The Interaction Center is designed to deal with
information-based and operational processes. z The processing interface is an efficient work
environment that provides quick access to critical information. z The openness and flexibility of the Interaction Center
enable you to integrate business processes in the best possible way. z Contact management enables you to evaluate the
complete contact history of business partners.
¤ SAP AG 2009
(©) SAP AG
IUT110
2-26
Exercises Unit: Interaction Center (IC) Topic: Using the IC After completing these exercises, you will be able to: • Describe the purpose of the IC and the areas in which it can be used • Use the IC to work through processes efficiently As an employee in the customer center, you need to process customer inquiries quickly, completely, and correctly. This increases both customer satisfaction and efficiency at work. A sound working knowledge of the IC will help you achieve this. 1-1
Which units make up the Interaction Center? What are their tasks? Unit 1: _____________________________________________ Task: _____________________________________________ Unit 2: _____________________________________________ Task: _____________________________________________ Unit 3: _____________________________________________ Task: _____________________________________________ Unit 4: _____________________________________________ Task: _____________________________________________
1-2
True or false? 1-2-1 The IC is the central point of access for agents to handle both simple and complex business processes. __________________________________________________ 1-2-2 The IC has flexible, powerful search functions. __________________________________________________ 1-2-3 The IC determines the process flows. __________________________________________________ 1-2-4 The IC automates business processes. __________________________________________________ 1-2-5 The data finder always identifies the business partner as the result of a search. __________________________________________________
(©) SAP AG
IUT110
2-27
1-3
Logon with user IUT110-## to the SAP CRM System TPZ. The logon process is described in the Solution of this exercise.
1-4
To which business partner is the device with serial number ISU11020## allocated? What is the address of the connection object? Proceed as follows: •
Choose the Point of Delivery by Device option within the Search Function field.
•
Enter the device serial number in the premise search window.
•
Press Enter to process the search criteria
Business Partner Number
1-5
Address
Enter the address of the connection object in which the device is located. Which premises are contained in the connection object from task 1-3? Proceed as follows: • In the search results list, click on the arrow to expand the Connection Object and find all assigned premises. • Premise Number
1-6
Short Text
End the interaction.
(©) SAP AG
IUT110
2-28
1-7
Identify all customers for the connection object in Pinewood Avenue 33##. Which business partners live in Pinewood Avenue 33##? Proceed as follows: • In the Search for Business Partner section, enter the address data as the search criteria. • You can also enter just part of the name of the street, for example, Pinewo*. • Press Enter to process the search criteria. Business Partner Number
First and last names of business partner
Select and confirm Max Mayer and complete the following table: Question
Answer
How many contract accounts are assigned to Mr. Mayer? Which types of contract does Mr. Mayer have? Which devices are assigned to Mr.Mayer? 1-8
Display the data environment of the premise for the contract ISU260A3##.
1-9
Display the data for the devices and complete the following table: Information
Electricity Meter
Gas Meter
Serial number Device category / material number Name of device category Division Disconnection status
(©) SAP AG
IUT110
2-29
Web Client - Exercises Unit: Interaction Center (IC) Topic: Customer Interaction Management After completing these exercises, you will be able to: • Create various customer contacts • Evaluate and display customer contact history By documenting all customer contacts comprehensively, you can provide a more efficient service to your customers. The link to business objects allows you to access the relevant information instantly.
2-1
Create a customer interaction for the following situation: 2-1-1
2-2
Customer ISU11030## calls to report a complaint with a move-in . You record the complaint in a customer interaction and save the interaction record.
Display the interaction history for a customer. 2-2-1
Display all customer interactions in the IC for customer ISU260A3##. Navigate to the detailed display for the interaction record to view the attached objects. How many, and what kind of contacts does the customer have? Date
(©) SAP AG
Category
Description
IUT110
Status
2-30
2-3
True or false? 2-3-1
All customer interactions are always created automatically. ______________________________________________________
2-3-2
Customer interactions are not grouped in any meaningful manner. ______________________________________________________
2-3-3
Customer interactions can only be displayed for one business partner at a time. ______________________________________________________
(©) SAP AG
IUT110
2-31
Web Client- Exercises Unit: Interaction Center (IC) Topic: Master Data in SAP Utilities After completing these exercises, you will be able to: • Explain the SAP business partner model • Explain the SAP Utilities master data • Explain the integration of SAP Utilities master data with SAP ERP As an employee in customer services, you have been assigned to telephone service. Some customers only want to obtain information, others request changes to data. Your central working environment is the IC.
3-1
Customer ISU11010## notifies you of new bank details that are to be used for automatic debits from his account.
3-1-1
•
Start from the IC.
•
Use the payment data link.
•
Perform complete process in IC.
Enter the selection criteria, and display the payment data view to view the current bank details for the customer’s account. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________
3-1-2
Click on the Create New Bank Details button, enter the new bank details, and save your data. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________
(©) SAP AG
IUT110
2-32
3-1-3
Assign the new bank details as the payment method for incoming payments. Save your changes. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ Return to the IC. ______________________________________________________
3-2
Change the description for electricity account ISU11020##. Change the description from Residential Account to Private Account 0##. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ End the contact.
3-3
True or false? 3-3-1
Data for a business partner who is also a contract partner, installer, and contact person, has to be entered more than once. ______________________________________________________
3-3-2
The contract account can be assigned to several business partners. ______________________________________________________
3-3-3
The contract account is the contract partner’s customer account. ______________________________________________________
3-3-4
The contract contains rate data for all divisions. ______________________________________________________
3-4
3-5
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 account ISU11020##. 1.
__________________________________________________________
2.
__________________________________________________________
3.
__________________________________________________________
True or false? 3-5-1
The connection object is always a building. ______________________________________________________
(©) SAP AG
IUT110
2-33
3-5-2
The connection object can comprise one or more premises. ______________________________________________________
3-5-3
The connection object is managed as equipment in the component PM (Plant Maintenance). _____________________________________________________
3-5-4
The device location is subordinate to the connection object. ______________________________________________________
3-5-5
Individual devices are installed in the connection object. ______________________________________________________
3-5-6
The premise is managed as a functional location in PM. ______________________________________________________
3-5-7
The installation groups together the measuring devices of a division that are allocated to it and a premise for the purpose of joint billing. ______________________________________________________
3-5-8
The installation manages basic billing control parameters. ______________________________________________________
(©) SAP AG
IUT110
2-34
Exercises Unit: Interaction Center (IC) Topic: Financial Information At the conclusion of this exercise, you will be able to: • Search for and display financial information about an account in the FCC
A customer of the company you are working for calls the interaction center for getting some financial inquiries. You would like to give the calling customer the information.
4-1
Identify the Account of the customer who is calling you. The Account ID is ISU260A3##. Get a quick financial overview of the customer. 4-1-1
How many Business Agreements and Contracts does the Business Partner have?
4-1-2
What are the amounts of all open items and due items of all involved business agreement together?
4-1-3
Concentrate now on Business Agreement ISU260T3##. Which amount of this Business Agreement is open?
4-1-4
What additional information could you see in the Account Balance?
4-1-5
Are there already installment plans existing for the Business Agreements?
4-1-6
End the Contact with the Customer
(©) SAP AG
IUT110
2-35
(©) SAP AG
IUT110
2-36
Solutions Unit: Interaction Center (IC) Topic: Using the IC
1-1 Unit 1: Identification bar Task:
Confirmed data in current process
Unit 2: Navigation Toolbar Task:
Transaction groupings for initiating various customer processes. Start comprehensive business processes, such as account display, installment plan creation, service initiation, etc
Unit 3: Workspace Task:
All views for a viewset – provide information and links to other processes
Unit 4: Telephony toolbar Task:
Controls integration with CTI components
1-2-1
True. The IC integrates both simple information and environment displays and workflow processes that are used to control comprehensive business processes.
1-2-2
True. The IC enables you to enter a variety of search criteria in order to find the data for a business partner. A business partner can be determined by means of the name or device number, for example.
1-2-3
False. The IC can be flexibly adjusted to the process flows of the user groups. True. The IC supports the user when working through process flows.
1-2-4
True. Since IC and workflow processes are integrated in the IC, business processes are controlled and forwarded automatically.
1-2-5
False. The data finder identifies the business objects you were searching for and that belong to a business partner.
1-2
(©) SAP AG
IUT110
2-37
1-3
Open the CRM Interaction Center Log on to the SAP CRM system using SAP GUI. Do some preparation steps which will allow you to start the CRM Web UI. System
TPZ
Client 770 User IUT110-## Password init Language EN or DE In the Favorites Menu choose CRM 7.0 or use the following Link: http://tpztdc00.wdf.sap.corp:52080/sap/crm_logon?sap-client=770 In the following Pop-Up-Window please enter once more: User Name IUT110-## Password the new password you selected above 1-4
In the Identification section of the Work Area, within the Search Criteria view, choose Point of Delivery by Device in the Search Function field and enter the number ISU11020## in the Serial Number field. Press Enter. The system confirms the premise in which the device is located. It also confirms the business partner and account which are currently active at that service location. Both objects are now displayed in the Information Bar.
1-5
1-6
Select the premise in the navigation area on the Environment tab page. The object is highlighted in color. Click on the right mouse button and choose Connection Object Environment and then Continue. Premise Number
Short Text
ISU11020##
Pinewood Avenue 20##, New York City
Return to the IC. Choose End .
(©) SAP AG
IUT110
2-38
1-7
In the identification area, search for the street in which the connection object is located. Enter the search criteria. Business Partner Number
First Name/Last Name
ISU260A3##
Max Mayer
Select Mr. Max Mayer. The system displays the data environment for the business partner. You can now answer the following questions: Question
Answer
How many contract accounts are Mr. Mayer has three contract accounts: assigned to Mr. Mayer? ISU260A3## ISU260C3## ISU260T3## Which types of contract does Mr. Mayer have?
Which devices are assigned to Mr. Mayer?
Mr. Mayer has four utility contracts: Electricity contract: ISU260A3## Gas contract: ISU260 B3## Water contract: ISU260C3## Electricity contract: ISU260D3## Mr. Mayer has 4 devices: Electric meter: ISU260A3## Water meter: ISU260C3## Gas meter: ISU260B3## Electric meter: ISU260D3##
1-8
Click on the Overview button on the Navigation Toolbar. Then click on the Technical Data Environment. Find the premise for contract ISU260A3##. 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.
•
Meters are allocated to all installations.
(©) SAP AG
IUT110
2-39
1-9 To display a device, click on the device . You can now answer the following questions: Information
Electricity Meter
Gas Meter
Serial number
ISU260A3##
ISU260B3##
Device category / material number
TD-SRA-00
TD-GA-01
Name of device category
Single rate meter
gas meter
Division
01
Gas
Disconnection status
Not disconnected
Not disconnected
(©) SAP AG
IUT110
2-40
Web Client -Solutions Unit: Interaction Center (IC) Topic: Customer Contact Management
2-1
From the main window of the IC, enter the selection criteria for the business partner ISU11030## and confirm the partner. 2-1-1
2-2
Click on the Interaction Record view, Search in the Reason field for a reason for the complaint and choose ‘4. Problems in Move-in /-out’. Enter some text in the Notes section and save the interaction. Click on End.
Identify business partner ISU260A3##. 2-2-1
Click on the Interaction Record view, look at the Interaction History at the bottom of the page. The system displays a list of all interactions for this customer. Click on a line to display the customer interaction details. The following interactions exist: Date
(©) SAP AG
Category
Description
Status
11.01.07
-
Move in [Contract]
Open
12.01.07
-
Move in [Contract]
Open
26.01.07
Complaint
Dunning reminder sent
Completed
IUT110
2-41
2-3 2-3-1
False. You can also enter customer contact data manually. The system creates the IC contact automatically based on configuration settings
2-3-2
False Interaction records can be cateogrized and grouped using the Reason/Priority field.
2-3-3
(©) SAP AG
False. The information system in ERP can evaluate all customer contacts according to different criteria. Within the IC, however, interactions can only be shown per business partner.
IUT110
2-42
Solutions Unit: Interaction Center (IC) Topic: Master Data in SAP Utilities
3-1 3-1-1
Once you have identified the customer ISU11010##, click on the Payment Data view. In the Existing Payment Data area you can see the currently stored bank details.
3-1-2 Click on the Create New Bank Details button. In the Bank details section, enter new bank details. In the Bank Key field, use the help to select a bank number, i.e. Chase Manhattan - 2222222222. In the Ctry field, confirm US. In the Bank Account field, enter an account number. Save the changes. You have now allocated new bank details to the business partner. 3-1-3
(©) SAP AG
In the new line for the bank details, click on the Assignments to Business Agreements column, where the text currently displays ‘No assignment’. Check the box for incoming payments and click on the Save button to assign the payment details to the account. Click on End.
IUT110
2-43
3-2
Identify business partner ISU11020## Click on the Overview view in the Navigation bar. Click on the Residential Account ISU11020## in the Environment view. At the detail screen, click on the Edit button. In the Text field, change the value from Residential Account to Private Account ##. Click on the Save button to save the changes and return to the Overview Screen . Click on End.
3-3
3-4
3-3-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-3-2
False. The contract account settings are such that you can only enter 1 business partner. However, a business partner can have several contract accounts. When you customize the contract account category, however, you can define the contract account so that it can be allocated to several business partners.
3-3-3
True. The contract account is the structure that allows the billing of posting data for contracts or contract items that have the same collection/disbursement agreements. A customer account is managed for a contract account.
3-3-4
False. The contract is an agreement between a business partners and a utility company that applies to a particular division. It contains control data for billing, budget billing plans, and accounts receivable and payable accounting. The rate data is stored in the installation and in the installation structure.
In ERP system TNU-770 Execute transaction code CAA3 to view the contract account. Enter account number ISU11020##The following three logs are located under the Extras menu: 1) Creation data 2) Field changes 3) Account changes
(©) SAP AG
IUT110
2-44
3-5 3-5-1
False. The connection object can also be a piece of land, fountain, or building site.
3-5-2
True.
3-5-3
False. The connection object is at the top of the functional location hierarchy.
3-5-4
True. Device locations are mapped as functional locations in the PM component and the connection object is the superordinate functional location.
3-5-5
False. Devices are installed in device locations and are thus only indirectly allocated to the connection object.
3-5-6
False. The premise is only used in SAP Utilities to group together installations of different divisions.
3-5-7
True. Devices, registers, and fixed payment billing factors assigned to a premise that are to be billed jointly are grouped together for a specific division. A premise can have several installations. These installations can refer to the same or different divisions.
3-5-8
True. The billing class and rate category are allocated to the installation. They have a considerable influence on the billing process.
(©) SAP AG
IUT110
2-45
(©) SAP AG
IUT110
2-46
Solutions Unit: Interaction Center (IC) Topic: Financial Information At the conclusion of this exercise, you will be able to: • Search for and display financial information about an account in the FCC A customer of the company you are working for calls the interaction center for getting some financial inquiries. You would like to give the calling customer the information.
4-1
Identify the Account of the customer who is calling you, ISU260A3##. Get a quick financial overview of the customer. Enter the identification number in the Account ID field and press enter to confirm/search.
Business Partner will be confirmed and also see the confirmed business partner in the account info box:
(©) SAP AG
IUT110
2-47
4-1-1
How many Business Agreements and Contracts does the Business Partner have?
Click on the Overview view, and then select the Business Agreements Overview to show the Business Agreements which exist for the customer. Click on the Contracts Overview to show the ISU service contracts which exist for the customer. Solution: 3 Business Agreements exist: - ISU260A3## with two contracts (electricity and gas), - ISU260C3## and ISU260T3## with one contract each (water / electricity)
(©) SAP AG
IUT110
2-48
4-1-2
Look at the Interaction History of the customer. What was the last contact with the customer about? Click on the Interaction Record view and then navigate to the Interaction History Overview. Solution: The customer got a reminder letter.
4-1-3
What are the amounts of all open items and due items of all involved business agreement together? Click on the Account Balance View and view the total balance for all business agreements in the Account Overview. Solution: The sum of all open and due amounts is 700.20 USD.
(©) SAP AG
IUT110
2-49
4-1-4
Concentrate now on Business Agreement ISU260T3##. Which amount of this Business Agreement is open? Solution: Actual open amount: 205.86 USD. These 205.86 USD are open more than 60 days. You get this information in the Balance overview of the account balance.
4-1-5
What additional information could you see in the Account Balance Solution: Last Dunning Notice from January 26, 2007 Dunning level 01 Total Amount 237.10 USD Last Billing (with navigation to archived Billing) Currently no Budget Billing
(©) SAP AG
IUT110
2-50
4-1-6
Are there already installment plans existing for the Business Agreements? Click on the Installment Plan button to pull up the Installment plan overview. Solution: Actually there are no existing installment plans for the Business Agreement.
4-1-7
End the Contact with the Customer Solution: Go to the current Interaction Record via Navigation bar. Add a note in the Interaction Record, change the status to “completed” and save the Interaction Record and use the End Button in the Task bar to End the contact.
(©) SAP AG
IUT110
2-51
(©) SAP AG
IUT110
2-52
Exercises Unit: Interaction Center (IC) Topic: Using the IC After completing these exercises, you will be able to: • Describe the purpose of the CIC and the areas in which it can be used • Use the CIC to work through processes efficiently As an employee in the customer center, you need to process customer inquiries quickly, completely, and correctly. This increases both customer satisfaction and efficiency at work. A sound working knowledge of the IC will help you achieve this.
1-1
1-2
Which three units make up the CIC? What are their tasks? Unit 1:
_____________________________________________
Task:
_____________________________________________
Unit 2:
_____________________________________________
Task:
_____________________________________________
Unit 3:
_____________________________________________
Task:
_____________________________________________
Unit 4:
_____________________________________________
Task:
_____________________________________________
True or false? 1-2-1 The IC is the central point of access for agents to handle both simple and complex business processes. __________________________________________________ 1-2-2 The IC has flexible, powerful search functions. __________________________________________________ 1-2-3 The IC determines the process flows. __________________________________________________ 1-2-4 The IC automates business processes. __________________________________________________ 1-2-5 The data finder always identifies the business partner as the result of a search. __________________________________________________
(©) SAP AG
IUT110
2-53
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:
• Start the data finder with the All Search Criteria
button.
• On the Technical Data tab page, enter the serial number in the Device data area.
1-4
•
Choose Continue
•
In the IC, choose Continue
to exit the data finder. twice.
Enter the address of the connection object in which the device is located. Which premises are contained in the connection object from task 1-3? Proceed as follows: • Select the premise in the navigation area on the Environment tab page. • Click on the right mouse button to choose the Connection Object Environment. Premise Number
Short Text
1-5
End the contact.
1-6
Identify all customers for the connection object in Massachusetts Avenue 0##. Which business partners live in Massachusetts Avenue 0##? Proceed as follows: • In the Identification area, enter the street as the search criterion. • You can also enter just part of the name of the street, for example, Massach*. • Enter the language key EN.
(©) SAP AG
IUT110
2-54
Business Partner Number
First and last names of business partner
Select Elmer 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 for the contract TB010110##.
1-8
From the data environment, save the devices that belong to the premise on the clipboard.
1-9
Display the data for the devices and complete the following table: Information
Electricity Meter
Gas Meter
Water Meter
Serial number Device category / material number Name of device category Division Current business partner Current device location 1-10 How can you recognize that advanced search criteria have been entered in the identification area? ____________________________________________________________ ____________________________________________________________
(©) SAP AG
IUT110
2-55
(©) SAP AG
IUT110
2-56
Exercises Unit: Interaction Center (IC) Topic: Customer Contact Management After completing these exercises, you will be able to: • Create various customer contacts • Evaluate and display customer contact history By documenting all customer contacts comprehensively, you can provide a more efficient service to your customers. The link to business objects allows you to access the relevant information instantly.
2-1
2-2
Create a customer contact for the following situation: 2-1-1
Customer TB010110## reports a complaint against an employee by telephone. You record the complaint in a customer contact.
2-1-2
You provide customer TB010110## with general information that you describe in the customer contact by adding object links. Insert contract TB010110## and contract account TB010110##.
Display the contacts 2-2-1
Display all customer contacts in the IC for customer TB010110##. Check the object list and switch to the detailed display for the object. How many, and what kind of contacts does the customer have? Date
(©) SAP AG
Class
Action
IUT110
Type
2-57
2-2-2
Use the customer overview in the IC 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 0008 complaint. To do this, use the information system. From the SAP Easy Access menu, choose: Utilities Industry Æ Information System Æ Report Selection Æ Customer Service Æ Evaluate 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 be displayed for one business partner at a time. ______________________________________________________
(©) SAP AG
IUT110
2-58
Exercises Unit: Interaction Center (IC) Topic: Master Data in SAP Utilities After completing these exercises, you will be able to: • Explain the SAP business partner model • Explain the SAP Utilities master data • Explain the integration of SAP Utilities master data with SAP ERP As an employee in customer services, you have been assigned to telephone service. Some customers only want to obtain information, others request changes to data. Your central working environment is the IC.
3-1
Customer TB010110## has two contract accounts. The following exercise refers only to the account Private Account 0##. The customer notifies you of new bank details that are to be used for automatic debits from his private account.
3-1-1
•
Start from the IC.
•
Use the customer overview.
•
Process each step from the customer overview.
Enter the selection criteria, display the customer overview, and enter the current bank details for the customer’s private account. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________
3-1-2
Switch from customer overview to change mode for the business partner, enter the new bank details, and save your data. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________
(©) SAP AG
IUT110
2-59
3-1-3
Switch from the customer overview to change mode for the contract account, choose the private account, and enter the new bank details as the payment method for incoming payments. Save your changes. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ Return to the IC.
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 automatic debits from his community account. 3-2-1
In the navigation area, on the Environment tab page, select the contract account for business partner TB010110## and choose Change Bank Data. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________
3-2-2
Enter new bank details for the business partner and save your data. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________
3-2-3
Enter the new bank details as the payment method for incoming payments in the contract account and save your data. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________
3-2-4
Enter a remark in the customer contact and save your data. ______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________
3-3
Change the contract description for electricity contract TB010130## in the community account. Change the description from Electricity Contract to Community Contract 0##.
(©) SAP AG
IUT110
2-60
______________________________________________________ ______________________________________________________ ______________________________________________________ ______________________________________________________ End the contact. 3-4
True or false? 3-4-1
Data for a business partner who is also a contract partner, installer, and contact person, has to be entered more than once. ______________________________________________________
3-4-2
The contract account can be assigned to several business partners. ______________________________________________________
3-4-3
The contract account is the contract partner’s customer account. ______________________________________________________
3-4-4
The contract contains rate data for all divisions. ______________________________________________________
3-5
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.
__________________________________________________________
3.
__________________________________________________________
True or false? 3-6-1
The connection object is always a building. ______________________________________________________
3-6-2
The connection object can comprise one or more premises. ______________________________________________________
(©) SAP AG
IUT110
2-61
3-6-3
The connection object is managed as equipment in the component PM (Plant Maintenance). _____________________________________________________
3-6-4
The device location is subordinate to the connection object. ______________________________________________________
3-6-5
Individual devices are installed in the connection object. ______________________________________________________
3-6-6
The premise is managed as a functional location in PM. ______________________________________________________
3-6-7
The installation groups together the measuring devices of a division that are allocated to it and a premise for the purpose of joint billing. ______________________________________________________
3-6-8
The installation manages basic billing control parameters. ______________________________________________________
(©) SAP AG
IUT110
2-62
Solutions Unit: Interaction Center (IC) Topic: Using the IC
1-1 Unit 1: Identification Task:
Select data using flexible search criteria.
Unit 2: Navigation Area Task:
Specific information for customer inquiries. Start comprehensive business processes using SAP Business Workflow, amongst other things.
Unit 3: Application Area Task:
Own overview pages containing, for example, SAP Business Workflow, inbox, CIC contact management, and much more.
Unit 4: Action Box Task:
Calls business processes.
1-2-1
True. The IC integrates both simple information and environment displays and workflow processes that are used to control comprehensive business processes.
1-2-2
True. The IC enables you to enter a variety of search criteria in order to find the data for a business partner. A business partner can be determined by means of the name or device number, for example.
1-2-3
False. The IC can be flexibly adjusted to the process flows of the user groups. True. The IC supports the user when working through process flows.
1-2-4
True. Since IC and workflow processes are integrated in the IC, business processes are controlled and forwarded automatically.
1-2-5
False. The data finder identifies the business objects you were searching for and that belong to a business partner.
1-2
(©) SAP AG
IUT110
2-63
1-3
Call the IC. From the SAP Easy Access menu, choose: Utilities Industry → Customer Service Æ Front-Office/Customer Interaction Center Æ Customer Interaction Center Switch to the data finder and click on All Search Criteria
.
Go to the Technical Data tab page. In the Device data area, enter the number TB010110## in the Serial Number field. Exit the data finder by choosing Continue. Choose Continue twice. The first time you choose Continue, the system searches for the data using the selection criteria. If the system finds data that meets the search criteria, the second time you choose Continue confirms the search criteria. The system displays the premise in which the device is located. It also displays all the master data for the business partner. 1-4
1-5
Select the premise in the navigation area on the Environment tab page. The object is highlighted in color. Click on the right mouse button and choose Connection Object Environment and then Continue. Premise Number
Short Text
TB010110##
Massachusetts Avenue 0##, Boston
TB010120##
Massachusetts Avenue 0##, Boston
Return to the IC. Choose End Contact.
(©) SAP AG
IUT110
2-64
1-6
In the identification area, search for the street in which the connection object is located. Enter the search criteria. Since this connection object contains more than one business partner, all the business partners appear in the hit list. Business Partner Number
First Name/Last Name
TB010110##
Elmer Petersheim
TB010120##
Constance Bishop
Select Mr. Elmer Petersheim. The system displays the data environment for the business partner. You can now answer the following questions: Question
Answer
How many contract accounts are Mr. Petersheim has two contract accounts: assigned to Mr. Petersheim? Private account: TB010110## Community account: TB010120## Which types of contract does Mr. Petersheim have?
Which devices are assigned to Mr. Petersheim?
1-7
Mr. Petersheim has four utility contracts: Electricity contract: TB010110## Gas contract: TB010180## Water contract: TB010120## Electricity contract: TB010130## Mr. Petersheim has 3 devices: Double rate meter for electricity: TB010110## Water meter: TB010120#### Gas meter: TB010180##
Select the premise and choose Premise Environment. From the tree structure, you can identify the following relationships:
1-8
•
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 has no devices. This is a flat-rate installation that does not measure consumption or energy.
•
Meters are allocated to all the other installations.
You are in the environment for premise TB010110##. To save all the devices to the clipboard, repeat the following procedure for each device:
(©) SAP AG
IUT110
2-65
Click on the device. This selects the line. Choose To Clipboard or F8. You have now added the object to the clipboard. Repeat this step for all devices in the premise. Once you have added all the devices to the clipboard, return to the IC. To check that this has been successful, call the Clipboard tap page in the navigation area. 1-9
On the Environment tab page in 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##
Device category / material number
TD-DRA-00
TD-GA-00
TD-WA-00
Name of device category
IS-U electricity meter
IS-U gas meter
IS-U water meter
Division
01
02
03
Current business partner
TB010110##
TB010110##
TB010110##
Current device location
TB010111DL0## TB010111DL0## TB010111DL0##
1-10 Call the data finder and choose All Search Criteria . The button turns green when advanced selection values have been added
(©) SAP AG
IUT110
.
2-66
Solutions Unit: Interaction Center (IC) Topic: Customer Contact Management
2-1 2-1-1
Call the IC. From the SAP Easy Access menu, choose: Utilities Industry → Customer Service Æ Front-Office/Customer Interaction Center Æ Customer Interaction Center Select your customer. In the Actions box, choose Contact Create (call group Customer). In the Class field, enter the value 0008 Complaint. In the Action field, enter the value 0001 Complaint about employee. Enter a reason for the complaint in the editor and save the contract.
2-1-2
Call the same function again. In the Class field, enter the value 1001 Information. In the Action field, enter the value 1001 General information provided. Enter a text of your choice for the information in the editor. Switch to the Business Objects tab page. To add links, click on the Add Objects button. Choose an object role that references the object type Contract. The system calls the data finder to search for the specific contract. In the contract field, enter TB010110## and choose Find. The electricity contract is included in the link list. Proceed in a similar way to add contract account TB010110## to the list. Save the contact.
(©) SAP AG
IUT110
2-67
2-2 2-2-1
Choose the Documents tab page in the navigation area. Choose Refresh. The system displays a list of all contacts for this customer. By double-clicking on the line, you can display the customer contact. You can configure the system to display customer contacts in the application area on the Customer overview tab page. The following contacts exist: Date
Class
Action
Type
10.03.99
Move-in
New customer moves in
-
16.04.98
Move-in
New customer moves in
-
16.04.98
Move-in
New customer moves in
-
Today’s date
Complaint
Complaint about employee
Today’s date
Info.
General information provided
2-2-2
In the Info group in the Actions box, choose Customer overview. The current customer contacts are listed in the table in the middle of the screen. By double-clicking on the individual contacts, you activate the detail display.
2-2-3
From the SAP Easy Access menu, choose: Utilities Industry Æ Information System Æ Report Selection Æ Customer Service Æ Evaluate Customer Contacts. Enter Contact Class 0008 Complaint as the selection criterion. Choose Execute (F8). All contacts relating to complaints are displayed. Return to the IC.
2-3 2-3-1
False. You can also enter customer contact data manually. The system creates the IC 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 evaluate all customer contacts according to different criteria.
(©) SAP AG
IUT110
2-68
Solutions Unit: Interaction Center (IC) Topic: Master Data in SAP Utilities
3-1 3-1-1
Once you have identified the customer, call the Customer overview in the Information call group. Double-click on the account Private Account 0##. The system takes you to the master data display for the contract account. Switch to the Payments/Taxes tab page. In the Incoming Payments area in the Bank Det. Inc. field you can see the bank details for incoming payments. Return to the customer overview.
3-1-2
Place the cursor in the address field of the business partner. Choose Change (F5). The system takes you to the change master data screen for the business partner. Switch to the Payment Transactions tab page. Enter new bank details. In the ID field, enter GIRO. In the Ctry field, enter US. In the Bank Account field, enter an account number. In the Bank Key field, use the F4 help to select a bank number. Save the changes. You have now allocated new bank details to the business partner. Return to the customer overview.
3-1-3
Position the cursor on Private Account 0##. Choose Change. The system takes you to the change master data screen for the contract account. Switch to the Payment/Taxes tab page. Enter the new bank details for incoming payments. Under Incoming Payments, enter GIRO in the Bank Det. Inc. field. When you double-click on the Bank Det. Inc. field, the system displays the new bank data. Save the changes. You have now defined new bank details for incoming payments and have returned to the customer overview. Return to the IC.
(©) SAP AG
IUT110
2-69
3-2 3-2-1
In the navigation area, select the second contract account. Right-click to call Change Bank Data.
3-2-2
The system takes you to the business partner, to record the new bank details. Switch to the Payment Transactions tab page. Enter new bank details. In the ID field, enter COM. In the Country field, enter US. In the Bank Account field, enter an account number. In the Bank Key field, use the F4 help to select a bank number. Save the changes. You have now entered new bank details for the business partner and have been automatically directed to the selected contract account.
3-2-3
In the contract account, switch to the Payment/Taxes tab page. In the Bank Det. Inc. field, enter COM. When you double-click on the Bank Det. Inc. field, the system displays the new bank data. Save the 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 notes field at the bottom of the screen and save the changes.
3-3 In the navigation area, select the contract and choose Change. In the Text field, enter the name Community contract 0##. Save the changes and return to the IC. 3-4 3-4-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-4-2
False. The contract account settings are such that you can only enter 1 business partner. However, a business partner can have several contract accounts. When you customize the contract account category, however, you can define the contract account so that it can be allocated to several business partners.
3-4-3
True. The contract account is the structure that allows the billing of posting data for contracts or contract items that have the same collection/disbursement agreements. A customer account is managed for a contract account.
(©) SAP AG
IUT110
2-70
3-4-4
False. The contract is an agreement between a business partners and a utility company that applies to a particular division. It contains control data for billing, budget billing plans, and accounts receivable and payable accounting. The rate data is stored in the installation and in the installation structure.
3-5 Enter the contract in the data finder and identify the business partner data. Double-click on the contract TB010130## to display the master data. The following three logs are located under the Extras menu: 1) Creation data 2) Field changes 3) Contract changes 3-6 3-6-1
False. The connection object can also be a piece of land, fountain, or building site.
3-6-2
True.
3-6-3
False. The connection object is at the top of the functional location hierarchy.
3-6-4
True. Device locations are mapped as functional locations in the PM component and the connection object is the superordinate functional location.
3-6-5
False. Devices are installed in device locations and are thus only indirectly allocated to the connection object.
3-6-6
False. The premise is only used in SAP Utilities to group together installations of different divisions.
3-6-7
True. Devices, registers, and fixed payment billing factors assigned to a premise that are to be billed jointly are grouped together for a specific division. A premise can have several installations. These installations can refer to the same or different divisions.
3-6-8
True. The billing class and rate category are allocated to the installation. They have a considerable influence on the billing process.
(©) SAP AG
IUT110
2-71
(©) SAP AG
IUT110
2-72
Move-In/Out
Contents: z The business processes New Contract, End Contract and Move Contract initiated in CRM and Move-In, Move-In/Out and Move-Out in ERP z Effects on both the business and technical master data
¤ SAP AG 2009
(©) SAP AG
IUT110
3-1
Move-In/Out: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe the business processes Move-In, Move-Out, and Move-In/Out z Describe the business processes New Contract, End Contract and Move Contract z Execute the business processes Move-In, Move-Out, and Move-In/Out z Explain the changes to the master data
¤ SAP AG 2009
(©) SAP AG
IUT110
3-2
Move-In: Business Scenario
z A customer calls and requests to initiate service in a location. z You execute the process with the following steps:
Check if the customer is an existing business partner
Search for and identify the premise as well as the start date for the service
Enter and check the personal data
Check the meter reading results
¤ SAP AG 2009
(©) SAP AG
IUT110
3-3
Definition of Move-In
Move-In Business partner
z With a Move-In, a contract is generated for each selected installation at a premise
Contract account
Contract
Installation
¤ SAP AG 2009
You use the Move-In to execute a large number of activities that are required to create the business partner supply. You create business master data or change existing data. In particular, you allocate a contract to an installation.
When you process a move-in, you can make a contract billable. You can also trigger payment requests levied at the start of supply and a welcome letter from the Move-In.
The New Contract creation process in CRM also generates a Move-in in ERP.
(©) SAP AG
IUT110
3-4
Move-In: Prerequisite Technical Master Data
z The following technical master data must be entered before Move-In:
Connection object
Premise
Installation
Connection object
Premise
z A device can be installed before Move-In, but this is not a prerequisite.
Installation
Device ¤ SAP AG 2009
The technical master data is represented in CRM by the IBase and IBase components.
(©) SAP AG
IUT110
3-5
Move-In: Business Master Data
Business partner
Î Should be re-used for existing customers
Contract account
Î Can be re-used for existing customers
Contract
Î Is created during Move-In
¤ SAP AG 2009
Each of these entities can be created during the Move-in process itself.
(©) SAP AG
IUT110
3-6
Move-In: Master Data Business master data
Technical master data
Business partner
Connection object
Contract Contract account
Premise
Contract
Installation
Move-In
Device
¤ SAP AG 2009
Technical and business master data are connected during a Move-In.
(©) SAP AG
IUT110
3-7
Contract Management - Master Data
SAP IS-U
SAP CRM
Business Partner
Business Partner
Contract Account
Bill
Contract
Billing
Installation
Consumption Premise
Business Agreement
Contract Connection Object
PoD & Premise
New
Connection Object
PoD
¤ SAP AG 2009
The New Contract creation process connects technical and business master data in CRM and ERP.
(©) SAP AG
IUT110
3-8
Move-In to SAP Utilities House
Connection Object
Apartment 1 = Premise Contract Contract 1: 1: Electricity Electricity
Contract Contract account account Business ?partner
Contract Contract 2: 2: Gas Gas
Contract Contract 3: 3: Water Water
Service Conn. Water
Utility Utility installation installation 1: 1: Electr. Electr. meter meter Utility Utility installation installation 2: 2: Gas Gas meter meter Utility Utility installation installation 3: 3: Water Water meter meter
Service Connection: Gas
Entrance Hall
Apartment 3
Dev. Dev. location: location: Corridor Corridor
Apartment 2
Dev. Dev. location: location: Basement Basement
Basement
Service Connection Electricity
Supply grid
Street ¤ SAP AG 2009
(©) SAP AG
IUT110
3-9
Move-In: Process
Customer visit/ call
Contract
Validation
Security deposit
Welcome letter
Contrac t
Bank de tails 1 d1 Paym en t m etho 1 Alternat ive payer .... CA doc um ent 1 CA doc um ent 3
Move-In completed
Move-In Customer moves in July
31 BB amount € 250
Business partner, account
Meter reading
Move-in Mrs. Smith
Move-in/out
Budget billing Customer contact plan
¤ SAP AG 2009
Necessary Move-In steps: •
Identify premise
•
Identify or enter customer
•
Select and, if necessary, process contract account or create new contract account
•
Create contracts
Optional Move-In steps: •
Supplement contact data
•
Prepare and carry out move-in meter reading
•
Record results of move-in meter reading
•
Maintain rate data
•
Check whether the billing construct can be billed
•
Maintain creditworthiness manually, or display result of automatic scoring
•
Request cash security deposit
•
Create budget billing plan
•
Create welcome letter
(©) SAP AG
IUT110
3-10
Move-Out: Business Scenario
z A customer reports a Move-Out. z You execute the Move-Out with the following steps:
Identify the customer
Enter the Move-Out date
Maintain the personal data (new address)
Create a meter reading order
¤ SAP AG 2009
(©) SAP AG
IUT110
3-11
Move-Out: Process
Customer reports Contract Final meter Move-Out Move-Out reading results confirmation
X Contrac t Bank de tails 1
1 Paym en t m etho d 1 Alternat ive payer .... FI-CA docum e nt 1 FI-CA doc um ent 3
Move-Out Customer moves-out
Move-Out complete
X July
31
BB amount $250
Contact data
Budget billing plan
Final billing
¤ SAP AG 2009
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 contracts
•
Stop any budget billing collection
•
Suspend any current dunning procedure
•
Change any dunning procedures that may affect open items
•
The Move-out terminates the relationship between the business master data and the technical data, timesliced by the move-out date.
•
The End Contract process initiated in CRM generates a Move-out and terminates the relationship.
(©) SAP AG
IUT110
3-12
Move-In/Out: Business Example
z A new customer reports a Move-In and the MoveOut of the previous customer. z You execute the Move-In/Out with the following steps:
Check if the customer is an existing business partner
Enter the premise and the Move-In/Out date
Enter and check the personal data
Enter the meter-reading results
¤ SAP AG 2009
(©) SAP AG
IUT110
3-13
Move-In/Out: Process
Move-Out Tran s
Move-In
port
¤ SAP AG 2009
(©) SAP AG
IUT110
3-14
Move-In/Out: Processing Options
Parameters
Parameters z
Business partner
z
Premise
z
Move-Out date
z
Move-Out date
z
New premise
z
Business partner or classification of new business partner
z
Move-In date
z
Move-In date
Move-In/Out for business partner
Move-In/Out for premise
Call in interaction center
¤ SAP AG 2009
The following processing options are available for the Move-In/Out transaction: •
Move-In/Out for premise You can process the Move-Out or Move-In of two different business partners in one premise.
•
Move-In/Out for business partner You can process the Move-Out of a business partner from one premise and the Move-In of the same business partner to another premise.
•
The Move Contract process initiated in CRM generates the required Move-out and Move-in
(©) SAP AG
IUT110
3-15
Move-In/Out: No Changes to Installation Data
01.02.2003
Move-in
Customer 1
Customer 2
Move-Out Move-In
Contract 2
Contract 1
Nov. 2nd
Dec. 2nd
Jan. 3rd
Feb. 3rd
Mar. 3rd
Apr. 3rd
May 3rd
Installation
¤ SAP AG 2009
(©) SAP AG
IUT110
3-16
Move-In/Out: Utility Installation History
Installation 10815 01.01.90 - 14.08.1992
Terminated contract 10004711
15.08.92 - 31.03.1993
No contract allocated
01.04.93 - 16.12.1996
Terminated contract 10004713
17.12.96 - 31.12.9999
Current contract 10409543
Display using the installation data environment ¤ SAP AG 2009
(©) SAP AG
IUT110
3-17
Move-In/Out: Summary
You are now able to: z Describe the business processes Move-In, Move-Out, and Move-In/Out z Describe the business processes New Contract, End Contract and Move Contract z Execute the business processes Move-In, Move-Out, and Move-In/Out z Explain the changes to the master data
¤ SAP AG 2009
(©) SAP AG
IUT110
3-18
Exercises – Web Client Unit: Move-In/Out Topic: New Contract Creation After completing these exercises, you will be able to: • Process new contract creation via CRM • Display the generated contract in ECC A customer comes in person to the service center and informs you that she would like utility contracts for an unoccupied apartment. You use the IC to perform the move-in with today’s date as the start date.
1-1
Logon with user IUT110-## to the SAP CRM System TPZ.
1-2
A business partner requests to initiate service at a location 1-2-1
Identify the customer
The customer tells you his name is Tom Snyder He provides his address as 30## Elm Street, New York City Identify the customer in the system.
1-2-2
Confirm the premise to be moved into Mr Snyder needs a contract for the apartment at 30## Park Avenue. Search for and confirm the premise into which Mr Snyder wants to move. The premise should then be copied into the Account Information section of the IC and the technical data copied Enter the number of the connection object here: _____________
(©) SAP AG
IUT110
3-19
1-2-3
Execute the new contract creation In the IC, begin the process using the Contract Management item on the Navigation bar and by choosing New Contracts. The system defaults the current date as the move-in date.
Perform the move-in for all the installations in the premise. Enter ISU_ELE_RESI as the product. Enter a new home phone number to be used: (212) 555-30## Enter a new cash security request for 100 USD. After saving the process, enter the number of the new contract here: ____________________________ 1-2-4
Log into the TNU-770 backend system and inspect the contract which has been created in the previous step. The logon process is described in the Solution of this exercise.
1-2-5
Display the new information for the current business partner in the overview Display the account balance overview. You can find a security deposit request here. Display it and note the document number: ______________________________________________________
(©) SAP AG
IUT110
3-20
Exercises – Web Client Unit: Move-In/Out Topic: Move-Out After completing these exercises, you will be able to: • Process a contract completion in the system • Display the changes in the system A customer telephones and informs you that she is moving out at the end of the month. You perform the move-out in the IC and enter the customer’s new address. You also request a meter reading order. 2-1
Business partner move-out 2-1-1
Identify the customer David Jackson lives in Pinewood Avenue 40##, 10022 New York City. Identify the customer in the system. Once you have done this, the business partner should be available in the IC.
2-1-2
Obtain an overview of the data environment of Mr Jackson. To do this, click on the Overview view from the Navigation bar How many contract accounts does he have? How many utility contracts does he have?
_________________________ _________________________
Complete the following table with the corresponding object keys: Division
Contract
Installation
Are there any outstanding receivables for Mr Jackson’s account? ______________________________________________________
(©) SAP AG
IUT110
3-21
2-1-3
Perform the move-out In the IC, perform the move-out by choosing Contract Management > End Contracts. Verify the contract(s) selected for completion. End date Last day of the current month On the Account & Payment Data view, enter a new phone number for Mr. Jackson. Click on the Submit button to save the process. View the results Click on the End button to end the interaction.
(©) SAP AG
IUT110
3-22
Exercises – Web Client(optional) Chapter 3: Move In/Out – Start of Supply via IC WebClient At the conclusion of this exercise, you will be able to: • Execute standard IC WebClient processes for Utilities • Get familiar with the related configuration A potential customer hears that the retailer, Sunshine Inc., offers good prices for supplying electricity. He would like to start his supply with the supplier Sunshine Inc. The prospect contacts the call center agent. The Agent identifies the caller and enters his service location into the system. Afterwards he starts a Start of Supply process for this new customer. 4-1
Logon with user IUT110-## to the SAP CRM System TPZ or TTZ. Check, whether the new customer is already known in the system. In the Search for Business Partner area enter the following data: Name Last
Kidman##
Name First
Alice
(©) SAP AG
IUT110
3-23
4-2
Create a new Service Location. In the Connection Object area enter the following data: Street City Country Region
Castle Drive ## 69190 Walldorf DE 08
In the Premise area enter the following data: Number of Persons 2 Floor 1 Premise Type Three-room apartment In the Point-Of-Delivery area enter the following data: PoD ID ISU_POD_1## Division Electricity Grid Level Type Voltage Level is preset as soon as you entered Electricity Grid Level Low Voltage Grid Low Voltage Grid SWB 4-3
Start the Start of Supply Process Create a contract for the Point-of-Delivery. Choose Contract Management -> New Contract. Product Start date
ISU_E_SUPPLY_01 The first of the over-next month
Choose Action_ID Start of Supply (NS view). Enter the Market Communication Data. Distributor SP_SWA (= key of Municipal Utility Company) New Service Provider SP_SAG (= key of your Company Sunshine Inc.) Choose Account and Payment Data. Create a new Business Agreement. Choose Summary. 4-4
Display the Contract and Switch Document in Activation.
(©) SAP AG
IUT110
3-24
Solutions – Web Client Unit: Move-In/Out Topic: New Contract Creation
1-2
A business partner requests to initiate service at a location 1-2-1
Identify the customer
The customer tells you his name is Tom Snyder He provides his address as 30## Elm Street, New York City Identify the customer in the system. Once you have done this, you find that the business partner already exists in the system. Account Number ISU11030##
1-2-2
Confirm the premise to be moved into Mr Snyder needs a contract for the apartment at 30## Park Avenue. Search for and confirm the premise into which Mr Snyder wants to move. The premise should then be copied into the Account Information section of the IC and the technical data copied Enter the number of the connection object here: Connection Object # ISU11030##
(©) SAP AG
IUT110
3-25
1-2-3
Execute the new contract creation In the IC, begin the process using the Contract Management item on the Navigation bar and by choosing New Contracts. Perform the move-in for all the installations in the premise. Enter ISU_ELE_RESI as the product. Click on Account and Payment Data to follow the guided procedure. Enter a new home phone number to be used: (212) 555-30## Click on the Security Deposit Amount field to bring up the Security Deposit Requests view. Enter a requested amount of 100 USD and a reason New customer. Click on Summary to follow the guided procedure and finish the transaction. Verify that the transaction is complete and click on the Submit button. After saving the process, you can find the contract number in the contract list.
1-2-4
Log into the TNU-770 backend system and inspect the contract which has been created in the previous step. From the SAPlogon pad, choose system TNU. Enter client number 770. Log into TNU-770 with userid IUT110-## and initial password init. Execute transaction ES22 – Display Contract and enter the contract number from the previous step. Navigate to the 3rd tab to see the product allocation and the other move-in information.
1-2-5
Back in the CRM system, click on the Overview button in the Navigation bar to view the data environment for the customer. Click on the Account Balance button in the Navigation bar to view the account balance overview. Clcik on the hotspot in the Balance Overview view to view the acount balance and the related documents. The document shown is the Cash Security Deposit Request created during the move-in.
(©) SAP AG
IUT110
3-26
Solutions – Web Client Unit: Move-In/Out Topic: Move-Out
2-1
Business partner move-out 2-1-1
Identify the customer David Jackson lives in Elm Street 40##, 10022 New York City. Identify the customer in the system. Once you have done this, the business partner should be available in the IC. Account number ISU11040##
2-1-2
Obtain an overview of the data environment of Mr Jackson. To do this, click on the Overview view from the Navigation bar How many contract accounts does he have? account_________________ How many utility contracts does he have? contract_________________
One ___One
Complete the following table with the corresponding object keys: Division
Contract
Installation
Are there any outstanding receivables for Mr Jackson’s account? _No___________________________________________________
(©) SAP AG
IUT110
3-27
2-1-3
Perform the move-out In the IC, perform the move-out by choosing Contract Management > End Contracts. Verify the contract(s) selected for completion. End date Last day of the current month On the Account & Payment Data view, enter a new phone number for Mr. Jackson. Click on the Submit button to save the process. View the results Click on the End button to end the interaction.
(©) SAP AG
IUT110
3-28
Solution – Web Client (optional) Chapter 3: Move In/Out – Start of Supply via IC WebClient At the conclusion of this exercise, you will be able to: • Execute standard IC WebClient processes for Utilities • Get familiar with the related configuration A potential customer hears that the retailer, Sunshine Inc., offers good prices for supplying electricity. He would like to start his supply with the supplier Sunshine Inc. The prospect contacts the call center agent. The Agent identifies the caller and enters his service location into the system. Afterwards he starts a Start of Supply process for this new customer. 4-1
Logon with user IUT110-## to the SAP CRM System TPZ or TTZ. The logon process is described in the Solution of the optional Exercise in Chapter 2. Check, whether the new customer is already known in the system. In the Search for Business Partner area enter the following data: Name Last Name First
(©) SAP AG
Kidman## Alice
IUT110
3-29
4-2
Create a new Service Location.
In the Connection Object area enter the following data: Street City Country Region
Castle Drive ## 69190 Walldorf DE 08
In the Premise area enter the following data: Number of Persons 2 Floor 1 Premise Type Three-room apartment In the Point-Of-Delivery area enter the following data: PoD ID ISU_POD_1## Division Electricity Grid Level Type Voltage Level is preset as soon as you entered Electricity Grid Level Low Voltage Grid Low Voltage Grid SWB
(©) SAP AG
IUT110
3-30
4-3
Start the Start of Supply Process Create a contract for the Point-of-Delivery. Choose Contract Management -> New Contracts.
Product Start date
ISU_E_SUPPLY_01 The first of the over-next month
Choose Action_ID Start of Supply (NS view). Enter the Market Communication Data. Distributor SP_SWA (= key of Municipal Utility Company) New Service Provider SP_SAG (= key of your Company Sunshine Inc.)
Choose Account and Payment Data:
Create a new Business Agreement:
(©) SAP AG
IUT110
3-31
Choose Summary.
4-4
Display the Contract and Switch Document in Activation.
(©) SAP AG
IUT110
3-32
Exercises - CIC Unit: Move-In/Out Topic: Move-In After completing these exercises, you will be able to: • Process a complete move-in in the system • Display the generated move-in document A customer comes in person to the service center and informs you that she would like utility contracts for an unoccupied apartment. You use the IC 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 customer
The customer tells you her name is Constance Bishop. She is currently living in Massachusetts Avenue 0##, 02116 Boston. Identify the customer in the system. Once you have done this, the business partner should be available in the IC.
1-1-2
Identify the new premise Mrs Bishop needs contracts for the new apartment on East Side Highway 0##. Identify the premise into which Mrs Bishop wants to move. The premise should then appear on the Clipboard tab page. From the Find action, choose Identify Premise. In the data finder, choose the Technical Data tab page and enter the street and house number in the Connection Object area. Choose Find. If a premise is found, this will appear in the navigation area on the Clipboard tab page. Select the entry and display the premise by clicking on the right mouse button and choosing the Display action. Enter the number of the premise here: _____________ Choose Environment -> Data to answer the following question: Which installations for Mrs Bishop's new apartment are in the premise? Enter them in the following table: Installation number
Division
Return to the IC.
(©) SAP AG
IUT110
3-33
1-1-3
Perform the move-in In the IC, perform the move-in from the Move I/O action by choosing M/In: Known Customer. Use the objects that you saved to the Clipboard tab page. Select these two entries on the Clipboard. The system prompts you to maintain the move-in date in an additional step in the IC. Enter today’s date here.
When you are asked, Do you want to adopt an existing contract account?, answer No. Perform the move-in for all the installations in the premise. You are now in the move-in processing screen. Name/Administration tab page In the contact data, record the fact that Mrs Bishop came by in person. Bank Data tab page Since 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 page
Check the payment methods that were entered. Mrs Bishop has agreed that any credit may be transferred to her bank account. Change the outgoing payment method accordingly. Contracts tab page Enter the following values in the new contracts: Switch between the contracts by clicking on the Electricity, Gas, and Water tab pages.
Division
Contract Text
01
East Side Highway 0## – Electricity
02
East Side Highway 0## – Gas
03
East Side Highway 0## – Water
Meter Reading Data tab page
Check whether meter readings already exist If not, estimate them: Select all the registers and choose Estimate. Save the move-in. Return to the IC.
(©) SAP AG
IUT110
3-34
1-1-4
Display the current business partner data. Choose Refresh in the navigation area on the Environment tab page. The system displays the new data you have created. Choose Refresh in the navigation area on the Documents tab page. A new contract exists. Display this by double-clicking on it. Choose the Business Objects tab page. You can find the move-in document here now. Display it and note the document number: ______________________________________________________
1-2
1-1-5
Customer overview
Display the customer overview for Constance Bishop. Note the premise in the bottom part of the screen.
1-1-6
Customer environment
Display the customer environment for Constance Bishop.
True or false? 1-2-1
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 shows the move-in date. ______________________________________________________
1-2-4
When a move-in takes place, a business partner and his/her contract accounts and contracts must already exist in the system. ______________________________________________________
(©) SAP AG
IUT110
3-35
(©) SAP AG
IUT110
3-36
Exercises - CIC Unit: Move-In/Out Topic: Move-Out After completing these exercises, you will be able to: • Process a complete move-out in the system • Display the generated move-out document A customer telephones and informs you that she is moving out at the end of the month. You perform the move-out in the IC and enter the customer’s new address. You also request a meter reading order. 2-1
Business partner move-out 2-1-1
Identify the customer Sarah Peterson lives in Massachusetts Avenue 1##, 02116 Boston. Identify the customer in the system. Once you have done this, the business partner should be available in the IC.
2-1-2
Obtain an overview of the data environment of Mrs Peterson. To do this, choose Customer Environment. How many contract accounts does she have? _________________________ How many utility contracts does she have? _________________________ Complete the following table with the corresponding object keys: Division
Contract
Installation
Are there any outstanding receivables for Mrs Peterson’s account? ______________________________________________________
(©) SAP AG
IUT110
3-37
2-1-3
Perform the move-out In the IC, perform the move-out from the Move I/O action by choosing Move-Out Partner. Use the object that you saved to the Clipboard tab page. Select the business partner Sarah Peterson on the Clipboard. Move-out date Last day of the current month Address Data tab page Enter Mrs Peterson's new address: Independence Avenue 0##, 02116 Boston. MR Data tab page
Create a meter reading order for the meters. Save the move-out. Return to the IC and update your data.
...
(©) SAP AG
IUT110
3-38
Exercises - CIC Unit: Move-In/Out Topic: Move-In/Out After completing 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 the premise Constitution Avenue 0##, 02116 Boston, 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 Determine whether Harry0## Jones is already a customer. Mr Jones does not exist in the system. Create the business partner in the selection area. To do this, choose the Create button and maintain the following data: Field Name
Value
Title
Mr
Category
Person
Gender
Male
Last name
Jones
First name
Harry0##
Street
Constitution Avenue
Number
0##
Postal code
02116
City
Boston
Country
US
Choose Enter. Identify Mr Jones again and then choose Enter twice.
(©) SAP AG
IUT110
3-39
3-1-2
Identify the premise and its environment Identify the premise Constitution Avenue 0##, Boston. From the Info action, choose Connection Object Environment. Find out who was previously registered as a contract partner at that address. Business Partner Number: _____________________________ Name: _____________________________________________ Select the premise and choose Object to Clipboard or F8.
3-1-3
Perform the move-in/out Perform the move-in/out in the IC by starting Premise Move-In/Out. Use the objects stored on the Clipboard to do this, namely the business partner Harry0## Jones and the premise Constitution Avenue 0##,02116 Boston. You are on the initial move-in/out screen. You can check the move-in or move-out date from here, for example. Choose Enter. You are now in move-out processing. Move-out: Address Data tab page Enter Mrs Smith's new address: Apple Tree Lane 0##, 12345 Washington DC. Move-out: MR Data tab page Estimate all the meter readings. Move-out: Save the move-out. You are now in move-in processing. Move-in: Bank Data tab page Mr Jones has account number 08154711## with the Mellon Bank in Boston. Move-in: Payment Data tab page Mr Jones agrees to a direct debit and would like any credit balances to be transferred to this account. Move-in: MR Data tab page Check the meter reading data. Have the meter readings from the move-out been transferred? What is their meter reading type? Move-in: Save the move-in.
(©) SAP AG
IUT110
3-40
3-1-4
Data environment for the premise after the move-in/out Display the premise environment. Which new contracts were created? Division
Contract
Installation
Switch the view from today’s data to a view that comprises the data for a particular period (for example 01/01/1998 to tomorrow). Note that the historical display of the contracts for the premise’s installation
(©) SAP AG
IUT110
3-41
(©) SAP AG
IUT110
3-42
Solutions - CIC Unit: Move-In/Out Topic: Move-In
1-1
Business partner move-in to a premise Utilities Industry → Customer Service → Front-Office/Customer Interaction Center → Customer Interaction Center 1-1-1
Identify the customer Enter the following data in the search criteria: Field Name
Value
Last name
Bishop or Bish*
First name
Constance or Co*
Street
Massachusetts Avenue or M*
House number
0##
Postal code
02100 or initial value
City
Boston or initial value
Choose Enter until the data is displayed in the navigation area. You can now find the identified business partner on the Clipboard tab page. 1-1-2
Identify the new premise. Enter the following data in the search criteria on the Technical Data tab page: Field Name
Value
Street
East Side Highway or Ea*
House number
0##
You can now find the premise you were looking for on the Clipboard tab page. To display the desired premise information: Select the premise on the Clipboard tab page and click the right mouse button to choose Display. In the premise display, choose Environment Æ Data.
(©) SAP AG
IUT110
3-43
The number of the premise is TB060110##. Installation number
Division
TB060110##
Electricity
TB060120##
Water
TB060170##
Gas
Return to the IC. 1-1-3
Perform the move-in The business partner line on the clipboard is selected. Select the premise line on the clipboard too. In the Move I/O action, choose M/in: known customer. Enter today’s date in the Move-in date field. Choose Execute (F8). When you are asked, Do you want to adopt an existing contract account?, answer no. Confirm that you want to execute the move-in for all three installations in the premise. Name/Administration tab page, Contact Data view
The personal visit that Mrs Bishop makes to the customer center is saved as the type of contact. Use the F4 input help top select the value Personal. Payment Data tab page Field Name
Value
Outgoing Payment Methods
B
Outgoing Bank Details
1
Contracts tab page Division Contract Text 01
East Side Highway 0## – Electricity
02
East Side Highway 0## – Gas
03
East Side Highway 0## – Water
Meter Reading Data tab page
Check whether meter readings already exist If not, estimate them. Select all the registers and choose Estimate. Save the move-in.
(©) SAP AG
IUT110
3-44
1-1-4
Display the business partner data. Proceed as described in the exercise.
1-1-5
Customer Overview From the Info action, choose Customer Overview. Return to the IC.
1-1-6
Customer environment From the Info action, choose Customer Environment. Return to the IC.
1-2
True or false? 1-2-1
False. All steps must be performed 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 contract account and contracts created.
(©) SAP AG
IUT110
3-45
(©) SAP AG
IUT110
3-46
Solutions - CIC Unit: Move-In/Out Topic: Move-Out
2-1
Business partner move out Utilities Industry → Customer Service → Front-Office/Customer Interaction Center → Customer Interaction Center 2-1-1
Identify the customer Enter the following data in the search criteria: Field Name
Value
Last name
Peterson or Pe*
First name
Sarah
Street
Massachusetts Avenue
House number
1##
Postal code
02116 or initial value
City
Boston or initial value
Choose Enter until the data is available in the navigation area. You can find the identified business partner on the clipboard now too. 2-1-2
Navigation area: Customer overview and customer environment From the Info action, choose Customer Environment. How many contract accounts does Mrs. Peterson have? No. of contract accounts
Contract account number
1
TB010140##
How many utility contracts does Mrs. Peterson have? Division
Contract
Installation
Electricity
TB010160##
TB010160##
Water
TB010170##
TB010170##
2
Return to the Customer Interaction Center. From the Info action, choose Customer Overview. Are there any outstanding receivables for Mrs. Peterson’s account? Yes.
(©) SAP AG
IUT110
3-47
2-1-3
Perform the move-out The business partner line on the clipboard is selected. From the Move I/O action, choose Move-out partner. Enter the move-out date Name/Administration tab page, Address Data view Field Name
Values
Street
Independence Avenue
House number
0##
Postal code
02116
City
Boston
Meter reading data tab page
Activate the service notif/order indicator. Save the move-out. Return to the IC. Update the Environment and Documents tab pages in the navigation area.
(©) SAP AG
IUT110
3-48
Solutions - CIC Unit: Move-In/Out Topic: Move-In/Out
3-1
Move-in/out of a premise
Utilities Industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center 3-1-1
Identify the new customer Enter the following data in the search criteria: Field Name
Value
Last name
Jones
First name
Harry0##
Search results: Using the specified selections, no object from in the business partner category was found. Create the business partner. Choose Enter until the data for the new business partner you have created appears on the clipboard. 3-1-2
Identify the premise and its environment Proceed as described in the exercise. Business partner
Last name
TB00011001
Ashley Smith
Return to the IC. 3-1-3
Perform a move-in/out for a premise. Select both objects from the clipboard. From the Move I/O action, choose Premise move-in/out. You can correct any data here if necessary. You start processing the move-in/out by choosing Enter.
(©) SAP AG
IUT110
3-49
Move-out: Address data tab page Field Name
Values
Street
Apple Tree Lane
House number
0##
Postal code
12345
City
Washington DC
Move-out: Tab page MR Data Select all registers Choose Estimate. Move-out: Save the move-out document. The system switches to move-in processing. Move-in: Bank Data tab page Field Name
Values
ID
1
Country
US
Bank Key
083000108
Bank Account
08154711##
Move-in: Payment Data tab page Field Name
Values
Incoming Payment Method
D (Direct debit)
Incoming Bank Details
1
Outgoing Payment
Methods
B (Outgoing paym./bank transfer)
Outgoing Bank Details
1
Move-in: MR Data tab page The meter readings are taken from move-out processing. The meter reading type is 04 Derived meter reading. Move-in: Save the move-in document.
(©) SAP AG
IUT110
3-50
3-1-4
Data environment of the premise after the move-in/out In the navigation area refresh the Environment tab page. Use the right mouse button to select the premise and choose Premise environment. New contracts Division
Contract
Installation
Internally assigned contract number TB000110## Internally assigned contract number TB000120## Data environment from 01/01/1998 – to date Choose Period F7 and enter 01.01.1998 in the Valid from field.
(©) SAP AG
IUT110
3-51
(©) SAP AG
IUT110
3-52
Work Management
Contents: z Technical Objects in Work Management z Service Orders and Service Objects z Service Products z Interfaces to External Systems
¤ SAP AG 2009
In a utility company a large number of work orders are accepted, planned, calculated, carried out, and if necessary, billed to a customer. SAP Utilities uses functions that already exist in the various components of the SAP standard system to manage these orders. These functions are merged with specific business processes in Work Management for SAP Utilities, and a large number of industryspecific functions have been added.
(©) SAP AG
IUT110
4-1
Work Management: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe the tasks of Work Management z Describe service order functions z Use service orders in utilities industry processes z Describe how you can offer services as products z List the most important interface of Work Management
¤ SAP AG 2003
(©) SAP AG
IUT110
4-2
Work Management: Business Scenario I z Acquisition, planning, calculation, execution of internal and external work orders z Creation of invoices for customers z Examples:
Creation and expansion of service connections
Energy consulting
Unscheduled meter reading
Disconnection and reconnection
Maintenance
Repairs
Installation, extension or removal of technical equipment
¤ SAP AG 2009
The daily work of a utility company involves the processing of a large number of work orders. The orders must be accepted, planned, calculated, executed, and when necessary, billed to a customer.
In this process, a distinction needs to be made between external work orders relating to the customer services and internal work orders. •
External work orders are mapped using service orders from the Customer Service (CS) component.
•
Internal work orders are mapped using maintenance orders from the Plant Maintenance (PM) component.
(©) SAP AG
IUT110
4-3
Work Management: Business Scenario II Utilities industry services in which Work Management is deployed: Typical services for private / commercial customers in the areas of ...... . .
Generation
Transmission
• Energy distribution
Plant maintenance Management of power plants
Distribution
Grid services
• Installation • Electricity supply • Meter reading
¤ SAP AG 2009
(©) SAP AG
IUT110
4-4
Work Management: Technical Objects
z Technical Objects in Work Management z Service orders and service objects z Service products z Interfaces to external systems
¤ SAP AG 2003
(©) SAP AG
IUT110
4-5
Technical Objects: Overview
Description:
Description:
Technical objects in transmission and distribution
Technical objects with a direct reference to customers
Example: z
Transformer substation
z
Transmission lines
Example: Plant Maintenance PM/CS
Customer Service SAP Utiliti es
z
Connection object
z
Premise
z
Device location
z
Transformer stations
z
Power transformers
z
Devices
z
Switching stations
z
Technical installation
Technical objects in supply area
¤ SAP AG 2009
(©) SAP AG
IUT110
4-6
Technical Objects: PM Supply Grid Pylons (equip.) Distribution station ST 435 (funct. loc.) Field 01 Line no. 186 (funct. loc.)
Distribution station ST 571
Field 02
Field 03
Field 01 Line no. 187 (funct. loc.)
Field 02
Field 03 Line no. 188
Transformer fields Line no. 189
Field 01
Object connection used to connect two systems with different hierarchies Line network with subsections
Field 02
Field 03 Distribution station with transformer fields Distribution station ST 768 ¤ SAP AG 2009
(©) SAP AG
IUT110
4-7
Technical Objects: SAP Utilities Connection Object
Conn. object func. loc.) Premise Technical installations (equipment)
Premise
Transformer (equipment)
Connection (equipment)
Device location (func. loc.)
07161927
07161927 0716192
0539802
0539802 0
125.256.01
125.256.01
Devices (equipment)
¤ SAP AG 2009
In addition to the technical master data previously shown in unit 2, this figure also shows the connection and the technical installation (of both pieces of equipment).
The connection is used to show the link between the supply grid and the connection object. In the "service connection" workflow template provided by SAP, the connection is created in one of the last steps and installed in the functional location, the SAP Utilities connection object.
The connection is dependent on the division.
The technical installation is not absolutely necessary in the SAP Utilities data model. It can be regarded as a supplement to the technical master data. It is used to map technical installations without having a direct influence on billing. Examples are large lighting systems, gardens, and so on.
The technical installation is dependent on the division.
A maximum of one technical installation can be created for each division in a premise. A piece of equipment is created in PM automatically.
The SAP Utilities "inspections" process enables you to maintain technical installations regularly.
(©) SAP AG
IUT110
4-8
Work Management: Service Orders and Objects
z Technical Objects in Work Management z Service orders and service objects z Service products z Interfaces to external systems
¤ SAP AG 2003
(©) SAP AG
IUT110
4-9
Services Premise
Home installation services Damage repairs Home installation checks (inspections) Device services (installation, removal, replacement)
me te re rea d r n r: 33 24 in ing : __ 4556611 _ __ __
Maintenance of appliances Aperiodic meter reading
OFF ON
Disconnection/reconnection Other on-site services ¤ SAP AG 2009
The reference points of the services are • Connection object • Device location • Device • Technical installation
The creation of service orders is integrated in the SAP Utilities processes. This includes, for example, • Aperiodic meter readings • Disconnection and reconnection • Device replacement • Inspections
(©) SAP AG
IUT110
4-10
Work Order Structure
Order Header
For example: Order type, dates, plant, reference object, priority, description
Equipment (assembly) Functional locations Maintenance notifications
Object list
Operations
For example: Work center, control key,description, standard time, activity type, wages
Material list
For example: Material, quantities, units of measure, Storage location, batch, item category, availability
Production resources
For example: Protective clothing, crane, traffic lights, fire extinguishers, signs, excavator
Billing rule Costs (planned/actual) ¤ SAP AG 2009
Header data is information used to identify and manage maintenance 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. You can enter a single object as a reference object in the order header and enter several objects in the object list.
Operations are used to describe the work to be carried out according to the order (the operation includes, for example, the work center, the time required and the control key).
Materials are spare parts that are needed and consumed to execute the order.
Production resources (for example, tools, protective clothing, and special heavy goods vehicles) are also needed to execute the order, but are not actually consumed in the order.
The data in the billing rule states who is usually responsible for the costs. The data is taken as proposals from the master record of the reference object. It can, however, be changed during the first stages 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.
(©) SAP AG
IUT110
4-11
Work Order Process Flow
Entry/notification Planning Release Printing Execution Confirmation Technical completion Billing document
For service orders only
Billing Business completion ¤ SAP AG 2009
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 operations, reserving spare parts, or determining working hours.
The order is then transferred to scheduling and control. Availability is checked, required capacity is provided, and the necessary shop papers are printed.
Execution includes obtaining spare parts from 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.
(©) SAP AG
IUT110
4-12
Creating a Work Order Using the Service Object
Functional location equipment
Description of work to be done, resources for work, material... external resources Technical object
Instruct ions
Service object
Maint./service order
Config.
Characteristics Values Dependencies ¤ SAP AG 2009
The service object is used to create maintenance and service orders in a standardized and effective way.
(©) SAP AG
IUT110
4-13
Work Order Example: Service Object Repair
Customer complains about defective device
Agent selects service object in IC
Service order with task list, resources, and materials, are sent to the responsible technician ¤ SAP AG 2009
In the IC, you can trigger the generation of a repair order by first selecting the relevant customer and then starting the process.
Select the corresponding technical object from the displayed customer overview screen.
The repair order is created automatically.
(©) SAP AG
IUT110
4-14
Work Order with Appointment Scheduling in the IC Agree date Work center Planning horizon: Standard Required capacity: 60 minutes Time
2.12.2010
3.12.2010
4.12.2010
5.12.2010
X
8:00 - 9:00
80 / 120
60 / 120
120 / 120
9:00 - 10:00
60 / 120
0 / 120
0 / 120
60 / 120
10:00 - 11:00
80 / 120
60 / 120
80 / 120
0 / 120
11:00 - 12:00
120 / 120
60 / 120
0 / 120
0 / 120
13:00 - 14:00
0 / 120
60 / 120
80 / 120
0 / 120
X
120 / 120
X
¤ SAP AG 2009
In the IC you can trigger the generation of a repair order with appointment scheduling by first selecting the relevant customer and then starting the "Repair Order with Date" process.
(©) SAP AG
IUT110
4-15
Work Management: Service Products
z Technical Objects in Work Management z Service orders and service objects z Service products z Interfaces to external systems
¤ SAP AG 2003
(©) SAP AG
IUT110
4-16
Service Product Concept
Connection object device….
Description of work to be done, resources for work, material... external resources
Technical object Instructions Service product
Customer order
Service order
Service material Config.
Characteristics Values Dependencies
Sales view price information ¤ SAP AG 2009
SAP Utilities uses the customer order from the Sales and Distribution component (SD) and the service order from Customer Service (CS) to process customer-related business transactions. These documents are connected by way of a service product. The service product is a service that is sold in SD and rendered in CS.
The system includes the task list and the technical object in the service order. You can use the configuration to define and analyze the task list individually. You can also use it to influence the price of the service product.
(©) SAP AG
IUT110
4-17
Service Product Example: Service Connection Service product
Service material
Task list 1. Dig trench Time: 0.5h per m Tool: Excavator
Configuration Cable per m
60.00
Trench per m
150.00
Connection box" Type A 1,200.00 Type B 1,500.00 BB amount for internal services 300.00
Characteristics Values
2. Secure excavation only if soil is loose
Ground:
Light
Length:
10m
3. Lay cable Material: X m cable
Connection type: A Internal servicesYes
4. Install connection box Time: 1h Material: Connection box 5. Fill trench Time: 0.2h per m
Quotation, customer order
Service object
Service order
¤ SAP AG 2009
(©) SAP AG
IUT110
4-18
Processing Installation Services
Customer Doc. 1
3
4
SAP Utilities
FI-CA
10 UTILI TY BI LL P. O . #:
Custom er
Premise
Q t y Shi pped
To tal
Pr i ce
Des cription
Wo r k f l o w M a n a g e m e n t
SD Request
Q t yO r der ed
DAT E
2
SALE SPE RSO N
5
Quotation
Order
Billing request
6
8
Invoice:
9
Installation services
a rn te Al t iv
PM/CS
Tot al Subt ot al Sal es Tax
SAP Utilities
e
7
Work order
Invoice: Installation & utility services
¤ SAP AG 2009
A service connection could be processed as follows: (0)
A customer requests a quotation for the installation of a service connection. The agent responsible identifies the customer or creates a corresponding customer master record.
(1)
The agent creates a customer quotation based on a service product in the Sales and Distribution component (SD).
(2)
A quotation is created and sent to the customer. A service order can be generated automatically in the background in the CS component (6).
(3)
The customer accepts the quotation.
(4)
The agent generates a sales order. The order items can be transferred automatically from the quotation.
(5)
A service order is created automatically in the background (if this was not done in step 3)
(6)
The service connection is created on-site.
(7)
If the service is invoiced according to consumption (that is, the actual costs incurred), a billing request is created in the SD component.
(8)
In the SD component, the invoice is triggered and posted. If the service is not invoiced according to consumption, but on a flat rate, the invoicing procedure is based on the sales order. As an alternative to invoicing in SD, it is also possible to create the invoice for the service in SAP Utilities and clear it with consumption billing.
(9)
The invoiced amount is then entered as a debit amount in the FI-CA component.
(©) SAP AG
IUT110
4-19
Work Management: Interfaces to External Systems
z Technical objects in Work Management z Service orders and service objects z Service products z Interfaces to external systems
¤ SAP AG 2003
(©) SAP AG
IUT110
4-20
Overview of Interfaces
ERP Standard
MDI Service orders Confirmations
SAP Work GBC Manag. Utilities
Service orders Confirmations
Mobile Devices Resource Planning
Applications Outage notifications and orders Monitoring of the situation
SCADA
Geographical data
AM/FM GIS
Transformer station outages
Outages Confirmations
Outage Analysis
Connection information
¤ SAP AG 2009
GBC: GIS Business Connector
GIS: Geographical Information System
AM/FM: Asset Management / Facility Management
MDI: Mobile Data Interface
SCADA: Supervisory Control and Data Acquisition
(©) SAP AG
IUT110
4-21
GIS Interface and Integration with the GBC
GBC Or PI
SAP
GIS
Object identification Transformer station
Transformer
Connection object
Connection
Connectivity "info
Object identification Connectivity "info Device location
Device
¤ SAP AG 2009
The GIS Business Connector enables business processes to run seamlessly between an SAP system and a GIS. The GBC can •
call GIS functions and data from the SAP System
•
call SAP system functions and data from the GIS
In addition to this, the GBC can manage the object keys of both systems, thus ensuring data consistency.
No programming is required to set up the GBC.
In this example, the information on the connections between the transformer and the GIS is stored in the GIS. You can call this information from the SAP system.
You can also map the integration of SAP and GIS using XI (Exchange Infrastructure).
(©) SAP AG
IUT110
4-22
Work Management: Summary
z Service objects simplify and standardize the processing of service orders. z Service products enable you to offer and sell services as products. z The service connection workflow is supplied with SAP Utilities. It contains quotation processing, order processing and invoicing. z Work Management contains interfaces to various external systems.
¤ SAP AG 2009
(©) SAP AG
IUT110
4-23
(©) SAP AG
IUT110
4-24
Exercises Unit: Work Management Topic: Service Orders After completing these exercises, you will be able to: • Perform the front office process Create service order.
You familiarize yourself with service orders and service objects.
1-1
Create a service order using the CIC. 1-1-1
Business partner Elmer Petersheim, in Massachusetts Avenue 0##, 02116 Boston, reports a device malfunction. Identify the business partner. Create a service order as a repair order. In the navigation area on the Environment tab page, select the dual rate meter and click on the right mouse button to call the Create repair order process.
1-1-2
Which order number has been assigned by the system? ______________________________________________________
1-1-3
Which work center has been determined? Which operations are transferred to the service order? ______________________________________________________
1-1-4
From where are the work center and operations transferred? ______________________________________________________ ______________________________________________________ ______________________________________________________
(©) SAP AG
IUT110
4-25
(©) SAP AG
IUT110
4-26
Solutions Unit: Work Management Topic: Service Orders
1-1
Create a service order. Utilities Industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center 1-1-1
You use the search function to determine the business partner by entering the data and confirming this with Enter. By choosing Enter a second time, the customer data will be stored on the Environment tab page. Expand the structure of Elmer Petersheim’s private account as far as the dual rate meter and select this. Click on the right mouse button to start the Create repair order process. The service order is created in the background. Save the customer contact. The contacts and service orders are displayed in the navigation area on the Documents tab page after you have chosen Refresh. You can display the document by selecting it and choosing Display (right mouse click). 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 on the Business Objects tab page (in each case, select the service order and click on the right mouse button to display it).
1-1-3
Display the service order. The work center is in the service order header. You can find the operations on the Operations tab page.
1-1-4
When you call the process you select a service object. The work center is stored in this service object. The operations are in the task list. The task list is also stored in the service object.
(©) SAP AG
IUT110
4-27
(©) SAP AG
IUT110
4-28
Device Technology
Contents: z Device Category
Device category data
Integration in the standard SAP system
z Device and Register
Device data
Register data
Integration in the standard SAP system
z Device History z Device Inspection
Sample lot
Certification
¤ SAP AG 2009
(©) SAP AG
IUT110
5-1
Device Technology: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe the tasks of the device category z Process device-related activities z Explain device inspection z Explain how the device category and the device are integrated in the standard SAP system
¤ SAP AG 2009
(©) SAP AG
IUT110
5-2
Device Technology: Business Scenario
z Technical mapping of complex devices and installation structures (such as integrated water meters, instrument panels) z Organization of billing-related data (such as rental prices, meter readings) z Recording of comprehensive device history as the basis for meter reading, billing, maintenance, and inspection z Device stocks managed on quantity and value basis z Integration in Materials Management and Asset Management
¤ SAP AG 2009
(©) SAP AG
IUT110
5-3
Device Technology: Device Category
z Device Category z Device and Register z Device History z Device Inspection
¤ SAP AG 2009
(©) SAP AG
IUT110
5-4
Device Category, Basic Device Category and Device
Basic device cat.
=> Basic functions of device categories, such as:
Meter Transformer Pressure regulator and so on Device cat. 1
=> Features of similar devices
Definition of technical device data Recording of inspection and certification periods The device category corresponds to the material in the Materials Management component (MM)
Device cat. 2
Device 1
=> Specific device data
Device 2 Device 3
¤ SAP AG 2009
Device number/serial number Operation data, such as installation, removal or meter reading Certification and maintenance data A device corresponds to a piece of equipment in the Plant Maintenance component (PM)
Examples of basic device categories: •
Meters measure consumption
•
Transformers convert electrical voltage, for example
•
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 determine the thermal quantity output with district heating
•
Correctors calculate standard cubic meters from gas values
•
Pressure regulators adjust gas pressure, for example
•
Sensors act as pulse generators, for example, temperature sensors
(©) SAP AG
IUT110
5-5
Integration with Logistics
SAP Utilities Device Management
Logistics
Device Category
Material
Device
Equipment
¤ SAP AG 2009
SAP Utilities functions of device management include: •
Technical data such as the register group, the input/output group, 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 execution of meter readings of registers in the service territory
•
Device inspection: Sampling procedure, certification, and periodic replacement
Integration of SAP Utilities Device Management with the standard ERP Logistics component makes it possible to use the following: •
Inventory Management (component MM-IM)
•
Purchasing (MM-PUR component)
•
Warehouse Management (the components MM-IM and MM-WM)
•
Plant Maintenance (the component PM)
•
Class system
(©) SAP AG
IUT110
5-6
Definition of Device Category
Device category
The device category groups together devices with the same features (data). Device categories are managed as materials with a material number in the Materials Management application component.
¤ SAP AG 2009
(©) SAP AG
IUT110
5-7
Device Category Data
General
Basic Data
• Construction class • Function class • Price class • Device catgy description
• Material description • Valuation, price
Certification
Logistics • Storage • Warehouse management • Transport data
Device Category
• Certification requirement • Certification periods
Planning
Other Data
• Procurement planning • Calculation • Forecast
• Register group • Winding group • Input/output group
depending on basic device category
MM Data
Data Specific to SAP Utilities
¤ SAP AG 2008
(©) SAP AG
IUT110
5-8
Device Category Elements
Function-related Informative
Material MM
Device Category SAP Utilities
Register Group
Input/Output Group
Winding Group ¤ SAP AG 2009
Certain functional group elements are required, depending on the basic device category. Examples: •
Devices belonging to the basic device category METERS must be allocated to a register group. However, an input/output group may be allocated for technical descriptions of the available device interfaces, if required.
•
The allocation of a winding group, in which the billing data is recorded, is mandatory for devices belonging to the TRANSFORMERS basic device category. An input/output group can also be maintained for information purposes (for example, for service technicians), if required.
Data concerning register groups can be arranged according to division category (the reactive current/active current indicator can only be maintained in the register group of the electricity division).
(©) SAP AG
IUT110
5-9
Device Technology: Device and Register
z Device Category z Device and Register z Device History z Device Inspection
¤ SAP AG 2009
(©) SAP AG
IUT110
5-10
Definition of Devices
Device category
Device
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 equipment numbers.
¤ SAP AG 2009
(©) SAP AG
IUT110
5-11
Device Data
Header Data General • Inventory number • Weight/volume • Reference data • Manufacturer data • Stock information
• Material no., serial no. • Equipment type and no. • Status
General • Device cat., basic cat. • Lock status • Change documents • Time slices
Operations Operations
• Installation and removal • Modification and disconn. • Certification • Meter reading
Device
• Maintenance plan orders • Service orders • Notifications • Capacity planning
Category-Specific Data
Plant Maintenance
• Group data, construct. yr • Manufacturer, cat. desc. • Owner status • Certification data
• Maintenance plant • Maint. planning plant • Maint. planner group • Resp. work center
PM
SAP Utilities
¤ SAP AG 2009
The device master record is divided into various areas: •
General data: Technical data, reference data, manufacturer data
•
Serialization data: Internal equipment number, plant, storage location, posting documents
•
SAP Utilities data: - Technical data: Register group, winding group, command group (depending on the basic device category) - Certification data / inspection data: Certification year and status, lot, replacement year, sample device status - Operation data: Installation, removal, modification, disconnection - Master data: Business partner, connection object, device location, location, premise, installations - Meter reading results
When devices are moved (goods receipt, installation), the equipment status is updated (ESTO, AVLB, INST). The device status informs the user that a particular business process has been performed. For example, ESTO means that the device was entered in the system using a goods receipt posting and is available in a warehouse.
(©) SAP AG
IUT110
5-12
Definition of a Register
Device category Device
Register
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
¤ SAP AG 2006
(©) SAP AG
IUT110
5-13
Register Data
General • Register category • Register type (time zone) • Pre-decimal places • Decimal places
Register configuration
• Recorded meter reading • Estimated meter reading • Multiple allocation
Technical • Unit of measurement • Register code, such as reactive or active energy • Display type
Meter readings
Meter reading
Register
• Reason • Type, meter reader • Date • Status
Meter reading
Register relationships
• Number of meter reading results per meter reading • Indicator: non-metering register
• Register relationship type • Relationship register • Operation code
Technical data
Sample register relationship
Process data
¤ SAP AG 2006
Examples of register relationships: •
Active/reactive relationship
•
Serial switching relationship
•
On-peak/off-peak relationship
•
Control relationship
•
Volume correction factor relationship (thermal gas billing)
•
Volume correction factor calculation (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".
(©) SAP AG
IUT110
5-14
Device Technology: Device History
z Device Category z Device and Register z Device History z Device Inspection
¤ SAP AG 2009
(©) SAP AG
IUT110
5-15
Device History
MM
PM
Purchase Requisition
Purchase Order Goods Receipt
Stock Transfer
Retirement
SAP Utilities
Inspection Certification Reprogramming
Device Management - Installation
Goods Issue
Installation
Removal/ Replacement
¤ SAP AG 2009
Devices are created in an integrated system using the Purchasing (MM-PUR), Inventory Management (MM-IM) and Plant Maintenance (PM) components. •
Devices are created as serialized 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, purchase order, and so on).
•
A prerequisite is that the device category has already been created and therefore exists as a material. The serial number profile in the material master ensures that the devices to be created are supplied with the necessary SAP Utilities data.
If the Materials Management (MM) component is not used, you can also create devices directly in SAP Utilities. The inventory management function is not supported here, however.
Although device installation is performed within SAP Utilities, it is based on enhanced functions of the Plant Maintenance component (PM).
(©) SAP AG
IUT110
5-16
Device History Documentation
z SAP UT UT
z z z z
MM
z z z z
PM
z z z
CS
z z
Device specification: Device category, device Installation: Installation, removal, replacement, installation structure Meter reading: Organization, meter reading order, meter reading result entry Inspection and certification: Periodic or sampling procedure Purchasing: Purchase orders, inquiry/quotation, outline agreement Warehouse logistics: Transport, inventory, transfer posting Inventory management: Goods movement, reservation Valuation, inventory, planning Maintenance: Technical objects and equipment Work planning, maintenance planning Maintenance processing Service contracts: Contracts, maintenance plans Service processing: Notification, order, confirmation Service planning: Terminate, task lists
¤ SAP AG 2009
(©) SAP AG
IUT110
5-17
Device Technology: Device Inspection
z Device Category z Device and Register z Device History z Device Inspection
¤ SAP AG 2009
(©) SAP AG
IUT110
5-18
Definition of Certification Procedure
z With external certification, a device is 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. z With internal certification, the utility company voluntarily inspects 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. z In the certification procedure, you can either inspect all devices or a sample of devices.
¤ SAP AG 2009
(©) SAP AG
IUT110
5-19
Certification Procedure
Description:
Description:
Only a representative sample of all devices is removed for inspection and replaced.
Devices due for certification are removed completely and replaced by identical devices.
Procedure: z
Create lot
z
Compile lot
z
Determine lot devices
z
Perform first drawing
z
Replacement orders are created automatically
z
Check
Procedure:
Sample
Periodic replacement
SAP UT
z
Create periodic replacement list
z
Select the device categories
z
Create list in dialog or batch
z
Replacement orders are created automatically
Certification of Devices
¤ SAP AG 2009
(©) SAP AG
IUT110
5-20
Sampling procedure
z 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.
z Goals:
Official lots: Renewal of the calibration validity of the lot devices if the sample devices are certified.
Internal lots: Quality control
¤ SAP AG 2003
(©) SAP AG
IUT110
5-21
Inspection Using the Sampling Procedure
Create Create lot lot
Compile Compile lot lot
Determine Determine lot lot devices devices
Perform Perform 1st 1st drawing drawing
Perform Perform 1st 1st drawing drawing
Inspect Inspect sample sample devices devices
No
?
Break Break up up lot lot
Transfer Transfer devices devices to to periodic periodic file file
?
Inspection passed
Yes
Certify Certify sample sample devices devices
Renew Renew lot lot
¤ SAP AG 2003
The flow chart displays the typical sample lot procedure. Some steps may be carried out differently depending on the configuration of the Customizing tables (for example, a second drawing is normally not possible).
If necessary, you can use the standard R/3 component quality management (PM-QM) to organize and manage the test data. This component contains comprehensive functions for organizing test rules, test transactions and test results.
(©) SAP AG
IUT110
5-22
Periodic Replacement
l ova Rem
z In periodic replacement, devices that are to be certified are removed, and replaced by the same kind of devices. Installation
z Devices that are to be replaced are managed in the periodic replacement list. z Devices that are to be replaced on a certain date are selected from the periodic replacement list. z A work order is then created for the devices that are to be replaced.
¤ SAP AG 2003
The periodic replacement component is optional. It is needed if: •
Devices are to be certified individually
•
A lot does not exist for the sampling procedure, and the devices have to be certified individually
(©) SAP AG
IUT110
5-23
Device Technology: Unit Summary
z The device category divides devices into functional groups and specifies their features. The device category corresponds to the material in MM. z 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. z Integration in the PM and MM application components allows you to completely process all service and logistics functions. z Devices are certified and inspected for internal and external purposes by means of periodic replacement and sampling procedures.
¤ SAP AG 2003
(©) SAP AG
IUT110
5-24
Exercises Unit: Device Management Technology Topic: Creating and Delivering Devices At the conclusion of this exercise, you will be able to: • Distinguish between devices, device categories, and basic device categories • Provide information on device technology • Explain the 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? ______________________________________________________ ______________________________________________________
(©) SAP AG
IUT110
5-25
1-2
Display all devices for customer TB010110## and select the double rate meter for electricity. 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
How long is the calibration validity? How long is the internal certification period? _____________________________________________________ ______________________________________________________
1-3
Specify the connection data for the 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. ______________________________________________________ ______________________________________________________
(©) SAP AG
IUT110
5-26
1-4
Display the material master record for the device TB01011##. The device category/material is allocated to plant U001.
1-5
True or false? 1-5-1
Device technology is integrated into the R/3 Logistics component. ______________________________________________________
1-5-2
The device is based directly on a basic device category. ______________________________________________________
1-5-3
The device category groups together similar devices. ______________________________________________________
1-5-4
The device category is managed in the MM component. ______________________________________________________
1-5-5
The register group is only 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
The device can be allocated to one or more lots. ______________________________________________________
1-5-8
The device can be checked both internally and externally only according to the sampling procedure. ______________________________________________________
(©) SAP AG
IUT110
5-27
(©) SAP AG
IUT110
5-28
Solutions Unit: Device Management Technology Topic: Creating and Delivering Devices
1-1 1-1-1
Select the customer in the CIC. Select the node for the Water contract and click to expand the subnode. Double-click on the node for Water meter, device TB010120##. The device category is displayed on the IS Data tab page. Do not exit this screen.
1-1-2
The MR Results button lists all the meter reading results. The F1 help provides information for the individual columns. The F4 help displays the meaning of the individual keys. Return to the device display.
1-1-3
You are located in the device display for TB010120##. On the Group Data tab page, double-click on the Register Group field. The system displays the master data for the register group. Here you can see the number of registers as well as their technical specifications Click on the back arrow to return to theCIC
(©) SAP AG
IUT110
5-29
1-2 1-2-1
Select the node for the Electric Contract and click to expand the subnodes. Switch to the IS Data tab page. On the bottom of the tab page, switch to Certification/Periodic Replacement. The Next repl. year field displays the year in which the device must next be certified, either internally or externally. Do not exit this screen.
1-2-2
In the IS Data view, choose the Ins. Data tab page. If there is an entry in the Lot field, this means the device is allocated to a lot. No entry means it has not yet been allocated to a lot. Do not exit this screen.
1-2-3
In the IS Data view, choose the Ins. Data tab page. If the Sample Device Status field is empty, the device was not drawn as a sample. Possible status of sample devices:
1-2-4
(©) SAP AG
-
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
The calibration validity is stored in the device category. You can display its master data by double-clicking on the Device Category field. Switch to the Certification/Order Data tab page. The calibration validity is displayed in years. It is used to calculate the next year of replacement. The internal certification period is displayed in the Int. cert. per. field. This shows the internal period set by the company, after which a device must be reinspected and certified.
IUT110
5-30
1-3
In the IS Data view, choose the Master Data tab page. 1-3-1
The current connection object is TB010110##.
1-3-2
The current device location is TB010111DL0##.
1-3-3
From the menu, choose Structure Æ Structure Graphic. Answer the question Expand structure upwards? with Yes. You can expand the structure further using the Levels above button. The current connection object is TB010110##.
1-4 •
Determine the device category for the device TB010110##.
•
Open a new session. From the SAP Easy Access menu, choose: Logistics Materials Management Material Master Material Display Display Current
•
Enter the key for the material/device category.
•
Select all views and confirm the entry.
•
Since materials are always defined for a specific plant, you must also specify the plant U001.
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 with the material number.
1-5-5
False. Although the register group is allocated to the device category, it is not only used for information purposes, but also has functional tasks when processing and checking meter reading results.
(©) SAP AG
•
Validation of the number of figures
•
Meter overflow
•
Conversion of results depending on the transformation ratio
IUT110
5-31
1-5-6
True. The device is managed in PM using the equipment number.
1-5-7
False. Devices can only be allocated to one lot.
1-5-8
False. In addition to the sampling procedure, the periodic replacement procedure can also be used.
(©) SAP AG
IUT110
5-32
Device Installation
Contents: z Installation / removal / replacement
Technical installation / removal / replacement
Billing-related installation / removal
z Installation structure z Rate data
Device allocations
Register relationships
¤ SAP AG 2009
(©) SAP AG
IUT110
6-1
Device Installation: Unit Objectives
At the conclusion of this unit, you will be able to: z 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. z 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. z Display devices of an installation and describe the installation structure.
¤ SAP AG 2003
(©) SAP AG
IUT110
6-2
Device Installation: Business Scenario
z Device installation if replaced periodically
Create and plan service orders
Execute service orders: Remove old devices and install new ones (device replacement)
¤ SAP AG 2003
(©) SAP AG
IUT110
6-3
Device Installation: Installation / Removal / Replacement
z Installation / removal / replacement z Installation structure
¤ SAP AG 2009
(©) SAP AG
IUT110
6-4
Business Scenario: Replacing Sample Devices Planning Planning the the work work orders orders
Creation Creation of of work work orders orders to replace to replace the the relevant relevant devices devices Sample Sample devices devices in in aa lot lot must must be be replaced replaced for for certification certification
Team leader of field sales force Agent Device inspection
Technical Technical closing closing of of the the service service order order and and triggering triggering of of the the invoice invoice
Field sales force employee
Agent Device inspection
Changes Changes to to data data in in the the system system ("full device ("full device replacement") replacement")
Team leader of field sales force
On-site On-site technical technical execution execution of of the the order order and and confirmation confirmation of of completing completing the the order order in in the the system system
¤ SAP AG 2006
Devices of a particular device category are due for certification. After the sample devices have been determined 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.
Once 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.
(©) SAP AG
IUT110
6-5
Service Order: Determine Device Location
Execute service order
Determine device location
z The device location describes where a device is installed in the connection object. z The address of the connection object links the device location to the regional structure. z The location can be specified in more detail using location data, location details, and a long text. The service order is used to forward this information together with the address data to the field employee. z The device location is a functional location in the PM application component. z The structure of the functional locations and the equipment (devices) installed provides a comprehensive overview of the technical systems installed. ¤ SAP AG 2009
(©) SAP AG
IUT110
6-6
Definition of the Device Location
Execute service order
Determine device location
Connection object Device location Device The device location is the location in the connection object that is independent of a division and in which any number of devices can technically be installed. ¤ SAP AG 2003
(©) SAP AG
IUT110
6-7
Device Location Data
Execute service order
Determine device location
Independent of division
Reference to premise
• Installation location for devices of all divisions • Installation location for all device categories
• The device location can be allocated to a premise if required
Device location
Location data
Integration with PM
• Exact location and location supplement • Long text • Link to regional structure
• The device location is defined as a functional location below the connection object
¤ SAP AG 2003
(©) SAP AG
IUT110
6-8
Placement of the Device Location in the PM Structure Execute service order
Determine device location
Equipment
Connection Higher-level
Connection Object
Functional Location Equipment
Device
Device Lower-level
Device Location
Functional Location
SAP Utilities Objects
PM Objects
Legend Installation of equipment
Hierarchical relationship between functional locations
¤ SAP AG 2009
(©) SAP AG
IUT110
6-9
Service Order: Device Replacement and Confirmation Execute service order
Determine device location
Replace device
Confirm service order
Service order executed
z The field employee performs an on-site meter reading for the sample device and then physically removes the device.
Me te Re a r n o: 3 ddin g :: 2 45 6 1 ____ __ _ _
z 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 have the same technical features. z A function test is performed and new meter readings are taken as a basis for billing. z This concludes the technical aspect of the service order and the field employee enters the corresponding confirmation in the system.
¤ SAP AG 2009
(©) SAP AG
IUT110
6-10
Data Changes: Installation Location Execute service order
Change System system
Determine device location
Device device carry out
Service order order
Service order executed
Locate installation
z 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. z 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
¤ SAP AG 2003
(©) SAP AG
IUT110
6-11
Data Changes: Device Replacement Execute service order
Change System
Determine device location
Locate installation
Execute device replacement
Execute device replacement
Service order
Service order executed
Data change completed
z 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. z Once the data has been saved, the device replacement is complete.
¤ SAP AG 2003
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 clearing 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.
(©) SAP AG
IUT110
6-12
Technical and Billing-Related Installation
Business Business partner partner
Contract Contract 11 (Company (Company code code 1) 1) Fresh Fresh water water
Installation Installation 11
Contract Contract 22
Contract Contract account account
(Company (Company code code 2) 2) Waste Waste water water
Installation Installation 22
Premise Premise
Billing-related installation
Device 1
Billing-related installation
Technical installation
Device Device location location
Connection Connection object object
¤ SAP AG 2003
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).
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.
(©) SAP AG
IUT110
6-13
Device Installation: Installation Structure
z Installation / removal / replacement z Installation structure
¤ SAP AG 2009
(©) SAP AG
IUT110
6-14
Installation Structure: Example
Serial switching
Electricity
Audio frequency ripple control receiver
Supply grid
Street
Device allocation Register relationship ¤ SAP AG 2009
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 audio frequency ripple control receiver. For information purposes, this is mapped in the system as an ARCR type device allocation. At the same time, one of the registers of the doublerate 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.
(©) SAP AG
IUT110
6-15
Technical Structure of Installation z Device allocations
z Register relationships
Audio frequency ripple control receiver
Reactive/active relationship
Transformer
Pressure regulator
Serial switching relationship
Customer-specific allocations
On-peak/off-peak relationship
Control relationship
VCF relationship
Relationship for calculating volume correction factor
Customer-specific relationships
¤ SAP AG 2009
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 included in consumption billing, is defined at register level for the "transformer" allocation type).
Register relationships: •
In a reactive/active relationship, all active registers and all reactive registers of the same register category are added together, and the total is used to carry out the cosine phi examination.
•
The serial switching relationship determines consumption and is relevant for billing.
•
The on-peak/off-peak relationship describes the relationship between registers with different register types (for example, on-peak and off-peak registers).
•
In a control relationship, all registers are added and the totals compared with the designated control register.
•
You need the VCF relationship (gas division only) for billing difference quantities resulting from different meter readings for the operating volume meter of the corrector and an additional external operating volume meter.
•
You need the VCF calculation relationship (gas division only) for billing difference quantities resulting from different meter readings for the operating cubic meter meter of the corrector and an additional external operating cubic meter meter.
(©) SAP AG
IUT110
6-16
Billing-Related Installation Structure z Rate Data
z Extrapolation data
Relevance to rental price
Expected period consumption
Relevance to billing
Price class
Rate type
Fixed consumption values for linear weighting (absolute / relative)
Rate fact group
Discount
¤ SAP AG 2009
You determine the rate and extrapolation data when you maintain the device installation. These can be changed at any time later from "Installation Structure" in the menu. •
The Relevance to rental price indicator determines whether a rental price is charged.
•
The Relevance to billing indicator at register level determines that a plausible meter reading result is expected for billing.
•
The price class is maintained at device category, device, or register level. Together with the price level, it determines the rental price from the rate.
•
The rate type is maintained at device or register level. Together with the rate category for the installation, it controls rate determination.
•
The rate fact group is also maintained at device or register level. It contains specific values (for example, constants) and/or keys (for example, price keys).
•
The discount for quantities and services is maintained at register level (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).
(©) SAP AG
IUT110
6-17
Device Installation: Summary
z The precise location of the devices is found using device location in SAP Utilities. The device location is a functional location in the PM component. z Devices can be installed or removed in two separate steps that are distinguished in terms of technical and billing factors. Devices can also be installed or removed in one step for both billing and technical data. z 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. ¤ SAP AG 2008
(©) SAP AG
IUT110
6-18
Exercises Unit: Device Management Installation Topic: Installation and Removal of Devices After completing these exercises, you will be able to: • Display all the devices in an installation • Install and remove devices • Explain integration with the PM component A customer’s water meter is faulty and must be replaced. To replace the 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. A customer’s water meter is faulty and must be replaced. To replace the 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
The water meter TB010120## for customer TB010110## was faulty. A field employee replaced the faulty device with a new device that has the same technical features. As the responsible office-based employee, you first perform a full removal of the old device and then a full installation of the new device in the system. Note: This operation can be processed quickly in one step using the device replacement transaction. In this transaction, the system carries out the full removal and installation automatically 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, using the CIC, determine the device location and installation to which the device is assigned.
1-1-2
Call Device Management in one session. Remove the device TB010120## in one step with today's date. Enter an appropriate removal reason and estimate the meter readings.
1-1-3
Then install the new meter TB010200## in one step. Choose today's date as the installation date. Enter a meter reading at installation of 97.8 m³ for the register.
(©) SAP AG
IUT110
6-19
Assign a rate type, fact group, and period consumption to the register. Enter an appropriate installation reason. 1-1-4
1-2
Finally, use the data environment display for the customer in the IC to check the device replacement in the utility installation.
Check the following features of the device you have just installed. 1-2-1
Installation date and installation reason: ______________________________________________________
1-2-2
Meter reading at installation: ______________________________________________________
1-2-3
The current business partner: ______________________________________________________
1-2-4
The 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
True or false? 1-4-1
During technical installation, the device is allocated to a device location and an installation. You cannot maintain rate data. On the other hand, you can create, search for, and change device locations. ______________________________________________________
1-4-2
Only devices from the same division can be installed in a device location. ______________________________________________________
1-4-3
You always have to maintain billing-relevant rate data when installing a device. ______________________________________________________
1-4-4
The device location is managed as a functional location in PM. ______________________________________________________
1-4-5
The device location is the highest level in the functional location hierarchy in PM. ______________________________________________________
1-4-6
The installation and removal of devices automatically generates a time slice for the device. ______________________________________________________
1-4-7
A device can be installed into several installations. ______________________________________________________
(©) SAP AG
IUT110
6-20
2
(Optional) Create a device allocation between the ARCR 508010## and the double rate meter 5040##. Use the installation TB010110## and the device location TB010111DL0##. Use the following values for the double rate meter: Installation date: Recorded meter reading: Period consumption: Rate type: Fact groups: A rental price is to be paid.
Today's date Register 1: 0 Register 1: 2000 Register 1: on-peak Residential customers
and register 2: 0 and register 2: 1000 and register 2: off-peak
Tip: First install the ARCR, then the double rate meter.
(©) SAP AG
IUT110
6-21
(©) SAP AG
IUT110
6-22
Solutions Unit: Device Management Installation Topic: Installation and Removal of Devices
1-1G 1-1-1
Find the customer TB010110## in the IC. Choose the water meter TB010120## by double-clicking on it and in the device, choose the Master Data tab page.
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: Installation: Old Device:
1-1-3
TB010111DL0## TB010120## TB010120##
Choose the following for device installation: Device Installation Æ Installation Æ Full Device Location: Installation: New Device: Rate Type: Fact Group: Period Consumption:
1-1-4
TB010111DL0## TB010120## TB010200## 3001 0001 Residential customer 100
In the IC, call the data for business partner TB010110##. Choose the action box Info Æ Customer Environment. Choose the installation TB010120## by double-clicking on it. Use the Device History button to branch to the historical display of the installation and the devices allocated to it.
(©) SAP AG
IUT110
6-23
1-2 1-2-1
Choose Device Management from the SAP Easy Access menu: Utilities Industry Æ Device Management Choose: Technology Æ Device Æ Display Enter TB010200## in the Serial Number field. Confirm the entry with Enter. The system displays the device master data. You can see the time slice overview by choosing the Display Time Slice Overview button. To check the installation date, choose IS Data Æ Act./Codes
1-3
1-2-2
Using the MR Results button you can call a list of the previous meter readings.
1-2-3
Choose the IS Data Æ Master Data tab page.
1-2-4
In the work area towards the top of the screen, choose the General tab page. The producer of the device is listed in the Manufacturer field.
1-2-5
Choose the Organization tab page. You can see the allocation to a plant maintenance planning plant here.
Choose Device Management from the SAP Easy Access menu: Utilities Industry Æ Device Management Choose: Technology Æ Device Æ Display Choose the following menu items to call the structure graphic: Structure Æ Structure Graphic The entire structure graphic is displayed.
(©) SAP AG
IUT110
6-24
1-4
2
True or false? 1-4-1
False. You cannot create device locations during installation.
1-4-2
False. The device location is a device installation location in the connection object that is not dependent on a division. The device location can be assigned to a premise, if desired.
1-4-3
False. The rate data relevant to billing is not required during technical installation. It can be added during billing-related installation or full installation.
1-4-4
True.
1-4-5
False. The connection object represents the level above the device location in the hierarchy.
1-4-6
True.
1-4-7
True.
Create device allocation: Call transaction EG31 full installation. In device location TB010111DL0## and installation TB010110##, install the ARCR 508010## with today's date. Save the device installation. Call the transaction EG31 full installation again. In device location TB010111DL0## and installation TB010110##, install the double rate meter 5040## with today's date. The system then automatically proposes the TRE you installed previously. Now maintain the data relevant for billing: Recorded meter reading: Period consumption: Rate type: Fact groups:
Register 1: 0 and register 2: 0 Register 1: 2000 and register 2: 1000 Register 1: on-peak and register 2: off-peak Residential customers
Activate the Pay rental price function for the on-peak register. Save the device installation.
(©) SAP AG
IUT110
6-25
(©) SAP AG
IUT110
6-26
Meter Reading
Contents: z Meter Reading Organization
Scheduling
Street Route
z Meter Reading Process
Meter Reading Order
Meter Reading Result
Monitoring
z Special Meter Reading Functions
Meter Reading by Customers via the Internet
Reversal
¤ SAP AG 2009
(©) SAP AG
IUT110
7-1
Meter Reading: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe the meter reading procedure
Scheduling and street route
Meter reading processing
z Enter meter reading results by means of:
Automatic and manual payment run
Single and mass entry
Single and mass estimation
Meter reading correction
¤ SAP AG 2003
(©) SAP AG
IUT110
7-2
Meter Reading: Business Scenario
z 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
z Meter reading processing
Creation of meter reading order
Enter or estimate meter reading results
z Start of billing and invoicing
Final billing, followed by invoicing
¤ SAP AG 2003
(©) SAP AG
IUT110
7-3
Meter Reading: Organization
z Meter Reading Organization
Scheduling
Street route
z Meter Reading Process
Meter reading order
Meter reading result
Monitoring
z Special Meter Reading Functions
Meter reading by customers via the Internet
Reversal
¤ SAP AG 2009
(©) SAP AG
IUT110
7-4
Types of Meter Reading Indicator z
Predefined meter reading strategy
z
Date and area scheduled in regional structure
z
Indicator z
There are special reasons for the meter reading request, such as a move-in/out
z
Date and area cannot be scheduled
z
Meter reading cannot be planned
Resources can be planned
Process z
Create meter reading schedule
z
Specify meter reading sequence
z
Process z
Create a single meter reading order
Create mass meter reading orders
z z
Enter consumption Check results
z
Enter results
z
Release for billing
z
Check results
z
Release for billing
Scheduled
Unscheduled
Meter reading ¤ SAP AG 2003
(©) SAP AG
IUT110
7-5
Scheduling and Regional Structure Master Data
Regional Structure
Scheduling
Business partner
Account
Postal "Regional Structure City
Street
Contract
Portion
Installation
MR unit
Street section
Premise Political structure Connection object ¤ SAP AG 2009
Scheduling is managed in the meter reading unit and portion objects.
Scheduling: • Control meter reading • Control periodic billing • Control budget billing collection
Portion: 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 unit entered in the installation in the contract.
Meter reading unit: A meter reading unit groups together installations (and the devices and registers installed in them) according to regional criteria for meter reading purposes.
(©) SAP AG
IUT110
7-6
Scheduling Tasks
Portion 1 Portion 2
MR unit 1
z Grouping of contracts
For joint billing
with same control for budget billing amounts
Budget billing cycle
Budget billing scheduling
z Grouping of utility installations
MR unit 2 MR unit 3
For joint billing
of specific billing classes and divisions
Control of special features of meter reading
MDE download
Intervals
¤ SAP AG 2009
(©) SAP AG
IUT110
7-7
Scheduling: Portion and Meter Reading Unit Examples
Portion A
Portion B
MR unit A.1 MR unit A.2
MR unit B.1
A
MR unit B.2
MR unit A.3
MR unit B.3
B
MR unit B.4 MR unit B.5
Portion C MR unit C.1 MR unit C.2
MR unit C.3
¤ SAP AG 2009
A portion normally contains several meter reading units that are structured according to regional and/or scheduling requirements.
The 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 methods.
Example: • Portions A and B represent different city districts consisting almost entirely of households and small businesses (such as residential customers). The 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 methods apply to commercial and industrial customers, major customers (industrial and business customers) 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 like islands "within" 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. • Commercial and industrial customers are billed monthly. This means that portion C is billed on June 15, July 15, and so on.
(©) SAP AG
IUT110
7-8
Scheduling: Generation of Schedule Records
Schedule Master Records
Schedule Records MR unit A_AUG01 2006
MR unit A_AUG01
Portion P_AUG01
A_AUG01 2007 etc.
Generation of schedule records Portion
P_AUG01 2006
Parameter record P1
P_AUG01 2007 etc.
¤ SAP AG 2009
Schedule records are generated from the entries in the parameter record and schedule master records (portion and meter reading unit).
Schedule records refer to specific dates. They control meter reading and billing.
Schedule records must be generated for portions and meter reading units before meter reading orders can be generated.
(©) SAP AG
IUT110
7-9
Scheduling: Annual Billing
27.7.
End billing period
Scheduled billing date
Portion A 28.7.
29.7.
30.7.
31.7.
1.8.
2.8.
3.8.
Meter reading period for meter reading unit 1
End End of of meter meter reading reading period period
Billing period Scheduled meter reading date
Meter reading period for meter reading unit 2 for all meter reading units Meter reading period for meter reading unit 3
2007 2007
2006 2006 Portion A 27.7. 28.7. 29.7. 30.7. 31.7.
1.8.
2.8.
Portion A 27.7. 28.7. 29.7. 30.7. 31.7.
3.8.
1.8.
2.8.
3.8.
Meter reading
Meter reading
Billing Billing
Billing
¤ SAP AG 2006
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.
(©) SAP AG
IUT110
7-10
Scheduling: Monthly Billing
27.
End of billing period
Target billing date
Portion 1 28.
29.
30.
31.
1.
2.
3.
Meter reading period for meter reading unit 1
End of meter reading period
Billing period
Meter reading period for MR unit 2
Target reading date
for meter reading units
Meter reading period for meter reading unit 2
August
July Portion 1 27. 28.
29.
30.
31.
1.
2.
Portion 1 27. 28.
3.
29.
30.
31.
1.
2.
3.
Meter reading
Meter reading
Billing
Billing
¤ SAP AG 2009
To generate schedule records for the above, the following settings are required: • Portion: - End of billing period:
August 3
- Target billing date:
August 1
- Period length:
1 month
• Meter reading units: - End of meter reading period*:
July 31
* When the meter reading unit is created, the end of the meter reading period is automatically adjusted to correspond to the end of the billing period.
(©) SAP AG
IUT110
7-11
Street Route
MR unit A
District 1 Street 1
Str ee tR ou te
Street 2
Connection object 1
Street n
Connection object 2
Device loc. 1
Connection object n
Device loc. 2
Device 1
Device loc. n
Device 2
District 2
District n
254.1247.02
Device n
¤ SAP AG 2009
You can use this component to determine the sequence in which devices in a service territory are read. This enables you plan the optimum route for the meter reader.
You make specifications in a meter reading unit according to the following criteria: • City • Street • House number (connection object) • Device location • Device
You can maintain the street route for a single meter reading unit or create a combined street route for several meter reading units. The prerequisite for a combined street route for several meter reading units is the joint allocation of different meter reading units in the corresponding scheduling master records.
The enhancement EDMLSORT (sorting of meter reading orders for printout and download) can be used for the street route.
(©) SAP AG
IUT110
7-12
Meter Reading: Process
z Meter Reading Organization
Scheduling
Street route
z Meter Reading Process
Meter reading order
Meter reading result
Monitoring
z Special Meter Reading Functions
Meter reading by customers via the Internet
Reversal
¤ SAP AG 2009
(©) SAP AG
IUT110
7-13
Planned Meter Reading Procedure Date for meter reading reached
Create meter reading orders
Output meter reading orders
Manual meter reading due
MDE reading due
Print meter reading orders
Download meter reading data
Perform meter reading
Perform meter reading
Enter meter reading results
Upload meter reading results
MR results determined Check meter reading results ¤ SAP AG 2009
(©) SAP AG
IUT110
7-14
Meter Reading Order Creation z Meter Reading Order
Individual order
Mass order
Date for meter reading reached
Create meter reading orders
Output meter reading orders
Manual meter reading due
MDE reading due
Print meter reading orders
Download meter reading data
Perform meter reading
Perform meter reading
Selection using From meter reading unit and Enter meter reading To meter reading unit results
Upload meter reading results
Schedule task in task management
z Individual Order Data
Selection using the meter reading unit, contract, installation, and device
Additional dates for billing control
z Mass Order Data
z Specification of Meter Reading Reason
MR results determined Check meter reading results
¤ SAP AG 2009
You can influence order creation using three control IDs: • Include meter reading category schedule record - If you select this field, the planned meter reading category for the schedule record has priority. This enables you to prepare meter readings by customers, providing the schedule record allows this. • Meter reading interval check - If you select this field, the system checks whether a meter reading order or meter reading result already exists in the meter reading interval. If it does, the system suppresses the meter reading order with the lower reading reason priority. - Deselecting this field speeds up meter reading order creation. The order is always created, even if you have defined meter reading reason priorities for interval checks in Customizing. • Ignore contracts - If you select this field and then create billing-relevant meter reading orders again, contracts that have already had meter reading orders created for them are not analyzed or checked again by the system to see if they are complete. This speeds up the process of recreating meter reading orders. • Suppress service orders / notifications - If you select this field, the system suppresses the creation of service orders that are automatically created as a result of Customizing settings.
(©) SAP AG
IUT110
7-15
Meter Reading Order Output Output media
• Cover page MDE • MR documents
Date for meter reading reached
• MR announcement • Card for meter reading" by customer
Meter reading information (selection)
Expected reading with area
Any number of previous meter reading results
Street route
Notes for the meter reader (dynamic / static)
Create meter reading orders
Output meter reading orders
Manual meter reading due
MDE reading due
Print meter reading orders
Download meter reading data
Perform meter reading
Perform meter reading
Enter meter reading results
Upload meter reading results
MR results determined Check meter reading results
¤ SAP AG 2009
(©) SAP AG
IUT110
7-16
Meter Reading Result Entry z Automatic
Upload interface
Automatic estimation
Date for meter reading reached
z Manual
Create meter reading orders
Output meter reading orders
Manual meter reading due
MDE reading due
Print meter reading orders
Download meter reading data
Perform meter reading
Perform meter reading
Enter meter reading results
Upload meter reading results
Fast entry
Fast entry without correction Fast entry with correction
Single entry
Result correction
Plausible results Implausible results
z Meter reading by customer
Via the Internet
Via WAP telephone
MR results determined Check meter reading results
¤ SAP AG 2009
(©) SAP AG
IUT110
7-17
Meter Reading Result Data z Reference to meter reading order with fast entry
Entry number
Check digit
Date for meter reading reached
Create meter reading orders
z MR data
Recorded meter reading
Date and time of meter reading
Note from meter reader
Meter reading type (for example, by utility company, by customer, estimation)
Meter reader number
Date and time of maximum meter reading
z Functions
Correction and release of meter reading result
Estimation of meter reading result
Output meter reading orders
Manual meter reading due
MDE reading due
Print meter reading orders
Download meter reading data
Perform meter reading
Perform meter reading
Enter meter reading results
Upload meter reading results
MR results determined Check meter reading results
¤ SAP AG 2009
(©) SAP AG
IUT110
7-18
Meter Reading Result Check: Overview z Entry of meter reading results
Manual
Automatic
Date for meter reading reached
z Types of validation
Fixed checks
Independent checks
Dependent checks
z Correction
Correction and release of meter reading result
Estimation of meter reading result
Correction aids
Create meter reading orders
Output meter reading orders
Manual meter reading due
MDE reading due
Print meter reading orders
Download meter reading data
Perform meter reading
Perform meter reading
Enter meter reading results
Upload meter reading results
MR results determined Check meter reading results
¤ SAP AG 2009
(©) SAP AG
IUT110
7-19
Process of Checking Meter Reading Results
Result Implausible Correction Aids Device: 4711000 Meter reading: 78133
Result Plausible Independent Checks For example z Consumption from previous period z Demand from previous periods z Demand compared with agreed max.
Dependent Checks For example Cosine phi for energy/demand z Usage hours z Control meters z
z
Checks can be configured for individual customers and customer groups
z
Permitted deviations between measured values and target values can be configured using tables
z
Tracking/monitoring of implausible results
¤ SAP AG 2009
(©) SAP AG
IUT110
7-20
Monitoring
z Selection of meter reading orders using the following data objects:
Contract
Installation
Device
Portion
Meter reading unit
Business partner
z Display (single or all):
Billing order
Meter reading order
Meter reading result
¤ SAP AG 2009
(©) SAP AG
IUT110
7-21
Meter Reading: Special Functions
z Meter Reading Organization
Scheduling
Street route
z Meter Reading Process
Meter reading order
Meter reading result
Monitoring
z Special Meter Reading Functions
Meter reading by customers via the Internet
Reversal
¤ SAP AG 2009
(©) SAP AG
IUT110
7-22
Meter Reading by Customers over the Internet
l ai m E
Meter Meter reading reading request request Utilities Utilities Customer Customer E-services E-services
SAP SAP UT UT
Customer Customer Meter ? reading
Entry Entry of of meter meter data data Internet Internet customer customer
Internet Internet
Energy Energy supplier supplier
¤ SAP AG 2008
(©) SAP AG
IUT110
7-23
Meter Reading by Customer over WAP Telephone
er gs sf i n an ad Tr r re e et
m
AP W
SAP SAP UT UT
SAP SAP BCM BCM
Customer Customer Meter ? reading
Internet Internet customer customer
Wireless Wireless Application Application Protocol Protocol
Energy Energy supplier supplier
¤ SAP AG 2008
SAP Business Communication Management
(©) SAP AG
IUT110
7-24
Meter Reading Reversal
Incorrect mass selection Reverse meter reading order Incorrect individual selection
Correct selection
Start meter reading order creation again
Meter reading order deleted
New meter" reading order
¤ SAP AG 2009
When a meter reading is reversed, all objects that were generated by the meter reading order creation and meter reading result entry are deleted: • Meter reading orders • Meter reading results (optional) • Billing orders
A reversal is necessary, for example, if you realize that the specifications from scheduling were incorrect after periodic meter reading orders have been created for a meter reading unit, or if you entered the wrong device when creating a control meter reading order.
On the initial screen, you can specify whether the meter reading results • are to be deleted: - this means that new meter reading orders are created for all devices when you recreate a meter reading order. • are not to be deleted: - this means that when you recreate a meter reading order, meter reading orders are only created for devices that have not been read. If a device has already been read, the corresponding meter reading results are included.
(©) SAP AG
IUT110
7-25
Meter Reading: Unit Summary
z Scheduled meter readings are controlled via meter reading
units z 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 over the Internet
z 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
z Configurable validations reduce the potential for error ¤ SAP AG 2003
(©) SAP AG
IUT110
7-26
Exercises Unit: Meter Reading Topic: Meter Reading for Individual Customers After completing 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 periodic meter reading, the company does not read the meters at all installations itself. For some customers, reading the meters themselves is an efficient use of resources. The customer reports the meter readings either in writing or by phone. An agent records the meter readings made by customers and enters them manually in the system. 1-1
Which meter reading units are contained in the portion T-A-00 (annual) or (T-C-00 (monthly)?
1-2
To which objects can the portion be directly or indirectly allocated?
1-3
Your business partner TB090110## would like interim contract billing. You use the IC to read the meters for all the allocated devices.
1-4
True or false? 1-4-1
The meter reading order controls the meter reading, billing, and invoicing processes.
1-4-2
The meter reading order can be output by printer or IDOC.
1-4-3
Meter reading results can be entered manually or automatically and are then 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.
(©) SAP AG
IUT110
7-27
(©) SAP AG
IUT110
7-28
Solutions Unit: Meter Reading Topic: Meter Reading for Individual Customers
1-1
Go to the SAP Easy Access menu and choose: Utilities Industry Æ Scheduling Æ Schedule Master Record Æ Portion Æ Display
1-2
1-1-1
Enter the portion T-A-00 (annual) or T-C-00 (monthly)..
1-1-2
Choose Enter.
1-1-3
The planned billing date is stored in the Sched Billing Date field. This is valid for all meter reading units allocated to this portion.
1-1-4
You can view the list of the allocated meter reading units by choosing the Where-Used List.
1-1-5
By expanding the Portion in MR units subdirectory, you can view all the meter reading units that belong to this portion.
The following relationships can exist: 1-2-1
The portion is entered directly in the meter reading unit
1-2-2
The portion is entered as an alternative portion directly in the contract
1-2-3
The portion is indirectly referenced via the meter reading unit in the installation
(©) SAP AG
IUT110
7-29
1-3
To enter meter readings, proceed as follows: 1-3-1
Call the IC, and from here, the data for your business partner TB090110##. Keep choosing Enter until the data is displayed in the navigation area. Perform the following steps for each utility contract.
1-3-2
To enter the meter readings for each contract, proceed as follows: • Click once on a utility contract to select it. • Choose Enter customer meter reading. • Confirm the defaults for:
-
Meter reading reason
02 Interim reading with billing
-
Meter reading type
02 Meter reading by customer
• Choose Continue (F8) or the button. • Enter the meter readings - even implausible values (very low/very high).
1-3-3
To correct meter readings, proceed as follows: • Select a register line. • Choose Correct. • You can see the expected value on the Forecast Data tab page in the Meter
Reading Data and Consumption Data fields. • The reading can be corrected in the Current MR field. • To release the meter reading, choose Release.
1-3-4
You return to meter reading entry: • Save the meter readings. • Complete the customer contact and save it.
1-3-5
You return to the IC.
1-3-6
Repeat the steps for the other utility contracts.
1-4-1
False. The meter reading order is an organizational aid for preparing 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 that are always checked, such as implausible previous meter reading results, 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 and then carried out automatically.
1-4
(©) SAP AG
IUT110
7-30
Billing Master Data
Contents: z Introduction
Billing master data
Billing process
z Rate Structure
Rate type and rate category
Rates, operands, and schemas
Prices
z Rate Determination z Rate Allocation
¤ SAP AG 2009
(©) SAP AG
IUT110
8-1
Billing Master Data: Unit Objectives
At the conclusion of this unit, you will be able to: z Explain the function of rate master data:
Billing class
Operands and operand values
Rate type and rate category
Prices
z Explain the concept of the rate structure:
Components of the rate
Flow definition of the variant programs in the schema
Rate determination
z Describe rate allocation
¤ SAP AG 2009
(©) SAP AG
IUT110
8-2
Billing Master Data: Business Scenario
z Sales and marketing requirements
Description of new products and market segments
z Energy industry
Specification, checking and release of new contracts
z Customizing of billing master data
Creation of rate category and rate type
Definition of rates, prices, and discounts
Maintenance of agreed special conditions
¤ SAP AG 2009
(©) SAP AG
IUT110
8-3
Billing Master Data: Introduction
z Billing master data enables you to specify contract billing rules for both residential and commercial and industrial customers and provides the basis for a complete mapping of all rates. z The extremely flexible and universal structuring of rates allows you to implement new and creative sales and marketing concepts. z An open architecture allows you to adapt and succeed in a changing environment.
¤ SAP AG 2009
(©) SAP AG
IUT110
8-4
Billing Process: Introduction z Billing of contracts for residential as well as commercial and industrial customers z 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 z Open to new billing procedures z Third party billing and cross-company code billing z Special features: Examples include thermal gas billing, billing for external generators and installations without a meter
¤ SAP AG 2009
(©) SAP AG
IUT110
8-5
Rate Structure Data relating to customer and installation
Rate data Prices and rate facts
Contract
Installation
Ra ca te te go ry
Rate
Rate 1 Rate determination pe
Inst. Inst. structure structure ty e Rate Rate cat. cat. facts/ facts/ at R Installation Installation facts facts
Data entry and analysis
Procedure data
Quantity conversion and proration
Rate n
Execution of variant programs according to schema
Schema 1 Var.pr. Values
Rate 1 - Step 1 VarProg. A - Step 2 VarProg. B . . Rate 2
x1 x2 .
- Step 1 VarProg. A - Step 2 VarProg. C - Step 3 VarProg. D . . . . . . . .
x3 x4 x5 . . . .
Rate n - Step 1 VarProg. A
Validation of billing results
E X E C U T I O N
xxx
Generation of billing line items
¤ SAP AG 2009
(©) SAP AG
IUT110
8-6
Rate Determination
Rate Type
Allocates A particular rate category and rate type for a particular period to a rate.
Rate Category
Household rate Water, ... ....
3.50 1 m3 Water . . 4.00 Mon thly rent . ....
¤ SAP AG 2009
The rate is determined dynamically 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.
(©) SAP AG
IUT110
8-7
Billing Class: 1 z Classifies installations within a division, for example residential/C&I contract z Can be valid for multiple rate categories z Used for validation in scheduling and in the billing master data z Enables several franchise fee groups to be defined z Can be used as a statistical criterion z If you change the billing class, you must also change the rate category. You do not have to perform a final billing
¤ SAP AG 2006
The billing class classifies installations for billing.
The billing class is also used for the following purposes: y 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. y As a statistical criterion, for example in the sales statistics.
(©) SAP AG
IUT110
8-8
Rate Category I z Valid for one division only z Belongs to a single billing class z Contains one valid billing schema z Controls billing - used to determine the rate in conjunction with the rate type z Determines which outsorting checks occur during billing z Controls accompanying backbilling and period-end billing for nonresidential customers z Controls advance billing and dynamic period control
¤ SAP AG 2006
The rate category classifies the installation for billing. The rate category is used in conjunction with the rate types to determine the rate.
Rate determination: rate type + rate category = rate
(©) SAP AG
IUT110
8-9
Rate Category II
Division Billing Scheme
Dynamic Period Control
Billing Class
Rate Category
Outsorting Group
Billing in Advance
Backbilling Period-End Billing
Notes
¤ SAP AG 2006
The rate category contains data that controls the processing of billing data. This includes: y Billing Scheme y Control of period-end billing and accompanying backbilling y 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).
(©) SAP AG
IUT110
8-10
Definition of Rate Type z Used to classify
Registers
Devices
Flat-rates
Reference values
for billing z Examples: On-peak and off-peak rates for active energy; On-peak rate for reactive energy; On-peak rate for active power; gas and water consumption; flat-rate installations z The rate type is used in conjunction with the rate category to determine the rate
¤ SAP AG 2006
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.
You can also allocate the rate type to the following objects: y 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 clearing price. y Facts - Used to determine rates that cannot be derived from registers. - Also used to determines rates for flat rate installations without installed devices. y Reference Values - Used to model street lights, for example
(©) SAP AG
IUT110
8-11
Rate z Billing rule for a device, register, or reference value z The sum of all the steps relevant to billing that are performed during the billing process z These steps are represented by one or more variant programs, the sequence of which is specified in the billing schema. z The rate can be permissible for either
the register
the device
the reference value (facts)
z Rate steps affect account determination and the creation of billing line items.
¤ SAP AG 2009
Rates specify: • How measured consumption values are extrapolated or divided up during meter reading data processing and prorations • Which billing-related values are measured by a register • Which reference values are billed (for example, for flat-rate services) • In which calculation formulas the measured values or reference values are used • Which prices are used • Which constants, factors, and influencing factors are included in the calculation • To which general ledger accounts the calculation results (bill line items) are posted • How the bill line items are treated statistically • The division and billing classes to which the rate is allocated
(©) SAP AG
IUT110
8-12
Example: Billing Rule for Electricity Variant Variant pool pool
*
QUANTITY FACTOR QUANTITY FACTOR Calculates Calculates x% x% of of aa quantity quantity
QUANTITY QUANTITY
Variant Variant pool pool
.. .. .. ACT_KWH ACT_KWH
.. .. .. NUMBER DEMAND NUMBER OF OF DEMAND DEMAND PEAKS PEAKS DEMAND Calculates Calculates N N peak peak averages averages DEMAND PRICE BILLING DEMAND PRICE BILLING LINE LINE ITEMS ITEMS Valuates Valuates demand demand with with aa price price
*
0.5 *0.5 REACT_KWH ACT_50% REACT_KWH - ACT_50% BILL_REACT BILL_REACT USD USD 0.06 * 0.06
ACT_50% ACT_50% BILL_REACT BILL_REACT BILLING BILLING LINE LINE ITEMS ITEMS
.. .. .. QUANTITY QUANTITY
-
QUANTITY QUANTITY
QUANTITY QUANTITY
Difference Difference of of two two quantities quantities
.. .. ..
Contract Contract text: text:
.. .. .. QTY PRICE QTY PRICE Valuates energy Valuates energy with with aa price price
*
BILLING BILLING LINE LINE ITEMS ITEMS
The The reactive reactive energy energy that that exceeds exceeds 50% 50% of of the the active active energy energy is is valuated valuated using using aa separate separate price. price.
¤ SAP AG 2003
(©) SAP AG
IUT110
8-13
Rate Structure
Rate
Rate step
Fact group
Elementary calculation and processing step
Grouping of individual facts allocated to a rate
¤ SAP AG 2003
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%.
(©) SAP AG
IUT110
8-14
Rate Data
Billing class
Permissibility
Division
Register operand
Rate
Validation class
Usage type Minimum time portion required for extrapolation
¤ SAP AG 2003
(©) SAP AG
IUT110
8-15
Data for the Rate Step
Variant program Debit and credit billing subtransactions
Debit and credit budget billing sub-transactions
Fine-tuned control of variants (additional parameters)
Rate step
Indicator for optional billing step
Franchise fee group
Statistical rate Input operand(s) and output operand(s)
¤ SAP AG 2009
Variants are modules in the rate or in the schema that contain a billing rule.
A sub-transaction is a key that classifies the document item for account determination. It differentiates the main transaction.
Optional billing step indicator: Schema steps can only be executed in billing if all input operands are supplied with values for the entire period that the step covers. If this is not the case, the optional indicator is checked: y If the indicator is not set, billing of the contract is terminated y If the indicator is set, the schema step is not executed. Processing then continues with the next schema step.
Input and output operand: Description determined within a company for the values that are used as input and output parameters in 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 to analyze the billing documents.
Franchise fee group: A company's own grouping of business partners subject to the same franchise fee conditions (such as major customers or households).
Fine-tuned variant control: Some variant programs require additional input parameters to define the action of the variant programs. Example: Depending on the settings, a variant that subtracts two values can also create negative differences or suppress them.
(©) SAP AG
IUT110
8-16
Fact Group
Fact Group
Operands Operand Values
¤ SAP AG 2009
A fact group is the grouping of individual facts allocated to a rate.
Facts are y Concrete values such as 100 kW y Keys, for example for prices that are allocated to operands and are valid for a certain period of time.
Operands are allocated to the fact group.
Operands manage the operand values.
The operand values represent the historically managed characteristics of the operands.
Example: Fact group X contains the following rate facts: y Minimum demand 20 kW y Discount 10% y This means that if the customer uses at least 20 kW, he/she receives a discount of 10%.
(©) SAP AG
IUT110
8-17
Operand Data
Determination of the demand peaks Operand category
Division
Weighting key
Operands
Access control
History management
Unit of measurement Rounding rules
¤ SAP AG 2003
The operand category classifies the operands for the variant programs.
Rounding rules consist of: y The place to which rounding is carried out: - 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. y The rounding type (the principle used to round): - + for rounding up - - for rounding down - 0 for rounding to the nearest whole number
(©) SAP AG
IUT110
8-18
Operand Categories/Examples
Operand category
Description
AMOUNT DEMAND FACTOR QUANT QPRICE REFVALUE SEASON TPRICE USERDEF
Amount Demand Number with decimal places Quantity Quantity-based price Reference value Season Time-based price User-defined value
¤ SAP AG 2006
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.
(©) SAP AG
IUT110
8-19
Rate Determination - Operands
Operand categories • Predefined • Control processing using variant programs
Operands
Operand values
• Defined individually
• Provide operands with values
• Serve as the parameters for variant programs
• Determine actual values
¤ SAP AG 2008
Facts (normal operand) y Rate facts y Rate category facts y Installation facts
Facts from RTP interface y The output parameter number of the RTP interface is stored in the facts (see above)
Facts from ERCHV y Values are read from DBERCHV
Register operand y Values are determined from meter reading results
(©) SAP AG
IUT110
8-20
Hierarchy
Allocation of Operand Values
Installation facts Have
Price A 0.55
precedence over
Rate category facts Have
Price B 0.60
precedence over
Rate facts and rate fact group
Price C 0.70
¤ SAP AG 2008
Operand values are usually stored in the rate facts and are, therefore, valid at rate level. Cross-rate operand values can also be defined in the rate category facts and installation facts. They have priority over the rate facts.
At rate fact and rate category fact levels, you can also enter replacement values. These replacement values give you more flexibility when allocating operand values.
You can also historically overwrite 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, the system cancels billing and outputs an error in the application log. Exception: the rate step is marked in the rate as an optional rate step.
In the rate facts and rate category facts, you define general operand values. These apply to groups of customers. An installation fact level, you define individual values, such as connection values and number of persons.
(©) SAP AG
IUT110
8-21
Schema I
z Is valid for a certain division z Is valid for a certain billing class z Contains one or more rates z Determines the sequence of the rate steps for billing z Contains indicators for
billing line item relevant to posting
billing line item relevant to statistics
¤ SAP AG 2009
A schema is a structure that determines the sequence in which variant programs of the rates to be billed are executed.
(©) SAP AG
IUT110
8-22
Schema II
z Dependent on the rate category in the installation z Influences sorting of the billing line items on the bill form z Controls the grouping of billing line items
¤ SAP AG 2009
(©) SAP AG
IUT110
8-23
Price Categories
z Quantity-based price for quantities and consumption values z Flat-rate fixed amounts per time unit (consumption flat-rates and flat-rate amounts) z Rental price for the use of a measuring device over a certain period of time z Time-based price for demand and connection values
¤ SAP AG 2006
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.
The price category is a characteristic in the header data.
(©) SAP AG
IUT110
8-24
Price Types
z Standard price: Price not based on quantity z Zone price: One or more quantity-based prices z Scale price: Quantity-based price
¤ SAP AG 2006
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.
The price type is a characteristic in the header data.
Block and scale limits are maintained in the historical data.
(©) SAP AG
IUT110
8-25
Discounts / Surcharges z The discount category defines a discount or surcharge. z The discount type determines the calculation of:
Absolute values
Relative values
z The reference defines how the discount is applied:
Quantity
Price
Amount
¤ SAP AG 2003
(©) SAP AG
IUT110
8-26
Billing Master Data: Unit Summary
z Billing master data is classified by:
Billing class
Rate category
Rate type
z The rate consists of:
Variants, which are provided with operands
A schema, which determines the processing sequence of the variants
Prices, discounts, and surcharges
z Indirect rate determination
Reduced maintenance of data in the case of rate changes
¤ SAP AG 2003
(©) SAP AG
IUT110
8-27
(©) SAP AG
IUT110
8-28
Exercises Unit: Billing Master Data Topic: Rate Structure
After completing 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 for the business partner. Provide information to customers on rates and price calculations.
1-1
Which rate categories have been defined in the installations for business partner TB110110##? 1-1-1
Electricity ______________________________________________________ ______________________________________________________
1-1-2
Water ______________________________________________________ ______________________________________________________
1-2
Which devices and registers are billed to the business partner? 1-2-1
Electricity ______________________________________________________
1-2-2
Water ______________________________________________________
(©) SAP AG
IUT110
8-29
1-3
Which rate types are allocated to the business partner at the following levels? 1-3-1
1-3-2
1-4
Electricity Device level:
________________________________________
Register level:
________________________________________
Water Device level:
________________________________________
Register level:
________________________________________
Carry out rate determination for the rate categories and rate types in tasks 1-1 and 1-3. Division
Rate category
Rate type
Rate determined
Electricity Electricity Water
1-5
Provide information on the electricity rate E1_1. 1-5-1
For which object is the rate permissible? __________________________________________________
1-5-2
From which components is the rate comprised? Name the variant programs and describe the functions: __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________ __________________________________________________
1-5-3
Which operands belong to the rate fact group? What is their significance? __________________________________________________ __________________________________________________ __________________________________________________
1-5-4
What is the energy price? __________________________________________________
(©) SAP AG
IUT110
8-30
1-6
(Optional) The consumption of the flat-rate installation for business partner TB010110## has increased. As a result, the installation must be extended by installing an additional meter as of today's date. Extend the flat-rate electricity installation by installing a meter using today’s date and the following details: Connection Object: Device Location: Installation: New Device:
TB010110## TB010112DL0## TB010130## TB010130## with installation meter reading 250
Make sure that you only allocate 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 allocate a suitable rate category to the installation and limit the installation facts: For example, rate category E1 instead of E4, since the installation is now measured and no longer a flat-rate installation.
(©) SAP AG
IUT110
8-31
(©) SAP AG
IUT110
8-32
Solutions Unit: Billing Master Data Topic: Rate Structure
1-1
Identify business partner TB110110## in the IC and display the data for this business partner. Go to the SAP Easy Access menu and choose: Utilities Industry → Customer Service → Front-Office/Customer Interaction Center → Customer Interaction Center From the Info action, choose Customer Overview for the business partner. The rate category is on the bottom tab page of each contract. Alternatively, you can double-click the installation(s) in the navigation area.
1-2
Display the utility installations for the business partner from the customer environment. In the installations, choose the Devices button.
1-3
Display the utility installations for the business partner from the customer environment. In the installations, choose the Billing View button. You can find the rate types for the devices in the billing view on the Rate Types tab page.
1-4
For rate determination, go to the SAP Easy Access menu and choose: Utilities Industry → Billing → Master Data → Define Rate Determination Division
Rate type
Rate determined
Electricity
1001
E1_1
Electricity
1002
E1_2
Water
3001
W1_1
(©) SAP AG
category
IUT110
8-33
1-5
Display the business partner installation. Choose Billing View. You can find the rates on the Rates tab page. Double click on the rate key. 1-5-1
In the Permissibility display area, you can see that the rate is only permitted for registers.
1-5-2
In the rate, choose the Rate Steps button. You can see a description of the variant by choosing Environment → Variant Documentation.
1-5-3
In the rate, choose the Facts button. You can now see the operands. You can display the operand values by choosing Expand. It is helpful to show the color legend here. Utilities → Color Legend.
1-5-4
(©) SAP AG
Double-click on the operand value. Depending on the price category, you may need to double-click on the price too (with block and scale prices).
IUT110
8-34
1-6
Call the maintenance screen for the flat-rate installation of business partner TB010110##:
In the navigation area, select the flat-rate installation. Click on the right mouse button to choose Rate Maintenance. Choose the time slice overview and specify today’s date for the selection. Set 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 E4 that was entered 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, you have to specify a rate category that matches a rate type at device or register level. 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 before the installation of the device. You may have to delete another automatically generated continuation line before you can copy the settings. Choose Copy to transfer the settings and then save them. The installation is now ready for billing-related device installation. Now call the device installation transaction from the SAP Easy Access menu by choosing: Utilities Industry Æ Device Management Æ Device Installation Æ Installation Æ Full Device Location: Installation: Activity Date: New Device:
TB010112DL0## TB010130## Today's date TB010130##
To continue processing, choose Enter. Activity Reason: Meter Reading Recorded: Periodic Consumption: Rate Type:: Fact Group:
02 Installation extension 250 1000 1002 Off-peak active energy 0001 Residential customer
Activate the indicator for payment of rental and clearing charges. Save your entries.
(©) SAP AG
IUT110
8-35
(©) SAP AG
IUT110
8-36
Billing and Invoicing
Contents: z Billing
Overview
Billing functions
Special functions
z Invoicing
Overview
Invoicing functions
Creation of print and contract accounting documents
z Exception Management
Overview
¤ SAP AG 2009
(©) SAP AG
IUT110
9-1
Billing and Invoicing: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe the billing process
Billing process, simulation
Credit memo, manual backbilling
Outsorting, bill reversal
z Describe the features of invoicing
Invoicing tasks and process
Special features of invoicing
Use of invoicing documents
z Describe the features of exception management
¤ SAP AG 2009
(©) SAP AG
IUT110
9-2
SAP Utilities Meter Reading / Bill / Invoice
MR order creation
MR recording
Billing
Billing order
Billing order
MR order
Plausible MR results
Invoice printout
Invoicing
Billing document
Print document
MR correction Implausible MR results
¤ SAP AG 2009
Meter reading order creation: Meter reading orders are created for each register.
Billing orders are created for each contract.
A billing order is automatically created with the meter reading order. However, the billing order does not have billable status. The billing order can only be billed once plausible meter reading results have been entered.
The billing order is deleted during billing. The billing process creates a billing document that is the basis for invoicing.
(©) SAP AG
IUT110
9-3
Billing Content z Overview
Billing procedures and special functions
Billing and simulation process
Formation of billing rules
z Billing functions
Scheduled dates and periods
Billing transactions
Billing and simulation
Document display
z Special functions
Credit memo, manual backbilling
Outsorting, reversal
¤ SAP AG 2009
(©) SAP AG
IUT110
9-4
Billing: Introduction
z Contract billing of the supply and services provided is the most important function of a utility company. z Integrated processing of both residential and commercial and industrial customers requires several billing rules. SAP Utilities
z Increased competition requires the billing process to be flexible and efficient. z Different types of simulation enable the correct billing to be performed.
¤ SAP AG 2003
(©) SAP AG
IUT110
9-5
Billing: Business Scenario
z 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
z Meter reading processing
Create meter reading order
Enter or estimate meter reading results
z Start of billing and invoicing
Final billing, followed by invoicing
¤ SAP AG 2009
(©) SAP AG
IUT110
9-6
Universal Billing Engine Data relating to customer and installation
Rate data Prices and rate facts
Contract
Installation
Rate cate gory
Rate determination
Rate
Rate 1
Rate n
Inst. Inst. structure structure pe ty Rate Rate cat. cat. facts/ facts/ e t a Installation Installation facts facts R
Data entry and analysis
Procedure data
Quantity conversion and proration
Execution of variant programs according to schema
Schema 1 Var.pr. Values
Rate 1 - Step 1 VarProg. A - Step 2 VarProg. B . . Rate 2
x1 x2 .
- Step 1 VarProg. A - Step 2 VarProg. C - Step 3 VarProg. D . . . . . . . .
x3 x4 x5 . . . .
Rate n - Step 1 VarProg. A
Validation of billing results
E X E C U T B O N
xxx
Generation of billing line items
¤ SAP AG 2003
(©) SAP AG
IUT110
9-7
Billing in SAP Utilities
Business Partner Commercial & industrial customers
Divisions
Residential customers
Water/ Elec- Waste water tricity
Co-generator
Consumption Service Flat rates
Gas Charges, taxes duties
District heating
Cable television Multimedia
Billing rules, variants
...
Price adjustment
Discounts, surcharges
General duties
Prorations
Franchise fees
...
¤ SAP AG 2009
(©) SAP AG
IUT110
9-8
Billing Procedure
Billing Procedure
Special Functions
Î On a monthly basis
Î Interim billing
Î Key date
Î Outsorting for bill verification
Î Period
Î Simulation
Î To-the-day
Î Manual backbilling
Î Seasonal
Î Manual credit memo
Î Comparative (best-rate billing)
Î Reversal procedure
Î For employees
Î Unbilled revenue reporting
Î Rolling (back-billing, final billing)
¤ SAP AG 2009
(©) SAP AG
IUT110
9-9
Definition of Billing
Meter reading
Billing
Invoicing Billing order processing that involves valuating consumption and services for individual contracts, and creating billing documents for invoicing. ¤ SAP AG 2003
(©) SAP AG
IUT110
9-10
Billing Tasks
Determination and conversion of quantities
Determination of billing periods
Determination of change date and proration to that date
Billing
Valuation of quantities with prices
Creation of billing documents for invoicing
Determination of • Rate data • Price data
¤ SAP AG 2003
(©) SAP AG
IUT110
9-11
Billing Periods
z Length of period for periodic billing
n days; 1, 2, 3, 4, 6, or 12 months
z Length of period for period-end billing
n + n days; 1, 2, 3, 4, 6, or 12 months
MO 1 8 15 21 28
TU WE TH
FR
SA SU
2 9 16 22 29
5 12 19 25
6 13 20 26
3 10 17 23 30
4 11 18 24 31
7 14 21 27
z To-the-day billing
Based on the date of the meter reading
z Month-based billing
Dependent on key date
z Month-based billing
Dependent on intervals
¤ SAP AG 2006
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 days Determines 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-based Bills a specific number of complete months. If the case of a move-in or move-out, the monthbased procedure can be billed based on the number of days.
(©) SAP AG
IUT110
9-12
Forms of Billing
z Periodic Billing Recurring periodic billing
z Floating Backbilling Special form of monthly periodic billing in which backbilling is performed for previous months using a current value for example, monthly comparison of N peak average
z Period-end Billing Billing occurs upon the conclusion of the billing cycle for example, 13th billing, when a year is back-billed
z Interim Billing unscheduled billing at any time; can be initiated at the customer's request
z Final Billing when the customer moves out or when the contract is terminated
¤ SAP AG 2009
(©) SAP AG
IUT110
9-13
Special Forms of Billing
z Best-rate billing The most favorable rate is chosen for the customer on the basis of several billing rules.
z Quantity-based rate for basic price The annual quantity consumed is used to determine the billing rule that applies.
z Demand-based rate determination The measured demand is used to determine the billing rule that applies.
z Season-based billing Examples: Different prices for each season, different billing rules for each season.
¤ SAP AG 2003
(©) SAP AG
IUT110
9-14
General Billing Functions
Decision variants Energy price
Demand price
Usage hours
Billing
Best-rate billing
Block and scale price
Basic and service price Seasonal values and variants
¤ SAP AG 2009
Energy prices are used to valuate measured or calculated consumption. For example: y Adjustment of calculated consumption over the course of the billing period y Comparison with maximum/minimum purchase quantities and further processing of difference quantities y Breakdown/valuation of energy quantities using different percentage rates or time criteria
Demand price
s are used to valuate measured or calculated demand. The number of the measured demand values used for calculating the demand to be billed is variable. For example: y Comparison with minimum demand, maximum demand, or other demand established in the contract, and further processing of the difference demand (such as excess demand) y Breakdown and valuation of demand using different percentage rates
You can valuate any number of demand replacement values with time-based prices for the provision of the supply. The demand replacement values can also be levied as a flat rate.
Block and scale price
Seasonal values and variants
Decision variants
(©) SAP AG
IUT110
9-15
Special Billing Functions
Determination of taxes, duties, and charges
Billability check
Consideration of register relationships
Billing
Energy feeding from small power producers
Billing of company and plant consumption
Manual credit memos and backbilling
¤ SAP AG 2003
(©) SAP AG
IUT110
9-16
Billing and Simulation Choose billing type
Date reached for billing
Billing Types
Description:
Billing
z
The billing order is deleted and cannot be billed again
z
Meter reading results cannot be changed again
z
Select type of billing
Billing selected
Simulation selected
Start billing
Start simulation
Check billing documents
Check simulation documents
Billing documents implausible
Billing documents correct
Billing documents incorrect
Outsort documents
Start invoicing
Reverse billing
Start invoicing simulation
Description:
Creation of billing documents used only for further processing in invoicing
Processing Steps:
Enter selection criteria
SAP UT
Creation of simulation documents that are only used for further processing in invoicing simulation Simulation
Processing Steps: z
Billing order is retained and and can still be used for simulation
z
Meter reading results can still be changed
z
Simulation document is created
Billing document is created
¤ SAP AG 2008
(©) SAP AG
IUT110
9-17
Simulation Types
Date reached for billing
Enter selection criteria
Billing selected
Start billing
Choose simulation type Simulation selected
Start simulation
Check billing documents
Simulation Types Description:
Select type of billing
Check simulation documents
Billing documents implausible
Billing documents correct
Billing documents incorrect
Outsort documents
Start invoicing
Reverse billing
Start invoicing simulation
Description: SAP UT
Billing can be simulated without a billing order for any group and for any period of time. Simulation
Billing is simulated on the basis of a billing order that can be processed. Billing simulation
Processing Steps:
Processing Steps:
z
Simulation period can be freely defined
z
Period is determined by the billing order
z
Extrapolation that takes account of meter reading results
z
Meter reading results relevant to billing are required
z
Period can already have been billed
z
Valuation of billing
z
Check capacity for billing
¤ SAP AG 2009
(©) SAP AG
IUT110
9-18
Document Types
Billing date reached
Enter selection criteria
Billing chosen
Start billing
Choose billing type
Check documents Simulation chosen
Start simulation
Check billing documents
Simulation
Billing documents implausible
Billing
Outsort documents
Check simulation documents
Billing documents correct
Billing documents incorrect
Start invoicing
Reverse billing
Start invoicing simulation
Description: Simulation document
z
Simulation produces a simulation document
z
Billing produces a billing document
Billing document
Purpose z
Documents the procedure
z
Saves and validates the results
z
Used for further processing of billing line items
¤ SAP AG 2003
(©) SAP AG
IUT110
9-19
Document Information
Billing date reached
Billing line items
Enter selection criteria
Billing chosen
Start billing
Choose billing type
Check documents Simulation chosen
Start simulation
Check billing documents
Internal billing data
Account data
Billing documents implausible
Rate data
Documents from • Simulation
Outsort documents
Check simulation documents
Billing documents correct
Billing documents incorrect
Start invoicing
Reverse billing
Start invoicing simulation
Price data
• Billing
Print data
Device data Meter reading data
¤ SAP AG 2003
(©) SAP AG
IUT110
9-20
Further Processing of Documents
Billing date reached
Billing documents implausible
Outsort documents
Choose billing type
Billing chosen
Simulation chosen
Start billing
Start simulation
Check billing documents
Invoicing
Invoicing simulation
Enter selection criteria
Check simulation documents
Process documents further
Billing documents correct
Billing documents incorrect
Start invoicing
Reverse billing
Start invoicing simulation
Documents from • Simulation • Billing
Billing reversal
Outsorting
¤ SAP AG 2003
(©) SAP AG
IUT110
9-21
Outsorting Procedure
Date reached for billing
Outsort Documents
Billing documents, for which the validation checks have failed, are outsorted automatically.
Billing selected
Simulation selected
Start billing
Start simulation
Check billing documents
Check simulation documents
Billing documents implausible
Billing documents correct
Billing documents incorrect
Outsort documents
Start invoicing
Reverse billing
Outsort Documents
Start invoicing simulation
Billing documents for a contract, for which the outsorting indicator is set, are not automatically processed further.
SAP UT
Automatic
Manual
Percntage or absolute amnt that the billing doc exceeds or falls below the following:
Purpose
Amount limit Final invoice amount Budget billing amount
Select type of billing
Description:
Description:
Possible Validations:
Enter selection criteria
Bills with a balance of zero
Check non-residential contract billing documents Check new rates
Check consumption values in complex installations
Check proration for different time slices
¤ SAP AG 2008
(©) SAP AG
IUT110
9-22
Process of Outsorting
Billing date reached
Billing
Invoicing
Bill printout
Enter selection criteria
Choose billing type
Billing chosen
Simulation chosen
Start billing
Start simulation
Check billing documents
Billing documents implausible
Outsort documents
Check documents
Exception list
Billing documents correct
Outsort documents
Start invoicing
Check simulation documents
Billing documents incorrect
Start invoicing simulation
Reverse billing
z Outsorting reasons
Outsort documents
Failed validation
Indicator set in the contract
z Further processing Reverse documents
Release documents
Reversal
Release
¤ SAP AG 2003
(©) SAP AG
IUT110
9-23
Billing Reversal
Date reached for billing
Reverse Billing
Only one billing document is reversed. This can occur with or without a subsequent correction bill.
Incorrect conditions for nonresidential contract Incorrect meter reading result
Technical fault
...
Select type of billing
Billing selected
Simulation selected
Start billing
Start simulation
Check billing documents
Check simulation documents
Billing documents implausible
Billing documents correct
Outsort documents
Start invoicing
Start invoicing simulation
Reverse documents Billing documents incorrect Reverse billing
Description:
Description:
Possible Reasons:
Enter selection criteria
SAP UT
Mass reversal
Individual reversal
More than one billing document is reversed. Selection takes place using document intervals or lists of individual documents.
Possible Reasons:
Incorrect billing group
Incorrect rates and prices
Incorrect sales tax ...
¤ SAP AG 2008
(©) SAP AG
IUT110
9-24
Billing Reversal Process
Document outsorted
Billing date reached
Reverse billing
Correct data
Restart billing
Enter selection criteria
Choose billing type
Billing chosen
Simulation chosen
Start billing
Start simulation
Check billing documents
Document implausible
Billing documents implausible
Outsort documents
Check simulation documents
Reverse documents
Billing documents correct
Start invoicing
Start invoicing simulation
Billing documents incorrect
Reverse billing
Billing order
16.2.04 Incorrect billing document
23.2.04 Reversed billing document
24.2.04 Corrected billing document Jane Smith
Jane Smith
Jane Smith
Electricity . . . . 900 Gas . . . . . . .1.000 Water . . . . . . . 700
Electricity . . . . 900 Gas . . . . . . 1.000 Water . . . . . . . 700
Total . . . . . 2.600
Total . . . . . . .2.600
Electricity . . . . 600 Gas . . . . . . 1.000 Water . . . . . . . 700 Total . . . . . . . 2.300
Reversal indicator set ¤ SAP AG 2003
(©) SAP AG
IUT110
9-25
Billing: Unit Summary
z Billing processes billing orders, valuates
consumption and demand, and creates billing documents for invoicing. z There are two types of billing: Simulation, which creates simulation documents Billing, which creates billing documents
z Outsorted billing documents require additional
processing - Documents must be either released or reversed. Reasons for outsorting: Failed validation Indicator set in the contract
z Individual or mass reversals enable quick correction
and subsequent billing. ¤ SAP AG 2003
(©) SAP AG
IUT110
9-26
Invoicing Content z Overview
Definition of invoicing and tasks involved
Distinguishing between invoicing and billing
z Invoicing functions
Invoicing units
Cross-company code invoicing
z Creation of FI-CA and print documents
Document flow
Bill printout
Outsorting, reversal
¤ SAP AG 2009
(©) SAP AG
IUT110
9-27
Invoicing: Introduction
z Invoicing links contract billing to contract accounts receivable and payable, and prepares bill printout. z The bill sum total is determined after clearing billing documents against the budget billings already paid, and against the taxes, charges, and duties that are due. SAP Utilities
z Flexible clearing options, such as payments for open items, reduce the amount of manual processing required.
¤ SAP AG 2009
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)
(©) SAP AG
IUT110
9-28
Invoicing: Business Scenario
z 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
z Meter reading processing
Create meter reading order
Enter or estimate meter reading results
z Start of billing and invoicing
Final billing, followed by invoicing
¤ SAP AG 2009
(©) SAP AG
IUT110
9-29
Definition of Invoicing
Meter reading Billing
Invoicing
The process that links the billing documents to contract accounts receivable and payable, and provides the basis for bill creation. ¤ SAP AG 2009
(©) SAP AG
IUT110
9-30
Invoicing: Overview Billing:
Contract Accounts Receivable and Payable:
Consumption billing creates billing documents by evaluating consumption values and services.
Contract Accounts Receivable and Payable makes processes relevant for payment available, and manages the individual accounts.
Transactions Relevant for Invoicing
Billing documents
Credit memos
Backbillings
Transactions Relevant for Invoicing SAP UT
FIFI-CA
Open items Paid budget billing amounts
Manual postings
Dunning charges
Payments on account
Invoicing
Bill printout
BB plan
Due date determination Clearing
Use of credits
¤ SAP AG 2008
(©) SAP AG
IUT110
9-31
Tasks of Invoicing
Optional Invoicing tasks Creation of budget billing plan
Joint invoicing
Cross-company code invoicing
Invoicing
Account determination
Due date determination
Credit clearing Budget billing clearing
¤ SAP AG 2009
Invoicing is the process that integrates contract billing with the Contract Accounts Receivable and Payable (FI-CA) component. It also forms the basis for bill creation.
Optional invoicing tasks: y Account maintenance y Interest on Cash securities y Interest on Receivables y Dunning y Late Payment Charges
Invoicing is used for the following: y Grouping together billing documents of contracts from the same contract account into one joint bill. y Posting documents to FI-CA (sub-ledger accounting) y Supplying bill printout documents for bill creation y Processing budget billing plans
(©) SAP AG
IUT110
9-32
Invoicing Units
Date for invoicing reached
z Creation of invoicing units
Enter selection criteria
Choose invoicing type
Invoicing chosen
Start invoicing Start invoicing
Summary of the billing documents in a contract account can be controlled at contract level.
Mandatory
Check the FI-CA document
Check bill printout document
Invoicing documents implausible
Invoicing documents correct
Invoicing documents incorrect
Outsort documents
Start bill printout
Reverse invoicing
Invoicing simulation chosen Start invoicing simulation
Check simulation documents Simulate bill printout
Contracts for which the documents must be invoiced together
Optional Contracts for which the documents can be invoiced together
Exclusive Contracts for which the documents must be invoiced separately
¤ SAP AG 2003
(©) SAP AG
IUT110
9-33
Mandatory and Optional Contracts: I
Contract account
Billing
Contract Contract 11
Document Document 11 Mandatory Mandatory
Mandatory Mandatory Joint Joint invoice invoice
Invoicing
Contract Contract 22 Mandatory Mandatory Joint Joint invoice invoice
Contract Contract 33 Mandatory Mandatory Joint Joint invoice invoice
Contract Contract 44 Optional Optional Joint Joint invoice invoice
Contract Contract 55 Exclusive Exclusive invoice invoice
Document Document 33 Mandatory Mandatory Document Document 44 Optional Optional
Document Document Optional Optional
Document Document 55 Exclusive Exclusive
Document Document Exclusive Exclusive
ll Bi
ll Bi
¤ SAP AG 2009
Contracts 1-3 have a joint invoicing ID. This means that a bill is only created when documents are available for all three contracts.
Contract 4 can - but does not have to be - invoiced with the other contracts.
Contract 5 is always invoiced separately
(©) SAP AG
IUT110
9-34
Mandatory and Optional Contracts: II
Contract account Contract Contract 11 Mandatory Mandatory Joint Joint invoice invoice
Contract Contract 22 Mandatory Mandatory Joint Joint invoice invoice
Contract Contract 33 Mandatory Mandatory Joint Joint invoice invoice
Contract Contract 44 Optional Optional Joint Joint invoice invoice
Contract Contract 55 Exclusive Exclusive invoice invoice
Billing
Invoicing
Document Document 11 Mandatory Mandatory Document Document 22 Mandatory Mandatory
Document Document
ll Bi
Document Document 33 Mandatory Mandatory Document Document 44 Optional Optional Document Document 55 Exclusive Exclusive
Document Document Exclusive Exclusive
ll Bi
¤ SAP AG 2009
(©) SAP AG
IUT110
9-35
Invoicing Options
Date reached for invoicing
z SAP Billing Documents
Enter selection criteria
Select type of invoicing
Invoicing simulation selected
Invoicing selected
Start invoicing Start invoicing
SAP Utilities billing documents SD billing documents
Check the ? FI-CA document
Check bill ? printout document
Billing documents implausible
Billing documents correct
Billing documents incorrect
Outsort documents
Start bill printout
Reverse invoicing
Start invoicing simulation Check simulation documents Simulate bill printout
PM/SM billing documents
z Company Code Allocation
Invoicing within a company code
Cross-company code invoicing
¤ SAP AG 2008
(©) SAP AG
IUT110
9-36
Source of Billing Documents
SAP Systems:
External Systems:
Central invoicing of all processes from consumption billing, sales and distribution and service management simplify the transactions.
Transactions Relevant for Invoicing
SAP Utilities consumption billing
SD Sales and Distribution
CS Customer Service
Using standard billing documents, billing results from external systems can be invoiced and monitored together with consumption billing results. ExternalTransactions
SD
Relevant for
Invoicing
SAP UT
CS
Telecommunications
Heating costs billing
Other unbundling services
Bill Jane Smith .... Electricity . . . Maintenance .. . Te lCo . . . . Total . . . .
. 600 1,500 . 700 2,800
¤ SAP AG 2008
(©) SAP AG
IUT110
9-37
Invoicing Various Services
Disposal service #1 Waste Waste water water Waste Waste Sale
Radiator Radiator
$$ 50 50 $$ 40 40 #5
$$ 35 35
Maint. charge #6
Utility service #2 Electricity Electricity Water Water Gas Gas
$$ 15 15 $$ 60 60 $$ 80 80
Total bill
Energy feeding #3 Electricity Electricity obtnmnt obtnmnt $$ 85 85
#4711:
Bill (#1-#7) $ 510 - Budgt bllng amnts pd (#1-#3) $ 330 Final invoice amount $180
Cable Cable TV TV
$$ 30 30
Extrnl bllng doc #7 Service xy $ 70
Due on January 15, 2010
Bill summary
Gas Gas pipe pipe $$ 45 45
Account: Bill #4711
Simplified Example without Tax !
Other services #4
A. Smith $ 180
Line items for each receivable: Bill #1 ... Bill #2 ... ................
in SAP Utilities - One division for several cont racts ("unbundling" electricity rate) - Various divisions (S,G,W,...) in SAP application - Invoices from SD/CS and SAP Utilities and billing from external systems
¤ SAP AG 2009
(©) SAP AG
IUT110
9-38
Cross-Company Code Invoicing
Total Bill #4711 Contracts for "xy" CoCd. 01
Company xy: Cons. billing #1 Electricity Gas Water
Mayer account (xy) Re. #4711 380,380,- $ Line items for each receivable:
1000,- $ 1500,- $ 600,- $
Bill #1 (xy) ... Bill #2 (zz) ...
Crss-CoCd. bllng for authrty zz:
Contracts for "zz" CoCd. 02
Contracts for "rs" CoCd. 03
SAP UT
Other services #2 Waste water Waste disposal
Bill #3 (rs)
Electricity rec. Gas rec. Water rec.
...
FI-CA
500,- $ 200,- $
General ledger 02 Loc. Auth. "zz"
Crss-CoCd bllng for TV co rs: Other services #3 Cable TV
General Ledger 01 Municipal utility companies xy
180,- $
Total bill #4711: Bill (#1-#3) 3980,- $ - Budgt bllng amnt pd (#1-#3)-3600,- $ still to be paid: 380,- $ Due on 01/15/04
Waste water rec. Waste dispsal rec. Cross-company code billing
General ledger 03 (not relevant for fin. statements) TV co "rs" Cable TV rec. Third party billing
FI
¤ SAP AG 2009
This is an example of invoicing for different company codes.
The municipal utility companies xy supply their customers with electricity, gas and water.
However, XY performs billing on behalf of local authority ZZ for waste water and waste disposal.
XY also performs billing on behalf of cable company RS for cable TV charges.
This whole process occurs in the same SAP system, although it involves different companies.
(©) SAP AG
IUT110
9-39
Bill Due Date
Date for invoicing reached
z The bill due date is determined from the following attributes:
Enter selection criteria
Terms of payment These determine the source of the baseline date
Invoicing simulation chosen
Invoicing chosen
Start invoicing Start invoicing
Check the FI-CA document
Choose invoicing type
Check bill printout document
Invoicing documents implausible
Invoicing documents correct
Invoicing documents incorrect
Outsort documents
Start bill printout
Reverse invoicing
Start invoicing simulation
Check simulation documents Simulate bill printout
Baseline date: Posting date, document date, or system date
z 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
Baseline date + terms of payment = bill due date ¤ SAP AG 2003
The bill due date can also be combined with the first budget billing.
Posting date: Date when a business transaction is transferred to one or more accounting ledgers on document entry.
Document date: Creation date of original document (for example, a vendor invoice).
System date: Date when a document is created in the system. This date is automatically specified by the system.
(©) SAP AG
IUT110
9-40
Document Flow in Invoicing
Date for invoicing reached
Enter selection criteria
Choose invoicing type
Invoicing simulation chosen
Invoicing chosen
Start invoicing Start invoicing
Check the FI-CA document
Billing documents
Credit memos/ backbillings
Check bill printout document
Invoicing documents implausible
Invoicing documents correct
Invoicing documents incorrect
Outsort documents
Start bill printout
Reverse invoicing
Start invoicing simulation
Check simulation documents Simulate bill printout
Print documents
Start invoicing Posting documents FI-CA
Budget billing plans
FI-CA documents
¤ SAP AG 2003
(©) SAP AG
IUT110
9-41
Clearing Overview
Date reached for invoicing
Enter selection criteria
Select type of invoicing
z The SAP Utilities clearing concept Start as part of SAP Utilities clearing processing defines: invoicing Invoicing selected
Start invoicing
Check the ? FI-CA document
the automatic determination of the use of a payment amount for entering a payment transaction
Billing documents implausible
Outsort documents
Check bill ? printout document
Billing documents correct
Billing documents incorrect
Start bill printout
Reverse invoicing
Invoicing simulation selected Start invoicing simulation Check simulation documents Simulate bill printout
the automatic allocation of posted open items to each other in account maintenance
z The selected items are cleared or partially cleared on the basis of these allocations. z The clearing concept provides flexible control and enables you to model your own clearing strategy in Customizing.
¤ SAP AG 2009
Clearing concept is discussed in greater detail in IUT240 – Financials Contract Accounting.
(©) SAP AG
IUT110
9-42
Bill Printout Procedure
Date for invoicing reached
Print document ready for output
Select print document
Choose output type
Start output
Enter selection criteria
Invoicing chosen
Invoicing simulation chosen
Start invoicing
Start invoicing simulation
Check the FI-CA document
Invoicing documents implausible
Outsort documents
Choose invoicing type
Check bill printout document
Check simulation documents
Invoicing documents correct
Invoicing documents incorrect
Start bill printout
Reverse invoicing
Start bill printout
Simulate bill printout
SAP spool Output
Print documents
Raw data interface
Dea
Dear M ada m/S
r ir: In r efer /Sir: Dear MInada M adam en ce r efer m/ Sir: en ce to yo ur to yo ur l ette r of 9/27 In r efer9/27 en ce lette r of ... to yo ... ur lett er 9/27 ... of
Mail processing Bill date
Archive ¤ SAP AG 2003
(©) SAP AG
IUT110
9-43
Reverse Invoicing Date reached for invoicing
Invoicing simulation selected Start invoicing simulation
Start invoicing
Mass reversal
Check bill ? printout document
Check the ? FI-CA document
or
individual reversal
Bill reversal:
Select type of invoicing
Invoicing selected
Reverse Invoicing
Enter selection criteria
Billing documents implausible
Billing documents correct
Outsort documents
Start bill printout
Check simulation documents Billing documents incorrect
Simulate bill printout
Reverse invoicing Reverse invoicing
Full reversal:
Bill printout and FI-CA documents for bills or partial bills are reversed by selection using a reconciliation key or document number.
SAP UT
Bill reversal
Mass reversal
Transaction
In addition to the bill, billing documents are also reversed by selection using a document number. Full reversal does not include reversal of partial billing documents.
Transaction
Reversal of FI-CA document
Reversal of FI-CA document
Reversal of bill printout document
Reversal of bill printout document
Possible reasons
Reversal of billing document
Possible reasons
Incorrect layout Printing problems
Incorrect billing
¤ SAP AG 2009
(©) SAP AG
IUT110
9-44
Procedure for Bill Reversal
Doc outsorted
Date reached for billing
Reverse invoicing
Correct data
Start invoicing again
Doc implausible
Enter selection criteria
Select type of billing
Billing selected
Simulation selected
Start billing
Start simulation
Check billing documents
Check simulation documents
Billing documents implausible
Billing documents correct
Outsort documents
Start invoicing
Start invoicing simulation
Reverse documents Billing documents incorrect Reverse Billing
Billing ?document
Bill Jane Smith .... Electri cit y . Gas . . . . Wate r . . .
. . 900 . 1,000 . . 700 ounts . 2,900 Budget billing am 300 . Credit memo . .
Reve rsed bill Jane Smith .... . . 900 Electri cit y . . . . 1,000 . . . Gas . . 700 Water . . . . . ount s . 2,900 Budget billing am . 300 Cred it memo . .
New bill Jane Smith .... 900 Electricit y . . . 1,000 Gas . . . . . . 700 Water . . . . ounts . 2,500 Budget billing am 100 Receivable . .
Reversal indicator set ¤ SAP AG 2009
Accounting documents from Contract Accounts Receivable and Payable (FI-CA), and that were created by SAP Utilities invoice processing, are reversed. Billing documents from the contract billing (IS-U-BI) component and budget billing amounts from the budget billing plan component can be re-used for invoicing after bill reversal.
(©) SAP AG
IUT110
9-45
Procedure for Full Reversal
Document outsorted Reverse invoice
Reverse billing
Correct data
Restart billing
Restart invoicing
Document implausible Billing order
16.2.03 Incorrect billing document
23.2.03 Reversed billing document
24.2.03 Corrected billing document
Jane Smith
Jane Smith
Jane Smith
Electricity . . Bil . . l . . 900 Gas . . . . . . 1.000 ith Jane Sm Water . . . . . . 700 ....
Electricity . . Re . . ver 900sed bill Gas . . . . . 1.000 ith Jane Sm Water . . . . - ....700
Electricity . . . . w . . 600 Ne bill Gas . . . . . . 1.000 e Smith Jan Water . . . . . . 700 ....
. 900 Total . . . . . 2.600 Electricity . . .. . 1.000 Gas . . . . . . . .700 . . . . . ter Wa .2.900 Bud. billings . . . 300 Credit memo .
. . 900 Total . . . . - 2.600 Electricity . . . 1.000 Gas . . . . . . . . 700 . . . . ter Wa . 2.900 Bud. billings . . . 300 Credit memo .
. 900 Total . . . . . 2.300 Electricity . . .. .1.000 Gas . . . . . . . 700 . . Water . 2.500 Bud. billings . . 100 . . . . . . Total
¤ SAP AG 2003
This function is a mixture of the bill reversal and billing reversal functions. It enables you to reverse different types of documents in one step.
(©) SAP AG
IUT110
9-46
Invoicing: Summary
z The invoicing procedure includes:
Invoicing and printing of the bill
Requests for budget billings or creation of partial bills
Different reversal procedures
Flexible clearing control
z Budget billing procedure
Budget billing amount: Statistical posting or real debit entry
Payment plan: Fixed amounts or variable amounts
z Output
¤ SAP AG 2008
(©) SAP AG
Printout on ERP printer using spool
Raw data interface for external mail processing
Archiving
IUT110
9-47
Exception Management: Introduction
z Business Process Exception Management (BPEM) is a tool which enables companies to manage process exceptions across all functional areas in one place. z BPEM uses case categories to differentiate exceptions and to identify solutions and agents.
SAP Utilities
z Cases are created automatically or manually, depending on the type of exception and its triggering process. z Worklists provide users with a list of exceptions to process.
¤ SAP AG 2009
Maintain case categories with transaction EMMACCAT1
Create cases with transaction EMMAC1
Monitor mass activities and other automatic processes with transaction FPEMMAMA
View processing logs with transaction EMMA
Process cases with transaction EMMACL and EMMACLS
Cases can be generated in many ways: manually by user, i.e. High Bill Complaint; automatically via a customer program; automatically by SAP program based on defined criteria, i.e. outsorting or error message.
Case solutions can be pre-defined, and can be executed manually or automatically.
Exceptions are not necessarily errors. Examples include: y High bill complaint y Research missing payment y Outsorted billing/invoicing documents y Implausible meter reads
(©) SAP AG
IUT110
9-48
Exercises Unit: Billing and Invoicing Topic: Billing a Business Partner
After completing these exercises, you will be able to: • Describe the billing process and tasks • Use the billing and simulation functions Business processes require the billing of an individual customer. In addition to periodic billing, this may be necessary due to a customer moving out, at the request of a customer, or to advise a customer, for example. Carrying out a simulation for any billing period, or for the actual billing period, allows you to provide specific information without altering data. 1-1
Your business partner TB100120## with contract account TB100120## requires a periodic billing. 1-1-1
Call the individual billing processing transaction. ______________________________________________________ ______________________________________________________
1-1-2
On the Individual Bill screen, enter the following information: the last day of the previous month as the document date, your account number, signify that you will create a meter reading order and results, select the Bill option and execute the transaction. ___________________________________________________ ___________________________________________________ ___________________________________________________ ___________________________________________________
(©) SAP AG
IUT110
9-49
1-1-3
Choose the appropriate schedule record date to create the order and record the meter readings in the process. Use the entry which is closest to the current date but not in the future. •
Enter a plausible meter reading for each device and register. Use the correction and estimate functions. Which values did you enter? Electricity register 1: ___________________________________ Gas register 1
___________________________________
Water register 1
___________________________________
1-1-4
Note in the log that a billing document has been outsorted. Call the outsort processing transaction and process it by releasing the outsorted document.
1-1-5
Call the Create Bill (individual) transaction.
1-1-6
Enter IBMMDDYY-XX in the Reconciliation Key field and confirm the contract account number and dates, then execute. Confirm the reconciliation key to be created and view the log/display the completed document.
(©) SAP AG
IUT110
9-50
1-2
Your business partner TB100110## would like an interim bill. Enter the meter readings supplied by the customer. Display the individual simulation of the bill. Check the results and then exit the genuine bill. 1-2-1
Enter the meter readings for business partner TB100110##. Use the IC to do this. ______________________________________________________ ______________________________________________________ ______________________________________________________ Which meter readings have you entered? ______________________________________________________ ______________________________________________________ ______________________________________________________
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
•
Use the contract account to make your selections.
•
Choose the Display bill level of processing.
______________________________________________________ ______________________________________________________ ______________________________________________________ 1-2-3
Process 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
•
Use the contract account to make your selections.
•
Choose the Bill level of processing.
______________________________________________________ ______________________________________________________ ______________________________________________________
(©) SAP AG
IUT110
9-51
1-3
Display the billing document for the water contract with business partner TB100110## and answer the following questions. 1-3-1
Display the billing document. ______________________________________________________ ______________________________________________________
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 document line item types are present and what do they mean? Document line item type
1-3-5
Meaning
What was the total billing quantity determined? ______________________________________________________
1-4
True or false? 1-4-1
Billing is always carried out after the meter reading and before invoicing. ______________________________________________________
1-4-2
Billing simulation must be carried out before billing. ______________________________________________________
1-4-3
After billing, 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. ______________________________________________________
(©) SAP AG
IUT110
9-52
Exercises Unit: Billing and Invoicing Topic: Invoicing a Business Partner
After completing these exercises, you will be able to: •
Describe the invoicing process and tasks
•
Use the invoicing and simulation functions
•
Explain the budget billing procedure.
The billing results are compared with the transactions in open item accounting. The final bill amount 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
Perform the invoice simulation for business partner TB100110## who was billed in exercise 1-2-3. Carry out the following steps: 2-1-1
Simulate the invoice. ______________________________________________________ ______________________________________________________
2-1-2
Check the log. ______________________________________________________ ______________________________________________________
2-1-3
Display the print document. ______________________________________________________ ______________________________________________________
2-1-4
Simulate the bill. ______________________________________________________ ______________________________________________________
(©) SAP AG
IUT110
9-53
2-2
Process the actual invoice for business partner TB100110##. 2-2-1
Invoice the business partner. ______________________________________________________ ______________________________________________________
2-2-2
Check the log. ______________________________________________________ ______________________________________________________
2-2-3
Display the bill from the customer overview. ______________________________________________________ ______________________________________________________
2-3
Provide information on the print document. 2-3-1
From the customer overview, display the print document for business partner TB100110##. ______________________________________________________ ______________________________________________________
2-3-2
How many line items does the print document contain? ______________________________________________________ ______________________________________________________
2-3-3
What is the final bill amount? ______________________________________________________ ______________________________________________________
2-3-4
Which rate was used in the calculation? ______________________________________________________ ______________________________________________________
2-3-5
What is the due date of the bill? ______________________________________________________
(©) SAP AG
IUT110
9-54
2-4
True or false? 2-4-1
Invoicing is only carried out after billing. ______________________________________________________ ______________________________________________________
2-4-2
The invoice constitutes a joint bill for all the contracts in a contract account. ______________________________________________________ ______________________________________________________
2-4-3
The invoice includes billing documents from other company codes. ______________________________________________________ ______________________________________________________
2-4-4
The due date of the bill is always derived from the posting date and the terms of payment. ______________________________________________________ ______________________________________________________
2-4-5
The invoice generates print documents. ______________________________________________________ ______________________________________________________
2-4-6
The invoice can be reversed separately or together with the bill. ______________________________________________________ ______________________________________________________
2-4-7
The invoice only includes statistically posted budget billing amounts. ______________________________________________________ ______________________________________________________
(©) SAP AG
IUT110
9-55
(©) SAP AG
IUT110
9-56
Solutions Unit: Billing and Invoicing Topic: Billing a Business Partner
1-1 From the SAP Easy Access menu, choose: 1-1-1
Utilities Industry → Billing → Billing Execution→ Individual Processing→ Individual Bill
1-1-2
Enter TB100120## in the Contract account. field, the last day of the previous month in the Document date field, and activate the checkbox next to the Enter billing order/ME results field and click on the Execute icon.
1-1-3
At the List of Schedule Records screen, scroll to the entry which is closest to and less than the current date, and click on it. At the next screen, Display Schedule Record, click on the Create Order button. At the next screen, Single Entry, click on the Estimate button, then click on the Save button to save the entry. Repeat this for each of the other contracts.
1-1-4
Click on the Log button to check the log and view the results. Note that one billing document has been outsorted. Follow the menu path: Utilities Industry → Billing → Billing Execution → Outsorting, enter TB100120## in the Business Partner field, and click on the Execute icon. Select the billing document and click on the Release document button
1-1-5
Follow the menu path: Utilities Industry → Billing → Billing Execution → Individual Processing → Individual Bill. Enter IBMMDDYY-XX in the Reconciliation Key field, click on the Invoice radio button in the Level of Processing section, confirm the account number and dates, then click on the Execute icon. Confirm the reconciliation key to be created. Confirm the billing documents in the pop-up window. Click on the Log button to view the log and results. Note the message which indicates a successful invoice.
(©) SAP AG
IUT110
9-57
1-2
From the SAP Easy Access menu, choose: Utilities Industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center Identify the customer. 1-2-1
In the navigation are on the Environment tab page, select the contract. Click the right mouse button to choose Enter customer meter reading. Enter the meter reading results for each individual contract You have to carry out this process three times.
1-2-2
Go to the SAP Easy Access menu and choose: Utilities Industry → Billing → Billing Execution → Individual Processing → Individual Simulation → Billing
1-2-3
Go to the SAP Easy Access menu and choose: Utilities Industry → Billing → Billing Execution → Individual Processing → Individual Bill
1-3
Go to the SAP Easy Access menu and choose: Utilities Industry → Billing → Billing Execution → Display Document 1-3-1
Choose the F4 help in the Document no. field. Enter your business partner number. The system offers all the billing document for the customer for selection. Select the most recent document by double-clicking on it.
1-3-2
On the Header Data tab page you can see the most important billing data.
1-3-3
On the Document Overview tab page you can see an overview of the billing lines.
1-3-4
ZWATER
Energy price
000004
Rental price
IQUANT
Quantities (meter readings)
1-3-5
(©) SAP AG
The billing quantity is visible both in the table overview and in the individual documents.
IUT110
9-58
1-4 1-4-1
True. Billing processes the meter reading results and provides the 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 only be used for simulating invoices.
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 exists. The result of billing are invoice orders.
1-4-4
True. In contrast to billing documents, billing simulation documents can only be processed further by invoicing simulation.
1-4-5
True.
(©) SAP AG
IUT110
9-59
(©) SAP AG
IUT110
9-60
Solutions Unit: Billing and Invoicing Topic: Invoicing a Business Partner
2-1
Go to the SAP Easy Access menu and choose: Utilities Industry → Invoicing → Execute Invoicing → Individual Processing → Create Bill 2-1-1
Select the Document Simulated checkbox.
2-1-2
Start the simulation.
2-1-3
Once the simulation is complete, choose Display Document. You can also call the print document using the following SAP Easy Access menu path: Utilities Industry → Invoicing → Execute Invoicing → Display Print Document
2-1-4 2-2
Choose the Simulate Bill button.
Go to the SAP Easy Access menu and choose: Utilities Industry → Invoicing → Execute Invoicing → 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
Go to the SAP Easy Access menu and choose: Utilities Industry → Customer Service → Front Office/Customer Interaction Center → Customer Interaction Center Identify the business partner by entering the business partner number in the Part. field. From the Info action, choose Customer Overview. Do not exit this display.
(©) SAP AG
IUT110
9-61
2-3 2-3-1
Double click on the bill amount.. You will automatically branch to the print document display.
2-3-2
You can see the number of document line items on the Document Overview tab page.
2-3-3
On the Header Data tab page you can see the bill total in the Amount field.
2-3-4
Choose Document Overview. In the Rate column, you can see the rate used in the calculation. On the Document Line Items tab page, scroll to different document line items using F6 Previous Line and F7 Next Line. Note the different document line item types.
2-3-5
Choose the Header Data tab page. The Net Due Date field contains the due date for the bill.
2-4 2-4-1
True. Invoicing processes the meter reading results and the contract accounting data and, using this information, generates the bill and the new budget billing plan.
2-4-2
False. With each contract in a contract account, you can specify whether it is to be billed together with other contracts or billed separately.
2-4-3
True.
2-4-4
False. The posting date, as well as the document or system date, can be used as the baseline date for calculating the billing due date.
2-4-5
True.
2-4-6
True.
2-4-7
False. Depending on the budget billing procedure, the final invoice amount is determined by clearing the statistically posted budget billing amounts or by including the outstanding partial bills.
(©) SAP AG
IUT110
9-62
Energy Data Management
Contents: z Overview z Profile Header z Profile Allocation for Register z Point of delivery z Profile Values z Formula Profiles z Synthetic Profiles
¤ SAP AG 2003
(©) SAP AG
IUT110
10-1
Energy Data Management: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe functions and content of EDM z Describe the components that make up profiles z Explain how profiles are allocated to the master data
¤ SAP AG 2006
(©) SAP AG
IUT110
10-2
Energy Data Management: Business Scenario
z Values determined by automated meter reading for an interval meter should be copied to the system
¤ SAP AG 2003
(©) SAP AG
IUT110
10-3
Components of Energy Data Management Profile Management
Billing Spot price
Additional agreement: Spot delivery
John Smith
EDM ? Historic profiles ? Price profiles
kW
10 Park Avenue
60
New York Billing period 05.01. – 06.01.
30 10
On-Peak kWh
? Forecast profiles
Consumption Price Charge 100 kWh $0.25 $25.00
Off-Peak kWh
400 kWh
$0.10 $40.00
Spot kWh
100 kWh
$0.50 $50.00
Amount Due
$115.00
Agreed price
Settlement ¤ SAP AG 2009
Energy Data Management (EDM) allows you to manage consumption data that is measured in intervals (load profile and load shape), as well as the related business processes.
EDM enables you to bill load shapes using RTP (real-time pricing) and time-of-use rates.
EDM allows the settlement of all interval meters and points of delivery that are not measured by load shape: y Settlement processes y Amounts and charges y Procurement schedules and profiles
(©) SAP AG
IUT110
10-4
Structure of Energy Data Management
a Dat y e nt r
Consumption meter en
Da ta try
Real-TimePricing
EXPORT
Point of delivery
EDM
l
Derived load profiles
a gn Si
IMPORT
Interval Meter
ad lo
Do wn lo ad Si gn al
wn Do
Load profile mgmt
Auto.MR MR Auto. Auto. MR systems systems systems
Prelim. billing
Contract A/R & A/P
MD E
Do wn Up l oa Meter reading document Customer meter reading
l oa
d
d
MR data mgmt
Invoicing
Billing
Print
Scheduling control
Other modules
Data entry
EDIFACT
Device Management
Public network
¤ SAP AG 2009
(©) SAP AG
IUT110
10-5
Energy Data Management and Billing z Variant-based billing
Differentiation of various rate periods using registers
Consumption billing for each register (for each rate period) using billing rules of varying complexity
Cost estimates derived from basic formulas
High billing throughput
z Profile-based billing
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
¤ SAP AG 2009
(©) SAP AG
IUT110
10-6
Profile Header z Profile Type Historical profile, schedule profile, formula profile, forecast profile, synthetic profile, day profile z Consistency check group Determines the checks that are executed when profile values are imported z Replacement Value Group Determines the calculation of plausible values that are used instead of missing or implausible values z Validity period z Profile value category Amount, factor, quantity, demand, price, other z Interval length 5, 10, 15, 30, 60 minutes
¤ SAP AG 2006
Characteristics for profile values are determined in the header data of a profile.
Once the profile header has been saved, only the description, the consistency check group, the replacement value procedure group, and the authorization group can be changed.
(©) SAP AG
IUT110
10-7
Profile Allocation for Register
Business Business partner partner
Regional Regional structure structure
z This allocation is historical and role-based
Contract Contract account account
Contract Contract
z Profiles can be allocated to (logical) registers of interval meters
Connection Connection object object
z The role determines the profile's task for this register z Examples of roles are measurement and forecast
Installation Installation
Premise Premise
Device Device
Register Register
Measured Measured profile profile
¤ SAP AG 2006
(©) SAP AG
IUT110
10-8
Point of delivery
Business Business partner partner
Contract Contract account account
Contract Contract
Point Point of of delivery delivery
Installation Installation
Device Device
Register Register
z Point to which a utility service is supplied or to which a utility service can be determined for a customer z A point of delivery has one external identification number at any time (point of delivery description according to metering code, for example) z The point of delivery is used for communication in automatic data exchange z The point of delivery is used to exchange meter reading results Measured Measured Profile Profile
¤ SAP AG 2003
(©) SAP AG
IUT110
10-9
Import Profile Values For example: Siemens metering Fröschl Görlitz Interval meter
SAP Utilities /EDM
Download AMR system
Conversion
Signal Profile
Interface
PoD
Other market participant
EDI subsystem
EDI
Meter reading result
For example, MSCONS
¤ SAP AG 2009
(©) SAP AG
IUT110
10-10
Profile Values z A profile value is saved for every interval z At least one status is saved for every profile value z Multiple versions can be managed for every profile z Profile values can be displayed in table or in graphical form z Profile values can be changed individually or for certain periods of time z Profile values can be imported using BAPI or IDoc z An OLE (Excel) interface exists z Profile values can be displayed on the web
¤ SAP AG 2003
(©) SAP AG
IUT110
10-11
1/4h demand ( kW)
Formula Profiles
100 90 80 70 60 50 40 30 20
17.01. 199 5
18.01. 199 5
19.01. 199 5
20.01. 1995
12:00
00:00
12:00
00:00
12:00
00:00
12:00
00:00
0
21.01. 1995
EDM
PoD
TL total load UI
NL net losses
+ +
request
request
SL street lights etc.
request
UI
rest load RL = TL - NL - SL - MC request
+ UI
scheduling
+ +
MC measured customers
UI
+
elementary load profile automatic
aggregated load profile
UI
formula-based profile
¤ SAP AG 2009
Formula profiles are used to calculate profile values on the basis of a functional connection.
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 added.
(©) SAP AG
IUT110
10-12
Synthetic Profiles Residential customer
Summer
Working day
Weekend
Winter
Working day
Weekend Winter
Sun 03.28
Mon 03.29
24:00
00:00
24:00
00:00
24:00
00:00
24:00
Summer
Working day
Weekend
00:00
Tue 03.30
Wed 03.31
Working day
Thu 04.01
Fri 04.02
Weekend
Sat 04.03
Sun 04.04
Working day
Mon 04.05
Tue 04.06
¤ SAP AG 2009
Synthetic profiles are used where an interval measurement does not take place.
Synthetic profiles are profiles whose values are generated based on predefined periods (defined using blocks of days and seasons) and the allocated day or annual profiles.
Synthetic profiles are used for classifying customers or customer groups.
Synthetic profiles are allocated at installation level.
(©) SAP AG
IUT110
10-13
Energy Data Management: Summary
You are now able to: z Describe the components that make up profiles z Explain how profiles are allocated to the master data
¤ SAP AG 2006
(©) SAP AG
IUT110
10-14
Exercises Unit: Energy Data Management Topic: Profile Management After completing these exercises, you will be able to: • Display profiles • Determine and interpret profiles Gain an overview of the EDM component.
1-1
Display the profile header allocated to business partner TR0101A0##. 1-1-1
What is the status of the profile header? ____________________________________________________________
1-1-2
What is the profile type of the profile header? ____________________________________________________________
1-2
Which role has been allocated to the profile of business partner TR0101A0##. To which device is the profile allocated? ____________________________________________________________
1-3
Display the profile values. What is the highest profile value? Enter 10.01.YYYY - 10.31.YYYY as the selection criteria (YYYY = current year). Display the profile graphically. _________________________________________________________________
(©) SAP AG
IUT110
10-15
(©) SAP AG
IUT110
10-16
Solutions Unit: Energy Data Management Topic: Profile Management
1-1
Display the profile header allocated to business partner TR0101A0##. Go to the SAP Easy Access menu and choose: Utilities Industry Æ Energy Data Management Æ Profile Management Æ Profile Header Æ Display Enter the business partner and choose Continue. Double click on the profile. The profile header is now displayed on the right of the screen. 1-1-1
What is the status of the profile header? In the Status field, click on the icon
1-1-2
.
Which profile type is assigned? The historical profile type is allocated to the profile.
1-2
Which role is allocated to the profile for business partner TR0101A0##? To which device is the profile allocated? Go to the SAP Easy Access menu and choose: Utilities Industry Æ Energy Data Management Æ Profile Management Æ Profile Allocation Enter the business partner and choose Continue. Double-click on the profile. You can now see the allocated role on the right of the screen.
1-3
Display the profile values. What is the highest profile value? Enter 10.01.YYYY – 10.31.YYYY as the selection criteria (YYYY = current year). Display the profile graphically. Utilities Industry Æ Energy Data Management Æ Profile Management Æ Profile Values Enter the business partner and the selection date. Select the profile. The profile values now appear on the right of the screen. In the upper screen area, select the column containing the profile values and execute the sorting function . Display the values graphically by selecting the graphic icon.
(©) SAP AG
IUT110
10-17
(©) SAP AG
IUT110
10-18
Real-Time-Pricing
Contents: z RTP Overview z RTP Interface Structure z RTP Interface Components
¤ SAP AG 2009
(©) SAP AG
IUT110
11-1
Real-Time-Pricing: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe the Real-Time-Pricing interface and its components z Explain the connection of the RTP interface to SAP Utilities billing
¤ SAP AG 2009
(©) SAP AG
IUT110
11-2
Real-Time-Pricing: Business Scenario
z Values determined by automated meter reading for an interval meter should be billed in the system
¤ SAP AG 2009
(©) SAP AG
IUT110
11-3
RTP Overview
SAP Utilities
Customer/ contract data
Download
Signal
AMR system
Device manage ment
Interval meter
EDM
PoD (OBIS indicator)
Load shape
RTP Interface
Invoicing
Contract accounting
System EDI / XML
Billing
MSCONS
Scheduling control
Other modules
¤ SAP AG 2009
The RTP interface is the link between the following SAP Utilities components: y Energy Data Management (EDM) y Contract Billing (BI)
The RTP interface is used to prepare the profiles managed in EDM for billing.
For this purpose, the RTP interface need to be allocated to the rate at which an interval meter is billed.
(©) SAP AG
IUT110
11-4
RTP Interface
z Allows time series, such as load shapes, to be billed z Uses the load shape data directly from EDM z Is fully integrated with SAP Utilities Billing z Allows flexible modeling of nonresidential customer and major customer billing using interval reading z Is easily extendable (customer-specific formulas and result functions)
¤ SAP AG 2009
(©) SAP AG
IUT110
11-5
RTP Billing
z Period-related billing
Time-of-use group (on/off-peak rates)
Day groups (week day/weekend day)
Season groups (summer/winter)
z Use of a spot price or an index price z Determination of demand values (highest demand, for example) z Inclusion of other profiles for billing z Determination of consumption groups
¤ SAP AG 2009
(©) SAP AG
IUT110
11-6
RTP Billing Example
E01 Load shape: Quantity
A03 Over limit 2: Quantity E03 Limit 2: Quantity A02 Over limit 1: Quantity
A04 Over limit 1: Demand
E02 Limit 1: Quantity A01 To limit 1: Quantity
¤ SAP AG 2009
(©) SAP AG
IUT110
11-7
RTP Billing Data Model Individual RTP interface PI
RTP Interface Rate cat. P1
Installation
Rates
Rate det.
VarProg.
...
Installation structure
P2
P12
Rate type Logical register Billing schema Rate 1 Profile
Step 1 Step 2
VarProg.
Operand values
Example: Quantity x price 1000kWh, 0.25 UNI Comparison of two demands 400kW, 300kW
Rate n Step 1 ¤ SAP AG 2009
(©) SAP AG
IUT110
11-8
RTP Interface Structure I z RTP formula z RTP components z Result parameters
RTP interface EDM repository
Formula
ƒ
RTP component "On-Off" component "Without rate period" component
Result parameter On-peak cons.
On-peak cons. Off-peak cons.
Off-peak cons.
Max. demand
Max. demand
¤ SAP AG 2009
The RTP formula contains a calculation algorithm based on profiles. Profiles in turn are the results of a formula calculation.
The RTP component defines the structure of parameter allocations in the RTP interface.
The result parameters are allocated to operand categories. The result parameters supply the operands in the RTP rate in SAP Utilities billing.
(©) SAP AG
IUT110
11-9
RTP Interface Structure II
Season type Day type Day time type Component control: DD.MM.YYYY.HH.MM - DD.MM.YYYY.HH.MM
Components
Profile
Pr1 = x1
In
x1
Formula
Out
yn = f(x1,x2,...
y1 y2
xm)
Active/Inactive
Components
Result function
Facts
e1 < sum > y1 -> e1;e2 y2 -> e3
e2 < sum >
quantity = e1;e2 = = e3 demand
e3 < peak >
EDM profile management
RTP interface
IS-U billing
Legend x: y: e: quantity:
Input parameter Output parameters Result parameter consumption
pr: profile f: formula demand: demand
¤ SAP AG 2009
The RTP component defines the structure of parameter allocations. y Example: You want to make parameter allocations separately according to on-peak and off-peak rate times. In order to do this, you define a time of use group that divides the day into on-peak and off-peak times.
(©) SAP AG
IUT110
11-10
Input Parameters Components Summer Weekend On-peak Off-peak Workday On-peak Off-peak Winter Weekend On-peak Off-peak Workday On-peak Off-peak
x1 ¤ SAP AG 2003
Input parameters are defined in the RTP interface. Profiles are allocated to the input parameters in the individual RTP components. The values from these profiles are used for executing formulas. Profiles can be allocated to input parameters according to the structure that has been defined in the RTP component.
(©) SAP AG
IUT110
11-11
Formula
Formula definition Input
Output
Formula
x1
y1
Profile
Virtual Profile
x2 Limit
yn = f(x1,x2, …
xn )
y2 Virtual
1
Profile
y3
x3 Limit
Virtual
2
Profile
Function Module ¤ SAP AG 2009
The formula is the basis of profile calculation on which the RTP calculations are based.
The formula is allocated to an RTP interface.
It contains a fixed number of input and output parameters depending on the formula.
(©) SAP AG
IUT110
11-12
Result Components
y1
Summer Weekend On-peak Off-peak Workday On-peak
e1
Off-peak Winter Weekend
e2
On-peak Off-peak Workday On-peak Off-peak
Result e1 e2 e3
Function sum average peak
Op. Cat. QUANT DEMAND DEMAND
¤ SAP AG 2003
(©) SAP AG
IUT110
11-13
Transfer of Results to RTP Operand
y1 result
function
Op. Cat.
e1 e2 e3
sum average peak
QUANT DEMAND DEMAND
IS-U IS-U billing billing schema: schema: Rate: ON_OFF_PEAK RegOperand RTP-Interface
ON_OFF_PEAK
001
....
...
...
007
QUANTI01
ONPEAKCON
008
QUANTI01
OFFPEAKCON ...
...
...
...
Pricing for ON Peak consumption Pricing for OFF Peak consumption
y1 = Output parameter e1 = Event parameter ¤ SAP AG 2003
Result parameters can be allocated to an output parameter.
Result parameters describe the result of an RTP interface once it has been executed. The values of a result parameter are defined using the result function.
The discrete result parameter is used as an operand in the rate (by allocating it to an operand).
(©) SAP AG
IUT110
11-14
Real-Time-Pricing: Summary
z The Real-Time-Pricing interface is fully integrated with the SAP Utilities billing procedure. z It links energy data management (profile management) to the SAP Utilities Billing functions. z You can use the RTP interface to establish certain billing regulations flexibly (for example, billing of interval meters with special price agreements).
¤ SAP AG 2009
(©) SAP AG
IUT110
11-15
(©) SAP AG
IUT110
11-16
Budget Billing Plan
Contents: z Budget billing procedure z Determination and requirements of budget billing
¤ SAP AG 2009
(©) SAP AG
IUT110
12-1
Budget Billing Plan: Unit Objectives
At the end of this unit you will be able to: z Explain the difference between a budget billing plan and a payment plan z Create and change budget billing plans
¤ SAP AG 2009
(©) SAP AG
IUT110
12-2
Budget Billing Plan: Business Scenario
z A customer's consumption pattern has changed. z After adjusting the period consumption, you recalculate the budget billing plan.
¤ SAP AG 2009
Budget billing plans can be created automatically during the movein process, or manually in a standalone process.
(©) SAP AG
IUT110
12-3
Budget Billing Procedure: Overview
Budget Billing Procedure
Payment plan
Budget billing A down payment, which is cleared with the final invoice amount and is recalculated for the next period
SAP UT
Budget billing categories
Statistical posting with budget billing requirements
Actual debit entry with partial bill
Monthly bills for an agreed amount (fixed or variable), and clearing at the end of the period
Payment plan categories
Fixed amounts Budget billing plan
Variable amounts Average monthly plan
¤ SAP AG 2009
Payment plans are used typically in US scenarios, while budget billing plans are mostly used in nonUS scenarios.
(©) SAP AG
IUT110
12-4
Payment Plan z 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, another simulation is made for the next period. In addition, actual billing occurs monthly. The results of this billing are shown on the bill and cleared in the last month of the billing period.
z Average Monthly Billing Plan / Equalized Billing Plan
The customer is charged an average amount based on billings over the last 12 months (or less in the case of new customers). In addition, actual consumption is calculated monthly, and the results are printed on the bill. The amounts due for later months are calculated using the average of the previous months bills plus the current bill and the accumulated difference.
¤ SAP AG 2009
(©) SAP AG
IUT110
12-5
Budget Billing Plan Overview Clearing Print
Budget billing cycle
Due date determination
Budget Billing Plan
Amount limits Min. amount Amount rounding
Manual Amount adjustment calculation Automatic factor determination
Grouping of budget billing amounts from one billing period Allocation of budget billing amounts to individual contracts Display of accumulated and individual budget billing amounts Display of the open budget billing amounts Automatic and manual determination of the budget billing amount ¤ SAP AG 2009
(©) SAP AG
IUT110
12-6
Creating or Adjusting Budget Billing Plans z Business Processes
For move-in
For periodic billing
Extrapolation
For invoicing
Budget billing plan
z Amount Determination
Manual calculation
Automatic extrapolation
Due date Grouping of contracts Amount check
z Due Date of Budget Billing Amounts
Terms of payment from the contract account
¤ SAP AG 2009
Utility companies often only bill for their services at the end of a supply period (with annual consumption billing, for example).
Therefore, to maintain liquidity during the current period, budget billing amounts are billed by anticipating the total amount owed by the customer.
The budget billing plan defines the dates and size of the budget billing amounts and forms the basis for budget billing.
Budget billing plans are normally created automatically (during invoicing or move-in, for example). However, you can also create them 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.
(©) SAP AG
IUT110
12-7
Quantity-Based Extrapolation Actual meter reading
Next scheduled meter reading date from scheduling
2006 2006 01.11.
....
....
Billing period
....
....
....
....
01.08.
2007 2007 01.09.
....
....
....
....
....
....
01.14.
Budget billing period
Extrapolation of consumption using configured weighting procedure; billing simulation for this period
Distribution Distribution of of total total simulated simulated amount amount over the budget billing due dates over the budget billing due dates ¤ SAP AG 2006
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.
For this reason, ensure you have generated schedule records for the next billing period before you simulate billing.
(©) SAP AG
IUT110
12-8
Budget Billing Item
Process Budget Billing Amounts
Due date determination using terms of payment Scheduling using the portion
Budget Billing Request
Creation of Partial Bills
Generation of statistical posting documents that are cleared as down payments with the final bill amount
FI-CA Update
SAP UT
Statistical posting
Generation of partial bills with actual debit-entry that are cleared as down payments against the final bill amount Actual debit entry
FI-CA Update:
Statistical posting document
With items for each contract
With repetition items for each budget billing item
Documents only in customer account with receivable
Sales tax posting on payments
Sales tax posting on receivables
Actual debit-entry With items for each contract
¤ SAP AG 2009
The budget billing dates are determined from the portion valid for the contract and the parameter record. The following details are defined: y Length of the budget billing period (several months or one year) y Budget billing cycle, meaning that the scheduled dates are at regular intervals over the period (monthly or every few months)
The specifications from 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 billing items result from the budget billing dates and the payment conditions in the contract account.
When requesting budget billing amounts, a debit entry can be generated in Contract Accounts Receivable and Payable or a statistical posting (budget billing amounts that do not affect the general ledger) can be carried out.
(©) SAP AG
IUT110
12-9
Budget Billing Plan: Summary
You are now able to: z Explain the difference between a budget billing plan and a payment plan z Create and change budget billing plans
¤ SAP AG 2009
(©) SAP AG
IUT110
12-10
Contract Accounts Receivable and Payable
Contents: z Overview z Documents z Account display z Payments z Returns z Dunning z Installment plan
¤ SAP AG 2009
(©) SAP AG
IUT110
13-1
Contract Accounts Receivable and Payable: Unit Objectives
At the conclusion of this unit, you will be able to: z Describe the document structure in contract accounts receivable and payable z Provide information on customer accounts z Explain some common business transactions in Contract Accounts Receivable and Payable and perform them in the system.
¤ SAP AG 2003
(©) SAP AG
IUT110
13-2
Contract Accounts Receivable and Payable: Business Scenario
z Document structure and posting z Display account balance z Payment for account balance z Process returns and post charges z Dunning for the contract account z Arrangement of installment plan
¤ SAP AG 2003
(©) SAP AG
IUT110
13-3
Contract Accounts Receivable and Payable: Overview
z Overview
z Documents z Account display z Payments z Returns z Dunning z Installment plan
¤ SAP AG 2009
(©) SAP AG
IUT110
13-4
Contract Accounts Receivable and Payable: Integration Business Information Warehouse
CO-PA SAP UT Invoicing
CO FI-GL
SD Invoicing
FI-CA Customer Relationship Management
Ext. Billing Systems
TR-CM
FSCM
¤ SAP AG 2009
You can transfer SD invoices directly to FI-CA subledger accounting. Under certain conditions you can also post SD invoices as invoicing requests, together with an IS-U invoice.
Print documents from external billing systems can be imported to FI-CA using a standardized IDoc interface and processed there.
Postings in FI-CA trigger an immediate posting in Cash Management (TR-CM).
Postings in FI-CA are transferred regularly (for example, daily) to the general ledger.
Additional account assignments from cost accounting are included, and forwarded to the account assignment objects. The component CO-PA is supplied with the necessary information from the ISU invoicing component for different update types. This information is transferred regularly using transfer reports that are triggered in FI-CA or IS-U.
The integration in Financial Supply Chain Management (FSCM) improves customer-oriented processes. Business partners can use the Biller Direct component to check bills and initiate payments (as well as other functions) on the Internet. The Credit Management component allows companies to create and check credit profiles.
FSCM was integrated with ERP 2005, which means that a separate instance is no longer required.
Extractors for open and cleared FI-CA items, and for other debit-relevant information, were developed for the Business Information Warehouse (BW).
Integration in Customer Relationship Management (CRM) makes it possible to efficiently process transactions in the Call Center.
(©) SAP AG
IUT110
13-5
Contract Accounts Receivable and Payable and FI-CA
z Contract Accounts Receivable and Payable is the FI-CA component (Financial Accounting-Contract Accounts Receivable and Payable) z FI-CA is designed and executed as a subledger for customer processing
¤ SAP AG 2009
(©) SAP AG
IUT110
13-6
FI-CA Open Architecture
SAP TEL
SAP UT
FI-CA IS-IS/CD
Data Exchange
Other
Open items Posting information Information Business processes, Workflow
¤ SAP AG 2009
IS-IS-CD: Insurance Industry Component: Industry Specific Component - Insurance - Collections/Disbursements
IS-T: Industry Specific Component Telecommunications
Other industries: Public Sector and Media
As of Release 4.64, the component FI-CAx has been delivered as an industry-independent solution of Financial Supply Chain Management.
(©) SAP AG
IUT110
13-7
FI-CA Special Features 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 (totals records)
Convenient processing of business transactions Documents are assigned to business partners and contract accounts (and contracts - depending on the industry) Standard processes (such as posting or paying) can be changed without making any modifications Integration in the SAP Customer Relationship Management (CRM) and SAP Business Intelligence solutions
¤ SAP AG 2009
(©) SAP AG
IUT110
13-8
FI-CA Central Objects z 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.
z 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-specific).
z Contract (industry-specific)
FI-CA
BP Account
Account
z Documents and items Contract Contract
Contract
IS-U ¤ SAP AG 2009
(©) SAP AG
IUT110
13-9
FI-CA Business Transactions
Payment (cash payer, direct debit payer)
OP (due)
Installm.plan
- Item (cleared)
General ledger
Several OPs
Interest
Charges
New due item
Original OP / Charges
OP (not due)
Original OP
Invoicing
Account display
Time
Doubtful entry Ind. val. adj. Write Off
Interest calc. Dunning
Collection Agency
Archiving
Deferral Returns ¤ SAP AG 2009
Archiving is only executed for cleared items.
General ledger transfer occurs at regularly scheduled intervals – defined by the customer.
(©) SAP AG
IUT110
13-10
Contract Accounts Receivable and Payable: Documents
z Overview
z Documents z Account display z Payments z Returns z Dunning z Installment plan
¤ SAP AG 2009
(©) SAP AG
IUT110
13-11
Documents: Aims
At the conclusion of this topic, you will be able to: z Explain the document structure in contract accounts receivable and payable z Post receivables items
¤ SAP AG 2003
(©) SAP AG
IUT110
13-12
Documents: Introduction
z If business processes are not integrated with SA Utilities or SD, or automatically connected to Contract Accounts Receivable and Payable by an interface, individual postings can be entered into the system as manual documents. z Examples include rent receivables, lease receivables, as well as receivables for an energy consultant.
¤ SAP AG 2008
(©) SAP AG
IUT110
13-13
Documents: Business Scenario
z Document structure and posting z Display account balance z Payment for account balance z Process returns and post charges z Dunning for the contract account z Arrangement of installment plan
¤ SAP AG 2003
(©) SAP AG
IUT110
13-14
Documents in Contract Accounts Receivable and Payable
Document header 1:N
1:N
G/L G/L G/Litems G/Litems items items
Business partner Business partner Business items partner items Business partner items items
¤ SAP AG 2009
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, data for sales tax, as well as any additional account assignments for cost accounting
(©) SAP AG
IUT110
13-15
Document Header Data
General • Document date • Document type • Document number
Reference and currency • Reference • Currency • Conversion rules
Additional data • Reversal document • Reversed with • Returns reason
General ledger • Posting date • Reconciliation key • Single document
Management data
Document header
• Created by • Date entered • Origin
¤ SAP AG 2009
As with all SAP transactions and documents, the userid of the creator and the date/time of creation are stored.
The origin key is an internal identifier which designates the process which created the document.
Origin keys are provided by SAP and are not changeable.
If the document is reversed, the original document is updated.
(©) SAP AG
IUT110
13-16
Header Data: General Document Data
General • Document date • Document type • Document number
Document header
¤ SAP AG 2003
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 preset externally when the document is entered. • The type of number assignment is decided by the document type entered in the document header. It specifies: - A number range from which the document number is chosen. - Whether the number is entered automatically or manually.
(©) SAP AG
IUT110
13-17
Document Header: Reference and Currency
General • Document date • Document type • Document number
Reference and currency • Reference • Currency • Conversion rules
Document header
¤ SAP AG 2003
The reference document number can contain the business partner document number or the number of the causal print document from IS-U Invoicing and can be used as search criteria. In correspondence, the reference document number is sometimes printed in place of the document number.
The transaction currency is the key of the currency, in which the document 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.
(©) SAP AG
IUT110
13-18
Document Header: Link to General Ledger Accounting
General • Document date • Document type • Document number
Reference and currency • Reference • Currency • Conversion rules
Document header
General ledger • Posting date • Reconciliation key • Single document
¤ SAP AG 2003
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 were written for transfer to downstream accounting. The key is entered as an external reference in the document header field "reference key" of the G/L account documents the summary records are transferred to the general ledger. 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.
(©) SAP AG
IUT110
13-19
Data on Business Partner Item
Business partner Contract account Contract Company code Process
Due dates: Net/Cash discount/deferral Clearing data Dunning data/ Interest calculation
Set automatically
Amounts Payment data
Business partner items Mandatory data entries
Repetition specifications
Cash management and forecast data
Additional data -Item text -Grouping -Period key Alternative partner for payments
Optional data entries
¤ SAP AG 2003
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 (incoming payment).
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.
Repetition specifications save memory space required for repetitive document items that only differ according to when they are due, for example, installment plan or budget billing plan items. The repetition items appear as 'normal' in the account balance display.
Not every document needs a business partner. One example of this is a normal payment that leads to clearing of the affected receivables lines. In this case, only a document header and general ledger item is written for the payment, since the data relevant for the account assignment comes from the receivables lines that linked the payment.
(©) SAP AG
IUT110
13-20
Data on G/L Account Item
General ledger: company code, G/L account Amounts and tax code
Account assignment for subsequent accounting
G/L items
¤ SAP AG 2003
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 is the decisive date for displaying daily financial status and liquidity forecast in cash management.
A planning level is allocated in the document item of Contract Accounts Receivable and Payable for updating in cash management. The planning level is valuated in the liquidity forecast.
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.
In some cases FI-CA documents do not contain G/L items. These are statistical documents. Statistical posting simplifies the administration of doubtful receivables 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. In the case of statistical budget billing amounts, the value added tax is also due with the first payment of the budget billing amount and, as a result, when the receivable is posted in the general ledger. Dunning charges are another example that are generally not paid.
(©) SAP AG
IUT110
13-21
Data Entry: Header Data and Default Values
General • Document date • Document type • Document number
Reference and currency • Reference • Currency • Conversion rules
Document header
• Clearing reason • Entry variants • Company code • Screen variants • Calculate taxes • Jurisdiction code • Net receivables
General ledger • Posting date • Reconciliation key • Single document
General data
Entry control
¤ SAP AG 2003
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. You can define a default value in Customizing.
(©) SAP AG
IUT110
13-22
Data Entry: Items z Receivables / credit memos Business partner BP1 Contract account CA 1 Amount $ 100 Business partner BP2 Contract account CA2 Amount $ 150
Business partner BP3 Contract account CA3 Amount $ 250
z Automatic determination of general ledger accounts and tax accounts using transactions z Classification using document type z Automatic determination of due dates using terms of payment in the contract account z Receivables or credit can be cleared immediately
¤ SAP AG 2003
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 put into the receivables and revenue lines. The same occurs for tax codes and tax accounts.
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 with specification of a start date at monthly or daily intervals (for example, for distributing a receivable amongst payment plans).
The document items of a document do not have to belong to the same business partner. Posting to different business partner is possible.
(©) SAP AG
IUT110
13-23
Transactions in Contract Accounts Receivable and Payable
Transactions explain the business transaction on which the posting of a line item is based.
z A transaction is a combination of main and sub-transactions z Texts for the transactions explain the business transaction and are available for correspondence z Transactions control FI-CA account determination z Transactions control FI-CA value added tax determination z FI-CA uses internal main and sub-transactions, which are assigned internally by various FI-CA business processes. The transactions also control these business processes. ¤ SAP AG 2003
Example in IS-U for • Main transaction: periodic billing • Sub-transaction: receivable from energy charge
(©) SAP AG
IUT110
13-24
Examples of Transactions Main transaction
Sub-transaction
Billing
Energy charge receivable Energy charge credit Clearing price receivable Clearing price credit Service charge receivable Service charge credit
Charges
Statistical dunning charge Dunning charge Charge for items in installment plan
¤ SAP AG 2003
(©) SAP AG
IUT110
13-25
Transfer to General Ledger Accounting
FI-CA documents 1. Doc.:
Amount Net Tax 2. Doc.: Amount Net Tax Reconciliation key:
Document posting
$ 580 $ 500 $ 80 $ 116 $ 100 $ 16 98126ISU01
Summary Record D C C
140000 800000 175001
$ 696 $ 600 $ 96
FI documents
Generate postings
Reconciliation key 98126ISU01
40 140000 696,-50 800000 600,-50 175001 96,-Reference key 98126ISU01 Reference transaction FKKSU
¤ SAP AG 2003
The reconciliation key is the key used to record totals records.
The reference key is derived from the reconciliation key, stored in the the general ledger document header and can be used to trace the original subledger documents for general ledger documents.
(©) SAP AG
IUT110
13-26
Summary Record z Transfer unit for postings from Contract Accounts Receivable and Payable to financial accounting z 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.
z Examples for summarization criteria are:
Company code and date
Debit/credit indicator
General ledger account
Currency
Criteria of subsequent systems or components (cost accounting)
¤ SAP AG 2003
(©) SAP AG
IUT110
13-27
Documents: Summary I
z The most important data in the document header is:
Document number
Reconciliation key
Posting date
Document date
z 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
z The G/L account item contains information on the corresponding G/L accounts and additional account assignments. ¤ SAP AG 2009
(©) SAP AG
IUT110
13-28
Documents: Summary II
z If necessary, documents can be posted manually in Contract Accounts Receivable and Payable. z This is possible for both receivables and credit memos. z An item can be entered:
individually in detail, or
in a list
¤ SAP AG 2009
(©) SAP AG
IUT110
13-29
Contract Accounts Receivable and Payable: Account Display
z Overview z Documents
z Account display z Payments z Returns z Dunning z Deferral and installment plans
¤ SAP AG 2009
(©) SAP AG
IUT110
13-30
Account Display: Objectives
At the conclusion of this topic, you will be able to: z Analyze the development of a contract account z Provide information on the items of a contract account z Use the navigation options in the account balance display
¤ SAP AG 2003
(©) SAP AG
IUT110
13-31
Account Display: Introduction
z Utility companies often have to deal with large numbers of items due to the large number of customers and budget billing payments z Information on contract accounts is given quickly and comprehensively z In addition to this, there are different displays that can be configured individually z Different display formats can be used depending on the tasks of the clerk (accounting, dunning, for example) z Individual selection of display variants can be defined in the user parameters
¤ SAP AG 2006
(©) SAP AG
IUT110
13-32
Account Display: Business Scenario
z Document structure and posting z Display account balance z Payment for account balance z Process returns and post charges z Dunning for the contract account z Arrangement of installment plan
¤ SAP AG 2009
(©) SAP AG
IUT110
13-33
Account Display: Initial Screen z Selections: - Business partner, contract account, contract Company code, installment plan, collective bill, reference - List category for restricting the items to be displayed according to "status“. Examples: All open, due, or statistical items - User-specific selections z List representation defines the line structure z Sorting is possible
¤ SAP AG 2003
(©) SAP AG
IUT110
13-34
Account Display: List Category z The list category determines which items are selected for the account display (such as open items or down payment requests). z The list category enables you to preconfigure frequently used selections. z As an alternative to selecting items using list categories, you can select:
A preset standard, for example, all open, non-statistical items
Define specific items in the detail selection
z Even if a list category is used, the selection can still be changed using "detail". This change is not saved, rather only used for the current display.
¤ SAP AG 2003
(©) SAP AG
IUT110
13-35
Account Display: Line Layout z Determines which fields of a document are included in the account display. z Different line structure variants can be selected in the account display. It is also possible to totalize and find values using particular criteria. z The same output list can be viewed in a number of ways. z Depending on the cursor position, you can branch to the detailed view of the document items, master data and the posting basis
¤ SAP AG 2003
(©) SAP AG
IUT110
13-36
Account Display: Balance Variant z Determines which balance groups will be displayed in the balance grid. z Balance groups are only shown when they contain values . Balance categories and balance grid are assigned to balance groups. z The balance grid enables receivable display in aging buckets. z Balance variants and balances are used in SAP CRM to display open items within the account display view.
¤ SAP AG 2009
Event 1299 controls the calculation of balances.
(©) SAP AG
IUT110
13-37
Account Display: Navigating in the Document Display Header
Business Partner item list
G/L item list
Overview
Detail screen of business of business partner items
Detail screen of G/L items
¤ SAP AG 2003
It is possible to return to the header display from any screen.
(©) SAP AG
IUT110
13-38
Account Display: Navigation and Functions
Document
Payment data
Display Change Reverse Clearing back Installment plan Budget billing plan Histories ...
From payment run From payment lot From returns document From repayment request Payment use
Basic list Account
Master data
Mass change Account maintenance Installment plans Budget billing plans Dunning notices Creditworthiness Partner locks
Business partner - Change contract account - Change contract
¤ SAP AG 2003
The agent can call up all debit processes with changing transactions.
(©) SAP AG
IUT110
13-39
Account Display: Summary I
z Variable item selection
All items / open items / cleared items (with / without payments)
Statistical items (all / budget billing plan / charges /...)
User-specific selection conditions (by due date / by transaction)
z Variable display
Line layout variants
User-defined account display
¤ SAP AG 2009
(©) SAP AG
IUT110
13-40
Account Display: Summary II
z Immediate access to environment data
Document
Business partner / contract account / contract
Payment use
Original receivables for installment plan items
Dunning history
...
z Sort and summary functions within the account display
¤ SAP AG 2009
(©) SAP AG
IUT110
13-41
Contract Accounts Receivable and Payable: Payments
z Overview z Documents z Account display
z Payments z Returns z Dunning z Installment plan
¤ SAP AG 2009
(©) SAP AG
IUT110
13-42
Payment Run: Objectives
At the conclusion of this topic, you will be able to: z Explain the processing steps of a payment lot z Post payments using a payment lot z Post payments at cash desk
¤ SAP AG 2003
(©) SAP AG
IUT110
13-43
Payments: Introduction
z Utility companies have to deal with large numbers of incoming payments in a reliable and efficient manner. z Payment flow reaches the utility company in various ways. These include data medium exchange, automatically read documents and other documents z Background and dialog processes are provided for processing payments, depending on the situation
¤ SAP AG 2006
(©) SAP AG
IUT110
13-44
Payment Run: Business Scenario
z Document structure and posting z Display account balance z Payment for account balance z Process returns and post charges z Dunning for the contract account z Arrangement of installment plan
¤ SAP AG 2003
(©) SAP AG
IUT110
13-45
Automatic and Manual Payments
z Automatic incoming payments
z Payment lot z Payment order lot
z Collection procedure
z Check lot
z Credit repayment z Returns
z Credit card lot Automatic
Manual
z Payment at cash desk z Returns lot
¤ SAP AG 2009
Automatic incoming payment: Incoming payment data from previous systems, financial institutions, or agencies is processed in payment lots. The system automatically creates a payment posting for the corresponding business partner. Payments are automatically allocated to one or more receivables items. If an incoming payment cannot be allocated to an item, it is possible to post an account at contract account level. Manual post-processing in the clarification worklist is also possible.
Collection procedure Payments are handled by collection or direct debit from financial institutes or credit card companies and the corresponding output media are created.
Credit repayment: Credit is automatically repaid via check or bank transfer, and the corresponding output media are created.
Returns processing Automatic returns processing with workflow link is provided for returned payments from financial institutions and credit card companies, as well as for returned incoming checks.
Payments fall into two categories – customer initiated (check mailed, etc) and company initiated (direct debit, etc).
Company initiated payments (incoming and outgoing) utilize payment method assigned at account or item level, and generate payment media to facailitate communication with banking institutions or check printing.
(©) SAP AG
IUT110
13-46
Payment Lot z The payment lot stores data from external payments. z Payment data is stored in a lot if:
It has the same source
It is to be processed together
z Data for a group of incoming checks is stored in a payment lot. This type of lot is accordingly called a check lot. z Bank transfers and/or debit memos that were received are extracted from an account statement and stored in a payment lot.
¤ SAP AG 2009
Customer initiated payments are usually processed with the various lot functions (Payment Lot, Check Lot, etc).
Lots group payments which are received and processed together.
(©) SAP AG
IUT110
13-47
Payment Lot: Structure I
Header entry
z Data is saved in the payment lot header if:
It applies to the entire lot
It is used as a default value for items
¤ SAP AG 2003
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
(©) SAP AG
IUT110
13-48
Payment Lot: Structure II
Header Entry
z Data is saved in the payment lot header if:
It applies to the entire lot
It is used as a default value for items
z An item is a payment with: Item 1 Item 2
Amount
Specifications for selection of receivables to be cleared
¤ SAP AG 2003
(©) SAP AG
IUT110
13-49
Payment Lot: Processing Steps New payment lot
Create
Close
Post
Payment lot complete
Postprocessing
Change
z 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.
¤ SAP AG 2009
Payment lots are typically processed automatically via file upload – but can be processed manually.
FPB3 – report RFKKZE00 - is used to generate payment lot from file.
(©) SAP AG
IUT110
13-50
Payment Lot: Create New payment lot
Create
Close
Post
Payment lot complete
z A payment lot can be created:
In dialog mode (for example a check lot)
By program (for example an incoming bank transfer lot)
z The following is specified:
Bank clearing account
Reconciliation key
Header data for the payment lot
Specifications for payment documents, selection categories and line layout of individual items to be entered
¤ SAP AG 2003
Default values on the header screen: • The actual date is proposed. • 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. • Select the bank clearing account to be posted.
(©) SAP AG
IUT110
13-51
Payment Lot: Create Items New payment lot
Create
Close
Post
Payment lot complete
z The essential entries are:
Amount
Payment use via selection category and selection value for choosing open items, which are cleared by payment.
z Selection categories are one character abbreviations that are defined in Customizing.
These include: G for business partner, K for contract account, V for contract
¤ SAP AG 2003
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.
The Details button branches to the detailed view of a 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.
(©) SAP AG
IUT110
13-52
Payment Lot: Change New payment lot
Create
Close
Post
Payment lot complete
Change
z Items can be deleted and added as long as the payment lot is not closed. z Data on items that have already been entered can also be corrected. z Interrupted entry of a payment lot can be resumed using this function.
¤ SAP AG 2003
(©) SAP AG
IUT110
13-53
Payment Lot: Close New payment lot
Create
Close
Post
Payment lot complete
z Closing a payment lot means that adding or deleting items is no longer possible. z Corrections can still be made on the payment lot items after closing. You can also re-open a lot z Posting cannot begin until a lot is closed.
¤ SAP AG 2003
(©) SAP AG
IUT110
13-54
Payment Lot: Post New payment lot
Create
Close
Post
Payment lot complete
z Postings can either be dealt with in dialog mode or in a background process (typical for mass data). z Postings to contract accounts including payment use with:
Clearing of open items and/or
Generation of payments on account
z Posting to an interim account if the payment use is unclear z A check deposit list can be printed for check lots
¤ SAP AG 2003
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 (optional). The document number of the check deposit posting is noted in the payment lot header. • For other lots: One posting of bank clearing 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 items - Postings on account - Expense/revenue (payment difference) - Generation of receivables (charges, interest).
(©) SAP AG
IUT110
13-55
Automatic Clearing: Process
z Determination of the amount available for clearing z Determination of the selection criteria for open items z Open item selection z Conversion of item currency to clearing currency z Distribution of clearing amount to open items (clearing control) z Generation of document items (such as cash discounts, charges, down payments) caused by clearing z Posting of the payment document and noting the clearing information in the cleared items
¤ SAP AG 2003
(©) SAP AG
IUT110
13-56
Payment Lot: Postprocessing New payment lot
Create
Close
Post
Payment lot complete
Postprocessing
If automatic allocation was not possible: z Clarification of payment use and transfer from interim account to a contract account in post processing z Correction of payment items (such as selection specifications) and restart of postings for selected items z Manual posting and clearing selected items z Generation of a repayment request if the payment use cannot be determined
¤ SAP AG 2003
(©) SAP AG
IUT110
13-57
Cash journal
z Cash structure z Automatic processes z Special functions z Role concepts z Evaluations
¤ SAP AG 2003
You can store your company's cash structure in the cash journal. The cash structure includes the company cash desks in individual subsidiaries and forms the master data (two-level hierarchy) as prerequisite for the cash journal.
The cash journal offers further functionalities: • Automatic processes - Default values: Company code, clearing account and lots that have already been created are proposed according to payment category. This is also the case for cash structure allocation. - Create lot and close • Special functions - Deposits and withdrawals as G/L account postings - Transfer persons responsible (only makes sense when using role concept) - Closing cash desk • Role concept (head of subsidiary, cashier with special authorization, cashier) • Evaluations can be carried out at the moment using the cash balance or historically (for each subsidiary, cash desk, user...)
(©) SAP AG
IUT110
13-58
Payment at cash desk Deutsche Bank Pay the bear er
CurrencyAmount
€
- four hundred
- 400,-
Amount in words
Red Cross
New York 1.4.1996
ON Or the hol der
City
Date Sign ature Th e pr in te d c hec k te xt mu st not be alt er ed i n a ny w ay.
Check no.
00000150900
X
Accou nt no.
X
Amou nt
X
12131400
Sort code
X Text
67291500 11
Do not write i n or stam p this field.
Business partner Contract account
Contract account
Post Post directly directly
Contract Document number
Post Post in in dialog dialog
Net due date Payment form no.
Payment Payment posting posting
Check deposit list
Receipt
¤ SAP AG 2003
The cash desk is integrated in the cash journal. This means that all incoming and outgoing payments are posted using the cash desk. You can navigate directly from the cash journal to the cash desk and from the cash desk to the cash journal. The system transfers the cash desk allocated to an agent and other settings (determined by the system or made by the user) to the cash desk. If you use the transaction cash journal, you cannot call the cash desk transaction directly.
If the cash journal is deactivated, you can only use the cash desk function.
Within the cash desk function, payments can be directly allocated to open items for a business partner.
You can use a payment proposal from clearing control or assign the payment manually.
A distinction is made between cash payments and payment by check or credit card. Incoming and outgoing payments can also be processed.
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.
(©) SAP AG
IUT110
13-59
Clearing: Dialog Processing z 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 are allocated to the individual items.
z The clearing can be posted if the difference:
Is zero (green light appears)
Is within a predefined tolerance limit (yellow light appears)
¤ SAP AG 2003
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 summarization of items in the display can be switched on and off. The line structure (information displayed on open items) can be varied. You can hide or display cash discount fields as well as display posting and clearing amounts as net or gross. You can change the currency that is displayed.
(©) SAP AG
IUT110
13-60
Payments: Summary
z Payment can be handled automatically and manually in Contract Accounts Receivable and Payable. z Payments are processed:
In payment lots
At the cash desk
z In clearing control, you can create detailed specifications for automatically clearing items, which can be changed during processing in dialog mode.
¤ SAP AG 2003
(©) SAP AG
IUT110
13-61
Contract Accounts Receivable and Payable: Returns
z Overview z Documents z Account display z Payments
z Returns z Dunning z Installment plan
¤ SAP AG 2009
(©) SAP AG
IUT110
13-62
Returns: Objectives
At the conclusion of this topic, you will be able to: z Describe returns processing z Post a return
¤ SAP AG 2003
(©) SAP AG
IUT110
13-63
Returns: Introduction
z Utility companies must deal with a large number of incoming and outgoing payments. z A certain percentage of these cannot be successfully processed because the account is incorrect, closed, or not covered z The additional workload is kept as low as possible by:
Reversing payment to the account
Passing on charges
Triggering subsequent activities such as correspondence or re-posting after the payment method has been locked for a limited period
¤ SAP AG 2006
(©) SAP AG
IUT110
13-64
Returns: Business Scenario
z Document structure and posting z Display account balance z Payment for account balance z Process returns and post charges z Dunning for the contract account z Arrangement of installment plan
¤ SAP AG 2003
(©) SAP AG
IUT110
13-65
Returns: Influencing Factors
Customer creditworthiness and tolerance group
Returns reason
Return category
Number of returns
Returns
Return amount
History
¤ SAP AG 2003
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).
Company-specific returns reasons can be allocated bank-specific returns reasons.
A business partner's creditworthiness provides information on his or her payment behavior. The creditworthiness value is made up of a manual and an automatic value. The automatic creditworthiness value is determined by multiplying the credit numbers from credit-relevant processes (for example dunning, returns) with the time-dependent credit rating and adding the results. Creditworthiness is then calculated using the following formula: Creditworthiness = automatic credit worthiness value x percentage credit factor + manual creditworthiness
History Maximum number of days that have passed since an event before the event can be included in the analysis of the returns history. • The return amount is important for: -
Determining bank charges (the system interprets the difference between the return amount of the house bank and the original paid amount as a charge, and posts it accordingly)
-
Calculating the company's graduated charges for processing returns
(©) SAP AG
IUT110
13-66
Returns: Configuration Activities
Correspondence
Pass on charges with/without tax
Incoming payment method
Returns Calculate lot charges
Post charges statistically
Payment block reasons Deferral days
Return amount Dunning block - Contract account - Items
¤ SAP AG 2003
Pass on bank charges: Means that the bank passes on the returns charges to the business partner or the accompanying contract account. If this is not the case, these charges are paid by the utility company.
Calculation of lot charge Means 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.
(©) SAP AG
IUT110
13-67
Returns Lot: Processing Steps New returns lot
Create
Close
Post
Returns lot complete
Postprocessing
Change
z Returns lot processing contains the following steps:
Create
Change (optional)
Close
Post
Postprocessing (for clarification and errors): Postprocessing is necessary if postings could not be carried out.
¤ SAP AG 2009
Returns lots are typically processed automatically via file upload – but can be processed manually.
FPB5 – report RFKKRL00 - is used to generate payment lot from file.
(©) SAP AG
IUT110
13-68
Returns Lot: Create New returns lot
Create
Close
Post
Returns lot complete
z A returns lot can be created:
Using a program (such as returns lot with DTAUS)
In dialog mode
z The following must be specified:
Reconciliation key
Whether the amount contains charges
Whether the amount contains taxes
Posting type (taking back payment, new receivables)
¤ SAP AG 2003
Default values on the header screen: •
The current date is defined.
•
The last values entered (if available) are inserted automatically for the currency and business area.
•
Document type, clearing reason, company code and selection category are stored in Customizing as default
(©) SAP AG
IUT110
13-69
Returns Entry New returns lot
Create
Close
Post
Returns lot complete
z The essential entries are:
Amount
Returns reason
Payment document number
¤ SAP AG 2003
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.
(©) SAP AG
IUT110
13-70
Returns Lot: Change New returns lot
Create
Close
Post
Returns lot complete
Change
z Items can be deleted and added if the returns lot is still open. z Data on items that have already been entered can also be corrected. z Interrupted entry of a returns lot can be resumed using this function.
¤ SAP AG 2003
(©) SAP AG
IUT110
13-71
Returns Lot: Close New returns lot
Create
Close
Post
Returns lot complete
z Once the returns lot is closed, no more changes can be made to it z If the returns lot has not been posted, it can be opened again z Posting cannot begin until a lot is closed
¤ SAP AG 2006
(©) SAP AG
IUT110
13-72
Returns Lot: Post New returns lot
Create
Close
Post
Returns lot complete
z You can decide whether postings are to be managed:
In dialog mode
In a background process
z For each return
The payment document and cleared items are determined
All activities stored in Customizing are executed
The returns history is written
¤ SAP AG 2003
(©) SAP AG
IUT110
13-73
Returns Lot: Post-processing New returns lot
Create
Close
Post
Returns lot complete
Postprocessing
z Clarification of return use z Correction of returns item and restart posting for selected items z Manual posting and clearing for selected items
¤ SAP AG 2003
(©) SAP AG
IUT110
13-74
Returns History
Record of business management data for returns processing, including: - Amounts - Document numbers
Basis for future handling of the contract account dependent on: Period of examination - Number of returns Returns history
¤ SAP AG 2003
(©) SAP AG
IUT110
13-75
Returns: Summary
z The utility company can configure the many settings in such a way that detailed work is taken care of in the background. z Some of these activities are:
Reversing the clearing for the contract account
Passing on charges with/without tax
Deferral of receivables
Setting payment and dunning blocks
Triggering correspondence
¤ SAP AG 2003
(©) SAP AG
IUT110
13-76
Contract Accounts Receivable and Payable: Dunning
z Overview z Documents z Account display z Payments z Returns
z Dunning z Installment plan
¤ SAP AG 2009
(©) SAP AG
IUT110
13-77
Dunning: Objectives
At the conclusion of this topic, you will be able to: z Describe the two-step dunning process z Display and explain the dunning history of a business partner/contract account z Name some of the influential factors in dunning z Describe the differences between classical and flexible dunning.
¤ SAP AG 2009
(©) SAP AG
IUT110
13-78
Dunning: Introduction
z Customer payments can only be reasonably controlled within utility companies if they are supported by automatic processes. z If payment is delayed, dunning automatically:
Creates a letter customer to the customer
Executes further activities
Triggers workflows (security requirement, disconnection order)
z This is a general procedure and can be adjusted to company requirements and individual customers or customer groups.
¤ SAP AG 2006
(©) SAP AG
IUT110
13-79
Dunning: Business Scenario
z Document structure and posting z Display account balance z Payment for account balance z Process returns and post charges z Dunning for the contract account z Arrangement of installment plan
¤ SAP AG 2003
(©) SAP AG
IUT110
13-80
Dunning: Dunning Proposal and Activities
Amount limits" Days in arrears Dunning frequency
Charge schedule Print forms
Business partner Contract account Open items
Determination of new "dunning levels
Generate dunning proposal
Generate dunning activities
Post interest and charges
Dunning history
¤ SAP AG 2009
The dunning program can be executed first as a dunning proposal and then, in a second run, as as a dunning activity run based on the dunning proposal. Items to be dunned are updated, dunning notices printed, and other dunning activities are executed in the activity run. Dunning proposals and activities can also be processed in a program run.
The dunning proposal can still be processed before the dunning notice is printed.
(©) SAP AG
IUT110
13-81
Dunning: Influential Factors
Dunning procedure
Dunning grouping
Minimum/maximum amounts
Creditworthiness
Dunning process
Days in arrears
Dunning frequency
¤ SAP AG 2009
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 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.
(©) SAP AG
IUT110
13-82
Dunning Proposal for a Business Partner
Determination of all business partner accounts Reading the dunning history Calculation of creditworthiness Generation of a dunning proposal
The new dunning level is determined Dunning information is not saved for items
Writing the dunning proposal in the dunning history
¤ SAP AG 2003
Possible selection parameters for a dunning proposal: y General selection criteria: - Company code - Business partner - Contract account - Net due date y Dynamic selection criteria (from the business partner item contract accounting document): - Document number - Business area - Contract - Division - Document date - Posting date - Currency - All other criteria from the document item can also be used.
(©) SAP AG
IUT110
13-83
Dunning: Configuration of Dunning Process
Creditworthiness and credit weighting
Dunning Levels
Dunning charges (scale schema)
Print all items
Dunning process
Interest
Payment period Dunning activities: Customer letter Disconnection order Deactivate installment plan
¤ SAP AG 2003
Every dunning procedure can be made up of different dunning levels. 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 time-dependent factor used to include the credit points of a dunning level in creditworthiness calculation.
(©) SAP AG
IUT110
13-84
Dunning: Determination of Dunning Level Where do the various influencing factors come from?
Contract account
Dunning procedure Dunning grouping
Open items
Due date Amount
Dunning history
Last dunning date Last dunning level
New dunning level
¤ SAP AG 2009
Items that have not yet been dunned have dunning level 0.
An open item receives the next highest dunning level if
more than the defined number of days in arrears have passed since the due date,
more days have passed since the due date than the number defined 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.
(©) SAP AG
IUT110
13-85
Dunning Activities for a Business Partner:
Save dunning level for receivables item Determine and post dunning charges Determine and post interest Execute dunning activities
Print dunning letter Deactivate installment plan, release for collection Generate disconnection document
Update dunning history
¤ SAP AG 2003
(©) SAP AG
IUT110
13-86
Dunning: Dunning History z Overview of all dunning levels for a "business partner / contract account 15.12.2009
800 $
01.01.2010 800 $ 4711 08.01.00 DL 4 $200 15.01.2010 1200 $ 4711 08.01.00 DL 4 $200 4712 08.15.00 DL 4 $150 30.01.2010 1500 $ 4711 08.01.96 DL 4 $200 4712 08.15.00 DL 4 $150 4713 MS 09.01.00 4711 14.11.2009 4 $200DL 3 $250 4712 08.15.96 DL 4 $150 4713 09.01.00 DL 3 $250 4712 14.12.2009 MS 4 $150 4713 09.01.96 DL 3 $250
Each dunning-relevant item has an entry in the dunning history
... 4713 29.12.2009 MS 3 $250 ... 4729 01.16.01 DL 1 $120 ... 4729 01.16.99 DL 1 $120 ...
Identification of the dunning run
4729 01.16.97 DL 1 $120
4729 25.01.2010 MS 1 $120 ¤ SAP AG 2009
(©) SAP AG
IUT110
13-87
New Capabilities for End-to-End Collections Management Business Rules/ Dunning run
Flexible determination of the next collection step based on busi-ness rules configured in Business Rules Framework (BRF) New dunning activity for creating work items Rule-based, automatic determination of responsible team/ agent Workload balancing
Manage Collections Work
Process Collections Work
Work list management, including:
Processing of work items in interaction center, including: Creating work lists Creating Monitoring work promise to pay lists Collection fact Reassigning work sheet items between Extended agents / teams collection history
Evaluate and Analyze
Evaluation of collection success per collection step Evaluation of promises-to-pay Analysis of work items / collectors’ efficiency Champion Challenger Analysis
¤ SAP AG 2009
(©) SAP AG
IUT110
13-88
Classical Dunning vs. New Dunning Dunning by Dunning
Dunning by Collection Strategy
Dunning level Æ dunning activities
Collection step ? dunning activities
Dunning procedure of contract account determines number and sequence of dunning levels
Rules engine determines next collection step according to collection strategy for group of contract accounts
Dunning level 2
Amount
Days
Collection step 2
Business Rules Framework
Dunning level 1
Amount
Days
Dunning data
Collection Strategy Credit rating Dunning history (last collection step)
¤ SAP AG 2009
Classical dunning is linear process based on the dunning procedure assignment
Flexible dunning is a dynamic process which allows variable activity determination using criteria limited only by imagination
(©) SAP AG
IUT110
13-89
Dynamic Activity Determination – Example
Treatement so far?
N L1 – Early reminder
Y
Previous treatment L1?
Y Next Treatment: L2
N
Previous treatment L2?
Y High Risk?
N
Medium Risk?
N
High Risk
Y
ELSE?
Y
Send to legal collections
Final contract?
Y
No Risk N
...
Y Send to legal collections Broken promises?
N
Call customer (L3A)
Y Disconnection notification
¤ SAP AG 2009
An example of a flexible strategy
(©) SAP AG
IUT110
13-90
Determination of Collection Activities with Business Rules Frame z Flexible, dynamic evaluation of a variety of parameters z Full customer context available (financial data, IS-U data, project extensions) Æ without data replication z Linear as well as decision-tree based collection strategies z Possibility of integrating manual and automatic activities
BRF Event
z Logic is transparent to the business
Regel Regel Regel
z Reduces previous programming efforts
Rule
optional
z Configurable by a key user
IF
ExpressionTHEN
Expression Ausdruck Ausdruck
Actions Action Action Actions Action Action
Expression Expression
¤ SAP AG 2009
(©) SAP AG
IUT110
13-91
Dunning by Collection Strategy
1. Business Rules Framework Dunning Proposal
Business rules evaluation for a contract (account) or group of contract (accounts)
Dunning Activity Run
2. Collection Step Definition of dunning activity, activity priority, dunning interval, charges & interest, alternative collection step
3. Organizational Management Responsibility determination
4. Capacity Planning & Workload Balancing Definition of max. no. of dunning notices in a dunning activity
¤ SAP AG 2009
As part of the dunning proposal run, the responsible organizational units and/or positions are determined and based on this information. Workload balancing is carried out. Only afterwards, the dunning activity run can create the final activities. If you want to carry out workload balancing not only for collections Workitems but also for other activities, e.g. sending reminder letters, it is essential that also these activities have a responsible organizational unit (at least a collection center) assigned.
(©) SAP AG
IUT110
13-92
Collections Management in the Interaction Center
To Do:
Contact a customer as a reminder to pay the overdue receivables
Powerful features in IC WebClient: z Work list entry based on overdue receivables, sorted by priority / ranking z Display of all relevant information for a collector z Possibility of drilling down into further details where needed z Providing all necessary functions for collections process
Optimize Interaction Center: Reduce processing time and increase customer satisfaction ¤ SAP AG 2009
Standard fact sheet provided
(©) SAP AG
IUT110
13-93
Dunning: Summary
z Dunning in Contract Accounts Receivable and Payable provides flexible dunning that can be adjusted to meet the utility company's requirements. z Customer payments can be controlled efficiently. The following activities are supported:
Customer letter
Creation of disconnection orders
Charging fees and/or taxes
z There are two techniques for executing dunning:
Classical dunning
Flexible dunning
¤ SAP AG 2009
(©) SAP AG
IUT110
13-94
Contract Accounts Receivable and Payable: Installment Plan
z Overview z Documents z Account display z Payments z Returns z Dunning
z Installment plan
¤ SAP AG 2009
(©) SAP AG
IUT110
13-95
Installment Plan: Aims
At the conclusion of this topic, you will be able to: z Add items to an installment plan z Recognize the main functions for processing installment plans
¤ SAP AG 2003
(©) SAP AG
IUT110
13-96
Installment Plan: Introduction
z Some customers are not able to keep up with payments to the utility company z In this situation, installment plans or deferrals can be arranged for one or more receivables in order to:
Accommodate the customer
Guarantee payment
¤ SAP AG 2006
(©) SAP AG
IUT110
13-97
Installment Plan: Business Scenario
z Document structure and posting z Display account balance z Payment for account balance z Process returns and post charges z Dunning for the contract account z Arrangement of installment plan
¤ SAP AG 2003
(©) SAP AG
IUT110
13-98
Installment Plan: Characteristics z Any number of open items as the basis of an installment agreement that are kept as original items z Interest calculation for installment plans z Installment plan charges z Letter to the customer z Change, add and delete individual installments z Update installment plan for incoming payment as well as (partial) clearing of original receivables z Deactivation of installment plans
¤ SAP AG 2003
(©) SAP AG
IUT110
13-99
Installment Plan Category Pre-definable installment plan categories make creating new installment plans easier. Installment plan parameters: Company Companyx y z Bill Bill Company xyz Company
Bill Bill
• Installment number or amount
7. Installment 5. Installment due June 01 Amount 4. Installment due due June 01 100 Amount May 01 3. Installment due 100 Amount 2. Installment due Apr 01 100 Amount Mar01 1. Installment 100 Amount
due Feb01 100 100 Amount
• Installment interval • Interval category • Rounding amount • Charges amount
¤ SAP AG 2003
(©) SAP AG
IUT110
13-100
Installment Plan: Summary
Simple procedure for creating and managing installment plans. z Installment plan categories make it easier to create installment plans on the basis of an enterprise model. z Either all open items, or any selection of open items, can be included. z Installment plan items are statistical document items that are saved in repetition groups.
¤ SAP AG 2003
(©) SAP AG
IUT110
13-101
(©) SAP AG
IUT110
13-102
Exercises Unit: Contract Accounts Receivable and Payable Topic: Manual Document Entry At the end of these exercises you will be able to: •
Post a document manually
Understand the kind of information that is contained in a FI-CA document and know 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 business partner’s contract account.
First, save your user profile by choosing System → User Profile → Own Data On the Parameters tab page, enter the following parameters: Make sure you use uppercase letters! If you are attending a course without US scenarios BUK: U100 FWS: EUR 8P3:
(company code) (currency key) (post without jurisdiction code)
If you are attending a course with US scenarios BUK: U300 FWS: USD 8P3: X
(company code) (currency key) (post with jurisdiction code)
Make sure you use uppercase letters. Your business partners have the following number ranges: TBCA... for business partners without US scenarios TB13... for business partners with US scenarios.
(©) SAP AG
IUT110
13-103
1-1
Post a receivable 1-1-1
Name the menu path that you use to post a document. _____________________________________________________
1-1-2
1-1-3
Now post a receivable for today's energy consultation. Use the following data: Data Field
Content
Note
Document Date
Today’s date
Is preset
Posting Date
Today’s date
Is preset
Reconciliation Key
01-YYMMDD##
YYMMDD = Today’s date,
## = Group number
Switch to the entry screen for document items. Enter other receivables for energy consultation for your business partner. Try to keep the number of entries to a minimum so that you can see which data the system determines automatically. Data Field
Content
Note
Business Partner
TBCA0110## (TB130110##)
Main Transaction
Miscellaneous Postings
Use F4 help
Subtransaction
Miscellaneous posting
Use F4 help
Amount
116
Do not save your entries. 1-1-4
Describe your receivable using the text: Energy consultation of YYMMDD. To enter the text you have to switch to the ZAP screen variant. To do this, choose the Line Layout icon or F9. For further options, see the Solutions.
1-1-5
Post the document and make a note of the document number. _____________________________________________________
1-1-6
Display the document.
1-1-7
Display the document item.
1-1-8
What general ledger information is contained in the business partner item? Data Field
Value
Source
Company Code G/L Account Account Determination ID
(©) SAP AG
IUT110
13-104
1-1-9
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 to Financial Accounting. _____________________________________________________
1-2-4
The document date and posting date always correspond to the entry date. _____________________________________________________
1-2-5
The reconciliation key can differ for each document item. _____________________________________________________
(©) SAP AG
IUT110
13-105
(©) SAP AG
IUT110
13-106
Exercises Unit: Contract Accounts Receivable and Payable Topic: Display Account Balance After completing these exercises, you will be able to: •
Use the different account balance display options. This means you can display the items required for analyzing the account using the most suitable field structure variant
•
Provide information on the balance and development of a contract account
•
Provide information on the items of a contract 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 contract account shows all items that have been posted to that account. _____________________________________________________
2-1-2
You can adjust the individual account balance display so that items other than those in the standard display are displayed according to user needs. _____________________________________________________
2-1-3
The list type determines the line layout (how the lines are structured) for the item display. _____________________________________________________
2-1-4
To display the items in a customer account in another line layout, you have to return to the initial screen. _____________________________________________________
(©) SAP AG
IUT110
13-107
2-2
Line item display for a business partner 2-2-1
What is the current balance for your business partner TBCA0110## (TB130110##)? _____________________________________________________
2-2-2
Which items make up the balance? _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________
2-2-3
Have any payments already been made? _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________ _____________________________________________________
2-3
Navigating the document display (optional) 2-3-1
Identify the receivable from the energy consultation with business partner TBCA0110## (TB130110##). Tip: Choose the correct line layout variant.
2-3-2
Who posted the receivable? _____________________________________________________
2-3-3
Which reconciliation key was used? _____________________________________________________
2-3-4
Have any taxes been calculated for the energy consultation? _____________________________________________________
(©) SAP AG
IUT110
13-108
Exercises Unit: Contract Accounts Receivable and Payable Topic: Payment After completing these exercises, you will be able to: •
Explain the processing steps for a payment lot
•
Post payments using a payment lot
•
Post payment at cash desk
A customer arrives and would like to pay cash for an energy consultation.
3-1
Payment lot 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 it. _____________________________________________________
3-2-2
After a payment lot has been closed it can no longer be changed. _____________________________________________________
3-2-3
The procedures for payment lots and check lots are identical. _____________________________________________________
(©) SAP AG
IUT110
13-109
3-3
Posting a payment lot 3-3-1
Create a payment lot PL-YYMMDD-##.
3-3-2
Enter the search term IUT110-##. Use the F4 Help to enter a bank clearing account.
3-3-3
Enter payments for two of your business partners: Amount
Business Partner
500
TBCA0210## (TB130210##)
800
TBCA0220## (TB130220##)
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 made in the account display for each business partner and note the effects of the posting. Tip: Use the Payment List hotspot.
3-4
Payment at cash desk 3-4-1
Display the open receivables for business partner TBCA0110## (TB130110##). What is the balance? _____________________________________________________
3-4-2
Which items make up the total?
3-4-3
Switch to the cash journal. Select the subsidiary WDF for training courses without US scenarios or BOS for training courses with US scenarios. Branch from here to the cash desk.
3-4-4
Post a payment for the amount of the balance for business partner TBCA0110## (TB130110##). To do this, make the following entries: Reconcil. Key
CD-YYMMDD-##
Business Partner
TBCA0110## (TB130110##)
Amount
Balance for TBCA0110## (TB130110##)
Print a receipt. Use the printer LOCL.
(©) SAP AG
IUT110
13-110
Exercises Unit: Contract Accounts Receivable and Payable Topic: Returns After completing these exercises, you will be able to: • •
Post a return Understand the effects of returns on payments that have already been made
In accounts receivable accounting, some returns are contained in the bank statement. You now have to post these.
4-1
Returns lot 4-1-1
Create the returns lot RL-YYMMDD-##.
4-1-2
Enter the search term IUT110-##. Make sure that Document no. is entered in the Selection Cat. field. Ensure that the Amounts contain bank charges and Calculate charges checkboxes are activated. Switch to New Items.
4-1-3
Enter a return for business partner TBCA0210## (TB130210##).
If necessary, open a second session to determine the required payment document number.
4-2
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 balance display and take a look at the changes.
Returns lot with charges (optional) Repeat the steps of the previous task for the new returns lot RN-YYMMDD-##. Increase the return amount by 10. This time, create a return for the payment made by business partner TBCA0220## (TB130220##) that you entered in exercise 3-3-3. Analyze the charge posting in the account balance display.
(©) SAP AG
IUT110
13-111
(©) SAP AG
IUT110
13-112
Exercises Unit: Contract Accounts Receivable and Payable Topic: Dunning After completing these exercises, you will be able to: • •
5-1
Explain the dunning history for a business partner/contract account Differentiate between various influencing factors for dunning and describe the resulting activities
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
5-3
Take a look at the dunning history for business partner TBCA0220## (TB130220##).
Dunning history in CRM 5-3-1
(©) SAP AG
Take a look at the dunning history for business partner Walter Dunning.
IUT110
13-113
(©) SAP AG
IUT110
13-114
Exercises Unit: Contract Accounts Receivable and Payable Topic: Installment Plan After completing these exercises, you will be able to: •
Create an installment plan and describe the range of this function
A business partner calls and wants to make payments in installments. You create an installment plan.
6-1
Creating an installment plan 6-1-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 TBCA0130## (TB130130##).
6-1-2
Check that the installment plan has been created in the account display. When you display the contract account from the IC, remember that the previous settings for the list type are still active. However, to display the installment plan, you also need to display the statistical items.
6-2
Creating an installment plan via CRM 6-2-1
Create an installment plan with twelve installments at monthly intervals for all open receivables for business partner ISU260A3##.
6-2-2
Verify that the installment plan has been created in the account overview and that the interaction record reflects the transaction.
(©) SAP AG
IUT110
13-115
(©) SAP AG
IUT110
13-116
Solutions Unit: Contract Accounts Receivable and Payable Topic: Manual Document Entry
1-1
Posting receivables 1-1-1
Specify the menu path that you use to post a document. Utilities Industry → Contract Accounts Receivable and Payable → Document Post
1-1-2
Post a receivable for today’s energy consultation. Utilities Industry → Contract Accounts Receivable and Payable → Document → Post Use the following data:
1-1-3
Data Field
Content
Note
Document Date
Today’s date
Is preset
Posting Date
Today’s date
Is preset
Reconciliation Key
01-YYMMDD##
YYMMDD = today’s date
Change to the 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, so that you can see which data the system determines automatically. 1.
From the Post Document: Initial Screen, choose Enter or the OItm Business partner item list button.
2.
Enter the following values:
Data Field
Content
Note
Business Partner TBCA0110## (TB130110##) Main Transaction
Miscellaneous Postings
Use F4 help
Subtransaction
Miscellaneous posting
Use F4 help
Amount
116
3.
(©) SAP AG
Do not save your entries
IUT110
13-117
1-1-4
Describe your receivable using the text: Energy consultation of YYMMDD. To enter text: -
Choose the line layout ZAP and enter the text in the text field using either the line layout icon or F9,
-
or change to the detail display for your business partner item (for example, by double-clicking on the current item in the list) and enter the text under Other data at the lower end of the entry screen..
If you have already saved the document: 1.
Choose Documen → Change from the menu.
The document number is preset.
1-1-5
1-1-6
2.
Choose OItm (Business partner item list).
3.
Select line layout ZAP.
4.
Enter the text in the text field.
Post the document and make a note of the document number. 1.
To post the document, choose Post.
2.
The document number is displayed in the message bar after posting.
Display the document. Utilities Industry → Contract Accounts Receivable and Payable → Document → Display
1-1-7
Display the document item. From the Display Document: Initial Screen, choose OItm to display the document items. Another possible solution: From the Display Document: Initial Screen, choose Enter. Then double-click on the summary of business partner items, or select the item with the cursor and choose Edit → Choose (F2) from the menu to display the business partner item.
1-1-8
What is the general ledger data? Data Field
Value
Source
Company Code
U100 (U300)
Entry for Post Document
G/L Account
140520
Account Determination
Account Determination ID
01
Contract Account
Double click on the business partner item. On the Basic Data tab page you can see the company code and the G/L account. The account determination ID is on the Add. Data tab page.
(©) SAP AG
IUT110
13-118
1-1-9
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.
Subtransaction in the document item
Other criteria include 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 a different contract account.
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 to Financial Accounting. True. Whilst it is possible to group documents using the reconciliation key, 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. There is only one reconciliation key for each document.
(©) SAP AG
IUT110
13-119
(©) SAP AG
IUT110
13-120
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 were 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 preconfigured in the standard settings by default. True. You define your own line item display by choosing Settings → Display / Change or F6 or the corresponding icon.
2-1-3
The list type determines the line layout of the item display. False. The list type determines which items are displayed.
2-1-4
To display the items in a contract account in a different line layout, you must return to the initial screen. False. You can change the line layout in the item display using the Select Line Layout button or by choosing Settings → Line Layout or Settings →Display/Change. You can then save the line layout in the user parameters. 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 in the variant display (provided you have activated them in your personal settings for account balance display).
(©) SAP AG
IUT110
13-121
2-2
Line item display for a business partner 2-2-1
2-2-2
What is the balance for business partner TBCA0110## (TB130110##)? 1.
Utilities Industry → Contract Accounts Receivable and Payable → Account → Account Balance
2.
Enter TBCA0110## (TB130110##) in the Business Partner field. The value in the List Type field is preset with Standard - All open items. The Line Layout field shows Standard line layout – acc. display.
3.
Choose Return.
4.
Choose the Totals hotspot.
5.
The balance appears in the Total field.
Which items make up the balance? Double-click on the Receivablesor the Total line to return to the display of the receivables that are still open. Alternatively, choose the Receivables hotspot directly.
2-2-3
2-3
Have any payments already been made? 1.
Go Back (F3) to Account Display: Initial Screen.
2.
Choose either a list type that shows not only open items (using the F4 Help, for example, the list type All Items), or choose the Detail button on the List Type subscreen. Select the Cleared Items field and choose Enter.
3.
Return to the account display. This displays all payments made that can be analyzed using the Payment List hotspot.
Navigating the document display (optional) 2-3-1
Identify the receivable from the energy consultation with business partner TBCA0110## (TB130110##). Choose the correct line layout variant.
(©) SAP AG
1.
Utilities Industry → Contract Accounts Receivable and Payable → Account → Account Balance
2.
Enter TBCA0110## (TB130110##) in the Business Partner field.
3.
Choose Enter.
4.
Choose Line layout (Shift+F4).
5.
Select the line layout variant Account display with document text (IUT110).
6.
You can now see which open receivable is for the energy consultation, if you entered the text Energy consultation ... in the exercise.
IUT110
13-122
2-3-2
2-3-3
Who posted the receivable? 1.
Double-click on the document. You are now in the Display Document: Item screen.
2.
Choose Document Header.
3.
You can read the user key of the person who created the document from the Created by field.
Which reconciliation key was used? Contained in the Reconcil. key field in the document header.
2-3-4
Have any taxes been calculated for the energy consultation? Choose the Overview button or select Goto → Overview from the menu. You can see the tax items in detail here by choosing the Taxes button.
(©) SAP AG
IUT110
13-123
(©) SAP AG
IUT110
13-124
Solutions Unit: Contract Accounts Receivable and Payable Topic: Payment
3-1
Payment lot Which steps must be carried out when processing a payment lot?
3-2
1.
Create
2.
Close
3.
Post
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 it. 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, since a check number must be entered for a check. This does not occur in the screen variant for the payment lot, however.
3-3
Posting a payment lot 3-3-1
3-3-2
(©) SAP AG
Create the 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).
Enter the search term IUT110-##. Use the F4 Help to specify a bank clearing account. If the value date is not set by default, enter today's date.
IUT110
13-125
3-3-3
Enter payments for two of your business partners: To enter the items, chose the New Items pushbutton. Amount
Business Partner
500
TBCA0210## (TB130210##)
800
TBCA0220## (TB130220##)
The business partner number has to be defined in the Selection value field in selection category G. 3-3-4
3-3-5
3-3-6
Save your entries and close the payment lot. 1.
Choose Save.
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.
Post the payments. 1.
Choose Post.
2.
Choose Start Directly.
3.
Choose Enter.
Check the status. The status should read Postings made.
3-3-7
Display the postings in the account display for the business partners and note the effects of the postings. Use the knowledge you have acquired in the unit Display Account Balance. Tip: Use the Payment List hotspot.
(©) SAP AG
IUT110
13-126
3-4
Payment at cash desk 3-4-1
3-4-2
3-4-3
Display the open receivables for business partner TBCA0110## (TB130110##). What is the balance? 1.
Utilities Industry → Contract Accounts Receivable and Payable → Account → Account Balance
2.
Enter the number of your business partner TBCA0110## (TB130110##) in the Business Partner field.
3.
Choose Enter.
4.
Choose the Totals hotspot. You can see the balance for the open items in the Total field.
Which items make up the total? 1.
Double-click on the Receivables field in the totals display. This takes you to the individual receivables display.
2.
Ensure that you have chosen the line layout variant Account display with document text (IUT110) to display the document text column. Amount
Item Type
116,00
Miscellaneous posting: Energy consultation from
(from the Post Document exercise)
Switch to the cash journal. Select the subsidiary WDF for training courses without US scenarios or BOS for training courses with US scenarios. Branch from here to the cash desk: Utilities Industry → Contract Accounts Receivable and Payable → Payments → Cash Journal → Cash Journal → To Cash Desk
3-4-4
(©) SAP AG
Post a payment for the amount of the open balance of business partner TBCA0110## (TB130110##). Reconcil. Key
CD-YYMMDD-## (Under Further posting specs)
Business Partner
TBCA0110## (TB130110##)
Amount
Balance of TBCA0110## (TB130110##)
1.
Ensure that the Inc.Cash Pymt checkbox is selected.
2.
To post the payment, choose Post or Post Online. If you have chosen the Post Online button, choose Save to make the posting.
3.
Select Print Receipt and confirm the print parameters.
IUT110
13-127
(©) SAP AG
IUT110
13-128
Solutions Unit: Contract Accounts Receivable and Payable Topic: Returns
4-1
Returns lot 4-1-1
4-1-2
4-1-3
Create a returns lot (RL-yymmdd-##). 1.
Utilities Industry → Contract Accounts Receivable and Payable → Payments → Returns → Returns Lot
2.
Enter RL-yymmdd-## in the Returns Lot field.
3.
Choose Create (F5).
Enter the search term (IUT110-##). Make sure that Document no. is entered in the Selection Cat. field. Ensure that the Amounts contain bank charges and Calculate charges checkboxes are activated. Switch to New Items. 1.
Search term: IUT110-##
2.
Make the settings listed above and save them using Save (CTRL+S), if these have not already bee preset.
3.
Choose New Items.
Enter a return for business partner TBCA0210## (TB130210##). If necessary, open a second session to determine the required payment document number.
(©) SAP AG
1.
System → Create Session
2.
Utilities Industry → Contract Accounts Receivable and Payable → Account → Account Balance
3.
Enter the number of your business partner TBCA0210## (TB130210##) in the Business Partner field.
4.
Choose the standard list type All items and line layout Account display with document text (IUT110).
5.
Choose the green checkmark (ENTER).
6.
Note or copy the payment document number.
7.
Close the second session: System Æ End Session
8.
In the Returns: Record/Process Items screen, enter the payment document number in the SelectionValue field and enter the return reason 01 Bank Account Overdraft. The Selection Cat. should be set to B.
9.
Choose Enter. The amount is determined automatically.
IUT110
13-129
4-1-4
4-1-5
4-1-6
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 in the Returns: Request Screen.
4.
Choose Close and confirm the action.
Post the returns lot. 1.
To do this, choose Post.
2.
Choose Start Online.
3.
Choose OK.
Check the status. The status should read Postings made.
4-1-7
Switch to the account balance display and take a look at the changes. Use the Payment List hotspot here too.
4-2
Returns lot with charges (optional) Repeat the steps in the previous task for a new returns lot (RN-yymmdd-##). Increase the return amount by 10. This time, generate a return for the payment entered for business partner TBCA0220## (TB130220##) in exercise 3-3-3. The solution is the same 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.
(©) SAP AG
IUT110
13-130
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 even be applied to individual line 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 Take a look at the dunning history for business partner TBCA0220## (TB130220##).
5-3
1.
Utilities Industry → Contract Accounts Receivable and Payable → Account → Further Information → Dunning History
2.
Enter TBCA0220## (TB130220##) in the Business Partner field.
3.
Choose Execute (F8).
4.
The dunning history is displayed.
Dunning history in CRM 1.
Identify business partner Walter Dunning, ISUUS02074.
2.
In the navigation toolbar, click on Collections > Dunning History.
3.
View the dunning notice which has been issued.
(©) SAP AG
IUT110
13-131
Solutions Unit: Contract Accounts Receivable and Payable Topic: Installment Plan
6-1
Creating an installment plan 6-1-1
6-1-2
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 TBCA0130## (TB130130##). 1.
Utilities Industry Æ Customer Service Æ Front Office/Customer Interaction Center Æ Customer Interaction Center
2.
Enter TBCA0130## (TB130130##) in the Part. field (in the search criteria). Choose Enter to display the business partner’s data. Then choose Confirm Partner with the green checkmark on the right of the data finder.
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.
Click the Select All (Shift+F7) button to choose all open items.
5.
Enter in the Start Date field. Then enter the required data in the No. of Instmnts, Inst. Interval, Interval Type and Rounding Amount fields.Choose Installment Plan or ENTER.
6.
Check the number of installments and the installment intervals and select Save or Ctrl+S.
7.
Enter a text for the contact and save it by choosing Save or Ctrl+S.
Check that the installment plan has been created in the account display. When you display the customer account from the IC, remember that the previous settings for the list type are still active. However, to display the installment plan, you also need to display the statistical items. Click the right mouse button on the contract account to 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 the account balance display.
6-2
Creating an installment plan in CRM 6-2-1
Create an installment plan with twelve installments at monthly intervals for all open receivables for business partner Max Mayer, ISU260A3##. 1.
(©) SAP AG
Log into CRM Interaction Center
IUT110
13-132
6-2-2
2.
Enter ISU260A3## in the Account ID field. Press Enter to process the search criteria and display the business partner’s data. Confirm the account and service location if required.
3.
Along the navigation bar, click on Account Balance to display the Account Overview. In the topmost view, click on Installment Plan.
4.
Verify that no current installment plans exist for the account. Click on New to pull up the Create New Plan view.
5.
Click the Select All button to choose all open items.
6.
Choose a plan type based on the requirements – 12 months, no fee.
7.
Enter in the Start Date field. Then verify the Print Parameter setting.
8.
Click the Save and Back button to save the plan and return to the Account Overview
Check that the installment plan has been created in the Account Overview. 1.
The Installment Plan View shows the newly created plan
2. Along the Navigation Bar, click on the Interaction Record to display the current interaction details where the plan has been saved. 3.
(©) SAP AG
End interaction by clicking on the End button.
IUT110
13-133
(©) SAP AG
IUT110
13-134
