Karl Liebstückel

Plant Maintenance with SAP®

Bonn � Boston

372 Book_M.indb 3 12/7/10 11:55:28 AM

Contents at a Glance

1 About this Book .......................................................... 15

2 Plant Maintenance and SAP: A Contradiction? .......... 23

3 Organizational Structures ........................................... 39

4 Structuring of Technical Systems ................................ 53

5 Business Processes ...................................................... 129

6 Integrating Applications from Other Departments .... 329

7 Plant Maintenance Controlling ................................... 381

8 New Information Technologies in Plant Maintenance ............................................................... 433

9 SAP Projects in Plant Maintenance ............................ 479

10 Usability ...................................................................... 513

A List of Sources ............................................................. 549

B Overviews .................................................................... 553

C The Author ................................................................... 577

D Acknowledgments ....................................................... 579

372 Book_M.indb 5 12/7/10 11:55:28 AM

7

Contents

Preface ......................................................................................... 13

1 About this Book ........................................................... 15

1.1 Target Audience ............................................................ 161.2 What this Book Can and Cannot Do .............................. 181.3 Structure of this Book ................................................... 18

2 Plant Maintenance and SAP: A Contradiction? ........... 23

2.1 Plant Maintenance Today: New Ideas Need New Space ............................................................................ 24

2.2 New Maintenance Terminology .................................... 262.3 Development of Maintenance Strategies ....................... 292.4 Development of SAP Plant Maintenance ....................... 312.5 SAP ERP 6.0 ................................................................. 32

3 Organizational Structures ............................................ 39

3.1 SAP Organizational Units .............................................. 393.1.1 The Plant from a Maintenance Perspective ....... 393.1.2 Maintenance-Specific Organizational Units ....... 403.1.3 Other General Organizational Units .................. 423.1.4 Plant-Specific and Cross-Plant Maintenance ..... 43

3.2 Work Centers ................................................................ 45

4 Structuring of Technical Systems ................................ 53

4.1 Actions Before Mapping Your Technical Systems in the SAP System ............................................................. 53

4.2 SAP Resources for Structuring Technical Systems and How to Use Them .................................................. 654.2.1 Functional Locations and Reference Functional

Locations ......................................................... 65

372 Book_M.indb 7 12/7/10 11:55:29 AM

8

Contents

4.2.2 Equipment and Serial Numbers ........................ 764.2.3 Links and Networks .......................................... 854.2.4 Material and PM Assemblies ............................ 874.2.5 Bill of Material ................................................. 914.2.6 Classification .................................................... 964.2.7 Product Structure Browser ................................ 1024.2.8 Special Functions ............................................. 103

5 Business Processes ...................................................... 129

5.1 What You Should Do Before You Map Your Business Processes in the SAP System ........................... 130

5.2 Planned Repairs Business Process .................................. 1375.2.1 Notification ...................................................... 1385.2.2 Planning ........................................................... 1545.2.3 Controlling ....................................................... 1805.2.4 Processing ........................................................ 1955.2.5 Completion ...................................................... 197

5.3 Immediate Repairs Business Process .............................. 2045.4 Shift Notes and Shift Reports ........................................ 2105.5 External Assignment Business Process ........................... 217

5.5.1 Basic Principles of External Assignment ............ 2175.5.2 External Services as an Individual Purchase

Order ............................................................... 2195.5.3 External Services with External Work Centers ... 2245.5.4 External Services with Service Specifications ..... 228

5.6 Refurbishment Business Process ................................... 2315.7 Subcontracting Business Process ................................... 2425.8 Preventive Maintenance Business Process ..................... 250

5.8.1 Basic Principles of Preventive Maintenance ...... 2515.8.2 Objects of Preventive Maintenance .................. 2535.8.3 Maintenance Task Lists ..................................... 2575.8.4 Preventive Maintenance – Time-Based ............. 2645.8.5 Preventive Maintenance – Performance-Based ... 2825.8.6 Preventive Maintenance – Time- and

Performance-Based .......................................... 2905.8.7 Inspection Rounds ............................................ 296

5.9 Condition-Based Maintenance Business Process ............ 3015.10 Calibration Inspection Test Equipment Business Process ... 305

372 Book_M.indb 8 12/7/10 11:55:29 AM

9

Contents

5.11 Pool Asset Management Business Process ..................... 3125.12 Project-Based Maintenance Business Process ................ 319

5.12.1 SAP Project System .......................................... 3195.12.2 Maintenance Event Builder .............................. 324

6 Integrating Applications from Other Departments .... 329

6.1 How Other Departments Are Involved .......................... 3296.2 Integration Within SAP ERP .......................................... 330

6.2.1 Materials Management .................................... 3316.2.2 Production Planning and Control ...................... 3396.2.3 Quality Management ........................................ 3446.2.4 Financial Accounting ........................................ 3446.2.5 Controlling ....................................................... 3496.2.6 Real Estate Management .................................. 3596.2.7 SAP ERP Human Capital Management .............. 3616.2.8 Service and Sales .............................................. 365

6.3 Integration With Other SAP Software ........................... 3686.3.1 Integration with SAP NetWeaver MDM ............ 3686.3.2 Integration with SAP SRM ................................ 370

6.4 Integration With Non-SAP Systems ............................... 3726.4.1 Operations Monitoring Systems ....................... 3736.4.2 Operations Information Systems ....................... 3756.4.3 Service Specifications and Activity Recording .... 379

7 Plant Maintenance Controlling ................................... 381

7.1 What Plant Maintenance Controlling is About .............. 3817.2 SAP Tools for Acquiring Information and How to

Use Them ..................................................................... 3857.2.1 SAP List Viewer ................................................ 3867.2.2 QuickViewer .................................................... 3927.2.3 SAP ERP Logistics Information System .............. 3967.2.4 SAP NetWeaver BW ......................................... 4057.2.5 Comparison of the LIS and SAP NetWeaver BW ... 414

7.3 SAP Tools for Budgeting and How To Use Them ............ 4167.3.1 Order Budgeting .............................................. 4167.3.2 Cost Center Budgeting ..................................... 4187.3.3 Budgeting with IM Programs ............................ 419

372 Book_M.indb 9 12/7/10 11:55:29 AM

10

7.3.4 Budgeting with WBS Elements ......................... 4227.3.5 Maintenance Cost Budgeting ............................ 426

8 New Information Technologies in Plant Maintenance ... 433

8.1 Internet and Intranet .................................................... 4338.1.1 SAP NetWeaver Portal and Roles ...................... 4348.1.2 After-Event Recording ...................................... 4388.1.3 Structure Display .............................................. 4408.1.4 Electronic Parts Catalogs ................................... 4428.1.5 Easy Web Transaction ....................................... 4448.1.6 Collaboration Folders ....................................... 4468.1.7 Vision or Reality? ............................................. 448

8.2 Mobile Maintenance ..................................................... 4548.2.1 Fundamentals of Mobile Maintenance .............. 4548.2.2 Paging .............................................................. 4598.2.3 SAP Mobile Asset Management ....................... 4608.2.4 RFID ................................................................ 470

8.3 Service-Oriented Architecture ....................................... 473

9 SAP Projects in Plant Maintenance ............................. 479

9.1 Possible Process for Your SAP Plant Maintenance Project .......................................................................... 4799.1.1 Implementation Strategy .................................. 4799.1.2 Methodology ................................................... 481

9.2 General Risk and Success Factors in SAP Projects: An Empirical Survey ...................................................... 484

9.3 Tips for Your Plant Maintenance Project ....................... 4889.3.1 Project Preparation ........................................... 4889.3.2 Business Blueprint ............................................ 5039.3.3 Implementation ............................................... 5099.3.4 Final Preparation .............................................. 5109.3.5 Go-Live and Support ........................................ 511

10 Usability ....................................................................... 513

10.1 What Is Meant by Usability? ......................................... 514

Contents

372 Book_M.indb 10 12/7/10 11:55:29 AM

11

10.2 Assessing Usability ........................................................ 51810.3 Importance of Usability in Plant Maintenance ............... 51810.4 SAP System Options to Improve Usability ..................... 521

10.4.1 Transaction Variants ....................................... 52110.4.2 General User Parameters ................................ 52310.4.3 Maintenance-Specific User Parameters ........... 52410.4.4 Customizing ................................................... 52610.4.5 List Variants ................................................... 52710.4.6 Roles and Favorites ........................................ 52810.4.7 Customizing Input Help ................................. 52910.4.8 Function Keys and Key Combinations ............. 52910.4.9 Upstream Transactions ................................... 53010.4.10 Customer Exits ............................................... 53310.4.11 GUI XT ........................................................... 535

10.5 Usability Study for SAP ERP 6.0 .................................... 53510.5.1 Preparation and Execution ............................. 53610.5.2 Results ........................................................... 54010.5.3 Conclusions .................................................... 544

Appendices ........................................................................ 547

A List of Sources ........................................................................ 549B Overviews .............................................................................. 553

B.1 Functional Comparison of Structuring Resources ..................................................................... 553

B.2 Functions of Notifications and Orders ........................... 554B.3 Integration Aspects ....................................................... 557B.4 Standard Reports of SAP PM-IS .................................... 562B.5 Enterprise Services for Plant Maintenance ..................... 565B.6 Authorization Objects in SAP EAM ............................... 570B.7 Customer Exits for Plant Maintenance ........................... 572

C The Author ............................................................................. 577D Acknowledgments .................................................................. 579

Index ........................................................................................... 581

Contents

372 Book_M.indb 11 12/7/10 11:55:29 AM

129

The following chapter forms the core of this book: it shows you how you can map and implement typical business processes of plant maintenance, such as planned repair tasks or preventive maintenance in the SAP system. However, business processes in particular are unique in character, so company must find its own way of mapping them—and this is where this chapter will assist you.

Business Processes5

This chapter deals with the core business of plant maintenance: business processes. After having already seen many companies from the inside, I can, in good conscience, state that each company has its own idea about what business processes in plant maintenance should be like and how they must be mapped in the SAP system, which means that you—like all other user companies before you—must consider how you can map your day-to-day activities in SAP EAM and how SAP EAM will support you in accomplishing tasks. No book can do this work for you, but I believe you’ll find this chapter helpful.

How do you now arrive at your business processes? The following section will use reference processes to show you the SAP EAM options you can use and provide many tips on how you can adapt SAP EAM to meet your own requirements. The following are selected reference processes:

Processing planned repair tasksEE

Processing immediate repair tasks such as troubleshooting measuresEE

Entering maintenance activities that have already been performed EE

(after-event recording)

Shift notes and shift reportsEE

Outsourcing maintenance tasksEE

Subcontracting, that is, subcontracting for service and repairEE

Reference processes

372 Book_M.indb 129 12/7/10 11:56:18 AM

130

5 Business Processes

Processing preventive maintenance measures based on time EE

and performance

Processing condition-based maintenanceEE

Processing refurbishment measuresEE

Processing test equipment calibrationsEE

Implementing maintenance projectsEE

Before looking at these processes in detail, the next section will give you a few tips about what you should do before you map the processes in SAP EAM.

What You Should Do Before You Map Your 5.1 Business Processes in the SAP System

Like the structuring of technical systems, the following principle should also apply in your search for all answers for business processes:

As much as is necessary, but as little as possible.

You’ll quickly notice that SAP EAM knows a lot of functions that you could use within the business processes. Find out what your business and technical requirements are and look for the easiest way to map these requirements in SAP EAM. The following sections will use numerous examples to demonstrate how you can implement this principle.

Question 1: Which Functions Should You Use?

Appendix B includes an overview of SAP EAM functions that you can use to process your business processes. The chapter will discuss in detail what the keywords specifically mean. I have included three columns there to indicate priority. Decide yourself, and assess the relevant func-tions according to their significance in your company.

The full functionality of the SAP system does not have to be, and should not be, implemented all at once.

372 Book_M.indb 130 12/7/10 11:56:18 AM

131

What You Should Do Before You Map Your Business Processes in the SAP System 5.1

In principle, you should provide users with solutions where they are needed the most. I recommend a three-tier priority list:

Priority A: absolutely necessary, must be implemented immediately in the EE

first phase

Priority B: could have additional benefits, possibly also include in the first EE

phase

Priority C: unnecessary for nowEE

First, deal with the functions with priority A.

If you have the courage to leave some gaps, remove the functions with prior-ity C from the list and banish them from your thoughts.

Question 2: Should You Use a Notification and/or an Order?

You can or must decide whether you want to use only the notification, the order, or both to support your business processes. The answer to this question generally depends on the functions and information that the individual objects have to offer and how important these functions are to you.

Notification

The basic differences between a notification and an order are:

A notification is used to EE request and document a maintenance activity, whereas an order is used to plan and implement a maintenance task.

A notification mainly contains EE technical information, whereas an order essentially contains processing information.

A notification has practically no EE integration points with other SAP applications, so it does not contain information about any costs, whereas an order, as a highly integrative object, has many connections to applications such as warehouse management, purchasing, and con-trolling.

This quite different orientation is reflected in the different functions (see Appendix A.2) and different information of both objects.

Notification vs. order

372 Book_M.indb 131 12/7/10 11:56:18 AM

132

5 Business Processes

A notification has the following characteristics:

HeaderdataEE Each notification has header data. This includes information that is used to identify and manage the notification. It applies to the com-plete notification.

NotificationitemEE You enter and maintain the data in a notification item to identify in more detail the problem or damage that occurred or for the executed action. A notification can have several items.

ActionsEE Actions document the work performed for a notification. They are particularly important in inspections to provide evidence of the work performed and the results established.

TaskEE data Task data describes activities that still have to be performed and may only have resulted from implementing the maintenance activity (for example, creating a report).

Figure 5.1 shows an overview of the structure of an order with the rel-evant information.

The order has a different structure:

HeaderdataEE Header data is information that is used to identify and manage the order. It applies to the complete order.

ObjectlistEE The object list contains the objects with which the order is executed (functional locations, equipment, assemblies, notifications). You can enter these objects on the order header as a reference object and/or on the object list.

OperationsEE You can use operations to describe the work that you want to be performed when the order is being implemented.

MaterialEE list The material list contains spare parts that are required and used when the order is being implemented. This is either stock material, for

Characteristics of a notification

Structure of an order

372 Book_M.indb 132 12/7/10 11:56:18 AM

133

What You Should Do Before You Map Your Business Processes in the SAP System 5.1

which a reservation is subsequently generated, or non-stock material, for which a purchase requisition is created.

Date/Time/Reported byDescriptionReference Object: Functional Location

EquipmentAssemblyMaterial Serial Number

Location DataBreakdown/Availability

ActivityExecution Factors

Activities

DatesTask Description

Tasks

Location of the DamageDamageCause of the Damage

TextNotification Items

Notification

Structure and Content of a NotificationFigure 5.1

Productionresources/toolsEE Production resources/tools (for example, tools, protective clothing, hand pallet trucks) are also required for implementing the order. However, unlike a material, they are not consumed.

SettlementruleEE In the settlement rule, you specify the cost unit (for example, cost center), to which the costs must be charged.

CostdataEE Cost data informs you about how high the estimated, planned, and actual costs are in the value categories for this order, which cost ele-ments are relevant for the order, which key figures of the Plant Main-tenance Information System are updated via the value categories, and how these key figures are updated by the actual costs of the order.

Figure 5.2 shows an overview of the structure of an order with the rel-evant information.

372 Book_M.indb 133 12/7/10 11:56:19 AM

134

5 Business Processes

e.g., Document, Material, Equipment, Numbers, Time, Availability

e.g.,Material, Quantity, Unit of Measure, Storage Location, Batch, Item Category, Availability

e.g., Work Center, Control Keys, Description, Standard Time, Activity Type, Payroll Data

Equipment, Functional Locations, Notifications, Assemblies

Operations

e. g., Order Type, Dates, Plant, Reference Object, Priority, Description

Object List

Material List

ProductionResources/Tools

Settlement Rule

Costs

e.g., Cost Center, Order, Project, System

e.g., Estimated, Planned, and Acutal Costs; Internal Services, Material, External Services

Order Header

Structure and Content of an OrderFigure 5.2

Decide as early as possible whether you want to use a notification and/or an order. If you make the same decision as the majority, or approximately 80%, of SAP user companies, you’ll use the notification and the order. The rest use only the order. There are some cases (mainly in the initial phase) where companies opt to use the notification only.

Question 3: Which Information Should You Store?

The third question applies to business information that you store in the system. There is information:

That you absolutely must store to be able to process a notification or EE

an order (for example, the reference object)

That you reasonably want to store in SAP EAM (for example, the cost EE

center)

The earlier principle must also apply here: as much as is necessary, but as little as possible.

A data graveyard, which is only created for its own sake and is of no interest to anyone, is not seen or analyzed by anyone, and only signifies time and ef-fort in terms of entering and maintaining data, makes no sense. Only enter data that is also information for you.

372 Book_M.indb 134 12/7/10 11:56:19 AM

135

What You Should Do Before You Map Your Business Processes in the SAP System 5.1

The SAP system also enables you to configure notifications and orders flexibly:

You can define the layout of screen templatesEE yourself based on the notification or order type (number, sequence, name and content of tabs).

The field selectionEE option enables you to differentiate important information from unimportant information or to hide fields that you do not require.

The LOG_EAM_SIMP business function must be activated for you to use a flexible screen layout for orders.

Actively use this option to define the appearance of the notification and or-der yourself and design your own layouts: For example, place the most im-portant information on the first tab and hide unimportant fields. You’ll find the explanations about how to do this in Sections 5.2.1, Notification, and 5.2.2, Planning.

Question 4: How Can You Ensure That the Users Accept the System?

Although this question essentially also applies to the structuring of technical systems, the topics user acceptance and usability in relation to maintenance processing are much more important, because work is per-formed in these areas on a daily basis.

There is no guarantee that the system is accepted by the users or is considered user-friendly. However, you can increase the likelihood by reading Chapter 10, Usability, and implementing the suggestions made there.

Question 5: What Role Does Business Process Modeling Play?

Business process modeling (BPM) plays a very important role when SAP systems are being implemented—regardless of the application. Proper analysis and documentation of the previous maintenance processes (actual analyses) and a detailed planned concept of the business processes indicating how they must subsequently be performed with the support of the SAP system are prerequisites for the implementation and are the basis for customizing SAP EAM.

Business function

Actual and planned processes

372 Book_M.indb 135 12/7/10 11:56:19 AM

136

5 Business Processes

The time and effort required to complete a full and correct business process modeling will definitely be worth it. For more information about this topic, see Chapter 9, Section 9.3.1, Project Preparation.

Question 6: When Should You Include the Other User Departments?

You should include other user departments in the company as soon as possible. If you choose sales order processing, particularly if you want to integrate warehouse management, purchasing, and controlling, this raises numerous questions that affect the business processes and require permits, such as:

What information must the automatically generated purchase EE

requisitions contain?

Who creates the purchase order?EE

Where is the acceptance of services performed entered?EE

How is the notification made for goods receipts?EE

Is the material delivered to or collected from the warehouse?EE

Who calculates the final costing and when?EE

Are the orders settled automatically?EE

What does the costing sheet look like for maintenance orders?EE

Experience shows that the permit process with the user departments in question takes longer than you would initially think.

Rule of thumb: If you double the time planned for approval with the affected user departments, you’ll more or less be on the right track. Specify the ap-proval process as early as possible. Specifically define who must look after which aspect and when, and who must make which decisions. Also check the “homework.”

We’ll now look at the business processes in detail. Let’s begin with the process of a planned repair task because this is the most comprehen-sive business process. This will make it easier to describe other business processes such as breakdown maintenance or follow-up entries using abstracts based on this process.

372 Book_M.indb 136 12/7/10 11:56:19 AM

137

Planned Repairs Business Process 5.2

Planned Repairs Business Process5.2

The business process for a planned repair task is characterized by the fact that the required resources (work centers, materials, external companies, and so on) can be planned but are only identified when the need arises. This business process occurs in, for example, the following cases:

If the casing on a pump has to be resealedEE

If the lift chain on a fork lift truck must be replacedEE

If a door in a building has to be replacedEE

If a pressure control valve in the process plant has to be changedEE

If test equipment has to be recalibratedEE

So the process for a planned repair differs from an immediate repair (see Section 5.3) in terms of the ability to schedule it (you can react to mal-functions but not plan them) and from preventive maintenance (see Section 5.8) in terms of the prescribed schedule (maintenance and inspection tasks have regular cycles and, consequently, recurring deadlines).

The process for a planned repair can be performed in the following five steps (see also Figure 5.3):

In Step 1, you enter the notification of specific damage or any other request (such as a request for a modification).

In Step 2, the order is created and planned from the notification. Typical planning tasks are creating operations, reserving spare parts, assigning external companies and, planning operating times.

In Step 3, you transfer the order to controlling. There, you check the corresponding availability, provide the required capacities, and print out the shop papers.

The processing phase (Step 4) involves the withdrawal of the spare parts from the warehouse and the actual processing of the order.

After you complete the tasks, the required actual times are confirmed in the completion in Step 5; you also enter technical completion confirma-tions about how the damage was processed and the status of the technical system here. Controlling settles the order, and the information is updated in the history.

Can be planned but not predicted

372 Book_M.indb 137 12/7/10 11:56:20 AM

138

5 Business Processes

Notification

Planning

Controlling

Implementation

Completion

HistoryMaterial Usage, Orders, Notifications, Information System, Usage List

•Technical Object•Description

•Date•Priority

•Work to be Performed•Resource Internal/External

•Material•Tools

•Capacity Leveling•Availability Check

Order Release••Paper Printout

•Material Withdrawal Planned/Unplanned•External Procurement

•Time Confirmation•Techn. Completion

•Order Settlement•Techn. Completion

Confirmation

Planned Repairs Business ProcessFigure 5.3

The following sections go through these five steps and explain the func-tions the SAP system offers.

Notification5.2.1

Notifications are the tool you use in exceptional operational situations in maintenance processing to:

Describe the technical emergency situation of an objectEE

Request a required task in the maintenance processingEE

Document the work performedEE

Notifications document maintenance tasks and make them available for analysis in the long term.

Opening Notifications

The notifications are either entered directly by the relevant requester (for example, a production employee) or transferred to plant maintenance via

Why use notifications?

Who enters notifications?

372 Book_M.indb 138 12/7/10 11:56:20 AM

139

Planned Repairs Business Process 5.2

the usual means of communication (for example, by telephone, form, or similar) and entered there.

There are different ways to create notifications in the SAP system:

SAP dialog transactions (IW21, IW24-26) that are directly available EE

in SAP EAM.

The EE Easy Web Transaction, a Web transaction that contains a simple HTML form (see Chapter 8, Section 8.1.5, Easy Web Transaction).

Procedures where the notification data accrues in upstream systems EE

(such as GIS, process control systems, and diagnostic systems). These are then transferred into SAP EAM through an interface (for example, the PM-PCS interface) and generate the notification there (see Chapter 6, Section 6.4.1, Operations Monitoring Systems).

The following descriptions initially focus on entering notifications in SAP EAM itself.

Notification Types

In earlier releases, SAP predefined three notification types in the standard system:

Activity report EE for documenting performed actions

Malfunction reportEE for information about malfunctions and problems that occur

Maintenance requestEE for requesting tasks to be performed

You can now define notification types as you want according to your own requirements. You should define the notification types based on the functions, in which the notification types differ in Customizing. You can define settings for each notification type in Customizing, such as:

Number rangeEE

Partner determination procedureEE

Print controlEE

Status schemaEE

One of the most important functions is the option to define your own screen layout for each notification type. The structure displayed in Figure

How are the notifications entered?

Defining notification types as you want

Screen layout

372 Book_M.indb 139 12/7/10 11:56:20 AM

140

5 Business Processes

5.1 containing all of the data of a notifi cation is refl ected in the layout of the M1 notifi cation type delivered by SAP (see Figure 5.4).

Notifi cation Type M1Figure 5.4

This notifi cation type consists of eight tabs and their subtabs. You’ll fi nd fi eld groups on every tab.

However, this type of screen layout would be overly complex for a pro-duction employee, for example, who merely wants to report damage.

Design suitable screen layouts for your notifi cation types. Adapted and sim-plifi ed screen layouts increase user acceptability. Use the Cross-Application Components • Notifi cation • Overview of Notifi cation Type • Screen Structure for Extended View or Screen Structure for Simplifi ed View Customizing functions for this purpose.

372 Book_M.indb 140 12/7/10 11:56:21 AM

141

Planned Repairs Business Process 5.2

An entry screen could look like the one confi gured for you as notifi cation type 00 (see Figure 5.5).

Notifi cation Type 00Figure 5.5

You can even set up the screen layout in such a way that a different layout appears when you change data compared to when you enter data. Use the activity type for the screen structure for this in the Customizing function.

When do you need this option? You need it, for example, when you want to provide a production employee with a screen that is as basic as possible for entering a notifi cation. But if the maintenance employee subsequently calls the same notifi cation later, he should be able to update the notifi cation with additional required information. If the same notifi -cation is called in change mode, for example, it could then have tabs and fi eld groups like those shown in Figure 5.6.

Notifi cation Content

The following screen groups or tabs are available as possible notifi cation content:

Reference object (equipment, functional location, assembly, material EE

serial number)

Responsibilities (for example, planner group, main work center)EE

Item and cause (for example, damage, cause of damage, object part)EE

Customizing

372 Book_M.indb 141 12/7/10 11:56:22 AM

142

5 Business Processes

Notifi cation Type 00 in Change ModeFigure 5.6

System availabilityEE (for example, system availability before/after)

Malfunction data (for example, breakdown, start/end/duration of EE

breakdown)

Start/end dates (for example, priority, required start, required end)EE

Item overview (for example, assembly, text)EE

Activities for notifi cation header and notifi cation itemEE

TasksEE for notifi cation header and notifi cation item

Causes for notifi cation header and notifi cation itemEE

Notifi cation and object addressEE

Partner overview (for example, partner role, partnerEE , address)

Warranty (for example, start/end of warranty)EE

Location (for example, maintenance plant, cost center, business area)EE

372 Book_M.indb 142 12/7/10 11:56:23 AM

143

Planned Repairs Business Process 5.2

Scheduling overview (for example, date of notification, completion, EE

technical control)

Maintenance plan (for example, maintenance task list, maintenance EE

plan)

Important information in the notification is the object in question—the reference object.

Flexible Reference Object

You can enter notifications as reference objects for all technical objects: functional location, equipment, assemblies, and material serial numbers. If you assign a lower-level object to a notification, the higher-level objects are also entered automatically. If you enter an assembly, the equipment and functional location are also automatically included in the notifica-tion.

You can also specifically enter notifications without specifying a technical object. This is the case:

If a malfunction report refers to an object that is not listed under a EE

number in the system

If the faulty object cannot exactly be located yetEE

If a notification refers to a new object to be provided as part of an EE

investment measure

You have the following options to specify the type of technical object to be entered:

For a EE notification type: in Customizing via the function Cross-Applica-tion Components • Notification • Overview of Notification Type • Screen Areas in Notification Header

For a EE user: within the notification by selecting Extras • Setting • Default Values

For an EE individual notification: within the notification by selecting Extras • Setting • Reference Object

When you receive a new notification from the requester and you have to decide whether the maintenance task is performed or not, it is very useful to get concise information about the object. You use the object information for this purpose.

Type of technical object

372 Book_M.indb 143 12/7/10 11:56:23 AM

581

Index

A

Actions, 201, 386, 554Address, 151, 154Address management, 117After-event recording, 208, 438Amount settlement, 356Approval, 199, 387, 553, 554ASAP, 481As-is analysis, 497, 505Asset accounting, 346Authorization concept, 482, 505Authorization Objects, 571Availability check, 158, 185, 332

capacity, 186material, 187production resources/tools, 186

Availability control, 416, 424, 431Availability of technical systems, 24

B

Bill of material, 55, 60, 91, 448multiple BOMs, 95variant BOM, 95

BOM, 378equipment BOM, 55, 92functional location BOM, 92material BOM, 55, 93

Building control systems, 30, 303, 372Business blueprint, 482, 494, 503Business completion, 203Business function, 34Business process master list, 495Business process modeling, 135, 499

C

CAD, 373, 477, 480, 507Calibration, 305

Call horizon, 268, 277, 284, 286Capacity planning, 48Capacity requirements planning, 182Catalog profile, 145, 147, 149Catalogs, 145CATS, 198, 363Change management, 489Characteristic, 398, 407, 409, 553Classes, 553Classification, 96, 148, 378, 468, 554Collaboration Folders, 446Company code, 42Completion confirmation, 199

collective time confirmation, 198individual time confirmation, 198

Condition-based maintenance, 30, 301, 375Confirmation, 191, 197, 310, 363, 476, 533, 556Construction type, 71, 93, 258Control inputs, 518Control key, 47, 160, 163, 183, 218, 220, 307Controlling, 349, 477

commercial, 383measure-based, 383object-based, 383operational, 381period-based, 383strategic, 382tactical, 381technical, 383

Controlling area, 42Cost accounting unit, 409Cost center budget, 418Cost centers, 350, 358Cost elements, 350, 358Costing, 50, 158, 174, 226, 241, 352Counter, 107, 282, 302, 441, 533, 553Cross-plant maintenance, 43Customer exit, 533, 573Cut-over plan, 495, 511

372 Book_M.indb 581 12/7/10 11:59:52 AM

582

Index

Cycle modification factor, 278

D

Data transfer, 104hierarchical, 104horizontal, 105

Deadline monitoring, 255, 270Deletion, 64Display variants, 391Document, 112, 172, 440, 448, 553Dynamic date calculation, 389

E

Early Warning System, 403Easy Web Transaction, 139, 444E-learning, 454Electronic parts catalog, 442Electronic signature, 468Equipment, 54, 59, 76, 83, 143, 147, 172, 306, 333, 346, 378, 386, 404, 409, 468, 476, 553, 563

equipment hierarchies, 82install/dismantle, 76place in storage/remove from storage, 78

E-selling, 452Estimated costs, 174, 177Event-driven process chains, 500External assignment, 217, 242

F

Field selection, 63, 135, 335First line maintenance, 24Flexible reports, 402FMEA, 31Functional location, 54, 59, 60, 65, 83, 143, 147, 378, 386, 409, 553, 563

alternative labeling, 73BOM, 55

G

GIS, 139, 373, 377, 469Guided procedures, 438GUI XT, 535

H

Handling unit, 337

I

IBIP, 507Immediate repair, 137, 204, 208IM Programs, 419Improvement, 28Individual purchase order, 219, 331InfoCube, 407, 408In-house production, 342Input planning, 493Inspection, 26Inspection lot, 256, 308, 556Inspection rounds, 296

K

Key figure, 398, 407, 409

L

Legacy data transfer, 482, 507Link type, 291LIS, 396, 401, 415Location, 41LSMW, 508

M

Maintenance, 27Maintenance Cost Budgeting, 426Maintenance Event Builder, 324, 557Maintenance item, 254

372 Book_M.indb 582 12/7/10 11:59:52 AM

583

Index

Maintenance package hierarchy, 278Maintenance plan, 155, 254, 307, 344, 533

cost display for maintenance plan, 272multiple counter plan, 255, 290, 293single cycle plan, 255, 282strategy plan, 255, 274, 287

Maintenance planner group, 121Maintenance schedules, 387Maintenance strategy, 29, 253, 275, 556Maintenance task list, 170, 254, 264, 275, 288, 306, 387, 533Main work center, 161Manufacturer guidelines, 25Mass change, 106, 181Master Data Management, 368Material, 55, 87, 132, 172, 178, 260, 334, 378, 386, 409

material requirements planning (MRP), 335material reservation, 167material type, 89, 334material where-used list, 170material withdrawal, 195, 467non-stock material, 168stock material, 167user departments, views, data, 90

Measurement document transfer, 111Measurement point, 386Measures, 386Measuring point, 107, 302, 441, 468, 533, 553MES systems, 373Mobile data entry systems, 30Mobile maintenance, 454MTBR, 410MTTR, 410Multiple counter plan, 556

N

Network, 320, 557Notification, 132, 138, 156, 157, 158, 205, 256, 325, 363, 386, 409, 440, 467, 476, 533, 554

actions, 132, 146item, 386notification item, 145notification type, 139, 147tasks, 132, 142, 146

Number assignment, 61

O

Object information, 144, 154, 158, 553Object link, 54, 85, 386Object list, 132, 173, 467Offset, 279OLAP, 397OLTP, 397Operations, 132, 160, 178, 259, 467Order, 132, 205, 256, 286, 325, 363, 386, 440, 467, 476, 533, 555

order budget, 179, 416order hierarchy, 178order release, 191order settlement, 158, 353, 355order type, 158, 194, 206, 220, 233, 264, 308

Organizational structure, 39Organizational unit, 39Overhead costs, 353

P

Paging, 459, 505, 554Partner, 142, 409, 467

partner determination procedure, 123, 139, 158, 460partner function, 123, 460partner transfer, 150partner type, 122

Partners, 121, 149, 154, 553, 554Permit, 124, 177Person, 161, 361, 363Planned repairs, 137, 204Planner group, 41, 161, 264, 409, 563Plant, 39, 409

maintenance plant, 40planning plant, 39

372 Book_M.indb 583 12/7/10 11:59:52 AM

584

Index

Plant maintenance controlling, 381Plant section, 41, 563PM assembly, 55, 87, 143, 553, 563PM-IS, 397, 399, 401, 404, 562PM-PCS interface, 304, 375, 556Pool asset management, 312Preliminary and follow-up buffers, 279Preventive plant maintenance, 137, 250, 556Prices, 351Printing, 151, 192, 554Priority, 158, 554Process control systems, 30, 139, 303, 372Production planning and control, 339Production resources/tools, 133, 172, 178, 260Product structure browser, 102Project-based maintenance, 319Project system, 319Purchase order, 333Purchase requisition, 168, 203, 219, 230, 331

Q

Quality management, 344QuickViewer, 392

R

Real estate management, 359Reference functional location, 54, 65, 72Reference locations, 386Refurbishment, 231, 557Reliability-based maintenance, 31Repair, 27Request, 409Reservation, 167, 191, 195, 203, 331Responses, 387Restart costs, 25RFID, 470Risk factors, 479Risk sources, 484

S

Sales, 365SAP Easy Document Management, 114SAP ERP Human Capital Management, 361SAP implementation project, 479SAP List Viewer, 386SAP Mobile Asset Management, 460, 480SAP NetWeaver BW, 405, 415, 426, 437SAP NetWeaver Portal, 434, 437, 444, 480SAP query, 396SCADA, 30, 303, 374Scheduling, 48, 158, 162, 178, 284, 294

lead time scheduling, 163network scheduling, 163overview, 273scheduling type, 164

Scheduling indicator, 266, 277Scheduling period, 268, 278Screen layout, 158Screen templates, 135Selection variants, 389Serial number, 40, 55, 76, 232, 234, 557

serial number profile, 80Serial numbers, 338, 386Service, 365Service entry sheet, 256Service-oriented architecture (SOA), 473Service specifications, 219, 228, 332, 379, 556Settlement rule, 133Shift factor, 267, 277Shift notes, 210Single cycle plan, 556Standard reports, 399Status, 186, 187, 190, 192, 202, 309, 312, 327, 339, 355, 448

status schema, 139, 158system status, 125, 152, 154user status, 125, 152, 154, 554

Strategy plan, 556Structure indicator, 61

372 Book_M.indb 584 12/7/10 11:59:52 AM

585

Index

Success factors, 479, 486Supplier Relationship Management, 368System availability, 142, 201

T

Tasks, 201, 554Technical completion, 202Test and measurement equipment, 344Test equipment, 305, 530, 557Test plan, 495Time confirmation, 467Tolerance, 267, 277Total productive manufacturing (TPM), 24Transaction/event chain diagram, 500Transaction variants, 521

U

Upstream transactions, 530Usability, 504, 513, 518, 521Usage decision, 310

User acceptance, 504User parameters, 523

V

Value chain diagram, 499Vendor portal, 450Virtual personnel capacities, 452Virtual spare parts storage, 451

W

Warranties, 119, 476, 553customer warranty, 119vendor warranty, 119warranty counter, 120

WBS elements, 320, 420, 422, 557Work center, 41, 45, 71, 121, 218, 226, 264, 339, 340, 361, 409, 556

main, 45performing, 45

372 Book_M.indb 585 12/7/10 11:59:52 AM