Sappress Plant Maintenance With Sap

5/25/2018 Sappress Plant Maintenance With Sap

1/27

Karl Liebstckel

Plant Maintenance with SAP

Bonn Boston


2/27

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


3/27

7

Contents

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

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

1.1 Target Audience ............................................................ 16

1.2 What this Book Can and Cannot Do .............................. 18

1.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 .................................... 26

2.3 Development of Maintenance Strategies ....................... 29

2.4 Development of SAP Plant Maintenance ....................... 31

2.5 SAP ERP 6.0 ................................................................. 32

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

3.1 SAP Organizational Units .............................................. 39

3.1.1 The Plant from a Maintenance Perspective ....... 39

3.1.2 Maintenance-Specic Organizational Units ....... 40

3.1.3 Other General Organizational Units .................. 42

3.1.4 Plant-Specic 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 .................................................. 65

4.2.1 Functional Locations and Reference Functional

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


4/27

8

Contents

4.2.2 Equipment and Serial Numbers ........................ 76

4.2.3 Links and Networks .......................................... 85

4.2.4 Material and PM Assemblies ............................ 87

4.2.5 Bill of Material ................................................. 91

4.2.6 Classication .................................................... 964.2.7 Product Structure Browser ................................ 102

4.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 .................................. 137

5.2.1 Notication ...................................................... 1385.2.2 Planning ........................................................... 154

5.2.3 Controlling ....................................................... 180

5.2.4 Processing ........................................................ 195

5.2.5 Completion ...................................................... 197

5.3 Immediate Repairs Business Process .............................. 204

5.4 Shift Notes and Shift Reports ........................................ 210

5.5 External Assignment Business Process ........................... 217

5.5.1 Basic Principles of External Assignment ............ 217

5.5.2 External Services as an Individual PurchaseOrder ............................................................... 219

5.5.3 External Services with External Work Centers ... 224

5.5.4 External Services with Service Specications ..... 228

5.6 Refurbishment Business Process ................................... 231

5.7 Subcontracting Business Process ................................... 242

5.8 Preventive Maintenance Business Process ..................... 250

5.8.1 Basic Principles of Preventive Maintenance ...... 251

5.8.2 Objects of Preventive Maintenance .................. 253

5.8.3 Maintenance Task Lists ..................................... 257

5.8.4 Preventive Maintenance Time-Based ............. 264

5.8.5 Preventive Maintenance Performance-Based ... 282

5.8.6 Preventive Maintenance Time- and

Performance-Based .......................................... 290

5.8.7 Inspection Rounds ............................................ 296

5.9 Condition-Based Maintenance Business Process ............ 301

5.10 Calibration Inspection Test Equipment Business Process ... 305


5/27

9

Conte

5.11 Pool Asset Management Business Process ..................... 312

5.12 Project-Based Maintenance Business Process ................ 319

5.12.1 SAP Project System .......................................... 319

5.12.2 Maintenance Event Builder .............................. 324

6 Integrating Applications from Other Departments .... 329

6.1 How Other Departments Are Involved .......................... 329

6.2 Integration Within SAP ERP .......................................... 330

6.2.1 Materials Management .................................... 331

6.2.2 Production Planning and Control ...................... 339

6.2.3 Quality Management ........................................ 344

6.2.4 Financial Accounting ........................................ 344

6.2.5 Controlling ....................................................... 3496.2.6 Real Estate Management .................................. 359

6.2.7 SAP ERP Human Capital Management .............. 361

6.2.8 Service and Sales .............................................. 365

6.3 Integration With Other SAP Software ........................... 368

6.3.1 Integration with SAP NetWeaver MDM ............ 368

6.3.2 Integration with SAP SRM ................................ 370

6.4 Integration With Non-SAP Systems ............................... 372

6.4.1 Operations Monitoring Systems ....................... 373

6.4.2 Operations Information Systems ....................... 3756.4.3 Service Specications and Activity Recording .... 379

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

7.1 What Plant Maintenance Controlling is About .............. 381

7.2 SAP Tools for Acquiring Information and How to

Use Them ..................................................................... 385

7.2.1 SAP List Viewer ................................................ 386

7.2.2 QuickViewer .................................................... 3927.2.3 SAP ERP Logistics Information System .............. 396

7.2.4 SAP NetWeaver BW ......................................... 405

7.2.5 Comparison of the LIS and SAP NetWeaver BW ... 414

7.3 SAP Tools for Budgeting and How To Use Them ............ 416

7.3.1 Order Budgeting .............................................. 416

7.3.2 Cost Center Budgeting ..................................... 418

7.3.3 Budgeting with IM Programs ............................ 419


6/27

10

7.3.4 Budgeting with WBS Elements ......................... 422

7.3.5 Maintenance Cost Budgeting ............................ 426

8 New Information Technologies in Plant Maintenance ... 433

8.1 Internet and Intranet .................................................... 433

8.1.1 SAP NetWeaver Portal and Roles ...................... 434

8.1.2 After-Event Recording ...................................... 438

8.1.3 Structure Display .............................................. 440

8.1.4 Electronic Parts Catalogs ................................... 442

8.1.5 Easy Web Transaction ....................................... 444

8.1.6 Collaboration Folders ....................................... 446

8.1.7 Vision or Reality? ............................................. 448

8.2 Mobile Maintenance ..................................................... 4548.2.1 Fundamentals of Mobile Maintenance .............. 454

8.2.2 Paging .............................................................. 459

8.2.3 SAP Mobile Asset Management ....................... 460

8.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 MaintenanceProject .......................................................................... 479

9.1.1 Implementation Strategy .................................. 479

9.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 ....................... 488

9.3.1 Project Preparation ........................................... 488

9.3.2 Business Blueprint ............................................ 503

9.3.3 Implementation ............................................... 5099.3.4 Final Preparation .............................................. 510

9.3.5 Go-Live and Support ........................................ 511

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

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

Contents


7/27

11

10.2 Assessing Usability ........................................................ 518

10.3 Importance of Usability in Plant Maintenance ............... 518

10.4 SAP System Options to Improve Usability ..................... 521

10.4.1 Transaction Variants ....................................... 521

10.4.2 General User Parameters ................................ 52310.4.3 Maintenance-Specic User Parameters ........... 524

10.4.4 Customizing ................................................... 526

10.4.5 List Variants ................................................... 527

10.4.6 Roles and Favorites ........................................ 528

10.4.7 Customizing Input Help ................................. 529

10.4.8 Function Keys and Key Combinations ............. 529

10.4.9 Upstream Transactions ................................... 530

10.4.10 Customer Exits ............................................... 533

10.4.11 GUI XT ........................................................... 53510.5 Usability Study for SAP ERP 6.0 .................................... 535

10.5.1 Preparation and Execution ............................. 536

10.5.2 Results ........................................................... 540

10.5.3 Conclusions .................................................... 544

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

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

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

Resources ..................................................................... 553

B.2 Functions of Notications and Orders ........................... 554

B.3 Integration Aspects ....................................................... 557

B.4 Standard Reports of SAP PM-IS .................................... 562

B.5 Enterprise Services for Plant Maintenance ..................... 565

B.6 Authorization Objects in SAP EAM ............................... 570

B.7 Customer Exits for Plant Maintenance ........................... 572

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

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

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

Conte


8/27

129

The following chapter forms the core of this book: it shows youhow you can map and implement typical business processes of

plant maintenance, such as planned repair tasks or preventivemaintenance in the SAP system. However, business processes in

particular are unique in character, so company must nd its ownway of mapping themand 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 youlike all

other user companies before youmust 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

youll nd 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 tasksE

Processing immediate repair tasks such as troubleshooting measuresE

Entering maintenance activities that have already been performedE

(after-event recording)

Shift notes and shift reportsE

Outsourcing maintenance tasksE

Subcontracting, that is, subcontracting for service and repairE

Reference

processes


9/27

130

5 Business Processes

Processing preventive maintenance measures based on timeE

and performance

Processing condition-based maintenanceE

Processing refurbishment measuresE

Processing test equipment calibrationsE

Implementing maintenance projectsE

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

Youll 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 specically mean. I have included three columns

there to indicate priority. Decide yourself, and assess the relevant func-tions according to their signicance in your company.

The full functionality of the SAP system does not have to be, and should not

be, implemented all at once.


10/27

131

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

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 theE

rst phase

Priority B: could have additional benets, possibly also include in the rstE

phase

Priority C: unnecessary for nowE

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 Notication and/or an Order?

You can or must decide whether you want to use only the notication,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.

Notication

The basic differences between a notication and an order are:

A notication is used toE request and documenta maintenance activity,whereas an order is used toplan and implement a maintenance task.

A notication mainly containsE technical information, whereas an order

essentially containsprocessing information.

A notication has practically noE 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 reected in the different functions (see

Appendix A.2) and different informationof both objects.

Notication

vs. order


11/27

132


A notication has the following characteristics:

Header dataE

Each notication has header data. This includes information that is

used to identify and manage the notication. It applies to the com-

plete notication.

Notifcation itemE

You enter and maintain the data in a notication item to identify in

more detail the problem or damage that occurred or for the executed

action. A notication can have several items.

ActionsE

Actions document the work performed for a notication. They are

particularly important in inspections to provide evidence of the work

performed and the results established.TaskE 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:

Header dataE

Header data is information that is used to identify and manage the

order. It applies to the complete order.

Object listE

The object list contains the objects with which the order is executed

(functional locations, equipment, assemblies, notications). You can

enter these objects on the order header as a reference object and/or

on the object list.

OperationsE

You can use operations to describe the work that you want to be

performed when the order is being implemented.

MaterialE 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 notication

Structure of

an order


12/27

133


which a reservation is subsequently generated, or non-stock material,

for which a purchase requisition is created.

Date/Time/Reported by

DescriptionReference Object: Functional Location

EquipmentAssembly

Material Serial Number

Location DataBreakdown/Availability

Activity

Execution FactorsActivities

Dates

Task DescriptionTasks

Location of the DamageDamage

Cause of the Damage

Text

Notification Items

Notification

Structure and Content of a NoticationFigure 5.1

Production resources/toolsE

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.

Settlement ruleE

In the settlement rule, you specify the cost unit (for example, cost

center), to which the costs must be charged.

Cost dataE

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 gures of the Plant Main-

tenance Information System are updated via the value categories, and

how these key gures 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.


13/27

134


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

e.g.,Material, Quantity, Unit of Measure, StorageLocation, 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 notication and/or an

order. If you make the same decision as the majority, or approximately 80%,

of SAP user companies, youll use the notication and the order. The rest

use only the order. There are some cases (mainly in the initial phase) where

companies opt to use the notication 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 notication orE

an order (for example, the reference object)

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

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 signies time and ef-

fort in terms of entering and maintaining data, makes no sense. Only enter

data that is also information for you.


14/27

135


The SAP system also enables you to congure notications and orders

exibly:

You can dene the layout of screen templatesE yourself based on the

notication or order type (number, sequence, name and content of

tabs).

The eld selectionE option enables you to differentiate important

information from unimportant information or to hide elds that you

do not require.

The LOG_EAM_SIMP business function must be activated for you to use

a exible screen layout for orders.

Actively use this option to dene the appearance of the notication and or-

der yourself and design your own layouts: For example, place the most im-portant information on the rst tab and hide unimportant elds. Youll nd

the explanations about how to do this in Sections 5.2.1, Notication, 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 acceptanceand usabilityin 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 implementedregardless of the application. Properanalysis 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 functio

Actual and plann

processes


15/27

136


The time and effort required to complete a full and correct business

process modeling will denitely 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 purchaseE

requisitions contain?

Who creates the purchase order?E

Where is the acceptance of services performed entered?E

How is the notication made for goods receipts?E

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

Who calculates the nal costing and when?E

Are the orders settled automatically?E

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

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

Rule of thumb: If you double thetime planned for approval with the affected

user departments, youll more or less be on the right track. Specify the ap-

proval process as early as possible. Specically dene who must look after

which aspect and when, and who must make which decisions. Also check

the homework.

Well now look at the business processes in detail. Lets 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.


16/27

137

Planned Repairs Business Process 5

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 identied when the need arises.This business process occurs in, for example, the following cases:

If the casing on a pump has to be resealedE

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

If a door in a building has to be replacedE

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

If test equipment has to be recalibratedE

So the process for a planned repair differs from an immediate repair(seeSection 5.3) in terms of the ability to schedule it (you can react to mal-

functions but not plan them) and frompreventive 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 aplanned repaircan be performed in the following ve

steps (see also Figure 5.3):

In Step 1, you enter the noticationof specic damage or any other

request (such as a request for a modication).In Step 2, the order is created and planned from the notication. 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.

Theprocessing 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 conrmed in

the completionin Step 5; you also enter technical completion conrma-

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 predicte


17/27

138


Notification

Planning

Controlling

Implementation

Completion

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

Technical ObjectDescription

DatePriority

Work to be Performed

Resource Internal/External

Material

Tools

Capacity LevelingAvailability Check

Order ReleasePaper Printout

Material Withdrawal Planned/UnplannedExternal Procurement

Time ConfirmationTechn. Completion

Order SettlementTechn. Completion

Confirmation

Planned Repairs Business ProcessFigure 5.3

The following sections go through these ve steps and explain the func-

tions the SAP system offers.

Notification5.2.1

Notications are the tool you use in exceptional operational situations in

maintenance processing to:

Describe the technical emergency situation of an objectE

Request a required task in the maintenance processingE

Document the work performedE

Notications document maintenance tasks and make them available for

analysis in the long term.

Opening Notications

The notications are either entered directly by the relevant requester (for

example, a production employee) or transferred to plant maintenance via

Why use

notications?

Who enters

notications?


18/27

139


the usual means of communication (for example, by telephone, form, or

similar) and entered there.

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

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

in SAP EAM.

TheE 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 notication data accrues in upstream systemsE

(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 notication there (see Chapter

6, Section 6.4.1, Operations Monitoring Systems).

The following descriptions initially focus on entering notications in

SAP EAM itself.

Notication Types

In earlier releases, SAP predened three notication types in the standard

system:

Activity reportE for documenting performed actions

Malfunction reportE

for information about malfunctions and problemsthat occur

Maintenance requestE for requesting tasks to be performed

You can now dene notication types as you want according to your

own requirements. You should dene the notication types based on the

functions, in which the notication types differ in Customizing. You can

dene settings for each notication type in Customizing, such as:

Number rangeE

Partner determination procedureE

Print controlE

Status schemaE

One of the most important functions is the option to dene your own

screen layout for each notication type. The structure displayed in Figure

How are the

notications

entered?

Dening

notication type

as you want

Screen layout


19/27

140


5.1 containing all of the data of a notication is reected in the layout of

the M1 notication type delivered by SAP (see Figure 5.4).

Notication Type M1Figure 5.4

This notication type consists of eight tabs and their subtabs. Youll nd

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 notication types. Adapted and sim-

plied screen layouts increase user acceptability. Use the Cross-Application

Components Notication Overview of Notication Type Screen

Structure for Extended View or Screen Structure for Simplied View

Customizing functions for this purpose.


20/27

141


An entry screen could look like the one congured for you as notication

type 00 (see Figure 5.5).

Notication 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 aspossible for entering a notication. But if the maintenance employee

subsequently calls the same notication later, he should be able to update

the notication with additional required information. If the same noti-

cation is called in change mode, for example, it could then have tabs and

eld groups like those shown in Figure 5.6.

Notication Content

The following screen groups or tabs are available as possible notication

content:

Reference object (equipment, functional location, assembly, materialE

serial number)

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

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

Customizing


21/27

142


Notication Type 00 in Change ModeFigure 5.6

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

Malfunction data (for example, breakdown, start/end/duration ofE

breakdown)

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

Item overview (for example, assembly, text)E

Activities for notication header and notication itemE

TasksE for notication header and notication item

Causes for notication header and notication itemE

Notication and object addressE

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

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

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


22/27

143


Scheduling overview (for example, date of notication, completion,E

technical control)

Maintenance plan (for example, maintenance task list, maintenanceE

plan)

Important information in the notication is the object in questionthe

reference object.

Flexible Reference Object

You can enter notications as reference objects for all technical objects:

functional location, equipment, assemblies, and material serial numbers.

If you assign a lower-level object to a notication, the higher-level objects

are also entered automatically. If you enter an assembly, the equipment

and functional location are also automatically included in the notica-tion.

You can also specically enter notications without specifying a technical

object. This is the case:

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

number in the system

If the faulty object cannot exactly be located yetE

If a notication refers to a new object to be provided as part of anE

investment measure

You have the following options to specify the type of technical object to

be entered:

For aE notication type:in Customizing via the function Cross-Applica-

tion ComponentsNoticationOverview of Notication Type

Screen Areas in Notication Header

For aE user: within the notication by selecting Extras Setting

Default Values

For anE individual notication: within the notication by selecting

ExtrasSettingReference Object

When you receive a new notication 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 technica

object


23/27

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, 505

Authorization Objects, 571Availability check, 158, 185, 332capacity, 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, 286

Capacity planning, 48Capacity requirements planning, 182Catalog prole, 145, 147, 149Catalogs, 145CATS, 198, 363Change management, 489Characteristic, 398, 407, 409, 553Classes, 553Classication, 96, 148, 378, 468, 554Collaboration Folders, 446Company code, 42

Completion conrmation, 199collective time confirmation, 198individual time confirmation, 198

Condition-based maintenance, 30, 301,375Conrmation, 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


24/27

582

Index

Cycle modication 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, 454

Electronic 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, 76

place in storage/remove from storage,78E-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, 208

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

KKey gure, 398, 407, 409

L

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

LSMW, 508

M

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


25/27

583

Ind

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

cost display for maintenance plan,272

multiple 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, 533

Main work center, 161Manufacturer guidelines, 25Mass change, 106, 181

Master 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, 167

user departments, views, data, 90Measurement document transfer, 111Measurement point, 386Measures, 386Measuring point, 107, 302, 441, 468,533, 553

MES systems, 373Mobile data entry systems, 30Mobile maintenance, 454MTBR, 410MTTR, 410

Multiple counter plan, 556

N

Network, 320, 557Notication, 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, 397

Operations, 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, 39

Overhead 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


26/27

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, 556

Pool 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, 80

Serial numbers, 338, 386Service, 365Service entry sheet, 256Service-oriented architecture (SOA), 473Service specications, 219, 228, 332,

379, 556Settlement rule, 133Shift factor, 267, 277Shift notes, 210Single cycle plan, 556Standard reports, 399

Status, 186, 187, 190, 192, 202, 309,312, 327, 339, 355, 448status schema, 139, 158system status, 125, 152, 154user status, 125, 152, 154, 554

Strategy plan, 556Structure indicator, 61


27/27

585

Ind

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 conrmation, 467Tolerance, 267, 277Total productive manufacturing (TPM),24

Transaction/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, 119

vendor warranty, 119warranty counter, 120WBS elements, 320, 420, 422, 557Work center, 41, 45, 71, 121, 218, 226,

264, 339, 340, 361, 409, 556main, 45performing, 45

Documents

Sappress Plant Maintenance With Sap