Skip to Content

Data Migration for Utilities – Step 1 – Data Profiling

This blog is a follow up to my previous blog on data migration in the Utilities Industry.http://Migration in Utilities Industry

Before we start the migration we need to identify the Data Migration tools which comes along with the SAP system. In the case of the SAP IS-Utilities package we have 2 chief tools

1.ISMW – Industry Solutions Migration Workbench.
This contains separate migration objects which correspond to separate business entities of the Industry solution (in our case the Utilities solution specific objects e.g. installation, move-in)

2.LSMW – Legacy System Migration Workbench.
This is the standard migration workbench which appears with the SAP R/3 core solution and has migration objects specific to the R/3 solution.

These are two specific tools which can be used for migration. In case these tools do not match our requirements we do have other options to fall back on like custom programs and reports.

 As mentioned earlier the first step in the Data Migration process is to profile the data.

Now what are the steps involved in Data Profiling.

1.    Identify the business streams.

With the help of the BPDD and the project plan we can identify the individual streams which define the various business processes. These streams individually demarcate the borders for the end to end solution.
Typically for an SAP IS-U Solution with SAP CRM on one end we would have the following streams.
1.    CRM – Customer Relation Management
2.    CS – Customer Service
3.    MET/TAM – Metering/Technical Asset Management
4.    BIL – Billing
5.    FICA – Finance with Contract Accounting

These streams have individual processes which start from getting a customer to receipt of money for services provided.The identification of streams also helps us to identify the team responsible for the business processes.

2.    Identify the migration objects per stream.
Now that we have the stream identified we need to have some sessions between the business process owners of the stream and the data migration team to identify the various objects which need to be migrated for the particular stream. This can be done using a two pronged approach.
1.    Identify which of the SAP standard objects need to be migrated. We take the list of the standard migration objects from ISMW and LSMW for the relevant stream and confirm with the business owners which are required for the solution.
2.    Identify the custom solutions built and choose whether it can be resolved by the modification of standard objects or we need to develop a custom solution .
This list is then updated per stream.

3. Find the cross stream dependencies.

Identify how the migration objects link up to each other and the dependencies upon the other migration objects. This can be done by having a session with all the business streams to understand how the processes are linked up.

4. Prepare a Object Sequence Document.

The migration objects after having identified the cross stream dependencies now need to be linked up. This would be useful in identifying the order in which we can migrate, how many we can migrate in parallel and how they are linked up.

I have found that DSM lists are quite useful in this regards. You can also set up a Visio diagram like the one below for better visual understanding.

5. Source System Identification

Once your migration objects have been identified and the sequence as well. We need to identify the source systems as well. This is a good time to have a workshop with the client to identify the various source systems from which the data is to be picked up. This will also help identify the Cutover strategy that would necessitate the blackout of systems and is quite crucial in large scale implementations.

You have now completed the first step of a migration process where you have identified your migration objects (building blocks) and you have also now identified your overall design on your migration approach.

Now keep looking at this space for the next steps in migration. Funny how new resolutions are at their most strongest while leading up to the new year but quickly forgotten afterwards.

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

    I am also a Wiproite and currently working on IS-U project.I  am interested to know how did you handle in-flight/incomplete transactions with the legacy system during migration events. did you use standard emigall objects for migrating incomplete transactions or have you built any custom objects for maintaining switch document status

    appreciate if you could share your experiences in this area please?