Configuration Uces 604 e

Configuration of UtilityCustomer E-Services

SAP ERP 6.0Enhancement Package 4

SAP Online Help 21.07.2009

Configuration of E-Services 2009 2

Copyright

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM,z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower,PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBMCorporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license fortechnology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, andother SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks ofBusiness Objects S.A. in the United States and in other countries. Business Objects is anSAP company.

All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.

These materials are subject to change without notice. These materials are provided by SAPAG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and



services are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.



Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,and menu options.

Cross-references to other documentation.Example text Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



Configuration of E-Services ...................................................................................................6

General Notes on Configuration.........................................................................................7

Authorizations for Controlling IS-U Functions in Front-End Syst..........................................9

Inclusion of SAP Utility Customer E-Services in a Portal................................................... 10

Detailed Documentation................................................................................................... 11

Services .......................................................................................................................... 12

Display Contract Overview............................................................................................... 13

Move-In ........................................................................................................................... 14

Entering Meter Readings ................................................................................................. 16

Interim Billing................................................................................................................... 19

Comparing Rates............................................................................................................. 20

Adjust Budget Billing Plan................................................................................................ 21

Adjust Payment Plan........................................................................................................ 22

Display Contract Overview............................................................................................... 23

Move-Out......................................................................................................................... 24

Move-In/Out..................................................................................................................... 26

Additional Parameters...................................................................................................... 27

Configuration of the Web Interface................................................................................... 30

Example Resource File RATEDATA ................................................................................ 33



Configuration of E-ServicesThe following provides information on the configuration of the SAP IS-U back-end systemand the Web application. To use SAP Utility Customer E-Services, you must make thesettings described below in the implementation guide for SAP for Utilities (SAP IS-U) and inthe master data for the Web application.

For detailed information on the individual Customizing settings to be made, see thedocumentation for the IMG activity, and the field help. At the same time as making settings inSAP IS-U, you must also make the settings for the individual functions in the Web application.Ensure that the settings for the functions, which you make in both the SAP IS-Uimplementation guide and the configuration file for the Web application, are compatible andread the notes in the documentation for the individual settings.

You can find more information on configuration in Customizing for SAP Utilities underCustomer Services Utility Customer E-Services (UCES).

Extended Configuration Management (XCM) is used to configure SAP Customer E-Services.This tool allows you to use a user interface to make all the settings required for theconfiguration of SAP Utility Customer E-Services, and to manage various different scenarios.For more detailed information about XCM, see the configuration guide for Biller Direct. As wellas the configuration in XCM, you can also make additional, optional settings in the Internetbrowser and in the WEB-INF/web.xml file.

Before you can work with SAP Utility Customer E-Services, use the XCM to carry out theconfiguration. To call the XCM, enter the path[protocol]://[server]:[port]/[UCES-context-root]/admin/xcm/init.do in your browser. bdisu is preset as [UCES-context-root].

The following section describes the individual, specific E-services for the utilities industry, andthe necessary settings for these services. The parameters referred to in this section areexplained in greater detail in section Parameters for the Extended Configuration Management(XCM) Configuration File of the Configuration of the Web Interface [Seite 30] documentation.



General Notes on ConfigurationSAP Utility Customer E-Services allows your customers to use the Internet to enter meterreadings and messages for move-in, move-out, and move-in/out. Customers can also displayan overview of their contracts and change their budget billing plan.

Your customers do not need to install SAP software to use SAP Utility Customer E-Services.All of the functions can be executed using a standard Web browser. For information onsystem requirements and the browsers supported by SAP Utility Customer E-Services, seethe introductory units of the Installation Guide for SAP Utility Customer E-Services, which youcan find on the SAP Utility Customer E-Services CD in the /DOCUMENTATION directory.

SAP Utility Customer E-Services 6.04 contains SAP Biller Direct version 6.04.The use of the SAP Biller Direct functions is optional.

Components for SAP Biller Direct

SAP ERP 6.0EnhancementPackage 4

FI-CA Industries release 6.04for the following solutions:

SAP for Utilities

SAP Contract AccountsReceivable and Payable

SAP NetWeaver7.0 with UsageType AS-JAVA asa component ofSAP ERP 6.0EnhancementPackage 4

SAP Biller Direct6.04 (Java frontend)

If you also want to use the functions of the SAP Biller Direct application, see the SAP BillerDirect configuration guide, which you can find on SAP Service Marketplace athttp://service.sap.com/erp-financials SAP Financial Supply Chain Management SAPBiller Direct Media Library Document. If you do not want to use the SAP Biller Directfunctions, you need only read the following sections in the configuration guide for SAP BillerDirect. Sections within units are indented. If no section is specified, then all the sections in theunit mentioned are relevant:

Documentation Landscape for SAP Solutions and Business Scenarios

SAP Notes

User Management

Configuration of the Web Application

Configuration of the Web Application with XCM

Configure Scenario

Define Data for User Management

Configure JCO RFC Server

Servlet-Parameter

Parameters of the Calling HTTP Request

Configuration and Data Security



Making Settings in the Internet Browser

Connection Between the Web Application and FI-CA

GRMG Heartbeat Monitoring

When reading the aforementioned units, note that for the configuration of SAPUtility Customer E-Services you only require those descriptions in the SAP BillerDirect configuration guide, which belong to the versions for Contract AccountsReceivable and Payable (FI-CA), SAP for Utilities, and FI_Usermanagement.Instead of [billerdirect-context-root] use [UCEScontext-root]. This is preset withthe value bdisu. Use the standard mode as the user mode.

For notes on guaranteeing secure data transfer, see the Introduction unit of the SAP BillerDirect installation guide, in the section Notes for the Implementation.

Ensure that the corrections described in SAP note 870250 have been imported.



Authorizations for Controlling IS-U Functions inFront-End Syst.To use the IS-U functions, you have to assign the necessary authorizations to the referenceuser (UCES_REF).

Use the PFCG transaction to create a new role. Choose the Authorizations tab page. Enter aname in the Profile Name field or have the system propose a name for the profile.

Under Maintain Authorization Data and Generate Profiles, choose the Change AuthorizationData pushbutton. Now add the authorization object E_ISUEBPP manually and then choosethe key values.

Generate the profile and save the role. To do so, enter the following key values in the tableISU_EBP_TFKAUTHT:

MC03

MI03

MO03

MR03

SA03

SL03

SS03

Allocate the new profile to the reference user.

Subsequent Changes to the Authorization at Runtime:Depending on the user (business partner), you can change the chosen authorizations atruntime. To do this, you have to implement the BAdI method in Customizing under SAPUtilities Customer Service Utility Customer E-Services (UCES) BAdI: Define GeneralMethods for UCES.

The BAdI contains method AUTH_CHANGE_LIST. You can filter the authorization againhere.



Inclusion of SAP Utility Customer E-Services in aPortalThe following table shows the URL addresses to be used to call SAP Utility Customer E-Services functions directly:

Function URL Address

Mete reading entry startEBPP.sap?nextpage=meterPrepare

Move-in startEBPP.sap?nextpage=moveInPrepare

Move-out startEBPP.sap?nextpage=moveOutPrepare

Move-in/out startEBPP.sap?nextpage=moveInOutPrepare

Log off startEBPP.sap?nextpage=logout

Adjust budget billing plan startEBPP.sap?nextpage=abbpPrepare

Display contract overview startEBPP.sap?nextpage=ContractPrepare

For more information, see the Integration of SAP Biller Direct in a Portal unit in the SAP BillerDirect configuration guide.



Detailed DocumentationTo enhance or modify the functions, you require the documentation for the function modulesused. All function modules used for the services are found in the BDISU function group (theyare allocated to the relative BOR object in the WEBINF/xml/function-mapping.xml file (onlyBUS1006)). You can find the additional documentation for the individual function modules inthis function group.



ServicesThe following provides information on the configuration of the SAP IS-U back-end systemand the Web application. To use SAP Utility Customer E-Services, you must make thesettings described below in the implementation guide for SAP for Utilities (SAP IS-U) and inthe master data for the Web application.

For detailed information on the individual Customizing settings to be made, see thedocumentation for the IMG activity, and the field help. At the same time as making settings inSAP IS-U, you must also make the settings for the individual functions in the Web application.Ensure that the settings for the functions, which you make in both the SAP IS-Uimplementation guide and the configuration file for the Web application, are compatible andread the notes in the documentation for the individual settings.

You can find more information on configuration in Customizing for SAP Utilities underCustomer Services Utility Customer E-Services (UCES).

Extended Configuration Management (XCM) is used to configure SAP Customer E-Services.This tool allows you to use a user interface to make all the settings required for theconfiguration of SAP Utility Customer E-Services, and to manage various different scenarios.

You can find detailed information on the XCM underhttp://service.sap.com/crm-inst andhttp://service.sap.com/crm Documentation and Education SAP CRM4.0 (incl. Edition 2004) Installation & Upgrade Guides Guides Web ApplicationInstallation Guide - SP03-SP05. As well as the configuration in XCM, you can also makeadditional, optional settings in the Internet browser and in the WEB-INF/web.xml file.

Before you can work with SAP Utility Customer E-Services, use the XCM to carry out theconfiguration. To call the XCM, enter the path[protocol]://[server]:[port]/[UCES-context-root]/admin/xcm/init.do in your browser. bdisu is preset as [UCES-context-root].

The following unit describes the individual, specific E-services for the utilities industry, and thenecessary settings for these services. The parameters referred to in this unit are explained ingreater detail in unit Parameters for the Extended Configuration Management (XCM)Configuration File.



Display Contract OverviewYou make the settings for the contract overview in Customizing for SAP Utilities underCustomer Service Utility Customer E-Services (UCES) Service: Display ContractOverview.



Move-InThe following two scenarios are possible:...

1. The user is already a customer of the utility company, and has a user and password.

2. The user is a new customer.

In the first case, the customer logs on using his/her user and password. In the second case,the customer uses a link, which executes the logon using a “dummy user” (parameterdummyUserMoveIn). In this case, the system only provides the move-in service for thecustomer.

Identification of PremiseThe system uses the postal code and a device number to determine the premise, into whichthe customer wants to move. This takes into account the possibility that the customerinadvertently entered the material number of the device. If more than one device exists withthe same number, in the same location, then additional input fields (location, street, housenumber) are displayed, until the system has uniquely identified the premise.

If the system cannot identify the premise, it attempts to use the postal code to determine theaddress, and checks whether it is actually in the service territory of the energy supplier. Forthis reason, the exact maintenance of the regional structure in the IS-U system is afundamental prerequisite. In addition, you must also specify the country in which the serviceterritory is located (parameter countrySupplyArea).

You can use the parameters daysPast and daysFuture to define how far in the past and inthe future the move-in date can be.

Confirmation of PremiseOnce the system has correctly determined the premise, the data is not yet ready for input,and must first be confirmed. If the system has determined the wrong premise, the customercan navigate backwards at any time. If the system cannot determine a unique premise, the E-service can be continued, but with restrictions. In this case, the customer must enter theaddress data manually. A check is also carried out on the regional structure in SAP IS-U. Ifthe address is located outside the service territory, the system informs the customer.

Personal DataIf the customer is already recognized, the system displays his/her personal data as not beingready for input. If it is a new customer, he/she must enter his/her data here.

Bill AddressThe customer can specify an alternative bill address. The fields are prepopulated with thecustomer address data, and can be overwritten.

Rate SelectionThe system uses the premise to determine the existing installations, along with devices andthe corresponding division. Depending on the register group, the utility company can offer thecustomer various rates. These must be defined in the fileWEBINF/lib/com/sap/fin/isu/resources/ratedata.properties.The appendix contains an example of this file, and a detailed description of how to maintain it.

Meter Reading Entry (for Move-In Dates that Are Not in theFuture)In this case, the entry date for the meter reading results is the move-in date. It cannot bechanged. The specification of meter readings is optional.



If the system was previously unable to identify the premise, the devices are not recognized.For this reason, the system displays an entry screen with an input field for a gas meter, awater meter, and a single-rate and dual-rate electricity meter. The customer can enter a meterreading for his/her meters here. This meter reading is then transferred to the notes field inSAP IS-U, in the parked document (transaction Accelerated Move-In / Move-Out / Move-In/Out Entry; EC70).

Selection of Payment MethodThe following three payment methods are possible:

Automatic debit

Bank transfer

Check

You must specify the relevant IS-U abbreviations for the payment methods (IS-U tableTFK042Z, transaction FQP1) in the parameters:

Parameter tokenAutomaticDebitfor automatic debit

Parameter tokenBankTransferfor bank transfer

Parameter tokenCheckfor check

In automatic debit, the customer can refer to bank data that has already been maintained, orspecify new bank details. The bank number is compared with the values stored in the IS-Utable BNKA.

Data for Owner and Previous Owner/TenantThese entries are optional and are, if necessary, transferred to the notes field in the parkeddocument in SAP IS-U (transaction Accelerated Move-In / Move-Out / Move-In/Out Entry;EC70).

Data Check ScreenBefore executing the data transfer, the system lists all the data entered. If the customerrecognizes an error, he/she can navigate backwards. Otherwise, he/she can trigger the datatransfer.

Screen Following Successful Data TransferAfter a successful data transfer, the system issues a message. The system lists all theentered data again. The customer can also print this list. If the customer has specified an E-mail address in his/her master data, the system creates a PDF form with the meter readingresults when the customer saves, and sends this form to the E-mail address. The system nowasks the customer to generate a form. The customer can then print this form, and send asigned copy to the utility company. The system stores the data entered in a parked documentin SAP IS-U (transaction Accelerated Move-In / Move-Out / Move-In/Out Entry: Access;EC70). You must use the parkedDocumentVariant parameter to specify the parkeddocument variants to be used. After releasing this document, the system calls the master datagenerator, which then creates the corresponding permanent data construct in SAP IS-U.



Entering Meter ReadingsEntry ScreenThe entry screen displays the meter readings of devices for all the premises belonging to acustomer. If entries without a meter reading order are to be displayed as not being ready forinput, and in grey (IS-U table TE410, field TREAT_INTERNETMR), make the appropriatesettings in the implementation guide for SAP for Utilities, under Device Management MeterReading Basic Settings Define Control Parameters for Meter Reading Data Processing.If entries are only to be ready for input if they have an existing meter reading order, thecurrent date must lie within the “Scheduled Meter Reading Date +/- Interval” (IS-U tableTE410, field INTV_INTERNET).

If the table contains a lot of lines (parameter startFilter), a filter is shown, which allows you torestrict the display to Premise Address, Division and/or Meter Reading Order Exists/Does NotExist. The corresponding restriction criterion is only displayed if different values exist. Whenentering meter readings, the customer can only enter as many predecimal and decimal placesas the device actually has. For devices with several meters, the customer must enter either allthe meter readings for a meter reading date, or none at all. The meter reading date must notlie before the previous meter reading date or in the future. After entry, the system carries outa validation for the meter reading results. In the case of implausible entries, the agent mustuse a dropdown box to select a remark. If several results are implausible, the systemspecifies the previously selected remark. IS-U table TE259 contains the remarks displayed.To activate the remarks for display, set the indicator Customer E-Service (CES) in theimplementation guide for SAP Utilities, under Device Management Meter Reading MeterReading Result Entry Define Notes from Meter Reader. At this point, you can define thefollow-up action for each remark.

Data Check ScreenBefore the data is transferred, all meter reading results that were entered are listed, alongwith their remarks. If the customer recognizes an error, he/she can return to the entry screen.Otherwise, he/she can trigger the data transfer.

Screen Following Successful Data TransferAfter a successful data transfer, the system issues a message. The system again lists all theentered meter reading results and, if applicable, their remarks. The customer can print thislist. If the customer has specified an E-mail address in his/her master data, the systemcreates a PDF form with the meter reading results when the customer saves, and sends thisform to the E-mail address.

Enter Meter Reading AnonymouslyThe Enter Meter Reading Anonymously service allows utility customers to enter their meterreadings without having to own an online account. Instead of logging on with a user name andpassword, customers can log on with a dummy user in the e-services.

Identification of the Business PartnerOn this screen, you identify the business partner for anonymous meter reading entry. On thestandard screen, you enter the business partner number and the device number. The systemchecks whether the data is correct and, if necessary, generates an error message.

This screen is structured in such a way that you can make the enhancements described herein your own projects. The additional input fields are already on the JSPcontent_meterreading_identify_html.jsp. You simply have to unhidethem by moving the relevant comment spaces:



The business partner number can be replaced by the contract account number or bythe contract number. The necessary functions have already been fully implemented.However, you cannot remove the input field for the device number from the screen.

You can also add the following input fields to check the data against the backendsystem. The necessary functions have already been implemented in Java – this meansthat all the data is sent to the backend system. In the backend system, you also haveto implement the function for checking the data in method mtr_change_meteridentify ofBAdIs ISU_UCES_METERREAD:

Business partner details

First name

Last name

E-Mail

Telephone

Date of birth

Business partner address details

Street

House number

House number supplement

Postal code

City

Region

Country

Premise address details

Street

House number

House number supplement

Postal code

City

Region

Country

Floor

Room

Location details

The screens that follow are the same as for meter reading entry. In Customizing tableUCES_CUST_MTR, you have to define in the METER field whether the user can enter meterreadings anonymously for one device only (value=2), for all devices assigned to a premise(value=1), or for all devices assigned to a business partner (value=0).



Interim BillingTo use the Interim Billing e-service, create a simulation scenario belonging to category 9(Simulate Period of Interim Billing) in Customizing for SAP Utilities under Contract BillingBilling Execution Define Simulation Scenarios, and enter value 002 in the ScE (SimulationScenario from External Call) field. Do not select any other fields.

Executing the Interim Billing E-ServiceYou have to enter a meter reading for the same date for all devices. UCES_CUST_IB-MAX_DAYS_PAST_MR defines how far in the past (from the current date) this date can lie.

An interim billing order is then generated in the system for the specified date. Billing andinvoicing are simulated for this interim billing order and the system displays the result. Inaddition to displaying an overview of the amounts, you can also display the bill as a PDF file.

With the following prerequisites, you can request an actual interim billing from the e-service:

Interim billing is permitted in the Customizing settings (UCES_CUST_IB-INTER_BILL_PERM).

The meter reading results you entered are plausible.

There are no open billing orders before the interim billing date.

There are no open invoicing orders.



Comparing RatesTo use the Rate Comparison e-service, create a simulation scenario belonging to category 2(Simulate Orders for One Year with Rate Category Comparison) in Customizing for SAPUtilities under Contract Billing Billing Execution Define Simulation Scenarios, and entervalue 001 in the ScE (Simulation Scenario from External Call) field. Also set the GrossLne(Gross Lines for Billing Simulation) indicator.

Under Alternative Rate Categories for Simulation, you can define a set of rate categories thatcan be simulated. Under the Alternative Rate Categories for an Application subnode, you candefine which of the rate categories are actually simulated in the Rate Comparison e-service.

In Customizing for SAP Utilities under Customer Service Utility Customer E-Services(UCES) Service - Bill Simulation / Interim Bill Define Text for Rate Category, you candefine a text for each rate category displayed in the simulation results. If you do not enter atext here, the system displays the short text of the rate category.

In Customizing for SAP Utilities under Customer Service Utility Customer E-Services(UCES) Service – Bill Simulation / Interim Bill Service Bill Simulation: Define PossibleRate Category Change for Service, you can define which rate category changes are possiblein the e-service. Under New Rate Categories, you can only specify rate categories that do notrequire the installation structure to be replaced.

Executing the Rate Comparison E-ServiceYou can either enter a meter reading for all devices or you can enter the annual periodconsumption. The period consumption is used to estimate meter reading results for all billingdates in a year for which no meter reading results are yet available. Existing meter readingresults remain unchanged.

As standard, the billing orders for a year are simulated if TERMTDAT of the schedule recordfor the portion lies within the year (Jan 1 to Dec 31) that is determined using the followingdata:

Start of billing period if no billing document exists yet for the contract or if the last billingdocument belongs to an interim bill.

ERCH-PTERMTDAT from the last billing document

For all existing schedule records with TERMTDAT in the period January 1 – December 31ofthis year, the internal billing orders are generated and simulated. Existing billing documentsfor the year are reversed internally and billed again. If all the schedule records for the yearhave not yet been generated, the system simulates a smaller period corresponding to theavailable records.

You have the option to change the simulation period in method ADJUST_SIM_PERIOD ofBAdI BADI_UCES_IB. Then all schedule records with TERMTDAT in the specified period aresimulated.



Adjust Budget Billing PlanYou make the settings for the Budget Billing Plan Adjustment service in Customizing for SAPUtilities under Customer Service Utility Customer E-Services (UCES) Service: BudgetBilling Plan Adjustment.



Adjust Payment PlanYou make the settings for the Payment Plan Adjustment service in Customizing for SAPUtilities under Customer Service Utility Customer E-Services (UCES) Service: PaymentPlan Adjustment.



Display Contract OverviewYou make the settings for the contract overview in Customizing for SAP Utilities underCustomer Service Utility Customer E-Services (UCES) Service: Display ContractOverview.



Move-OutSelection of PremiseThe system displays all existing premises for a business partner. After selecting the premiseand entering a move-out date, the customer is taken to the meter reading entry. You can usethe parameters daysPast and daysFuture to define how far in the past and in the futurethe move-out date can be.

Meter Reading Entry (for Move-Out that Is Not in the Future)In this case, the creation date is the move-out date. It cannot be changed. The specification ofmeter readings is optional.

New AddressThe customer must now enter his/her new address. The system later stores this in theremarks field of the parked document.

Selection of Payment MethodThe following three payment methods are possible:

Automatic debit

Bank transfer

Check

You must specify the relevant IS-U abbreviations for the payment methods (IS-U tableTFK042Z, transaction FQP1) in the parameters:

Parameter tokenAutomaticDebitfor automatic debit

Parameter tokenBankTransferfor bank transfer

Parameter tokenCheckfor check

In automatic debit, the customer can refer to bank data that has already been maintained, orspecify new bank details. The bank number is compared with the values stored in the IS-U/CCS table BNKA.

Data for Owner and Subsequent Owner/TenantThese entries are optional and are, if necessary, transferred to the notes field of the parkeddocument in SAP IS-U.

Data Check ScreenBefore executing the data transfer, the system lists all the data entered. If the customerrecognizes an error, he/she can navigate backwards. Otherwise, he/she can trigger the datatransfer.

Screen Following Successful Data TransferAfter a successful data transfer, the system issues a message. The system lists all theentered data again. The customer can also print this list. If the customer has specified an E-mail address in his/her master data, the system creates a PDF form with the meter readingresults when the customer saves, and sends this form to the E-mail address.

The system stores the data entered in a parked document in SAP IS-U (transactionAccelerated Move-In / Move-Out / Move-In/Out Entry: Access; EC70). You must use the



parkedDocumentVariant parameter to specify the parked document variants to be used.After releasing this document, the system calls the master data generator, which then createsthe corresponding permanent data construct in SAP IS-U.



Move-In/OutThe move-in/out comprises both the move-out and move-in services. If the customer wants touse the contract account from the move-out for both services, he/she can only specify thepayment method once (see the oneAccount parameter). The entry screen then appears at theend of the move-in/out, before the all the data is listed for the customer to check.



Additional ParametersUseParameters for controlling the Web interface are defined in the XCM configuration file. Thefollowing documentation describes the parameters:

Entering Meter ReadingsParameter: startFilter (default value: 8)

Use: Meter reading entry (move-in / move-out / move-in/out)

Meaning: At the meter reading entry, a table with all the meter readings is displayed. As thiscan be very comprehensive, you can use a filter to restrict the display to the premise address,division and entries with/without meter reading order. The parameter specifies the number ofentries required before the filter is to appear.

Move-In / Move-Out / Move-In/OutParameter: businessPartnerType

Use: Move-in / move-out / move-in/out

Meaning: If you activate this parameter, you can specify the business partner type as a group,organization, or person. If the parameter is not active, the business partner type isautomatically set to person.

Parameter: startFilter (default value: 8)

Use: Meter reading entry (move-in / move-out / move-in/out)

Meaning: At the meter reading entry, a table with all the meter readings is displayed. As thiscan be very comprehensive, you can use a filter to restrict the display to the premise address,division and entries with/without meter reading order. The parameter specifies the number ofentries required before the filter is to appear.

Parameter: countrySupplyArea (default value: DE)

Use: Move-in / move-in/out

Meaning: If the system could not identify the premise, into which the customer is to move – forexample, in the case of a customer typing error – the system checks whether the premiseaddress is located in the service territory of the company. This parameter (system value) isused to define the country in which the service territory is located.

Parameter: daysPast (default value: 30)


Meaning: To avoid senseless data and typing errors, you can specify here how many days amove-in / move-out / move-in/out can lie before the current date.

Parameter: daysPast (default value: 30)


Meaning: To avoid senseless data and typing errors, you can specify here how many days amove-in / move-out / move-in/out can lie after the current date.

Parameter: dummyUserMoveIn (default value: ESERVICE)

Use: Move-in

Meaning: To access the Internet services, the customer must first use his/her user andpassword to log on. When a new customer reports a move-in, he/she must not apply for auser beforehand, but is logged on using a “dummy user”. Only the move-in service is thenavailable to the customer. The customer must logon using the page jsp/isuExtensions/



direct_logon_html.jsp, on which the user name and the password of the dummy user mustalso be defined. After the logon, the user name is compared with the value of the parameter.If they match, then further menu options are hidden.

Parameter: parkedDocumentVariant (default value: 0001)


Meaning: Parked documents are created for the move-in / move-out / move-in/out services.Different company-specific values are defined in the parking variant. This parameter is usedto maintain the name of the parking variant (table TECAMIOVAR).

Parameter: tokenAutomaticDebit (default value: E)


Meaning: Three possible payment variants are intended for the move-in / move-out / move-in/out services. One of these variants is automatic debit. At this point you must define thevalue set for this purpose in the SAP system Customizing (table TFK042Z, transactionFQP1).

Parameter: tokenCheck (default value: F)


Meaning: Three possible payment variants are intended for the move-in / move-out / move-in/out services. One of these variants is payment by check. At this point you must define thevalue set in the SAP system Customizing (table TFK042Z, transaction FQP1).

Parameter: tokenBankTransfer (default value: G)


Meaning: Three possible payment variants are intended for the move-in / move-out / move-in/out services. One of these variants is bank transfer. At this point you must define the valueset in the SAP system Customizing (table TFK042Z, transaction FQP1).

Parameter: oneAccount (default value: X)

Use: Move-in/out

Meaning: The move-in/out service consists of two services, move-out and move-in. Themove-out is processed using the recognized contract account. The contract account isunknown for the move-in. If you set the parameter (‘X’), the contract account for the move-outis used for the move-in. This means that there is only one payment method for the move-inand move-out. If you do not set the parameter, a new contract account is created, or isdetermined using a user exit. This means that there is one payment method for the move-inand one for the move-out.

Required Entry FieldsRequired entry fields are indicated on the E-services input template by a ‘*’ at the end of thename. Values must be entered in these data fields. To change normal fields to required entryfields, and vice versa, you must simply change the corresponding entry in the resource files.

A field name without a prefixed structure name is generally a required entry field. A field namethat only has a prefixed structure name for the corresponding screen is not a required entryfield. For example, NAME1=lastname* would always be a required entry field, ,S_OWNER_ADDRESS-NAME1=lastname would specify that this field is not a required entryfield for the input screen used by the S_OWNER_ADDRESS structure.

Field SequenceThe field sequence can vary depending on the logon language (for example, the fieldsequence in German would be Street, House Number, whereas the sequence in the USAwould be House Number, Street). An allowance is made for this in the properties file. All keysthat end in ‘.order’ specify a field sequence (for example street.order=s12 means street, thenhouse number, then house number supplement).



Inclusion of Additional FieldsIf an additional field is to be displayed on an input screen, you must simply enhance theexport structure of the corresponding function module, and create a field of the same name inthe corresponding JSP and resource files.



Configuration of the Web InterfaceParameters for the Extended Configuration Management(XCM) Configuration FileParameters for controlling the Web interface are defined in the XCM configuration file. Thefollowing table provides a description of the individual parameters.

Parameter Use Function

startFilter

(default value: 8)

Meter reading entry

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

During the meter reading entry, the systemdisplays a table with all meter readings. Asthis table can be very large, you can use thefollowing filter criteria:

Premise address

- Division

Entries with/without meter reading order

The parameter specifies the number ofentries required before the filter is to appear.

countrySupplyArea

(default value: DE)

Move-in/move-out If the system could not identify the premise,into which the customer is to move – forexample, in the case of a customer typingerror – the system checks whether thepremise address is located in the serviceterritory of the company. This parameter isused to define the country in which theservice territory is located.

daysPast

(default value: 30)


To avoid senseless data and typing errors,you can specify here how many days amove-in / move-out / move-in/out can liebefore the current date.

daysFuture

(default value: 30)


To avoid senseless data and typing errors,you can specify here how many days amove-in / move-out / move-in/out can lieafter the current date.

dummyUserMoveIn(default value: ESERVICE)

Move-in To access the Internet services, thecustomer must logon using a user andpassword. When a new customer reports amove-in, he/she must not apply for a userbeforehand, but is logged on using a dummyuser. Only the move-in service is thenavailable to the customer. The customermust logon using the pagejsp/isuExtensions/direct_logon_html.jsp, on whichthe user name and the password of thedummy user must also be defined. After thecustomer has logged on, the systemcompares the user name with the parametervalue. If the values match, the system hidesfurther menu options. The dummy usercannot refer to more than one businesspartner and/or contract account in SAP IS-U.



parkedDocumentVariant

(default value: 0001)


The system creates a parked document forthe services move-in, move-out, and move-in/out. Different company-specific values aredefined in the parking variant. You use thisparameter to maintain the name of theparking variant (IS-U table TECAMIOVAR).

tokenAutomaticDebit

(default value: E)


The customer has a choice of threepayment variants for the services move-in,move-out, and move-in/out. One of theseoptions is automatic debit. At this point, youmust define the value for the payment byautomatic debit. This value was set in theimplementation guide for the SAP IS-Usystem (IS-U table TFK042Z, transactionFQP1).

tokenCheck

(default value: F)


The customer has a choice of threepayment variants for the services move-in,move-out, and move-in/out. One of theseoptions is payment by check. At this point,you define the value for the payment bycheck. This value was set in theimplementation guide for the IS-U system(IS-U table TFK042Z, transaction FQP1).

tokenBankTransfer

(default value: G)


The customer has a choice of threepayment variants for the services move-in,move-out, and move-in/out. One of theseoptions is bank transfer. At this point, youmust define the value for the payment byautomatic debit. This value was set in theimplementation guide for the SAP IS-Usystem (IS-U/CCS table TFK042Z,transaction FQP1).

oneAccount

(default value: X)

Move-In/Out The move-in/out service consists of theservices, move-out and move-in. The move-out is processed using the recognizedcontract account. The contract account isunknown for the move-in. If you set theparameter ‘X’, the system uses the move-out contract account for the move-in. Thismeans that there is only one paymentmethod for the move-in and move-out. If youdo not set this parameter, the systemcreates a new contract account, or uses aBAdI in the BD_MVE_INTERNET_MOVEINfunction module to determine a contractaccount. This means that there is onepayment method for the move-in and one forthe move-out.

meterreadingFutureMoveIn

(Default value: Blank)

Move-in Here, you can allow your customers to entertheir meter readings when they move-in.

meterreadingFutureMoveOut

(Default value: Blank)

Move-out Here, you can allow your customers to entertheir meter readings when they move-out.

tokenElectricity

(Default value: 1)

Meter reading entry Define the technical name of the Electricitydivision here according to the settings in



your backend system.

tokenGas

(Default value: 2)

Mete reading entry Define the technical name of the Gasdivision here according to the settings inyour backend system.

tokenWater

(Default value: 3)

Mete reading entry Define the technical name of the Waterdivision here according to the settings inyour backend system.

Required Entry FieldsRequired entry fields are indicated on the SAP Utilty Customer E-Services input screens byan asterisk (*) at the end of the name. Values must be entered in these data fields. To changenormal fields to required entry fields, and vice versa, you must simply change thecorresponding entry in the resource files. You can find these in the WEB-INF/lib/com/sap/fin/isu/resources directory.

A field name without a structure name preceding it is generally regarded as a required entryfield. Field names with a structure name preceding them are, in contrast, only regarded asrequired entry fields for the screen in question.

NAME1=Nachname* is, for example, a required entry field. S_OWNER_ADDRESS-NAME1=Nachname specifies that this field is an exception, and is not a requiredentry field for the input screen that uses the structure S_OWNER_ADDRESS.Which screens use which structures is defined for the respective service in theresource file in the WEBINF/lib/com/sap/fin/isu/resourcesdirectory.

Field SequenceThe field sequence can vary depending on the logon language. In Germany, for example, thesequence runs Street, House Number. In the USA, however, the sequence is usually HouseNumber, Street. This is included in the resource files: All keys that end with .order specify afield order (for example, street.order=s12 specifies the sequence Street, House Number,House Number Supplement). You can find the meanings of the values, and a more precisedescription of the services in the resource file, in theWEBINF/lib/com/sap/fin/isu/resources directory.

Inclusion of Additional FieldsIf additional fields are to be displayed on an screen, you must enhance the export structurefor the corresponding function module, and create a field with the same name in thecorresponding JSP file (directory WEB-INF/jsp) and resource file (directory WEB-INF/lib/com/sap/fin/isu/resources).



Example Resource File RATEDATAYou use this file to define the rates offered to the customer. You must specify thecorresponding master data template in SAP IS-U, and additional rate data (such as estimatedconsumption and base price), for the name displayed on the Web interface.

The order of the lines is not important. However, you cannot omit objectattributes (such as rate.maxNumberOfPersons).

To create your own file, we recommend that you copy the example file andmodify it with your own values.

######################################################## C U S T O M I Z I N G F O R R A T E D A T A ######################################################### rules: ## ------ ## o all lines have to start with the prefix 'rate'. ## o the divison ID (R/3 ID) follows ## o afterwards the device group ## -> device group 'noPremise' is used, if the pre- ## mise is not known. ## o each element is separated by a '.' ## o you can define global settings with a single '*' ## (texts like '0*' is not possible) ########################################################

# maximum number of persons in a householdrate.maxNumberOfPersons=8# default number of persons in a householdrate.defaultNumberOfPersons=4

# --------------------# division electricity# --------------------

# name of the division (depending on the device type)rate.01.*.name=Strom# device type (number of rates per device type)rate.01.*.type=2# should there be a rate displayed, if there is no premise known?# -> if 'YES', use the device group 'noPremise'. If not, the '*'# are used.rate.01.usedForNoPremise=YES# estimated consumption per person in a household# -> for device type 2, a dayConsumption and/or theconsumptionPercentage# is needed, too.rate.01.*.1.estimatedConsumption=100rate.01.*.1.dayConsumption=80rate.01.*.2.estimatedConsumption=200rate.01.*.2.dayConsumption=160rate.01.*.3.estimatedConsumption=300rate.01.*.3.dayConsumption=240rate.01.*.4.estimatedConsumption=400



rate.01.*.4.dayConsumption=320rate.01.*.5.estimatedConsumption=500rate.01.*.5.dayConsumption=400rate.01.*.6.estimatedConsumption=600rate.01.*.6.dayConsumption=480rate.01.*.7.estimatedConsumption=700rate.01.*.7.dayConsumption=560rate.01.*.8.estimatedConsumption=800rate.01.*.8.dayConsumption=640# unit for the device grouprate.01.*.unit=KWH# data for each rate:# o name# o R/3 name# o annualBaseFee# o usage price per 1 unit (device type 1)# o usage price 1 per 1 unit (device type 2)# o usage price 2 per 1 unit (device type 2)# o currencyrate.*.*.0.name=Keine Auswahl

rate.01.111.1.name=Best Singlerate.01.111.1.r3name=SAPrate.01.111.1.annualBaseFee=72.00rate.01.111.1.usagePrice1=1.39rate.01.111.1.usagePrice2=0.89rate.01.111.1.currency=EURrate.01.111.2.name=Best Familierate.01.111.2.r3name=SAPrate.01.111.2.annualBaseFee=90.00rate.01.111.2.usagePrice1=1.29rate.01.111.2.usagePrice2=0.93rate.01.111.2.currency=EURrate.01.111.3.name=Eco Zukunftrate.01.111.3.r3name=SAPrate.01.111.3.annualBaseFee=120.00rate.01.111.3.usagePrice1=1.19rate.01.111.3.usagePrice2=0.99rate.01.111.3.currency=EUR# defaultly selected rate (0 - no choice)rate.01.111.default=3

# default caserate.01.*.1.name=Best Singlerate.01.*.1.r3name=SAPrate.01.*.1.annualBaseFee=72.00rate.01.*.1.usagePrice1=1.39rate.01.*.1.usagePrice2=0.89rate.01.*.1.currency=EURrate.01.*.2.name=Best Familierate.01.*.2.r3name=SAPrate.01.*.2.annualBaseFee=90.00rate.01.*.2.usagePrice1=1.29rate.01.*.2.usagePrice2=0.93rate.01.*.2.currency=EURrate.01.*.3.name=Eco Zukunftrate.01.*.3.r3name=SAPrate.01.*.3.annualBaseFee=120.00rate.01.*.3.usagePrice1=1.19rate.01.*.3.usagePrice2=0.99rate.01.*.3.currency=EUR



rate.01.*.default=3

# ------------# division gas# ------------

# name of the division (depending on the device type)rate.02.*.name=Gas# device type (number of rates per device type)rate.02.*.type=2# estimated consumption per person in a household# -> for device type 2, a dayConsumption and/or theconsumptionPercentage# is needed, too.rate.02.*.1.estimatedConsumption=10rate.02.*.2.estimatedConsumption=20rate.02.*.3.estimatedConsumption=30rate.02.*.4.estimatedConsumption=40rate.02.*.5.estimatedConsumption=50rate.02.*.6.estimatedConsumption=60rate.02.*.7.estimatedConsumption=70rate.02.*.8.estimatedConsumption=80rate.02.*.*.consumptionPercentage=68# unit for the device grouprate.02.*.unit=KWH# should there be a rate displayed, if there is no premise known?# -> if 'YES', use the device group 'noPremise'. If not, the '*'# are used.rate.02.usedForNoPremise=YES# data for each rate:# o name# o R/3 name# o annualBaseFee# o usage price per 1 unit (device type 1)# o usage price 1 per 1 unit (device type 2)# o usage price 2 per 1 unit (device type 2)# o currencyrate.02.noPremise.1.name=Gas Singlerate.02.noPremise.1.r3name=SAPrate.02.noPremise.1.annualBaseFee=72.00rate.02.noPremise.1.usagePrice1=1.39rate.02.noPremise.1.usagePrice2=0.89rate.02.noPremise.1.currency=USDrate.02.noPremise.2.name=Gas Familierate.02.noPremise.2.r3name=SAPrate.02.noPremise.2.annualBaseFee=78.00rate.02.noPremise.2.usagePrice1=1.36rate.02.noPremise.2.usagePrice2=0.86rate.02.noPremise.2.currency=USD# defaultly selected rate (0 - no choice)rate.02.noPremise.default=1

# default caserate.02.*.1.name=Gas Singlerate.02.*.1.r3name=SAPrate.02.*.1.annualBaseFee=72.00rate.02.*.1.usagePrice1=1.39rate.02.*.1.usagePrice2=0.89rate.02.*.1.currency=USDrate.02.*.2.name=Gas Familierate.02.*.2.annualBaseFee=78.00



rate.02.*.2.usagePrice1=1.36rate.02.*.2.usagePrice2=0.86rate.02.*.2.currency=USD# defaultly selected rate (0 - no choice)rate.02.*.default=1

# --------------# division water# --------------

# name of the division (depending on the device type)rate.03.*.name=Wasser# device type (number of rates per device type)rate.03.*.type=1# should there be a rate displayed, if there is no premise known?# -> if 'YES', use the device group 'noPremise'. If not, the '*'# are used.rate.03.usedForNoPremise=YES# estimated consumption per person in a household# -> for device type 2, a dayConsumption and/or theconsumptionPercentage# is needed, too.rate.03.*.1.estimatedConsumption=10rate.03.*.2.estimatedConsumption=20rate.03.*.3.estimatedConsumption=30rate.03.*.4.estimatedConsumption=40rate.03.*.5.estimatedConsumption=50rate.03.*.6.estimatedConsumption=60rate.03.*.7.estimatedConsumption=70rate.03.*.8.estimatedConsumption=80# unit for the device grouprate.03.*.unit=M3# data for each rate:# o name# o R/3 name# o annualBaseFee# o usage price per 1 unit (device type 1)# o usage price 1 per 1 unit (device type 2)# o usage price 2 per 1 unit (device type 2)# o currencyrate.03.FB_03_01.1.name=Wasser Singlerate.03.FB_03_01.1.r3name=SAPrate.03.FB_03_01.1.annualBaseFee=62.00rate.03.FB_03_01.1.usagePrice=2.39rate.03.FB_03_01.1.currency=EURrate.03.FB_03_01.2.name=Wasser Familierate.03.FB_03_01.2.r3name=SAPrate.03.FB_03_01.2.annualBaseFee=68.00rate.03.FB_03_01.2.usagePrice=2.36rate.03.FB_03_01.2.currency=EUR# defaultly selected rate (0 - no choice)rate.03.FB_03_01.default=2

# default caserate.03.*.1.name=Wasser Singlerate.03.*.1.r3name=SAPrate.03.*.1.annualBaseFee=62.00rate.03.*.1.usagePrice=2.39rate.03.*.1.currency=EURrate.03.*.2.name=Wasser Familierate.03.*.2.annualBaseFee=68.00



rate.03.*.2.usagePrice=2.36rate.03.*.2.currency=EUR# defaultly selected rate (0 - no choice)rate.03.*.default=2

Configuration Uces 604 e

Documents

Transcript of Configuration Uces 604 e