IUT250 Customer Service

IUT250

IUT250 Kundenservice......................................................................................................................................................1 Copyright.......................................................................................................................................................................2 SAP Utilities (IS-U/CCS)..........................................................................................................................................3 Prerequisites...............................................................................................................................................................4 Target Audience.........................................................................................................................................................5 Course Objectives......................................................................................................................................................6 Course Objectives......................................................................................................................................................7 Course Content: IUT250............................................................................................................................................8 Customer Service - Overview........................................................................................................................................1 Customer Service Overview: Unit Objectives...........................................................................................................2 mySAP Utilities: The Comprehensive Solution for Utility Companies....................................................................3 Functional Scope of the IS-U/CCS System...............................................................................................................4 Sales and Marketing in IS-U/CCS (1).......................................................................................................................5 Master Data Generator...............................................................................................................................................6 Sales and Marketing in IS-U/CCS (2).......................................................................................................................7 Internet Self Services: Home Page............................................................................................................................8 IS-U/CCS Integration Model.....................................................................................................................................9 Customer Service in IS-U/CCS...............................................................................................................................10 Component Hierarchy..............................................................................................................................................11 Processes in the Area Menu.....................................................................................................................................12 Customer Interaction Center (L Form)....................................................................................................................13 Integration with External Communications Systems (1).........................................................................................14 Sequence of Business Processes..............................................................................................................................15 Business Scenario (1)...............................................................................................................................................16 Business Scenario (2)...............................................................................................................................................17 Customer Service - Overview: Unit Summary........................................................................................................18 Customer Interaction Center (CIC)................................................................................................................................1 Customer Interaction Center: Topic Objectives........................................................................................................2 CIC: Introduction, Requirements...............................................................................................................................3 Overview of CIC Functions.......................................................................................................................................4 Overview of Additional CIC Functions.....................................................................................................................5 IS-U/CCS Integration: Front Office...........................................................................................................................6 Typical Front Office Calls.........................................................................................................................................7 Technical Structure....................................................................................................................................................8 CIC Terminology.......................................................................................................................................................9 The CIC in Different Layouts..................................................................................................................................10 Processing a CIC Contact........................................................................................................................................11 Customer Contact.....................................................................................................................................................12 User Session.............................................................................................................................................................13 Data Finder: Process Flow.......................................................................................................................................14 Data Finder: Use......................................................................................................................................................15 Starting a Call in the CIC (Standard Layout)...........................................................................................................16

CIC Telephony Functions........................................................................................................................................17 The Action Box........................................................................................................................................................18 The Navigation and Application Area.....................................................................................................................19 The Application Area (L Form)...............................................................................................................................20 Customizing the L Form..........................................................................................................................................21 Customer Interaction Center (CIC): Exercises........................................................................................................22 Customer Interaction Center (CIC) Solutions..........................................................................................................26 CIC Configuration.........................................................................................................................................................1 CIC Configuration: Unit Objectives..........................................................................................................................2 CIC Terminology.......................................................................................................................................................3 CIC Profile: Framework and Components................................................................................................................4 CIC Configuration: Overview....................................................................................................................................5 CIC Customizing (1)..................................................................................................................................................6 CIC: Visible Components..........................................................................................................................................7 CIC: Quick Keys........................................................................................................................................................8 CIC Customizing (2): L Form....................................................................................................................................9 CIC Customizing (2): Vertical Slots........................................................................................................................10 Hidden Components.................................................................................................................................................11 CIC Customizing (3)................................................................................................................................................12 CIC Customizing (4)................................................................................................................................................13 SAP Components and Profile Requirements (1).....................................................................................................14 SAP Components and Profile Requirements (2).....................................................................................................15 CIC Customizing (5)................................................................................................................................................16 Procedure.................................................................................................................................................................17 Organizational Plan..................................................................................................................................................18 Allocate the CIC Profile in the Organizational Plan................................................................................................19 CIC Organizational Structure (Administration).......................................................................................................20 CIC profile...............................................................................................................................................................21 Assigning a CIC Profile to a User ID (1).................................................................................................................22 Assigning a CIC Profile to a User ID (2).................................................................................................................23 CIC Profile: Inheritance...........................................................................................................................................24 Starting the CIC.......................................................................................................................................................25 CIC Configuration: Summary..................................................................................................................................26 Exercises..................................................................................................................................................................27 Customer Interaction Center (CIC) Solutions..........................................................................................................30 Navigation and Application Area..................................................................................................................................1 Navigation and Application Area: Unit Objectives:..................................................................................................2 Customer Overview: Requirements...........................................................................................................................3 Information Views.....................................................................................................................................................4 IS-U Navigator...........................................................................................................................................................5 IS-U Navigator: Structure..........................................................................................................................................6 IS-U Navigator: Customizing....................................................................................................................................7

The Navigation and Application Area.......................................................................................................................8 The Navigation Area..................................................................................................................................................9 Data Environment for the Navigation Area.............................................................................................................10 Data and Documents in the Navigation Area..........................................................................................................11 Application Area - Displaying HTML Pages..........................................................................................................12 CIC Application Area..............................................................................................................................................13 The Application Area (L Form)...............................................................................................................................14 Workflow Inbox.......................................................................................................................................................15 Defining HTML Calls..............................................................................................................................................16 HTML Configuration (1).........................................................................................................................................17 HTML Configuration (2) - External Parameters.....................................................................................................18 HTML Configuration (3) - Internal Parameters.......................................................................................................19 HTML Configuration (4).........................................................................................................................................20 Customer Overview (1)............................................................................................................................................21 Customer Overview (2)............................................................................................................................................22 Customer Overview.................................................................................................................................................23 Addendum: Customer Contacts...............................................................................................................................24 What is Customer Contact Management?................................................................................................................25 General Requirements..............................................................................................................................................26 Which Data does a Customer Contact Contain?......................................................................................................27 Creation....................................................................................................................................................................28 Example: Customer Contact in the Business Process..............................................................................................29 Structure of Customer Contacts...............................................................................................................................30 Contact Classes, Contact Activities.........................................................................................................................31 Object Links.............................................................................................................................................................32 Configuration...........................................................................................................................................................33 Configuration Determination...................................................................................................................................34 A Customer Contact for Every Print Activity..........................................................................................................35 Analysis of Customer Contacts................................................................................................................................36 Customer Contact.....................................................................................................................................................37 Navigation and Application Area: Unit Summary...................................................................................................38 Navigation and Application Area: Exercises...........................................................................................................39 Navigation and Application Area: Solutions...........................................................................................................44 Front Office Processes...................................................................................................................................................1 Front Office Processes: Unit Objectives....................................................................................................................2 Calls (technical).........................................................................................................................................................3 Business Object Repository (BOR)...........................................................................................................................4 Call Definition: Method.............................................................................................................................................5 Call Definition: Workflow and Test Procedure.........................................................................................................6 What Is a Front Office Process?................................................................................................................................7 Front Office Process: Example..................................................................................................................................8 Front Office Process (Technical)...............................................................................................................................9

Differences Between Front Office Processes and Workflows.................................................................................10 Data Flow of a Front Office Process........................................................................................................................11 Data Export and Data Import...................................................................................................................................12 Action Box Call: Data Flow....................................................................................................................................13 Data Flow: Clipboard --> Transaction.....................................................................................................................14 Data Flow: Context Menu --> Transaction..............................................................................................................15 Available Data Flow Functions...............................................................................................................................16 Front Office Process: Editor Steps...........................................................................................................................17 Front Office Process: Markers.................................................................................................................................18 Marker: Example.....................................................................................................................................................19 Front Office Process: Table Processing...................................................................................................................20 Table Processing: Example......................................................................................................................................21 Front Office Process: Initial Data Creation (1)........................................................................................................22 Front Office Process: Initial Data Creation (2)........................................................................................................23 Front Office Processes: Unit Summary...................................................................................................................24 Front Office Processes Exercises.............................................................................................................................25 Front Office Processes Solutions.............................................................................................................................30 Connection to External Systems....................................................................................................................................1 Connection to External Systems: Unit Objectives.....................................................................................................2 Integration with External Communications Systems (2)...........................................................................................3 Workflow Inbox.........................................................................................................................................................4 E-Mail and Fax Messages in the Workflow Inbox....................................................................................................5 Starting the Workflow through SAPconnect.............................................................................................................6 Externally Triggered Callback...................................................................................................................................7 SAP Archive Link: Components...............................................................................................................................8 Archive Scenarios: Overview....................................................................................................................................9 Archiving of Inbound Documents: Early/Simultaneous Archiving.........................................................................10 Archiving Outbound Documents.............................................................................................................................11 Displaying Archived Documents.............................................................................................................................12 Call Center-Integration............................................................................................................................................13 Internet Integration...................................................................................................................................................14 R/3 Client/Server Architecture with ITS.................................................................................................................15 Five-Level Client/Server Architecture.....................................................................................................................16 Internet Transaction Server......................................................................................................................................17 IS-U/CCS Internet Services.....................................................................................................................................18 Internet Services for the Utility Company...............................................................................................................19 Example: 'Display Bill' Scenario.............................................................................................................................20 Customer Internet Self- Services.............................................................................................................................21 WAP Self-Services..................................................................................................................................................22 Connection to External Systems: Unit Objectives...................................................................................................23 Disconnection and Reconnection...................................................................................................................................1 Disconnection and Reconnection: Unit Objectives...................................................................................................2

Disconnection and Reconnection: Business Scenario...............................................................................................3 Process of Disconnection and Reconnection.............................................................................................................4 Disconnection Triggers..............................................................................................................................................5 Disconnection Document: Log Function...................................................................................................................6 Disconnection Document and Reference Object.......................................................................................................7 Disconnection Document: Components....................................................................................................................8 Confirm Discon-nection Order..................................................................................................................................9 Reversal of Disconnection Activities.......................................................................................................................10 Disconnection Document: Basic Functions.............................................................................................................11 Contract-Specific Disconnection.............................................................................................................................12 Create Disconnection Order: Example....................................................................................................................13 PM/SM Order for Disconnection/Reconnection......................................................................................................14 Disconnection Document: Secondary Functions (Outlook)....................................................................................15 Customizing: Processing Variants...........................................................................................................................16 Customizing: Offsets...............................................................................................................................................17 Customizing: Order Codes.......................................................................................................................................18 Addendum: Work Management - Plant Determination...........................................................................................19 Disconnection Workflows: Confirmation Status.....................................................................................................20 Disconnection Document and Workflow.................................................................................................................21 Disconnection/Collection Workflows: Overview....................................................................................................22 Start of Disconnection/Collection Workflows.........................................................................................................23 Disconnection/Collection Workflows: Create Disconnection Document...............................................................24 Disconnection/Collection Workflows: Relationships..............................................................................................25 Disconnection Workflows: Confirmation Status.....................................................................................................26 Disconnection Reason Obsolete After Creation of Disconnection Order...............................................................27 Disconnection Reason Obsolete After Confirmation of Disconnection Order........................................................28 Important Wait Steps...............................................................................................................................................29 Disconnection and Reconnection: Unit Summary...................................................................................................30 Disconnection and Reconnection Exercises............................................................................................................31 Disconnection and Reconnection: Solutions...........................................................................................................34 Move-In/Out..................................................................................................................................................................1 Move-In/Out: Unit Objectives...................................................................................................................................2 The Complete Process................................................................................................................................................3 Move-In/Out: Contents (1)........................................................................................................................................4 The Move-In Process.................................................................................................................................................5 Move-In: Overview (Technical)................................................................................................................................6 Move-In: Process.......................................................................................................................................................7 Move-In: Initial Screen..............................................................................................................................................8 Move-In: Address Data..............................................................................................................................................9 Move-In: Full Screen...............................................................................................................................................10 Move-In: Meter Readings........................................................................................................................................11 Service Orders for Move-In and Final Meter Reading............................................................................................12

Security Deposits.....................................................................................................................................................13 Move-In: Security Deposits.....................................................................................................................................14 Move-In: Budget Billing Plan (1)............................................................................................................................15 Move-In: Budget Billing Plan (2)............................................................................................................................16 Move-In: Due Dates for Budget Billing..................................................................................................................17 Move-In: Log...........................................................................................................................................................18 Status of Move-In Processing..................................................................................................................................19 Move-In: Reversal...................................................................................................................................................20 Automatic Owner Move-In......................................................................................................................................21 The Owner Assignment Process..............................................................................................................................22 Owner Assignment in the Premise...........................................................................................................................23 Move-In/Out: Contents (2)......................................................................................................................................24 The Move-Out Process...........................................................................................................................................25 Move-Out: Overview (Technical)............................................................................................................................26 Move-Out: Process...................................................................................................................................................27 Move-Out: Full Screen............................................................................................................................................28 Move-Out: Budget Billing Plan...............................................................................................................................29 Move-Out: Meter Readings.....................................................................................................................................30 Changes to Installation Data....................................................................................................................................31 Move-Out: Reversal.................................................................................................................................................32 Move-In/Out: Contents (3)......................................................................................................................................33 The Move-In/Out Process........................................................................................................................................34 Move-In/Out (Premise)............................................................................................................................................35 Move-In/Out (Business Partner)..............................................................................................................................36 Move-In/Out Processing Variants............................................................................................................................37 Selection Criteria for Move-In/Out..........................................................................................................................38 Move-In/Out: Summary (1).....................................................................................................................................39 Move-In/Out: Summary (2).....................................................................................................................................40 Move-In, Move-Out, Move-In/Out Exercises.........................................................................................................41 Move-In, Move-Out, Move-In/Out Solutions..........................................................................................................48 IS-U Sales Processing....................................................................................................................................................1 IS-U Sales Processing: Unit Objectives.....................................................................................................................2 IS-U Sales Processing: Process and Objects (1)........................................................................................................3 IS-U Sales Processing: Process and Objects (2)........................................................................................................4 Sales Transaction.......................................................................................................................................................5 Products and Profiles.................................................................................................................................................6 IS-U Sales Processing: Process and Objects (3)........................................................................................................7 Workflow 1: ISUProdCRM (Simplified)...................................................................................................................8 IS-U Sales Processing: Process and Objects (4)........................................................................................................9 IDE Process..............................................................................................................................................................10 Workflow 2: ISUIdeEnrCom (Simplified, Detailed)...............................................................................................11 Master Data Generator: Process and Objects (5).....................................................................................................12

Utility products........................................................................................................................................................13 Set Types..................................................................................................................................................................14 IS-U Sales Processing: Process and Objects (6)......................................................................................................15 Master Data Template (Simplified).........................................................................................................................16 Attributes..................................................................................................................................................................17 Master Data Template (1)........................................................................................................................................18 Master Data Template (2)........................................................................................................................................19 Master Data Template Category..............................................................................................................................20 What's Next?..................................................................................................................................................................1 CRM Integration with 4.63........................................................................................................................................2 System Landscape: CRM, IS-U/CCS, and BW.........................................................................................................3 Overview (1)..............................................................................................................................................................4 The Future System Landscape...................................................................................................................................5 Integration Approach (1)............................................................................................................................................6 Overview (2)..............................................................................................................................................................7 Integration Approach (2)............................................................................................................................................8 Replication of Objects in IS-U and CRM..................................................................................................................9 System Interaction in the Sales Process...................................................................................................................10 Functions Planned in 4.63 (or Later).......................................................................................................................11 Overview (3)............................................................................................................................................................12 SAP Internet Sales Function Blocks........................................................................................................................13 Internet Sales Architecture.......................................................................................................................................14 mySAP.com Workplace: Sales Representative.......................................................................................................15 The Mobile Sales User Interface: Overview............................................................................................................16 Appendix........................................................................................................................................................................1 Appendix A: CIC Components:................................................................................................................................2 Appendix: HTML Templates...................................................................................................................................15

IUT250 Kundenservice

IUT250 Customer Service  SAP AG 1999

   

R/3 System Release 4.63 / mysap Utilities/ Customer Care Service Date: October 2001 5004 4902

Copyright

Copyright 2001 SAP AG. All rights reserved. Neither this training manual nor any part thereof may be copied or reproduced in any form or by any means, or translated into another language, without the prior consent of SAP AG. The information contained in this document is subject to change and supplement without prior notice. All rights reserved.

 SAP AG 1999



              



Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft Corporation. Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation. Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc. ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc. TouchSend Index ® is a registered trademark of TouchSend Corporation. Visio ® is a registered trademark of Visio Corporation. IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation. Indeo ® is a registered trademark of Intel Corporation. Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape Communications, Inc. OSF/Motif ® is a registered trademark of Open Software Foundation. ORACLE ® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated. UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation. ADABAS ® is a registered trademark of Software AG The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG. Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.

SAP Utilities (IS-U/CCS) Level 2

Level 3 IUT220

3 days

Device Management IUT221

IUT225

2 days

Energy Data Management

3 days

Work Management IUT110

5 days

Introduction to the ISU/CCS

IUT210

3 days

Basic Data/ Basic Functions

IUT230

5 days

Billing and Invoicing IUT240 5 days Contract Accounts Receivable and Payable IUT250 4 days Customer Service IUT280

2 days

Print Workbench

 SAP AG 1999

IUT235

2 days

Real Time Pricing

Prerequisites

 Knowledge of the Windows environment  Basics of R/3  Course IUT 110: Introduction to the IS-U/CCS System  Course IUT 210: Master Data and Basic Functions  Course BC 600: SAP Business Workflow - Introduction

 SAP AG 1999

Target Audience

 Participants 

Project managers responsible for implementing IS-U



Project team modeling business processes with IS-U



Administrators optimizing processes in the IS-U environment



Consultants preparing for IS-U implementation

 Duration: 4 days

 SAP AG 2001 1999

Course Objectives

This course will enable you to understand:  The basics (including configuration options) of the Customer Interaction Center (CIC), an efficient work environment for the customer service agent  Customer contact management in IS-U/CCS  Typical customer service processes (move-in/out, disconnection and reconnection, service connection management)  The basics of SAP workflow, which enables you to configure your business processes flexibly in ISU/CCS

 SAP SAP AG 1999  AG 2001

Course Objectives

At the conclusion of this course, you will be able to:  Recognize the configuration options of the CIC and use the CIC as a working environment  Describe and use customer contact options  Perform the business processes of move-in, moveout, and disconnection/reconnection, as well as describe the Customizing options for these functions

 SAP SAP AG 1999  AG 2001

Course Content: IUT250

Introduction Unit 1

Overview of Customer Service

Unit 6

Integration with External Systems

Unit 2

Customer Interaction Center (CIC)

Unit 7

Disconnection and Reconnection

Unit 3

CIC Configuration

Unit 8

Unit 4

Navigation and Application Area

Move-In, Move-Out, Move-In/Out

Unit 9

IS-U Sales Processing

Unit 5

Front Office Processes

Unit 10

Outlook

Appendix Exercises and solutions are at the end of each unit  SAP AG 1999

Customer Service - Overview

Contents:  This unit provides you with an overview of the functional scope of IS-U/CCS and its integration with the standard SAP functions  Shows how Customer Service relates to the rest of ISU/CCS  Shows the structure of the Customer Service component  Introduces some key terminology

 SAP AG 1999

Customer Service Overview: Unit Objectives

This unit will give you an overview of The integration of IS-U/CCS in the standard SAP system The integration of the Customer Service component in IS-U/CCS The structure of the Customer Service component The functions available in the Customer Service component

 SAP SAP AG 1999  AG 2001

mySAP Utilities: The Comprehensive Solution for Utility Companies

Str ategic Enterprise Strategic E nterpr ise MManageme anageme ntnt

CCustomer ustomer Service S ervic e

Engi neering && Engineering Constr ucti on C onstructi on Engi neering && Engineering Constr ucti on C onstructi on Sal Sales esCCycle ycle&& Billing Billing

Sales Sal esCCycle ycle

Energy a EnergyDat Data Manag ement M anage ment

Invoic i ng Invoicing

Business

 Finances & Controlling  Human Resource Management  Logistics

Busi Business nessI Intelligence ntellig ence && Data ehous ing Data War Ware housing

Mar ket RResearch Market esearch &&Anal A nalysis ysis

Human H um anRResource esource MManageme anageme ntnt

MManagerial anagerial Acco unti ng Accounti ng

Fina ncial Financial Acc ounti ng Accounting

Marketi Marketing ng Program Program M anagement Manageme nt

Product/ Product/ Brand arketing BrandM Marketing

Regulat ory Reg ulatory Reporting/FERC R eporting/FER C Sales Sal es Cha nnels Channels

Sal anagem ent Sales esMManagem ent

Pr oductio nn Productio

Plant enanc e Plant M Maint ainten ance

Decommissi oni ng Dec ommissioni ng

Operati ons Ma Operations Management nagement

Maintenance Maintenance&& Wor ent WorkkMManagem anagement

Transmissi Transmission on && Distr ibution Servic e Distribution S ervice

Connecti on Connection on &&Installati Inst allation Manageme nt Manag ement

Ser Service vice MManage ment anagement

Meter M eter Reading R eading MManagement anage ment

Ser Service vice Ag Agreement reement

Special mer SpecialCCusto ustomer Process Processes es

RRetail etailBilling Billing

Traders Tr aders Wor Workbenc kb enchh

Risk R isk MManagement anageme nt

Rec ei vabl agement Recei vables es Man Managem ent

Pr ocurement Procurement

Treasur Tr easuryy

Wholes Wh olesale ale Billing Billing

Pool/ Pool/ ISO ISO

Reco Reconciliati nciliation on &&Settlement S ettlement

Third arty Settl ent ThirdPParty Settlem ement

Fixed Fixed Asset Asset Management Management

Real Real Estate Estat e

Network

 SAP Customer Relationship Management  SAP Supply Chain Management  SAP Business Intelligence  SAP Business-to-Business E-Commerce

 SAP AG 1999



See the SAP homepage for a link to the current solution map: http://www.sap.com

Functional Scope of the IS-U/CCS System

Generation

Transmission

Distribution

Customer service & billing

All customer-related business processes IS-U/ CCS

Customer Relationship Management Special business processes

PM MM

Marketing & Sales

SD

FI

Consumption Entry Installation Services

Consumption Billing Billing of Services

Meter & Device Management CRM

Work Management  SAP AG 1999

Invoicing Invoicing

Contract Account

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

Call Center  Gives you fast, direct access to all relevant information and transactions that are required for a customer contact- such as the customer overview, changing master data, displaying bills, entering meter reading results, displaying account information, and more  Work items allow IVR-supported callbacks

IS-U Sales Support  Product modeling based on configured materials and pricing  IS-U sales processing with generation of quotations and orders  Master data generation for order execution

IS-U Content for BW  Sales statistics, consumption statistics, transaction statistics, and so on  SAP AG 1999

Master Data Generator Product selection via mySAP CRM channels:

Master data generation or change in mySAP Utilities:

Fixed product information

Master data template

mySAP CRM product

mySAP Utilities product

Master data generator

Configuration

Configuration

Variable product information

Workflow  SAP AG 1999

mySAP Utilities

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

Internet Self Services  B2C (Business to Customer scenarios) 

Registration / password changes for Internet users



Maintaining move-in data



Maintaining move-out data



Maintaining personal data



Displaying consumption history



Entering meter reading results



Display and payment of bill



Granting a collection authorization



Account balance display

 The data is updated immediately or forwarded to an agent for verification  SAP AG 1999

Internet Self Services: Home Page

Select a service

Enter user name and password

 SAP AG 1999

IS-U/CCS Integration Model

SD

FI

E

& S ER

E

IC

SAP business partner

V

Device Management

CO

Con sum Entr ption y

SD

R

External sales systems

Customer information system

U

R

PM/ CS

CA

MM

ct ra ts In Bill t n un ) vo in o C co A ic g/ in C c A FIg ( S TOM E

s tion a ll a Inst rvices Se

Plant Maintenance & Customer Service

Sales & Distribution

C

Financial Accounting

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

IS-U components

External consumption recording systems

SAP standard components External systems

AM

GIS, MM CAD, Asset M a Materia nagement & SCADA ls Mana gement  SAP AG 1999

  



 



SAP business partner model => The business partner (the contract partner in this case) is the central data object. Cross-application component FI-CA for contract accounts receivable and payable is designed to cope with a large volume of postings for a large number of customers. The development of industry-specific enhancements for the utilities industry means that the SAP standard components Plant Maintenance (PM) and Customer Service (CS) can be used. These provide optimal conditions for managing service-orientated businesses. PM/SM is integrated with the following components: SD: management of customer quotations and orders, as well as execution of billing CO: allocation and settlement of service-related costs MM: processing of material requirements and goods movements related to service activities The Asset Management component (AM) supports the management of fixed assets. Material master records are maintained in the Materials Management component (MM) at the same time as device categories in IS-U; purchasing and stockkeeping of devices are processed via MM components. IS-U/CCS can be linked to external systems (consumption entry systems or billing systems, for example).

Customer Service in IS-U/CCS Business Partners:

Integration of Logistics & Accounting

W or kf lo w

Customer Customer Service Service

Other roles

W or kf lo w

Divisions: Electricity Services & Sales Gas Water Waste water District heating Device Management Waste disposal Meters/Devices/Service Multimedia Connections Service order Service contract Basic Goods Functions Charges

w lo kf or W

Consumption Entry

w lo kf or W

Contract A/R & A/P

Residential/ nonresidential customer Customer Information System Prospect & Marketing Owner Bill recipient Billing/ Installer Invoicing

Link to external billing systems

 SAP AG 1999

IS-U/CCS can be used in all market segments of the utilities industry (divisions/sectors). You can use IS-U/CCS to bill the consumption and manage the data of the following customers: - Residential customers - Nonresidential customers - Service customers - Prospects (potential customers) The business partner concept also allows you to manage data for other business partner roles, such as installers or bill-to parties.  The Customer Service component is part of IS-U/CCS and offers an efficient, process-oriented approach to processing business transactions. This component makes use of the functions of other IS-U/CCS components and is supported by the SAP Workflow System where necessary. The emphasis is always on providing a process-orientated view.  

Component Hierarchy

SAP Utilities Basic Functions Master Data Device Management Contract Billing

Front Office

Configure front office

CIC

Configure CIC

Customer Information

Configure data environment display

Invoicing Contract A/R + A/P Customer Service Work Management Information System Tools  SAP AG 1999

Customer Contacts

Process Execution

Define customer contact classes Define customer contact types ... Move in/out

Move-in Move-Out Owner Allocation

Disconnection/Reconnection

Processes in the Area Menu Customer Interaction Center Process execution Move-in/out/Move-in/ Move-out Owner allocation ACM E Mov ers

Disconnection/reconnection Rate maintenance

Marketing

0716192

The Johnsons

Sales processing  SAP AG 1999

Processes are transactions that support the most common business processes in a utility company.  The move-in business process is used to register the start of a customer's energy supply to a particular address. The result of move-in is a technical object that is complete and ready for billing.  Conversely, move-out is used to register the end of the energy supply to that address. A new address or bank details can be entered. Move-out supports a process for the final billing and meter reading.  Move-in/out is the generic business process for moving in and moving out and has a unified initial screen to allow you to perform the two transactions in a single step.  A business partner who owns the premise in question can be defined in the system using owner allocation.  There is also a transaction to support the business processes of disconnecting and reconnecting an installation or a device.  Rate maintenance allows you to change billing-relevant data.  You can define a loyalty program to give customers gifts or rewards within the framework of customer service.  IS-U sales processing provides support with all processes from creating a quotation up to the customer move-in.

Customer Interaction Center (L Form) Identification Identification

Telephony Telephony controls

Call Call status status

Action Action box box

Navigation Navigation area area

 SAP AG 1999

Application Application area area

Integration with External Communications Systems (1)

WWW

Fax

Letter

Archive integration

Telephone Call center integration

Internet

In person

Internet integration

IS-U/CCS CIC functions

IS-U Customer Information System

 SAP AG 1999

IS-U can be integrated with a variety of external communications systems used in your business on a daily basis.  The following slides deal with the three most important applications of this communications technology:  Archiving documents created in IS-U (bills to customers or welcome letters, for example) and carrying out optical archiving for incoming (or outgoing) documents that would otherwise only exist in paper form (such as faxes or letters).  Linking to a call center solution via the SAPPhone component. 

Sequence of Business Processes

Service Initial conndata ection creation

Move-in/out Move-in Move-out Move-in ACM E mov ers

 SAP AG 1999

Business Scenario (1)

An agent in the Customer Service department ofIDES Energy Inc. has a large number of customer-related business transactions to process in the course of the day. The work environment must be specially designed with this workload in mind. It is equally important, however, that the processes involved are as efficient as possible. Therefore this course deals with the following topics:

 The CIC as an efficient working environment  Options for configuring customer service processes: front office processes, workflow processes, and Web calls  Customer contact management  SAP AG 1999

Business Scenario (2)

The business transactions dealt with in the individual scenarios are taken from IDES Energy Inc. These include:  Various information functions  Various change functions  Move-in and move-out  Disconnection and reconnection  Create customer contact  Using IS-U sales processing

 SAP AG 1999  SAP AG

Customer Service - Overview: Unit Summary  mySAP Utilities with IS-U/CCS is an integrated component of the SAP enterprise software and uses functions of the mySAP standard components FI, CO, AM, SD, PM/SM, and MM.  The Customer Service component makes use of existing ISU/CCS functions. Its main purpose is to support the business processes of your utility company with efficient processes in the system.If you wish, you can use the SAP workflow system to help model efficient processes.  The CIC can be used to handle typical customer service processes. It enables agents to perform information and service functions efficiently. Customer contact management also assists the agent in supporting customers.  Typical business processes in customer service include:

     SAP SAP AG 1999  AG

IS-U sales processing Move-in, move-out and move-in/out Disconnection and reconnection Creating service connections

Customer Interaction Center (CIC)

Contents:  Customer Interaction Center (CIC) terminology  Using the Customer Interaction Center (CIC)  Functional scope of the CIC  Work processes in the CIC

 SAP AG 1999

Customer Interaction Center: Topic Objectives

At the conclusion of this unit, you will be able to:  Use the CIC  Describe the functional scope of the CIC

 SAP SAP AG 1999  AG 2001

CIC: Introduction, Requirements

 Customer orientation is becoming more important in competition SAP Utilities

 Utility companies have set up special departments for customer service  Customer-oriented processes are characterized by their similarity and frequent occurrence  Business processes need to be processed efficiently

 SAP AG 1999

Overview of CIC Functions

 Starting point for processing all business processes  Central starting point for processing transactions 

Efficient user interface (as few dialog steps as possible)

 Supported by fuzzy search to identify customers using incomplete/imprecise data  Appropriate work environment for every user 

Users can configure their own interface

 SAP AG 1999

Overview of Additional CIC Functions

 Call center integration 

Automatic caller identification by means of telephone number (ANI)

 Computer Telephony Integration (CTI) 

Agent allocation to telephone numbers/telephone queues



"Soft phone" functions

 Reminder scripting functions to provide call support  Logging of all activities  Automatic callback

 SAP AG 1999

Alongside the front office functions, the CIC offers the following additional functions: A call center is the area in a company where telephone calls are made and received. The CIC supports call center agents with telephone functions.  ANI stands for Automatic Number Identification  The CTI component is the interface to the telephone. The CTI establishes a link to SAP software via the SAPphone Gateway.  The Scripting component provides prompts to support agents, and can be customized for each individual agent.  



The logging component logs all the activities performed by an agent during the course of a call. The activities are logged in tables.



Callback can be planned and then executed automatically.

IS-U/CCS Integration: Front Office Information on and inquiries about: Business Partners:

Residential customer

Utility Services

Nonresidential customer Other customer Prospect Supplier Source of Info:

Agent

Customer Contact Management

Identification Account

Budget Billing

Sale of Goods

Customer Prospect Connection Premise

Immediate Information/ service consultation execution (optional) Account Status Move-In Payments Move-Out Rates/ Installment Conditions Plan Meter Reading Quotation

Workflowsupported process execution (optional)

Service Connection Disconn./ Reconn.

IS-U/CCS Customer Information System

 SAP AG 1999

The front office supports communication between the customer and the contact person in your enterprise.  You can use the functions of the customer information system directly from the front office.  Customer contact management enables the agent to view and create customer contacts quickly . 

Typical Front Office Calls Premise Premise

Create quotation for new service connection Customer information for the agent

Budget billing

Change budget billing plan R

Move-in/move-out processing Logging customer contacts

Bill INV OICE #:

P.O. #:

SOLD TO

Qty Or dered

Qty S hipped

PREMISE

Descr iption

Price

Total

Reprint bill

OFF ON

S ubt otal Sales Tax Data

SALE SPE RS ON

Total

Disconnection at customer request Complaints processing

 SAP AG 1999



Front office calls are the business processes that are carried out daily in your company.

Technical Structure

Phone system

IVR

CTI middleware

R/3 CIC

Applications (IS-U, CS, SD…)

SAPphone

SAPconnect

Internet Mail Fax

Optional use  SAP AG 1999



CTI architecture with IVR. IVR is an optional, yet frequently used method of customer interaction.



PROCESS FLOW  The IVR script initializes the interaction with the caller  IVR sends call-specific data to the telephony server  Phone system forwards call to wait queue/phone extension  Phone system informs CTI link of the forwarded call  CTI link informs telephony server  SAP application server is informed of incoming call  Agent sees dialog box with ANI  Phone call is forwarded to agent  Phone server transfers call-specific data



This course covers the configuration and use of the Customer Interaction Center within the mySAP Utilities component.

CIC Terminology

 Framework  Components  Component profiles  Agent  Call Center  CTI layer  CIC profile

 SAP AG 1999



 

   

The framework is a "toolkit" structure that enables you to flexibly customize the CIC. You can add any type of component to the framework in order to provide agents with the best possible working environment. The components represent the functions that can be used in the CIC. The instances of the individual components are referred to as "component profiles". They define, for example, which processes can be called in the action box. You can define different component profiles for each component. All users of the CIC front office functions are called "agents". A call center is the area in a company where telephone calls are made and received. Companies usually have several different call centers. The CTI establishes a link to SAP software via the SAPphone Gateway. It forms the interface to the phone system. The CIC profile provides a custom-tailored screen view for the agents in the call center. It is specially customized to each individual agent's skills and responsibilities. The profile is based on a framework and component profiles, and is linked with the agent through the organization management functions.

The CIC in Different Layouts

 Six vertical screen areas (SAP standard and IS-U)

 L form for large pictures (IS-U-specific)  L form for small pictures (IS-U-specific)

 SAP AG 1999

The framework is the foundation for all the functions that can be used in the CIC. The definition of a framework (framework ID) is identical to defining a screen in which you can select different functions for the agents in the various screen areas. The same framework can result in different screen views; only the components (screen areas) have the same arrangement. The framework enables the interaction between the selected components by dividing the system functions in visible (screen presentation) and hidden (background processing) components and using an event-driven mechanism.  First choose a screen for the framework. By selecting a screen, you determine the basic screen layout of the CIC. You have three options: Screen with six vertically arranged screen areas (slots) Screen arrangement in L form (large), number 8101 Screen arrangement in L form (small), number 8100 

Processing a CIC Contact

CIC contact

Business partner search and confirmation Customer overview / data environment

Clipboard

Processing the business process in the application area Start from action box / environment End of contact with logging  SAP AG 1999

Customer Contact

Contact Contact is is created created with with "End "End contact" contact"

Activate Activate / deactivate contact contact Contact Contact data data

Field Field for for user-defined user-defined text text  SAP AG 1999

User Session

User session

Call

E-mail

...

@

......

Call

 SAP AG 1999

Data Finder: Process Flow

Entry

Tool for finding data objects

Search criteria Name first/last Street/house number City/zip code ........... Company code Division ..............

Hit list (optional)

Selection

Object

Object type required  SAP AG 1999

The data finder search takes all the search criteria into account together in an AND operation. The data finder supports generic (wildcard) searches using *. To search for the name Winfield or Wingfield, for example, you can enter the string Win*field in the name field of the search criteria.  Two different components are available for finding data in IS-U (i.e. for identifying data objects): · ISUSDPART (business partner search in IS-U) · ISUFINDER (IS-U data finder) The functionality of both components has been tailored for use in the CIC. For example, the IS-U data finder component (ISUFINDER) can only be used together with a framework with vertical slots, while component ISUSDPART (business partner search in IS-U) is provided for the L-shaped framework.  The business partner search component in IS-U is a specific search function that exclusively provides data for IS-U/SD business partners. If you use the CIC with the L-shaped framework architecture, you should use the business partner search in IS-U.  

Data Finder: Use

Tool for finding data objects  Identification of entry objects for calls in the CIC (standard layout)  Search function for entering IS-U transactions

t n o Fr ce/CIC i off

 Search method for objects in the BOR

 SAP AG 1999



The Business Object Repository (BOR) is the strategic, object-oriented interface with SAP business functions (see the section on front office calls).

Starting a Call in the CIC (Standard Layout)

Search criteria

Clipboard

Name Street/city

Customer Bill number

Calls - Display bill - Bill-related complaint - Customer contact - ....

Object called

Data finder Hit list Selection

Ele c bill tricity ......

 SAP AG 1999

The CIC is an interface for entering the business processes that agents deal with in their daily business activities.  These business processes are started using data that is either entered by the agent directly, determined via a search function, or stored in the clipboard.  Processed data (such as a customer, contract or device) is sent back from the business process to the clipboard and stored there. 

CIC Telephony Functions Telephony Telephony controls

•• Forward, Forward, conference, conference, call call waiting, waiting, hold, hold, ... ...

Customer Customer is is displayed displayed

 SAP AG 1999

Call Call status status of of all all calling calling parties parties ANI ( Automatic Number Identification ANI Automatic Number Identification)) DNIS ((Dialed Dialed Number Number Identification Identification Service Service)

The Action Box

Drop-down Drop-down menu menu •• Overviews Overviews •• Transactions Transactions •• CIC CIC processes processes •• Workflows Workflows  SAP AG 1999

The Navigation and Application Area

 Prerequisite: CIC profile must be integrated with component profile category DEFAULT_WORKSPACES  NAV_AREA component for the navigation area  APPL_AREA_2 component for the application area

Central Customizing maintenance in SAP Utilities  SAP AG 1999

The Application Area (L Form)

Tab pages with  Customer overview  Account balance  CIC contact  SAPGUI for HTML: IS-U/CSS and R/3 transactions  Sales and distribution processing  Workflow inbox  Any HTML pages

 SAP AG 1999

Customizing the L Form Customizing is performed in two areas within the Implementation Guide Customizing for CIC standard functions 

Customer Service -> Customer Interaction Center (CIC)

Customizing for IS-U extensions 

SAP Utilities -> Customer Service -> Customer Interaction Center

 SAP AG 1999

Customer Interaction Center (CIC): Exercises Unit: Customer Interaction Center (CIC) Topic: Using the CIC

• Description of the objectives and application areas of the CIC • Using the CIC for efficient process Quick, complete processing of customer inquiries raises customer satisfaction and increases efficiency. Experience in using the CIC contributes considerably to these goals. In these exercises you implement the CIC using examples of typical customer inquiries.

Business partner

PJ0203A0## (0##: group number) Rose Taylor 0## Oxlade Drive Boston MA, 02100

Contract account number

PJ0203A0## (0##: group number)

Electricity contract/installation

PJ0203A0## (0##: group number)

Water contract/installation

PJ0203B0## (0##: group number)

Electricity meter

PJ0203A0## (0##: group number) Double-rate meter

Water meter

PJ0203B0## (0##: group number) Single-rate meter

Move-in document

PJ0203A0## (0##: group number)

Connection object

PJ0203A0## (0##: group number)

1-1 True or false? 1-1-1 The CIC serves as the central work environment for each agent and can be individually configured to meet their individual requirements. _________________________________________________________ 1-1-2 The CIC contains a tool for finding data objects (such as business partners, contract accounts and contracts) created in the IS-U system. _________________________________________________________ 1-1-3 The data finder always provides the business partner as its search result. _________________________________________________________ 1-1-4 The CIC supports you in providing simple information, as well as processing complex business processes. _________________________________________________________ 1-1-5 Front office processes can only be performed using the action box in the CIC. _________________________________________________________ 1-2

The CIC (L form) is divided into four units that efficiently help agents perform their customer service duties. Name these four units and describe their purposes: Unit 1: _____________________________________________ Purpose: _____________________________________________ Unit 2: _____________________________________________ Purpose: _____________________________________________ Unit 3: _____________________________________________ Purpose: _____________________________________________ Unit 4: _____________________________________________ Purpose: _____________________________________________

1-3 Search criteria The upper left of the CIC contains the Business partner block, which you can use to identify your business partner based on the specified criteria. You can enter additional criteria using the data finder (pushbutton

“All search criteria”).

1-3-1 Use the wildcard search function of the business partner search to find all business partners whose last name begins with T. Did you find any? ______________________________________________________ 1-3-2 You determine that this information is insufficient for identifying the business partner and are given the address as additional information: Oxlade Drive, house number 0## (0##: group number). (Note that house numbers are saved in the system with leading zeros.) Determine the correct business partner. Business partner:________________________________________ 1-3-3 Search for another customer whose electricity installation is on Oxlade Drive. How many customers do you find using this information? As additional information you are given the number PJ0203A0## of the defective device. Business partner:______________________________________________

1-4 Information from the CIC Business partner PJ0203A0## wants to know how much their last bill was. Display the bill. You can simulate the bill on the screen. Final bill amount: _______________________________________________ When is the bill due? ________________________________________ How much is the future budget billing amount? ___________________________ Use the customer overview for information.

1-5 Navigation area: Process Change bank data Process description: A business partner named Taylor on ## Oxlade Drive (##: group number) calls. She would like repayments to be transferred to the following account in the future: bank number 083000108, account number 345670## (0##: group number). 1-5-1 First, search for customers named Taylor on 0## Oxlade Drive (##: group number) and start the Change bank details process. Enter the bank details in the business partner. Save the data, then branch to the contract account, where you must specify the bank details for outgoing payments. Change the outgoing payment method from Check to Bank transfer. Enter the bank details you just defined in field “Bank details outg.”. Save the data, then branch to the screen for creating a customer contact. You can save this without making any changes. Customer contacts will be explained in detail in the next unit.

Customer Interaction Center (CIC) Solutions Unit: Customer Interaction Center (CIC) Topic: Using the CIC

Business partner

PJ0203A0## (0##: group number) Rose Taylor 0## Oxlade Drive Boston MA, 02100

Contract account number

PJ0203A0## (0##: group number)

Electricity contract/installation

PJ0203A0## (0##: group number)

Water contract/installation

PJ0203B0## (0##: group number)

Electricity meter

PJ0203A0## (0##: group number) Double-rate meter

Water meter

PJ0203B0## (0##: group number) Single-rate meter

Move-in document

PJ0203A0## (0##: group number)

Connection object

PJ0203A0## (0##: group number)

1-1 True or false? 1-1-1 True 1-1-2 True 1-1-3 True: While you can enter other search criteria in the data finder, such as a contract, a contract account, or a device number, the result is always the corresponding business partner. 1-1-4 True 1-1-5 False: Within the CIC, front office processes can be performed both with the action box and via the context menu of the corresponding object in the navigation area.

1-2

CIC structure (L form)

Unit 1: Identification and installation Purpose: Selecting data using flexible search criteria. Unit 2: Navigation area Purpose: Providing specific information to customer inquiries. Starting comprehensive business processes, such as with SAP Business Workflow. Unit 3: Application area Purpose: User-defined overview pages, such as SAP Business Workflow inbox, CIC contact activity management, and more Unit 4: Action box Purpose: Calling specific business processes. 1-3 Search criteria From the SAP Easy Access menu, choose Utilities Industry → Customer Service → Front Office/Cust.Interact.Center → Customer Interaction Center. 1-3-1 To start a wildcard search, enter “T*” under the last name in the search criteria and then click on the hourglass button. A list of business partners is displayed (if a dialog box is displayed with the message that the hit list may be incomplete, you can simply click to confirm). 1-3-2 Business partner

PJ0203A0## (0##: group number)

1-3-3 Open the data finder in the business partner search. Click on the Technical data tab and enter O* in the Street field. Now enter the number PJ0203A0## in the Serial number field and press Enter. The arrow in the data finder is now green, which means search criteria have been defined. Press Enter to search for the corresponding business partner and press Enter again to confirm. The required device can be found in the business partner’s data environment. Business partner

PJ0203A0## (0##: group number)

1-4 Information from the CIC Enter the specified customer number in the search criteria and identify the customer. Then start the Customer overview process from the Info call group in the action box. The amount of the last bills is displayed in the Bills area. Double-click on the last billing amount. The system displays the bill document. Press the Simulate bill button. A dialog box appears where you enter Printer as the output type and LT0Q as the output device. When you press Enter, the bill is displayed. Return to the document overview and click on the Header data tab page. The Due date for net payment is located in the General data group. The future budget billing amount is displayed in the Budget billing due dates area of the customer overview. The cumulated budget billing amount is calculated from the budget billing payments for water and electricity.

1-5 Navigation area: Process Change bank data Identification Identify the customer using the search criteria, as described in Exercise 1-3. Start the transaction Click the right mouse button on the contract account in the customer environment. Click on Change bank data in the context menu. This activates the change mode for the contract partner. Click on the Payment transactions tab page and enter the specified bank details with any ID (such as 0002). Press the Save button. You branch to the contract account. Choose the second tab strip, Payments/Taxes, and enter a B for bank transfer in the Outgoing payments field, and enter the bank details ID in the Bank details ID field. Using the F4 selection, you can view all bank details entered in the business partner, and select one of them. Save the changes in the contract account. You automatically branch to the Create Contact screen. The fields are already filled with data so that you only have to save to log the customer contact.

CIC Configuration

Contents:  Structure of the Customer Interaction Center (CIC)  IS-U-specific components  Linking a CIC profile with an HR organizational unit

 SAP AG 1999

CIC Configuration: Unit Objectives

At the conclusion of this unit, you will be able to:  Integrate IS-U functions in the CIC  Customize the CIC  Define the CIC assignments via the organizational structure

 SAP SAP AG 1999  AG 2001

CIC Terminology

Framework + Components Visible components Hidden components +

Component profiles = Customer Interaction Center profiles (CIC profile)

 SAP AG 1999

    

The structure of the CIC enables you to selects the components you want and arrange them on the screen (framework). The purpose of the framework is to enable you to use the components you want to use. The system functions are divided into visible components (that appear on the screen) and hidden (background processing) components. You need to modify most of the components. These modifications are referred to as component profiles. The CIC profile is a collective profile composed of all the settings made in the individual components contained in a framework. The CIC profile determines what the agent's user interface looks like. Infotype "CIC profile 1260" allocates the agents in the structure organization. You can define and allocate CIC profiles based on the agent profiles at your company.

CIC Profile: Framework and Components

Framework

Component profile

Visible components ACTION_BOX Action box

ACTION_BOX_1 FO config. IS-U

BD_ANZEIGE

Business object display

ACTION_BOX_2 General FO config.

ISUFINDER

IS-U data finder

CCONT_4

Four components

CCONT_2

Two components

CTI_PROFIL_1

Administration 1

CTI_PROFIL_2

Administration 2

CUST_OVIEW HTML customer overview CCONT

Component container

Hidden Components BD_MARK

Selection function

CTI

Telephony integration

CALLCTR

Call center

CALLBACK Call back

CIC

i le f o pr

 SAP AG 1999

Visible components are displayed as subscreens in the slots. Hidden components provide background functions that do not need their own screen areas.  Examples of visible components include: · Action box · Clipboard · IS-U data finder · Component container Examples of hidden components include: · Selection function · Telephony integration  Example: Use the Action box component.. This component is allocated to a framework so that it can be arranged on the screen. You then create one or more component profiles for the action box component. In this case, the component profile is a front office configuration. The CIC profile, new versions of which can be created for different agent groups, can contain the action box. In this case, the action box is assigned a component profile (a front office configuration). The CIC profile is allocated to agent groups (such as planning or organization departments) using the structure organization. 

CIC Configuration: Overview

CIC profile Profile attributes Profile category + instance

FO framework Components Visible / hidden

C o m p o n e n t c o n f i g u r a t i o

n  SAP AG 1999

Action box Instances Calls

Navigation and application area N/A components Instances Calls . . .

Calls Methods Front office processes Workflows BDC sessions HTML operations

CIC Customizing (1)

Title bar

1. Create framework

 SAP AG 1999

A framework serves as a placeholder for the screen structure. When you create a new framework, none of the existing frameworks contains the components you need in the required layout. Framework customizing also sets the screen title and controls whether the framework is active.  You can reuse frameworks because they only determine the selection and positions of the visible components in the screen and determine which hidden components are assigned. The same framework can result in different screen views; only the components have the same arrangement. 

CIC: Visible Components

 Visible components can be arranged on the screen. Examples of components provided by SAP include: 

Action box: calls SAP transactions



Business object display: saves business objects and business data



Call status display: displays the status of calls for the agent's extension



Find and display customer data: functions for finding and displaying customer data



Application area: provides an area for integrating HTML pages



Quick keys: the pushbuttons assigned to the telephony functions

 SAP AG 1999

CIC: Quick Keys

End call Cancel hold

Wait Hold/retrieve

Pick up Deflect

Cancel wait Consult

Update Connect

Hold Direct dial

 Provides fast access to frequently used telephony functions  Minimizes the search with mouse and menu  Replaces the phone handset  Configuration of screen position and key assignment  Are displayed in the lower margin of the CIC screen if necessary

 SAP AG 1999

CIC Customizing (2): L Form

Slot Slot 11 Business Business partner partner

Slot Slot 22 Phone Phone

Slot Slot 5 Navigation Navigation area area

Slot Slot 66 Application Application area area

Slot Slot 44 Action Action box box 1. Create framework 2. Assign visible components to slots

Slot Slot 33 Not Not used used Slot Slot 77 Not Not used used

 SAP AG 1999

In this step, you determine which visible components you want to have in the framework, as well as the slots in which they will appear.  The selection and arrangement of the components cannot be chosen freely in the L-shaped framework. The following component assignments are possible: Slot 1: ISUSDPART: business partner identification Slots 2 and 4: ABOX_SLIM, CALL_STATE, QUICK_KEYS Slot 5: NAV_AREA: navigation area Slot 6: APPL_AREA_2: application area  You can use several special components at the same time in the application and navigation areas in slots 5 and 6. You configure these settings in Customizing under Maintain Navigation and Application Areas.  Slots 3 and 7 are normally not used in IS-U. You can use these slots to integrate a solution database, for example. For more information on solution databases, refer to the IMG under Customer Service -> Solution Database. In a framework , you cannot use the same component more than once with different component profiles. A component can only be used once in a framework. 

CIC Customizing (2): Vertical Slots

Title bar Slot 1: Component container Slot 2: Script display Slot 3: Customer component X Slot 4: Find and display customer data

1. Create framework 2. Assign visible components to slots

Slot 5: Action box Slot 6: Telephony function keys

 SAP AG 1999

In the framework with six vertically arranged slots, you can arrange the following visible components in any order: ACTION_BOX: Starts calls with table display ABOX_SLIM: Starts calls. Displayed as application toolbar with drop-down menus BD_DISPLAY: Clipboard for saving objects (such as a contract account) CALL_STATE: Displays the current calling parties (when telephony integration is active) CCONT: Component container for adding additional components ISUFINDER: IS-U search criteria QUICK_KEYS: Function keys SCRIPT_DISP: Reminder scripting display SOL_SEARCH: Input screen for the solution database  APPL_AREA: Standard application area for HTML configuration calls that are started in the action box. 

Hidden Components

 Background processing functions 

Not displayed in the user interface



Background functions provide services to the framework



Example 1: Select function

 

An object saved in the clipboard should be selected for immediate further processing

Example 2: Telephony integration



The component has been assigned a certain CTI OK code (such as "Hold"). The component uses the extended SAPphone API to perform the requested CTI activity.

 SAP AG 1999



There are three different types of hidden components: 1. Independent components - AUTOCALL (automatic ac-tivity) - CALLBACK (return calls) - CIC_TOOLBAR (icon bar and toolbar), use required - HLOG (logging) 2. Components required for certain visible components to work - CTI (telephony integration) for CALL_STATE - HIDDEN SCRPT (scripting) for SCRIPT_DISP 3. Components that can be used in combination with visible components - BD_MARK (selection function) with BD_DISPLAY - CALLCTR (call center) with CALL_STATE

CIC Customizing (3) Slot Slot 11 Business Business partner partner

Slot Slot 22 Phone Phone

Slot Slot 5 Navigation Navigation area area

Slot Slot 66 Application Application area area

Slot Slot 44 Action Action box box 1. Create framework 2. Assign visible components to slots 3. Assign hidden components to the framework

Slot Slot 33 Not Not used used Slot Slot 77 Not Not used used

 SAP AG 1999

Hidden components enable background processing. Hidden components can be arranged in any order. There is no limit to the number of possible hidden components.  SAP supplies the following hidden components:  Return calls: (CALLBACK) Creates and processes return calls. This component is not part of the framework screen and is therefore considered to be hidden.  Call center strategy: (CALLCTR) Controls processing of the call information  Toolbar: (CIC_TOOLBAR) While it appears on the screen, it does not occupy any of the slots, and is therefore considered to be hidden  CTI: (CTI) Supplies all the telephony functions in the background  Scripting engine: (HIDDEN SCRPT) Component used to determine values for variables like "customer's name" and "time of day"  Logging: (HLOG) Logs the agents' activities  Hidden action box: (HIDDEN_ABOX) Every framework with a visible action box also requires a hidden action box component  If you do not use telephony integration, you do not need the components CALL_STATE , SCRIPT_DISP, HIDDEN SCRPT, CALLCTR, or CTI. 

CIC Customizing (4)

e l i f o r p CIC

Slot Slot 11 Business Business partner partner

Slot Slot 22 Phone Phone

Slot Slot 5 Navigation Navigation area area

Slot Slot 66 Application Application area area

Slot Slot 33 Not Not used used

Slot Slot 44 Action Action box box

1. Create framework 2. Assign visible components to slots 3. Assign hidden components to the framework 4. Assign framework and component profiles in the CIC profile

Slot Slot 77 Not Not used used

 SAP AG 1999

The CIC profile combines the framework with the instances of the components used. Organization management is used to establish a link between the CIC profile and the agent.  If you defined that an action box is to appear in slot 4, for example, then you determine which action box is used in this step. 

SAP Components and Profile Requirements (1)

IS-U

X X X X

X X

Visible components

Description

Component profile required

ACTION_BOX

Action box

ACTION_BOX_CONFIGURATION

ABOX_SLIM

Action box

ACTION_BOX_ CONFIGURATION_SLIM

BD_DISPLAY

Business obj. display

No profile required

CALL_STATE

Call status

No profile required

CCONT

Component container

COMPCONT_PROF

ISUSDPARTNER

Search functions

No profile required

QUICK_KEYS

Quick keys

QUICK_KEYS_CONFIGURATION

SCRIPT_DISP

Script display

SCRIPT_PROFILE

SOL_SEARCH

Solution search

No profile required

X

APPL_AREA_2

Application area

DEFAULT_WORKSPACES

X

NAV_AREA

Navigation area

DEFAULT_WORKSPACES

X

X: Is used in IS-U (L form)  SAP AG 1999

Description Action box comp. configuration Action box comp. configuration

Without telephone X X X

Component container IS-U business partner search Quick keys button configuration profile

X X X

Scripting profile

SAP Components and Profile Requirements (2)

Hidden components

Description

Component profile required

BDMARK

Selection function

BD_MARK_PROF

CALLBACK

Callback queue

CALLBACK_ASSIGN_QUEUE_ PROFILE

CALLBACK_PROCESS_QUEUE_ PROFILE CALL_CENTER_COMP_ CONFIGURATION

BDD profile Selection function Assign callback queue profile Callback component configuration Edit callback queue profile Call center component

TBAR_PROF

CIC toolbar

CALLBACK_CONFIGURATION

CALLCTR CIC_TOOLBAR CTI

Call center component CIC toolbar / exclusion CTI

CTIADM_PROF No profile required

HIDDEN_SCRPT

Script text

No profile required

HLOG

Logging

ACTIVITY_LOGGING_ PROFILE

HIDDEN_ABOX

Action box

No profile required

 SAP AG 1999

Description

Without telephone X X X X

X

CTI administration profile Assign CTI wait queue profile X Activity codes log profile

X X

CIC Customizing (5)

e l i f o r p CIC

Slot Slot 11 Business Business partner partner

Slot Slot 22 Phone Phone

Slot Slot 55 Navigation Navigation area area

Slot Slot 66 Application Application area area

Slot Slot 33 Not Not used used Slot Slot 77 Not Not used used



SAP AG 1999

Slot Slot 44 Action Action box box

1 2

3

4

5. Assign CIC profile to an organizational level in organization management

Procedure

1. Analysis of the business processes 2. Definition of front office processes 3. Define a front office configuration 4. Define frameworks 5. Define the component profile 6. Define CIC profiles 7. Allocate CIC profiles to organizational plan

Customer Interaction Center  SAP AG 1999

To use the CIC, you have to analyze the business processes and define them in the system (steps 1 and 2). The processes are summarized in a front office configuration which is used in the CIC as a component profile for the action box.  Using the front office without the CIC (not possible after Release 4.51)  You have to define a configuration determination in order to assign a specific front office configuration to each individual agent.  Using the CIC (available from IS-U/CSS V4.51)  You can integrate other CIC functions (CIC components) into the framework.  You can define modifications for each CIC component in the form of component profiles. The front office is the component profile for the action box component. 

Organizational Plan

Organizational unit Organizational unit Job

Organizational unit Job

Organizational unit

Position

Position

Holder

Holder

Position

Holder

Holder  SAP AG 1999

The organizational plan is a means of modeling your company's structure in the system. The organizational plan comprises organizational units and all their interrelationships. Organizational units represent logical business units in your company and can be structured to form a hierarchy that represents your business as a whole. The organizational units can be function-based or region-based or reflect other aspects of your business (examples are: business areas, departments, project groups). The organizational plan can have any number of organizational unit levels (the slide shows two levels).  The organizational plan contains positions that are linked to the organizational units.  Positions can have one or more holders assigned to them (and each holder can be assigned to more than one position). Holders are responsible for particular tasks and are one of the following: A user - someone with an SAP system user ID A person - someone, maybe an employee in your company, without an R/3 system user  Workflow tasks can only be carried out by holders with access to the R/3 system.  The organizational plan also contains jobs, which describe tasks that occur in a number of different positions.  

Allocate the CIC Profile in the Organizational Plan

Organizational unit e.g. utility company

CIC

?

Organizational unit

?

e.g. customer service

?

Position

Position

Position

e.g. move-in/out processing

e.g. bill complaints

e.g. technical service

User

User

User

e.g. Mr. Miller

e.g. Mr. Smith

e.g. Mr. Jones

i le f o pr

?

 SAP AG 1999

The energy company depicted above has the organizational unit Customer service. The unit has three different positions- an agent is allocated to each of them.  CIC profiles can be allocated to users on either the position or organizational unit level. To do this, use infotype "CIC profile". Infotypes enable you to describe and define the different attributes and characteristics of objects. 

CIC Organizational Structure (Administration)

Customer service organization

Organizational unit

Sales agent 1 Sarah Hodder Sales agent 2

Position

Peter Fellows Erin McCart Patricia Needham

User

Rose Loo Sales agent 3 John Wilkens Peter Nichols Betsy Groh

 SAP AG 1999

The organizational structure is used to model your company's organizational plan. It is a hierarchical structure consisting of organizational units, positions, and holders. You can assign user names or personnel numbers to the positions. A user can hold several positions in different organizations. For example, an agent can belong to sales and service at the same time.  To create a new position in the hierarchy, position the cursor on the line that contains the name of the organizational unit and click the Create position button. You can choose an abbreviation for the position in the F4 list display. Press Save.  To assign a user in the hierarchy, position the cursor on the line that contains the name of the position and press Assign holder. Enter the SAP user ID and save. 

CIC profile Tailored to different skills ... CIC profile for new agent CIC profile for agent

Scripting support required

No scripting support required

Tailored to different requirements... CIC profile for sales agent CIC profile for service agent

Sales functions in action box and telephony toolbar required Service functions required in action box No telephony toolbar required

 SAP AG 1999



The CIC profile saves settings regarding the configuration and screen structure of the Customer Interaction Center. It can be configured according to the specific requirements of a certain agent, a group, or an entire call center. For example, a new agent may need support from the scripting component, while another agent may not want to see this component while working with the Customer Interaction Center. Call centers that deal with different types of calls usually need different components and functions.

Assigning a CIC Profile to a User ID (1)

Customer service organization Sales agent 1 Sarah Hodder Sales agent 2 Peter Fellows Erin McCart

CIC profile CIC profile for A CIC profile CIC profile for sales agent

Patricia Needham

1. Choose the desired organizational level. 2. Choose Goto -> Object description -> Enhanced object description

 SAP AG 1999

The CIC profile saves the configuration and screen structure for the framework. The CIC profile is assigned to the agent through the HR infotype. An infotype enables you to describe and define different attributes and characteristics for objects.  A CIC profile must be assigned for every agent who works in the CIC, either at the organizational unit level (all agents within the same organizational unit use the same CIC profile) or at position level (agents who are assigned to the same position use the same CIC profile).  To assign a CIC profile (infotype 1260) to an agent or an organization, proceed as follows: 1. Click the required organizational level (either organizational unit or position). 2. Choose Goto -> Object description -> Enhanced object description. 

Assigning a CIC Profile to a User ID (2)

Maintain Planning Data: Choose Infotype Object Edit Goto Utilities Settings System Help

3. Choose infotype "CIC profile"

 Plan variant

01

Current plan

Object cat.

S

Position

Object ID

50012948

Object abbrev. Active

Agent 1

Agent 1

Planned Submitted

Approved Period

Infotype name Object Description CIC profile

4. Click the Create or Change icon



Rejected

5. Press F4 to display list of available CIC profiles 6. Choose the CIC profile and click the "Adopt" icon

 SAP AG 1999

3. A list of infotypes appears. Scroll down this list until you reach CIC profile (infotype 1260). 4. Click the infotype icon Create or Change. 5. Press F4 in the next screen. A list of all the available CIC profiles is displayed in the CIC profile ID field. 6. Choose the required CIC profile and choose Input/Save.

CIC Profile: Inheritance CIC profile: ALL Framework: S4 1. Script: Standard 2. Action box: Sales 3. Find: Customer ...

Telesales organization Sales agents Sarah Hodder New agents Peter Fellows

CIC profile: New Framework: S4 1. Script: New agent

Erin McCart Patricia Needham

New agent starts CIC:

Framework: S4 1. Script: New agent 2. Action box: Sales 3. Find: Customer

 SAP AG 1999

When a CIC profile does not contain all the component profiles in the framework at a lower level, then the system searches for a different CIC profile with the same framework at a higher level in the organizational structure, in order to retrieve the additional profiles.  This method is useful for providing new employees with special components or for defining default values if the Customizing at a lower level is incomplete.  You can display the selected configuration in the CIC Front Office screen by choosing Agent -> Framework status. 

Starting the CIC

 At the start of the front office transaction (CIC0): 

The system searches the organization management to determine which profiles to assign to the executing user.



The profiles determine which components the framework loads for the user and how the individual components work.



The profile values are saved in a generic framework information store.



The framework loads all configurable visible and hidden components.

 SAP AG 1999



Profile 00000001 is defined as the default profile in the IS-U application. Therefore, users who have not been assigned to an organizational unit, a position, or a job can still call the CIC.

CIC Configuration: Summary

You are now able to:  Integrate front office functions into the CIC  Define frameworks  Create component profiles  Define CIC profiles  Assign a CIC profile to an employee or an organizational unit

 SAP AG 1999

Exercises Unit: Customer Interaction Center (CIC) Topic: Configuring the CIC

• Create a CIC framework and a CIC profile

You want to extend the existing CIC standard profile with specific additional calls. In this section, you will create a CIC framework and a CIC profile for the Customer Interaction Center.

1-1

Framework The framework describes the screen layout of the Customer Interaction Center. Choose the components you want to use and arrange them on the screen. The framework differentiates between different types of component. Which ones? 1. ______________________________ 2. ______________________________ Which components are used in framework ZFRAME000? 1. _______________________________ 2. _______________________________ 3. _______________________________ 4. _______________________________ 5. _______________________________ 6. _______________________________ 7. _______________________________

1-2

Create the framework and CIC profile In this exercise, you will define the structure of the Customer Interaction Center in several steps. 1-2-1 Creating the framework ID with components First create your own framework ID. To do this, copy framework ZFRAME000 to your own framework ID ZFRAME0## (0##: group number). 1-2-2 Creating the CIC profile Create a CIC profile with the key ZPROF0## (0##: group number) and name CIC profile group 0## and allocate it to your framework ID ZFRAME0## (0##: group number). Use CIC profile ZPROF000 as a copy template. 1-2-3 Creating component profiles What are the component profiles used for? For which components of the original front office structure are the profiles needed? Which component profile category is responsible for the instantiation of the action box, and what is the current instance in your CIC profile ZPROF0##? After you have displayed the component profiles assigned in your CIC profile, change the instantiation of several of the components. 1-2-4 Defining the component profile for the action box In Customizing, call up the component configuration that you identified as the instantiation of the profile type for component ABOX_SLIM in Exercise 1-2-3. Which call types can be defined as calls in the action box? Copy configuration ZABOX000 to the name ZABOX0## and define this instantiation in the profile attributes of your CIC profile, ZPROF0##.

1-2-5 Assigning the CIC profile to an agent For a specific agent to be able to use a specific Customer Interaction Center, that agent must be assigned the appropriate CIC profile in the organizational structure. At which levels of the organizational structure can you allocate CIC profiles to agents? 1.___________________________ 2.___________________________ Allocate your CIC profile to a position. A position has been created for you for the purposes of this course. You an find it using the following menu path: Tools → Business Workflow → Organizational Structure → Organizational Structure → Organization and Staffing → Change. First call up the staff assignments for organizational unit IDES_5310 and define the assignment of your CIC profile to position Customer Service ## (##: group number). 1-2-6 Calling the Customer Interaction Center Call the CIC and choose the CIC profile you created. Identify business partner PJ0203A0## (##: group number) and examine the data environment of the navigation area. Which object is the entry object? Which calls have been defined for the contract account?

Customer Interaction Center (CIC) Solutions Unit: Customer Interaction Center (CIC) Topic: Creating a CIC Profile

1-1

Framework

We differentiate between visible and hidden components in the framework. In Customizing, choose Utilities Industry → Customer Service → Customer Interaction Center. The Change View "CIC Framework" Overview screen appears. You will find framework ZFRAME000 there. Select this framework and then choose the Visible components and Hidden components functions in turn. The following visible components have been selected: ISUSDPART IS-U Business Partner Search CALL_STATE Call state ABOX_SLIM IS-U Action Box Slim NAV_AREA IS-U Navigation Area APPL_AREA_2 IS-U Application Area The following hidden components have been selected: CIC_TOOLBAR Toolbar BD_MARK BDD Selection service 1-2

Create the framework and CIC profile

1-2-1 Creating the framework ID with components In Customizing, choose Utilities Industry → Customer Service → Customer Interaction Center → Maintain Front Office Framework ID and Parameters. Select entry ZFRAME000 and choose the Copy function. Change the copied framework ID to ZFRAME0## and the framework description to IS-U framework group 0##. Do not change the title number, the screen, or the status. Press Enter. The message appears that the entry to be copied has dependent entries. This refers to the allocated components, which you also want to copy. Choose the Copy all button in the message. Choose Copy all in the dialog box. A confirmation prompt appears informing you that 7 entries were copied. Choose Confirm and then save your entries.

1-2-2 Creating the CIC profile In Customizing, choose Customer Service → Customer Interaction Center (CIC) → CIC Profiles → Maintain CIC Profiles. Now select CIC profile ZPROF000, choose the Copy as ... function, and enter CIC profile ZPROF0## (0##: group number) with profile description CIC profile group 0## and your framework ID ZFRAME0## (0##: group number). Press Enter. The message appears that the entry to be copied has dependent entries. This refers to the allocated components, which you also want to copy. Choose the Copy all button in the message. Choose Copy all in the dialog box. A confirmation prompt appears informing you that 5 entries were copied. Choose Confirm and then save your entries. 1-2-3 Creating component profiles Select your CIC profile ZPROF## and navigate to the profile attributes. The component profiles enable you to create individually instances of the selected components. You only need to modify the components you selected yourself. Of the components that have been selected in framework ZFRAME0##, components IS-U Action Box Slim ABOX_SLIM (using profile category ACTION_BOX_CONFIGURATION_SLIM) and component BDD selection service BD_MARK (using profile category BD_MARK_PROF) require special profiles. In addition, the definition of the navigation and application area is integrated in a CIC profile as a profile with component profile category DEFAULT_WORKSPACES. 1-2-4 Defining the component profile for the action box Choose IMG path Customer Service → Customer Interaction Center (CIC) → Component Configuration → Settings for Action Box → Determine Configuration Profiles for Action Box. Enter the configuration name ZABOX000 and choose Display. The following types of calls can be used: -

Method

-

Workflow

-

Front office processes

-

Batch input sessions

-

HTML operations

Copy configuration ZABOX000 to the name ZABOX0## (##: group number) and define this configuration in the profile attributes of your CIC profile, ZPROF0##, under profile category ACTION_BOX_CONFIGURATION_SLIM.

1-2-5 Assigning the CIC profile to an agent A CIC profile can be used in the following levels in the organizational structure: 1. Organizational unit level (all agents within the same organizational unit use the same CIC profile) 2. Position level (agents who are assigned to the same position use the same CIC profile) Double-click on the organizational unit in the search area and search for organizational unit IDES_5310. Double-click on the Customer Service organizational unit in the selection area to display the staff assignments of the Customer Service organizational unit in the overview area. When you double-click on position Customer Service ## (##: group number), the detailed information is displayed in the detail area of the screen. Choose Goto → Object details → Extended object description to access the object processing screen. Scroll down the infotype list and select item CIC profile. Choose the infotype icon Create. In the next view, press F4 for field CIC Profile ID to display a list of available CIC profiles. Choose the profile ZPROF0## (0##: group number) and then save your entry. You have already been allocated to this position as a user. 1-2-6 Calling the Customer Interaction Center Choose path Utilities Industry → Customer Service → Front Office/Cust.Interact.Center → Customer Interaction Center and choose entry Customer Service ## from the dialog box. The premise appears as the entry object in the environment display of the navigation area. The calls that appear for the contract account include Display, Change, Customer account, Change bank data, and Post deferral.

Navigation and Application Area

Contents:  Customer overview: requirements  The navigation area  The application area  HTML connection  Addendum: Customer contact

 SAP AG 1999

Navigation and Application Area: Unit Objectives:

At the conclusion of this unit, you will be able to:  Explain the processes and Customizing of the navigation and application area

 SAP AG 1999

Customer Overview: Requirements

 Flexible definition of 

What is displayed (content)



How it is displayed (layout)

 Simple Customizing 

No screen modifications



No re-coding of ABAP programs

 Integration in the CIC initial screen 

Initial screen must be as static as possible, so that as few screen changes as possible (or none at all) are necessary

 SAP AG 1999

Information Views

Customer center Simple display transaction

Process transaction

Information Views Display of print documents

Data environment (IS-U navigator)

Preprogrammed information views

Configurable information views

act ntr o C Inquiry

?

 SAP AG 1999

Transactions or report programs that provide information are known in IS-U as information views. The following information views are available in IS-U:  Simple display transaction: Common transactions that have usually already been defined, often in the form of BOR methods (Display customer, for example)  Process transactions: Usually a business process involving several entities, such as Move-in/out  Hard-coded information views: Fixed lists such as the Account overview, for example  Freely-configurable information views: Lists whose structure can be changed in Customizing  Data environment: Hierarchical lists that give the user a rapid overview of the data environment of an object (Connection object environment, for example)  Display of print documents: On-screen display of forms such as a bill  You can use the IS-U navigator to define your own data-environment-based information views. 

IS-U Navigator

Overview of the data environment for a selected object

Navigation allows you to branch to the detailed display of a single object Object link display relating to key date or period

Can be called from the front office, IS-U master data, or as an independent transaction

 SAP AG 1999

The main task of the IS-U navigator is to display data environments for objects you specify. This will only work for objects that belong to an object type defined in the BOR.  Data environments can be called from the front office. To integrate a data environment into the front office, you use the BOR method BusinessView.DisplayEnvironment in Customizing for the relevant front office configuration. 

IS-U Navigator: Structure

Environment

Data Environment from 01/01/98 to 12/31/9999 Edit Goto Extras System Help

Business partner

1000000001 Smith Thomas

IS-U contract account 30000100001 private account Utility contract

01/01/98- **.**.** 1000000056 Walldorf 1012 Main St.

Utility installation 2000000074 Electricity Walldorf 1012 Main St., 1st floor Device 04/01/98 - **.**.** 900000000000004711 Device 01/01/98 - **.**.** 900000000000004812 Utility Contract Utility contract

Data environment relates to a key date or period Initial object: business partner Hierarchical structure of the data environment

03/01/98 - **.**.** 3000000998 Boston 1012 Main St.

Utility installation

40000009998 Boston Gas Main St.10 1st Floor

Navigation to detail display possible

 SAP AG 1999



The entry object does not have to be at the top of the hierarchy. The IS-U navigator also determines higher-level data objects.

IS-U Navigator: Customizing IS-U Navigator: Create Configuration Environment Edit Goto Extras System

Help

 Define entry object  Create hierarchy:

Business partner IS-U Contract acct Utility contract Utility installation Device Move-in document

Create parent  Create child  Create sibling 

 Define navigation type:

Structure reader  BOR navigation 

 Maintain structure nodes:

Control  Navigation  Display options 

ExportParameter  SAP AG 1999

To create a navigator configuration in transaction ECNC, you first specify the entry object. The object types that you can use in your hierarchy are predefined by the system. When you choose Create child, Create parent or Create sibling, the system proposes possible object types for you to select and assign to positions within the hierarchy. You can choose between object types whose objects are read either by the structure reader or via the BOR. Wherever possible, however, you should choose objects that are determined using the structure reader. There are two reasons for this:  1. The structure reader is a special report program designed to fetch data more quickly than is possible via the BOR.  2. The structure reader also determines a time relationship between the objects, which means that you can display time references in the navigator environment.  In structure node maintenance, you define  whether the object is to be displayed with time references (only if it is determined using the structure reader)  which nodes should be expanded when the environment is started  how the object is to be formatted at runtime (display options)  

The Navigation and Application Area

 Prerequisite: CIC profile must be integrated with component profile category DEFAULT_WORKSPACES  NAV_AREA component for the navigation area  APPL_AREA_2 component for the application area

Central Customizing maintenance in SAP Utilities  SAP AG 1999

The Navigation Area Up Up to to 10 tab tab pages, pages, for for example •• Documents Documents •• Clipboard Clipboard

Data Data environment

 SAP AG 1999

Context Context menu menu

•• Overviews Overviews •• Transactions Transactions •• Front Front office office processes processes •• Workflows Workflows

Data Environment for the Navigation Area Business partner Contract account Premise Utility contract Utility installation Device Print document

 Component NAV_VIEW can be used in navigation or application area  Select the structure 

Technical view



Business data view



Document view



Technical deregulation view

I account information IM BB plan 1 IM BB plan 2 IM BB plan 3 IM credit history IM customer payments IM dunning items IM paid items Customer contact

 Object categories to be displayed  Additional selection parameters 

Maximum number



Maximum age

Service order Service notification Sales order Customer quotation

 Activity profile

 SAP AG 1999

From the initial screen of the activity, press the "Activity profile" button to maintain the activity profile that is linked with your data environment. You use this feature to determine which transactions can be called at runtime by double-clicking or through the context menu for an object category in the data environment. The maintenance interface of the activity profile is similar to the maintenance interface for creating an action box configuration.  The activity groups are automatically generated in your activity profile, and correspond to the displayed object categories in the assigned data environment. The following objects are available for defining the data flow:  : The object selected at runtime  : The current business partner at runtime 

Data and Documents in the Navigation Area

 Customer data environment  Customer contacts  Service orders and service notifications  Quotations and sales orders  Deregulation processes (cross-company data exchange)  Clipboard

 SAP AG 1999

Application Area - Displaying HTML Pages

 Displaying HTML pages 

Intranet



Internet



HTML pages

 SAP action box transactions can be started from within HTML pages.  Multiple, parallel workspaces  Can pass on information: 

From the CIC to HTML pages (e.g. customer number, material number)



Between different HTML pages



From an HTML page to a CIC / action box transaction (e.g. order number, answers in survey)

 SAP AG 1999

CIC Application Area

Web search

Microsoft Technical

 SAP AG 1999

The application area component can be used to display HTML pages (among other things). When several pages are started, these pages are displayed in different tabstrips. The application area can be used to display HTML pages created by the customer or those in the intranet or Internet. The application area can call HTML pages via an Internet/intranet address, a file/path name, or an SAP Web Repository ID. When you use the application area, several HTML pages can exist in parallel. The different pages are displayed in different tabs in the application area. Each individual tab is called a workspace.  Possible uses for the application area:  Intranet applications  HTML scripting applications ("branch" scripting, buttons for starting action box transactions that are called from scripts, script responses returned to SAP or a data warehouse)  BAPIs and customer-specific input screens  When an HTML page is called in the action box, but no application area has been configured in the framework, the HTML page is displayed in a dialog box. 

The Application Area (L Form)

Tab pages with  Customer overview  Account balance  CIC contact  SAPGUI for HTML: IS-U/CSS and R/3 transactions  Sales and distribution processing  Workflow inbox  Any HTML pages

 SAP AG 1999

Workflow Inbox  Lists all work items pending for execution  Restriction via (workflow) task filter  Received e-mail (SAPconnect)

Component: WF_INBOX  SAP AG 1999

Defining HTML Calls

 Define the HTML configuration  Define external parameters  Define internal parameters

 SAP AG 1999



If you want to use HTML configurations in the application area, configure the required settings in the IMG under path Customer Service -> Customer Interaction Center -> Component Configuration -> Application Area -> Maintain HTML Configuration of the Application Area.

HTML Configuration (1)

HTMLConfig

SERVICE_NOTIF_CREATE

HTML configuration Text

Service notification

External URL

x

WWW object ID

CIC_SERV_NOT_CREATE.HTML;CIC1.JS;CCM_BACK.GIF;CCM_

Configuration

SN_CRE

Stop button Navigation button Refresh button Delete button URL separator 1 URL separator 2

;

 SAP AG 1999

Example of an HTML configuration using a WWW object ID and a transaction call from the action box In this activity, you configure the HTML pages that can be executed in the application area. Under "HTML configuration", enter the name of the configuration, an explanatory text, and the source of the HTML page (URL, path in file system).  A URL with external parameters then has the following format: "=" [[ "=" ]]  A URL can have the following appearance: http://server1/ABoxCalls/CustomerInquiry.html?Customer=0000815&SD_Doc=000000000002305 In this example, is "?" and is "&". separates the root URL from the block of arguments. separates the individual pairs of argument name and argument value. Because different pages can be used to process the arguments of different indicators, these values can be configured. SAP recommends using the separators "?" and "&", because the ITS (Internet Transaction Server) requires these values.  

HTML Configuration (2) - External Parameters

HTMLConfig

SERVICE_NOTIF_CREATE

External parameters Parameter NOTIF_TYPE customer

Text Multiline Element type Required Notification type Export and import  Customer

customer_name Customer name

Import

Proc.seq. 2



Import

 SAP AG 1999



If you want to pass on parameters to the HTML page at startup, you have to maintain them as external parameters.

HTML Configuration (3) - Internal Parameters

HTMLConfig

SERVICE_NOTIF_CREATE

Internal parameters Parameter Customer

Text Customer

Multiline

Element type Export

Equipment

Equipment

Export

d_code d_codegrp

Problem Code grp. - Problem

Export Export

dl_code

Object part

Export

dl_codegroup notif_text

Code grp. - ObjParts Notification text

Export Export



Required

Proc.seq.

 SAP AG 1999

Internal parameters are passed on by the HTML call. Select the names of the internal and external parameters in accordance with the parameters that are expected by the URL of the HTML page.  The "Customer overview" component also calls an HTML configuration. This HTML configuration is called again whenever a business partner is identified or corrected. When you customizing this HTML configuration, make sure that you set the external parameters that will be supplied with data by object category ISUPARTNER to edit sequence 1, and the external parameters that you want to supply with the key (current business partner data) to edit sequence 2. Choose the names of the parameters as they will be expected in the called HTML page. You can also define an alternate HTML configuration that will be displayed whenever no business partner is currently identified. The name of this HTML configuration consists of the name of the HTML configuration for customer info plus an appended _INIT.  

HTML Configuration (4)

HTMLConfig

SAP

HTML configuration Text

SAP Home Page

External URL

http://www.sap.com

WWW object ID Configuration Stop button Navigation button Refresh button Delete button URL separator 1 URL separator 2

 SAP AG 1999

Customer Overview (1) Customer Customer data

This structure is based on HTML data selection PARTNER

Business Business partner partner Premise Contract account Utility contract Utility installation Device Print document Account info level 1 IM account balances IM BB plan 1 IM BB plan 2 IM BB plan 3 IM credit history IM customer payments IM dunning items IM paid items

Customer Customer contact

Customer Customer contacts Service Service notifications notifications Service Service orders orders

Service Service order order Service Service notification notification Sales order Customer quotation

 SAP AG 1999



To customize the HTML customer overview, go to Customizing under SAP Utilities -> Customer Service -> Customer Interaction Center -> Define HTML Customer Overview. You can use this activity to edit the HTML data selection (view) of the customer information function. The HTML data selection indicates which levels (nodes) and which data from the maximum number of available levels will be displayed.

Customer Overview (2) This structure is based on HTML data selection ACCOUNT

Business Business partner partner Contract Contract account account

Customer Customer and and contract account contract account

Premise Utility contract contract Utility installation Device

Print document document

Account Account balance, balance, account account overview, overview, billing billing documents

Account Account info info level level 1 IM IM account account balances IM BB plan 1 IM BB plan 2 IM BB plan 3 IM credit history IM customer payments IM dunning items

Premises Premises and and contracts contracts

IM paid items Customer contact Service order Service notification Sales order

 SAP AG 1999



Customer quotation

You can also integrate the HTML customer overview in the application area in the CIC. To do this, go to Customizing, choose Utilities Industry -> Customer Service -> Customer Interaction Center -> Maintain Navigation and Application Area and then add the CUSTINFO component. You can also maintain a configuration for the CUSTINFO component under Customer Service -> Customer Interaction Center -> Component Configuration -> Application Area -> Maintain HTML Configuration of Application Area.

Customer Overview

Enter Enter payment payment data data

Start Start process, process, e.g. e.g. •• Payment Payment •• Installment Installment plan plan

 SAP AG 1999



The above example illustrates the call of a transaction from the HTML display within the application area.

Addendum: Customer Contacts

At the conclusion of this addendum, you will be able to:  Create a customer contact  Customize customer contacts  Gather information on previous customer contacts

 SAP SAP AG 1999  AG 2001

What is Customer Contact Management?

Component for logging and analyzing contacts between a utility company and its customers

 SAP AG 1999

General Requirements

Two-way customer contacts (Customer Utility company) Automatic customer contact management Efficient and flexible analysis

 SAP AG 1999

Which Data does a Customer Contact Contain? Manual

Automatic

With data entry

With or without data entry

Customer contact  Business

partner, contact person  Date and time of contact  Process description (contact class, contact activity)  Communication medium (type of contact: telephone, letter, etc.)  Reference to external documents (additional documents)  Priority  Assessment of the contact (the customer is dissatisfied, etc.)  Notes on the contact  Reference to data objects or documents  Self-defined data (division, company code)  SAP AG 1999

In addition to the general data stored in the contact, you can store:  References to data objects ( such as a device number) and documents (such as a bill). You can also enhance the data fields stored in the contact.  If non-system documents (MS Word documents, for example) that are relevant to the customer contact exist outside the R/3 system, you can describe these documents in the Additional documents field in the customer contact.  Customer contacts can be assigned a priority to ensure that the most urgent activities are tackled first. In a future version of IS-U, this priority will be passed on to service orders.  In Customizing, you determine which data objects or documents are to be inserted into which customer contacts. 

Creation

Manual

Automatic

Automatic

With data entry

From a front office process or workflow

Within an IS-U transaction

With or without data entry

BCONTACT.CREATE

Customer contact  SAP AG 1999

You create a customer contact manually if for example, you want to log an inquiry made on the telephone.  Customer contacts can be automatically created as an additional result of a transaction, such as changes to a budget billing amount. When a contact is created automatically and any of the data that is required to create this contact is unavailable, a dialog box is displayed to enter this data.  Use the BCONTACT.CREATE method in the BOR for creating customer contacts. 

Example: Customer Contact in the Business Process

Enter Assign Log bank details bank details customer Identification in the in the contact business contract partner account

Customer data is stored in the clipboard

 SAP AG 1999



The logging of a customer contact can be part of a business process. In the above example, an customer contact is created when the bank details are changed.

Structure of Customer Contacts

Contact class Complaint

Service

Information/

4711 Mrs. Schulz

Billing Reversed

Budget billing changed

Device complaint

Other

Quotation created Confirmation given

Billing created

Other

4712 Mr. Maier

Rate info given

Billing

Account Info given

BB info provided

Bill info given

MR info given

Other

Other

Contact activity  SAP AG 1999



Individual customer contacts are described in IS-U by certain contact activities, which are grouped in contact classes.

Contact Classes, Contact Activities

Activity Activity

Activity

Contact class Activity Activity

 Contact classes group the contacts, for example: 

information, complaints, etc.

 Contact activities describe a process within a contact class, for example: 

Rate information provided



Account information provided



Both of these belong to the Information contact class

 SAP AG 1999



You can define contact classes and contact activities in Customizing to correspond to the customer contacts used in your enterprise.

Object Links

 Object links in customer contacts are classified by their role, for example: 

Move-in customer



Faulty device

 You can define roles in Customizing  You can allocate roles to contact activities, so that 

an object link is mandatory



a maximum of one object link exists per contact activity



no object links can be created

 Object references are created as general object links using the generic object services  You can use as many objects as you want in a reference

 SAP AG 1999

Configuration

 Aim:

Automatic creation of customer contacts

by  Pre-assigning certain fields in the customer contact 

Contact class, contact activity



Contact type, contact direction, customer information, additional documents



Business partner and contact person (category, grouping, type, and function category of business partner)

 SAP AG 1999



You can configure the system to automatically create customer contacts by pre-assigning various customer contact fields in Customizing.

Configuration Determination

Call context = Program context + sub-context

 Dependent on calling program  Dependent on user

User group

Configuration User group

CUST CUST DEV ....

Program context

SAPLEC50 ....

SubSub-context Configuration

ABCD ...

001 002 003 .... .... ....

 SAP AG 1999

The fields and screens of customer contacts can be configured to suit individual user groups. Each SAP user must be allocated to a user group. To do this, use parameter CUG (user specifications).  You can also define different configurations for particular programs. To find out in which programs you can do this, see the F4 help. In the example above, a different configuration is used whenever a particular user group uses the move-in function (program SAPLEC50).  If customer contacts are created within front office processes, no entries need to be made in the table. The Configuration parameter is assigned a value by the process data flow. 

A Customer Contact for Every Print Activity

IS-U print workbench Text 1

Text 2

Form class

Application form

All bills

Automatic customer contact for every printout

Specific bills only

Customizing  SAP AG 1999

You can configure the system so that a customer contact is created after every print activity. triggered by the IS-U print workbench.  Customizing tables control how customer contacts are created. If a contact is to be created every time the form class is used for notifications, the control parameters must be defined in the form class. 

Analysis of Customer Contacts

Report RBCONTFO

Method ContactOverview

Account overview

Statistical overview

Contacts for a customer

As additional information

Analysis by:

Can be used in:

 Previous

 Business

partner

 Date  Contact

 Workflows  The

class

CIC

customer contacts can be called from the CIC

 Activity

 SAP AG 1999

The system gives the agent an up-to-date overview of previous customer contacts in the accounts overview display.  The customer contact overview is provided as a standard front office call. 

Customer Contact

Contact Contact is is created created with with "End contact" contact" Component: CONTACT_MAINTENANCE

Activate Activate // deactivate deactivate contact contact creation creation

Contact Contact data

Field Field for for user-defined user-defined text text  SAP AG 1999

Navigation and Application Area: Unit Summary

You are now able to:  Configure the Customizing settings for the

navigation and application area  Integrate HTML pages in the application area  Configure and manage customer contacts

 SAP AG 1999

Navigation and Application Area: Exercises Unit: Navigation and Application Area Topic: Configuring the Navigation and Application Area and Creating and Evaluating Customer Contacts • Configuring the data environment in the navigation area • Calling a data environment • Creating an IS-U Navigator environment • Integrating the IS-U Navigator environment with a CIC configuration • Processing customer contacts The CIC provides a fast, comprehensive overview of the environment of a specific data object. This chapter will explain how these data environment displays are configured and integrated as calls in the CIC configuration. In addition, the CIC provides various options for creating customer contacts. These options are illustrated below. 1

Components in the navigation and application area 1-1 The navigation and application areas each contain several tab strips that can contain special components like the clipboard, contact processing of the current customer contact, the customer overview, and the data environment. Determine the current instantiation under profile category DEFAULT_WORKSPACES in your CIC profile, ZPROF0##. Copy this profile to the name ZNAV0## (0##: group number). Write down 1. The selected clipboard component for the navigation area _________________________ and 2. The component in the environment of the navigation area and its profile. _________________________ In addition, copy the latter profile to name ZUMF0## (0##: group number) and change the data environment display of the navigation area such that the business partner is now the entry object in the data structure. Define your profile, ZUMF0##, in the appropriate tab page of your navigation area in profile ZNAV0##. Then change the instantiation of profile category DEFAULT_WORKSPACES to ZNAV0## in CIC profile ZPROF0##. 1-2 Displaying the IS-U data environment

The IS-U navigator provides an overview of the environment of a data object (for example, a customer, a connection object, etc.) in IS-U. Display the environment of the connection object on Oxlade Drive 0## (0##: group number) for the business partner with the customer number PJ0203A0##. 1-2-1 How do you proceed? ______________________________________________________ 1-2-2 Which devices are installed in the connection object? ______________________________________________________ 1-2-3 Navigate forward and display the bank details that are entered in the business partner. What did you find? Bank details________________________________________ 1-2-4 How can you determine whether these bank details are used for the direct debit of open receivables in the customer’s account in FI-CA? ______________________________________________________ 1-3 Creating a navigator configuration You can define data environments for an object (for a business partner, for example) yourself. You define the information you want to see on your list. In this exercise, create a navigator configuration that looks like this: Z_GR0## I____ISUPARTNER Business partner I____ISUACCOUNT IS-U: Contract account I____ISUCONTRCT Utility contract I____BUDBILPLAN Budget billing plan I____INSTLN Utility installation 1-3-1 Create a navigator configuration Create a navigator configuration with the key Z_GR0## (0##: group number) and the entry object Contract account. 1-3-2 Create the hierarchy structure Create the hierarchy structure such that it looks like the diagram above. 1-3-3 Object type attributes Take the validity period into account for the utility installation. Save the navigator configuration. 1-4 Integrate the navigator configuration as a call from the data environment of the navigation area. To be able to display the data environment for the contract account from within the CIC, you have to integrate it as a call in the action profile of the data environment in the navigation area. In the previous exercises, you created your own data environment, ZUMF0## (##:group number). Now add this call to the data environment. 1-4-1 Create the call Integrate your navigator configuration as a new transaction under the contract account. Select VKUM as the call ID code and Environment contract account as the description. You must also enter a short text that you would like to see

used for this call in the CIC. Select an icon of your choice for the call. The method for this call is DISPLAYENVIRONMENT of object type ISUBUSVIEW. The processing type is now 2 Display/Change. 1-4-2 Define the data flow Define the export data flow for the following fields: Initial object, From-date (today’s date), To-date (today’s date) and Navigator configuration. Use your configuration Z_GR0## (0##: group number) as the navigator configuration. Now define the import data flow. Once the environment has been displayed, the Contract account object should be placed on the clipboard. Insert the relevant objects as target elements in the import data flow and assign them the appropriate values from the call container using F4 help. Save the action profile. 1-4-3 Display the data environment for the contract account From within the CIC, display the data environment for the contract account of business partner PJ0203A0##. 1-5 Integrating an HTML page in the customer overview You want to display SAP’s Web site, http://www.sap.com ,in the customer overview of the application area. To do this, create an HTML configuration called ZCUSTINFO0## (##: group number) in the application area and integrate it as a component profile in application area ZNAV0##. Test your changes. 2

Customer contact Business partner

PJ0203A0## (0##: group number) Rose Taylor 0## Oxlade Drive Boston 02100

Contract account number

PJ0203A0## (0##: group number)

Electricity contract/installation PJ0203A0## (0##: group number) Water contract/installation

PJ0203B0## (0##: group number)

Electricity meter

PJ0203A0## (0##: group number) D Double-rate meter

Water meter

PJ0203B0## (0##: group number) Single-rate meter

Move-in document

PJ0203A0## (0##: group number)

2-1 True or false? 2-1-1 You can only create customer contacts manually. ______________________________________________________

2-1-2 You can define the customer contacts required by your enterprise in Customizing. ______________________________________________________ 2-1-3 Customer contact management provides the agent with a quick overview of a business partner's previous customer. ______________________________________________________ 2-1-4 The CIC contact contains all the objects related to the business partner that have been saved during the course of processing that business processor – even those that were placed in the clipboard. ______________________________________________________ 2-2 Creating a customer contact manually A customer calls your utility company and asks for information about her outgoing payment method. The agent displays the customer’s contract account and answers the question. The agent then logs the customer contact with a link to the contract account. This last step is the one you will carry out in this exercise. First, identify the business partner with customer number PJ0203A0### and create a customer contact. You can find the Create contact process in the action box under the Customer call group. To create a customer contact, select the activity Payment information. Select a contact type, and specify the contact as received. You also need to link the contact to the contract account. Attach the customer’s contract account in the form of a BOR object to the contact and create a note with the following text: Customer wishes to pay by direct debit. Save the contact. 2-3 Analyzing customer contacts When a customer calls, an agent will often find it helpful to have immediate access to records of previous contacts with the customer. The agent will usually call this information from the CIC. You can access an over view of the customer contacts at various points in the CIC. , which you will practice in this section. Display all previous customer contacts for business partner PJ0203A0##. 2-3-1 To do this, use the Documents overview in the navigation area. Select the Initial Reporting of a Move-In contact from the list by double-clicking on it. You then branch to the corresponding contact. The move-in document is stored as the object in this contact. Display the move-in document. 2-3-2 You will find the Customer overview in the Information call group. You can also display previous contacts here. Which customer contacts have already occurred? 2-4 Creating a customer contact within a business process Many business processes already incorporate the creation of a customer contact. You will learn how to define a customer contact as a step in a CIC process in the next exercise. In this exercise, you will create a customer contact as part of a business process. The advantage of process chains like this is that values can be pre-assigned to certain fields in Customizing.

Process description: Your business partner, Ms. Brown of 0## Oxlade Drive (0##: group number), appears in person at your Customer Center. She wants to change her budget billing amount because she is expecting lower consumption in the future. The process Change budget billing plan consists of the following steps: Change budget billing plan Create customer contact A customer contact is created in the last step. The customer contact can contain predefined data such as: the contact class, contact activity and business partner. 2-4-1 Start the Change budget billing plan process. Change the budget billing amount of the electricity contract to UNI 100 and the water contract to UNI 120. To do this, use the Change BB amount button in the budget billing plan. 2-4-2 Once you have saved, the screen for creating customer contacts automatically appears. Check that the budget billing plan has already been created as the object link. Change the contact type and save the customer contact. 2-5 CIC contact The CIC contact is a contact that automatically logs all the activities performed in the CIC when a business partner calls. In addition to the business partner, all the objects that are located in the clipboard when the contact is ended are also referenced. Call up the CIC and call up your business partner PJ0203A0## again. Call the customer overview. Copy the electricity contract to the clipboard. Return to the CIC and press End contact to end the contact. Call the business partner again and navigate to the CIC contact that was just generated. Which object was referenced, and which contact class and contact activity were automatically selected? Where is the proposal for contact class and contact activity maintained for the CIC contact in Customizing?

Navigation and Application Area: Solutions Unit: Navigation and Application Area Topic: Configuring the Navigation and Application Area and Creating and Evaluating Customer Contacts 1

Navigation and Application Area 1-1 Choose Customer Service → Customer Interaction Center (CIC) → CIC Profiles → Maintain CIC Profiles. The instantiation under profile category DEFAULT_WORKSPACES is ZNAV000. In Customizing, choose SAP Utilities → Customer Service → Customer Interaction Center → Maintain Standard Settings for Navigation and Application Area, select profile ZNAV000 and choose Copy as. Enter profile name ZNAV0## and profile text “Profile group 0##”. Press Enter. The message appears that the entry to be copied has dependent entries. This refers to the allocated components, which you also want to copy. Choose the Copy all button in the message. Choose Copy all in the dialog box. A confirmation prompt appears informing you that 6 entries were copied. Choose Confirm and then save your entries. Select the new profile and choose Display areas. Double-click on the third tab page, navigation area clipboard, and you will see the selected component BD_DISPLAY, which controls the clipboard for temporarily saving objects. You can also double-click on the first tab page, environment of the navigation area, to see component NAV_VIEW with profile ZUMF000. Now go to Customizing and choose: SAP Utilities → Customer Service → Customer Interaction Center → Define Data Environment for Navigation Area. and copy profile ZUMF000 to your new profile ZUMF0##. Select this profile and start change mode. You see the business partner as the top node in the structure. Set the Display active flag in subscreen Business Partner Attributes and save your profile. Now go to the IMG activity Maintain Standard Settings for Navigation and Application Area and save your environment configuration, ZUMF0##, under profile ZNAV0## (navigation area, first tab page). In the last step, save the instantiation of your navigation and application area in the profile attributes of your CIC profile, ZPROF0##. To do this, choose Customer Service → Customer Interaction Center (CIC) → CIC Profiles → Maintain CIC Profiles. The responsible profile category, DEFAULT_WORKSPACES, is given the instantiation ZNAV0##. 1-2 Displaying the IS-U data environment

1-2-1 How do you proceed? Enter customer number, PJ0203A0##, in field Business partner in the search criteria and press Enter twice in order to fill the data environment in the navigation area. Position the cursor on the premise and click the right mouse button to select the Connection object environment. A list containing the data environment for the connection object on Oxlade Drive 0## (0##: group number) is displayed. Press the corresponding button to expand the environment. 1-2-2 Which devices are installed in the connection object? You see that the connection object contains an object location in which the following devices have been installed: Device: Device:

PJ0203A0## PJ0203B0##

and

1-2-3 Navigate forward and display the bank details that are entered in the business partner. What did you find? To branch to the contract partner display, double-click on the Business partner field or on the ID located beside it. Scroll forward to the third tab page, Payment transactions. All bank details for the business partner are entered here. In this case they are: Account: 1230## at Mellon Bank, Massachusetts, bank number: 70070010. 1-2-4 How can you determine whether these bank details are used for the direct debit of open receivables in the customer’s account in FI-CA? Display the contract account to see whether these bank details are used (either by navigating forwards from the data environment list, or from the business partner via the Contract accounts button). The first set of bank details is stored in tab page Payments/Taxes as an incoming payment method and is therefore used for the direct debit of open receivables. 1-3 Creating a navigator configuration 1-3-1 Create a navigator configuration In Customizing, choose the following path SAP Utilities Customer Service → Customer Information → Configure Data Environment Display and enter key Z_GR0## (0##: group number). Choose Create. Select ISUACCOUNT as the initial object and enter Navigator Configuration Group 0## (0##: group number) as the description. (0##: group number). Press Enter to confirm. 1-3-2 Create the hierarchy structure You have selected the contract account as the entry object. This is now displayed against a yellow background. 1. Business partner: Position the cursor on the initial object. Choose Create father to insert the business partner into your list. To do this, choose the element from the structure reader navigation.

2. Utility contract: Position the cursor on the initial object. Choose Create child to insert the utility contract into your list. To do this, choose the element from the BOR navigation. 3. Budget billing plan: Position the cursor on the utility contract. Choose Create child to insert the budget billing plan into your list. To do this, choose the element from the BOR navigation. 4. Utility installation: Position the cursor on the budget billing plan. Choose Create brother to insert the utility installation into your list. To do this, choose the element from the BOR navigation. 1-3-3 Object type attributes Position the cursor on the utility installation and select menu path Edit → Choose. A dialog box appears. Mark the With validity checkbox. Confirm your entries and save. 1-4 Integrating the navigator configuration as a call from the data environment of the navigation area 1-4-1 In Customizing, select the activity SAP Utilities → Customer Service → Customer Interaction Center → Define Data Environments for Navigation Area. Use Maintain Action Profile to change action profile ZUMF0## (0##: group number). Expand transaction group 0003 and position the cursor on the transaction under which you want the new call to appear. Choose Create transaction. Enter data in the fields of the dialog box as follows: Call ID code Call ID Call ID code menu Icon name Processing type

VKUM Environment contract account Account envir. Use F4 help to choose an icon 2

In the call definition, choose type Method and enter ISUBUSVIEW in the Object type field. Enter DISPLAYENVIRONMENT in the Method field. Choose Standard (generated) as the parameter dialog and choose Run in application area if possible in the runtime specifications.

1-4-2 Define the data flow In the export data flow, assign the contract account the following values using the F4 help: Entry object: From-date To-date Navigator configuration

&NODEOBJECT.CONTRACTACCOUNT& DATE in format YYYYMMDD DATE in format YYYYMMDD Z_GR0##

In the import data flow, choose New target element to create element CAccount with data type reference Object type ISUACCOUNT. Use the F4 Help to assign the target elements the following value: Contract account

&ROOTOBJECT&

Go Back to exit the definition of the data flow and save the action profile. 1-4-3 Display the data environment for the contract account Select business partner PJ0203A0## using the search area. Select the contract account in the data environment of the navigation area and click the right mouse button to select your new call. Expand the entire tree. You see the budget billing plan and the utility installation under the two contracts for the contract account. When you return to the CIC, the contract account is saved in the clipboard of the navigation area. 1-5 Including an HTML page in the customer overview Choose Customer Service → Customer Interaction Center (CIC) → Component Configuration → Application Area → Maintain HTML Configuration of Application Area. Use New entries to create a new entry with the name ZCUSTINFO0## (## = group number). Define the external URL http://www.sap.com and a text label. Activate the stop, navigation, and refresh keys and save your entry. Now integrate HTML configuration ZCUSTINFO0## as a profile of component CUSTINFO in application area ZNAV0##. Choose the following IMG activity: SAP Utilities → Customer Service → Customer Interaction Center → Maintain Navigation and Application Area. Define your HTML configuration, ZCUSTINFO0##, with the title Customer Overview in the display area of the first tab page. Call the CIC again and select your profile under position Customer Service ##. Enter business partner PJ0203A0## in the search criteria and press Enter twice to confirm. SAP’s home page should now appear in the application area.

2

Customer contact Business partner

PJ0203A0## (0##: group number) Rose Taylor 0## Oxlade Drive Boston MA, 02100

Contract account number

PJ0203A0## (0##: group number)

Electricity contract/installation

PJ0203A0## (0##: group number)

Water contract/installation

PJ0203B0## (0##: group number)

Electricity meter

PJ0203A0## (0##: group number) Double-rate meter

Water meter

PJ0203B0## (0##: group number) Single-rate meter

Move-in document

PJ0203A0## (0##: group number)

2-1 True or false? 2-1-1 _________________________________________________________ False. Customer contacts are also created automatically. 2-1-2 True 2-1-3 True 2-1-4- True 2-2 Enter business partner number PJ0203A0## in the search criteria. You can find the Create contact process in the action box under the Customer call group. Start the process. To create the customer contact, select the Payment information activity from the Information contact class using the F4 help. In the Contact type field, use the F4 help to select a contact type. In the Direction field, specify the contact as received. Choose the Business objects tab page. The subscreen for creating object links appears. To create the reference to the contract account, press the Add object button. Once you have selected BOR object Contract account in the dialog box that appears, navigate to the data finder search screen to identify the contract account. Enter business partner PJ0203A0## and press Enter. As the system only finds one contract account, the system automatically inserts this in the table as the object link. At the bottom of the screen there is a notepad in which you can enter text. Save the contact. 2-3

2-3-1 To do this, use the Documents overview in the navigation area and press the button to refresh the display. Expand the previously saved contacts and select the Initial Reporting of a Move-In contact from the list by double-clicking on it. You then branch to the corresponding contact. The move-in document is stored as the object in this contact. Display the move-in document. 2-3-2 The following customer contacts have been created to date: - A new customer moves in Payment information angelegt worden. 2-4 2-4-1 Identify the customer and display the data environment in the navigation area. You will find the Change Budget Billing Plan process under the Customer call group. After you have started the Change budget billing plan process, a dialog box appears with sub-budget-billing plans for the electricity and water divisions. Select a line and branch to the change mode of the sub-budget-billing plan. Press the Change BBamt button. A dialog box appears in which you can change the sub-budget-billing amount for both the electricity and water contracts. Change the budget billing amount for electricity to UNI 100 and for water to UNI 120. Press Enter. You return to the initial screen and can see that the budget billing amounts have been changed. Save the entries. You will be asked if you wish to send the customer a letter confirming the change to the budget billing plan. Choose No. 2-4-2 The customer contact appears automatically. Choose the Business objects tab page to navigate to an overview of existing object links. There is already an entry for the budget billing plan here. Enter a different contact type (use the F4 help) in the Contact type field and save the customer contact. 2-5 Choose business partner PJ0203A0## again and press Enter to store it in the data environment of the navigation area. Call the Customer overview from call group Information in the action box. Position the cursor on the company code in the contract subscreen and press the Object to clipboard button. Press F3 to return to the CIC and make sure that the electricity contract has been copied to the navigation area clipboard. Press the End contact button to end this CIC transaction and then call the same business partner again. In the Documents tab page of the navigation area, double-click to display the last saved CIC contact Activity in Customer Interaction Center The referenced object is the electricity contract with number PJ0203A0##. The contact class is 22 CIC Contact and the contact type is 1 Activity in Customer Interaction Center. You can define these default settings in the IMG with path Financial Accounting → Contract Accounts Receivable and Payable → Business Transactions → Customer Contacts → Define Configuration under configuration CIC_DEF.

Front Office Processes

Contents:  Using front office processes  Customizing front office processes  Special methods for modeling complex front office processes

 SAP AG 1999

Front Office Processes: Unit Objectives

At the conclusion of this unit, you will be able to:  Create front office processes  Use special support methods in front office processes

 SAP SAP AG 1999  AG 2001

Calls (technical) Calls (technical)

 Methods (from the BOR)  

Change customer Data environment of connection object

CIC

ile f o pr

 Front office processes 

Change bank details SAP Utilities

 Workflows  

Disconnection/reconnection Service connection

 Test runs (CATT procedures)  BDC sessions  SAP AG 1999

 



 

Behind every front office call you always find one of the four process categories listed above. BOR methods: Methods from the Business Object Repository have a significant part to play in integrating business processes into the front office. Methods are also the smallest units with which you can work when configuring front office processes and workflows. Computer Aided Test Tool (CATT): CATT procedures are not based on BOR methods. A CATT procedure is a record of a specific sequence of R/3 transactions that can be executed and transported in batch input. First, the transactions are executed in their most typical sequence. This sequence is recorded to form a business process. Transactions are always in a fixed linear sequence. CATT procedures should therefore be used as a last resort and only if no BOR methods exist for the transactions and applications you need to integrate in your business process. For a detailed description of how to create CATT procedures, please see the documentation under R/3 library -> Cross-application components -> Computer Aided Test Tool. Workflows: The definition of workflows is described in detail under R/3 Library -> Basis -> Business Management -> SAP Business Workflow. Front office processes: You can model front office processes for use in the IS-U system only. This unit describes the modeling of front office processes in detail.

Business Object Repository (BOR) BOR Object Type BOR objects Customer 10004711 Customer 10004712 Customer 10004713 ...

Contract

Cust.

Methods Change Create Display ...

Key fields Customer number ....

Attributes Name Customer group Address ...

Events Customer created Name changed ...

 SAP AG 1999

The Business Object Repository is the strategic, object-oriented interface with R/3 business functionality.  The BOR is a fundamental prerequisite for configuring and using the front office.  A BOR object type describes the attributes and applications that objects of the same type (customers or contracts, for example) have in common. A BOR object is a specific instance of a BOR object type, as in, for example, customer Smith with customer number 10004711.  A BOR method can be used as a front office call. You can, for example, use the method CREATE with the object type ISUPARTNER to integrate a front office call for creating a customer into the front office. This is a simple example of a front office call. For more complex business processes, you may need several steps - that is, a sequence of several BOR methods. 

Call Definition: Method

 Uses the Business Object Repository and a method  To determine whether a BOR is available: 

Press F4 and search for Description or



SWO1 and search the Business Object Repository

 

Choose business objects / organizational categories

Display the object type and determine the suitable method



Parameters: Are exported for the transaction

 SAP AG 1999

  

Accessing the directory of business objects: Tools --> Business Workflow --> Development --> Business Object Builder The following information is helpful in determining suitable BORs:  The method should have a dialog, otherwise it will not be displayed.  If the parameters do not contain the information that you want to transfer from the CIC (such as the customer number), then you don't have the right BOR.  BAPIs (characterized by a green dot) are usually not suitable for CIC transactions.

Call Definition: Workflow and Test Procedure

 Workflow 

Define the task type and task ID

 Test procedure (CATT) 

Requirements regarding window size and command field confirmation



Not very effective in the call center environment

 SAP AG 1999

What Is a Front Office Process?

 A sequence of R/3 functions that represent a business process  A process carried out by a front office agent  A process that is dealt with immediately  A process that can trigger background processes (workflows)

 SAP AG 1999

A front office process enables you to model R/3 functions in a pre-defined sequence. The purpose of a front office process is to model a business process in the system that can be carried out immediately in the front office by an agent in direct contact with a customer.  A front office process can be cancelled at any time.  A front office process can contain a workflow as one of its process steps. In such a case, the workflow is triggered by the front office process, which then proceeds immediately with the next process steps (so it is not necessary to wait for the workflow to be completed).  

Front Office Process: Example

Step 1 BOR method

Identifica ntification

Enter bankdetails inthe busin ess usine part ner rtn

Step 2 BOR method

Step 3 BOR method

Assign bankdetails in the contract account

Log customer contact

Custom stomer datais stored in th e the clipboard

Change Bank Data  SAP AG 1999

This slide illustrates a simple example of a front office process. The process Change bank data comprises three process steps. Behind each process step is a method from the Business Object Repository.  In the first process step, the business partner is changed using the method ISUPARTNER EDIT.  In the second process step, the contract account is changed using the method ISUACCOUNT EDIT.  In the third process step, a customer contact is created using the method BCONTACT CREATE. 

Front Office Process (Technical)

Step 1

Step 2

Step 3

Front office process

Workflow

BOR method

 Sequence of process steps from     

BOR methods Front office processes Workflows CATT procedures Editor steps

 Used for modeling customer-specific business processes  SAP AG 1999

Customizing for front office processes is a powerful tool which enables you to integrate complex IS-U business processes into the CIC/front office.  A front office process consists of one or more process steps, which can, in turn, consist of other processes.  An editor step is a screen that is generated by the system with fields that are a direct reflection of its defined parameters. An editor process enables you to enter data required by subsequent process steps. You use the data flow to define how the entries made by an agent are processed by the front office process. For the fields in an editor step to be processed further, the subsequent steps have to be able to import the parameters. An example of such a process is Workflow with users/notes, which is supplied as part of the standard IS-U system. 

Differences Between Front Office Processes and Workflows

 Front office processes: Chain of processing steps that 

Are usually to be processed immediately



Are carried out by front office agents



Are not logged

 Workflow: Chain of processing steps that 

Are not processed immediately (back office)



Are carried out by different agents and/or departments



Are logged

 SAP AG 1999

The purpose of a front office process is to model a business process in the system that can be carried out immediately in the front office by an agent in direct contact with a customer. A workflow, on the other hand, is used to send tasks to specific agents for processing via the integrated inbox.  Unlike a workflow, a front office process is not a persistent. That means the sequence of a front office process is not written to the database. The progress of a workflow, on the other hand, is stored in the database in the form of a step log.  A front office process can be cancelled at any time. A workflow process must be completed according to its pre-defined end point.  A front office process can contain a workflow as one of its process steps. This means that workflows can be triggered by front office processes. After a workflow has been called, the system resumes the front office process, meaning that the subsequent steps can be processed immediately. 

Data Flow of a Front Office Process

CIC data CIC CIC data data flow flow Process container Process Process data data flow flow 1

2

3

Process step 1 container

Process step 2 container

Process step 3 container

Import data flow Export data flow

 SAP AG 1999

Just as in SAP Business Workflows, every front office process has its own data container which contains all the data necessary to control the process.  Each process step also has its own container. This is supplied during runtime with data from the process container by the process manager .  The necessary parameters for the process container are pre-defined by the process step interface. These parameters are assigned suitable values via the data flow defined for each process step. Taking the data flow for the call as a whole into account, an import and an export data flow is defined for each individual step.  The values available for use in the import data flow are constants, system fields and data from the process container. 

Data Export and Data Import

Bus. object display Service notification

200000334

Customer

Becker Berlin

Export from business object display to transaction

 SAP AG 1999

Import from transaction to business object display

Action Box Call: Data Flow

 Export data from the business object display to the transaction 

Customer number, contact person, order number

 Export constants to the transaction 

System date, time, user ID, order types, priorities

 Import data from the transaction back to the business object display 

Document numbers, material numbers

 Main object is already known from the call

 SAP AG 1999



The Maintain Data Flow screen is displayed as soon as a new call is created. If the call already exists and you want to update the data flow, position the cursor on the call and click on Data flow.

Data Flow: Clipboard --> Transaction Example: Start an action box call from the clipboard Transaction SAPphone.  The next integration level provides features such as Predictive Dialing and IVR (Intelligent Voice Response) using data from the R/3 system. You can select a large number of customer to call as part of a campaign. R/3 manages the data for the scheduled calls and coordinates communication with the call center system. 

Internet Integration

TAPI client

Presentation

. . . R/3 architecture with internet enhancments

Web server

Internet Customer dienstmitarb.

Fertig.-Sales Orders Create

Customer Order Accept

BOM auflösen

Customer Order

Part

Material reserv.

Prod. Order

Werkspersonal

Fertig.-Produkte Sales Orders herstell. freig.

Fertigung Material Scheduled Dates Task

delivery Confirm

Application

SAP internet transaction server R/3 Internet Application Components BAPIs

R/3 IS-U/CCS

Possible IS-U/CCS implementations: - Internet scenarios for receiving customer information - Intranet scenarios for field service/ partner access to CCS transactions

Database  SAP AG 1999



The use of BAPIs (Business Application Programming Interfaces) means that IS-U functions can be accessed via the internet. BAPIs are specially-developed methods that do not issue dialog messages, making them ideally suited as a communications interface between the R/3 system and the web server.

R/3 Client/Server Architecture with ITS

Presentation SAPGUI

...

...

...

WebBrowser WebServer Internet Transaction Server

Application

Database  SAP AG 1999

The Internet Transaction Server extends the three-level client/server structure of the R/3 system into the Internet.  Using an R/3 System via a SAPGUI and an Internet Transaction Server at the same time does not cause any problems. 

Five-Level Client/Server Architecture Request

Web Browser

HTTP Server

Internet Transaction Server

R/3 Application Server

R/3 Database Server

Response

Service Files

HTML Business Templates

 SAP AG 1999

The Internet Transaction Server connects the three-level client/server architecture of the R/3 to the two-level HTTP client/server architecture.  From the view of the R/3 System, the ITS and the HTTP server create an intermediate level between the application and presentation levels.  From the view of the Internet user, the ITS takes care of interactive HTML pages (which are generated for runtime). 

Internet Transaction Server

 Connection between WWW and R/3 R/3

WS

SE80

Internet Transaction Server



Converts R/3 data into HTML pages

 Requirements: 

Intel-based server



Windows NT Server 4.0

 Availability: 

With R/3 installation (Server Components CD)

SAP@Web Studio  SAP AG 1999



The SAP@Web Studio essentially has two main tasks: To publish the delivered SAP services and templates from the R3 installation on the ITS To create user-defined services and templates.

IS-U/CCS Internet Services Utility company

Customer self-services Customer overview

Provider selection Move-Out/ Move-In

Logon at provider's website MR result entry

Customer overview

Maintain personal data BB plan management

Invoicing SAP GUI for HTML

Register internet user

Bill display Payment Internet Application Components

 SAP AG 1999

There are two kinds of internet scenario:  Processes for the customer  Processes for employees and partners of the utility company  For the customer-related scenarios, SAP supplies the Internet Application Components (IACs). IACs are developed in an R/3 environment and placed on the internet transaction server using HTML templates. They can then be inserted into the World Wide Web. Customers can then call up information using a web browser. The online integration of the IACs with IS-U ensures that all IS-U validations and consistency checks apply.  The employee and partner-related scenarios are applications with which you can access the complete range of IS-U functions via a web browser. In this way, for example, a sales employee can simulate a bill for a prospect using a PC with internet access. This is made possible by the SAP GUI for HTML, which translates every R/3 screen into HTML code.  IS-U is fully integrated with the internet. 

Internet Services for the Utility Company

Budget Budget billing billing plan plan management management

 SAP AG 1999

Move-in/ Move-in/ move-out move-out

Device Device management management

You can see from the above IS-U sample screens that an utility company employee sees exactly the same screen in the web browser as from a workplace with the SAP GUI for Microsoft Windows.  IS-U uses native HTML tags, which means that you can use all the IS-U functions via a web browser without having to install additional software.  No additional software is needed  You do not have to download any plug-ins, either 

Example: 'Display Bill' Scenario

Customer

Log Log on on to to the the WWW WWW

Utility company

WWW

R/3 R/3 IS-U/CCS IS-U/CCS

Homepage Homepage of of the the utility utility company company

Choose Choose your your service service Choose Choose your your billing billing data data Cust. Cust. no./password/(meter no./password/(meter no.) no.)

Selected Selected bill bill is is displayed displayed

Authorization Authorization check check Find Find selected selected bill bill

B A P I

ISIS-U /CCS

 SAP AG 1999

A typical example of a utility customer accessing the homepage of a utility company is to display his/her last bill.  First, the customer logs on to the Internet, goes to the homepage of the utility company, and chooses one of the services offered there, such displaying the last bill. The web server displays a screen in where the customer must enter a customer number and password. A BAPI programmed in IS-U exchanges data between the web server and IS-U, checking the data entered by the customer, fetching the billing data from IS-U, and finally making this data available to the web server so that the customer can view it. The formatting and layout of the billing data on the internet page is controlled by the web server. 

Customer Internet Self- Services

Account Account and and bill bill display display

Maintenance Maintenance of of personal personal data data

 SAP AG 1999

Customer Customer meter meter reading reading

WAP Self-Services WAP (Wireless Application Protocol) is the worldwide standard for providing internet communications on digital mobile phones

Logon Logon and and authorization authorization check check

WAP WAP services services  SAP AG 1999

Meter Meter reading reading dataentered dataentered and and validated validated

Connection to External Systems: Unit Objectives

 The CIC enables you to integrate and then call archiving systems  JAVA, JAVAscript and ActiveX components can be integrated into the HTML customer overview  You can use R/3 functions in the web browser via the SAP GUI for HTML  SAP offers pre-prepared internet applications for customer self-services  Using WML templates, customer self-services can also be accessed by WAP cell phones

 SAP AG 1999

Disconnection and Reconnection

This unit:  Explains the business processes disconnect and reconnect  Introduces the disconnection document concept  Describes the workflow provided for this process  Shows you the Customizing options

 SAP AG 1999

Disconnection and Reconnection: Unit Objectives

At the conclusion of this unit, you will be able to:  Use the disconnection document  Display the service orders  Carry out disconnection and reconnection using the workflow  Specify the settings in Customizing

 SAP SAP AG 1999  AG 2001

Disconnection and Reconnection: Business Scenario

A customer who has arranged to settle his utilities bills in cash is in arrears with his payments, despite repeated reminders. IDES Utilities Inc. therefore has no choice but to disconnect the electricity supply until the outstanding amounts have been paid. The disconnected devices are to be reconnected as soon as the payments have been made. To achieve this scenario, the project team uses the IS-U functionality for disconnecting/reconnecting:

 Disconnection documents, disconnection orders, reconnection orders  Links to PM order management  Workflow to automate the entire process flow from disconnection to reconnection

 SAP AG 1999

Process of Disconnection and Reconnection

Create disconnection document

Create disconnection order

Agent/ system

Perform disconnection

Enter disconnection data Confirm disconnection order

Technician Technician Agent

Agent/ system

Enter reconnection Confirm reconnection data order Perform RECONN.

Agent Technician

Trigger RECONN. Create reconnection order

Agent/ system

Agent/ Agent/ system system

 SAP AG 1999

The graphic shows a possible procedure for the business process disconnect and reconnect: 

  



  

Disconnection is triggered either manually by an agent (if the customer has requested the disconnection, for example) or automatically by the system (if, for example, the disconnection dunning level has been reached in the dunning run). The system then generates a disconnection document. Disconnection documents can also be created manually by agents. The system generates a disconnection order, complete with all the documents the technician needs to disconnect the installation. The technician carries out the disconnection using the documents. The disconnection is performed in the system: the disconnection order is confirmed and disconnection data is entered. The confirmation status indicates whether the visit was successful or not (for example, disconnection performed, entry not possible). Reconnection is triggered either manually by an agent (if the customer requested the original disconnection, for example) or automatically by the system (if, for example, payment has been received since the disconnection dunning level was reached in the dunning run). The system generates a reconnection order, complete with all the documents the technician needs to reconnect the installation. The technician carries out the reconnection. The reconnection is performed in the system: the reconnection order is confirmed and reconnection data is entered. The confirmation status indicates whether the visit was successful or not (for example, reconnection performed, entry not possible).

Disconnection Triggers

FI-CA dunning level reached Create disconnection document

Customer request System Technical reasons

Vacant status (move-out without move-in)  SAP AG 1999

The disconnection is initiated when the disconnection dunning level is reached in Contracts Accounts Receivable and Payable (FI-CA) for the relevant contract account. When the dunning notice is printed, a disconnection document is generated automatically. A disconnection order can be generated from this disconnection document. This initiates the disconnection.  Disconnection is also initiated if the customer requests it, if it is necessary for technical reasons, or if the customer moves out of the premise. 

Disconnection Document: Log Function

Create disconnection document

Create disconnection order

Agent/ system Agent/ system

Perform disconnection

Technician

Disconnection document

Enter reconnection Confirm reconnection data order Perform RECONN.

Agent Technician

Enter disconnection data Confirm disconnection order

Agent Trigger RECONN.

Create reconnection order

Agent/ system

Agent/ system

 SAP AG 1999



The processing unit for the agent is the disconnection document. A disconnection document is created for every business process or instance of disconnection. It is used for logging the individual steps of the process. It enables you to branch directly to the entities included in the process.

Disconnection Document and Reference Object FI-CA dunning level reached

Vacant status (no move-in after move-out)

Customer request

Contract account

Contract

Premise

Connection object Premise

Technical reasons

Contract account Contract

Installation Device  SAP AG 1999





 



The reference object is used to determine potential disconnection objects: all the devices or flat-rate installations (disconnection objects) that are subordinate to the reference object in the IS-U data hierarchy are proposed for disconnection in the disconnection document. Exception: installations that have an explicitly guaranteed supply cannot be disconnected. Disconnection documents generated when the disconnection dunning level is reached contain all the contract account items that had reached the disconnection dunning level when the last dunning notice was printed. The devices or flat-rate installations that can be disconnected are therefore determined on the basis of the contract account. You can display default values for contracts. However, the contract account remains the reference object (the contract alone is not a reference object). The selection process is described in more detail later. Disconnection documents created when a customer moves out and no new customer is to move in apply to all the devices in a premise. It is also possible to carry out disconnection for specific objects (for technical reasons or if the customer requests it). The levels at which you can disconnect are: connection object, premise, contract account, contract, installation, or device. The object on which the disconnection order is based is displayed in the disconnection document as the reference object.

Disconnection Document: Components

Disconnection doc.

Disconnection Document: Change Edit Goto Extras System Help

Reference object

Data hierarchy Change/display reference object

Disconnection activities Release Disconnection order Entry of disconnection Reconnection order Entry of reconnection data Completion

Detailed display

Disconnection objects Device 1 Device 2 Flat-rate installation

Detailed display of device/ installation

 SAP AG 1999

The reference object is recorded in the disconnection document. Here, you can display the reference object, branch to the data hierarchy of the reference object, or switch to a different reference object.  All disconnection and reconnection orders created (including their parallel PM orders) and all entries of disconnection and reconnection data are recorded as disconnection activities in the disconnection document. You can also branch to the service orders and to the disconnection data.  All the devices in the disconnection document are recorded as disconnection objects in the document. You can branch from any device to the material serial number display. Disconnection occurs per device. Disconnection of flat-rate installations is also possible. 

Confirm Disconnection Order

Relevance to billing Confirmation status

New order

Confirmation Enter disconnection method

Calculate charges Enter billing

 SAP AG 1999

  

  

Default confirmation statuses are defined in Customizing and can be overwritten. For example, you can substitute the status Devices disconnected with No one home. You can also create a new order. This makes sense if the customer wasn't at home and you therefore need to create a new order. An indicator for billing relevance allows you to decide whether the basic price should still apply at the time of disconnection. To use this function, you have to establish settings for basic price calculation in the schema step. In this schema step, you would select the Disc. period exempt field. The field for billing relevance is selected as follows:  Field selected: The basic price is not charged for the disconnection period when the installation is billed.  Field not selected: The basic price is charged for the disconnection period when the installation is billed. It is possible to select this field during order creation. You can enter the disconnection type (device sealed, for example). You can enter meter reading results (or estimations) You can charge fees for disconnections using a charge schema in Customizing.

Reversal of Disconnection Activities

Disconnection Disconnection document Disconnection Disconnection activities activities 6 Release Release 5 Disconnection Disconnection order order Entry Entry of of disconnection disconnection Reconnection Reconnection order order Entry Entry of of reconnection reconnection data data Completion Completion

4 3

2 1

You can cancel activities in disconnection documents in reverse order (last to first)

 SAP AG 1999



You can cancel activities in the disconnection document in reverse order, that is, from last to first only.

Disconnection Document: Basic Functions

Disconnection document Disconnection/ reconnection order

Entry

 Selection of objects

 Confirmation of disconnection/ reconnection order

 Creation of service orders or notifications (PM)

 Selection of objects

 Enter meter readings  Charge schema  Relevance to billing

 SAP AG 1999



Disconnection and reconnection orders are created as follows: All objects are displayed that can be disconnected. The devices selected for disconnection are indicated as such. . These devices are a subset of all devices displayed. The system displays different devices depending on whether you have defined contract-account- or contract-specific disconnection in Customizing. The user then decides which of these devices to actually disconnect. For each disconnection or reconnection document a service order can be generated in the background in the Plant Maintenance (PM) application component. When the disconnection document is displayed again, the generated service orders are recorded in the disconnection document. The disconnection/reconnection order receives a confirmation status in the disconnection document. If PM orders were created in parallel to the disconnection/reconnection order, these are further processed and released in Plant Maintenance. When you enter the disconnection or reconnection, the corresponding service orders can be confirmed in the background. You must establish settings accordingly in Customizing in order to use this option. The order in question must also have been released.

Contract-Specific Disconnection

Item has reached dunning level 04 (disconnection)

Business partner

Contract account

Contract 1

Contract 2

Contract 3

1,000 UNI DL 02

1,300 UNI DL 01

1,000 UNI DL 04

2,500 UNI DL 03

3,000 UNI DL 01

2,500 UNI DL 02

Gas meter

Electricity meter

Water meter

The disconnection document proposes disconnection for all devices that belong to contract 3 (in this example, the water meter) Devices that belong to other contracts (1 and 2) can also be selected manually, if necessary

 SAP AG 1999

The system usually proposes devices for disconnection from all contracts from a certain contract account.  If you want to disconnect devices from individual contracts, you have to establish customizing settings contract-specific disconnection. 

Create Disconnection Order: Example

Objects to be disconnected

Disconnection order 1

Device 1

Device 1

Device 2

Device 2

Device 3 Flat-rate installation Device 4

Entry of disconnection Device 1 Disconnection order 2

PM/SM order A

Device 4 PM/SM order B

 SAP AG 1999

All devices and flat-rate installations belonging to the reference object are proposed for disconnection. Devices in installations with a guaranteed supply are not proposed, however. In the example, devices 1 to 4 and one flat-rate installation are proposed by the system. An item reaches the disconnection dunning level. The item belongs to a contract to which devices 1 and 2 are assigned. The system marks devices 1 and 2 for disconnection. The devices are selected and placed in disconnection order 1.  Once disconnection has taken place, the relevant data, including the date and time of disconnection, is entered. In the example, only device 1 was actually disconnected.  Later it is decided that another device (device 4) should be disconnected. A second disconnection order is created to do this (disconnection order 2).  A separate PM/CS order is generated for every disconnection order. 

PM/SM Order for Disconnection/Reconnection

Order code

PM

MM

PS

CO

PM/CS order

Transactions

Components

Capacity load utilization

Confirmation Confirmation of of times times

Purchase requisition

Purchase Purchase order order

Material reservation

Goods Goods issue issue

Goods Goods receipt receipt

 SAP AG 1999







 

If you enter an order code in the disconnection document when a disconnection or reconnection order is generated, either a service order or a notification will be created automatically in the background, depending on your customizing settings. In the service order, the required operations are specified. These operations can be carried out by your own company staff or by external companies. The basis for capacity planning is the allocated planned times. A purchase requisition can be initiated automatically for the external services. The components allocated to the operations are reserved in the warehouse. Materials can be withdrawn and staged on the basis of reservation. A procurement process is initiated for external materials that are not kept in stock. Important utilities, such as special tools or drawings, can also be allocated to the operations. The actual data is entered on the basis of the service order using the appropriate confirmation functions.

Disconnection Document: Secondary Functions (Outlook)

Remove devices Update creditworthiness

Adjust budget billing plan

Trigger Disconnection document interim billing

Create customer contact

Create customer notification

 SAP AG 1999

    

You can adjust the budget billing plan directly through the navigation button Change budget billing plan. Customers will be sent notification of the (completed) disconnection and of the costs that were incurred. This might include a list of the items that resulted in disconnection. It will be possible to create an interim bill using the meter readings taken on the disconnection date. The process of disconnection and reconnection will be logged in a customer contact. At the moment, customer contacts are stored in a separate front office process step. The business partner's creditworthiness can be updated as part of the disconnection process.

Customizing: Processing Variants

Disconnection document

Fixed, unique allocation for each disconnection reason

Processing variants Disconnection reason and long text Default values: Order codes (disconnection and reconnection) and PM planning plant for PM orders in Service Management Order Default values: Date offsets and times of day codes for order creation and entry processes

Define charge schema Define relevance to billing  SAP AG 1999

One processing variant is allocated to a disconnection document. The processing variant contains the default values for the functions of the disconnection document, and is specified in Customizing.  It contains one single disconnection reason and a descriptive long text.  You use order codes to specify the default values for the service order. You specify the order codes in Work Management. You can also define a default value for the PM planning plant.  The following allocations of processing variants to disconnections are provided as standard: A disconnection from FI-CA contains the processing variant DUNN; a disconnection upon customer request contains the processing variant CUST; and a disconnection for technical reasons contains the processing variant TECH. You can change these allocations using the user exit EXIT_SAPLEDCN_001.  

Customizing: Offsets

SpErfDatOffset WIBAufDatOffset SpAuftrDatOffset

WIBErfDatOffset

Time

Create disconnection order Scheduled

Enter Create Enter disconn- reconnection RECONN. ection order Scheduled disconnection reconnection reason date Disconnection date Reconnection date Disconnection activity date Reconnection activity date

 SAP AG 1999

In the processing variants you can specify offsets. An offset is the interval between today's date and another date. You can use offsets to plan when disconnection should be carried out. Offsets can also help with the entry of disconnection data by providing a default value for the disconnection date, based on the system's assumption of when disconnection took place. The same applies to reconnection.  When you generate a disconnection order, a planned disconnection date is proposed, calculated on the basis of today's date + the disconnection order date offset.  When you enter disconnection data, it is assumed that disconnection took place on the disconnection date, which is calculated as today's date minus the disconnection entry date offset. The disconnection activity date for each individual device/installation is assigned the same value.  The planned reconnection date is calculated as the date when the reconnection order is generated + the reconnection order date offset. It follows that the reconnection date is calculated as the date when the reconnection data is entered minus the reconnection entry date offset. 

Customizing: Order Codes Create disconnection order - Default value from

Customizing

Create reconnection order

Order codes

DC00

RC00

- Default value from Customizing - Specified manually

- Specified manually

Allocated to

Allocated to

Service object e.g. SPERRUNG

Service object e.g. WIB Derivation of

Default values for the automatic creation of PM orders

PM plant

Order type

Work center

Bus. area

0001 DISCONN.

SM01

E.20

0001

DISC

0001 RECONN.

SM02

E.50

0001

RECO

...

Service object

...

...

...

...

Task list FL group

...

Re. type

Ref. obj. type

1

01

02

1

02

02

...

...

...

Order profile

 SAP AG 1999

When you are carrying out disconnection or reconnection, you can use order codes to establish a link to PM order management functionality. Order codes are defined in Work Management Customizing.  If when you are generating a disconnection or reconnection order you also specify an order code in the disconnection document, a PM order can be created automatically in the background. The order code used for the disconnection/reconnection order can either be specified manually by the user or derived automatically by the system from the Customizing settings for the processing variant.  The order code is assigned a service object with the ID 00 in Work Management Customizing. In the example, order code DC00 is assigned the service object DISCONNECTION and order code RC00 is assigned the service object RECONNECTION.  The service object masks an order profile. The order profile specifies the data that is to be used for the automatic creation of a service order for a combination of PM planning plant and service object. In the order profile, you can store default values for the order type, the relevant work station, the business area, and the task list group. A task list group is a logical grouping of general maintenance task lists. You can also use the order profile to specify whether a functional location or a piece of equipment must be entered for the creation of an order. 

Addendum: Work Management - Plant Determination

Connection object

Address Regional structure

Regional structure group Regional structure group

Regional structure area

+

Maintenance planning plant

Service object + ID

 SAP AG 1999

In order to be able to generate service orders or notifications, the system requires a maintenance planning plant. If the plant has not already been defined in Customizing you must determine it before you create orders.  You can define a default maintenance planning plant in Customizing (you should do this if you always want to use the same plant). Although the system will always propose this plant in the disconnection document, you can change it manually at any time. If no maintenance planning plant is specified in the disconnection document, the system uses the following logic to find a plant: 1) The regional structure group from the connection object of the device is used for plant determination. If the connection object is not assigned to a regional structure group, the regional structure group of the street or street section is used. 2) One or more regional structure groups can be assigned to a regional structure area. This allows larger enterprise area groupings. 3) Each regional structure area and service object can be assigned a maintenance planning plant.  A message is displayed if the system cannot find any maintenance planning plant at all. If you ignore the message, the system does not create a service order or notification. 

Disconnection Workflows: Confirmation Status

Objects involved in disconnection activities

Confirmation status for disc./reconn.

Confirmation status

Completion type

Create new service order

 SAP AG 1999

You can define your own confirmation status for disconnection and reconnection.  Confirmation status for disc./reconn.: you specify whether each confirmation status is for disconnection or reconnection.  Other objects in the activity: Tells you whether other objects can be included in the disconnection or reconnection activity.  Completion type: you can set the service order to Technically completed or Not completed.  You can also create a new disconnection or reconnection order.

Disconnection Document and Workflow

Disconnection document  No reconnection if the installation has not been disconnected  No new disconnection order if the installation is already disconnected

Consistency Consistency

Workflow

 Agent determination  Processing of confirmation reasons  New order  Disconnection reason obsolete  Deadlines

Flow Flow control control

 SAP AG 1999

The design of the disconnection document itself goes a long way towards ensuring the consistency of the whole business process: Reconnection can only be triggered after a corresponding disconnection. If a device or a flat-rate installation has already been disconnected, it is not possible to generate a second (redundant) disconnection order for this disconnection object.  The supplied workflow samples for the disconnection/reconnection business processes also offer enhanced flow control options: Agent determination for your specific enterprise structure for the individual steps within the workflow A suitable response to the confirmation reasons when entering the disconnection and/or reconnection The option for generating a new order for specific confirmation reasons (for example, because the customer was not at home) Automatic response to a disconnection reason that has become obsolete (for example, trigger reconnection as the result of a payment received) Options for introducing escalation measures (for example, because the technician was refused entry) Automatic monitoring of dates and deadlines (for example, disconnection order was created, but no confirmation was received after x days) 

Disconnection/Collection Workflows: Overview

IS-U disconnection: customer request

IS-U disconnection: collection

IS-U collection at account level

Reconnection Subflow Terminate disconnection workflow with follow-up  SAP AG 1999

 









The following workflow templates are relevant to disconnection and reconnection and are provided by SAP: The workflow IS-U disconnection upon customer request models the process carried out when the customer requests disconnection of the installation. This workflow corresponds to the functions of the workflow IS-U disconnection: collection procedure, which is described in more detail below. The workflow IS-U disconnection: collection procedure models the process from disconnection to reconnection, when triggered by overdue payments. You use it to monitor the process and print multiple service orders. The workflow IS-U collection procedure at account level models the following process: the collector takes action to obtain debts from the customer. If successful, the payment can be posted; if not, an agreement can be reached with the customer about payment (in the form of an installment plan or a deferral of payment for certain items). Service orders are not generated for this. A central sub-workflow (sub-workflow for reconnection) is used in the workflows IS-U disconnection: collection procedure and IS-U disconnection: customer request . This workflow contains the reconnection process in full. The workflow Terminate disconnection workflow and follow up terminates the workflow in question (IS-U disconnection at customer request and IS-U disconnection: collection procedure) and generates an event that restarts the disconnection workflow after a predefined length of time has elapsed.

Start of Disconnection/Collection Workflows

Front office/CIC call

FI-CA

Dunning run Items at disconn. dunning level Print-out of dunning notice

IS-U disconnection: customer request

Manual

Follow up

IS-U disconnection: collection

Manual

Follow up

IS-U collection at account level

Manual

 SAP AG 1999

The workflows are triggered as follows:  The workflow IS-U disconnection at customer request is normally started from the front office.  The workflow IS-U disconnection: collection procedure is triggered by the event "disconnection document generated". Once an item in the contract account has reached the disconnection dunning level, the corresponding work item appears in the inbox of the relevant agent after the dunning run and the printout of the dunning notice.  The workflow IS-U collection procedure at account level is also triggered by a dunning notice being printed.  The workflows IS-U disconnection: collection procedure and IS-U disconnection at customer request can write a work item resubmission automatically, for example, if the customer could not be contacted. Once the period specified in the workflow ends, the workflow begins again.  In addition, all workflows can be started manually (intended primarily for testing purposes). In the case of disconnection and reconnection, however, this will only work if the necessary data has been prepared in advance.

Disconnection/Collection Workflows: Create Disconnection Document Front office/CIC

IS-U disconnection: customer request

Create disconn. document

Print-out of dunning notice

Create disconn. document

IS-U disconnection: collection

Disconn. document created

IS-U collection at account level

Disconn. document created

 SAP AG 1999

In the workflow IS-U disconnection: customer request, a disconnection document is created in the background using the values transferred from the front office (customer identification).  When a dunning notice is printed (if items that have reached the disconnection dunning level are found), a disconnection document is generated simultaneously. The workflows IS-U disconnection: collection procedure and IS-U collection procedure at account level are automatically triggered in parallel by the event "disconnection document generated".  The workflow IS-U disconnection: collection procedure is automatically disabled if the disconnection document is created within the IS-U disconnection: customer request workflow. 

Disconnection/Collection Workflows: Relationships Print-out of dunning notice

IS-U collection at account level IS-U disconnection: collection

Disconn. Disconn. reason reason obsolete obsolete

Create installment plan

Process documents for open items

Post payment

Disconn. Disconn. reason reason obsolete obsolete

 SAP AG 1999

In contract accounts receivable and payable, the system checks in certain situations whether the contract account contains items that have reached the disconnection dunning level. The status is checked in the following cases: When a document is reversed At the cash desk When processing a payment lot During payment In account maintenance In the installment plan When deferring open items  If none of the items are at the disconnection dunning level any more, the event "disconnection reason obsolete" is posted. This also occurs in the workflow IS-U collection procedure at account level, for example, when a payment is posted or a payment agreement is reached.  The event "disconnection reason obsolete" triggers a reaction in the workflow IS-U disconnection: collection procedure. The exact consequences will be described in detail later. 

Disconnection Workflows: Confirmation Status

Create disconn. order Confirm disconn. order Disconn. reason suspended

Disconn. complete

Entry refused

Disconnection document Confirmation status New order

Entry not poss.

No one home

New order? Follow up?

End of loop  SAP AG 1999



Different options are specified in the workflow, depending on the confirmation status entered in the disconnection document:  If the technician visits the customer but does not disconnect the installation after all (because the customer promises the technician that payment is on its way, for example), you have the option of suspending the disconnection (confirmation status: confirmed: disconnection suspended).  If disconnection is suspended or performed, no further disconnection order is required. The workflow waits for the disconnection reason to become obsolete (see the following slides).  If no one was available, or if disconnection was not possible for technical reasons, you have the option of generating a new disconnection order, which sends the technician to perform disconnection again. You can also start a resubmission, which places the work item in the inbox again at a later stage.

Disconnection Reason Obsolete After Creation of Disconnection Order

Generate disconn. order

 Disconnection order generated but not confirmed User decision:

Confirm disconn. order Create reconnection order Confirm reconnection order

Was the disconnection agent stopped? Yes Workflow ended Work item deleted

No Confirm disconn. order Reconnection order, if necessary

 SAP AG 1999

The event disconnection reason obsolete can occur at any one of a number of stages in the workflow. The workflow uses the appropriate wait steps to react flexibly to this event in accordance with the processing context at the time of the event.  If the Disconnection reason obsolete event occurs after the disconnection order is generated but before its confirmation (entry of disconnection), a user decision is required: If the technician can be contacted, the workflow is ended and the work item for confirming the disconnection is deleted. However, if the disconnection agent could no longer be reached the disconnection order is confirmed and a reconnection triggered, if necessary. The creation of a reconnection order depends on the confirmation status. 

Disconnection Reason Obsolete After Confirmation of Disconnection Order

Create disconn. order Confirm disconn. order

 Disconnection confirmed

Confirmation reason: Was the disconnection carried out? No

Create reconnection order Confirm reconnection order

Workflow ended Work item deleted

Yes Create reconnection order Confirm reconnection order

 SAP AG 1999

The event disconnection reason obsolete can occur at any one of a number of stages in the workflow. The workflow uses the appropriate wait steps to react flexibly to this event in accordance with the processing context at the time of the event.  If the event disconnection reason obsolete occurs after the disconnection order has been generated and confirmed, the next steps are determined by the confirmation reason: If it is stated in the confirmation that disconnection took place, the reconnection process is triggered automatically - the relevant agent is instructed via a work item in his/her inbox to create a reconnection order. If it is stated in the confirmation that disconnection did not take place, the workflow is terminated. 

Important Wait Steps

Wait for Disconnection reason obsolote event Wait for confirmation of disconnection order Wait for confirmation of reconnection order It is also possible to define missed deadlines, which take effect after a freely definable length of waiting time has elapsed.

 SAP AG 1999



In addition to the wait steps defined for processing the event disconnection reason obsolete, the wait steps shown on the slide are also modeled in the workflow.

Disconnection and Reconnection: Unit Summary  Disconnection can be triggered by FI-CA, or can be carried out manually upon customer request or for technical reasons.  The disconnection document records the status of disconnection and enables you to branch to the entities included: reference objects, disconnection objects and disconnection activities.  Service orders (PM) can be generated to correspond to the disconnection and reconnection orders created.  The workflow "IS-U Disconnection: Collection Procedure" makes the following activities possible: 

Agent determination



Creation of multiple service orders



Automatic follow-ups or escalation activities

  SAP SAP AG 1999  AG

A response to a disconnection reason that has become invalid.

Disconnection and Reconnection Exercises Unit: Disconnection and Reconnection Topic: Carrying Out the Process Using the Workflows Provided by SAP At the conclusion of this unit, you will be able to: •

Carry out the disconnection and reconnection processes in various forms

In the following exercises you will carry out the disconnection and reconnection processes in a number of variations. These tasks are based on the following scenarios: a) The customer has already been dunned and his due amounts have reached the disconnection dunning level. Service to the customer is disconnected. After disconnection, the customer pays the open items in full. A reconnection is then carried out. b) A customer calls to request that the electricity supply to their vacation home be disconnected for a specified period of time (disconnection at customer’s request). c) The customer has already been dunned and his due amounts have reached the disconnection dunning level. Therefore, service to the customer is to be disconnected. As the customer is not available when the technician calls at the premise, however, disconnection has to be postponed until the technician can pay a second visit (optional). 1-1 Disconnection and collection procedure/customer contacted This exercise is based on the following scenario: Customer PJ0601A0## has been dunned and the amounts due have already reached the disconnection dunning level. Service to the customer is disconnected. After disconnection, the customer pays the open items in full. A reconnection is then carried out. 1-1-1 Determine the active workflow for the dunning letter for customer PJ0601A0## using the CIC. Display the work item but do not process it at this time. Make a note of the disconnection document number. 1-1-2 The agent’s processing interface is the workplace inbox or the Inbox tab page in the application area. Search the work items there to find the work item for generating a disconnection order for your business partner’s disconnection document. 1-1-3 Call up the work item for generating a disconnection order for your disconnection document and carry it out. Display the reference object and the data environment of your reference object. Which processing variant was used?

Which offset is proposed for the disconnection order in the IMG? Now create a disconnection order. Create a service order in SM/CS as well. To do this, use order code DC00 and maintenance planning plant U003. 1-1-4 Check the disconnection in a second session. You can get an overview of the situation at any point by using the Log function of the disconnection document. Search for the disconnection document via the process transaction in the Utilities industry menu. Search for the disconnection document via the process transaction in the Utilities industry menu. Display the service order. 1-1-5 The technician was able to carry out the disconnection. Confirm the disconnection order using the integrated inbox. 1-1-6 Display the customer account. The customer pays the outstanding sum of UNI 1000 in full. Post an incoming payment with payment at cash desk. Use the following data: Recon. key

IUT250

Business partner

PJ0601A0##

Contract account

PJ0601A0##

Amount

1000

Bank clrg acct

113100

Company code

U300

Currency

UNI

Payment lot

IUT250-##

Clear the items completely by posting an item in dialog. Please do not print a receipt once posting is complete. 1-1-7 The work item for reconnection now appears in the inbox. Perform a reconnection. Create a reconnection order. Create a service order in SM/CS as well. To do this, use order code RC00 and maintenance planning plant U003. Confirm the reconnection using the integrated inbox or the Inbox tab. Choose Confirmed: reconnection completed as the confirmation status.

1-2 Disconnection at customer’s request This exercise is based on the following scenario: Customer PJ0603A0## calls to request that the electricity supply to their vacation home be disconnected for a specified period of time (disconnection at customer’s request). 1-2-1 Execute a disconnection upon customer request using the CIC. Use customer PJ0603A0##. Carry out the process Disconnection: customer reqst for business partner PJ0603A0##. 1-2-2 Create the contact using the values that are proposed. 1-2-3 Determine the active workflows for your customer, and determine the disconnection document number. To do this, choose the Active workflows process from the action box. 1-2-4 Create a disconnection order. However, this time don’t create an additional SM/CS order. To do this, call the inbox in a second session. Which processing variant is active for disconnection upon customer request? Confirm the disconnection via the integrated inbox as you did in the last exercise. The technician was able to carry out the disconnection. 1-2-6 The work item for reconnection now appears in the inbox. Execute a reconnection and then confirm it. Choose “Confirmed: reconnection completed” as the confirmation status. 1-3 Disconnection and collection procedure/customer not home This exercise is based on the following scenario: Customer PJ0601A0## has been dunned and the amounts due have already reached the disconnection dunning level. Therefore, service to the customer is to be disconnected. As the customer is not available when the technician calls at the premise, however, disconnection has to be postponed until the technician can pay a second visit. 1-3-1 Determine the active workflow for customer PJ0602A0## using the CIC. Display the work item but do not process it at this time. Make a note of the disconnection document number. 1-3-2 The integrated inbox is the processing interface for the agent. Search the work items there to find the work item for generating a disconnection order for your business partner’s disconnection document. 1-3-3 Call up the work item for generating a disconnection order for your disconnection document and carry it out. Now create a disconnection order. Create a service order in SM/CS as well. To do this, use order code DC00 and maintenance planning plant U003. 1-3-4 The technician was not able to carry out disconnection, as no one was available when he called at the premise. Using the relevant status, confirm the disconnection order in the integrated inbox. Do not generate a new order.

Disconnection and Reconnection: Solutions Unit: Disconnection and Reconnection Topic: Carrying Out the Process Using the Workflows Provided by SAP 1-1 Choose Utilities Industry → Customer Service → Process Execution → Front Office/Customer Interaction Center → Customer Interaction Center. 1-1-1 Enter PJ0602A0## as a search criterion in the Partner field and identify this business partner. Start the search. Select the contract account in the Environment tab page in the navigation area, and start the Active dunning workflow process for this business partner. A window appears containing two entries- one for the main workflow and the sub-workflow allocated to it. Choose the active workflow (double-click). The workflow step log is displayed automatically. You can analyze the process flow and determine the disconnection document number. 1-1-2 Choose menu path Office → Workplace → Inbox → Workflow or the Inbox tab page in the application area. 1-1-3 Position the cursor on the work item and call it by double-clicking on it. Select the Execute function. This takes you automatically to the disconnection document in processing mode; you can also create a disconnection order here. In the disconnection document, execute the Display ref. object and Ref. Obj. Data envirnmnt functions. The processing variant is DUNN. The value 0 day is set as an offset for the disconnection order date. You can find the setting in the SAP Easy Access menu by selecting: Tools → Accelerated SAP → Customizing → Edit Project. Go to the SAP Reference IMG and choose: SAP Utilities → Customer Service → Process Execution → Disconnection/Reconnection → Define Processing Variants for Disconnection Documents.

Display the settings for processing variant DUNN. Here you will also see the default values for the date offsets. Note that the device determined on the basis of the reference object is already flagged for disconnection. The parallel service order in PM/CS will only be generated if the relevant values are entered in the Order code and Plan. plant ord. fields. In this example, default values are proposed for the order code and maintenance planning plant. These values come from customizing settings for processing variant CUST. You create the disconnection order and the parallel service order by choosing Save. 1-1-4 Go to the SAP Easy Access menu and choose Utilities Industry → Customer Service, Process Execution → Disconnection/Reconnection → Display Disconnection Document. to display your disconnection document. The service order number can be found in the table of disconnection activities. To display a disconnection document, double-click on the corresponding entry. You can branch directly from there to the service order using the Display order function. 1-1-5 To do this, choose menu path Office → Workplace → Inbox → Workflow or the Inbox tab page. . Choose the work item for confirming your disconnection order by doubleclicking on it and carry it out. As disconnection did take place, you can keep the confirmation status proposed. If you branch to Discnctn, you will see that the device is already flagged as disconnected (default value). The disconnection is confirmed when the disconnection order is saved. The status of the work item is concluded. The work item is no longer in the inbox.

1-1-6 You can use the following menu path to display the customer account: Utilities Industry → Contract Accounts Receivable and Payable, Account → Account Balance (or alternatively, from within the CIC). An item is due in the amount of UNI 1000. If you use list type 0002, you can also see the charges resulting from the last dunning run (UNI 5). These charges do not have to be cleared in order to cancel the disconnection reason. To reach the payment at cash desk function, choose menu path: Utilities Industry → Contract Accounts Receivable and Payable, Payments → Cash Account → Payment at Cash Desk or call the process for posting a payment in the CIC. Carry out the posting using the Post item online function and entering the specifications listed in the above table. The system assigns the incoming payment of 1000 UNI to the open item of 1000 UNI. Accept this assignment and choose Save. The payment document is now posted. Once the document has been posted, you will be asked if you wish to print a receipt. Choose No. 1-1-7 Create the reconnection order the same way as you created the disconnection order. Proceed in the same way. Proceed as in exercise 1-1-5 (confirmation of disconnection order). Proceed in the same way. The business process is now complete.

1-2 Disconnection at customer’s request 1-2-1 First, identify business partner PJ0603A0##. Then perform the CIC process. You can find the process in the action box under call group Technology. 1-2-2 The process Disconnection: customer reqst consists of two steps: once the relevant workflow has been started, you branch automatically to customer contact creation. Here, the fields are already filled with values which you can accept or reject, supplied by the workflow. Choose Save to create the contact. 1-2-3 Execute the Active workflows front office process for business partner PJ0603A0##. Choose the active workflow (double-click). This takes you automatically to the workflow step log, where you can determine the number of the disconnection document with which you execute further processing. 1-2-4 Proceed as you did in the exercise for creating a work order based on a work item. Proceed in the same way. Plant ord. fields must be left empty to prevent an SM/PM order being generated along with the disconnection order. PM/CS order The CUST processing variant is active for disconnection upon customer request. 1-2-5 Choose the work item for confirming your disconnection order by doubleclicking on it and carry it out. As disconnection did take place, you can keep the confirmation status proposed. The disconnection is confirmed when the disconnection order is saved. The status of the work item is concluded. The work item is no longer in the inbox. 1-2-6 The procedure is the same as the procedure for creating and confirming reconnection orders. Proceed in the same way.

1-3 Disconnection and collection procedure/customer not home 1-3-1 Choose menu path: Utilities Industry → Customer Service → Front Office/Customer Interacion. Center → Customer Interaction Center. Enter PJ0602A0## as a search criterion in the Partner field and identify this business partner. Execute the Active workflows process for this business partner. Choose the active workflow (double-click). This takes you automatically to the workflow step log, where you can determine the number of the disconnection document with which you execute further processing. 1-3-2 Choose Office → Workplace → Inbox → Workflow. 1-3-3 Proceed as you did in the exercise for creating a work order based on a work item. Proceed in the same way. 1-3-4 Choose Office → Workplace → Inbox → Workflow. Choose the work item for confirming your disconnection order by doubleclicking on it and carry it out. As disconnection did not take place, use Confirmed: nobody reached as the confirmation status. Under Discnctn, ensure that you remove the indicator that flags the device as disconnected. Do not set the New order indicator. The disconnection is confirmed when the disconnection order is saved. The status of the work item is concluded. The work item is no longer in the inbox. 1-3-5 To ensure that the disconnection does not get forgotten, the system sends a special follow-up work item to the inbox after a predefined period of time has elapsed to remind the agent of the pending disconnection. Before this, the work item appears in workflow resubmission. Display this follow-up work item. When will this work item appear as a new work item in the integrated inbox? Where do you define this resubmission period? Wait until the specified time has elapsed and check to see if the work item really does appear in the integrated inbox after this time.

Move-In/Out

Contents:  Move-in  Move-out  Move-in/out

 SAP AG 1999

Move-In/Out: Unit Objectives

At the conclusion of this unit, you will be able to:  Perform move-in/out with all of the functions provided  Explain the technical master data for move-in/out

 SAP SAP AG 1999  AG 2001

The Complete Process

Service connection

Initial data creation

Move-in/out Move-in

Move-out ACM E Mov ers

 SAP AG 1999

Move-in

Move-In/Out: Contents (1)

 Move-in  Move-out  Move-in/out

 SAP AG 1999

The Move-In Process

Service Initial data conn. creation

Move-in T r an spor

t

 SAP AG 1999

During move-in processing, you establish a utility service for a customer. You can change or create master data. You allocate a contract to an installation and thereby enable the customer's contract to be billed. Move-in also triggers the payment requests and welcome letters sent at the beginning of utility service.  Before you begin move-in processing, there must be an installation available on the move-in date.  When a customer moves in for the first time, you must create an installation.  You can allocate devices to the installation before or after move-in.  If one of the installations is still allocated to a contract, you must first perform a move-out.  The move-in can apply to one or more contracts. When you create the move-in document, the installation and move-in date you initially specified is assigned to these contracts. However, you cannot create the move-in document if the move-in date is in a period in which one the installations was already billed. 

Move-In: Overview (Technical)

Move-in

 A move-in links the technical master data object installation to the business partner and the contract account when a contract is concluded.

Installation

 In move-in processing, you can create:

Contract



Business partners



Contract accounts



Contracts

Contract account

Business partner

 SAP AG 1999

In move-in processing, you usually have to create a new contract because a contract is required in the case of a new agreement on utility services.  If the business partner and the contract account are already in the system, they do not have to be recreated. 

Move-In: Process Notification Meter by phone reading

Overall check

Customer Welcome contact letter

Move-in Mrs. Smith

Move-in

Move-in processed

Move-in Customer moves in

July

31 Bud. billing $ 250

Business partner account

Contract

Budget billing plan

Cash security deposit

 SAP AG 1999

The customer calls to notify the utility company of his/her move-in. In addition to creating master data objects, you can carry out the following activities within the Move-in business process: Enter meter readings Perform overall check Create log entry for customer contact Create budget billing plan Request cash security deposit Send a welcome letter  When the move-in document is saved, a welcome letter and a budget billing plan can be created automatically. You define settings for budget billing plans in the contract settings in Customizing and settings for welcome letters in document settings in Customizing.  The overall check is used to check contracts for their ability to be billed.  

Move-In: Initial Screen Create Move-In Document Move-in document Business partner Contract account

For external number assignment only If already exists References for • Business partner • Contract account

References Move-in date Premise Installation

Required field Contract

Required field: Premise or installation(s) If already exists

 SAP AG 1999

Move-In: Address Data

Copy address

Address of business partner: 10 Main Street

Premise address

YES

11000 Berlin

10 Main Street 11000 Berlin

NO

Address of business partner:

Move-in  SAP AG 1999

When the business partner moves in, you can automatically assign him/her the address of the premise as a default address. To do this, choose SAP Utilities --> Customer Service --> Process Execution --> Move-In/Out --> Move-In -> Define Move-In Control Parameters at Document Level. If the move-in is processed for several premises in one move-in document, the system uses the first address entered for the premise of the installation.  If this control parameter is not set, the address has to be entered manually.  If you specify a business partner that already exists in the system, their address is displayed automatically in the move-in document. 

Move-In: Full Screen

Move-In Document 4711 Admin/Name

Bank/Pymt Data

Contract Data

Full Screen

Business partner

 Name

 Address  Bank

details

 Communication

data  Relationships

Contract account

 General

data  Account

control

 Dunning

Contract (contracts)

data  Data

assignment  Bill

 General

data

 Incoming/outg.

payments

for budget billing

 Account

assignment  Cash

security deposits

 SAP AG 1999



You can enter the most important master data for the business partner, contract account and contracts in the move-in screen. You maintain more specific data in the full screen.

Move-In: Meter Readings

Move-In Document 4711

MR data Device

Reg.

Meter Reading

100004

OnP

34689 kWh

100004

OffP

6790 kWh

100005

Dem.

600 kW

Direct entry of meter readings Validation

Correction or

OR: Trigger MR order creation

Release

of MR Results

 SAP AG 1999



In move-in processing, you can enter meter readings directly or trigger meter reading order creation.

Service Orders for Move-In and Final Meter Reading

.....…document 4711

MR data Scheduled MR categ. Service notif./order Start date

Create service order/notif with delay

PM/CS PM/CS order order

Transactions Transactions

Components Components  SAP AG 1999

You can establish Customizing settings such that a service order or notification is automatically created every time you create meter reading orders. A separate order is created for each device.  Orders and notifications can be created automatically when you:  Save a move-in document  Trigger an event in a later workflow 

Security Deposits

Payments made by the customer that are requested at the time of move-in and that are paid back (or used to settle any open balance) and when the utility contract is terminated.  Apply to the customer's contract  Can be cash or noncash  Can be refunded on the expiration date or before the contract is terminated

 SAP AG 1999



Only cash security deposits can be created through move-in processing.

Move-In: Security Deposits

Security deposits required?

Customizing:

Company code

Div. class

Billing class

0001

GAS

SPECIAL

0001

GAS

RATE

Move-in

YES NO

Entry: Amount of security deposit Reason for security deposit or Reason for exemption

1st National Pay to the order of

$

In words

$

Amount

- 400,-

Shelbyville 1.4.1996

to or

City

Date

Signature Do not change or mark printed areas

Check no.

X

00000150900

Acct no.

X Amount

X Bank Number

12131400

Security deposit is created automatically

X Text

67291500 11

Do not write in this space

 SAP AG 1999

Via move-in processing, cash security deposits can be created automatically if you have established customizing settings accordingly. Three fields are provided for entering the amount of the security deposit, the reason for the deposit, or the reasons for an exemption from security deposits.  Requests for cash security deposits are defined at the contract level in connection with the company code, division and billing class.  If a security deposit was created, you can branch to it in the change mode in move-in processing. 

Move-In: Budget Billing Plan (1)

Move-In Document 4711 BB plan Contract

BB amount

100004

100

100005

75

Maintain budget billing plan

 Automatic creation of a budget billing plan using the budget billing amount entered; the amount applies to all due dates  You can branch to Maintain Budget Billing Plan  SAP AG 1999

A budget billing plan is automatically created in move-in processing if you enter a budget billing amount and branch to Change Budget Billing Plan. A budget billing plan cannot be created unless the contract is able to be billed.  You can also branch to budget billing plan maintenance from the move-in change screen. There you can use all budget billing change maintenance functions. 

Move-In: Budget Billing Plan (2)

Move-In Document 4711 Electricity contract Joint invoice: 1

Gas contract Joint invoice:1

2nd budget billing plan

1st budget billing plan

03/15/00 04/15/00 05/15/00 06/15/00

Sub-BB plan 03/15/00 04/15/00 05/15/00 06/15/00 ....

 SAP AG 1999

$50 $50 $50 $50

03/15/00 04/15/00 05/15/00 06/15/00 ....

$150 $150 $150 $150

Sub-BB plan 03/15/00 04/15/00 05/15/00 06/15/00 ....

Water contract Joint invoice: 2

$100 $100 $100 $100

$70 $70 $70 $70

Move-In: Due Dates for Budget Billing Budget billing dates ..... 06/15/1999 07/15/1999 08/15/1999 09/15/1999 Periodic billing 10/15/1999 11/15/1999 12/15/1999 01/15/2000 02/15/2000 03/15/2000 04/15/2000 05/15/2000 06/15/2000 07/15/2000 08/15/2000 09/15/2000 Periodic billing 10/15/2000 11/15/2000 12/15/2000 ....

Budget billing requests Move-in date 02/18/2000

10/15/1999 ... 02/15/2000 03/15/2000 04/15/2000 05/15/2000 06/15/2000 07/15/2000 08/15/2000 09/15/2000

----$150 $150 $150 $150 $150 $150 $150

Periodic billing 09/30/2000

 SAP AG 1999

Due dates for budget billings are generated via the schedule records of the portion (from the meter reading unit or the contract).  Budget billings before the current date can no longer be requested. The budget billing plan is only created for future dates up until the end of periodic billing. 

Move-In: Log  Automatic log for 

Creation of move-in documents



Every change to a move-in document

Detail

Long text

Cat. Message S S S S S S

Move-in document 4711 created Contract 100000001 created BB plan created MR results entered Security deposit created Welcome letter sent

 SAP AG 1999



In Customizing you specify whether this change log is displayed.

Status of Move-In Processing

Status of move-in processing

ent 4711 Move-in docum readings Status 03: Meter prepared Contract 2 Move-in status 03 Bank details 1

Contract 1 Move-in status 05

01 Master data maintained 03 Meter readings prepared 04 Readings partially entered 05 Readings entered completely 06 Billing data complete 07 Budget billing plan created 08 Cash security deposit requested 09 Welcome letter triggered 10 Welcome letter printed 99 Reversed

Ban k d etails 1

Contract 3 Move-in status 05 Bank d etails 1

 SAP AG 1999

A status is displayed for each move-in document. The status indicates the extent to which the move-in has been processed.  Since a move-in can apply to several contracts (electricity, gas, water, and so on) that are all processed differently, a processing status is assigned to each contract. The processing status of the entire move-in is determined by the lowest status of the individual contracts.  The processing status is determined at runtime and is not an attribute of the move-in document. 

Move-In: Reversal

Move-in document 4711

Reversal of move-in document

Contract 1 Bank details 1

Contract 2 Bank d etails 1

Contract 3 Bank details 1

 Deletion of meter reading data  Deletion of budget billing plan  Deletion flag for contract

 SAP AG 1999

    

You can reverse the entire move-in document. Reversal cannot be carried out if billing has taken place after the move-in date. Changes to master data (change of address or cash security deposit data) must be reversed manually. The meter reading data and the budget billing plan are deleted automatically. The contract receives a deletion flag. If the move-in object is incorrect you must reverse the move-in. There is a separate function for changing the move-in date. Additional reasons for reversing a move-in include: The move-in was created with an incorrect business partner The move-in was erroneously created with the installations of an incorrect premise The business partner subsequently informs you that he or she does not assume responsibility for some of the installations. In this case, you have to reverse the move-in and create a new move-in document with the correct installations.

Automatic Owner Move-In

Business partner moves out

Owner moves in

Move-in

Move-out

-

Contract account

-

Contract account Owner

Business partner Terminate contract

Installation 03/01/95 - 12/31/96 01/01/97 - 12/31/99

Create contract

 SAP AG 1999

IS-U supports a function whereby move-in is triggered automatically for the owner when your customer (the current tenant) moves out.  A workflow is available for the owner change process. When a customer (new tenant) moves into a premise, a move-out request will be generated automatically for the owner assigned to the premise.  Sample workflow for automated contract billing: ISUACBMovein, ISUACBMveout, ISUACBISub. 

The Owner Assignment Process

Connection Object

Premise

Historical

Option of automatic move-in

Change Owner Assignment

Property 1 Key date 07/28/1998 Installation Hierarchy

Owner No maintenance

Premise

Property 1 Connection object Premise Installation

Premise

 SAP AG 1999

The owner assignment process transaction fulfills a US requirement: Automatic Contract Billing (ACB). Owner assignment ensures that when a tenant moves out of a house, the owner of the house automatically becomes the utility company's contract partner. This function can be made subject to a charge or can be activated for specific seasons (the owner might only be responsible for consumption in the winter months, for example).  You can define a customer's property in the system and manage this data historically. You can define connection objects and premises as property, or you can specify other property such as individual installations or all the installations of a particular division.  Once you have assigned a premise to an owner with this transaction, you can no longer change the owner data directly in the premise. 

Owner Assignment in the Premise

Connection object

Apartment 1

Premise

Entrance hall

Apartment 3 Not historical

Create .. Change ..

Apartment 2

Owner

No automatic move-in

Basement

 SAP AG 1999

A business partner can be assigned as the owner of a premise. Data on premises is not managed historically, so it is not possible to display a history for the owner-topremise assignment.  This type of assignment does not allow for automatic triggering of a move-in when a business partner moves out.  

Move-In/Out: Contents (2)

 Move-in  Move-out  Move-in/out

 SAP AG 1999

The Move-Out Process

Service connection

Initial data creation

Move-in

Move-out ACM E mov ers

 SAP AG 1999

During move-in processing, you establish utility service for a customer. You can make any necessary changes to the business partner's master data that result from a move-out. In particular, the assignment between a contract and an installation is terminated as of the move-out date.  A move-out stops all payment plans. You can trigger a move-out confirmation letter as well as a bill directly from move-out processing.  One or more contracts and corresponding installations must exist on the move-out date in order for the move-out to be performed. 

Move-Out: Overview (Technical)

Move-out Installation

The move-out  Terminates the utility contract on the move-out date  Ends the link between contract and installation

Contract Account

Customer Business partner

 SAP AG 1999

From a technical standpoint, when a customer moves out of a premise, his/her contract is terminated and separated from the installation. The contract can no longer be used.  The link between technical and business master data is ended in a move-out. 

Move-Out: Process Cash Customer Notification Move-out Meter by phone reading order security contact confirmation deposit creation Move-in Mrs. Smith

Move-in/out

Move-out processed

Move-out Customer moves out

July

31 BB pymt

Contract

$250

Bank details 1 1 Payment method 1 Alternative payer .... document 1 Contract accounting document 3 Contract accounting

Changes to master data

Meter reading

Budget billing plan

Final billing

 SAP AG 1999

 

The customer notifies the utility company of his/her move-out: Within the Move-out business process, you can carry out the following activities: Maintain master data (such as changing bank details or address) Enter meter readings Dissolve budget billing plan and cash security deposit Create log entry for customer contact Create a final bill Send a move-out confirmation

Move-Out: Full Screen

Move-In Document 4711 Bank/Pymt Data Contract Data

Admin/Name

Control Data

Full Screen

Name

Business partner

Address Bank

details

Communication

data Relationships

Contract account General

data



Stop budget billing



Dunning/final billing



Account

assignment Bill

control



Move-out confirmation Automatic final billing

Dunning

data Incg/outg.

payments 

Contract (contracts) Are terminated

 SAP AG 1999

 

You can not only change master data but also establish additional settings for move-in/out. You can specify dunning data different from the data in the contact account for final billing.

Move-Out: Budget Billing Plan

Final

Budget billings paid Budget billing plan Due on

Amount

Open

10/15/99 11/15/99 12/15/99 01/15/00 02/15/00 03/15/00 ...

$150 $150 $150 $150 $150 $150

----$150 $150

09/15/00

$150

$150

Move-out on 01/17/2000

Settlement with final billing

Bill

xyz

Quantity x Price 2000,00 Budget billings paid 600,00 Total $1400,00

Open budget billings are not: • Requested • Dunned

 SAP AG 1999

 

The budget billing plan is deactivated in the case of a move-out. Open receivables from the budget billing plan are no longer requested or dunned. Paid budget billings are taken into account during invoicing of the final bill.

Move-Out: Meter Readings

Move-In Document 4711

MR data Device

Reg.

Meter reading

100004

OnP

34689 kWh

100004

OffP

6790 kWh

100005

Dem.

600 kW

Direct entry of meter readings Validation

Correction or

OR: Trigger MR order creation

Release

of MR results

 SAP AG 1999



When you create a move-out document, a meter reading order is automatically created for all registers of devices allocated to billing installations. No order is created if you have already entered a meter reading result.



You can define settings for meter reading orders in Customizing under SAP Utilities → Customer Service → Process Execution → Move-In/Out → Move-Out → Define Control Settings at Contract Level.

Changes to Installation Data

02/01/1998

Cust. 1

Cust. 2

Move- Move-in out

C2

C1

Installation

Time slice 1: 04/15/97- 01/31/98

Contract 2

Contract 1

Nov 1

Dec 1

Jan 1

Time slice 2: from 02/01/98

Feb 1

March 1

Apr 1

May 1

 SAP AG 1999

In the process of initial data creation, a utility installation is created with a single time slice. If the customer moves into this installation, the installation is allocated to a contract. When the customer moves out, the contract is terminated via a final billing and another time slice begins for the installation (starting on the move-out date). No contract is allocated to the installation during this time slice.  If a customer moves into the installation again, the current time slice is allocated to a new contract.   

Move-Out: Reversal

Move-out doc. 4711

Reversal of move-out document

Contract 1 Bank d etails 1

Contract 2 Bank details 1

Contract 3 Ba nk details 1

 Deletion of meter reading data  Reactivation of budget billing plan  Restoration of contract

 SAP AG 1999

Move-out reversal is always carried out for the entire move-out document, not for individual items. Move-out cannot be reversed if a move-in has already been posted to the premise. If the customer moving out has already received the final bill, then billing must be reversed manually.  Changes to master data (changes of address or bank details, for example) must be undone manually.  Meter reading data is deleted automatically. The budget billing plan is reactivated and outstanding due amounts are requested again. The contract is released for use again. 

Move-In/Out: Contents (3)

 Move-in  Move-out  Move-in/out

 SAP AG 1999

The Move-In/Out Process

Service connection

Initial data creation

Move-in/out Move-in

Move-out

Move-in

ACM E Mov ers

 SAP AG 1999

You can process the following during initial move-in/out processing: Move-in/out (move-out and subsequent move-in) to a premise Move-in/out (of business partner) Move-in or Move-out  You can also use move-in/out processing to find existing move-in/out documents for a particular premise or business partner.  You can use enhancement EXSBTI01 to define default entries for move-in/out fields.  You can use a field selection function to restrict the number of fields to be displayed or maintained. 

Move-In/Out (Premise)

= move-out + move-in from or to a premise

Move-in

Move-out

Contract account

Contract account

Business partner

Business partner Terminate contract

Installation 03/01/95 - 12/31/96 01/01/97 - 12/31/9999

Create contract

 SAP AG 1999

 

Move-in/out from or to a premise always applies to one or more installations of that premise. Move-in/out from or to an installation means: The business partner moves out of the installation, resulting in termination of the existing contract. and Another business partner moves into the installation, resulting in the conclusion of a new utility contract.

Move-In/Out (Business Partner)

= move-out + move-in of a business partner

Move-out Premise Premise (installations) (installations)

Terminate contract

Business partner

Business partner Contract acct

Move-in Premise (installations)

Create contract

 SAP AG 1999

A move-in/out relating to a business partner applies to two premises: the premise the business partner moves out of and the premise the business partner moves into.  Move-in/out of a business partner means: The business partner moves out of a premise (installation(s)), resulting in termination of the existing contract(s), and The same business partner moves into another premise (installation(s)), resulting in conclusion of (a) new contract(s). 

Move-In/Out Processing Variants

Manual steps

Manual steps

 Selection

 Selection

of premise  Entry of business partner and bank details

of premise  Entry of business partner and bank details  Mailing

Automatic steps  Customer

address  Contract account, contract and budget billing plan Fast  Move-in reading move-in/out  Welcome letter

 Contracts

Single-step processing

Front Office Context

Edit

Goto

System

billing plan

 Security

deposits

 Move-in

reading taken and

 Welcome X

Front Office Initial Screen

 Budget

entered

Access from

Front Office

and billing address account

 Contract

Help

letter checked

and sent

Proc.

Search criteria Last/first name Street/house no. Zip/City/State Business partner Transaction date Info Envir. Call Description

Address ty. Bus.part. Conn.obj. Phone Change Transact. Call Descriptio n

 SAP AG 1999

You can control special move-in/out activities using processing variants. You can use either special or general processing variants. Special variants speed up move-in/out processing. You use general variants on the initial screen for move-in/out processing. The following options are available: Hold in the move-in/out initial screen when called from the Customer Interaction Center Automatically identify the premise Trigger command automatically when the Return key is pressed  During move-in/out processing you can save changes to business partner and contract account data as scheduled changes. The changes are then activated on the move-in or move-out date. You use report BUSPCDACt to activate scheduled changes. 

Selection Criteria for Move-In/Out

Fixed-term deposit

Process Move-In/Out: Initial Screen Edit Goto Extras System

Header data Document number Move-in/out date

Search parameters for move-out Contract account Business partner Premise

Search parameters for move-in

Help

Variant

Processing Processing variants variants Process Process move-in/out or move-out Process Process move-in move-in

Contract account Business partner Premise

 SAP AG 1999

There are several types of selection criteria for move-in/out processing: The move-in/out screen provides you with several pages for move-in/out data. You can use establish special variants in Customizing to speed up move-in/out processing: You can use the following settings: o Automatic contract selection during move-in/out processing o Automatic installation selection during move-in/out processing o Create move-out in the background o Copy business partner's current contract o Reverse move-in/out in background o Attempt move-in, even if move-out not possible o Period for move-in/out document display o New contract account if change of contract o Reasons for change of contract  You can define default processing variants via user groups.   

Move-In/Out: Summary (1)

 Requirements for move-in 

Existing premise with installation(s), from initial data creation, for example

 Move-in (technical standpoint): 

Linking the contract to the installation



Linking business and technical master data

 Move-in (business standpoint):

 SAP SAP AG 1999  AG



Creation of business master data, budget billing plan, cash security deposits and customer contact



Entry of meter readings



Welcome letter

Move-In/Out: Summary (2)

 Move-out (technical standpoint): 

Termination of a contract



Installation and contract no longer linked

 Move-out (business standpoint): 

Deactivate budget billing plan



Entry of meter readings, changes to master data



Settlement of cash security deposits in final billing



Move-out confirmation

Move-in/out = move-out + move-in relating to

 SAP SAP AG 1999  AG



Business partner or



Premise

Move-In, Move-Out, Move-In/Out Exercises Unit: Move-In, Move-Out, Move-In/Out Topic: Move-In Processing At the conclusion of this unit, you will be able to: • Answer questions about workflow • Perform a move-in Move-in and move-out are frequent processes that the agent often has to carry out without prior notice. You can also use the CIC to perform move-in activities.

Business partner

PJ0402A0## (0##: group number) Mark Dommer North Shawnee Boston MA, 02116

Contract account number

PJ0402A0## (0##: group number)

Premise

PJ0402A0## (0##: group number) 0## Mahler Place Boston MA, 02100

Electricity contract

PJ0402A0## (0##: group number)

Electricity installation

PJ0402A0##

Water contract

PJ0402B0## (0##: group number)

Water installation

PJ0402B0##

Electricity meter

PJ0402A0## (0##: group number) Double-rate meter

Water meter

PJ0402B0## (0##: group number) Single-rate meter

Move-in document

1-1 True or false? 1-1-1 In the move-in process, you can process the objects Business partner, Contract account and Contract in full screen maintenance mode. ______________________________________________________ 1-1-2 You can create cash security deposits and budget billing plans from move-in processing. ______________________________________________________ 1-1-3 When a customer moves out, the installation is managed historically although the customer’s contract is terminated. ______________________________________________________ 1-2 Creating a move-in Process description: Customer Marc Dommer (currently residing at 0## North Shawnee, Boston, MA 02116) already exists in the system as a business partner (PJ0402A##). Mr. Dommer calls to inform you that he has moved into 0## Mahler Place, Boston, MA 02100 as of the first of the month. He needs water and electricity service. 1-2-1 Choose Move-in in the Move-in/out processing. Choose Utilities Industry  Customer Service  Process Execution  Move-in/out. Enter business partner Marc Dommer. You do not have to specify the contract account. The system will either find the existing contract account automatically for the move-in or, if there are several possible contract accounts, it will display a dialog box from which you can select the relevant one. Specify the search parameters for the premise Marc Dommer will be moving into. Create the move-in for the first of this month. Move-in processing displays all the installations that are assigned to the premise you have selected. Please select the installations for electricity and water. 1-2-2 In move-in processing, the system automatically records a customer contact. Specify that the contact was by telephone and enter the name of the business partner who contacted you. 1-2-3 Assign the company code U300 to both contracts in move-in processing. Assign the jurisdiction code for Boston (MA0011000) to the contracts. Use account determination ID 01 for receivables and credit items. Both contracts are always to be invoiced together.

1-2-4 Confirm the move-in readings for Electricity meter

PJ0402A0##

Water meter

PJ0402A0##

Register 1 Register 2 Register 1

10 5 10

1-2-5 You agree on a budget billing amount with Marc Dommer of 150 UNI a month, 70 UNI for electricity and 80 UNI for water. Enter the budget billing amount for the contracts. Display the budget billing plan. 1-2-6 Create a welcome letter from move-in processing. Display the welcome letter in the spool. Enter LT0Q as the printer and enter * in the RDI field.

Exercises Unit: Move-In, Move-Out, Move-In/Out Topic: Move-Out Processing At the conclusion of this unit, you will be able to: • Perform a move-out

Move-in and move-out are frequent processes that the agent often has to carry out without prior notice.

Business partner

PJ0403A0## (0##: group number) James Donaldson 0## North Shawnee Boston, MA 02100

Contract account number

PJ0403A0## (0##: group number)

Premise

PJ0403A0## (0##: group number)

Electricity contract Electricity installation Water contract Water installation

0## North Shawnee Boston, MA 02100 PJ0403A0## (0##: group number) PJ0403A0## (0##: group number) PJ0403B0## (0##: group number) PJ0403B0## (0##: group number)

Electricity meter

PJ0403A0## (0##: group number) Double-rate meter

Water meter

PJ0403B0## (0##: group number) Single-rate meter

Move-out document

___________ (Assigned by the system)

1-3 Creating a move-out Process description: Customer James Donaldson (living at 0## North Shawnee, Boston, MA 02100) notifies you by letter that he is moving out on 08/31/01. The customer has taken the readings for electricity and water and included them in the letter. The customer would like to receive the final bill at his new address at 37 Market Street, San Francisco, CA 94022. In addition, the customer has notified you that he would like to pay the final bill by direct debit (any credit items can be paid with a check) because his account is no longer valid. 1-3-1 Create the move-out document. Go to move-in/out process execution: (Utilities Industry  Customer Service  Process Execution  MoveIn/Out) and create the move-out document for 08/31/01. You only need to enter the search parameters for the business partner and you will be automatically prompted to enter all other data. 1-3-2 Change the address Once you have entered the data, go to the screen Create Move-Out Document. Enter James Donaldson’s new address. Overwrite the existing address: 37 Market Street San Francisco, CA 94022. Choose Enter. The message Error in Address Check is displayed. Choose Yes since this address is outside of your service territory. If you want to keep the old address, go to business partner maintenance and create an additional address for Mr. Donaldson. Go to the address overview and create the address. Choose Back and define the address as the standard address. Copy the address. 1-3-3 Change the payment data Display the payment data. You want to change the customer to a cash payer. You do not have to change the bank details. Delete the entries in the Incoming method and Bank details ID fields. Do not change the Outgoing method. This means that bank details are no longer used for direct debit and credit items will be paid by check.

1-3-4 Enter meter readings Branch to the meter reading data. Enter Meter reading by customer as the current meter reading type. Enter the meter readings. They are: Electricity meter register 1: Electricity meter register 2: Water meter register 1:

2000 3640 1800

Note the column RS (Status of meter reading ) next to the meter data. Choose Enter. Are the meter readings plausible? The meter reading results must have the status 1 (billable) or 4 (released by agent). If the readings are implausible (status 2), a note is displayed in the status bar. Choose Enter to confirm the note. Choose Enter to confirm the note. Releasing a meter reading with status 2. You would like to determine whether consumption has changed significantly. Select the line of the meter reading and choose Correct. On this screen, the expected values and the upper and lower tolerance limits are displayed. Choose Release. This meter reading result has the status 4 and can be billed. Note the column S (status) next to the meter data. Choose Enter. Confirm the notes in the status bar by choosing Enter. End budget billing plan. Ensure that the End budget billing plan indicator is selected. No further budget billings are charged if this indicator is set. Save the move-out document. Document number: ______________ The move-out has now been entered and must undergo automatic processing. The move-out document is billed, invoiced and printed in a batch run at night. Since at the moment there is no new tenant for the premise, your work is finished.

1-3-5 Check the data environment of the connection object. In the CIC, select Connobject Environment from the action box Info. Enter North Shawnee 0## in Technical Data. Expand the connection object view by placing the cursor on the connection object and choosing Expand subtree . Choose Period

and enter the period from 01/01/97 to today’s date.

Is the business partner displayed? Are the devices displayed?

Move-In, Move-Out, Move-In/Out Solutions Unit: Move-In, Move-Out, Move-In/Out Topic: Move-In Processing

1-1 True or false? 1-1-1 True 1-1-2 True 1-1-3 True 1-2 Choose Utilities Industry → Customer service → Process Execution → Move-In/Out or Utilities industry → Customer Service → Front Office Customer Interaction Center → Customer Interaction Center from the SAP menu. 1-2-1 In the Move-In tab page, enter the first day of this month as the move-in date. To find your business partner, use the F4 button in the BusPartner field. Choose the tab page Partner, general (last name and search term) and enter the search parameter Name 1 “Dommer” and search term 1 “Group 0##”. Alternatively, you can enter the data directly in the fields Last name/First name, Street and so on. Enter Mahler Place 0## (group number ##) in the Street/house no. fields in the Premise search parameters. Choose Move-in → Create move-in. A list of installations that match the search parameters you specified under Determination of premises appears. Select the installations for electricity and water. Then a list of business partners that match the search parameters you specified under Determination of contract account/customer appears. Select your business partner. You do not have to specify the contract account. If there is only one contract account for this business partner in the system, move-in/out processing will select it automatically in the initial screen. If there are several contract accounts for your business partner, the system will display a list of possible accounts and you will have to select one. If you do not wish to use an existing contract account for the move-in but would rather create a new one, enter the appropriate category in the Contract account category field. You can then create a new contract account in move-in processing. You can also use the front office process Create move-in by using the Action Box call group Move-In/Out once you have found the business partner and premise in the front office or CIC. You only have to enter a move-in date as additional parameter. You are automatically taken to move-in/out processing. 1-2-2 You can enter data for the customer contact in the tab page Name/Administration. Enter 1 for telephone in the Contact type field and enter the business partner. 1-2-3 A new contract is now automatically created for every installation. Go to the tab page Contracts in Move-in.

1. The relevant company code: CoCd=U300 2. The indicator for joint invoicing JI=1 (the contracts are to appear on one bill) 3. The account determination ID for receivables/credit items of the contract AD=01 1-2-4 Display meter reading data by choosing MReadingData. 1-2-5 Choose Contracts for an overview of the contract. Enter the budget billing amounts in the BB amount fields. To see the budget billing plan, click on the button Budget billing plan. The remaining due dates carry on until the end of September. 1-2-6 Choose Welcome letter to create the welcome letter during move-in processing. You can display the move-in letter by choosing System → Own spool requests.

Solutions Unit: Move-In, Move-Out, Move-In/Out Topic: Move-Out Processing

1-3 Creating a move-out 1-3-1 Choose Utilities Industry → Customer Service → Process Execution → Movein/out Enter 08/31/01 as the move-out date. You only need to enter search parameters for the business partner. A list of contracts appears. Select the contracts for electricity and water. You can also create the move-out creation process in the front office or CIC once you have identified the business partner. 1-3-2 You then branch to Create Move-Out Document. Click on the Address data tab page to enter James Donaldson’s new address. Overwrite the existing address: 37 Market Street CA 94022 San Francisco Enter CA or California. Press Enter. The message Error in Address Check is displayed. Choose Yes since this address is outside of your service territory. 1-3-3 Branch to the customer’s bank details by choosing Bank/payData. You want to change the customer to a cash payer. You do not have to change the bank details. Delete the entry ‘D’ in the Incoming method field and delete the entry ‘0001’ in the Bank details ID field. Do not change the entry ‘C’ in the Outgoing method field.

1-3-4 Branch to the meter reading data. Enter 02 Meter reading by customer in the Actual MR type field. Enter the meter readings. They are: Electricity meter register 1: Electricity meter register 2: Water meter register 1:

2000 3640 1800

Are the meter readings plausible? Device PJ0403A0##, register 001. Consumption ok. Status 1 Device PJ0403A0##, register 002. Consumption not ok. Status 2 Device PJ0403B0##, register 001. Consumption ok. Status 1 Under Contract/ctrl.data, ensure that the Stop budget billing plan (SB) indicator has been selected. No further budget billings are charged if this indicator is set. Save the move-out document. 1-3-5 In the CIC, call Connobject. Environment from the Info action box, and enter the address of the connection object in Technical Data. You receive the overview once you have determined the connection object. YES. But only if the period extends to the move-out date. The offset to the move-out date is displayed in the contract. YES, in the installation and in the device location.

IS-U Sales Processing

Contents:  Sales transaction  Quotations and orders  Products  Set types  Customizing  Workflow  Product engine and CRM

 SAP AG 1999

IS-U Sales Processing: Unit Objectives

At the conclusion of this unit, you will be able to:  Use the sales transaction  Create quotations and orders  Create products  Customize products  Explain the set type concept  Explain the integration between products and CRM

 SAP SAP AG 1999  AG 2001

IS-U Sales Processing: Process and Objects (1)

IS-U IS-U CIC CIC

IS-U IS-U Sales Sales

Product Product

CRM CRM SIC SIC

Material Material

CRM CRM CIC CIC

Configuration Configuration // set set type type

Quotation/ Quotation/ Sales Sales Order Order

Master Master Data Data Reference Reference

Master Master Data Data template template category category

Master Master Data Data generator generator

Master Master Data Data Objects Objects

IDE?

IS-U/CCS

Internet Internet

Workflow  SAP AG 1999











You sell a utility product to a customer. Depending on the product, you can enter additional information in the configuration. You then start pricing and generate a quotation. If the customer accepts the quotation, the master data generator creates the IS-U data. 1. Select product. The product can be called from the CIC, the Internet, or from a sales transaction. The product must be defined as a material. You can also link additional information with the product (material) through set types. 2. Create quotation The system performs this step automatically as soon as you save a utility quotation in IS-U. All the data from the utility quotation is included in the SD quotation. No documents are created in IS-U. The customer accepts the quotation The customer accepts the quotation You can perform the activity directly in the (quotation) document overview in the CIC. If the customer does not accept the quotation, the process ends at this point. 3. Create order The system also performs this step automatically. To do this, the items from the quotation are copied to the new order. 4. Create/change IS-U data Immediately after the SD order is created, the system calls the master data generator for each utility product, in order to create or change any necessary IS-U data. In the process, a workflow controls the transfer of customers from another company to your utility company.

IS-U Sales Processing: Process and Objects (2)

IS-U IS-U CIC CIC

IS-U IS-U Sales Sales

Product

CRM CRM SIC SIC

Material

CRM CRM

Configuration / set type

Quotation/ Sales Order

Master Data Reference

Master Data Template category

Master Data generator

Master Data Objects

IDE?

IS-U/CCS

Internet Internet

Workflow  SAP AG 1999

Products can be called from different environments. Telesales. In the telesales process, products are called from the CIC. Method UtilCustomerOrder.CreateForUtilProducts can be used to call the sales transaction. In addition, an integrated entry form exists for the application area (this form has to be configured manually beforehand; view cluster CRM_CIC_DEFWS).  Sales transaction. The sale of products and the creation of a quotation/order or order can be started in ISU from the transactions ISU_SALES_QUOTATION and ISU_SALES_ORDER, respectively. To do this, choose the following path from the SAP menu: Utilities Industry --> Customer Service --> IS-U Sales Processing --> Create Sales Quotation or Create Sales Order.  Internet. Products can be placed in the Internet via online stores and product catalogs. In this case, however, no quotation/order or order is created. Instead, method UtilityProduct.IsuProductImplement (the master data generator) is called.  CRM. In future versions, the products will be offered to customers via the CRM - e.g. the Contact Center or the Webshop. IS-U will be the background system in this scenario.  

Sales Transaction Connect. object

Simulation

Premise Partner account Simulation price Products

Set Types Quotation items  SAP AG 1999

Products and Profiles Separate screens and functions a) Business partner and account b) Connection object and premise

Organizational structure a) Distribution channel

Quotation and order

b) Sales organization c) Division

Quotations and orders

Master data template a) Business partner and account b) Connection object and premise  SAP AG 1999

Reference customer

IS-U Sales Processing: Process and Objects (3)

IS-U CIC

IS-U Sales

Product

CRM SIC

Material

CRM

Configuration / set type

Quotation/ Sales Order

Master Data Reference

Master Data Template category

Master Data generator

Master Data Objects

IDE?

IS-U/CCS

Internet

Workflow  SAP AG 1999



The process flow from the creation of the quotation to the execution of the master data template is controlled by workflow ISUProdCRM.

Workflow 1: ISUProdCRM (Simplified) Order created for CRM processing

Quotation created for CRM processing

Workflow started

Simplification Determine IS-U data from SD document

Wait for quotation to be refused

Customer response Wait for quotation to be accepted

Cancel workflow

IS-U: Create sales order for quotation (if necessary) Determine item data from order IS-U: IDE enrolment communication New items are pending for processing Generate ISU product  SAP AG 1999

Determine next product

No products have been assigned

Workflow ended

IS-U Sales Processing: Process and Objects (4)

IS-U CIC

IS-U Sales

Product

CRM SIC

Material

CRM

Configuration / set type

Quotation/ Sales Order

Master Data Reference

Master Data Template category

Master Data generator

Master Data Objects

IDE?

IS-U/CCS

Internet

Workflow  SAP AG 1999

IDE Process Direct communication between the partners

Customer

New utility company

1. Inquiry from prospective customer

Distribution Distribution list

2. Inquiry

3. Answer

4. Reply regarding prospective customer

Old utility company  SAP AG 1999

Workflow 2: ISUIdeEnrCom (Simplified, Detailed) Workflow started Collect the necessary data (several steps, simplified!) IS-U: IDE send enrolment inquiry Wait for answer

Inquiry answered, accepted Timeout End workflow

Inquiry answered, rejected IS-U: Prepare IDE message Send mail 1 of 3

 SAP AG 1999

Workflow ended

Inquiry answered, error IS-U: Prepare IDE message Send mail

Master Data Generator: Process and Objects (5)

IS-U CIC

IS-U Sales

Product

CRM SIC

Material

CRM

Configuration / set type

Quotation/ Sales Order

Master Data Reference

Master Data Template category

Master Data generator

Master Data Objects

IDE?

IS-U/CCS

Internet

Workflow  SAP AG 1999

Utility products Materials Management

Sales and Distribution

Material

Class

Characteristics

IS-U Product

Field attributes, set types Required, output, proposal

Master data template

Set Types

ABAP/4, DDIC

Availability IDE, quantity

 SAP AG 1999

Utility products SD documents refer exclusively to material masters (in short: materials). It is therefore necessary to create a separate material for each utility product. The prices are determined in SD depending on the material.  Specific data from IS-U, such as the serial number and period consumption, can be specified by the agent when the sales quotation is generated; the system then passes on this data to all subsequent processes up to the master data generator. To do this, you define set types that you can assign to your utility products. From a technical perspective, the set types refer to characteristics and classes, which in turn are assigned to the material.  You can also define whether you want to use the workflow for the supplier switch  You have to assign a master data template to the product. This template controls which data is ultimately entered.  

Set Types

DDIC structure

Check modules

Programs

Screen number

 SAP AG 1999

Set types and classes Specific data from IS-U, such as the serial number and period consumption, can be specified by the agent when the sales quotation is generated; the system then passes on this data to all subsequent processes up to the master data generator. To do this, you define set types that you can assign to your utility products.  A set type mainly contains a list of fields and a screen that is used to display and check these fields.  To define user-defined utilities product set types, choose Customizing and the industry-specific component Utilities Industry → Customer Service → IS-U Sales Processing → Define user-defined utilities product set types.  

IS-U Sales Processing: Process and Objects (6)

IS-U CIC

IS-U Sales

Product

CRM SIC

Material

CRM

Configuration / set type

Quotation/ Sales Order

Master Data Reference

Master Data Template category

Master Data generator

Master Data Objects

IDE?

IS-U/CCS

Internet

Workflow  SAP AG 1999

Master Data Template (Simplified) Business partner Bank details Pymt card

Attributes

Address data Contract account Connection object Address of IO Device location Device data Premise Installation Installation history Facts Device data Contract

 SAP AG 1999

Move-in

The user maintains the following data in the template:  Which values are used to create the master data. In the process, the objects are assigned attributes (you can differentiate here between constants, parameters, and other methods).  Whether optional parts of the template category are used or not (for example, create connection object with or without a device location).  Which parts of the template category can be used multiple times (for example, create business partner with one or two addresses).  SAP provides the two master data templates SALES_PARTNER and SALES_SERVLOC as examples. You can use the appropriate function in the initial screen to copy these templates and modify them to create the objects with your required standard values. You will generally not have to change the assignments of parameters to fields. However, you can do so should this prove necessary. You then enter the names of the new master data templates in a profile for sales processing, to enable their use there. 

Attributes

Attributes

Contract

Status

Name

Req Sc

Data supply

Value

Nu

Scr

Descript.

Contract

Parameter

Contract

Contract

BUKRS

Constant

U100

CCode

VBEGINN

Not changed

Cont.start

 SAP AG 1999



Attributes are the master data fields that can be maintained in the template (for example, the division of the utility installation, the billing class of the utility installation, or - in the above example - the contract, company code, contract start date, and so on).

Master Data Template (1)

Status

Name

Req Sc

Contract

Data supply

Value

Parameter

Contract

Nu

Scr

Descript. Contract

• Not defined • Constant • Identifying constant • Parameter • Virtual • Key reference • Not changed

 SAP AG 1999

  

 

 

Not defined: The field remains blank Constant: The field should accept a specific constant when the object is created Identifying constant: After you identify the environment determiner, you can create a parameter with category identifying constant in the master data template. This value determines the selection criteria that are used to select from different objects of the same category. If no such parameter is defined, the search is cancelled. Parameter: This field is supplied with data from a set type Virtual: Values for this type of attribute are determined at runtime. This task is performed by a customer-defined function module, which you enter as an attribute value in the master data template. Function modules for virtual attributes must possess a specific interface. Refer to function module ISU_VIRT_ATTR_REGIO_DEMO (demonstration solution: meter reading unit as virtual attribute) as an example for your own solutions. Please refer to the detailed documentation in the coding of this sample solution. Key reference: A higher-level object is referred to Not changed

Master Data Template (2) NewCust

Sales_Partner

Bank

Name

Data supply

Value

Partner

Parameter

SALES_PARTNER

Name

Data supply

Value

House

Parameter

SALES_HAUS

Name

Data supply

Value

Pymt card Address CAccount

ConnObj Sales_Servloc

Address Dev. loc.

DEVLOC Parameter

Devices

HAUS

SALES_DEVL Key reference OC_ Conn. obj. node

Name

Parameter

Value

Premise

Data supply

SALES_VSTELLE_

HAUS

Key reference Conn. obj. node

Premise Installation History Facts Devices Contract Move-in  SAP AG 1999



The master data template allows IS-U master data to be created or changed automatically with the help of the master data generator.

Master Data Template Category

 BCONTACT  BPARTNER  CONNOBJ  DEVICE_LOCATION  INSTALLATION  NEWCUST  PREMISE  RATECHANGE

 SAP AG 1999

         

Master data template categories define the structure of master data templates. The template category determines: Which master data the template can be create (for example, business partner, utility installation, and so on) Which attributes (master data fields) can be maintained in the template (for example, division of utility installation, billing class of utility installation, and so on) The sequence in which the master data is created (for example, the connection object first, then the premise, and so on) Which programs are used for processing Which foreign key relationships exist among the master data (for example, can the premise use the key of the connection object that was created previously?) The two most useful master data template categories are: NEWCUST to create a new customer RATECHANGE to change the rates of an existing installation It usually makes sense to use one of these two template categories to create master data templates. All other independent template categories are contained as sub-nodes in these categories. You can also use one of the other independent template categories to define your master data templates, if they better meet your requirements.

What's Next?

 SAP AG 1999

CRM Integration with 4.63

CRM Integration with 4.63

 SAP AG 1999

System Landscape: CRM, IS-U/CCS, and BW Business Partners: Information Resid. Cust. System

Retention Marketing Product Manage- Analysis &Brand Customer ment Mgmt. Tele DevelopMarketing ment

Service Level Mgmt.

mySAP CRM 3.0

Service Center

Internet Marketing Field Sales

Internet Tele Customer Sales Bus.Part. Service Self Sales Mgmt CollaborService Interaction &Support ation

BW

Center

ex tra of C an RM cto aly rs si dat si

BW

Consumption Entry

Data transfer

s in or sis ion ct a r aly act t n r a ns ex fo tra p

Waste

Charges Taxes / Fees

BW extractors

mySAP BW 3.0

of R/3 master and transaction data for target group selection and other analyses in BW

Fla da tfiles ta su from ch as exte pro rna sp l ec ts

 SAP AG 1999

4.63

Device Management District Heating Water Meters/Devices/Conn Waste Disposal Cable TV ections Service Order Work Service Contract ManagementGoods

ta d ou da an gr M ter get R C as tar BW m r in of o BW ta f ion da lect e s

a n B for W

of selected target groups, top n analyses and other analyses in BW according to CRM

mySAP Utilities

Billing & Invoicing

of business partners, contract accounts, contracts, products and technical master data

Internet Sales

Field Service

Nonresid. Cust. Sales Cust. Service Cust. Prospect Contract Owner Bill Accounting Recipi Installer ent Sectors: Electricity Installation Gas Services Water

Marketing & Sales

Replication via CRM Middleware

External data

mySAP Financials

Overview (1)

CRM Integration with mySAP Utilities 4.63 ... The Future System Landscape ... Integration of the Data Model ... Master Data Generator ... Internet Sales ... Mobile Sales ... Sales Representative

 SAP AG 1999

The Future System Landscape

R/3 CRM

IS-U/CCS IS-U data model

Middleware server

in Pl ug -

BW BW data model for CRM

 SAP AG 1999

B D O C

B D O C

CRM data model

B D O C

CRM data model

CRM business process

Mobile client B D O C

CRM data model

Mobile business process

Integration Approach (1)    

IS-U

ug -in Pl Billing Invoicing Technical objects FI-CA

CRM

Distribution Distribution

IS-U data model

   

Business partner Contracts Technical objects Products B D O C

Middleware server B D O C

CRM data model

B D O C

Direct access (RFC)  Customer environment  IS-U objects for CIC  Transaction calls

Cross-system customer fact sheet  SAP AG 1999

CRM data model

     

Call Center Internet Sales Quotations Campaigns Activities …

Overview (2)

CRM Integration with mySAP Utilities 4.63 ... The Future System Landscape ... Integration of the Data Model ... Master Data Generator ... Internet Sales ... Mobile Sales ... Sales Representative

 SAP AG 1999

Integration Approach (2) IS-U

CRM

B. partner

B. partner

Account Account

Bill Bill

Contract Contract

Contract Contract

Billing Billing

IBASE IBASE

Installation Installation

POD POD

 SAP AG 1999

Premise Premise

Connection Connection object object

BP BP agreement agreement

Replication of Objects in IS-U and CRM IS-U

Middleware

CRM

Business Business partner partner

Business Business partner partner

Contract Contract account account

Business Business partner partner agreement agreement

IS-U IS-U contract contract CRM CRM contract contract Installation Installation

Point Point of of delivery delivery

Premise Premise

Connection Connection object object  SAP AG 1999

IBASE IBASE

System Interaction in the Sales Process CRM

Contract item (contains the CRM product)

Middleware

Replication of contract item

Inbound connector

Interprets the BDOC and determines which master data template is to be used based on the incoming data

Master data generator

A specific OO script is executed, based on the master data template. New data is created and/or existing data changed during this process.

IS-U

Master data is created or changed in IS-U (depending on the selected CRM product); Billing takes place in IS-U.

 SAP AG 1999

Functions Planned in 4.63 (or Later)

 Product availability check at service location  Cross-selling / up-selling based on properties of service location  Field force scheduling / appointments (LRP)  Profitability analysis  Bill inserts as marketing channel

 SAP AG 1999

Overview (3)

CRM Integration with mySAP Utilities 4.63 ... The Future System Landscape ... Integration of the Data Model ... Master Data Generator ... Internet Sales ... Mobile Sales ... Sales Representative

 SAP AG 1999

SAP Internet Sales Function Blocks Web

Shopping basket

Product catalog

Marketing

catalog

Data analyzing

Order & payment

Order

Configuration

Business partner

APO

BW Middleware Middleware

Synchronizing, Synchronizing, mapping, mapping, connectivity connectivity OLTP

Sales Order, Logistics Execution, Financials  SAP AG 1999

Availability

Internet Sales Architecture Business execution

Business service

Internet

Presentation

Publish R/3 back-end

KPRO

CRM System

PM PK

Index server

Publish Browser

Plug-in Plug-

Middleware

ITS

BP

Web server

Browser

Flow

Order

APO

 SAP AG 1999

BW

Browser

IPC

mySAP.com Workplace: Sales Representative

 SAP AG 1999

The Mobile Sales User Interface: Overview Menu bar Standard tool bar

One tile set with three tiles

Navigation bar

 SAP AG 1999

Status bar

Appendix

Contents:  CIC components  HTML templates

 SAP AG 1999

Appendix A: CIC Components: Components

Description

Visible

Hidden

Function

ACTION_BOX

Action Box

X

Calls R/3 transactions (tabstrip presentation)

APPL_AREA

Application Area

X

Display/work area for HTML transations

BD_DISPLAY

Business Data Display

X

Displays business objects and data (visual representation)

CALL_STATE

Call State

X

Provides the state of calls at agent's telephone extension, required for telephony functionality

CCONT

Component Container

X

Holds other visible components (tabstrip presentation)

CSEARCH_DISP

Look-up Functions

X

Provides contact search and display functionality

QUICK_KEYS

Quick Keys

X

Provides pushbuttons for telephony functions

SCRIPT_DISP

Display Script

X

Displays reminder scripting

SOL_SEARCH

Solution Search

X

Search the solutions database

CALLBACK

Call Back Queue

X

Used to create and process callbacks (screens not part of the framework)

CALLCTR

Call Center Component

X

Call center policy component, required for telephony functionality

CIC_TOOLBAR

CIC Application Toolbar/Excls

X

Lists exclusions for the application toolbar and indicates GUI statuses, required

CTI

CTI

X

Provides CTI functionality, required for telephony functionality

HIDDEN SCRPT

Script Text

X

Reminder scripting engine, required for scripting functionality

HLOG

Logging

X

Logs activities

HIDDEN_ABOX

Action Box

X

Supports Action_Box

Appendix B: CIC Configuration You customize the Front Office framework in the IMG.

By creating a CIC profile, you specify what the Front Office includes and looks like for an agent or group of agents. On two screens in the IMG, you indicate the framework ID (which determines the components included in the Front Office screen) and the component profiles for each of these components. The CIC profile enables you to link all of this information to a specific position or an entire level in an organization. Visible Components (Technical Name)

Component Profile(s) Needed (Technical Name)

Profile Name

ACTION_BOX

ACTION_BOX_CONFIGURATION

ACTION BOX COMP CONFIGURATION

CCONT

COMPCONT_PROF

COMPONENT CONTAINER

CSEARCH_DISP

CONTACT_SEARCH_CONFIGURATION

CONTACT SEARCH DISPLAY PROFILE

QUICK_KEYS

QUICK_KEYS_CONFIGURATION

QUICK KEYS BUTTON CONFIG PROF

HIDDEN SCRPT

SCRIPT_PROFILE

SCRIPTING PROFILE

Hidden Components (Technical Name)

Component Profile(s) Needed

Profile Name

CALLBACK

CALLBACK_ASSIGN_QUEUE_PROFILE,

(Technical Name) CALLBACK_CONFIGURATION, CALLBACK_PROCESS_QUEUE_PROFILE

CALLBACK QUEUE ASSIGN PROFILE, CALLBACK COMP CONFIGURATION, CALLBACK QUEUE PROCESS PROFILE

CALLCTR

CALL_CENTER_COMP_CONFIGURATION

CALL CENTER COMPONENT CONFIG

CIC_TOOLBAR

TBAR_PROF

CIC APPLICATION TOOLBAR

CTI

CTIADM_PROF, CTIQA_PROF

CTI ADMINISTRATION PROFILE, CTI QUEUE ASSIGNMENT PROFILE

HLOG

ACTIVITY_LOGGING_PROFILE

ACTIVITY CODES LOGGING PROFILE

A CIC profile links together a framework ID, a set of components, and their profiles. It can be linked to an organizational unit or position in an organizational structure.

Appendix C: Telephony controls and Agent Work Mode The total list of telephony controls and agent work modes provided is: •

Agent Login

Logs the agent into the switch into the specified queue. •

Agent Logout

Logs the agent out of the switch from the specified queue. •

Set Agent Workmode

Ready - Available to receive calls Not Ready - Not available to receive calls Work Ready - Working on previous call, but available to receive calls Work Not Ready - Working on previous call, not available to receive calls. •

Inwait (Wait for Call)

Set the agent’s workmode to Ready and hourglass until a call is delivered. If there is already a call at the extension, do not hourglass—just return immediately. •

Inwait answer

Wait for call, then automatically answer the call.

•

Cancel Inwait

Set the agent’s workmode to Not Ready and unblock any other sessions blocking in Inwait (Wait for Call). •

Answer Call

Answer an alerting call at the extension. If no call is selected by the R/3 application, the CTI server finds the call and answers it.

•

Consultation Call Place the existing call on hold and issue a consultation call to another number. If there is no call at the extension, make an original call from the extension to another number.

•

Reconnect Call After a consultation call, when the original call is still on hold, the agent may want to drop the consultation call and reconnect to the original call. With some switches, the reconnect call operation is the only way to do this.

•

Alternate Call When two calls are at an extension, alternate between the held call and the active call. May not be supported by all CTI servers and switches.

•

Conference Call Conference a held call and an active call together so that all parties can communicate.

•

Blind Transfer Take an active call and unconditionally transfer it to a supplied number. The agent cannot determine whether the call reached its intended destination.

•

Warm Transfer Place the existing call on hold, then place a consultation call to a number supplied by the agent. If the agent successfully reaches the party, the agent may transfer the held party to the consulted party. After the transfer, the agent is dropped from the call.

•

Hold Call Place an active (connected) call at the extension into a held state.

•

Toggle held state Toggle hold/unhold states.

•

Retrieve Call Retrieve a held call at the agent’s extension into the connected state. No other call at the extension may be active—there may only be one active or connected call at any one extension at any one point in time.

•

Deflect Call Deflect an alerting (ringing) call from the agent’s extension to another extension or queue. Some switches do not support this operation.

•

Drop Self Drop the agent’s extension from a conference call. The call is not destroyed; the other parties on the conference call may continue to communicate.

•

Drop Party Drop a specific party (other than yourself) from a conference call. Not all CTI servers support this for all users, as it can be interpreted as a supervisory function.

•

Place outbound call Place call.

•

End Call Destroy a call (disconnect all on-switch parties from a conference call). Some switches/CTI servers only disconnect the agent from the call and do not tear down the existing call; therefore, this operation’s action depends on the switch and CTI server.

•

End call / inwait End a call, go into ready work mode and wait for new call.

•

End call / work / not ready End a call, then go into 'after call' mode (for follow-up work). Not available to take calls.

•

End call / not ready End a call, then go into not ready mode (for other purposes, e.g. lunch break,…).

•

End call / work ready Switch work mode to work-ready, then end call.

•

End call / inwait answer End call, wait for another new call, and automatically answer it.

•

Refresh from call-attached data Refresh onscreen data (Business Data Display) from call-attached data. Must have one or more calls at extension for this to be effective.

•

Refresh callstate Refresh the Call State window manually.

•

Quit call management Leave the application.

Appendix D: SAPphone - CTI Interface In CIC, all soft phone controls of the agent screen and all different work modes and statuses of the agent are communicated through the SAPphone - CTI interface. This interface is a published RFC Interface of R/3. SAPphone currently provides an extensive number of APIs, which are the central gateway between the R/3 system applications (for example, CIC) and the CTI middleware products / telephony servers. The SAP Complementary Software Program is preparing a certification process for the SAPphone RFC interface. A list of available telephony servers will be published by CSP on SAPnet.

Appendix E: Call Center Glossary Action Box – A component with which an agent can perform available business transactions. The business transactions are organized by tabs. The action box pre-fills transactions with information from the business data display. Activity – An action performed by an agent. CIC components flag activities for logging purposes. Agent - A person who handles inbound or outbound calls. synonyms: customer service representative (CSR), telephone service representative (TSR), rep, associate, consultant, customer service professional Agent login – The act of an agent signing onto a queue. Agent logout - The act of an agent signing off from a queue. Agent work mode – The state of an agent in terms of what the agent is doing and whether the agent can accept calls. Automatic Call Distributor (ACD) - The specialized telephone system used in incoming call centers. It is a programmable device that automatically answers calls, queues calls, distributes calls to agents, plays delay announcements to callers, and provides real-time and historical reports on these activities. It may be a stand-alone system, or ACD capability may be built into a CO, network, or PBX. Automatic Number Identification - A telephone network feature that passes in real time the caller’s phone number to the call center Synonyms: Caller ID (US), Calling Line Identification (CLI) (non-US). Blind transfer call – A call that an agent transfers to another agent without first talking to the other agent. Business Data Display – A component that displays business objects such as customers, sales orders, and service notifications that an agent has touched, created, or changed during a call. Call-attached data – Information relating to a call, generally collected through an IVR before the call reaches an agent or added by a previous agent during the call. Callback queue – A grouping of calls to be made by agents at a future point in time. Caller ID - See Automatic Number Identification. Call Center - An umbrella term that generally refers to reservations centers, help desks, information lines, or customer service centers, regardless of how they are organized or what types of transactions they handle. The term is being challenged by many, because calls are just one type of transaction, and the word center doesn’t accurately depict the many multi-site environments. Call state – A component with which an agent can view the telephony state of any party participating in the call.

CIC profile - an outline of information that determines how CIC functions. A CIC profile identifies a framework ID and individual profiles of components in the framework. Component container - A special type of component that increases the number of components the front office can include from six to eleven. It accomplishes this by including up to five components in one tab-strip customizable subscreen.

Component - A major feature in CIC and the functionality behind it. A component can be either visible or hidden. A visible component presents a subscreen, which the CIC framework includes in one of its six subscreen areas or “slots” in the front office. A hidden component provides a feature that has no visible interface.

Conference call – A call that generally connects three or more parties so that every party can speak with every other party. Consultation call – A call in which an agent puts a party on hold and then calls another agent or party. Contact Search and Display – A component that displays information about a caller. CIC can determine this information from ANI and display it automatically when the phone call arrives. Or, the agent can search for the information manually. Computer Telephony Integration (CTI) - The software, hardware, and programming necessary to integrate computers and telephones so they can work together seamlessly and intelligently. Customer Interaction Center - The R/3 application offering call center functionality to customer service organizations. The CIC application enables agents to process inbound and outbound calls and process any business transaction related to a customer. Companies can use CIC in a variety of business scenarios including sales, service, collections, or human resources. Deflect – The act of sending an inbound call to another extension or queue without answering it. Dialed Number Identification Service – A telephone network feature that passes a numeric string to a call processing system to indicate which number the caller dialed. Framework – A program that determines the front office configuration based on the CIC profile and executes all component programs. The framework consists of configuration tables, the front office screen, a default empty subscreen, titles, and component processing functionality. Framework ID – A unique alphanumeric name of up to 15 characters that identifies a list of components. Front office - The main CIC screen from which an agent performs activities and transactions. It can be customized for agent and business needs. Hold – The act of putting a party in a state of waiting. Inbound call - A call received by a call center from an outside party.

Inwait – The mode in which an agent is available to receive calls. Logging – The recording by CIC of call-related activities including activities performed by agents, events occurring in the background, and business transactions. CIC writes the recorded information to logging tables. Outbound call – A call placed by an agent or predictive dialing system to an outside party. Predictive dialing - An external system that automatically places listed outbound calls and delivers answered calls to agents. When the dialer detects a busy signal, an answering machine, or ringing but no answer, it puts the number back in the list. Queue – A list defined in a switch to which calls are placed until an agent becomes available. Quick Keys - A maximum of 12 pushbuttons that act as fast access keys for any function or transaction call of CIC or the R/3 System. Reminder scripting - Scripting that appears when certain activities occur. It provides basic instructions and reminders. Script - Text created in SAPscript for reminder scripting. It can be fully customized and can include variables. Slot – One of the six subscreen areas in the front office. Switch – An electronic device that opens or closes circuits, completes or breaks an electrical path, or selects paths or circuits. Telephony controls – Controls typically available on a telephone that are available in the CIC front office via pushbuttons. Telephony server – Specialized telephony software that acts as a bridge, directly or indirectly depending on configuration, between the R/3 System and a PBX or computer telephony integration (CTI) middleware system. Toolbar - The component that determines the application toolbar CIC uses. Although the application toolbar is visible to the agent, this component is a hidden component, because it does not present a subscreen. Visible component - A component that presents a subscreen, which the CIC framework includes in one of its six subscreen areas in the front office. Warm transfer call – A call in which an agent asks another agent to accept a call before transferring the call.

Appendix F: Acronyms ACD

Automatic Call Distributor

ACW

After Call Work

ANI

Automatic Number Identification

ARU

Audio Response Unit

BRI

Basic Rate Interface

CCR

Customer Controlled Routing

CI

Customer Interaction

CIC

Customer Interaction Center

CPE

Customer Premises Equipment

CS

Customer Service

DN

Dialed Number

DNIS

Dialed Number Identification Service

ISDN

Integrated Services Digital Network

IVR

Interactive Voice Response

IXC

Inter Exchange Carrier

LAN

Local Area Network

LEC

Local Exchange Carrier

PABX

Private Automatic Branch Exchange

PBX

Private Branch Exchange

PRI

Primary Rate Interface

PSN

Public Switched Network

TAPI

Telephony Applications Programming Interface

TSAPI

Telephony Services Application Programming Interface

VRU

Voice Response Unit

LO840 Appendix: Workflow Topic: Creating a Workflow Task This supplement to the LO840 course describes how you can: •

Create a standard Workflow task that is triggered when a defined transaction is executed from the CIC Action Box for a specific customer.

•

Assign the Workflow task to a user within your organization.

Within your organization, each time a sales order is created by the call center agent for a specific customer, it must be approved by a supervisor. Create a Workflow task that is triggered each time the call center agent creates a sales order for this customer, and assign the task to the appropriate supervisor.

Procedure Overview 1.

Define Standard Task - Task type - BOR object type - Method - Triggering event - Activate event linkage

2.

(TS, T, WS, WF, TG) (Business object involved) (What we want the recipient to do) (What triggers the Workflow task)

Define Standard Role - Role type - Container definition - Responsibility definition

(Determines who will process the task) (Responsibility) (Element, table, field) (Specific customer(s) for whom WF is to be triggered)

3.

Assign Default Role to Task - Defining who is responsible for processing the WF task

4.

Assign Standard Task/Responsibility to Agent/Position - Assigning standard tasks to a position or user from within the organizational structure Reference Information Business Object Repository:

SWO1

Common Business Object Types: Customer contract BUS2034

Customer inquiry

BUS2030

Customer quotation

BUS2031

Maintenance notification

BUS2038

Maintenance order

BUS2007

Sales order

BUS2080

Service order

Service notification

BUS2032 BUS2088

Procedure 1.

Define Task

Choose Tools  Business Workflow  Development, and then Definition tools  Tasks/Task groups  Create. Enter task type TS (Standard task) and then choose Create. Complete the following information: Name Abbreviation:

CIC-WF-##

Name:

Verify Sales Order

Object Method BOR object type: BUS2032 (Sales order) Method:

EDIT

Confirm the message “Transfer missing elements from the object method” with Yes. Work item text:

(The text that should appear in the Workflow recipient’s inbox)

Note: Choose the icon Insert variables to display possible variables that you can include in the Work item text. For example, “Please verify sales order &_WI_OBJECT_ID.SALESDOCUMENT&”. Choose the icon Container and check that the sales order is in the list of container elements displayed. Triggering Event Choose the icon Insert event. Enter the following data: Object type:

Sales order = BUS2032

Event:

CREATED

Note: At this stage, event linkage icon is inactive (Red).To activate event linkage, select event and then choose Edit  Event  Activate/deactivate event linkage, or click on the event linkage icon. A terminating event is not required.

Set the type of task Goto Agent Assignment and select Attributes Set the task as a General Task Green arrow back and save 2.

Define Standard Role Choose Definition Tools  Standard roles  Create. Choose the icon Create.

Abbreviation: Name: Role type:

CIC-WF-## Verification responsibility Responsibility

Save the role. The pushbuttons Container definition and Responsibilities are now displayed. Choose the pushbutton Container definition and then the icon Create. Confirm the message “Create with ABAP Dictionary field proposals?” with Yes. Enter table VBAK. The field attributes are displayed. Select the field name KUNNR (Element = SoldToParty) and create the required element. Save the container. To define the responsibilities in the role (for example, for which customer(s) the verification is to be performed), choose the pushbutton Responsibilities and then the icon Create. Enter the name of the responsibility (Verification for Customer ####) and the required validity dates. For example, enter Sold-to party from 3000 to 3000 (WF is therefore only triggered for this customer). Note: Once you save, the responsibility is displayed as being complete. 3.

Assign Default Role to Task

Call up the standard task you created in the change mode. Choose the tabstrip Default roles. In the column Standard role, enter the standard role (responsibility) that you created for the agent. Save the assignment of the responsibility to the agent. Call up the standard role in the change mode. In the screen Change Responsibility, select the responsibility you created and choose the icon Assign agent. To assign the responsibility to a specific agent, choose the agent type User and enter the name of the required agent within your organizational structure. To assign the responsibility to a group of agents, choose the agent type Position and select the required position (Agent ##). In the dialog box that is displayed, choose the icon Create. 4.

Assign Standard Task/Responsibility to Agent/Position

It is also possible to assign standard Workflow tasks and responsibilities to agents or positions from within the PDORG. Choose Logistics  Service management  Customer interaction center, and then Administration  CIC structure  Organizational structure  Change Enter the required organizational structure and then choose Change. Choose pushbutton Staff assignments to display agents within the organization. Select the required agent/position and then choose the pushbutton Task profile. To assign a standard task to the agent/position, choose the pushbutton Assign task and select the task (CIC-WF-##) that you created. Save the task assignment. To assign a responsibility to the agent/position, choose the pushbutton Assign responsibility and select the responsibility (CIC-WF-##) that you created. Save the responsibility assignment. Choose Edit  Refresh to refresh the organization environment. Test the Workflow task by creating and saving a sales order for customer ####. Check the agent's Office inbox for the workflow item that should

Appendix: HTML Templates Table of Contents: HTML Templates * Configuring the Services * Configuration with the Object Navigator (SE80) * Configuration with the SAP@Web Studio (optional) * Creating Your Own HTML Templates * Structuring the URL * Structuring the Templates * Debugging Functions * ewhv_functions * Sample Templates * SAPLEWHV_EXAPMLE1.html * SAPLEWHV_EXAPMLE2.html *

HTML Templates In the CIC (L-shaped framework), the customer information is displayed in an HTML template by default. To use this template, you first have to configure a service as described in section . You also have the option of defining your own layouts in separate HTML templates. To do this, proceed as described in section .

Prerequisites In order to use the HTML-based customer information, the following services must exist on the ITS: EWHV (templates for the layout) ISU_GLOBAL (HTMLBusiness functions for reading the node data: ewhv_functions.html; debugging functions: ewhv_debug.html and ewhv_debugfunctions.html) ITS system libraries To ensure that the HTML customer overview is displayed correctly, you should use the latest version of the ITS (4.6C) and the current HTML library. IS-U version 4.6B included templates whose layout was modified to suit the limited options available in this release. However, you can (and should) always use the latest versions with your R/3 IS-U system.

Configuring the Services In Release 4.61, you have to publish the services on your ITS with the SAP@Web Studio This means the necessary files have to be copied to the appropriate locations on the ITS server. Note You can also publish the services directly from the Object Navigator (transaction SE80) starting in Release 4.62.

Configuring with the Object Navigator (SE80) Make sure you meet the prerequisites: Check the Utilities/Settings… in the ITS tab page to make sure the correct Web server and targets for publishing have been configured. Then proceed as follows: Choose the Internet Service category in the object list selection Enter the names of the services to be created: EWHV and ISU_GLOBAL. Click on the required service with the right mouse button. Choose Publish? Complete service from the context menu. Should errors occur at any time during the publishing process, a log with the corresponding message texts is output. If no errors occur, the message The object was published is displayed in the status bar. Also be sure to read the online documentation for SE80. To do this, choose function Help → Application Help → Integration of Internet Services in SE80 from within the Object Navigator.

Configuration with the SAP@Web Studio (optional) Procedure: Check under Project/Site Definition to make sure you are connected with the R/3 System. Please use the online help if you have any difficulties configuring the site definition.

Figure 1: Example of How You Can Define the Web Server or ITS Host in the Web Studio Configure a new ITS project: EWHV or ISU_GLOBAL. Connect to the R/3 System: Tools/Source Control/Connect to R/3 Click on the corresponding service with the right mouse button and choose Get from the context menu. Choose All files and click on OK. Choose the File View tab from the object selection list, click the service folder with the right mouse button, and choose Publish from the context menu.

Creating Your Own HTML Templates You can define your own HTML template to create your own customized view of the IS-U data. To use your own HTML templates, you have to create a new template on the ITS that conforms to the EWHV naming conventions – that is, it must be called .html. You can create this template in the SAP@Web-Studio or in transaction SE80. Note

You can also use NT tools to edit the template in the ITS file system – in this case, pay particular attention to the naming conventions. Note If you use the SAP@Web-Studio under 4.61, you do not have to check this template into the R/3 System, as it is only used from the ITS. If you try to check the template into the R/3 System anyway, an error message will be displayed because the name does not correspond to the standard R/3 naming conventions1. Should it be necessary to check in a template anyway, please rename it accordingly beforehand (naming conventions: starts with “Z” instead of “SAP”. Do not publish the template under this name (starting with “Z”) on the ITS, however, because the service only detects templates that meet the naming convention SAPLEWHV_.html.

Structure of the URL The URL that you can use to access the HTML-based customer information function (among others) with a browser outside the SAP system has the following structure:

http:////!? ~okcode=+&view=&objkey=&classid=isupartner The placeholders indicated with have to be replaced as follows:

The URL of the ITS at your company, such as ITS1.MyCompany.com



scrips/wgate/ewhv



Name of the HTML data selection, such as PARTNER



Number of the business partner (with leading numbers for strictly numeric partner numbers), such as 0000004711

You can also append “&debug=1” or “&debug=2” to the URL if you want to use the debugging options described in section . We recommend using the debugging functions if you want to create your own templates, as it will give you an overview of the objects and fields that can be displayed.

Structure of the Templates The main template for the HTML-based customer information function is saplewhv_100.html. This template is used to load the libraries used, provide the debugging functions, and dynamically integrate the HTML template for the layout(VIEWNAME.html).

Debugging Functions The templates of the HTML-based customer information function provide two debugging modes for your use. These modes are activated with parameters “debug=1” and “debug=2”, which can be specified in the URL. Mode 1 shows an overview of the displayed objects with their (hierarchical) dependency and the names of the object types and classes; mode 2 displays an overview of the objects and the transported field attributes (contents). An example of a URL that activates debugging mode 2 appears below:

1

The naming conventions will be synchronized in the next release.

http://pwkk4.wdf.sap-ag.de:1080/scripts/wgate/ewhv/!? view=account&classid=isupartner&objkey=0000004171&~okcode=+&debug=2 The debugging functions are also available for templates that you define yourself. They must however satisfy the naming conventions described in section 0.

ewhv_functions To address the data in the templates, a number of special HTMLBusiness functions are supplied in file ewhv_funktions.html in service ISU_GLOBAL. If you want to write your own templates, we recommend familiarizing yourself with the general HTMLBusiness functions.

Function

Description

object = root()

Returns the object that starts the cluster builder. This is “Business partner” for the HTML-based customer information function. Example: `partner = root();`

value = attrib(obj, attr)

Returns the value of attribute “attr” of object “obj”. Example: `value=attrib(partner,"DESCRIPTION")`

object = child( obj, ind )

Returns the sub-object with index “ind” for an object “obj”. Example: child1 = child(partner, 1)

num = child_dim( obj )

Returns the number of sub-objects “num” for an object “obj”. Example: num = child_dim(partner)

object = childoftype( obj, typeid, ind )

Returns the sub-object “object” with type “typeid” and index “ind” for an object “obj”.

num = childoftype_dim(obj, typeid )

Returns the number of sub-objects “num” of type “typeid” for an object “obj”.

object = father( obj )

Returns the parent object of object “obj”.

id = typeid( obj )

Returns the type ID “typeid” of an object “obj”.

clsid = classid( obj )

Returns the class ID “clsid” of an object “obj”.

cls = class( obj )

Returns the class “cls” of an object “obj”.

Example: acct = childoftype(partner, "ACCOUNT", 1)

object = ObjectOfClass( clsid, ind Returns the object with the index “ind” of a class “clsid”. ) num = ObjectOfClass_Dim( clsid )

Returns the number of objects in a class

name = attrib_name( cls, ind )

Returns the name of the attribute with the index “ind” of a class “cls”. (Only works when the meta info parameter is set.)

text = attrib_text( cls, ind )

Returns the text of an attribute with the index “ind” of a class “cls”. (Only works when the meta info parameter is set.)

num = attrib_dim( cls )

Returns the number of attributes in a class “cls”. (Only works when the meta info parameter is set.)

key_atr =class_key( cls, ind )

Returns the key attributes with the index “ind” of a class “cls”. (Only works when the meta info parameter is set.)

num = class_key_dim( cls )

Returns the number of key attributes in a class “cls”. (Only works when the meta info parameter is set.)

An example HTML template appears below. This template is intended to illustrate how you can address the objects and their data. This template is supplied as SAPLEWHV_EXAMPLE1.html with service EWHV. Alternatively, you can enter it manually as described below. HTML data selection EXAMPLE1 must be present in the IMG. Make sure that the structure selection “First by contract account, then by premise” is specified and that the display has been activated for the business partner and the contract account. Please do not select any fields from the presentations of the business partner or contract account, to make sure that all the fields will be available for display.

Example Templates SAPLEWHV_EXAPMLE1.html `include (~service="isu_global", ~language="", ~theme="99", ~name="ewhv_functions.html");` `partner = root();` Name: `attrib(partner,"DESCRIPTION")` Street: `attrib(partner,"STREET")` Partner `attrib(partner,"NAME1")` has class `class(partner)` and classid `classid( partner )`. Object partner has `child_dim( partner )` child object(s). `acct = childoftype(partner, "ACCOUNT", 1)` `repeat with id from 1 to childoftype_dim(partner, "ACCOUNT")` `acct = childoftype(partner, "ACCOUNT", id)` `typeid(acct)`: `attrib(acct,"VKONT")` `end`

SAPLEWHV_EXAPMLE2.html The above example has been extended below in order to illustrate the HTMLBusiness layout functions. The documentation of these functions can be found in SAPNet: http://mysap.wdf.sap-ag.de:2080/ - SAP Business HTML Cookbook. `include (~service="system", ~language="", ~theme="dm", ~name="templateLibrarydhtml.html");` `include (~service="isu_global", ~language="", ~theme="99", ~name="ewhv_functions.html");` `SAP_TemplateGroupboxBegin(groupBoxLabel="Data Box", width="600")` `partner = root();` Name: `attrib(partner,"DESCRIPTION")` Street: `attrib(partner,"STREET")` Partner `attrib(partner,"NAME1")` has class `class(partner)` and classid `classid( partner )`.

Object partner has `child_dim( partner )` child object(s). `acct = childoftype(partner, "ACCOUNT", 1)` `SAP_TemplateTableBegin(title="Accounts");` `SAP_TemplateTableRowBegin();` `SAP_TemplateTableCellBegin(subtype="TEXT")` TypeID `SAP_TemplateTableCellEnd();` `SAP_TemplateTableCellBegin(subtype="TEXT")` Account # `SAP_TemplateTableCellEnd();` `SAP_TemplateTableRowEnd();` `repeat with id from 1 to childoftype_dim(partner, "ACCOUNT")`

`acct = childoftype(partner, "ACCOUNT", id)` `SAP_TemplateTableRowBegin(); SAP_TemplateTableCellBegin(subtype="NONEDIT1"); typeid(acct); SAP_TemplateTableCellEnd(); SAP_TemplateTableCellBegin(subtype="NONEDIT1"); attrib(acct,"VKONT"); SAP_TemplateTableCellEnd(); SAP_TemplateTableRowEnd();` `end` `SAP_TemplateTableEnd()` `SAP_TemplateGroupboxEnd()`