topic Re: Data migration procedure and guildlines in Application Development and Automation Discussions

Data migration procedure and guildlines

Former Member — Wed, 28 Jun 2006 02:00:30 GMT

Hi Guys,

Is there any person have experience in doing a new data migration project?

I need to know the steps in detail like which module going to upload to SAP system first, the test plan after migration....

Btw, I also need to know which data or field that need to be maintain first...for example when I create customer master, what kind of information that I need to maintain before I am able to create customer records.

Furthermore, I also wish to know how I can find out all the mandatory fields that I needed to be maintain when I doing my migration in SAP.

Hope that got expert out there can give me some steps, hints, tips and way to carry the migration project.

Your help will be very much appreciated.

Best regards,

rukawaw

Re: Data migration procedure and guildlines

abdul_hakim — Wed, 28 Jun 2006 02:09:30 GMT

hi,

steps to be carried out for data migration.

1.Ensure that whether u r going to do one time transfer or frequent data transfer.One time transfer includes transferring master data and frequent data transfer includes transactional data.

2.Analyse the legacy data and identify the source from where it is coming from.

3.Record the corresponding SAP Transaction to know about the details like screen sequence,screen program name,screen field name,mandatory fields etc.

4.Generate the program based on the recording.

5.Read the data from your legacy system.Depends on whether the data is in presentation/application server you could use either GUI_UPLOAD/OPEN DATASET variants.

5.Convert the data into SAP format.

6.Replace the values from your recording with the value converted in SAP Format.

7.Finally you could do the transfer using either Session/Call transaction techniques.

8.You could also use LSMW for master data transfer as it is not suited for frequent data transfers.

Cheers,

Abdul Hakim

Re: Data migration procedure and guildlines

Former Member — Wed, 28 Jun 2006 02:31:00 GMT

Hi Hakim,

Thanks for replying.

1 more question to ask. How we can rectify the mandatory fields that need to be maintained in SAP? reading the documentation inside BAPI?

Re: Data migration procedure and guildlines

Former Member — Wed, 28 Jun 2006 02:57:28 GMT

I did this a loooong time ago.

You have to decide whether or not you actually want to upload all of your old data. In a legacy system, there will be data integrety issues. If you simply upload all of the old data, you will be copying a lot of your old problems.

Whether you upload or create new, you will need master data first (customers, vendors, GLs, cost centers, etc, etc.) We found it useful to create a table that linked the data from the old system to the new SAP system. For example, in the old system, GL 1-234-567-89 translated to GL 112233.

We converted in the middle of a fiscal year but we didn't copy over all of the FI transactions. We simply created a single transaction that copied the balance of each account.

To migrate customers, vendors or FI transactions, there are a number of standard SAP programs to take care of this for you (RFBIBL00 for FI transactions).

We can't tell you which fields are mandatory. A lot of this is controlled by configuration and will be particular to your system. You will have to go to your functional people and ask them.

Rob