Header goes hereDraftUser manualNotification Creation

Prepared by:Chandan Kumar07 Sept 2014

Table of ContentsScenario31Notification Processing31.1Create Notification31.1.1Definition and Prerequisites31.1.2Menu Path and Transaction code31.1.3Responsibility31.1.4Screen capture41.2Change/Release Notification81.2.1Definition and Prerequisites81.2.2Menu Path and Transaction code81.2.3Responsibility81.2.4Screen capture81.3Close Notification111.3.1Definition and Prerequisites111.3.2Menu Path and Transaction code111.3.3Responsibility111.3.4Screen capture11

ScenarioMaintenance notification will be created in SAP in BCML to report the abnormal machine conditions or to request a maintenance activity in the Season period. User or the concerned department can create Maintenance notifications in system using their login details. Once a notification is created in system it is available to viewed or changed to the other users based on their authorization.

Users will report the following categories of incident through different types of notification as explained below

a) Preventive (Scheduled) Notification type =M1, only if there is a scheduled/planned plant stoppageb) Plant Breakdown Notification Type = M2, This will also be categorized as the critical maintenance and the stoppage time of the machine will be calculated as Breakdown Hours in SAP.c) General (Corrective) Notification type = M3, This will be categorized as the maintenance related to inspection or general activity reporting.d) Equipment Stoppage - Notification Type = ZS, It will capture the stoppage on the equipment, but it is not the plant stoppage. The stoppage time will be captured as Breakdown Hours.e) Opportunity Notification Type =ZM, It will be created on a Functional Location and not on equipment. It will capture defect due to Grid Disturbance, Cane Shortage, Reduce Crush, & Inclement Weather.

Notification Processing

Create Notification

Definition and PrerequisitesThis Notification type will be created by user in case of a scheduled maintenance activities. Any abnormal condition in machine or location which needs a schedule maintenance requirement shall be informed to the maintenance department by creating a M1 type notification.

1.1 Menu Path and Transaction codeSAP R/3 menuSAP Menu > Logistics >Plant Maintenance>Maintenance processing >Notification> Create(General)

Transaction codeIW21

1.1 1.1.2

ResponsibilityFloor technician, Shift Supervisor, Maintenance Engineer1.1 1.1.3 1.1.3

Screen capture

Input FieldMandatory/OptionalAvailable Values

Notification typeMandatoryPreventive =M1Breakdown=M2Corrective = M3Opportunity=ZMEquipment Stoppage = ZS

Prss Enter or click on Icon .

Detail Entry screen of Notification. Fill the fields as shown below by selecting the proper Equipment, Functional location and writing the problem details in short text and lobg text box.You need to select the planner group and Main work center in the entry screen.

After selecting the Equipment/Functional locatoin, an Object Information pop up box appears to show the details of already created notificaitons, orders in the system for the selected object.

To select the equipment from graphical structure display enter the top level functional location in the Functional location field eg..GCM and click on the structure icon

It opens the stuctural display of all equipments installed in the main functional locaiton at lower levels. Click on Expand Whole.

User can double click the equipment in the graphics display to automatically fill the Equipment field.

In case of M2 & ZS type Malfunction/Equipment Stoppage notifications, it is required that the creator enters the Breakdown start and end date and time at the time of creation of Notification. The user must tick the Breakdown Indicator check box in case of M2 notification.

Enter further details on the Notifcation create screen.

Save Notification and note the notificaiton number generated.

Input FieldMandatory/OptionalInput Values

Notification short text

OptionalShort description of incident

Reference Object - Functional locationOptional Functional location

Reference Object - EquipmentMandatoryEquipment Number

Description OptionalLong text description of incident

Responsibilities Planner GroupMandatoryPlanner group for the work area

Responsibilities Main Work centreMandatoryMain work centre responsible

Reported ByOptional Persons name who is reporting

Start/End date & timeOptionalRequired start/End date for completion of work

Item Object part OptionalObject part codes from catalogue

Item Defect codeOptional Defect code from catalogue

Cause textOptionalShort text for Cause

1.2 Change/Release Notification

2 1.2 1.2.1 1.2.1 1.2.1 Definition and PrerequisitesNotification once created in system is visible to all users based on their authorization. Notification email will also trigger to the responsible persons and HODs, managers etc based on the planner group and plant of the notification. This mail will be sent when the Notification is released (status REL) in the system. The process of releasing the Notification happens in the change mode of Notificaiton.

Notification can be changed by the Menu path

1.2 Menu Path and Transaction codeSAP R/3 menuSAP Menu > Logistics >Plant Maintenance>Maintenance processing >Notification>Change

Transaction codeIW22

1.2 1.2.3 ResponsibilityMaintenance Engineer, Maintenance technician, Maintenance manager1.2 1.2.4 1.2.4 Screen captureNotification status bar shows status =OSNO, means Outstanding notification when opened first in IW22. This notification is in change mode and further changes to update the correct equipment, cause or object part etc can be made to it by the Maintenance engineer/technician handling the incident

The details long text box contains the incident details text as per the person who has entered or further any text added by another person with the login ID, time and date stamp.

Click the Green Flag symbol to release the order. The notification status changes to NOPR, once it has been released.

1.3 Close Notification

1.3.1 Definition and Prerequisites Once the notification is released, its status changes to NOPR in the status bar. The Notification can be closed when work on it has finished and proper causes, and activity details are updated in it for correct record keeping. The Notification status changes to NOCO.

To close Notification, go to change mode and click on the Flag as shown . The systems ask for Reference date and time and propose it as current date and time. Accept the proposal or modify and then Notification is closed. 1.3.2 Menu Path and Transaction codeSAP R/3 menuSAP Menu > Logistics >Plant Maintenance>Maintenance processing >Notification>Change

Transaction codeIW22

1.3.3 ResponsibilityMaintenance Engineer, Maintenance Manager, Originator of Notification

1.3.4 Screen capture

Input FieldMandatory/OptionalAvailable Values

Reference DateMandatoryCurrent system Date/Proposed

Reference TimeMandatoryCurrent system time/proposed

Notification status changes to NOCO (closed) and it can be reopened if required by clicking In process again based on the authorization of the person user ID and role.

The Notification is now closed and status changes to NOCO. This notification is now closed for any changes unless put in process again by an authorized person. Local disclaimer and copyright statements go herePwCPage 15 of 15