Karl Liebstckel

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 ............................................................ 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-Specifc Organizational Units ....... 40
3.1.3 Other General Organizational Units .................. 42
3.1.4 Plant-Specifc 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
372 Book_M.indb 7 12/7/10 11:55:29 AM
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 Classifcation .................................................... 96
4.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 Notifcation ...................................................... 138
5.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 Purchase
Order ............................................................... 219
5.5.3 External Services with External Work Centers ... 224
5.5.4 External Services with Service Specifcations ..... 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
372 Book_M.indb 8 12/7/10 11:55:29 AM
9
Contents
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 ....................................................... 349
6.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 ....................... 375
6.4.3 Service Specifcations 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 .................................................... 392
7.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
372 Book_M.indb 9 12/7/10 11:55:29 AM
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 ..................................................... 454
8.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 Maintenance
Project .......................................................................... 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 ............................................... 509
9.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
372 Book_M.indb 10 12/7/10 11:55:29 AM
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 ................................ 523
10.4.3 Maintenance-Specifc 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 ........................................................... 535
10.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 .............................................................................. 553
B.1 Functional Comparison of Structuring
Resources ..................................................................... 553
B.2 Functions of Notifcations 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
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 fnd its own
way of mapping themand this is where this chapter will assist
you.
Business Processes 5
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 fnd 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 tasks
E
Processing immediate repair tasks such as troubleshooting measures
E
Entering maintenance activities that have already been performed
E
(after-event recording)
Shift notes and shift reports
E
Outsourcing maintenance tasks
E
Subcontracting, that is, subcontracting for service and repair
E
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
E
and performance
Processing condition-based maintenance
E
Processing refurbishment measures
E
Processing test equipment calibrations
E
Implementing maintenance projects
E
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.
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 specifcally mean. I have included three columns
there to indicate priority. Decide yourself, and assess the relevant func-
tions according to their signifcance 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 E
frst phase
Priority B: could have additional benefts, possibly also include in the frst E
phase
Priority C: unnecessary for now E
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 Notifcation and/or an Order?
You can or must decide whether you want to use only the notifcation,
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.
Notifcation
The basic differences between a notifcation and an order are:
A notifcation is used to
E
request and document a maintenance activity,
whereas an order is used to plan and implement a maintenance task.
A notifcation mainly contains
E
technical information, whereas an order
essentially contains processing information.
A notifcation has practically no
E
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 refected in the different functions (see
Appendix A.2) and different information of both objects.
Notifcation
vs. order
372 Book_M.indb 131 12/7/10 11:56:18 AM
132
5 Business Processes
A notifcation has the following characteristics:
Header data
E

Each notifcation has header data. This includes information that is
used to identify and manage the notifcation. It applies to the com-
plete notifcation.
Notifcation item
E

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

Actions document the work performed for a notifcation. They are
particularly important in inspections to provide evidence of the work
performed and the results established.
Task
E
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 data
E

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

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

You can use operations to describe the work that you want to be
performed when the order is being implemented.
Material
E
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 notifcation
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 by
Description
Reference Object: Functional Location
Equipment
Assembly
Material Serial Number
Location Data
Breakdown/Availability
Activity
Execution Factors
Activities
Dates
Task Description
Tasks
Location of the Damage
Damage
Cause of the Damage
Text
Notification
Items

Notification
Structure and Content of a Notifcation Figure 5.1
Production resources/tools
E

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 rule
E

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

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 fgures of the Plant Main-
tenance Information System are updated via the value categories, and
how these key fgures 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
Production
Resources/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 Order Figure 5.2
Decide as early as possible whether you want to use a notifcation and/or an
order. If you make the same decision as the majority, or approximately 80%,
of SAP user companies, youll use the notifcation and the order. The rest
use only the order. There are some cases (mainly in the initial phase) where
companies opt to use the notifcation 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 notifcation or
E
an order (for example, the reference object)
That you reasonably want to store in SAP EAM (for example, the cost
E
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 signifes 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 confgure notifcations and orders
fexibly:
You can defne the layout of screen templates
E
yourself based on the
notifcation or order type (number, sequence, name and content of
tabs).
The feld selection
E
option enables you to differentiate important
information from unimportant information or to hide felds that you
do not require.
The LOG_EAM_SIMP business function must be activated for you to use
a fexible screen layout for orders.
Actively use this option to defne the appearance of the notifcation and or-
der yourself and design your own layouts: For example, place the most im-
portant information on the frst tab and hide unimportant felds. Youll fnd
the explanations about how to do this in Sections 5.2.1, Notifcation, 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 implementedregardless 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 defnitely 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
E
requisitions contain?
Who creates the purchase order?
E
Where is the acceptance of services performed entered?
E
How is the notifcation made for goods receipts?
E
Is the material delivered to or collected from the warehouse?
E
Who calculates the fnal 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 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, youll more or less be on the right track. Specify the ap-
proval process as early as possible. Specifcally defne 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.
372 Book_M.indb 136 12/7/10 11:56:19 AM
137
Planned Repairs Business Process 5.2
Planned Repairs Business Process 5.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 identifed when the need arises.
This business process occurs in, for example, the following cases:
If the casing on a pump has to be resealed
E
If the lift chain on a fork lift truck must be replaced
E
If a door in a building has to be replaced
E
If a pressure control valve in the process plant has to be changed
E
If test equipment has to be recalibrated
E
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 fve
steps (see also Figure 5.3):
In Step
1
, you enter the notifcation of specifc damage or any other
request (such as a request for a modifcation).
In Step
2
, the order is created and planned from the notifcation. 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 confrmed in
the completion in Step
5
; you also enter technical completion confrma-
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
History
Material 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 Process Figure 5.3
The following sections go through these fve steps and explain the func-
tions the SAP system offers.
Notification 5.2.1
Notifcations are the tool you use in exceptional operational situations in
maintenance processing to:
Describe the technical emergency situation of an object
E
Request a required task in the maintenance processing
E
Document the work performed
E
Notifcations document maintenance tasks and make them available for
analysis in the long term.
Opening Notifcations
The notifcations are either entered directly by the relevant requester (for
example, a production employee) or transferred to plant maintenance via
Why use
notifcations?
Who enters
notifcations?
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 notifcations in the SAP system:
SAP dialog transactions (IW21, IW24-26) that are directly available
E
in SAP EAM.
The
E
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 notifcation data accrues in upstream systems
E
(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 notifcation there (see Chapter
6, Section 6.4.1, Operations Monitoring Systems).
The following descriptions initially focus on entering notifcations in
SAP EAM itself.
Notifcation Types
In earlier releases, SAP predefned three notifcation types in the standard
system:
Activity report
E
for documenting performed actions
Malfunction report
E
for information about malfunctions and problems
that occur
Maintenance request
E
for requesting tasks to be performed
You can now defne notifcation types as you want according to your
own requirements. You should defne the notifcation types based on the
functions, in which the notifcation types differ in Customizing. You can
defne settings for each notifcation type in Customizing, such as:
Number range
E
Partner determination procedure
E
Print control
E
Status schema
E
One of the most important functions is the option to defne your own
screen layout for each notifcation type. The structure displayed in Figure
How are the
notifcations
entered?
Defning
notifcation 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 notifcation is refected in the layout of
the M1 notifcation type delivered by SAP (see Figure 5.4).
Notifcation Type M1 Figure 5.4
This notifcation type consists of eight tabs and their subtabs. Youll fnd
feld 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 notifcation types. Adapted and sim-
plifed screen layouts increase user acceptability. Use the Cross-Application
Components

Notifcation

Overview of Notifcation Type

Screen
Structure for Extended View or Screen Structure for Simplifed 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 confgured for you as notifcation
type 00 (see Figure 5.5).
Notifcation Type 00 Figure 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 notifcation. But if the maintenance employee
subsequently calls the same notifcation later, he should be able to update
the notifcation with additional required information. If the same notif-
cation is called in change mode, for example, it could then have tabs and
feld groups like those shown in Figure 5.6.
Notifcation Content
The following screen groups or tabs are available as possible notifcation
content:
Reference object (equipment, functional location, assembly, material
E
serial number)
Responsibilities (for example, planner group, main work center)
E
Item and cause (for example, damage, cause of damage, object part)
E
Customizing
372 Book_M.indb 141 12/7/10 11:56:22 AM
142
5 Business Processes
Notifcation Type 00 in Change Mode Figure 5.6
System availability
E
(for example, system availability before/after)
Malfunction data (for example, breakdown, start/end/duration of
E
breakdown)
Start/end dates (for example, priority, required start, required end)
E
Item overview (for example, assembly, text)
E
Activities for notifcation header and notifcation item
E
Tasks
E
for notifcation header and notifcation item
Causes for notifcation header and notifcation item
E
Notifcation and object address
E
Partner overview (for example, partner role, partner
E
, address)
Warranty (for example, start/end of warranty)
E
Location (for example, maintenance plant, cost center, business area)
E
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 notifcation, completion,
E
technical control)
Maintenance plan (for example, maintenance task list, maintenance
E
plan)
Important information in the notifcation is the object in questionthe
reference object.
Flexible Reference Object
You can enter notifcations as reference objects for all technical objects:
functional location, equipment, assemblies, and material serial numbers.
If you assign a lower-level object to a notifcation, the higher-level objects
are also entered automatically. If you enter an assembly, the equipment
and functional location are also automatically included in the notifca-
tion.
You can also specifcally enter notifcations without specifying a technical
object. This is the case:
If a malfunction report refers to an object that is not listed under a
E
number in the system
If the faulty object cannot exactly be located yet
E
If a notifcation refers to a new object to be provided as part of an
E
investment measure
You have the following options to specify the type of technical object to
be entered:
For a
E
notifcation type: in Customizing via the function Cross-Applica-
tion Components

Notifcation

Overview of Notifcation Type

Screen Areas in Notifcation Header
For a
E
user: within the notifcation by selecting Extras

Setting

Default Values
For an
E
individual notifcation: within the notifcation by selecting
Extras

Setting

Reference Object
When you receive a new notifcation 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, 554
Address, 151, 154
Address management, 117
After-event recording, 208, 438
Amount settlement, 356
Approval, 199, 387, 553, 554
ASAP, 481
As-is analysis, 497, 505
Asset accounting, 346
Authorization concept, 482, 505
Authorization Objects, 571
Availability check, 158, 185, 332
capacity, 186
material, 187
production resources/tools, 186
Availability control, 416, 424, 431
Availability of technical systems, 24
B
Bill of material, 55, 60, 91, 448
multiple BOMs, 95
variant BOM, 95
BOM, 378
equipment BOM, 55, 92
functional location BOM, 92
material BOM, 55, 93
Building control systems, 30, 303, 372
Business blueprint, 482, 494, 503
Business completion, 203
Business function, 34
Business process master list, 495
Business process modeling, 135, 499
C
CAD, 373, 477, 480, 507
Calibration, 305
Call horizon, 268, 277, 284, 286
Capacity planning, 48
Capacity requirements planning, 182
Catalog profle, 145, 147, 149
Catalogs, 145
CATS, 198, 363
Change management, 489
Characteristic, 398, 407, 409, 553
Classes, 553
Classifcation, 96, 148, 378, 468, 554
Collaboration Folders, 446
Company code, 42
Completion confrmation, 199
collective time confirmation, 198
individual time confirmation, 198
Condition-based maintenance, 30, 301,
375
Confrmation, 191, 197, 310, 363, 476,
533, 556
Construction type, 71, 93, 258
Control inputs, 518
Control key, 47, 160, 163, 183, 218,
220, 307
Controlling, 349, 477
commercial, 383
measure-based, 383
object-based, 383
operational, 381
period-based, 383
strategic, 382
tactical, 381
technical, 383
Controlling area, 42
Cost accounting unit, 409
Cost center budget, 418
Cost centers, 350, 358
Cost elements, 350, 358
Costing, 50, 158, 174, 226, 241, 352
Counter, 107, 282, 302, 441, 533, 553
Cross-plant maintenance, 43
Customer exit, 533, 573
Cut-over plan, 495, 511
372 Book_M.indb 581 12/7/10 11:59:52 AM
582
Index
Cycle modifcation factor, 278
D
Data transfer, 104
hierarchical, 104
horizontal, 105
Deadline monitoring, 255, 270
Deletion, 64
Display variants, 391
Document, 112, 172, 440, 448, 553
Dynamic date calculation, 389
E
Early Warning System, 403
Easy Web Transaction, 139, 444
E-learning, 454
Electronic parts catalog, 442
Electronic signature, 468
Equipment, 54, 59, 76, 83, 143, 147,
172, 306, 333, 346, 378, 386, 404, 409,
468, 476, 553, 563
equipment hierarchies, 82
install/dismantle, 76
place in storage/remove from storage,
78
E-selling, 452
Estimated costs, 174, 177
Event-driven process chains, 500
External assignment, 217, 242
F
Field selection, 63, 135, 335
First line maintenance, 24
Flexible reports, 402
FMEA, 31
Functional location, 54, 59, 60, 65, 83,
143, 147, 378, 386, 409, 553, 563
alternative labeling, 73
BOM, 55
G
GIS, 139, 373, 377, 469
Guided procedures, 438
GUI XT, 535
H
Handling unit, 337
I
IBIP, 507
Immediate repair, 137, 204, 208
IM Programs, 419
Improvement, 28
Individual purchase order, 219, 331
InfoCube, 407, 408
In-house production, 342
Input planning, 493
Inspection, 26
Inspection lot, 256, 308, 556
Inspection rounds, 296
K
Key fgure, 398, 407, 409
L
Legacy data transfer, 482, 507
Link type, 291
LIS, 396, 401, 415
Location, 41
LSMW, 508
M
Maintenance, 27
Maintenance Cost Budgeting, 426
Maintenance Event Builder, 324, 557
Maintenance item, 254
372 Book_M.indb 582 12/7/10 11:59:52 AM
583
Index
Maintenance package hierarchy, 278
Maintenance plan, 155, 254, 307, 344,
533
cost display for maintenance plan,
272
multiple counter plan, 255, 290, 293
single cycle plan, 255, 282
strategy plan, 255, 274, 287
Maintenance planner group, 121
Maintenance schedules, 387
Maintenance strategy, 29, 253, 275, 556
Maintenance task list, 170, 254, 264,
275, 288, 306, 387, 533
Main work center, 161
Manufacturer guidelines, 25
Mass change, 106, 181
Master Data Management, 368
Material, 55, 87, 132, 172, 178, 260,
334, 378, 386, 409
material requirements planning
(MRP), 335
material reservation, 167
material type, 89, 334
material where-used list, 170
material withdrawal, 195, 467
non-stock material, 168
stock material, 167
user departments, views, data, 90
Measurement document transfer, 111
Measurement point, 386
Measures, 386
Measuring point, 107, 302, 441, 468,
533, 553
MES systems, 373
Mobile data entry systems, 30
Mobile maintenance, 454
MTBR, 410
MTTR, 410
Multiple counter plan, 556
N
Network, 320, 557
Notifcation, 132, 138, 156, 157, 158,
205, 256, 325, 363, 386, 409, 440, 467,
476, 533, 554
actions, 132, 146
item, 386
notification item, 145
notification type, 139, 147
tasks, 132, 142, 146
Number assignment, 61
O
Object information, 144, 154, 158, 553
Object link, 54, 85, 386
Object list, 132, 173, 467
Offset, 279
OLAP, 397
OLTP, 397
Operations, 132, 160, 178, 259, 467
Order, 132, 205, 256, 286, 325, 363,
386, 440, 467, 476, 533, 555
order budget, 179, 416
order hierarchy, 178
order release, 191
order settlement, 158, 353, 355
order type, 158, 194, 206, 220, 233,
264, 308
Organizational structure, 39
Organizational unit, 39
Overhead costs, 353
P
Paging, 459, 505, 554
Partner, 142, 409, 467
partner determination procedure,
123, 139, 158, 460
partner function, 123, 460
partner transfer, 150
partner type, 122
Partners, 121, 149, 154, 553, 554
Permit, 124, 177
Person, 161, 361, 363
Planned repairs, 137, 204
Planner group, 41, 161, 264, 409, 563
Plant, 39, 409
maintenance plant, 40
planning plant, 39
372 Book_M.indb 583 12/7/10 11:59:52 AM
584
Index
Plant maintenance controlling, 381
Plant section, 41, 563
PM assembly, 55, 87, 143, 553, 563
PM-IS, 397, 399, 401, 404, 562
PM-PCS interface, 304, 375, 556
Pool asset management, 312
Preliminary and follow-up buffers, 279
Preventive plant maintenance, 137, 250,
556
Prices, 351
Printing, 151, 192, 554
Priority, 158, 554
Process control systems, 30, 139, 303,
372
Production planning and control, 339
Production resources/tools, 133, 172,
178, 260
Product structure browser, 102
Project-based maintenance, 319
Project system, 319
Purchase order, 333
Purchase requisition, 168, 203, 219,
230, 331
Q
Quality management, 344
QuickViewer, 392
R
Real estate management, 359
Reference functional location, 54, 65, 72
Reference locations, 386
Refurbishment, 231, 557
Reliability-based maintenance, 31
Repair, 27
Request, 409
Reservation, 167, 191, 195, 203, 331
Responses, 387
Restart costs, 25
RFID, 470
Risk factors, 479
Risk sources, 484
S
Sales, 365
SAP Easy Document Management, 114
SAP ERP Human Capital Management,
361
SAP implementation project, 479
SAP List Viewer, 386
SAP Mobile Asset Management, 460,
480
SAP NetWeaver BW, 405, 415, 426, 437
SAP NetWeaver Portal, 434, 437, 444,
480
SAP query, 396
SCADA, 30, 303, 374
Scheduling, 48, 158, 162, 178, 284, 294
lead time scheduling, 163
network scheduling, 163
overview, 273
scheduling type, 164
Scheduling indicator, 266, 277
Scheduling period, 268, 278
Screen layout, 158
Screen templates, 135
Selection variants, 389
Serial number, 40, 55, 76, 232, 234, 557
serial number profile, 80
Serial numbers, 338, 386
Service, 365
Service entry sheet, 256
Service-oriented architecture (SOA), 473
Service specifcations, 219, 228, 332,
379, 556
Settlement rule, 133
Shift factor, 267, 277
Shift notes, 210
Single cycle plan, 556
Standard reports, 399
Status, 186, 187, 190, 192, 202, 309,
312, 327, 339, 355, 448
status schema, 139, 158
system status, 125, 152, 154
user status, 125, 152, 154, 554
Strategy plan, 556
Structure indicator, 61
372 Book_M.indb 584 12/7/10 11:59:52 AM
585
Index
Success factors, 479, 486
Supplier Relationship Management, 368
System availability, 142, 201
T
Tasks, 201, 554
Technical completion, 202
Test and measurement equipment, 344
Test equipment, 305, 530, 557
Test plan, 495
Time confrmation, 467
Tolerance, 267, 277
Total productive manufacturing (TPM),
24
Transaction/event chain diagram, 500
Transaction variants, 521
U
Upstream transactions, 530
Usability, 504, 513, 518, 521
Usage decision, 310
User acceptance, 504
User parameters, 523
V
Value chain diagram, 499
Vendor portal, 450
Virtual personnel capacities, 452
Virtual spare parts storage, 451
W
Warranties, 119, 476, 553
customer warranty, 119
vendor warranty, 119
warranty counter, 120
WBS elements, 320, 420, 422, 557
Work center, 41, 45, 71, 121, 218, 226,
264, 339, 340, 361, 409, 556
main, 45
performing, 45
372 Book_M.indb 585 12/7/10 11:59:52 AM