How to upload Transactional Data from Legacy to SAP system

January 3, 2010 by mySAP
Filed under: SAP Tip

How to migrate huge volume of Sales Orders (1,000), Purchase Orders (2,000), Production Orders (500) to the new SAP system?

What I know is to have the open orders be created to the new SAP system, however if these are too many, how can I maintain in the new system?

It is common in migrations (from legacy to SAP) to create new order types, exclusively for converted orders (orders that existed in the legacy system at the time of conversion) and assign an external number range to the new order types.

This way, you can use the same or similar order numbers that were used in the old system. You still use the equivalent of VA01, because they are new orders in the SAP system. Remember, your customers and vendors will still want to talk to your company in terms of the old order numbers.

Also, you would be well advised not to use an LSMW recording to create Sales docs, unless your legacy sales orders are very simple and uniform. In most companies, you will have to migrate order partners (soldto/shipto/billto/payer/carrier, etc etc.) You will have to migrate order texts (comments), you will have to migrate order prices, you will have to migrate order dates/qtys/material/customer material), etc, for all your sales docs.

A recording will give you endless problems dealing with the differences in each order in this case. Better instead to use LSMW Direct input (object 0090 program RVINVB10). I will admit that this is a tough LSMW program to learn, but it is the best to use during execution.

Alternatively, the volume of sales orders you speak of is not outside the realm of manual load. If a client came to me and asked me to spec out such a task, I would give him two options, of hiring a small team of clerks to manually enter the orders or of having a skilled IT professional perform the tasks of research, create the LSMWs, test them, and executing the load during go-live. Considering that clerical wages are low, and IT professional fees are high, it might be cheaper for the client to go ‘manual’.

Although a mass migration is a big task, it can easily be broken down into discrete subtasks. You have mentioned transactional data, but you haven’t mentioned master data, which is also a substantial problem in a new system.

Don’t even think about loading TX data until the master data has been cleaned, verified, and loaded, and verified again. This of course all takes place AFTER the system has been configured to meet the requirements of your business users.

If this is your first migration, and there is noone on your implementation team that has done a migration before, you would be well advised to hire a consulting company to guide you through the process.

Solution by Dogboy49, http://forums.sdn.sap.com/profile.jspa?userID=3483110