011000358700005807892005 e

25
7/25/2019 011000358700005807892005 e http://slidepdf.com/reader/full/011000358700005807892005-e 1/25 © SAP AG 1 ©SAP AG2005 ERP2005 RKT Project Role Implementation Business Package for Maintenance Technician SAP AG

Upload: prashanthcn

Post on 28-Feb-2018

213 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 1/25

© SAP AG 1

©SAP AG2005

ERP2005 RKT

Project

Role Implementation

Business Package for 

Maintenance Technician

SAP AG

Page 2: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 2/25

© SAP AG 2

©SAP AG2005

Requirements for Role in ECC

Requirements for Role in BW

Business Package for Maintenance Technician

Requirements for Role in EP

Implementation of

Role MaintenanceTechnician

Page 3: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 3/25

© SAP AG 3

©SAP AG2005

Requirements for Role in ECC

Requirements for Role in BW

Business Package for Maintenance Technician

Requirements for Role in EP

Implementation of

Role MaintenanceTechnician

Page 4: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 4/25

© SAP AG 4

© SAP AG 2005

Getting Started (1)

The portal content you need to implement the role Maintenance

Technician is included in the ERP shipment and can be installed from

the installer.

Besides that, you can also download Business Packages from the

SAP Developer Network using the link below:

https://www.sdn.sap.com/irj/sdn/developerareas/contentportfolio

Here you also find detailed documentation on all Business Packages.

Page 5: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 5/25

© SAP AG 5

© SAP AG 2005

Getting Started (2)

To implement the role Maintenance Technician in mySAP ERP 2005,

you need

ERP ECC 6.0■ PLM Extension 2005 (Maintenance Technician Web Dynpros)

■ SCM Extension 2005 (Confirmation Web Dynpros)

■ R/3 Plant Maintenance implementation

■ NetWeaver 2004s Enterprise Portal SP05

■ Business Package for Common Parts

■ Business Package BP ERP05 MAINTENANCE TECH 1.0 (Business

Package for Maintenance Technician)■ Optional: Business Warehouse 7.02

 You find up-to-date information about installation of the Business

Package for Maintenance Technician in SAP Note 849573.

Page 6: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 6/25

© SAP AG 6

© SAP AG 2005

Getting Started (3)

In the Portal Administration you will find the content of the

Maintenance Technician role (iViews, pages, worksets): Content

 Administration → Portal Content  → Content Provided by SAP →

Content for Specialists  → Maintenance Technician.

In the Portal Administration you need to implement the system aliases

SAP_ERP_MANUFACTURING and SAP_BW.

You can add further iViews and pages to the role to meet your 

requirements. It is not recommended to make substantial changes to the

role structure. It is also not recommended to change the Object-Based

Navigation.

 Note: The Business Package for Maintenance Technician is not integrated with the BP for Assets or BP

for Asset Services.

Page 7: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 7/25

© SAP AG 7

© SAP AG 2005

Defining User Accounts

Note that all users assigned to this role will need a professional user

license.

For each of the users that will use the role-content in their portal, youwill have to ensure that the user has

 A user account in the Enterprise Portal (EP)

  A user account in the Enterprise Core Component (ECC), plus

authorization for the appropriate transactions. In some cases, default

personalization parameters (e.g. plant) will also be required for the

user/s.

If BW is used - a user account in the Business Information

Warehouse (BW) plus authorization for the appropriate objects.

Page 8: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 8/25

© SAP AG 8

©SAP AG2005

Requirements for Role in ECC

Requirements for Role in BW

Business Package for Maintenance Technician

Requirements for Role in EP

Implementation of

Role MaintenanceTechnician

Page 9: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 9/25

© SAP AG 9

© SAP AG 2005

Implementing the Work Centers for the Role (1)

The role Maintenance Technician contains the following work centers:

  Work Overview

The work overview provides a personalized worklist of notifications,orders, tasks and confirmations. It allows direct access to the

confirmation. You can also create new notifications and orders here, or

call up after-event order recording.

  Structure Display

The structure view displays the structure of technical objects including

the object details. From here you can also dismantle, install, or replace

pieces of equipment. The structure view also displays the maintenance

schedule for a technical object, as well as the number of spare partsthat are currently available in the plant for the technical object.

Page 10: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 10/25

© SAP AG 10

© SAP AG 2005

Implementing the Work Centers for the Role (2)

Each work center provides access to a range of work lists and / orservices appropriate to the tasks performed by the user. In addition,the report launch pad provides access to the reports required. The

work centers and associated applications for the role are described inthe Portal Content Directory.

Each of these building blocks can be configured in the Portal Administration to meet your specific needs. Each application is startedin the portal as an iView.

In the Work Overview of the Maintenance Technician role you findpre-configured pages and iViews for the creation of notifications andorders. You can either update the notification / order types and text

given in these pages or create new iViews / pages for your ownnotification / order types.

The back-end requirements for each building block are described inthe sections that follow.

Page 11: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 11/25

© SAP AG 11

© SAP AG2005

Changes to the Service Map

Service Map

The Service Map is generated based on the Portal Content Directory. Sample

texts are delivered in the Business Package for Maintenance Technician, which

you can change. To adjust the texts, maintain the texts in the page properties.

Page 12: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 12/25

© SAP AG 12

©SAP AG2005

Requirements for Role in ECC

Requirements for Role in BW

Business Package for Maintenance Technician

Requirements for Role in EP

Implementation of

Role MaintenanceTechnician

Page 13: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 13/25

© SAP AG 13

© SAP AG 2005

Scope of Role Maintenance Technician in ECC

The role Maintenance Technician is involved in the business process

“Maintenance Technician” in mySAP ERP 2005.

General Implementation Information:RKT Learning Map SAP ERP 2005: Learning Map for People Productivity - Cross-

Topics & Technology

Solution Manager Structure

Page 14: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 14/25

© SAP AG 14

© SAP AG2005

Configuration Settings in ECC

Prerequisite for the implementation of the role Maintenance Technician isa live R/3 Plant Maintenance (PM) implementation. From the availablePlant Maintenance processes you should have implemented at leastEmergency Maintenance and / or Corrective Maintenance.

 You will need to customize worklists and web dynpro applications for therole Maintenance Technician

These configuration tasks are grouped in the SAP Solution Manager byconfiguration objects:

The Maintenance Technician role can also be implemented based on R/3 Customer Service (CS). The

implementation effort will probably be higher, though.

Page 15: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 15/25

© SAP AG 15

© SAP AG2005

Configuration Settings in ECC – Confirmation

IMG-Path:

Integration with Other mySAP.com Components→ Business Packages /

Functional Packages→Maintenance Technician→ Confirmation

For time and overall completion confirmation, define which screen areas and

functions you need and assign them to plant/order type.

Page 16: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 16/25

© SAP AG 16

© SAP AG 2005

Configuration Settings in ECC – Personal Object Worklist

IMG-Path:

Cross-Application Components→ General Application Functions→

Generic mySAP Suite Functions→ Personal Object Worklist (POWL)

For the Maintenance Technician, default categories and queries are delivered for notifications, operations (orders), tasks and confirmations.

If the default delivery does not meet your requirements, you can define new POWLtypes and categories in customizing as well as new default queries for all users.Here you can also decide if the default types and queries for the MaintenanceTechnician should be visible for the users.

In addition to the customizing settings, all users can define new queries on theportal related to the POWL types and categories set up in customizing.

Default queries delivered for the Maintenance Technician role are:

Confirmations

 Notifications

 Notifications reported by me

Tasks

Orders/Operations

Orders/Operations reported by me

For detailed information on POWL functionality, please refer to the SAP ERP 2005 Learning Map forPeople Productivity - Cross-Topics & Technology→Work Center Building Blocks in Detail→

Configuration of the Personalized Object Work List.

Page 17: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 17/25

© SAP AG 17

© SAP AG2005

Configuration Settings in ECC – Personalization (1)

IMG-Path:

Cross-Application Components→ General Application Functions→

Generic mySAP Suite Functions→ Personalization

For the Maintenance Technician, it should be sufficient for the administrator to execute the

activity Personal izat ion Data: Col lect ive Processing . Here the administrator enters default

values for specific applications within the Maintenance Technician role.The activity Personalization Data: Single Processing can be executed by each user. Entries in

this activity are only valid for the respective user and overrule entries in the collective

processing activity.

The personalization activities can be integrated in an iView so that they can also be accessed

from the portal. Please refer to the online documentation of the ERP Common Business

Package.

Activate the delivered Business Add-Ins. They contain coding relevant for the Maintenance

Technician processes.

For the Maintenance Technician role the customizing activities Edit Personalization Hierarchy, Edit

Personalization Dialog, Display Personalization Data, Delete Personalization Data and Reorganize

Personalization Data are not relevant.

Page 18: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 18/25

© SAP AG 18

© SAP AG2005

Configuration Settings in ECC – Personalization (2)

■ DIA_MT_NOTIFICATION

The notification type entered in this dialog is relevant if you want to create a notification from the

Structure Display.

■ DIA_MT_OBJLIST

The system status and period of time entered here are relevant for the selection of notifications and

orders in the object information.

■ DIA_MT_ORDER_AER

The order type, plant and business area entered in this dialog are relevant for the after-event order

recording.

■ DIA_MT_ORDER_STRUCTURE

The order type, plant and business area entered in this dialog are relevant if you want to create an

order from the Structure Display.■ DIA_MT_PLANT

The plant entered in this dialog decides for which plant the stock availability per spare part will be

displayed in the Structure Display.

■ DIA_MT_REP

The parameters entered in this dialog are relevant for the BW queries you want to access from the

Maintenance Technician role.

In the activities Personalizat ion Data: Collect ive Processin g and Single Processin g 

you find the following personalization dialogs relevant for the Maintenance

Technician role:

For the Maintenance Technician role the customizing activities Edit Personalization Hierarchy, Edit

Personalization Dialog, Display Personalization Data, Delete Personalization Data and Reorganize

Personalization Data are not relevant.

Page 19: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 19/25

© SAP AG 19

© SAP AG 2005

Personalization Settings for Notifications andOrders (1)

 Apart from the customizing settings described on the last slides, there

is a personalization feature which needs to be carried out in a backend

transcation (SE80).

The notification and order web dynpros of the role Maintenance

Technician can be personalized on notification / order type level. The

standard delivery lists the available notification / order fields and areas

for these web dynpros. You should decide for which notification / order

type you want to offer which fields / areas and personalize the web

dynpros accordingly.

Note: The layout definition for the notification and order web dynpros is

not connected to the R/3 field selection for notifications and orders.

The personalization on notification / order type level needs to be carried out in the connected backend

system. You need to have administrator rights to carry out the personalization on notification / order type

level.

Page 20: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 20/25

© SAP AG 20

© SAP AG 2005

Personalization Settings for Notifications andOrders (2)

In the connected backend system choose the Object Navigator(transaction SE80) and display Package RPLM_QIMT -> EmbeddedPackages.

For notifications: RPLM_QIMT_NOTIF_UI -> Web Dynpro -> Web Dynpro Applicat. ->double-click on QIMT_NOTIFICATION_APP. In the (horizontal) menu bar choose WebDynpro Application -> Test -> Execute in Administration Mode.Enter a notification number of the notification type for which you want to define the layoutand change or display the notification. Put the cursor in any field of the notification webdynpro and press the Control (Ctrl) key together with right-click mouse. Thepersonalization dialog will appear.

For orders: RPLM_MT_UI -> Web Dynpro -> Web Dynpro Applicat. -> double-click onMT_ORDER_APP. In the (horizontal) menu bar choose Web Dynpro Applicaton -> Test -

> Execute in Administration Mode.Enter an order number of the order type for which you want to define the layout andchange or display the order. Put the cursor in any field of the order web dynpro and pressthe Control (Ctrl) key together with right-click mouse. The personalization dialog willappear.

Page 21: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 21/25

© SAP AG 21

© SAP AG2005

Reporting Settings in ECC

IMG-Path:

Integration with Other mySAP.com Components→ Business Packages /

Functional Packages→Maintenance Technician→ Reporting

The following reports are included in the Maintenance Technician role per default:

■ R/3 List Reports: Order- and Operation List, Notification List

■ BW Analytics: MTTR (Mean-Time To Repair / Mean-Time Between Repairs), Removal/Installation

of Equipment, Damage Analysis – Notifications, Cause Analysis – Notifications.

If these are the reports you want to use, execute the activity Transfer Default Values for 

LaunchPad .

If you need further or different reports, also execute the activity Compile Report List .

Page 22: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 22/25

© SAP AG 22

© SAP AG2005

Business Add-ins in ECC

IMG-Path:

Integration with Other mySAP.com Components→ Business Packages /

Functional Packages→Maintenance Technician→ Business Add-Ins

Change URL Parameter  You can use this BAdI to influence the URL parameters for calling BW queries and

BW templates.

Generate URLs for DMS Documents

 You can use this BAdI to generate URLS on the Content Server to display DMS

documents (CA-DMS) outside of the internal system landscape (such as Firewall).

Page 23: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 23/25

© SAP AG 23

©SAP AG2005

Requirements for Role in ECC

Requirements for Role in BW

Business Package for Maintenance Technician

Requirements for Role in EP

Implementation of

Role MaintenanceTechnician

Page 24: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 24/25

© SAP AG 24

© SAP AG 2005

Customizing the BW Content for Role

In the standard delivery of the Maintenance Technician role you already

find four BW queries you can access. If you want to add further BW web

templates or queries to the role, enter your query and web template

name here:

Integration with Other mySAP.com Components → Business Packages /

Functional Packages → Maintenance Technician → Reporting →

Compile Report List.

The query‘s parameter names need to be added in the BAdI

MT_LAUNCHPAD which you find here:

Integration with Other mySAP.com Components → Business Packages /Functional Packages → Maintenance Technician → Business Add-Ins →

Change URL Parameter.

For detailed information on the functionality of the report launch pad, please refer to the SAP ERP 2005

Learning Map for People Productivity - Cross-Topics & Technology→Work Center Building Blocks in

Detail→ Configuration of the Report Launch Pad.

Page 25: 011000358700005807892005 e

7/25/2019 011000358700005807892005 e

http://slidepdf.com/reader/full/011000358700005807892005-e 25/25

© SAP AG2005

Copyright 2005 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, 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, z/OS, AFP,

Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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 aretrademarks 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 intendedstrategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, productstrategy, 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 k ind 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 useof hot links contained in these materials and does not endorse your use o f third-party Web pages nor provide any warranty whatsoever relating to third-party

Web pages.