cancel
Showing results for 
Search instead for 
Did you mean: 

LMSW u2013 how to import (load) a file

Former Member
0 Kudos

Hello all,

ECC6.0

I have an excel file with all customer data.

I have created my recordings in LSMW and now I need to know: How do I import the file in LSMW transaction?

Please explain me detailed steps because I am raw in LSMW.

In LSMW is it possible to import an EXCEL file? Do I have to do anything special to import u201C.xlsu201D files?

Or is it just possible to import (in LSMW) a u201C.txtu201D file?

Many thanks,

Barbara

Accepted Solutions (1)

Accepted Solutions (1)

Manoj_Mahajan78
Active Contributor
0 Kudos

Dear Barbara,

See below links for LSMW details-

For information regarding LSMW steps visit the following link:-

http://www.sap-img.com/abap/upload-direct-excel.htm

http://www.sap-img.com/abap/excel_upload_alternative-kcd-excel-ole-to-int-convert.htm

http://www.sapdevelopment.co.uk/file/file_upexcel.htm

www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc

http://www.allsaplinks.com/lsmw.html

http://help.sap.com/bp_blv1500/BL_US/html/dataconv_lsmw.htm

steps-

Advantages of LSMW:

u2022 Most of the functions are within R/3, hence platform independence.

u2022 Quality and data consistency due to standard import techniques.

u2022 Data mapping and conversion rules are reusable across projects.

u2022 A variety of technical possibilities of data conversion.

u2022 Generation of the conversion program on the basis of defined rules

u2022 Interface for data in spreadsheet format.

u2022 Creation of data migration objects on the basis of recorded transactions.

u2022 Charge-free for SAP customers and partners.

Working With LSMW:

Use TCODE LSMW

Objects of LSMW:

u2022Project u2013 ID with max of 10 char to Name the data transfer project.

u2022 Subproject u2013 Used as further structuring attribute.

u2022 Object u2013 ID with max of 10 Characters, to name the Business object .

u2022 Project can have multiple sub projects and subprojects can have multiple objects.

u2022 Project documentation displays any documentation maintained for individual pop ups and processing steps

User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.

Object type and import techniques:

u2022 Standard Batch / Direct input.

u2022 Batch Input Recording

o If no standard programs available

o To reduce number of target fields.

o Only for fixed screen sequence.

u2022 BAPI

u2022 IDOC

o Settings and preparations needed for each project

Preparations for IDOC inbound processing:

u2022 Choose settings -> IDOC inbound processing in LSMW

u2022 Set up File port for file transfer, create port using WE21.

u2022 Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.

u2022 Setup partner type (SAP recommended u2018USu2019) using WE44.

u2022 Maintain partner number using WE20.

u2022 Activate IDOC inbound processing.

u2022 Verify workflow customizing.

Steps in creating LSMW Project:

u2022 Maintain attributes u2013 choose the import method.

u2022 Maintain source structure/s with or without hierarchical relations. (Header, Detail)

u2022 Maintain source fields for the source structures. Possible field types u2013 C,N,X, date, amount and packed filed with decimal places.

u2022 Fields can be maintained individually or in table form or copy from other sources using upload from a text file

u2022 Maintain relationship between source and target structures.

u2022 Maintain Field mapping and conversion rules

u2022 For each Target field the following information is displayed:

o Field description

o Assigned source fields (if any)

o Rule type (fixed value, translation etc.)

o Coding.

o Some fields are preset by the system & are marked with Default setting.

u2022 Maintain Fixed values, translations, user defined routines u2013 Here reusable rules can be processed like assigning fixed values, translation definition etc.

u2022 Specify Files

o Legacy data location on PC / application server

o File for read data ( extension .lsm.read)

o File for converted data (extension .lsm.conv)

u2022 Assign Files u2013 to defined source structures

u2022 Read data u2013 Can process all the data or part of data by specifying from / to transaction numbers.

u2022 Display read data u2013 To verify the input data being read

u2022 Convert Data u2013 Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.

u2022 Display converted data u2013 To verify the converted data

Import Data u2013 Based on the object type selected

u2022 Standard Batch input or Recording

o Generate Batch input session

o Run Batch input session

u2022 Standard Direct input session

o Direct input program or direct input transaction is called

BAPI / IDOC Technique:

u2022 IDOC creation

o Information packages from the converted data are stored on R/3 Database.

o system assigns a number to every IDOC.

o The file of converted data is deleted.

u2022 IDOC processing

o IDOCS created are posted to the corresponding application program.

o Application program checks data and posts in the application database.

Finally Transport LSMW Projects:

u2022 R/3 Transport system

o Extras ->Create change request

o Change request can be exported/imported using CTS

u2022 Export Project

o Select / Deselect part / entire project & export to another R/3 system

u2022 Import Project

o Exported mapping / rules can be imported through PC file

o Existing Project data gets overwritten

o Prevent overwriting by using

u2018Import under different name

u2019

Regds

MM

Edited by: MANOJ MAHAJAN on Dec 10, 2008 4:06 PM

Answers (3)

Answers (3)

Former Member
0 Kudos

Sorry I haven't replayed before.

All answers helped me to search the right solution for my issue.

Thanks all,

Barbara

Former Member
0 Kudos

Dear Barbara,

There are 2 ways for transporting LSMW data from a system to another.

1.1 Export/import

This method gives you the opportunity to select the subprojects or objects you want to transfer. Hence you don't transfer the object a colleague might have created and that should stay in development system.

LSMW -> Extras -> Export project

1.2 Transport request

With this method, you can transport a LSMW project in full (you can not select the objects you want). With this method, the project will be transported as any other SAP object in a transport order.

LSMW -> Extras -> Create change request

Best Regards,

Amit

Note: Few reference:

[LSMW - Useful|http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc]

[LSMW|http://www.sap-basis-abap.com/sapgeneral/step-by-step-legacy-system-migration-workbench-lsmw.htm]

[SAP Help - LSMW|http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm]

Lakshmipathi
Active Contributor
0 Kudos

Check this link

[LSMW Steps|http://www.sapbrainsonline.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html]

thanks

G. Lakshmipathi

Former Member
0 Kudos

Thanks,

But this link is blocked for me. Most web links are blocke here where I am.

Barbara