SAP EAM Data Migration Part 1 – Introduction
Hello to the SAP Community,
I am starting a series of blog posts around the migration of SAP Plant Maintenance data from SAP ERP Central Component (ECC) to SAP S/4HANA® Cloud. In this series you will learn some of the key table relationships, tricks, tips and processes for migrating your data using the files approach. I hope you will enjoy this series and learn what it takes to successfully migrate SAP Plant Maintenance data.
Links to future blog posts will be updated as they are published
Part 2 – Work Centers can be found with this link Part 2
Part 3 – Characteristics and Classes can be found with this link Part 3
Part 4 – Functional Locations and Equipment can be found with this link Part 4
Part 5 – Bills of Materials can be found with this link Part 5
Part 6 – Task Lists can be found with this Link Part 6
Part 7 – Maintenance Items and Plans can be found with this Link Part 7
Part 8 – Open Notifications (Future Topic)
Part 9 – Open Work Orders (Future Topic)
I was recently a team lead for the SAP Enterprise Asset Management work stream that was part of a larger effort to migrate a Customer from SAP ECC to SAP S/4HANA Cloud version 1709. Overall, it was a very successful go-live, though not without some stress and headaches. I am writing a series of blog posts to walk through in some detail the methodology that was used to extract, transform and prepare the objects/files for loading into the new system. This Customer did not use SAP Data Services, nor was the Team allowed to directly connect to the legacy system. This required us to use the Files method to migrate the data to SAP S/4HANA Cloud.
Hopefully you will find it to be an interesting journey and I hope you will tag along to see how it all ends up.
The General Process
The SAP S/4HANA Cloud Version 1709, SAP Data Migration Cockpit did not have all the SAP Plant Maintenance Data Objects that the Customer needed to use to migrate their data. A hybrid approach was undertaken to leverage what was available in the SAP Data Migration Cockpit and supplement with the SAP Legacy System Migration Workbench Tools as well as some Custom Development for the attachments to objects, open notifications and work orders.
Generally, the overall process involved the download of tables using transaction code SE16N and other transactions from the Legacy SAP ECC System for SAP Plant Maintenance business processes to local drives. Once downloaded, there were steps to review, sort, clean-up, transform and select the records relevant for the conversion. After the tables were scrubbed, further steps to link tables based on key field relationships, extracted the relevant data records, aligned the records for the load file templates and then populated the load files for upload into SAP S/4HANA Cloud using the combination of tools already discussed above. While the SAP Legacy System Migration Workbench Tools are no longer supported in SAP S/4HANA, some still worked and provided a way to augment the SAP Data Migration Cockpit. There was an extensive effort to test, validate and check the data converted using the SAP Legacy System Migration Workbench Tools to ensure the data was converted completely and correctly. Subsequent releases of SAP S/4HANA and the SAP Data Migration Cockpit expand the capabilities and provide a more robust tool.
EAM Data Objects Supporting the PM Business Process
PM Data Object Relationships
The following graphic shows the general relationships between some of the SAP Plant Maintenance Objects, master data (orange) and business transactions (green). It is similar to the above diagram and contains additional details and relationships to be considered. Not all of the objects are identified as the graphic would be too complex and the Customer did not use all of the objects,
Objects Extracted from SAP ECC
The following objects were extracted from the Legacy SAP ECC System.
- Work Centers
- HR Employee Assignment To Work Centers (Manually Created And Assigned in SAP S/4HANA Cloud)
- Characteristic Values assigned to the technical objects.
- Functional Locations
- Materials (Coordinated with the Materials Management Team)
- Equipment Bom
- Material Bom
- Functional Location Bom
- General Task Lists
- Equipment Task Lists
- Functional Locations Task Lists
- Maintenance Items
- Maintenance Plans
- Maintenance Plan Scheduling
- Open Notifications (Custom Extract and Load Program)
- Open Work Orders (Custom Extract and Load Program)
- Purchase Orders (coordinated with the Procurement Team)
- Attachments (Services For Objects)
- Long Text For Some Objects
This is the start of a series of blog posts that will go into further details regarding the relevant objects, tables extracted that were used for the migration process and the key table relationships. Not all SAP Plant Maintenance relevant objects were used by the Customer. The above list focuses on the ones that were relevant.
In the next blog post, A Journey in Data Migration Part 2 – Work Centers we will dive into the objects for the work centers, identifying the key relationships, tables and methods used to extract, clean-up and prepare the load files.
This series will not be a complete how to do every step needed, it is a collection of notes, comments, tips. and process steps from each object extracted to provide consistency and document what was done.This Document does not contain an exhaustive list of all the SAP Plant Maintenance Objects and how to extract them. This was based on a scope from a specific Customer, based on their needs and covers many of the core SAP Plant Maintenance objects that a typical conversion would need.
I hope you will stay tuned for further blog posts and I look forward to your comments, feedback and engaging conversations. Please follow my profile to get updates as new content is added.
Thank you and happy to share.
Thanks for Knowledge Sharing,We had a requirement to load the data for Quipmet task list and general task list .There is Standard templates available to load the data ,But for tasks list and general task list We want to load Service data in to SAP HANA .In standard template there is no fields available to map target system .So please let me know if there any bapi's to load or must we use LSMW OR custom Ltmc to develop to load this fields.
Thanks in advance.
That is a topic in an upcoming Blog Post. Stay tuned....
Wonderful article and the diagrams are outstanding.
Can you please explain the relationship between Characteristics and Measuring points & counters ?
Thanks in advance.
That is going to be included in a future Blog Post as part of the Functional Locations and Equipment.
Generally you use the characteristics to identify what you are measuring in the measurement point or counter. These can be either qualitative (Good, Normal, Bad) or quantitative (250 Deg F Operating Temp, 1000 rpm, 100 Miles, etc.) conditions The characteristics used for quantitative must be numeric. The measuring points can also be counters that drive scheduling of the maintenance plans. Code Groups are created for the qualitative characteristic values.
Basically in table IMPTT-ATINN = CABN-ATINN
Does that answer your question?
Thanks for the explanation Michael.
Yes, It answered my question and looking for more EAM articles..
Greetings for the day
Looking forward for your further blog post, Thank your time and information.
You are very welcome, enjoy.
Thanks for the effort Michael, really interesting. We are waiting for the next topics
Thanks for your insights Michael. What was the typical planning for this implementation? How long dit it take?
Original Project was scheduled for 9 months, actually took 12 months due to Customer constraints in other areas. The final migration for the Plant Maintenance functionality was done over a month prior to go live and we migrated data sequentially, with the open work orders and notifications the last pieces prior to scheduling all of the maintenance plans. It could have all been faster, however we had minimal resources available, which extended the activities.
Thanks Michael. Therefore, this means that the original project was scheduled, between the Core Model design + Testing + Roll out in Production in 9 months. Right?
Really wonderful document
Thanks for Sharing
Waiting for your new Blog
You are very Welcome, Glad you enjoyed. Please look at the othe Blogs and I hope to add more soon.
Thanks you for your sharing knowledge !
Thank you and enjoy the series.
Thanks for this great summary, however, I have a question for the Future - Part 9 topic abpout Work Orders.
We have a program to migrate Work Order data, but we face an issue with the task lists: we have task lists and we have the operations from the source system. When calling the BAPI_ALM_ORDER_CREATE we receive the error message Please choose another operation. By debugging we have found out that this error comes up because we have 0010 operation ID (among others) in the operations list, however, the BAPI seems to have added already an operation with 0010, and therefore we receive this error. This, however, has already been solved.
Currently we can migrate the WOs provided that we do not specify the task list for the BAPI. But we should store also the Task list ID to be displayed in IW33.
So we have added it to the corresponding AFKO fields. CHecked the database table, the values are stored to PLNTY, PLNAL amd PLNNR, but the transaction does not show it.
Which other table(s) should it be added to for the transaction to show it?
Check structure CAUFVD that is where it is pulling it from the work order.
Best of luck.