master guide sap® for utilities - sap help portal · pdf filemaster guide sap for...

Master Guide SAP® for Utilities Using SAP ERP 6.0 Enhancement Package 6, SAP CRM 7.0 Enhancement Package 2, SAPNetWeaver 7.03

Target Audience Consultants Administrators Others

Document version 1.0 – 11/08/2011

© Copyright 2011 SAP AG. All rights reserved.

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

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

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

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks 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 or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle and Java are registered trademarks of Oracle.

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

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

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

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other

SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

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

These materials are subject to change without notice. These materials are provided by SAP 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 for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet address:

service.sap.com/instguides

Typographic Conventions Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

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

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Master Guide SAP for Utilities

4 June 2010

History of Changes The Master Guide is regularly updated in SAP Service Marketplace at service.sap.com/instguides.

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

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

Master Guide Version Important Changes

1.00 (July 2011) Validation Version – Draft

1.01 (November 2011) Covers the full range of SAP for Utilities business scenarios


July 2011 5

Contents Contents ........................................................................................................ 5

1. Getting Started ............................................................................ 8

1.1. About this Document ................................................................... 8 Purpose ......................................................................................................... 8 Constraints ................................................................................................... 8

1.2. Related Information ................................................................... 11 1.3. Related Master Guides .............................................................. 12 1.4. SAP Solution Manager ............................................................... 13 1.5. Important SAP Notes ................................................................. 14

2. SAP for Utilities Overview ........................................................ 16

2.1. Enhancement Packages ............................................................ 18 Enhancement Package Key Concept ....................................................... 18

2.2. Key Facts About Enhancement Packages............................... 20 2.3. Enhancement Package Implementation .................................. 21

Process ....................................................................................................... 21 2.4. Product Versions, Instances and Software ............................. 23

Component Versions ................................................................................. 23 Product Version – Instance ....................................................................... 23 SAP ERP 6.0 Enhancement Package 6 – Utilities/Waste&Recycl./Telco ................................................................... 23 SAP ERP 6.0 Enhancement Package 6 – SAP Utility Customer E-Services ...................................................................................................... 23 SAP ERP 6.0 Enhancement Package 6 – SAP FSCM – Biller Direct ...... 24 SAP NetWeaver 7.03 Business Intelligence (BI) Content Add-On 7.46 . 24 SAP NetWeaver 7.03 – Application Server Java ...................................... 24 SAP NetWeaver 7.03 – Content Server ..................................................... 24 SAP NetWeaver 7.03 – Process Integration/XI Content .......................... 24 SAP EHP1 for SAP NetWeaver 7.03 – Adobe Document Services ......... 25 SAP EHP1 for SAP NetWeaver 7.03 – Search and Classification (TREX) ......................................................................................................... 25 SAP CRM 7.0 – CRM Application Server Java ......................................... 25 SAP CRM 7.0 – CRM Application Server ABAP ....................................... 25 SAP CRM 7.0 – CRM Application Server Java ......................................... 25 SAP CRM 7.0 - TREX .................................................................................. 26 SAP EHP3 for NetWeaver 7.0 – Business Intelligence (BI) ..................... 26 SAP EHP3 for SAP NetWeaver 7.0 – Content Server .............................. 26

2.5. System Landscape ..................................................................... 27

3. Business Scenarios of SAP for Utilities and SAP for Waste and Recycling ....................................................................... 28

3.1. Scenarios for SAP for Utilities .................................................. 28


6 June 2010

3.1.1 Scenario Group Grid Life Cycle Management (Market Role Grid Management) .............................................................................................. 28 3.1.2 Scenario Group Workforce Management Procurement and Warehousing (Market Role Grid Management) ........................................ 29 3.1.3 Scenario Group Preparation of Grid Usage Services (Market Role Grid Management) ............................................................................. 30 3.1.4 Scenario Group Grid Usage Management (Market Role Grid Management) .............................................................................................. 31 3.1.5 Scenario Group Point of Delivery Administration (Market Role Metering Point Administration) ................................................................. 33 3.1.6 Scenario Group Meter Administration Services (Market Role Meter Management) .................................................................................... 33 3.1.7 Scenario Group Meter Operation Services (Market Role Meter Management) .............................................................................................. 35 3.1.8 Scenario Group Metered Data Collection Management (Market Role Metered Data Management) .............................................................. 37 3.1.9 Scenario Group Energy Settlement and Aggregation (Market Role Metered Data Management) .............................................................. 37 3.1.10 Scenario Group Measurement Data Aggregation Administration (Market Role Metered Data Management) ...................... 37 3.1.11 Scenario Group Execution of Billing for Energy Products and Services (Market Role Execution of Billing for Energy Products and Services) ..................................................................................................... 37 3.1.12 Scenario Group Customer Financials Management (Market Role Metered Data Management Execution of Billing for Energy Products and Services) ............................................................................. 38 3.1.13 Scenario Group Energy Capital Management - Retail (Market Role Balance, Forecast and Trade)........................................................... 40 3.1.14 Scenario Group Selling of Energy and Services (Market Role Energy Sales, Customer Service) ............................................................. 41 3.1.15 Scenario Group Customer Service Management ......................... 43 3.1.16 Scenario Group Preparation of Energy Supply Products and Services (Market Role Preparation of Energy Products and Billing) ..... 45 3.1.17 Scenario Group Handling of Device and Measurement Data (Market Role Preparation of Energy Products and Billing)..................... 45 3.1.18 Scenario Group Grid Usage and Service Provider Agreement – Retail (Market Role Preparation of Energy Products and Billing) ....... 46 3.1.19 Scenario Group Customer Financials Management (Market Role Execution of Energy Billing & Customer Financials Management (Billing Agent)) ..................................................................... 49 3.1.20 Scenario Group Execution of Billing for Energy Products and Services (Market Role Execution of Energy Billing & Customer Financials Management (Billing Agent)) .................................................. 49 3.1.21 Scenario Group Customer Credit Risk-Based Collections Management (Market Role Financial Customer Collection Service (Collection Agent)) ..................................................................................... 49


July 2011 7

3.1.22 Scenario Group Plant Life Cycle Management (Market Role Generation (Plant Operator)) ..................................................................... 49 3.1.23 Scenario Group Resource Management (Market Role Generation (Plant Operator)) ..................................................................... 50 3.1.24 Scenario Group Energy Capital Management - Generation (Market Role Generation (Plant Operator)) .............................................. 51

3.2. Scenario Groups for SAP for Waste and Recycling ............... 51 3.2.1 Scenario Group Development Services .......................................... 51 3.2.2 Scenario Group Selling of Waste Services ..................................... 51 3.2.3 Scenario Group Planning and Fullfillment of Services .................. 52 Description ................................................................................................. 57 Technical System Landscape ................................................................... 57

3.3 Other scenarios .......................................................................... 60

4. Solution Wide Topics ............................................................... 64

4.1. Service-Oriented Architecture (SOA) ....................................... 64

5. References ................................................................................. 69

5.1. Tools and Resources for Planning Your System Landscape ............................................................................................ 69


8 July 2011

1. Getting Started 1.1. About this Document

Purpose This Master Guide is the central starting point for the technical implementation of SAP for Utilities. You can find cross-scenario implementation information as well as scenario-specific information in this guide.

The central starting point for the technical upgrade of your SAP application/solution is the Upgrade Master Guide, which you can find on SAP Service Marketplace at: http://service.sap.com/instguides.

Use the Master Guide to get an overview of SAP for Utilities, its software units, and its scenarios from a technical perspective. The Master Guide is a planning tool that helps you to design 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

You can find the most current information about the technical implementation of SAP for Utilities and the latest installation and configuration guides on SAP Service Marketplace at: http://service.sap.com/instguides We strongly recommend that you use the documents available here. The guides are regularly updated.

Constraints The business scenarios that are presented here serve as examples of how you can use

SAP software in your company. The business scenarios are only intended as models and do not necessarily run the way they are described here in your customer-specific system landscape. Ensure to check your requirements and systems to determine whether these scenarios can be used productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors before going live.

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

All the scenario information in this guide refers to the current releases SAP ERP 6.0 Enhancement Package 6 and SAP CRM 7.0 Enhancement Package 2, and not to the required minimum releases.

Further Information The following documents provide more information about the scenarios:


July 2011 9

Content Location

Scenario 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 at service.sap.com/securityguide

The following scenarios of SAP for Utilities are part of other Master Guides:

Account and Contact Management

Campaign Management

Credit and Collections Management

IC Management

IC Marketing

Reconciliation and Closing

For detailed information, see the following:

SAP CRM 7.0 Master Guide of SAP CRM on the SAP Service Marketplace at http://service.sap.com/crm-inst SAP CRM SAP CRM 7.0 Plan Master Guide SAP CRM 7.0

http://service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 6 for SAP ERP 6.0

SAP ERP 6.0 Master Guide on the SAP Service Marketplace at http://service.sap.com/erp-inst SAP ERP 6.0 Installation Master Guide for SAP ERP 6.0.

SAP for Telecommunications Master Guide on the SAP Service Marketplace at http://service.sap.com/instguides Industry Solutions

You can find an overview about the whole functionality of SAP for Utilities in the solution map: http://service.sap.com/bmet SAP Business Maps Industry-Specific Maps Utilities

The business scenarios that are presented here serve as examples of how you can use SAP software in your company. The business scenarios are only intended as models and do not necessarily run the way they are described here in your customer-specific system landscape. Make sure that you check your requirements and systems to determine whether these scenarios can be used productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors before going live.

This Master Guide provides just one way to implement each business scenario. This is the implementation valid for the 2011 edition. For other ways to implement business scenarios, see the Scenario Component List Viewer in SAP Service Marketplace (http://service.sap.com/scl)


10 July 2011


July 2011 11

1.2. Related Information The following table contains links to crucial information for implementing this solution:

Content Location

Information about technical and release planning issues on SAP components

service.sap.com/pam

Information about the latest version of installation and upgrade guides for SAP components

service.sap.com/instguides

Information about SAP Notes service.sap.com/notes

Information about released platforms service.sap.com/platforms

Information about sizing and calculation of hardware requirements (such as CPU, disk, and memory resource) with the Quick Sizer tool

service.sap.com/sizing

Information about network security – SAP Security Guide

service.sap.com/securityguide

Information about network integration service.sap.com/network

Information about high availability service.sap.com/ha

Information about creating error messages

service.sap.com/message

Performance Map service.sap.com/performancemap

General information about SAP for Utilities

service.sap.com/utilities

Documentation on SAP Help Portal help.sap.com/

Information about Support Package Stacks, latest software versions and patch level requirements

service.sap.com/sp-stacks


12 July 2011

1.3. Related Master Guides This Master Guide is based on Master Guides for cross-industry applications. You can find more information about the relevant applications in the following documents:

Title Location

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

SAP ERP 6.0 Enhancement Package 6 service.sap.com/erp-inst SAP ERP 6.0 SAP Enhancement Packages for SAP ERP 6.0 SAP Enhancement Package 6 for SAP ERP 6.0 Master Guide SAP Enhancement Package 6 for SAP ERP 6.0

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

SAP CRM 7.0 Enhancement Package 2 service.sap.com/crm-inst SAP CRM 7.0 SAP Enhancement Packages for SAP CRM 7.0 Plan Master Guide SAP CRM 7.0 Enhancement Package 2

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

Installation Master Guide – SAP NetWeaver 7.0

SAP NetWeaver 7.0 Enhancement Package 3

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

Installation Master Guide – SAP NetWeaver 7.0


July 2011 13

1.4. SAP Solution Manager SAP provides the SAP Solution Manager as the highly recommended platform to efficiently support the implementation of your solution. Using SAP Solution Manager significantly accelerates the implementation process and helps you to achieve your business goals. At the same time, SAP can deliver Support Services based on the business scenarios designed and documented in SAP Solution Manager. Implementation content for your solution may further accelerate the implementation process. For information about availability of content specifically tailored to your solution, see SAP Service Marketplace under http://service.sap.com/solutionmanager.

In this Master Guide, the installation of software components required for each business 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 release combination in the Software Lifecycle Manager.


14 July 2011

1.5. Important SAP Notes Before starting the installation, you must read the SAP Notes that are mentioned in the relevant installation guides. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at service.sap.com/notes.

SAP Note Number Title Description

838003 Industry Add-Ons integrated in SAP ECC 600

Provides the names of the former IS add-ons that have been integrated into SAP ERP Central Component 6.0 and that are available as business function sets. This note is updated on a regular basis.

856284 SAP ERP Central Component 6.0: Inst./Upgrad and architecture

Information about software architecture of SAP ERP Central Component 6.0 (SAP ECC 6.0) and its installation or upgrade.

1566412 Enhancement Package 6 for SAP ERP 6.0: Required SWC

Information about installation of dedicated parts of SAP Enhancement Package 6 (EhP6) for SAP ERP 6.0.

849887 SAP ERP 6.0: Support Package Stacks Release and Info Note

Contains a list of all SAP ERP 6.0 Release and Information Notes (RIN) that have been issued for SAP ERP 6.0. This note is updated every time a new Release and Information Note is issued for SAP ERP 6.0.

1492537 1064635

Add. Info: Update to Enhancement Package 6 for SAP ERP 6.0 SAP ERP Enhancement Packages: SP Stacks Release Info Note

Contains a list of all Release Information notes for: SAP ERP Enhancement Package Releases, SAP ERP Enhancement Package Support Package (SP) Stacks and Corresponding or equivalent SAP ERP 6.0 Support Package Stacks

881842 Release strategy for SAP Utilities as of ECC 6.0

Information about the activation and upgrade of the SAP Utilities industry extension


July 2011 15

SAP Note Number Title Description

855534 Dual Stack and SAP Business Suite 7

Information on using both SAP Business Suite ABAP and Java Components in your system landscape Embedded SAP NetWeaver Components in SAP ERP 6.0.

1162804 FG_PART: Time dependency of the business partner in IS-U

Problems occur in IS-U for various functions (for example, move-in and move-out) in connection with the business partner.

824757 Dependencies between SAP ERP component lists

The note is relevant only if you require component information for processes and role-based Work Centers with dependencies to other process or role-based Work Centers.

1179512 Release restrictions for SCM 7.0

This note provides information about release restrictions for SCM 7.0.

1003900 TREX 7.1: Central Note Information about installing SAPNetWeaver TREX 7.1 and links to further information

1093900 Upgrade from TREX 7.0 to TREX 7.1

Information about how to upgrade from SAP NetWeaver TREX 7.0 to TREX 7.1

1249465 TREX 7.1: Installing TREX for Embedded Search

Information about installing SAPNetWeaver TREX 7.1

1123452 FG_PART: Limitation Business Partner in IS-U und FS-BP

You use a Financial Services (FS) application and Utilities in one system. When you do this, various problems occur in connection with the business partner.

1115493 CRM Web UI: Mandatory SICF services for CRM framework

This note describes the basic SICF services necessary to run a CRM Web UI.


16 July 2011

2. SAP for Utilities Overview SAP for Utilities is a portfolio of solutions that support all of the critical billing and CRM business processes of electricity, gas, and water utilities in regulated and deregulated markets. 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 business solutions, the SAP xApps portfolio of packaged composite applications, SAP solutions for small 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 technical implementation of the following business scenarios of SAP for Utilities: Auditing Billing for Commercial and Industrial Customers Billing for Residential Customers Billing of Energy Products Billing of Services Billing of Unmetered Services Billing of Utility Services Billing-Relevant Device and Measurement Data Management Bulky (Loose) Waste Collection Campaing Management for Utilities with Bill Supplement Change of Supplier Cleaning and Winter Services Connections Management Consumption Data Collection Container Services Customer Complaints Management Customer Interaction Management (E-Services) Customer Interaction Management (Interaction Center) Customer Service in the Interaction Center Decommissioning 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 Demand Side Management Discharge System Services Disconnection and Reconnection Management Document Management by Streamserve Electronic Customer Services Energy Data Management Energy Data Management – Commodity Enhanced Contract Management for Waste and Recycling Extended Customer Service and Sales in the Interaction Center Grid Engineering and Construction


July 2011 17

Grid Maintenance and Operations Grid Operation – Inventory Management Grid Operation – Sourcing and Procurement of Goods and Services Grid Operation – Workforce Management Grid Usage Invoice Verification and Payment Grid Usage Receivables Management and Payment Handling Inventory Management Invoice Verification and Payment of Services IS Utilities Business Prozesses Measurement Data Aggregation and Settlement Measurement Data Processing Meter and Device Management Measurement Data Processing Meter Operation – Inventory Management Meter Operation – Sourcing and Procurement of Goods and Services Meter Operation – Workforce Management Plant Engineering and Construction Plant Maintenance Plant Operations Point of Delivery Master Data and Registration Management Processing Grid Usage Registration Procurement of Services and Spare Parts in ERP Procurement of Services and Spare Parts in SRM Receivables Management and Payment Handling Reconciliation and Settlement Registration for Grid Usage Request Management of Technical Device Master Data Selling of Energy Supply Products (E Services) Selling of Energy Supply Products (Interaction Center) Selling of Energy Supply Products (Key Account Management) Selling of Utility Services Service and Product Planning Service Connection Management Service Provider Agreements Sourcing and Procurement of Goods and Services Treatment and Disposal Waste Asset and Container Management Waste Flow Management Weighing Workforce Management


18 July 2011

2.1. Enhancement Packages Enhancement Package Key Concept We have adapted our major release strategy to better fit your adoption cycle. To ensure that you benefit from new developments and innovations while minimizing the impact on your core operational systems, SAP uses enhancement packages to speed up the delivery of new functions. With SAP enhancement packages, you can install and activate new functions depending on your business needs without having to perform a system upgrade. You can selectively implement the new functions and activate the software upon business demand. As a result, you can isolate the impact of software updates and make new functions available faster due to shortened test cycles. Implementation There 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 full enhancement package. Instead, you can update the software components that are related to the 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 system behavior. The new functions are available in the system, but are not active. After the installation, no user interface or process change takes place. You must explicitly activate new functions so that they become visible in the system. As a result, changes are predictable and there are no side effects as only the activated areas change. With the switch framework technology (transaction SFW5), it is possible to control the activation of new SAP objects in ABAP-based SAP systems. The activation process triggers a 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 new developments 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 can check functional changes and the impact of an activated business function in advance in the business function documentation.

Test the installation and activation on a sandbox system.


July 2011 19

Maintenance SAP enhancement packages have Support Packages of their own that are equivalent to the Support Package versions of the underlying SAP system. You must install the enhancement package in combination with the latest available Support Package stack. This approach reduces installation, modification adjustment, and testing effort. Using this strategy, you can install SAP enhancement packages as a normal maintenance activity together with Support Package stacks. An enhancement package requires a specific Support Package stack level in the source release SAP system. If the SAP system is on a lower Support Package stack level, all relevant Support Package stacks are automatically included into the download queue, as well as the latest available Support Packages for the enhancement package. Tools The 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 Change Management work center) supports the download of a consistent queue that includes all necessary Support Packages and enhancement packages. In addition, SAP Solution Manager calculates a valid import queue for the selected SAP system and generates the enhancement 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 the upgrade of an SAP system to a higher release including an enhancement package, you use the standard installation and upgrade tools (SAPinst, SAPup and SAPJup). To install an enhancement package on an existing SAP system, you use the SAP Enhancement Package Installer (SAPehpi). It allows enhancement packages to be installed with reduced downtime. SAPehpi uses the shadow system installation strategy, a well-known feature in the upgrade technology.


20 July 2011

2.2. Key Facts About Enhancement Packages

The following list summarizes important facts about the enhancement package concept and recommended approaches:

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

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

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

We recommend installing the latest available enhancement package version. Install enhancement packages and Support Packages in one single step (this

includes the preconditioned Support Packages). SAP enhancement packages have Support Packages of their own that are equivalent

to the Support Package versions of the underlying SAP system. SAP enhancement packages have the same maintenance period as the underlying

core application. The installation of an enhancement package is irreversible. As long as you do not activate a business function, the installation of an

enhancement package has no impact on existing business processes or user interfaces.

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

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

Test the installation process and activation of new functions in advance on a sandbox system. Ensure that you evaluate the runtime and the SAP system behavior, its dependencies and impacts. Make sure that your SAP system is free of errors before going live.


July 2011 21

2.3. Enhancement Package Implementation In the following, you will find an overview of the steps involved in the three different enhancement package implementation scenarios.

Process Enhancement Package Installation in an Existing SAP System Process

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 the

download 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 dependency

analyzer 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 Solution

Manager (transaction SWF5) New Installation of an SAP System with Enhancement Packages Process

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

2. If you want to install further technical usages: 1. You identify the relevant installable parts of the enhancement package. 2. You make sure that you have set up your SAP Solution Manager system for the

download of packages, and that you have configured the Maintenance Optimizer. 3. You download the installation queue. 4. You perform the installation. 5. You activate the business functions using the switch framework (transaction

SWF5). 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


22 July 2011

In this scenario, you can use transaction SAINT for installing additional technical usages, because software component SAP_APPL 6.06 is already present in your system (part of technical usage Central Applications). This is a prerequisite for using SAINT.

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

Upgrade to an SAP System Including an Enhancement Package Installation Customers who are upgrading from a lower release to an SAP system for which enhancement packages are available can include parts of enhancement packages into the upgrade process.

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

Process 1. 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 the upgrade.

2. You identify the relevant installable parts of the enhancement package. 3. You make sure that you have set up your SAP Solution Manager system for the

download of packages, and that you have configured the Maintenance Optimizer. 4. You download the required parts of enhancement packages and Support Packages

as 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 package into 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.

Tools Standard upgrade tools (SAPup and SAPJup) SAP Solution Manager Maintenance Optimizer


July 2011 23

2.4. Product Versions, Instances and Software

Component Versions The following table gives an overview of the SAP product versions, instances and software components required for SAP for Telecommunications business scenarios and the corresponding installation guides.

This Master Guide provides just one way to implement each business scenario. For other ways to implement business scenarios, see the Scenario & Process Component List in SAP Service Marketplace at http://service.sap.com/scl. The Scenario & Process Component List helps you to find realization alternatives for SAP solutions, business scenarios and processes. It shows you which application components are needed to realize a business scenario or process.

Product Version – Instance Comprised Software Components, Add-Ons and Instances

Detailed Information

SAP ERP 6.0 Enhancement Package 6 – Utilities/Waste&Recycl./Telco Installation of: SAP ERP 6.0 – SAP ECC Server IS-UT 606 FI-CA 606 SAP APPL 6.06 EA-APPL 606 Based on: SAP NetWeaver 7.0– Application Server ABAP

For detailed information, see service.sap.com/erp-inst SAP ERP 6.0 Installation SAP ERP 6.0 Installation Activation of Business Function Set Telco: See the SAP ERP 6.0 EHP 5 Master Guide at service.sap.com/erp-inst SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 5 for SAP ERP 6.0 For detailed information, see service.sap.com/instguides SAP NetWeaver 7.0 (2004s) Installation 2 – Installation SAP NetWeaver Systems SAP NetWeaver 7.0 incl. EHP1 - Installation Guides - Installation Guides

SAP ERP 6.0 Enhancement Package 6 – SAP Utility Customer E-Services Installation of:

SAP IS-U/UCES – JSP Frontend


24 July 2011

SAP ERP 6.0 Enhancement Package 6 – SAP FSCM – Biller Direct Installation of:

SAP ERP 6.0 – SAP ECC Server Financial Supply Chain Management – Biller Direct 6.06 Based on: SAP ERP 6.0 – SAP FSCM – Biller Direct

For detailed information, see service.sap.com/erp-inst SAP ERP 6.0 Installation Installation SAP Biller Direct

SAP NetWeaver 7.03 Business Intelligence (BI) Content Add-On 7.46 Installation of: SAP Web AS 7.00 – SAP Web AS ABAP Enhancement Package 3

Installation of BI CONT 7.46

For detailed information, see service.sap.com/instguides SAP Components SAP Basis SAP Basis Installation on <Operating System>:<Database System>. For detailed information on the SAP NetWeaver 7.03 - Business Intelligence (BI) components, see the Master Guide SAP NetWeaver at service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.03 Installation. See SAP Note 1558363 BI_CONT 7.46: Information about installation and upgrade.

SAP NetWeaver 7.03 – Application Server Java Installation of SAP NetWeaver 7.03 – Application Server Java

For detailed information on the SAP NetWeaver 7.01 - Application Server Java components, see the Master Guide SAP NetWeaver at service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.03 Installation.

SAP NetWeaver 7.03 – Content Server Installation of: SAP Content Server 6.40

For detailed information, see service.sap.com/instguides SAP NetWeaver SAP NetWeaver 7.03 Installation Installation Standalone Engines

Installation SAP Content Server 6.40 on <Operating System>.

SAP NetWeaver 7.03 – Process Integration/XI Content Installation of: For detailed information, see


July 2011 25

XI Content IS-UT 606 service.sap.com/erp-inst SAP NetWeaver SAP NetWeaver PI 7.03 Installation 2 – Installation – SAP NetWeaver Systems Installation Guides – SAP NetWeaver PI 7.03

SAP EHP1 for SAP NetWeaver 7.03 – Adobe Document Services SAP EHP1 for SAP NetWeaver 7.03 – Search and Classification (TREX) Installation of: SAP NetWeaver 7.03 – Search and Classification (TREX) TREX 7.03

For detailed information, see service.sap.com/installnw70 SAP NetWeaver 7.03 Installation 3 – Installation – Standalone Engines Installation – SAP NetWeaver Search and Classification TREX

SAP CRM 7.0 – CRM Application Server Java Installation of: SAP Web AS 7.02 – SAP Web AS Java

For detailed information, see service.sap.com/instguides SAP NetWeaver 7.03 Installation 2 – Installation SAP NetWeaver Systems SAP EHP 3 for SAP NetWeaver 7.0 - Installation Guides service.sap.com/crm-inst SAP Enhancement Package 2 for SAP CRM 7.0 Install SAP EHP 1 for SAP CRM 7.0 – Installation Documentation

SAP CRM 7.0 – CRM Application Server ABAP Installation of: SAP Web AS 7.02 – SAP Web AS ABAP SAP CRM ABAP 7.0 SAP AP 7.00 SAP CRM UIF 7.0

For detailed information, see service.sap.com/installnw70 SAP NetWeaver 7.0 (2004s) Installation 2 – Installation SAP NetWeaver Systems SAP NetWeaver 7.0 SR - Installation Guides For detailed information, see service.sap.com/crm-inst SAP CRM 7.0 Install CRM Installation Guide

SAP CRM 7.0 – CRM Application Server Java


26 July 2011

Installation of SAP Web AS 7.0 – SAP Web AS Java Tealeaf 4.5 SAP Shared Web Components 7.0 SAP Shared Java Components 7.0 SAP Shared Java Application 7.0 CRM Java Web Components 7.0 CRM Java Components 7.0 CRM Java Applications 7.0 CRM IPC Mobile 7.0 SAP Java Data Dictionary 7.0

For detailed information, see service.sap.com/installnw70 SAP NetWeaver 7.0 (2004s) Installation 2 – Installation SAP NetWeaver Systems SAP NetWeaver 7.0 SR - Installation Guides For detailed information, see service.sap.com/crm-inst SAP CRM 7.0 Install Installation Guide

SAP CRM 7.0 - TREX Installation of: SAP NetWeaver 7.1 – Search and Classification (TREX) TREX 7.1

For detailed information, see service.sap.com/installnw70 SAP NetWeaver 7.0 (2004s) Installation 3 – Installation – Standalone Engines Installation SAP NetWeaver Search and Classification TREX

SAP EHP3 for NetWeaver 7.0 – Business Intelligence (BI) Installation of SAP Web AS 7.01 – SAP Web AS ABAP Installation of BI CONT 7.46

For detailed information, see service.sap.com/installnw70 SAP NetWeaver 7.0 (2004s) Installation 2 – Installation SAP NetWeaver Systems SAP NetWeaver 7.0 SR <> - Installation Guides See SAP Note 916834 BI_CONT 7.03: Installation and Upgrade Information.

SAP EHP3 for SAP NetWeaver 7.0 – Content Server Installation of SAP Content Server 6.40

For detailed information, see service.sap.com/installnw70 3 – Installation - Standalone Engines SAP Content Server Installation - Content Server 6.40 on <Operating System>


July 2011 27

2.5. System Landscape

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

The following graphic provides an overview of a possible system landscape for SAP for Utilities:

ECC – Host

RDBMS

CRM Host

TREX Host

IPC Host

IPC 5.0

Portal Host

FSCM - Host

SAP NetWeaver 7.03 Application Server ABAP

SAP CRM 7.02 – CRM Server

SAP NetWeaver 7.03 – SAP Content Server

RDBMS

Content Server Host

Based onSAP NetWeaver 7.03– Enterprise Portal

PI/XI Host

SAP NetWeaver 7.03 –Process Integration (PI/XI)

PI/XI Content FINBASIS 702

PI/XI Content FI-CA 702

BI - Host

RDBMS

Based onSAP NetWeaver 7.03 –Application Server ABAP

RDBMS

SAP NetWeaver 7.03 – Search and Classif. (TREX)

Based on SAP NETWEAVER 7.03 –AS ABAP

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

RDBMSRDBMS

SAP ERP 6.0 (EHP6) – SAP ECC

RTOM 7.1 SP01

RTOM Host

RDBMS

The IPC functions for pricing has been integrated in the Virtual Machine Container (VMC) of SAP NetWeaver 7.0. You no longer have to install SAP NetWeaver Application Server JAVA to run the JAVA applications for pricing, since these are now processed on SAP NW Application Server ABAP only. For scenarios in which you use priving, you have to activate the Virtual Machine Container (VMC), which is a prerequisite for running pricing. For information about activating VMC, see SAP Note 854170.

We do not recommend installing all components on one host. Instead you can distribute the components among several hosts, as shown in the diagram above. The diagram provides just one example; there are several ways to distribute the components. The distribution depends on many factors, such as sizing, security, available hardware, and so on. In practice, any distribution of components among hosts is possible.

Business Scenarios of SAP for Utilities and SAP for Waste and Recycling

28 July 2011

3. Business Scenarios of SAP for Utilities and SAP for Waste and Recycling 3.1. Scenarios for SAP for Utilities

3.1.1 Scenario Group Grid Life Cycle Management (Market Role Grid Management) Grid Engineering and Construction Description This business scenario enables you to construct, engineer, and extend grids. The options cover strategic portfolio management through to project accounting. You start a project with investment planning. During the project you use the Resource Planning and Time Management processes as well as the integration into Order Management. The scenario also supports you in creating equipment and managing documents. You can also integrate external systems such as CAD or GIS into the processes. Technical System Landscape The following SAP product versions and software instances are required for the Grid Engineering and Construction scenario:

SAP Enhancement Package 6 for SAP ERP 6.0 – Utilities/Waste&Recycl./Telco (current release)

For more information about the installation of these instances, see section Product Versions, Instances and Software.

Grid Maintenance and Operations Description You use this business scenario to maintain and operate transmission and distribution grids. This scenario provides various maintenance strategies that allows the grids to function reliably at the lowest possible costs. This includes preventive or reliability-based maintenance, as well as detailed planning of the maintenance budget. You can also integrate external systems such as SCADA or outage management systems into the processes. The Work Clearance Management process supports activities in safety-critical areas. Technical System Landscape The following SAP product versions and software instances are required for the Grid Maintenance and Operations scenario:


SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release) For more information about the installation of these instances, see section Product Versions, Instances and Software.


July 2011 29

Service Connection Management Description You can use this business scenario to install service connections and to execute disconnections and reconnections. You can also process complaints about grid services and service connections. Technical System Landscape The following SAP product versions and software instances are required for the Service Connection Management scenario.

SAP ERP 6.0 Enhancement Package 6 – Utilities/Waste&Recycl./Telco Optional:


3.1.2 Scenario Group Workforce Management Procurement and Warehousing (Market Role Grid Management) Grid Operation - Workforce Management Overview You, in the role of Grid Operator, can use this business scenario to ensure optimal use of your maintenance and service resources. This is particularly important for planning maintenance and service orders, workforce deployment, and dispatching tasks. Connections to mobile functions for processing order data play an increasingly important role in this business scenario. Technical System Landscape The following SAP product versions and software instances are required for the Grid Operation – Workforce Management scenario:



Grid Operation - Sourcing and Procurement of Goods and Services Description You, in the role of Grid Operator, can use this business scenario to increase the efficiency of external procurement of materials and spare parts (for example, poles, cross arms, insulators, cables and fuses) and services (for example, installations or replacements of poles, 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 possible sources to meet a requirement that has come up either during planning or in the specialist departments. You can also monitor goods deliveries and the current status of a service at any time. This business scenario also supports live auctions as well as any kind of bidding procedures to round off the procurement.


30 July 2011

Technical System Landscape The following SAP product versions and software instances are required for the Grid Operation – Sourcing and Procurement of Goods and Services scenario:



Grid Operation Inventory Management Description You, in the role of Grid Operator, can use this business scenario to manage the quantities and values of your material stock. It supports you in planning, entering, and verifying all goods movements. You can also take a physical inventory of the warehouse stock when performing settlements for stock. Technical System Landscape The following SAP product versions and software instances are required for the Grid Operation – Inventory Management scenario:



3.1.3 Scenario Group Preparation of Grid Usage Services (Market Role Grid Management) Definition of Grid Usage Products and Preparation of Billing Description You, in your role of the Grid Access Provider, can use this business scenario to prepare the billing of grid usage products. You define, manage, and publish grid usage tariffs in order to guarantee non-discriminatory grid access. These grid usage tariffs can be based on measurement 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 gas pipeline connecting a house with a grid. Technical System Landscape The following SAP product versions and software instances are required for the Definition of Grid Usage Products and Preparation of Billing scenario.

SAP ERP 6.0 Enhancement Package 6 – Utilities/Waste&Recycl./Telco SAP NetWeaver Business Intelligence Content Add-On 7.46



July 2011 31

3.1.4 Scenario Group Grid Usage Management (Market Role Grid Management) Service Provider Agreements Description You can use this business scenario to make service provider agreements with another service provider. In service provider agreements, two service providers specify rules and conditions 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. They also enter them in the IT system so they are accessible in subsequent business scenarios and processes.

The SAP Collaborative Services Management for Utilities component requires service provider agreements for the following business scenarios and related processes:

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 the

Metering Point Administrator) Definition of Grid Usage Products and Preparation of Billing (of the Grid

Access Provider)

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

Technical System Landscape The following SAP product versions and software instances are required for the Service Provider Agreements scenario.

SAP ERP 6.0 Enhancement Package 6 – Utilities/Waste&Recycl./Telco (current release)


Processing Grid Usage Registration Description You, in the role of the Grid Access Provider, can use this business scenario to exchange information with third parties, for example, with the Metering Point Administrator or the Balance Supplier, about changes in the master data of the point of delivery and about registrations for grid usage. You need this information to update contracts and billing-relevant data for grid usage billing. Technical System Landscape The following SAP product versions and software instances are required for the Processing Grid Usage Registration scenario:


Optional:


32 July 2011

SAP NetWeaver 7.03 – Process Integration with XI Content (current release) SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release) SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP (current

release) For more information about the installation of these instances, see section Product Versions, Instances and Software.

Grid Usage Receivables and Payment Handling Description You can use this business scenario to map the entire process of grid usage accounting in deregulated markets on Grid Access Provider side. This business scenario is based on a subledger that focuses on the needs of grid usage businesses that handle a high volume of master data and transaction data. A high level of automatization minimizes manual work. This business scenario provides full control and reconciliation of the subledger and the general ledger. Extensive handling capabilities for account receivables and payments ensure revenues and a low rate of outstanding debts. With pre-defined interfaces to SAP and non-SAP systems, receivables and payment handling are easily integrated with the general ledger and the billing system. This business scenario enhances the business scenario Receivables Management and Payment Handling with regard to grid usage specifics. With this business scenario, you can do the following:

Process an end customer’s individual receivables that are relevant for invoicing service providers (for example, suppliers)

Process aggregated receivables on invoicing service providers that have been deduced from the end customer’s receivables

Receive incoming payments on service provider level and payment advice notes (electronic or paper) from other service providers that refer to individual receivables You can allocate payments and payment advice notes and process them at end customer level. You can pay back payments on account. For outstanding payments, you can create lists of open bills, from which you can trigger dunning activities.

This business scenario includes communicating with other service providers in order to exchange payment advice notes and non-payment advice notes. The data that is exchanged relates to end customers to whom you provide services or with whom you have made contractual agreements. Technical System Landscape The following SAP product versions and software instances are required for the Grid Usage Receivables Management and Payment Handling scenario:




July 2011 33

3.1.5 Scenario Group Point of Delivery Administration (Market Role Metering Point Administration) Point of Delivery Master Data and Registration Management Description You, in your combined role as Metering Point Administrator and Grid Access Provider, can use this business scenario to manage the master data for a point of delivery (PoD). You validate and register changes in the master data and then forward them to all other market participants who are affected. These changes include changes of address, settlement-related data 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 of delivery start or stop their service. Furthermore, if other market participants contact you to request master data for a PoD, you can process these requests. All of these activities have to be in line with the rules of the national regulation authority. Using this business scenario, you can run your business in the deregulated utilities market. This allows you to fulfill regulatory requirements regarding market communication. Technical System Landscape The following SAP product versions and software instances are required for the Point of Delivery Master Data and Registration Management scenario:


Optional: SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 SAP NetWeaver 7.03 – Process Integration with XI Content


3.1.6 Scenario Group Meter Administration Services (Market Role Meter Management) Service Provider Agreements See

Request Management of Technical Device Master Data Description You, in your role of the Meter Administrator, can use this business scenario to respond to requests for technical master data that you receive from other market roles, for example, the Balance Supplier or the Grid Access Provider. These other market roles may also request changes to the technical device or the installation. You can forward these requests to the Meter Operator for execution and distribute the updated technical master data to all market participants who are involved at the point of delivery for which the devices have been changed. Technical System Landscape The following SAP product versions and software instances are required for the Request Management of Technical Device Master Data scenario.



34 July 2011



July 2011 35

Customer Complaints Management Description You can use this business scenario to process and resolve process complaints regarding customers' energy supply, service issues, or disputes by goodwill actions, such as issuing credit vouchers, rebates, coupons, refunds, and substitutions. This also includes the routing of complaints about services or products related to different market roles (for example, house connection from the distributor). The business process Complaints and Returns Analysis provides insights about the entire business scenario. Technical System Landscape The following SAP product versions and software instances are required for the Customer Complaints Management scenario:

SAP Enhancement Package 6 of- SAP ERP 6.0 – Utilities/Waste&Recycl./Telco (current release)

SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP (current release)

SAP NetWeaver 7.03 Enhancement Package 1 – Adobe Document Services (current release)

SAP NetWeaver 7.03 Enhancement Package 1 - Search and Classif. (TREX) (current release)

Optional: SAP NetWeaver Business Intelligence Content Add-On 7.46


3.1.7 Scenario Group Meter Operation Services (Market Role Meter Management) Meter and Device Management Description You use this business scenario to install and replace meters – either smart meters or traditional meters - and other devices at the customer location, and map the entire structure of installed devices. The scenario also provides support for the legally required inspection and certification of existing installed devices. You can use this scenario to integrate the processes of Material Management with the customer-related processes. It also supports data exchange with the Advanced Meter Infrastructure (AMI), that is, the Meter Data Unification System (MDUS). Technical System Landscape The following SAP product versions and software instances are required for the Meter and Device Management scenario:


Optional: SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46



36 July 2011

Meter Operation - Workforce Management Description You, in your role of the Meter Operator, can use this business scenario to ensure optimal use of your maintenance and service resources. This is particularly important for planning maintenance and service orders, workforce deployment, and dispatching tasks. Connections to mobile functions for processing order data play an increasingly important role in this business scenario. Technical System Landscape The following SAP product versions and software instances are required for the Meter Operation – Workforce Management scenario.



Meter Operation - Sourcing and Procurement of Goods and Services Description You, in your role of the Meter Operator, can use this business scenario to increase the efficiency of external procurement of materials and spare parts (for example, meters, transformers, insulators, cables, and fuses) and services (for example, installations or replacements of meters, external certifications of devices, and so on). This business scenario supports all phases of materials management (planning, purchasing, goods receipt, inventory management, and bill verification). You can determine possible sources to meet a requirement that has come up either during planning or in the specialist departments. You can also monitor goods deliveries and the current status of a service at any time. Technical System Landscape The following SAP product versions and software instances are required for the Meter Operation – Sourcing and Procurement of Goods and Services scenario:


SAP SRM 7.0 / SAP NetWeaver 7.03 – SRM Server Optional:

SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 For more information about the installation of these instances, see section Product Versions, Instances and Software

Meter Operation - Inventory Management Description You, in your role of the Meter Operator, can use this business scenario to manage the quantities and values of your material stock. It supports you in planning, entering, and verifying all goods movements. You can also take a physical inventory of the warehouse stock when performing settlements for stock. Technical System Landscape The following SAP product versions and software instances are required for the Meter Operation – Inventory Management scenario:



July 2011 37


3.1.8 Scenario Group Metered Data Collection Management (Market Role Metered Data Management) Service Provider Agreements See page 30.

3.1.9 Scenario Group Energy Settlement and Aggregation (Market Role Metered Data Management) Measurement Data Aggregation and Settlement Technical System Landscape The following SAP product versions and software instances are mandatory for the Measurement Data Aggregation and Settlement scenario:




3.1.10 Scenario Group Measurement Data Aggregation Administration (Market Role Metered Data Management) Service Provider Agreements See page 30.

3.1.11 Scenario Group Execution of Billing for Energy Products and Services (Market Role Execution of Billing for Energy Products and Services) Billing of Energy Products Description You, in the role of the Billing Agent, can use this scenario to execute billing and invoicing of energy 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 and managing billing master data as well as budget billing. Technical System Landscape The following SAP product versions and software instances are required for the Billing of Energy Products scenario.


Optional:


38 July 2011

SAP NetWeaver Business Intelligence Content Add-On 7.46 For more information about the installation of these instances, see section Product Versions, Instances and Software

Billing of Utility Services Description You, in the role of the Billing Agent, can use this business scenario to bill and invoice services for all kinds of customer groups including commercial and industrial, and residential customers. Your execution tasks include setting up and managing billing master data. Services can be executed by the retailer, the distributor or another market participant. Services are defined by the Balance Supplier, sold by the market role responsible for selling services (Customer Service Responsible) and billed by the Billing Agent. The Balance Supplier provides the billing rules. Billable services include street lights (unmetered), insurances, energy saving services, and technical grid or service connection services. Technical System Landscape The following SAP product versions and software instances are required for the Billing of Utility Services scenario:




3.1.12 Scenario Group Customer Financials Management (Market Role Metered Data Management Execution of Billing for Energy Products and Services) Receivables Management and Payment Handling Description You can use Receivables Management and Payment Handling to manage and monitor the receivables due from your customers. You can use the following components to help you manage receivables successfully:

Contract Accounts Receivable and Payable (FI-CA) Contract Accounts Receivable and Payable provides standard accounts receivable and accounts payable functions, such as payments, dunning, and installment plans. It has been designed specifically for processing mass data.

SAP Financial Supply Chain Management (FSCM): SAP Biller Direct and SAP Biller Consolidator for Electronic Bill Presentment and Payment With SAP Biller Direct, you can provide your customers with bills and credit memos electronically and enable them to make payments over the Internet. SAP Biller Consolidator connects billers and customers by means of network software. The software bundles bills with the required format conversions, assigns them to the correct customer, and makes them available over the Internet.


July 2011 39

You can also use Receivables Management and Payment Handling to carry out the steps necessary for closing subledger accounting in Contract Accounts Receivable and Payable, such as:

Transfer postings from Contract Accounts Receivable and Payable to the SAP component Accounting (FI, CO)

Reconcile posting material transferred Finally, with Receivables Management and Payment Handling, you can extract the tax-relevant data for the audit by the tax authorities from the productive system according to the German principles of data access and verifiability of digital documentation (GDPdU). The volume of mass data in Contract Accounts Receivable and Payable means that you cannot retain this data for the duration of the ten year retention period in the productive system. You can therefore extract the data prior to archiving into files and transfer these to the auditor. If you create the extract files in AIS format, you can transfer these to the auditor directly for evaluation in their auditing software. If an evaluation system is available for auditing, you can import the files containing the extracted data to this system for management and evaluation, and manage, display, select, and extract these files to other files. Technical System Landscape The following SAP product versions and software instances are required for the Receivables Management and Payment Handling scenario.


SAP ERP 6.0 Enhancement Package 6 – SAP FSCM – Biller Direct (current release) SAP NetWeaver 7.03 – Process Integration XI Content FI-CA (for External Cash

Payment Integration) (current release) Optional:


Reconciliation and Closing Description Reconciliation and closing supports closing operations and the reconciliation of postings between the contract account subledger and the general ledger. The closing operation includes the transfer of the necessary information to the relevant ledgers (G/L, Controlling, FM) and the reconciliation of the transferred information. The reconciliation mechanisms are highly automated and allow backtracking between the general and the subledger. Closing activities, such as foreign currency valuation, doubtful receivables, individual value adjustments and the resolution of deferred revenue are part of this scenario. Necessary data for authorities as well as closing reports are provided. Technical System Landscape The following SAP product versions and software instances are required for the Reconciliation and Closing scenario.




40 July 2011

Auditing Description You can use this business scenario to extract tax-relevant data from the productive system to SAP Utilities. This is used for auditing by the tax authorities according to the German principles for data access and verifiability of digital documentation. Due to the mass volume of data in Contract Accounts Receivable and Payable, it is not possble keep this data in the productive system for the ten years that you are legally obliged to retain data. Therefore, you can extract the data to files before it is archived. If you create the 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 to that system, where you can manage, display, select the data, and extract it back to the files. Technical System Landscape The following SAP product versions and software instances are required for the Auditing scenario.



3.1.13 Scenario Group Energy Capital Management - Retail (Market Role Balance, Forecast and Trade) Energy Data Management – Commodity Description This business scenario is applicable to the Balance Responsible Party, a market role or department of an energy supplier. You can use this business scenario to manage and process utilities time series data, such as load 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 increased volumes of load profiles. Load profiles of high granularity could, for example, be used in forecasting to improve schedules of a supplier. Therefore, suppliers can now base their schedules – dependent on the accuracy to be achieved – either on synthetic profiles or load profiles for customer segments such as residential customers or small and medium-sized businesses. This business scenario covers the following areas:

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

Forecasting and Schedule Management You can use this scenario to automatically create and provide energy forecasts and schedules.


July 2011 41

Load profile data basis for Billing This scenario provides the data basis to create energy supply bills based on different types of load profiles (for example, measured load profiles). Technical System Landscape The following SAP product versions and software instances are required for the Energy Data Management – Commodity scenario:



3.1.14 Scenario Group Selling of Energy and Services (Market Role Energy Sales, Customer Service) Campaign Management See the SAP CRM 7.0 Enhancement Package 2 Master Guide.

IC Marketing See the SAP CRM 7.0 Enhancement Package 2 Master Guide.

Account and Contact Management See the SAP CRM 7.0 Enhancement Package 2 Master Guide.

Selling of Energy Supply Products (E-Services) Description You can use this business scenario to identify the right products and retrieve product-related information such as descriptions of product characteristics and an estimated price based on your 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 utility company. Variants of these processes are available via other channels or for other user roles such as the Interaction Center Agent or the Key Account Manager. Technical System Landscape The following SAP product versions and software instances are required for the Selling of Energy Supply Products (E-Services) scenario.


SAP ERP 6.0 Enhancement Package 6 – SAP FSCM – Biller Direct (current release) SAP ERP 6.0 Enhancement Package 6 – SAP Utility Customer E-Services (current


Selling of Energy Supply Products (Interaction Center) Description You, in the role of the call center agent of a utility company (for example a utilities retailer), can use this business scenario to propose the right products (single/individual product or products in a package) to the customer and subsequently quote or sell these products in a


42 July 2011

fast and convenient way. For increased efficiency, one or more contracts can be set up and configured simultaneously. Within a product, you can sell a combination of the following:

utility products (representing energy supply products) materials (like air conditioners or other goods that are shipped to the customer) and 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 a waiting state until positive confirmation from other market participants is received. Only then does the supply contract become active. The utility company monitors the contracts according to their terms and conditions by checking the integrity of the contract when changes are required. Additionally, follow-up activities can be triggered. For example, a notification is sent to the relevant sales manager when high-value supply contracts are lost to a competitor. The processes described in this business scenario are specific to call-centers. Variants of these processes are available via other channels or for other user roles. Technical System Landscape The following SAP product versions and software instances are required for the Selling of Energy Supply Products (Interaction Center) scenario.


SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP SAP NetWeaver 7.03 – Adobe Document Services

Optional: SAP CRM 7.0 Enhancement Package 2 – CRM Application Server Java SAP NetWeaver 7.03 – Search and Classif. (TREX) SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release)


Selling of Energy Supply Products (Key Account Management) Description You, in the role of the Key Account Manager of a utility company (for example a retailer), can use this business scenario to manage the selling contract management processes for commercial and industrial (C&I) customers. This includes managing sales opportunities as well 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 necessary individually for the customer. Finally, you can turn quotations into supply contracts in an easy and convenient manner. The supply contracts are now completely prepared for billing processes. A main focus lies on the execution of mass processes for handling many quotation and contract items per document at the same time. Large C&I customers may have many hundreds of points of delivery for which the key account manager has to manage quotations and contracts. In liberalized markets, regulatory compliance requires additional processes. As a typical market rule, supply contracts cannot be directly concluded and activated. Before activation, other market participants need to be involved. This is part of the business scenario Registration 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 a waiting state until positive confirmation from other market participants is received. Only then


July 2011 43

does the supply contract become active. Moreover, this business scenario allows the monitoring of the sales pipeline and analytical evaluations like the analysis of contract or customer profitability. This business scenario is used by the Key Account Manager. Variants of these processes are available thrpough other channels or for other user roles, for example the Interaction Center Agent. Technical System Landscape The following SAP product versions and software instances are required for the Selling of Energy Supply Products (Key Account Management) scenario.


SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP SAP NetWeaver 7.03– Adobe Document Services SAP NetWeaver 7.03 – Search and Classif. (TREX)

Optional: SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release) SAP CRM 7.0 Enhancement Package 2 – CRM Application Server Java SAP NetWeaver 7.03 – Process Integration (current release)


Selling of Utility Services Description You can use this business scenario to address the sale of utility-related services that typically occurs in the call center of a utility operating in a competitive energy retail market. The retail company acts as the Customer Service Responsible and is the single point of contact to the customer. The utility-related services can either be service products (for example, meter services, meter reading services, meter billing services, energy consultancy services, installation or maintenance services), materials (for example, energy efficient appliances) or a combination of both. This scenario complements the scenario of setting up energy supply products as well as managing energy contracts and quotations. The processes described here are available via several channels like Call Center or Customer Self-Service. Technical System Landscape The following SAP product versions and software instances are required for the Selling of Utility Services scenario.



SAP ERP 6.0 Enhancement Package 6 – SAP FSCM – Biller Direct (current release) SAP SRM 7.0 / SAP NetWeaver 7.03 – SRM Server SAP SEM


3.1.15 Scenario Group Customer Service Management


44 July 2011

Customer Interaction Management (E-Services) Description You can use this business scenario to address the utility-specific processes that are made available in the Internet portal or Internet presence of a typical utility retailer. This includes many variations of the deregulated contract management process, entering meter readings, billing and financial inquiries, customer requests for disconnection and reconnection, and other supporting processes associated with the maintenance of customer or master data. Technical System Landscape The following SAP product versions and software instances are required for the Customer Interaction Management (E-Services) scenario:

SAP Enhancement Package 6 of SAP ERP 6.0 – Utilities/Waste&Recycl./Telco (current release)

SAP Enhancement Package 6 of- SAP ERP 6.0 – SAP FSCM – Biller Direct (current release)

SAP Enhancement Package 6 of- SAP ERP 6.0 – SAP Utility Customer E-Services (current release)


Customer Interaction Management (Interaction Center) Description You can use this business scenario to address the utility-specific processes that used in the call center of a typical utility retailer. This includes various processes that manage supply contracts as well as packages of contracts and other products or programs. It also includes processes to enter meter readings, handle billing and financial inquiries, manage customer requests for disconnection and reconnection, and other supporting processes associated with the maintenance of customer or master data. Technical System Landscape The following SAP product versions and software instances are required for the technical implementation of Customer Interaction Management (Interaction Center) scenario:



SAP NetWeaver 7.03– Adobe Document Services (current release) Optional:

SAP NetWeaver 7.03 - Search and Classif. (TREX) SAP NetWeaver Business Intelligence Content Add-On 7.46 SAP CRM 7.0 Enhancement Package 2 – CRM Application Server Java

Customer Complaints Management See page 34.

IC Management See the SAP CRM 7.0 Enhancement Package 2 Master Guide.


July 2011 45

3.1.16 Scenario Group Preparation of Energy Supply Products and Services (Market Role Preparation of Energy Products and Billing) Definition of Energy Supply Products and Preparation of Billing Description You can use this business scenario to define and prepare for billing, invoicing and the subsequent cash processes. Technical System Landscape The following SAP product versions and software instances are required for the Definition of Energy Supply Products and Preparation of Billing scenario.


SAP NetWeaver Business Intelligence Content Add-On 7.46 (current release) Optional:

SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP For more information about the installation of these instances, see Product Versions, Instances and Software Component Versions [page 11].

Definition of Utility Services and Preparation of Billing Description You can use this business scenario to specify and prepare services for billing, invoicing, and the subsequent cash process. Technical System Landscape The following SAP product versions and software instances are required for the Definition of Utility Services and Preparation of Billing scenario.


SAP NetWeaver Business Intelligence Content Add-On 7.46 (current release) For more information about the installation of these instances, see section Product Versions, Instances and Software.

3.1.17 Scenario Group Handling of Device and Measurement Data (Market Role Preparation of Energy Products and Billing) Billing-Relevant Device and Measurement Data Management Description You can use this business scenario to request and receive billing-relevant device and measurement data. You can request and store device data that you have received from the Meter Administrator. The Meter Administrator also informs you if device data has changed. Interfaces to various external systems allow you to receive measurement data that you can validate and store. You send requests for non-periodic meter readings to the relevant market participant. Technical System Landscape


46 July 2011

The following SAP product versions and software instances are required for the Billing-relevant Device and Measurement Data Management scenario:




Disconnection und Reconnection Management Overview The Disconnection and Reconnection Management scenario is applicable to the Balance Supplier Party, a market role or department of a (energy) supplier. You can use this business scenario to manage and process the disconnection and reconnection requests. New state-of-the-art smart meter technology, Advanced Meter Infrastructure (AMI), allows a bi-directional information flow between an ERP system and a smart meter. Smart meters, for use by commercial and industrial (C&I) customers as well as household customers, can be disconnected and reconnected automatically, for example, if energy theft is detected. You can use this business scenario in order to handle disconnection and reconnection processes in either an AMI or a non-AMI environment. This business scenario allows the handling of disconnection and reconnection processes as well as triggering communication between 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 underlying processes in a more efficient and cost-saving manner compared to processes where field service representatives have to perform disconnection or reconnection manually at the end customer site. Furthermore, disconnection and reconnection processes can be triggered more often. Technical System Landscape The following SAP product versions and software instances are required for the Disconnection and Reconnection scenario.


Optional: SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46


3.1.18 Scenario Group Grid Usage and Service Provider Agreement – Retail (Market Role Preparation of Energy Products and Billing)

Service Provider Agreements See page 30.


July 2011 47

Registration for Grid Usage Description This business scenario is applicable to liberalized utilities markets and contains processes relevant to the Balance Supplier market role. In liberalized utilities markets several independent market participants (retailers, grid companies, and so on) collaborate with each other. The market role model introduced by ebIX describes the business models of the different participants in terms of market roles. One of these market roles is the Balance Supplier (usually the utilities retailer). You, in the role of the Balance Supplier (retailer), can use this business scenario to request that the Metering Point Administrator (usually the distribution company) changes grid usage registration at a point of delivery (PoD – the location where the customer consumes the energy) and informs all affected market parties. Business processes are defined by the regulation 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 this PoD. The Metering Point Administrator is responsible for maintaining this registration and informing the other market participants who are either involved or affected by the change. If the end customer has previously been supplied with energy by another Balance Supplier, that Balance 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 (for example, timelines or details about message exchange) to be considered. After you have sent the request for registration, the Metering Point Administrator checks all rules and responds with either a positive or negative registration message. Upon ending a supply contract with the end customer and ending the supply for the related PoD, 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 the contract. In other cases, you receive messages from both another Balance Supplier and the Metering Point Administrator informing you about a customer loss and the corresponding termination 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 market communication Technical System Landscape The following SAP product versions and software instances are required for the Registration for Grid Usage scenario:


SAP CRM 7.0 Enhancement Package 2 (for Registering for Grid Usage Terminating Grid Usage)

Optional: SAP NetWeaver 7.03 – Process Integration with XI Content (current release) (for

connection to third-party system for example, EDIFACT-Adapter) SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release)



48 July 2011

Grid Usage Invoice Verification and Payment Overview You can use this business scenario to map the process of grid usage invoices in deregulated markets at the balance supplier’s side. This includes communicating with other service providers in order to receive bills, create complaints, perform payments, and send payment or non-payment advice notes. The data that is exchanged relates to end customers (points of delivery) to whom you provide services or with whom you have made contractual agreements. You can receive electronic bills (or paper bills), have them checked automatically, 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 Landscape The following SAP product versions and software instances are required for the Grid Usage Invoice Verification and Payment scenario:


Optional: SAP NetWeaver 7.03 – Process Integration (PI/XI) SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46


Invoice Verification and Payment of Services Overview You can use this business scenario to receive electronic bills (or paper bills), have them checked automatically, and post them to accounting. You can then clear the posted bill documents, create payment advice notes for service providers, and send them in electronic or paper format. The individual data exchange processes are logged and you can monitor them closely. The invoices considered in this scenario are for services (other than grid usage) provided by a service provider for a metering point. Generally, the charges for these services are event and/or time-based charges for each point of delivery, for example, charges for special meter-reading services within a month (event-based), or charges for meter administration services (time-based) (see grid usage invoices, which are generally based on energy consumption and/or based on demand for each point of delivery). Technical System Landscape The following SAP product versions and software instances are required for the Invoice Verification and Payment of Services scenario:





July 2011 49

3.1.19 Scenario Group Customer Financials Management (Market Role Execution of Energy Billing & Customer Financials Management (Billing Agent))

Receivables Management and Payment Handling See page 36.

Reconciliation and Closing See page 37.

Auditing See page 38.

3.1.20 Scenario Group Execution of Billing for Energy Products and Services (Market Role Execution of Energy Billing & Customer Financials Management (Billing Agent)) Billing of Energy Products See page 36.

Billing of Utility Services See page 37.

3.1.21 Scenario Group Customer Credit Risk-Based Collections Management (Market Role Financial Customer Collection Service (Collection Agent))

Credit and Collections Management See the SAP ERP 6.0 Enhancement Package 6 Master Guide.

3.1.22 Scenario Group Plant Life Cycle Management (Market Role Generation (Plant Operator)) Decommissioning Description This business scenario addresses the utility-specific processes that typically exist within the call center of a vertically- integrated utility company. This includes the many variations of the move-in/ move-out process, metering, billing and financial inquiries, and other supporting processes associated with the maintenance of customer or master data. The processes described here are call center-specific, but variations of these processes are available via other channels. Other relevant scenarios for the call-center are

IC Marketing


50 July 2011

IC Sales with CRM Sales Order IC Sales with ERP Sales Order IC Service IC Management

Technical System Landscape The following SAP product versions and software instances are required for the Customer Service in the Interaction Center scenario:




3.1.23 Scenario Group Resource Management (Market Role Generation (Plant Operator)) Workforce Management Description With this business scenario, you can optimize the use of your plant maintenance and service resources. In addition to planning plant maintenance and service orders, human resource planning and dispatching tasks are also significant. This scenario also accommodates the growing role of providing a connection to mobile order data processing. Technical System Landscape The following SAP product versions and software instances are required for the Workforce Management scenario.



Sourcing and Procurement of Goods and Services Technical System Landscape The following SAP product versions and software instances are required for the Sourcing and Procurement of Goods scenario.



Inventory Management Description With this business scenario, you map the quantity-based and value-based handling of your material stocks. The scenario supports you when planning, entering, and approving the movement of goods. You can also carry out an inventory of the warehouse stocks in order to account for the stocks. Technical System Landscape


July 2011 51

The following SAP product versions and software instances are required for the Inventory Management scenario:



3.1.24 Scenario Group Energy Capital Management - Generation (Market Role Generation (Plant Operator)) Energy Data Management – Commodity See page 39.

3.2. Scenario Groups for SAP for Waste and Recycling

3.2.1 Scenario Group Development Services Service and Product Planning Description With 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 the costs for communal waste disposal services. Technical System Landscape The following SAP product versions and software instances are required for the Service and Product Planning scenario:


SAP Waste and Recycling Applications by Prologa 5.0 – SAP ECC Server Add-On (current release)

Optional: SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release) SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP (current

release) For more information about the installation of these instances, see section Product Versions, Instances and Software

3.2.2 Scenario Group Selling of Waste Services Enhanced Contract Management for Waste and Recycling Description The Contract Management for SAP Waste and Recycling supports you in managing quotations, 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 data generator only after transfer into a contract.


52 July 2011

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 Landscape The following SAP product versions and software instances are required for the Enhanced Contract and Account Management for Waste and Recycling scenario:




Campaign Management See the SAP CRM 7.0 Enhancement Package 2 Master Guide.

IC Marketing See the SAP CRM 7.0 Enhancement Package 2 Master Guide.

Lead-to-Cash See the SAP CRM 7.0 Enhancement Package 2 Master Guide

Quotation and Order Management See the SAP CRM 7.0 Enhancement Package 2 Master Guide.

Integrated Sales Analysis See the SAP CRM 7.0 Enhancement Package 2 Master Guide.

3.2.3 Scenario Group Planning and Fullfillment of Services Waste Flow Management Description You can use this business scenario to manage waste flows within and outside of your company. For this purpose, you can define special material management settings and also define 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 it with data from planned flows. You can be sure that, for your waste flows, the legal monitoring requirements and the necessary documents are generated. Technical System Landscape The following SAP product versions and software instances are required for the Waste Flow Management scenario.


SAP Waste and Recycling Applications by Prologa 2.0 – SAP ECC Server Add-On Optional:


July 2011 53

SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release) SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP (current


Cleaning and Winter Services Description You 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. The location of the objects is described using addresses or geocoordinates. The system also allows 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 waste disposal orders for cleaning objects defined, and can then bill the customer. Technical System Landscape The following SAP product versions and software instances are required for the Cleaning and Winter Services scenario:

SAP Enhancement Package 6 for SAP ERP 6.0 – Utilities/Waste&Recycl./Telco SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP



Container Services Description This business scenario provides you with the business processes required for providing, collecting, and changing containers, from creating a periodic or aperiodic waste disposal order to confirming orders using mobile devices (such as on-board units). Technical System Landscape The following SAP product versions and software instances are required for the Container Services scenario:


Optional: SAP NetWeaver Business Intelligence Content Add-On 7.46 SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP


Discharge System Services Description This business scenario provides you with the business processes required for emptying containers (such as household trashcans), from creating a periodic or aperiodic waste disposal order to confirming orders using mobile devices (such as on-board units). Technical System Landscape


54 July 2011

The following SAP product versions and software instances are required for the Discharge System Services scenario.


Optional: SAP CRM 7.0 Enhancement Package 2 – CRM Application Server ABAP SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46


Bulky (Loose) Waste Collection Description Public and private waste disposal companies can use this business scenario to create common waste disposal services for commercial and municipal customers. The collection of bulky and loose waste includes creating waste disposal orders for bulky waste, manual planning and disposition, outputting waste disposal orders, and confirming completed orders. Technical System Landscape The following SAP product versions and software instances are required for the of Bulky (Loose) Waste Collection scenario:


Optional SAP NetWeaver Business Intelligence Content Add-On 7.46


Waste Asset and Container Management Description You can use this business scenario and its standard processes to manage central waste disposal objects and containers. Technical System Landscape The following SAP product versions and software are required for the Waste Asset and Container Management scenario.


Optional: SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release)


3.2.4 Scenario Group Treatment and Disposal Weighing Description You can use this business scenario to define the processes for the automated entry of weighing data. The system allows you to use direct data communication with external weighing systems to receive data and to process it directly in SAP Waste and Recycling.


July 2011 55

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 the appropriate postings for existing waste disposal documents. Technical System Landscape The following SAP product versions and software instances are required for the Weighing scenario.




Treatment and Disposal Description You can use this business scenario to define the infrastructure for your waste disposal facilities and recyclable material processing facilities. You can define any type of facility (such as waste incineration plant, dump, intermediate storage facility, or storage facility for recyclable material). You can define and execute typical process and process templates for waste treatment and preparation in the different facility types. The system also allows you to map the separation and merging of waste from the same waste fraction or different waste fractions. The seamless integration in the Materials Management (MM) component ensures that the stock and material flow mapped correctly. Technical System Landscape The following SAP product versions and software are required for the Treatment and Disposal scenario.




3.2.5 Scenario Group Waste Asset Life-Cycle Management Plant Engineering and Construction Description With this business scenario, you can construct, extend, and change power plants. The options cover comprehensive project planning through to project-specific accounting. You can start projects based on a comprehensive, company-wide project portfolio and strategically plan your investements. During the project you use the Resource Planning and Time Management processes as well as the integration with Order Management. The project not only supports you with creating equipment and with document management, but also with monitoring and documenting changes to your equipment or the configuration of power plants. You can also integrate external systems such as CAD or GIS into the processes. Technical System Landscape The following SAP product versions and software instances are required for the Plant Engineering and Construction scenario:


56 July 2011




Plant Maintenance Description You can use this business scenario to operate power plants. The scenario provides you with various processes to ensure that your power plant runs reliably and cost-effectively The option cover the entrie work order cycle – from budgeting and planning, through preparing and executing tasks, to confirming, reporting, and managing. You can control industial hygiene and safety measures using the Work Clearance Management processes. You can also integrate external systems for process information (PI) or control systems (SCADA - Supervisory Control and Data Acquisition) with the processes. Analytics tools are available to optimize the reliability of equipment. Technical System Landscape The following SAP product versions and software instances are required for the Plant Maintenance scenario:




Decommissioning See page 48.

3.2.6 Scenario Group Billing of Waste Services Billing for Residential Customers Description You use this business scenario to bill, invoice, and print your company’s supply and demand services for residential customers. Contract billing allows you to map all possible combinations of different billing steps. The dynamic rate determination allows you to quickly adjust complete customer groups for new rates in the company. Contract billing also allows you to map rate models to deregulated markets. Invoicing provides the necessary processes for creating bills, in connection with a contract billing. It guarantees the integration of Contract Accounts Receivable and Payable (FI-CA) in SAP Utilities (IS-U). Technical System Landscape The following SAP product versions and software instances are required for the Billing for Residential Customers scenario.


SAP NetWeaver Business Intelligence Content Add-On 7.46 (current release)


July 2011 57


Billing for Commercial and Industrial Customers Description You can use this business scenario to bill, invoice, and print your company’s supply and demand services for commercial and industrial customers. Contract billing allows you to map all possible combinations of different billing steps. The dynamic rate determination allows you to quickly adjust complete customer groups for new rates in the company. Contract billing also offers provides the opportunity to map rate models to deregulated markets (for example, real-time pricing). Invoicing provides the necessary processes for creating bills, in connection with a contract billing. It guarantees the integration of contract accounts receivable and payable (FI-CA) in SAP Utilities (IS-U). Technical System Landscape The following SAP product versions and software instances are required for the Billing for Commercial and Industrial Customers scenario.




3.2.7 Scenario Group Credit Risk and Collections Management Receivables Management and Payment Handling See page 36.

Reconciliation and Closing See page 37.

Auditing See page 38.

3.2.8 Scenario Group Customer Service Management Customer Service in the Interaction Center Description This business scenario addresses the utility-specific processes that typically exist within the call center of a vertically- integrated utility company. This includes the many variations of the move-in/ move-out process, metering, billing and financial inquiries, and other supporting processes associated with the maintenance of customer or master data. The processes described here are call center-specific, but variations of these processes are available via other channels. Other relevant scenarios for the call-center are

IC Marketing IC Sales with CRM Sales Order IC Sales with ERP Sales Order IC Service


58 July 2011

IC Management Technical System Landscape The following SAP product versions and software instances are required for the Customer Service in the Interaction Center scenario:




Complaints and Returns Management See the SAP CRM 7.0 Enhancement Package 2 Master Guide.


July 2011 59

Electronic Customer Services Description This business scenario allows utility company customers to use web application SAP Utility Customer E-Services (SAP UCES) to change customer data, enter the current meter reading, and execute move-ins and move-outs, among other things. SAP IS-U /Utility Customer E-Services contains the application SAP FCSM Biller Direct. Technical System Landscape The following SAP product versions and software instances are required for the Electronic Customer Services scenario:


Optional: SAP ERP 6.0 Enhancement Package 6 – SAP FSCM – Biller Direct SAP ERP 6.0 Enhancement Package 6 – SAP Utility Customer E-Services




60 July 2011

3.3 Other scenarios

Demand Side Management Description Demand Side Management (DSM) is a process of managing the energy demand of end users by influencing the consumed energy quantity or the patterns of energy use. It promotes energy efficiency and aims to optimize generation resources by reducing peak demand when energy supply systems are under stress. You can use this business scenario to define DSM programs and applications, receive and review applications submitted by end customers, create and manage agreements that define the specific commitments made by both the energy supplier and the customer, pay out and distribute incentives, and monitor and analyze program performance Technical System Landscape The following SAP product versions and software instances are required for the Demand Side Management scenario:



SAP NetWeaver 7.03 Business Intelligence Content Add-On 7.46 (current release) Optional:

SAP NetWeaver 7.03 – Process Integration (PI/XI) SAP NetWeaver 7.03 - Search and Classif. (TREX)



July 2011 61

Document Presentment by StreamServe Description You use this business scenario to implement flexible and automated document presentment and output from SAP NetWeaver-based applications. The scenario is realized using SAP Document Presentment by StreamServe and provides:

High-volume output capabilities Multi-channel output Document process automation, personalization, and optimization

Technical System Landscape The following SAP product versions and software instances are required for the Document Presentment by StreamServe scenario: Mandatory:

SAP Enhancement Package 6 for SAP ERP 6.0 – Utilities/Waste&Recycl./Telco For more information about the installation of these instances, see section Product Versions, Instances and Software.


62 July 2011

Measurement Data Processing Description You, in the role of the Metered Data Collector or Metered Data Responsible, can use this business scenario to collect metered data You can collect metered data periodically according to a specific schedule, or aperiodically. If metered data collection is scheduled, the system determines the relevant meters and creates meter reading orders. Depending on the type of measurement data (discrete or interval measurement data), and the method used for collecting that data, you have different options: For discrete measurement data, if you are planning a reading by a meter reader you can print the meter reading orders or download them to a mobile data entry device. If you are planning to do a customer self reading, you can print cards and send them to your customers. You can transfer the meter reading results to the system using mass activities, or you can enter them manually. If the meter is an advanced meter which can be read remotely and you use MDUS (Meter Data Unification and Synchronization) integration, you can send out meter reading requests for discrete meter reading to the MDUS system. The MDUS system then reads the meters and sends the meter reading results as requested. As soon as meter reading results are entered, the system carries out validations/ validates the data. Results that do not pass validation are implausible and the system does not process these any further. The agent can however correct such meter reading results manually or release them (nonetheless).If data is missing, the system provides replacement values on the basis of estimation procedures. To calculate consumption values on the basis of /from meter reading differencesduring the meter reading process, you can activate the quantity determination function. You can estimate the consumption based on measurement data such as meter reading results or consumption values. You can monitor the progress of the meter reading process, and check which meter readings are plausible, implausible, or missing. In Monitoring, you can also check which contracts have already been billed. If you use Business Process Exception Management, you can assign clarification cases to agents, who then process the cases. Depending on the problem type, different business processes are allocated to the cases. These business processes support the agents in processing and solving the cases. Finally, you can provide the data obtained to other market participants. For interval measurement data you use this business scenario to collect and manage interval-related data in the form of measured load shapes or synthetic profiles. You can also manage price profiles. The interval measurement data is made available in the system using automated meter reading systems including synchronization processes. You can also receive interval-related data (such as energy consumption values) from other market participants. In contrast to measured load shapes, which represent exact consumption or demand quantities, synthetic profiles can be used as standard profiles for a large number of customers with comparable consumption patterns. When no metered data is available yet, you can use synthetic profiles to generate profile values on the basis of predefined and corresponding day and annual profiles. You can send interval-related data (such as energy consumption values, prices, etc.) to other market participants using enterprise services. For example, a distributor who performs the metered data responsible role, can send interval data (profiles) to a supplier who performs the balance supplier role. You can schedule the sending of profiles in advance and thus send scheduled profiles on the corresponding due dates. You can monitor the intercompany data exchange. The data exchange is based on enterprise services and the process is mass data-enabled. Technical System Landscape


July 2011 63

The following SAP product versions and software instances are required for the Measurement Data Processing scenario:




Plant Operations Description You can use this business scenario to operate power plants. The scenario supports you during the typical processes of regular operation such as monitoring and checking energy generation, executing regular inspections, and determining and reporting unusual activity. During revision phases and when a power plant is shut down, you can plan and coordinate your production team's work. Technical System Landscape The following SAP product versions and software instances are required for the Plant Operations scenario:




Solution Wide Topics

64 July 2011

4. Solution Wide Topics 4.1. Service-Oriented Architecture (SOA)

SAP´s delivery on SOA (service-oriented architecture) differs from the pure architectural concept of SOA in the delivery of ready-to use enterprise services. Enterprise services are SAP-defined Web services which provide end-to-end business processes or individual business process steps that can be used to compose business scenarios while ensuring business integrity and ease of reuse. SAP designs and implements enterprise service interfaces to ensure semantic harmonization and business relevance. This section deals with the service-enablement of SAP Business Suite 7.

Service Enablement

The service enablement of SAP Business Suite consists of one or more of the following SAP components:

SAP Business Suite 7

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

SAP NetWeaver PI 7.0 or higher

SAP NetWeaver Process Integration (SAP NetWeaver PI) is an open integration and application platform that provides tools enabling you to set up a service-oriented architecture for business applications. You can use the platform for providing, discovering, and consuming services, integrating applications using the integration server, and managing business processes. Process integration is required in a runtime 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 that contains the definition of all enterprise services and models. ES Repository is shipped with SAP NetWeaver PI 7.1 and with SAP NetWeaver CE 7.1. The Enterprise Services Repository is a design time environment that enables you to create and enhance enterprise service definitions and to view enterprise service models.

In a SAP NetWeaver 7.0 landscape you will require the Integration Repository to create and enhance enterprise service definitions in a design time environment.

SAP NetWeaver CE 7.1


July 2011 65

The SAP NetWeaver Composition Environment (SAP NetWeaver CE) provides a robust 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 services. SAP NetWeaver CE offers the tools and the environment necessary for running 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 host the enterprise service online documentation.

Services Registry

The Services Registry is shipped with SAP NetWeaver PI 7.1. and SAP NetWeaver CE 7.1. and is required for the publication of enterprise service end-points (Web services) 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 different runtime and design time use cases:


66 July 2011

SAP Applications

SAP Business Suite

SAP NetWeaver PI 7.0 (Integration Repository)

SAP NetWeaver PI 7.1 (ES Repository)

SAP NetWeaver CE 7.1 (ES Repository)

SAP Solution Manager 7.0 (Solution Composer)

SAP NetWeaver 7.1 Services Registry

Runtime Usage: Enterprise Service Provisioning

Required Optional

Process integration and mediated communication

One option required

Design Time Usage: Create and enhance enterprise service definitions

Required One option required Recommende

d

View enterprise service models

One Option Required Recommended

Design and develop composite applications

Required Recommended

Recommended

Enterprise service online documentation

Required

Publications of enterprise service end-points

Optional Required

Installation of the Service-Oriented Architecture (SOA)

The installation of service interfaces, and therefore the service enablement of SAP Business Suite, 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 identify the 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


July 2011 67

SAP Note 1324838 provides a mapping of business functions and software component versions to technical usages. You use this documentation to identify the required technical usages for your list of software component versions and business functions.

Installation of the software component ECC-SE

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

Selection and installation together with the other parts of the enhancement package

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

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

To install the content required for the enterprise service definitions you must select the 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.1 versions. Unpack the ZIP file and copy the tpz files corresponding to your SAP NetWeaver version into the import directory of your Integration Repository (for SAP NetWeaver PI 7.0) or Enterprise Services Repository (for SAP NetWeaver ES Repository 7.1). Use the import function to import the content files into the corresponding 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 the technical 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 Enterprise Services Repository. Use the import function to import the content files into the Enterprise 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 you must download the content file for the corresponding Business Suite application product version from the Service Marketplace. Then you must import the content file into your Solution Composer. Refer to SAP Note 1224284 for further information.


68 July 2011

Services Registry (optional)

The services registry is shipped with SAP NetWeaver PI 7.1 and CE 7.1. You must install the services registry and then publish the enterprise services from the Business Suite application to the registry using the transaction SOAMANAGER in the backend.

For further information regarding the installation of SAP NetWeaver PI, CE and ES Repository, refer to the corresponding SAP NetWeaver Installation and Master Guides.

Related Documentation

For more information about the service-oriented architecture (SOA), see the following information sources:

SDN Community in the SAP Network at https://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 at

https://wiki.sdn.sap.com/wiki/x/LQ0 (registration required) SAP Note 1224284: Enterprise Services, Installing and Accessing the SOA

Documentation SAP Note 1359215: Technical prerequisites for using enterprise services SAP note 838402: Problems with non-Unicode system landscapes

References

July 2011 69

5. References 5.1. Tools and Resources for Planning Your

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

Tools

On SAP Service Marketplace, we provide some tools that allow you to look up more detailed information about business scenarios and business processes. These tools include the following:

Tools for Looking Up Information about Business Processes and Scenarios

Tool Purpose Business process repository (BPR) viewer

To look up descriptions of business scenarios and business processes

Scenario and process component list

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

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

Tools for Supporting Installations and Upgrades

Tool Purpose Solution Manager System Landscape To model and set up your system landscape SAP Solution Manager Maintenance Optimizer

To install support packages and SAP enhancement packages

Business process repository

To access configuration documentation, links to Customizing activities and master data transactions, specifically tailored for individual business processes or business scenarios

Business process change analyzer (available with SAP enhancement package 1 for SAP Solution Manager 7.0)

To analyze the effects of transports and support packages as well as activation logs for business functions

As of SAP Solution Manager 7.0 with support package 23, these tools have been enhanced to provide a better support for the setup of your system landscape and for installing and activating business functions. For more information, see SAP Library for SAP Solution Manager on SAP Help Portal at http://help.sap.com under SAP Solution Manager.

SAP Solution Manager: Implementation Content

References

70 July 2011

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

System Landscape Guide

To get an overview of the necessary steps for planning a system landscape, use the System Landscape Guide on SAP Service Marketplace at http://service.sap.com/instguides under SAP Business Suite Applications. The guide also provides 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) Viewer

The business process repository viewer (BPR viewer) is a tool on SAP Service Marketplace that allows you to preview the existing business scenarios and business processes that are shipped as part of SAP Solution Manager content. You can make use of the information in SAP Solution Manager during your implementation project by taking 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 Viewer Procedure Calling Up the BPR Viewer

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

Working with the BPR Viewer

To call up information about business scenarios or business processes, 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

For each business scenario, business process, or implementable step, you can select between different versions that depend on varying components and releases. To display the descriptions of a business scenario, business process, or implementable step, choose the

References

July 2011 71

Documentation tab page. To display configuration documentation, choose the Configuration tab page.

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

Scenario and Process Component List

The scenario and process component list (SCL/PCL) is a tool on the SAP Service Marketplace that allows you to find realization alternatives for SAP solutions, business scenarios, and processes for your SAP enhancement package installation. You find the tool at http://service.sap.com/scl.

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

Using the SCL/PCL Procedure

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, and processes. You can find out which components are needed and the available alternatives.

o SAP Components and Possible Scenarios

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

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. You can make your selection by using an alphabetical index or a full-text search. It is also possible to see all scenarios for a certain solution. You will then get a list of the alternative ways to realize these scenarios. You can also search for the identified business functions of a SAP enhancement package.

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

References

72 July 2011

4. Add the scenario Billing Analysis in ERP to the Selected Scenarios/Processes/Variants list and choose Show Realization Alternatives. The SCL/PCL then lists the different possibilities. With options like Validity you can switch between possible and impossible realization alternatives. The Optional Comp. dropdown list helps you to find the minimum required SAP product versions.

master guide sap® for utilities - sap help portal · pdf filemaster guide sap for...

Documents