topic Re: LSMW Data Migration in Application Development and Automation Discussions

LSMW Data Migration

Former Member — Wed, 17 May 2006 16:19:25 GMT

Hello Gurus

Can anyone tell me if it's possible to perfectly migrate the complete document flow from sales to accounting for documents that have already been billed?

That is, we want to load a new system with existing data from an older SAP version. Can we load old sales orders, along with the old billing and accounting documents, and keep all of the dates as they are {in the past}? How would you replicate a sales order that contains a reference to a billing document, if the billing document doesn't yet exist?

Can anyone provide any insight as to how I might do this? The SLO group is not an option {too expensive}.

I've been experimenting with the LSMW, which will work well for master data. I'm struggling with how to proceed with transaction data.

Any insight appreciated,

Lee

Re: LSMW Data Migration

Former Member — Wed, 17 May 2006 16:33:41 GMT

Hi Lee,

This would be my approach.

All important documents like orders, deliveries, invoices etc. are linked to SAP standard idoc types(intermediate documents) and message types. SAP also provides inbound and outbound programs to import and export the same for every version of SAP.

Versions of idoc types are compatible and it is possible to work with older versions of idoc types in newer systems.

So the steps that would be help is

1: Export all documents in current version into idocs.

2: Import these into newer version via idocs.

Not much coding is required in this approach as programs on both the inbound and outbound are provided by SAP.

Regards,

Anand.

Re: LSMW Data Migration

Former Member — Wed, 17 May 2006 17:12:50 GMT

Thanks Anand

What I'm still a little stuck on is this:

All of the 'old' orders I want to move in are of course already billed, transferred to accounting, paid and cleared.

I want to completely replicate the document flow, so that it is as accurate as my current system. Is it possible? Or would I need to recreate the sales orders (via idoc or other), and then rebill everthing using dates in the past, and then pay and clear again?

Can I use Idocs to move in all of the documents in the chain?

Re: LSMW Data Migration

Former Member — Thu, 18 May 2006 05:09:05 GMT

It is not needed that one create only the basic order document and create the rest of the document flow online.

Although I havent worked on this scenario, there is nothing that states the one cannot create a delivery for an SD order via idocs.

Both online transactions and Idocs may create the same order, billing docs etc. Therefore they must have the same capacity of maintaining document flows.

There may be a requirement to code a couple of user exits to reflect the exact flow as in the 'old' system; other than that I dont see any blocks to this process.

Re: LSMW Data Migration

Former Member — Thu, 18 May 2006 05:42:58 GMT

Hi lee,

i think serialization of message types will help you in this regard.place the message types in the sequence in the manner you want to create sales order then delivery then billing and so on. i think this will help you.

Re: LSMW Data Migration

Former Member — Thu, 18 May 2006 05:47:35 GMT

Hai Lee

I will send you How to Upload Material Data through LSMW Direct Input Method

You Just Follow the steps as given Bellow

Using Tcode MM01 -- Maintain the source fields are

1) mara-amtnr char(18)

2) mara-mbrsh char(1)

3) mara-mtart char(4)

4) makt-maktx char(40)

5) mara-meins char(3)

the flate file format is like this as follows

MAT991,C,COUP,Srinivas material01,Kg

MAT992,C,COUP,Srinivas material02,Kg

AMT993,C,COUP,Srinivas material03,Kg

MAT994,C,COUP,Srinivas material04,Kg

MAT995,C,COUP,Srinivas material05,Kg

goto Tcode LSMW

give Project Name

Subproject Name

object Name

Press Enter -

Press Execute Button

It gives 13 radio-Button Options

do the following 13 steps as follows

1) select radio-Button 1 and execute

Maintain Object Attributes

select Standard Batch/Direct Input

give Object -- 0020

Method -- 0000

save & Come Back

2) select radio-Button 2 and execute

Maintain Source Structures

select the source structure and got to click on create button

give source structure name & Description

save & Come Back

3) select radio-Button 3 and execute

Maintain Source Fields

select the source structure and click on create button

give

first field

field name matnr

Field Label material Number

Field Length 18

Field Type C

Second field

field name mbrsh

Field Label Industrial Sector

Field Length 1

Field Type C

Third field

field name mtart

Field Label material type

Field Length 4

Field Type C

fourth field

field name maktx

Field Label material description

Field Length 40

Field Type C

fifth field

field name meins

Field Label base unit of measurement

Field Length 3

Field Type C

save & come back

4) select radio-Button 4 and execute

Maintain Structure Relations

go to blue lines

select first blue line and click on create relationship button

select Second blue line and click on create relationship button

select Third blue line and click on create relationship button

save & come back

5) select radio-Button 5 and execute

Maintain Field Mapping and Conversion Rules

Select the Tcode and click on Rule button there you will select constant

and press continue button

give Transaction Code : MM01 and press Enter

after that

1) select MATNR field click on Source filed(this is the field mapping) select MATNR and press Enter

2) select MBRSH field click on Source filed(this is the field mapping) select MBRSH and press Enter

3) select MTART field click on Source filed(this is the field mapping) select MTART and press Enter

4) select MAKTX field click on Source filed(this is the field mapping) select MAKTX and press Enter

5) select MEINS field click on Source filed(this is the field mapping) select MEINS and press Enter

finally

save & come back

6) select radio-Button 6 and execute

Maintain Fixed Values, Translations, User-Defined Routines

Create FIXED VALUE Name & Description as MM01

Create Translations Name & Description as MM01

Create User-Defined Routines Name & Description as MM01

after that delete all the above three just created in the 6th step

FIXED VALUE --MM01

Translations --MM01

User-Defined Routines --MM01

come back

7) select radio-Button 7 and execute

Specify Files

select On the PC (Frontend) -- and click on Create button(f5)

give the path of the file like "c:\material_data.txt"

description : -

separators as select comma radiao- button

and press enter save & come back

😎 select radio-Button 8 and execute

Assign Files

Save & come back

9) select radio-Button 9 and execute

Read Files

Execute

come back

10) select radio-Button 10 and execute

Display Imported Data

Execute and press enter

come back

Come back

11) select radio-Button 11 and execute

Convert Data

Execute

come back

Come back

12) select radio-Button 12 and execute

Display Converted Data

Execute & come back

13) select radio-Button 13 and execute

Start Direct Input Program

select the Program

select continue button

go with via physical file

give the lock mode as 'E'

and execute

Thanks & regards

Sreenivasulu P

Re: LSMW Data Migration

Former Member — Thu, 18 May 2006 06:02:45 GMT

I just got another idea that might help. It would be worth investing in creating a new idoc type that combines the entire flow. Thus one such idoc represents not just an order or delivery, but the entire cycle of oredr-delivery-GI-Billing-Accounting.

Such an idoc would either succesfully create the entire flow or fail. You would also have an effective tracking of documents created in processing logs.

This is a lot more development, but it makes the process smoother and practically controllable.

Regards,

Anand.

Re: LSMW Data Migration

Former Member — Fri, 19 May 2006 13:28:00 GMT

Thanks everyone for your help. Much appreciated. When I arrive at a solution, I'll update the thread.

Cheers,

Lee