Scribd
Upload
207 views

SAP PM Activities

This document outlines key cut-over tasks for an SAP Plant Maintenance implementation including: 1. Setting up number ranges for master data objects like equipment, measurement points, and maintenance plans. 2. Creating selection screen variants for transaction screens. 3. Defining maintenance strategies and scheduling initial maintenance plans. 4. Transferring open orders, notifications, and historical data from the legacy system. 5. Configuring finance-related settings like cost element groups and labor rates.

Uploaded by

kiran reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
207 views

SAP PM Activities

This document outlines key cut-over tasks for an SAP Plant Maintenance implementation including: 1. Setting up number ranges for master data objects like equipment, measurement points, and maintenance plans. 2. Creating selection screen variants for transaction screens. 3. Defining maintenance strategies and scheduling initial maintenance plans. 4. Transferring open orders, notifications, and historical data from the legacy system. 5. Configuring finance-related settings like cost element groups and labor rates.

Uploaded by

kiran reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Objective:

This document can guide the consultants as check list during the Cut Over Activities of SAP Plant
Maintenance Implementation.

1. Characteristics to be used in Measuring Points & Technical Objects


2. Classes to be used in Technical Objects
3. Cost Element Groups maintained in PM Costing Variants / Settlement Profile / Allocation Structures
4. Permits
5. Strategies for Maintenance Plans
6. ABAP Query Reports
7. Preparation of Template & Execution of Strategy based / Multi Counter Plan scheduling
8. Maintenance Notification / Order uploading template

Characteristics:

All the characteristics should have been created as per the usage in Measuring Points & Technical Objects.
This will avoid the duplication of master creation, errors, etc., Characteristics which will be used in Permits
also should be created accordingly.

Classes:

All classes should be created based on the usage either in Equipment / Functional Location / Permits
(Licenses) category.

Cost Element Groups:

Cost Element groups should be created as per the assignment of those groups in the configuration front.
Generally, cost elements will not / should not be assigned in the configuration directly as it tends to change
according to client (DEV / QAS / PRD). So, its advisable to create cost element groups & assign them in the
configuration.

Those cost element groups should be defined as Master data before uploading Maintenance orders / scheduling
Maintenance plans.

Permits:

During Cut Over activities / Back logs, Permit functionality may not be required as the orders are in past &
they might have got approval in legacy system already. Once all the Back logs are uploaded, these Permit
system should be activated.

Maintenance Strategies:

As per the business requirement, Maintenance Strategies should have been defined before uploading Task List
& Maintenance Plans. Maintenance Strategy should be defined as per Scheduling Indicator. Each scheduling
indicator should be restricted with one or 2 (max) maintenance strategies.

ABAP Query Reports:


ABAP query reports should be created in the Live Production Client as per the requirement.

Template for Maintenance Plan Scheduling:

This template should have been shared with Power Users & the same should have been prepared as per the
Technical Object. This template is required for strategy & multi counter plan. For single cycle plan, start date
can be arrived easily, so this template will not be required.

This template should contain details like Technical Object, Operations on that, Last date / reading happened on
operation wise, next date / reading on which that operation should fall on due, current counter reading for
performance based cycle.

Template for Notifications / Orders:

This Template should have been shared with the Power users & these details should be captured from cut off
date. This details contain Open orders, In Process Orders with Partial Confirmation / Partial GI, etc.,
Completed Orders without Settlement, etc.,

Historical Orders can be captured separately using IW61.

Conclusion:

This document can guide you in the critical phase of Implementation Project as check list. This list may not
have 100 % data, but it will give some overall idea on the Cut Over details.

Plant Maintenance Cut-Over Activities/Tasks


4113,161

Here is a list of cut-over tasks that should be considered during go-live.

Please contribute:

1. Number Ranges (manual activity, or manually created transports)

 Measurement points
 Measurement documents
 Equipment masters
 Maintenance plans
 Maintenance items
 Task lists: general, equipment and functional locations
 Notifications
 Orders
 DMS documents
2. Reports

 Create default variants for selection screens e.g. IW28/9


 Create default layouts for ALV displays e.g. IW38/9

3. Maintenance Plans

 Strategies for maintenance plans


 Create initial measurement documents which are required for counter based maintenance
plans
 Schedule maintenance plans from start-date of go-live

4. Batch Programs/Interfaces

 Schedule batch reports such as IP30/CO99/KO8G, custom developed reports/programs, etc.


 Schedule batch reports with distribution lists to email data to users
 Schedule batch programs for interfaces

5. Master and Legacy Data

 Transfer open orders/notifications from legacy system to SAP


 If required, transfer historical data to SAP: orders, notifications, measurements, etc.
 Classes & Characteristics (you can ALE these from one system to another)
 Stock levels for maintenance spares
 Run program RI_IFLOT2IFLOS if you are using alternative labels for functional locations

6. Master and Legacy Data

 Set up local printers


 SmartForm/SAPScript fonts
 Printer settings for barcodes

7. Finance Data

 Set up labour rates via KP26


 Create cost element groups for value categories (OIK2)

8. Translations

 IMG activities
 Classes/characteristics

9. Maintenance Stock

 Print bin labels


 Check posting periods are open
 Stock levels for maintenance spares
 

10. Miscellaneous

 Data for non-customisable Z tables


 QuickView/ABAP Query reports
 Parameter ID settings (transaction SU3)
 Selection variable settings (transaction STVARV)
 User favorite menus (requires Z program)
 User personal lists (requires Z program)
 Workflow activities e.g. email addresses

Cut Over Activities – Plant Maintenance (SPRO


front)
1294,441

The following information is the continuation of Document created by Mr. Pete Atkin

http://scn.sap.com/community/eam/blog/2013/07/25/faq-cut-over-activities

Objective:

This document will give the insight of Cut Over Activities to be done in terms of Plant Maintenance module
implementations.

Number Ranges:

1. Equipment (Transaction Code: OIEN)


2. Measuring Point (Transaction Code: IK09)
3. Maintenance Plan (Transaction Code: IP20)
4. Maintenance Item (Transaction Code: IP21)
5. Task List (Transaction Code: OIL4 / OIL5 / OIL0)
6. Maintenance Notification (Transaction Code: IW20)
7. Maintenance Order (Transaction Code: OION)

Generally, Number ranges will be defined as Client Level setting.

Number Ranges for Equipment, Measuring Point & Maintenance Plans can be defined based on the categories.
This will be helpful over the period to understand the category of Master data by viewing its number.

Equipment:
Equipment categories can be defined as per Business Requirement. Equipment Number ranges can be defined
based on Equipment categories.

Measuring Point:

Measuring Points can be classified as follows.

1. Measuring Point
2. Measuring Point Counter
3. Measuring Point Qualitative

Maintenance Plan:

Maintenance Plans can be classified as follows.

1. Time based Maintenance Plan – Notification


2. Time based Maintenance Plan – Order
3. Performance based Maintenance Plan – Notification
4. Performance based Maintenance Plan – Order
5. Calibration Order (if requires to provide authorization based on category)

Task List:

Task List has its own classification as Equipment, Functional Location & General. So, the same can be
followed to define the number ranges.

Maintenance Notification:

Maintenance Notification types are client level configuration, so its not possible to define the number ranges
based on Notification type & Maintenance Planning Plant / Maintenance Plant combination. If this requires to
differentiate the notifications based on Maintenance Plant, then separate notification types should be defined &
the control can be given through authorization.

But Number ranges for Notifications can be defined at Notification type level.

Maintenance Order:

The same scenario as Maintenance Notification applies to Maintenance Order as well. Number ranges can be
possible at Maintenance Order type. If you want to differentiate at Planning plant level, then Order types
should be created & assignment should have been made accordingly.

Selection Screen Variants:

Selection Screen Variants can be defined in the Configuration & the same can be transported to Target clients.
Else, this can be done as Client Level Settings.

1. Functional Location (OIW6)


2. Equipment (OIYC)
3. Measuring Points (OIRF)
4. Measurement Documents (OIRL)
5. Maintenance Plan (OIY9 / OIWW / OIW5)
6. Maintenance Item (OIWY)
7. Task list (OIWO)
8. Notifications (OIWI / OIWK / OIW1 / OIYZ / OIYW)
9. Orders (OIWL / OIWU / OIUI)
10. Confirmations (OIYG / OIW3)

The above given list are the commonly used data on List editing. As per the requirement, Selection variants
can be defined.

Conclusion:

These are the basic Cut Over Activities to be done for SAP Plant Maintenance.

You might also like