SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Need help on guidelines to load data into SAP ISU :: Data Migration

Former Member

‎2014 May 22 12:22 PM

0 Kudos
337

Scenarios:

  • Data Volume is 3 TB
  • Customer has 24 million sites
  • More than 450 million of Meter Readings
  • Customer's legacy data contains information for last 20 years
  • The 20 years of data is full of various scenarios like Meter Exchanges, Removals, Move In, Move Outs, various types of Invoices etc.

Issue:

  • There is no clarity on scope of data to be migrated into SAP ISU.

Help required from SAP

  • Is there a standard guideline from SAP which defines how much data to load as part of data migration?
  • The main objective is to make sure after data migration SAP does not get overload with data and should not impact the performance of SAP ISU.


3 REPLIES 3

TammyPowlas
Active Contributor

‎2014 May 22 12:33 PM

0 Kudos
202

Not sure SAP has guidelines but typically you don't migrate all that history into SAP

Usually you store the history somewhere else, like a data warehouse

We only migrated historical meter readings (1 year old +) as they were needed for a peak billing calculation - that's it

I also recommend using the SAP RDS Data Migration Solution using Data Services - it does the heavy lifting for you.

Good luck

william_eastman
Product and Topic Expert
Product and Topic Expert

‎2014 May 22 6:18 PM

0 Kudos
202

Are you only asking in regards to meter reading history - or history in general?

For meter readings: If the history is required - then maybe migrate it to a custom table, or into a data warehouse.  Under no circumstances would we recommend converting that much history into standard tables - it would affect performance and would not provide any functional benefit.

regarding general history - in order to convert some of that data, you would be required to create historical configuration of many areas as well - and that is quite an effort, which generally nobody would undertake.

daniel_mccollum
Active Contributor

‎2014 May 22 10:49 PM

0 Kudos
202

Draw a line in the sand, create a green fields model of the customer base, & follow the EMIGALL object priority for creating the required objects to continue BAU after implementation.

Anything more detailed than that recommendation is more of a consulting issue.

Good luck