H2 ISU Efficiency Cookbook

SAP AG Neurottstr. 16

D-69190 Walldorf

Increased Efficiency Project IS-U/CCS Available Optimization Options

Copyright 2003 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA 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, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.


2

Symbols

Symbol Meaning

Caution

Example

Note

Recommendation

Step


3

1 Introduction.................................................................................................6 2 Field Selection and Field Reduction .........................................................8 3 Enhancement Concept .............................................................................11

3.1 Introduction........................................................................................11 3.2 Business Partner and Contract Account............................................12

3.2.1 Business Partner..................................................................................12 3.2.2 Contract Account ................................................................................14

3.3 Other Master Data Objects................................................................16 3.3.1 Contract...............................................................................................17 3.3.2 Installation ..........................................................................................17 3.3.3 Device .................................................................................................18 3.3.4 Device Location..................................................................................19 3.3.5 Point of Delivery.................................................................................19 3.3.6 Premise ...............................................................................................20 3.3.7 Connection Object ..............................................................................20 3.3.8 Connection ..........................................................................................21

3.4 Device Management Attachment ......................................................22 3.5 Billing and Invoicing Attachment:.......................................................25 3.6 Attachment for Accounts Receivable and Payable:...........................26

4 Sample Forms (Application Forms) ........................................................28 5 Customer Overview ..................................................................................29 6 Accelerated Move-In, Move-Out and Move-In/Out Processing.............31

6.1 Interface Simplification ......................................................................31 6.1.1 Configurable Tab for Move-in / Move-out Screen .............................31 6.1.2 Hiding Unnecessary Fields .................................................................35

6.1.2.1 Contract Fields.....................................................................35 6.1.2.2 Business Partner Fields.......................................................36 6.1.2.3 Contract Account Fields ......................................................36

6.2 Preassignment of Fields ....................................................................37 6.2.1 Reference Move-In Document............................................................37

6.2.1.1 What Does a Valid Reference Move-In Document Look Like? 37

6.2.1.2 Defining which reference move-in document is used..........38 6.2.2 Enhancements (Customer Exits),........................................................39

6.2.2.1 Overview..............................................................................39 6.2.2.2 Preassignment of Contract Account Data ...........................40 6.2.2.3 Preassignment of Contract Data .........................................41 6.2.2.4 Preassignment of Security Deposit Data.............................42 6.2.2.5 Preassignment of Budget Billing Amount ............................42 6.2.2.6 Preassignment of Welcome Letter Form.............................43 6.2.2.7 Preassignment of Form for Move-Out Confirmation............43


4

6.2.2.8 Changes to Control Parameters for Move-In...................... 43 6.2.3 Specific logics for individual fields, .................................................. 44

6.2.3.1 Account Determination ID for Contract (EVER-KOFIZ)...... 44 6.2.3.2 Company Code for Contract (EVER-BUKRS) .................... 44

6.2.4 Proposing Move-In Meter Reading Results ....................................... 44 6.3 Using Processing Variants................................................................ 45

6.3.1 Special Processing Variants ............................................................... 46 6.3.2 General Processing Variants .............................................................. 49 6.3.3 Example: Processing Variants............................................................ 51

6.4 Automating Subsequent Processing................................................. 53 6.4.1 Customizing for Move-In................................................................... 53

6.4.1.1 Creating a Budget Billing Plan ............................................ 53 6.4.1.2 Requesting Security Deposits............................................. 54 6.4.1.3 Posting Move-In Charges ................................................... 54 6.4.1.4 Welcome Letter................................................................... 54

6.4.2 Move-Out Customizing...................................................................... 55 6.4.2.1 Move-Out Confirmation....................................................... 55 6.4.2.2 Final Bill .............................................................................. 55

6.4.3 Customizing for Special Move-In/Out Cases..................................... 55 6.4.3.1 Transfer security deposits................................................... 55 6.4.3.2 Customer Change and Contract Change Without Invoicing56

6.4.4 SAP Business Workflow.................................................................... 57 6.4.4.1 Events ................................................................................. 58 6.4.4.2 Attributes............................................................................. 59 6.4.4.3 Example: Workflow for Automatic Owner Move-In ............. 60

6.5 Additional Fields in the Move-In and Move-Out Screen.................... 61 6.5.1 Customer Subscreens: Overview ....................................................... 61 6.5.2 Using Customer Subscreens: Procedure ............................................ 62 6.5.3 Menu Enhancements .......................................................................... 64 6.5.4 Additional Group Boxes for Configurable Tabs ................................ 64

6.6 Define Additional Consistency Checks ............................................. 64 6.6.1 Checking Contract Data ..................................................................... 65 6.6.2 Checking Contract Account Data....................................................... 65 6.6.3 Checking Business Partner Data ........................................................ 67 6.6.4 Checking Meter Reading Results....................................................... 67 6.6.5 Move-In: General Checks .................................................................. 68 6.6.6 Move-Out: General Checks................................................................ 69 6.6.7 Information Log ................................................................................. 70

6.6.7.1 Messages Delivered by SAP .............................................. 70 6.6.7.2 Customer-Specific Messages ............................................. 70

6.7 Deactivating Undesired Dialog Boxes............................................... 71 6.7.1 Dialog Box for Object Selection ........................................................ 71

6.7.1.1 Selection of Installation for Move-In.................................... 71 6.7.1.2 Selection of Contracts for Move-Out................................... 71


5

6.7.2 Yes-No Decisions ...............................................................................72 6.7.2.1 Contract Account Question During Move-In........................72 6.7.2.2 Contract Account Question During Contract Change..........72 6.7.2.3 Save Question During Move-In ...........................................73 6.7.2.4 Save Question During Move-Out.........................................73

6.7.3 Logs ....................................................................................................74 6.7.3.1 Success Message Log for Move-In .....................................74 6.7.3.2 Information Log for Move-Out or Move-In ...........................75

6.8 Performance Improvements ..............................................................75 6.8.1 Program Corrections ...........................................................................76 6.8.2 Functions to be Deferred.....................................................................76

6.8.2.1 Final Bill for Move-Out .........................................................76 6.8.2.2 Creating Service Orders and Notifications ..........................76 6.8.2.3 Correspondence Printing of Welcome Letters and Move-Out

Confirmations 77 6.8.2.4 Overall Check ......................................................................78

6.9 Miscellaneous....................................................................................78 6.9.1 Use of SAP Enhancements (Customer Exits) .....................................78 6.9.2 Using Business Add-Ins (BAdIs)........................................................78 6.9.3 Function Module ISU_MOVE_IN_GET_ATTR_FROM_EXT ........79 6.9.4 Structure ISU06_MOVEIN_EXT.......................................................79

7 Bill Correction ...........................................................................................81 7.1 Bill Reversal.......................................................................................81 7.2 Collective Bill and Reversal ...............................................................81

8 Account Balance Display.........................................................................83 8.1 Define Selection Criteria....................................................................83 8.2 Output Mode for Header Data ...........................................................83 8.3 Output Mode of Navigation Area .......................................................84 8.4 Output Mode of Items List .................................................................85 8.5 Additional Information in the Menu ....................................................85 8.6 Chronology Output ............................................................................86 8.7 Other Events......................................................................................86

9 Appendix....................................................................................................87 9.1 Calling Customer Exit Function Modules in the Implementation Model87 9.2 Implementing Customer Exits for Enhancements and Object

Management in the Installation AreaFehler! Textmarke nicht definiert. 9.3 Connection Between the Function Module of the Customer Exit and

the General Procedure in a Subscreen .............................................88 9.4 Procedure when Testing Customer Exits in the System....................88


6

1 Introduction In August 2002, SAP commenced the IS-U/CCS Efficiency Project. The motivation behind this project was a number of customer projects, in which demands were made for increased efficiency in certain IS-U/CCS mass dialog processes (such as business partner search, business partner identification, move-in, move-out, move-in/out, change bank details, and billing correction).

SAP analyzed a number of customer projects and determined that improvements needed to be made in many such projects, and also within functions supplied by SAP.

Therefore, SAP will provide the following packages within the IS-U/CCS Efficiency Project: Documentation Efficient IS-U/CCS Processes Existing Optimization

Possibilities. This is the document you are reading. It describes the optimization possibilities that are currently available with SAP IS-U/CCS. For example, we determined that we were not taking full advantage of all the optimization possibilities in processes such as move-in, move-out and move-in/out, which are used very regularly. This cookbook is intended to provide relevant information and stress the importance of placing particular value on efficient processes during implementation projects.

Documentation IS-U/CCS Efficiency Project New Developments. In summer 2003, SAP will deliver new developments to our customers (for example, accelerated move-in/out entry, and the express transactions Change Bank Details and Change Budget Billing Amount). These deliveries will take the form of an AOSP (Add-On Support Package) for Release 4.64 in July 2003, and an AOSP for Release 4.71 in September 2003. These modifications are described in this document.

Delivery of new developments, which are only activated in the system if the customer demands them.

Enhanced Delivery Customizing SAP will enhance the delivery customizing in some areas (for example, fields can be automatically hidden via business configuration sets (BC sets) See section 0 Field Selection and Field Reduction).

Project Reviews for Efficient Processes. If the demand, and corresponding capacity is sufficient, SAP will also offer project reviews and check the efficiency of mass dialog processes in the customer projects (such as move-in, move-out, move-in/out, change bank details, change budget billing amount, and billing correction).

As explained previously, this document relates to the existing optimization potential in IS-U/CCS. This sets out the optimization potential from SAPs side, with reference to hiding fields, preassignment of fields, and enhancements to the customer overview. A main focus of this cookbook is section 6, Accelerated Move-In, Move-Out and Move-


7

In/Out Processing. Our analysis of customer projects and live installations revealed that the optimization potential was far from being achieved here too.

Recommendation We recommend that you implement the hints described in this cookbook within your company. These optimization measures can significantly improve your processing time.


8

2 Field Selection and Field Reduction This section describes how you can hide unnecessary fields within the master data objects in IS-U/CCS. During the implementation project it is essential to hide unnecessary fields, in order to guarantee efficient processes. This allows accelerated processing, and prevents the user becoming frustrated by fields that he/she does not require.

You can also declare certain fields as mandatory fields or display fields.

Note Consider undertaking this action within your implementation project, as it reduces processing time. We have determined that the measures described were ignored in many implementation projects, and are therefore reminding you explicitly of their necessity.

You can access the field selection via various paths: In releases up to IS-U/CCS Release 4.71 you access transaction SFAC, for hiding

fields, in Customizing for SAP Utilities under: Tools System Adjustment Field Selection Select Fields. For this you must know the module pool and corresponding screen for the master data object. These are listed later.

As of IS-U/CCS Release 4.71 you can also reach the transaction via the Customizing for SAP Utilities directly for the respective master data object. For example, using Master Data Utility Installation Define Field Selection for Utility Installations. In this case, you no longer need to know the module pool or screen group, as this data is transferred directly in the customizing activity.

Specific field selection methods exist for the business partner and contract account master data objects. Transaction SFAC is not used for these objects. The corresponding settings for business partner can be found in the Customizing for Cross-Application Components under SAP Business Partner Business Partner Basic Settings Field Modification. You can find the corresponding settings for the contract account in Customizing for Financial Accounting under Contract Accounts Receivable and Payable Basic Functions Contract Accounts Field Modifications.

If you have an older IS-U/CCS release than Release 4.71, you need the module pool and screen group in transaction SFAC. Because this information is difficult to determine, they are listed again later. Additionally, you can also find this information in the documentation on the aforementioned customizing activity. You can also find further information on transaction SFAC in the customizing activity. In most cases you do not


9

need to enter the screen group. The screen group is then displayed via a dialog window, and can then be selected using the mouse.

List of relevant module pools and screen groups for transaction SFAC: Master Data

o SAPLES20 Contract (screen group ES20) o SAPLES30 Installation (screen group MAIN) o SAPLES55 Connection object (screen group 0001) o SAPLES65 Device location (screen group 0001) o SAPLES60 Premise (screen group 0001)

Device management o SAPLE10R Device data, dialog box (screen group 1100) o SAPLITO0 Data for technical objects (screen group 0001) o SAPLITO0 Equipment-specific data (screen group 0002) o SAPLEG27 Device group (screen group 0001) o

Customer Service o SAPLEC60 Selection screen for move-in/out (screen group

MAIN) o SAPLES20 Move-in contract data 1 (screen group SUBS) o SAPLEC50_CONTR Move-in contract data 2 (screen group

EC51) o SAPLEUMZ Move-in/out, gas data for meter reading

request creation o (screen group 0001) o SAPLES50 Owner allocation (screen group 0200) o

To hide fields within the move-in or move-out processing (for example, for business partner or contract account), you can find further information in the section 6 on Accelerated Move-In, Move-Out and Move-In/Out Processing. It is possible for all customers, but above all for small and medium-sized municipal utility companies, to automatically activate a reduced field view in all master data objects. As this customer area often doesnt need all the functions in the interface, it is possible to reduce the fields in the master data area without a great manual effort.

During the implementation project, small and medium-sized municipal utility companies often have neither the budget nor the time to spend days hiding fields. This can now be done automatically. A hierarchical business configuration set (BC set) with the key


10

ISU_FIELDS_LIGHT_HEADER exists for this purpose. This BC set automatically reduces the fields in the following master data objects to the minimum necessary: Business partner Contract account Contract Installation Connection object Premise Device location Device

The reduced fields were defined for this customer segment, together with an application service provider (ASP). Once the BC set is activated, the corresponding fields are automatically hidden. Activating the BC set is only advisable in an implementation project, and not when the system is in operation.

You can find more information in the online documentation for the aforementioned BC set. This BC set is delivered at the same time as the new developments for the IS-U/CCS Efficiency Project. This is to take place in July 2003, with an AOSP for Release 4.64, and in September 2003, with an AOSP for release 4.71.


11

3 Enhancement Concept

3.1 Introduction This section deals with the enhancement of master data objects in IS-U/CCS, using customer-specific fields. You will also learn how to preassign fields with certain contents, which customer exits exist for the individual master data templates, and which functions are available.

Note In the implementation project, make full use of the ability to preassign fields in processes.

All customer exits are listed for all master data objects, even if they have nothing to do with field enhancements. In this way, you get an overview of all customer exits for IS-U/CCS master data objects.

We are approaching our desired objective of clarifying all customer exits in IS-U/CCS in one document, in so far as it is now possible to see the location of exits and what they mean for all areas (such as device management, billing).

Unless otherwise indicated, all specifications apply for IS-U/CCS Releases 4.64 and 4.71.

The following master data objects are included: Business partner Contract account Contract Installation Device Device location Point of Delivery Premise Connection object Connection

Note The procedure for the business partner and contract account master data objects differs considerably from the procedure for all other master data objects. Business partner and contract account both have respective work menus. Other master data objects have different procedures.


12

3.2 Business Partner and Contract Account

3.2.1 Business Partner Field Enhancement The business partner address menu is available with the BUPT transaction, and allows you to make various settings for business partners.

You can also find basic information on this subject in the Business Data Toolset Developers Manual in the SAP Service Marketplace http://service.sap.com. Choose Login now and log on with your user and password. Then select Solution Details Industry Solutions mySAP Utilities Product Information IS-U/CCS General Cookbooks & Guidelines.

A template for enhancing customer-specific fields is available with the function group PARTNER_ENHANCEMENT_REF. Transaction SE80 takes you to package / development class EE04.

Field Enhancement for Business Partner in Move-In and Move-Out You can show or hide standard fields for business partners in move-in and move-out via transaction BUCP (see also section 6, 0 Business Partner Fields). The transactions SMOD and CMOD are available for field enhancements for business partners in move-in and move-out. You can find two customer exits under the SAP enhancement EMDBP003. You can use this enhancement to add your own fields and standard fields, which do not yet exist in the delivery of the business partner in move-in. This is a screen enhancement and not a database enhancement.

Other Enhancements for Business Partner: The transactions SMOD and CMOD are also used for other business partner-related enhancements. Enhancements EMDBP001 to EMDBP005 exist for business partners (see figure 1).

HarisHighlight


13

Figure 1: Other Business Partner Enhancements

Enhancement EMDBP005 is not relevant for Europe or the USA.

Preassignment of Fields In the task level menu a business partner (transaction BUPT) does not include a preassignment logic for the business partner

Other Customizing Activities The following customizing activities are also involved in the settings for business partners.

Settings for Creating Standard Customers in Customizing for SAP Utilities under Master Data Business Partner.


14

The system settings for standard customers in IS-U/CCS are maintained here. You can also make special settings in Customizing for standard customers.

Define Move-In Control Parameters at Document Level in Customizing for SAP Utilities under Customer Service Process Execution Move-In/Out Move-In. Here you can, for example, set whether the business partner is to adopt the connection object address during move-in.

3.2.2 Contract Account Field Enhancement The contract account work menu is available via the CAWM transaction, and allows you to make various settings for contract accounts (see figure 2).

Note You can also find basic information on this subject in the Business Data Toolset Developers Manual in the SAP Service Marketplace http://service.sap.com. Choose Login now and log on with your user and password. Then select Solution Details Industry Solutions mySAP Utilities Product Information IS-U/CCS General Cookbooks & Guidelines.

Experience shows that it is not so simple to program the event module for the contract account. Therefore, the function group ACCOUNT_ENHANCEMENT_REF is used as a template. It is found under transaction SE80 in the EE03 development class (see figure 2). This template allows you to add customer-specific fields for the contract account.


15

Figure 2: Copy Template ACCOUNT_ENHANCEMENT_REF

Field Enhancement for Contract Account in Move-In and Move-Out The transactions SMOD and CMOD are available for field enhancements for contract accounts in move-in and move-out. You can find two customer exits under the SAP enhancement EMDCA001. You can use this enhancement to add your own fields and standard fields, which do not yet exist in the delivery of the contract account in move-in. This is a screen enhancement and not a database enhancement.

Documentation about the enhancement is available. Function module documentation is available as of IS-U/CCS Release 4.71. You can find further information in unit 6, in the section on Additional Fields at the Move-In and Move-Out Screen. You can show or hide standard fields for contract accounts in move-in and move-out, using the transaction CARP (see also the section on Contract Account Fields). Preassignment of Fields Event 1017 is important for the preassignment of fields for contract accounts (contract account: preassign data when creating contract accounts). Copy template FKK_SAMPLE_1017 to guarantee that the interface operates correctly (see figure 3).


16

Figure 3: Template for Preassignment of Fields for Contract Account

In this context, three tables are relevant for further events for accounts receivable and payable:

TFKFBM This table serves as a template for specifying functions for the various events.

TFKFBS This contains the functionality that is run in all cases.

TFKFBC This table contains the modules that have been changed by the customer.

3.3 Other Master Data Objects The following specifications apply for all master data objects, with the exception of the business partner and contract account.

There are two basic forms of enhancement: Enhancements using transaction SMOD and CMOD (classic customer exits)

These require the original procedure, which is used for most master data objects.


17

Enhancements using transaction SE19 in the form of BAdI implementations This technology is used for all new master data objects, as of Release 4.71.

Transaction SMOD provides you with an overview of the customer exits supplied by SAP. Transaction CMOD allows you to use existing Exits to implement customer-specific enhancements. Here you can include customer-specific fields in screens, preassign fields, and define customer-specific tests.

You can also access the customer exits via transaction SE80 and by selecting the corresponding package. The name of the relevant function group always begins with X.

Example You can find the customer exits for the package (as of IS-U/CCS Release 4.71) or development class (up to IS-U/CCS Release 4.64) EE07 under function group XE07.

You can find further information and task lists for the procedure in the appendix for unit 6, in the sections Using SAP Enhancements (Customer Exits) and Using Business Add-Ins (BAdIs).

3.3.1 Contract Enhancement and Preassignment of Fields: Transactions SMOD and CMOD are available for enhancing and preassigning fields for contracts.

There are ten customer exits under the SAP enhancement EMDK0001. Customer exits 1 to 10 allow you to enhance customer-specific fields in an individual subscreen, and customer exit 2 is also used for preassigning fields. Customer exit 1 serves the customer-specific checking of screen fields. Customer-specific authorization checks are not intended at this point.

Under enhancement EMDK0001 you find the include CI_EVER, which you can use to include customer-specific fields in the EVER database table.

3.3.2 Installation Enhancement and Preassignment of Fields: Transactions SMOD and CMOD are available for enhancing and preassigning fields for installations.

There are eleven customer exits under the SAP enhancement EMDI0001. Customer exits 1 to 10 allow you to enhance customer-specific fields in an individual subscreen, and customer exit 2 is also used for preassigning fields. Customer exit 11 is used to implement customer-specific authorization checks (this function is available as of IS-U/CCS Release 4.71).

In appendix 9 of this cookbook you will find documents, which go into further detail regarding the settings for customer exits 1 to 10.


18

Table EANL contains installation data. Use the customer include CI_EANL to include customer-specific fields in the database table. You can define this include with enhancement EMDI0001. Table EANLH contains time slice data. There is also a corresponding customer include (CI_EANLH) for this table (see figure 4) for including customer-specific historical data.

Figure 4: Table EANL

3.3.3 Device Enhancement and Preassignment of Fields: Transactions SMOD and CMOD are available for enhancing and preassigning fields for devices.

There is one customer exit under the SAP enhancement EMDK0001. Unlike for most other IS-U/CCS master data objects, the customer-specific fields are not shown in one subscreen, but are shown in a separate tab page in the device. However, the customer-exit can only be used to create a device via the Materials Management (MM) component. If a new device is


19

created in this case, the Additional Data pushbutton appears. This applies for Materials Management transactions, such as MIGO, MB1C and MB01.

When creating a device using Plant Maintenance (PM), you can enter data directly onto the Other tab page. You do this by using transaction IQ01 to define enhancement ITOB0001. This is not possible via transaction IQ04. In change mode, however, you can use both transactions to access customer-specific fields.

Table EQUI contains device data. The customer include CI_EQUL is used to include customer-specific fields in the database table. You cannot preassign fields for devices. You can use the field selection to display fields for device and connection (both based on equipment) differently.

You can find a list of all customer exits in device management in section 3.4 Device Management Attachment.

3.3.4 Device Location Enhancement and Preassignment of Fields: Transactions SMOD and CMOD are available for enhancing and preassigning fields for device location.

There are ten customer exits under the SAP enhancement ES650001. Customer exits 1 to 10 allow you to enhance customer-specific fields in an individual subscreen, and customer exit 2 is also used for preassigning fields. Customer exit 1 serves the customer-specific checking of screen fields. Customer-specific authorization checks are not intended at this point.

Table IFLOT contains technical object data. The customer include CI_IFLOT is used to include customer-specific fields in the database table. You can also use SAP enhancement ECIIFLOT to create this include.

The customer include CI_IFLOT is equally relevant for connection objects and device locations. Within your project, you decide which fields for connection object and device location are to appear in an individual subscreen. You can show and hide the fields in the Process before Output (PBO) event for the subscreen, as required. In this case, you cannot show and hide the fields via the field selection.

3.3.5 Point of Delivery Enhancement and Preassignment of Fields: When the point of delivery is the most recent master data object, two technologies are used:

1. There are four enhancements, EEDMUI01 to 04, for changing the point of delivery ID: EEDMUI01 adjusts the area structure EEDMUI02 adjusts the German structure (metering code) EEDMUI03 and 04 adjust the English structure (UK)

Enhancements EEDMUI03 and 04 are available as of IS-U/CCS Release 4.71.


20

The enhancements have two customer exits. One checks the metering code, the other is used to propose the metering code. At present (IS-U/CCS Releases 4.64 and 4.71) there is no available system documentation for the function module.

You must assign the customer exits in the Customizing for SAP Utilities under Master Data Point of Delivery Define Structure of Point of Delivery ID. Observe the documentation for the customizing activity.

2. The actual enhancement of customer-specific fields for point of delivery is carried out via BAdI implementation ISU_EDM_POD_CUSTOMER, which you can call with transaction SE18. If the BAdI implementation is carried out within the project, then a third tab page Others appears under the Header tab page, next to the Grid and Origin tab pages. The customer-specific fields are shown on this tab page.

This function is available as of IS-U/CCS Release 4.72.

Note You can find further information on points of delivery in the Help Portal in the SAP Library.

3.3.6 Premise Enhancement and Preassignment of Fields: Transactions SMOD and CMOD are available for enhancing and preassigning fields for premises.

There are ten customer exits under the SAP enhancement EMDP0001. Customer exits 1 to 10 allow you to enhance customer-specific fields in an individual subscreen, and customer exit 2 is also used for preassigning fields. Customer exit 1 serves the customer-specific checking of screen fields. Customer-specific authorization checks are not intended at this point.

Under enhancement EMDP0001 you find the include CI_EVBS, which you can use to include customer-specific fields in the EVBS database table.

3.3.7 Connection Object Enhancement and Preassignment of Fields: Transactions SMOD and CMOD are available for enhancing and preassigning fields for connection objects.

There are ten customer exits under the SAP enhancement ES550001. Customer exits 2 to 11 allow you to enhance customer-specific fields in an individual subscreen, and customer exit 3 is also used for preassigning fields. Customer exit 2 serves the customer-specific checking of screen fields. Customer-specific authorization checks are not intended at this point.

You can find customer exit 1 under SAP enhancement ECONNOBJ. It runs a duplicate check for the connection object.


21

Table IFLOT contains technical object data. The customer include CI_IFLOT is used to include customer-specific fields in the database table. You can also use SAP enhancement ECIIFLOT to create this include.

The customer include CI_IFLOT is equally relevant for connection objects and device locations. Within your project, you decide which fields for connection object and device location are to appear in an individual subscreen. You can show and hide the fields in the PBO event for the subscreen, as required. In this case, you cannot show and hide the fields via the field selection.

3.3.8 Connection Enhancement and Preassignment of Fields: Transactions SMOD and CMOD are available for enhancing and preassigning fields for connections.

There are seven enhancements, IEQM0001 to IEQM0007, each with one customer exit (see figure 5).

Figure 5: Enhancements for Equipment

Table EQUI contains connection data (equipment data). The customer include CI_EQUL is used to include customer-specific fields in the database table. You can only store customer-specific fields for time-independent data. You can use the field selection to display fields for device and connection (both based on equipment) differently. You can find the field selection


22

in Customizing for Plant Maintenance and Customer Service under Master Data in Plant Maintenance and Customer Service Technical Objects Equipment. 3.4 Device Management Attachment Some customer requirements, related to device installation / removal and replacement, are delivered by SAP as customer exits. You must enter these functions in the Customizing for SAP Utilities under Device Management Installation Basic Settings Define System Parameters for Installation / Removal / Replacement. Selecting the F4 button in the Customizing table gives you an overview of the functions offered (see figure 6). Selecting F1 Help provides you with detailed documentation.

Figure 6: Additional functions for device installation / removal / replacement for IS-U/CCS Release 4.71.

Customers cannot change these additional functions.

The following list shows the important customer exits from device management:

Package / Development Class EE07 Enhancements (Transaction SMOD):

E07 (IS-U/CCS: Device installation and installation structure) EDMDI001 (Customer-specific default values for installation, removal and

replacement) EDMDI002 (Customer-specific checks for installation, removal and replacement)


23

EDMDI003 (Customer-specific data for goods movement during installation and removal)

Customer Exits:

EXIT_SAPLE30B_001 (Permissibility checks for device replacement) EXIT_SAPLE30D_001(Default values for installation, removal and replacement) EXIT_SAPLE30D_002(Checks for installation, removal and replacement) EXIT_SAPLE30D_001(Entries for goods movement during installation, removal and

replacement) EXIT_SAPLEG42_001 (Device modification, device and register data after

modification) EXIT_SAPLEG42_002 (Check device info record, device modification, device and

register data) EXIT_SAPLEG60_001 (Default allocation of logical registers)

Package / Development Class EE10 Enhancements (Transaction SMOD):

EDMCERT1 (Certification / rev.: subscreens for processing customer-specific data) EDME10L1 (IS-U: enhancement for IS-U dialog box at goods receipt / installation

device) EDME10L2 (IS-U: Enhancement for checking device data B37+B12... ) EDMEG901 (IS-U: Change order and notification codes for periodic replacement) EDMEG902 (IS-U: Determine plant and work center for uninst. Samp. Devices) EDMEGTUR (IS-U: periodic replacement customer-specific fields) EDMLOT01 (IS-U: assemble checks / selections for lot (EG8A)) EDMLOT02 (IS-U: enhancement for determination of lot devices) EDMLOT03 (customer enhancements in lot combination) EDMRPLYR (IS-U: determination of replacement year) EUSDEC01 (IS-U: follow-up action certificate at inspection lot completion)-{}-

Customer Exits:

EXIT_SAPLE10CERT_001 (Customer Exit PBO EG97) EXIT_SAPLE10CERT_002 (Customer exit PAI EG97) EXIT_SAPLE10CERT_003 (Customer exit update EG97) EXIT_SAPLE10R_001 (User exit: checks for IS-U data during goods receipt/ device

creation)


24

EXIT_SAPLE10R_002 (User exit: Preassignment of data for dialog box when creating devices)

EXIT_SAPLE10R_003 (User exit: device data check during device modification) EXIT_REGWDR01_001 (Customer exit: change order code and notification code

for periodic replacement) EXIT_REGWDR01_002 (Customer exist: Determine plant and work center for

uninst. samp. devs) EXIT_SAPLE10T_001(User exit: periodic replacement) EXIT_REGLOS04_001 (User exit: further checks at device level for EG8A) EXIT_SAPLE10M_002(User exit: determine lot devices (ISU_EGLO_CREATE)) EXIT_SAPLE10U_001 (Customer exit: check for source lots at lot combination) EXIT_SAPMEG8C_001 (Customer exit: check for target lots at lot combination) EXIT_SAPMEG8C_002 (Customer exit: check for source lots at lot combination)

EXIT_SAPLE10M_001 (User exit: determination of replacement year) EXIT_SAPLE10USDEC_001 (IS-U: Decision whether device is to be certified) EXIT_SAPLE10USDEC_002 (IS-U: retrieve meter reading data, modify device list)

Function Group XEQM Enhancements (Transaction SMOD):

IEQM0001 (Additional checks when installing equipment at technical location) IEQM0002 (Additional checks when defining equipment hierarchies) IEQM0003 (Additional checks before posting equipment) IEQM0004 (Object is permitted for contract partner (ordermaintenance contract) IEQM0005 (Object permitted for sales contract (maintenance contract

maintenance contract)) IEQM0006 (Object permitted for sales contract (maintain maintenance contract) IEQM0007 (Check / change manufacturer field for equipment master)

Customer Exits:

EXIT_SAPLIEL2_002 (Check user defined rules on installation of equipment at functloc.)

EXIT_SAPLIEL2_001 (Check customer-specific regulations for defining equipment)

EXIT_SAPMIEQ0_001 (Check customer-specific regulations before posting equipment)


25

EXIT_SAPLIPW0_001 (Object is permitted for contract (copy order / maintenance order))

EXIT_SAPLIPW0_002 (Object is permitted for contract (copy maintenance order))

EXIT_SAPLIPW0_003 (Object is permitted for contract (maintain maintenance order))

EXIT_SAPMIEQ0_002 (Customer-specific check/change for manufacturer data for technical object)

Function Group XQSM Enhancements (Transaction SMOD):

IQSM0001 Automatic serial number assignment IQSM0002 Check when copying object list IQSM0003 Serial numbers, user exit for additional data IQSM0004 Serial numbers, user exit after leaving serial screen IQSM0005 Serial numbers, user exit to posting IQSM0007 Serial numbers, user exit for material movement IQSM0008 Check for serial numbers character string

Customer Exits:

EXIT_SAPLIPW1_001(Automatic serial number assignment) EXIT_SAPLIPW1_002 (Check when copying object list) EXIT_SAPLIPW1_003 (Serial number, user exit for additional fields) EXIT_SAPLIPW1_004 (Serial numbers, user exit after leaving serial screen) EXIT_SAPLIE01_005 (Serial numbers, user exit to posting) EXIT_SAPLIE01_007 (Serial numbers, user exit to goods movement) EXIT_SAPLIPW1_008 (Check serial number string)

3.5 Billing and Invoicing Attachment: The following list shows the enhancements from the billing and invoicing areas:

EBIA0001 IS-U: Complete customer-specific fields in billing document EBIA0002 IS-U: Differentiate according to customer-specific dates EBIA0003 IS-U: Customer-specific checks in billing and overall check EBIA0004 IS-U: Customer exit for external compressibility calculation EBIA0005 IS-U: Termination control for mass runs


26

EBIA0006 IS-U: Period control for determining time portion in billing EBIA0007 IS-U: Customer-specific actions in billing reversal EBIA0008 IS-U: Customer-specific actions in update billing reversal EBIA0009 IS-U: Daily / monthly adjustment for move-in/out EBIA0011 IS-U: Billing update EBIA0012 IS-U: Complete customer data in billing object OBJ EBIA0013 IS-U: Customer checks in billing selection EBIA0014 IS-U: Complete customer-specific fields in manual billing document EBIA0015 IS-U: Backbilling customer exit EBIA0016 IS-U: Determination of billing calorific value EBIA0017 IS-U: Individual document display EBIA0018 IS-U: Customer conditions for backbilling line summary EBIA0019 IS-U: Customer-specific billing comparison EBIA0020 IS-U: Change current period during dynamic period control EBIA0021 IS-U: Change current period during dynamic period control EBIA0022 IS-U: Change contract sequence for billing EBIA0023 IS-U: Check for facts EBIA0024 IS-U: Enhancement for determining special operand values EBIA0025 IS-U: Determine different weighting for measured quantities EBIA0026 IS-U: Postprocessing for gas factors EBIA0027 IS-U: Enhancement for authority check facts EBIA0028 IS-U: Enter / save customer facts in billing object EBIA0029 IS-U: Permit multiple adjustment reversals EBIA0030 IS-U: Customer exit for customer overview report in BRE

3.6 Attachment for Accounts Receivable and Payable: By customizing events via transaction FQEVENTS, a new tool for the overview and management of events is available as of Release 4.71.

The transaction offers you several possibilities for searching for an event:

List of all events Direct access to event number Predefined search terms Combination of search terms (w1 AND w2) OR (w3 and w4) Full text search (only in German and English)

You select the search variants via the push button (Personal Screen Settings).


27

The documentation for sample function modules and tables with sample function modules, standard function modules and installation-specific function modules are displayed for a selected event. You can display this module directly or copy it. You can also allocate new, installation-specific function modules to the event.


28

4 Sample Forms (Application Forms) The following explains how you to handle the creation of forms in an implementation project. Within the IS-U/CCS Efficiency Project we have determined that some customers did not access the SAP standard sample forms when creating forms.

In many cases customers did not even know that sample forms are delivered with the SAP print workbench, or how to access these sample forms.

A sample form is delivered for the most important existing form classes within IS-U/CCS and FI-CA. Following the system installation, you can find the sample forms in your client 000.

To do this, log onto your development client and call transaction EFRM for processing forms. From the menu, select Utilities Copy from Client and enter client 000 in the following dialog box.

Select (Transfer). The system goes to client 000 and displays all the sample forms from client 000. You can now copy the sample form you require into your development client and continue working on it there.

The following figure shows a section of the segment of the sample forms delivered in client 000.

Figure 7: Segment of Sample Forms from Client 000

Recommendation Always use a sample form when starting activities involving forms in the implementation project. This considerably reduces the implementation time, when compared to the time required to create a form without using a sample.

You must also observe that, as of Release 4.71, SAP offers Smart Forms as an alternative to SAPscript. This means that, in future releases, SAP will also deliver sample forms for Smart Forms, and will focus more on this technology.


29

5 Customer Overview This unit explains how to use the SAP HTML customer overview, and how it is possible to enhance it with additional information. Along with the search and identification of a business partner using the Customer Interaction Center (CIC), the customer overview is a central and important function. The objective of the customer overview is to provide a quick overview of the relevant master and movement data (such as meter reading results, consumption, billing documents, account information).

Within the IS-U/CCS Efficiency Project, SAP determined that some customers have not used the SAP HTML customer overview function. Instead of using this function, they have only used the data environment for information retrieval, which subsequently leads to a comprehensive and time-consuming navigation. It takes too long for the agent to access the relevant information.

The following measures reduce the processing time within the customer overview: Documentation on the enhancement possibilities of the SAP HTML customer

overview. From SAPs viewpoint, it is difficult to define a standard customer overview for all customers. The demands differ greatly, depending upon region, country and company type. If you require additional fields, you can include these in the customer project using the enhancement concept of the HTML customer overview.

At a given time, SAP will enhance the standard HTML customer overview with additional information (such as meter reading results, and consumption quantities).

You can find further a description of the HTML customer overview in the Help Portal in the SAP Library.

You can find detailed information in unit 3.2.1.1 Maintaining the HTML Configuration of the Application Area, and unit 7 HTML Templates. Both these sections describe how the HTML customer overview is included in the CIC. They also describe how to define new HTML templates, in order to display additional fields in HTML customer overview, for example.

You can also find basic information on this subject in the SAP Utilities Documentation in the Help Portal under the Internet adress http://help.sap.com SAP Industry Solutions SAP for Utilities Customer Service Customer Interaction Center.

Note Make sure that the data selection (Customizing Define HTML Customer Overview) precisely matches the fields shown. Fields that are not displayed but are selected, limit performance.


30

Note You can find information on how to use the customer overview via CRM in our cookbook Fact Sheet in the SAP Service Market Place http://service.sap.com. Choose Login now and log on with your user and password. Then select Solution Details Industry Solutions mySAP Utilities Product Information mySAP CRM for Utilities Cookbooks & Guidelines.


31

6 Accelerated Move-In, Move-Out and Move-In/Out Processing

6.1 Interface Simplification

Summary The following section describes how you can simplify the interface for move-in / move-out processing:

- You can configure the move-in / move-out tab according to your needs - You can hide contract, contract account or business partner fields that you do not require.

6.1.1 Configurable Tab for Move-in / Move-out Screen The move-in and move-out screen is structured in tab pages. Each tab page includes group boxes. For example, for SAP layouts on the bank details tab page, the group boxes are Business Partner Bank details and Business Partner Credit Cards. You can use the Customizing to determine the number of tab pages on the move-in and move-out screens and the position of group boxes for individual tab pages. These settings are grouped under the term Layout.

SAP delivers the standard layouts SAP (complete layout) and SAPR (reduced layout). To define a layout that suits your requirements, select the following path in IS-U Customizing: SAP Utilities Customer Service Process Execution Move-In / Out Move-In Configure Tabs for Move-In Screen or Move-Out Configure Tabs for Move-Out Screen. Here you can determine the number, title and sequence of tab pages, as well as the group box position.

The Layout is also located in the move-in screen. Selecting this button allows you to switch between the standard SAP-delivered layout and your reduced layout.

To ensure that the layout you defined is used for the move-in or move-out screen, make the following settings: If you always want to use the same layout, select the following path in the IS-U

Customizing: SAP Utilities Basic Settings / Enterprise Structure Define Default Layout for Tabs. Enter the layout for the move-in in the line ISU_MOVEIN, and the layout for the move-out in the line ISU_MOVEOUT.

If you want to use different layouts, you can use the processing variants to differentiate between the individual cases. Enter the layout in the specific fields in the processing variants. For detailed information, see section 6.3.

Example


32

The following illustrations show the difference between the SAP layout (illustration 8) and a reduced layout (illustration 9). The reduced layout contains only two tab pages (the SAP layout, in contrast, has seven) The first tab page of the reduced layout contains three group boxes, the second has only one group box S0031 (contract data).

In the group box Business Partner Name and General Data, additional individual fields were hidden. Section 6.1.2.2 describes how this function works.


33

Figure 8: Move-In with SAP Layout


34


35

Figure 9: Move-In Screen with Reduced Layout

Figure 10: Definition of Layout in Customizing

6.1.2 Hiding Unnecessary Fields

6.1.2.1 Contract Fields You can show or hide contract fields that are located in the move-in screen, by selecting the path SAP Utilities Tools System Modifications Field Selection Select Fields (transaction SFAC). For technical reasons, two module pools exist, in which you can maintain the different fields:

Enter SAPLES20 in the module pool field, and select Display. Select the screen group IS-U Contract Fields in Move-In. This takes you to a screen containing modifiable fields for the contract. You can use the radio buttons to determine characteristics for each field; for example whether it is a mandatory field, and whether it is to be displayed or hidden.


36

Enter SAPLEC50_CONTR in the module pool field, and select Display. Select the screen group Move-In: Individual Maintenance of Contract Data. You are taken to a screen for the display of modified fields for the contract and can use the radio buttons to determine, for each field, whether, for example, it is a mandatory field, and whether it is to be displayed or hidden.

Note As of IS-U Release 4.71, the Customizing activity Define Field Selection for Move-In Contract Data is available for this purpose, and can be found under the following path: Customer Service Process Execution Move-In / Out Move-In.

6.1.2.2 Business Partner Fields To hide or display business fields that are situated in the move-in or move-out screen, call transaction BUPT twice in the IS-U system. In the SAP Easy Access Menu, select Customizing Basic Settings Field Modification External Applications (transaction BUCP). For the move-in, select the external application ISU0001. For the move-out, select the external application ISU0002. You can select the option Hide, Required Entry, Optional Entry or Display for each field group.

Example The fields for the business partner drivers license are not required in your system. They should not, therefore, be displayed in the move-in or move-out screen. Proceed as follows:

1. Select the lines with external application ISU0001 (move-in).

2. Select Field Modification.

3. Select the line ISU010 (ISU Data Contract Partner) in the Data Set table.

4. Select (Detailed View).

5. Select Hide for the field groups 411 (ISU: drivers license) and 414 (ISU: drivers license country and region).

6. Save your entries.

7. Select the lines with the external application ISU0002 (move-out) and repeat steps 2 to 6.

Note As of IS-U/CCS Release 4.71, the Customizing activity Select Business Partner Fields for Move-In and Move-Out Screen is available, and can be found under the following path: Customer Service Process Execution Move-In / Out.

6.1.2.3 Contract Account Fields


37

To hide or show contract account fields that are situated in the move-in or move-out screen, call transaction CAWM twice in the IS-U system. Select the menu path, Customizing Field Grouping External Application (transaction CARP). For the move-in, select the external application ISU0001. For the move-out, select the external application ISU0002.

Note As of IS-U/CCS Release 4.71, the Customizing activity Select Contract Account Fields for Move-In and Move-Out Screen is available, and can be found under the following path: Customer Service Process Execution Move-In / Out.

6.2 Preassignment of Fields

Summary In this section you learn how to preassign individual fields from the master data contract and contract account. This means that these fields are automatically maintained by the system. As a result, the agent does not have to make manual entries in the fields. This makes particular sense for those fields whose values are determined by set rules, and has the following advantages:

Reduced steps for the expert,

Reduced processing time, particularly for move-in

Prevention of errors that can arise due to manual entries

At the end of the section, you also learn how to derive meter reading results (for example, during a move-in) from meter reading results that already exist.

SAP offers the following alternatives for preassigning fields: Reference Move-In Document Enhancements (Customer Exits), Specific logics for individual fields Specific Customizing (for proposing meter reading results)

6.2.1 Reference Move-In Document You can use a reference move-in document when creating a move-in. This means that the following business master data is proposed: Contract account data if a new contract account is created in the system when the

move-in is created Contract data

6.2.1.1 What Does a Valid Reference Move-In Document Look Like?


38

A reference move-in document can be a normal move-in document, which you have created in the system. It must however fulfill the following conditions:

a) Non-deregulated case:

For each installation from the move-in document that is to be created, precisely one contract from the same division must exist in the reference move-in document.

Example You want to create a move-in document for the electricity and gas divisions. The following move-in documents are available in the system:

Move-in document 1 contains two contracts one from the electricity division and one from gas.

Move-in document 2 contains three contracts one from the electricity division, one from gas, and one from water.

Move-in document 3 contains three contracts two from the electricity division and one from gas.

You can use move-in documents 1 and 2 as reference move-in documents, but not move-in document 3.

b) Deregulated case:

For each installation from the move-in document that is to be created, exactly one contract from the same division and service type must exist in the reference move-in document.

Example You want to create a move-in document for the electricity and gas divisions. You have two installations for each division one for the service type Distribution and one for the service type Supply. Therefore, you require a reference move-in document with (at least) four contracts.

In both cases, the contract account category of the reference move-in document must correspond to the contract account category for the move-in document to be created.

Note As of IS-U/CCS Release 4.61, you can also use a reversed move-in document as a reference move-in document.

6.2.1.2 Defining which reference move-in document is used


39

The user can enter the reference move-in document number in the initial screen for the Create Move-In (EC50E) and Move-Out (EC60) transactions.

When you create move-in documents using the Customer Interaction Center (CIC), you can transfer the reference move-in document to the BOR method as an import parameter for creating a move-in document (for example, the parameter ReferenceMiDocument for the method Create to the BOR object type MOVEINOUT).

6.2.2 Enhancements (Customer Exits),

6.2.2.1 Overview The following table contains an overview of the enhancements that you can use for preassigning fields during move-in or move-out. You can find detailed information in the following sections and in OSS note 152498.

Enhancement Function Module

Contract Account FI-CA Event 1017 (Contract account: Preassign data when creating contract account)

FKK_SAMPLE_1017

Contract EMDK0001 (IS-U utility contract: Include subscreens and check fields)

EXIT_SAPLES20_002

Security Deposit EC500001 (IS-U move-in: Determine security deposit amount and reason)

EXIT_SAPLEC50_001

Budget Billing Amount ECSBTI02 (IS-U move-in: Determine budget billing amount)

EXIT_SAPLEC50_004

Welcome Letter ECSBTI01 (IS-U move-in: Determine application form)

EXIT_SAPLEC50_003

Move-out Confirmation and Control Parameters for Move-out

ECSBTO0 (IS-U move-out: Determine default values)

EXIT_SAPLEC55_011


40

Control Parameters for Move-in

BAdI ISU_MOVEIN_CUSTOMIZE

6.2.2.2 Preassignment of Contract Account Data You can use FI-CA event 1017 to preassign data for a contract account that is to be created.

Proceed as follows:

Create a function group and, within this function group, a copy of function module ISU_EVENT_1017.

In Customizing, select the following path: Financial Accounting Contract Accounts Receivable and Payable Program Enhancements Define Customer-Specific Function Modules. Select event 1017 and go to the installation-specific function modules. Add an entry with number 1 and the name of the function module that you have created. Save this data.

Example The short text for the installation address is transferred to the contract account description. To determine the data for the installation, you can use the function module ISU_MOVE_IN_GET_ATTR_FROM_EXT (see section 6.9.3). INCLUDE ieadrtyp. DATA: l_movein_ext TYPE isu06_movein_ext, l_movein_ext_pos TYPE isu06_movein_ext_pos, l_addr_lines TYPE eadrln. * get move-in data CALL FUNCTION 'ISU_MOVE_IN_GET_ATTR_FROM_EXT' IMPORTING y_movein_ext = l_movein_ext EXCEPTIONS access_denied = 1 OTHERS = 2. * leave this function module if it is called outside move-in * processing CHECK sy-subrc = 0. READ TABLE l_movein_ext-tpos INTO l_movein_ext_pos INDEX 1. CHECK sy-subrc = 0. * read installation address CALL FUNCTION 'ISU_ADDRESS_PROVIDE' EXPORTING


41

x_address_type = co_for_installation x_anlage = l_movein_ext_pos-ever-anlage IMPORTING y_addr_lines = l_addr_lines EXCEPTIONS not_found = 1 parameter_error = 2 object_not_given = 3 address_inconsistency = 4 installation_inconsistency = 5 OTHERS = 6. IF sy-subrc = 0. * copy address description to contract account description z_fkkvk-vkbez = l_addr_lines-line1. ENDIF.

6.2.2.3 Preassignment of Contract Data You can use the SAP enhancement EMDK0001 to preassign data for a contract that is to be created.

Proceed as follows:

Create a project for the SAP enhancement EMDK0001 (see section 6.9.1. Use the function module EXIT_SAPLES20_002.

Use function module ISU_MOVE_IN_GET_ATTR_FROM_EXT to access the data available in move-in (see section 6.9.3).

Example Depending upon the contract account class, the account determination characteristic for the contract is to be preassigned. To determine the data for the contract account, you can use the function module ISU_MOVE_IN_GET_ATTR_FROM_EXT (see section 6.9.3). INCLUDE iewmodes. DATA: l_movein_ext TYPE isu06_movein_ext. * initialize export parameter y_everd = x_everd. * proceed if and only if contract is to be created CHECK x_wmode = co_create. * get move-in data CALL FUNCTION 'ISU_MOVE_IN_GET_ATTR_FROM_EXT' IMPORTING y_movein_ext = l_movein_ext


42

EXCEPTIONS access_denied = 1 OTHERS = 2. * leave this function module if it is called outside move-in * processing CHECK sy-subrc = 0. CASE l_movein_ext-fkkvkp1-ktokl. WHEN '0001'. y_everd-kofiz = '01'. WHEN '0002'. y_everd-kofiz = '02'. WHEN OTHERS. y_everd-kofiz = '03'. ENDCASE.

6.2.2.4 Preassignment of Security Deposit Data You can use SAP enhancement EC500001 (function module EXIT_SAPLEC50_001) to preassign the following security deposit data per contract: Security deposit amount and currency (parameter Y_REQUEST and Y_WAERS) Reason for demanding security deposit (parameter Y_REASON) Reason for exemption from security deposit (parameter Y_WAIVEREAS)

This data is displayed on the move-in screen in the contract data and is included if a security deposit is required when a move-in document is changed or created.

Proceed as follows:

Create a project for the SAP enhancement EC500001 (see section 6.9.1). Use the function module EXIT_SAPLEC50_001.

The data available in the move-in is retrieved at the interface (parameter X_MOVEIN_EXT, see section 6.9.4).

6.2.2.5 Preassignment of Budget Billing Amount You can use the SAP enhancement ECSBTI02 (function module EXIT_SAPLEC50_004) to define the budget billing amount per contract. This data is displayed on the move-in screen in the contract data and is included if a budget billing plan is created when a move-in document is changed or created.

Proceed as follows:

Create a project for the SAP enhancement ECSBTI02 (see section 6.9.1). Use the function module EXIT_SAPLEC50_004.

The data available in the move-in is retrieved at the interface (parameter X_MOVEIN_EXT, see section 6.9.4).


43

6.2.2.6 Preassignment of Welcome Letter Form You can use SAP enhancement ECSBTI01 (function module EXIT_SAPLEC50_003) to preassign the following welcome letter data: Application form (parameter Y_FORMBEGR) Indicator, to define whether a form selection dialog is desired when printing the

welcome letter (parameter Y_AUSWBEGR).

Proceed as follows:

Create a project for the SAP enhancement ECSBTI02 (see section 6.9.1). Use the function module EXIT_SAPLEC50_003.

The data available in move-in is retrieved at the interface (parameter X_MOVEIN_EXT, see section 6.9.4).

6.2.2.7 Preassignment of Form for Move-Out Confirmation You can use SAP enhancement ECSBTO01 (function module EXIT_SAPLEC55_011) to preassign the form for move-out confirmations.

You can also change the following move-out control parameters, and thus change the values determined in Customizing (SAP Utilities Customer Service Process Execution Move-In/Out Move-Out): Move-out control parameters at document level (changing parameter XY_E490A) Move-out control parameters at contract level (table parameter TXY_E490AV).

Proceed as follows:

Create a project for the SAP enhancement ECSBTO01 (see section 6.9.1). Use the function module EXIT_SAPLEC55_011.

The data available in move-out is retrieved at the interface (parameter X_MOVEOUT_EXT).

6.2.2.8 Changes to Control Parameters for Move-In In Customizing for SAP Utilities under Customer Service Process Execution Move-In/Out you can make various settings in the following activities. These settings are partly dependent upon the company code for the contract and the billing class for the installation: Define System Parameters for Move-In and Move-Out Move-In Define Move-In Control Parameters at Document Level


44

Move-In Define Move-In Control Parameters at Contract Level It is sometimes necessary for the settings to depend upon other factors (such as the contract account category or the contract account class). You can use the Business Add-In (BadI) ISU_MOVEIN_CUSTOMIZE to realize this requirement. See the section 6.9.2.

6.2.3 Specific logics for individual fields, Specific preassignment logics are implemented for some contract fields. These are only relevant if you do not use a (valid) reference move-in document or any of the aforementioned enhancements for the corresponding fields.

This means that the preassignment of fields using a reference move-in document and enhancements always has priority over the determination logics described below.

6.2.3.1 Account Determination ID for Contract (EVER-KOFIZ) The account determination ID for the contract (field EVER-KOFIZ) can be proposed using the SET-GET parameter KMM. You can define the value of the SET-GET parameter in the user master record.

6.2.3.2 Company Code for Contract (EVER-BUKRS) You can determine the company code for the contract (field EVER-BUKRS) from the following elements: The franchise contract defined in the installation (field EKON-BUKRS) The (postal) regional structure The responsible company code of the contract account (in accordance with table

TFK001B), provided this allocation is unique

6.2.4 Proposing Move-In Meter Reading Results For a contract to be billed in IS-U/CCS, the move-in meter readings are required. In practice, however, a separate move-in meter reading is not carried out in many cases. It is more common for meter readings that already exist in the system to be adopted, where possible (for example, meter readings upon installation, or final meter readings from the previous contract).

In the IS-U system, you can fulfill this requirement through Customizing settings. You can find the field Propose interval for move-in (TE410-INTV_PROP_MOVEIN) in the Customizing menu for the IS-U system, under SAP Utilities Device Management Meter Reading Basic Settings Define Technical Control Parameters for Meter Reading Data Processing. For more information, read the F1 Help and observe the indicator.

Example


45

In the field Propose Interval for Move-In, enter the value 10 and set the indicator. Enter a move-in with a move-in date of January 15. If a final meter reading result already exists for the move-out date January 10, the

system automatically derives a move-in meter reading result from the meter reading result.

If a final meter reading result already exists in the system for the move-out date January 2, the meter reading result is not used to derive the move-in meter reading result.

Note The Customizing settings are dependent upon the company code and division. However, when you create a move-in document they are read to an event, which does not yet generally recognize the company code of the contract (to be created). In this case, the system accesses the table entry with an empty company code key (see OSS note 116173).

6.3 Using Processing Variants

Summary This section informs you how to use the general and specific processing variants to significantly accelerate move-in/out processing. The processing variants allow you, for example, to:

- Display or hide certain dialog boxes,

- Carry out certain actions (for example, creating mandatory move-outs or move-out reversals) in the background (without dialog),

- Allocate the layouts for the move-in and move-out screen that you defined in section 6.1.1, to different user groups.

To do this, go to the Customizing menu for SAP Utilities and select Customer Service Process Execution Move-In/Out and proceed as follows:

Define at least one special processing variant. The special processing variants always relate to a certain action, which you can execute within move-in/out processing. Possible actions are, for example, Create Move-In, Reverse Move-In or Move-In/Out for Premise.

Define at least one general processing variant. The general processing variants always refer to the initial screen for move-in/out processing.

Allocate the general processing variants to user groups.

You can view an example for the processing variants at the end of this section.


46

6.3.1 Special Processing Variants The special processing variants always relate to a certain action, which you can execute within move-in/out processing. Possible actions are: Create move-in Change move-in Display move-in Reverse move-in Create move-out Change move-out Display move-out Reverse move-out Move-in/out for business partner Move-in/out for premise Environment for business partner Environment for premise Create contract change with invoicing Create customer change Reverse customer change Create contract change without invoicing Reverse contract change Remove product allocation

You can also find this list of actions in the drop-down menu for the field OKCODE.

You can define the following parameters for each of these actions: Automatic contract selection for move-out (field Auto cntrt seln)

You can define at what point before the creation of a move-out the user sees the dialog box for contract selection for a move-out, You have the following options:

o No automatic selection (highlight contracts) If more than one contract is found for a premise, you are taken to the Select Contracts for Move-Out dialog box, where you must select the contracts for the move-out. The system highlights the contracts it has found.

o Select all without dialog (except when specifying a contract) All contracts are selected for a specified premise. The dialog box only is only displayed and the corresponding contracts selected when you specify a contract number or a serial number.

o Select all without dialog (individual contract statement, if necessary) As in the previous point, except that the dialog box does not appear even if you specify a contract number or serial number.


47

o Always select all contracts for specified business partner/premise without dialog All contracts for the business partner or premise are selected without a dialog box. This also applies if you only specify one contract.

o No automatic selection (only specified contracts are selected) As in the first option, a dialog box always appears for the contract selection. Only the specified contracts are selected.

Automatic contract selection for mandatory move-out (field Auto cntrt seln) You can define at what point before the creation of a mandatory move-out (see below) the user sees the dialog box for contract selection for move-out.

Automatic installation selection for move-in/out (field Auto cntrt seln) You can define at what point before the creation of a move-in or move-out the user sees the dialog box for installation selection for move-out.

o Always display installation selection list The system selects the installations that belong to the data you have entered.

o Display selection list if system finds more than one installation o Select all installations for a premise, without dialog

If you select this option, the installation selection list is not displayed. o Display installation selection list if specification is incomplete

All installations for a premise are automatically selected if you do not specify an installation, point of delivery, or serial number. When you specify an installation, point of delivery, or serial number, the selection dialog appears if you have not entered all installations for the premise.

Create move-out in background (indicator Move-out in BG) Create mandatory move-out in background (field Mand. m/o in BG)

If you select an installation for a move-in and this installation is already allocated to a contract, you can end this contract with a mandatory move-out. You can define how mandatory move-outs are to be created:

o In the foreground (with dialog) o In the background (automatically, without dialog) o Not at all.

Copy business partners existing contract account (field Copy CA.) You can define whether to copy a business partners existing contract account for the move-in.

Create reversal in background (indicator Reversal BG) You can define whether or not move-in and move-out reversals are to be carried out in the background.

Attempt move-in, even if move-out is not possible (indicator M/I without M/O) You can define whether or not the system should attempt to carry out the move-in


48

part of the move-in/out, even if the move-out part cannot be created. Possible cases for using this action are:

o The move-out has already been entered in the system, but the move-in has not yet been entered. o Individual installations for the premise were never allocated contracts.

Period for displaying data environment (field Display Period) Contract account transfer during contract change (field Cntrt acct chg.)

You can define whether or not a new contract account is to be created during a contract change.

Reasons for contract change (field Reason cont.chg) Reasons for customer change (field CC reason) Document selection list for move-in / move-out (field Document Selection)

If the system only finds one move-in or move-out document, you can define whether you still want the lists for selecting the following documents to be displayed:

o Move-in documents for the function Display / change / reverse move-in, and

o Move-out documents for the function Display / change / reverse move-out Control business partner selection list (field BP Selection)

You can use this action to determine whether or not the business partner selection list is also displayed for the Create Move-In and Move-In/Out for Premise functions if the system was able to use the search data to uniquely determine the business partner.

Layout for move-out processing (field Layout move-out) Use this action to define which layout (see section 6) is used when processing a move-out.

Layout for forced move-out processing (field Mand. m/o in BG) This action enables you to define which layout (see section 6) is used when a forced move-out is processed (forced move-out = a move-out that is entered due to a move-in notification without prior move-out notification).

Invoice reversal in move-in/out (field Invoice rev.) Here, you determine whether or not billing and invoicing documents for the respective contracts are to be automatically reversed in the case of a move-out, move-out reversal or move-in reversal. This function is only available if you have activated the automatic reconciliation key determination. See event 1113 of contract accounts receivable and payable (Sample: Propose document key / reconciliation key).

Note This parameter is not related to the AdjustmentReversal, which can occur when

creating a move-out within a period that has already been billed. You can also find the settings for adjustment reversal during move-out in Customizing for SAP


49

Utilities under Customer Service Process Execution Move-Out Define Move-Out Control Parameters at Contract Level. The field Adj.rev.m/o (adjustment reversal for move-out).

Layout for move-in processing (field Layout move-out)

This action enables you to define which layout (see section 6) is used when a move-in is processed.

6.3.2 General Processing Variants The general processing variants always relate to the initial move-in/out processing screen (transactions EC60, EC50E, EC51E, EC52E, EC53E, EC55E, EC56E, EC57E, EC58E).


50

Figure 11: Initial Processing for Move-In/Out (Transaction EC60)

You can make the following settings: Preassign move-in / move-out date (indicator Date def. value)

You can set the system so that it proposes the current date as the move-in and move-out date move-in/out processing is called from the CIC.


51

Interrupt an action during move-in/out, call from front office (indicator Intrpt act. FO) If you do not set this indicator, the system omits the initial screen for move-in/out processing when it is called from the CIC.

Identify premise (indicator Ident. premise) The system uses the specified search criteria to automatically identify the premise if you select ENTER at the initial screen for move-in/out processing.

Read address for identified premises and business partners (indicator Read addresses) The system automatically determines and displays the address for the identified premises and the business partner who is moving out.

Command to be carried out when Continue is selected (field: Perf. Action) You can determine which action is to be executed when Continue is selected. As a rule, the option Execute last incomplete activity is the most useful.

Action-oriented view when calling from front office (field: Act-Ortd. view) When calling move-in/out processing from the CIC, you can define that only those fields that are used for the action selected in the CIC are visible on the initial screen.

Example Use the method Create for BOR object type MOVEINOUT to call the move-in/out processing from the CIC.

o If you call this method with the parameter OKCODE = CREI (create move-in), no fields for the move-out are visible.

o If you call this method with the parameter OKCODE = UMZB (move-in/out for premise), the group box Determine Installation is omitted from the move-in tab page.

Number of possible premises (field No.of premises) You can define how many tab pages for determining contracts for the move-out, and for determining installations for the move-in are displayed on the initial screen for move-in/out processing.

Contract selection (field PoD Selection) Controls whether the point of delivery is used to select installations for the move-in, or contracts for the move-out.

Structure category for point of delivery ID (field Structure cat.) You can define which structure category is to be used for the point of delivery ID.

6.3.3 Example: Processing Variants User group 1 can carry out the following actions: Create move-in documents


52

Create move-out documents Process move-in/outs for the business partner

Step 1: Special Processing Variants Define a special processing variant, ZSV1 for each of these actions. The Special Processing Variants then contain the following lines:

Figure 12: View for Special Processing Variants


53

When the user creates a move-in, move-out, or move-in/out for a business partner, the system takes into account the settings from the line with the corresponding OKCODE.

The line with the OKCODE Default if no special is used if the user executes a different action for which no line exists.

Step 2: General Processing Variants Define a general processing variant ZGV1 and

H2 ISU Efficiency Cookbook

Documents

Transcript of H2 ISU Efficiency Cookbook