PM-Maintenance Plan and Notification - Config PDF

SAP PM Configuration
Pack
Published by Team of SAP
Consultants at SAPTOPJOBS
Visit us at www.sap-topjobs.com
Copyright 2007-09@SAPTOPJOBS
All rights reserved. No part of this publication may be reproduced, stored in a

retrieval system, or transmitted in any form, or by any means electronic or
mechanical including photocopying, recording or any information storage and
retrieval system without permission in writing from SAPTOPJOBS
INDEX
1. MAINTENANCE PROCESSING.............................................................3
2. DEFINE PLANT SECTIONS ..................................................................4
3. DEFINE MAINTENANCE PLANNER GROUP......................................6
4. SET MAINTENANCE PLAN CATEGORY.............................................8
5. DEFINE NUMBER RANGES FOR MAINTENANCE PLANS............11
6. MAINTENANCE AND SERVICE NOTIFICATION TYPE .................16
7. DEFINE SCREEN TEMPLATE FOR NOTIFICATION TYPE ..........20
8. FORMAT NOTIFICATION LONG TEXT ............................................34
9. SET FIELD SELECTION FOR NOTIFICATIONS .............................38
10. DEFINE NUMBER RANGES................................................................42
11. DEFINE TRANSACTION START VALUE ..........................................47
12. ASSIGN NOTIFICATION TYPES TO ORDER TYPES .....................51
13. MAINTAIN CATALOG ..........................................................................53
14. DEFINE CATALOG PROFILE .............................................................63
15. CHANGE CATALOG AND CATALOG PROFILE...............................66
16. DEFINE PARTNER DETERMINATION .............................................69
17. DEFINE PRIORITIES...........................................................................77
18. DEFINE RESPONSE MONITORING ..................................................82
19. OVER VIEW OF NOTIFICATION TYPE ............................................88

1. Maintenance Processing
Maintenance processing is to deal with maintenance plan and

notification in Plant maintenance.
Structure of maintenance plan is to have
Maintenance item
Maintenance plan
Maintenance Item:-
It describes which preventive maintenance task must be

carried out periodically on which objects.
Maintenance Plan:-
Broadly maintenance plan can be classified as
¾ Preventive maintenance plan

¾ Breakdown maintenance plan
¾ Counter based maintenance plan etc.
Maintenance plan contains the scheduling of maintenance

information. Further the maintenance plan can be divided into
following types
a. single cycle plan

b. Based on maintenance strategy
c. Multiple counter plans
Similarly, there is notification processing which triggers PM

order mainly for breakdown maintenance.
We shall discuss those topics here one by one.

2. Define Plant Sections
BACKGROUND
This configuration setting enables to define plant sections.
Plant section is used to divide the plant logically for ease of

reporting and responsibilities.
SCENARIO
Define plant section for IND6.
INSTRUCTIONS
Follow the Menu Path: IMGÆPlant Maintenance and

customer servicesÆ Maintenance plans, Work centers, Task
Lists and PRTs Æ Basic Settings Æ Define Plant Sections
Click
Click
Maintain the following fields

Field name Field description and value
Key identifying the plant. E.g.
IND6
Key identifying the plant
section. E.g. IN1
Identification of responsible
person. E.g. Mark
Contact number. Enter if
required.
Click
Impact of this configuration in Master Data /

Transaction
Plant section defined here will be used in transactions.

3. Define Maintenance planner group
BACKGROUND
This configuration setting enables to define maintenance

planner group.
Maintenance planning group can be a person or a department.

It can be assigned to technical objects.
SCENARIO
Define planner group for IND6
INSTRUCTIONS

Lists and PRTs Æ Basic Settings Æ Define maintenance
planner group
Click
Click

Key identifying the planning
plant. E.g. IND6
Key identifying the planner
group. E.g. IN6
Person or department name.
e.g. David to indicate name.
Contact number can be
entered if required for info
purpose.
Click Save .

Transaction
Maintenance planner will be used in the transaction.

4. Set Maintenance Plan category
BACKGROUND
This configuration setting enables to define Maintenance Plan

category.
Maintenance plan category defines which call object to be

generated for a maintenance plan when maintenance call is
due.
I.e. with reference to the maintenance plan, system can trigger

the following call objects.
9 Maintenance order
9 Service order
9 Maintenance order with maintenance notification
9 Service order with service notification
9 Maintenance order with WCM objects
9 Maintenance notification
9 Service notification
9 Service entry sheet
9 Inspection lot
Maintenance plan category defined can be assigned as a

default to users using parameter id WAT.
SCENARIO
Define maintenance plan category.
INSTRUCTIONS
Lists and PRTs Æ Maintenance Plans Æ Set Maintenance Plan
categories
Click
Click

Key identifying the
maintenance plan category.
E.g. I6
Text defining the maintenance
plan category. E.g. IND6 PM
order call
Select from the available
entry.
Available entries are
E.g. Select Maintenance or

service order.
Tick in this check box will
create change document. E.g.
Tick the check box.
Confirmation for completing
the call object. It can control
scheduling of maintenance
plan after completion.
E.g. Tick this check box.
enable to create maintenance
plan with reference to outline
agreement.
Order category in which the
reference object to be used.
Select from available entries.
Repeat the above steps to create further maintenance plan
categories.
Click

Transaction
Maintenance plan categories defined here is used in

maintenance plan.
5. Define Number Ranges for maintenance Plans
BACKGROUND
This configuration setting enables to define number range for

maintenance plan.
Number range to the maintenance plan is assigned through

the maintenance plan category.
Note: - Number ranges are assigned directly in the production

system normally.
SCENARIO
Define number range for maintenance plan category I6.
INSTRUCTIONS

Lists and PRTs Æ Maintenance Plans Æ Define number ranges
for maintenance plans
Click
Click
Note I6 is not assigned with any number range.

To create additional group (additional number range) from the
top follow the menu path as shown below
Enter the required text, from number and To number.
Click
Click on
Click
Tick the required group check box. E.g.
Click
Click
Click

Transaction
Number range defined here will be used when performing the

relevant transaction
6. Maintenance and Service Notification Type
BACKGROUND
This configuration setting enables to define notification type.
Notification is the process of informing and recording any

deviation from the specification. SAP defined standard
notification types are
9 Customer complaint
9 Vendor complaint
9 Internal problem notification
Apart from the above types, any other type of notification can
be created according to the business requirements.
SCENARIO
Define Notification type for Breakdown maintenance type I6.
INSTRUCTIONS

customer servicesÆ Maintenance and Service Processing Æ
Maintenance and Service Notifications Æ Notification creation
Æ Notification Types Æ Define Notification Types
Click
To create new notification type, it is suggested to copy from
the standard Notification type.
Select Notification type M1 by pressing the grey box in the left.
Click
Field Name Field description and value
Key identifying the notification
type
Origin of notification. Select
from available entries.
E.g. malfunction report

Date and time to propose
when completing notification.
E.g. C to indicate
malfunctioning end.
It is used to define object or
subject when creating
maintenance notification.
Catalog profile is the collection
of codes and code group. We
will discuss about it later.
LIS structure update control
Leave it as it is with SAP
standard settings.
assign the notification number
immediately on start of
transaction rather than
assigning number at the time
of saving.
Number range copied from the
source as 01
Click
Click

Transaction
New notification type with I6 can be created.

7. Define Screen template for notification type
BACKGROUND
This configuration setting enables to define the screen

template for Notification.
Information in the quality notification can be grouped in to

different tab screens.
Main tab screens are
General Data
Defect
Problem type
Causes
Task
Activity
SCENARIO
Define the screen template for notification type I6
INSTRUCTION

Æ Notification Types Æ Set Screen Template for the
notification type
Click
Enter Notification type. E.g. I6
Click
Click
Maintain the following data

Field name Field description and
value
Key identifying the tab
page screen already
defined. Select the
right tab page. E.g.
10\TAB01 –
Notification 1 screen
to enter further screen
details.
Tick this check box.
This is for better
screen display and
navigatiaon.
Screen area to display
sub screens under the
tab screen TAB01.
E.g. select 005 to
enter object details.
Maintain the screen
area as shown. You
can select from the
available entries.***
*** available screen entries as shown below
Click
Click in the top to assign the next tab screen.
Note:- When using other tab screen, it is not possible to
maintain the screen area.


Click
Click
Click

Transaction
While creating notification type I6, screen sequence will be as

per the setting performed here.
Note: - In the tab page, the first is reference object 005; still it
is not appearing here. Apart from this header screen data and
object screen has to be defined, hence it is not appearing here
now.
Let us review this after completing entire config.

8. Format Notification Long text
BACKGROUND
This configuration setting enables to define formatting of

notification long text.
This is to indicate for each notification type
9 Changeability of long text entered in the notification
9 Maintain long text with user id, date and time.
SCENARIO
Define the format notification for long text.
INSTRUCTION

Æ Notification Types Æ Define Long text control for notification
type
Click
Click
Enter I6
Click
Select the I6 row
Click

maintain the log with user id,
date and time
Tick in this check box will not
allow any changes to the long
text when processing
notification. But additional
long text can be added.
Each long text line will be
formatted with tick in this
check box. Otherwise only the
first line will be formatted.
Key in which the long text is
to be formatted. Leave it
blank.***
*** Following are few examples of sap script format key
/ - Indicates new line
/: SAP Script control command.
/* commenting line, this line will not be taken into output.

Click
Click
9. Set Field Selection for Notifications
BACKGROUND
This configuration setting enables to define field selection for

notification.
This will help to make any field/s optional, mandatory, or to

hide. The process is similar to that explained in work center
field selection.
Here the setting should be done specific to the notification

type.
SCENARIO
Define the field selection for notification type I6.
INSTRUCTION

Æ Notification Types Æ Set field selection for Notification
Click
Double click on
Friends, rest of the screen control is same as explained above.
I.e Select the row, click on .
Click on the desire row and click new values.
Maintain the relevant radio button for maintenance category.
As it has already been explained, it is not repeated here.

Transaction
While creating notification type I6, field control will be as per

the setting performed here.
10. Define Number Ranges
BACKGROUND
This configuration setting enables to define number range for

notification.
Number range is assigned to the notification type level.
Note: - Number ranges are normally done directly at the

production system.
SCENARIO
Discuss number range definition.
INSTRUCTION

Æ Notification Types Æ Define Number Ranges
Click
Click to assign number range
Note:- Notification type I6 is assigned automatically when
copying.
Let us try to assign it to other number range. E.g. to
.
Click on notification type I6
Click to select the element
Tick the check box of required group. E.g. internal service

notification
Click
Click
Click
Click

Transaction
While creating notification type I6, number will be assigned as

per the setting done here.
11. Define Transaction start value
BACKGROUND
This configuration setting enables to define transaction start

value. Certain value can be assigned to few fields at the time of
beginning the transaction automatically.
E.g. When creating notification using transaction code IW21,

one has to enter the notification type as a mandatory entry. It
is possible to make certain notification type as a default type.
The above will simplify the transaction to some extent.
SCENARIO
Assign notification type I6 to start transaction value.
INSTRUCTION

Æ Notification Types Æ Define Transaction start value
Click
Double click on IW21

Key identifying the notification
type. E.g. I6
Initial screen which is to be
accessed. Select from the
available entries.
Tick in this check will display
the initial screen of the
transaction. Other wise,
directly system will popup the
Malfunctioning tab screen
with out initial screen display.
Click
Click

Transaction
While creating notification, initial screen with value defined
here will appear.
On pressing enter in the initial screen, system will directly

popup the next screen as per this setting. In this example, it
should popup the Malfunctioning screen.
12. Assign Notification types to order types
BACKGROUND
This configuration setting enables to define the relation

between Notification type and order type.
When creating the maintenance notification, it is possible to

create PM orders for performing the maintenance task. If an
order type is maintained here, system will create the PM order
automatically.
However you will be able to create any order type.
SCENARIO
Define order type to notification type I6.
INSTRUCTION

Æ Notification Types Æ Assign Notification Types to Order
types
Click
Maintain the maintenance order type, E.g. PM01

Click
Click

Transaction
When creating PM order from Notification, order type PM01

will be assigned automatically.
13. Maintain Catalog
BACKGROUND
This configuration setting enables to define the catalog. Please

note that the catalog maintenance is available in Easy access
as well as in configuration.
It is recommended to provide access to maintain the catalog

must at one single point to maintain the uniformity and
consistency.
Catalogs are mainly used to maintain
Defect details,
Codes,
Activities to be performed
Causes of the problem
Action taken etc.
If given a chance to enter the descriptive value, there won’t be
any uniformity to identify a defect or a cause. Through code,
every body has to convey a defect in same codes.
This will help in uniformity and reporting. However, one will be

able to add more information in the long text.
Catalog data is a client level data.
SCENARIO
Discuss catalog. SAP defined catalogs are sufficient. We shall

discuss it with existing one.
INSTRUCTION
Æ Notification Content Æ Maintain Catalogs
Click
Double click
Click to create new catalogs.
Double click to view its detail.

Key identifying catalog. E.g. 5
to indicate causes.
Short text to identify the
catalog and key word helpful
to search the catalog.
allow to create selected set. ***
mark the catalog as marked
for deletion.
** Tick in this check box will
allow you to maintain the
follow-up action to the code
group when maintaining
under this type of catalog.
Note:- Useful only for catalog
of Task type. i.e. catalog type
2.
*** Selected set is the collection of codes from code group

maintained at Plant level.
** Follow-up action is the process of triggering another activity
(like changing equipment status) through a function module.
Steps in follow-up actions are:-
9 Function module has to be developed to perform the

defined action,
9 it has to be assigned to a follow-up action (freely
defined alpha numeric digits).
9 This follow-up action can be assigned to codes.
Click
Click
Double click
This enables to maintain the master data of code group and

codes.
Enter the desired catalog. E.g. 5 to maintain the codes groups
of causes.
Code group name or * to denote generic entry, inside the

transaction correct code group can be maintained.
Click
Click to create new code group
Maintain following fields

Key identifying the code
group. Any alpha numeric 8
digit key. E.g. IN6-PD1.
Text describing the code
group. E.g. Production
Causes.
Status of the code group.
Click
Similarly create required catalogs.
Select the desired code group. E.g. IN6-PD1
Double click codes in the left side to maintain codes.
Click
Enter code. E.g. 0001
Enter short description of code. E.g. Less curing time.
Maintain required entries as explained above.
Click
Click
Note:- There is no facility to maintain the follow-up action to

this type of catalog. It is available only for task type, i.e catalog
type 2.
Note: - If the business situation requires follow-up action for

causes also, you can create your own type.

Transaction
Code group and codes related to various causes can be defined

under this catalog type 5.
As shown above, different types of code group can be created
and different codes under each code group can be assigned.
Below screen shows codes maintained under Production

causes.
This codes will be used when processing notification.

14. Define catalog profile
BACKGROUND
This configuration setting enables to define the catalog profile.

Catalog profile is the collection catalogs. It is assigned to
notification type.
This help to control the use of codes and code groups.
SCENARIO
Define catalog profile.
INSTRUCTION

Æ Notification Content Æ Define catalog profile
Click
Click

Key identifying the catalog
profile.
Maintain the text the next
window.
Message type when system
checks the catalog profile at
the time notification
processing. If no message type
is maintained, it is not
checked.
Click
Click
Select the above created row
Double click
Click
Maintain the allowed catalog and code group

Click
Click

Transaction
Catalog profile defined is assigned to the notification type and

there by the usage of codes and code group for a notification
type is controlled.
15. Change catalog and catalog profile
BACKGROUND
This configuration setting enables to assign the catalog profile

to a notification type.
When creating a notification type, usage of codes and code

groups are restricted according to the codes and code groups
allowed in the catalog profile. (which we discussed above).
SCENARIO
Define catalog profile to notification type I6..
INSTRUCTION

Æ Notification Content Æ Change catalog and catalog profile
for notification type
Click
Double click on
Maintain the catalog profile and allowed catalogs as shown

below
Click
Click
Click

Transaction
Catalog profile and catalog defined here is used when

processing notification.
16. Define partner determination
BACKGROUND
This configuration setting enables to define partner profile.
Partner is nothing but other people who are involved in a

document.
E.g. in a notification, there must be a person who must have

created, and there must be a person as responsible to attend
and one more person can be a kind of contact person or
coordinator.
Similarly in purchase order, Vendor, delivery plant if different

from vendor office, transporter can be partners.
In SAP apart from defining partners, it must also be specified

who is that partner is to be. I.e. in SAP technical terms.
Following are few examples.
SAP USER – SAP identifies it with the user id

Customer – SAP identifies with customer master
Vendor – SAP identifies with vendor master record
When creating a notification type, partners must be assigned

according to this setting.
SCENARIO
Create and assign partner profiles for notification type I6.
INSTRUCTION

Æ Partners Æ Define partner determination and partner
function
Click
Double click
Select the radio button to maintain partner

function for Plant maintenance notification
Click
Click to create new entries.

key identifying the partner
determination procedure
e.g. I6
Description of the procedure.
E.g. PF for IND6
Double click to create partner function
Click to create new entries

Key identifying the partner
function. E.g. US
Description of the partner
function. E.g. User as author
Key identifying the type of
partner. E.g. US to indicate
User possible entries are
Key to define the higher level
partner function and there by
to define hierarchy. Leave it
blank
allow user of partner function
only once in the master data.
Leave it blank
Key identifying hierarchy.
Leave it blank
Note: - Create as many partner functions as required.
Double click
Select row I6
Double click
Click to create new entries

determination procedure. E.g.
I6
function. E.g. US
Tick in this check box will not
allow to change partner in the
document. Leave it blank.
make partner as mandatory.
Tick this check box.
allow use of partner function
only once in the document.
Leave it blank.
update the maintenance
appointment calendar of
maintenance person. I.e. the
user. Leave it blank
Maintain other partners as required.

Click
Click
Double click
Select Notification type I6
Assign partner determination procedure I6 to it.

Click
Click
Double click
Identify the required notification type. E.g. I6

Double click
Maintain the following partner function as shown here here.
Click
Click

Transaction
Partners to the notification type I6 will be assigned as per the

setting maintained here.
17. Define priorities
BACKGROUND
This configuration setting enables to define priorities.
Priorities must be defined for every notification. By

maintaining priorities, automatically the completion date will
be determined.
SCENARIO
Define priorities for notification I6..
INSTRUCTION

Maintenance and Service Notifications Æ Notification
Processing Æ Response Time Monitoring Æ Define Priorities
Click
Double click
Click
Maintain entries as shown beloe
Click
Click two times

Double click
Click
Maintain following fields

Key identifying the priority
type. E.g. I6
Priority order number. E.g.
U - Urgent
H – High
N – Normal
Relative start date for
notification. Value to calculate
start date automatically. E.g.1
Relative end date for
notification. Value to calculate
end date automatically. E.g.1
Text identifying the priority
order.
Start date Unit and end date
Unit respectively. E.g. D to
indicate Days in both.
Click
Click two times
Double click
Identify I6 notification type
Double click
Enter priority type

Click
Click

Transaction
Priorities to the notification type I6 will be set as per the

setting performed here.
18. Define response monitoring
BACKGROUND
This configuration setting enables to define response time

monitoring.
Response time monitoring is mainly to monitor or to instruct

other responsible team member to carryout certain task within
stipulated duration.
Steps in response time monitoring are

9 Defining the response time for each specific code
under specific catalog.
9 Assign this code with response to a response profile.
9 Assign the response profile to a notification type.
Similarly service time also defined here. Service time mainly

indicate the service entitlement for a customer services. Mainly
applicable for customer service notifications.
SCENARIO
Define response time profile and assign it to notification type

I6.
INSTRUCTION

Maintenance and Service Notifications Æ Notification
Processing Æ Response Time Monitoring Æ Define Response
Monitoring
Click
Double click
Click
Maintain the response profile key and text as shown below
Note:- Hierarchy is used for escalation procedure. Different

response profile with hierarchy number is assigned to a
response hierarchy. Hierarchy level 1 is the highest.
Select the above created entry
Double click
Click

Key identifying the priority
type. E.g. Enter H – High from
I6 priority type. Note: any
priority type can be selected.
Task catalog type. I.e 5 to
indicate for cause catalog
type, 2 to indicate Task
catalog type. E.g. 2
Task code group to which the
response is applicable. E.g.
PM01 to indicate for all
maintenance task it should be
applicable.
To which cause code under
cause code group PM01 is this
response time applicable. E.g.
2001 – Processing of damage.
Duration within which the
task is to be carried
performed. E.g. 3
Unit of interval. E.g. H to
indicate Hour
Partner function of
responsible person. E.g. I3 to
indicate responsible person
Specify the partner function
object. I.e responsible person
id must be specified. E.g.
SAPUSER to indicate the user.
Note:- this user id must be
available in SAP.
Click
Click
Double click
Click
Maintain service profile and description
Click
Click
Select the row created above

Click
Click
Maintain the entries as shown below
Note: - Define more entries with different counter if required.
Response profile is maintained here to perform this service

profile which covers, person responsible, time duration.
Note: - this service profile is meaningful only for the task PM01
with code 2001.
Click
Click till the below screen is reached
Double click
Maintain the service window and response profile to
notification type I6

Transaction
Response monitoring for notification type I6 will be set as per

the setting performed here.
19. Over View of Notification Type
BACKGROUND
This configuration setting enables to define various

parameters of notification type.
It is possible to do most of the notification related

configuration using this setting, however it is recommended to
look at the other methods when one is learning.
Now, let us check what is there here for us for notification

configuration.
SCENARIO
Discuss over view of notification type.
INSTRUCTION

Maintenance and Service Notifications Æ Over view of
Notification type
Click
Position notification type I6

Possible settings are displayed in the left side
Select notification type I6

Double click
Screen type header and screen type object are mandatory

entry.
Maintain header screen and
Maintain
Click
Double click
Note: - We have discussed this earlier.
Double click
Not to maintain anything here
Double click
We have discussed this earlier

Double click
Double click
Double click

Double click
Double click
We have already discusses this in master data topic.

User status profile can be assigned to notification type.
Double click
Click
Click
Transaction
The entire notification related settings is completed and

system should perform as per this settings when creating
notification of type I6.
When creating notification, system first prompt the

malfunctioning screen
Notification main screen

Note: - Reference Object is appearing now after maintaining
the header data object screen in the over view of notification
type setting.

PM-Maintenance Plan and Notification - Config PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

PM-Maintenance Plan and Notification - Config PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

SAP PM Configuration

All rights reserved. No part of this publication may be reproduced, stored in a

2. DEFINE PLANT SECTIONS ..................................................................4

3. DEFINE MAINTENANCE PLANNER GROUP......................................6

4. SET MAINTENANCE PLAN CATEGORY.............................................8

5. DEFINE NUMBER RANGES FOR MAINTENANCE PLANS............11

6. MAINTENANCE AND SERVICE NOTIFICATION TYPE .................16

7. DEFINE SCREEN TEMPLATE FOR NOTIFICATION TYPE ..........20

8. FORMAT NOTIFICATION LONG TEXT ............................................34

9. SET FIELD SELECTION FOR NOTIFICATIONS .............................38

10. DEFINE NUMBER RANGES................................................................42

11. DEFINE TRANSACTION START VALUE ..........................................47

12. ASSIGN NOTIFICATION TYPES TO ORDER TYPES .....................51

13. MAINTAIN CATALOG ..........................................................................53

14. DEFINE CATALOG PROFILE .............................................................63

15. CHANGE CATALOG AND CATALOG PROFILE...............................66

16. DEFINE PARTNER DETERMINATION .............................................69

17. DEFINE PRIORITIES...........................................................................77

18. DEFINE RESPONSE MONITORING ..................................................82

19. OVER VIEW OF NOTIFICATION TYPE ............................................88

Maintenance processing is to deal with maintenance plan and

Structure of maintenance plan is to have

It describes which preventive maintenance task must be

Broadly maintenance plan can be classified as

¾ Preventive maintenance plan

Maintenance plan contains the scheduling of maintenance

a. single cycle plan

Similarly, there is notification processing which triggers PM

We shall discuss those topics here one by one.

This configuration setting enables to define plant sections.

Plant section is used to divide the plant logically for ease of

Define plant section for IND6.

Follow the Menu Path: IMGÆPlant Maintenance and

Maintain the following fields

Impact of this configuration in Master Data /

Plant section defined here will be used in transactions.

This configuration setting enables to define maintenance

Maintenance planning group can be a person or a department.

Define planner group for IND6

Follow the Menu Path: IMGÆPlant Maintenance and

Maintain the following fields

Impact of this configuration in Master Data /

Maintenance planner will be used in the transaction.

This configuration setting enables to define Maintenance Plan

Maintenance plan category defines which call object to be

I.e. with reference to the maintenance plan, system can trigger

Maintenance plan category defined can be assigned as a

Define maintenance plan category.

Field name Field description and value

E.g. Select Maintenance or

Impact of this configuration in Master Data /

Maintenance plan categories defined here is used in

This configuration setting enables to define number range for

Number range to the maintenance plan is assigned through

Note: - Number ranges are assigned directly in the production

Define number range for maintenance plan category I6.

Follow the Menu Path: IMGÆPlant Maintenance and

Note I6 is not assigned with any number range.

Enter the required text, from number and To number.

Tick the required group check box. E.g.

Impact of this configuration in Master Data /

Number range defined here will be used when performing the

This configuration setting enables to define notification type.