Processing Repairs in SAP Plant Maintenance

157 Pages·2016·11.005 MB·English

by  Karl Liebstückel

Karl Liebstückel
Processing Repairs in SAP® Plant Maintenance
This E-Bite is protected by copyright. Full Legal Notes and Notes on Usage can be found at the end of this
publication.
SAP PRESS E-Bites
SAP PRESS E-Bites provide you with a high-quality response to your specific
project need. If you’re looking for detailed instructions on a specific task; or if you
need to become familiar with a small, but crucial sub-component of an SAP
product; or if you want to understand all the hype around product xyz: SAP
PRESS E-Bites have you covered. Authored by the top professionals in the SAP
universe, E-Bites provide the excellence you know from SAP PRESS, in a
digestible electronic format, delivered (and consumed) in a fraction of the time!
Manu Kohli
Incident Management with SAP EHS Management
ISBN 978-1-4932-1330-6 | $19.99 | 100 pages
Jawad Akhtar
Configuring Kanban in SAP ERP MM and PP
ISBN 978-1-4932-1337-5 | $14.99 | 80 pages
Matt Chudy and Luis Castedo
Purchasing with SAP ERP Materials Management
ISBN 978-1-4932-1371-9 | $9.99 | 85 pages
The Author of this E-Bite
Dr. Karl Liebstückel is a professor of information management and
business software at the Würzburg-Schweinfurt University of Applied
Sciences, Germany. He is the managing director of a consulting firm
and was chairman of the German SAP User Group (DSAG) from
2007 to 2012.
What You’ll Learn
Manage planned and unscheduled repairs to your plant with SAP EAM. With this
E-Bite, you’ll master the five stages of managing repairs: notification, planning,
controlling, processing, and completing. Guided by expert tips on tailoring your
SAP EAM implementation to meet your specific plant needs, you can ensure you’ll
have the timely notifications, spare parts, and work orders necessary to keep your
plant in tip-top shape.
1 Notification
1.1 Creating Notifications
1.2 Reference Objects
1.3 Catalogs and Catalog Profiles
1.4 Partners and Address
1.5 Documents, Printing, and Status
2 Planning
2.1 Creating an Order
2.2 Responsibilities and Scheduling
2.3 Materials and Production Resources
2.4 Estimated Costs
2.5 Documents and Objects
3 Controlling
3.1 Mass Change
3.2 Capacity Requirements Planning
3.3 Availability Checks
3.4 Order Release
3.5 Shop Paper Printing
4 Processing
5 Completion
5.1 Confirmations
5.2 Completions
6 Immediate Repairs
This E-Bite is an excerpt from Plant Maintenance with SAP—Practical Guide by
Karl Liebstückel.
1 Notification
Notifications are the maintenance processing tool that you use in exceptional
operational situations to perform the following activities:
Describe the technical emergency situation of an object
Request a required task in the maintenance processing
Document the work performed
Notifications create document maintenance tasks and make them available for
analysis in the long term. In the following sections we will explain how to create a
notification, assign an object to it, and the types of information you can store in
one.
1.1 Creating Notifications
Notifications are either entered directly by the relevant requester (for example, a
production employee) or transferred to plant maintenance using the usual means
of communication (for example, by telephone or form) and entered there.
There are different ways you can create notifications in the SAP system, as
follows:
SAP dialog transactions
You can use the SAP dialog transactions (IW21, IW24–26), which are
directly available in SAP EAM.
Easy Web Transaction
You use the Easy Web Transaction—that is, a web transaction that contains
a simple HTML form.
Your own web transactions
In addition, you can develop your own web transactions, the data of which is
transferred by BAPIs to the SAP system.
Upstream systems
Procedures are used in which the notification data is created in upstream
systems (such as geographic information systems [GIS], process control
systems, and diagnostic systems). This is then transferred to SAP EAM via
an interface (for example, PM-PCS interface) and creates the notification
there.
In earlier releases, SAP predefined three notification types in the standard
system:
Activity report
For documenting performed actions
Malfunction report
For information about malfunctions and problems that occur
Maintenance request
For requesting tasks to be performed
You can now define notification types as you wish 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, for example, the
following settings for each notification type in Customizing:
Number range
Partner determination procedure
Print control
Status profile
One of the most important functions, however, is the option to define your own
screen layout for each notification type. The structure displayed in Figure 1,
containing all the data of a notification, is reflected in the layout of the M1
notification type delivered by SAP (see Figure 2).
Figure 1 Planned Repairs Business Process
This notification type consists of eight tabs, with individual tabs containing sub-
tabs. Thus, for example, the I tab still contains sub-tabs for items, causes of
TEMS
damage, tasks, and actions. Each tab has up to five field groups.
However, this type of screen layout would be overly complex for a production
employee, for example, who merely wants to report damage.
Design Your Own Layouts for Notifications
You can design suitable screen layouts for your notification types—adapted
and simplified screen layouts increase user acceptability. Use the Customizing
function S S E V S S
CREEN TRUCTURE FOR XTENDED IEW OR CREEN TRUCTURE FOR
S V for this purpose.
IMPLIFIED IEW
Figure 2 Notification Type M1
An entry screen could look like the one configured for you as notification type 00
(see Figure 3).
Different Layouts for Entering and Changing
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. In this case,
use the activity type for the screen structure 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 notification. If the maintenance employee calls the same message at a
later point, however, he or she must be able to add further necessary information.
Figure 3 Notification Type 00
If the same notification is called in change mode, for example, it could then have
tabs and field groups like those shown in Figure 4.
Figure 4 Notification Type 00 in Change Mode
The following screen groups or tabs are available as possible notification content:
Reference object (for example, equipment, functional location, assembly,
material serial number)
Responsibilities (for example, planner group, main work center)
Item and cause (for example, damage, cause of damage, object part)
System availability (for example, system availability before, after)
Malfunction data (for example, breakdown, start, end, duration of
breakdown)
Start/end dates (for example, priority, required start, and required end)
Item overview (for example, assembly, text)
Activities for notification header and notification item
Tasks for notification header and notification item
Causes for notification header and notification item
Notification and object address
Partner overview (for example, partner role, partner, address)
Warranty (for example, start, end of warranty)
Location (for example, maintenance plant, cost center, business area)