Sie sind auf Seite 1von 39

Module 4.

SAP Plant Maintenance


Notification Overview

Version: V1.0

Date: 24/04/2013

Course Content
To go directly to a particular section, click
on
hyperlink
1. Notification
Definition
Notification Type
Notification Process Flow
Menu Path for Create, Change and Display
Notification
2. Display Notification
3. Notification Action Log
4. Notification Status
5. Display Notification List
List Display using ZiW29
List Editing using ZiW28
6. Notification Print
2

Notification

Back to Table of Contents


3

Notification: Definition
What is a Notification?
A formal request, to execute task(s) such as
repairing, modifying or improving an equipment.
A Notification can also be used to record
maintenance activities/history or to manage
inspection requests.

Notification: Type
There are 4 types of notification. The
Notification type determines the content and
the N1
usage
of the
notification.
Work
Request
(maintenance or corrective)
To request the execution of works
N2 Inspection Report (Notification created via
Meridium)
Work associated with Inspection dept.
N3 Activity Report
To document history or tasks (where no
N1 exists)
N4 Notification Other Departments
Example: Operation department Routines
5

Notification and Work Order:


Process Flow

Operations
Maintenance
Coordinator

Maintenance
leader

End Job

Close Job

Planner

Scheduling

Area
Maintenance
Supervisor

Record
Labour hours

NO
Create
Notification

Accept
Job?
DAILY MEETING - Agree Finish Date
Approve
Job
Request

Create
Work
Order

Execute
Jobs

Plan
Work
Order

Approve
Planning

Schedule
Daily
Jobs

WEEKLY SCHEDULING MEETING


Produce
Weekly
Schedule

Notification: Menu Path


Use the following transaction path to create,
change and display a Maintenance Notification:
Transaction ZIW21 is used for the creation of N1
notifications.
Menu SAP
Logistics
Plant maintenance
Maintenance processing
Notification
IW21 Create (General) *
IW22 Change
IW23 Display
ZIW21 - Fast entry for notification type N1
* Not for General use.

Notification: Create
Essential points when creating notification:
It is imperative that the correct Functional Location
(TAG) is used as this increases the efficiency of the
maintenance process and ensures correct history
and cost allocation.
Whenever possible we are always looking to capture
costs and history at the Tag level to provide accurate
data for reliability and cost feasibility studies.
A notification should ONLY be created against a 5th
level Functional Location.

Display Notification

Back to Table of Contents


9

Notification: Display
Use transaction iW23 to display a
Notification.

Enter Notification Number

Symptom text
provided while
creating the
notification using
transaction ZiW21

Functional Location populated based on


Tag Number entered while creating the
notification using transaction ZiW21
Detail of problem provided while creating
the notification using transaction ZiW21

Symptom code provided while creating


the notification using transaction ZiW21
10

Notification: Display
Click to go back to Display
Notification Initial Screen

Planner Group and Main Work Center


fields will be inherited from Technical
Object
Badge # provided
while creating the
notification using
transaction ZiW21

11

Notification: Action log


Action log shows changes made to a
notification
!!
It can be accessed
by clicking button
Transaction
iW23

Note:
The action log can also be
viewed in iW22 (Change
Notification)

Tip!
Youll find the creators
ID here as well.
Back to Table of Contents

12

Notification: Status
The Status indicates the phase of life cycle of the
notification.
Transaction
iW23
To access the Status, click on the information button.
User status

There are 2 status types:


System status
User statuses
System Status:
The System Status is set
automatically during the
different phases of the
notification.
Back
to Table of Contents

System
status

13

Notification status
User Status:
Some user statuses are set automatically and
some are set manually.
To set a status manually the user sets/ticks the
suitable status.
The User Status can be divided
into:
Status with status number
Never set the APPR
status manually as it is
set automatically after
Notification is Put in
process (System Status:
NOPR)

(Only one status can be set at a time)


These user statuses are normally set
automatically by the system.

Status without status number


(More than one status check box can be
ticked at the same time)
The majority of these user statuses are normally
set manually by the user.
14

Notification: System Status


Main system statuses:
OSNO

Outstanding notification

NOPR

Notification in process

NOPO

Notification postponed

NOPT

Notification printed

ORAS

Order assigned

NOCO

Notification completed

DLFL

Deletion Flag

15

Notification: User Status

User statuses to be put manually:


TERE
Technical report to make
TAOU
Turnaround - Out of scope
TAIN
Turnaround - In scope
TAWA
Turnaround - To be scoped
TEDO
Technical report done
INF
Inform Originator on Completion
Automatic user statuses:
AWAP
Released
APPR
CET

Awaiting Approval
Notification created and not Approved/
Approved
Notification Approved/Released
Critical Equipment Team
If it is identified as Critical Equipment in

16

PM Notification: Process
Overview
Requestor

Approver
APPR
APPR

Creation of an
N1 notification
AWAP
AWAP

Maintenance
NOPR
NOPR

Work order
assignment

Turn
Around
to be
scoped?

Analysis of
notification

OSNO
OSNO

ORAS
ORAS

Turn
Around in
scope?

Yes
TAWA
TAWA
TAOU
TAOU

No
Works carried
Out (Normal)

TAWA
TAWA

Yes

No

Works carried
Out (TA)

TAWA
TAWA
TAIN
TAIN

Rejected
Work order
closure

Technical report
to be drawn up
TERE
TERE

Technical report
finished

Deletion set on
notification
DLFL
DLFL

TEDO
TEDO

NOCO
NOCO

Notification
closure
NOCO
NOCO

TERE
TERE

Approval of
technical report
TEDO
TEDO

TERE
TERE

17

Display Notification List

Back to Table of Contents


18

Notification lists
Use the following transaction codes to get the List
Maintenance Notifications:
ZIW28 List Editing: Change
ZIW29 List Editing: Display

ZIW28 and ZIW29 have identical search/display


screens and also have the same functionality.
The only difference is that ZIW28 allows you to
make changes to a notification, and ZIW29 only
allows you to display it.
Separate presentations cover the functionality of
ZIW28 and ZIW29 in detail.

19

Notification: List Display


Transaction
ZiW28/ZiW29
Get Variant

The notification search


screen contains many
fields so creating a search
that
will
return
the
required results is very
complex.
To help, a comprehensive
set of searches have been
created/ saved and these
should meet all your
search requirements.
These saved searches are
called variants and can be
ZIW28/29
have onan
retrieved by clicking
identical
set of variants.
the Get Variant
Icon.
20

Notification: List Display

Maintain
search value

A81 corresponds to Area 8 ISBL


A82 corresponds to Area 8 OSBL

Execute

Choose

Choose the Variant


as per the
requirement

21

Notification: List Display


After the variant has been selected ( example: AA-A8100 Display newly created N1 notifications for Area
8) the associated search parameters will be
automatically passed to the selection
screen.
Transaction
Execute

ZiW28/29

22

Notification: List Display


To view the details of Notification(s), select the
row(s) and click on Notification button.

Click to go back to
Display follow up
Notifications screen

23

Notification Print

Back to Table of Contents


24

Notification: Print
The Output device LP01 must be entered in your user
profile, before printing within SAP.
Note: This is a one time activity. Once it is maintained and saved, it is
not required to perform this action again.

Select Own Data using the below menu path or transaction SU3.
Save the changes
Select the
Defaults tab

Tick Output
Immediately
Check box

Maintain Output
Device as LP01
25

Notification: Print
Transaction
ZiW28/ZiW29
Get Variant

The notification search


screen contains many
fields so creating a search
that
will
return
the
required results is very
complex.
A comprehensive set of
search
have
been
created/
saved
which
should meet all your
search requirements.
These saved searches are
called variants and can be
ZIW28/29
have onan
retrieved by clicking
identical
set of variants.
the Get Variant
Icon.
26

Notification: Print
After the variant has been selected the
associated
search
parameters
will
be
automatically passed to the selection screen.
Execute

Transaction
ZiW28/29

27

Notification (1)
There are 3 methods to select notifications and
these can be combined if required.
Method 1:
All notifications within the display table can be selected
by clicking on the
icon.

Selected rows will be highlighted in yellow

If the

icon is clicked again all rows will be

28

Notification (2)
Method 2:

To select a range of notifications, left mouse


click on the Select
icon to the left of the
line, then drag down.
Release the left mouse button when all the
required notifications have been selected.

29

Notification (3)
To select multiple individual notifications,
press and hold down the keyboard control key
, then left mouse click on the Icon
adjacent to the required notifications.

30

Notification: Print Display Table


To print the display table click on the

icon

The printed report shows the list of notifications


in the display table.

31

Notification: Print With Long Text


Select the required notifications then click on the
macro button.

The printed report shows notifications details and


long text.

32

Notification: Print Export To Excel


The display table can be exported to an excel
spreadsheet by following the steps below.
1
Export
to
Excel

2
3
4

Use Save
As
command
to save the
file

33

Notification: Print Open A Notification


To open a single notification double click on
its number.

To open multiple notifications, firstly select the


notifications required then click on the
macro button.

34

Notification: Print
It is possible to print individual Notifications from
transaction iW22 (either using this transaction
directly, or accessing the notification via ZIW28
list display).
Transaction
iW22

Shop paper 8010 will be useful for Operations

35

Notification: Print
Click to go
back

Print
Preview of
shop paper
8010

36

Notification: Print
Shop paper 8020 provides the Notification Header details

Click to go
back

Print
Preview of
shop paper
8020

37

Notification: Print
Shop paper 8030 is
useful for Maintenance

Click to go
back

Print
Preview of
shop paper
8030

38

39

Das könnte Ihnen auch gefallen