PM Maintenance Notifications
`
`The following Help Topics are available:
`
`
`
`
`
`..... ~ ..........~ .................~ ..................................~..~ ........~ .......
`
`
`
`
`
`For Help on Help, Press F1
`Version
`
`SAP-00005773
`
`

`
`Version
`Prepared for R/3 Release 2.2.
`August 1994
`
`SAP-00005774
`
`

`
`Copyrights
`
`@1994 SAP AG. All rights reserved.
`Neither this documentation nor any part of it may be copied or reproduced in any form or by any
`means or translated into another language, without the prior consent of SAP AG.
`
`SAP-00005775
`
`

`
`Maintenance Processing in the PM System
`
`This section provides an overview of the processing of unplanned maintenance tasks in the PM
`System. It describes the steps that can be carried out when creating, planning, executing,
`controlling and analyzing these tasks, in order to make effective use of the system functionality.
`Ixlt ~.od.u~.tJ..o.r]..to..M aJ.r~texxaxx~.e..P.~.o.~.~.s.s.mg
`
`SAP-00005776
`
`

`
`Introduction to Maintenance Processing
`
`Introduction
`
`The PM System supports the planning, processing and completion of maintenance tasks for the
`entire plant maintenance area. It provides a step-by-step explanation of the plant maintenance
`processes, thereby providing the basis for rational decision-making as regards cost-intensive
`installations, replacement investments and changes in maintenance strategies. It distributes
`up-to-date information on a regular basis to all the departments concerned.
`The PM System supports the creation, planning, control and analysis of all the tasks which need to
`be carried out in maintenance areas. These include not only unplanned tasks or those caused by
`malfunction, but also maintenance and inspection tasks which are planned on a regular basis.
`Furthermore, the PM System can also map functions such as investments, reconstructions,
`retooling, which although they do not belong to plant maintenance itself, need to be processed
`using the same procedures.
`
`Range of Functions
`
`Maintenance processing in the PM System comprises several steps, which, however, do not
`necessarily all need to be performed in full. On the one hand, the wide range of functions available
`enables you to process a large-scale repair with numerous planning steps such as preliminary
`costing, work scheduling, staging, dispatching and permits. On the other hand, the flexibilty of the
`system alows you to react immediately in cases of damage and create the necessary orders and
`shop papers with a minimum number of entries in a short space of time.
`
`SAP-00005777
`
`

`
`Maintenance Processing for Unplanned Tasks
`
`The PM System enables each company to determine its maintenance process flow according to its
`individual requirements.
`
`Areas of Processing
`
`Maintenance processing for unplanned tasks can be divided into the following major areas:
`description of object condition
`The main element in this area is the maintenance notification. It is used to describe the condition
`of a technical object or to enter a malfunction at a technical object and request the repair of the
`damage.
`execution of the maintenance tasks
`The main element in this area is the maintenance order. It is used to plan the execution of
`maintenance tasks in detail, to trace the progress of the work and to calculate the costs for the
`maintenance tasks.
`completion of the maintenance tasks
`The main element in this area is the maintenance history. It is used to store the most important
`maintenance data long term. This data can be called up at any time for evaluation purposes.
`
`¯
`
`The Main Processing Steps
`
`Processing unplanned maintenance tasks in the PM System can be divided into the following steps:
`1. reporting a malfunction or a defect in a system or part thereof, in other words describing the
`condition of the system
`2. requesting a maintenance task
`3. creating a maintenance order and planning the task
`4. releasing the maintenance order
`5. executing the order
`6. completing the task and confirming completion of the order
`7. entering technical information such as findings, cause and downtimes, activities
`8. completing the order and the PM notification, storing the relevant data for evaluations and for
`planning future maintenance activities
`The organization of your company, and in particular of your maintenance department, determines
`which employees perform these steps in which areas, and the amount of detail in which the data for
`the individual steps needs to be entered. For example, one company may plan a task in great
`detail, while another company will only plan a rough outline for the same task.
`The following diagram provides an overview of the major steps in maintenance processing for
`unplanned tasks:
`
`SAP-00005778
`
`

`
`PM Workshop
`
`~iecuti°n
`
`terial issue
`curing PRTs
`rksXeps
`
`Releasing the
`
`order®
`
`Completion
`
`etlon
`
`t~O confirmation
`I
`
`PM Plannin~l
`
`Createthe order
`Planningthetask
`-who
`-when, forhowlong
`-whatsteps
`
`- resouross
`
`Technical info n-nation
`- breakdown
`- causes
`-objectsaffected
`-activities
`
`®P
`
`M History
`
`Requestinga
`
`task®
`
`Plant
`Malfunction, error
`Request
`Activity
`
`PM Noti ficati on I
`I
`- what
`-when
`-where
`-technical
`information
`- breakdown
`
`Steps 1,2, 7 and 8 refer to the maintenance notification and are therefore described in this. The
`other steps refer to the maintenance order and are described in PM Maintenance Orders. At the
`end of this manual, there is a short description of the connection between maintenance notifications
`and maintenance orders.
`Regular maintenance tasks are described in detail in the manual PM Maintenance Planning.
`
`SAP-00005779
`
`

`
`Description of Maintenance Notifications
`
`This section tells you what a maintenance notification is and what it is used for in the PM System.
`
`SAP-00005780
`
`

`
`Definition
`
`What is a Maintenance Notification?
`
`A maintenance notification, PM notification for short, is used to
`¯ describe the condition of a technical object in the PM System
`¯
`refer the maintenance department to a task that needs to be carried out
`¯ document the tasks that are carried out
`
`What Types of Maintenance Notification Exist?
`
`There are three types of PM 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 a
`system has reduced or zero performance, or that its output is of a reduced quality.
`As a rule, a malfunction report requires the maintenance department to arrange for a specific repair
`task to be carried out, for the ideal condition of the object to be restored (according to DIN Norm
`31051).
`A special case of malfunction report is when a machine operator determines a malfunction,
`immediately repairs it and subsequently documents the malfunction that occurred, its effect and the
`way in which it was rectified. In this case, the PM notification is only entered after completion of the
`maintenance task as a completion confirmation.
`
`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 records which activities were carried out when, at what time and with what results.
`For this reason, the activity report is the central place for storing data from a completed
`maintenance order. Whenever a maintenance order is confirmed as completed, any data that is
`important for later evaluations is automatically saved in an activity report.
`A typical activity report is the inspection findings, because it describes the results of an inspection
`carried out to test the actual condition of the object (according to DIN Norm 31051). The inspection
`measure was not requested specially using a malfunction report. In most cases, it is based upon an
`inspection order.
`Another typical activity report is the maintenance findings. This documents the technical values of
`the object determined during and/or after regular maintenance work. These maintenance jobs are
`carried out in order to maintain the ideal condition of the object (according to DIN Norm 31051) and
`always result from maintenance plans.
`Typical examples of the activities documented in activity reports are "Fill up oil" or "Check pressure"
`or "Tighten screws".
`
`SAP-00005781
`
`

`
`Maintenance Request
`
`A maintenance request is a targeted instruction to Plant Maintenance, to carry out an activity as
`described. The decisive factor in this case is that there is no malfunction.
`Maintenance requests are typically used for investments, for example if an employee requires a
`new monitor, or if all the telephones in one part of the building in a company need replacing.
`
`For which Objects can Maintenance Notifications be Created?
`
`All the types of PM notification described can be created both for a functional location and for a
`piece of equipment, with or without an assembly. The hierarchy of these objects is in the order
`listed; in other words, if you create a PM notification for an assembly of a piece of equipment and
`the equipment is allocated to a functional location, the system copies all the relevant data
`pertaining to the equipment and the functional location.
`However, it is also possible to create PM notifications without entering an object. This is the case,
`for example, when a malfunction report refers to an object that is not managed with a number in the
`system, or when a maintenance request refers to an object that is to be set up as part of an
`investment.
`Note
`This guide only describes malfunction reports, activity reports and maintenance requests as used in
`unplanned maintenance.
`
`SAP-00005782
`
`

`
`Configuration
`
`What are the Components of a Maintenance Notification?
`
`A PM notification comprises the following components:
`¯ header data
`¯
`location and account assignment data
`¯
`item data
`¯ task data
`¯ breakdown and system availability data
`¯
`schedule overview
`
`What are the Individual Components Used for?
`
`The individual components contain data that belongs together. Each group of data is contained in a
`separate screen:
`
`Header Data
`
`Each PM notification contains header data. Header data is information which is used in identifying
`and managing the maintenance notification. It is valid for the whole notification. It comprises:
`¯ number, description and type of notification
`¯ desired dates by which the necessary tasks should be completed, and time at which the
`malfunction described began.
`¯ management data: the person(s) who created and who last changed the notification, date of
`entry and last change, name of person making the request, time of entering the request
`¯
`reference object: functional location and/or equipment, to which the PM notification refers
`¯ maintenance planning group reponsible for carrying out the job
`¯
`status of maintenance notification, which provides information on the stage of processing which
`the notification has reached
`
`Location and Account Assignment Data
`
`The location and account assignment data is copied from the master record of the reference object
`and is also valid for the whole PM notification. The location data provides information regarding the
`physical location within the company at which the functional location or equipment is situated. The
`account assignment data provides information as to whom the maintenance costs are normally to
`be debited.
`
`Item Data
`
`An item in a maintenance notification describes damage or a malfunction in greater detail and
`provides information on which activities were carried out at the reference object of the notification.
`A maintenance notification can have several items. Each item contains the following data:
`¯
`short description of the malfunction arising (malfunction report) or the activity carried out (activity
`report), or the action to be carried out (maintenance request)
`
`SAP-00005783
`
`

`
`¯ exact component at a functional location, piece of equipment or in the assembly where the
`malfunction has occurred or where the activity has been performed
`key for the malfunction and its cause
`¯
`short description of the cause
`¯
`¯
`classification of the malfunction
`key and short description of the activities performed
`¯
`There is an item list which displays several items on each screen page with the most important item
`data plus an item detail screen for each item, which contains the more detailed entries.
`
`Task Data
`
`The task data describes the tasks which need to be carried out. In a malfunction report, this refers
`to the tasks needed to repair the damage or to prevent it from occurring in the future; in a
`maintenance request it refers to the activities requested for some other reason. You can enter the
`following for each individual task to be carried out:
`¯
`key for the task to be carried out
`¯ notes on the catalog on which it is based and the resulting key
`¯
`short, precise work instructions
`¯ planned start and end of the task
`¯ adminstrative data: name of person(s) who created and last changed the task, date of creation
`and of last change
`There is a task list which displays several tasks on each screen page with the text and the key and
`a detail screen for each task which contains additional entries.
`
`Breakdown and System Availability Data
`
`The availability data describes the system breakdown and system availability determined before,
`during and after the malfunction. You can enter the following information here:
`¯
`start, end and duration of the malfunction
`¯
`key for indicating whether the malfunction led to the reference object breaking down
`¯ effect of the malfunction on other parts of the system
`¯ availability and condition of the system before and after the malfunction occurred
`¯ availability and condition of the system after the malfunction was repaired
`
`Schedule Overview
`
`The schedule overview displays all the dates that have been stored for the PM notification up to the
`current date on one screen. These comprise:
`¯ date and time the notification was entered
`¯ date and time for start and end of the malfunction
`¯ date and time for the desired start and end of the activity
`¯ date of the technical inspection and completion of the notification, plus reference date for the
`maintenance history.
`
`SAP-00005784
`
`

`
`Creating a Maintenance Notification
`
`This section explains how to create maintenance notifications in the system. Since each company
`determines individually who can enter which data at what time, the procedures described below
`may vary in some respects from your own.
`Example:
`In some companies, the employees in Production enter the malfunction reports directly into the
`system. The employee in Plant Maintenance is the first person to give the instruction for removing
`the malfunction, which he does by changing the previously entered notification.
`In other companies, the malfunctions are normally reported by telephone to the maintenance
`department. The employee in Plant Maintenance who creates the notifications in the system has
`sufficient knowledge of the task at hand to be able to enter the job instructions necessary for
`repairing the malfunction at the same time.
`The standard version of the PM System offers a direct entry function for each of the three standard
`types of maintenance notification. Furthermore, there is an extra entry function for any other types
`of notification that might be used in your company.
`It contains the following topics:
`,.8 .c..op.e...o.f.. Entr.~
`
`.¢ma.t mg.ao.A~.tbdt~.o.A
`,.CJ’.e.a_t i~9.a.M ai~te n.aJ&c.e..Re.q~ue.s.t
`,.CJ’.e.a_t i~9.a..Us.e r-.8#e.cifJ c..Maint .e n a [lc..e.No.t #it.at [o.n
`
`SAP-00005785
`
`

`
`Scope of Entry
`
`Scope of Entry of a Malfunction Report
`
`The first topic in this section describes how to create a malfunction report. Here we have assumed
`that only the malfunction or damage is entered in step one, in other words, that the PM notification
`is created using only malfunction-related data. The data that refers to repairing the malfunction and
`to technical findings is entered in the system in step two, that is, as a change to the PM notification.
`How to make these changes is described in the following section, Chan~..a M..aj.nteo.ance
`Notification.
`
`Scope of Entry of an Activity Report
`
`The second topic in this section describes how to create an activity report. The activity report
`documents the actual condition of a maintenance object, usually determined during an inspection,
`together with the activities carried out in connection with this. It differs from a malfunction report in
`that no concrete malfunction exists as a trigger, which means that you do not have to describe the
`malfunction, but instead simply the activities that have been carried out. For this reason, the header
`data screen of an activity report is configured somewhat differently to that of the malfunction report.
`
`Scope of Entry of a Maintenance Request
`
`The third topic in this section describes how to create a maintenance request. You use the
`maintenance request to ask the maintenance department to carry out a particular activity. However,
`there is no malfunction or damage. All that is initially important in the maintenance request is the
`measures requested. The data relating to the execution of the tasks is only entered in the system in
`step two, in other words by changing the maintenance notification. How to make these changes is
`described in the following section, .C__h_a__n_~ a Maintenance Notification.
`
`Scope of Entry of a User-Specific Maintenance Notification
`
`The fourth and last topic in this section describes how to create a different type of maintenance
`notification from the standard ones mentioned above. This is the case if your company uses
`individual maintenance notification types, because for instance particular notifications are to be
`evaluated separately. If you want to create one of these notifications, you need to use the general
`create function, which contains a field where you can enter the notification type.
`Note
`You can of course also use the general create function for the standard notification types. However,
`this requires more online processing than when using the special functions.
`
`SAP-00005786
`
`

`
`KCreating a Malfunction Report
`
`When you create a malfunction report, you should provide as much information as possible
`regarding the malfunction to Maintenance Planning. Enter as much of the following as you can:
`¯ which malfunction has occurred
`¯ where the malfunction has occurred
`¯ what effect it has
`¯ who is reporting it
`¯ what further damage has been caused
`The following sections describe how to enter this information in the PM System.
`
`Selecting a Malfunction Report
`
`Proceed as follows to select the initial screen for the malfunction report:
`
`1. Select Logistics--> Plant maintenance -~ PM processing
`You obtain the screen PM Processing.
`
`2. In this screen, select Notifications -~ Create (special)
`-~ Malfunction report
`
`You see the screen Create PM Notification: Malfunction Report. This is the header data screen
`for the malfunction report.
`
`Describing a Malfunction
`
`.
`2.
`
`.
`
`.
`
`First describe which malfunction or damage has occurred:
`In the first block, enter which malfunction has occurred.
`If the line intended for description is not long enough, select the SAP word processing function
`with Goto --~ Notification --~ Long text and enter a long text there.
`In the second block, enter the start of the malfunction. The system enters the current date and
`time as a default, but you can overwrite these entries. If the maintenance notification is to be
`treated with a particular priority, then enter this here.
`In the third block, enter the object at which the malfunction has occurred, that is, the functional
`location and/or the equipment and/or the assembly in the appropriate field. You can find the
`names of these objects using the match code.
`If you cannot enter a reference object, read the section ~.ec;.ia.!..(~s.e.;..(~[f~.atj.r~q..a..M.a]fu.rl.c;t.i.Q.n..
`~ort w]~bou~ a F~eterence Object below.
`You can also display the structure of the functional location or piece of equipment named and
`select the relevant object from there.
`To do this, select Details -~ Reference object -~ Structure list or Details --~ Reference
`object --~ Structure graphic.
`Select the assembly. The system then automatically copies the superior structure levels into the
`maintenance notification as well.
`Caution
`In the field "Assembly" you can only enter an assembly which is contained in the equipment bill of
`
`SAP-00005787
`
`

`
`material. If you enter another assembly, you will obtain an error message.
`
`Describing a Breakdown
`
`If the malfunction has resulted in the machine breaking down, you can record the breakdown in one
`of the following two places:
`¯
`in the field Breakdown
`¯
`in the screen Create PM Notification: Malfunction, Breakdown, which you access by means of
`Goto --~ Malfunction, Breakdn
`As a rule it should be sufficient if you enter the start of malfunction in the header data screen and
`flag the Breakdown field. This indicates that the system broke down at the time specified. The
`breakdown data screen is primarily relevant for the end of the breakdown and the length of
`downtime.
`
`Describing System Availability and Effects
`
`If you want to enter information regarding the availability of the system before and after the
`malfunction, and/or you want to indicate which other parts of the system have been affected by the
`malfunction at the reference object, proceed as follows:
`
`1. Call up the screen for the availability data with Goto --~ System availability.
`2. Describe the condition and availability of the system, following the instructions in the online
`documentation.
`
`Entering the Person who Reported the Malfunction
`
`If the malfunction report was reported to you by another person, you can enter this person in the
`system as follows.
`
`1. Select Details -~ Reported by
`You obtain the pop-up window Reported by.
`2. Enter the name of the person reporting the notification and the time the report was made. Then
`press Continue to return to the previous screen.
`
`Entering an Item
`
`In the last block of the header data screen, the item block, enter the damage as accurately as
`possible. If there are several cases of damage, describe each one in a separate item.
`
`.
`
`Enter the data for the first damage in the relevant fields, following the instructions in the online
`documentation.
`2. If the line intended for description is not long enough, select the SAP word processing function
`with Goto -~ Item --~ Item long text and enter a long text there.
`3. If required, enter the object component or assembly at which the activity was carried out,
`following the instructions in the online documentation.
`
`Entering a New Item
`
`If you want to describe further damages, you need to create a new item for each damage:
`
`1. For each new item select Edit --~ New lines -~ Item.
`
`SAP-00005788
`
`

`
`The item counter on the right-hand side of the screen increases by one each time. In this way
`you can always tell which item is displayed.
`2. Enter the data for the remaining items.
`Example:
`In the header data of the maintenance notification, the malfunction is described as "Pump has
`reduced performance". This is divided into two items, as follows: "Outlet supports leaking" and
`"Oil leak at starter motor".
`If you have created several items, you can call up the various items by means of the item list.
`
`Calling up the Item List
`
`To display several items in a screen, call up the item list with Goto --~ Item --> Overview.
`You can also enter further items in the item list in the same way as described above.
`
`Saving
`
`Save the maintenance notification with Notification --~ Save.
`
`SAP-00005789
`
`

`
`Special Case: Creating a Malfunction Report Without a
`Reference Object
`
`It may be the case that the person who entered a malfunction report is unable to enter the
`reference object, for example because the malfunction affects a part of the building that is not
`managed under an object number, or because the malfunction occurred at a small system, for
`example a telephone, which is not managed as a piece of equipment.
`If you cannot name a reference object, leave the appropriate fields in the malfunction report empty.
`Instead, enter the location data as accurately as possible in the appropriate screen.
`The maintenance planner processes the malfunction report, in other words changes it (see the
`section ~a~=n~.!~.g~a~M~a~[f~u~n~c~tj~n~R~e~.D~a~t~a~)~ entering a reference object if possible. The system
`then automatically copies the location data, overwriting the location data entered originally.
`
`SAP-00005790
`
`

`
`Special Case: Creating a Malfunction Report After Removing
`the Malfunction
`Often you will need to use a combination of the functions "Create malfunction report" and "Change
`malfunction report", for example when the person using a piece of equipment determines a
`malfunction, repairs the malfunction by means of a particular maintenance task and only then
`reports what he or she has done. In this case you create a malfunction report, because it is a
`question of damage to the machine, but at the same time you enter all the activities that you carried
`out in order to repair the malfunction (see the section .~.h..a..n..gj.n.~g..a...M...a.!.f.u..n...c.tj..Q..n.....R..e.p.~=D.#t..a..).
`
`SAP-00005791
`
`

`
`Creating an Activity Report
`
`When you create an activity report, you will already have carried out an activity, which you now
`want to document by means of the activity report. You should therefore enter as much of the
`following information as you know:
`¯ which activity you have carried out
`¯ where you carried out the activity
`¯ what effects it may have (had)
`¯ what was its scope
`The following sections describe how to enter this information in the PM System.
`
`Selecting an Activity Report
`
`Proceed as follows to select the initial screen for the activity report:
`
`In the PM Processing screen, select Notifications --> Create (special)
`--> Activity report
`You obtain the screen Create PM Notification: Activity Report.
`
`Describing an Activity
`
`.
`2.
`
`.
`
`.
`
`First enter a short and fairly general description of the activity you have carried out:
`In the first block, enter the activity you have performed.
`If the line intended for the description is not enough, select the SAP word processing function
`with Goto --~ Notification --~ Long text, where you can enter a long text.
`The system proposes the name of the person making the entry with the time and date of entry
`as default values. If these entries are incorrect, you can overwrite them with the required values.
`In the second block, enter the object at which the activity was carried out. Enter the relevant
`functional location and/or the equipment and/or the assembly in the corresponding field. You
`can find the numbers of these objects using the matchcode.
`If you cannot enter a reference object, plase refer to the section~.e£ia.!..Cas.e.;..C[~a.ti.[!~
`.lY].a.!fu. D.~;~i Q D...I~ ~p Q r~. Y~j~ b.Q u~..a..l~.e~f~.r.e.n.c e...O.bj.e.c[ .. above.
`You can also display the structure of the functional location or equipment entered and search for
`the relevant object from that.
`To do this, select Details --> Reference object --> Structure list or Details --~ Reference
`object --> Structure graphic.
`Select the assembly. The system then automatically copies the superior structure levels into the
`PM notification as well.
`Caution
`You can only enter an assembly in the "Assembly" field which is conbtained in the equipment bill of
`material. If you enter a different assembly you will receive an error message.
`
`Entering Downtimes
`
`If carrying out the activity has led to the object or system breaking down, you can report this as
`follows:
`
`SAP-00005792
`
`

`
`1. Select Goto -~ Malfunction, Breakdn.
`You obtain the screen Create PM Notification: Malfunction, Breakdown.
`2. Enter the data, following the instructions in the online documentation.
`3. To return to the screen Create PM Notification: Activity Report, select the Notification button.
`
`Describing System Availability and System Condition
`
`If you want to record the availability and condition of the system before and after the activity,
`proceed as follows:
`
`1. Select Goto -~ System availability.
`You obtain the screen Create PM Notification: System Availability.
`2. Make all the necessary entries, following the instructions in the online documentation as
`necessary.
`3. To return to the screen Create PM Notification: Activity Report, select the Notification button.
`
`Entering an Item
`
`In the third block, for the item, describe the scope of the activity, for example "Oil changed" or
`"Pressure checked". Proceed as follows:
`1. Enter a brief, precise description of the first step of the activity you have carried out (for example
`"Oil changed").
`2. If the line intended for the description is not long enough, select the SAP word processing
`function with Goto --> Item --> Item long text to enter a long text.
`3. If necessary, enter the object part or assembly at which the activity was carried out, following
`the instructions in the online documentation.
`4. Then enter all the activities that were carried out in detail in the list at the bottom of the screen,
`for example "Oil level measured" and "Oil refilled". Follow the instructions in the online
`documentation.
`
`5. If you need extra lines, add these on using the menu Edit--~ Newlines -->Activity.
`
`Entering a New Item
`
`If you want to enter further items for additional activities, proceed as follows:
`
`1. For each new item, select Edit -> New lines -> Item.
`This increases the item counter on the right side of the screen by one, which means you can
`always see which item is displayed.
`2. Enter the data for the additional items. An additional item might for example be "Pressure
`checked".
`If you have entered several items, you can call them up using the item list.
`
`Calling up the Item List
`
`To view several items in a screen, call up the item list with the function Goto -> Item -> Overview.
`You can enter several items in the item list, as described above.
`
`Classifying an Activity Report
`
`SAP-00005793
`
`

`
`If you usually classify activity reports within your company, you need to enter the class in the item
`detail screen. Proceed as follows:
`
`1. Select the item detail screen with Goto --> Item --> Detail. You obtain the screen Create PM
`Notification: Item Detail.
`2. Classify the notification by entering the name of the relevant class in the field Error class.
`If you do not know it, you can search for it in two ways:
`with the F4 help button and the matchcodes
`
`with the menu Goto -~ Item --> Find class
`Select the appropriate error class.
`
`Saving/Completing
`
`If the activity report is only to be saved but not yet completed, select Notification --> Save.
`If the activity report is to be completed directly, that is, transferred to the maintenance history,
`select Notification --> Functions --> Complete (see the section C.Q.m.~..a..Maj.nt.e.r~.a.n£e..
`
`As a rule you will complete an activity report directly, since the work is carried out in full, and only
`reported in retrospect. It is therefore unusual to have to make any changes.
`
`SAP-00005794
`
`

`
`Creating a Maintenance Request
`When entering a maintenance request you should provide as much information as possible for
`Maintenance Planning regarding the activities you want the maintenance department to carry out
`for you. Enter the following information in as much detail as possible:
`¯ what is being requested
`¯ the object or area to which the request refers
`¯ who requested the activity
`
`Selecting a Maintenance Request
`
`To select the initial screen for the maintenance request, proceed as follows:
`1. Select Logistics --~ Plant maintenance -~ PM processing.
`You obtain the screen PM Processing.
`
`2. In this screen, select Notifications --~ Create (special)
`-~ PM request.
`
`You obtain the screen Create PM Notification: PM Request.
`
`Describing a Maintenance Request
`
`.
`2.
`
`.
`
`.
`
`First describe what you are requesting:
`In the first block enter which activity you are requesting of the maintenance department.
`If the line intended for the description is not long enough, select the SAP word processing
`function with Goto -~ Notification -~ Long text, where you can enter a long text.
`In the second block, enter the time at which the activity requested is to be carried out. You can
`overwrite the entries proposed by the system. If the maintenance request is to be treated with a
`particular priority, then enter this.
`If your maintenance request refers to a particular object, enter this in the third block. Enter the
`functional location and/or the equipment and/or the assembly in the appropriate field. You can
`search for the objects using the matchcode.
`If you cann