Module 4.

SAP Plant Maintenance

Create N1 Notification

Version: V1.0

Date: 24/02/2013

Course Content
To go directly to a particular section click on the
hyperlink
1. Notification
Definition
Notification Type
Notification Process Flow
2. Create N1 Notification
3. Display Notification
4. Display Notification List

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
theN1
usage
of Request
the notification.
Work
(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
e.g. Operation department Routines

Notification and Work Order:

Process
Flow
This course only deals
with the first
part of the
Maintenance
notification
process.Planner
leader

Operations
Maintenance
Coordinator

End Job

Scheduling

Area
Maintenance
Supervisor

Record
Labour hours

Close Job

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

Create N1 Notification

Back to Table of Contents

7

Notification: Create using

ZIW21 (N1 Type)

An N1 notification requires the following mandatory informatio

The Tag number (861G1003B) that is affected.
Plant (this field will default if the User sets
parameter ID IWK to M100).
Description of the problem 40 character
Symptom code which is selected from a
predefined list (e.g. ID17 = Leakage, ID23 Over
heating...)
The person who initially detected the problem
(SATORP Badge no).
8

Notification: Create using

ZIW21 (N1 Type)
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 studies.
A notification should ONLY be created against a 5th
level Functional Location.

Notification: Create using

ZIW21 (N1 Type)
Transaction ZIW21 is used for the creation of N1
notifications.

Note:
In order to make the Plant field
default to M100, follow the steps
below and set parameter ID IWK to
Value M100 . This has to be done
only once.

Plant not
defaulted

If plant not
defaulted standard
text will not appear

10

Notification: Create using

ZIW21 (N1 Type)
Transaction
ZiW21

Plant
defaulted

Standard
text appears

11

Notification: Create using

ZIW21 (N1 Type)

The Tag number can be found adjacent to the

equipment or on the P&ID & will be in the format 861G-1003-B

Click
Enter
button

When manually entering the Tag number in ZiW21,

you must remove the dashes for example
The tag field has a
861G1003B
Enter Tag
search
function
number
which can be used
if the tag number
cannot be found.
This
search
function
is
covered
in
The
greyed out
fields do not
another
course.
become editable until
the Tag field is populated
and the enter icon is clicked

12

Notification: Create using

ZIW21 (N1 Type)

The Object Information box displays previous

notifications/work orders created against the same tag
number.
The box shows if the problem was reported on a
previous shift and if so, the notification currently under
creation is not required and can be exited without
saving
If the work was completed, the completion date is

Last 3
displayed.
Notifications

Last active
work order
Double click
to view
13

Notification: Create using

ZIW21 (N1 Type)
Maintain
Symptom Text

Planner group
defaults from
Functional
Location
It should not
be modified in
ZIW21

14

Notification: Create using

ZIW21 (N1 Type)
Symptom Text should clearly describe the defect or
requirement.
Symptom Text is limited to 40 characters. This text
appears in all notification list reports so should be as
The table
shows examples
of good & bad Symptom Text
meaningful
as possible.

Additional information relating to the work request can

be added in the Details field.
15

Notification: Create using

ZIW21 (N1 Type)

The symptom code is a catalogue of ISO damage

codes.
The symptom code CAN ONLY be selected from the
drop down, it MUST NOT be typed directly into the
field.

Click to view
Symptom
codes

Select the code

which best
describes the
problem

16

Notification: Create using

ZIW21 (N1 Type)

More Details This

is a free text box
with unlimited
characters

SATORP Badge # of the

person who initially
detected the problem
17

Notification: Create using

ZIW21 (N1 Type)
The notification creator DOES NOT enter the priority
code on an N1 Notification.
Operation Maintenance Coordinator and Maintenance
Leader assign the Priority code in the notification
during the daily meeting.

>>Creator Never sets the

PRIORITY <<

18

Notification: Create using

ZIW21 (N1 Type)

Save. The system

automatically assigns
a notification number

19

Display Notification

Back to Table of Contents

20

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
21

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

22

Display Notification List

Back to Table of Contents

23

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.

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

These saved searches are

called variants and can be
ZIW28/29 have an identical set
retrieved
clicking
on
of
variants. by
There
is a separate
the Get training
Variant Icon.
detailed
presentation
covering these transactions.24

Notification: List Display

Maintain
search value

A8 corresponds to
Area 8

Execute

Choose

Choose the Variant

as per the
requirement

25

Notification: List Display

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

26

Notification: List Display

The Notification list is displayed based on the
selection criteria. 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

27

28