Sap Isu PDF

SAP for Utilities
Release Notes
SAP IS-U 4.72 March 2004
______________________________________________________________ SAP for Utilities Release Notes

SAPNet Version 4.72, March 2004 This version of the release notes may differ from the version provided with the system.
Copyright(c) 2004 SAP AG. All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any form or by any means or translated into another language, without the prior consent of SAP AG. The information contained in this document is subject to change without notice. SAP is a registered trademark of SAP AG. All other products which are mentioned in this documentation are registered or not registered trademarks of their respective companies.
Inhaltsverzeichnis SAP Utilities ______________________________________________________________
1 1.1 1.2 1.3 1.4 1.4.1 1.4.1.1 1.4.1.2 1.4.1.3 1.4.1.4 1.5 1.5.1 1.5.1.1 1.5.1.2 1.5.1.3 1.6 1.6.1 1.6.2 1.6.2.1 1.6.2.2 1.6.2.3 1.6.3 1.6.3.1 1.6.4 1.6.4.1 1.6.4.1.1 1.7 1.7.1 1.7.2 1.7.3 1.7.4 1.7.5 1.7.6 1.7.7 1.7.8 1.7.9 1.7.10 1.7.11 1.7.12
IS-U SAP Utilities Efficient Processes in IS-U/CCS Changes to Implementation Guide (IMG) for Release 4.72 New entries in the Utilities Industry menu for Release 4.72 IS-U-BF Basic Functions IS-U-BF-PS Portioning and scheduling Billing Class/Division Category (Enhanced) Activate all Meter Reading Units for Portion (Enhanced) Create Schedule Records for an Unlimited Time in Advance (Changed) Amount Transfer in Portion Change IS-U-MD Master Data IS-U-MD-POD Point of delivery Authorization Group for Device Information Record (Enhanced) Customer Enhancement for Device Information Record Customer Enhancement for Point of Delivery (Enhanced) IS-U-DM Device Management Permitted Values for Register Codes IS-U-DM-DI Device installation Validation During Device Allocation at Register Level (New) IDocs for Rate Maintenance and Device Allocation (New) Inclusion of Meter Reading Data in Bill Correction (New) IS-U-DM-MR Meter Reading Authorization Check (Enhanced) IS-U-DM-IS Device Inspection IS-U-DM-IS-SL Sampling Procedure Generic Lock for Complilation of Sample Lots IS-U-EDM Energy Data Management Determination of Consumption Factors in Backbilling Managing Day Value Profiles Analyses for Point of Delivery and Service Provider (New) Unit of Measurement in Formula Profiles and RTP Billing (New) Analysis Program: Points of Delivery for Settlement Document (New) Archiving Object ISU_EUFASS (New) Formual Profiles (Enhanced) Analysis Program: Documents for Point of Delivery (New) Profile Header (Enhanced) Profile Value Import (Enhanced) Context for Profile Allocation Role (New) Measurement Units (Enhanced)
1 1 3 5 6 6 6 7 7 7 8 8 8 8 9 9 9 10 10 10 10 11 11 11 11 11 12 12 13 13 14 15 15 17 18 19 19 20 20
______________________________________________________________
SAP AG iii
1.7.13 1.7.14 1.7.15 1.7.16 1.7.17 1.8 1.8.1 1.8.2 1.8.3 1.8.3.1 1.8.3.2 1.8.3.3 1.8.3.3.1 1.8.3.4 1.8.3.4.1 1.8.4 1.8.4.1 1.8.4.2 1.8.4.3 1.8.4.4 1.8.4.4.1 1.8.4.4.2 1.9 1.9.1 1.9.2 1.9.3 1.9.4 1.9.4.1 1.9.4.2 1.9.4.3 1.9.4.4 1.9.5 1.9.5.1 1.9.5.2 1.9.5.3 1.9.5.4 1.10
Profile Roles (Enhanced) Archiving Object ISU_SETTLB (New) Business Add-In for Settlement Unit (New) Wizard for Creating Settlement Parameters (Enhancement) Day Offset Taken Into Account for Synthetic Profiles (New) IS-U-BI Contract Billing New form of cross-installation billing using installation groups Selective Rate Transport IS-U-BI-BD Billing Master Data Implausible Meter Readings for Mass Simulation Authorization Object for Prices IS-U-BI-BD-RS Rate Structure Maintain Billing Schemes: Notes for Schema Steps IS-U-BI-BD-DS Discounts/Surcharges Authorization Object for Discounts or Surcharges IS-U-BI-PC Billing Execution Bill Correction Billing Simulation Scenarios Adjustment Reversal in the Deregulated Scenario IS-U-BI-PC-AU Automatic Billing and Simulation Price Block Adjustment Decimal Places for Meter Reading Results during Proration IS-U-IN Invoicing Changes during a Reversal Grouping Together Partial Bill Document Line Items Procedure for Determining Tax Codes IS-U-IN-PC Invoice Processing Defer Open Items in Invoicing New Customizing Settings for Gross Prices New Functions for the Event: Document Enhancements (R402) New Parallel Processing Object for Bill Reversal IS-U-IN-BB Budget Billing Plan Extrapolation of Budget Billing Amounts Using Meter Readings or Period Consumption Values Amount Transfer in Portion Change Adjustment of Standing Budget Billing Amount in Event R995 New Functions and Enhancements for Budget Billing Plans and Invoicing IS-U-CA Contract Accounts Receivable and
20 21 23 23 23 23 24 25 25 25 25 26 26 26 26 27 27 27 27 28 28 28 29 29 29 30 30 30 31 31 31 32 32 32 33 33
______________________________________________________________
SAP AG iv
1.10.1 1.10.2 1.10.3 1.10.4 1.10.5 1.10.6 1.10.7 1.10.8 1.10.9 1.10.10 1.10.11 1.10.12 1.10.13 1.10.14 1.10.15 1.10.16 1.10.17 1.10.18 1.10.19 1.10.20 1.10.21 1.10.22 1.10.23 1.10.24 1.10.25 1.10.26 1.10.27 1.10.28 1.10.29 1.10.30 1.10.31 1.10.32 1.10.33 1.10.34 1.10.35 1.10.36 1.10.37
Payable Account Balance Display Archiving for Tax Reporting Argentina (Changed) Archiving Authorization Objects BAPIs in Contract Accounts Receivable and Payable Boletos Business Information Warehouse Cash Desk Cash Journal Closing operations Submission of Receivables to Collection Agencies Collective Bills Company Codes Generation of Correspondence Connecting SAP Dispute Management to Contract Accts. Rec. and Payable Dunning Enhanced Message Management New and Modified Events Conversion of Finnish Bank Statement to MultiCash (Enhanced) Foreign Currency Valuation Funds Management IDoc Interfaces for Communication with External Billing Systems Modified IMG Activities in Contract Accounts Receivable and Payable New IMG Activities in Contract Accounts Re Payable Information System Deferral and Installment Plan Integration Interest Calculation Business Locks Mass Activities Master Data Evaluation of Open Items Processing Incoming and Outgoing Payments Payment Transactions Collections in the Print Workbench Postings and Documents Prenotifications
34 34 35 35 36 37 38 39 40 41 42 42 43 44 46 47 50 51 52 55 55 56 59 60 61 63 65 66 67 68 68 69 70 70 72 74 74 79
______________________________________________________________
SAP AG v
1.10.38 1.10.39 1.10.40 1.10.41 1.10.42 1.10.43 1.10.44 1.10.45 1.11 1.11.1 1.11.2 1.11.2.1 1.11.2.2 1.11.2.3 1.11.2.4 1.11.3 1.11.3.1 1.11.3.1.1 1.11.3.1.2 1.12 1.12.1 1.12.1.1 1.13 1.13.1 1.13.1.1 1.13.1.2 1.13.1.3 1.13.1.4 1.13.1.5 1.13.1.6 1.13.1.7 1.13.1.8 1.13.1.9 1.13.1.10 1.13.1.11 1.13.2 1.13.2.1
New Reports Requests Processing Returns Connecting the Schedule Manager in Contract Accounts Receivable and Payable Stop Future Payment (Denmark) Tax Reporting in Contract Accounting (New) Write-Offs Generic Withholding Tax Reporting (Enhanced) IS-U-CS Customer Service Waste Disposal-Specific CIC Configuration IS-U-CS-FO Front Office Enhanced data environment in the CIC customer environment Permanent Hit List Layout Switching for the Customer Interaction Center Changes to the Customer Interaction Center, CIC IS-U-CS-BT Process Execution IS-U-CS-BT-DR Installation Disconnection/Reconnection Accelerated Move-In / Move-Out / Move-In/Out Entry BAdI ISU_SERVORD_EDCN IS-U-WM Work Management IS-U-WM-MB Work Management Mobile Business Mobile Asset Management for Utilities IS-U-WA Waste Management IS-U-WA-MD Master Data Archiving for Route and Waste Disposal Order Objects New Functions in Property Maintenance Changed Billing for Charge Assessment Waste Disposal-Specific CIC Configuration Enhancements for the waste disposal order Improvements in Cleaning Object Maintenance Enhancement for Route Integration of SAP Waste and Recycling with Sales and Distribution (SD) Enhancements to Service Frequency Improvements to Container Location Management Waste Disposal Installation Creation IS-U-WA-PC Processing General Cargo Entry at Waste Disposal Installation
80 80 82 83 84 84 84 85 85 85 85 85 86 87 88 89 89 89 90 90 90 90 91 91 91 92 93 93 94 95 96
98 99 100 100 100
______________________________________________________________
SAP AG vi
1.13.2.2 1.13.3 1.13.3.1 1.14 1.14.1 1.14.2 1.14.3 1.14.4 1.14.5 1.14.6 1.14.7 1.14.8 1.14.9 1.14.10 1.14.11 1.15 1.15.1 1.15.1.1
Create and Process Weighing Procedures IS-U-WA-IF Interfaces Hardware Configuration at Waste Disposal Installation Entrance / Exit IS-U-IDE Intercompany Data Exchange Authorization Check for Point of Delivery (New) Adjustment Reversal in the Deregulated Scenario Data Exchange Processes for Master Data Changes (New) Definition and Consistency Check for Deregulation Processes (Enhanced) Framework for Outgoing Data Exchange Processes (Enhanced) Definition of Check Parameters in Customizing (New) Manual Billing in the Deregulated Scenario (New) ID Type in Customizing (neu) Service Provider (Enhanced) Hide Subprocesses (New) BAdI for Checking User Input (New) IS-U-TO Tools IS-U-TO-ARC Archiving Archiving for Route and Waste Disposal Order Objects
101 101 102 102 102 103 103 106 106 108 108 108 109 109 110 110 110 110
______________________________________________________________
SAP AG vii
SAP Utilities ______________________________________________________________
1 IS-U
SAP Utilities
1.1 Efficient Processes in IS-U/CCS

Use A large number of new developments have been shipped as part of the Increased Efficiency Project in IS-U/CCS. These developments improve the efficiency of frequently used mass dialog processes. New or enhanced functions are now available in the following areas: Master data: o o You can now use the new Maintain Bank Data transaction (FPP4). You can hide fields that you do not require in the Customizing settings for master data objects in IS-U/CCS. In addition to this, you can also define required entry fields or select fields to be displayed only.
Meter Reading: o o o o You can now display the previous meter reading result on the entry screen. Premise has been added to the selection criteria in the transaction Monitoring Meter Reading Data (EL31) The parameter Premise has been added to method MeterReadingDocument.MeterReadingDisplay from object type MTRREADDOC. You can now also display a business partner's name in the list of meter reading results or meter reading orders.
Billing: o o You can now use Selective Rate Transport . You can also now use the Price Information (ISU_PRICE_INFO) function module to provide your customers with the latest price information, for example in the Customer Interaction Center or a welcome letter. You can Correct Bills. New simulation forms have been added to the transactions Mass Activity: Billing Simulation (EA39) and Mass Simulation via Installation Intervals (EAMASI).
o o
Invoicing: o o o o The Express Transaction: Change Budget Billing Amount (EA61EX) optimizes the way you work with budget billing plans. A number of changes have been made to this transaction When you invoice a billing document you can now clear the next or first budget billing plan item when you use the Partial Bill Procedure as the budget billing procedure. Several enhancements have been made to the Reversal Functions. The billing key date enables you to allocate a single billing key date to a billing document and the resulting print documents. You can group together billing documents that have the same billing key
______________________________________________________________
SAP AG 1
SAP Utilities ______________________________________________________________
date. o o o You can now also print existing budget billing plans and payment plans in display mode. In bill printout, you can now sort print documents using different criteria, for example, street route. There are now two reports that enable you to find contracts that have not been billed for a long time and also identify contract accounts for which a budget billing plan has not been created for a long time.
Contract Accounts Receivable and Payable: o o You can now use the Account Balance Display. Previously, you could display the name and address of a business partner in the evaluation report: Evaluate Open Items. Now, you can also do this with the following reports: Display installment plan history Display security deposit Display dunning history
Customer service: o The Accel. Move-In / Move-Out / Move-In/Out (EC70) transaction helps you optimize the processing of move-ins, move-outs and move-in/move-outs. This transaction has been enhanced in several ways The following functions are also available in the transaction Accel. Move-In / Move-Out / Move-In/Out: o Error Processing Monitoring parked documents
You can now enter interim meter readings in rate maintenance. The meter reading is entered on the day before the installation from-date. Entering interim meter readings is optional, and takes place in a subscreen.
Customer Interaction Center o o General changes The business partner search now has a new function. This function means that the search does not use individual value entries in the corresponding search fields. Instead it uses a general search string within the search parameters of the IS-U Data Finder. You can now set up a permanent hit list for the business partner search. Further new functions for the business partner search include: o See also For further information on these and other functions that increase efficiency when using our product, read the Cookbook Incr. Efficiency IS-U/CCS - New Developments. You can download this from the Service A general search string in the IS-U Data Finder search parameters. Screen variants in the CIC Framework Customizing.
The Customer Overview has been enhanced.
______________________________________________________________
SAP AG 2
SAP Utilities ______________________________________________________________
Market Place under service.sap.com/utilities. Select Product Information -> IS-U/CCS -> General -> Cookbooks&Guidelines.
1.2 Changes to Implementation Guide (IMG) for Release 4.72

Use As of SAP Utilities Release 4.72, changes have been made to the structure of the following areas in SAP Utilities. You must regenerate the project IMGs if you want these changes to be included. o Master Data Under Basic Settings, the functional location Area from the Waste Management component has been added to the activity Define Structure Indicator and Category of Functional Locations.
Device Management Technology The activity Define Permitted Values for Register Code has been added to the Register Group.
Energy Data Management The activity Define Units of Measurement for Division Category/Profile Value Category has been added to Profile Management. The node Profile Allocation has also been added. The activity Define Roles for Profile Allocation is allocated to this node.
Contract Billing The activity Maintain Bill Correction Control has been added to Billing Execution.
Invoicing The activity Define Tax Determination Procedure for Each Company Code Group has been added to Basic Settings. The activities Override Application Form for Bill Simulation and Define Criteria for Grouping Partial Bill Items have been added to Bill Printout. The complete Budget Billing Plan section has been restructured.
Contract Accounts Receivable and Payable Basic Functions The activity Define Different Accounts for Consumption Shares from Previous Years (IS-U) has been added to Postings and Documents under Document -> Define Account Assignments for Automatic Postings -> Automatic G/L Account Determination.
Customer Service The activities Set Time-Delayed Restart in IS-U Error Monitor and Maintain Message Table for Time-Delayed Restart in IS-U Error Monitor have been added to Process
______________________________________________________________
SAP AG 3
SAP Utilities ______________________________________________________________
Execution under Move-In/Out -> Fast Data Entry and under the "CRM Integration" node. o Work Management o The complete section on Mobile Asset Management for Utilities has been added to Work Management.
Waste Management The activities SD Integration and Define Period Control for Selections have been added to Basic Settings. The following activities have been added to Master Data: Under Property, the activities Define Number Ranges for Technical Locations for a Property and Field Selection Control for Property Address Data. Under Service Frequency, the activity Activate Incompleteness Check for Service Frequency. Under Billing, the activities Consistency Check for Waste-Disposal-Specific Billing Data and Define Scheduling for Charge Assessment. The activity Define User Status has been added to Processing of Waste Disposal Orders. The complete Waste Disposal Installations section has been added to Waste Management.
Information System The Process Statistics section has been added to the Business Information Warehouse section under Settings for Application-Specific DataSources (PI) -> Utilities Industry.
Intercompany Data Exchange The following activities have been added to Bill and Payment Advice Note Processing: Define Process Control (Part 2) The name of the existing activity Define Process Control has been changed to Define Process Control (Part 1). Define ID for Bill and Payment Advice Note Parts Define Check Parameters
Tools Archiving The functions Activate Info Structure for Prepayment Documents, Activate Archive Info Structure for Waste Disposal Order and Route have been added to the activity Activate Info Structure for Archiving. The activity Define Control Parameters for Archiving has been added to Archiving. System Modifications The Analyses node and the activity Analysis Function for Deregulation have been added to the section User-Defined Enhancements for Energy Data Management. The activity Define Field Check has been added to User-Defined Enhancements for IDE under Change of Supplier -> Message Data. The node Bill and Payment Advice Note Processing has been added. This contains the Define Identification Systems activity.
______________________________________________________________
SAP AG 4
SAP Utilities ______________________________________________________________
1.3 New entries in the Utilities Industry menu for Release 4.72
Use The following transactions have been added to the SAP Menu: o Business Master Data: Business Partner: -> Maintain Bank Data (FPP4) -> Enter Registration ID (DK) (FPDKCPR)
Contract Accounts Receivable and Payable: Account: -> Further Information -> Clarification Case for Account Balance (FPDM00) Payments: -> Cash Journal -> Cash Journal Evaluation (FPCJR) -> Payment Run -> Enter Registration ID (DK) (FPDKCPR) -> External Payment Banks -> Clarification of Transferred Payments (FPCVS) Standing Request: -> Approve Request (FKKORDA) Periodic Processing: -> For Contract Accounts -> Boleto -> Mass Run (FB01) -> For Contract Accounts -> Boleto -> Single Generation (FBO1S) -> For Contract Accounts -> Boleto -> Mass Reversal (FBO1C) -> For Contract Accounts -> Reversal of Check Payments (FPCHS) -> For Contract Accounts -> Dunning Notice -> Forward Telephone List (FPVT) -> For Contract Accounts -> Set Processing Locks (FKLOCK2) -> For Contract Accounts -> Delete Processing Locks (FPLKDEL)
-> Forward Postings -> Preparation -> Recreate Totals Records (FPT6) (moved from Tools -> Delete -> Contract Accounts Receivable and Payable -> Totals Records (FPT6)) -> Forward Postings -> Execution -> Cash Management Transfer (FPCF) -> Closing Preparation -> Reverse Foreign Currency Preparation (FPW2) -> Correction Postings: The sequence of the Correction Posting and Closing Preparation nodes has been changed in the menu so that the Closing Postings node is displayed first followed by the Correction Postings node in the menu. -> Evaluation of Open Items -> Evaluate (Parallel Processing) (FPO4P) -> Extraction for Business Information Warehouse -> Extract Installment Plans (FPIPBW) o Administration: -> Create Search Index for Archived Payment Lot (FP05ARC)
Tools Administration Mass Processing: -> Schedule Mass Activity (FPSCHEDULER) -> Enhanced Message Management -> Display Clarification List (EMMACL)
______________________________________________________________
SAP AG 5
SAP Utilities ______________________________________________________________
-> Enhanced Message Management -> Clarification List With Shortcut (EMMACLS) -> Enhanced Message Management -> Clarification with Automatic Processes (EMMACAP) -> Enhanced Message Management -> Creation of Clarification Cases in Mass Run (FPEMMACGEN) Administration of Customer Portal: -> Customer Messages Worklist (IQS8) -> Create Customer Notifications (FPACTEN) Transfer Data to SAP Credit Management: -> Transfer Credit Data (FPCM1) -> Replicate Creditworthiness (FPCM2) Data Archiving: -> Contract Accounts Receivable and Payable -> Foreign Currency Valuation (FPAR09) -> Contract Accounts Receivable and Payable -> Clearing History (FPAR10) -> Contract Accounts Receivable and Payable -> Doubtful Entries (FPAR11) -> Contract Accounts Receivable and Payable -> Invoice Creation by Third Party (FPAR12) Delete: -> Contract Accounts Receivable and Payable -> Totals Records (After Document Archiving) (FPARS1) -> Contract Accounts Receivable and Payable -> Logs of Submission for Collection (FP03DML) -> Contract Accounts Receivable and Payable -> Entries in Dunning Telephone List (FPVT1)
1.4 IS-U-BF
1.4.1 IS-U-BF-PS
Basic Functions
Portioning and scheduling
1.4.1.1 Billing Class/Division Category (Enhanced)

Use As of SAP Utilities Release 4.72, you can enter any number of billing class and division category combinations in the portion and meter reading unit. Previously, you could only enter a maximum of 5 combinations. This restriction no longer applies. Table TE420AS has been created for billing classes and division categories for the portion. This contains the combinations for each portion. Table TE422AS has been created for billing classes and division categories for the meter reading unit. This contains the combinations for every meter reading unit.
______________________________________________________________
SAP AG 6
SAP Utilities ______________________________________________________________
Effects on Existing Data An XPRA transfers the data in the system to the new tables. Further user action is not required.
1.4.1.2 Activate all Meter Reading Units for Portion (Enhanced)

Use You can now activate all meter reading units of a portion using transaction E43E. You can find this transaction in the Utilities Industry menu under Scheduling -> Environment. When you change a portion, you no longer have to call and activate each meter reading unit individually. Once the program Activate all Meter Reading Units of a Portion is complete, the messages are displayed in the IS-U log. Only meter reading units that do not have schedule records are activated. If schedule records do exist for a meter reading unit, you must continue to update these using transaction E41G (Change Meter Reading Unit). See also For further information, see the program documentation.
1.4.1.3 Create Schedule Records for an Unlimited Time in Advance (Changed)

Use You can now generate schedule records more than seven years in advance. To do this, you must define a corresponding upper limit for schedule records in the Customizing activity Define Control Parameters for Scheduling. The Customizing activity Define Control Parameters for Scheduling contains the fields Warning Limits for Schedule Records and Upper Limit for Schedule Records: o If you execeed the value in the Warning Limit for Schedule Records field when you generate the schedule records, a dialog window appears. You can then decide either to continue using the entries you have made, or cancel processing. A value is not set as a default in the warning limit field. The value in the Upper Limit for Schedule Records field displays the maximum number of years in advance for which you can generate schedule records. This field contains 7 years as a default value.
Effects on Customizing SAP Utilities Customizing menu under Basic Functions -> Portioning and Sceduling -> Define Control Parameters for Scheduling.
______________________________________________________________
SAP AG 7
SAP Utilities ______________________________________________________________
1.4.1.4 Amount Transfer in Portion Change

Use As of SAP Utilities Release 4.72, you can specify in transaction EA65 ( Adjust Budget Billing Plans to Changed Billing Dates) whether a new budget billing plan is created using extrapolation or by transferring previous amounts. Previously, you could only select extrapolation. Effects on Customizing In event R923 (Amount Transfer in Portion Change), you can change the default data that is transferred from the previous budget billing plan. To do this, create your own function module and enter it in Customizing in the Define Customer-Specific Function Modules activity. You can now use a new indicator in Define Control Parameters to define whether extrapolation is called during a cycle change, or whether the data from the previous budget billing plan is used. See also For further information about this transaction, see the online documentation Adjustment of Budget Billing Plans to New Billing Dates .
1.5 IS-U-MD
1.5.1 IS-U-MD-POD
Master Data
Point of delivery
1.5.1.1 Authorization Group for Device Information Record (Enhanced)

Use As of SAP Utilities Release 4.72, device info records have an authorization group (as do the normal PM devices). As a result, you can also perform enhanced authorization checks for this object. Effects on Customizing You make the necessary settings in Customizing for Plant Maintenance and Customer Service -> Master Data in Plant Maintenance and Customer Data -> Technical Objects -> General Data ->Define Authorization Groups.
1.5.1.2 Customer Enhancement for Device Information Record

Use As of SAP Utilities Release 4.72, the device info record contains more customer-defined fields.
______________________________________________________________
SAP AG 8
SAP Utilities ______________________________________________________________
You can use Business Add-In (BAdI) ISU_EGERR_CUSTOMER, customer include CI_EGERR, you can create customer-defined fields and display them on a special subscreen in the device information record. See also BADI ISU_EGERR_CUSTOMER
1.5.1.3 Customer Enhancement for Point of Delivery (Enhanced)

Use As of SAP Utilities 4.72, you can enter further customer-specific fields for the point of delivery. With business add-in ISU_EDM_POD_CUSTOMER, you can use customer include CI_EUIHEAD to create user-defined fields and display them on a special subscreen in the point of delivery. See also BADI ISU_EDM_POD_CUSTOMER
1.6 IS-U-DM
Device Management
1.6.1 Permitted Values for Register Codes

Use You can find the Register Code field at register level. Previously you could enter any value in this field. As of SAP Utilities Release 4.72, you can specify in Customizing that only certain values are permitted as register codes (EDIS codes, for example). These settings are dependent on the division category. In the following transactions, the system checks whether the entered values are permitted based on the Customizing settings: o o o Device Installation Device Modification Register Group Maintenance
Effects on Data Transfer A help report uses the existing register codes to enter the permitted values in a Customizing table: REG_TEKENNZIFF_XPRA Effects on Customizing You can define the permitted values for register codes in Customizing for SAP Utilities under Device Management -> Technology -> Register Group -> Define Permitted Values for Register Codes.
______________________________________________________________
SAP AG 9
SAP Utilities ______________________________________________________________
1.6.2 IS-U-DM-DI
Device installation
1.6.2.1 Validation During Device Allocation at Register Level (New)

Use As of SAP Utilities Release 4.72, the following validations are performed at register level during device allocation: o o For transformer allocation, only the register belonging to division category Electricity is permitted For pressure regulator allocation, only the register belonging to division category Gas, Water, Waste Water, and District Heating is permitted
1.6.2.2 IDocs for Rate Maintenance and Device Allocation (New)

Use As of SAP Utilities Release 4.72, the data for releasing IDocs (intermediate documents) during rate maintenance and device allocation is collected and sent when you save the data.
1.6.2.3 Inclusion of Meter Reading Data in Bill Correction (New)

Use As of SAP Utilities Release 4.72, you can process meter reading data directly in the Bill Correction transaction (EABICO). The data is displayed in an ALV grid control. All meter reading results, including those that lie in the future, are displayed for the billing documents that you select. The following functions are available: o CREATE You can now create a control reading or an interim meter reading with or without billing. You can set the default values (Control, Interim) in Customizing. If you need to change the meter reading reason, you can overwrite the entry in the ALV grid control. If you select the incorrect meter reading and choose Create, a corresponding meter reading order is created. If it is a control reading, the incorrect meter reading is automatically estimated as a result of the newly entered value. CORRECTION You can now correct the meter reading results. RELEASE You can now manually release an implausible meter reading result.
o o
______________________________________________________________
SAP AG 10
SAP Utilities ______________________________________________________________
o o
ESTIMATE You can now estimate a meter reading result. RESET You can now reset the data to its original state.
Effects on Customizing Controling Bill Correction
1.6.3 IS-U-DM-MR
Meter Reading
1.6.3.1 Authorization Check (Enhanced)

Use As of SAP Utilities Release 4.72, there is a new authorization object (E_MR_DOC2) in meter reading that also checks the company code. If you use the one-client model for deregulation, you can define authorizations that support the processing of supplier and distibutor data. In addition, the following transactions are new in the authorization check for meter readings: o o o Order Creation (EL01) Meter Reading Result Estimation (EL30) Monitoring of Meter Reading Data (EL31)
Previously, the authorization check was available for the following transactions: o o o o Single Entry (EL28) Fast Entry Without/With Correction (EL20, EL22) Correction of Plausible/Implausible Meter Reading Results (EL27, EL29) Reversal of Meter Reading Results (EL37)
A BAdI with method EL31_CHECK_SELOPTIONS has also been created. As a result, you can specific that the Monitoring of Meter Reading Data transaction (EL31) terminates if the amount of data selected is too large. This prevents unnecessary timeouts, which can occur if you make an error when entering data.
1.6.4 IS-U-DM-IS 1.6.4.1 IS-U-DM-IS-SL
Device Inspection Sampling Procedure
1.6.4.1.1 Generic Lock for Complilation of Sample Lots
______________________________________________________________
SAP AG 11
SAP Utilities ______________________________________________________________
Use As of SAP Utilities Release 4.72, you can choose how to lock the lot device when compiling sample lots in the Compile Lot - Background Processing transaction (EG8A). You have the following options: o Lock devices individually Every device included in the sample lot is locked individually (if possible). If there are a large number of devices in the lot, this method can take a long time and can lead to problems with the size of the lock table. Generic lock of all devices and pieces of equipment All devices in the relevant client are locked. If this is not immediately possible, the system waits before trying again. You can choose how many times you want the system to retry setting the lock. The devices are locked very quickly in this method because only one lock is used.
If the lot is small or medium-sized, it makes sense to lock the devices individually. If the lot is large, you have the option to call the transaction several times in succession thus reducing the number of devices in each run. Alternatively, you can use the generic lock method. If you decide to use this method, it is important to take the following points into account: o The generic lock of devices and equipment means that you cannot make any changes to devices or pieces of equipment in the relevant client until the device data has been changed. The time involved depends on the number of devices in the lot and on the performance of the database. You can only set the generic lock if no devices are already locked. We recommend that you only use the generic lock at times when no other users need to access the system.
o o
1.7 IS-U-EDM
Energy Data Management
1.7.1 Determination of Consumption Factors in Backbilling

Use As of SAP Utilities Release 4.72, you can determine consumption factors for a (dynamic) backbilling period. In order to do this, you have to implement the Time Slices for Consumption Factor BAdI (ISU_BI_USAGE_FACTOR). You must also write a variant that provides you with non-aggregated consumption factors. This variant must work analog to variant QUANTI24. If you enter a backbilling group for a schema step that determines consumption factors, the system corrects the consumption factors that were determined in previous documents. However, if you reverse the document created during backbilling, the system reverts back to the status before billing. You can also make other changes in the internal table of consumption factors created by your variant (or variant QUANTI24). Effects on Existing Data Consumption factors created by variant QUANTI24 are normally aggregated from all schema steps for each operand. If consumption time slices are not located within the billing period, billing terminates with
______________________________________________________________
SAP AG 12
SAP Utilities ______________________________________________________________
an error. If you want to determine consumption factors for (dynamic) backbilling, use the BAdI ISU_BI_USAGE_FACTOR to switch off the period checks. Read the BAdI's example coding to do this. Existing consumption factors are not influenced by the new function. You can only use a reversal to restore previous consumption factors if billing was executed with Release IS-U/CCS 4.72. Effects on System Administration Use BAdI ISU_BI_USAGE_FACTOR to implement your own logic. For more information, see the documentation on this BAdI.
1.7.2 Managing Day Value Profiles

Use As of SAP Utilities 4.72, you can manage day value profiles in Energy Data Management. o o o Each day has exactly one value The value is always entered at the time of the day offset A value exists for every day
Restrictions: o o o o o o o o It is not possible to enter multiple values for a day It is not possible to enter a value for a time that is different to the day offset in the profile header It is not possible to convert the interval length when you open the profile In formula calculation, only use formulas that are compatible with day value profiles In formula calculation, only use day value profiles that have the same day offset If one of the input parameters or output parameters of a formula is a day value profile, all other input and output parameters also have to be day value profiles In RTP billing, no functions are permitted to split a day (for example, no separation into on-peak times (08:00:00-19:59:59) and off-peak times (20:00:00-07:59:59)) The DataSource (0UC_EDM_01) does not use day value profiles
Effects on Existing Data This does not affect existing data. See also Enhancements to Profile Value Import Enhancements to Formula Profiles
______________________________________________________________
SAP AG 13
SAP Utilities ______________________________________________________________
1.7.3 Analyses for Point of Delivery and Service Provider (New)

Use As of SAP Utilities Release 4.72, you can perform analyses for the following data: o Service provider o Data exchange Change of supplier
Point of delivery Services and contracts Supply scenarios Settlement units Data exchange Change of supplier
You use the Analyses for Point of Delviery and Service Provider program to evaluate existing data. It does not create any new data or change existing data. You can find the program in the Utilities Industry menu under Intercompany Data Exchange -> Utilities. Effects on Data Transfer The program run time depends on the size of the dataset and on the maximum number of hits for each selection.
1.7.4 Unit of Measurement in Formula Profiles and RTP Billing (New)

Use As of SAP Utilities 4.72, you can enter a dimension and a unit of measurement when you create a formula for input and output parameters. If you enter a dimension, the following checks take place for each dimension when you allocate profiles to a formula profile and when you execute the RTP interface: o o o The units of measurement for all input profiles of a profile value category must be the same. The units of measurement for all output profiles of a profile value category must be the same. The units of measurement for all input profiles of a profile value category must be transferable to the target unit of measurement - it must have the same dimension.
If you enter a unit of measurement in addition to the dimension, no checks are made for the corresponding parameters.
______________________________________________________________
SAP AG 14
SAP Utilities ______________________________________________________________
Effects on Existing Data Adapt the formulas for which less stringent unit of measurement checks are to be performed. If you carry out a thermal gas conversion in Energy Data Management, you must enter a dimension and a unit of measurement for the parameters in the formula. The influencing factors such as temperature, pressure, calorific value, and so on are defined as profiles belonging to profile value category Factor. However, the measurement units are different. The measured quantity has the dimension Volume, whereas the unmeasured quantity has the dimension Energy. As a result, it is not possible to create a formula profile that processes the above mentioned gas factors correctly without the new Dimension and Unit of Measurement fields. Effects on Customizing The Dimension and Unit of Measurement fields have been added to the input and output parameters in the formula definition. The following rules apply for creating a formula: o o See also The formula GAS01 now exists for the thermal gas conversion in Energy Data Management (add reference to function module ISU_EDM_FORMULA_0019). If you enter a dimension for one parameter in a formula, you must also enter a dimension for all input and output parameters of that formula. If you enter a unit of measurement within a dimension for one parameter in the formula definition, you must also enter measurement units for all parameters of that dimension.
1.7.5 Analysis Program: Points of Delivery for Settlement Document (New)

Use As of SAP Utilities Release 4.72, an analysis program exists which allows you to display the points of delivery for settlement documents. You can find the program in the SAP Menu under Utilities Industry -> Energy Data Management -> Settlement -> Analyses for Settlement -> Points of Delivery for Settlement Document.
1.7.6 Archiving Object ISU_EUFASS (New)

Use As of SAP Utilities Release 4.72, when profile allocations and usage factors are archived, the data is written to one or more archive files. You use archiving object ISU_EUFASS to archive data from the following tables: o o ELPASS: Profile allocations for installation EUFASS: Usage factors for installation
______________________________________________________________
SAP AG 15
SAP Utilities ______________________________________________________________
EUFASS_HIST: Usage factors for installation (historical)
Checks The following conditions must be fulfilled to ensure that only profile allocations and usage factors that are no longer needed are archived: o o The profile allocations and usage factors must lie within the specified range of the object key and the reference object type. The retention period of the profile allocations and usage factors must have expired. You can define the retention periods for profile allocations and usage factors separately. However, the retention period for the profile allocations must always be longer than that for the usage factors. You define retention periods in Customizing.
In a subsequent analysis process you can define your own checks to determine the achivability of settlement documents thus making further restrictions. For more information, see the documentation for BAdI ISU_EDM_EUFASSARCHIV and method ANALYSE_EUFASS. Effects on Existing Data Once you have executed the deletion report, all profile allocations and usage factors (based on the archive created beforehand) are deleted from the database. Function and report allocation o Analyze, Archive Analysis of profile allocations and usage factors with regard to possible archiving. Archiving of relevant profile allocations and usage factors. Display Reads archives for profile allocations and usage factors and issues parts of data in a list. Delete Deletes profile allocations and usage factors from the databased based on the previously created archive. Reload Reloads deleted profile allocations and usage factors that you have archived. Only use this function if it is absolutely necessary.
o o
Display individual profile allocations and usage factors Using the standard business view for object ISU_EUFASS, it is possible to display archived profile allocations and usage factors individually by means of the archive information system (SAP AS). The information structure provided by SAP (SAP_ISU_EUFASS) contains the following fields: o o o OBJKEY Object key OBJTYPE Reference object type LOGLPRELNO
______________________________________________________________
SAP AG 16
SAP Utilities ______________________________________________________________
Logical number of the load profile allocation o o o BIS Date until which a time slice is valid ARCH_AB From-date of the last archiving ARCH_BIS To-date of the last archiving
You can display the information structure in transaction ESARJ09. You can display individual profile allocations and corresponding usage factors from the archive. You do this using the Display Installation transaction, which you can find in the SAP Menu under Utilities Industry -> Technical Master Data -> Installation -> Display . The system can only find profile allocations and corresponding usage factors that are included in the archive index.
Effects on Customizing You can define time-related conditions for archiving in Customizing. You can define a minimum retention period in the system for each profile allocation and usage factor. The retention period for profile allocations must always be longer than that for usage factors. SAP Utilities -> Tools -> Archiving -> Define Retention Period for Archiving Objects
1.7.7 Formual Profiles (Enhanced)

Use Allocation of Documentation to Formulas in the Formula Definition Before SAP Utilities Release 4.72, you could call function module-specific documentation in the formula definition (Customizing forSAP Utilities under Tools -> System Modifications -> User-Defined Enhancements for Energy Data Management -> Formulas -> Define Formula). The formula definition is a characteristic of the formula. You can now create your own documentation for the formula definition. You can then also call the documentation in the profile header (transactions EEDM06, EEDM07, EEDM08). Enhancement to the Where-Used List in the Formula Definition Before SAP Utilities Release 4.72, you could display a where-used list for formula definitions. The former where-used list specified where the formula is used in the RTP interface. However, since the formula definition is also used for calculating formula profiles, you can now call an additional where-used list specifying the allocation of formulas in the formala calculation.
______________________________________________________________
SAP AG 17
SAP Utilities ______________________________________________________________
Automatic Creation and Change of Formula Allocations You can have profile headers created or changed automatically for mass processes (in the background without using the Create/Change Profile Header transactions). Before SAP Utilities Release 4.72, this was not possible for profiles belonging to the Formula Profile profile category. The following service function modules are now available, which allow you to have complete formula allocations created or changed automatically: o o ISU_S_FORMINST_CREATE ISU_S_FORMINST_CHANGE
Update of Elementary Profiles During Calculation Before SAP Utilities Release 4.72, you could not generate a synthetic profile with a formula profile (output profile). You can now generate an elementary profile in parallel to an output profile (profile copy). As a prerequisite, you must have entered the profile type for the copy in the relevant formula definition. All user-defined profile types are offered for selection in the formula definition (Customizing for SAP Utilities under Tools -> System Modifications -> User-Defined Enhancements for Energy Data Management -> Formulas -> Define Formula). When you select a profile type, the output profiles in the formula allocation contain two additional fields: Create Profile Copy and Profile Number of Profile Copy. If you select the Create Profile Copy field and save the formula allocation, an elementary profile is created automatically. The profile header entries are the same as those in the output profile. The new profile only belongs to a different profile category. The generated profile number is displayed in the Profile Number of Profile Copy field. When you perform a formula profile calculation, all profiles including the profile value status are copied to the profile copy. In the profile copy header, the profile number of the source profile is displayed in the new Source Profile field. You cannot change the profile values or the status of the profile copy. If you double click on the profile number on the formula allocation, you can branch to the profile value display by means of the calendar function. If values have already been calculated for the formula profile (in this case, the field for the profile copy is selected later on or it has beendeactivated), the profile copy is updated with the calculated values so that the formula profile and the profile copy are consistent. This action can take quite a long time. If there are more than three months worth of values that need updating, you must confirm via a dialog box whether you want the alignment between the two profiles to take place.
Calculation of Day Value Profiles You can calculate day value profiles using day offsets (for example, gas day).
______________________________________________________________
SAP AG 18
SAP Utilities ______________________________________________________________
1.7.8 Analysis Program: Documents for Point of Delivery (New)

Use As SAP Utilities Release 4.72, an analysis program exists which allows you to display documents for the point of delivery. You can find the program in the SAP menu under Utilities Industry -> Energy Data Management -> Settlement -> Analysis for Settlement -> Display Documents for Point of Delivery.
1.7.9 Profile Header (Enhanced)

Use As of SAP Utilities Release 4.72, business add-in ISU_EDM_PROFHEAD allows you to display a number of additional fields by choosing a new tab page in the profile header.
See also BADI ISU_EDM_PROFHEAD
1.7.10 Profile Value Import (Enhanced)

Use Enhancement to the Selection Options when Monitoring Profile Value Import When you call BAPIs BAPI_ISUPROFILE_IMPORT and BAPI_ISUPROFILE_UPLOAD, you can use parameter UPLOADINFO to include an external reference. As of SAP Utilities Release 4.72, you can use this external reference for selection purposes in monitoring for profile value import (transaction EDM1). If the profile value import is based on the point of delivery ID, the PoD ID is also included in the display. As of SAP Utilities Release 4.72, you can use the point of delivery ID for selection purposes in monitoring for profile value import (transaction EDM1). Once you have made a selection, you can double click on the point of delivery ID to branch to the point of delivery display (transaction EEDM11). Import of Day Value Profiles As of SAP Utilities Release 4.72, you can import day value profiles with a day offset (for example, gas day). See also Managing Day Value Profiles
______________________________________________________________
SAP AG 19
SAP Utilities ______________________________________________________________
1.7.11 Context for Profile Allocation Role (New)

Use As of SAP Utilities 4.72, you can select additional information as context as well as the role for a profile allocation in the profile allocation transaction. In the settlement procedure, the context for a profile allocation is used to uniquely determine the settlement parameter. The following context categories existed before SAP Utilities 4.72: o o o Settlement unit Supply grid Settlement procedure
Now you can define additional context categories in Customizing. Effects on Customizing You can define context categories in Customizing in addition to those predefined by SAP. Define Context for Profile Allocation
1.7.12 Measurement Units (Enhanced)

Use Previously, all measurement units were displayed for their corresponding divisions and profile value categories. As of SAP Utilities Release 4.72, you can influence the search help for the meter reading measurement units in the profile header transactions (EEDM06, EEDM07, EEDM08). Also, the relevant measurement units are displayed as default values based on division and profile value category. You can define your own values in Cutomizing in addition to the standard entries. To fo this, enter a division, a profile value category, and a dimension. Effects on Customizing You make the necessary settings under Define Measurement Units for Division/Profile Value Category.
1.7.13 Profile Roles (Enhanced)

Use As of SAP Utilities 4.72, you can specify in Customizing that profiles that belong to a specific role can no longer be changed once they have been billed. Previously, this restriction was predefined by SAP and was limited to certain profile role categories
______________________________________________________________
SAP AG 20
SAP Utilities ______________________________________________________________
(Reading and Forecasting). Effects on Customizing You can find the new field in Customizing for SAP Utilities under Energy Data Management -> Profile Management -> Profile Allocation -> Define Roles for Profile Allocation.
1.7.14 Archiving Object ISU_SETTLB (New)

Use As of SAP Utilities Release 4.72, archivable settlement documents are written to one or more archive files. Archiving object ISU_SETTLB is used to archive data from the following tables: o o o o o o o o o o o o EEDMSETTLDOC: Settlement document (header) EEDMSETTLUF: Usage factors for each settlement run EEDMSETTLIN: Load shapes for each settlement run EEDMSETTLDOCERR: Settlement document (errors) EEDMSETTLDOCLINE: Settlement document (lines) EEDMSETTLDOCPARV: Settlement document (persistent value parameters) EEDMSETTLDOCRUN: Settlement document (run) EEDMSETTLDOCSNDP: Settlement document (sent profiles) EEDMSETTLDOCSNDS: Settlement document (sent profiles) status EEDMSETTLDOCUNIT: Settlement document (settlement units accounted for) EEDMSETTLDOCUPDP: Settlement document (updated profiles) EEDMSETTLDOCALER: Settlement document (alerts)
Checks The following conditions must be fulfilled to ensure that only settlement documents that are no longer needed are archived: o o The status of the settlement document is Ended, Ended Manually, or Canceled. The retention period has exceeded.
You can determine the retention period in Customizing. In a subsequent analysis process you have the option to define your own checks to determine the archivability of settlement documents. This allows you to make further restrictions. For more information see the documentation for BAdI ISU_EDM_SETTL_ARCHIV and method ANALYSE_SETTLDOCS.
______________________________________________________________
SAP AG 21
SAP Utilities ______________________________________________________________
Effects on Existing Data Once you have executed the deletion report, all settlement documents are deleted from the database based on the previously created archive. Function and report allocation o Analyze, archive Analysis of settlement documents with regard to possible archiving. Archiving of relevant settlement documents. Display Reads settlement document archives and issues parts of the data in a list. Delete Deletes settlement documents from the database based on the previously created archive. Reload Reloads deleted settlement documents that you archived. Only use this function if it is absoultely necessary.
o o o
Individual document display Using the standard business view for object ISU_SETTLB, it is possible to display archived settlement documents individually by means of the archive information system (SAP AS). The information structure provided by SAP (SAP_ISU_SETTLB) contains the following fields: o o o o o SETTLDOC Settlement document DATEFROM From-date of settlement document DATETO To-date of settlement document SETTLPROCESS Settlement procedure SETTLDOCSTATUS Status of settlement document
You can display the information structure in transaction ESARJ09. You can display individual settlement documents from the archive. You do this using the Display Settlement Document transaction, which you can find in the SAP Menu under Utilities Industry -> Energy Data Management -> Settlement -> Settlement Document -> Display. The system can only find profile allocations and corresponding usage factors that are included in the archive index. Effects on Customizing You can define time-related conditions for archiving in Customizing. You can define a minimum retention period in the system for each settlement document: SAP Utilities -> Tools -> Archiving -> Define Retention Period for Archiving Objects
______________________________________________________________
SAP AG 22
SAP Utilities ______________________________________________________________
1.7.15 Business Add-In for Settlement Unit (New)

Use As of SAP Utilities Release 4.72, you can display additional fields by means of a new tab page. See also BADI ISU_EDM_SETTLUNIT
1.7.16 Wizard for Creating Settlement Parameters (Enhancement)

Use You can use a wizard to create settlement parameters automatically in the system. As of SAP Utilities Release 4.72, the wizard not only uses the parameter name to describe the profile but also includes the ID of the settlement unit, the grid, or the reference profile for information purposes.
1.7.17 Day Offset Taken Into Account for Synthetic Profiles (New)
Use As of SAP Utilities Release 4.72, the day offset specified in the profile header data is taken into account when you generate a synthetic profile. o Example: Day offset: 06:00:00 Generation for 01.01.2004 to 31.01.2004 corresponds to the period from 01.01.2004, 06:00:00 until 01.02.2004, 05:59:59.
The day offset is also taken into account when you generate the synthetic consumption (when updating the usage factor for example). o Example: Day offset: 06:00:00 Consumption for 01.01.2004 valid for 01.01.2004, 06:00:00 until 02.01.2004, 05:59:59
Effects on Existing Data If you have already defined a day offset for your synthetic profiles in the profile header data, this is now taken into account. If you do not want to make any changes to the calculation logic, delete the day offset in the profile header data.
______________________________________________________________
SAP AG 23
SAP Utilities ______________________________________________________________
1.8 IS-U-BI
Contract Billing
1.8.1 New form of cross-installation billing using installation groups

Use You can group utility installations together to create installation groups. An installation group consists of a primary installation and one or more secondary installations. In order to create an installation group, you must: o o Enter a grouping type in the historical part of the utility installation that you want to use as the primary installation. Enter an installation role in the historical part of the utility installations that you want to use as secondary installations. Enter the key of the primary installation in the Primary Installation field.
You can view all installations that belong to an installation group in the transaction Display Installation (ES32). To do this, select Display Installation Group from the menu. You can also use the report ISU_INSTGR_DISPLAY for this. If you enter an installation that belongs to an installation group in the initial screen, the report displays all other installations in this group. The transaction Billing View of Installation contains a similar function. If you select the Complete Installation Groups field, the system displays all installations in an installation group. In the transaction Monitoring Meter Reading Data, you can also select the Installation Group field (in the Installation section) to display all billing orders in an installation group. The most important function of installation groups is that they support a new form of multiple-installation billing. When primary installations are billed, you can access billing data from secondary installations. When secondary installations are billed, you can also access billing data from primary installations. You can define these billing rules in the IMG activity Define Billing Rules for Installation Groups. You can use this technique, for example, to bill serial switchings: o o o o Define the utility installation with the primary meter as the primary installation. Define utility installations with secondary meters as secondary installations. When you bill the primary installation, use the data exchange from the secondary installations to the primary installation to access consumption values in the secondary installations. Use the data exchange from the primary installation to the secondary installations to distribute consumption value difference (consumption from primary meters minus total consumption from secondary meters) among the secondary installations.
This is an alternative way of billing serial switchings. Previously, all secondary meters had to be installed in the secondary installations as well as in the primary installation. If you use installation groups, you no longer have to install large numbers of meters in the primary installation. In addition to this, you do not have to read all meters on the same day. This procedure also enables you to distribute consumption value difference. However, if you use installation groups, all secondary installations - within certain intervals have to be billed together with the primary installation. Important: If you use installation groups, you must create certain indexes for some database tables. If you do not do this, the performance when processing installation groups will be very poor. For more information, see SAP note 706837.
______________________________________________________________
SAP AG 24
SAP Utilities ______________________________________________________________
Effects on Existing Data Existing data is not changed.
1.8.2 Selective Rate Transport

Use As of SAP Utilities Release 4.72, you can use the reports Selective Rate Transport - Download (REA_RTRANS_DOWNLOAD_MUSTER) and Selective Rate Transport - Upload (REA_RTRANS_UPLOAD) to transport selected billing master data in a local file between different systems or clients. Selective rate transport is executed in two steps: 1. 2. Objects to be transported are downloaded from the source system Objects to be transported are uploaded to the target system
You can use the following criteria to select the objects to be transported: o o o o Rate Category Schema Rate Division
1.8.3 IS-U-BI-BD
Billing Master Data
1.8.3.1 Implausible Meter Readings for Mass Simulation

Use As of SAP Utilities 4.72, you can select the Ignore Implausible Meter Reading Results field. This reduces the number of installations that cannot be simulated. For further information, see the documentation on the field. Effects on Existing Data This field is not selected in existing simulation types. Mass simulation is executed as before.
1.8.3.2 Authorization Object for Prices

Use A new authorization object for prices is available as of SAP Utilities Release 4.72.
______________________________________________________________
SAP AG 25
SAP Utilities ______________________________________________________________
The previous authorization object for prices (E_PRICE) has now been replaced by the authorization object E_PRICE1. In addition to the authorization fields Activity, Division and Billing Class, this object also checks the Authorization Group. Effects on System Administration Adjust the authorization profiles of all employees responsible for prices so that they correspond to the new E_PRICE1 authorization object. Authorization object E_PRICE is no longer used.
1.8.3.3 IS-U-BI-BD-RS
Rate Structure
1.8.3.3.1 Maintain Billing Schemes: Notes for Schema Steps

Use As of SAP Utilities Release 4.72, you can edit schema step notes in the following transactions: Create Billing Schema (EA35) and Change Billing Schema (EA36). You can then display these notes in the Display Billing Schema transaction (EA37). The schema step notes are an addition to the existing notes in the schema header data. You edit schema step notes on the schema step screen. In the line you want to edit, double click on the new Schema Step Notes column. An icon indicates that a note has been entered for a schema step. You can display and print the schema step notes and the schema steps together as list. Use the Print Schema Steps (REASCHEMA) report to do this, or select Print on the schema step screen. Effects on Data Transfer The schema step notes are transported during an individual or complete transport of billing Customizing.
1.8.3.4 IS-U-BI-BD-DS
Discounts/Surcharges
1.8.3.4.1 Authorization Object for Discounts or Surcharges

Use Previously, the authorization for maintaining discounts and surcharges could only be controlled using the transactions Create/Change/ Display Discount/Surcharge (EA47, EA48, EA49). As of SAP Utilities Release 4.72, you can now use the new Authorization Object for Discounts/Surcharges (E_DISCOUNT). This enables you to assign authorizations from a combination of activity, division and billing class. Effects on System Administration Enhance the authorization profile for all employees responsible for discounts or surcharges.
______________________________________________________________
SAP AG 26
SAP Utilities ______________________________________________________________
1.8.4 IS-U-BI-PC 1.8.4.1 Bill Correction

Use
Billing Execution
As of SAP Utilities Release 4.72, you can use the Bill Correction function (transaction EABICO) within the framework of the increased efficiency project. This function enables you to do the following: o o o o o o o o Display a print document from the optical archive, or, if an optical archive is not available, simulate the bill printout and display the simulated result Reverse a bill or reverse a bill for adjustment Correct meter reading results Simulate a bill based on new meter reading results Display information from the new, simulated bill Rebill and invoice using the corrected meter reading results Print the corrected bill Create a customer contact
Effects on Customizing You can make the necessary settings in the SAP Utilities Customizing menu under: Contract Billing -> Billing Execution -> Maintain Billing Control .
1.8.4.2 Billing Simulation Scenarios

Use You can use the transaction Execute Simulation Scenarios (EASIM) to execute different scenarios for billing simulation. Effects on Customizing You can define the simulation scenarios in the Define Simulation Scenarios activity. Before you do this, you must define categories in the Customer-Specific Categories for Simulation Scenarios activity, for example, the standard SAP categories. The simulation scenario category specifies how simulation scenario is implemented. Simulation scenario categories are implemented using an implementation model based on ABAP OO classes. You can use this model to implement your own categories of simulation scenarios.
______________________________________________________________
SAP AG 27
SAP Utilities ______________________________________________________________
1.8.4.3 Adjustment Reversal in the Deregulated Scenario

Use Previously, you could not execute an adjustment reversal (transaction EA21) if you wanted to send documents to an invoicing service provider. As of SAP Utilities Release 4.72, you can execute an adjustment reversal and then send the documents that are subsequently invoiced to the invoicing service provider.
1.8.4.4 IS-U-BI-PC-AU
Automatic Billing and Simulation
1.8.4.4.1 Price Block Adjustment

Use As of SAP Utilities Release 4.72, you can adjust block differences instead of block limits when you modify price blocks for the billing period. You can use the Customer-Specific Price Block Adjustment BAdI (ISU_BI_PR_BLOCK_ADJ) to do this. You can call this BAdI in the following variants: QUANTI01, QUANTI11, QUANTI21 COMPUT50, COMPUT51 and DEMAND19. The new variant Multiply Blocks Dependent on Pricing Quantity by a Factor COMPUT29 enables you to use a factor to adjust price blocks. You can control whether block limits or block differences are adjusted. Effects on System Administration If you want to adjust block differences during price block adjustment, you must make the appropriate settings in the ISU_BI_PR_BLOCK_ADJ BAdI. The block difference adjustment is saved as a code example. Block limits are adjusted as default. For more information, see the documentation on this BAdI.
1.8.4.4.2 Decimal Places for Meter Reading Results during Proration

Use Previously, in the case of meter readings determined for a proration date, you could only transfer the number of meter-reading-relevant decimal places from the meter reading group. As of SAP Utilities Release 4.72, you can now determine these meter readings more accurately. In order to do this, you must maintain the Number of Decimal Places for Proration in a meter reading group and allocate this group to the corresponding operand. Effects on Customizing In the activity Define Meter Reading Group, maintain the Dec. Place Pror . field. This ensures that, in the case of proration, the system rounds down to the number of decimal places entered in this field. In
______________________________________________________________
SAP AG 28
SAP Utilities ______________________________________________________________
order for this to take affect, the number of decimal places for proration has to be larger than the number of decimal places for the register or the decimal places relevant for meter reading.
1.9 IS-U-IN
Invoicing
1.9.1 Changes during a Reversal

Use As of SAP Utilities Release 4.72, the following changes have been made to the reversal functions: o o The function Automatic Partial Reset now enables you to reverse part of a payment that was cleared by a specific bill. None of the other cleared items are affected by this. When you reverse a bill, you always have to enter a posting date that is not located in a closed posting period. You can now automate this process by defining in Customizing whether a bill reversal for a closed posting period automatically uses the current system date or not. You can now recreate the original invoicing units after a bill has been reversed. You can now reverse additional, dependent billing documents during a bill reversal. This enables companies in deregulated markets, for example, to execute bill reversals for supply and grid documents. You can now individually determine the posting date of a print document to be reversed. This is useful, for example, for mass reversal since the posting date can only be specified globally at the start of the transaction. You can now reverse individual bills within a collective bill without having to reverse the complete collective bill. You can also reset or recall budget billing requests for individual bills.
o o
Effects on Customizing Make the necessary settings in the Customizing menu for SAP Utilities under Invoicing -> Basic Settings -> Define Basic Settings for Invoicing.
1.9.2 Grouping Together Partial Bill Document Line Items

Use As of SAP Utilities Release 4.72, you can group together partial bill document line items. You may want to do this, for example, if you have split budget billing items into several subtransaction items in order to post them to Contract Accounts Receivable and Payable. Normally, these line items are printed separately on a bill depending on the transaction. Now, you can group these lines together for the bill printout. Effects on System Administration You can specify which lines are grouped together for every creation reason and every account determination characteristic from invoicing.
______________________________________________________________
SAP AG 29
SAP Utilities ______________________________________________________________
In the partial bill, it makes sense to group the line items from all subtransactions. In a periodic bill, you can also group lines items together based on their due date. This means that you only print one line item in the periodic bill and that this line contains the total balance from the partial bill. In the Field Name (ERDZ) field, define one or more field names that are identical with the field names of the ERDZ structure. The system then uses this field to group together the partial bill line items on the bill. For further information about this field, read the F1 help documentation. Effects on Customizing Make the required settings in the Define Criteria for Grouping Partial Bill Items activity.
1.9.3 Procedure for Determining Tax Codes

Use Previously, you could only specify for each client whether the tax code is determined when billing is executed or when invoicing is executed. As of SAP Utilities Release 4.72, you can now create additional company code groups and specify procedures for these groups that are different to the procedure specified in the client settings. Effects on Customizing Define the exceptions in the activity Define Tax Determination Procedure For Each Company Code Group. Here, you can specify the time and date type of tax code determination for each company code group. If you do not enter any data here or do not define the company code of the contract account to be billed or invoiced, the system uses the tax code determination procedure saved in the client settings.
1.9.4 IS-U-IN-PC
Invoice Processing
1.9.4.1 Defer Open Items in Invoicing

Use As of SAP Utilities 4.72, you can defer the following open items from the contract account during invoicing: o o Open items that are included as sub-items in the print document and are part of the final bill amount. Remaining open portions of items that have been partially cleared by integrated account maintenance in invoicing.
The items are deferred until the due the due date of the bill. The due date of the items and, if necessary, the existing deferral date must not be later than the due date of the bill.
______________________________________________________________
SAP AG 30
SAP Utilities ______________________________________________________________
Effects on Customizing In the activity Item Selection in Account Maintenance/Define Subitems, select the option Item Selection for Bill Printout (Subitems) for Invoicing. In the field PS (Defer Items until Bill Due Date), select the items you want to defer. You can also select open items in the event IS-U Invoicing: Subitems (R410).
1.9.4.2 New Customizing Settings for Gross Prices

Use As of SAP Utilities Release 4.72, you can make the following settings for gross prices: o o You can decide whether the different price sections of a gross price are included in the bill or not You can specify the maximum difference between the gross price and the price sections
Previously, it was only possible to make these settings by modifying each presort function module. Effects on Customizing Make the required settings in the Define Sort Criteria for Bill Printout activity.
1.9.4.3 New Functions for the Event: Document Enhancements (R402)

Use As of SAP Utilities Release 4.72, you can specify whether a new item that has been created in the event Document Enhancements (R402) is included in the final bill amount and whether it is included in the print document at all. o o If you do not want an item to be included in the final bill amount, you must set the indicator X_NOT_TOTAL_AMNT in the table N_FKKOP when the item is created in event R402. If you do not want the item to be printed, set the indicator X_NOT_PRINTREL in this table as well.
You can use this new function for additional items in the print document as well for a new document.
1.9.4.4 New Parallel Processing Object for Bill Reversal

Use Previously, the parallel processing object VKONT was used for Bill Reversal (EA33) and Full Reversal (EA34). This object creates intervals for all contract accounts, even if they do not actually contain any print documents to be reversed. As of SAP Utilities Release 4.72, VKONT has been replaced by the new parallel processing object
______________________________________________________________
SAP AG 31
SAP Utilities ______________________________________________________________
REV_ERDK. This new object creates intervals for contract accounts that have print documents and that have been selected based on the selection conditions in bill reversal. The object tries to modify the intervals so that the same number of print documents is reversed in all intervals. The parallel processing object is selected automatically at the start of each transaction. Effects on Existing Data The previous parallel processing object VKONT is no longer available for bill reversal. This may cause an error in the Technical Settings tab page when viewing old reversal runs. If this happens, you cannot choose another tab page. You then have to call up the transaction again and directly select the desired tab page.
1.9.5 IS-U-IN-BB
Budget Billing Plan
1.9.5.1 Extrapolation of Budget Billing Amounts Using Meter Readings or Period Consumption Values
Short Text Previously, the necessary meter readings and period consumption values had to be saved on your database if you wanted to extrapolate a budget billing amount. As of SAP Utilities Release 4.72, meter readings and period consumption values are taken directly from the main memory when a budget billing amount is extrapolated. When you save the extrapolated budget billing amount, you can decide whether you want to save the meter readings and period consumption values on your database. Effects on Customizing To use this function, you must make the necessary settings in the activity Define Control Parameters for Express Transaction.
1.9.5.2 Amount Transfer in Portion Change

Use As of SAP Utilities Release 4.72, you can specify in transaction EA65 ( Adjust Budget Billing Plans to Changed Billing Dates) whether a new budget billing plan is created using extrapolation or by transferring previous amounts. Previously, you could only select extrapolation. Effects on Customizing In event R923 (Amount Transfer in Portion Change), you can change the default data that is transferred from the previous budget billing plan. To do this, create your own function module and enter it in Customizing in the Define Customer-Specific Function Modules activity. You can now use a new indicator in Define Control Parameters to define whether extrapolation is called during a cycle change, or whether the data from the previous budget billing plan is used.
______________________________________________________________
SAP AG 32
SAP Utilities ______________________________________________________________
See also For further information about this transaction, see the online documentation Adjustment of Budget Billing Plans to New Billing Dates .
1.9.5.3 Adjustment of Standing Budget Billing Amount in Event R995

Use As of SAP Utilities Release 4.72, you can automatically adjust the standing budget billing amount when you create a budget billing plan. You can activate, deactivate or change the standing budget billing amount. The interface of event Change (Standing) Budget Billing Amount (R995) has been enhanced to make this possible. In order to activate this function, define your own settings in event R995. This does not affect existing settings. Effects on Customizing To adjust the standing budget billing amount, define your own function module in event R995 or change an existing function module. You can do this in the Define Customer-Specific Function Modules activity See also For more general information about event R995 see the documentation on the function module Change (Standing) Budget Billing Amount (ISU_SAMPLE_R995).
1.9.5.4 New Functions and Enhancements for Budget Billing Plans and Invoicing
Use As of SAP Utilities Release 4.72, you can use the following new or enhanced functions to process budget billing plans: o You can now specify whether a budget billing plan can be created if a move-in meter reading result is missing. To do this, activate the corresponding indicator in the Define Control Parameters activity. Previously, after calling the generic object services, you had to select a budget billing plan in a dialog box in order to use the available services. Now, once you have called the generic object services, you can use the services directly for the budget billing plan. The new fields Text for Item and Item can only be Cleared have been added to the Change Budget Billing Plan transaction (EA62). You can change these fields for each due date. When you print a periodic bill, you can also print the posting date of the requested partial bills. The posting date can only be used for partial bills that have been created in the future.
o o
______________________________________________________________
SAP AG 33
SAP Utilities ______________________________________________________________
You can also print a budget billing plan at a later date. You can use this function when you change, display or create a budget billing plan. You can set a default value in the dialog box that is used for selecting the print time. In addition to this, you can also specify whether several changes that have been made for a customer are grouped together in one letter. You can make these settings in the activity Define Control Parameters.
1.10 IS-U-CA
Contract Accounts Receivable and Payable
1.10.1 Account Balance Display

Use
Restriction of Item Selection If you select the button Period for Item Selection (F7) on the initial screen of the account balance display, you can restrict the period that the system uses for selecting the items in the account balance. Context Menu in the Account Balance You can call up a context menu by clicking on the right mouse button when the cursor is on an item in the account balance. In events 1247 and 1248, you can adjust the functions of the context menu to meet your requirements or add to them. Fields: ClearFI-CA/PrD (OPBEL_KK_RG) and ClearFI-CA/PrD (AUGBL_KK_RG) As of SAP Utilities Release 4.72, these fields are now maintained as follows: If the document item was created as a result of invoicing, the system enters the print document number in the field ClearFI-CA/PrD. The system also adds the letter F for invoicing at the end of the number. If the document item was created by a normal posting document, the system enters the standard number. The clearing number of a document is entered in the field ClearFI-CA/PrD (AUGBL_KK_RG) in the same way. Display documents from a print document You can now display all documents that belong to a print document in the Display Print Document transaction (EA40). This function has been integrated in the account balance display. When you view a document that belongs to a print document, you can now display all other documents that belong to this document. To do this, place the cursor on the print document and select from the menu Environment -> Additional Functions -> Documents for Print Document. The item list is kept in the background. Simplified Display of Print Document The display of a print document in account balance display has been simplified. The system no longer displays certain document items. On the selection screen, you can also set the indicator Cum.Bills if you want to hide further document items. For further information and examples, see the documentation on SAP for Utilities 4.72 in the SAP Help Portal on the Internet under http://help.sap.com ZK>-> SAP Industry Solutions -> SAP for Utilities ->
______________________________________________________________
SAP AG 34
SAP Utilities ______________________________________________________________
4.72 -> Contract Accounts Receivable and Payable -> Basic Functions -> Account Balance Display Effects on Customizing Define the required function modules for events 1247 and 1248 in the Implementation Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules.
1.10.2 Archiving for Tax Reporting Argentina (Changed)

Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the following new archive info structures for archiving objects FKK_GENREP, FKK_GENREV, and FI_MKKGENS are delivered and must be used for Argentina: o o o SAP_FICA_ARREP1 SAP_FICA_ARREV1 SAP_FICA_ARRES1
You must use these info structures in conjunction with the following function modules: o o o FKK_AR_EVENT_0515 FKK_AR_EVENT_0520 FKK_AR_EVENT_0525
The system calls these function modules to include Argentina-specific fields from the tax reporting tables in the archive info structures above. Only by using these info structures with these function modules do you ensure that the system correctly connects the Argentine tax reports to the archive. Effects on Customizing You need to assign the above function modules to each of the relevant tax events: 0515, 0520, and 0525. You do so in Customizing for Financial Accounting, under Contract Accounts Receivable and Payable -> Basic Functions - > Tax Reports -> Tax Reporting - Argentina -> Basic Settings -> Activate Recording of Tax Data.
1.10.3 Archiving
Use Document Archiving In future, the program for archiving documents ( RFKKAR10) checks whether the balance of the document is zero (check DOCUMENT-01). Two new events are available: o In event 0501 you can check document headers in blocks.
______________________________________________________________
SAP AG 35
SAP Utilities ______________________________________________________________
In event 0505, you can carry out installation-specific checks at document level.
If you need data from other tables for the document check in event 0505, you should read this data in advance in event 0501 in order to avoid adverse effects on performance. In event 0501, you can select all of the data required for the documents transferred and save it to the local memory. This means that you can carry out all additional checks for event 0505 with no individual database access. The archiving log of the document archiving device has been change over to the Archive Development Kit (ADK) standard log. You can now no longer display the details of documents that cannot be archived in the detailed error log. Instead, click on the document number in the detail log to go to the document display. The number of archived entries in the individual tables is no longer displayed for the individual documents. These totals are now only displayed for all archived documents. However, you can display the archive entered before deletion using the Archive File Browser (transaction AS_AFB) and thus check the archived structures/content. Archiving Information about the Foreign Currency Valuation You can use the new archiving object FI_MKKVAL to archive the data that arises from the foreign currency valuation. The prerequisites for the archiving are described in the documentation for report RFKKAR36. Archiving Clearing Histories You can archive clearing histories with the new archiving object FI_MKKPCR. The prerequisites for the archiving are described in the documentation for report RFKKAR41. Archiving of Doubtful Entries You can archive data for doubtful receivables with the new archiving object FI_MKKDRVA. The prerequisites for the archiving are described in the documentation for report RFKKAR44. Archiving of Transfer Records for Invoicing by Third Parties You can use the new archiving object FI_MKKTHI to archive data fo invoicing by third parties (see also documentation for report RFKKTHPAR01).
1.10.4 Authorization Objects

Use Maintaining Interval Variants With authorization object F_KKVARI, you can restrict the authorizations for maintaining interval variants: o o In the field OBJECT_KK, define the authorization for individual objects, such as GPART and VKONT. In the field ACTVT, you can control the authorizations for the following activities: Activity 01 Description Create variants
______________________________________________________________
SAP AG 36
SAP Utilities ______________________________________________________________
02 03 06 07
Change variants Display intervals Delete variants Generate variants
New Authorization Object F_FKKCJ for the Cash Journal The authorization object F_FBCJ, which controls the authorizations for the cash journal, has been replaced by the authorization object F_FKKCJ. In the field ACTVT, you can control the authorizations for the following activities: Activity 01 02 03 10 33 B5 Description Add or create Change Display Post Read Display history
If you cannot change over to the authorization object F_FKKCJ in the cash journal quickly, see SAP note 667984. This note contains a description of how you can continue to use the old authorization object F_FBCJ in the FI-CA Cash Desk. Note that you should deactivate this temporary solution as soon as possible. After Release 4.72, SAP will only support the authorization object F_FKKCJ.
1.10.5 BAPIs in Contract Accounts Receivable and Payable

Use Requests You can now use new BAPIs for the business object CA_REQUEST to process requests. The following methods are supported: Create BAPI_REQUEST_CREATE Getdetail BAPI_REQUEST_GETDETAIL Change BAPI_REQUEST_CHANGE Delete BAPI_REQUEST_DELETE
Create request
Read request
Change request
Delete request
______________________________________________________________
SAP AG 37
SAP Utilities ______________________________________________________________
EasyCreate BAPI_REQUEST_EASYCREATE AddPeriods BAPI_REQUEST_ADDPERIODS DeletePeriods BAPI_REQUEST_DELETEPERIODS AddSpecialDates BAPI_REQUEST_ADDSPECIALDATES DelSpecialDates BAPI_REQUEST_DELSPECIALDATES AddLineItems BAPI_REQUEST_ADDLINEITEMS DelLineItems BAPI_REQUEST_DELLINEITEMS
Create request with template
Add execution periods for request
Delete execution periods for a request
Add special dates for request
Delete special dates for a request
Add request items
Delete request items
Changes to the BAPIs for FI-CA Documents The parameters ItemRelation and CardData have been added to the BAPI CtrAcDocument.Create, The parameters DocumentHeader and DocumentHeaderX have been added to the BAPI CtrAcDocument.Change New BAPI for Contract Accounts From Release 4.72, you can use the new BAPI CtrAcContractAccount.GetOpenItems. Changes to the BAPI for Contract Accounts The selection field in the parameter ValueSelektions has been extended.
1.10.6 Boletos
Use Creating Boletos To improve the performance of the program for creating Boletos, you can use the payment method to restrict the selection of open items.
______________________________________________________________
SAP AG 38
SAP Utilities ______________________________________________________________
If you also consider statistical documents in Boletos, you can delete or integrate the required statistical documents in event 6303 (see FKK_SAMPLE_6303). Mass Reversal of Boletos You can now use a mass reversal transaction (FPO1C) for Boletos created by a mass run (see SAP menu: Periodic Processing -> For Contract Accounts -> Boleto). You select the run to be reversed using the run date and the run ID for the creation run. After the reversal, you can create new Boletos for the open items in the reversed Boletos. The system automatically records the new run date and run ID for the payments assigned to the banks during the creation of the Boletos. Creating Boletos Online In the transaction Create Boleto from Open Items (FBO1S), you can create Boletos online. To do this, select the required open items manually by business partner, contract account, and document number and specify the bank and account to which the payment is to be made. This transaction is particularly useful for installment plans. You can select the individual installment plan items by business partner, contract account, payment method, and due date and create one Boleto for these items. The system assigns the run date and run ID automatically and saves this data in the header of the Boleto. The payment assigned to the bank is updated in table DFKKBOL_BANKID. Effects on Customizing You make the settings for creating Boletos in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Payments -> Creation of Incoming and Outgoing Payments -> Boleto.
1.10.7 Business Information Warehouse

Use Extracting Open Items During the evaluation of receivables balances in the Business Information Warehouse (BW), you can now simulate the clearing of credits with the oldest open receivables for a business partner. The credits are only cleared if the transaction currency of the receivables and the credits to be cleared is the same. In event 2506, you can determine which of the following data has to agree for the credits to be cleared: o o o Company code Business area General ledger account
If you do not define the event individually, clearing only takes place if the company code and the general ledger account are the same for the receivable and the credit. In the simulation, the due date of the credits is fixed to the due date of the receivables cleared. This means that when the items are totaled and sorted, the status is the status that would be reached if the
______________________________________________________________
SAP AG 39
SAP Utilities ______________________________________________________________
credits were cleared with the oldest receivables due. If a credit memo is to be distributed over several receivables, the extractor simulates several fictitious items. The restriction by business partner has been added to the extraction of open items. This means that you can now restrict the extraction of open items to a subset of business partners before the open item analysis. You can use event 2504 to restrict the quantity of business partners selected. The functions of event 2505 have also been enhanced to enable you to exclude combinations of business partner, contract account, and contract (GPART/VKONT/VTREF) that are not required from the extraction quantity. The system recognizes the runs to be restricted from the naming convention used in the event modules. The fields LAUFD and LAUFI have been added to the interface of event 2505 for this purpose. Extracting Installment Plan Data You can use a new mass activity to extract installment plan data for the evaluation in the Business Information Warehouse (BW). The data can be extracted either with or without consideration of previous extractions (delta queue). As standard, only the most important data for the installment plan headers, installment plan items, and original items is extracted. However, you can extend the extract structures. You can use events 2525 and 2530 to read additional data and fill additional fields in the extract structures.
1.10.8 Cash Desk

Use General Ledger Account Postings In the cash desk (Short Account Assignment) The function for transferring incoming and outgoing payments in the Cash Desk has been enhanced and you can now carry out the transfer postings with a tax on sales and purchases part. The field Tax Code has been added to the area G/L Account Posting on the tab page Specifications for Payment on the initial screen of the Cash Desk. The following fields have been added to the Customizing activity Define Short Account Assignments for Transfer Postings in the Cash Desk: o Tax on Sales and Purchases Code Here you can define a tax code for each short account assignment key, that is, each G/L account posting. Authorization Group With the authorization group you can assign specific authorizations to allow a clerk, for example, to use only certain short account assignment keys. Maintain the authorization via authorization object F_KK_KUKON.
Barcode Scanner With Release 4.72, the connection of barcode scanners has been implemented in the cash journal and the Cash Desk. In the Customizing activity Maintain Specifications for Cash Desk/Cash Journal, you can define whether the barcode entry field is to be displayed or hidden. If the barcode entry field is available, you display or hide the field dependent on the workplace via the Cash Desk menu Extras -> Barcode Entry -> Display/Hide. In the menu under Extras -> Hold Settings, you can save the settings user-specific. The barcode scanned must be interpreted in event FKK_SAMPLE_6050 and the data required for the
______________________________________________________________
SAP AG 40
SAP Utilities ______________________________________________________________
entry must be entered on the input screen for the cash desk/cash journal. Effects on Customizing You make the system settings in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Payments -> Processing Incoming/Outgoing Payments -> Cash Desk/Cash Journal.
1.10.9 Cash Journal

Use Reversing Withdrawals In the cash journal menu under Edit, you can use the function Reverse Withdrawal to reverse withdrawal documents. This function does not just reverse the document; it also corrects the cash desk balance. Barcode Reader From Release 4.72, you can connect a barcode reader in the cash journal and the cash desk. In Customizing, you can define whether the barcode entry field is to be hidden or displayed. If the barcode entry field is available, you display or hide the field dependent on the workplace via the Cash Desk menu Extras -> Barcode Entry -> Display/Hide, provided the workplace has a barcode reader. In the menu under Extras -> Hold Settings, you can save the settings user-specific. The barcode read is interpreted in event 6060. Enter the data required on the input screen for the cash desk or the cash journal. For more information, see the sample function module FKK_SAMPLE_6060. Effects on Customizing Posting Areas 0150 and 0160 The field Payment Type has been added to the posting areas 0150 - Cash Journal: Specifications for Posting Cash Desk Differences - and 0160 - Cash Journal: Bank Clearing, Deposit, and Withdrawal Accounts. You can define a separate cash desk clearing account per payment type: CS CP CH PO CO Incoming and outgoing cash payment Credit card payment Incoming check payment Postal order payment Outgoing check payment
The introduction of the new payment type CO for outgoing check payments means that you can now define separate cash desk clearing accounts for incoming and outgoing check payments. Make sure that you also enter the cash desk clearing accounts that you enter here in the activity Define Bank Clearing Accounts for Payment Lots and that they are as follows: Validity for the Corresponding Lot Types
______________________________________________________________
SAP AG 41
SAP Utilities ______________________________________________________________
PymtType PymtLot CS X CP CH PO CO
CheckLot
CardLot X
Online Check
X X X
Maintain Specifications for Cash Desk/Cash Journal From Release 4.72, you can make the specifications for the cash desk and the cash journal together in the activity Maintain Specifications for Cash Desk/Cash Journal.
1.10.10 Closing operations

Use Summarization Accounts and Summarization Company Codes for Reclassifications You can now display reclassifications for a group of accounts or company codes - previously, you could only display the reclassifications in the balance of one receivables or payables account of a business partner within a company code. Summarization accounts are required for key date-related open items whose receivables and payables accounts are displayed in one item in the financial statements (for example, same type of legal transaction for several utility provider divisions in the case of different receivables accounts per division). Summarization company codes are required where company codes are in the legal entity that has to create the financial statements (for example, consolidated financial statements). See the release information for Foreign Currency Valuation and Evaluation of Open Items. Effects on Customizing Summarization Accounts and Summarization Company Codes for Reclassifications You make the specifications for reclassification by summarization company codes and accounts in the Implementation Guide for Contract Accounts Receivable and Payable under Closing Operations -> Reclassifications.
1.10.11 Submission of Receivables to Collection Agencies

Use The following functions have been added to the submission of receivables to collection agencies: o o Derivation of collection agency responsible Deletion of submission logs
Derivation of Collection Agency Responsible
______________________________________________________________
SAP AG 42
SAP Utilities ______________________________________________________________
If you want to release receivables to different collection agencies using rules in your organization, from Release 4.72, you can define these derivation rules in Customizing for Contract Accounts Receivable and Payable. The derivation rules defined in Customizing are evaluated by the derivation tool. The derivation tool is always called in the function module FKK_COLL_AG_SAMPLE_5060 if items are released for collection individually in transaction FP03E or in the mass release via transaction FP03M. The derivation tool determines the relevant collection agency in one or more derivation steps from a sequence of source fields of the enhanceable structure FKKCOLLAG. The number of derivation steps corresponds to the number of derivation rules that you define in Customizing. Deletion of Submission Logs You can now delete logs recorded in table DFKKOPCOLL by the mass run for submitting receivables to collection agencies (FP03M). You can do this with transaction Delete Submission Logs (FP03DML) (see SAP menu: Periodic Processing -> Delete Data). Effects on Customizing You define the derivation rules for the responsible collection agency in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Submission of Receivables to Collection Agencies -> Define Derivation Rules for Responsible Collection Agency.
1.10.12 Collective Bills

Use From Release 4.72, you can group documents from different contract accounts in a collective bill document in order to process them together. You can manage and process all of the individual documents in a collective bill together via a third account the collective bill account. You can create a joint invoice and make the payment or in the case of payment arrears, dun all of the items in the collective bill together. Collective bills are particularly useful, for example, for billing property and house building companies that process receivables from utilities companies for their tenants, and for companies with branch-head office relationships. Effects on Existing Data At master data level, you have to assign the individual contract accounts to a collective bill account. A collective bill account is a contract account of the contract account category collective bill account. You have to define this account in the master record of every contract account whose postings you want to group in a collective bill. There is no change to the assignment of contract accounts that you link via the collective bill account to your business partners. To link an account with the collective bill account: 1. 2. In the SAP menu choose Contract Account -> Create or Change. In the field Collective Bill Account in the area Invoice Creation on the tab page General Data, enter the required collective bill account.
Once you have assigned the account to a collective bill account, when you enter posting documents in this account, each business partner item is automatically linked to a statistical posting document
______________________________________________________________
SAP AG 43
SAP Utilities ______________________________________________________________
(collective bill document) in the collective bill account. Effects on Customizing To use collective bills, you have to carry out the following in the Implementation Guide for Contract Accounts Receivable and Payable: o Under Program Enhancements -> Define Customer-Specific Function Modules, enter FKK_COLL_BILL_CREATE_0063 for event 0063, provided this module is not already integrated in the industry-specific module for event 0063. In the industry components Utilities and Telecommunications, this module is already integrated in the industry-specific module for event 0063. Under Basic Functions -> Contract Accounts -> Number Ranges and Contract Account Categories -> Configure Contract Account Categories and Assign Number Ranges, enter a contract account category for collective bill accounts. Set the indicator in the column CB (contract account is collective bill account) and assign a number range to the contract account category. Under Basic Functions -> Postings and Documents -> Document -> Maintain Document Account Assignments -> Document Types -> Maintain Document Types and Assign Number Ranges, create a document type for collective bill documents and assign a number range to this document type. Under Basic Functions -> Postings and Documents -> Document -> Maintain Document Account Assignments -> Maintain Default for Document Type for Collective Bill, define the document type that you defined in the previous step as the default for creating collective bill documents.
The main and subtransaction for the collective bill item are determined in event 2222. You can overwrite industry definitions implemented for this event. This event has already been defined for the industry component Utilities.
1.10.13 Company Codes

Use Replacement of the Responsible Company Code in Contract Accounts Receivable and Payable Previously, the responsible company code had the following control characteristics in FI-CA: o o o It determined the company codes in which you could post to a contract account It was the company code in which payment transactions were processed It was (regardless of Customizing) the company code in which payments on account were posted
The coupling of these functions heavily restricts the options in some areas and leads, for example, to you having to introduce auxiliary company codes to portray the organizational model. From Release 4.72, the responsible company code is replaced by the following three new entities: o Company code group The company code group includes all company codes that are permitted for posting to a contract account. One company code group is assigned to each contract account. Company code groups can overlap. This means, for example, you can have a group G1 that consists of company codes 0001,
______________________________________________________________
SAP AG 44
SAP Utilities ______________________________________________________________
0002, and 0003, and group G2 that consists of 0001 and 0003. o Paying company code Exactly one paying company code is always assigned to each company code group. A paying company code is responsible for payment transactions. You have to define house banks and payment methods for paying company codes. Several company code groups can have the same paying company code. The paying company code does not have to be in the company code group itself. Standard company code One standard company code is assigned to every contract account. You use the standard company code for all postings for which no company code can be determined by other means (for example, for payments on account).
Transition from Responsible Company Code to the New Entities The conversion of the responsible company codes to company code groups and paying company codes takes place automatically during the first check (contract account or document) where you check the validity of a company code group or where the company code group is a prerequisite. For each responsible company code, the system creates a company code group with the same key. The company codes that were previously assigned to the responsible company code are assigned to this company code group. The responsible company code is assigned as the paying company code for the group. This ensures continuity for the existing organizational model. The name of the responsible company code is taken as the name for the company code group. Since the new name is language-dependent, it is automatically created in all languages used in the installation. The languages are determined empirically by analyzing the document type texts. Changes to the Contract Accounts For new contract accounts, the company code group and standard company code are mandatory requirements. For existing contract accounts, you can use conversion report RFKKSTDBK to add the standard company code. The standard company code receives the value of the former responsible company code. You can convert the contract accounts in stages you do not have to convert them all at once. The system handles accounts that you have not yet converted as if you had converted them. Changes to Checks in Contract Accounts The validity of certain fields was previously coupled to the combination with the country of the responsible company code. The following changes have occurred in these checks: o The country from the paying company code of the company code group is used for: o Payment methods Own bank details
The country of the standard company code is used for: Withholding tax codes Region County code Tax exemptions
Restrictions for Company Code Groups
______________________________________________________________
SAP AG 45
SAP Utilities ______________________________________________________________
Using the new event 1010, you can check whether a company code group is permitted in a contract account. This enables you to prevent, for example, that cross-country groups (in certain contract accounts) are used. Authorization Check In the authorization object F_KKVK_BUK, the responsible company code was used for the check in the master data maintenance. The standard company code is now used instead. Payment Program You can also specify the paying company code in a business partner item. In this case, this specification overrides the paying company code determined via the company code group of the contract account. If a paying company code specified in the line item is in a different country to the paying company code determined via the contract account, you also have to specify a payment method in the line item. In this case you cannot use the payment methods from the contract accounts since they refer to a different country. In the parameters for the payment run/debit memo run, you restrict the company codes to be processed. All relevant company code groups and their paying company codes are determined for the company codes internally. If these are in different countries, the country of the payment run must be assigned via a different parameter. In a payment run, you can still only create payments for one country. Effects on Customizing You define the company code groups in the Implementation Guide for Contract Accounts Receivable and Payable under Organizational Units -> Define Company Code Groups. You assign the company codes to the groups under Organizational Units -> Assign Company Codes to Company Code Groups.
1.10.14 Generation of Correspondence

Use Balance Notification You can use event 9552 to create balance notifications. In this event you decide whether a balance notification is to be created. Requests and Standing Requests To print requests and standing requests, you can use events 0766: Print Request and 0767: Create Request Printout, and correspondence type 0039 Request (see also the release information for Requests). Effects on Customizing You define customer-specific function modules in the Implementation Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules.
______________________________________________________________
SAP AG 46
SAP Utilities ______________________________________________________________
1.10.15 Connecting SAP Dispute Management to Contract Accts Rec. and Payable
Use From Release 4.72, you can create and manage complaints (disputes) from your business partners with regard to incorrect invoices and credits or missing invoices and credits as dispute cases in a dispute system as part of SAP Dispute Management. These dispute cases contain attributes, such as the reason for the complaint, the priority, the disputed amount, the clerk responsible for resolution, and contact data of the business partner. During the processing of the dispute case, you can trigger functions such as the reversal of an invoice, write-offs, and postings of invoice-related credits. From the dispute case you can display the follow-on postings for the case. To get an overview, you can display a list with all dispute cases for a business partner or document. Definition of terms used Dispute System The system in which the dispute cases are created and managed. The system in which Contract Accounts Receivable and Payable runs. The complaint of the business partner as object to be managed in SAP Dispute Management. The dispute case contains attributes such as the amount, data about the status of processing and for categorizing the dispute as well as, in the record, a list of related objects to which the case references (for example, document, invoice business partner, contract, contract account). The following case types are differentiated: - FICA: Incorrect invoice, incorrect credit - FCA2: Missing payment The case types are differentiated by their attributes. A dispute case of the case type Missing Payment describes, for example, the case when a customer complains about a dunning
FI-CA System
Dispute Case
Case Type
______________________________________________________________
SAP AG 47
SAP Utilities ______________________________________________________________
notice that was executed despite payment having been made. The clerk's job is to find this payment, which may have been incorrectly assigned, and potentially reassign it and then close the case. With a dispute case of the case type Incorrect Invoice, the customer has complained about an incorrect invoice amount. Here the clerk has to check the amount and trigger any adjustment postings, such as reversals, write-offs, or credits. Internal Dispute Type Internal categorization of a dispute case that each dispute case must have. Since the system behaves differently in different case types, and each customer can create installation-specific case types, an internal categorization (assignment) is necessary. Thus, the dispute type A001, for example, is an incorrect invoice, and dispute type B001 is a missing payment.
Creating Dispute Cases Dispute cases are created from the dispute system. However, you can also create dispute cases in the FI-CA system. In the document display, you can use the function Create Dispute Case to create a dispute case. A dialog box appears, where you can set the default values defined for event 1250. For a sample form of event 1250, see sample function module FKK_SAMPLE_1250. The specification of a business partner is mandatory in each dispute case; the specification of a contract account and contract is option and determines the level of detail of the dispute case. The system includes the document displayed as a disputed document in the case. The data and amounts of the document are used to determine the default values. Dispute cases are only created at document level, not at line item level. You can create several dispute cases for one document.
______________________________________________________________
SAP AG 48
SAP Utilities ______________________________________________________________
You can create a dispute case from the account balance. This enables you to create dispute cases without an invoice reference, for example, for cases of the type Missing Payment after Dunning Notice. The same dialog box appears for creating the case. Enter the amount specified by the customer as paid as the disputed amount; then assign the case to a business partner. When you create a dispute case, the system proposes contact data of the contact person, such as name and e-mail address from the address data of the business partner; you can overwrite this data. Displaying Dispute Cases In the document display, you can use the function Display Dispute Case to display invoice-related dispute cases. However, this function is only active if such a dispute case exists. If, for example, you have entered various disputed partial amounts for various reasons, you can simultaneously create several dispute cases for one document. If there are several dispute cases for one document, the system first displays an overview of all cases, and there you can select the case you want to display. If you create a new dispute case for a document for which a dispute case already exists, the system notifies you of this before sending the dialog for creating a case. In the account balance you can display an icon on which you can double-click to display a dispute case. To do this, include the field IDISP (placeholder for icon Dispute Case) in a line layout variant for items whose document number is included in a dispute case. You also have to set the indicator Field-Sensitive Double-Click in the settings. With the function Environment -> Account -> Dispute Case -> Display in the menu of the account balance display, you can display a list of all of the dispute cases for the business partner/contract account. With report RFKKDM00 you can select dispute cases across all business partners and contract accounts. This report provides additional selection options to the master data. Changing Dispute Cases When you display a dispute case you can use the function Change to switch the mode and therefore change a dispute case. However, from the FI-CA system you can only change the disputed amount. With case type Incorrect Invoice, you can include additional documents in the dispute case. With the case type Missing Payment, the payments received since the creation of the dispute case are listed on the lower part of the screen. The system only adds the payment amounts posted in the dispute case via the payment lot as potential candidates for the missing payment, since you can assume that payments posted by the payment program cannot be #missing#. From this list of payments you can create one or more payments, identify them as missed, and assign them to the dispute case. The case can then be closed in the dispute system. In the dispute system, an amount field with the total of all potentially suitable payments received since the creation of the case is managed before the assignment of the payment found. With the assignment of the payment found, the document number of this payment and the identification of the related payment lot are included in the case. By double-clicking on these objects in the case you can display the payment document or the payment lot item. With the case type Missing Credit, you can list the credits posted since the creation of the dispute case, identify them and assign them to the case. Only the amounts of the credits that fulfill the following criteria are added in the dispute case: o o They are not statistical They are not down payments
______________________________________________________________
SAP AG 49
SAP Utilities ______________________________________________________________
o o
They were not posted by the payment run They were not posted with the main/subtransaction defined in posting area 0113 for posting payments on account
Follow-On Postings for Dispute Case Follow-on postings for dispute cases are reversals, write-offs, credits (invoice adjustments), and the posting of replacement receivables. In these postings, the corresponding amount fields are updated in the relevant dispute cases automatically. With the exception of the case type Missing Payment, incoming payments are not automatically logged follow-on postings. For example, in the case of an underpayment of an invoice, a dispute case is not created automatically for the residual open amount. Dispute cases are generally independent of the existence of open items and are not tied to the clearing or partial clearing of open items. You can also post invoice-related credits (invoice adjustments) or replacement receivables with transaction FPE1 - if, for example, you reverse an incorrect invoice and then post the corrected invoice. To do this, enter the document number to which the adjustment/replacement receivable refers on the initial screen of the transaction. You can also enter such postings with reference to a dispute case. In this case you have to enter the case ID (external identification of the case). The input help shows you the cases for the business partner, and you can select a case. You can also call up the transactions for reversals and write-offs in the case display of the dispute system. The dispute system calls up the corresponding transaction in the FI-CA system. You can then complete the data and post the document. However, the transactions should only be called up in the display of dispute cases in the dispute system, since the amounts (for example, amount written off) of the case could be changed during the update. Locked dispute cases cannot therefore be updated and you have to subsequently post the corresponding IDoc in this situation. Integration in the Payment Run If an open dispute case exists, you can reduce the amount to be collected from a business partner by the disputed amount. You can make the logic of the reduction dependent on the status, the priority, the complaint reasons, and whether the dispute case is an invoice-related dispute case or a dispute case without invoice reference. The reduction therefore makes more sense for the collection of an invoice for which there is exactly one invoice-related dispute case than for the collection of the first random item to be collected where the dispute case has no invoice reference. In order to be able to make these decisions flexibly, you can define your process logic for event 0610. For a commented example, see the sample module FKK_SAMPLE_0610_DISPUTE. Effects on Customizing Activating Dispute Management You have to activate the integration of SAP Dispute-Management with Contract Accounts Receivable and Payable (FI-CA) at company code level in the FI-CA system. To do this, set the activity Dispute in the activity Set Up Company Codes for Contract Accounts Receivable and Payable in the Implementation Guide for Contract Accounts Receivable and Payable under Organizational Units.
______________________________________________________________
SAP AG 50
SAP Utilities ______________________________________________________________
1.10.16 Dunning
Use
In the dunning history, you can display a text for the business partner. As standard, the text appears with the name and address of the business partner; with a customer-specific function module defined in event 4700, you can adjust this text to meet your requirements. The dunning activity with the Dunning activity: Dunning notice printout (synchronous) (ISU_DUNNING_PRINT_REMIND_0350) function module is no longer part of the example Customizing settings. Use the dunning notice printout from the correspondence container instead. If however, you still want to use the ISU_DUNNING_PRINT_REMIND_0350 event, you must also incorporate the print parameter in the FPVB dunning activities run: 1. 2. 3. 4. 5. 6. 7. 8. 9. Execute the RAVC0ALS report using transaction SE38. Enter FI-CA_MASS in the P_APPL field and choose Execute. Choose layout 0004. Choose Tab page titles. Make the new entry 2| print parameter and select this entry. Choose Position of groups on the tab pages. Make the new entry 1| S2306. Save this entry. Transport the Customizing request with the view.
Effects on Customizing
Register your function module in the Implementation Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules for event 4700.
1.10.17 Enhanced Message Management

Use The Enhanced Message Management Analysis (EMMA) has been enhanced so that you can now analyze the application logs of any jobs in the R/3 system. The transaction code is no longer required to identify the job logs. Instead, business process areas and business process codes have been introduced. The Customizing has been changed so that you now have to activate EMMA for complete business process areas instead of for individual transaction codes; you can also define the suppression of messages during log preparation per business process area. Business process areas consist of similar business processes, such as billing and invoicing. Business process codes rewrite a specific activity of a business process area regardless of whether this activity was carried out by a transaction, a report to be started online or in the background, or by a mass activity (for example, reversal of a document in transaction FP08, or mass reversal of documents with transaction FP08M).
______________________________________________________________
SAP AG 51
SAP Utilities ______________________________________________________________
Installation-specific transactions are evaluated via the interface IF_EMMA_LOGMSG_PROCESS. The Customizing for the case category has been revised with regard to user-friendly aspects. For existing case categories, you have to maintain the assigned business process code, since this has taken over the role of the clarification case type as decisive selection criterion for case generation. You can now use clarification types for several business area codes; they are no longer coupled to an SAP entity and are used as optional specification for the categorization of case categories. The role resolution has been integrated in Customizing for clarification case processing. You can now insert business object attributes into the Customizing for clarification case categories without programming. To do this, connect the objects of the message pool with the new case container via a data flow definition. In the Customizing for the clarification case categories, the administrative data of the author and the last person to make changes is recorded. With transaction FPEMMACGEN (see SAP menu: Periodic Processing -> Mass Processing Administration -> Enhanced Message Management Analysis -> Create Clarification Cases), you can now create clarification cases in a mass run. You can also create clarification cases for individual intervals of a mass activity or for several. Effects on Customizing Make the system settings required for Enhanced Message Management Analysis in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions.
1.10.18 New and Modified Events

Use New Events 0063: Include Document in Collective Bill 0086: Industry Grouping Key for Rounding 0104: Clearing: Arrears Surcharges 0113: Clearing: Transaction for Payment on Account 0175: Account Assignment Derivation for Tax Items in PS-CD 0211: Payment Lots: Propose Key for New Lot 0222: Payment Lot: Include Screen for Customer Fields 0232: Payment Lot: Additional Data for Item 0254: Payment Reversal of Locked Checks 0367: Dunning: Leading Contract Account and Company Code 0501: Document Archiving: Check Header 0505: Document Archiving: Check Complete Document
______________________________________________________________
SAP AG 52
SAP Utilities ______________________________________________________________
0580: G/L Account Check for Accounting Rules 0652: Payments: Partner Bank Selection 0671: Payments: Round Payment Amount 0766: Correspondence: Print Request 0767: Correspondence: Create Request 0798: Printing: Output Mode of Attached Payment Media 1010: Contract Account: Check Company Code Group 1054: Business Partner: Determine CCARD_ID for Automatic Creation 1091: Change Payment Card Data: Print Correspondence 1092: Change Payment Card Data: Create Correspondence 1247: Account Balance: Determination of Document Category 1248: Account Balance: Supplement Context Menu 1250: Dispute: Default Values for Creation of Dispute Case 1251: Dispute: Distribute Follow-On Postings to Disputes 1252: Dispute: Define Communication Channel 1253: Dispute: Include Screen for Customer Fields 1254: Dispute: Additional Activities for Manual Changes 1311: Checks for Posting Area 1010 1742: Mass Activity: Set Locks 1743: Mass Activity: Set Locks, Move Parameters 1766: Mass Activity: Evaluation of Open items OP04 1767: Mass Activity: Integration FI/COPA 1840: Mass Activity: Credit Liability Update 1841: Mass Activity: Credit Liability Update, Move Parameters 1842: Mass Activity: SAP Credit Management Score Replication 1843: Mass Activity: SAP Credit Management Parameters, Score Replication 1970: 1099 Reporting: Determine Reporting Flag 1971: 1099 Reporting: Items Relevant for 1099 Reporting 2065: Interest: Set Value Date 2404: Posting via IDoc: Processing of Customer Header Segment 2504: BW: Open Items, Restrict Selection 2506: Open Item BW Extraction: Parameters for Credit Clearing 2805: ICWC Account Balance: Create Info Items
______________________________________________________________
SAP AG 53
SAP Utilities ______________________________________________________________
2806: ICWC Account Balance: Create Item Groupings 2807: ICWC Account Balance: Prepare Items 2821: ICWC Documents: Correspondence Category Independent Data 2822: ICWC Documents: Correspondence Category Dependent Data 3031: Installment Plan: Determine Print Type for Payment Forms 3910: Migration: Document Transfer - Convert Document Data 3920: Migration: Document Transfer - Check Document Data 4030: SD/FICA Integration: Enhanced Transaction Determination 4256: Credits: Create Additional Correspondence 4257: Credits: After Creation of Correspondence 4258: Credits: Check Payment Method (Transfer/Check) 4500: SAP Credit Management: Supplement FI Summary 4501: SAP Credit Management: Filter Open Items 4502: SAP Credit Management: Determine Liability Category 4600: XI: Add FI Summary for SAP Credit Management 4601: XI: Asynchronous Outbound Interface for FI Summary 5125: Transfer of Open Items: Payment on Account 6060: Cash Desk: Barcode Interpretation 6302: Boleto: Determination of Default Instruction Key 6303: Boleto: Assignment of Instruction Key 6306: Boleto: Selection of Statistical Documents 6351: Boleto: Adjust Data Parameters for Account Statements FKK_EMMA_MASS_CREATE_CASES: Creation of Clarification Cases in Enhanced Message Management Analysis (EMMA) 6507: Requests: Supplement Customer Fields for Approval 9050: Print Collection Letter 9051: Create Collection Letter 9052: Analyze Items from Collection Case 9053: Attributes for Collection Case 9510: BAPI: Create Request (ExtensionIn) 9511: BAPI: Create Request (ExtensionOut) 9512: BAPI: Change Request (ExtensionIn) 9513: BAPI: Change Request (ExtensionOut)
______________________________________________________________
SAP AG 54
SAP Utilities ______________________________________________________________
9514: BAPI: Create Execution Period for Request (ExtensionIn) 9516: BAPI: Read Request (ExtensionOut) 9552: Balance Confirmation: Check Balance 9557: Document Extracts: Additional Data Records for Import 9558: Document Extracts: Additional Data Records for Deletion 9570: Set Mass Locks
Deleted Events Events 0161, 1706, and 1707 are no longer available. Effects on Customizing You define installation-specific function modules in the Implementation Guide for Contract Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific Function Modules.
1.10.19 Conversion of Finnish Bank Statement to MultiCash (Enhanced)

Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the Bank Statement: Finland Reference Payments - Convert to MultiCash report (RFEBFI00) has been enhanced to convert the following types of bank statement files in FI-CA: o o o Reference payments Direct debits Direct invoices
You can also specify further processing of the converted file with the FI-CA MultiCash report, RFKKKA00.
1.10.20 Foreign Currency Valuation

Use In the foreign currency valuation (transaction FPW1) (see SAP menu: Periodic Processing -> Closing Preparations), you can now save the valuation difference for each open item. This enables you to further process the revaluation of an open item in closing preparations, for example, in the key date-related open item list and during reclassification of customers with credit balances. By saving the valuation difference, you can make a more flexible assignment of valuation methods to company codes. This means that the foreign currency valuation is compatible with different GAAPs. This means that you can valuate open items differently according to the reporting view (valuation area).
______________________________________________________________
SAP AG 55
SAP Utilities ______________________________________________________________
Each foreign currency valuation that requires correction postings is logged. You can use the new transaction Log for Foreign Currency Valuation (FPW2), you can get an overview of all foreign currency valuations. You can also reverse individual valuation runs in the display if you have the authorization to run them again later with more current data. Effects on Customizing In the Implementation Guide for Contract Accounts Receivable and Payable under Closing -> Foreign Currency Valuation, define: o o o Valuation methods Valuation areas for each reporting view (for example, HGB, IAS, US GAAP) Valuation variants For each company code and for each local currency, you can configure the valuation method to be used for a foreign currency valuation, and for which valuation area the valuation is to be carried out. The general ledger accounts that the unrealized gains and losses are to be posted to You can define different accounts dependent on the valuation area.
1.10.21 Funds Management

Use As of Release 4.72 you can use Contract Accounts Receivable and Payable integrated with component Funds Management (PSM-FM). Funds Management was only released for industry-specific component Public Sector Contract Account Receivable and Payable until now. As of Release 4.72, Funds Management is released for Utilities Industry, all other industry-specific components can use Funds Management with a pilot project. Prerequisites for the Integration In order to be able to maintain data for Contract Accounts Receivable and Payable in Funds Management, you must: o o Activate Funds Management in Customizing (see Activate/Deactivate Funds Management) Define function module FKK_EVENT_FM_1102 (FM Integration: Account Assignment Derivation) with event 1102 SAP provides this function module as a standard function module. If Funds Management is not active, the function module will not run.
If you want to use the component Fund Accounting, you must define function module FKK_FM_SAMPLE_0032 (Fund Accounting: Supplementing Document Items) with event 0032 . SAP provides this function module as standard function module. If Fund Accounting is not active, the function module is not run. Restrictions Note that Funds Management does not support the update of all postings for Contract Accounts Receivable and Payable. See SAP note 686383 for a list of restrictions. Activating FM Account Assignments in Contract Accounts Receivable and Payable
______________________________________________________________
SAP AG 56
SAP Utilities ______________________________________________________________
All relevant tables and structures of Contract Accounts Receivable and Payable must be enhanced with the organizational unit of Funds Management, the FM area FM Area and the following Funds Management account assignment elements: o o o o o Commitment item Funds center Fund Functional area Funded program
Note that you cannot use the account assignment element Grant of component Public Sector Management at the moment. The exception to this is the document tables of the business partner and G/L items and their counterparts for sample documents. In the interest of performance in systems in which Contract Accounts Receivable and Payable is not used in connection with Funds Management, the FM account assignment fields are not included in tables DFKKOP and DFKKOPK. If you want to connect Contract Accounts Receivable and Payable to Funds Management, you must activate Funds Management in the IMG of Contract Accounts Receivable and Payable. On activation, the FM account assignment fields are included in the tables mentioned automatically. SAP provides corresponding Customer includes for the integration of FM account assignment fields. For more information, see the documentation on activity Activate FM Table Fields for Contract Accounts Receivable and Payable in Customizing. Fields for FM expenditure and revenue account assignment were also included in the business partner items in order to improve performance. As such, the document for the FM account assignment must display zero balance for an invoice. The FM information is available immediately for clearing. FM Account Assignment Logic for Automatically Generated Docs To derive FM account assignments in automatically generated documents (for example, charge postings), you must define derivation rules in Customizing. The system can derive the FM account assignments assigned automatically from the contract account, main and subtransaction. You can also use the derivation rules to determine default values for entering documents manually and entering requests. Enhancing Cash Security Deposits You can also enter an FM account assignment when creating Cash Security Deposits. Commitment Item, Fund, Funds Center and Functional Area are ready for input on the processing screen. If you do not enter any FM account assignment, the system derives these automatically from the rules defined. The derivation also takes place automatically with the migration of Cash Security Deposits. Enhancements for Doubtful Areas and Individual Placings The posting data is supplied automatically with the FM account assignment for the two business transactions. All other FM account assignment data, apart from the commitment item is passed on through the original document. The system determines the commitment item based on event 1750Make Defined Installation-Specific Function Module with Tax Adjustment. This ensures that the FM account assignment is adjusted accordingly. Enhancement with Posting of Delayed Revenue The system copies the FM account assignment automatically from the original document into the delayed revenue posting. In order to use this function, you must include structure IFKKFMOBJ in table
______________________________________________________________
SAP AG 57
SAP Utilities ______________________________________________________________
FKKDEFREV. Updates in Funds Management The update of FM document data takes place at the same time as the transfer of total records to Contract Accounts Receivable and Payable into the general ledger (DFI-GL) with program RFKKGL00 (see SAP menu: Periodic Processing -> Forward Postings -> Execute -> Transfer to General Ledger). The update of payments and other clearing transactions take place automatically in Contract Accounts Receivable and Payable. The system updates all clearings and clearing reversals as well as invoices and payments on account online in the totals tables of Contract Accounts Receivable and Payable. Enhanced Transactions in the Utilities Industry-Specific Component As of SAP Utilities Release 4.72, utilities-specific postings in Contract Accounts Receivable and Payable and transactions that trigger these postings can now process Funds Management data and transfer them to Funds Management where they are verified with the general ledger. The following transactions have been enhanced for SAP Utilities 4.72 so that the Contract Accounts Receivable and Payable in SAP Utilities can be fully integrated with Funds Management: 1. Manual Postings in IS-U-CA (Transaction: Post Document FPE1): You can now enter commitment item, fund center, fund and functional area as Funds Management (FM) account assignment elements in manual postings. If you do not enter a FM account assignment, the system transfers the data automatically based on the allocation in the derivation rule for Funds Management data (defined in the transaction: Derivation Strategy for FM Object Assignment Customizing FMDERIVE). This enhancement is implemented in function module ISU_EVENT_1100. 2. Write-off The Write-Off Items transaction (FP04) has been enhanced so that the FM account assignment can be determined for a write-off document. For write -off documents in posting area 1052 (Write-Off: Specifications and Default Values) or 1053 (Mass Write-Off: Specifications and Default Values ) select one of the following three FM account determination options in the field Inherit CO Account Assignments from Item To Be Written-Off. o o o The FM account assignment is determined from the cost element of the expense or sales revenue account for the write-off. The FM account assignment is inherited from the open item to be posted. The FM account assignment is determined from the derivation rule for FM object assignments that is defined for the posting document.
This enhancement is implemented in function module ISU_EVENT_5030. 3. Invoicing Invoicing derives the FM account assignment for postings triggered in Contract Accounts Receivable and Payable. This is done at a subtransaction level that refers to billing line items. If the business partner lines are grouped together before the IS-U-CA document is posted in invoicing, the FM account assignment is also included. Effects on Customizing You define the settings for Funds Management in the IMG of Contract Accounts Receivable and Payable under Integration -> Funds Management (PSM-FM).
______________________________________________________________
SAP AG 58
SAP Utilities ______________________________________________________________
Define FM account Assignment Derivation You define the FM account assignment derivations in the activity Define FM Account Assignment Derivation. Contract Accounts Receivable and Payable uses the derivation strategy from Funds Management by default (see the IMG of Funds Management) Government Master Data -> Allocations to Account Assignments from Other Components -> Define Account Assignment Derivation). If you want to use your own derivation strategy in Contract Accounts Receivable and Payable, you must set the indicator Use Derivation Strategy of Contract Accounts Receivable and Payable in maintenance view TFK_FMDERIVSTRAT . To do this, call the view on this using transaction SM30. However, note that the derivation strategy of Contract Accounts Receivable and Payable is no longer supported. Fund Accounting If you want to use Fund Accounting, you must activate the Fund in the IMG of Public Sector Management under Basic Settings -> Activate Account Assignment Elements. You can also read the activation status in the IMG of Contract Accounts Receivable and Payable in activity Activation Status of Fund Accounting. When the fund is active the system generates additional clearing lines that ensure that the balance is cleared for each document and company code. Define G/L account for the fund clearing in activity Define Accounts for Fund Clearing .
1.10.22 IDoc Interfaces for Communication with External Billing Systems

Use Evaluation of Mass Runs by Enhanced Message Management Analysis The evaluation of Enhanced Message Management Analysis has been activated for the following programs: o o o Document Data Transfer (transactions FKK_EBS_TOI_COPA and FKK_EBS_TOI_COPA_E) Linking with Archive Data (transactions FKK_EBS_ARC and FKK_EBS_ARC_E) Reversal of Documents (transactions FKK_EBS_MRD and FKK_EBS_MRD_E)
Functional Enhancements in the IDOC FKK_EBS_TOI_COPA (Document Data Transfer from External Billing Systems) To define and process customer- or project-specific document header data, you can now define a replacement segment for the segment E1FKK_EBS_TOI_HEADER in Customizing. You can use event 2404 to process header segment data. You can also change the standard processing by defining the standard segment E1FKK_EBS_TOI_HEADER in Customizing. For example, you can change the field BLART or AWTYP. In event 2404, you can also create the object relations between documents via the interface T_FKKOPREL. By defining a customer- or project-specific segment you can transfer the additional data contained
______________________________________________________________
SAP AG 59
SAP Utilities ______________________________________________________________
therein, for example, the classification key, to the document header. The optional field DOC_TYPE (document type) has been added to the segment E1FKK_EBS_TOI_HEADER. With this segment you can override the document type defined in the interface Customizing at document level. Maintaining Object Relations at Item Level The maintenance of object relations (interface T_FKKOPREL) has been added to event 2413. This means that you can now fill the object relations at document item level from a customer- or project-specific ITEM additional segment. Effects on Customizing In the Implementation Guide for Contract Accounts Receivable and Payable under Data Transfer -> Communication with External Billing Systems -> Transfer of Accounting Documents, the following activities have been enhanced: o o Basic Settings for Document Transfer You can now define a customer- or project-specific header data segment. Define Translation of External Tax ID You can now define (optional) a tax on sales and purchases code as well as the condition key for each external tax code. If you define a tax on sales and purchases code, this is available in events 2405 and 2406 for comparison.
1.10.23 Modified IMG Activities in Contract Accounts Receivable and Payable

Use There have been changes to the following system settings with Release 4.72: Organizational Units As part of the changeover of the company code concept in Contract Accounts Receivable and Payable, you now have to make the settings for the company code in the following activities: - Set Up Company Codes for Contract Accounts Receivable and Payable - Define Company Code Groups - Assign Company Codes to Company Code Groups Basic Functions o Contract Accounts The activity Activate Additional Checks for Changes to the Business Partner Master Record has been moved from the section Technical Settings to the section Contract Accounts. Postings and Documents In the section Define Account Assignments for Automatic Postings, the activity Define CO Account Assignments has been renamed to Define CO Account Assignment Keys. Here you can also define the required specifications for the Nota Fiscal in Brazil. To do this,
______________________________________________________________
SAP AG 60
SAP Utilities ______________________________________________________________
Contract Accounts Receivable and Payable uses the Customizing of the standard FI. Business Transactions o Payments The activity Specifications for the Clarification of Incoming Checks under Basic Functions -> Check Management has been renamed to Define Specifications for the Clarification of Cashed Checks. The activities in the sections Cash Desk and Cash Journal under Business Transactions -> Payments -> Processing of Incoming/Outgoing Payments have been grouped under the section Cash Desk/Cash Journal. The activity Maintain Responsibilities for Cash Journal Users has been moved from the IMG to the menu (see SAP menu Payments -> Cash Journal -> Responsibilities). In the section Creation of Incoming/Outgoing Payments, the activity Define Specifications for Responsible Company Code has been replaced by the activity Define Specifications for Paying Company Code. In the same section, the activity Specifications for Transferring Open Items to the Responsible Company Code is no longer available. o Submitting Receivables to Collection Agencies The activity Define Strategy for Derivation of Collection Agency Responsible has been renamed to Define Derivation Rules for Collection Agency Responsible and has been enhanced.
Technical Settings The activity Activate Dependency Check for Business Partner Master Data Changes is no longer available.
1.10.24 New IMG Activities in Contract Accounts Receivable and Payable

Use In the Implementation Guide for Contract Accounts Receivable and Payable, the following new settings are available:
Basic Functions o Contract Partner This section and the subsection Changes to Payment Transactions, with the activities Client-Specific Settings, Company Code-Specific Settings, Define Processing Variants, and Define Rules for Follow-Up Actions are new. Bank Chains In this section you can now Define Scenarios, Define Bank Chains, and Configure Bank Chains as in the component Financial Accounting (FI).
______________________________________________________________
SAP AG 61
SAP Utilities ______________________________________________________________
Postings and Documents In the section Automatic G/L Account Determination, you can Define Accounts for Surcharges on Late Payment. Requests For requests you can Make Settings for Approving Requests. Open Item Management You can define Short Account Assignments for Transfer Postings in Account Maintenance. Enhanced Message Management The settings for maintaining clarification case categories have been changed over as follows: Specifications for Processing Clarification Cases - Generate Selection Screen for Clarification List - Define Reasons for Reversing Clarification Cases - Specifications for Customer-Defined Business Processes and Messages - Define Customer Business Process Areas for Message Management - Define Customer Business Processes for Message Management - Define Customer Business Processes for Processes from CIC
Business Transactions o Processing Incoming and Outgoing Payments The Customizing for the cash desk/cash journal has been changed over (see release information). Boleto In this section you can make all of the settings required for processing Boletos in Brazil. Write-Offs For write-offs you can Maintain Alternative Expense and Contract Account. Transfers You can now Define Default Values for Transfer Reasons. Doubtful Entries and Individual Value Adjustments You can Define an Age Grid for Value Adjustment Variants.
Integration o Financial Supply Chain Management Biller Direct You can make the following settings for the integration of SAP Bille Direct: - Define Clearing Account for Overpayments - BAdI: Determination of Bill Details - BAdI: Assignment of Business Partners to User IDs
______________________________________________________________
SAP AG 62
SAP Utilities ______________________________________________________________
- Specifications for the Integration of SAP Dispute Management Credit Management You can make the following new system settings as part of the integration of SAP Credit Management: - Activate Credit Management - Maintain Credit Segments - Assign Open Items to Credit Segments - Define Specifications for Credit Management Dispute Management For the integration of SAP Dispute Management you can Make Basic Settings for Dispute Management.
Funds Management The following settings have been provided for the integration of Funds Management in the FI-CA standard: - Activate FM Table Fields for Contract Accounts Receivable and Payable - Define FM Account Assignment Derivation - Display Activation Status of Fund Accounting - Define Accounts for Funds Clearing
Closing Operations o In the Foreign Currency Valuation you can: - Define Valuation Areas - Define Valuation Variants - Define Valuation Area-Specific Accounts for Exchange Rate Differences In Reclassifications you can: - Define Summarization Accounts - Define Company Codes for Summarization
Technical Settings You can Activate Parallel Update in Cash Management. Program Enhancements As part of the introduction of the classification key you can activate the prepared enhancements.
1.10.25 Information System

Use Preselections of Master Data (Transaction FPSELP)
______________________________________________________________
SAP AG 63
SAP Utilities ______________________________________________________________
When you select by dunning data, you can now consider only open items if required previously all cleared items were selected automatically. Data Extracts (GDPdU) From Release 4.72, all developments for the realization of the German Principles of Data Access and Verifiability of Digital Documentation (GDPdU) area available in all releases maintained by SAP. In Releases 4.64, 4.63, and 4.61 however, only the export programs FPDE_EXP, FPDE_AEXP, and FPDE_EXTR are available. All export programs support the SAP format AIS, which can be imported into IDEA. For the Contract Accounts Receivable and Payable objects, the following export, import, and deletion transactions are available: o Document Extracts FPDE_EXP FPDE_AEXP FPDE_IMP
FPDE_DEL You can also select SD documents for the FI-CA documents and export them. o Partner Extracts o FPDEP_EXP FPDEP_IMP FPDEP_DEL
Customizing Extracts FPDEC_EXP FPDEC_IMP
FPDEC_DEL You can use the transactions FPDE_EXTR (evaluation system) and FPDE (extract overview) for all extract objects. Evaluating Open Items Transaction FPO4P provides you with a parallel variant for transaction FPO4. For each interval, this transaction creates a list and a list with the totals records (similar to transaction FPO1P (Open Items for Key Date Parallel). However, in contrast to transaction FPO4, transaction FPO1P has certain restrictions. Parallelization is therefore only possible if the layout sorting corresponds to the parallelization object. The output is not in ALV format and no additional output in the dataset is possible. For transaction FPO4, the memory has been optimized. If you do not want to display line items, the report no longer collects all items in the memory if you have selected an object and a variant (technical settings) (see also the documentation for the report). You can now group the spool requests for individual intervals for the evaluation with transaction FPO1P and transaction FPO4P. Transactions FPO1 and FPO1P can now also calculate the evaluation for different currency types and therefore consider a currency valuation. Transaction FPRECL has therefore also been changed. You can now also post adjustments to reclassifications for different currency types.
______________________________________________________________
SAP AG 64
SAP Utilities ______________________________________________________________
1.10.26 Deferral and Installment Plan

Use Clearing Locks on Installment Plan Items When you display installment plans, you can now also display the clearing locks as well as the payment, dunning, and interest locks. When you create and change installment plans, you can create and set clearing locks. Improved Display of Processing Locks Previously, you could only display the different processing locks (payment, dunning, interest, and clearing locks) in installment plan items via a joint icon (lock), which, when you placed the cursor on it, displayed the type of locks that existed in a quick info. You could only see details, such as the lock reason, by double-clicking on the icon. The display of the installment plan items now also has, in addition to the joint lock icon, a column for each processing lock with the respective lock reason. If there are several locks of the same type with different lock reasons, a tilde appears (~). Double-click on one of these fields to display the details for the locks. Easier Maintenance of Processing Locks Previously, you could only maintain processing locks (payment, dunning, interest, and clearing locks) for installment plan items by double-clicking on the field for displaying the lock icon. Then you had to select the type of lock. Now you can maintain the lock you have selected directly by double-clicking on one of the new table fields. You can also set an unlimited (time) lock by entering a lock reason directly. If there is only an unlimited (time) lock for a lock type, you remove this from the table field by deleting the lock reason. Selection by Classification Key You can also select items for which a new installment plan is to be created by classification key. Standard Company Code instead of Responsible Company Code If the system cannot derive a unique company code from the original receivables when you are creating an installment plan, the system posts the installment plan to the standard company code. New Display Fields in the Installment Plan History When you display the installment plan history (SAP menu: Account -> More Information -> Installment Plan History), the contract account, business partner, and address of the business partner are displayed for each installment plan. New Fields in the Header Data of the Installment Plan History The fields Number of Installments and Distributed Interest and Charges are stored in the header data for the installment plan history. Determination of Company Code, Contract, Business Area, and Business Place No Longer in Event 3000 When you create an installment plan, the company code, contract, business area, and business place are taken from the original item as standard, as long as these fields have the same value in all original items
______________________________________________________________
SAP AG 65
SAP Utilities ______________________________________________________________
selected. Previously, this check took place in a standard module processed in event 3000. This check now takes place in the standard coding before event 3000. The source code of the standard module FKK_SAMPLE_3000 has been deleted. If you do not want to fill these fields in the installment plan, or want to enter other values, you can do this by defining event 3000 accordingly. Printing of Payment Forms for Installment Plans - List of Correspondence Created When you are printing payment forms for installment plans (SAP menu: Periodic Processing -> For Contract Accounts -> Correspondence -> Print Installment Plan Payment Forms), you can use the entry Correspondence in the environment menu to display a list of the correspondence created (installment plan letters and payment forms).
1.10.27 Integration
Use Event 4030: Determination of SD/FI-CA Transaction Before the upgrade from Release 4.6* to Release 4.7*, you have to close all of the reconciliation keys in the old system and transfer the postings to the General Ledger and Profitability Analysis (CO-PA). Event 4030 has been introduced to determine the main and subtransaction of an FI-CA document during the transfer of an SD billing document. In this event you have access to all of the information in an SD billing document, which means that a more detailed transaction determination is possible here in contrast to Customizing. With the new event 4040 you can restrict the selection of contract accounts when you create/change an SD order. In the SD document flow, FI-CA documents that have already been archived are also displayed now. Transfer of Totals Records to the General Ledger (Report RFKKGL00) Errors in the transfer of FI-CA totals records to the general ledger no longer lead to a program termination. From Release 4.72, report RFKKGL00 continues the transfer with the next company code and logs the errors in the spool list. There you can check the completeness of the transfer. Integration of FI-CA with SAP Credit Management With SAP Credit Management you can manage liabilities and scores for a business partner. The central Credit Management server manages information from different systems, such as CRM, Contract Accounts Receivable and Payable (FI-CA), and Accounts Receivable Accounting (FI-AR), and carries out operational credit queries. The use of the interface technology of the Exchange Infrastructure means that you can also connect external systems to SAP Credit Management. FI-CA now has an interface for transferring credit information from SAP Credit Management. The FI-CA document interfaces (report RFKKBIB0, BAPI, IDoc interface) support the transfer of the partner message ID for SAP Credit Management. This transfer guarantees the synchronization of the liability update over several systems. In FI-CA there are mass activities for the following activities:
______________________________________________________________
SAP AG 66
SAP Utilities ______________________________________________________________
o o o
Sending the liability for a business partner to SAP Credit Management Sending an FI summary to SAP Credit Management Replication of the score in SAP Credit Management
FI-CA also supports the liability query for the online credit check in SAP Credit Management. You can influence the program flow in the following events: o o o 4500: Add FI Summary 4501: Filter Open Items for Liability Determination 4502: Determination of Liability Category
For a description of the integration of industry-specific processes, see the release information for the corresponding industry components. Effects on Customizing You configure SAP Credit Management in the Implementation Guide for Contract Accounts Receivable and Payable under Integration -> Financial Supply Chain Management -> Credit Management. o In order for the internal processes of Contract Accounts Receivable and Payable (for example, creditworthiness) to derive the data from SAP Credit Management, you have to activate Credit Management here. In the activity Define Specifications for Credit Management, you define the default values, such as the interest rate for the liability subject to interest and the liability category. The credit segments that you enter in the activity Maintain Credit Segments must agree with those of SAP Credit Management. There the credit segments are used to split the liability into different areas (for example, country A and B). In the activity Assign Open Items to Credit Segments, you use the parameters Posting Area, Division, Account Determination ID, and Business Area to decide which credit segment an open item is to be assigned to.
o o
1.10.28 Interest Calculation

Use Interest Calculation Rule There are two new calculation methods for defining interest calculation rules: o 30/30E You should only use the method 30/30E for exponential interest calculation. The system calculates exponential interest on a monthly basis. act/actY In the method act/actY, the suffix Y stands for Year. It indicates that the calculation is based on the number of days in a calendar year.
______________________________________________________________
SAP AG 67
SAP Utilities ______________________________________________________________
Setting #Interest Calculation To Date With a function module processed in event 2065 you can change the date for the Interest Calculation To for clearing items. For amounts cleared in the account maintenance, as standard the due date of the invoice and clearing date of both items are used to calculate the interest. In event 2065 you can use the due date of the invoice amount and the value date of the payment amount to calculate the interest for amounts cleared in the account maintenance. Effects on Customizing You define interest calculation rules in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Interest Calculation -> Item Interest Calculation -> Define Interest Calculation Rule.
1.10.29 Business Locks

Use Setting Processing Locks With the new transaction FKLOCK2 (Set Processing Locks) in the SAP menu under Periodic Processing -> For Contract Accounts, you can create processing locks. From the selection criteria Business Partner, Contract Account, Contract, Company Code, you can set mass locks for a combination of Lock Category, Process, Lock Reason. Locks created in this way contain the data of the creating run in the fields DFKKLOCKS-LAUFI and DFKKLOCKS-LAUFD in table DFKKLOCKS. You have to define event 9570 for the following application-specific locks: Lock Category 21 22 41 51 Object Insurance policy Partner locks for insurance policy Utility contract Contract object partner account
To delete mass locks, you can use transaction FPLKDEL (Delete Mass Locks Set) in the SAP menu under Periodic Processing -> For Contract Accounts.
1.10.30 Mass Activities

Use Repeated Processing of a Job Interval If an interval cannot be processed in a payment run, interest run, or interest calculation run for cash security deposits because the data is locked by another processing function, the system can restart the
______________________________________________________________
SAP AG 68
SAP Utilities ______________________________________________________________
processing of this interval automatically and as frequently as required. Effects on Customizing You have to enter the maximum number of repetitions in the field Maximum Int. Repetitions in the specifications for General Control on the tab page Job Control under Technical Settings -> Prepare Mass Activities in the Implementation Guide for Contract Accounts Receivable and Payable.
1.10.31 Master Data

Use Changing the Bank Data of a Business Partner With the new transaction Maintain Payment Data (FPP4) (see SAP menu: Master Data -> Business Partner), you can: o o o o o o o Create new bank details Change existing bank details Delete existing bank details Create new payment cards Change existing payment card details Create customer contacts Print confirmation letters
This makes changing business partner-related bank data much easier. In the transaction Maintain Payment Data, you can, for example, change the bank details of a customer who changes from being a cash payer to a direct debit payer simultaneously in the business partner master record and in dependent objects, such as the contract account. You can also control follow-up actions, such as reversing dunning notices, by means of flexible rules. If you set the indicator Create Bank ID in the client-specific settings in Customizing, in event 1053 you can determine new bank details ID for the business partner concerned. If you set the indicator Create Credit Card ID in the client-specific settings in Customizing, in event 1054 you can determine a new payment card ID for the business partner concerned. With a function module processed in event 1083 you can make further changes to the contract account when you save the data. In this event, you can, for example, change the field Posting Control Group in the contract account if a customer changes from being a cash payer to a direct debit payer. Effects on Customizing You make specifications for changing bank data in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Contract Partner -> Changes to Payment Transactions in the following activities: o o Client-Specific Settings Company Code-Specific Settings
______________________________________________________________
SAP AG 69
SAP Utilities ______________________________________________________________
o o o
Define Processing Variants Define Rules for Follow-Up Actions Specifications for Posting Credits in Follow-Up Actions
If you want to send confirmation letters, define the required form for correspondence type 0036 under Basic Functions -> Correspondence -> Define Application Forms for Correspondence. You define event modules under Program Enhancements -> Define Customer-Specific Function Modules.
1.10.32 Evaluation of Open Items

Use Currency Type and Currency Valuation When you enter a currency type on the selection screen for the Key Date-Related Open Item List (transaction FPO1), the report replaces the first local currency with a currency with this currency type. If you also enter a valuation variant and a valuation key date, the report does not display the original amounts of the items; instead, it displays the amounts calculated by the currency valuation for the valuation key date.
1.10.33 Processing Incoming and Outgoing Payments

Use Payment Lot: Archive Connection From Release 4.72, you can display archived lots and non-archived lots. When you display documents posted by a payment lot, you can also display the related payment lot items if the lot has been archived. This display option requires an additional index table that is created during archiving with effect from Release 4.72. For payment lots archived before 4.72, you can recreate these index entries using report RFKKPLAR. Payment Lot: Default Value for New Key If you want to create a new lot, you can have the system default a suitable key. The prerequisite for this function is that you have registered a suitable module for event 0211. Payment Lot: Installation-Specific Fields in Items If additional fields are included in the payment lot item via the customer include CI_FKKZP, you can display these on the detail screen and the list screen. To do this you have to provide an include screen. The program name and the number of the include screen are determined in event 0222. For more information see the documentation and the coding examples in the related sample function module FKK_SAMPLE_0222. Payment Lot: Installation-Specific Additional Function
______________________________________________________________
SAP AG 70
SAP Utilities ______________________________________________________________
The detail screen for the payment lot item contains an installation-specific addition function that you can define to meet your requirements. This function is available under Extras -> XXX, and you can also call it up via a separate pushbutton (optional). In event 0232, the texts for the processing menu and the function key (xxx) are determined, along with which function module is to be called when the user executes this function. For more information, see the documentation for the function module FKK_SAMPLE_0232. Payment Lot: Clarification o o o o From Release 4.72, you can have the clarification account determined dependent on the document type. Posting area 1040 has been extended accordingly. From Release 4.72, clerks can also create notes during clarification. If clearing is to be posted online during clarification, the note to payee entered in the payment lot also appears on the processing screen for the open items (first 80 characters). In the search with errors function, you can now also search for business partner with just the name (and optionally the city) in the field Sold-to-Party/Account Holder.
Payment Lot: Changes to Protected Fields o In check lots, you can use the special function Correct Check Number to correct the check number for individual payments in lots that have already been closed or posted. You may need to make a correction, for example, if, when creating the check deposit list, you discover that check numbers have been entered incorrectly. To carry out this function you need authorization 014 for authorization object F_KK_SOND. You make the change in the check lot display. On the first screen, choose Edit -> Correct Check Numbers. Then call up the detailed display for the check payment to be corrected and select Edit -> Correct Check Numbers. The check number field is then ready for input you can overwrite the number and save. In payment lots created automatically, you can change the bank data of the payer and the note to payee during clarification. A correction is necessary, for example, if a data reader has incorrectly interpreted a hand-written note to payee. To carry out this function you need authorization 017 for authorization object F_KK_SOND. To make the fields on the tab pages Payment Data or Note to Payee ready for input, select Edit -> Change Bank Data.
Payment Lot: Transfer with Report RFKKZE00 In the transfer structures BFKKZP and BFKKZS (ZFKKZP/ZFKKZS), the field lengths of the fields SELW1, SELW2, and SELW3 have been extended from 30 characters to 35. If you do not create the files with these record structures with ABAP programs, you may have to adjust the data declarations and the coding in the programs. Effects on Customizing Payment Lot: Clarification You define the clarification account in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Payments -> Processing of Incoming/Outgoing Payments -> Define Clarification Account. If you want to use the document type as selection criterion, you first have to select the field Document Type as additional key field via Goto -> Key Selection.
______________________________________________________________
SAP AG 71
SAP Utilities ______________________________________________________________
1.10.34 Payment Transactions

Use Payment Program: Restriction to One Payment Card Type From Release 4.72, you can restrict the payment run to one payment card type. You can then run separate payment runs for each payment card type, event though the payment method is always the same card payment. For contract accounts with other payment card types, a corresponding message is created in the application log and a payment exception is created. Payment Program: Selection of Partner Bank via New Event In the new event 0652, you can override the automatic selection of partner banks created by the payment program. In the standard system, the partner bank is selected as a result of the bank details defined either in the contract account or the contract (differentiated by incoming payment and outgoing payment). You can override this by explicitly specifying bank details in the line item. However, it is not possible, for example, to select a partner bank dependent on the currency of the items paid if these bank details are not entered in the items to be paid. Using event 0652, you can now set a different bank details ID dependent on the items to be paid, or prevent payment. See the documentation for function module FKK_SAMPLE_0652. Payment Media Creation: Settings for the Note to Payee The standard options for defining the note to payee have been enhanced for the creation of payment media. In the user-defined specifications, you can now specify the number of items to be prepared only once per payment. This avoids the contents of PAYH and PAYHX being output per item, even though these are the same for all items. In the definition of the item content (FQP5 -> Note to Payee: Content), the sequence (item number) decides whether the content is prepared per payment or per item. If, for example, you have specified 2 information items per payment and 1 information item per item, you have to provide a total of 3 items with content. The first two apply per payment, which means that here only the fields from the structures PAYH and PAYHX are useful. The third item is then repeated for each item. The fields from the structure PAYP are useful here. Payment Media Creation: Correspondence Banks If you use the payment media formats EDIFACT, S.W.I.F.T. (MT 100, 101, 103, 104, 200, and 202), (customer development), from Release 4.72 you can define correspondence banks. This means that you can specify a bank chain with up to three intermediary banks (correspondence banks) in Customizing for the transfer from one bank to another. You can define general and recipient-specific bank chains. You then specify recipient-specific bank chains in the transactions for creating and changing business partner data (FPP1, FPP2) on the tab page Payment Transactions, in the area Bank Chains. The function module FI_PAYMENT_BANK_CHAIN_SET determines the bank chains during the payment media creation and places them in the corresponding structures. If you want to use the function for the payment media formats stated, you have to add the call of the
______________________________________________________________
SAP AG 72
SAP Utilities ______________________________________________________________
function module FI_PAYMENT_BANK_CHAIN_SET to the function modules defined for the events 20 and 30, or, for customer-defined developments, the events 21 and 31. The function module FI_PAYMENT_BANK_CHAIN_SET contains the data in the corresponding event module as import parameter. Check Management: New Status for Processing Check Locks A new check status (Locked) has been introduced with Release 4.72. This means that you can lock a check and report the lock to the bank, without having to reverse the related payment or issue a replacement check. The check is locked in check management and reported to the bank using transaction FPCHX. After a specific deadline (usually 24 hours) the bank guarantees that this check can no longer be cashed. You reverse the related payment document after this deadline by regularly scheduling transaction FPCHS so that the cleared items are open again. By running the payment run again you can create a new check if required. If checks are cashed within the deadline, you can define, in the settings for the voiding reason, whether the checks are to be deemed 'cashed' automatically or whether clarification cases are to be created. This procedure is interesting for US customers and is known by the name 'Stop Payment'. It is an alternative to the previous way of issuing a replacement check. Invalid checks that have not yet left the company premises should be voided and reissued as previously. A check lock is not necessary in these cases. Check Management: Enhanced Maintenance in Change Mode If you want to correct the data of a check that was created via a payment run, only a few fields are modifiable. You cannot even change a status set by accident. From Release 4.72, the button 'Administrator has been added in change mode (F6). When you press this button, additional fields are ready for input. To carry out this function you need authorization 018 for authorization object F_KK_SOND. Effects on Customizing You make the settings for bank chains in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Bank Chains: o o o Define Scenario Activate Bank Chains Set Up General Bank Chains
In the activity Define Scenario, you define for each scenario, whether the bank chain is determined via the general bank chain search and/or via the partner-specific bank chain search. If both fields are set, the partner-specific bank chain search has priority over the general bank chain search. Using the fields Sender Bank, Recipient Bank Country, Recipient Bank, and Currency, you can define a ranking for the bank chain search for each scenario. SAP delivers four standard scenarios; you can also generate your own scenarios. The bank chains that you create in the activity Set Up General Bank Chains are independent of the bank details of a business partner or of the house banks. For a bank chain ID, you can create up to three intermediary banks. The intermediary banks are linked independently of the recipient and sender banks. Check Management: Settings for Voiding Reasons If you want to use the new check status 'Locked, you need a voiding reason or a lock reason, as for
______________________________________________________________
SAP AG 73
SAP Utilities ______________________________________________________________
voiding. Whether a reason is permitted as a lock reason depends on the indicator Lock. You can also define whether the cashing of a locked or voided check is to be posted automatically or whether a clarification case (for check encashment) is to be created. In the field Activity, you can enter a 6 digit code to control additional activities (for example, setting limited clearing locks) in customer modules. You can evaluate this field directly or use it as a key for your own customer table.
1.10.35 Collections in the Print Workbench

Use Using Collections, you can now group application forms to process them together. A Collection is an application form of the form type Collection. In a Collection, you can group both application forms from the same form class, and also application forms from different form classes. You can define your own parameters for the technical components of a Collection, for example, a specific printer. You can classify the individual application forms so that they are issued sequentially or bundled. You can process Collections using transaction EFRM (SAP menu: Print Workbench -> Application Form -> Process), as for application forms.
1.10.36 Postings and Documents

Use Postings and Documents: Classification Key as New Characteristic in Document The new attribute Classification Key has been added to the Contract Accounts Receivable and Payable document and the request. The classification key provides a similar function to the reference number, but allows keys with a length of up to 35 characters. The classification key is an enhancement supported in the system. This means that the attribute is not initially active in the system delivered; you have to activate it explicitly in your installation. Functions of the Classification Key The classification key o o o o Can be entered in the document header Is available as input field in the document display, document change, document reversal, and mass reversal, and you can use this field to identify the required document(s) Is inherited in the business partner items and can be displayed in the account balance or in the processing of open items Can be used as selection criterion in the account balance, in the selection of open items (for example, in the payment lot or in online posting), and for the write-off or creation of an installment plan
______________________________________________________________
SAP AG 74
SAP Utilities ______________________________________________________________
Is a possible selection criterion in payment advice notes for incoming payments
Activating the Classification Key You activate the field Classification Key in Customizing using a report that creates the required fields and database indexes. In test mode, the report shows which enhancements would be made. If the classification key is active and you have posted documents with classification keys, the system administrator must update the database statistics for table DFKKKO. This is the only way to make sure that the new indexes are also used. If you use requests, the same applies for table DFKKORDERPOS. Deactivating the Classification Key You can deactivate the classification key but only manually. To do this, you have to remove the field OPORD from the CI includes to which it was added. You then have to convert the database tables; this can involve a long runtime if there are a lot of data records affected. SAP therefore recommends that you weigh-up the use of the classification key and then adhere to this decision. Postings and Documents: Negative Postings From Release 4.72 you can create negative postings in Contract Accounts Receivable and Payable. A negative posting reduces the transaction figures for the account posted to in the general ledger. A debit posting as negative posting therefore does not lead to an increase of the debit transaction figures; it leads to a reduction of the credit transaction figures. This enables you to show transaction figures for accounts after an incorrect posting and subsequent correction (for example, invoice posting and reversal) as if neither the incorrect posting nor the correction had taken place. Negative postings have been supported in the general ledger (FI-GL) for a long time. You decide whether to permit negative postings at company code level. The corresponding setting in the company code table is also effective for Contract Accounts Payable and Receivable. In addition, in Contract Accounts Receivable and Payable, the document type decides whether a posting is to be posted negatively. You can designate a document type such that negative postings are always created, or such that negative postings are only created for corrections in the same fiscal year. For more information about the setting for the document type, see the Customizing for the document types and the field documentation for the field Negative Posting. A description of negative postings for the most important business transaction follows: Reversal For a reversal, the document type used decides: o o o Whether a negative posting is never permitted Whether a negative posting is always permitted That a negative posting is created if the posting and reversal are in the same fiscal year
A special feature is that the items in the reversal document for which the account to be posted to has been
______________________________________________________________
SAP AG 75
SAP Utilities ______________________________________________________________
swapped in comparison to the original document are not posted negatively This can be the case for aperiodic reversals (swap of P&L accounts) or for posting incoming payments where the reversal is used to post back to the clarification account. Resetting Clearing After resetting clearing, all accounts should appear as if the clearing had not taken place. This means that the inverse posting of cash discount, small differences, exchange rate differences, and taxes that were posted due to the clearing are to be posted negatively. The display in the receivables accounts is retained. Example You reset clearing for a payment received. After the clearing reset, the payment with clearing of open items becomes a type of payment on account again, which means that the credit from the payment is an open item in the receivables account. From the view of the account balance in the receivables account, it is irrelevant whether there was a payment on account or whether items were cleared. Returns Returns should be treated like reversals. The first item in a returns clearing account is, however, never posted negatively; the same applies to returns charges. Individual Identification of Individual Posting Items If you want to post a document for which negative postings are required for all items manually, all you have to do is select an appropriate document type. However, if you only want to post individual items negatively, you have to enter the entire transaction in two documents. Example Transfer posting from an incorrect G/L account to the correct G/L account. The reset in the incorrect G/L account should be posted negatively, the posting to the correct account not. First enter a negative posting: Clearing account to incorrect G/L account. Then a 'normal posting: Correct G/L account to clearing account. Payments on Account If, on receipt of payment, you first post on account instead of clearing immediately and then carry out clearing later, (for example, via account maintenance or during processing of a subsequent payment), the debit and credit side of the receivables account increases by the amount of the payment on account. If you want to avoid this effect, make sure that every clearing of a posting on account is posted negatively. To do this, you have to indicate in Customizing for the main and subtransaction used for payments on account that each clearing of this item is to be posted negatively. Postings and Documents: Parallel Open Item Processing for Partners If a business partner has several contract accounts, before Release 4.72, it was not possible for two clerks to process open items in different contract accounts for this business partner simultaneously (for example, during account maintenance). Parallel processing in different accounts of a business partner is possible from Release 4.72. Postings and Documents: Hold Status of Open Item Processing During manual processing of clearing transactions, you can save the status of open item processing and
______________________________________________________________
SAP AG 76
SAP Utilities ______________________________________________________________
reload it later. For this purpose, the new functions Hold Processing Status and Retrieve Processing Status are available on the processing screen for open items. When you hold the status, you have to specify an identification. You can hold several processing statuses in parallel for the same object (for example, same business partner, same collective bill). A processing status is held in the system for 30 days. This period starts from the last time the status is saved. For each processing status, the system also saves the object being processed in addition to the identification. This is either the business partner to whom the open items belong, or for assignment at detail level, the collective bill, the installment plan or the bundle for which assignment of clearing amounts is to take place at the level of the related original item. If the business partner is not unique, the partner with the most active items is set. When you retrieve a held status, in the detail assignment for collective bills, installment plans, and bundles, only identifications that belong to the object named are permitted. The possible entries help (F4) offers a correspondingly restricted selection. When you retrieve a held status during the processing of open items for one or more business partners, the identifications permitted are those where the business partner held is correct for at least one of the currently selected items. The possible entries help (F4) also offers a correspondingly restricted selection here. In general, the held status is mixed with the current selected items. These can be different to the items that were selected when the processing status was held. Possible causes are: o o o Other selection criteria Clearing or partial clearing that has taken place in the meantime Different amounts for clearing in a different currency Here the amounts are translated for open item processing and the translation result may have changed due to changes in the exchange rate.
If a clearing amount was recorded in a held status, and this clearing amount is higher than the total amount of the open items when the status is retrieved, the maximum possible clearing amount is set. If a cash discount amount was specified, this is reduced accordingly so that the cash discount percentage rate is retained. Whenever the held status cannot be used again completely, the user sees a message with details of the variance in the long text. Postings and Documents: Transfer Postings in Account Maintenance In the account maintenance, you can transfer difference amounts to a G/L account defined in Customizing. You have to specify the amount to be posted and similar to the payment lot a short account assignment that the system can use to determine the company code, account, business area, and CO account assignments. The fields for the transfer posting are only active if the user has been assigned to a tolerance group for which a maximum amount and maximum percentage rate for the transfer posting have been specified in Customizing. You cannot transfer to tax-relevant accounts. Postings and Documents: Arrears Surcharges
______________________________________________________________
SAP AG 77
SAP Utilities ______________________________________________________________
If open items are cleared by payments or clearing of payments, you can define arrears surcharges. These surcharges have the opposite effect to cash discount. For example, if you set a surcharge of 2.00 for an invoice for 100.00, a payment of 100.00 leads to postings for partial clearing in the amount of 98.04 and revenue from payment surcharges of 1.96. Since the calculation of surcharges is dependent on the value date of the payment, clearing transactions with surcharges can only consider additional credit items (for example, from payments on account) if they have the same due date. All other credit items are locked for the current clearing transaction. If clearing processing takes place online, you can deactivate or reduce the surcharges calculated manually. The following transactions enable the calculation and posting or surcharges: o o o o o Payment Lot Cash Desk and Cash Journal General posting online Account Maintenance Automatic Clearing
In order to enable the calculation of surcharges you have to define an installation-specific function module for event 0104. Postings and Documents: Mass Postings and Cash Management For mass postings that run in parallel processes, waiting time may occur due to competing accesses during the update of data for Cash Management. Contract Accounts Receivable and Payable therefore offers a parallel update mode that you can activate for specific categories of mass runs. Cash Management is then updated at the end of each process. If the process is terminated before the Cash Management update, the update takes place when you close the relevant reconciliation key. If the update also fails here, you can transfer the data recorded separately individually. To do this, in the menu for Contract Accounts Receivable and Payable choose Periodic Processing -> Execution -> Cash Management Transfer. Document Transfer During the document transfer, you can also transfer the identification of the partner message from SAP Credit Management (field PRTID) with the header structure. You can also transfer the identification of the subapplication in Contract Accounts Receivable and Payable (field SUBAP) with the item structure (BFKKOP). During the document transfer, you can transfer the company code for the automatic payment transactions (field PYBUK) with the item structure (BFKKOP). You can also transfer the following new structures: o o BFKKOPREL: Relation between objects BFKKOPC: Card supplement for open items
______________________________________________________________
SAP AG 78
SAP Utilities ______________________________________________________________
Effects on Customizing Classification Keys To activate the classification key, in the Implementation Guide for Contract Accounts Receivable and Payable choose Program Enhancements -> Prepared Enhancements -> Classification Key. Postings and Documents: Negative Postings You make the setting for the company code (negative postings possible) in the Implementation Guide for Financial Accounting under Financial Accounting Global Settings -> Company Code -> Check and Supplement Global Parameters. You make the setting for the document type in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Postings and Documents -> Document -> Maintain Document Account Assignments -> Document Types -> Maintain Document Types and Assign Number Ranges. The main and subtransactions that you want to define for a negative clearing (example: Payments on Account) are in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Postings and Documents -> Document -> Maintain Document Account Assignments -> Maintain Subtransactions. Transfer Postings in Account Maintenance You define the short account assignments in the Implementation Guide for Contract Accounts Receivable and Payable under Basic Functions -> Open Item Management -> Short Account Assignments for Transfer Postings in Account Maintenance. You maintain the tolerance groups under Basic Functions -> Postings and Documents -> Document -> Tolerance Groups for Amount Limits and then the entries Define Tolerance Groups and Assignment of Tolerance Groups to Users. Arrears Surcharges To create the installation-specific function module for event 0104 and to register, in the Implementation Guide for Contract Accounts Receivable and Payable choose Program Enhancements -> Define Customer-Specific Function Modules. To define the accounts to be posted to in the case of arrears surcharges, choose Basic Functions -> Postings and Documents -> Document -> Define Account Assignments for Automatic Postings -> Automatic G/L Account Determination -> Define Accounts for Arrears Surcharges. Mass Postings and Cash Management You activate the parallel update of Cash Management for selected processes via: Technical Settings -> Activate Parallel Update of Cash Management.
1.10.37 Prenotifications
Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the following prenotification functions have been added: o The Create Prenotification File program has been enhanced to cover requirements for Denmark.
______________________________________________________________
SAP AG 79
SAP Utilities ______________________________________________________________
SAP delivers a new payment medium format, PBS_PRENOTE, required for sending prenotification files to the Danish clearing house PBS. o The Process Return File program has been enhanced to handle incoming files in formats DK603 for Denmark, AUTH for Finland, and ACH for the United States. It additionally creates a PBS605 file to send back to the Danish clearing house, PBS, if required; and it processes bank statement data contained in the return file sent by the US clearing house, ACH.
Effects on Customizing A Business Add-In is available for Denmark that enables you to delete business partner CPR and CVR numbers after you have processed the return file from PBS. You can create an implementation in Customizing for Financial Accounting, under Contract Accounts Receivable and Payable -> Business Transations -> Payments -> Incoming/Outgoing Payment Processing -> Add-In: Deletion of CPR/CVR Numbers (Denmark).
1.10.38 New Reports

Use Report RFKK_MA_SCHEDULER The program RFKK_MA_SCHEDULER creates and starts new mass activity runs. Once the run has started, the program monitors all parallel jobs started. This program is particularly helpful if you want to schedule and monitor mass activities using the Schedule Manager or your own report.
1.10.39 Requests
Use Printing Requests You can print requests and standing requests as of Release 4.72. All header data on the request and all request items with additional information on the business partners and contract accounts are available for the printout of a request. All execution dates and special dates are also available for the printout of standing requests. Generation and printout occur with events 0766: Print Request and 0767: Generate Request Printout with correspondence 0039 Request; correspondence type 0039 uses form class FI_CA_REQUEST. SAP provides sample form FI_CA_REQUEST_SAMPLE_SF. Entering Notes You can enter notes for requests and standing requests. If you generate documents from requests, the notes are copied over into the notes on the documents. Business Blocks You can set the clearing block for request items payment/dunning/ interest and clearing blocks that are copied into the documents when the documents are generated. You can enter a block reason and validity period for each request item and block.
______________________________________________________________
SAP AG 80
SAP Utilities ______________________________________________________________
Entering Documents for each Request Item If you create requests with lots of lines and in some circumstances several business partners and contract accounts, this can cause quite a number of documents that can no longer be represented clearly. For this reason, you can only generate documents from requests and standing requests for each request item. You define the corresponding specifications for requests for each request category in Customizing. Multi-Level Control You can also enter requests and standing requests with a tax code that contains several tax rates. The calculated tax amount that is displayed in the request item is determined from the total of amount of the individual tax rates. Classification Key in Request Items You can enter the new field Classification Key in the request items if you have activated the standard enhancement for the classification key. As the classification key is a header field of the document you can only enter different classification keys in a request if you generate documents for each request item. Displaying Requests in Account Balance By defining corresponding function modules for events 1203, 1209 and 1211 you can display requests and standing requests in account balance. SAP provides function modules FKK_EVENT_1203_REQUEST, FKK_EVENT_1209_REQUEST and FKK_EVENT_12011_REQUEST for this that you can define for the events mentioned or use as templates for your own function modules . BAPIs for Processing Requests In the future you will be able to use BAPIs to process requests and standing requests (see release information BAPIs). Approving Requests Until now you could only approve requests through workflow. As of Release 4.72 you can approve requests using a worklist. You define which classes and categories of requests should be approved through a worklist in Customizing. Event 5510 was enhanced for a customer-specific differentiation between approval by worklist or by workflow. You can also suppress the entry of an approval reason for event 5510 when starting the workflow. Effects on Customizing To generate documents for each request item, set the indicator Document for each item in the IMG of Contract Accounts Receivables and Payable, under Basic Functions -> Requests -> Document Creation -> Define Specifications for Document Creation. You define which requests should be approved per request class, request category, or document type through a worklist in the IMG of Contract Accounts Receivable and Payable, under Basic Functions -> Requests -> Define Settings for Approving Requests .
______________________________________________________________
SAP AG 81
SAP Utilities ______________________________________________________________
1.10.40 Processing Returns

Use Read Returns Data from Archive Via transaction FPO9, (SAP menu: Payments -> Returns -> Returns Lot), you can display returns that have already been archived. Note that when you are archiving, archived returns are no longer available for the determination of the number of returns an important value for determining the returns activities. Zero Total Tax Items If charges are posted for a return, and the charges have a tax code with a tax rate of 0.0%, the system creates zero total tax items and displays these in the returns document. Automatic Creation of Returns Lots At the time of creation, you can create the manual posting items Type of Posting = 3 directly. Check for Changed Bank Details You can check for a return whether the bank details of the partner have changed since the last payment run. If this is the case, you can either use an alternative returns reason, or you can define your own activities to be carried out by the return via event 0293. Version Numbering and New Fields in the Returns History The new activity fields and the version numbering have been included in the returns history; you can display both using the display variant. Selection via Payment Form Number When you are assigning payments, you can also use the payment form number as selection criterion. New Returns Category "External Payment Collector" If a confirmation of a payment receipt forwarded by a payment collector is incorrect, a return occurs. You have to process such returns in a separate account not the bank clearing account for bank returns. You can determine the G/L account required in the automatic account determination using the new returns category 05 (External Payment Collector). Reversal of Returns with a Clarification Document From Release 4.72, you can also reverse returns with a clarification document. During the reversal of the document (SAP menu: Document -> Reverse), a returns lot that has already been closed is reopened and, if necessary, a new reconciliation key created, and you can then process the clarification case again in the returns lot. The creditworthiness of the business partner concerned is reset accordingly. Save Display Variant for Returns Display In the header of the returns lot you can save a user-dependent line layout variant for data entry. Effects on Customizing You make the settings for the new returns category External Payment Collector in the Implementation Guide for Contract Accounts Receivable and Payable under Business Transactions -> Returns -> Define Charges Accounts for Returns.
______________________________________________________________
SAP AG 82
SAP Utilities ______________________________________________________________
1.10.41 Connecting the Schedule Manager in Contract Accounts Receivable and Payable
Use From Release 4.72, you can schedule mass activities in Contract Accounts Receivable and Payable with the program RFKK_MA_SCHEDULER - Schedule Mass Activities using the Schedule Manager (see SAP menu: Periodic Processing -> Mass Processing Administration). In addition, the following periodic programs have been changed over so that you can also schedule these with the Schedule Manager: Technical Names RFKKFIKEYCLOSE Name Automatic Closure of Reconciliation Keys Check Totals Tables Transfer of FI-CA Totals Records to General Ledger Transfer of Account Assignment Data to Profitability Analysis Bill Payment Cards Document Transfer Payment Lot Transfer Returns Lot Transfer Data Transfer for Manually Issued Checks Transfer of Cashed Checks Transfer of Data from Account Statement to Payment/Returns Lot Transfer of Payment Advice Notes from Sequential File
RFKKABS1 RFKKGL00
RFKKCOPA00
RFKKPCDS RFKKBIB0 RFKKZE00 RFKKRL00 RFKKCM00
RFKKCR00 RFKKKA00
RFKKAV00
______________________________________________________________
SAP AG 83
SAP Utilities ______________________________________________________________
RFKKCOPM RFKKRD00
Read Collection Agency File Post Revenue Distribution
1.10.42 Stop Future Payment (Denmark)

Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), you can generate a file to send to PBS to cancel a future (within two business days) direct debit payment for a business partner. To do so, from the SAP Easy Access menu, choose Accounting > Financial Accounting > Contract Accounts Receivable and Payable > Payments > Payment Run -> Stop Future Payment (DK).
1.10.43 Tax Reporting in Contract Accounting (New)

Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), you can prepare value-added tax (VAT) reporting with the new program, Tax Reporting in Contract Accounting (RFKKTX00). Effects on Customizing A new Business Add-In, FKK_TAX_REP_00, is available that enables you to modify the list layout to cover country-specific requirements. An implementation is delivered for Mexico, IMP_MX_TAX_REP_00. Note, also, that a new function module is delivered for Mexico, FKK_MX_EVENT_0934, which you must assign to event 934 in Customizing for Financial Accounting, under Contract Accounts Receivable and Payable -> Program Enhancements -> Define Customer-Specific Function Modules (assign under Installation-Specific Function Modules ). Refer to the function module documentation for more information.
1.10.44 Write-Offs
Use In the transaction Write-Off (FPO4), you can enter notes for a write-off document created. To do this, in the menu choose Extras -> Notes -> Enter Notes.
______________________________________________________________
SAP AG 84
SAP Utilities ______________________________________________________________
1.10.45 Generic Withholding Tax Reporting (Enhanced)

Use As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), Generic Withholding Tax Reporting has been enhanced to enable you to select withholding tax data from FI-CA. Under the group box Further Selections, you can select which application the system is to retrieve data from when you run the program, and specify other parameters relevant to FI-CA. Effects on Customizing A new Business Add-In, FKK_WTAX_REP00, is available that enables you to enhance the report to cover country-specific requirements in the output. You can add parameters to the selection screen and modify business partner and withholding tax data. An implementation is delivered for the United States, IMPUS_IDWT_1099MISC.
1.11 IS-U-CS
Customer Service
1.11.1 Waste Disposal-Specific CIC Configuration

Use You can use the new CIC profile ISUWASTE to display a waste disposal-specific data environment in the navigation area of the CIC. Detail data is also provided in the waste disposal-specific HTML customer overview. You can restrict the number of container locations or properties to be displayed for the selected data, and can define an address filter for these objects. The document overview of the waste disposal-specific CIC configuration has been enhanced. Waste disposal order items are now also listed. Effects on Customizing SAP provides the complete Customizing for the CIC navigation area and the HTML customer overview. You must simply assign the new CIC profile ISUWASTE to your agents in HR Org.Management. To use the waste disposal-specific HTML customer overview, you must still enter the URL of your Internet Transaction Server (ITS) in the HTML configuration ISUWASTEINFO.
1.11.2 IS-U-CS-FO
Front Office
1.11.2.1 Enhanced data environment in the CIC customer environment

Use As of SAP Utilities Release 4.72, various new objects and functions are now available in the CIC data environment. These objects and attributes are also available in the HTML customer overview and the fact sheet in CRM. The following new objects are available in the business and technical view in the data environment:
______________________________________________________________
SAP AG 85
SAP Utilities ______________________________________________________________
o o o o
Switch document Point of delivery Infomodule, partner balances Budget billing plan
The following new objects are available in the document view: o Switch document
In addition, an option for displaying reversed documents is now also available for the print document node. Effects on Customizing You can use the transactions Define Data Environment for Navigation Area (ENVD) or Define HTML Customer Overview Data Selection (EHVD) to select the new data. Activate the new objects for the CIC data environment and make the settings for the display. You can also find the corresponding activities in Customizing, under SAP Utilities -> Customer Service -> Customer Interaction Center. For information on the necessary Customizing settings, see the cookbook Efficient Processes in IS-U/CCS - New Developments for Release IS-U/CCS 4.64 or IS-U/CCS 4.71. The relevant section is "Customizing Settings" in unit 9 Customer Interaction Center. See also For detailled information on enhancements for the CIC data environment, see the cookbook Efficient Processes in IS-U/CCS - New Developments for Release IS-U/CCS 4.64 or IS-U/CCS 4.71, unit 9 Customer Interaction Center. The cookbook is available on the SAP Service Marketplace, under http://service.sap.com/utilities -> Product Information -> IS-U/CCS -> General -> Cookbooks & Guidelines.
1.11.2.2 Permanent Hit List

Use As of SAP SAP Utilities Release 4.72, you can now display the hit list for the business partner search in the Customer Interaction Center (CIC) on its own tab page in the navigation area or application area, instead of in a dialog box. This has the following advantages: o o The hit list is integrated in the CIC interaction concept. The hit list display no longer blocks other functions. This is particularly relevant for CTI (Computer Telephony Integration) functions. The hit list is still supported, and the business partner selection / confirmation is considerably easier to execute than it was previously. If details in the list make it difficult to select the business partner, you no longer need to reenter the search criteria and execute the search again in order to find the correct business partner. The ANI (Automatic Number Identification) search is also integrated. This was not accessible previously. Up until now, if the ANI search result was not unique (more than one business partner
______________________________________________________________
SAP AG 86
SAP Utilities ______________________________________________________________
for one telephone number), the telephone number used by the ANI search was entered automatically in the telephone number field in the business partner search criteria. This meant that the call center employee's work was not interrupted by having to make a forced selection in another dialog box. Since the selection from the hit list no longer has to take place immediately, the ANI hit list can also be displayed. This prevents the user from having to execute another search. Effects on Customizing Activate the integrated hit list function by configuring the ISU_HITLIST component (workspace) on a tab page (display area) in the application area or navigation area. You can do this in the SAP Utilities Customizing, under Customer Service -> Customer Interaction Center -> Maintain Standard Settings for Navigation and Application Areas. As for the present hit list, you can use the object presentation to set the display (column contents). To do this, select Define Object Presentation in Customizing for SAP Utilities, under Customer Service. For further information on Customizing settings for the hit list, see the cookbook Efficient Processes in IS-U/CCS - New Developments for Release IS-U/CCS 4.64 or IS-U/CCS 4.71. See the "Customizing Settings" section in unit 9, Customer Interaction Center. The cookbook is available under http://service.sap.com/utilities - > Product Information -> IS-U/CCS -> General -> Cookbooks & Guidelines.
1.11.2.3 Layout Switching for the Customer Interaction Center

Use The layout switching function allows you, in the Customer Interaction Center, to simply and efficiently use the space available in the SAPGUI window when processing processes. You can use Expand/Collapse Application Area or function key F5 to temporarily activate the application area and all the tab pages in full-screen mode. This means that no CIC components outside the application area are displayed. (By defining your own program function status (PF status) you can also use other pushbuttons and function keys. SAP provides the aforementioned setting as an example, however.) This also gives you considerably more space for the individual components and processes loaded in the application area. This is particularly beneficial for the more complex HTML calls (such as the customer overview) and the component workspaces (such as the billing correction or budget billing amount adjustment. This significantly improves usability, particularly when using the "small" layout. You can also expand the navigation area (Expand/Collapse Navigation Area or function key F7) in order, for example, to view data fields or the fixed hit list on the full screen. The application area is then temporarily not displayed. In this case, the components located above the navigation and application area are still displayed. This means, for example, that you can still interact when identifying the business partner. All CIC functions (such as Computer Telephony Integration (CTI) commands or the End contact function) are also available in the alternative layouts. You can also switch directly between the different tab pages of the application area or navigation area. By repeating the function you used to get to the alternative layout you return to the original layout. When you end the contact, the system automatically switches back to the original layout. By triggering the corresponding function you can also switch directly between the alternative layouts.
______________________________________________________________
SAP AG 87
SAP Utilities ______________________________________________________________
Effects on Customizing To use the Layout Switching function you must allocate the hidden component ISULAYOUTSWITCH to the CIC framework. You must also use the CIC_TOOLBAR2 component to configure a GUI status that has the suitable function code LAYOUT_TGL. For example, this is the case for component profile ISU_EFF, which uses the GUI status ISUTEL from the function group EECICTOOLBAR_ISU. You can find the CIC framework in Customizing for SAP Utilities, under Customer Service -> Customer Interaction Center -> Maintain Front Office Framework ID and Parameters. Unlike the CIC_TOOLBAR2 component, the LAYOUTSWITCH component does not require a component profile. The CIC_TOOLBAR2 component uses the component profile TBAR2_PROF to allocate a GUI status to the CIC. This component replaces the CIC_TOOLBAR component and enhances its functions. This makes it possible, for example, to allocate a customer-specific GUI status to the CIC, without making any modifications. You maintain the aforementioned component profile in Customizing for SAP Utilities, under Customer Service -> Customer Interaction Center -> Define Standard Toolbars and User-Defined GUI Status.
1.11.2.4 Changes to the Customer Interaction Center, CIC

Use As of SAP Utilities Release 4.72, the following new functions are available for the Customer Interaction Center (CIC): o o o o o o o General search string in IS-U data finder Different layouts in the business partner identification component (ISUSDPART) Fixed hit list for business partner identification Identification of a dependent contract account during a business partner search Layout switching for enlarging the application area and navigation area Retrieval of additional data for the data environment and customer overview Inclusion of methods and workspaces for new functions, such as: Bill display (in PDF format) from archive or simulation Bill correction Bank data changes Budget billing adjustment Accelerated move-in/out entry Meter reading results for each premise
Effects on Customizing For information on the necessary Customizing settings, see the cookbook Efficient Processes in IS-U/CCS - New Developments for Release IS-U/CCS 4.64 or IS-U/CCS 4.71. See the "Customizing Settings" section in unit 9, Customer Interaction Center.
______________________________________________________________
SAP AG 88
SAP Utilities ______________________________________________________________
See also You can find detailled information on changes and new developments for the CIC in the cookbook Efficient Processes in IS-U/CCS - New Developments for Release IS-U/CCS 4.64 or IS-U/CCS 4.71, unit 9 Customer Interaction Center. The cookbook is available on the SAP Service Marketplace, under http://service.sap.com/utilities -> Product Information -> IS-U/CCS -> General -> Cookbooks & Guidelines.
1.11.3 IS-U-CS-BT 1.11.3.1 IS-U-CS-BT-DR
Process Execution Installation Disconnection/Reconnection
1.11.3.1.1 Accelerated Move-In / Move-Out / Move-In/Out Entry

Use As of SAP Utilities Release 4.72, the following new functions have been added to the accelerated move-in / move-out / move-in/out entry(transaction EC70): o o o Integration of the note object: You can now create notes for a parked document. E-Mail addresses: You can now enter an E-mail address for move-in and move-out customers. Payment cards: You can now create payment card data for move-in and move-out customers. In contract account you can also enter links to payment cards for incoming payments and outgoing payments. Business partner addresses: In addition to the European address display, the American display is also now available.
Effects on Customizing To use the new functions, you must first indicate the corresponding fields of the accelerated entry interface as visible or hidden. You do this in Customizing, under SAP Utilities -> Customer Service -> Process Execution -> Move-In/Out -> Fast Data Entry -> Define Parking Variants. See also You can find detailled information on the new developments for the accelerated move-in / move-out / move-in/out entry in the cookbook Efficient Processes in IS-U/CCS - New Developments for Release IS-U/CCS 4.64 or IS-U/CCS 4.71. This cookbook is located on the SAP Service Marketplace, under the Internet address http://service.sap.com/utilities -> Product Information -> IS-U/CCS -> General -> Cookbooks& Guidelines. See also OSS note 677175.
______________________________________________________________
SAP AG 89
SAP Utilities ______________________________________________________________
1.11.3.1.2 BAdI ISU_SERVORD_EDCN

Use The new BAdI ISU_SERVORD_EDCN is available within the disconnection (transactions EC85 and EC86). The BAdI allows you to create a disconnection order or reconnection order. You can use the BAdI to enter or change the following values: o o o The order code for the disconnection/reconnection order The maintenance planning plant for the disconnection/reconnection order The selection of devices to be disconnected
In this way the device selection can be either division-dependent or based on device characteristics. You can select the order code and the maintenance planning plant for the device to be disconnected. The BAdI is provided with an example code, which selects the device based on its division. First, all devices from the electricity division are disconnected, then all devices from the gas division, and so on. The code is correspondingly valid for creating reconnection orders. It is possible to manually change the input value in the dialog transaction at any time.
1.12 IS-U-WM
1.12.1 IS-U-WM-MB
Work Management
Work Management Mobile Business
1.12.1.1 Mobile Asset Management for Utilities

Use As of SAP Utilities Release 4.72, the new mobile application Mobile Asset Management for Utilities (MAU) is available. A service technician can use this application to perform mobile processing for the most important processes in the utilities industry. In this way, the following processes are supported both for orders and for notifications: o o o o Device replacement Disconnection / collection / reconnection Aperiodic meter reading Customer-specific processes with reference objects for the utilities industry (such as repairs)
Effects on Customizing Execute the necessary Customizing for the Mobile Asset Management application.
______________________________________________________________
SAP AG 90
SAP Utilities ______________________________________________________________
Execute the following IMG activities for the Mobile Asset Management for Utilities application: o o o See also Further information can be found on the SAP Service Marketplace, under http://service.sap.com/utilities -> Product Information -> Asset & Work Management -> Mobile Asset Management for Utilities. Define material numbers for mobile processing Define device numbers as unique for mobile processing Define sections for overview pages
1.13 IS-U-WA
1.13.1 IS-U-WA-MD
Waste Management
Master Data
1.13.1.1 Archiving for Route and Waste Disposal Order Objects

Use As of SAP Utilities Release 4.72, you can archive the route and waste disposal order objects. The following prerequisites and restrictions apply here: o Route Archiving You can now archive routes that are no longer used. To do this, the archiving object ISU_ROUTE has been created. You can use the archiving workbench (transaction SARA) to process this archiving object. To archive a route, it must have the status Deletion Flag Set. You set this directly in the route. To be able to set this status, the routes must no longer have an active service, and must not be allocated to any waste disposal order that still has an open status. The archiving program consists of the following parts: The routes to be archived are analyzed in advance to see if they can be archived. If they can be archived then a deletion flag is set. You can use the BAdI EEWA_ROUTE_ARCHIVE to influence this analysis. For further information, see the documentation for the BAdI. In the write program the routes to be archived are entered in the archive files. The archive files are then written in the archiving system. In the deletion program, the archived routes are deleted from the database. Note that the archived data can no longer be reloaded in the system.
In the initial screen for route maintenance, you can use Call Archive to display archived routes. o Waste Disposal Order Archiving You can now archive waste disposal orders that, for example, have already been processed and are no longer kept in the system. The archiving object ISU_EORDER was created for this purpose. You can use the archiving workbench (transaction SARA) to process this archiving object. To archive a waste disposal order, the waste disposal order must have the status Deletion Flag Set.
______________________________________________________________
SAP AG 91
SAP Utilities ______________________________________________________________
To do this, call transaction Delete Order and set the indicator Set Deletion Flag. The archiving program consists of the following parts: The waste disposal orders to be archived are analyzed in advance to see whether they can be archived. If they can be archived, then a deletion flag is set. You can use BAdI EEWA_WDO_ARCHIVE to influence this analysis. For further information, see the documentation for the BAdI. In the write program, the waste disposal orders to be archived are entered in the archive files, which are then written in the archiving system. In the deletion program, the archived orders are deleted from the database. Note that you can no longer reload archived data in the system.
Effects on Customizing To use the new functions, you must execute the following activities in the implementation guide (IMG): o o See also See the online help for further information on the archiving workbench. Activate Info Structure for Archiving Define Retention Periods for Archiving Objects
1.13.1.2 New Functions in Property Maintenance

Use As of SAP Utilities Release 4.72, you can maintain an individual address for a property. This address maintenance is achieved by linking the property to the functional location. When you create a property, the functional location is automatically created in the background. For further information on the necessary settings, see Effects on Customizing. The link to the functional location allows you to use the new integration of the waste disposal industry in SD billing. It is also possible, as well as allocating a property to an object allocation, to maintain an allocation to an SD contract. Along with the functional enhancement to the property, the processing has also been improved in the following ways: o o o o It is now possible, using the search help for maintenance by cleaning object address, to select more than one property, and to transfer these properties to the maintenance. The header and item data for the property are now maintained on their own tab page, and no longer on one screen. You can place time restrictions on the allocation of a cleaning object to a property. This means that you can select the to-date for the allocation yourself. You can use the BAdI ISU_WA_ROB_ADR_CHECK to carry out individual checks to see whether the allocation of a cleaning object to a property is permissible. This is particularly valid for the address. For more information, see the documentation for the BAdI.
______________________________________________________________
SAP AG 92
SAP Utilities ______________________________________________________________
Effects on Existing Data The connection of the functional location to the property makes it necessary to create functional locations for existing properties. This is done using the report ISU_CREATE_FUNCLOC_FOR_AREA. Effects on Customizing To use the new functions for maintaining the property, you must execute the following Customizing activities: o o Define Number Ranges for Functional Locationsfor a Property Field Selection Control for Property Address Data
1.13.1.3 Changed Billing for Charge Assessment

Use As of SAP Utilities Release 4.72, you can now use a new billing procedure for assesssing charges. This new billing procedure will use the partial billing procedure for budget billing plan creation to replace the old procedure for charge assessment. The new procedure is based on SAP Utilities (IS-U) billing, and is fully integrated in this process. Existing billing variants are still valid. To implement the procedure, execute the following actions: o To transfer your own prorations (such as quarters from charge period) tothe billing, you must execute the customer enhancement EBIA002. For further information, see the documentation for the customer enhancement. To determine due dates for the charge assessment, you must execute the Customizing activity Define Scheduling for Charge Assessment. For further information on how the definitions affect the billing, see the documentation for the Customizing activity. To calculate the due dates for open items in the invoice, and allocate document lines to charge periods, you must define the FI event R406. For further information on this event, see the documentation for the function module ISU_SAMPLE_R406. SAP provides function module BG_SAMPLE_R406 for this event. This function module is a standard definition, which you can use as a template.
Effects on Existing Data You can continue to use the old billing procedure. This procedure will not, however, be further developed.
1.13.1.4 Waste Disposal-Specific CIC Configuration

Use You can use the new CIC profile ISUWASTE to display a waste disposal-specific data environment in the navigation area of the CIC. Detail data is also provided in the waste disposal-specific HTML
______________________________________________________________
SAP AG 93
SAP Utilities ______________________________________________________________
customer overview. You can restrict the number of container locations or properties to be displayed for the selected data, and can define an address filter for these objects. The document overview of the waste disposal-specific CIC configuration has been enhanced. Waste disposal order items are now also listed. Effects on Customizing SAP provides the complete Customizing for the CIC navigation area and the HTML customer overview. You must simply assign the new CIC profile ISUWASTE to your agents in HR Org.Management. To use the waste disposal-specific HTML customer overview, you must still enter the URL of your Internet Transaction Server (ITS) in the HTML configuration ISUWASTEINFO.
1.13.1.5 Enhancements for the waste disposal order

Use New functions are now available within waste disposal order processing, which further standardize the creation, output, deletion, planning and confirmation of waste disposal orders, and integrate these processes more strongly in SAP components. The following enhancements exist: o Standard Selection The selection screens for waste disposal order creation, output, deletion, planning and confirmation have been standardized and additional fields (such as SD Contract and Location) have been included. BAdIs are used to implement the selection. The BAdIs also provide the function for defining your own selection screens. o You can use the BAdI ISU_WA_ORDER_CREATE to realize your own implementation for creating a waste disposal order. For outputting, deleting, planning and confirming waste disposal orders you can use the BAdI ISU_WA_ORDER_SELECT to realize your own implementation.
General Status Management The status of a waste disposal order is currently updated in a structure field of the order item. Using the general status management provides a business link between transaction and status. If you execute a business transaction when processing waste disposal processes, the system status of the waste disposal order changes and in turn influences the execution of other business transactions. The statuses are provided by SAP and cannot be changed or enhanced. The field previously used for the status is, therefore, obsolete. Waste Disposal Order Archiving You can find further information on archiving a waste disposal order in the release information Connecting the Route and Waste Disposal Order Objects to the Archiving Workbench. SD Integration You can find further information on SD integration in the release information Integration of SAP Waste and Recycling, and Sales and Distribution (SD). Enhancing the Confirmation for Waste Disposal Orders You can now define confirmation fields for the service area for confirming resource assignment for
______________________________________________________________
SAP AG 94
SAP Utilities ______________________________________________________________
a waste disposal order. In addition, you can also now define your own confirmation fields. You can find more information under Define Confirmation Categories. o Integration in Controlling You can now internally post confirmed vehicle and personnel services for a waste disposal order. You define the service type for the CO posting in the IMG activity Define Confirmation Categories, under "Fields for Vehicle/Personnel". You can use the indicator Cost Collector to define whether the internal CO service posting for the corresponding route takes place at route level or at item level. A prerequisite for this is that corresponding cost objects exist at route or item level. The cost distribution is implemented in the BAdI ISU_WA_ORDER_CONFIRM. You can realize your own implementation there. Order Changes During Planning In order planning it is now also possible to change corresponding order data during planning. This allows you to make changes to orders without changing the master data (such as the route or service frequency).
Effects on Existing Data To integrate existing waste disposal orders in the general status management, a status must be assigned for each order. The assignment of new statuses is carried out with the XPRA ISU_XPRA_ORDER_STATUS_CREATE, and is dependent upon the previous statement. For further information, see the documentation for the XPRA and the documentation for the ISU_XPRA_ORDER_STATUS_CREATE report. Effects on Customizing To use the function for enhancing the confirmation of waste disposal orders, and the integration in Controlling, you must execute the following Customizing activity: o Define Confirmation Categories
1.13.1.6 Improvements in Cleaning Object Maintenance

Use As of SAP Utilities Release 4.72, you can maintain the cleaning object more efficiently. For this purpose, the following changes have been made in the maintenance dialog: o o o o The cleaning object maintenance now takes place as a single-screen transaction. This means that the initial screen and processing screen are no longer separate. You can use the search help for the address of a cleaning object to select several objects and transfer them to the display. The Regional structure group and Element of political regional structure fields in the address area are now available for input. The from-date and to-date of the time slice for the cleaning object are transferred as filter criteria for displaying services, when navigating to the service frequency.
______________________________________________________________
SAP AG 95
SAP Utilities ______________________________________________________________
1.13.1.7 Enhancement for Route

Use As of SAP Utilities Release 4.72, new functions are now available within the route master data object. These functions improve the inclusion of the route and subsequent processes in SAP standard components. The following enhancements exist: o General Status Management Up until now you have been able to create, change or display a route in the system. You can now also use the general status management to delete routes. You need to delete routes if they become obsolete, due to grouping or similar processes, and are no longer to appear in the system. In particular, it must be possible to restrict or completely prevent the option of allocating further waste disposal orders or services to these routes. The general status management makes various statuses available to restrict the use of the route, or to make the route only permissible for certain processes. The statuses are provided by SAP, and cannot be changed or enhanced. From now on, the status of the route is displayed in the maintenance screen for the route. There, you can also change the status of the route (for example, you can set the status to inactive, or can set a deletion flag). Location and Account Assignment From now on, you can assign location and account assignment data to the route. This has the following effects on the subsequent processes: The location and maintenance plant fields describe the organizational assignment of the route. You can use these fields to select waste disposal orders (when creating, planning, confirming, or deleting routes). In the waste disposal industry the 'location' and 'maintenance plant' fields can often be equated with the depot. The delivering plant and storage location fields describe the location at which the route delivers or removes containers that are intended for container transport. The waste disposal installation describes the location at which the collected waste is disposed of. Here, you must differentiate between whether the logistic component or the enhanced logistic component is to be used. If you use the enhanced logistic, the waste disposal installation object is available, and can be entered here. In addition, you should only use the plant and storage location fields for defining the waste disposal installation. This location data is used as the destination for a subsequent material posting using weighing record creation within the confirmation.
All this location data is transferred as default values to the waste disposal order. There, it can be changed during the planning or confirmation. You can use the account assignment data to allocate the route to organizational areas within your company that are relevant to account assignment. These allocations are effective during the CO account assignment for waste disposal orders. Here, you can decide whether the waste disposal order costs are grouped at route level (header record for waste disposal order) or at order item level (item record for waste disposal order). You use the Cost Collector for Waste Disposal Order field in the route to control this. In addition you can, during the account
______________________________________________________________
SAP AG 96
SAP Utilities ______________________________________________________________
assignment at route level, distinguish which account assignment object is to be used. The cost center, standing order and billing order objects are available. o Route Archiving For information on route archiving, see the release information Connecting the Route and Waste Disposal Order Objects to the Archiving Workbench. Waste Disposal Calendar You can now enter a specific appointment postponement in the waste disposal calendar (transaction EWACAL) and, when maintaining non-workdays, directly in the route. This removes the restriction that meant that the postponement of non-workdays was restricted. In the future it will no longer be possible to enter a correction indicator for the postponement of a non-workday. Modifying dependent services when changing the service frequency for a route It is now possible, when changing the service frequency for a route, to modify dependent services (services in which the route is entered as the productive route). You can use the BAdI ISU_WA_ADAPT_SERVICE for this purpose.
Effects on Existing Data To integrate existing routes in the general status management, an initial status must be assigned for each route. The ISU_XPRA_ROUTE_STATUS_CREATE XPRA is used for assigning the initial status. For further information, see the XPRA documentation and the documentation for the report ISU_XPRA_ROUTE_STATUS_CREATE. Use the report REWA_ROUTE_DATES_CORRECT to modify existing waste disposal calendars and non-workday definitions for a route. This report converts the correction indicator for the non-workday to a specific date. For further information, see the documentation for the report. See also You can find further information on general status management in the online help.
1.13.1.8 Integration of SAP Waste and Recycling with Sales and Distribution (SD)
Use As of SAP Utilities Release 4.72, it is now possible to use contracts with SD functions and follow-on functions. In a new waste disposal contract it is now possible to maintain a service frequency for a service product. In this way, you can maintain a technical object list for a piece of equipment, a functional location or a material.You create and configure waste disposal contract, and invoice services and products in SD. You can create a waste disposal order from the maintenance for the service frequency directly into the waste disposal contract. Further logistical processing, such as planning, outputting, confirming and deleting waste disposal orders, takes place in SAP Waste and Recycling: o o The waste disposal order generated from SD is included in the document flow of the waste disposal contract. Saving the waste disposal order confirmation automatically triggers the generation of a debit memo request with reference to the waste disposal contract.
______________________________________________________________
SAP AG 97
SAP Utilities ______________________________________________________________
o o
Confirming the waste disposal order updates the technical object list for a container transport. The invoicing of services performed takes place in SD, and is carried out according to the values transferred to the debit memo request from the confirmation. This means you can transfer the values to either FI-CA or FI-AR.
Effects on Customizing To use the new SD integration functions, you must execute the following Customizing activities: o o See also For further information, see the Cookbook on SD integration, under http://service.sap.com/utilities -> Product Information -> SAP Waste and Recycling. This cookbook describes the necessary Customizing settings in detail. Define Settings for SD Integration This document describes the settings in Customizing in both SD and in SAP Waste and Recycling. Allocate Service products to Service Types
1.13.1.9 Enhancements to Service Frequency

Use As of SAP Utilities Release 4.72, the following new functions are available for maintaining the service frequency: o New Authorization Field There is a new authorization field in the authorization object for service frequencies. The authorization field ISU_EWAOBJ has been added to the authorization object service frequency E_SERVFREQ. You can use this authorization field to control for which object (container location, cleaning object, route, SD contract) the service frequency can be maintained. Create Waste Disposal Order You can now create a waste disposal order directly from the service frequency. To do this, you must indicate the service, for which the order is to be generated, and select Create order. Incompleteness Check for Service Frequency You can now define your own checks to see how complete service frequency data is. This is useful, for example, for checking customer-specific fields before saving data. The BAdI ISU_WA_SF_CMPL_CHECK is available for implementing these checks. The BAdI is delivered with standard method definitions. For more information, see the BAdI documentation. In Customizing, you can define when the checks are to be carried out. Allocation Table: Waste Fraction <-> Container Category You can now define waste fractions in the system, and allocate waste to these fractions. The waste fraction is defined as a material group. The waste is defined as material for the Material Management (MM) component. The allocation is executed by maintaining a material group for a material. You can allocate the waste fraction to, among others, a route or a guarantor contract. Furthermore, you can allocate permitted container categories to a waste fraction. These allocations are checked when you maintain services and plan waste disposal orders.
______________________________________________________________
SAP AG 98
SAP Utilities ______________________________________________________________
Period Control for Service Selections You can now preassign the from-date and to-date for various standard selections of services and waste disposal orders. These include: The service overview from the service frequency and the CIC The order overview from the service frequency and the CIC
The service display in the service frequency The settings for this are made in the Customizing for the waste disposal industry. The following functions have also been changed: o Conversion to single-screen transaction You can now only use transaction ERONEW to maintain the service frequency. Transactions ER01, ER02 and ER03 are now obsolete. Input sequence changed You can now maintain the fields for the service in any order. This is because no fields are now indicated as mandatory. This means that once you have entered the route for a new service, the fields for the service can be called automatically for the route. A new incompleteness test for the service frequency ensures that data is complete and consistent. Filter option for service display You can now filter the tree display for the services. For container services you can filter by service type and container category. For the remaining objects you can only filter by service type.
Effects on Existing Data If you have already defined waste as materials in the system, and want to use the check functions for waste fraction <-> container category, you must still create waste fractions and allocate these to your waste. Effects on System Administration Adjust the authorization profiles of all employees, who are responsible for service frequencies, to the new authorization field. Effects on Customizing To use the new and changed functions, you must execute the following Customizing activities: o o o Define Waste Fractions Define Period Control for Selections Activate Incompleteness Check for Service Frequency
1.13.1.10 Improvements to Container Location Management

Use As of SAP Utilities Release 4.72, you can maintain the container location more efficiently. The following changes have been made to the maintenance dialog:
______________________________________________________________
SAP AG 99
SAP Utilities ______________________________________________________________
o o o o o
In the tree display for the container location, the selected container is now indicated in color and marked with a green tick. In the tree display, a further level has been inserted below the container. This level displays the object allocations for the container. The marked container is transferred to the service frequency during forward navigation, and is set as the initial object there. During forward navigation, the key date for container location management is also transferred to the service frequency for selecting services for this key date. You can now override the container location address. Previously the container location address was copied from the waste disposal object for the container location. In the container location object you can now jump to the container location maintenance and maintain an alternative address there.This address is copied for the subsequent logistical processes. A functional enhancement now allows you to allocate containers to SD contracts, as well as to allocate containers to object allocations. These containers are thus entered in the technical object list for a selected item from the SD contract. This process takes place in the background. This makes it possible to use SD billing to bill waste disposal services.
1.13.1.11 Waste Disposal Installation Creation

Use As of SAP Utilities Release 4.72, you can group together objects from the Waste Disposal Industry component that are necessary for mapping a waste disposal installation (such as functional location, plant, storage location, warehouse number and business partner). This grouping allows you to enter and allocate documents more easily at the waste disposal installation entrances / exits. Effects on Customizing To create waste disposal installations, you must execute the following Customizing activities: o o Define Waste Disposal Installation Types Define Number Ranges for Waste Disposal Installations
1.13.2 IS-U-WA-PC
Processing
1.13.2.1 General Cargo Entry at Waste Disposal Installation

Use As of SAP Utilities Release 4.72, you can use the general cargo entry to map general cargo deliveries at a waste disposal installation entrance/exit. To do this, you must enter the waste disposal installation affected, the vehicle making the delivery, and the material delivered. These are then booked in/out, and a sales document is created when specified by a customer.
______________________________________________________________
SAP AG 100
SAP Utilities ______________________________________________________________
Effects on Customizing To use the general cargo entry, you must execute the following Customizing activities: o o o Define Number Range for General Cargo Entry Define Order Types for Waste Disposal Installations Define Waste
1.13.2.2 Create and Process Weighing Procedures

Use As of SAP Utilities Release 4.72, you can use the accelerated weighing entry to map weighing procedures at waste disposal installation entrances / exits, control a possible connected traffic light or barrier, and determine the weight of a vehicle when empty: o Weighing Procedures You can use the accelerated weighing entry to weigh and reweigh vehicles when they use the waste disposal installation. You can enter view controls that have been executed, or samples that have been taken, for a weighing procedure. The waste disposal order can then be automatically confirmed. For external deliveries, the material can be booked in and the sales document that was defined in the order type for waste disposal installation can be created. You can use the function Take Sample to document a view control or the taking of a sample at the scales. If a view control is rejected, you can directly create a delivery lock for the waste and the premise. In the weighing procedure transaction, you can enter the loading and unloading times. Determine Weight When Empty You can use the Enter weight when empty function to enter a vehicle weight directly in the vehicle master. Traffic Light Control You can use the functions Switch traffic light to red and Switch traffic light to green to control traffic lights or barriers that are connected to the scales.
Effects on Customizing To use the accelerated weighing entry, you must execute the following Customizing activities: o o o o o o Define Number Ranges for Weighing Procedures Define Order Types for Waste Disposal Installations Define Waste Define Hardware Profiles Define Hardware Profile Controls Define Hardware Profile Groups
______________________________________________________________
SAP AG 101
SAP Utilities ______________________________________________________________
1.13.3 IS-U-WA-IF
Interfaces
1.13.3.1 Hardware Configuration at Waste Disposal Installation Entrance / Exit

Use As of SAP Utilities Release 4.72, you can connect external devices (such as a weighbridge) for mapping the entrances and exits at a waste disposal installation. To do this, you must connect and configure the corresponding devices. o Hardware Profiles The technical parameters for the device connected are defined in the hardware profiles. You can call these hardware profiles either using a serial interface or by TCP/IP. Hardware Profile Control A hardware profile control implements the log, which is necessary for communication with the external device. For this reason a JavaScript is defined, which, using the device object, can be written in or read from the device. Hardware Profile Groups You can group different hardware profiles and hardware profile controls in a hardware profile group. Hardware profile groups link a weighbridge with further devices (such as a card reader or traffic light).
Effects on Customizing To configure the hardware you must execute the following Customizing activities: o o o Define Hardware Profiles Define Hardware Profile Controls Define Hardware Profile Groups
1.14 IS-U-IDE
Intercompany Data Exchange
1.14.1 Authorization Check for Point of Delivery (New)

Use As of SAP Utilities Release 4.72, the point of delivery has a new authorization object (E_POD), which enables authorizations to be assigned to the Create, Change, and Display activities in conjunction with an authorization group. The authorization check is active for the following transactions: o o o Create Point of Delivery (EEDM09) Change Point of Delivery (EEDM10) Display Point of Delivery (EEDM11)
______________________________________________________________
SAP AG 102
SAP Utilities ______________________________________________________________
Note: The authorization object is not used for the point of delivery in the installation (Point of Delivery subscreen in the installation transaction).
1.14.2 Adjustment Reversal in the Deregulated Scenario

Use Previously, you could not execute an adjustment reversal (transaction EA21) if you wanted to send documents to an invoicing service provider. As of SAP Utilities Release 4.72, you can execute an adjustment reversal and then send the documents that are subsequently invoiced to the invoicing service provider.
1.14.3 Data Exchange Processes for Master Data Changes (New)

Use As of SAP Utilities 4.72, you can use data exchange basic process CHCD_OUT to send the following master data changes to the market partner: o o o o o o o o o o Device replacement, Device modification Change installation facts and reference value Change installation Change non-billable service Change contract Change connection object Change contract account Change premise Change business partner Change allocation of load profile (synthetic profile) for installation Contract account changed Connection object address changed Contract changed Installation facts changed Installation changed Allocation of load profile to installation changed Non-billable services changed
This replaces the following IDE events: CH_ACCOUNT CH_COADDR CH_CONTR CH_FACTS CH_INSTLN CH_LPASSGN CH_NBSERV
______________________________________________________________
SAP AG 103
SAP Utilities ______________________________________________________________
CH_PARTNER CH_PREMISE EXCH_DEVIC
Business partner (contract partner) changed Premise changed Device changed
Data can only be sent using data exchange processes if the corresponding IDE event is not active.
The following changes have been made to data exchange basic process CHCD_OUT: o o Name changed to Point of Delviery Master Data Changes Optional Process parameter Event for master data change defines, which master data changes to send: CH_ACCOUNT Contract account changed CH_COADDR Connection object address changed CH_CONTR Contract changed CH_FACTS Installation facts changed CH_INSTLN Installation changed CH_LPASSGN Allocation of load profile to installation changed CH_NBSERV Non-billable services changed CH_PARTNER Business partner (contract partner) changed CH_PREMISE Premise changed EXCH_DEVIC Device changed If you do not specify any process parameters, all master data changes are communicated. In monitoring of data exchange processes, you can choose whether to log all master data changes under one data exchange process or to use the optional process parameter Event for Master Data Change in the definition of the data exchange process so that you can use different data exchange processes depending on the context. You can save and display multiple data objects as references for the data exchange task: Business partner Installation Contract Contract account Premise Device
Connection object The reference that is automatically saved depends on the master data changes that have been made. Format module ISU_COMPR_VDEW_UTILMD_CHCD_OUT serves as a template for user-defined modules used to convert data into IDoc format. Format VDEW_UTILMD can only be used in certain test cases and should therefore be replaced with a user-defined format.
______________________________________________________________
SAP AG 104
SAP Utilities ______________________________________________________________
Effects on Existing Data
If you only want to use data exchange process CHCD_OUT to send contract partner changes (as was previously the case), enter value CH_PARTNER - Business partner changed for the optional process parameter Event for Master Data Change in Customizing for the corresponding data exchange process. Other master data changes are not then communicated. Effects on System Administration An example implementation for sending master data using data exchange basic process CHGN_OUT is provided in BAdI ISU_IDE_DATEXCONNECT by means of the following methods: DATEXCONNECT_BILLINGINST _CHNG Framework: DATEX call in isu_comev_billinginst_changed DATEXCONNECT_INSTFACTS_CHNG Framework: DATEX call in isu_comev_instfacts_changed DATEXCONNECT_INSTLN_CHANGED Framework: DATEX call in isu_comev_instln_changed DATEXCONNECT_NBSERVICE_CHANGED Framework: DATEX call in isu_comev_nbservice_changed DATEXCONNECT_CONTRACT_CHANGED Framework: DATEX call in isu_comev_contract_changed DATEXCONNECT_COADDR_CHANGED Framework: DATEX call in isu_comev_coaddr_changed DATEXCONNECT_ACCOUNT_CHANGED Framework: DATEX call in isu_comev_account_change DATEXCONNECT_PREMISE_CHANGED Framework: DATEX call in isu_comev_premise_changed DATEXCONNECT_PARTNER_CHANGED Framework: DATEX call in isu_comev_partner_changed DATEXCONNECT_LPASS_CHANGED Framework: DATEX call in isu_comev_lpass_changed If you want to use a different project-specific data exchange basic process to transfer master data, you can replace the methods of BAdI ISU_IDE_DATEXCONNECT with your own implementation.
Effects on Customizing If you want to use the data exchange basic process to transfer the point of delivery master data, make the following modifications in Customizing: 1. 2. 3. Deactivate the corresponding IDE event Define at least one data exchange process on the basis of data exchange basic process CHCD_OUT. Define a new format for basic process CHCD_OUT and specify a process module for the conversion of the data into IDoc format. The interface of the user-defined module must be the same as the interface for ISU_COMPR_VDEW_UTILMD_CHCD_OUT.
You need to make the following enhancements to the master data:
______________________________________________________________
SAP AG 105
SAP Utilities ______________________________________________________________
Create a data exchange definition for the relevant data exchange process for each third party service provider (all service providers not managedin your own system) to whom you want to send the master data changes. Use your own format for the conversion of the data into IDoc format.
1.14.4 Definition and Consistency Check for Deregulation Processes (Enhanced)

Use As of SAP Utilities 4.72, you can specify that a parameter configuration can only be used in one service provider agreement. An additional automatic consistency check prevents the same parameter configuration from being used for different market partners, processing service providers, point of delivery groups, or supply scenarios. You can also use selected context fields in the search help to restrict the number of hits for project-specific parameters. Effects on System Administration If you want to restrict the number of hits for project-specific parameters, define the following import parameters in the search help: DEREGSCENARIO ID of supply scenario DEREGPROC Deregulation process DEREGSPINIT Service provider (market partner) DEREGSPPART Processing service provider DEREGPODGROUP ID of point of delivery group DEREGCONTRACTID Contract ID (reference number)
Effects on Customizing If you want to use the new consistency checks for your own deregulation processes, you can activate them in Customizing. To do this, go to SAP Utilities -> Tools -> System Modifications -> User-Defined Enhancements for IDE -> Define Deregulation Processes and select the Only Use Parameter Configuration Once field.
1.14.5 Framework for Outgoing Data Exchange Processes (Enhanced)

Use As of SAP Utilities 4.72, you can use your own unmodified export basic processes instead of the basic processes provided by SAP: CHCD_OUT Send Point of Delivery Master Data Changes INV_OUT Send Invoicing Document (Create/Reverse) EXPUSAGE Send Consumption Data (From Billing)
______________________________________________________________
SAP AG 106
SAP Utilities ______________________________________________________________
EXPREQSWT Supply EXPRESSWT Supply Effects on Existing Data
Send Request for Change of Supplier/Start or End of Send Reply for Change of Supplier/Start or End of
BAdI ISU_IDE_DATEXCONNECT is included in the used event modules or BOR methods. The standard implementation corresponds with the logic used previously. If you do not want to use your own user-defined basic processes instead of those in the above list, you do not have to make any changes. Effects on System Administration BAdI ISU_IDE_DATEXCONNECT provides the following methods: DATEXCONNECT_USAGE_INFO Framework: DATEX call in isu_prepare_usage_info DATEXCONNECT_BILLINGINST_CHNG Framework: DATEX call in isu_comev_billinginst_changed DATEXCONNECT_INSTFACTS_CHNG Framework: DATEX call in isu_comev_instfacts_changed DATEXCONNECT_INSTLN_CHANGED Framework: DATEX call in isu_comev_instln_changed DATEXCONNECT_NBSERVICE_CHANGED Framework: DATEX call in isu_comev_nbservice_changed DATEXCONNECT_CONTRACT_CHANGED Framework: DATEX call in isu_comev_contract_changed DATEXCONNECT_COADDR_CHANGED Framework: DATEX call in isu_comev_coaddr_changed DATEXCONNECT_ACCOUNT_CHANGED Framework: DATEX call in isu_comev_account_changed DATEXCONNECT_PREMISE_CHANGED Framework: DATEX call in isu_comev_premise_changed DATEXCONNECT_PARTNER_CHANGED Framework: DATEX call in isu_comev_partner_changed DATEXCONNECT_LPASS_CHANGED Framework: DATEX call in isu_comev_lpass_changed DATEXCONNECT_SWITCH_OUT Framework: COMEV in CL_ISU_IDE_SWITCH_COM=>SEND_MSGDATA DATEXCONNECT_PROCESS_INVOICE Framework: DATEX call in isu_comev_process_invoice If you want to use a project-specific data exchange basic process, you can replace the methods belonging to BAdI ISU_IDE_DATEXCONNECT with your own implementation.
______________________________________________________________
SAP AG 107
SAP Utilities ______________________________________________________________
See also Release Information: Data Exchange Processes for Master Data Changes
1.14.6 Definition of Check Parameters in Customizing (New)

Use Incoming bills can be processed automatically during intercompany data exchange. The processing of documents includes a number of different processes (for example, identification, check before data is copied, copying data, check after data is copied, data transfer).You can also define your own function modules for these processes to check amounts, time limits, bill periods, billed quantities, and so on. Previously, it was not possible to define check parameters directly, rather they had to be defined locally in the individual function modules. As of SAP Utilities 4.72, you can define check parameters in Customizing as well as setting checks as standard checks or defining checks directly in a service provider agreement based in point of delivery group, bill or payment advice note type, or document type. You can define service provider agreement types for the new deregulation process INV_INCHCK (Check Parameter for Bill and Payment Advice Note Receipt). You can use function module ISU_DEREG_GET_INV_INCHCK in customer-specific check modules to determine the checks predefined in Customizing or those defined in service provider agreements based on points of delivery, point of delivery groups, bill and payment advice note types, document types, and check types. Effects on Customizing You define check parameters in Customizing for SAP Utilities under Define Check Parameters. You define new service provider agreements based in deregulation process INV_INCHCK in Customizing for SAP Utilities under Define Service Provider Agreement Types.
1.14.7 Manual Billing in the Deregulated Scenario (New)

Use Previously, you could only send a manual billing document (transaction EA16) in payment processing for intercompany data exchange if it was invoiced in combination with other (non-manual) billing documents. As of SAP Utilities 4.72, you can also invoice and send manual billing documents individually in the deregulated scenario.
______________________________________________________________
SAP AG 108
SAP Utilities ______________________________________________________________
1.14.8 ID Type in Customizing (neu)

Use Incoming bills can be processed automatically during intercompany data exchange. An ID type is required so that the system can interpret bill lines. Previously, you had to specify the ID type in the parameter configuration of the service provider agreement for bill receipt for each document type. As of SAP Utilities 4.72, you can set the ID type directly in Customizing for each permitted document type per bill or payment advice note type. This has the advantage that a service provider agreement is not necessarily a requirement. If the ID type is defined in Customizing as well as in the service provider agreement, the ID type from the agreement is used. Effects on Customizing Customizing for SAP Utilities -> Intercompany Data Exchange -> Bill and Payment Advice Note Processing -> Make Basic Settings.
1.14.9 Service Provider (Enhanced)

Use Identification of Service Provider Using the External Number (ID) A check is perfomed in the service provider transactions ( EEDMIDESERVPROV01, EEDMIDESERVPROV02) to ensure that the external numbers in the system are unique. This check was changed for SAP Utilities 4.64 (AOSP14) so that only the service type has to be unique. Take this into account in your projects when identifying the service provider in the data exchange processes (see note 601412). The following function modules and methods have changed: Function modules: o o ISU_SERVICE_PROV_GET_BY_EXT_ID ISU_DB_ESERVPROV_SINGLE_EXT_ID
Methods: o o SELECT_BY_EXTERNAL_ID SELECT_DB_SERVPROV_EXTERNALID
If more than one service provider is found for an external number, the exception NOT_UNIQUE (service provider not unique) is issued. You use new method SELECT_DB_SERVPROV_EXTID_BOTH of class CL_ISU_SERVICEPROVIDER to determine multiple service providers for the first and second external numbers, for example.
______________________________________________________________
SAP AG 109
SAP Utilities ______________________________________________________________
1.14.10 Hide Subprocesses (New)

Use As of SAP Release 4.72, you can hide subprocesses when processing documents in bill and payment advice note processing. You define in Customizing whether a subprocess can be hidden. You can hide a subprocess as long as it is still to be executed. If the current processing status of the document does not allow the subprocess to be executed, you cannot hide it. The subprocesses are hidden by means of the dialog for displaying document data. You can display all subprocesses that are to be executed according to the Customizing settings and the service provider agreement. You can find these functions in the menu under Edit -> Subprocesses -> Display and Edit -> Subprocesses -> Hide. The following authorization is required to hide subprocesses: Authorization object: E_INV_DOC Bill receipt for Document/PAN Authorization field: INV_ACTIVT Authorization check for Activity Value: Hide Subprocess (9) Effects on Customizing The relevant subprocesses must be marked as hidable in Customizing: Make Basic Settings Define Process Control (Part 1) Define Process Control (Part 2)
1.14.11 BAdI for Checking User Input (New)

Use As of SAP Utilities 4.72, you can enhance the check for the data entered in the Enter Bill/Payment Advice Note dialog by defining method CHECK_USER_INPUT of BAdI ISU_INV_REMADV_DLG.
1.15 IS-U-TO
1.15.1 IS-U-TO-ARC
Tools
Archiving
1.15.1.1 Archiving for Route and Waste Disposal Order Objects

Use As of SAP Utilities Release 4.72, you can archive the route and waste disposal order objects. The following prerequisites and restrictions apply here:
______________________________________________________________
SAP AG 110
SAP Utilities ______________________________________________________________
Route Archiving You can now archive routes that are no longer used. To do this, the archiving object ISU_ROUTE has been created. You can use the archiving workbench (transaction SARA) to process this archiving object. To archive a route, it must have the status Deletion Flag Set. You set this directly in the route. To be able to set this status, the routes must no longer have an active service, and must not be allocated to any waste disposal order that still has an open status. The archiving program consists of the following parts: The routes to be archived are analyzed in advance to see if they can be archived. If they can be archived then a deletion flag is set. You can use the BAdI EEWA_ROUTE_ARCHIVE to influence this analysis. For further information, see the documentation for the BAdI. In the write program the routes to be archived are entered in the archive files. The archive files are then written in the archiving system. In the deletion program, the archived routes are deleted from the database. Note that the archived data can no longer be reloaded in the system.
In the initial screen for route maintenance, you can use Call Archive to display archived routes. o Waste Disposal Order Archiving You can now archive waste disposal orders that, for example, have already been processed and are no longer kept in the system. The archiving object ISU_EORDER was created for this purpose. You can use the archiving workbench (transaction SARA) to process this archiving object. To archive a waste disposal order, the waste disposal order must have the status Deletion Flag Set. To do this, call transaction Delete Order and set the indicator Set Deletion Flag. The archiving program consists of the following parts: The waste disposal orders to be archived are analyzed in advance to see whether they can be archived. If they can be archived, then a deletion flag is set. You can use BAdI EEWA_WDO_ARCHIVE to influence this analysis. For further information, see the documentation for the BAdI. In the write program, the waste disposal orders to be archived are entered in the archive files, which are then written in the archiving system. In the deletion program, the archived orders are deleted from the database. Note that you can no longer reload archived data in the system.
Effects on Customizing To use the new functions, you must execute the following activities in the implementation guide (IMG): o o See also See the online help for further information on the archiving workbench. Activate Info Structure for Archiving Define Retention Periods for Archiving Objects
______________________________________________________________
SAP AG 111

Sap Isu PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Isu PDF

Uploaded by

Copyright:

Available Formats

SAP for Utilities

______________________________________________________________ SAP for Utilities Release Notes

Copyright(c) 2004 SAP AG. All rights reserved.

Inhaltsverzeichnis SAP Utilities ______________________________________________________________

Inhaltsverzeichnis SAP Utilities ______________________________________________________________

Inhaltsverzeichnis SAP Utilities ______________________________________________________________

Inhaltsverzeichnis SAP Utilities ______________________________________________________________

98 99 100 100 100

Inhaltsverzeichnis SAP Utilities ______________________________________________________________

SAP Utilities ______________________________________________________________

1.1 Efficient Processes in IS-U/CCS

SAP Utilities ______________________________________________________________

The Customer Overview has been enhanced.

SAP Utilities ______________________________________________________________

1.2 Changes to Implementation Guide (IMG) for Release 4.72

SAP Utilities ______________________________________________________________

SAP Utilities ______________________________________________________________

SAP Utilities ______________________________________________________________

1.4.1.1 Billing Class/Division Category (Enhanced)

SAP Utilities ______________________________________________________________

1.4.1.2 Activate all Meter Reading Units for Portion (Enhanced)

1.4.1.3 Create Schedule Records for an Unlimited Time in Advance (Changed)

SAP Utilities ______________________________________________________________

1.4.1.4 Amount Transfer in Portion Change

1.5.1.1 Authorization Group for Device Information Record (Enhanced)

1.5.1.2 Customer Enhancement for Device Information Record

SAP Utilities ______________________________________________________________

1.5.1.3 Customer Enhancement for Point of Delivery (Enhanced)

1.6.1 Permitted Values for Register Codes

SAP Utilities ______________________________________________________________

1.6.2.1 Validation During Device Allocation at Register Level (New)

1.6.2.2 IDocs for Rate Maintenance and Device Allocation (New)

1.6.2.3 Inclusion of Meter Reading Data in Bill Correction (New)

SAP Utilities ______________________________________________________________

Effects on Customizing Controling Bill Correction

1.6.3.1 Authorization Check (Enhanced)

1.6.4 IS-U-DM-IS 1.6.4.1 IS-U-DM-IS-SL

Device Inspection Sampling Procedure

1.6.4.1.1 Generic Lock for Complilation of Sample Lots

SAP Utilities ______________________________________________________________

Energy Data Management

1.7.1 Determination of Consumption Factors in Backbilling

SAP Utilities ______________________________________________________________

1.7.2 Managing Day Value Profiles

SAP Utilities ______________________________________________________________

1.7.3 Analyses for Point of Delivery and Service Provider (New)

1.7.4 Unit of Measurement in Formula Profiles and RTP Billing (New)

SAP Utilities ______________________________________________________________

1.7.5 Analysis Program: Points of Delivery for Settlement Document (New)

1.7.6 Archiving Object ISU_EUFASS (New)

SAP Utilities ______________________________________________________________

EUFASS_HIST: Usage factors for installation (historical)

SAP Utilities ______________________________________________________________

1.7.7 Formual Profiles (Enhanced)

SAP Utilities ______________________________________________________________

SAP Utilities ______________________________________________________________

1.7.8 Analysis Program: Documents for Point of Delivery (New)

1.7.9 Profile Header (Enhanced)

See also BADI ISU_EDM_PROFHEAD

1.7.10 Profile Value Import (Enhanced)

SAP Utilities ______________________________________________________________

1.7.11 Context for Profile Allocation Role (New)