Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Applies to:

SAP ECC, SAP BI

Summary

A maintenance plan describes dates and scope of the maintenance and inspection activities to be carried out on a technical object (equipment or functional location). These inspection activities on the equipment need to be tracked for various analytics purposes such as compliance reporting, asset replacement analysis, asset lifecycle maintenance history analysis, etc. The data from the maintenance plan call history forms the base for all this analysis. This document covers an approach to design a custom extractor for maintenance plan calls data extraction.

Author(s):    Chetan Bhogle

Company:    Deloitte Consulting

Author Bio

     Chetan is working in SAP BI area since last seven years. Chetan is working with Deloitte Consulting. Chetan has designed and developed analytical solutions for SAP EAM, CRM, Finance and other functional areas. Chetan has expertise in designing and developing comprehensive asset maintenance analytical solutions for utilities.

Table of Contents 

1.            Importance of maintenance plan call data.

2.            Various ways in which maintenance plans can be configured in SAP ECC.

3.            Understanding the relevant tables.

4.            Understanding the standard extractor

5.            FM based custom extractor.

6.            Delta enable for FM based custom extractor

7.            Recommended additional enhancements.

1. Importance of maintenance plan call data

 

A maintenance plan describes dates and scope of the maintenance and inspection activities carried out on a technical object (equipment or functional location).   These inspection activities on the equipment need to be tracked for various analytics purposes such as compliance reporting, asset replacement analysis, asset lifecycle maintenance history analysis, etc. The data from the maintenance plan call history forms the base for all this analysis.

2. Various ways in which maintenance plans can be configured in SAP ECC

There are various ways in which a maintenance plan can be configured in ECC. The below mentioned diagram outlines most commonly used configurations -

3. Understanding the relevant tables


 
 

4. Understanding the standard extractor

SAP provides 0PM_MAINTPOS_ATTR data-source with as a standard content. However this data source is more focused around the master/administrative data associated with the maintenance plans i.e. data from MPLA table. This extractor does not extract call history from MHIS. 0PM_MAINTPOS_TEXT is the text data-source for maintenance items.

5. FM based custom extractor

To suffice the reporting requirement on the maintenance plan call history, it is recommended to create a function module based extractor. The tables in scope for this FM based extractor can be MPLA, MMPT, MHIS, MPOS, MHIO, and OBJK. The below mentioned diagram suggests the join conditions between all these tables.
A dataset of join between MHIS and MPLA and then further joined on MPOS and MHIO, can then further be joined with OBJK to explode the object list. A look up MMPT is recommended to get the frequency texts as these are often required in the reports especially for multi-counter maintenance plans. This design will normalize the maintenance item level information at each object in the object list for that maintenance plan.

6. Delta enable for FM based custom extractor

Usually the data volumes are very high for maintenance plan call history data. Hence it is recommended to make the FM based extractor as delta enabled.   
Safety interval lower limit 1 is recommeded. Depending on the configuration, delta logic can be based on the combination of the following date fields -

MHIS-ABRUD: Date of the call

MHIS-HORDA: Call date

MHIS-FIXDA: Fixed/skipped on

MHIS- MANDA: Manual call date

MHIS- LRMDT: Date of last completion in maintenance plan (It is important to note that LRMDT will not get updated in MHIS table unless the next call is generated).

7. Recommended additional enhancements

 A. Conversion of maintenance plan call frequency

Usually time based maintenance plans are set for a yearly, monthly or weekly frequency. However the field MHIS-ZYKZT stores this frequency in seconds. It may be required to convert this into year, month or week depending on the unit for frequency of inspection that can be obtained from MMPT table.

B.  Derivation of next planned due date

The field MHIS-NPLDA stores the planned date for the maintenance plan call. It is often required by the business to report not only on the current planned date but also on the next planned date. Hence, it is recommended to stamp the NPLDA of the subsequent call on the previous call.

1 Comment

  1. Hi Chetan,

    Good document. we are having same requirement but for delta getting all data with our FM. Can you please share the FM code. In advance appreciate your help

    Regards,

    Ram