SAP Enterprise Asset Management

SAP Enhancement Package 4

© SAP 2009 / 1

SAP ERP 6.0 Enhancement Package 4

Rotables Management (Internal, Sub-Contracting and Warranty Claims)

Integrated Service Procurement

Inspection/Operator Rounds

Continuous Improvements

Fleet Maintenance including BI Business Content for Fleet

Time Zone Support

Maintenance Cost Budgeting (MCB)

Flexible Reporting

Work Clearance Management (WCM)

Authorisations

SOA Services

Other

Enhancements to Fleet Maintenance

Summary of Enhancements

The field length of the field “gas station” increased from 3 characters to

4 characters.

Ability to concurrently reverse a Consumption Relevant Measurement

Document (CRMD) and its associated Material Goods Movement

documents that are created when executing Transaction IFCU.

Function modules to enable reporting in US units of measure in the

PMIS report S114.

Display of the Assembly field of the reference object screen (O110)

when the display has been customized to show the fleet plate number.

PM Order basic order view is available for Fleet.

Capability to monitor via a BADI the validity of the odometer reading

entry when the measurement document is created from within a work

order.

New Business Warehouse (BW) Content

© SAP 2009 / 2

Increased length of “Gas station” field

The field length of the field “gas station” is increased from 3 characters to 4

characters.

Useful for organizations which would like to keep consistency between their plant

number and gas station number.

© SAP 2009 / 3

Reversal of consumption relevant documents

Transaction IFCU “Consumption Relevant Measurement Document Recording”

posts individual documents for measurement documents, goods movements for

fuel/oil and associated FI/CO documents.

There is no way to find out the corresponding documents (which goods

movements and measurement documents had been created together) later to

cancel it all in one step.

Now there is possibility to concurrently reverse a Consumption Relevant

Measurement Document (CRMD) and its associated Material Goods Movement

documents that are created when executing Transaction IFCU.

If it‟s required to reverse an IFCU entry all documents can be reversed in one

step.

© SAP 2009 / 4

Reversal of Consumption Relevant Documents

(cont.)

Example of consumption entries and reversal of documents

© SAP 2009 / 5

US units in PMIS report S114

© SAP 2009 / 6

The PMIS report S114 has been enhanced to enable reporting in US units

(transaction MCIZ).

US units in PMIS report S114

© SAP 2009 / 7

Enhanced report S114 for average fuel consumption in US units:

Possibility to select

relevant fields in the

report

Display Assembly Field

© SAP 2009 / 8

It is now possible to have the “Equipment & Assembly” fields available for

notifications and orders for a fleet objects.

Simplified Order View

© SAP 2009 / 9

Validity of odometer reading entry from PM

Order

© SAP 2009 / 10

There is validity checking for all transactions used to create odometer readings. For

example in transaction IFCU there is IMG configuration that allows monitoring of

odometer/fuel entries to make sure they are within configured limits. Another example if

odometer readings are entered using transactions IK11 or IK22, there are BADI‟s that can

be used to monitor the validity of the entry prior to creating a measurement document.

The capability to monitor the validity of the odometer reading entry when the measurement

document is created from within a work order has been provided by means of a BADI.

Validity of odometer reading entry from PM

Order

© SAP 2009 / 11

The BADI check is supported for all the transaction's which support saving of the

measurement documents e.g. IK11, IK21

Note that no Standard Implementation is provided for the BADI, except an example

implementation which has a sample code containing a call to customer exit. There will be no

action performed until BADI implementation is activated.

Now the BADI implementation can check if the

entered value is consistent with the rule for control

of odometer. Results will depend on what has

been programmed in the BADI

Enhancements to BI Content for Fleet Maintenance

NetWeaver®

7.0 Enhancement Package 1

Enhancements to BI for Fleet

Fleet attributes of the equipment master data included in BI.

New query for Litres fuel per 100 kilometres (l/100km) (In US units - Miles per Gallon) (by

vehicle type).

New query for Cost per kilometer (in US units by mile) (by vehicle type).

New query for Asset value at current depreciated price versus maintenance costs (current).

© SAP 2009 / 12

Fuel Consumption litres per 100km

Query: 0PM_C12_Q0003

© SAP 2009 / 13

CET +1EST -5

Time Zones - Traditional Approach

New York

NY 7:00am a technician creates an

Order for 10:00 am

India +5 1/2

Bangalore

Bangalore 4:30pmhis colleague finds the

Order for 10:00 am

Walldorf

Wdf 1:00pmhis colleague finds the

Order for 10:00 am

© SAP 2009 / 14

Time Zones - New Concept

Overall principles:

A User can set his/her own settings in the Transaction via function „Set time Zone‟

in the Application tool bar

The currently used Time Zone is shown on the button (= Reference Time Zone)

The Reference Time Zone can be switched inside the running transaction

Date / time is always recalculated in UI or in print output into the Reference Time

Zone (in print output the Reference Time Zone is printed as additional field)

Entities are always stored on data base in System Time Zone ( = Time Zone

of the Database/Application Server)

© SAP 2009 / 15

Time Zone Support

© SAP 2009 / 16

Time Zone Support

New York

NY 7:00am a technician creates an

Order for 10:00 am

System Time ZoneUTC

Walldorf

Wdf 1:00pmhis colleague finds the

Order for 4:00 pm

Bangalore

Bangalore 4.30pmhis colleague finds the

Order for 7:30 pm

© SAP 2009 / 17

Time Zone Support

New York

NY 7:00am a technician creates an

Order for 10:00 am

System Time ZoneUTC

Walldorf

Wdf 1:00pmhis colleague finds the

Order for 4:00 pm

Bangalore

Bangalore 4.30pmhis colleague finds the

Order for 7:30 pm

© SAP 2009 / 18

Enhancements to Maintenance Cost Budgeting

Enhancement to the Extractor 0PM_PRM_PLCS_1 so that it will not terminate

when an error or dialog occurs at any step during the extraction process.

Additional selection options to the datasource 0PM_PRM_PLCS_1

Improved performance of the Extractor 0PM_PRM_PLCS_1

Delta capability for Extractor 0PM_PRM_PLCS_1

© SAP 2009 / 19

Flexible Reporting – ERP and BW

© SAP 2009 / 20

Work Clearance Management

How to achieve compliance in asset operations

So far SAP‟s EAM application covers the life cycle of technical assets. This includes

the main phases “design and specify”, “procure and build”, “operate and maintain”

and “decommission and dispose”.

There is no function available today to store information about the environment in

which the technical assets are used for production and service.

The Work Clearance Management (WCM) application tracks the conditions to

create a safe working environment for maintenance activities. But this does not reach

out to the production environment itself.

To close the gap and to track compliance in asset operations two enhancements are

available with ECC 6.0 EhP4:

Mode dependent tagging: allows the definition of operational asset conditions

Line-ups: allows the surveillance of the operational asset conditions

© SAP 2009 / 21

Introduction of ”plant modes”

Technical assets that are used in production facilities operate under defined

conditions during the production process.

Depending on the product or service that is produced or delivered and on the

quantity of the output the technical assets are operated in various modes.

These modes are called “plant modes”.

© SAP 2009 / 22

Definition of the mode dependent operational

conditions

© SAP 2009 / 23

Overview - Authorization enhancements in

EAM

In order to comply with access control requirements, sensitive data must be

restricted from users who do not have the proper authorizations.

Especially in the area of maintenance there is the need to protect sensitive

data. Some objects in a complex technical structure are sensitive, other

objects in that technical structure are not. For example a pump in a structure

of a ship is normally not sensitive, but if this pump is part of the nuclear

engine it is sensitive and the access / visibility of this object and the related

maintenance information must be restricted.

The intended inheritance of the authorization functionality around the

authorization group (I_BEGRP) for PM technical objects, Functional Location

and Equipment to maintenance work orders works as designed in most

cases. The authorization group (I_BEGRP) is inherited from the technical

object to the maintenance work order and the authorization check works for

example in transaction IW32.

When a user without this specific authorization group executes the

transaction code IW32 against an order with the restricted authorization

group, user is denied access.© SAP 2009 / 24

Check of authorization group

Order

I_BEGRP =“001”

E2

E1

E3

M TP1

TP2 TP3

TP4 TP5

E4

Order

I_BEGRP =“000”

Jet engine EJ200 I_BEGRP =“000”

Radar

I_BEGRP =“001”

The order has inherited the authorization

group from the related technical object

(Functional Location or Equipment).

A user can only maintain an order when he

belongs to the right authorization group.

Mr. Engine Specialist

Mr. Engine SpecialistI_BERGRP =“000”

I_BERGRP =“000”

I_BEGRP =“001”

I_BEGRP =“000”

© SAP 2009 / 25

EAM – SOA Services Bundle: Maintenance Processing

Enterprise Services

The following enterprise services have been developed: Activate Maintenance Plan

Check Maintenance Plan Creation

Check Maintenance Plan Update

Create Maintenance Plan

Deactivate Maintenance Plan

Find Maintenance Plan by Elements

Find Maintenance Plan Item by Elements

Read Maintenance Plan

Read Maintenance Plan Schedule Line

Reset Maintenance Plan Delete Indicator

Set Maintenance Plan Delete Indicator

Update Maintenance Plan

Find Maintenance Task List Simple by Elements

Read Maintenance Task List

Check Maintenance Confirmation Creation

Find Maintenance Confirmation Simple by Elements

Read Maintenance Confirmation

Reset Maintenance Order Delete Indicator

Set Maintenance Order Delete Indicator

Simulate Maintenance Order Scheduling

Create Measuring Device

Find Material by Elements

© SAP 2009 / 26

Maintenance Plan Item

“Do Not Rel Immediately” flag

© SAP 2009 / 27

Generic Object Services

Button to indicate that documents are attached

© SAP 2009 / 28

Multi-Level Equipment List (IE07)Enhanced

Additional Parameters:

Maintenance Packages

Maintenance Items

Operations

Maintenance Dates

© SAP 2009 / 29

Multi-Level Functional Location List

(IL07)Enhanced

Additional Parameters:

Maintenance Packages

Maintenance Items

Operations

Maintenance Dates

© SAP 2009 / 30

Task Lists – Action Log

© SAP 2009 / 31

Enhancements to PM Order Material Planning

Change Requirement Date

© SAP 2009 / 32

Print Forms in Adobe Format

© SAP 2009 / 33

Copyright 2008 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.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet™, SAP Business ByDesign, ByDesign, PartnerEdge 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 and associated logos

displayed 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. 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. 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

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch

SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet™, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die

dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen

von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu

Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen

Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten

Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die

Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder

ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck

sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung

dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks

zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über

Internetseiten Dritter ab.

Alle Rechte vorbehalten.

© SAP 2009 / 34