© SAP AG 1

©SAP AG 2007

SAP ERP 6.0 Enhancement Package 2Ramp-Up Knowledge Transfer

Business Description

Basic Maintenance Processing

© SAP AG 2

©SAP AG 2007

Role DefinitionTypical Scenarios

Business ContextBenefits

© SAP AG 3

© SAP AG 2007

Business Motivation

Simplify process of breakdown and corrective maintenanceAutomize most process steps to accelerate processingOffer a unified and easy-to-use user interface

Extend target group of EAMnon asset intensive industries (i.e. Retail)maintenance staff with no access to backendnon maintenance staff with need to report a problem

© SAP AG 4

©SAP AG 2007

Role DefinitionTypical Scenarios

Business ContextBenefits

© SAP AG 5

© SAP AG 2007

Process Simplification

Complete end-to-end maintenance processLean notification handlingMost process steps hidden in background.

PROCESS SIMPLIFICATION

Work OrderExecution

Service Procurement

MaintenancePlanning

Work OrderExecution

Service Procurement

MaintenancePlanningCreate Notification

Background Processing

© SAP AG 6

© SAP AG 2007

Access Simplification

ACCESS SIMPLIFICATION

Access Simplification by Pool roles and POWER listsSAP NetWeaver Business Client (using Portal Content)Alternatively SAP Enterprise Portal Client

© SAP AG 7

© SAP AG 2007

Transaction Simplification

Example: Notification Creation and Equipment CreationNew WebDynpro ABAP screens for notification creationfor equipment creation

TRANSACTION SIMPLIFICATION

SAPGUI Web Dynpro

© SAP AG 8

©SAP AG 2007

Role DefinitionTypical Scenarios

Business ContextBenefits

© SAP AG 9

© SAP AG 2007

Complete Data

Reporter Processor Service Provider

Scenario – Process View

ServiceProvider

Create Notification MaintenancePlanning

Service Procurement

Work OrderExecution

Execute Work

ExternalInternal

WorkCenter

Execute WorkCheck/ConfirmWork

Create Invoice

Request Service Prov.

ReportProblem

© SAP AG 10

© SAP AG 2007

Complete Data

Step Processedin Dialog

Processedin Background

Scenario – Step-by-Step View

Purchaserequisition

Execute Work

WorkCenter

Execute WorkCheck/Confirm Work

Confirm Notification

Create Invoice

PurchaseOrderRequest Serv. Prov.

Report Problem Order

Resp.Person

Tech.Complete

Notif.

Notif.

1

2

4

5

6

InternalOperation

ExternalOperation

Create Equipment3

Step 1: A problem is reported by a normal employee within a notification. The notification is saved in theERP backend.

Step 2: A Processor completes the data in the newly created notification (f.ex. enters the equipment).

Step 3: If no equipment is available, a new equipment must be created with the necessary assignments (i.e. partners). If the first processor (f.ex. a secretary) is not authorized to create equipments, he/she uses thefunction Replace Processor to assign the authorized person.

Step 4: The processor requests either an internal or an external service provider.

The internal service provider is represented by a responsible person (personel number). The externalservice provider is a supplier. Step 4 leads to the automatic creation of a maintenance order in the ERP backend, based on the preceding notification. In case of an internal service provider, an internalprocessing operation is created within the order, in case of an external service provider an externalprocessing operation is created which triggers a purchase requisition.

Step 5: The processor checks whether the work has been performed correctly and if not, starts a postprocessing.

Step 6: The processor completes the notification which automatically comletes the order in thebackground.

© SAP AG 11

© SAP AG 2007

User interface

SAP NetWeaver Business Client

SAP Enterprise Portal

© SAP AG 12

© SAP AG 2007

SAP NetWeaver Business Client in SAP ERP

SAP NetWeaver Business Client …… is SAP’s next generation desktop client using

the latest smart client technology. … is an alternative client to the SAP NetWeaver

Portal client for users requiring fast access to Web Applications.

… offers role-based access to SAP applications In a multiple-system environment, roles for SAP NetWeaver Business Client are defined in the SAP NetWeaver Portal Content Directory.In a one-system environment (SAP All-In-One case), roles for SAP NetWeaver Business Client can also be defined in PFCG in SAP ERP.

… can host existing SAP UIs in the “canvas”area (including SAP GUI and WebDynpro) as well as any other web based content.

… is available with SAP ERP 6.0 Enhancement Package 2.

Roles and Work Centers in SAP ERP run in the SAP NetWeaver Portal Client and in the SAP NetWeaver Business Client.

© SAP AG 13

©SAP AG 2007

Role DefinitionTypical Scenarios

Business ContextBenefits

© SAP AG 14

© SAP AG 2007

Portal Environment for Problem Reporter

© SAP AG 15

© SAP AG 2007

NWBC for Problem Reporter

© SAP AG 16

© SAP AG 2007

Request Service Provider

The processor can request either an internal or an external service provider.

It is also possible to do this in a 2-step-procedure:

First the internal service provider is assigned to check the problem.

Then, if the internal service provider is unable to solve the problem, an external service provider canbe assigned.

© SAP AG 17

© SAP AG 2007

Checking existing notifications

Whenever the processor requests a service provider for a certain notification with a certain referenceobject, the system checks whether there are already existing notifications/orders for that object.

If a notification/order that refers to the same object is found, the processor gets the choice to either assignthe newly created notification to the existing request or to treat it as a separate and independen request.

© SAP AG 18

© SAP AG 2007

Postprocessing

In case the work was not performed correctly, the processor can start a postprocessing.

This leads to an entry in the long text of the notification.

Also, the person responsible can be exchanged.

Postprocessing is also used when the processor wants switch from an internal to an external serviceprovider. In that case after starting the postprocessing the internal service provide is deleted from thenotification an the external service provider is entered by the processor. This means that in the order in thebackground a new operation for external processing will be created which subsequently leads to thecreation of a purchase requisition.

© SAP AG 19

© SAP AG 2007

Notification confirmed

© SAP AG 20

© SAP AG 2007

Backend Notification and Order

Notification assignedto object list

Person responsibleand

work center

In the ERP backend system a maintenance order is created based on the notification of the problemreporter.

The notification is entered into the object list of the order (no header notification).

Internal or external service providers are automatically assigned by means of a partner determinationprocedure.

The complete cycle of order processing is executed in the background, hidden from both the problemreporter and the processor.

© SAP AG 21

© SAP AG 2007

Copyright 2007 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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 is a registered trademark of Oracle Corporation.

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and 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.

Java is a registered trademark of Sun Microsystems, Inc.

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

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.