Isu En722771400837087

SAP
AG
Release Notes
________________________________________________________________
Release Notes SAP Utilities 4.62
________________________________________________________________
SAP AG
Release Notes
SAP AG
Release Notes
________________________________________________________________
Copyright 2000 SAP AG. All rights reserved.

No part of this documentation may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP AG.
SAP AG further does not warrant the accuracy or completeness of the information, text,
graphics, links or other items contained within these materials. SAP AG shall not be liable for
any special, indirect, incidental, or consequential damages, including without limitation, lost
revenues or lost profits, which may result from the use of these materials. The information in
this documentation is subject to change without notice and does not represent a commitment
on the part of SAP AG in the future.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, NT and Excel and SQL-Server are registered trademarks of
Microsoft Corporation.
IBM, OS/2, DB2/Universal Database, AIX, OS/400 and AS/400 are a registered
trademark of International Business Machines Corporation.
OSF/Motif is a registered trademark of Open Software Foundation.
ORACLE is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX-OnLine for SAP and Informix Dynamic Server are registered trademarks of
Informix Software Incorporated.
UNIX and X/Open are registered trademarks of SCO Santa Cruz Operation.
CORBA is a registered trademark of Object Management Group, Inc.
SAP, R/2, R/3, RIVA, ABAP, SAPoffice, SAPmail, SAPaccess, SAP-EDI, SAP
ArchiveLink, SAP EarlyWatch, SAP Business Workflow, R/3 Retail, SAP DB are
registered trademarks of SAP AG.
ADABAS is a registered trademark of Software AG
SAP AG assumes no responsibility for errors or omissions in these materials.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1
1.1
1.2
1.3
1.4
1.4.1
1.4.2
1.4.2.1
1.4.3
1.4.3.1
1.4.4
1.4.4.1
1.5
1.5.1
1.5.2
1.5.2.1
1.5.2.2
1.5.2.2.1
1.5.2.3
1.5.2.3.1
1.5.2.4
1.5.2.4.1
1.5.2.5
1.5.2.5.1
1.5.2.5.2
1.5.3
1.5.3.1
1.5.3.2
IS-U SAP Utilities

IS-U Release 4.62
Changes to the Implementation Guide
(IMG) in release 4.62
Processing the gross price
IS-U-MD Master Data
New: Point of Delivery Service
IS-U-MD-CT Utility Contract
IS-U-MD-IN Installation
New: Internal Load Profiles Can Now Be
Assigned to an Instal
IS-U-MD-POD Point of
delivery
Point of Delivery
IS-U-DM Device
Management
Device Management and Billing Now
Separate
IS-U-DM-TD Technical Device
and Connection Data
Changed: Selection Extended for Goods
Movement via Serial Nu
IS-U-DM-TD-RG Register Group
New fields in Device Installation,
Modification and Register
IS-U-DM-TD-WG Winding Group
New Transformer Type low-voltage
current transformer gro
IS-U-DM-TD-DC Device Category
IS-U-DM-TD-DE Device
New: Periodic replacement data in the
device master record
Extened selection options for serial
number selection
IS-U-DM-DI Device
installation
Display of MR Results from Device
Modification
Device Information Records
2
2
2
5
6
6
7
7
8
8
8
8
10
10
10
10
11
11
11
11
11
12
12
12
12
13
13
13
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.3.3
1.5.3.4
1.5.3.5
1.5.3.6
1.5.3.7
1.5.3.7.1
1.5.3.8
1.5.3.8.1
1.5.3.8.2
1.5.3.8.3
1.5.3.8.4
1.5.3.8.5
1.5.3.8.6
1.5.3.9
1.5.3.9.1
1.5.3.10
1.5.3.10.1
1.5.3.10.2
1.5.3.11
1.5.3.11.1
1.5.3.11.2
1.5.3.11.3
1.5.3.12
1.5.3.12.1
1.5.3.12.2
New Device Installation Functions

System Message for Period Consumption
Period Consumption During Device
Installation
Deletion of Period Consumption if Device
Installation Revers
IS-U-DM-DI-DG Device Grouping
IS-U-DM-DI-IN Installation
Suppression of Mulitple Billing-Related
Device Installations
Changed: No GET Parameters for
Installation, Removal, and Re
New: Enhancement to Device Installation
and Replacement
Change: New Parameters in Enhancement
EBIS0002
IS-U-DM-DI-OU Removal
IS-U-DM-DI-CH Replacement
New: Enhancement to Device Installation
and Replacement
IS-U-DM-DI-MO Modification
Function Module for Device Modification
IS-U-DM-DI-IS Installation
structure
Change: New Parameters in Enhancement
EBIS0002
13
14
14
14
14
15
15
15
15
16
16
16
17
17
17
17
17
17
18
18
18
18
19
19
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.4
1.5.4.1
1.5.4.2
1.5.4.3
1.5.4.4
1.5.4.4.1
1.5.4.4.2
1.5.4.4.2.1
1.5.4.4.2.2
1.5.4.5
1.5.4.5.1
1.5.4.5.2
1.5.4.5.3
1.5.4.5.4
1.5.4.5.4.1
1.5.4.5.4.2
1.5.4.6
1.5.4.6.1
1.5.4.6.2
1.5.4.6.3
1.5.4.6.4
1.5.4.6.4.1
1.5.4.6.4.2
1.5.4.6.4.3
1.5.5

IS-U-DM-MR Meter Reading
New: Technical Control Parameters in
Meter Reading Data Proc
Code field added to IDoc
ISU_MR_UPLOAD
List of Implausible Meter Reading
Results
IS-U-DM-MR-OR Meter Reading
Organization
New: Customer Include for Street Route
IS-U-DM-MR-OR-S Street Route
Automatic Adjustment of Street Route
New: Street Route Display
IS-U-DM-MR-DT Meter Reading
Order
New Field: Order was output
Additional Print Parameters for Parellel
Order Output Proces
New tranfser parameter in method
MeterDocCreate
IS-U-DM-MR-DT-O Order Output
New: Send Customer Meter Reading Cards
by E-Mail
Enhancement to multiple meter reading
order creation
IS-U-DM-MR-RT Meter Reading
Result
No deletion of MR results during
reversal of move-in/out
Parallel Processing for Mass Estimations
order creation
IS-U-DM-MR-RT-M Monitoring
New: ABAP List Viewer (ALV) in Manual
Monitoring
Manual MR monitoring via Collective Bill
Account
order creation
IS-U-DM-IS Device
Inspection
19
19
19
20
20
21
21
21
21
21
21
22
22
22
22
22
23
23
23
23
24
24
24
24
25
25
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.5.1
1.5.5.1.1
1.5.5.2
1.5.5.2.1
1.6
1.6.1
1.6.2
1.6.3
1.7
1.7.1
1.7.2
1.7.3
1.7.4
1.7.5
1.7.6
1.7.6.1
1.7.6.2
1.7.6.2.1
1.7.6.2.2
1.7.6.2.3
1.7.6.2.4
1.7.7
1.7.7.1
1.7.7.1.1
1.7.7.1.2
1.7.7.1.3
IS-U-DM-IS-SL Sampling
Procedure
New: Exclude Devices from Sample Drawing
IS-U-DM-IS-PR Periodic
Replacement
New: Entry of Serial Number During
Periodic Replacement List
IS-U-EDM Energy Data
Management
Separate
New Component: Energy Data
Management (IS-U-EDM)
New: Internal Load Profiles Can Now Be
Assigned to an Instal
IS-U-BI Contract Billing
Document Line Item Data Reduction
New Features in Manual Billing
Custom Data Output in the Document
Display
New: Table DBERCHT for Saving Individual
Document Texts
Separate
IS-U-BI-BD Billing Master
Data
New Variants in Billing
IS-U-BI-BD-RS Rate Structure
New: Dynamic Period Control in Billing
New Functions in the Facts
Gross Prices
New Features for Maintaining Rate and
Billing Schema
IS-U-BI-SF Special
Functions
IS-U-BI-SF-GA Gas Billing
Calculation of Average with Lowest
Calorific Value
Enhancement of reading daily calorific
values.
Saving the Volume Correction Factor in
25
25
25
25
26
26
26
29
29
29
30
31
31
31
32
32
32
32
33
33
33
34
34
34
35
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.7.8
1.7.8.1
1.7.8.1.1
1.8
1.8.1
1.8.2
1.8.3
1.8.4
1.8.5
1.8.6
1.8.7
1.8.7.1
1.8.7.2
1.8.7.3
1.8.7.4
1.8.7.5
1.8.7.6
1.8.8
1.8.8.1
1.8.8.2
1.8.8.3
1.8.8.4
1.8.8.5
1.8.8.6
the Register
IS-U-BI-PC Billing
Execution
IS-U-BI-PC-AU Automatic
Billing and Simulation
Manual MR monitoring via Collective Bill
Account
IS-U-IN Invoicing
Define EDI transmission
New methods for object PrintDoc
Create joint consumption and partial
bills
Stop bill printout
Debit entry from statistical items in
invoicing
New event in invoicing for due date
synchronization
IS-U-IN-PC Invoice
Processing
Cash and Bill Accounting in England
Document type assignment for contract
accounts receivable an
Checking the sort order for reversal of
invoicing documents
Enhanced rounding functionality in
invoicing
Event for Tax Determination in Invoicing
Changes to tax determination time and
date type.
IS-U-IN-BB Budget Billing
Plan
New Budget Billing Plan - Payment Schema
Adjustment of budget billing plans to
changed billing dates
Adjustment of individual budget billing
plans
Selective Release of the Payment Plan
Balance-Forward Amount
Changes and New Features in the Payment
Plan
New Features in the Manual History of
the Payment Plan
35
35
35
35
36
36
36
37
37
37
38
38
38
39
40
40
41
41
42
42
42
43
43
43
44
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.9
1.9.1
1.9.2
1.9.3
1.9.4
1.9.5
1.9.6
1.9.7
1.9.8
1.9.9
1.9.10
1.9.11
1.9.12
1.9.13
1.9.14
1.9.15
1.9.16
1.9.17
1.9.18
1.9.19
1.9.20
1.9.21
1.9.22
1.9.23
1.9.24
1.9.25
1.9.26
1.9.27
1.9.28
1.9.29
1.9.30
1.9.31
1.9.32
IS-U-CA Contract
Accounts Receivable and Pay
Legal Tax Reporting for Argentina
Changes to Submitting Receivables to
External Collection Age
Cash and Bill Accounting in England
Changes in Correspondence for Security
Deposits
Changes in Archiving
Changes in Authorization Management
Changes in the Account Balance Display
New BAPIs
Changes to Payment at Cash Desk
Changes to Check Management
Changes to Submitting Receivables to
External Collection Age
Changes to the Contract Account
Changes to Correspondence
Changes in Creditworthiness
Changes to Doubtful Entries and
Individual Value Adjustments
Changes to Dunning
Changes to Events
Changes to the Implementation Guide for
Contract Accounts Re
Changes to Deferral and Installment Plan
International Developments
Changes to Integration with Other
Components
Changes to Interest Calculation
Changes to Job Control
Changes to Mass Activities
Changes to Open Item Management
Changes in Payment Processing
Changes to the Payment Program
Changes to Postings and Documents
Changes to Posting Areas
Changes to Returns
Changes to Reversals
Changes to Single Roles in Contract
Accounts Receivable and
45
45
45
46
47
47
47
48
49
50
52
53
54
55
57
57
58
58
60
62
62
63
64
65
65
65
66
69
74
76
76
78
79
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.9.33
1.9.34
1.9.35
1.10
1.10.1
1.10.2
1.10.2.1
1.10.2.2
1.10.2.3
1.10.2.4
1.10.2.5
1.10.3
1.10.3.1
1.10.3.1.1
1.10.3.1.2
1.10.3.1.3
1.10.3.1.4
1.10.3.2
1.10.3.2.1
1.10.4
1.10.4.1
1.10.5
1.10.5.1
1.10.6
1.10.6.1
1.10.7
1.10.7.1
1.10.7.2
1.11
1.11.1
New Reports
Changes to Security Deposits
Changes in Taxation Procedure
IS-U-CS Customer Service
New: Master Data Template and Master
Data Generator
IS-U-CS-FO Front Office
New: Processing Documents Received in
CIC
Enhancements to Data Environments of
Customer Interaction Ce
Workflow Inbox for the Application Area
in the Customer Inte
Managing Orders and Appointments
IS-U-CS-BT Process
Execution
IS-U-CS-BT-IO Move-In/Out
New: Contract Change without Invoicing
Changed: Enhanced Functions in Move-In
and Move-Out Processi
New: Customer Change
No deletion of MR results during
reversal of move-in/out
IS-U-CS-BT-DR Installation
Disconnection/Reconnect
New Functions in the Areas
Disconnection/Reconnection/Collec
IS-U-CS-CC Customer Contact
New: Archiving of Customer Contacts
IS-U-CS-MA Marketing
IS-U Sales Suport with SD-CAS
IS-U-CS-CRM Integration:
Customer Relationship M
New: IS-U Sales Processing
IS-U-CS-ISS Internet
Self-Services
New: Business to Customer Internet
Scenario: Report Move-Out
New: Enter Meter Reading Results via WAP
IS-U-WM Work Management
IS-U-WM-PC Processing
80
81
82
82
82
84
84
84
85
85
85
86
86
86
87
88
89
89
89
90
90
91
91
92
92
93
93
94
95
95
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.11.1.1
1.11.1.2
1.11.1.3
1.11.1.4
1.12
1.12.1
1.12.2
1.12.3
1.12.3.1
1.12.3.2
1.12.3.3
1.12.4
1.12.4.1
1.12.4.2
1.12.5
1.12.5.1
1.13
1.13.1
1.13.2
1.13.3
1.13.4
1.13.5
1.13.6
1.13.7
1.13.8
1.13.9
Disaggregation of Sales and Distribution

(SD)/Customer Servi
Managing Orders and Appointments
New Selection Parameters for Periodic
Inspection Processing
Determination of Work Center for Orders
IS-U-WA Waste Management
Changed: Area Menu for Waste Management
New: Confirmation of Waste Disposal
Orders
IS-U-WA-MD Master Data
Changes and Additions to the Service
Frequency
Fleet Management
New: Route
IS-U-WA-PC Processing
New: Change and Display Waste Disposal
Order
New: Confirmation of Waste Disposal
Orders
IS-U-WA-IF Interfaces
Download und Druck von
Entsorgungsauftrgen
IS-U-IDE Intercompany
Data Exchange
New: Table DBERCHT for Saving Individual
Document Texts
Changed: Communication Control
New: Reference Number
New: Default Values for Deregulation
Scenarios
New: Determination of the Distribution
Company from Regional
Enrollment Process: Workflow for
Communication with Other Se
New Procedure for Creating Outbound
IDocs for Billing Docume
New Field in Contract: Service Provider
Responsible for Invo
New: Processing of Electonically
Transmitted Consumption and
95
95
96
96
97
97
98
99
99
99
100
101
101
101
102
102
102
102
103
104
105
106
106
107
107
108
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.13.10
1.13.11
1.13.12
1.13.13
1.13.14
1.13.15
1.13.16
1.14
1.14.1
1.14.1.1
1.14.1.2
1.14.1.3
Restrictions to IDE Functions

New Determination Function for Service
Provider Terms of Pay
Point of Delivery
New: Point of Delivery Service
New Procedure for Payment Transactions
with Third Parties
New Design for Service Providers
New: Status Management for Communication
in Enrollment Proce
IS-U-TO Tools
IS-U-TO-ARC Archiving
New: Archiving of Customer Contacts
Archiving Meter Reading Results
Parallel Processing of IS-U Archiving
Runs
108
110
110
112
113
113
114
114
114
114
115
116
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1 IS-U SAP Utilities

1.1 IS-U Release 4.62
Use
The following is an overview of changes contained in release 4.62 of the Utilities Industry (IS-U)
component. You need SAP standard release 4.6C in order to install IS-U 4.62.
Click here for instruction on how to generate release notes for both IS-U 4.62 and R/3 4.6C.
The new release contains enhancements that may require Customizing activities. See Changes to the
Implementation Guide (IMG) with Release 4.62 for a list of Customizing activities. These activities are
usually only required for new or enhanced functions.
Many release notes contain direct links to the IMG for SAP Utilities. You can also use the Business
Engineering Workbench to view all upgrade and/or delta Customizing activities. See Upgrade
Customizing/Delta Customizing). Enter 462 for the To release.
If you have any questions, contact your IS-U consultant or hotline.
1.2 Changes to the Implementation Guide (IMG) in release 4.62

Use
Changes to the IMG of the Utilities Industry (IS-U) component are outlined in the following. To adopt the
changes, regenerate your project IMGs.
o
Master Data
-
Business Partner
The activity Define Primary Utility Company has been added to the Installer area.
The activity Define Information Release was removed from the Contract Partner area and
added to the Intercompany Data Exchange area under Process Management. It is now called
Define Information Release Status for Business Partner.
Utility Installation
The activity Define Information Release was removed from the Contract Partner area, and
added to the Intercompany Data Exchange area under Process Management. It is now called
Define Information Release Status for Installations.
Point of Delivery
The area Point of Delivery is new. It contains the activities Define Number Ranges for Point
of Delivery IDs, Define Point of Delivery Type, and Define Structure of Point of Delivery ID
Device Management
Meter reading
In Basic settings, the activity Define Control Parameters for Meter Reading Data Processing is
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
new.
o
Energy Data Management

The area Energy Data Management is new. It contains the following areas:
-
Basic Settings
Profile Management
Interface to External Systems
Interface to RTP Billing
Contract Billing
-
Billing Master Data

The area Dynamic Period Control was added to the Schemas area. Dynamic period control
contains the activities Define Dynamic Period Control and Define Dynamic Backbilling
Groups.
Invoicing
-
Invoice Processing
This area now contains the activity Define Rounding Rules for Rounding Amount
Carryforward.
Budget Billing Plan

The area Budget Billing Plan is new. This area contains the activities Define Payment Plan
Categories (AMB/BBP) for USA and Canada and Adjust Standard Value for
Balance-Forward Amount . These activities were previously assigned to the Basic Functions
area.
Contract Accounts Receivable and Payable

-
Basic Functions
In the area Postings and Documents -> Document -> Define Account Assignments for
Automatic Postings -> Automatic G/L Account Determination, the activity Define Accounts
for Expense/Revenue from Cash Payments (ISU) was removed and the activity Define CO
Short Account Assignments for IS-U Contracts added.
The activity Define Classification Determination for Tax Reporting has been added to the area
Define Specifications for Official Document Numbers.
The activity Maintain Minimum Amounts for Taxes has been added to the area Particular
Aspects of Tax Reporting.
The area Tax Reports now contains the new area Legal Tax Reporting for Argentina.. This
area contains Basic Functions , Sales/Purchase Tax Reporting, Revenue Tax Reporting
and the activity Verify Customizing Consistency.
For further changes in Accounts Receivable and Payable, see Additional Changes.
Customer Service
-
Customer Interaction Center

The activities Establish Settings for Workflow Inbox Components , Define Process for
Inbound Documents and Define Processes for Customer Callbacks are new.
Process Execution
Define Reasons for Contract Change has been moved from Move-Out to Move-In/Out.
The Move-In/Out area now contains the activity Define Reasons for Customer Change.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Owner Allocation has been moved from Move-In/Out to Process Execution.
Internet Self Services

The activity Define Specialist Settings for IS-U is new.
Marketing
Business Partner Segmentation is new.
The activities Configure Consumption History and Define Business Partner Segmentation
are new.
IS-U Sales and Distribution Processing

The area IS-U Sales and Distribution Processing is new.
The activities Define Utility Products, Define Master Data Templates for Utility Products,
Generate Characteristics for Utility Products for Allocation to SD MMaterials, Define
Master Data Templates for Sales Order/Quotation, Define Profiles for IS-U Sales
Order/Quotation, and Define User-Defined Utility Product Set Types are new.
Work Management
The area Work Management has been restructured.
-
Master Data
Activities Define Service Objects, Define Set Levels for Service Objects and Allocate
Service Objects to Division and Set level. These activities were formerly under Orders.
Processing
The activity Define Plant and Work Center Determination for Orders has been added to the
Orders. Work Center Determination is new. Define Plant Determination for Orders was
allocated to Master Data.
The activity Define Plant Determination for Orders has been added to Notifications. This
activity was previously under Master Data.
Service Connection Processing now contains the activity Define Control Parameters for
Disaggregation of SD/CS.
The area Supply Permit Processing is new. It contains the activities Allocate Catalog, Code
Group and Code to Permit and Define Permit Determination. These areas were formerly
under Processing or Master Data.
Waste Management
-
Basic Settings
The area Basic Settings is new. The activities Define Confirmation Categories and Define
Difficulties are new. The activity Define Service Areas was formerly called Define Product
Areas and belonged to Master Data.
Master Data
The area Vehicles is new. It contains the activity Define Container Service Types and new
activity Allocate Waste Attributes to Vehicle Type.
The area Service Frequency is new. It contains the activities Define Number Ranges for
Service Frequency and Define Customer.
The activity Define Number Ranges for Routes is new.
Processing
The activity Define Notes for Confirmation has been added to the area Waste Disposal
Orders.
Interfaces
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The area Interfaces is new. It contains the old activity Define Form for Downloading Service
Frequency (formerly under Processing) and the new activity Define Form for Downloading
Waste Disposal Orders.
o
Information System
Intercompany Data Exchange
General Settings
The area Basic Settings is new. The activity Define Operational Area is new.
Service Provider
The activity Define Service Types was changed.
The activities Define Service Providers, Allocate Operational Area and Perform
Certifications are new.
The activities Define Rate Categories for Service Provider and Define Rate Categories for
Supplier Change and Contract End Date have been placed under Process Management.
The area Convergent Billing is now called Payment for Third Parties.
The activity Define Payment Classes for Service Provider is new.
Communication Control
The activities Define Number Ranges for Reference Numbers and Define Processing
Events are new.
The area Communication Control of Inbound Messages is new.
The activities Allocate Register Type, Allocate Units of Measurement and Allocate Line
Item Types are also new.
Process Management
The activities Define Service Types for Operation Areas and Configure Default Table for
IDE Process Control are new.
The area Status Management is new.
The activities Define Business Status forIDE Workflow and Define Technical Status for IDE
Workflow are new.
Tools
-
Archiving
The activity Activate Info Structure for Archiving is new.
System Modifications
The area User-Defined Enhancements Energy Data Management is new. It contains the
activity Define Structure of Point of Delivery ID.
The area User-Defined Enhancements for Energy Data Management is new. It contains the
areas Interval Lengths, Formulas and Results Functions.
The area User-Defined Variant Programs contains the activity Define Line Item Types.
1.3 Processing the gross price

Use
You can now process gross billing documents in invoicing.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Do the following to invoice gross billing documents:

o
Check that the presort key defined in the billing documents for bill printout refers to function module
ISU_BILL_TYPE_GROSS_PRICE_CONT (billing type for billing gross price). To establish settings
for this in Customizing choose: SAP Utilities -> Invoicing -> Bill Printout -> Define Sort Criteria for
Bill Printout. Billing documents are sorted according to contract. This means that for each contract one
or more tax lines are printed on the bill. The parameter no subtotal is not taken into account when
processing gross prices.
Define an account which includes gross price tolerances, which appear even when gross billing
documents are inconsistent. All gross lines of a billing document lead to the final bill amount. The
actual posting- relevant lines of a billing document (including tax) need not be identical to the gross
amount. In order to clear these differences, an offsetting item is posted for the open item. Define the
accounts in Customizing under Financial Accounting -> Contract Accounts Receivable and
Payable -> Basic Functions -> Postings and Documents -> Document -> Define Account
Assignments for Automatic Postings -> Automatic G/L Account Determination -> Accounts for
Rounding of Gross Amounts (IS-U)
The maximum permissible difference is 0.01 UNI per each tax item incurred. If the tolerance is overriden,
invoicing of the invoicing unit is canceled.
Note that only the gross lines of the billing document are used in the print document. The relative price
elements cannot be printed.
See also
Further information about the gross price is available in release note Gross Price
1.4 IS-U-MD
Master Data
1.4.1 New: Point of Delivery Service

Use
In deregulated markets, a point of delivery is supplied with services. These are known as point of delivery
services. Examples include distribution, supply and meter reading services.
A point of delivery service is used primarily for communication between service providers.
You can divides point of delivery services into billable and non-billable services. Billable services are
modelled using contracts is IS-U; non-billable services are stored in the new table ESERVICE (point of
delivery service).
With the point of delivery service, we have created a new business object in IS-U. The point of delivery
service has two subobjects, contract and non-billable service. This does not entail any new levels in the
data model.
The point of delivery service contains the service provider and the service type. This means that
Communcation Control can always the service provider with whom the system has to communicate for each
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
point of delivery.
A point of delivery is created automatically during every enrollment; this also includes the necessary
contracts and non-billable services.
During a manual move-in, the system also creates any non-billable services required for the point of delivery.
During a move-out, the non-billable services are canceled, unless you have configured the system
accordingly in the Customizing activity Define Service Types.
Like the contract, the point of delivery service contains a start and finish date that define its validity period.
Effects on Data Transfer
Billable point of delivery are created through migration, in the same way as contracts were previously. The
non-billable service exist as a new migration object.
Effects on Customizing
Define the service types in Define Service Types. Allocate the service providers to the operational areas in
Allocate Operational Area.
See also
For more information, see
o
New: Point of Delivery
Changed: Communication Control.
1.4.2 IS-U-MD-CT
Utility Contract
1.4.2.1
Short text
Account Assignment-Relevant Field in Contract

Use
The contract now contains the new field CO account assignment (CO account determination key for IS-U
contract).
The account determination key represents a combination of the fields listed below (defined in Customizing)
used for CO account assignment:
o
Cost center
Profit center
Order
Project (planning element for project structure)
Account assignment to profitability segment (CO-PA)
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Previously, you could only maintain this account assignment in the contract. The use of the new account
assignment key makes contract maintenance easier for the following reasons:
o
The agent no longer has to deal with large numbers of possible account assignment combinations
Assigning postings from billing to accounts based on the profitablity segment can now be done by
activating the Assignment to a Profitability Segment field for each account determination key
Effects on Existing Data

The contracts that already exist in your system are converted by an SAP program. For each combination of
account assignments in the contracts, the program creates a generic account determination key and stores it
in the contract master.
The attributes previously used in the contract (cost center, profit center, order, project and account
assignment to profitability sector) are no longer used as of this release.
Store the account determination key in Store CO Account Assignments for IS-U Contracts
1.4.3 IS-U-MD-IN
Installation
1.4.3.1 New: Internal Load Profiles Can Now Be Assigned to an Instal

Use
Previously: You could only assign external load profiles (whose values where not managed in IS-U) to an
installation.
Now: You can also assign internal load profiles (whose values are managed in the Energy Data
Management (IS-U-EDM) component) to an installation. Double-click on an internal load profile to
navigate directly to the Display Profile transaction.
You can assign a historical consumption factor to each load profile; the values of the corresponding load
profile are multiplied by this factor. The consumption factor is determined automatically for synthetic
profiles that are maintained in the IS-U-EDM component.
See also
For more information, see the Release Note Assigning Load Profiles to an Installation in section See also.
1.4.4 IS-U-MD-POD
Point of delivery
1.4.4.1 Point of Delivery

Use
Registers, devices and installations are now allocated to points of delivery. A point of delivery has a unique
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
point of delivery ID. This is used in deregulated markets to uniquely identify a point at which energy is
drawn, regardless of the geographical boundries of distribution grids.
Points of delivery can be divided into two groups, deregulation points of delivery and technical points of
delivery.
o
Deregulation point of delivery

These are usually provided by distributors or market regulation authorities. They are used in
Intercompany Data Exchange (IDE) to uniquely identify the point to which energy is supplied during
communication with the supplier or with other service providers .
Points of delivery are allocated to an installation. Note that an installation can only have one point of
delivery, but a point of delivery can be allocated to several points of delivery. This is the case in
installation coupling, where two installations with the same point of delivery are required in order to
bill a supply contract and a distribution contract.
Technical point of delivery

In this case, registers are allocated to a point of delivery. This view is relevant for the Energy Data
Management (EDM) component.
The point of delivery is used to identify profiles that are allocated to registers in IS-U/EDM. When
profile values are imported ( load shape), the point of delivery is specified. The system can then
determine the interval meter allocated to the point of delivery. Consequently, the profile values can be
automatically copied to the profile allocated to the interval meter. This enables you to import measured
load shapes without any knowledge of the objects managed in IS-U/EDM. You only need to know the
point of delivery ID.
In this way, you can perform a simple data transfer for load shapes from an automated meter reading
system.
A point of delivery can be used for both deregulation (IDE) and techincal (EDM) purposes simultaneously.
This is the case for distributors that use EDM and use the point of delivery to communicate with suppliers.
Suppliers only use the point of delivery for deregulation purposes.
You can also distinguish between internal and external point of delivery IDs. In the case of deregulation
points of delivery, an installation is created with an external and an internal ID. This is done for technical
reasons; the internal point of delivery ID cannot be seen externally. The point of delivery remains inactive
until it is assigned and external ID. An ID is allocated to the point of delivery in the installation.
Point of delivery IDs are usually created with a predefined structure, from which you can derive information,
such as the distribution company and postal code of the area in which the point of delivery is located).
To do this, you must display the point of delivery ID in its formatted form. We support an unformatted form,
as well as the structure category metering code. You can define additional formats yourself.
Each point of delivery is created with the necessary point of delivery services. These are determined from the
operational area in which the point of delivery is located.

You must now allocate an internal point of delivery ID to each installation. To ensure this happens an XPRA
is started at the point of upgrade that creates the necessary points of delivery. The XPRA only creates
internal point of delivery IDs. To allocate any existing point of delivery IDs you must define your own
programs.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Ensure that a point of delivery is created for each installation, and that the point of delivery and installation
are linked.
Define the structure of the point of delivery ID in the following Customizing activity: Define Point of
Delivery ID. Here you define both the structure itself, and the function module that formats the display.
See also
For more information, see Point of Delivery Service and Default Value Procedure
1.5 IS-U-DM
Device Management
1.5.1 Device Management and Billing Now Separate

Use
You can now use the IS-U Device Management (IS-U-DM) and Billing (IS-U-BI) components separately.
You can use IS-U as follows:
o
For billing (in the case of suppliers, for example)

If you use IS-U mainly for billing, you only have to maintain the device data necessary for billing
customers, such as rate data, device allocations, register relationships and logical register data. You
store device data in a device info record. To do this, go to Utilities Industry -> Device Management
-> Installation -> Device Info Record.
An interface with the Plant Maintenance (PM) application component is no longer necessary. The
system communicates with other applications via the point of delivery. For example, the point of
delivery is used for importing consumption data.
For managing devices (in the case of meter operators or transmission and distributions companies, for
example).
You now store rate data in the devce data and not directly in the rate data. This allows you to validate
and estimate meter reading results without assigning them to a rate first.
All billing functions are still available in device management. However, you are no longer required to
maintain billing objects before using functions such as validation.
1.5.2 IS-U-DM-TD
Technical Device and Connection Data
1.5.2.1 Changed: Selection Extended for Goods Movement via Serial Nu

Use
You can limit your selections as follows:
o
Selection via material number
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
All serial numbers for the material entered are displayed for transfer
o
Selection via sending plant and storage location

Serial numbers fulfilling criteria of sending plant and storage location are displayed
Extended selection by calling serial number list

You can compile the serial numbers to be transferred by calling the serial number list. Choose
Extended selection to do this.
The new selection options can be combined in any way desired.
1.5.2.2 IS-U-DM-TD-RG
Register Group
1.5.2.2.1 New fields in Device Installation, Modification and Register

Use
The following fields have been added at the register level:
o
Validation class for independent validations
Unit of measurement for billing
Weighting key
Interval length
Time-of-use type
1.5.2.3 IS-U-DM-TD-WG
Winding Group
1.5.2.3.1 New Transformer Type low-voltage current transformer gro (3-phase)

Use
Transformer type low-voltage current transformer group (3-phase) is new.
These transformers behave like low-voltage current transformers during:
o
Processing of winding groups
Installation, removal, replacement and modification of devices:
Processing of device relationships
Transformers of type low-voltage current transformer group (3-phase) cannot be allocated to the
categories transformer group and meter board.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.2.4 IS-U-DM-TD-DC
Device Category

Use
o
1.5.2.5 IS-U-DM-TD-DE
Device
1.5.2.5.1 New: Periodic replacement data in the device master record

Use
In the device master record, certification and inspection data are now found under Cert./ins. data.
Cert./ins. data now contains information on periodic replacement. A message is displayed if a device is in a
periodic replacement list.
1.5.2.5.2 Extened selection options for serial number selection

Use
You can now select serial numbers using the following:
o
Device category data

-
Division
Funktion class
Construction class
Device category description
Measurement type
Type of certification requirement
Data from the device master record
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Certification number
Certification status
1.5.3 IS-U-DM-DI
Device installation
1.5.3.1 Display of MR Results from Device Modification

Use
You can now display meter reading results directly from the functions Device Modification and Display or
Change Device Info Record
To do this, choose Goto -> Meter Reading Results -> Display.
1.5.3.2 Device Information Records

Use
You can now use device info records.
In a device info record, one material can only be allocated to one serial number at a given time (T1). Devices
and device info records are treated identically. For example, if at T1 there is a device of material (device
category) M1 with serial number (device number) G1, then there cannot be a device info record in the same
device category with device number G1.
Device info records, like devices that have undergone technical installation, can be in device allocations and
register relationships. They can also be installed and removed for billing. They are prorated when they
undergo billing-related removal from the last installation. They are processed like normal devices during
meter reading processing. However, you cannot use PM functions here.
You can create, change and display device info records under Device Management -> Device Installation
-> Device Information Record
You can create device info records automatically via billing-related installation.
To specify whether device info records are created automatically at the time of billing-related installation, go
to Customizing and choose Define System Parameters for Installation/Removal/Replacement .
1.5.3.3 New Device Installation Functions

Use
Up until now you could only enter period consumption for 365 days (meaning period consumption was also
annual consumption).
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Now you can enter period consumption for any number of days.
This means the period consumption is valid for the number of days you specify starting on the day of device
installation up until the next change.
Example:
Period consumption of 300 kWh is valid for 30 days starting on 01/01/2000. This corresponds to annual
consumption of 3600 kWh. During device installation, you enter 300 in the Period cons. and 30 in the No.
of days field.
1.5.3.4 System Message for Period Consumption

Use
A system messsage now prompts you to enter or maintain period consumption one day after meter reading
results are entered or at the time of technical or billing-related installation or move-in.
If you define the period consumption starting more than one day after the last meter reading, then two period
consumption values are used to estimate consumption and the forecaset period is split in two. This means
that consumption cannot be estimated accurately.
See also
System message for period consumption
1.5.3.5 Period Consumption During Device Installation

Use
You now have to enter period consumption during device installation. Period consumption is used as a basis
for extrapolations when no meter reading result is available.
Previously, a reference value from the rate was used as a basis for extrapolations.
However, after releases 4.62 it will not longer be possible to enter a reference value in the rate.
1.5.3.6 Deletion of Period Consumption if Device Installation Revers

Use
The period consumption entered during a device installation is now deleted when the installation is reversed.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.3.7 IS-U-DM-DI-DG
Device Grouping

Use
o
1.5.3.8 IS-U-DM-DI-IN
Installation
1.5.3.8.1 Suppression of Mulitple Billing-Related Device Installations

Use
You can now decide whether a device can be installed for billing in multiple installations at the same time.
To do this, go to Customizing and choose Define System Parameters for Installation/Removal/Replacement.
The parameters NOMULTINS and INMULTINST are new and are used as follows:
o
NOMULTINST (device may not be installed in more than one installation)

You cannot install a device or a device info record for billing in one installation if the device is installed
in another installation at the same time (or will be installed in another installation later).
INMULTINST (device may be installed in more than one installation)

If you try to install a device for billing and the device is already installed in another installation (or will
be installed in another installaton later), you receive an information message that you must confirm.
1.5.3.8.2 Changed: No GET Parameters for Installation, Removal, and Re

Use
On the initial screen for device installation, removal and replacement, the connection object, device location
and installation are no longer proposed from the Set-Get_Parameter.
This means you no longer have to delete default values.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________

Use
o
Weighting key
Interval length
Time-of-use type
1.5.3.8.4 New: Enhancement to Device Installation and Replacement

Use
You can now use Enhancement IEQM0001 (Additional checks for equip. installation at functional locations)
during full and technical installation as well as replacement of a device.
First define System Parameters for Installation/Removal/Replacement and copy entry PMIEQM0001 (Call
user exit at installation/removal/replacement) to the table.
1.5.3.8.5 Change: New Parameters in Enhancement EBIS0002

Use
New parameters have been added to the following function modules in enhancement EBIS0002:
o
EXIT_SAPLE20Q_001 (IS-U: User Exit for Rate Type Input Help)
EXIT_SAPLE20Q_002 (IS-U: User Exit for Input Help for Rate Fact Group)
EXIT_SAPLE20Q_003 (IS-U: User Exit for Checking Rate Type and Fact Group for PAI Event)
EXIT_SAPLE20Q_004 (User Exit for Proposal Logic for Rate Type and Fact Group for PBO Event)
The following parameters are new:

o
X_ETDZ (technical data of installed register)
X_V_EGER (device data)
These function modules are called during installation (both full and billing-related installation) and rate
maintenance.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________

Use
o
1.5.3.9 IS-U-DM-DI-OU
Removal

Use
1.5.3.10 IS-U-DM-DI-CH
Replacement

Use
1.5.3.10.2 New: Enhancement to Device Installation and Replacement

Use
You can now use Enhancement IEQM0001 (Additional checks for equip. installation at functional locations)
during full and technical installation as well as replacement of a device.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
First define System Parameters for Installation/Removal/Replacement and copy entry PMIEQM0001 (Call
user exit at installation/removal/replacement) to the table.
1.5.3.11 IS-U-DM-DI-MO
Modification
1.5.3.11.1 Function Module for Device Modification

Use
You can now use function module EXIT_SAPLEG42_001 during device modification.
The function module is called after device data is updated and updates user-defined data related to the
modification.
For more information, see the function module documentation.

Use
o
Weighting key
Interval length
Time-of-use type

Use
o
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.3.12 IS-U-DM-DI-IS
Installation structure
1.5.3.12.1 Change: New Parameters in Enhancement EBIS0002

Use
New parameters have been added to the following function modules in enhancement EBIS0002:
o
EXIT_SAPLE20Q_001 (IS-U: User Exit for Rate Type Input Help)
EXIT_SAPLE20Q_002 (IS-U: User Exit for Input Help for Rate Fact Group)
EXIT_SAPLE20Q_003 (IS-U: User Exit for Checking Rate Type and Fact Group for PAI Event)
EXIT_SAPLE20Q_004 (User Exit for Proposal Logic for Rate Type and Fact Group for PBO Event)
The following parameters are new:

o
X_ETDZ (technical data of installed register)
X_V_EGER (device data)
These function modules are called during installation (both full and billing-related installation) and rate
maintenance.

Use
o
1.5.4 IS-U-DM-MR
Meter Reading
1.5.4.1 New: Technical Control Parameters in Meter Reading Data Proc

Use
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
You can now define technical control paameters for meter reading data processing that allow you to:
o
Define the number of meter reading orders to be processed together during order output, reversal and
estimation.
Activate the consistency check for the table of meter reading results.
Deactivate the authorization check for the table of meter reading documents.
Define settings so that only plausible results are displayed when you correct plausbile meter reading
results.
Define settings so that only implausible results are displayed when you correct implausbile meter
reading results.
Define settings so that the dependent validation for serial switching is only carried out for primary
meters and that secondary meters can only undergo independent validations.
The parameters you define are valid across the system.

Establish settings in Customizing under Define Technical Control Parameters for Meter Reading Data
Processing.
1.5.4.2 Code field added to IDoc ISU_MR_UPLOAD

Use
The Code field has been added to IDoc ISU_MR_UPLOAD.
You can now enter the register code when you upload meter readings. This means that you no longer have to
specify the register.
The meter reading is allocated to the appropriate register of the device via the register code.
1.5.4.3 List of Implausible Meter Reading Results

Use
You can now output a list of implausible meter reading results from the Execute Correct Implausible
Meter Reading Results screen. You can correct the results in the list directly from this screen.
1.
Go to Execute Correct Implausible Meter Reading Results and choose Implausible MR results.
You branch to ALV list of implausible results.
2.
Enter your selection criteria and choose Execute.

A list of all implausible results is displayed matching the selection criteria you entered.
3.
Select the meter reading results you want to correct.
4.
Choose Correction to process the results.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.4.4 IS-U-DM-MR-OR
Meter Reading Organization
1.5.4.4.1 New: Customer Include for Street Route

Use
A customer include has been added to table ELWEG (street route)
You can now save your own data in the street route of a meter reading unit for reporting purposes.
1.5.4.4.2 IS-U-DM-MR-OR-S
Street Route
1.5.4.4.2.1 Automatic Adjustment of Street Route

Use
Up until now when you changed the meter reading unit of an installation, the street route of the previous
meter reading unit was not automatically adjusted. Instead, a system message prompted you to delete any
unneeded devices from the street route of the previous meter reading unit.
Now, when you change the meter reading unit a dialog box is displayed. You can decide whether the street
route of the previous meter reading unit is to be automatically adjusted.
In IDoc ISU_4K the adjustment is made automatically in the background.
1.5.4.4.2.2 New: Street Route Display

Use
Up until now, the menu path Utilities Industry -> Device Management -> Meter Reading -> Meter
Reading Organization contained the path Maintain Street Route. Here you were able to either change or
display the street route for a meter reading unit.
The menu path Display Street Route is new. Here you can only display street routes for a meter reading
unit.
Effects on System Administration
You can now issue your employees display authorizations for street routes.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.4.5 IS-U-DM-MR-DT
Meter Reading Order
1.5.4.5.1 New Field: Order was output

Use
When an order has been successfully output, the Order was output field is selected in the meter reading
document.
The ABAP list viewer (ALV) in manual monitoring allows you to use the Change layout field to display
the Order was output field.
See also
You can find more information on the ABAP list viewer in release note New: ABAP List Viewer (ALV) in
Manual Monitoring.
1.5.4.5.2 Additional Print Parameters for Parellel Order Output Proces

Use
You can now enter additional parameters during parallel order output processing.
To go to order output, go to the IS-U menu and choose Device Management -> Meter Reading ->
Parallel Processing.
1.5.4.5.3 New tranfser parameter in method MeterDocCreate

Use
You can now use the parameter MeterReadingDocument.MeterDocCreate to transfer not only one
device, but also a table with all device numbers for which orders are to be created via this method.
This improves system performance.
1.5.4.5.4 IS-U-DM-MR-DT-O
Order Output
1.5.4.5.4.1 New: Send Customer Meter Reading Cards by E-Mail

Use
You can now use enhancement EDMEL35C to specify whether a customer receives his or her meter reading
cards by e-mail or by mail.
If you select the field Print card for MR by customer field, the card is sent either as an e-mail or as a
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
letter, depending on the output type you have chosen.
1.5.4.5.4.2 Enhancement to multiple meter reading order creation

Use
Up until now, meter reading documents for multiple order creation were created if you maintained a control
group in the technical register data.
Functions for multiple order creation have been enhanced as follows:
o
Orders for multiple readings are output on a form.
In manual monitoring, if selection criteria include a document in a multiple reading order, then all other
meter reading documents in the multiple reading order are displayed.
When you reverse a meter reading and selection criteria include a multiple reading order, then all other
documents in the order are displayed.
When you estimate a meter reading and selection criteria include a multiple reading order, then all other
1.5.4.6 IS-U-DM-MR-RT
Meter Reading Result
1.5.4.6.1 No deletion of MR results during reversal of move-in/out

Use
Previously, when you reversed a move-in, readings with reason 06 (move-in reading) were deleted. This also
applied to reason move-out readings with reason 03 (final reading for move-out).
Now these readings are not deleted if:
o
they were not estimated or derived
they only have meter reading reason 06 (move-in reading) or 03 (final reading for move-out)
These meter reading results are then stored in the system without a scheduled meter reading date and with
meter reading reason 09 (interim reading).
1.5.4.6.2 Parallel Processing for Mass Estimations

Use
You can now distribute mass estimation across several processes to be handled by several different systems
or by one system simultaneously.
You can enter various parameters, such as start time, start event, etc.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.5.4.6.3 Enhancement to multiple meter reading order creation

Use
o
1.5.4.6.4 IS-U-DM-MR-RT-M
Monitoring
1.5.4.6.4.1 New: ABAP List Viewer (ALV) in Manual Monitoring

Use
You can now use the ABAP list viewer to display meter reading results and orders during manual
monitoring.
You can use the ALV to edit lists. For example, you can change the sequence of columns, hide certain
columns, and add more columns. You can also store your own display variants.
1.5.4.6.4.2 Manual MR monitoring via Collective Bill Account

Use
You can now use the Collective bill accounts field when making selections via the contract or business
partner in manual meter reading monitoring.
If you select the Collective bill accounts field, the system selects:
1.
All contract accounts for the selection made
2.
All collective bill accounts for these contract accounts
3.
All contracts found via the contract accounts of the collective accounts.
The system displays:
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
4.
Meter reading documents and billing documents for these contracts
You can also select the Billing order selec. field in Automatic Billing and Simulation to select billing
orders for collective bill accounts.
1.5.4.6.4.3 Enhancement to multiple meter reading order creation

Use
o
1.5.5 IS-U-DM-IS
1.5.5.1 IS-U-DM-IS-SL
Device Inspection
Sampling Procedure
1.5.5.1.1 New: Exclude Devices from Sample Drawing

Use
You can now exclude devices from the sample drawing procedure during device installation, modification
and reconnection.
Select field no sample device (exclude devices for installation/ modification/removal from sample
drawing) in Customizing activity Define Parameter(s) for Sampling Inspection/Certification.
You can determine whether a device has been excluded from sample drawings by looking at the sample
device status when you display the device.
1.5.5.2 IS-U-DM-IS-PR
Periodic Replacement
1.5.5.2.1 New: Entry of Serial Number During Periodic Replacement List
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Use
You can now enter a serial number interval when you create periodic replacement lists. This enables you to
further restrict the device category.
Up until now you could only enter an entire device category.
1.6 IS-U-EDM
Energy Data Management

Use
o

example).
1.6.2 New Component: Energy Data Management (IS-U-EDM)

Use
Energy Data Management (IS-U-EDM) is a new IS-U component that must be purchased separately.
IS-U-EDM Release 4.62 is a First Customer Shipment (FCS) that is not intended for general use. This means
that you cannot implement IS-U-EDM without prior permission from SAP.
IS-U-EDM allows you to manage consumption data and related business processes. It is especially useful for
managing and billing consumption data measured at specific intervals (such asload profiles or load shapes).
The most important IS-U-EDM functions are:
o
Profile management
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
You can create, change and display profile values. You can display values as graphics or in
standard table format.
Functions for defining profiles can be found under Utilities Industry -> Energy Data
Management -> Profile Management -> Profile Header and under Energy Data
Management -> Profile Management -> Profile Values.
You can manage interval data in profiles. Examples of interval data include energy consumption,
transformation factors and prices. You can use 15-minute, 30-minute and 1-hour intervals. You
can also adjust the intervals provided to meet your requirements.
You can adjust interval lengths in Customizing.
You can display the status of profile values and versions.

You can define how the status is displayed in Customizing under Define Display of Profile Value
Status.
Definition and management of synthetic profiles

-
You can manage synthetic profiles and their values in your own predefined structure. Such
structures allow you to manage synthetic profiles differently according to season, for example.
You establish settings for synthetic profiles in Customizing under Basic Settings.
Functions for defining synthetic profiles can be found under Utilities Industry -> Energy Data
Management -> Profile Management -> Profile Header.
You can allocate synthetic profiles to installations in order to characterize the consumption
patterns of an installation. You also allocate a usage factor to profiles. In conjunction with the
synthetic profile, the usage factor determines the consumption of an individual installation. The
system can re-calculate the usage factor at the time of billing.
Functions for installations can be found under Utilities Industry -> Technical Master Data.
The system can automatically update the usage factor of a synthetic profile for an installation. To
implement this function, you have to add variant program QUANTI24 to the billing program in
Customizing under Define Schemas.
Integration of profiles with IS-U

You can allocate profiles to the registers you already manage in IS-U. In this way, profile data is linked
to the IS-U data model and profiles are integrated into standard IS-U business processes.
Before you can allocate profiles to registers, you have to Define Roles for Profile Allocation in
Customizing.
To do this, go to Utilities Industry -> Energy Data Management -> Profile Management -> Profile
Allocation.
Automatic calculation of profile values

Profile values can be calculated automatically using predefined formulas. For example, you can use the
total consumption measured by different meters at one location to form a singl profile for a customer.
Functions for defining automatic profile calculation can be found under Utilities Industry -> Energy
Data Management -> Profile Management -> Profile Header.
The functions for executing and monitoring automatic profile calculation can be found under Utilities
Industry -> Energy Data Management -> Automatic Profile Calculation.
Import of profile values

You can import profile values via:
-
BAPIs (Business Application Programming Interface) ISUPROFILE.Upload (corresponding IDoc

of basic type ISUPROFILE_UPLOAD01)
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
IDocs of basic type MSCONS

The function for automatic import monitoring can found under Utilities Industry -> Energy Data
Management -> Monitoring -> Profile Import.
o
OLE interface
Microsoft Excel has been integrated into IS-U-EDM via OLE interface (Object Linking and
Embedding)
This interface enables you to:
-
Export profile values (including status) to a Microsoft Excel file.
Import profile values (including status) of an elementary profile from a Microsoft Excel file.
The system performs predefined checks during the import process. You can define Consistency
Checks in Customizing.
You can display and edit profile values using all the standard Microsoft Excel functions, such as
graphics and macros.
You can also store data changed online in Microsoft Excel files.
OLE interface functions can be found under Utilities Industry -> Energy Data Management ->
Profile Management -> Profile Header.
You can use the functions described above if you have installed Microsoft Excel.
o
Internet Application Components

You can use the Internet Application Component EWEBIAC_PRODIS to display profile values.
However, you can only display profile values managed in IS-U.
Real-time-pricing (RTP) billing

RTP billing allows you to bill consumption measured at certain intervals (that is, load profiles) stored in
IS-U-EDM.
This means you can bill consumption measured in 15-minute intervals, for example. RTP billing allows
you to structure rates more freely, especially for nonresidential customers. As a result, you can control
billing more easily for:
-
Individual installations
This includes special agreements with a particular customer on the delivery of a fixed amount of
energy over a certain period (spot purchase agreement)
Groups of installations (rate-related)

This includes special price agreements for a group of customers for a limited time.
The advantage of RTP billing is that it allows you to bill much smaller units of time (such as 15-minute
intervals) that correspond to metering intervals.
You define the types of RTP billing that you want to use in Customizing under Define RTP Interfaces.
You must establish the following customizing settings before you can use the RTP interface:
-
Define the rates with a relevant usage type under Define Rates.
Define operands with usage type RTP under Define Operands.

The RTP interface allows you to model billing rules for nonresidential customers in an extremely
flexible fashion. You can override billing rules for a particular rate by modifying the installation
structure accordingly.
o
Modifications to the installation structure

During device installation and modification you can specify the length of metering intervals. You
cannot process interval meters using standard meter reading procedures.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
EDM functions can be customized in the implementation guide (IMG) under Energy Data Management . It
contains the following areas:
o
Basic Settings
Profile Management
Interface to External Systems
Interface to RTP billing
1.6.3 New: Internal Load Profiles Can Now Be Assigned to an Instal

Use
Previously: You could only assign external load profiles (whose values where not managed in IS-U) to an
installation.
Now: You can also assign internal load profiles (whose values are managed in the Energy Data
Management (IS-U-EDM) component) to an installation. Double-click on an internal load profile to
navigate directly to the Display Profile transaction.
You can assign a historical consumption factor to each load profile; the values of the corresponding load
profile are multiplied by this factor. The consumption factor is determined automatically for synthetic
profiles that are maintained in the IS-U-EDM component.
See also
For more information, see the Release Note Assigning Load Profiles to an Installation in section See also.
1.7 IS-U-BI
Contract Billing
1.7.1 Document Line Item Data Reduction

Use
Document line items from billing documents are now stored in a distributed manner in order to reduce the
data volume.
o
The line item fields are distributed among four tables. The fields are separated by semantic reasons,
which means that a line item is not necessarily written to all four tables.
Line items that are less important and are not archived (e.g. info line items for meter readings, general
calculation steps, and so on) are saved in parallel tables whose structure precisely corresponds to the
above four tables. The data in the parallel tables can be deleted after the invoice documents have been
archived.
Archiving is controlled through the line item type and through enhancement EBIA0001.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The separation into the new tables was implemented as follows:

o
DBERCHZ1: In addition to all the fields that are not contained in the other three structures, also
contains customer include CI_ERCHZ. This table is written to for every line item.
DBERCHZ2: Contains all the fields of the line item that involve device data.
DBERCHZ3: Contains all fields that involve amounts or price data.
DBERCHZ4: Contains all fields that are only rarely filled in the line items.
The parallel tables (with identical structure) are named DBERCHZ5 to DBERCHZ8.
The old line items are not affected by this new functionality. When line items are displayed, the new
structures are accessed first. If the line items are not present there, the old line items are accessed. Please note
that changes and new items are only saved in the new structures.
Table DBERCHZ has been replaced by eight tables: DBERCHZ1 through DBERCHZ4 and DBERCHZ5 to
DBERCHZ8. However, arhiving is only performed for tables DBERCHZ1 through DBERCHZ4 and for the
old table DBERCHZ. Table DBERCHZ will therefore become obsolete in the long term.
Check your modified and customer-specific programs and function modules to see whether they access or
reference the old table DBERCHZ. If so, either use the standard access modules or modify your programs to
use the new structures.
In Customizing for the Utilities industry component, you have to choose Tools -> System modification ->
Customer variant programs and set the NOT_ARCHIVE field for all the line item types that should not be
archived in the table for defining line item types.
1.7.2 New Features in Manual Billing

Use
The following new features are now available for creating the manual billing:
o
Previously, the individual net amounts were calculated automatically as soon as you pressed Continue.
You now select Start manual billing. The advantage of this approach is that no automatic proration
occurs when you navigate between the tab pages within manual billing.
The display of the individual areas in manual billing has been converted to tab pages.
You can now enter texts for a document in the Texts tab page. You can decide whether you want to
save the text for the current line item or for the document header. The first line of teh saved texts appear
in the overview table below the text field. Text lines in the document header are assigned to line item
"0". All other texts are saved under the line item for which they were entered. The texts can be printed
on the bill.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.7.3 Custom Data Output in the Document Display

Use
You can now display the customer include data from the billing tables in the Single line tab page. This is
made possible by the new Individual data tab page. The data is transported by function module
EXIT_SAPLEA23_001 (call for individual document display).
When enhancement EBIA0017 (enhancement for individual document display) is active, the Individual data
tab strip is displayed.
1.7.4 New: Table DBERCHT for Saving Individual Document Texts

Use
You can use the new table DBERCHT to enter individual texts for single documents.
In this release, document texts can only be maintained within manual billing or using the direct input module
for manual billing:
You can enter a text up to 100 characters in length in the Text field of the new table. Several document texts
can be saved for a line item. If you want to save a text for the document header, save it for line item "0";
otherwise, the corresponding line item is saved in the Line item field.
You can enter an identifier for bill printing in the text item field. For example, you can note where the
corresponding text should be printed. You can choose this identifier freely.
New levels have been created in the following form classes to print out the texts:
Bill:
is_u_bi_bill
Collective bill:
is_u_bi_collective_bill_new

Use
o

________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
example).
1.7.6 IS-U-BI-BD
Billing Master Data
1.7.6.1 New Variants in Billing

Use
The following new and modified variant programs are now available in billing:
o
BACKBI04: Update amounts in the periodic billing period
SETITLE02: Determine a rental price with the same price class
IF10: IF variant for billing operation
IF11: IF variant for billing period (e.g. current period, correction period, etc.)
Please read the documentation for the variants.
1.7.6.2 IS-U-BI-BD-RS
Rate Structure
1.7.6.2.1 New: Dynamic Period Control in Billing

Use
You can now flexibly backbill billing periods that are based on estimated meter reading results whenever an
actual meter reading is recorded. The preliminary billing documents are corrected during backbilling.
Because the recording of estimated or actual meter readings cannot be predicted, the billing module has to be
able to dynamically control the structure of the periods under analysis.
Several restrictions apply to the use of dynamic period control. For example, it may not be used together with
advance billing, budget billing payments, or floating backbilling/period-end billing.
The initial instantiation of dynamic period control is based on the interpretation of meter reading types
described above. Other instantiations are possible in the future. Changes to Customizing may result for this
reason.
More information is available in Customizing for the Utilities Industry under Information on dynamic period
control.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.7.6.2.2 New Functions in the Facts

Use
o
The following changes have been made to the Currency field in the installation/rate/rate category
facts :
When several currencies are entered in the price,
-
A symbol is now displayed in addition to the currency. The corresponding currencies are
displayed in the quick info for the symbol.
Previously, only one currency was displayed for each price
The following changes have been made to the installation facts:

-
When a transaction currency is entered in the contract account,

The price is now displayed in this currency.
Previously, the price was not displayed in this currency; instead, the currency that was entered
first in the price was always displayed.
When no transaction currency has been entered in the contract account, the price is displayed in
the currency specified for the company code.
Change documents are written in this release. You can display these documents in the installation
facts under Environment -> Change installation facts.
1.7.6.2.3 Gross Prices

Use
You can now bill using gross prices. To do this, create a gross price by selecting the new Gross price field in
price maintenance. You have to create the net components of the gross price individually (exception: the
franchise fee if you use the gross or max gross procedure - in this case, enter the net price including franchise
fee; the net energy price is calculated at runtime.
You define in the billing schema which net prices are grouped together with the gross price to form a gross
group. To do this, assign the variants that process these prices the same value of the corresponding prices in
the new "Gross group" field. You have to set the Gross line item field in the variant that processes the gross
price.
Notes on processing gross prices in invoicing are available in the following text.
1.7.6.2.4 New Features for Maintaining Rate and Billing Schema

Use
Several new features and improvements have been implemented in the maintenance of rate and billing
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
schema:
o
You can now create rates that are allowed for interval meters. You then enter an RTP interface instead
of register operands. You can use operands in which the RTP operand field is active in the rate steps.
These operands are supplied with values through the RTP interface. To achieve this, you have to assign
the number of a result parameter in the rate facts.
When you change a rate and save your changes, the system checks whether any blocked schemas that
use this rate exist. If so, a dialog box containing a list of the blocked billing schemas is displayed. From
this list, you can navigate to schema maintenance to cancel the block and modify the schema.
When you choose the Insert rate function when creating or changing a billing schema, the system now
displays a selection screen. This helps you avoid long rate selection lists.
You can now call a list of rates from the initial screens for maintaining rates and schemas.
If a schema contains one or more incomplete rates, the Update rates function is now offered.
Previously, this function only updated the selected rate. It now automatically updates all incomplete
rates.
You can change the sequence of rate steps in a rate that is already used in a schema. Previously, this had
no effect on the schema, to enable manual changes to the sequence in the schema.
In most cases, however, changes to the rate step sequence have to be copied to the involved schemas. If
the sequence in the rate differs from the sequence in the schema, a new function, Sort steps is now
available. When you start this function, the step sequence from the rate is copied to the schema. In
addition, if the sequences differ, a warning message is displayed when you check the schema.
The billing schema contains new fields for processing gross prices. More information on gross prices is
available here.
Dynamic period control can now be used in billing schemas. More information on dynamic billing
control is available here.
1.7.7 IS-U-BI-SF
1.7.7.1 IS-U-BI-SF-GA
Special Functions
Gas Billing
1.7.7.1.1 Calculation of Average with Lowest Calorific Value

Use
There is now a new way to calculate averages to determine the calorific value for billing. The lowest calorific
value in the billing period is used for billing. If the gas procedure or calorific district is changed, the lowest
value of each time slice is used.
To use this type of average calculation:
1.
Enter 03 (=lowest value) in field Type AvgCalc in Calorific Value Procedure
2.
Select field Average for the daily and monthly calorific values.
This type of average calculation is only possible for true calorific values.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.7.7.1.2 Enhancement of reading daily calorific values.

Use
You can now define daily calorific values in enhancement EBIA0016 (enhancement for determination of
billing calorific values) when you use either the customer calorific value or the vendor calorific value for
billing.
You can determine the calorific value differently than is defined in the calorific value procedure for several
days in the billing period without creating additional prorations. The calorific values determined in the
enhancement can be used for different types of average calculation.
When you activate this enhancement, you have to determine all the calorific values.
1.7.7.1.3 Saving the Volume Correction Factor in the Register

Use
You can now enter a volume correction factor in the register. To do this, a new special procedure, VC factor
from register, has been created in Customizing for the Utilities industry under Define Volume Correction
Factor Procedure.
When this special procedure is selected, the volume correction factor specified in the register is used for
billing. You can choose how the historical changes to the VC factor should be taken into account by
maintaining field Access VCfactor in the volume correction factor procedure accordingly. The entries for
determining temperatur, measured pressure, etc. are not taken into account in this special procedure.
If you specify a volume correction factor procedure with special procedure VC factor from register in the
gast procedure, you have to enter the volume correction factor during device installation. You can change the
volume correction factor later under Change rate data.
To use this function, you have to select the new special procedure in Customizing for the Utilities industry
under Define Volume Correction Factor Procedure.
1.7.8 IS-U-BI-PC
1.7.8.1 IS-U-BI-PC-AU
Billing Execution
Automatic Billing and Simulation
1.7.8.1.1 Manual MR monitoring via Collective Bill Account

Use
You can now use the Collective bill accounts field when making selections via the contract or business
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
partner in manual meter reading monitoring.

If you select the Collective bill accounts field, the system selects:
1.
All contract accounts for the selection made
2.
All collective bill accounts for these contract accounts
3.
All contracts found via the contract accounts of the collective accounts.
The system displays:

4.
Meter reading documents and billing documents for these contracts
You can also select the Billing order selec. field in Automatic Billing and Simulation to select billing
orders for collective bill accounts.
1.8 IS-U-IN
Invoicing
1.8.1 Define EDI transmission

Use
You can now determine whether to transmit print documents via Electronic Data Interchange (EDI).
To activate EDI transmission see the example under Financial Accounting -> Contract Accounts
Receivable and Payable -> Program Enhancements -> Define Customer-Specific Function
Modules in function module ISU_SAMPLE_R412 (Set IS-U Invoicing Pring Block/Transmit EDI).
Define a customer-specific function module for event R412 (Set IS-U Invoicing Pring Block/Transmit
EDI).
&SEE ALSO&
For further information see the function module documentation.
1.8.2 New methods for object PrintDoc

Use
There are two new methods available for business object PrintDoc:
o
You can create invoicing documents using method PrintDocument.Create.
You can display invoicing logs using method PrintDocument.InvoiceLogDisplay.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.8.3 Create joint consumption and partial bills

Use
You can now create joint consumption and partial bills. You can also invoice consumption bills together with
the creation of monthly partial bills.
To generate a joint bill, use transaction EA45 (create bill and partial bill together - single run) or EA46
(create bill and partial bill together - mass run).
When summarizing consumption and partial bills, the parameters youdefined in the contract for invoicing
contracts together, are taken into account. Only the consumption and partial bills that have different contracts
are summarized.
If several partial bills are created separately the consumption bills are only invoiced together with these
partial bills.
If there is only one type of bill (ie only consumption bills or only partial bills) the report then contains
Create bill or Create partial bill.
1.8.4 Stop bill printout

Use
You can stop the bill printout either long-term or temporarily, by using program enhancement R412.
Function module ISU_SAMPLE_R412 contains an example of this program enhancement.
You can remove a temporary print block if, beforehand you enter value 2 for parameter XY_PrintLock. To
remove the print block use transaction EA40 (display print document). Select Lift print block. You require
invoicing authorization.
Additional information is available in the function module documentation.
To define a customer-specific function module for event R412 in Customizing choose: Financial
Accounting -> Contract Accounts Receivable and Payable -> Program Enhancements -> Define
Customer-Specific Function Modules.
1.8.5 Debit entry from statistical items in invoicing

Use
You can now transfer statistical items, that were created with statistic key G, into the debit entry along with
the posting and document date of invoice creation. You can also transfer the corresponding combination of
business partner/contract account into the invoice. The due date and payment method are also transferred
from the corresponding invoicing into the debit entry.
The statistical items are cleared by debit entry.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
You can print the detailled information for the debit entry on the invoice.
If you reverse an invoice the debit entry is reversed too. The statistical items remain available.
You can define this additional invoicing functionality in Customizing.
Define this function under Define Control for Additional Invoicing Functions.
You can define the selection of statistical items to be used for debits under Item Selection in Account
Maintenance/ Define Sub-Items.
You create the document type for debit entry with the specification of the document type for invoicing.
Maintain debit entry transactions with the Define Account Assignments for Down Payments and Charges. At
the same time you must Define Accounts for Charges Receivable Revenue.
1.8.6 New event in invoicing for due date synchronization

Use
You can select which document items must have the same due date. Use program enhancement Contract
accounts receivable and payable to define report R411 (IS-U Invoicing: Selection of Items with Clearing
Number 8) as customer-specific, in table Template function module. Use this event to control which
contract A/R & A/P documents with clearing restriction 8 Items until next regular invoice cannot be
processed are to be synchronized with the invoice due date.
For further information see the function module documentation.
Define the customer-specific function module for event R411 in Customizing under Financial Accounting
-> Contract Accounts Receivable and Payable -> Program Enhancement -> Define
Customer-Specific Function Modules.
1.8.7 IS-U-IN-PC
Invoice Processing
1.8.7.1 Cash and Bill Accounting in England

Use
You can now determine a two-step tax determination code for contract accounts in England. The Tax
determination procedure field is displayed in the contract account. You use this field to determine whether
a contract account for bill accounting or cash accounting is involved.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The two-step determination is performed as follows:

1.
Determine the preliminary tax determination code in posting area R001
2.
Determine the final tax determination code, based on the preliminary tax determination code and the tax
determination procedure (bill/cash accounting) in posting area R008
Note: The sales tax code itself is determined based on the posting date and the final tax determination
code.
In comparison, "simple" tax determination involves the following steps:

1.
Determining the tax determination code in posting area R001
2.
Determining the tax determination code based on the posting date and the tax determination code from
posting area R001.
The following special features apply to the new tax determination procedure:
o
Cash accounting
Taxes are determined during invoicing based on the tax date type. If the tax has changed during the
billing period, amounts and consumptions are not prorated.
For more information, please refer to Release Note Changes to Tax Determination Time and Date Type.
Bill accounting
Taxes are determined during billing. If the tax has changed during the billing period, amounts and
consumptions are prorated.
1.
To maintain the tax date type for cash accounting, define the basic settings for invoicing.
2.
Activate the two-step determination of the tax determination code.
3.
Maintain the two-step determination of the tax determination code.
1.8.7.2 Document type assignment for contract accounts receivable an

documents in invoicing
Use
You can now define document types for contract A/R & A/P documents which
o
are a result of collective bill creation
are a result of creating bills and partial bills together
The assignment of document types for partial bills extends to:

o
Interest document type
Interest document type for cash security deposit
Document type for debit positions

The previous posting areas are no longer used. The document types are now managed in the following tables:
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
TE507_01 (Maintain assignment of document types for consumption billing)
TE507_03 (Maintain assignment of document types for partial bill)
TE507_04 (Maintain assignment of document types for bill reversal)
Conversion report ISU_XPRA_R400_TE507_BLART is proposed.

Define document types in Customizing for Financial Accounting by choosing: Contract Accounts
Receivable and Payable -> Basic Functions -> Postings and Documents -> Document -> Maintain
Document Assignments -> Document Types.
1.8.7.3 Checking the sort order for reversal of invoicing documents

Use
You can now define in Customizing whether the document sort order for the reversal of invoicing documents
needs to be checked.
If you activate the document sort order check, the system also checks whether the invoiced billing documents
also have subsequent documents, which have already been invoiced. An invoicing document can only be
reversed once all subsequent invoicing documents have been reversed.
The check must always be activated for payment plan procedures, since problems may arise when treating
the difference amounts.
To activate the sort order check choose Define Basic Settings for Reversal
1.8.7.4 Enhanced rounding functionality in invoicing

Use
If you want to administer rounding amounts in invoicing you must define the rounding rules for invoiced
amounts, independently of the rounding rules for contract accounts receivable and payable.
When invoicing occurs, you can now enhance business partner items and general ledger items, which are a
result of the rounding of invoiced amounts. A new event R409 is now available. You can use function
module ISU_SAMPLE_R409 (event R409: enhance rounding item) as a template.
If you want to enhance rounding items, define the customer-specific function module for event R409 Define
customer-specific function module.
You must also Define rounding rules for invoiced amount.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.8.7.5 Event for Tax Determination in Invoicing

Use
You can use the program enhancement for contract A/R and A/P to specify event R413 IS-U Invoicing: Tax
Determination for Billing Documents in table Function module template according to customer
requirements.
Function module ISU_SAMPLE_R413 contains a template for the program enhancement.
Function module ISU_DETMWSKZ_ITALY_R413 contains an example of how to use this functionality:
The billing lines refer to backbilling and corrections to provisional billing. The same tax that was determined
in provisional billing is used in the standard procedure. If you want to determine a more current tax, use the
above mentioned function module. In this case the tax information from previous bills is ignored.
For more information see the function module documentation.
You cannot allocate tax indicators to billing lines in tax determination in invoicing, which means that
changes to data storage are necessary. Tax indicators determined in invoicing are no longer defined in the
billing document, but in a reference table of print document lines for billing lines.
Conversion of the billing document lines is not necessary.
Define a customer-specific function module for event 413 in Customizing under Financial Accounting ->
Contract Accounts Receivable and Payable -> Program Enhancement -> Define Customer-Specific
Function Modules.
1.8.7.6 Changes to tax determination time and date type.

Use
You can enter the tax determination time and date separately for invoicing.
You can enter the contract billing date or invoicing date as the tax determination time. If you have defined an
alternative tax method in the contract account, the time of tax determination is already automatically defined.
In this case you must not enter data regarding the determination date in the basic settings for invoicing.
See the information regarding Cash-/bill accounting functionality in England.
In invoicing you must define the date category, on the basis of which tax determination takes place.
Up until now you had to define the time and date of tax determination for invoicing generally by entering a
fixed value as the date category.
Your previous Customizing data for tax determination is transferred using a conversion report.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
A conversion report is proposed to convert the previous Customizing data to the basic settings in invoicing.
You can define the tax determination time and date category for tax determination in invoicing in the basic
settings for invoicing.
1.8.8 IS-U-IN-BB
Budget Billing Plan
1.8.8.1 New Budget Billing Plan - Payment Schema

Use
You can now include the billing amount in the budget billing plan.
Alternatively you can use this function for montly billing. To do this select the Budget billing plan = 4 field
in the contract account.
A 12 month budget billing plan is generated. The dates are generated on the basis of the combinaton of the
meter reading unit and portion. Every 3 months interim meter readings are generated with billing.
Budget billing plans for this method are created in invoicing. You can not create budget billing plans
manually.
The maximum amount you can change the budget billing amounts to is the level of the billing portion.
This new budget billing procedure uses the installment plan as the data storage object.
To maintain the payment schema category in Customizing choose SAP Utilities -> Invoicing -> Budget
Billing Plan -> Define Control Parameters for Budget Billing Amount and maintain the field PS cat..
There is a new subtransaction for the payment schema (from the object installment plan).
You must create external transactions and allocate them to the internal transactions 0800 (main transaction)
and 0030 (subtransaction) in Financial Accounting in Customizing.
The extrapolation document (a downpayment request document) is provided with a separate internal
subtransaction 0090 (for the internal main transaction of the downpayment request 3000). Separate document
types are defined for the payment schema (from the object installment plan) and the down payment request.
1.8.8.2 Adjustment of budget billing plans to changed billing dates

Use
You can now adjust budget billing plans to changed billing dates.
To change the billing dates do one of the following:
o
Enter a portion in the contract
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Replace the meter reading unit in the installation
Change the portion in a meter reading unit. This change takes place in the schedule records.
In all instances you can adjust existing budget billing plans to new billing dates, using transaction EA65.
The existing budget billing plan is shortened to the date of the replacement. One or more budget billing plans
are generated, which contain the new end of billing period.
Changes to master data are taken into account, such as collective invoicing or an override of the budget
billing cycle.
You cannot reverse the transaction. It is possible to reverse the portion back, but the new budget billing plans
cannot be combined with the old budget billing plans.
1.8.8.3 Adjustment of individual budget billing plans

Use
You can now automatically adjust budget billing plans by using transaction E61M. This also applies for
individual budget billing plans.
1.8.8.4 Selective Release of the Payment Plan Balance-Forward Amount

Use
You can now define in the contract whether you want to release the balance-forward amount for a payment
plan with type BBP in the clearing month or not. You can define this separately in the payment plan data of
the contract depending on whether a credit or a receivable is involved.
By default, neither of the two new fields are filled, which means the balance-forward amount is released in
the clearing month. Therefore, when you upgrade to IS-U/CCS 4.62, nothing changes in the processing of the
balance-forward amount.
1.8.8.5 Changes and New Features in the Payment Plan

Use
The following changes and new features have been activated in the payment plan:
o
Changed determination of the date of the starting and ending period

-
Starting date
Now: The date is set to the first day of the starting month.
Previously: The date was set to the last day of the month preceeding the starting month.
Ending date
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Now: The date is set to the last day of the ending month.
Previously: The date was set to the last due date in the ending month.
o
New field Starting year when creating the payment plan

You can enter the starting year in addition to the starting month. This means you can create payment
plans that start in the past. Please note the following, however:
-
Before you define a starting date with month/year, a move-in must already exist. Please note that
the starting date of a payment plan is always the first day of the starting month.
No invoiced billing documents may exist as of the starting date. If they do, the system
automatically proposes the next possible starting date.
Separate transactions for changing and displaying the payment plan

-
Transaction EK93 is now available for changing payment plans and EK94 for displaying. These
transactions have been added to the invoicing menu and replace the former transactions.
Previously, you could only change (EA62) and display (EA63) payment plans through the budget
billing plan.
Menu enhancements for the payment plan

You can now navigate back and forth between the functions create, change, display, and manual
history.
1.8.8.6 New Features in the Manual History of the Payment Plan

Use
The following new features are now available:
o
The differentiation between creating, changing, and displaying has been eliminated. The fields are now
always ready for input.
The first time you create a manual history for a contract, you can choose whether you want to calculate
the history from the monthly gross amounts (like before) or from consumption values (new).
You only have to enter the currency and consumption unit in the header data. Previously, you had to
enter this information for each item.
If the same gross amount or consumption valie applies to the individual periods of an interval, you can
create all this data at once.
You can change and delete the data for several periods at once.
To use a manual history as a template, set field History as template in the initial screen.
This enables you to create example history data for certain customer categories. You can copy this data
to the manual history of a contract later. The data is saved in a separate table.
When you create/change the manual history for a contract, you can copy the data from other histories
and from templates.

The history for a contract has to consist either entirely of monthly gross amounts or entirely of consumption
values.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
If you have a contract with a history consisting of monthly gross amounts and you want to create a history
consisting of consumption values, you have to delete the monthly gross amounts first.
1.9 IS-U-CA
Contract Accounts Receivable and Pay
1.9.1 Legal Tax Reporting for Argentina

Use
Customizing for the Utilities Industry solution now contains the area "Legal Tax Reporting for Argentina".
Previously this area was located under Financial Accounting -> Contract Accounts Receivable and
Payable.
More information is available in Customizing for the Utilities industry solution, under Legal Tax Reporting
for Argentina
1.9.2 Changes to Submitting Receivables to External Collection Age

Use
Incoming Collection Agency Information
Once an external collections agency has fulfilled a collection order, it informs the client either by telephone,
in writing, or in a file, which amounts it was able to collect in full, and which amounts it was unable to
collect at all, or only partially. The form in which the information is forwarded to the client determines which
procedure then applies.
o
Information submitted in the form of a collections agency file:

The collections agency provides information on outstanding debts in the form of a file that is read by
program RFKKCOPM. When the system reads the payment information contained in the file, it
checks which items are included in the amount: collected and non-collected payments, as well as
interest and charges which the company has billed to the customer. If interest and charges are included,
the system posts them as interest and charges requests.
To post the collected payments, program RFKKCOPM creates a file which creates a payment lot.
You then execute the payment lot transfer program and post the payment lot.
Information given by letter or telephone:

The collections agency provides information on outstanding debts either in writing or by telephone. If
the collected payments include interest and charges, you firstly post these manually as interest and
charges requests. Using transaction Payment advice note from collections agency you then create a
payment advice note. When you receive the payment, you use the payment advice number to select the
items to be cleared from the payment lot.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Manual Flagging for Collection Order

This transaction allows you to flag individual outstanding items of a business partner for inclusion in a
collection order.
First of all you select open items by specifying the business partner, contract accounts, documents or net due
dates. You get a list of the items meeting your selection criteria. Then you select the items you want to
include in a collection order, and submit these to the external collections agency.
1.9.3 Cash and Bill Accounting in England

Use
You can now determine a two-step tax determination code for contract accounts in England. The Tax
determination procedure field is displayed in the contract account. You use this field to determine whether
a contract account for bill accounting or cash accounting is involved.
The two-step determination is performed as follows:
1.
Determine the preliminary tax determination code in posting area R001
2.
Determine the final tax determination code, based on the preliminary tax determination code and the tax
determination procedure (bill/cash accounting) in posting area R008
Note: The sales tax code itself is determined based on the posting date and the final tax determination
code.
In comparison, "simple" tax determination involves the following steps:

1.
Determining the tax determination code in posting area R001
2.
Determining the tax determination code based on the posting date and the tax determination code from
posting area R001.
The following special features apply to the new tax determination procedure:
o
Cash accounting
Taxes are determined during invoicing based on the tax date type. If the tax has changed during the
billing period, amounts and consumptions are not prorated.
For more information, please refer to Release Note Changes to Tax Determination Time and Date Type.
Bill accounting
Taxes are determined during billing. If the tax has changed during the billing period, amounts and
consumptions are prorated.
1.
To maintain the tax date type for cash accounting, define the basic settings for invoicing.
2.
Activate the two-step determination of the tax determination code.
3.
Maintain the two-step determination of the tax determination code.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.9.4 Changes in Correspondence for Security Deposits

Use
Form level ITEM has been replaced by form level ITEMS in the form class for security deposits
(IS_U_CA_SECURITY_DEPOSIT). As a result, several requests for security deposits are now possible for a
single security deposit.
1.
Check whether you use user exits for the old form level ITEM.
If so, copy your source text to another name in the customer namespace.
2.
Generate the application forms for form class "Security deposits" again.
3.
Add a new user exit to the new form level ITEMS and insert the source text you copied above into the
new user exit.
1.9.5 Changes in Archiving

Use
1.9.6 Changes in Authorization Management

Use
Authorization Assignment for Functions in Master Data Maintenance
Release 4.62 includes authorization object F_KK_FCODE. You can use this authorization object to assign
authorizations for master data dialog (such as contract account dialog).
For example, you might want to stipulate that certain users are not permitted to assign any other partners to a
contract account in the transaction Change contract account .
The authorization check is not activated until you select transaction CAS7 and enter function module
VKK_FICA_AUTH_EVENT_DCUAC provided by SAP.
Proceed as follows:
1.
Call transaction CAS7 .
2.
Mark event DCUAC and double-click on Assign event-> Function module.
3.
Choose New entries.
Enter a number in the customer namespace (such as 1000010).
4.
Enter the name of the function module - VKK_FICA_AUTH_EVENT_DCUAC.
5.
Under "call" enter X, and under "application" enter VKK .
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
6.
Save the new entry.
Authorization Assignment for Functions in Check Management

As from Release 4.62 you can use authorization object F_KKCR_BUK to protect the following activities in
check management:
01
02
03
06
85
Add or create checks

Change checks
Display checks
Delete checks
Cancel assignments for payment run
1.9.7 Changes in the Account Balance Display

Use
Account Balance from the Archive
You can now display items from the archive in the account balance display.
From the account balance display initial screen, select the With archive parameter under Further
selections.
In order to output archived items in the display, you must choose a line layout variant that contains the
Archived items (XARCH) field.
Navigating the Account Balance

The division of the navigation block into two columns, partner/account (left) and account/partner (right) does
not take place in the account balance. Instead there is now a wider left section. This allows you to output the
full length of the account name.
Note for Insurance Industry Component
The contracts (insurance objects) for the partner are now displayed in the navigation block for the account
balance instead of the accounts for the partner. The contract number and the name are output here as
standard. You can realize the output of further contract data (locks and payment methods, for example) by
using the new event 1214.
Display/Change Settings
You can now make all user-specific settings (SPA/GPA parameters) for the account balance display using
the menu path Settings -> Change/display. This function is active on the initial screen as well as from the
list. When you save the entries in the settings dialog box, these are updated in the user master data.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Send Payment Form

You can now provide the customer with a payment form by following Environment -> Send payment
form.
This means that the payment form correspondence (correspondence type 0022) is created.
A dialog box appears in which you can also specifically alter the amount. As standard, the total amounts for
the displayed items are filled in the amount field.
You can also levy charges on the customer for sending the correspondence.
When printing, you can output all displayed items individually or in total.
Account Balance Roles

Account balance roles are now available in the initial screen for account balance. This is an extension of the
master data selection.
Example
Prerequisite
Define the group parent account balance role. In the system settings for contract accounts receivable and
payable for the appropriate account balance role, define a function module to determine all group
subsidiaries.
Result
If you only specify one business partner and no account balance role on the initial screen for account balance,
all items for this business partner are displayed.
However, if you specify the business partner and the account balance role (group parent, for example), all
items for the group subisidiaries are also displayed.
If no account balance role is defined in the system, this field is not shown on the initial screen.
The delivery of account balance roles takes place per industry sector. However, you can expand this delivery
by using installation-specific account balance roles.
Define account balance roles in the IMG for contract accounts receivable and payable under Basic
Functions -> Account Balance Display -> Define Account Balance Roles.
1.9.8 New BAPIs

Use
BAPI: FI-CA Reconciliation Key
Release 4.62 includes a new BAPI for business object CTRACRECKEY for processing reconciliation keys.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
This BAPI enables you to create and close reconciliation keys when you are working in external systems.
The following methods are supported:
Create
Close
ExistenceCheck
GetDetail
GetList
criteria
- Create new reconciliation key

- Close existing reconciliation key
- Check existence of a reconciliation key
- Detailed data on a reconciliation key
- Creates a list of reconciliation keys that fulfil the given
BAPI: FI-CA Contract Account

The following methods of business object CtrAcContractAccount have changed:
Create
Change
GetList
Create contract account

Change contract account
Get a list
1.9.9 Changes to Payment at Cash Desk

Use
Managing Postings to Cash Desk
You can now define the cash desk structure for your company in the master data. By using the cash desk
structure, the movement data produced when posting with the cash desk can be updated. The cash desk
structure also evaluates the postings to the cash desks and makes further postings available for evaluation.
These include deposits, withdrawals, opening balances and differences.
Master Data
You can define multiple offices in the cash desk structure. You can assign multiple cash desks to these
offices.
Movement Data
The movement data includes the information that can be evaluated, which is produced by postings at the cash
desks, by opening balances or by closing balanceas when closing the cash desk. These postings are in the
Post withdrawals, Post deposits and Post difference categories.
Example
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
If an employee brings a certain amount from a cash desk to the bank in the course of a day, make a posting of
the category 'bank clearing account to cash desk'. The following data is then saved in the movement data:
Office
Cash desk number
Time of entry
Person making the entry
Currency
Document number belonging to the posting
The following functions are available:
All cash desks can be opened automatically by a user who has the appropriate authorization. The
following payment lots are created by the system for all cash desks for every posted currency:
-
Payment lot for cash desk
Check lot
Credit card lot
Postal remittance lot
The system proposes a cash desk for every clerk. The user has to make a choice if there are multiple
permitted cash desks.
The opening balance is determined automatically and updated in the movement data.
Posting deposits in (own) cash desk
Posting withdrawals from (own) cash desk
Posting cash desk differences
Postings of the category 'bank clearing account to cash desk'.

(incoming payments to bank accounts)
Closing the cash desks

The lots that are still open are closed automatically. Clerks can only
close their own cash desk. Administrator mode allows the closure of all
cash desks.
Determining the current cash desk balance (cash balances per currency)
Check balances, postal remittances
Historical evaluation of cash desk development
Submission of lots to another processing clerk

Only closed lots can change responsibility. This function is used if not every clerk has the authorization
for postings relevant to the general ledger. Responsibility for the items in the lot is passed to an
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
adminstrator (office manager, for example), who then makes the "Cash desk to bank clearing account"
posting when he is brings the money to the bank.
Dependent functions
The cash desk assigned to the clerk and further assignments determined by the system (or ones done
manually) are passed on to the cash desk.
Maintain the settings for the cash desk in the Contract Accounts Receivable and Payable IMG under:
Business Transactions -> Payments -> Incoming/Outgoing Payment Processing -> Cash Desk
Default Values for Posting Cash Desk Deposits and Withdrawals or Define Master Data for Cash
Journal.
1.9.10 Changes to Check Management

Use
Changes in Check Repository
The check repository has been enhanced in Release 4.62. Now you can:
o
Create checks
Search for checks
Change checks
Void checks
Delete checks
For example, you can search for checks by using the payment document number or the business partner.
From the hit list you can display one or several checks, or issue replacement checks. You can save the
overview and process this further outside of the R/3 system.
Deleted checks are transferred to a separate deletion table.
You can manually enter checks that have been cashed. A function module provides you with an interface for
mass processing of cashed checks, for instance via an electronic account statement.
Several data fields have been added to the check repository:
You can now enter the name and address of the person to whom the check was given.
When you need to void checks, you can state a voiding reason and set a reporting status. The reporting status
indicates whether the bank has to be notified that a check has been voided, or whether this notification has
already been made. If the voiding notification has been made, you can enter the appropriate date, and set the
status to already reported.
When checks are cashed, the reporting status Cashing is now saved in the check repository. This indicates
whether checks that have been issued have to be reported to the bank before they are cashed, or alternatively
when notification has to be made (positive payment).
You can evaluate the report status and pass on the information to your house bank in a corresponding file.
You can make the settings for the report status in bank-dependent Customizing for checks.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Creating additional payees is a new feature. The system can read this information as required, and print the
payees on the check (two-party checks).
As with mass creation of checks in the payment program, you can now use three different types of check
numbering in the check repository. Read the Numbering of checks section in the release information on
payments.
You can use the check number lot to guarantee unbroken internal number assignment with checks. Make the
required system settings for check number lots in the implementation guide for Contract Accounts
Receivable and Payable.
To transfer pre-numbered checks from a payment run to the check repository, use the function Transfer
checks from payment run. There you can assign the correct check number to the outgoing payments, and
transfer the check data to the check repository. You can also display and review payment runs that have
already been assigned.
With the new authorization object F_KKCR_BUK you can protect the following activities in the check
repository:
01
02
03
06
85

Change checks
Display checks
Delete checks
You maintain the report status for check creation, and defaults for check number lots, in the Implementation
Guide for Contract Accounts Receivable and Payable -> Business Transactions -> Payments ->
Incoming/Outgoing Payment Creation -> Settings for Check Creation.
1.9.11 Changes to Submitting Receivables to External Collection Age

Use
Incoming Collection Agency Information
Once an external collections agency has fulfilled a collection order, it informs the client either by telephone,
in writing, or in a file, which amounts it was able to collect in full, and which amounts it was unable to
collect at all, or only partially. The form in which the information is forwarded to the client determines which
procedure then applies.
o
Information submitted in the form of a collections agency file:

The collections agency provides information on outstanding debts in the form of a file that is read by
program RFKKCOPM. When the system reads the payment information contained in the file, it
checks which items are included in the amount: collected and non-collected payments, as well as
interest and charges which the company has billed to the customer. If interest and charges are included,
the system posts them as interest and charges requests.
To post the collected payments, program RFKKCOPM creates a file which creates a payment lot.
You then execute the payment lot transfer program and post the payment lot.
Information given by letter or telephone:
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The collections agency provides information on outstanding debts either in writing or by telephone. If
the collected payments include interest and charges, you firstly post these manually as interest and
charges requests. Using transaction Payment advice note from collections agency you then create a
payment advice note. When you receive the payment, you use the payment advice number to select the
items to be cleared from the payment lot.
Manual Flagging for Collection Order

This transaction allows you to flag individual outstanding items of a business partner for inclusion in a
collection order.
First of all you select open items by specifying the business partner, contract accounts, documents or net due
dates. You get a list of the items meeting your selection criteria. Then you select the items you want to
include in a collection order, and submit these to the external collections agency.
1.9.12 Changes to the Contract Account

Use
Authorization Assignment for Functions in Master Data Maintenance
Release 4.62 includes authorization object F_KK_FCODE. You can use this authorization object to assign
authorizations for master data dialog (such as contract account dialog).
For example, you might want to stipulate that certain users are not permitted to assign any other partners to a
contract account in the transaction Change contract account .
The authorization check is not activated until you select transaction CAS7 and enter function module
VKK_FICA_AUTH_EVENT_DCUAC provided by SAP.
Proceed as follows:
1.
Call transaction CAS7 .
2.
Mark event DCUAC and double-click on Assign event-> Function module.
3.
Choose New entries.
Enter a number in the customer namespace (such as 1000010).
4.
Enter the name of the function module - VKK_FICA_AUTH_EVENT_DCUAC.
5.
Under "call" enter X, and under "application" enter VKK .
6.
Save the new entry.
Authorization Assignment for Functions in Check Management

As from Release 4.62 you can use authorization object F_KKCR_BUK to protect the following activities in
check management:
01
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
02
03
06
85
Change checks
Display checks
Delete checks
1.9.13 Changes to Correspondence

Use
Inclusion of Time of Issue in the Balanced Account Statement
From Release 4.62, the time of issue will be taken into account during item selection between two account
statements, as well as the date of issue.
Previously, an account statement that was created on 07/19/2000 at 04:45, for example, included all items up
to 07/18/2000 at 23:59:59. This meant that items that had been created just before the run did not appear on
the account statement.
The new functionality allows you to take items into account that had clearly been posted before the account
statement was created.
Introducing Correspondence Roles
Correspondence roles enable:
o
The formation of the correspondence to be sent, according to the correspondence role
The determination of the recipient address type on the basis of the correspondence role
The correspondence roles can be specified in the master data along with the alternative or additional
recipients.
When you define a "copy recipient" correspondence role, for example, you can then:
o
Define a special application form for this correspondence type and this correspondence role in
Customizing for application forms, for example one that presents the data in a less detailed form and
also prints the "copy" text.
However, you can also use and application form that is valid for all roles. In this case, you can check
which correspondence role was created in the application form, as this is available in the
DFKKCOH-CORR_ROLE field.
Define an address type for every correspondence type and correspondence role in address type
Customizing.
You can now send the correspondence for the recipient of an account statement in the "initial recipient"
role to the address defined under the "initial recipient address" address type. In the same way, the
account statement in the "secondary recipient" role can be sent to the address from the "secondary
recipient address" address type.
New "four-weekly" Period in Correspondence Periods

Four-weekly periodicity has been introduced alongside the already existing correspondence periodicities.
This periodicity is intended to be used primarily in English-speaking areas.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Dunning Locks for Incoming Correspondence

You can set a dunning lock for incoming correspondence in the correspondence history.
This dunning lock is taken into account in the correspondence dunning run and can prevent a dunning notice
if necessary.
Displaying Correspondence History from the Archive
You can now set the Display from archive indicator in the correspondence history.
When you set the indicator, the correspondence that is already in a file for data archiving is displayed. See
also: Also display from data archive.
Periodical Correspondence Creation Possible in Simulation Mode
You can now set an indicator for the simulation run for correspondence creation runs for periodical
correspondence.
When you set the indicator, entries are created in the correspondence container that have an appropriate
characteristic.
When restarting the creation run, all correspondence is deleted from the simulation. This means that it is
possible to have a complete simulation for every correspondence creation, which also supports the actual
creation of the print product.
If the result is satisfactory, the creation run is executed once more without a simulation indicator.
Transaction Texts now Available in all Form Classes
A 1:1 level was introduced for hierarchy levels that represent line items in all form classes, to make the long
texts for the main and sub-transactions available for printing.
Language Determination in Correspondence
The correspondence language for the print product is now determined in event 0768.
Individual Correspondence Creation
Since Release 461 it has been possible to implement interactive individual creation for every correspondence
type.
These are based on the events:
o
0793
Single Correspondence: Data Assignment
0794
Single Correspondence: Input Check
0795
Single Correspondence: Creation Call
The OSS Note 194899 is used for implementation instructions.

In order to maintain correspondence types, go to Basic Functions -> Correspondence -> Define
Correspondence Types in the contract accounts receivable and payable IMG.
In order to maintain correspondence roles, go to Basic Functions -> Correspondence -> Define
Correspondence Roles in the contract accounts receivable and payable IMG.
In order to maintain address determination, go to Basic Functions -> Correspondence -> Configure
Address Determination in the contract accounts receivable and payable IMG.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.9.14 Changes in Creditworthiness

Use
Manually Updating the Creditworthiness Value
You can now manually update the creditworthiness value. This means that the creditworthiness value can no
longer change dependent on time, and no longer reduces itself.
This function makes sense if the customer has declared bankruptcy. The update can be released again
manually, and the creditworthiness is calculated just as before. As long as the update takes place
automatically when a certain dunning level is reached, there is one dunning activity available to you.
However, the release of the update always has to take place manually, even if the dunning notice is reversed.
No change is necessary in Customizing to manually update the creditworthiness value.
However, if the update is to be triggered by a dunning activity, a suitable dunning activity must be assigned
to a dunning level. (See also: Function module for the activity).
In order to maintain dunning activities, go to Business Transactions -> Dunning Notices -> Configure
Dunning Activities in the contract accounts receivable and payable IMG.
In order to maintain dunning procedures, go to Business Transactions -> Dunning Notices -> Configure
Dunning Procedures.
1.9.15 Changes to Doubtful Entries and Individual Value Adjustments

Use
Mass Run for Automatic Doubtful Entries and Individual Value Adjustments in Contract
Accounts Receivable and Payable
Previously, you could mark receivables as doubtful with a manual maintenance transaction, or make an value
adjustment with a certain percentage rate. One or more cumulated FI-CA transfer posting documents are
then created for the receivables that have been value adjusted. You now have the option of automatically
marking receivables as doubtful on the basis of their age and making an individual value adjustment.
The new Value adjust receivables according to age mass run for automatic doubtful entries and
individual value adjustments offers the following functionality:
o
You can use value adjustment variants to define the age from which a receivable is to be value adjusted
by a certain percentage rate.
The mass run can select open items as well as items that have already been value adjusted. This enables
you to enter a value adjustment manually and make the percentage rate for the value adjustment
dependent on the age of the receivable.
You can define customer-specific checks and exceptions by using an exit.
The mass run is realized as a mass activity and offers the option of parallel processing.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Maintain the following settings in the IMG under Contract Accounts Receivable and Payable ->
Business Transactions -> Dountful Entries and Individual Value Adjustments:
Maintain Value Adjustment Variants for Automatic Value Adjustments
Maintain Processing Methods for User Exits for Automatic Value Adjustments
Only for the Czech Republic and Slovakia

-
Maintain Variant Determination for Automatic Adjustments
Account Determination Individual Value for Accounting Value Adjustments
1.9.16 Changes to Dunning

Use
Reversing a Dunning Run
This function enables you to completely reverse a dunning run, or just to reverse the entries in a dunning
proposal for which the dunning activity run was not successful.
In order to specify a document type for the reversal of charges and interest, go to Business Transactions ->
Reversal -> Define Default Values for Reversal in the Contract Accounts Receivable and Payable IMG.
The document type you defined must be permitted for mass processing.
1.9.17 Changes to Events

Use
New Events
o
0105
Additional texts for OI processing
(see also: Function module documentation for FKK_SAMPLE_0105)
0140
Additional data for down payments and charges
(the I_FKKKO parameter is new here, see also: Function module documentation for FKK_SAMPLE_0140)
0150
Additional industry sector data for items from clearing reset
(see also: Changes to returns and the function module documentation for FKK_SAMPLE_0150)
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
0250
Data for returns
0259
Preliminary check on item to be processed
0768
Correspondence: Language determination
(see also: Correspondence language determination and the function module documentation for
FKK_SAMPLE_0768)
0793
Individual correspondence creation: Value assignments
(see also: Individual correspondence creation and the function module documenation for
FKK_SAMPLE_0793)
0794
Individual correspondence creation: Input checks
(see also: Individual correspondence creation and the function module documentation for
FKK_SAMPLE_0794)
0795
Individual correspondence creation: Call print module
(see also: Individual correspondence creation and the function module documentation for
FKK_SAMPLE_0795)
1124
Mass document change
(see also: Changes to postings and documents and the function module documentation for
FKK_SAMPLE_1124)
1125
Mass document change
(see also: Changes to postings and documents and the function module documentation for
FKK_SAMPLE_1125)
1214
Account balance - navigation - contracts list
(see also: Changes to the account balance display and the function module documentation for
FKK_SAMPLE_1214)
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
9550
Document journal - document output
(see also: Function module documentation for FKK_SAMPLE_9550).
2090
Interest calculation - checking tolerance days
1230
Account balance in the Workplace: Supplement data
Changed events
o
0295
Process contract account
1.9.18 Changes to the Implementation Guide for Contract Accounts Re and

Payable
Use
The following Customizing activities have been included in the Contract Accounts Receivable and Payable
IMG for the first time, or have been changed:
o
Basic Functions
-
Postings and Documents

New
You can define line layout variants for mass document changes.
Account Balance Display

New
You can now define roles for the account balance.
Correspondence
New
You can now define correspondence roles. You can also use the archive
information structure for the correspondence archive.
Business Transactions
-
Security Deposits
New
You can now assign withholding tax codes to main and sub-transactions when processing
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
incoming and outgoing payments.

-
Payments
New
When processing incoming and outgoing payments, you can now define default values for credit
card and payment order lots.
You can now also define master data for the cash journal and accounts for posting cash desk
deposits and withdrawals. These activities have been grouped with both of the activities already
available (Maintain cash desk specifications and Define accounts for expense/revenue
cash desk differences) in the chapter entitled Cash desk.
You can now define instruction keys for the execution of payment orders for banks when creating
incoming and outgoing payments.
You can also define parameters for foreign payment transactions with the DTAZV payment
medium format. You can also make settings for check creation and check and change number
ranges for payment orders.
You can now also define payment release workflows for main and sub-transactions and for
repayments.
You can define value adjustment variants for automatic adjustments and
processing methods for user exits for automatic adjustments, for
doubtful entries and individual value adjustments.
Changed
The Define clearing account for person presenting check activity has been renamed to
Define clearing account for incoming checks.
Returns
The Configure screen variants for returns lot activity has been deleted.
Data transfer
New
As part of data transfer, you can now generate your own transfer structures for transferring documents,
payment and returns lots. You can also compare your own existing structures with those delivered by
SAP.
Program Enhancements
New
You can now define user IDs for bank transactions here.
Changed
The Define formats activity has been renamed to Define payment medium formats.
Country-specific Customizing
-
Write-offs
For the Czech Republic and Slovakia, you can define automatic general ledger account
determination and percentage rates for writing off value adjusted receivables.
Doubtful entries and individual value adjustments

You can also define account determination for accounting adjustments and variant determination
for automatic adjustments, when marking receivables as doubtful and making individual value
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
adjustments.
1.9.19 Changes to Deferral and Installment Plan

Use
Distribution of Interest and Charges to Installment Plan Due Dates
Interest and charges are now distributed to all due dates in installment plans.
1.9.20 International Developments

Use
PORTUGAL
Interest Calculation: Tolerance Days
If the due date for an item falls on a public holiday, the interest is calculated as follows:
o
If payment is made on the day following the public holiday, no interest is calculated.
If payment is made two or more days after the public holiday, interest is calculated for the items as if
the due date has fallen on a working day.
You can use event 2090 to check how many days after the public holiday the receivables were paid.
Minimum Amount for Interest Calculation

When calculating interest on overdue items, you can specify a minimum amount for the interest to be posted,
in connection with the amount of time to the due date. This function is used in Portugal.
The following Customizing settings are possible:
Amount of time to due date
Minimum amount
up to 8 days
9 days or more
1000 ESP
1500 ESP
Posting example
Interest calculated
600 ESP (6 days after due date)
Interest and any

minimum amount
1000 ESP posted
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________

1500 ESP posted

1700 ESP posted
UNITED KINGDOM
Tax Report for Clearing Date
From Release 4.62 you can use the report RFKKTAXCUM_UK to output a list of sales/purchase tax
amounts, according to the company code and tax code.
ITALY
Tax Exemptions
You can make an evaluation of tax exemptions that expire on a key date per contract account, by using the
Evaluate tax exemption end mass activity.
Correspondence is created per contract account if the tax exemption expires.
Define the specifications for the minimum amounts for interest calculation in the Contract Accounts
Receivable and Payable IMG: Business Transactions -> Interest Calculation -> Item Interest
Calculation -> Define Interest Calculation Rules.
1.9.21 Changes to Integration with Other Components

Use
Transferring Invoices from to Contract Accounts Receivable and Payable from Sales
It is now possible to transfer invoices from Sales (SD) to Contract Accounts Receivable and Payable (FI-CA)
instead of to SAP Accounts Receivable (FI-AR) for the IS-U/CCS, IS-T and IS-PS-CA industry solutions.
Scope of functions for the interface between SD and FI-CA:
o
You can find a general description in the Release Information for Release 1.1B;
You can find extended information in the Release Information for Release 1.2, in the Release
Information for Release 4.51, and in the Release Information for Release 4.61
The changes for Release 4.62 are described in this Release Information.
You can find current enhancements for this Release Information in the OSS Note no. 316164.
New Reversal Procedure for SD Invoices

The new reversal procedure for SD invoices, which has existed in the standard release since Release 4.61, is
now supported when transferring SD invoices to FI-CA. You can find a general description of this function
in the Release Information entitled New reversal procedure.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
When transferring the reversal invoice to financial accounting, the acounting document produced is marked
as reversed and the open items are cleared immediately. If the new procedure cannot be executed, an
accounting document with a reversed +/- symbol is then produced. This can be the case if the invoice has
already been cleared, or if the payment order has already been created for the invoice.
No Reversal of the SD Invoice in the Case of Receivable Transfer (Subrogation)

If the receivables (open items) are transferred when there is a change of customer, the SD invoice can no
longer be reversed after this point. The reversal of the invoice is refused as the open item(s) were cleared in
contract accounts receivable and payable with the reason "21" - receivable transfer (subrogation) .
If you want to transfer SD invoices to Contract Accounts Receivable and Payable, you must make some
settings in the Contract Accounts Receivable and Payable IMG (see IMG structure: Contract Accounts
Receivable and Payable -> Integration -> Sales).
1.9.22 Changes to Interest Calculation

Use
Minimum Amount for Interest Calculation
When calculating interest on overdue items, you can specify a minimum amount for the interest to be posted,
in connection with the amount of time to the due date. This function is used in Portugal.
The following Customizing settings are possible:
Amount of time to due date
Minimum amount
up to 8 days
9 days or more
1000 ESP
1500 ESP
Posting example
Interest calculated
Interest and any

minimum amount
1000 ESP posted
1500 ESP posted
1700 ESP posted
Define the specifications for the minimum amounts for interest calculation in the Contract Accounts
Receivable and Payable IMG: Business Transactions -> Interest Calculation -> Item Interest
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Calculation -> Define Interest Calculation Rules.
1.9.23 Changes to Job Control

Use
Linking standard reports to the job container
From Release 4.62 you can link any standard report to the job container in Contract Accounts Receivable and
Payable.
This has already been done for payment and returns lots.
1.9.24 Changes to Mass Activities

Use
Refreshing distribution intervals
When refreshing distribution intervals, you can now distinguish between the size and number of intervals.
Up to now, a distribution variant was created either by giving the interval size or the required number of
intervals. When refreshing these distribution variants however, the existing number of objects was
distributed among intervals in such a way that the number of intervals remained the same. With a large
increase in basic data, this lead to an increase in the runtime for each interval. In contrast to this, with only a
small amount of basic data, the number of intervals was reduced.
From this Release, when it refreshes the distribution variant, the system will check how the variant was
created. If the number of objects for each interval was defined, the system will take this into account after
refreshing. The system will also reset the number of intervals after the refresh.
1.9.25 Changes to Open Item Management

Use
Processing open items at clearing
From Release 4.62 open items are displayed in table control. Display with a HTML GUI (using the browser)
is also possible.
The function keys have been arranged underneath the table with the selected open items.
When you are searching for certain open items, the items that fulfill the search criteria are displayed at the
top of the list and flagged with an icon in the column filter.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.9.26 Changes in Payment Processing

Use
Reopen Clarification Cases with Incoming Payment
In the following cases a new clarification case is automatically created for incoming payments, or the amount
requiring clarification in an existing clarification case is changed:
o
complete or partial reset of clearing for an incoming payment document that was posted via a payment
lot or a check lot
reversal of a clarification document or partial clarification document for an incoming payment
reversal of the payment document if the payment purpose was posted directly without clarification, and
a suitable procedure is selected in the cancellation transaction
When you reset a clearing, you must select the option Clearing amount to clarification account in the
Posting the clearing amount transaction on the entry screen.
If you want to reverse a payment document, select the Post function and a dialog window appears. Here you
can choose between Reverse payment document and Transfer post to clarification account .
Dependencies
If you create a clarification case for a payment lot that has already been closed, the status changes again to
Postprocessing required.
If you have defined a corresponding function module (such as FKK_SAMPLE_0241) at event 0241, a new
reconciliation key is assigned and opened automatically.
Processing Help in Incoming Payment Clarification

The system offers you support when you are trying to clarify incoming payments. For example, if a customer
has stated an incorrect number in the note to payee, you can use the new search function Find similar. The
system supports a search for the following numbers:
o
Customer number
Account number
Contract number
Document number
The search function operates as follows:

If you choose the Find similar function, the system first evaluates the cursor position. If you have positioned
the cursor in the Selection proposals area, the corresponding field value is adopted for the search, and the
object you are looking for (customer, contract account, contract, or document) is set on the basis of the
cursor position.
If the cursor is in the Usage text field, the term selected is used for the search.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Example (parentheses denote the cursor position)

Payment 4711-58(1)2 for March 2000
The value 4711-5812 is taken for the search. The settings of the previous search call are used for the object
that you are looking for now.
The system searches for similar objects. An object is regarded as being similar to the value you are looking
for if one of the following conditions is fulfilled:
o
The customer stated one digit more (example 4711-5812 instead of 471-5812)
The customer stated one digit less (example 4711-5812 instead of 4711A-5812)
The customer stated one incorrect digit (example 4711-5812 instead of 4712-5812)
The customer mixed up two digits (example 4711-5812 instead of 4711-8512)
When the system finds objects, it reads the names of the relevant business partners, and compares them with
the name of the person who placed the payment order. The hits with the greatest concordance are displayed.
You can transfer them to the selection proposal.
Credit Card Lot

You can now create lots for credit card payments either manually or via an interface. To date you could only
create such lots from the cash desk.
Several modes for payment processing are supported. You can find further details in the online help for the
corresponding field in the credit card lot header.
Acute Clarification Cases in Incoming Payment Clarification
In the selection screen for incoming payment clarification, you can now use the function Only acute
clarification cases. The system only calls up those clarification cases that need to be processed
immediately.
You can specify the criteria for the urgency of a clarification case in the system settings (for example, all
unallocated incoming payments with an amount exceeding 10,000 $).
The mySAP.com Workplace provides you with a mini application for displaying acute clarification cases.
When you log on, you are given an overview of the acute clarification cases. You can go directly from this
mini application to the clarification worklist for acute clarification cases.
Check Lot without Check Deposit Posting

In the header of a check lot you can give the instruction that no posting should be made for the total amount
of the lot for check deposit. In this case, you must specify the check clearing account in the header of the lot,
and not the check deposit account.
You can find further information in the online help for the new field Without posting for check deposit.
Payment Lot
In the payment lot you now have a search and sort function in the list view. This function is also available in
the returns lot.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Payment Lot Transfer

The format for transferring payment lots from a file has been changed. The header structure contains the
following new fields:
payment card lot (BFKKZK-XCRDS)
lot for payment orders (BFKKZK-XZAUS)
processing card payments (BFKKZK-CCZAH)
The item structure has the following new fields:
payment card type (BFKKZP-CCINS)
payment cards: card number (BFKKZP-CCNUM)
It is no longer necessary to state the version in the structure. Customer structures ZFKKZ* are now
supported for the different versions of transfer structures BFKKZ*. Report RFKKZEZG generates the
ZFKKZ* structures.
You can now use the payment lot transfer program to transfer check lots as well.
Returns Lot Transfer

It is no longer necessary to state the version in the header data of the transfer file. Customer structures
ZFKKR* are now supported for the different versions of transfer structures BFKKR*.
Report RFKKZERG generates the ZFKKR* structures.
Workflow for Releasing Repayments

You now have a release workflow for repayments. To create your own workflow you can use sample
workflow WS21000084.
Repayments that are defined in Customizing as being subject to approval will only be disbursed by the
payment program if the workflow for repayments has deleted the disbursement lock.
Check Lot Without Check Deposit Posting
In posting area 1031 (specifications for check lot) you can define a proposal value for the new field Without
posting for check deposit.
Maintain the instruction keys for banks in the Implementation Guide for Contract Accounts Receivable
and Payable -> Business Transactions -> Payments -> Incoming/Outgoing Payment Creation ->
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Define Instruction Keys.

Define User IDs for bank transactions in the Implementation Guide for Contract Accounts Receivable and
Payable under Program Enhancements -> Define User IDs for Bank Transactions.
Define specifications for Check number assignment and Check forms in the Implementation Guide for
Contract Accounts Receivable and Payable -> Business Transactions -> Payments ->
Incoming/Outgoing Payment Creation -> Settings for Check Creation.
If you want a clarification case to be displayed as being acute in the Clarification worklist, you have to
define a workflow role with responsibilities.
1.
Create a workflow role with responsbilities with regard to the fields of DDIC structure
FKKCFZST_DISPL.
2.
Enter this workflow role in the Implementation Guide for Contract Accounts Receivable and Payable
unter Technical Settings -> Prepare Processing of Clarification Worklist. Double-click on PLOT.
3.
In the Display acute clarification cases frame, enter the ID of the role and set the Active flag.
1.9.27 Changes to the Payment Program

Use
Payment orders
Payment orders are new in automatic payment business. As part of the debit memo procedure and for
transfers, the payment program creates a payment order instead of posting a payment document. A payment
order is created when the payment is made but the posting is only to be made in the system when the
payment appears on the account statement of the house bank. In this case, payment notification is created and
the transfer order sent to the bank by DME.
Between the time the payment run is executed and the account statement is processed, all the items in a
payment order are flagged. This means that payment is not carried out by a new payment run. These items
cannot be subject to other clearing transactions, such as reversal, dunning and interest calculations on
overdue payments, during this time.
Each payment order automatically receives a number that is unique to the client. Payment orders consist of
header data and line item data. The header contains information on the posting area making the payment, the
payment amount, method, the house bank account and other payment-related data. A separate record is
created in the item data for each line item that has been paid. This contains the gross amount, cash discount
deduction, withholding tax amount and the line item key.
The number of the payment order is on the payment form or in the data medium. This number takes the place
of the document number of the payment document, which is filled by the payment program immediately
when the payment is posted.
The number of the payment order also appears on the house bank's account statement. This allows you to
select the paid items quickly and easily from the payment order. The payment orders in the statement are
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
collected in a payment order lot. This is like a payment lot (for example, for incoming transfers) and it can
be created automatically or manually.
Each payment order executed creates a new item in the payment order lot. Each item contains the payment
amount and the number of the payment order.
Payment orders offer the following advantages:

o
With foreign currency payments you can use the bank's conversion rate for posting. When posting with
the payment program, however, the rates defined in Customizing are used. When the account statement
is posted subsequently, and the incoming and outgoing accounts are cleared, rate difference postings are
usually generated.
If the date a payment order is executed lies in the future, the items will be cleared only when the
payment has been made. This gives you an exact list of open items at the key date.
If taxes are to be deducted at payment, the tax report is done once the payment has been posted by the
bank, and no longer at the time of the payment run.
Payments according to due date

With one payment for each due date, you can guarantee, as part of data medium exchange, that items with
different due dates are settled on a particular due date. However, only those items with the same due date are
paid together.
In the company-code-specific system settings for the payment method, you can define that only one payment
per due date is to be made for the items.
The common due date of the items to be paid is stored in the header record of the payment. A reference can
be made to this date in the payment medium printout and in the data medium exchange. This allows you, for
example, give your house bank an individual execution date for each payment.
If the total of items to be paid form a credit balance, requiring an outgoing payment, the items involved will
be added to the next due date.
Example
Invoice
1000
Credit memo
500
Invoice
200
Invoice
700
due
due
due
due
10.02.2000
11.02.2000
11.02.2000
12.02.2000
Grouping according to due date would give the following result:

10.02.2000 balance
11.02.2000 balance
12.02.2000 balance
1000
300700
can be paid
cannot be paid
can be paid
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
In this case, the items from 11.02.2000 are added to 12.02.2000, with the following results:
10.02.2000 balance
12.02.2000 balance
1000
400
can be paid
can be paid
Cross-business-partner payment
For a contract account, you have always been able to give an alternative paying contract account, but from
the same business partner (FKKVKP-VKONV). This means that open items from both accounts can be
paid together.
Now, in addition to entering the paying contract account, you can also enter the paying business partner. This
means that the open items in the relevant account/partner are paid in one payment.
Example
Partner
Son
Daughter
Father
account
V-SON
V-DAUGHTER
V-FATHER
paid through partner/account

FATHER
V-FATHER
FATHER
V-FATHER
This means that open items from the business partners SON and DAUGHTER are taken together with the
open items of the business partner FATHER, using the payment method defined in the account V-FATHER.
Therefore, there is only one direct debit from account V-FATHER.
In such case, the payment data of business partner V-FATHER also applies to payment of items on the
V-SON and V-DAUGHTER accounts.
Locks on the V-FATHER account affect items on the V-SON and V-DAUGHTER accounts. Locks on the
account V-SON only affect that account, and not V-DAUGHTER or V-FATHER.
Common payment only takes place if the parallel processing object of the payment run is the business
partner.
The payment run skips the items of accounts V-SON and V-DAUGHTER. These are not shown in the log.
The items of V-SON and V-DAUGHTER are read and paid only when the items of account V-FATHER are
processed.
Therefore the items of accounts V-SON and V-DAUGHTER are not paid if the payment run does not select
business partner FATHER.
Payment Medium Format ETEBAC
Release 4.62 provides you with the French payment medium format ETEBAC in Contract Accounts
Receivable and Payable.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Instruction Key
In the Implementation Guide for Contract Accounts Receivable and Payable you can now define instruction
keys to provide banks with instructions on how to execute payment orders.
You can make the values in Financial Accounting table T045W available in Contract Accounts Receivable
and Payable.
User ID for Bank Transactions
In Release 4.62 it is possible to define user IDs for conducting payment transactions by way of data medium
exchange.
User IDs are assigned by the house banks so that the bank can identify the person presenting the data
medium.
To date the system read these values from Financial Accounting tables. If you make the appropriate
specifications in the Implementation Guide for Contract Accounts Receivable and Payable, these values can
now be transferred to Contract Accounts Receivable and Payable, thus guaranteeing data consistency.
Numbering of Checks
There are three different methods for numbering checks:
1.
automatic assignment
2.
internal assignment with sequence numbers
3.
external number assignment
Automatic check number assignment is the procedure used to date, in which the document number is used as
the check number.
Internal check number assignment ensures that check numbers are assigned in sequential order.
External number assignment is for checks whose numbers have been passed on to you by the bank. The
check repository makes these numbers known to the system.
You can make the corresponding specifications for check number lots in the Implementation Guide for
Contract Accounts Receivable and Payable.
Settings for Check Printing

In the Implementation Guide for Contract Accounts Receivable and Payable you can now define a dedicated
check form for each house bank account, instead of just having one form for all accounts.

The standard system delivery provides you with 10 default number ranges with local buffer that you can use
for payment orders. These number ranges enable smooth parallel processing of payment runs.
No. range
00
Interval
0000000001 - 09999999999
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
01
.
.
.
09
1000000000 - 19999999999
9000000000 - 99999999999
You only need to intervene manually if the default settings for these number ranges are incorrect in any way,
or if you want to increase the amount of number ranges to satisfy high parallel-processing requirements. In
such cases, you can process number ranges in the Implementation Guide for Contract Accounts Receivable
and Payable -> Business Transactions -> Payments -> Incoming/Outgoing Payment Creation -> Check
Number Ranges for Payment Orders.
You can decide for each payment method whether a payment order is to be created. The relevant payment
method indicators are set in the country-specific data (see the IMG for Contract Accounts Receivable and
Payable -> Business Transactions -> Payments -> Incoming/Outgoing Payment Creation -> Define Payment
Methods.
In order to be able to select according to the number of a payment order in the payment order lot, you must
define a selection criterion that refers to the payment order (PYORD).
You can define default values for a payment order lot posting in posting area 1031 (Contract Accounts
Receivable and Payable IMG -> Business Transactions -> Payments -> Incoming/Outgoing Payment
Processing -> Define Default Values for Payment Order Lots ).
If you wish to define that there should be only one payment per due date for the item to be paid, choose the
following path: Contract Accounts Receivable and Payable -> Business Transactions -> Payments
-> Incoming/Outgoing Payment Creation -> Define Specifications for Responsible Company Code
Changes in Procedure
Creation of Payment Orders
Creation of payment orders is conducted automatically by the payment program. A payment order is
flagged as being completed if the related open items were cleared when the payment order lot was posted.
Report RFKKPYOL provides you with an overview of payment orders that have not yet been completed.
You can use this report to select payment orders by their execution date. In this way you can display payment
orders that should already have been executed. You can also select payment orders of a certain payment run.
Report RFKKPYOD allows you to explicitly delete payment orders. You can only delete payment orders
whose execution date is at least 30 days in the past, and whose status is either executed, reversed or
expired.
It only makes sense to explicitly delete payment orders if forms or data media have not yet been sent off, or
recalled.
You cannot delete payment data (Report RFKPYD00) of a payment run where there are still open payment
orders.
The transactions for administration of payment orders are:
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Change payment order
Display payment order
Reverse payment order
Dependent Functions
Open items that are part of a payment order are treated like cleared items in document changes.
1.9.28 Changes to Postings and Documents

Use
Mass Document Changes
You can now change multiple line items at the same time with the new transaction for mass document
changes.
Selecting the line items to be changed takes place in the same way as the selection of open items, with the
entry of business partners, contract accounts, contracts or document numbers.
The open business partner items selected are displayed in a list and can be changed there. You can define the
appearance of the list by defining line layout variants for mass document changes.
The following data can be changed:
o
Payment data
Dunning data
Due date data
Locks
Data on payment (alternative payer, alternative payment recipient)
You can include every customer-defined field that is included in the FKKOP structure in a line layout
variant.
If you want to define alternative business partners (for payment) that have not yet been created, you can
create these business partners from the mass change.
When executing the changes, the same checks and events are executed as when changing an individual
document (transaction FPE2). Instead of event 1121 ( Before saving a document change), the new event
1125 (Before saving all changes) will be executed.
The event 1124 (After item selection) is also available. In this event you can determine whether an item can
be changed or split (see below).
When making mass document changes, change documents are produced as when changing individual
documents.
In addition to changing individual fields, you can also split line items in mass changes. The subitems
resulting from this can be changed like the original item. That means that you can enter different alternative
payment recipients, payment methods or locks, as for the original item.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
In order to split a line item, click on the Copy button. The original item is then copied and the amounts are
ready for input. You can enter the amounts manually. Alternatively, you can add the item to an amount field
automatically by double clicking on it, so that the total of the subitem amounts once again corresponds to the
original amount. You can also specify percentage rates, on the basis of which the amounts are split.
When you click the Delete button, the subitems created by a split are deleted again.
You can also define a general splitting rule for a set of selected items.
Example
Doc. no.
4711
4733
Amount
100
200
BPART
1002
1002
Payt lock
A
A
Alt. payt recipient
Both documents are selected, and a total amount to be split of 300 DEM is the result. This is to be split as
follows:
20%, alternative payment recipient G1, no payment lock
30%, alternative payment recipient G2, no payment lock
50%, payment lock A remains in force
This results in:
Doc. no.
Subitem amount
4711
4711
4711
4733
4711
4711
20
30
50
40
60
100
BPART
1002
1002
1002
1002
1002
1002
Alt. payt recipient
payment lock
G1
G2
A
G1
G2
A
This means that 20+40 = 60 DEM can be disbursed to the alternative payment recipient G1 and 30+60 = 90
DEM to G2.
You can only use one splitting rule for each mass change.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Define the specifications for mass document changes in the Contract Accounts Receivable and Payable
IMG -> Basic Functions -> Postings and Documents -> Document -> Screen Preparation -> Define
Line Layout Variants for Mass Document Change
1.9.29 Changes to Posting Areas

Use
Posting area 1032
In this posting area, you can define the default values for payment order lots.
Posting area 1033

In this posting area, you can define the default values for credit card lots.
1.9.30 Changes to Returns

Use
Posting to clarification accounts
You can decide for each returns reason whether to post to a clarification account, if the return cannot be
posted elsewhere.
Customizing with reference to house bank
Returns activities, graduated charges and amount differences can now be set, dependent on the house bank.
This can be useful if you work together with several house banks and have agreed on different conditions
(for example, depending on volume).
Switch to table control
List processing has been switched from step loop to table control. This allows you to select list fields by a
different method (see also Effects on Customizing).
Event 0295 changed
The interface of event 0295 was changed such that you can now modify the activities to be carried out. This
applies in particular to business locks, but also to all other activities, such as deleting payment methods. You
can use function module FKR2_ACTIVITIES_PROCESS as a reference for using the activities.
New event 0259
This is where returns items for processing and items from the payment and clearing document are
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
transferred. You can determine, based of the payment and clearing document, whether the item is to be
placed directly in the clarification worklist, for example, because the amount is very high, or the return date
lies well in the past.
List view
You can now use an ALV report for returns. This means you can view, process and print a returns lot
according to different criteria.
Delete outgoing payment method
You can set returns activities such that the outgoing payment method will be deleted in the contract account
in the case of credit memo returns.
Clarification processing
From Release 4.62 you can declare returns items with the function item invalid as being invalid. A returns
item can be invalid if:
-
It concerns an incorrect duplicate entry
The underlying document is reversed and the lot can no longer be changed.
This means that an item always becomes invalid if the returns clearing account has already been credited and
this item has to be posted to a dummy account. A returns item can only be declared invalid in clarification
processing. In the open returns lot you can use the function delete line to remove the returns item.
When posting returns, the new receivables can be supplemented by sector- and customer-specific fields. You
can use a function module for this, which is called at event 0150. This function module is also called if new
receivable items are created when clearing is reset.
If you already have your own function module for this event, you must check the program logic and adjust it
if necessary. There are now three processes, instead of two, for which the function module is called. You will
find further information in the documentation for this function module FKK_SAMPLE_0150.
For every return posted, event 0250 is called. The interface for this event has been enhanced to include the
field I_MODUS. You can find out which values the parameters can accept, and which data is transferred,
from the documentation on function module FKK_SAMPLE_0250.
Defining the list layout
You can now use field selection instead of screen variants to define the layout of the returns list.
To maintain field selections for returns, select from the IMG Business Transactions -> Returns ->
House-bank-specific Customizing
To carry out house-bank-specific Customizing for
o
Returns activities
Graduated charges
Maximum amount differences
Application forms for returns notifications
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
create a returns reason with the house bank ID. When processing the returns items, the system first tries to
find the house-bank-specific settings given in the returns item. If none are found, the system will conduct
activities in line with the reason for the return.
For this, select from the IMG Business Transactions -> Returns -> .
Posting to clarification account
If you wish to make a posting to the clarification account for a particular returns reason, you can enter an
account for that particular returns reason in Customizing. If, for example,
an item cannot be posted in a returns posting, but there is an entry for a clarification account, then a posting
will be made to this account.
Select from the Contract A/R & A/P IMG Business Transactions -> Returns -> .
1.9.31 Changes to Reversals

Use
Enhancements to the function Reset clearing
When resetting clearing you can now determine, from Release 4.62, to what extent the clearing is to be reset:
Fully
Partially
You can also determine whether the clearing amount is to be:
Posted as new item to one of the business partners involved
Distributed among the partners, accounts, contracts, company codes, business areas and divisions
involved
Posted as new item to the clarification account for incoming payments.
Scope of clearing reset

Instead of resetting clearing fully, you can reset part of it. You can determine this for any combination of the
following data:
-
Business partner
Contract account
Contract
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Company code
Business area
Division
Collective invoice number
Posting the clearing amount

One or more new line items are usually created for the clearing amount that has been reset.
If you wish to post the whole amount to one of the combinations of business partner, contract account,
contract, company code, business area and division, choose the setting Create new open items.
If the amount is to be divided as previously between business partner, contract account, contract, company
code, business area and division, choose Retain account distribution.
If the clearing was posted through an incoming payment in a payment lot, and the payment assignment has to
be clarified again, choose Clearing amount to clarification account.
Settings
No system settings are given for clearing resetting or clearing amount posting. This is deliberate to avoid the
wrong settings being used by mistake. If you want a default setting, you can save the relevant one.
Dependencies
If you post the clearing amount to the clarification account, a new clarification case is automatically opened
or the amount in an existing clarification case is increased.
If you reset the clearing of a collective invoice wholly or in part, new open items are always posted to the
collective invoice.
With the setting Retain account distribution, in the most straightforward case, only the clearing
information is reset and no new open items are created. This is the case when there are:
No cash discount, small differences, rate differences or withholding tax posted when clearing
No statistical items cleared
The system recognizes automatically whether this combination exists. For this reason, the setting in Release
4.61 No new items for clearing amount, is no longer necessary.
1.9.32 Changes to Single Roles in Contract Accounts Receivable and

Use
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.9.33 New Reports

Use
Open Item List
Previously, you could select already open items for a key date with the key date-related open item list
transaction. With Release 4.62 this transaction is also available as a mass run (OI List for Key Date).
The selected data can be output in text format. The list this creates can also be processed outside the R/3
system.
Open Item Evaluation

You can now include multiple predefined selections in a run when evaluating open items. The prerequisite is
that the selections refer to the same object (business partner, for example) and that the selection of the
desired items only differs by one selection criterion.
Example
All female business partners in Frankfurt
All female business partners in Munich
This preselection can be so constructed that they only differ in one criterion, the city.
You can now schedule, execute and periodically repeat the selection of open items using the Job Container.
You can now display items from collective invoices, installment plans and original receivables separately in
the list for the evaluation of open items (Key Date-Related Open Item List). Using the dunning level and
the dunning procedure, you can also only select items that have already been dunned.
Document Journal (Report RFKKBELJ00)

From Release 4.62 you can create a list of all documents available in the system. The following selection
criteria are available:
Document number
Posting date
Reconciliation key
Company code
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The report creates an index for optical archiving.
Tax Report for Clearing Date for Great Britain

With Release 4.62, you can use the report RFKKTAXCUM_UK to output a list of sales/purchase tax
amounts, cumulated according to company code and tax code.
1.9.34 Changes to Security Deposits

Use
Account assignments for cash security deposits
Up to now, it has always been determined for each application (internally) whether cash security deposits
were to be assigned to contracts or contract accounts.
From Release 4.62, you can now control these settings. In the system, you can set the following in General
settings for cash security deposits:
o
All cash security deposits are assigned to contract accounts throughout the system.
This has always been the standard setting for Telecommunications, and means that the field Contract
is hidden in the transactions for creating, displaying and changing cash security deposits.
This setting should not be selected for Utilities if:
-
Cash security deposits are to be created automatically at move-in (assignment of a contract to an

installation)
Cash security payments are to be offset automatically when the contract is billed
All cash security deposits are assigned to contracts throughout the system.
This has always been the standard setting for Utilities and is also recommended for
Telecommunications.
You can enter a contract, but it is not obligatory.

With this setting, the field Contract is active, but it is not a required field. If a contract is entered when
creating a cash security deposit, the request to furnish security and then the cash security deposit is
assigned to the contract. If no contract is entered, the assignment will be to the contract account.
Withholding tax for interest calculation on cash security deposits

When interest is calculated on cash security deposits, a withholding tax posting is made for each interest
document at contract account/contract level. The interest amount determined is the basis for calculating this
tax.
Prerequisites
Withholding tax indicator for outgoing payments is set in the contract account.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
In the IMG for Contract Accounts Receivable and Payable, maintain the settings in Define General
Parameters for Security Deposits .
To assign withholding tax codes to main and sub-transactions, make the relevant settings in the Contract A/R
& A/P IMG: Business Transactions -> Security Deposits -> Assign Withholding Tax Code to Main
and Sub- Transactions.
1.9.35 Changes in Taxation Procedure

Use
Tax exemption - Italy
With the new mass activity Evaluate end of tax exemption, you can evaluate, for each contract account,
tax exemptions that expire on a key date.
If a tax exemption expires, correspondence is generated for each contract account.
Tax reports at clearing date for United Kingdom

From Release 4.62 you can use the report RFKKTAXCUM_UK to output list of accumulated sales/purchase
tax amounts according to company code and tax code.
You can make the settings for tax reporting in the Contract A/R & A/P IMG under Basic Functions -> Tax
Reports:
o
Activate Recording of Tax Data
Define Specifications on Data to be Recorded
Define Report Times for Sales/Purchase Tax
Define Report Times for Other Tax Code
See also
Tax reporting for Contract Accounts Receivable and Payable must be set up. Please pay particular attention
to OSS Note 0197201.
1.10 IS-U-CS
Customer Service
1.10.1 New: Master Data Template and Master Data Generator

Use
You can now use the master data template and master data generator to create master data automatically in
IS-U.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The following business processes are examples of utility services used to create or change data:
o
Registration of a new customer with an energy company
Rate change for an existing customer.
Both processes require the creation of new data for objects in the data model, or changes to existing data.
You can handle these business processes using IS-U transactions. These enable you to enter data in all the
fields of the affected objects individually. However this is often a lengthy process, consisting of complex
tasks.
Some applications can be made easier by using a template application. This means that most of the fields in
an application have been assigned a fixed value, and the user only has to maintain certain outstanding fields.
The system determined the fixed values from the context or the service type.
Examples of such applications are:
o
Sales processes in SD or CRM
Internet self service functions
Data exchange between energy companies and distributors during a supplier change
Import of utility contracts closed by a partner company
This restricted view of the data model is supported by the master data template. To use a master data
template, carry out the following steps:
o
Choose an autonomous SAP master data template category that matches the business process
concerned. The category determines which objects can be created or changed. For an overview of the
master data template categories available, see IS-U Master Data Generator: Master Data Template
Categories.
Create a master data template in the category you have chosen. In the definition, specify which fields
are to contain a fixed value and which can be maintained in the template application (individual data).
Integrate the master data generator into your application. When you call the master data generator,
maintain the individual data. The generator adds the fixed values from the definition to this information,
and then uses the complete set of data to maintain the relevant IS-U objects.
The master data templates and master data generator enable you to large-scale changes to objects by means
of a few changes. You can also use a master data template for initial data creation.
Example:
o
You want to carry out rate changes for customers. To do this, choose the master data template category
RATECHANGE, which is designed for changing data in the installation.
You then create a master data template for the master data template category. In the defintion of the
template, enter the rate category of the installation as a fixed value. This means that the rate category is
automatically entered in all the installations allocated to this product. Specify that the change date can
be accessed by the template application.
From your application, call the function module ISU_PRODUCT_IMPLEMENT (process master data
template). Transfer the key of the master data template and the value entered in the application to the
function module. The function module carries out the changes in background- no additional dialog steps
are necessary.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Establish the necessary settings in Define Master Data Template.
1.10.2 IS-U-CS-FO
Front Office
1.10.2.1
SHORTTEXT&
Externally Triggered Call-Back Queries for the Customer Interaction Center

Use
You can now process externally triggered call-back queries in the Customer Interaction Center (CIC). In this
way, for example, an Interactive Voice Response device (IVR), or a web page can register that the business
partner wants his/her call returning.
For every call-back requirement, the system starts a workflow that uses the workflow inbox component to list
the work items for the application area .
Work items of this type can only be processed in the CIC. When they are executed, the system copies the
business partner to the CIC and creates a new register index in the application area, from which you can call
additional functions.
Establish the necessary settings in Define Process for Customer Call-Back.
1.10.2.2 New: Processing Documents Received in CIC

Use
You can now process any documents received, such as E-mails, faxes or scanned documents, in the
Customer Interaction Center (CIC).
The system starts a workflow for each document received. The process flow of the workflow is listed using
the new workflow inbox component. Before the workflow appears in the inbox, the system identifies the
business partner using the sender details. If you want, you can have the system send an automatic
confirmation of receipt to the sender.
In the inbox, the document is represented by a workitem that can only be executed in the CIC. When the item
is executed, the system copies the business partner to the CIC and creates a new register index in the
application area. Here, the system displays the text of the document, and enables you to start any other
processing steps, such as composing an answer to the document, or triggering a call.
Establish the necessary settings in the following Customizing activities:
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Establish Settings for the Workflow Inbox Component
Define Processes for Inbound Documents
1.10.2.3 Enhancements to Data Environments of Customer Interaction Ce

Use
The data environments in the navigation area of the Customer Interaction Center (CIC) now contains the
following enhancements:
o
Workflows for the business partner
Deregulation processes
Support for collective bill accounts
To establish and activate the enhancements in your navigation view profiles, perform the necessary
Customizing activities.
For more information, see Define Data Environment for Navigation Area
1.10.2.4 Workflow Inbox for the Application Area in the Customer Inte Center
Use
There is now a workflow inbox component for the application area of the Customer Interaction Cener (CIC).
The work items for the call center agents can be filtered for certain tasks or task groups, so that each agent is
only allocated work items suited to his/her work environment.
In general, work items are processed in the full screen. However, the processing of certain items (for
example received documents or consultation calls) is integrated into the CIC.
Establish the necessary settings in Establish Settings for the Workflow Inbox Component.
1.10.2.5 Managing Orders and Appointments

Use
You can now use Front Office process Create order with time data (INSORDTM) to generate orders. You
can also enter respective times in addition to the start and end dates. You can use these dates at a later stage
for the continuation and evaluation of orders (basic function for an appointment with a customer).
Before this release you could only enter the order start and end dates.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
You must establish the following settings in Customizing so that the dates are not transferred by scheduling.
To do this choose Scheduling -> Plant Maintenance and Service Orders.
1.
Maintain scheduling types.

Select field DateTime (basic date with time).
2.
Set scheduling parameters

-
Enter Do not adjust date in Adjust dates field .
Enter a scheduling type, which also allows you to enter/display the time.
If you want to use appointments with customers in other Front Office processes you must enhance the time
parameters. See process INSORDTM for an example illustrating this.
1.10.3 IS-U-CS-BT
1.10.3.1 IS-U-CS-BT-IO
Process Execution
Move-In/Out
1.10.3.1.1 New: Contract Change without Invoicing

Use
The function for changing a contract without invoicing enables you to change the payment form of some of
the contracts in a contract account without triggering separate invoicing.
You can use the contract change without invoicing function in a move-in/out when the contracts have
already been included in an invoiced billing document. It can also be called from the Customer Interaction
Center (CIC) or Front Office. You can cancel a contract change without invoicing.
When a contract change without invoicing is performed, the contracts are ended with a move-out, and new
contracts created with a move-in.
When the move-out is created, the latest billing document for the transfer contract is adjusted for reversal
whenever possible, and a new billing document is created with billing procedure 07 (contract change). This
billing document usually has bill amount zero and is never invoiced. No new meter readings are recorded
either. Instead, the last billed meter readings when the move-in was created are copied.
When the move-in is created, the open items of the transfer contract are reposted to the target contract
determined by the move-in (depending on the Customizing settings). This is only possible within the same
company code. Items that have already been paid are not reposted. Security deposits can be transfered.
Budget billing plans are treated as follows: they are deactivated by the move-out after the user has set the
payments to "payment on account". The move-in then creates a new budget billing plan with the deactivated
budget billing plan as a template. You then have to maintain the accounts to allocate the payments.
When you cancel a contract change without invoicing, the transfer documents that were generated by the
move-in are cancelled. Installment plans have to be deactivated manually. The contract change billing
document is cancelled, and a new billing document for the transfer contract is generated with reference to the
original reversal-adjusted bill. This new billing document is not invoiced either under certain circumstances.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Prerequisite: You have configured the contract change reasons under Define Reasons for Contract Change
such that field nI (contract change without invoicing) is selected. You also have to configure the settings for
reposting receivables during a contract change without invoicing.
To call the function from the CIC or Front Office, you have to copy the call that is shipped in the SAP
standard configuration for IS-U 4.62 (ISU462) to your Front Office configuration under Configure Front
Office.
To prevent the transfer contract from being invoiced again if the contract change is cancelled, you have to
create and activate a project for SAP enhancement EBIA0019 (customer-specific invoice comparison). The
program coding must be:
o
Y_NINVOICE_CUSTOMER = '3'.
1.10.3.1.2 Changed: Enhanced Functions in Move-In and Move-Out Processi

Use
You can now use the following functions:
o
To preassign Customizing data individually, use the Business Add-In (BAdI)

ISU_MOVEIN_CUSTOMIZE (IS-U: Override Move-In Processing in Customizing)
To enhance the menu of the move-in and move-out screens, use the following BAdIs:
-
ISU_MOVEIN_MENUE (IS-U: Menu Enhancement for Move-In)
ISU_MOVEOUT_MENUE (IS-U: Menu Enhancement for Move-Out)
In move-in processing, you can enhance the move-in date by adding an actual move-in date, which can
differ from the date specified in the system. In the same way, you can add an actual move-out date to
the move-out date
To generate a service order for the meter reading at move-in, enter the start date for service orders and
notifications in the Start date field on the move-in screen. In the case of service orders, you can also
enter a start time (in the Start time field). In addition, you can preassign data to these fields using
enhancement ECSBTMR1, which has been available since Release 4.61.
The same applies to service orders/notifications that are generated in move-out processing for final
billing.
In move-in processing, the system can now automatically request non-cash security deposits. To do
this, use the security deposit fields on the move-in screen (on the Contract data tab page).
To configure the system to automatically request non-cash security deposits, use the field Automatically
request security in the Customizing activity Define Control Parameters for Move-In on Contract Level.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.10.3.1.3 New: Customer Change

Use
The customer change functionality is now available.
The following functions are possible when contracts have already been used an invoiced billing document:
o
Create a customer change
Cancel a customer change
Repost open items due to customer change

This function is based on method TRANSFEROPENITEMS for BOR object category MOVEINDOC
(move-in), and can also be performed together with creating a customer change.
These functions can be used through the Customer Interaction Center (CIC) or Front Office or in the
move-in/move-out function. To call the function the Front Office, use method CREATE of BOR
object type MOVEINOUT (move-in/move-out) and pass on the relevant OK code.
When a customer change is created, the transfer contract is terminated through a move-out, and a new
contract created through a move-in. The move-out date is set to the end of the billing period of the latest
invoiced billing document for the transfer contract.
In addtion, you can enter the actual move-out date for the move out and an actual move-in date for the move
in. This enables you to document when the move-out customer left the apartment and the move-in customer
actually moved in. If these dates lie in the future, the changes to the business partner data and contract
account data of the move-out customers as planned changes, with the actual move-out date as the validity
date. For the move-in customer, the changes to the business partner data and contract account data are saved
in the system as planned changes, with the actual move-in date as the validity date.
When the move-out is created, the latest billing document for the transfer contract is reversed, and a new
billing document is created with billing transaction 08 (customer change). This billing document usually has
the billing amount zero and is never invoiced. No new meter readings are entered either. Instead, the last
billed meter readings are copied when the move-in is created.
When you create the move-in, depending on the Customizing settings, the open items of the transfer contract
are reposted to the target contract created by the move-in. This is only possible within the same company
code. Items that have already been paid are not reposted. Security deposits can be transferred.
Budget billing plans are subject to special treatment: They are deactivated by the move-out after the user has
set the payments to payment on account. The move-in then creates a new budget billing plan with the
deactivated budget billing plan as a template. You then have to maintain the accounts to allocate the
payments. The customer change sets a posting block on the transfer contracts. This is displayed only in the
move-out document.
The posting blocks are cancelled when the customer change is cancelled, as are the reposting documents
generated by the move-in. Installment plans have to be deactivated manually. The customer change billing
document is cancelled and a new bililng document is created for the transfer contract, with reference to the
original (reverse-adjusted) billing document. This new billing document may not be invoiced either,
depending on the circumstances.
Methods SETFICALOCK, RELEASEFICALOCK, and GETFICALOCKSTATE of BOR object type
MOVEOUTDOC (move-out document) are available for setting, releasing, and determining the status of the
posting block.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Prerequisite: You have configured the reasons for customer change under Define Reasons for Customer
Change. The settings for reposting receivables during the customer change also have to be maintained here.
To call the functions from the CIC or the Front Offcie, you have to copy the calls shipped in the SAP
standard system for IS-U 4.62 ("ISU462") to your Front Office Configuration under Configure Front Office.
To prevent repeat invoicing of the transfer contract when the customer change is cancelled, you have to
create and activate a project for SAP enhancement EBIA0019 (customer-specific bill comparison). The
program code has to be:
Y_NINVOICE_CUSTOMER = '3'.
See also
For information regarding the effects of the customer change on SD/FI-CA integration, please refer to release
note Changes in the Integration with Other Components.
1.10.3.1.4 No deletion of MR results during reversal of move-in/out

Use
Previously, when you reversed a move-in, readings with reason 06 (move-in reading) were deleted. This also
applied to reason move-out readings with reason 03 (final reading for move-out).
Now these readings are not deleted if:
o
they were not estimated or derived
they only have meter reading reason 06 (move-in reading) or 03 (final reading for move-out)
These meter reading results are then stored in the system without a scheduled meter reading date and with
meter reading reason 09 (interim reading).
1.10.3.2 IS-U-CS-BT-DR
Installation Disconnection/Reconnect
1.10.3.2.1 New Functions in the Areas Disconnection/Reconnection/Collec

Use
The following functions are now available:
o
Budget billing stop as a result of a utility disconnection

When you enter a disconnection, you can also have the system stop budget billing for all the contracts
affected by the disconnection. The budget billing stop is automatically reversed when you enter the
reconnection. The settings in Customizing act as default values and can be changed manually when you
enter the disconnection.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Interim billing as a result of a utility disconnection

When you enter meter reading results in the context of a disconnection, you can activate the billing
procedure interim billing for the devices affected by the disconnection.
Posting of disconnection/reconnection charges on contracts e

Previously, disconnection and reconnection charges were posted to a corresponding contract account.
Now the charges are only posted to contracts. You can also use an enhancement to have the system
influence the preselection of values and data.
Make the appropriate Customizing settings for the following functions:
o
Budget billing stop as a result of a utility disconnection

For each disconnection processing variant, you can define whether the system stops budget billing.
For more information, see Define Processing Variants for Disconnection Documents.
o
Interim billing as a result of a utility disconnection

For each disconnection processing variant, you can define whether the system creates a billing order for
an interim billing.
For more information, see Define Processing Variants for Disconnection Documents.
Effect on Batch Input
The method for creating a disconection without dialog processing, DarkCreateOfDisconnection (BOR object
type DISCONNECTION), now has an additional parameter. This is an indicator that controls whether the
system stops budget billing for the current disconnection.
Changes to the Interface
There are two new fields in the disconnection object area of disconnection processing. The first of these
controls whether the systemstops budget billing for the contracts affected by the current disconnection. The
second controls whether the system automatically creates an interim billing for the devices affected by the
disconnection after the disconnection has been confirmed.
In disconnection/reconnection, the system only allows to post charges to the contracts.
1.10.4 IS-U-CS-CC
Customer Contact
1.10.4.1 New: Archiving of Customer Contacts

Use
Archiving for customer contacts consists of the following functions:
o
Archiving start, including deletion of successfully archived documents

You can restrict the selection of contacts to be archived by the following criteria:
-
Contact number
Number of days from contact date (at least 100)
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Business partner
Contact class
Search for previously archived contacts using an archive index
Detailed display of an archived contact on the usual screen
Note that archived contacts cannot be changed or reloaded.

To use this function, choose the following IS-U menu: Utilities Indsutry -> Tools -> Customer Contacts
-> Archive Customer Contacts.
1.10.5 IS-U-CS-MA
Marketing
1.10.5.1 IS-U Sales Suport with SD-CAS

Use
Using the new logical database ECRMMKT_PARTNER (logical database for business partner
segmentation), you can separate business partner into groups for the purpose of marketing campaigns. This
segmentation is based on master data and selected transaction data (for example consumption data).
Currently, the logical database requires the component SD-CAS in order to be used for marketing purposes.
In addition, the business partners that you intend to select must be created with an SD customer master
record (including sales and distribution data).
If you want to evaluate consumption data that was created before you upgraded to IS-U 4.62 then you must
transfer it to the Consumption data table (DBERCHV). You can use the installation facts in the
Installation facts (normal) table (ETTIFN), or the billing line items in the Document line items table
(DBERCHZ) as a source for the consumption data
Consumption data from the installation facts
If you previously (before the upgrade to 4.62) used the installation facts as the basis for saving consumption
data, you can take the data direct from the Installation facts (normal) table to build your Consumption
data table. To do this, design a report that reads the data records you require (for example those that were
written to table Installation facts (normal) using a specific operand) usingthe following function modules:
o
ISU_DB_ETTIFN_FORALL (array-select for table ETTIFN)
ISU_DB_ETTIFN_FORALL_ANLAGE (array-select for table ETTIFN with the installation as the key
part)
ISU_DB_ETTIFN_INDEX_SELECT_ALL (reads ETTFN records (filtered selection with index))
ISU_DB_ETTIFN_SELECT (reads ETTIFN records (filtered selection))
From the Entry value (installed value) field in each of the data records, you can derive the discounted
consumption. The undiscounted consumption can be derived from the value to be billed field. This data can
now be updated in the Bill.qty (billing quantity) field of the Consumption history table. The consumption is
updated in accordance with the current time slice. The table is updated in the billing document, under the
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
billing document number of which the installation facts were also written. For more information, read the
table Billing document (ERCH) with the following function modules:
o
ISU_DB_BILL_SINGLE (Reads billing documents (by document number))
ISU_DB_BILL_SELECT (Reads billing documents (filtered selection))
When you have read this information, fill the Document lines: internal table (ERCHV) of the billing
document read. Then perform an update for the changed billing document using the function module
ISU_DB_BILL_UPDATE (update billing document).
Consumption data from old billing documents
Consumption data is also stored in the billing line items of the old billing documents. To read this data, use
the following function modules:
o
ISU_DB_BILL_SINGLE (Reads billing documents (by document number))
ISU_DB_BILL_SELECT (Reads billing documents (filtered selection))
You can recognize the billing line items that contain the data you require by the following fields
o
Rate number (TARIFNR)
Name of variant program (PROGRAMM)
Type of document line item (BELZART)
When you have identified the correct line item, take the consumption from the Bill.qty field, and the period
from the Valid from (date, from which the time slice is valid) and Valid to (date, to which the time slice is
valid) fields. You then enter this data in the line items of the Document lines: internal table(ERCHV). If
required, you can also copy the Logical reg. no. field (logical register number), or the device number.
When you have filled the Document lines: internal (ERCHP)table with data, perform an update using the
function module ISU_DB_BILL_UPDATE.
The consumption data is evaluated based on the entries in the Consumption history table. This table can be
filled by including the variants QUANTI22 and/or QUANTI23 in the billing schema . If you also want to
include older billing documents in the evaluations, then generate DBERCHV accordingly using the
migration object CONSHIST when you upgrade to IS-U 4.62.
To evaluate consumption data in the context of IS-U Sales Support using SD-CAS, carry out the following
activities:
o
Configure Consumption History and
Define Standard Values for Business Partner Segmentation.
1.10.6 IS-U-CS-CRM
Integration: Customer Relationship M
1.10.6.1 New: IS-U Sales Processing
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Use
IS-U Sales Processing supports the sale of utility products. These are essentially products that can be sold to
residential and industrial customers in the mass market. The transactions are oriented towards the efficient
processing of sales quotations and orders. A utility product can be represented by the closing of a utility
contract (enrollment), or it can be a service (such as a new connection). A normal sellable material, such as
gas heating, can also be a utility product.
The sale of utility products is based on the Sales and Distribution (SD) component. Each utility product
originates from an SD material that determines the basic characteristics of the product. Quotations and orders
for utility products are processed using SD quotations and sales orders.
The creation of sales orders and quotations for utility products is supported by a screen that enables you to
create and search for customers and premises, select utility products based on system proposals, and, if
necessary, to configure them. These activities are typically carried out in a customer service department or
call center. If a customer accepts a quotation then a sales order is created. You can call this function in
Utilities industry -> Customer Service -> IS-U Sales Processing.
The sales order is automatically processed; this is controlled by a workflow. Sales processing also supports
automatic data exchange between supplers and distributors. SAP provides a template workflow that performs
this data exchange. You can adjust this workflow to meet local market requirements by adding or removing
steps. Data exchange is generally only necessary for utility products based on a contract.
When data exchange is complete, the last step of the workflow creates all the data required to bill the new
utility contract. This includes the installation, allocation of a device, the contract, and installation facts.To
configure this step, you must define a master data template for every utility product based on a contract.
Using this template, the system creates all the master data required to bill the contract.
Establish the necessary settings in:
o
Define Utility Products
Define Master Data Templates for Utility Products
Generate Characteristics for Utility Products for Allocation to SD Materials
Define Master Data Templates for Sales Quotation/Order
Define Profiles for Sales Quotation/Order
Define User-Defined Utility Product Set Types
1.10.7 IS-U-CS-ISS
Internet Self-Services
1.10.7.1 New: Business to Customer Internet Scenario: Report Move-Out

Use
Utility customers can use this function to report a move-out. After you have been identified through your
user ID and password, the system prompts you to enter the move-out date and choose the divisions for the
move-out.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
You can change your address data and payment method, as well as enter final meter readings.
You can use Business Add-In (BAdI) ISU_IAC_MOVEOUT (ISU: BAdI for Internet integration move-out) to add user-defined fields and checks, as well as control the entry and change of ISU data.
A move-out is created with customer contact and meter readings in the ISU system.
Depending on the Customizing settings, address changes and other changes take effect immediately or at
some point in the future.
You can configure the process in Customizing under Define Control Parameters for Internet Self-Services
such that the changes are not updated immediately in the system. Instead, a work item is generated in am
agent's work list. The clerk can then check the data and update it after checking.
1.10.7.2 New: Enter Meter Reading Results via WAP

Use
A number of scenarios from Internet Self-Services have now also been made available for the WAP standard
(Wireless Application Protocall). This scenarios were considered appropriate for use with mobil terminals
(for example WAP cell phones or Personal Digital Assistants (PDA)). The WAP functions are identical to
their counterparts in IS-U Internet Self-Services. However, they are restricted by the limitations of mobile
terminals.
SAP provides WML template (Wireless Markup Language) that can be adjusted to meet your company's
requirements. The templates are supplied in their own Internet Service (prefix EWAPIAC), and correspond
to their counterpart HTML services (prefix EWEBIAC).
The initial scenario is Enter meter reading results with premise selection.
We do not provide example templates for any other scenarios. You can create your own WML templates
based on the HTML services and convert the services for WAP usage.
Like the standard Internet scenarios, WAP scenarios require an SAP Internet Transaction Server (ITS)
suitable for Release 4.6C. You can operate an ITS instance using a combination of HTML and WAP/WML
services. The difference between HTML and WML is configured on the service level with the additional
WML-specific parameter ~xmltype. Assign this parameter the value WML.
All the WAP-specific MIME types must be activated on the web server. Otherwise the WML pages will be
unable to send data. They are as follows:
o
Application/vnd.wap.wmlc
Application/vnd.wap.wmlscriptc
text/vnd.wap.wml
text/vnd.wap.wmlscript
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.11 IS-U-WM
Work Management
1.11.1 IS-U-WM-PC
Processing
1.11.1.1 Disaggregation of Sales and Distribution (SD)/Customer Servi Work

Management
Use
You can now use SD and CS processes in a disaggregated scenario in the Work Management component
(IS-U-WM).
A business process (such as creation of new service connection) is split over separate SAP Systems or
different company codes. All steps involved in the whole process are executed in these units.
Customer-related steps, such as quotation, sales order and invoicing, must be processed in an SAP System
where both the standard system and the industry-specific Utilites (IS-U) System are installed.
Logistics-related steps such as Service Order and Resource Planning must be executed in a system where the
standard system is installed. The IS-U System is optional in this case.
Communication between all systems involved takes place using the following IDocs:
o
IDoc ISU_SDSM_ORDER
This IDoc transfers the sales order data from an IS-U System to an SAP Standard System and creates a
service order for each relevant item.
IDoc ISU_SDSM_COMP
This IDoc confirms the technical completion of a service order in the SAP Standard System to the IS-U
System. The invoicing block for the sales order items is removed in the IS-U System, the new service
connection is created and installed.
Use report REWM_ISU_SDSM_COMP to select completed service orders in the SAP Standard System and
generate IDocs from category ISU_SDSM_COMP.
Define the Control Parameters for Disaggregation of SD/CS processing in Customizing.
See also
Further information is available in specification Disaggregation of SD (Sales and Distribution)/CS
(Customer Service) in Work Management. This is obtainable from SAP.
1.11.1.2 Managing Orders and Appointments

Use
You can now use Front Office process Create order with time data (INSORDTM) to generate orders. You
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
can also enter respective times in addition to the start and end dates. You can use these dates at a later stage
for the continuation and evaluation of orders (basic function for an appointment with a customer).
Before this release you could only enter the order start and end dates.
You must establish the following settings in Customizing so that the dates are not transferred by scheduling.
To do this choose Scheduling -> Plant Maintenance and Service Orders.
1.
Maintain scheduling types.

Select field DateTime (basic date with time).
2.
Set scheduling parameters

-
Enter Do not adjust date in Adjust dates field .
Enter a scheduling type, which also allows you to enter/display the time.
If you want to use appointments with customers in other Front Office processes you must enhance the time
parameters. See process INSORDTM for an example illustrating this.
1.11.1.3 New Selection Parameters for Periodic Inspection Processing

Use
You can now use the following new parameters for periodic inspections:
o
Inspection period in months or years

Note: The system does not convert the inspection periods from months into years and vice versa.
You can use the following functions to restrict the selection for inspection periods:
-
Create/extend inspection list
Change inspection list
Display inspection list
Create orders/notifications for inspections
Individual technical installations or equipment

When creating or extending an inspection list you can enter individual technical installations or
equipment, which are transferred into the inspection list.

The month and year fields for inspection periods are included in the inspection list. These new fields are,
however, only maintained with entries relevant to this change in the inspection list.
1.11.1.4 Determination of Work Center for Orders

Use
In addition to plant determination for work orders, you can also define determination of reponsible work
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
centers.
You must allocate a reponsible work center to the service object and regional structure group. If you do not
maintain determination, then the work center for the service object is used.
You can use work center determination:
o
for the creation of orders
for device replacement (periodic replacement)
for inspections
for disconnection and reconnection
for aperiodic meter reading
with BAPI UtilServOrder.CreateMultiple
with method UtilServOrder.CreateByOrderCode
with Front Office Process Create repair order (SMREP02)
Define plant and work center determination for work orders.
1.12 IS-U-WA
Waste Management
1.12.1 Changed: Area Menu for Waste Management

Use
The following changes have been made to the Waste Management menu:
o
Master data
-
List processing from the Plant Maintenance (PM) component and the general Inventory
Management menu have been added to menu entries Container and Vehicle.
The transaction for creating vehicles under menu item Vehicle has been changed. Previously,
vehicles were created as a material/serial number (transaction IQ01). Waste Management now
uses Create vehicle (transaction IE31).
Menu item Create/Change/Display vehicle category has been deleted. The Waste
Management component (IS-U-WA) now uses the vehicle categories that are defined in master
data Customizing for Plant Maintenance and Customer Service.
Menu item Route is new.
Processing
The following new menu items have been added under menu item Waste disposal order:
-
Change and display waste disposal order
Confirm waste disposal orders for route
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Confirm waste disposal order
In the menu entry Periodic Service for Residential Customers, the subsequent entry Create has been
deleted because the corresponding contract is created as part of the move-in.
o
Interfaces
The menu item itself is new, and contains the following functions:
-
Download services for external route planning

This menu item was previously located under menu item Processing.
Download waste disposal orders

This menu item is new.
1.12.2 New: Confirmation of Waste Disposal Orders

Use
You can now confirm waste disposal orders in one of the following ways:
o
Using a Business Application Programming Interface (BAPI) or an IDoc

This enables you to load the results of the waste disposal order (driver, vehicle, type, quantity, date,
time, and so on) from an external system, such as the on-board computer of a vehicle.
Manually
To enable you to enter the results of the waste disposal order provided on paper by the driver, we have
added the following entries to the Waste Management menu:
-

To confirm a an individual order, choose Container. A screen appears that displays the individual
items of the waste disposal order.
The confirmation category determines which of the fields (of the order and weight data) you use to confirm
the waste disposal order. You define the confirmation category in Customizing, where you also allocate it to
a service area. The system then offers you appropriate confirmation types for each service area.
To confirm additional fields, proceed as follows:
o
For fields belonging to the waste disposal order, use the customer include
CI_EWA_ORDER_RESULT_HEAD for the header, and CI_EWA_ORDER_RESULT_EMPTYING
for the items.
For fields belonging to the weight data record, use the customer
includeCI_EWA_ORDER_RESULT_WEIGH.

You do not have to convert waste disposal orders manually.
1.
Define the Confirmation Categories.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
2.
Define the Service Areas.
3.
Define the Notes on Confirmation.
1.12.3 IS-U-WA-MD
Master Data
1.12.3.1 Changes and Additions to the Service Frequency

Use
You can now maintain additional data for the service frequency. This data affects the technical and business
processing of the service frequency.
The layout of the processing screen has also been changed to enable you to navigate more easily between
individual objects, and to enter all the most important data for a service frequency at once.
The service frequency offers the following new functions:
o
You can maintain difficulties>/> for the service frequency on the container level. These can affect
route planning, the billing of waste disposal services and the renumeration of staff.
You can maintain exceptions to the service dates for each service frequency. This is done on the
container level. The system observes these exceptions during order creation and adjusts the service
dates accordingly. You can also postpone fixed service dates (namely dates that were not defined as
exceptions), delete them or create additional service dates.
You can restrict the service frequency seasonally, and allocate it to a factory calendar.
1.12.3.2 Fleet Management

Use
You can now model your vehicles in the system using fleet management from the Plant Maintenance (PM)
and Customer Service (CS) components. The previous maintenance procedure (carried out in the Waste
Management menu) now no longer apply; it has been replaced by the maintenance of vehicle types in fleet
management.
To make full use of fleet management, maintain the following Customizing activities:
o
Define Types of Technical Objects (mandatory)
Settings for Fleet Management

-
Assign View Profile and Equipment Category to Fleet Object (optional)
Define Consumable Types (optional)
Define Usage Types for Fleet Objects (optional)
Define Engine Types for Fleet Objects (optional)
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Make Settings for Units of Measurement for Consumption Monitoring (optional)
Define Special Measurement Positions for Fleet Objects (optional)
Define Calculation Method for Fleet Consumption (optional)
Set Field Selection for Specific Fields in Fleet Management (optional)
Define Waste Management-Specific Attributes of the Vehicle Types (mandatory)
1.12.3.3 New: Route

Use
You can now use the route for both route planning and scheduling and dispatching. A route is a regional
summary of premises composed of one or more service areas. It is linked to the regional structure. The route
does not indicate the sequence in which the premises are approached.
You can make use of the following functions:
o
Allocation of the route to a city or street section

This is done via the regional structure. You can allocate several routes to the city/street section both on
city and street levels.
Allocation of the route to a standard vehicle and a crew, using the resource master.
The system proposes default values for both the standard vehicle and crew when you create the waste
disposal orders. You can maintain the crews in the Organization Management (BC-BMT-OM)
component.
Allocation of the route to a waste type (such as biological waste or paper) and one or more service
areas.
Allocation of the route to one or more service frequencies

If you want to allocate a route to a container on the service frequency level then the system proposes a
default value.
Factory calendar
This enables you to control how the system handles (service) dates that do not fall on a working day.
You can maintain a factory calendar for each route. You can also maintain non-working days as
exceptions on the level of the entire factory calendar, or seperately for each individual non-working
day.

The route is allocated to the containers to be services within the service frequency. The system verifies that
the route exists in the system. If you have assigned the containers a route that does not exist then you must
maintain the routes again accordingly.
Definieren Sie Nummernkreise fr Routen.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.12.4 IS-U-WA-PC
Processing
1.12.4.1 New: Change and Display Waste Disposal Order

Use
You can now change and display waste disposal orders individually. The Waste Management menu has been
adjusted to enable you to do this: the Processing entry now contains the subentry Change and Display
Waste Disposal Order.
You can make the following changes to the data of an individual waste disposal order:
o
Postpone the order date of the entire waste disposal order
Postpone/delete individual items of the waste disposal order.
1.12.4.2 New: Confirmation of Waste Disposal Orders

Use
You can now confirm waste disposal orders in one of the following ways:
o
Using a Business Application Programming Interface (BAPI) or an IDoc

This enables you to load the results of the waste disposal order (driver, vehicle, type, quantity, date,
time, and so on) from an external system, such as the on-board computer of a vehicle.
Manually
To enable you to enter the results of the waste disposal order provided on paper by the driver, we have
added the following entries to the Waste Management menu:
-

To confirm a an individual order, choose Container. A screen appears that displays the individual
items of the waste disposal order.
The confirmation category determines which of the fields (of the order and weight data) you use to confirm
the waste disposal order. You define the confirmation category in Customizing, where you also allocate it to
a service area. The system then offers you appropriate confirmation types for each service area.
To confirm additional fields, proceed as follows:
o
For fields belonging to the waste disposal order, use the customer include
CI_EWA_ORDER_RESULT_HEAD for the header, and CI_EWA_ORDER_RESULT_EMPTYING
for the items.
For fields belonging to the weight data record, use the customer
includeCI_EWA_ORDER_RESULT_WEIGH.

You do not have to convert waste disposal orders manually.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.
Define the Confirmation Categories.
2.
Define the Service Areas.
3.
Define the Notes on Confirmation.
1.12.5 IS-U-WA-IF
Interfaces
1.12.5.1 Download und Druck von Entsorgungsauftrgen

Use
You can now
o
download waste disposal orders to an external system, for example an on-board computer in a vehicle.
This is done using a raw data interface (RDI), which transfers specific data on the waste disposal order,
for example the address, container data, route, driver, and vehicle.
print waste disposal orders for the driver of the route.

This is done using a SAPScript interface. SAP provides the application form
IS_U_WA_ORDER_DOWNLOAD for this purpose. It contains the same fields as the waste disposal
order, giving the driver a route sheet with all the necessary data. You can also define your own forms
that only contain the fields you require.
Define your own application form to meet your company's requirements. Use the form
IS_U_WA_ORDER_DOWNLOAD as a template.
For more information, see Define Form for Downloading Waste Disposal Order.
1.13 IS-U-IDE
Intercompany Data Exchange
1.13.1 New: Table DBERCHT for Saving Individual Document Texts

Use
You can use the new table DBERCHT to enter individual texts for single documents.
In this release, document texts can only be maintained within manual billing or using the direct input module
for manual billing:
You can enter a text up to 100 characters in length in the Text field of the new table. Several document texts
can be saved for a line item. If you want to save a text for the document header, save it for line item "0";
otherwise, the corresponding line item is saved in the Line item field.
You can enter an identifier for bill printing in the text item field. For example, you can note where the
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
corresponding text should be printed. You can choose this identifier freely.
New levels have been created in the following form classes to print out the texts:
Bill:
is_u_bi_bill
Collective bill:
is_u_bi_collective_bill_new
1.13.2 Changed: Communication Control

Use
You can now define communication control specifially by operational area and service type.
Previously, you could only process inbound or outbound IDocs by triggering certain types of processing.
These were based on the processing event. This was done by allocating function modules, as supplied by
SAP, to the processing event
The new procedure is based on the assumption that different areas use different communication standards.
This is especially relevant for suppliers that operate in different geographical distribution grids.
The new communication control consists of the following components:
o
Activation of processing events

Both SAP standard processing events and user-defined processing events must be activated. This
enables you to suppress the activities triggered by the events, or select activities to be suppressed.
Determination of operational areas

An operational area is always determined dynamically, and is based indirectly on the point of delivery.
Using the services of a point of delivery, the system determines the distribution company and, by means
of a determination table, finds the relevant operational area. This table can be configured in
Customizing. If a distribution company operates the same division in several operational areas then you
must define a new distribution company for each of these operational areas. Alternatively, you can
define your own determination procedure for operational areas.
Determination of function modules for the processing event

In addition to the operational area, the determination function also depends on the service type of the
communication partner. This means that in markets with more than two service providers for different
service types, one communication method can be defined for each service provider.
Example
An operational area has three service providers, a supplier, distributor, and a meter operator. A
customer informs the supplier that his/her telephone number has changed. Depending on how the
operational area is regulated, one of the following actions can be performed:
-
The supplier sends the change notification to one of the other service providers
The supplier sends the change notification to both of the other service providers
The supplier sends each service provider a different notification.

Determination is still dependent on the service type of each service provider. This is intended for cases
when your company operates as service provider with different service types, and manages them in one
system. This enables you to define different communication methods depending on your company's
role as a service provider.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The old communication control is no longer supported. However, the Processing control table
(ECOMCONTR)- used to determine the function module of a processing event- is still available and can be
used as a basis for the new Customizing activities. If the need arises, you can still used ECOMCONTR. To
do this, contact SAP.
Establish the necessary settings in the following Customizing activities
o
Activate Processing Events
Define Operational Areas
Allocate Operational Area
Allocate Function Module to Processing Events

In this activity, you define the function modules called by the processing events.
1.13.3 New: Reference Number

Use
The deregulation of the energy market requires the exchange of information between companies involved in
providing a service to a customer. Examples include energy supply and grid usage.
This primarily affects the following information types and functions:
o
Exchange of meter and consumption data
Exchange of billing data
Payment information
The above functions can be logically allocated to a cycle (for a certain customer/connection object), and to a
period. This period starts with the exchange of meter data and finishes when the bill is payed.
The reference number links these logically connected functions, and enables you to audit the account.
The allocation of the functions to a reference number (and thereby to a period) is also required for technical
reasons.
Depending on the energy market, a reference number may also be necessary for communicating with third
parties. In these markets, an external reference number is maintained in addition to the internal one.
o
Define Function Modules Permitted for Each Processing Event
Allocate Function Modules to Processing Events
Define Number Ranges for Reference Numbers

Create the number ranges for object ISU_CREFNO.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.13.4 New: Default Values for Deregulation Scenarios

Use
You can now define default values that determine which deregulation scenario applies to a certain point of
delivery.
Previously, this function was primarily directed at distributors and suppliers. You were unable to use default
tables to determine which service provider takes on which role.
In the deregulated market, the deregulation scenario determines how many installations or contracts are
created for a customer, and which data is entered in fields used in Intercompany Data Exchange (IDE). To
support automated processes, such as enrollment, or manual move-in, you can preassign data to fields in
Customizing, or establish settings to reflect the market situation.
Using the default value procedure, you can determine the following information:
o
Which service types (and which services) are required?
Does the company bill customers itself, or through another service provider?
Does the company create its own bills and perform collection, or through another service provider?
If a service provider creates the bills for an external point of delivery service then the following applies:
-
Does this service provider own the receivables made by the external service provider, or does it
perform convergent billing?
The answers to the above questions determine how many point of delivery services can be created as
contracts, and how many as non-billable services.
The system also proposes the payment class in order to determine the terms of payment.
To use this functon, maintain the following two Customizing tables:
o
Determine Service Types for Operational Areas

In the case of some service types, the corresponding service provider must be entered as a default value.
This requires you to know the distribution company for the point of delivery, using which you can find
the operational area.
Configure Default Table for IDE Process Control

Here you define the relationships to external service providers from a billing perspective. This entails:
-
Who calculates the bill
Who sends the bill to the customer and performs collection
Whether the bill is issued through convergent billing, or through accounts receivable pledging
The last point is especially important for the number of contracts that have to be created. If the bill
is issued through accounts receivable pledging then the system assumes one contract is sufficient.
In the case of convergent billing, one additional contract is created for each convergent billing. In
Release 4.62, the number of billed services for each point of delivery is restricted to two services.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.13.5 New: Determination of the Distribution Company from Regional

Use
You can now store the distribution company of a operational area in the regional structure (namely in cities
and streets). This means that you can use the regional structure to determine the address of the distribution
company (for example when you determine the operational area). This is done using the function module
ISU_ADDRESS_PROVIDE (address-formatting for displaying and determining IS-U data).
Since different distribution companies can be responsible for different divisions, the distribution companies
are stored in the regional structure by division.
1.13.6 Enrollment Process: Workflow for Communication with Other Se Providers

Use
The deregulation of the energy market requires the exchange of information between companies involved in
the supply of a service to customer. Examples include energy supply and gird usage.
There is now a template workflow that you can copy and adjust to meet your requirements. This workflow,
ISUIDEENRCOM is based on the requirements of a supplier in the Texan market. The workflow handles the
communication steps with third parties necessary to carry out an enrollment. It is integrated in the superior
workflow for the enrollment process.
The workflow requires that the distribution company and point of delivery are known for the contract
involved in the enrollment process. You can handle several contracts, and thereby several points of delivery
for one customer.
The following data must have been created as a result of the previous workflow process:
o
Business partner
Contract account
Premise.
Any missing information is collected in the workflow. This information comes partially as a result of
communication with other service providers. Otherwise it is determined dynamically from the IDE default
values as defined in Customizing. The workflow prepares the master data to be created and returns it to the
enrollment process. The process then uses the master data generator to create the necessary master data.
Status management is also integrated in the component; this enables customers to individually define statuses
as well as when they change.
The workflow is primarily designed to handle the standard enrollment process. We have integrated only
rudimentary functions for handling exceptional circumstances and errors, since these are generally handled
differently by each customer.
Establish the necessary settings in the following activities:
o
Allocate Service Provider to Payment Frequency
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Define Payment Classes for Service Providers
See also
For more information, see New: Status Management for Communication in Enrollment Process.
1.13.7 New Procedure for Creating Outbound IDocs for Billing Docume
Use
Certain scenarios in the deregulated market require the electronic exchange of billing documents between
service providers.
The IDocs necessary for this exchange are now generated using a report that reads the index created in
Invoicing.
Previously, the IDocs were written directly during bill printout.
The new procedure means that you now longer have to execute bill printout for the document after it has
been invoiced. If Invoicing determines that a IDoc must be generated then the system writes an index record
and sets the new Do not print indicator.
To generate the IDocs, start a report.
The IDocs are generated by the report REDISDN0 (Generate electronic bills). You must schedule the report
accordingly.
See also
Define Sending of EDI Documents
1.13.8 New Field in Contract: Service Provider Responsible for Invo

Use
You must now maintain the service provider responsible for invoicing in the contract. Previously, this field
was only contained in the installation history.
If you need to historically reconstruct the service provider responsible for invoicing (to ensure an accurate
data exchange in the case of a reversal) then you must now perform a contract change.
We do not support automatic data conversion, and assume that all customers who upgrade to 4.62 and use
Intercompany Data Exchange (IDE) are aware of this. We will implement measures in advance of the
upgrade to ensure that the data transfer is as simple as possible. However, in previous releases (such as 4.51
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
and 1.2) the data model was different again, which makes the transfer more difficult.
If you already use the IDE component, and have not already contacted SAP then do so immediately.
1.13.9 New: Processing of Electonically Transmitted Consumption and

Use
In the deregulated market, wire companies send meter and consumption data to the corresponding suppliers
electronically. The new process makes it possible to process these consumption and meter notifications
automatically.
If a consumption notification is reversed then any follow-up documents resulting from Billing/Invoicing are
reversed automatically.
This action is triggered by the processing event USG_IN_ACT. The corresponding fucntion module is
ISU_COMPR_USAGE_INFO. It serves as a template and is oriented towards the requirments of the North
American market. Should your requirements be different, such as in the process flow of the function module
or the IDoc interface then make a copy of ISU_COMPR_USAGE_INFO and adjust it accordingly.
The IDoc interface is used to exchange data between companies.
o
Allocate Register Type

Here, you allocate the regsiter type used in the IDoc to the corresponding IS-U regsiter type.
ISU-Zhlwerksart zu .
Allocate Unit of Measurement

Here, you allocate the corresponding IS-U unit of measurement (used internally) to the IDoc unit of
measurement.
Define Processing Events

Define a valid processing function module for the processing event USG_IN_ACT.
Define Function Modules for Processing Events
Define Communication Control
1.13.10 Restrictions to IDE Functions

Use
The functions available in this release do not yet cover the complete scope of functions in the Intercompany
Data Exchange (IDE) component. Note that restrictions also exist in the IS-U standard functions.
The data model and general design of the IDE functions were selected to meet the requirements that have so
far come from the North American and European markets. However, note that in detail the functions are
oriented towards the North American market. Other markets that use different functions can take the function
supplied in IDE as templates and then adapt them to their requirements.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The detailed functions are still heavily oriented towards suppliers that operate as billing agents. To a great
extent, these functions have been carried over from the last release. Elements necessary for the complete
integration of a supplier that does not operate as a billing agent (and therefore acts as the oppposite number
to the above supplier) are missing.
There follows a list of the main restrictions to the IDE component. It is based on previous market
requirements and cannot be considered to be complete.
Restrictions to IS-U standard functions
o
Billing-relevant device installation not possible

Scenario:
From a supplier's point of view, the consumption of several points of delivery has to be processed in
billing together. This leads tp problems as one contract has to be created for each point of delivery. The
standard solution to this in IS-U is the billing-relevant installation of all the regsiters to be aggregated in
a single installation.
Do not choose this option as communication takes place on the level of the individual registers. It is
not clear how, for example, the omission of individual points of delivery would affect the
billing-relevant construct.
Alternatives include an outline contract for larger customers. In some markets you can also combine
several points of delivery and then request a single point of delivery in their place.
No adjustment reversal
We have not evaluated the consequences of carrying out an adjustment reversal, especially how it
affects automatic data exchange. If the processing events for reversal, billing and invoicing are active
then refrain from using an adjustment reversal.
Missing functions
o
We do not support the storage of electronically transmitted historical consumption data.

To use this function you must define your own solution
Customers in different distribution grids

If a distribution company has customers in different distribution grids then device numbers may occur
twice. This scenario can only be modelled using a workaround that creates different material master
records for the affected devices.
We do not support transaction statistics from deregulation processes such as enrollments.
Issuing of electronic bills

When you send electronic bills from Invoicing, the system can only take into account items from IS-U
Billing. Other items, such as SD charges, budget billing plan payments, installment payments, dunning
and interestcharges that were intially generated in Invoicing are not contained in the electronic bill.
There is no communication interface for inbound and outbound interval data.
The system supports a maximum of two billed point of delivery services (distributor and supplier).
Change in bill creation from distributor to supplier

There is currently no automatic process that supports either this or the reverse process. You must
develop your own solution. As of Release 4.62, the service provider that issues the bill is to be stored
in the contract. Since this information is normally historically any changes involve a contract change.
There is no interface or associated processes for electronic data exchange involving service requests.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.13.11 New Determination Function for Service Provider Terms of Pay

Use
Previously, terms of payment were determined on the basis of the service provider and the account
determination ID, both of which are stored in the contract. However, the use of the account determination ID
lead to the creation of additional account determination IDs that were not necessary for postings. In turn, this
resulted in the replication of Customizing for account determination in FI-CA.
You can now determine the terms of payment independently using the new fieldSP pay class (payment
class of service provider) in the contract.
The system determines the terms of payment along with the service provider. As before, the terms of
payment consist of the payment method and payment frequency.
Table TEPFCS, previously used in these instances, is now obsolete, though we do not intend to delete it. It
can still be used to manually adjust entries to match the contract, and to establish settings in Customizing
accordingly.
Implementing this new development in the contract requires a higher expenditure of time and resources. If
you previously used the account determination ID to determine the terms of payment then you must set the
new SP pay class field accordingly in all the contracts. Since the account determination ID can be used
differently, and, since it is unknown which values are converted to which payment ID, we do not offer an
XPRA to implement this conversion automatically.
If you previously used the terms of payment in a deregulated environment, you must convert the contract
using your own reports. For more information, contact SAP.
During the data transfer, ensure that the SP pay class field is maintained correctly. This is especially
important if the servive is invoiced externally. It is of no importance to the entries in this field whether the
service billed internally, or through convergent billing.
o
Define Payment Class for Service Providers
1.13.12 Point of Delivery

Use
Registers, devices and installations are now allocated to points of delivery. A point of delivery has a unique
point of delivery ID. This is used in deregulated markets to uniquely identify a point at which energy is
drawn, regardless of the geographical boundries of distribution grids.
Points of delivery can be divided into two groups, deregulation points of delivery and technical points of
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
delivery.
o
Deregulation point of delivery

These are usually provided by distributors or market regulation authorities. They are used in
Intercompany Data Exchange (IDE) to uniquely identify the point to which energy is supplied during
communication with the supplier or with other service providers .
Points of delivery are allocated to an installation. Note that an installation can only have one point of
delivery, but a point of delivery can be allocated to several points of delivery. This is the case in
installation coupling, where two installations with the same point of delivery are required in order to
bill a supply contract and a distribution contract.
Technical point of delivery

In this case, registers are allocated to a point of delivery. This view is relevant for the Energy Data
Management (EDM) component.
The point of delivery is used to identify profiles that are allocated to registers in IS-U/EDM. When
profile values are imported ( load shape), the point of delivery is specified. The system can then
determine the interval meter allocated to the point of delivery. Consequently, the profile values can be
automatically copied to the profile allocated to the interval meter. This enables you to import measured
load shapes without any knowledge of the objects managed in IS-U/EDM. You only need to know the
point of delivery ID.
In this way, you can perform a simple data transfer for load shapes from an automated meter reading
system.
A point of delivery can be used for both deregulation (IDE) and techincal (EDM) purposes simultaneously.
This is the case for distributors that use EDM and use the point of delivery to communicate with suppliers.
Suppliers only use the point of delivery for deregulation purposes.
You can also distinguish between internal and external point of delivery IDs. In the case of deregulation
points of delivery, an installation is created with an external and an internal ID. This is done for technical
reasons; the internal point of delivery ID cannot be seen externally. The point of delivery remains inactive
until it is assigned and external ID. An ID is allocated to the point of delivery in the installation.
Point of delivery IDs are usually created with a predefined structure, from which you can derive information,
such as the distribution company and postal code of the area in which the point of delivery is located).
To do this, you must display the point of delivery ID in its formatted form. We support an unformatted form,
as well as the structure category metering code. You can define additional formats yourself.
Each point of delivery is created with the necessary point of delivery services. These are determined from the
operational area in which the point of delivery is located.

You must now allocate an internal point of delivery ID to each installation. To ensure this happens an XPRA
is started at the point of upgrade that creates the necessary points of delivery. The XPRA only creates
internal point of delivery IDs. To allocate any existing point of delivery IDs you must define your own
programs.
Ensure that a point of delivery is created for each installation, and that the point of delivery and installation
are linked.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Define the structure of the point of delivery ID in the following Customizing activity: Define Point of
Delivery ID. Here you define both the structure itself, and the function module that formats the display.
See also
For more information, see Point of Delivery Service and Default Value Procedure
1.13.13 New: Point of Delivery Service

Use
In deregulated markets, a point of delivery is supplied with services. These are known as point of delivery
services. Examples include distribution, supply and meter reading services.
A point of delivery service is used primarily for communication between service providers.
You can divides point of delivery services into billable and non-billable services. Billable services are
modelled using contracts is IS-U; non-billable services are stored in the new table ESERVICE (point of
delivery service).
With the point of delivery service, we have created a new business object in IS-U. The point of delivery
service has two subobjects, contract and non-billable service. This does not entail any new levels in the
data model.
The point of delivery service contains the service provider and the service type. This means that
Communcation Control can always the service provider with whom the system has to communicate for each
point of delivery.
A point of delivery is created automatically during every enrollment; this also includes the necessary
contracts and non-billable services.
During a manual move-in, the system also creates any non-billable services required for the point of delivery.
During a move-out, the non-billable services are canceled, unless you have configured the system
accordingly in the Customizing activity Define Service Types.
Like the contract, the point of delivery service contains a start and finish date that define its validity period.
Billable point of delivery are created through migration, in the same way as contracts were previously. The
non-billable service exist as a new migration object.
Define the service types in Define Service Types. Allocate the service providers to the operational areas in
Allocate Operational Area.
See also
o
New: Point of Delivery
Changed: Communication Control.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
1.13.14 New Procedure for Payment Transactions with Third Parties

Use
There is now a new procedure, by means of which the service provider who issues the bill can assume the
role of the single provider from the customer's point of view. This also applies to billable services provided
by third parties (other service providers). The procedure enables the bill-issuing provider to buy the services
of the third party, and then charge the customer for all the services. To achieve this, we have introduce a new
payment method, which can be found in the payment class entered in the contract.
The procedure assumes that the third party creates the bills for its services itself, and then sends them
electronically to the bill-issuing service provider. When a bill is recieved, an index is automatically
generated. This ensures that the entire amount in transferred to the Financial Accounting (FI) component,
and that the paid bills are itemized for the third party. To generate the IDocs for itemization and transfer to
FI, you have to periodically start reports.
Unlike the previous procedure, convergent billing, the service provider becomes the owner of the receivable,
making a posting seperation in Contract Accounts Receivable and Payable redundant. A company code with
a contract is sufficient.
Payment transactions in convergent billing have also changed. There is now a new report for generating the
IDocs.
In the case of convergent billing, the IDocs are generated by the reportREREMITADV (processing module
for bank transfer notifications) for the bill consolidator scenario, or by the report
REREMITADV_SOLEPRV (processing module for bank transfer notifications) for the sole provider
scenario. Each report must be scheduled in the context of an FI payment run.
The transfer to FI is carried out by the report RECTHP01 (program for generating FI vendor postings) for
bill consolidator-scenario, or by RECTHP02 (program for generating FI vendor postings) for the sole
provider scenario.
Establish the necessary settings in:
o
Communication Control
Define Function Modules Permitted for Processing Events
Allocate Function Modules to Processing Events

Define a valid processing module for the processing event PAYM_POSTD. You can use the processing
event PAY_PROPOS for testing. This enables you to generate payment proposals from the
corresponding IDocs.
1.13.15 New Design for Service Providers

Use
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
The Customizing data of service providers has now been separated from the business data. This means that
the vendor number is no longer maintained in Customizing but in its own transaction. A Business partner
field has also been added. aufgenommen.
The table previously used, TEPRV is obsolete but has not been deleted. It still enables you to adjust entries to
the new procedure manually, and to establish the necessary settings in Customizing.
An XPRA automatically converts the data for the new tables ESERVPROV (service provider) and
ESERVPROVP (service provider/vendor). Following the conversion, maintain the business partners
manually if necessary. To do this choose the following menu path:
Utilities Industry -> Intercompany Data Exchange -> Service Provider -> Create/Change
Partner Data for Service Provider.
Establish the necessary settings in Define Service Provider.
1.13.16 New: Status Management for Communication in Enrollment Proce

Use
In the communication workflow for enrollment, you can now determine and maintain the business status of
the process. The system also enables you to display this in the Customer Interaction Center (CIC).
o
Define Payment Classes for Service Providers
See also
For more information, see Enrollment Process: Workflow for Communicating with Other Service Providers .
1.14 IS-U-TO
1.14.1 IS-U-TO-ARC
Tools
Archiving
1.14.1.1 New: Archiving of Customer Contacts

Use
Archiving for customer contacts consists of the following functions:
o
Archiving start, including deletion of successfully archived documents
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
You can restrict the selection of contacts to be archived by the following criteria:
-
Contact number
Number of days from contact date (at least 100)
Business partner
Contact class
Search for previously archived contacts using an archive index
Detailed display of an archived contact on the usual screen
Note that archived contacts cannot be changed or reloaded.

To use this function, choose the following IS-U menu: Utilities Indsutry -> Tools -> Customer Contacts
-> Archive Customer Contacts.
1.14.1.2 Archiving Meter Reading Results

Use
You can now
o
Archive meter reading results that are no longer needed online

The meter reading documents are deleted from databases EABL (meter reading document) and EABLG
(meter reading reason of the document) and written to the archive files. Archiving object ISU_EABL
has been created to archive meter reading results.
Display archived meter reading results

From manual monitoring, choose Call archive or menu path Goto -> Call archive to reach the List for
archive info structure.
To display the data the data that was written to the archive after an archiving run, but before deletion,
choose Evaluate from the Archive Administration: Initial Screen and then run report
RELARCH_READ_ARCHIVE_EABL (display meter reading results archive).
Restore archives
This is only valid for complete archives (not individual documents) and should therefore only be used
in exceptional cases. Therefore, you should not archive meter reading results that you still need for
current transactions (e.g. cancellation documents).
Transactions that cancel meter reading documents or make other changes to them take the current
archiving status of the meter reading document into account. As a result, these functions may not be
possible.
The Utilities industry menu contains a new menu item, Archive meter reading results under Tools ->
Data archiving -> Meter reading.
You can perform the following actions with this menu item:
o
Start preparation program

All the specified installations and their meter reading results are analyzed to see where archiving is
possible, and an index is written indicating which meter reading document number can be
archived from which date. An internal check of the possible retention period is performed.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Schedule archiving
The meter reading results that have been flagged for archiving are written to an archive file.
Schedule deletion
The meter reading results that have been written to the archive file are deleted from the
appropriate database tables.
Start evaluations
The archived meter reading results are displayed.
Manage archiving runs

An overview of the archiving runs and their status (complete, incomplete, error) is displayed.
Before you start an archiving run for the first time, you have to activate the archive info structures for the
individual document types.
To determine the retention period for the meter reading results, define the retention period for archiving
objects.
1.14.1.3 Parallel Processing of IS-U Archiving Runs

Use
You can now start archiving runs of billing documents, print documents, and budget billing schedules as
mass runs in parallel processing. This enables you to distribute the individual jobs to several processors/batch
processes, which speeds up processing.
Each of these jobs processes an assigned interval of contract accounts. The intervals are formed before the
archiving run is scheduled. The standard report performs the following activities for the respective intervals
of the respective archiving object:
o
Analyses the documents, selection of documents to be archived
Archives the documents selected by the analysis run
Deletes the archived documents (if automatic start of the deletion run has been activated in Customizing
for the archiving object).
For report details, please refer to the documentation of IS-U Archiving

Menu path:
You will find the scheduling for parallel processing for archiving in the IS-U menu under the following
paths:
o
Tools -> Data archiving -> Parallel processing -> Billing

for archiving the billing document line items and headers
Tools -> Data archiving -> Billing

for archiving the print document line items and headers, as well as budget billing schedules.
________________________________________________________________
SAP AG
Release Notes
SAP
AG
Release Notes
________________________________________________________________
Parameters:
The parameters of the archiving run are maintained under "Archiving settings" and "Logs". The parameters
are the same for all archiving objects, and correspond to the parameters in the selection screen of the
archiving report. Restrictions to the documents to be archived are not supported.
Specifically, the parameters relevant for archiving are:
In the "Archive settings" screen:
o
Comment, mnemonic comment for archiving run, to easily identify the run in archive administration
Runtime limit, applies to both the analysis and the archiving run itself. Please note, however, that any
started deletion jobs are executed to completion regardless of the runtime limit.
In the "Logs" screen

o
Log type, degree of detail of log for the individual reports
The other parameters are part of the parallel processing environment, and are described in the corresponding
documentation (insert reference!).
Administration of the archiving runs:
You still use transaction SARA to administer the archiving runs and display their logs. You can navigate to
this transaction with menu path Environment -> Archive administration within the parallel processing
tools.
________________________________________________________________
SAP AG
Release Notes

Isu En722771400837087

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Isu En722771400837087

Caricato da

Copyright:

Formati disponibili

SAP

Release Notes SAP Utilities 4.62

Copyright 2000 SAP AG. All rights reserved.

IS-U SAP Utilities

New Device Installation Functions

current transformer gro

Disaggregation of Sales and Distribution

Restrictions to IDE Functions

1 IS-U SAP Utilities

1.2 Changes to the Implementation Guide (IMG) in release 4.62

Energy Data Management

Interface to External Systems

Interface to RTP Billing

Billing Master Data

Budget Billing Plan

Contract Accounts Receivable and Payable

Customer Interaction Center

Owner Allocation has been moved from Move-In/Out to Process Execution.

Internet Self Services

IS-U Sales and Distribution Processing

Intercompany Data Exchange

1.3 Processing the gross price

Do the following to invoice gross billing documents:

1.4.1 New: Point of Delivery Service

New: Point of Delivery

New Design for Service Providers

Changed: Communication Control.

Account Assignment-Relevant Field in Contract

Project (planning element for project structure)

Account assignment to profitability segment (CO-PA)

Effects on Existing Data

1.4.3.1 New: Internal Load Profiles Can Now Be Assigned to an Instal

1.4.4.1 Point of Delivery

Deregulation point of delivery

Technical point of delivery

Effects on Existing Data

1.5.1 Device Management and Billing Now Separate

For billing (in the case of suppliers, for example)

Technical Device and Connection Data

1.5.2.1 Changed: Selection Extended for Goods Movement via Serial Nu

Selection via material number

Selection via sending plant and storage location

Extended selection by calling serial number list

The new selection options can be combined in any way desired.

1.5.2.2.1 New fields in Device Installation, Modification and Register

Validation class for independent validations

Unit of measurement for billing

1.5.2.3.1 New Transformer Type low-voltage current transformer gro (3-phase)

Processing of winding groups

Installation, removal, replacement and modification of devices:

Processing of device relationships

1.5.2.4.1 New Transformer Type low-voltage current transformer gro (3-phase)

Processing of winding groups

Installation, removal, replacement and modification of devices:

Processing of device relationships

1.5.2.5.1 New: Periodic replacement data in the device master record

1.5.2.5.2 Extened selection options for serial number selection

Device category data

Device category description

Type of certification requirement

Data from the device master record

1.5.3.1 Display of MR Results from Device Modification

1.5.3.2 Device Information Records