SAP™ for Utilities 2010 powered by SAP NetWeaver®

Master Guide SAP for Utilities

SAP for Utilities 2010 1

Master Guide

SAP™ for Utilities 2010powered by SAPNetWeaver

Using SAP® ERP 6.0 Enhancement Package5, SAP CRM 7.0 Enhancement Package 1,SAPNetWeaver 7.0 Enhancement Package2

Target Audience

System administrators

Technology consultants

Document Version 1.10 – July 12th, 2010

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

http://www.sap.com/


2 SAP for Utilities 2010

Copyright© Copyright 2010 SAP AG. All rights reserved

No part of this publication may be reproduced or transmitted in any form or for anypurpose without the express permission of SAP AG. The information contained hereinmay be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks ofMicrosoft Corporation.

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

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

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

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWinare trademarks or registered trademarks of Citrix Systems, Inc.

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

Java is a registered trademark of Sun Microsystems, Inc.

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

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAPBusinessObjects Explorer, and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of SAP AG in Germanyand other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP France in the United States and in other countries.

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

These materials are subject to change without notice. These materials are provided bySAP AG and its affiliated companies ("SAP Group") for informational purposes only,



without representation or warranty of any kind, and SAP Group shall not be liable forerrors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statementsaccompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.



Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

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

Typographic Conventions

Type Style Description

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

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and tabletitles.

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

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

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

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

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



History of ChangesThe Master Guide is regularly updated in SAP Service Marketplace atservice.sap.com/instguides.

Make sure you have the latest version of the Master Guide by checking SAP ServiceMarketplace immediately before starting the installation.

The following table provides an overview of the most important changes that weremade in the latest versions.

Master Guide Version Important Changes

1.00 (March 18th, 2010 ) Validation version

1.10 (July 12th, 2010) Covers full range of SAP for Utilities businessscenarios

Getting Started

About This Document


Contents1 Getting Started......................................................................... 91.1 About This Document .................................................................... 91.2 Related Information ...................................................................... 101.2.1 Planning Information ........................................................................... 101.2.2 Further Useful Links ............................................................................ 111.2.3 Related Master Guides ........................................................................ 111.2.4 SAP Solution Manager ......................................................................... 121.3 Important SAP Notes ................................................................... 132 SAP for Utilities - Overiew .................................................... 152.1 SAP Enhancement Packages ...................................................... 162.1.1 Enhancement Package Key Concept ................................................. 162.1.2 Key Facts About Enhancement Packages ......................................... 182.1.3 Enhancement Package Implementation ............................................. 192.2 Product Versions, Instances and Software Component

Versions ........................................................................................ 212.3 System Landscape ....................................................................... 253 Business Scenarios of SAP for Utilities ............................. 263.1 Account and Contact Management ............................................ 263.2 Auditing ......................................................................................... 273.3 Billing of Energy Products .......................................................... 283.4 Billing of Services ........................................................................ 293.5 Billing of Utility Services and Non-Energy Products ................ 303.6 Billing-Relevant Device and Measurement Data

Management ................................................................................. 313.7 Bulky (Loose) Waste Collection .................................................. 323.8 Campaign Management ............................................................... 333.9 Cleaning and Winter Services ..................................................... 343.10 Container Services ....................................................................... 353.11 Credit Risk and Collections Management.................................. 363.12 Customer Complaints Management ........................................... 373.13 Customer Interaction Management (E-Services) ...................... 383.14 Customer Interaction Management (Interaction Center) .......... 393.15 Definition of Energy Supply Products and Preparation of

Billing............................................................................................. 403.16 Definition of Grid Usage Products and Preparation of Billing . 413.17 Definition of Utility Services and Preparation of Billing ........... 423.18 Discharge System Services ........................................................ 43

Getting Started

About This Document


3.19 Disconnection and Reconnection Management ....................... 443.20 Energy Data Management – Commodity.................................... 453.21 Enhanced Contract Management for Waste and Recycling .... 473.22 Grid Access – Service Provider Agreements ............................ 483.23 Grid Operation – Inventory Management ................................... 493.24 Grid Operation – Sourcing and Procurement of Goods and

Services ......................................................................................... 503.25 Grid Operation – Workforce Management ................................. 513.26 Grid Usage Invoice Verification and Payment ........................... 523.27 Grid Usage Receivables Management and Payment

Handling ........................................................................................ 533.28 IC Management ............................................................................. 543.29 IC Marketing .................................................................................. 553.30 Invoice Verification and Payment of Services ........................... 563.31 Meter Operation – Inventory Management................................. 573.32 Meter Operation – Sourcing and Procurement of Goods and

Services ......................................................................................... 583.33 Meter Operation – Workforce Management ............................... 593.34 Meter and Device Management ................................................... 603.35 Metered Data Collection .............................................................. 613.36 Metered Data Validation and Consumption Data Calculation .. 623.37 Point of Delivery Master Data and Registration Management . 633.38 Processing Grid Usage Registration .......................................... 643.39 Receivables Management and Payment Handling .................... 653.40 Reconciliation and Closing ......................................................... 663.41 Registration for Grid Usage ........................................................ 673.42 Request Management of Technical Device Master Data .......... 693.43 Selling of Energy Supply Products (E-Services) ...................... 703.44 Selling of Energy Supply Products (Interaction Center) .......... 713.45 Selling of Energy Supply Products (C&I) ................................... 733.46 Selling of Utility Services ............................................................ 753.47 Service Connection Management ............................................... 763.48 Service Provider Agreements ..................................................... 773.49 Service and Product Planning .................................................... 783.50 Treatment and Disposal ............................................................... 793.51 Waste Asset and Container Management .................................. 803.52 Waste Flow Management ............................................................. 813.53 Weighing ....................................................................................... 824 Solution Wide Topics ............................................................ 83

Getting Started

About This Document


5 References ............................................................................. 885.1 Implementable Steps ................................................................... 885.2 Tools and Resources for Planning Your System Landscape .. 966 The Main SAP Documentation Types ............................... 100

Getting Started

About This Document


1 Getting Started1.1 About This DocumentPurposeThis Master Guide is the central starting point for the technical implementation of SAP forUtilities. You can find cross-scenario implementation information as well as scenario-specificinformation in this guide.

Use the Master Guide to get an overview of SAP for Utilities, its software units, and itsscenarios from a technical perspective. The Master Guide is a planning tool that helps you todesign your system landscape. It refers you to the required detailed documentation, mainly:

Installation guides for single software units

SAP Notes

Configuration documentation

SAP Library documentation

For a general overview of the available SAP documentation, see The Main SAPDocumentation Types.

You can find the most current information about the technical implementation ofSAP for Utilities, and the latest installation and configuration guides on SAPService Marketplace at service.sap.com/instguides.

We strongly recommend that you use the documents available here. The guidesare regularly updated.

Constraints

The business scenarios that are presented here serve as examples of how you canuse SAP software in your company. The business scenarios are only intended asmodels and do not necessarily run the way they are described here in your customer-specific system landscape. Check your requirements and systems to determinewhether these scenarios can be used productively at your site. Furthermore, werecommend that you test these scenarios thoroughly in your test systems to ensurethey are complete and free of errors before going live.

This Master Guide primarily discusses the overall technical implementation of SAP forUtilities, rather than its subordinate components. This means that additional softwaredependencies might exist without being mentioned explicitly in this document. You canfind more information on component-specific software dependencies in thecorresponding installation guides.

Getting Started

Related Information


1.2 Related Information1.2.1 Planning InformationFor more information about planning topics not covered in this guide, see the followingcontent on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Latest versions of installation and upgradeguides

service.sap.com/instguides

Installation Guide: SAP Enhancement PackageInstallation Using SAP Enhancement PackageInstaller (SAPehpi) 7.02


Troubleshoothing and Administration forInstallations Using SAPehpi (ABAP)


How to Install SAP Enhancement Package 5for SAP ERP 6.0: A Practical Guide

service.sap.com/instguides ->SAP Business Suite Applications ->SAP ERP -> SAP ERP 6.0 -> SAPEnhancement Packages forSAP ERP 6.0 -> SAP EnhancementPackage 5 for SAP ERP 6.0

How to Install SAP Enhancement Package 1for SAP CRM 7.0: A Practical Guide

service.sap.com/instguides ->SAP Business Suite Applications ->SAP CRM -> SAP Enhancement Package1 for SAP CRM 7.0 -> Install

Information about technical and releaseplanning issues on SAP components

service.sap.com/pam

General information about SAP for Utilities service.sap.com/utilities

General information about SAP NetWeaver –Business Intelligence

service.sap.com/bi

General information about SAP CustomerRelationship Management

service.sap.com/crm

SAP Business Maps – information aboutapplications and business scenarios

service.sap.com/businessmaps

Sizing, calculation of hardware requirements –such as CPU, disk and memory resource –with the Quick Sizer tool

service.sap.com/quicksizer

Released platforms and technology-relatedtopics such as maintenance strategies andlanguage support

service.sap.com/platforms

To access the Platform Availablity Matrixdirectly, enter service.sap.com/pam.

Network security service.sap.com/securityguide

High Availability service.sap.com/ha

Performance service.sap.com/performance

Information about Support Package Stacks,latest software versions and patch levelrequirements

service.sap.com/sp-stacks

Getting Started

Related Information


Information about Unicode technology service.sap.com/unicode@sap

Documentation on SAP Help Portal help.sap.com/

1.2.2 Further Useful LinksThe following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service Marketplace

Information about creating error messages service.sap.com/messages

SAP Notes search service.sap.com/notes

SAP Software Distribution Center (softwaredownload and ordering of software)

service.sap.com/swdc

SAP Online Knowledge Products (OKPs) –role-specific Learning Maps

service.sap.com/rkt

1.2.3 Related Master GuidesThis Master Guide is based on Master Guides for cross-industry applications. You can findmore information about the relevant applications in the following documents:

Title Location

SAP ERP 6.0 service.sap.com/erp-inst SAPERP 6.0 Installation Master Guide forSAP ERP 6.0

SAP ERP 6.0 Enhancement Package 5 service.sap.com/erp-inst SAPERP 6.0 SAP Enhancement Packagesfor SAP ERP 6.0 SAP EnhancementPackage 5 for SAP ERP 6.0 MasterGuide SAP Enhancement Package 5 forSAP ERP 6.0

SAP CRM 7.0 service.sap.com/crm-inst SAPCRM 7.0 Plan Master Guide SAPCRM 7.0 SR1

SAP CRM 7.0 Enhancement Package 1 service.sap.com/crm-inst SAPCRM 7.0 SAP Enhancement Packages forSAP CRM 7.0 Plan Master Guide SAPCRM 7.0 Enhancement Package 1

SAP NetWeaver 7.0 service.sap.com/instguides SAPNetWeaver SAP NetWeaver 7.0 (2004s)

Installation Master Guide – SAPNetWeaver 7.0

SAP NetWeaver 7.0 Enhancement Package 2 service.sap.com/instguides SAPNetWeaver SAP NetWeaver 7.0 (2004s)

Installation Master Guide – SAPNetWeaver 7.0

Getting Started

Related Information


1.2.4 SAP Solution ManagerSAP provides the SAP Solution Manager as the highly recommended platform to efficientlysupport the implementation of your solution. Using SAP Solution Manager will significantlyaccelerate the implementation process and help you to achieve your business goals. At thesame time, SAP will be able to deliver Support Services based on the business scenariosdesigned and documented in SAP Solution Manager. Implementation content for yoursolution may further accelerate the implementation process. For information about availabilityof content specifically tailored to your solution, see SAP Service Marketplace underservice.sap.com/solutionmanager.

In this Master Guide, the installation of software components required for eachbusiness scenario is described on the basis of SAP Business Suite 7 releases.If you want to implement different realization possibilites for a specific business,please, check the availability of the business scenario for the according releasecombination in the Software Lifecycle Manager.

Getting Started

Important SAP Notes


1.3 Important SAP NotesThis section contains important SAP Notes for SAP for Utilities.

You must read the following SAP Notes before you start the installation. These SAP Notescontain the most recent information on the installation, as well as corrections to theinstallation documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find onSAP Service Marketplace at service.sap.com/notes.

SAP Note Number Title Description

838003 Industry Add-Onsintegrated in SAP ECC 600

Provides the names of theformer IS add-ons that havebeen integrated into SAP ERPCentral Component 6.0 andthat are available as businessfunction sets.

This note is updated on aregular basis.

856284 SAP ERP CentralComponent 6.0:Inst./Upgrad andarchitecture

Information about softwarearchitecture of SAP ERPCentral Component 6.0 (SAPECC 6.0) and its installation orupgrade.

1325776 Enhancement Package 5for SAP ERP – requiredSupport Packages

Information on installationprerequisites for SAPEnhancement Package 5 forSAP ERP 6.0: RequiredSupport Package Stacks

849887 SAP ERP 6.0: SupportPackage Stacks Releaseand Info Note

Contains a list of all SAP ERP6.0 Release and InformationNotes (RIN) that have beenissued for SAP ERP 6.0.

This note is updated every timea new Release and InformationNote is issued for SAP ERP6.0.

1323537 Release Info SAPEnhancement Package 5for SAP ERP 6.0

The SAP ERP 6.0Enhancement Package 5complements the SAP ERP 6.0release in a number of focusareas.

881842 Release strategy for SAPUtilities as of ECC 6.0

Information about theactivation and upgrade of theSAP Utilities industry extension

1298878 Installation ofEnhancement Package 5for SAP ERP 6.0

Information about how to installEnhancement Package 5 forSAP ERP 6.0

Getting Started

Important SAP Notes


SAP Note Number Title Description

855534 Dual Stack and SAPBusiness Suite 7

Information on using both SAPBusiness Suite ABAP and JavaComponents in your systemlandscape

Embedded SAP NetWeaverComponents in SAP ERP 6.0.

1162804 FG_PART: Timedependency of thebusiness partner in IS-U

Problems occur in IS-U forvarious functions (for example,move-in and move-out) inconnection with the businesspartner.

824757 Dependencies betweenSAP ERP component lists

The note is relevant only if yourequire component informationfor processes and role-basedWork Centers withdependencies to other processor role-based Work Centers.

1179512 Release restrictions forSCM 7.0

This note provides informationabout release restrictions forSCM 7.0.

1003900 TREX 7.1: Central Note Information about installingSAPNetWeaver TREX 7.1 andlinks to further information

1093900 Upgrade from TREX 7.0 toTREX 7.1

Information about how toupgrade from SAP NetWeaverTREX 7.0 to TREX 7.1

1249465 TREX 7.1: Installing TREXfor Embedded Search

Information about installingSAPNetWeaver TREX 7.1

1123452 FG_PART: LimitationBusiness Partner in IS-Uund FS-BP

You use a Financial Services(FS) application and Utilities inone system. When you do this,various problems occur inconnection with the businesspartner.

SAP for Utilities - Overiew

Important SAP Notes


2 SAP for Utilities - OveriewSAP for Utilities is a portfolio of solutions that support all of the critical billing and CRMbusiness processes of electricity, gas, and water utilities in regulated and deregulatedmarkets. It includes solutions that address the industry-specific needs of transmission,transportation, distribution, and retail utilities.

In the SAP for Utilities portfolio, SAP offers the SAP Business Suite family of businesssolutions, the SAP xApps portfolio of packaged composite applications, SAP solutions forsmall and medium-sized businesses, other specialized applications and packaged solutions,and services from SAP Customer Services Network.

This SAP for Utilities Master Guide provides a central starting point for the technicalimplementation of the following business scenarios of SAP for Utilities:

Account and Contact Management

Auditing

Billing of Energy Products

Billing of Services

Billing of Utility Services

Billing-Relevant Device and Measurement Data Management

Bulky (Loose) Waste Collection

Campaign Management

Cleaning and Winter Services

Container Services

Credit Risk and Collections Management

Customer Complaints Management

Customer Interaction Management (E-Services)

Customer Interaction Management (Interaction Center)

Definition of Energy Supply Products and Preparation of Billing

Definition of Grid Usage Products and Preparation of Billing

Definition of Utility Services and Preparation of Billing

Discharge System Services

Disconnection and Reconnection Management

Energy Commodity Trading

Energy Data Management – Commodity

Enhanced Contract Management for Waste and Recycling

Grid Access – Service Provider Agreements

Grid Operation – Inventory Management

Grid Operation – Sourcing and Procurement of Goods and Services

Grid Operation – Workforce Management

Grid Usage Invoice Verification and Payment


SAP Enhancement Packages


Grid Usage Receivables Management and Payment Handling

IC Management

IC Marketing

Invoice Verification and Payment of Services

Meter Operation – Inventory Management

Meter Operation – Sourcing and Procurement of Goods and Services

Meter Operation – Workforce Management

Meter and Device Management

Metered Data Collection

Metered Data Validation and Consumption Data Calculation

Point of Delivery Master Data and Registration Management

Processing Changes of Point of Delivery and Grid Usage Registration

Receivables Management and Payment Handling

Reconciliation and Closing

Registration for Grid Usage

Request Management of Technical Device Master Data

Selling of Energy Supply Products (E-Services)

Selling Energy Supply Products (Interaction Center)

Selling of Energy Supply Products (Key Account Management)

Selling of Utility Services

Service Connection Management

Service Provider Agreements

Service and Product Planning

Treatment and Disposal

Waste Asset and Container Management

Waste Flow Management

Weighing

2.1 SAP Enhancement Packages2.1.1 Enhancement Package Key ConceptWe have adapted our major release strategy to better fit your adoption cycle. To ensure thatyou benefit from new developments and innovations while minimizing the impact on your coreoperational systems, SAP uses enhancement packages to speed up the delivery of newfunctions.

With SAP enhancement packages, you can install and activate new functions depending onyour business needs without having to perform a system upgrade.




You can selectively implement the new functions and activate the software upon businessdemand. As a result, you can isolate the impact of software updates and make new functionsavailable faster due to shortened test cycles.

ImplementationThere are three different scenarios to implement an enhancement package:

Installation of an enhancement package on an existing SAP system

New installation of an SAP system including an enhancement package

Upgrade of an SAP system including an enhancement package

The installation process of enhancement packages consists of two different steps:

Technical installation of an enhancement package

Activation of new functions using the switch framework technology

You have a choice on both levels – installation and activation. You do not need to install a fullenhancement package. Instead, you can update the software components that are related tothe functional enhancements you want to use.

From a business point of view, functional enhancements are grouped into business functions(BFs). The technical installation of the business functions does not change the systembehavior. The new functions are available in the system, but are not active. After theinstallation, no user interface or process change takes place. You must explicitly activate newfunctions so that they become visible in the system. As a result, changes are predictable andthere are no side effects as only the activated areas change.

With the switch framework technology (transaction SFW5), it is possible to control theactivation of new SAP objects in ABAP-based SAP systems. The activation process triggersa background job that automatically performs all changes in the SAP system.

You cannot reverse a business function once it is activated.

After you have activated a business function, you can see the changes and newdevelopments in the SAP system, for example:

Menu entries

New screens

New fields on the application user interfaces

IMG activities required for the implementation

New table entries in Customizing tables and system tables

You can create a transport request with the current settings of the switch framework. You cancheck functional changes and the impact of an activated business function in advance in thebusiness function documentation.

Test the installation and activation on a sandbox system.

MaintenanceSAP enhancement packages have Support Packages of their own that are equivalent to theSupport Package versions of the underlying SAP system. You must install the enhancementpackage in combination with the latest available Support Package stack. This approachreduces installation, modification adjustment, and testing effort. Using this strategy, you can




install SAP enhancement packages as a normal maintenance activity together with SupportPackage stacks.

An enhancement package requires a specific Support Package stack level in the sourcerelease SAP system. If the SAP system is on a lower Support Package stack level, allrelevant Support Package stacks are automatically included into the download queue, as wellas the latest available Support Packages for the enhancement package.

ToolsThe enhancement package installation requires the following tools:

SAP Solution Manager Maintenance Optimizer

Installation or upgrade tools (depending on your scenario)

The SAP Solution Manager Maintenance Optimizer (accessible from the ChangeManagement work center) supports the download of a consistent queue that includes allnecessary Support Packages and enhancement packages. In addition, SAP SolutionManager calculates a valid import queue for the selected SAP system and generates theenhancement package stack configuration file that you require for the installation.

For the new installation of an SAP system including enhancement package as well as for theupgrade of an SAP system to a higher release including an enhancement package, you usethe standard installation and upgrade tools (SAPinst, SAPup and SAPJup). To install anenhancement package on an existing SAP system, you use the SAP Enhancement PackageInstaller (SAPehpi). It allows enhancement packages to be installed with reduced downtime.SAPehpi uses the shadow system installation strategy, a well-known feature in the upgradetechnology.

2.1.2 Key Facts About Enhancement PackagesThe following list summarizes important facts about the enhancement package concept andrecommended approaches:

Install only selected parts of the enhancement package. The selection is driven bythe functional need from a business point of view.

You cannot mix the installation of different enhancement package versions in yourABAP-based SAP system. You can have just one enhancement package version inthe SAP system.

SAP enhancement packages are cumulative, meaning that each new enhancementpackage includes new innovations of its own as well as all innovations delivered withprior packages.

We recommend installing the latest available enhancement package version.

Install enhancement packages and Support Packages in one single step (thisincludes the preconditioned Support Packages).

SAP enhancement packages have Support Packages of their own that are equivalentto the Support Package versions of the underlying SAP system.

SAP enhancement packages have the same maintenance period as the underlyingcore application.

The installation of an enhancement package is irreversible.

As long as you do not activate a business function, the installation of anenhancement package has no impact on existing business processes or userinterfaces.




You can only activate business functions in ABAP-based systems, not in Java-basedSAP systems.

The activation of most business functions and extension sets is irreversible. Only asmall number of business functions is reversible.

Test the installation process and activation of new functions in advance on a sandboxsystem. Ensure that you evaluate the runtime and the SAP system behavior, itsdependencies and impacts. Make sure that your SAP system is free of errors beforegoing live.

2.1.3 Enhancement Package ImplementationIn the following, you will find an overview of the steps involved in the three differentenhancement package implementation scenarios.

ProcessEnhancement Package Installation in an Existing SAP SystemProcess

1. You find out, which of the new functions are interesting for your business.

2. You analyze the landscape dependencies.

3. You identify the relevant installable parts of the enhancement package.

4. You make sure that you have set up your SAP Solution Manager system for thedownload of packages, and that you have configured the Maintenance Optimizer.

5. You download the installation queue.

6. You perform the installation.

7. You analyze the impact of the business function activation with the dependencyanalyzer and the impact analyzer (transaction SWF5).

8. You activate the business functions.

9. You perform additional Customizing, if necessary.

10. You test the new functions.

Tools

SAP Solution Manager Maintenance Optimizer (mandatory)

SAP Enhancement Package Installer (SAPehpi)

Switch framework with Dependency Analyzer and Impact Analyzer in SAP SolutionManager (transaction SWF5)

New Installation of an SAP System with Enhancement PackagesProcess

1. You install the SAP system.

The installation of SAP ERP 6.0 including enhancement package 5 comprises thetechnical usage Central Applications. The installation of the technical usage CentralApplications implies that the system is ready for use without installing any furthertechnical usages. Of course, you can optionally install additional technical usages.

2. If you want to install further technical usages:






3. You download the installation queue.

4. You perform the installation.

5. You activate the business functions using the switch framework (transactionSWF5).

3. You perform the Customizing for the SAP system.

4. You test the SAP system.

Tools

Standard Installation tool SAPinst

SAPehpi or SAINT to install additional technical usages

In this scenario, you can use transaction SAINT for installing additional technicalusages, because software component SAP_APPL 6.05 is already present inyour system (part of technical usage Central Applications). This is a prerequisitefor using SAINT.

Switch framework with Dependency Analyzer and Impact Analyzer in SAP SolutionManager (transaction SWF5)

Upgrade to an SAP System Including an Enhancement PackageInstallationCustomers who are upgrading from a lower release to an SAP system for whichenhancement packages are available can include parts of enhancement packages into theupgrade process.

The use of SAP Solution Manager Maintenance Optimizer is mandatory if youwant to include enhancement packages in your release upgrade.

Process1. You plan the upgrade to the new release. Decide which parts of the enhancement

package you want to include into the upgrade procedure before you start with theupgrade.



4. You download the required parts of enhancement packages and Support Packagesas well as the enhancement package stack configuration file.

5. You perform the upgrade including parts of the enhancement package.The upgrade program asks if you want to include parts of an enhancement packageinto the upgrade process.

6. You activate the business functions using the switch framework (transaction SWF5).

7. You perform the delta Customizing for the SAP system.

8. You test the SAP system.


Product Versions, Instances and Software Component Versions


Tools

Standard upgrade tools (SAPup and SAPJup)

SAP Solution Manager Maintenance Optimizer

2.2 Product Versions, Instances andSoftware Component Versions

The following table gives an overview of the SAP product versions, instances, and softwarecomponent versions required for SAP for Utilities business scenarios and the correspondinginstallation guides.

Before you commence installation, it is imperative that you know whichcomponents and which release of these components are required for thebusiness scenarios you plan to use. It is not recommended to install allcomponents as a matter of course. Only install those components that arerequired for the business scenarios you will use.

For more information about the required components, review the softwarecomponent matrix for each business scenario.




Product Version – Software InstanceComprised Software Components, Add-Ons and Instances

Detailed Information

SAP ERP 6.0 Enhancement Package 5 – Utilities/Waste&Recycl./TelcoInstallation of:

SAP ERP 6.0 SR4 – SAP ECC Server

IS-UT 605

FI-CA 605SAP APPL 6.05

EA-APPL 605

based on SAP NetWeaver 7.02 –Application Server ABAP

For detailed information, seeservice.sap.com/erp-inst SAP ERP6.0 Installation SAP ERP 6.0 SR4 –Installation Documentation

Activation of Business Function Set Utilities forSAP ECC Industry Extension Utilities,Waste & Recycling 6.0: For detailedinformation, see the SAP ERP 6.0 MasterGuide at service.sap.com/erp-inst

For detailed information, seeservice.sap.com/instguides SAPNetWeaver 7.0 (2004s) Installation 2 –Installation SAP NetWeaver Systems SAPNetWeaver 7.0 SR <> - Installation Guides

SAP NetWeaver 7.0 – Business Intelligence (BI)Installation of:

SAP Web AS 7.00 – SAP Web AS ABAP

Enhancement Package 2

Installation of BI CONT 7.05

For detailed information, seeservice.sap.com/instguides SAPComponents SAP Basis SAP BasisInstallation on <OperatingSystem>:<Database System>.

For detailed information on the SAPNetWeaver 7.0 - Business Intelligence (BI)components, see the Master Guide SAPNetWeaver atservice.sap.com/instguides SAPNetWeaver SAP NetWeaver 7.0 (2004s) Installation.

See SAP Note ??? BI_CONT 7.05:Information about the installation and upgrade.

SAP NetWeaver 7.0 – Application Server JavaInstallation of SAP NetWeaver 7.0 –Application Server Java

For detailed information on the SAPNetWeaver 7.0 - Application Server Javacomponents, see the Master Guide SAPNetWeaver atservice.sap.com/instguides SAPNetWeaver SAP NetWeaver 7.0 (2004s) Installation.






SAP NetWeaver 7.0 – Content ServerInstallation of:

SAP Content Server 6.40For detailed information, seeservice.sap.com/instguides SAPNetWeaver SAP NetWeaver 7.0 (2004s) Installation Installation Standalone Engines

Installation SAP Content Server 6.40 on<Operating System>.

SAP NetWeaver 7.0 – Process Integration/XI ContentInstallation of:

XI Content IS-UT 605For detailed information, seeservice.sap.com/erp-inst SAPNetWeaver SAP NetWeaver PI 7.2Installation 2 – Installation – SAPNetWeaver Systems Installation Guides –SAP NetWeaver PI 7.2

SAP EHP1 for SAP NetWeaver 7.0 – Adobe Document Services

SAP EHP1 for SAP NetWeaver 7.0 – Search and Classification (TREX)Installation of:

SAP NetWeaver 7.01 – Search andClassification (TREX)TREX 7.01

For detailed information, seeservice.sap.com/installnw70 SAPNetWeaver 7.0 (2004s) Installation 3 –Installation – Standalone EnginesInstallation – SAP NetWeaver Search andClassification TREX

SAP CRM 7.0 – CRM Application Server ABAPInstallation of:

SAP Web AS 7.01 – SAP Web AS ABAP

SAP CRM ABAP 7.0

SAP AP 7.00SAP WEB UIF 7.0

For detailed information, see:

service.sap.com/installnw70 SAPNetWeaver 7.0 (2004s) Installation 2 –Installation SAP NetWeaver Systems SAPNetWeaver 7.0 incl. EHP2 – InstallationGuides

For detailed information, see:service.sap.com/crm-inst SAP CRM7.0 Install SAP CRM 7.0 – InstallationDocumentation






SAP CRM 7.0 – CRM Application Server JavaInstallation of:

SAP Web AS 7.01 – SAP Web AS JavaFor detailed information, seeservice.sap.com/installnw70 SAPNetWeaver 7.0 Installation 2 –Installation SAP NetWeaver Systems SAPNetWeaver 7.0 SR<> - Installation Guides

service.sap.com/crm-inst SAP CRM7.0 Install SAP CRM 7.0 – InstallationDocumentation

SAP ERP 6.0 Enhancement Package 5 – SAP Utility Customer E-ServicesInstallation of:

SAP IS-U/UCES – JSP Frontend

SAP ERP 6.0 Enhancement Package 5 – SAP FSCM – Biller DirectInstallation of:

SAP ERP 6.0 – SAP ECC Server

Financial Supply Chain Management –Biller Direct 6.05

Based on:

SAP Web AS 7.01 – SAP Web AS JAVA

For detailed information, seeservice.sap.com/erp-inst SAP ERP6.0 Installation Installation SAP BillerDirect

For detailed information, seeservice.sap.com/instguides SAPNetWeaver 7.02 Installation 2 -Installation - SAP NetWeaver SystemsSAP NetWeaver 7.0 SR<> - InstallationGuides


System Landscape


2.3 System LandscapeThe following diagram provides an overview of a possible system landscape for SAP forUtilities.

ECC – Host

RDBMS

CRM Host

TREX Host

IPC Host

IPC 5.0

Portal Host

FSCM - Host

SAP NetWeaver7.02 ApplicationServer ABAP

SAP CRM 7.01 – CRMServer

SAP NetWeaver7.02 – SAPContent Server

RDBMS

Content Server Host

Based onSAP NetWeaver7.0 – Enterprise Portal

XI Host

SAP NetWeaver 7.02 –Process Integration (PI/XI)

XI Content FINBASIS 700

XI Content FI-CA 700

BI - Host

RDBMS

Based onSAPNetWeaver 7.02 –Application ServerABAP

RDBMS

SAP NetWeaver7.01 – Searchand Classif.(TREX)

Based onSAP NETWEAVER 7.02 –AS ABAP

SAP ERP 6.0 (EHP5) –SAP FSCM-Biller Direct

RDBMSRDBMS

RDBMS

SAP ERP 6.0 (EHP5) – SAP ECC

We strongly recommend that you use a minimal system landscape for test anddemo purposes only. For performance, scalability, high availability, and securityreasons, do not use a minimal system landscape as your production landscape.

Business Scenarios of SAP for Utilities



3 Business Scenarios of SAP forUtilities

3.1 Account and Contact ManagementOverviewYou can use account and contact management to manage and maintain your accounts andcontacts.

In addition to master data maintenance, the integration of transaction data such as businesstransactions and contacts provides you with an overview of the most important data, as wellas quick access to and easy maintenance of all the information on your account or contact.

In the context of account and contact management, accounts can be understood ascompanies or organizations, but can also be individuals and groups that have a relationshipwith your company as customers or prospects.

Account and contact management is particularly useful for sales employees and managerswho work only occasionally in the system in order to carry out preparatory and follow-upactivities for their sales calls.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Account and Contact Management.

InstallationSequence

Product Version - Instance Optional

1 SAP CRM 7.0 Enhancement Package 1 – CRMApplication Server ABAP

2 SAP ERP 6.0 Enhancement Package 5–Utilities/Waste&Recycl./Telco

x

3 SAP NetWeaver 7.0 – Business Intelligence 7.05 x

4 SAP CRM 7.0 Enhancement Package 1 – SAPGroupware Connector

x

For more information about the installation of these instances, see Product Versions,Instances and Software Component Versions [page 11].

Further InformationThe following documents provide more information about Account and Contact Management.

Content LocationScenario Description See the documentation in SAP Solution Manager

Configuration Documentation See the documentation in SAP Solution Manager

Scenario Security Guide For more information, see SAP Service Marketplace atservice.sap.com/securityguide


Auditing


3.2 AuditingOverviewYou can use this business scenario to extract tax-relevant data from the productive system toSAP Utilities. This is used for auditing by the tax authorities according to the Germanprinciples for data access and verifiability of digital documentation.

Due to the mass volume of data in Contract Accounts Receivable and Payable, it is notpossble keep this data in the productive system for the ten years that you are legally obligedto retain data. Therefore, you can extract the data to files before it is archived. If you createthe extract files in AIS format, you can transfer them directly to the auditor for evaluation.

If an evaluation system exists for auditing, you can import the files with the extracted data tothat system, where you can manage, display, select the data, and extract it back to the files.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Auditing.



1 SAP ERP 6.0 – SAP ECC Server

You can also implement this scenario/process withSAP enhancement package 5 for SAP for Utilities.


Further InformationThe following documents provide more information about Auditing.





Billing of Energy Products


3.3 Billing of Energy ProductsOverviewYou, in the role of the Billing Agent, can use this scenario to execute billing and invoicing ofenergy products for all kinds of customer groups including commericial and industrial (C&I)and residential customers. The billing agent’s execution tasks comprise setting up andmanaging billing master data as well as budget billing.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Billing of Energy Products:



1 SAP ERP 6.0 Enhancement Package 5 –Utilities/Waste&Recycl./Telco

2 SAP NetWeaver 7.0 – Business Intelligence 7.05

3 SAP BW 7.02

4 SAP Enhancement Package 2 for SAP NetWeaver7.0


Further InformationThe following documents provide more information about Billing of Energy Products:





Billing of Services


3.4 Billing of ServicesTechnical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Billing of Services:




2 SAP NetWeaver 7.0 Enhancement Package 1 –Business Intelligence (BI)


Further InformationThe following documents provide more information about Billing of Services:





Billing of Utility Services and Non-Energy Products


3.5 Billing of Utility Services and Non-Energy Products

OverviewYou, in the role of the Billing Agent, can use this business scenario to execute billing andinvoicing of services for various customer groups including commercial and industrial (C&I)and residential customers. The Billing Agent’s execution tasks comprise setting up andmanaging billing master data. Services can be executed by the retailer, the distributor orother market participant. Services are defined by the Balance Supplier, sold by the marketrole responsible for selling services (Customer Service Responsible) and billed by the BillingAgent. The billing rules are also provided by the Balance Supplier.

Services to be billed include street lights (unmetered), insurance, energy-saving services,and technical grid or service connection services.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Billing of Utility Services:




2 SAP NetWeaver 7.0 Enhancement Package 1 –Business Intelligence (BI)


Further InformationThe following documents provide more information about Billing of Utility Services:





Billing-Relevant Device and Measurement Data Management


3.6 Billing-Relevant Device andMeasurement Data Management

OverviewYou can use this business scenario to request and receive billing-relevant device andmeasurement data. You can request device information from the market participant acting asmeter administrator and store this information. The meter administrator also informs you ifdevice data has changed. Interfaces to various external systems allow you to receivemeasurement data that you can validate and store. For non-periodic readings, you sendrequests for meter readings to the relevant market participant.

Technical System LandscapeThe following SAP product versions and software instances are required for the technicalimplementation of Billing-relevant Device and Measurement Data Management:





3 SAP NetWeaver 7.0 Enhancement Package 2 x


Further InformationThe following documents provide more information about Billing-Relevant Device andMeasurement Data Management:





Bulky (Loose) Waste Collection


3.7 Bulky (Loose) Waste CollectionOverviewPublic and private waste disposal companies can use this business scenario to createcommon waste disposal services for commercial and municipal customers. The collection ofbulky and loose waste includes creating waste disposal orders for bulky waste, manualplanning and disposition, outputting waste disposal orders, and confirming completed orders.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Bulky (Loose) Waste Collection:



1 SAP Enhancement Package 5 for SAP ERP 6.0 –Utilities/Waste&Recycl./Telco




Further InformationThe following documents provide more information about Bulky (Loose) Waste Collection:





Campaign Management


3.8 Campaign ManagementSee the SAP CRM 7.0 Enhancement Package 1 Master Guide.


Cleaning and Winter Services


3.9 Cleaning and Winter ServicesOverviewYou can use this business scenario to create different types of cleaning and winter services.You can define categories of cleaning objects and hierarchies of cleaning objects. Thelocation of the objects is described using addresses or geocoordinates. The system alsoallows you to define cleaning methods and levels of priority for winter services.

Cleaning objects are grouped by properties, and are allocated to a customer via a contract.Using this scenario, you can create, plan, output, and confirm periodic and aperiodic wastedisposal orders for cleaning objects defined, and can then bill the customer.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Cleaning and Winter Services:


Product Version – Instance Optional



3 SAP NetWeaver 7.0 usiness Intelligence 7.04 x


Further InformationThe following documents provide more information about Cleaning and Winter Services:





Container Services


3.10 Container ServicesOverviewThis business scenario provides you with the business processes required for providing,collecting, and changing containers, from creating a periodic or aperiodic waste disposalorder to confirming orders using mobile devices (such as on-board units).

This business scenario includes the following processes:

Periodic Waste Disposal Order

Aperiodic Waste Disposal Order

Manual Planning and Dispatching of Waste Disposal Orders

Graphical Planning and Handling of Waste Disposal Orders

Outputting Waste Disposal Orders

Executing Waste Disposal Orders

Confirming Waste Disposal Orders

Confirming Waste Disposal Orders Using Mobile Devices

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Container Services.







Further InformationThe following documents provide more information about Container Services.





Credit Risk and Collections Management


3.11 Credit Risk and CollectionsManagement

OverviewIn this business scenario, you can segment your customers according to their risk. You cancontrol and continually monitor sales and service processes, and respond immediately whenexceptional situations arise. The scenario takes account of business rules, customer history,the collection specialist's skills and responsibilities, and the capacity available, all of whichcontributes to the flexibility of your customer processing in Collections Management.

Collection specialists have a detailed overview of their customers and access to all therequired tools and functions for the necessary measures. Heads of department can track theprogress of Collections Management at all times and, if necessary, take action.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Credit Risk and Collections Management.




2 SAP ERP 6.0 Enhancement Package 5 – BillerDirect - FSCM



5 SAP Waste and Recycling Applications byProloga 2.0 – SAP ECC Server Add-On

x


Further InformationThe following documents provide more information about Credit Risk and CollectionsManagement.





Customer Complaints Management


3.12 Customer Complaints ManagementOverviewYou can use this business scenario to process and resolve process complaints regardingcustomers' energy supply, service issues, or disputes by goodwill actions, such as issuingcredit vouchers, rebates, coupons, refunds, and substitutions. This also includes the routingof complaints about services or products related to different market roles (for example, houseconnection from the distributor). The business process Complaints and Returns Analysisprovides insights about the entire business scenario.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Customer Complaints Management



1 SAP ERP 6.0 – SAP ECC Server

You can also implement this scenario/processwith SAP enhancement package 5 for SAP forUtilities.


3 SAP NetWeaver 7.0 Enhancement Package 2 –Adobe Document Services

4 SAP NetWeaver 7.0 Enhancement Package 2 -Search and Classif. (TREX)



Further InformationThe following documents provide more information about of Customer ComplaintsManagement.





Customer Interaction Management (E-Services)


3.13 Customer Interaction Management (E-Services)

OverviewYou can use this business scenario to address the utility-specific processes that are madeavailable in the Internet portal or Internet presence of a typical utility retailer. This includesmany variations of the deregulated contract management process, entering meter readings,billing and financial inquiries, customer requests for disconnection and reconnection, andother supporting processes associated with the maintenance of customer or master data.

Technical System LandscapeThe following SAP product versions and software instances are required for the technicalimplementation of Customer Interaction Management (E-Services)




2 SAP NetWeaver 7.0 Enhancement Package 1 –Application Server ABAP

Alternating

3 SAPNetWeaver 7.2 – SAP Utility Customer E-Services

Alternating

4 SAPNetWeaver 7.0 – SAP Utility Customer E-Services

Alternating


Further InformationThe following documents provide more information about of Customer InteractionManagement (E-Services)





Customer Interaction Management (Interaction Center)


3.14 Customer Interaction Management(Interaction Center)

OverviewYou can use this business scenario to address the utility-specific processes that used in thecall center of a typical utility retailer. This includes various processes that manage supplycontracts as well as packages of contracts and other products or programs. It also includesprocesses to enter meter readings, handle billing and financial inquiries, manage customerrequests for disconnection and reconnection, and other supporting processes associated withthe maintenance of customer or master data.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Customer Interaction Management (Interaction Center)





3 SAP CRM 7.0 Enhancement Package 1 – CRMApplication Server Java

x



6 SAP NetWeaver 7.0 Enhancement Package 2 –Search and Classif. (TREX)

7 SAP NetWeaver 7.0 Enhancement Package 2 –Process Integration (PI/XI)

x


Further InformationThe following documents provide more information about of Customer InteractionManagement (Interaction Center.)





Definition of Energy Supply Products and Preparation of Billing


3.15 Definition of Energy Supply Productsand Preparation of Billing

OverviewYou can use this business scenario to define and prepare for billing, invoicing and thesubsequent cash process.s

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Definition of Energy Supply Products and Preparation of Billing.






Further InformationThe following documents provide more information about Definition of Energy SupplyProducts and Preparation of Billing.





Definition of Grid Usage Products and Preparation of Billing


3.16 Definition of Grid Usage Products andPreparation of Billing

OverviewYou, in your role of the Grid Access Provider, can use this business scenario to prepare thebilling of grid usage products. You define, manage, and publish grid usage tariffs in order toguarantee non-discriminatory grid access. These grid usage tariffs can be based onmeasurement data or capacity data. Grid usage is often billed on the basis of meter readings.Capacity data can be based on the demand of an electric cable or the capacity of a gaspipeline connecting a house with a grid.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Definition of Grid Usage Products and Preparation of Billing.






Further InformationThe following documents provide more information about Definition of Grid Usage Productsand Preparation of Billing.





Definition of Utility Services and Preparation of Billing


3.17 Definition of Utility Services andPreparation of Billing

OverviewYou can use this business scenario to specify and prepare services for billing, invoicing, andthe subsequent cash process.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Definition of Utility Services and Preparation of Billing.






x


Further InformationThe following documents provide more information about Definition of Utility Services andPreparation of Billing.





Discharge System Services


3.18 Discharge System ServicesOverviewThis business scenario includes business processes such as those required for emptyingcontainers (for example, household trashcans), creating a periodic or aperiodic wastedisposal order and confirming orders using mobile devices (for example, on-board units).

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Discharge System Services.







Further InformationThe following documents provide more information about Discharge System Services.





Disconnection and Reconnection Management


3.19 Disconnection and ReconnectionManagement

OverviewThe Disconnection and Reconnection Management scenario is applicable to the BalanceSupplier Party, a market role or department of a (energy) supplier.

You can use this business scenario to manage and process the disconnection andreconnection requests.

New state-of-the-art smart meter technology, Advanced Meter Infrastructure (AMI), allows abi-directional information flow between an ERP system and a smart meter. Smart meters, foruse by commercial and industrial (C&I) customers as well as household customers, can bedisconnected and reconnected automatically, for example, if energy theft is detected.

You can use this business scenario in order to handle disconnection and reconnectionprocesses in either an AMI or a non-AMI environment. This business scenario allows thehandling of disconnection and reconnection processes as well as triggering communicationbetween SAP for Utilities and an MDUS (Metered Data Unification and Synchronization)system using SAP NetWeaver PI.

Using automated communication to a single smart meter, utilities can handle the underlyingprocesses in a more efficient and cost-saving manner compared to processes where fieldservice representatives have to perform disconnection or reconnection manually at the endcustomer site. Furthermore, disconnection and reconnection processes can be triggeredmore often.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Disconnection and Reconnection Management:





x


4 SAP NetWeaver 7.0 – Process Integration (PI/XI) x


Further InformationThe following documents provide more information about Disconnection and ReconnectionManagement.







3.20 Energy Data Management –Commodity

OverviewThis business scenario is applicable to the Balance Responsible Party, a market role ordepartment of an energy supplier.

You can use this business scenario to manage and process utilities time series data, such asload profiles of different customer segments, forecasts and schedules.

State-of-the-art smart meter technology, such as AMI (Advanced Meter Infrastructure),provides utilities time series data of high granularity and requires the processing of increasedvolumes of load profiles. Load profiles of high granularity could, for example, be used inforecasting to improve schedules of a supplier. Therefore, suppliers can now base theirschedules – dependent on the accuracy to be achieved – either on synthetic profiles or loadprofiles for customer segments such as residential customers or small and medium-sizedbusinesses.

This business scenario covers the following areas:

Energy Data RepositoryThe Energy Data Repository is a central, company-wide database that stores allenergy-related data of the supplier. The Energy Data Repository was designed tostore utilities time series data of different types being characterized by constant timeintervals (for example, measured values for interval sizes such as 15, 30 and 60minutes, or one day). However, meter readings and consumption-related factors arealso kept in the database. Load profile data is validated, supervised, and changedwithin the Energy Data Repository.

Forecasting and Schedule ManagementYou can use this scenario to automatically create and provide energy forecasts andschedules.

Load profile data basis for BillingThis scenario provides the data basis to create energy supply bills based on differenttypes of load profiles (for example, measured load profiles).

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Energy Data Management - Commodity:





3 SAP NetWeaver 7.02 – Process Integration (PI/XI)


Further InformationThe following documents provide more information about Energy Data Management –Commodity. .


Enhanced Contract Management for Waste and Recycling


3.21 Enhanced Contract Management forWaste and Recycling

OverviewThe Contract Management for SAP Waste and Recycling supports you in managingquotations, contracts and orders.

The data that you enter during the creation of a quotation, for example, container location,service data and route, are initially saved separately. They are created with the master datagenerator only after transfer into a contract.

You can also directly create a contract or a quotation (the creation of a quotation is optional).Thus, these functions allow an efficient management of sales processes.

Technical System LandscapeThe following SAP product versions and software instances are required for the technicalimplementation of Enhanced Contract and Account Management for Waste and Recycling:







Further InformationThe following documents provide more information about Enhanced Contract and AccountManagement for Waste and Recycling.





Grid Access – Service Provider Agreements


3.22 Grid Access – Service ProviderAgreements

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Grid Access – Service Provider Agreement:




2 SAP NetWeaver 7.0 Enhancement Package 1 – BusinessIntelligence (BI)

x


Further InformationThe following documents provide more information about Grid Access – Service ProviderAgreement.





Grid Operation – Inventory Management


3.23 Grid Operation – InventoryManagement

OverviewYou, in the role of Grid Operator, can use this business scenario to manage the quantitiesand values of your material stock. It supports you in planning, entering, and verifying allgoods movements. You can also take a physical inventory of the warehouse stock whenperforming settlements for stock.

Technical System LandscapeThe following SAP product versions and software instances are required for the technicalimplementation of Grid Operation – Inventory Management:




2 SAP SCM 7.0 – SCM Server x


Further InformationThe following documents provide more information about Grid Access – InventoryManagement.





Grid Operation – Sourcing and Procurement of Goods and Services


3.24 Grid Operation – Sourcing andProcurement of Goods and Services

OverviewYou, in the role of Grid Operator, can use this business scenario to increase the efficiency ofexternal procurement of materials and spare parts (for example, poles, cross arms,insulators, cables and fuses) and services (for example, installations or replacements ofpoles, street lights, meters, and so on).

This business scenario supports all phases of materials management (planning, purchasing,goods receipt, inventory management and bill verification). You can determine possiblesources to meet a requirement that has come up either during planning or in the specialistdepartments. You can also monitor goods deliveries and the current status of a service at anytime.

This business scenario also supports live auctions as well as any kind of bidding proceduresto round off the pocurement.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Grid Operation – Sourcing and Procurement of Goods and Services:




2 SAP SRM 7.0 / SAP NetWeaver 7.02



Further InformationThe following documents provide more information about Grid Operation – Sourcing andProcurement of Goods and Services.





Grid Operation – Workforce Management


3.25 Grid Operation – WorkforceManagement

OverviewYou, in the role of Grid Operator, can use this business scenario to ensure optimal use ofyour maintenance and service resources. This is particularly important for planningmaintenance and service orders, workforce deployment, and dispatching tasks. Connectionsto mobile functions for processing order data play an increasingly important role in thisbusiness scenario.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Grid Operation – Workforce Management:






Further InformationThe following documents provide more information about Grid Operation – WorkforceManagement.





Grid Usage Invoice Verification and Payment


3.26 Grid Usage Invoice Verification andPayment

OverviewYou can use this business scenario to map the process of grid usage invoices in deregulatedmarkets at the balance supplier’s side. This includes communicating with other serviceproviders in order to receive bills, create complaints, perform payments, and send payment ornon-payment advice notes. The data that is exchanged relates to end customers (points ofdelivery) to whom you provide services or with whom you have made contractualagreements. You can receive electronic bills (or paper bills), have them checkedautomatically, and post them to accounting. You can then clear the posted bill documents,create payment advice notes for end customers, and send them in electronic or paper format.The individual data exchange processes are logged and you can monitor them closely.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Grid Usage Invoice Verification and Payment.




2 SAP NetWeaver 7.02 – Process Integration(PI/XI)

x



Further InformationThe following documents provide more information about of Grid Usage Invoice Verificationand Payment.





Grid Usage Receivables Management and Payment Handling


3.27 Grid Usage Receivables Managementand Payment Handling

OverviewYou can use this business scenario to map the process of grid usage receivables andpayments.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Grid Usage Receivables Management and Payment Handling.






Further InformationThe following documents provide more information about of Grid Usage ReceivablesManagement and Payment Handling.





IC Management


3.28 IC ManagementSee the SAP CRM 7.0 Enhancement Package 1 Master Guide.


IC Marketing


3.29 IC MarketingSee the SAP CRM 7.0 Enhancement Package 1 Master Guide.


Invoice Verification and Payment of Services


3.30 Invoice Verification and Payment ofServices

OverviewYou can use this business scenario to receive electronic bills (or paper bills), have themchecked automatically, and post them to accounting. You can then clear the posted billdocuments, create payment advice notes for service providers, and send them in electronicor paper format. The individual data exchange processes are logged and you can monitorthem closely.

The invoices considered in this scenario are for services (other than grid usage) provided bya service provider for a metering point. Generally, the charges for these services are eventand/or time-based charges per metering point - for example, charges for special meterreading services within a month (event-based), or charges for meter administration services(time-based) (see Grid Usage Invoices, which are generally energy consumption basedand/or demand-based for each metering point).

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Invoice Verification and Payment of Services.




2 SAP NetWeaver 7.02 – Process Integration/ XI-Content



Further InformationThe following documents provide more information about Invoice Verification and Payment ofServices.





Meter Operation – Inventory Management


3.31 Meter Operation – InventoryManagement

OverviewYou, in your role of the Meter Operator, can use this business scenario to manage thequantities and values of your material stock. It supports you in planning, entering, andverifying all goods movements. You can also take a physical inventory of the warehousestock when performing settlements for stock.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Meter Operation – Inventory Management.





Further InformationThe following documents provide more information about Meter Operation – InventoryManagement.





Meter Operation – Sourcing and Procurement of Goods and Services


3.32 Meter Operation – Sourcing andProcurement of Goods and Services

OverviewYou, in your role of the Meter Operator, can use this business scenario to increase theefficiency of external procurement of materials and spare parts (for example, meters,transformers, insulators, cables, and fuses) and services (for example, installations orreplacements of meters, external certifications of devices, and so on). This business scenariosupports all phases of materials management (planning, purchasing, goods receipt, inventorymanagement, and bill verification). You can determine possible sources to meet arequirement that has come up either during planning or in the specialist departments. Youcan also monitor goods deliveries and the current status of a service at any time.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Meter Operation – Sourcing and Procurement of Goods and Services.





3 SAP SRM 7.0 / SAP NetWeaver 7.01 – SRMServer


Further InformationThe following documents provide more information about Meter Operation – Sourcing andProcurement of Goods and Services.





Meter Operation – Workforce Management


3.33 Meter Operation – WorkforceManagement

OverviewYou, in your role of the Meter Operator, can use this business scenario to ensure optimal useof your maintenance and service resources. This is particularly important for planningmaintenance and service orders, workforce deployment, and dispatching tasks. Connectionsto mobile functions for processing order data play an increasingly important role in thisbusiness scenario.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Meter Operation – Workforce Management.





Further InformationThe following documents provide more information about Meter Operation – WorkforceManagement.





Meter and Device Management


3.34 Meter and Device ManagementOverviewYou can use this business scenario to install and replace meters – either smart meters ortraditional meters – and other devices at the customer location, and map the entire structureof installed devices. The scenario also provides support for the legally required inspectionand certification of existing installed devices.

You can use this scenario to integrate the processes of Material Management with thecustomer-related processes. It also supports data exchange with the Advanced MeterInfrastructure (AMI), that is, the Meter Data Unification System (MDUS).

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Meter and Device Management.






Further InformationThe following documents provide more information about Meter and Device Management.





Metered Data Collection


3.35 Metered Data CollectionOverviewYou, in your role of the Metered Data Collector, can use this business scenario to collectmetered data. For periodic meter readings, you collect the data according to a specificschedule. You can also collect aperiodic readings. You apply a basic validation check whenentering the metered data and provide the gathered data to other market participants.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Metered Data Collection.





3 SAP NetWeaver 7.0 Enhancement Package 2 x


Further InformationThe following documents provide more information about Metered Data Collection.





Metered Data Validation and Consumption Data Calculation


3.36 Metered Data Validation andConsumption Data Calculation

OverviewYou can use this business scenario to distribute requests for measurement data to theMetered Data Collector and to receive metered data provided by the Metered Data Collector.You validate this data and correct it if necessary. If data is missing, you can providereplacement values. You can estimate the consumption based on metered data such asmeter reading results.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Metered Data Validation and Consumption Data Calculation.





3 SAP NetWeaver 7.0 Enhancement Package 2


Further InformationThe following documents provide more information about Metered Data Validation andConsumption Data Calculation.





Point of Delivery Master Data and Registration Management


3.37 Point of Delivery Master Data andRegistration Management

OverviewYou, in your combined role as Metering Point Administrator and Grid Access Provider, canuse this business scenario to manage the master data for a point of delivery (PoD). Youvalidate and register changes in the master data and then forward them to all other marketparticipants who are affected. These changes include changes of address, settlement-relateddata and active service providers.

These changes are triggered either by change notifications or by registration processes.Registration processes are executed whenever service providers assigned to the point ofdelivery start or stop their service.

Furthermore, if other market participants contact you to request master data for a PoD, youcan process these requests. All of these activities have to be in line with the rules of thenational regulation authority.

Using this business scenario, you can run your business in the deregulated utilities market.This allows you to fulfil regulatory requirements regarding market communication.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Point of Delivery Master Data and Registration Management:





3 SAP NetWeaver 7.0 Enhancement Package 2 –Process Integration with XI Content

(for Managing Point of Delivery Master Data)

4 SAP NetWeaver 7.0 Enhancement Package 2 –Process Integration with XI Content

(for Managing Grid Usage Registrations andTerminations)

x


Further InformationThe following documents provide more information about Point of Delivery Master Data andRegistration Management.





Processing Grid Usage Registration


3.38 Processing Grid Usage RegistrationYou, in the role of the Grid Access Provider, can use this business scenario to exchangeinformation with third parties, for example, with the Metering Point Administrator or theBalance Supplier, about changes in the master data of the point of delivery and aboutregistrations for grid usage. You need this information to update contracts and billing-relevantdata for grid usage billing.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Processing Changes of Point of Delivery and Grid Usage Registration:






Further InformationThe following documents provide more information about Processing Changes of Point ofDelivery and Grid Usage Registration.







3.39 Receivables Management andPayment Handling

OverviewReceivables management and payment handling is based on a subledger that focusesespecially on the needs of businesses that handle a high volume of master and transactiondata. The aim is to minimize manual work through a high level of automatization. The solutionprovides full control and reconciliation of the subledger and general ledger. Extensivehandling capabilities for accounts receivable and payments ensure revenues and a low rateof outstanding debts. With predefined interfaces to SAP and non-SAP systems, receivablesand payment handling is easily and highly integrated with the general ledger, billing system,customer relationship management, and credit risk management. It provides a strong andaccurate foundation for collections management and the interaction center for financialcustomer care.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Receivables Management and Payment Handling.





3 SAP NetWeaver – BW 7.01 x

4 SAP ERP 6.0 Enhancement Package 5 – SAP FSCM– Biller Direct

x

5 SAP NetWeaver 7.0 – Process Integration XI ContentFI-CA

(for External Cash Payment Integration)


Further InformationThe following documents provide more information about Receivables Management andPayment Handling.





Reconciliation and Closing


3.40 Reconciliation and ClosingOverviewReconciliation and closing supports closing operations and the reconciliation of postingsbetween the contract account subledger and the general ledger. The closing operationincludes the transfer of the necessary information to the relevant ledgers (G/L, Controlling,FM) and the reconciliation of the transferred information. The reconciliation mechanisms arehighly automated and allow backtracking between the general and the subledger. Closingactivities, such as foreign currency valuation, doubtful receivables, individual valueadjustments and the resolution of deferred revenue are part of this scenario. Necessary datafor authorities as well as closing reports are provided.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Reconciliation and Closing.





Further InformationThe following documents provide more information about Reconciliation and Closing.







3.41 Registration for Grid UsageOverviewThis business scenario is applicable to liberalized utilities markets and contains processesrelevant to the Balance Supplier market role. In liberalized utilities markets severalindependent market participants (retailers, grid companies, and so on) collaborate with eachother. The market role model introduced by ebIX describes the business models of thedifferent participants in terms of market roles. One of these market roles is the BalanceSupplier (usually the utilities retailer).

You, in the role of the Balance Supplier (retailer), can use this business scenario to requestthat the Metering Point Administrator (usually the distribution company) changes grid usageregistration at a point of delivery (PoD – the location where the customer consumes theenergy) and informs all affected market parties. Business processes are defined by theregulation authority within the energy markets.

When you conclude a new contract with an end customer (consumer of energy) at a PoD,you, as the responsible Balance Supplier, have to be registered for supplying energy to thisPoD. The Metering Point Administrator is responsible for maintaining this registration andinforming the other market participants who are either involved or affected by the change. Ifthe end customer has previously been supplied with energy by another Balance Supplier, thatBalance Supplier’s registration has to be terminated, and you, as the new Balance Supplier,have to be registered (this is the Change of Supplier process). There are local regulations (forexample, timelines or details about message exchange) to be considered. After you havesent the request for registration, the Metering Point Administrator checks all rules andresponds with either a positive or negative registration message.

Upon ending a supply contract with the end customer and ending the supply for the relatedPoD, the registration for grid usage by you as the Balance Supplier has to be terminated.This is done actively by you in those cases where the customer asks you directly to end thecontract. In other cases, you receive messages from both another Balance Supplier and theMetering Point Administrator informing you about a customer loss and the correspondingtermination of grid usage registration.

Using this business scenario, you can run your business in the deregulated utilities market.This business scenario covers:

Fulfillment of regulatory requirements regarding capabilities in market communication

Direct integration of sales and contract management-related processes with marketcommunication

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Registration for Grid Usage.




2 SAP CRM 7.0 Enhancement Package 1

(for Registering for Grid Usage Terminating GridUsage)

x







4 SAP NetWeaver 7.0 Enhancement Package 2 –Process Integration (PI/XI)

(for connection to third-party system for example,EDIFACT-Adapter)

x


Further InformationThe following documents provide more information about of Registration for Grid Usage.





Request Management of Technical Device Master Data


3.42 Request Management of TechnicalDevice Master Data

OverviewYou, in your role of the Meter Administrator, can use this business scenario to respond torequests for technical master data that you receive from other market roles, for example, theBalance Supplier or the Grid Access Provider. These other market roles may also requestchanges to the technical device or the installation. You can forward these requests to theMeter Operator for execution and distribute the updated technical master data to all marketparticipants who are involved at the point of delivery for which the devices have beenchanged.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Request Management of Technical Device Master Data.





Further InformationThe following documents provide more information about of Request Management ofTechnical Device Master Data.





Selling of Energy Supply Products (E-Services)


3.43 Selling of Energy Supply Products(E-Services)

OverviewYou can use this business scenario to identify the right products and retrieve product-relatedinformation such as descriptions of product characteristics and an estimated price based onyour consumption. Additionally, you can inform the utility company about a move-in or move-out in a fast and convenient manner.

The processes described in this business scenario are used by a customer of a utilitycompany. Variants of these processes are available via other channels or for other user rolessuch as the Interaction Center Agent or the Key Account Manager.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Selling of Energy Supply Products (E-Services).




2 SAP ERP 6.0 Enhancement Package 5 – SAPUtility Customer E-Services


4 SAP NetWeaver 7.0 Enhancement Package 1 –Application Server ABAP

x

5 SAP NetWeaver 7.0 – SAP Utility Customer E-Services

(Easy Adoption landscape)

x

6 SAP NetWeaver 7.2 – SAP Utility Customer E-Services

(Accelarated Innovation landscape)

x


Further InformationThe following documents provide more information about of Selling of Energy SupplyProducts (E-Services).





Selling of Energy Supply Products (Interaction Center)


3.44 Selling of Energy Supply Products(Interaction Center)

OverviewYou, in the role of the call center agent of a utility company (for example, a retailer), can usethis business scenario to propose the right products (a single or individual product, orproducts in a package or bundle) to the customer and subsequently quote or sell theseproducts in a fast and convenient manner. For increased efficiency, one or more contractscan be set up and configured simultaneously.

Within a package, you can sell a combination of the following:

Utility products (representing energy supply products)

Materials (such as air conditioners or other goods that are shipped to the customer)

Service products (for example, energy audits or check-ups)

If market rules require the activation of a new supply contract, the new contract remains in awaiting state until positive confirmation from other market participants is received. Only thendoes the supply contract become active.

The utility company monitors the contracts according to their terms and conditions bychecking the integrity of the contract when changes are required. Additionally, follow-upactivities can be triggered. For example, a notification is sent to the relevant sales managerwhen high-value supply contracts are lost to a competitor.

The processes described in this business scenario are specific to call-centers. Variants ofthese processes are available via other channels or for other user roles.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Selling of Energy Supply Products (Interaction Center).


Product Version – Instance Optional




x



x


7 SAP NetWeaver 7.0 Enhancement Package 1 –Process Integration – XI Content IS-UT 605

x



Selling of Energy Supply Products (Interaction Center)


Further InformationThe following documents provide more information about of Selling of Energy SupplyProducts (Interaction Center).


Configuration Documentation See the documentation in SAP Solution Manage



Selling of Energy Supply Products (C&I)


3.45 Selling of Energy Supply Products(C&I)

OverviewYou, in the role of the Key Account Manager of a utility company (for example a Retailer), canuse this business scenario to manage the selling contract management processes forcommercial and industrial (C&I) customers. This includes managing sales opportunities aswell as creating suitable quotations for energy supply for the customer’s points of delivery.Additionally, you can determine energy prices and other price components, if necessaryindividually for each customer. Finally, you can turn quotations into supply contracts in aneasy and convenient manner. The supply contracts are now fully prepared for billingprocesses.

The main focus is on the execution of mass processes for handling many quotation andcontract items per document at the same time. Large C&I customers may have manyhundreds of points of delivery for which the key account manager has to manage quotationsand contracts.

In liberalized markets, regulatory compliance requires additional processes. As a typicalmarket rule, supply contracts cannot be directly concluded and activated. Before activation,other market participants need to be involved. This is part of the business scenarioRegistration for Grid Usage that fully integrates with the present business scenario.

If market rules require the activation of a new supply contract, the new contract remains in awaiting state until positive confirmation from other market participants is received. Only thendoes the supply contract become active. Moreover, this business scenario allows themonitoring of the sales pipeline and analytical evaluations such as the analysis of contract orcustomer profitability.

This business scenario is used by the Key Account Manager. Variants of these processes areavailable via other channels or for other user roles, for example the Interaction Center Agent.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Selling of Energy Supply Products (Key Account Management).






x




7 SAP NetWeaver 7.0 Enhancement Package 1 –Process Integration – XI Content IS-UT 605

x


Selling of Energy Supply Products (C&I)






Further InformationThe following documents provide more information about of Selling of Energy SupplyProducts (Key Account Management).





Selling of Utility Services


3.46 Selling of Utility ServicesOverviewYou can use this business scenario to address the sale of utility-related services that typicallyoccurs in the call center of a utility operating in a competitive energy retail market. The retailcompany acts as the Customer Service Responsible and is the single point of contact to thecustomer.

The utility-related services can either be service products (for example, meter services, meterreading services, meter billing services, energy consultancy services, installation ormaintenance services), materials (for example, energy efficient appliances) or a combinationof both.

This scenario complements the scenario of setting up energy supply products as well asmanaging energy contracts and quotations. The processes described here are available viaseveral channels like Call Center or Customer Self-Service.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Selling of Utility Services.



1 SAP ERP 6.0 Enhance Package 5 –Utilities/Waste&Recycl./Telco





6 SAP ERP 6.0 Enhancement Package 5 – SAPFSCM – Biller Direct

7 SAP ERP 6.0 Enhancement Package 5 – SAPUtility Customer E-Services


Further InformationThe following documents provide more information about of Selling of Utility Services.





Service Connection Management


3.47 Service Connection ManagementOverviewYou can use this business scenario to install service connections and to executedisconnections and reconnections. You can also process complaints about grid services andservice connections.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Service Connection Management.





Further InformationThe following documents provide more information about of Service ConnectionManagement.





Service Provider Agreements


3.48 Service Provider AgreementsOverviewYou can use this business scenario to make service provider agreements with anotherservice provider. In service provider agreements, two service providers specify rules andconditions for market processes in order to exchange services that are specific to market-roles.

Two service providers have to negotiate and conclude service provider agreements. Theyalso enter them in the IT system so they are accessible in subsequent business scenariosand processes.

The SAP Collaborative Services Management for Utilities component requiresservice provider agreements for the following business scenarios and relatedprocesses:

Registration for Grid Usage (of the Balance Supplier)

Grid Usage Invoice Verification and Payment (of the Balance Supplier)

Point of Delivery Master Data and Registration Management (of theMetering Point Administrator)

Definition of Grid Usage Products and Preparation of Billing (of the GridAccess Provider)

Further applications of service provider agreements are possible based on yourown project-specific developments.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Service Connection Management.





Further InformationThe following documents provide more information about of Service ConnectionManagement.





Service and Product Planning


3.49 Service and Product PlanningOverviewWith this business scenario, you can carry out long-term resource and quotation planning.

Service territory planning enables you to define areas of responsibility within your company.With the exact planning of relevant service territories, you can also calculate in detail thecosts for communal waste disposal services.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Service and Product Planning.






Further InformationThe following documents provide more information about of Service and ProductManagement.





Treatment and Disposal


3.50 Treatment and DisposalOverviewYou can use this business scenario to define the infrastructure for your waste disposalfacilities and recyclable material processing facilities. You can define any type of facility (suchas waste incineration plant, dump, intermediate storage facility, or storage facility forrecyclable material). You can define and execute typical process and process templates forwaste treatment and preparation in the different facility types.

The system also allows you to map the separation and merging of waste from the samewaste fraction or different waste fractions. The seamless integration in the MaterialsManagement (MM) component ensures that the stock and material flow mapped correctly.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Treatment and Disposal.






Further InformationThe following documents provide more information about Treatment and Disposal.





Waste Asset and Container Management


3.51 Waste Asset and ContainerManagement

OverviewYou can use this business scenario and its standard processes to manage central wastedisposal objects and containers.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Waste Asset and Container Management.






Further InformationThe following documents provide more information about Waste Asset and ContainerManagement.





Waste Flow Management


3.52 Waste Flow ManagementOverviewYou can use this business scenario to manage waste flows within and outside of yourcompany. For this purpose, you can define special material management settings and alsodefine waste flows from generator through transport to waste disposal facility (for example,allow or reject flows). The system allows you to monitor data from actual flows and compare itwith data from planned flows. You can be sure that, for your waste flows, the legal monitoringrequirements and the necessary documents are generated.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Waste Flow Management.






Further InformationThe following documents provide more information about Waste Flow Management.





Weighing


3.53 WeighingOverviewYou can use this business scenario to define the processes for the automated entry ofweighing data. The system allows you to use direct data communication with externalweighing systems to receive data and to process it directly in SAP Waste and Recycling.

You can use this scenario to generate weighing documents, which are saved in the system.You post the corresponding material flows in the Materials Management (MM) component,and generate (in the case of an external delivery) bills for your customers, or generate theappropriate postings for existing waste disposal documents.

Technical System LandscapeThe following SAP product versions and software instances are mandatory for the technicalimplementation of Weighing.






Further InformationThe following documents provide more information about Weighing.




Solution Wide Topics

Weighing


4 Solution Wide TopicsService-Oriented Architecture (SOA)SAP´s delivery on SOA (service-oriented architecture) differs from the pure architecturalconcept of SOA in the delivery of ready-to use enterprise services. Enterprise services areSAP-defined Web services which provide end-to-end business processes or individualbusiness process steps that can be used to compose business scenarios while ensuringbusiness integrity and ease of reuse. SAP designs and implements enterprise serviceinterfaces to ensure semantic harmonization and business relevance. This section deals withthe service-enablement of SAP Business Suite 7.

Service EnablementThe service enablement of SAP Business Suite consists of one or more of the following SAPcomponents:

SAP Business Suite 7

Enterprise services are an integral part of the software components of the SAPBusiness Suite applications. Enterprise services are the technical interfaces to thefunctionality available in the business application.

SAP NetWeaver PI 7.0 or higher

SAP NetWeaver Process Integration (SAP NetWeaver PI) is an open integration andapplication platform that provides tools enabling you to set up a service-orientedarchitecture for business applications. You can use the platform for providing,discovering, and consuming services, integrating applications using the integrationserver, and managing business processes. Process integration is required in aruntime environment to consume enterprise services in a mediated scenario.

Most asynchronous services can only be consumed in a mediated scenario.

Enterprise Services Repository

The Enterprise Services Repository (ES Repository) is the central repository thatcontains the definition of all enterprise services and models. ES Repository isshipped with SAP NetWeaver PI 7.1 and with SAP NetWeaver CE 7.1. TheEnterprise Services Repository is a design time environment that enables you tocreate and enhance enterprise service definitions and to view enterprise servicemodels.

In a SAP NetWeaver 7.0 landscape you will require the Integration Repositoryto create and enhance enterprise service definitions in a design timeenvironment.

SAP NetWeaver CE 7.1

The SAP NetWeaver Composition Environment (SAP NetWeaver CE) provides arobust environment for the design and implementation of composite applications.

The design time environment of SAP NetWeaver CE can be used for the model-driven design and development of composite applications based on enterprise


Weighing


services. SAP NetWeaver CE offers the tools and the environment necessary forrunning composite applications fast and efficiently in a runtime environment.

SAP Solution Manager 7.0

The Solution Composer, shipped with SAP Solution Manager 7.0, is required to hostthe enterprise service online documentation.

Services Registry

The Services Registry is shipped with SAP NetWeaver PI 7.1. and SAP NetWeaverCE 7.1. and is required for the publication of enterprise service end-points (Webservices) that have been configured and activated in the SAP Business Suite.

Overview: SAP's Applications for SOA Enablement

The following table describes the SAP applications required or recommended for differentruntime and design time use cases:

SAP Applications

SAPBusinessSuite

SAPNetWeaverPI 7.0(IntegrationRepository)

SAPNetWeaverPI 7.1 (ESRepository)

SAPNetWeaverCE 7.1 (ESRepository)

SAP SolutionManager 7.0(SolutionComposer)

SAPNetWeaver 7.1ServicesRegistry


Weighing


Runtime Usage:

EnterpriseServiceProvisioning

Required Optional

Processintegration andmediatedcommunication

One option required

Design Time Usage:

Create andenhanceenterpriseservicedefinitions

Required One option required Recommended

Viewenterpriseservice models

One Option Required Recommended

Design anddevelopcompositeapplications

Required Recommended Recommended

Enterpriseservice onlinedocumentation

Required

Publications ofenterpriseservice end-points

Optional Required

Installation of the Service-Oriented Architecture (SOA)The installation of service interfaces, and therefore the service enablement of SAP BusinessSuite, consists of one or more of the following phases:

Identification of software components and required business functions

You use the technical data section of the enterprise service documentation to identifythe following data for each enterprise service:

o the software component version with which the service was shipped

o the business function(s) required to be activated

Identification of technical usages

SAP Note 1324838 provides a mapping of business functions and softwarecomponent versions to technical usages. You use this documentation to identify the


Weighing


required technical usages for your list of software component versions and businessfunctions.

Installation of the software component ECC-SE

The software component ECC-SE contains service implementations for ECC (theERP Central Component). This component must be explicitly installed if you intend touse enterprise services for ECC functionality. In this case you must also select thetechnical usage “ESA ECC-SE” during the enhancement package installation.

Selection and installation together with the other parts of the enhancementpackage

In the enhancement package installation process you must select all the technicalusages you have identified for service enablement together with the technical usagesyou identified for enhanced features in SAP Business Suite. The selected technicalusages will install the corresponding software components that contain the enterpriseservices interfaces and implementations.

Enterprise service definitions for SAP NetWeaver PI 7.0 or ES Repository (SAPNetWeaver 7.1) (optional)

To install the content required for the enterprise service definitions you must selectthe technical usage “XI Content” in the enhancement package installation process.This usage type downloads the content files for both SAP NetWeaver 7.0 and 7.1versions. Unpack the ZIP file and copy the tpz files corresponding to your SAPNetWeaver version into the import directory of your Integration Repository (for SAPNetWeaver PI 7.0) or Enterprise Services Repository (for SAP NetWeaver ESRepository 7.1). Use the import function to import the content files into thecorresponding repository (Integration Repository or Enterprise Services Repository).(ChooseTools Import Design Objects)

Enterprise service models for ES Repository (SAP NetWeaver 7.1) (optional)

To install the content required for the enterprise service models you must select thetechnical usage “ESR Content” in the enhancement package installation process.This usage type downloads the content files for SAP NetWeaver ES Repository 7.1.Unpack the ZIP file and copy the tpz files into the import directory of your EnterpriseServices Repository. Use the import function to import the content files into theEnterprise Services Repository. (Choose Tools Import design objects)

The enterprise service models are not available for the Integration Repository(SAP NetWeaver PI 7.0)

Enterprise service online documentation for Solution Composer (optional)

To install the content required for the enterprise service online documentation youmust download the content file for the corresponding Business Suite applicationproduct version from the Service Marketplace. Then you must import the content fileinto your Solution Composer. Refer to SAP Note 1224284 for further information.

Services Registry (optional)

The services registry is shipped with SAP NetWeaver PI 7.1 and CE 7.1. You mustinstall the services registry and then publish the enterprise services from theBusiness Suite application to the registry using the transaction SOAMANAGER in thebackend.


Weighing


For further information regarding the installation of SAP NetWeaver PI, CE and ESRepository, refer to the corresponding SAP NetWeaver Installation and MasterGuides.

Related DocumentationFor more information about the service-oriented architecture (SOA), see the followinginformation sources:

SDN Community in the SAP Network athttps://www.sdn.sap.com/irj/sdn/soa (registration required)

The SAP Enterprise Service Workplace at http://ESWorkplace.sap.com

The Enterprise Services Wiki in the SAP Network athttps://wiki.sdn.sap.com/wiki/x/LQ0 (registration required)

SAP Note 1224284: Enterprise Services, Installing and Accessing the SOADocumentation

SAP Note 1359215: Technical prerequisites for using enterprise services

SAP note 838402: Problems with non-Unicode system landscapes

https://www.sdn.sap.com/irj/sdn/soa

http://ESWorkplace.sap.com/

https://wiki.sdn.sap.com/wiki/x/LQ0

References

Implementable Steps


5 References5.1 Implementable StepsIn the following section, you will get an overview of implementable steps offered by SAP. Animplementable step is part of an end-to-end process and describes the scope of animplementation project (which typically lasts approximately one to three months). Itaddresses a single line of business. It creates value in itself and therefore represents anentity that is implementable. The implementable steps listed here are grouped according tobusiness logic — each implementable step belongs to one or several value scenarios.

The list of implementable steps in this section contain all implementable stepsthat are available for SAP Business Suite customers. The list has been createdto give you an overview of what is available in addition to the businessprocesses or business scenarios that are described in detail in this MasterGuide. Note that implementable steps often run across several SAPcomponents such as SAP ERP, SAP CRM, SAP SCM, or SAP SRM. So if youwant to implement an implementable step, make sure that you have licensedand installed the required SAP components and releases.

You can find the implementable steps in the business process repository (BPR) of SAPSolution Manager. To read the descriptions of the implementable steps or to find moreinformation about required components and releases, use planning tools such as the BPRviewer and the SCL/PCL viewer. For more information about these tools, see Tools forPlanning Your System Landscape.

Implementable Steps in SAP Solution ManagerYou can find the following implementable steps in the business process repository of SAPSolution Manager under Solutions/Applications Cross-Application ImplementationPackages Scenarios:

Value Scenario Implementable Step

Accelerate Financial ClosesGroup Close

Local Close

Accelerating Lead-to-Cash


Campaign Management

Lead and Opportunity Management

Lead-to-Cash

Sales Performance Management

Sales Planning

Account & Trade Promotion Account and Content Management

References

Implementable Steps



Management Sales Planning

Trade Promotion Management

Asset Safety and Compliance

Keep the Assets Safe

Keep the Environment Safe

Keep the People Safe

Keep the Stakeholders Informed and Involved

Asset Visibility and Performance

Conduct Improvement Programs

Optimize Maintenance & Plant Operations

Set Up Plant Dashboards and Act on Alerts

Automate Global HR and Payroll

Administer HR Data

Analyze Labor Costs

Benefits Administration

Financials: Period-End Close

Run Payroll

Time Management

Build the Workforce

Onboarding

Planning & Budgeting

Reporting & Analytics

Talent Acquisition

Centralized Sourcing and ContractManagement

Central Contract Management

Central Sourcing

Operational Procurement

Supplier Management

Collaborative Demand and Supply Collaborative Demand Management

References

Implementable Steps



Planning Sales & Operations Planning

Supply Planning

Consume to Cash in High VolumeBusinesses

Convergent Charging

Convergent Invoicing

Credit & Collections Management

Financial Customer Care and DisputeManagement


Continuous Product Change andTransformation

Change Audit and Aprproval

Change Implementation

Change Initiation

Change Investigation

Continuous Product and ServiceInnovation

Managing Innovation

Portfolio Management

Program and Project Management

Strategy and Planning

Corporate Shared Service Center Multifunctional Shared Service Framework

Shared Services Operations

Track Delivery Performance

Creating the Optimal Offer

Additional Processes for Creating the OptimalOffer

Campaign Management

Catalog Management in CRM

Creating the Optimal Offer

IC Sales with CRM Sales Order

References

Implementable Steps



Quotation and Order Management in CRM (withCRM Billing and Rebates)

Quotation and Order Management in CRM WebChannel

Customer To Cash (B2B)

Accounts Receivable

Billing

Collections Management

Credit Evaluation and Management

Customer Care

Dispute Resolution

e-Invoicing

Develop a High-Performing Workforce

Compensation Management

Employee Performance Management

Succession Management

Talent Assessment and Review

Talent Development & Learning

Talent Intelligence

Differentiation Through ServiceExcellence

Complaints and Returns Management

Differentiation Through Service Excellence

IC Management

IC Service

Service Contract Management

Service Order Management

References

Implementable Steps



Service Planning

Delivering Efficient After Sales Service

Customer Service

Service Delivery

Service Parts Planning and Procurement

Service Parts Warehousing

Service Sales and Marketing

Develop a High-Performing Workforce

Compensation Management

Employee Performance Management

Succession Management

Talent Assessment and Review

Talent Development & Learning

Talent Intelligence

Differentiation Through ServiceExcellence

Complaints and Returns Management

IC Management


IC Service


Drive Efficient HR Operations

HCM Service Delivery

Operations & Governance

Shared Services Framework

Efficient Manufacturing Operations forDiscrete Industries

Enterprise-Level Planning and Control (DiscreteIndustries)

Manufacturing Execution (Discrete Industries)

Plant-Level Operations (Discrete Industries)

References

Implementable Steps



Efficient Manufacturing Operations forProcess Industries

Enterprise-Level Planning and Control (ProcessIndustries)

Manufacturing Execution (Process Industries)

Plant-Level Operations (Process Industries)

Embedded Product Compliance

Developing Compliant Product

Maintaining Compliant Product

Manufacturing Compliant Product

Integrated Product Development forDiscrete Industries

Component and Task Sourcing

Product Design

Ramp-Up for Production

Integrated Product Development forProcess Industries

Material Sourcing

Product Development

Ramp-Up for Production

Integrated Sourcing and Procurement

Contract Management

Operational Procurement

Spend Analytics

Strategic Sourcing

Interactive Customer LifecycleManagement


Campaign Management

Campaign Management in CRM Web Channel

IC Marketing


Interactive Customer Lifecycle Management

Lead-to-Cash

Loyalty Management

References

Implementable Steps



Modeling the Enterprise Data Warehouse (EDW)

Quotation and Order Management in CRM WebChannel

Segmentation and List Management

Invoice To Pay

Bank Communications Automation

Core Accounts Payable

Invoice Management Automation

Record Retention and Archiving

Logistics and Fulfillment Management

Customer Commitment

Global Trade Management

Inbound Freight Management

Storage and Fulfillment

Manage Financial and OperationalPerformance

Improve Planning and Forecasting

Profitability Management

Managing Risk and Compliance

Access Management

Duty Reduction & Trade Compliance

Enterprise Risk Management

Risk-Based Internal Controls

Manage Treasury and Financial Risk

Manage Global Financial Risks

Managing Cash and Liquidity

Optimize Debt and Investments Strategies

Optimize Payments and Bank Communication

Manufacturing Network Planning andExecution

Manufacturing Network Planning

Material Supply & Replenishment

Outsourced Manufacturing

References

Implementable Steps



Production Planning & Execution

Optimize Workforce Scheduling

Service Optimization

Service Order Completion


Shift & Schedule Management

Workforce Scheduling Analytics

Optimized Assets Operations andMaintenance

Asset Planning and Scheduling

Operations and Maintenance

Service Procurement

Spare Parts Management

Planning, Building and CommissioningAssets

Asset Information Management

Asset Portfolio Management

Capital Project Management

Real Estate Lifecycle Management

Acquisition & Construction Management

Facilities Management

Lease & Space Management

Service Parts Planning and Logistics

Service Parts Claims and Returns

Service Parts Planning and Procurement

Service Parts Sales

Service Parts Warehousing

References

Tools and Resources for Planning Your System Landscape


5.2 Tools and Resources for Planning YourSystem Landscape

To plan your system landscape, you can use a few tools and resources that are available toyou as SAP customer.

ToolsOn SAP Service Marketplace, we provide some tools that allow you to look up more detailedinformation about business scenarios, business processes, and implementable steps. Thesetools include the following:

Tools for Looking Up Information about Business Processes, Scenarios, andImplementable Steps

Tool Purpose

Business processrepository (BPR) viewer

To look up descriptions of business scenarios, businessprocesses, and implementable steps

Scenario and processcomponent list

To look up the required components and releases for a businessscenario, business process, or implementable step

In addition, there are tools in SAP Solution Manager that support you before, during, or afterthe installation of your SAP product or SAP enhancement package. These tools include:

Tools for Supporting Installations and Upgrades

Tool Purpose

Solution Manager SystemLandscape To model and set up your system landscape

SAP Solution ManagerMaintenance Optimizer

To install support packages and SAP enhancementpackages

Business process repository

To access configuration documentation, links toCustomizing activities and master data transactions,specifically tailored for individual business processes,business scenarios, or implementable steps

Business process change analyzer(available with SAP enhancementpackage 1 for SAP SolutionManager 7.0)

To analyze the effects of transports and supportpackages as well as activation logs for businessfunctions

As of SAP Solution Manager 7.0 with support package 23, these tools havebeen enhanced to provide a better support for the setup of your systemlandscape and for installing and activating business functions. For moreinformation, see SAP Library for SAP Solution Manager on SAP Help Portal athttp://help.sap.com under SAP Solution Manager.

SAP Solution Manager: Implementation Content

http://help.sap.com/

References



To get implementation content that supports you during the configuration of your businessprocesses, business scenarios, and implementable steps, you need the SAP SolutionManager add-on Implementation Content ST-ICO 155 L022 (SP25).

SAP Business Suite: Landscape Implementation — Technical PlanningGuideTo get an overview of the necessary steps for planning a system landscape, use theLandscape Implementation — Technical Planning Guide on SAP Service Marketplace athttp://service.sap.com/instguides under SAP Business Suite Applications . The guide alsoprovides you with more information about the following:

Examples of reference system landscapes

Planning tools such as the business process repository

Deployment options

Typical implementation process

Business Process Repository (BPR) ViewerThe business process repository viewer (BPR viewer) is a tool on SAP Service Marketplacethat allows you to preview the existing business scenarios, business processes, andimplementable steps that are shipped as part of SAP Solution Manager content. You canmake use of the information in SAP Solution Manager during your implementation project bytaking the pre-delivered implementation content as the starting point for your project scope.The implementation content is delivered with the following assigned information:

Description of the business scenario, process, or implementable step

Configuration content (Customizing activities or configuration documentation)

Using the BPR ViewerProcedureCalling Up the BPR Viewer

You can call up the BPR viewer directly using the Internet addresshttps://implementationcontent.sap.com/bpr. Alternatively, you can also call upthe Internet address http://service.sap.com/bpr first, to see more backgroundinformation about the BPR viewer and additional material on SAP Service Marketplace.

Working with the BPR Viewer

To call up information about business scenarios, business processes, or implementablesteps, navigate the following paths in the BPR viewer:

BPR Object Location

Business scenario Under Solutions/Applications

Business process Under Organizational Areas

Implementable step Under Solutions/Applications

http://service.sap.com/instguides

https://implementationcontent.sap.com/bpr

http://service.sap.com/bpr

References



For each business scenario, business process, or implementable step, you can selectbetween different versions that depend on varying components and releases. To display thedescriptions of a business scenario, business process, or implementable step, choose theDocumentation tab page. To display configuration documentation, choose the Configurationtab page.

The BPR Viewer displays all descriptions, but only a selection of theconfiguration documentation. To view all configuration documentation, installand use SAP Solution Manager at your customer site.

Scenario and Process Component ListThe scenario and process component list (SCL/PCL) is a tool on the SAP ServiceMarketplace that allows you to find realization alternatives for SAP solutions, businessscenarios, and processes for your SAP enhancement package installation. You find the toolat http://service.sap.com/scl.

The SCL/PCL helps you to bridge the gap between the business view and the technical viewin SAP's products. It shows you which application components are needed to realize abusiness scenario or a process and which business scenarios are possible with a given set ofapplication components.

Using the SCL/PCLProcedure

1. Go to SAP Service Marketplace at http://service.sap.com/scl.

2. To start the SCL/PCL, choose Start Application.

The following selection options are provided:

o SAP Scenarios and Realization Alternatives

With this option you can browse SAP's solutions, business scenarios, andprocesses. You can find out which components are needed and the availablealternatives.

o SAP Components and Possible Scenarios

This option allows you to browse SAP's products and components and to findout, which business scenarios and processes you can realize using thecomponents.

For more information on how to use the tool, refer to the Help section.

3. Select SAP Scenarios and Realization Alternatives.

Select one or several scenarios, processes, and variants you want to realize. Youcan make your selection by using an alphabetical index or a full-text search. It is alsopossible to see all scenarios for a certain solution. You will then get a list of thealternative ways to realize these scenarios. You can also search for the identifiedbusiness functions of a SAP enhancement package.

In the following steps we chose the scenario Billing Analysis in ERP as an example.

4. Add the scenario Billing Analysis in ERP to the SelectedScenarios/Processes/Variants list and choose Show Realization Alternatives. The

http://service.sap.com/scl

http://service.sap.com/scl

References



SCL/PCL then lists the different possibilities. With options like Validity you can switchbetween possible and impossible realization alternatives. The Optional Comp.dropdown list helps you to find the minimum required SAP product versions.

The Main SAP Documentation Types


6 The Main SAP Documentation TypesThe following is an overview of the most important documentation types that you need inthe various phases in the life cycle of an SAP solution.

Documentation types in the software life cycle

ImplementationImplementation

Master Guide

ConfigurationDocumentation Release Notes

ComponentInstallation Guide

ComponentUpgrade Guide

Upgrade Master Guide

OperationOperation UpgradeUpgrade

Solution ManagementGuide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Cross-Phase DocumentationSAPterm

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30languages, as well as many definitions and glossary entries in English and German.

Target group:

Relevant for all target groups

Current version:

Located in the SAP Help Portal at help.sap.com Additional InformationGlossary (direct Access) or Terminology (available as terminology CD)

In the SAP-System in transaction STERM

SAP Library

The SAP Library is a collection of function- and process-oriented documentation for SAPcomponents. The SAP Library also contains the Business Scenario Descriptions.

Target group:

o Consultants

o System administrators



o Project teams for implementations or upgrades

Current version:

o Located in the SAP Help Portal at help.sap.com

o Also located in the SAP Service Marketplace at service.sap.com/ibc (only theBusiness Scenario Descriptions)

Implementation Guide (IMG)

The Implementation Guide is a tool for configuring the SAP system to meet customerrequirements. Its structure and documentation are component-oriented.

Target group:

o Solution consultants

o Project teams for implementations or upgrades

Current version:

o In the SAP menu of the SAP system under Tools Customizing IMG

Security Guide

The Security Guide describes the settings for a medium security level and offers suggestionsfor raising security levels. A collective security guide is available for the SAP NetWeavertechnologies like SAP Web Application Server (SAP Web AS). This document containsgeneral guidelines and suggestions about system security. Other technologies and individualapplications have a Security Guide of their own.

Target group:


Solution consultants

Project teams for implementations or upgrades

Current version:

Located in the SAP Service Marketplace atservice.sap.com/securityguide

ImplementationMaster Guide

The Master Guide is the starting point for implementing an SAP solution. It lists the requiredSAP components and third party applications that are required for each Business Scenario. Itprovides scenario-specific descriptions of preparation, execution, and follow-up of animplementation. It also offers references to other documents, such as Component InstallationGuides and SAP Notes.

Target group:



Project teams for implementations

Current version:

Located in the SAP Service Marketplace at service.sap.com/instguides

Component Installation Guide



The Component Installation Guide describes the technical implementation of an SAPcomponent, taking into account the combinations of operating systems and databases. Itdoes not describe any business-related configuration.

Target group:



Current version:


Configuration Documentation in SAP Solution Manager

SAP Solution Manager is a tool with various functions, one of its main functions being theconfiguration of SAP solutions and Business Scenarios. It contains IMG activities,transactions, and so on, as well as documentation. Instead of the configurationdocumentation in SAP Solution Manager, there may be separate Business ScenarioConfiguration Guides in the SAP Service Marketplace for earlier shipments of the BusinessScenarios.

Target group:



Current version:

In SAP Solution Manager

Located in the SAP Service Marketplace at service.sap.com/ibc

Production OperationSolution Operation Guide

The Solution Operation Guide is the starting point for operating an SAP solution. The guiderefers users to the tools and documentation that are needed to carry out various tasks, suchas monitoring, backup/restore, master data maintenance, transports, and tests. It also refersusers to other documents, for example the SAP Library, the Master Guide, and theComponent Management Guides.

Target group:




Project teams for implementations or upgrades

Current version:


UpgradeUpgrade Master Guide

The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of anSAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as the Component Upgrade Guidesand SAP Notes. Instead of an Upgrade Master Guide, there may be several Business



Scenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the BusinessScenarios of an SAP solution.

Target group:


Project teams for upgrades

Current version:


Component Upgrade Guide

The Component Upgrade Guide describes the technical upgrade of an SAP component,taking into account the combinations of operating systems and databases. It does notdescribe any business-related configuration.

Target group:



Current version:


Release Notes

Release notes are documents that contain short descriptions of new features or changes inan SAP component since the previous release. Release notes about ABAP developmentsenable the SAP system to generate delta and upgrade IMGs.

Target group:

Consultants


Current version:

Located in the SAP Service Marketplace atservice.sap.com/releasenotes

In the SAP menu of the SAP system under Help Release information

SAP™ for Utilities 2010 powered by SAP NetWeaver®

Documents

Transcript of SAP™ for Utilities 2010 powered by SAP NetWeaver®