Skip to Content

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.

To report this post you need to login first.

9 Comments

You must be Logged on to comment or reply to a post.

  1. Pete Atkin

    Here’s some PM related cut-over tasks I have collected:

    – Stock levels/counts

    – Transfer open orders and notifications

    – Measurement documents

    – Schedule background jobs (e.g. IP30, custom developed reports/programs, etc)

    – Strategies for maintenance plans

    – Schedule maintenance plans

    – PO creation/updates (e.g. partial deliveries)

    – Selection screen variants (e.g. IW38)

    – Report display variants (e.g. IW38)

    – Number ranges (manual transports)

    – Data for non-customisable Z tables

    – Quickview/ABAP Query reports

    – Classes & Characterisitics (you can ALE these from one system to another)

    – Printer setup (including SAPScript/SmartForm fonts)

    – Load SAP GUI

    (0) 

Leave a Reply