Professional Documents
Culture Documents
A. INTRODUCTION.............................................................................................4
B.1.0 MANAGEMENT OF TECHNICAL OBJECTS…………………………..11
B.1.1 CREATE WORK CENTRE………….………………….…….……………11
B.1.2 CHANGE WORK CENTRE………….………………….…………………15
B.1.3 DISPLAY WORK CENTRE……………………………………………….15
B.2.0 CREATE EQUIPMENT.................................................................................16
B.2.1 INSTALLATION EQUIPMENT TO A FUNCTIONAL LOCATION......20
B.2.2 CHANGE EQUIPMENT ............................................................................21
B.2.3 DISPLAY EQUIPMENT...............................................................................21
B.3.0 FUNCTIONAL LOCATION..........................................................................22
B.3.1 CREATE FUNCTIONAL LOCATION:......................................................22
B.3.2 FUNCTIONAL LOCATION STRUCURAL DISPLAY.............................25
B.4 .0 CREATE EQUIPMENT BOM......................................................................30
B.4.1 CHANGE EQUIPMENT BOM ....................................................................31
B.4.2 DISPLAY EQUIPMENT BOM ....................................................................31
B.5.0 GENERAL TASK LIST.................................................................................32
B.5.1 CREATE GENERAL TASL LIST................................................................33
B.5.2 CHANGE GENERAL TASL LIST...............................................................35
B.5.3 DISPLAY GENERAL TASL LIST...............................................................35
B.5.4 CREATE EQUIPMENT TASKLIST….……………………………..……36
B.5.5 CHANGE EQUIPMENT TASK LIST.........................................................38
B.5.6 DISPLAY EQUIPMENT TASK LIST........................................................38
C.1.0 PM PROCESSING........................................................................................39
C.1.1 MAIN PROCESSING STEPS.......................................................................39
C.2.0 CREATE MAINTENANCE PLAN..............................................................40
C.2.1 SHEDULE MAINTENANCE PLAN...........................................................46
C.2.2 DEAD LINE MONITORING OF MAINTENANCE PLAN.....................48
D.1.0 CREATE MAINTENANCE ORDER W.R.T NOTIFICATION..............51
Required Fields
• Client
• User
• Password
• Language
Screen Banner
Standard Tool Bar
Screen Header
Title Bar
Application Tool Bar
Screen Body
Insert/Overtype
Indicator
Server
Status Bar
SAP System ID
The Standard Toolbar contains the Command field and the standard
SAP Toolbar buttons.
Command Field: The Command field is used to enter transaction
codes that take you directly to a system task without using menus.
Keyboard
Keyboard Butto
Button Keyboard
Button
Button Description
Description Description
Description
Shortcut
Shortcut n Shortcut
Shortcut
Enter Key Enter/Continue Ctrl + Page Up First page
Ctrl + S Save to database Page Up Previous page
F3 Back Page Down Next page
Ctrl + Page
Shift + F3 Exit System Task Last page
Down
Down
F12 Cancel None Create New session
Create shortcut on
Ctrl + P Print None Desktop
Desktop
Ctrl + F Find F1 F1 Help
Customize Local
Ctrl + G Find next Alt + F12
Layout
Layout
A. INTRODUCTION
There are varied Operations, Options, and Screens in the system, it is not practical for all of
them to be documented. Moreover, the system also provides a drill down help at most of
the places and varied selection criteria. Further online help available for the explanation of
the fields, which can be seen by pressing ‘F1’ by positioning the cursor at the relevant
field.
There are short cut methods available as ‘Transaction codes’ which can be seen, noted and
practiced by looking at “ System – Status” at the relevant screen.
1. Functional locations
2. Equipment Master
mySAP ECC 6.0 <Owner: Adinarayana Reddy> Page No.
5
3. Equipment Boms
4. Work centre
5. Maintenance Task Lists
6. Maintenance Planning
7. Maintenance Processing
8. Information System
Each section in the Module has its set of Options and Transactions. In brief these are
explained below:
Functional Location
A functional location is an element in a technical structure, representing an area of a system
at which an object can be installed.
Equipment Master
Equipment is an individual, physical object that is to be maintained independently. It can
be installed in a technical system or part of a technical system.
Equipment Boms
A “Bill Of Material” (BOM) is a complete, formally structured list of the components
making up a technical object or an assembly. The list contains the object numbers of the
individual components together with their quantity and unit of measure. The components
can be stock or non-stock spares or assemblies, which in turn can be described using
maintenance BOMs
Work Centers: This deals with defining a set of establishment of an Organization which
actually performs a given task or job. This master data is created to the extent required in
the beginning and can be appended based on requirements.
Maintenance Task Lists: These are set of operations which are expected to be repeatedly
used are listed and attached with requirements like components, PRTs etc and kept for
usage whenever required.
Maintenance Planning: The Task lists with frequency attached can be planned by the
system and the same are Planned initially for first time by giving the start date and the
system keeps the track from then onwards. The orders for the system-planned tasks are
obtained by running ‘Deadline monitoring’ at fixed intervals for a specified number of days
for which orders are to be created.
Information System: The transactional data captured in the above systems is available for
the analysis based on various parameters, such as Planner group wise, Equipment wise,
Damage wise, etc.
TERMINOLOGY:
Functional Location
A functional location is an element in a technical structure, representing an area of a
system at which an object can be installed.
Equipment
Euipment is an individual, physical object, which is to be maintained independently. It
can be installed in a technical system or part of a technical system.
sub-pieces of equipment are themselves pieces of equipment. They are objects, which
are to be maintained as autonomous units and for which an individual maintenance
history is to be built up.
Maintenance Plant
The maintenance plant of a technical object is the plant at which it is installed. The
technical object is physically located in this plant, eg, SM01
Bill of Material
A bill of material (BOM) is a complete formally structured list of the components
making up a technical object or assembly. The list contains the object number of each
component together with the quantity and unit of measure. The components can be
stock or non-stock spares or assemblies, which in turn can be described by BOMs.
Work Center
A work center is where an operation or activity is carried out within a production plant.
A work center can represent a machine or a group of machines as well as a person or a
group of people.
Maintenance Strategy
The maintenance strategy controls the sequence of regular maintenance tasks.
The following is determined by the maintenance strategy:
the scheduling rule for individual maintenance tasks
the allocation of maintenance packages
Maintenance Package
A maintenance package is nothing but the frequency of carrying out preventive
maintenance operations.
Maintenance Item
mySAP ECC 6.0 <Owner: Adinarayana Reddy> Page No.
8
A maintenance item provides information on technical objects, operations to be
performed and operation frequency.
One or more maintenance items can be allocated to a maintenance plan.
Maintenance Plan
A maintenance plan describes the dates and scope of the maintenance and inspection
activities to be performed, and can therefore be used to ensure that technical objects run
optimally.
Maintenance Notification
A maintenance notification is used to describe the condition of a technical object in the
PM System, to refer the maintenance department to a task that needs to be carried out
and to document the work performed.
There are three types of maintenance notification in the standard version of the PM
System:
Malfunction Report
Activity Report
Maintenance Request
Malfunction Report
A malfunction report describes a malfunction at an object, which affects its
performance in some respect. Using a malfunction report, for example, an employee in
Production can report that performance of a system is reduced or that its output is of a
reduced quality.
Activity Report
An activity report describes a maintenance activity which has already been carried out,
and which was not necessary due to a malfunction or a damage. It simply provides
technical documentation that record which activities were carried out when, at what
time and with what results.
Maintenance Request
A maintenance request is a targeted instruction to the maintenance department to carry
out an activity in the manner described. The decisive factor in this case is that there is
no malfunction.
Maintenance Order
A maintenance order can be used to plan execution of maintenance tasks, monitor the
work progress and allocate the costs for maintenance tasks. A maintenance order can
be created with reference to one or more notifications or without referencing to a
notification. It gets generated when a maintenance plan is scheduled.
Maintenance History
Usage List
The usage of a piece of equipment can be relevant to performance, damage frequency,
breakdown behavior and the comparison of products from different manufacturers. For
the purposes of maintenance, therefore, it is important that you can find out at any time,
when and where a piece of equipment is or was installed. This information may be
found in the usage list in the PM system.
Notification History
Data concerning past problems and malfunctions arising at a technical object, and
maintenance activities that were carried out on a technical object, can have a significant
bearing on future maintenance activities. For this reason, it is important that
information on malfunctions, causes, downtime, etc. is stored on a long-term basis and
can be called at any time. Only by evaluating past maintenance activities, in particular
those involving malfunctions, useful changes can be made to ensure smooth
operation in future. This historical data may be found in the PM system in the
maintenance history.
Order History
Certain data from completed and historical PM orders is particularly important for a
meaningful analysis of the performance of past maintenance activities, and for effective
and well-founded planning of future maintenance tasks. This data is stored in two
places in the PM system:
Completed PM orders in the order database.
This chapter deals with the various options of the master data related to Equipment,
functional locations, etc. which are referred as the ‘Technical Objects’ in SAP terminology
A main work center is maintenance work center, which carries out maintenance
activities on a equipment.
These Work centers are identified with the Equipment Master and will appear as default
while raising any Notification against that equipment or location. However a
Enter
And Save
Now Work Centre created for Plant SM01
And we can Change and Display the Work centre using the following Menu path
Enter the work centre earlier created and display the data
mySAP ECC 6.0 <Owner: Adinarayana Reddy> Page No.
15
B.2 CREATE EQUIPMENT
General data - Equipment description (say Punching machine), Object type, Weight,
Acquisition date & value, manufacturer, Manufacturer part no., Authorisation group
Enter the number of equipment earlier created and change any data.
Save the changes.
Enter the number of equipment earlier created and display the data.
In the “explosion of levels below” tick “Location Hierarchy” equipment installed, Eqpt hierarchy and
bom explosion. & then execute (F8).
The relevant options have to be ticked, for Functional Location hierarchy, Equipment
installed, etc. to allow the system to take into account for the data to be displayed. E.g., if
BOM explosion is not ticked, the same cannot be seen in the result screen.
In the Plant field, one should be careful to enter a right plant matching the functional
location other wise kept blank. Entry of wrong plant will not allow the system to show the
BOM.
The master data of these can be viewed by ‘Display’ option under them. In case of listing
of locations or equipments, the same can be done by
Menu path: Logistics – Plant maintenance – Technical Objects – (FunctLoc /Equipment) - List
Editing – display’ (IH08) option under them and the system displays a screen requesting some
fields for the selection criteria. On entering the data in the relevant fields, and executing,
the list display appears. The system shows the list with standard fields. User can set the
fields of the choice for display, as is the case in any other listing criteria through display
field selection in Settings – Variants.
Enter the Plant as SM01 & BOM usage as 4(Plant maintenance) and press Enter
Enter the number of BOM earlier created and change any data.
Save the changes
Enter the number of BOM earlier created and view the data.
The maintenance task lists are the List of Operations, which are listed and kept for repeated
usage. This includes, details like work center will take up an activity, Operation
description, carried out and Components attached, etc..These are used / copied to any order
whenever required.
In case of regular Preventive Maintenance Schedules, the Task lists are created and
attached to Plans, which will be prompted by the system from time to time, based on the
frequency defined. The critical PM schedules are those schedules for equipments which are
having defined set of Operations and cannot be planned on a frequency basis, but are to be
carried out during Shutdowns. Those operations are listed as Task Lists without allocating
the Frequency and they can be viewed, listed, attached to Orders created for execution
during Shut down. These are to be listed with ‘Usage’ field as ‘4’ For the
Task List to be allowed to be used further, the Task List status is to be given as ‘4 –
Released general’ in the header info.
The description of operation in the Task List are not required to be defined, if standard text
for that operation is entered in the ‘Std Txt’ field. This also enables the system to list these
operations, when one needs to list all Operations in All Task lists.
These General Task lists are used where the ‘n’ number of equipments are having
identical Operations. OR if the Equipments are having different task lists for each
equipment then we have to create task lists for each equipment wise.
Enter
Select all the fields and Click Tab MntPack, appears bellow screen
And Save General task list saves giving the group number
Enter the number of task list earlier created and change any data.
Save the changes
Enter the number of task list earlier created and view the data.
Next select all line items and click on Mnt Pack Tab
Enter the number of task list earlier created and change any data.
Save the changes
Enter the number of task list earlier created and view the data
This chapter deals with processing of unplanned jobs reported using Maintenance
Notifications and processing of Maintenance Orders created
a) With reference to Maintenance Notification,
b) from Maintenance Plans,
c) Directly without a Notification or Plan.
PM NOTIFICATION
Production department to notify all the maintenance requests uses this. This can also be
used for requesting the jobs between sections, such as request for Cranes, request for
Calibration, etc..
Menupath–Logistics>PlantMaintenance>PreventiveMaintenance>Maintenance
Planning>Maintenance Plans>Create-Strategy Plan (IP42)
Enter
And Save
Menupath–Logistics>PlantMaintenance>PreventiveMaintenance>Maintenance
Planning>Scheduling for Maintenance Plans>Schedule (IP10)
Enter
CLICK on START TAB , A Pop-up menu appears start cycle and gives date
Menupath–Logistics>PlantMaintenance>PreventiveMaintenance>Maintenance
Planning>Scheduling for Maintenance Plans>Deadline monitoring(IP30)
After Scheduling the maintenance plan deadline monitoring is to be done for maintenance
plan date monitoring and system will create automatic maintenance Orders for the
schedules
The system helps in planning the preventive maintenance schedules automatically. The
activities and their frequencies are mentioned in the Task Lists. These task lists are used in
creating the Maintenance plans. For the first time the planning cycle is to be given by the
user to enable the system to continue to plan the schedules by taking earlier activities which
are already planned. Subsequent planning is done by the system automatically by using the
deadline monitoring.
The ‘Dead line’ monitoring will make the system to generate the Orders for next
stipulated number of days and these orders are used for further working
T.C = IP30
Enter
Menu Path: Logistics – Plant maintenance – Maintenance processing – Notifications – Create (general)
– IW21
Following screen appears in which the notification type screen comes with the Pull down
help:
After pressing creation TAB a pop-up window will appear asking some required fields
Like Order type = PM01, planning plant =SM01 and Maint.work centre = SML-WORK
And select
Go to operations Tab
Go to Components Tab
Menu Path: Logistics – Plant maintenance – Maintenance processing – Order – Change – IW32
Enter
Reservation Number
This is the notification used to report the emergency jobs such as breakdown. The only
difference in the screen is the Reqd start and End dates are referred as Malfunction start
and end as the job is supposed to be attended immediately.
Note: For the above notification, clicking the ‘Order’ Field in the notification can directly
generate an order.
The history updating in the notification or history available only in notification means the
analysis on Object Part, Damage, Cause and Activity analyses. Rest of the detailed history
is to be maintained in the long text available in the PM order next to ‘Description’ field.
ACTIVITY REPORT
An activity report describes a maintenance activity which has already been carried out, and
which was not necessary due to a malfunction or a damage. As in above two types of
notifications, this also provides technical documentation that record which activities were
carried out when, at what time and with what results for historical analysis. Only
Maintenance Departments will use this type of Maintenance Notification for those
Maintenance Orders where no notification exists.
The difference from the above two types is that there is no start and end dates fields, but,
the field for entering the activity carried out is directly displayed instead of going through
‘Activities’ button in the header.
This is useful, where the Order is directly generated by the system for Preventive
Maintenance Schedule.
1. Correct Work Center or Planner group must be entered, without which, the notification
will not appear in the list displays and goes unnoticed by the section that is supposed to
take action.
2. The system with the help of the master data will copy the Planner group and
Maintenance Work centers, on pressing ‘Enter’ button after entering an Equipment in
the Reference Object. If an agency other than that is suggested by the system is to
work, the person raising the notification must change it to the relevant planner group
and the work center.
3. Activity report is to be used only by the maintenance section to record the activities
performed in case of there is no notification exist for the job. If the notification already
exists, the updating is to be done in the respective notification.
4. Any section to know what are all the requests made to them by various sections is
obtained by:
5. The data in the fields of Object Part, Damage, Cause and Activity are important as
these are useful for Historical analysis of the data, such as Number of failures of a
particular part, Type or repetition of damages, etc.
Enter
Once the order is completed the one need to enter the actual data, which is the actual
historical record of the activities, performed.
Menu Path: Logistics – Plant Maintenance – Maintenance processing – Completion confirmation –
Individual entry – Entry (IW41)
Apart from the confirmation of actual time for the job, a check box need to be ticked if any
pending reservations (reserved but not drawn) are to be cleared.
However, the fields ‘Personal No’, Wage Type’ and ‘Activity Type’ need not be entered, as
these are associated with some other Cross Applications.
Save
On job completion the system needs the method of the costs of the maintenance orders is to
be settled, that are to a cost center. There could be a case where the same order costs are to
be split among various cost centers. This rule is created at this stage.
This is to be done as follows:
In the change mode of the order, there would be an icon on the Application bar
The Technical completion also means the relevant job actual entries are completed. The
system also prompts for “Check” the completion of the notification. Once this is done no
further changes are allowed either in Notification or the Order. Hence the Technical
completion is to be done on completion of all the data required be maintained.
On performing the above step, the system status in the order will be shown as ‘TECO’
In the above steps the order creation for planning, entry of actual data, and rule for cost
settlement is done. Now in this step the Actual Order costs are to be settled to a cost center.
Menu Path: Logistics – Plant Maintenance – Maintenance processing – Environment – Order
settlement – Single (KO88)
A test run can be done with the tick mark on which comes by default. This will indicate,
errors if any, during settlement. Then run the same by removing the tick mark for actual
settlement when there are no errors in test run.
Once the above operation is done, the Order is ready for closing. Following step ensures
the same.
The system displays a screen requesting some fields for the selection criteria on entering
the data in the relevant fields, and then execute the list display appears. The system
shows the list with standard fields. User can set the fields of the choice for display, as is
Menu Path: Logistics – Plant maintenance – Maintenance processing – Orders – Change (IW32)
In the order change mode, one can put short description as “Skipped” with a reason in the
short description. Further explanations can be maintained in the Long text available next to
the Short text. Then further follow the path in the same screen as:
For any reason an order to be rescheduled, the same can be done as follow:
Menu Path: Logistics – Plant maintenance – Maintenance processing – Orders – Change – Functions –
Scheduling
Also the Basic start and end dates can be modified in the Order itself and saved. However
Re-scheduling of the order is considered as an open order by the system for PM schedule
generation. Hence if the same activity is due, an order will not be generated unless the
previous activity is closed.
In case of any Order created and to be scheduled to a Turnaround, then the field ‘Revision’
is to be used for the same.
Usually the ‘Revision’ numbers are to be created by a central agency based on the decision
for the annual shut down dates. This number will be available in the pull down help. If
separate identity is to be given for Shutdown jobs and Turnaround jobs, different Revision
numbers will be created.
Once the order is assigned to a ‘Revision’ number, the Basic start and End dates will be
automatically taken same as the “Revision” dates. This will help in keeping the
reservations effective during those dates. Exact start and end dates can be modified when
required.
In case the Revision dates themselves are modified, eg, Turnaround in May is postponed to
August, then the Revision dates will be modified by the central Agency. This will not
automatically reschedule the dates in the individual maintenance orders. For such cases,
following method is to be followed.
Menu Path: Logistics – Plant Maintenance – Maintenance processing – Orders – List Editing –
Change(IW38)
While giving the options in the List editing, “Revision” field must be entered along with
the concerned planner groups and then execute.
In case the Orders are to be accounted separately against ‘Revision’, a detailed structure
will be created by the Central Planning cell and will be available at the Pull down help. The
correct WBS (Work Breakdown Structure) element is to be entered in the field available on
clicking ‘Additional data’ in the Order screen.
In the above screen the list of orders are displayed select the order and click on details.
The Plant Maintenance Information System is available for the overall analysis for the
Planner group, Object damages, Equipment and other cost analysis.
The Planner group analysis gives the analysis on number of notifications generated against
that planner group, Orders generated, costs incurred, etc