Module4.2_PM_Create_N1_Notification_ZIW21_24.02.2013_V1.0

1

SAP Plant Maintenance

Create N1 Notification

Module 4.2

Version: V1.0 Date: 24/02/2013

2

Course Content

1. Notification

– Definition

– Notification Type

– Notification Process Flow

2. Create N1 Notification

3. Display Notification

4. Display Notification List

To go directly to a particular section click on the hyperlink

3

Notification

Back to Table of Contents

4

Notification: Definition

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.

What is a Notification?

5

Notification: Type

There are 4 types of notification. The Notification type determines the content and the usage of the notification.

N1 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 Departmentse.g. Operation department Routines

6

DAILY MEETING - Agree Finish Date

Create Notification Accept

Job?

Approve Job

Request

Operations Maintenance Coordinator

Maintenance leader

Planner Scheduling Area Maintenance

Supervisor

Create Work Order

Plan Work Order

Approve Planning

Schedule Daily Jobs

WEEKLY SCHEDULING MEETING

Produce Weekly

Schedule

NO

End Job

Notification and Work Order: Process Flow

Execute Jobs

Record Labour hoursClose Job

This course only deals with the first part of the notification process.

7

Create N1 Notification


8

An N1 notification requires the following mandatory information :

Notification: Create using ZIW21 (N1 Type)

• 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).

9

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.

Essential points when creating notification:


10

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.

If plant not defaulted standard text will not appear

Plant not defaulted

11


Standard text appears

Plant defaulted

Transaction ZiW21

12

Enter Tag number

The Tag number can be found adjacent to the equipment or on the P&ID & will be in the format 861-G-1003-B

When manually entering the Tag number in ZiW21, you must remove the “dashes” for example 861G1003B

The greyed out fields do not become editable untilthe Tag field is populated and the enter icon is clicked

Click ‘Enter’ button


The tag field has a search function which can be used if the tag number cannot be found. This search function is covered in another course.

13

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 displayed.

Last 3 Notifications

Double click to view

Last active work order


14


Planner group defaults from

Functional Location

It should not be modified in

ZIW21

Maintain Symptom Text

15

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 meaningful as possible.

The table shows examples of good & bad Symptom Text

Additional information relating to the work request can be added in the “Details” field.


16

Click to view Symptom

codes

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.

Select the code which best

describes the problem


17

More Details – This is a free text box

with unlimited characters

SATORP Badge # of the person who initially

detected the problem


18

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 <<


19


Save. The system automatically assigns a notification number

20

Display Notification


21

Notification: DisplayUse transaction iW23 to display a Notification.

Enter Notification Number

Detail of problem provided while creating the notification using transaction ZiW21

Symptom code provided while creating the notification using transaction ZiW21

Functional Location populated based on Tag Number entered while creating the

notification using transaction ZiW21

Symptom text provided while

creating the notification using

transaction ZiW21

22

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

23

Display Notification List


24

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 retrieved by clicking on the Get Variant Icon.

Notification: List Display

Transaction ZiW28/ZiW29

Get Variant

ZIW28/29 have an identical set of variants. There is a separate detailed training presentation covering these transactions.

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

25


Execute

Maintain search value

A8 corresponds to Area 8

Choose the Variant as per the

requirementChoose

26


Transaction ZiW29

Execute

After the variant has been selected ( e.g.: ‘AA-A8-100’ – Display newly created N1 notifications for A8) the associated search parameters will be automatically passed to the selection screen.

27

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

28

Documents

Module4.2_PM_Create_N1_Notification_ZIW21_24.02.2013_V1.0