LSMW procedure

Hi
Could Anybody guide me the LSMW procedure step by step. to uplad the data from notepad to R/3
thank u
regards
sesidhar
Edited by: Somnath Manna on Sep 18, 2008 5:59 AM

Hi,
Please refer this link,
LSMW - Step by Step
[LSMW procedure|http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc]
http://www.sapgenie.com/saptech/lsmw.htm
http://service.sap.com/lsmw
http://www.sapbrain.com/TUTORIALS/TECHNICAL/LSMW_tutorial.html
Hope it will help you.
Regards,
R.Brahmankar

Similar Messages

LSMW procedure for PP master data

Hi
i have some doubts regarding LSMW .... can we upload PP master data BOM,Resource,MasterRecipe and Production versios through LSMW. could u pls guide me in this issue.
Regards
hgvd

Hgvd,
You will create the procedures. I have never seen detailed procedures published for all possible LSMW scenarios, probably because, they are always different for each project..
Every Data requirement is different, based upon the business requirements. The LSMW project concept is pretty intuitive, so even without much training, a novice can create data upload functionality. Read the docs previously quoted in this thread, and if you want more detail, try the old online word doc at
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000455036&_SCENARIO=01100035870000000112&_OBJECT=011000358700000728862003E
Although this doc is for an old version of LSMW, it is particularly useful for a novice, since it contains so much detail. There is some added functionality is later versions of LSMW, but for the objects you have mentioned, this doc should suffice.
Best Regards,
DB49

Problem with LSMW ?

Hi all,
i have a dought regarding can we use <b>Batch session</b> and <b>call transaction</b> methods in LSMW ?

Hi,
LSMW does not supports call transaction methods.
It supports only Batch input session, Recording, BAPI & Idoc methods.
Following are the steps to create the LSMW Procedure through Batch Input Session Method.
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
8) select radio-Button 8 and execute
   Assign Files
   Save & come back
9) select radio-Button 9 and execute
   Read Files
   Execute
   come back
   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
Regards
Sreeni

Mass PO Change By LSMW

Hi Gurus,
I want the LSMW procedure to mass change the PO. Suppose to change the multiple line items or Price of each line item.
Plz suggest.
Thanks & Regards
Akshay

Hi
Please create a BDC for Changing of Purcahse Orders, even this is not possioble using LSMW.
Thanks & Regards
Kishore

Screen shots of lsmw using bapi and idoc.

hi
can anybody plz send me the step by step lsmw procedure using
bapi and idoc screen shots.
regards
vijay

Refer this link... it has step by step procedure with screen shots....
http://www.****************/Tutorials/LSMW/LSMWMainPage.htm
Regards,
Pavan

Transferring open items and balances

Hello!
Do anyone know if there are SAP tools for the transfer of Account Receivables (AR), Account Payables (AP) open items and General Ledger (GL) balances from old SAP environment 4.6C to newer SAP environment 6.0?
What should be considered when doing this procedure; what tasks should be done in source client, what tasks should be done in target client?

Hi,
There is no interface where you can transfer balances or any other master data from lower version to higher....this is altogether different.
If you want to do so ..you have to follow the normal LSMW procedure for uploading the balances ..extracting the same from the lower version i., 5.0
Assign points
Zia

Need help in FM used in IDOC

Hi experts,
Need help with IDOC. I'm creating 2 FM to process an existing idoc.
first FM will use the data from idoc 1 to populate EDIDD for idoc 2.
second FM will use the data from idoc 2 to populate EDIDD for idoc 3.
when during processing, I encountered error message "No function module for input process code <second FM>".
although i already link the FM to be used, why does FM 1 cannot call FM 2 directly?
Thanks.

In LSMW object attributes... give like this..
Message Type CREMAS Vendor master data distri
Basic Type CREMAS04 Vendor master data distri
Enhancement
after that continue normal LSMW procedure.

Need help in IDOC Creation

Hi Guys,
I need to create a Vendor Master using LSMW via IDOC Process..What are all the points needs to consider..
Thanks
Prabhu

In LSMW object attributes... give like this..
Message Type CREMAS Vendor master data distri
Basic Type CREMAS04 Vendor master data distri
Enhancement
after that continue normal LSMW procedure.

Stock upload conversion program

Hello Experts,
I have few questions below.
What is the case that we require to do a BDC program for stock upload? What is the difference of using LSMW Vs BDC?
I have about 500 materials and need to upload the stock into SAP from external excel file and need to move them into physical bins.
Do I need to develop a conversion program for LSMW to full fill my requirement.I am asked to write a functional spec for stock upload.Please help..
Do i need a seperate conversion program for stock transfer from 998 storage to physical bin?I should also print the SU labels during this program.
Please explain the process.
Thanks for your time in advance.
Edited by: RKsap193 on Oct 13, 2008 12:28 PM

If you send your personal email than i can send you the document with screen shot.
Here is the complete step bu step process to load initial stock with LSMW
you can use LSMW or BDC program
LSMW can eb designed by analyst and BDC can be desined by ABAPer
I did not find any documentation describing scenario of initial stock entry of material to HU & WM managed storage location. It inspired me to write this wiki.
I use the following scenario of loading initial stock entry:
u2022     Creation of inbound delivery using standard batch input import method - program RM07MMBL with following tip:
o   Input file from legacy system is prepared it such a way that one line contains information about one palette (or other packing materials) and storage bin coordinate.
o   In the standard field MTSNR (Material slip) storage bin coordinates information is recorded.
o   Field MTSNR is transferred to field LIKP-LIFEX (External Delivery ID)
u2022     Creation of transfer order in reference to inbound delivery using batch input recording of transaction LT03
o   Field NLPLA (Destination Bin) is read using simple ABAP code from delivery header - LIKP-LIFEX
To create transfer order for inbound delivery in transaction LT03, material in inbound delivery must be packed, i.e. handling unit must be created. It can be archived by using an automatic packing functionality (packing instruction and packing instruction determination).
After TO confirmation the goods receipts can be posted for deliveries.
Standard output can be generated for handling unit using message type E128 (EAN128 sticker). If needed storage bin information can be printed to simplify label sticking on palette or other packing materials in the warehouse complex.
In this scenario homogeneous materials are packed into one handling unit.
Step 1: LSMW for initial stock entry in MM using 561 movement type:
This is the well known standard LSMW procedure which use standard batch input import method - program RM07MMBL .
1a. LSMW Process steps:
I apply only following tip: in the standard field MTSNR (Material slip) storage bin coordinates information is recorded.
1b. Maintain Source Fields LSMW process (step No. 3):
1c. Input file - example:
1d. Create batch input session LSMW (step No. 14).
It is important to set "1" for Max. number of items. It ensures that one delivery is created per one input line.
1e. Log sample from batch input session.
1f. Inbound delivery monitor - transaction VL06I
Selecting deliveries for Putaway you can control deliveries created in preceding step
Each delivery is packed:
and output - message type E128 is created:
Step 2: LSMW for transfer order creation in reference to inbound delivery:
This LSMW procedure is based on batch input recording of LT03 transaction.
2a. LSMW Process steps
2b. Maintain Source Fields LSMW (step No. 3).
Deliveries numbers can be simply generated to input file form inbound delivery monitor (see 1f step)
There is no need to fill LGTYP (Storage type) and LGPLA (Storage section) because these fields are derived in LT03 transaction from storage bin - LGPLA (only if LGPLA is unique for all storage types and storage section - LAGP table).
2d. Display Read Data LSMW (step No. 10)
2e. Run Batch Input Session (step No. 14)
Log from the batch input session:
LT23:
I have customized the system to automatically confirm TO. Finally all HU are put away.
Tip & Trick
You can confirm TO using RF devices (standard transaction LM02) while label sticking on a palette.
Last step is to post GR for inbound deliveries which were put away. It can be done collectively in inbound delivery monitor by selecting deliveries for goods receipt:
Summary
u2022     Easy to implement: two simple LSMW scenarios (one with few ABAP lines)
u2022     Standard message type for label printout with information about storage bin coordination
u2022     Possibility to analyze correctness of data migration in inbound delivery monitor before posting GR
u2022     Possibility to confirm label sticking with RF transaction
u2022     This scenario can be adapted for non homogeneous HUs

BDC/LSMW for SPRO to MM to Purchasing to PR to Release Procedure to ...

Hi experts,
May I know those screen in SPRO can do BDC or LSMW? I am facing problem on trying up the BDC using SM35 on the following screen. (I can't get the transaction code).
The path is:
SPRO -> MM -> Purchasing -> PR -> Release Procedure -> Set up Procedure With Classification -> Release Strategies.. The SAP program is SAPL0ME2, but I can't execute it using SE38 since it's a program Type 'F'.
So may I know any possible way for us to use recording approach on these to do Mass insertion of data?
Thanks.
Cheers,
Wong
Edited by: Julius Bussche on Sep 12, 2008 10:37 AM

Hi Vijay,
First, you can try on SM30, V_T16FS. Simply double-click on 1 release strategy, then Click on "Classification". You will see the classification screen allow us to enter value on each characteristic of the class.
However, I try using SHDB (recording), it shows empty screen on the value for class in the 'Classification' screen.
Thanks.
Cheers,
Isaac.

LSMW step by step procedures

Hello Gurus,
Can anybody please provide the LSMW step by step procedures for
1. Business Partners
2. Material Master
3. Vendor Master
4. Inventory Balances
5. Purchasing Info Records
Thank you very much

Hi
http://www.sapgenie.com/saptech/lsmw.htm
http://service.sap.com/lsmw
http://www.sapbrain.com/TUTORIALS/TECHNICAL/LSMW_tutorial.html
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://www.esnips.com/web/LSMW
blog
/people/hema.rao/blog/2006/09/14/lsmw--step-by-step

Lsmw Step by step procedure

Hi Abap Gurus,
I very new to abap and this site.
Can any body provide the step by step procedure in lsmw.
I can give points to good answers.

Hi rangamma,
can U go through this info.
Step-by-Step Guide for using LSMW to Update Customer Master Records
Note! The screenprints in this article are from IDES Release 4.6. They may differ slightly in other versions.
Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC as shown in Figure 1.
Figure 1                Conversion Task with Project, Subproject and Object
The main screen of LSMW provides wizard-like step-by-step tasks, as shown in Figure 2. To complete your data conversion, you need to execute these steps in sequence. Once a step is executed, the cursor is automatically positioned to the next step.
Note that these steps may look different depending upon your Personal menu settings. You could make step numbers visible by Numbers on icon or hidden by Numbers off icon. You can execute a step by double-clicking on the row. Toggle icon Doubleclick=Display or Doubleclick=Edit, makes the step in display mode or change mode.
Figure 2 LSMW Wizard initial screen
Step 1: Maintain Object attributes
In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
Figure 3                Object type Transaction Recording
The system calls the transaction code XD02 and prompts you to complete the Change
Customer transaction, as shown in Figure 4. Enter the key customer information (I entered customer number 1000, sales organization 1000, distribution channel 01, and division 00) and choose Sales view within Sales area data. Make changes to these three fields (I entered, sales office 1010, sales group 110, and customer group 01) and save the transaction.
Figure 4                Transaction recording for Transaction Code XD02
Once the transaction is completed, R/3 records the flow of screens and fields and saves the information, as shown in Figure 5.
Default Values
Field Names
Figure 5                Transaction recording overview
Note that the fields are populated with default values. The values you entered when you recorded the transaction are set by default.
Note that if you have more fields in the recording than needed, you can remove them by clicking Remove Screen field icon.
Observe that the transaction-recording process stores field names in a technical format. By pressing the F1 key on individual screen fields and then pressing the F9 key, the system displays technical names. You then can replace the technical names with descriptive names. Double-click on the field RF02D-KUNNR and enter the name as KUNNR and the description as Customer Account Number and remove the default value. (See Figure 6.)
Figure 6                Field attributes
Similarly, double-click on all other fields with default values and make appropriate changes. Once you have made changes, the recording overview screen looks like what you see in Figure 7.
Figure 7                Transaction Recording Overview with screen field attributes
Save your changes. When you go back to the initial screen, you will see that the initial screen steps have changed. Since you want to import data via the BDC method, the Direct Input and IDoc-related steps are hidden, as they are not relevant.
Step 2. Maintain Source Structures
Give a name and a description to the source structure (Figure 8).
Figure 8                Source Structure
Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest way is to click on Table Maintenance icon to enter Fieldname, Type and Length for each field as shown in Figure 9.
Figure 9                Source fields of source Structure
Note that your input file will have four fields as key fields and you need to update three fields in the system.
Step 4: Maintain Structure Relations
Execute a step to Maintain Structure Relations. (See Figure 10.) Since, there is only one Source and Target Structure, the relationship is defaulted automatically.
Figure 10 Structure Relation
Step 5: Maintain field mapping and conversion rules
Field RF02D-D0310 represents that you chose Sales view for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of X.
If your source file already has the field value, you choose rule Source Field.
Keep cursor on field KUNNR and click on Assign Source field icon to choose source field CUSTOMER from structure XD02S as shown in Figure 11.
Figure 11 Assign source fields
Similarly, assign Source Field rules to the remaining fields.
Once all the fields are mapped, you should have an overview screen as shown in Figure 12.
Figure 12 Field mapping and Conversion rules overview
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.
Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt. (See Figure 13.)
figure 13 File attributes
Create an Excel file (Figure 14) with your data and save it as a Tab-delimited text file on your local drive (C:\) and name it XD02.txt.
Figure 14 Source data in Excel file (saved as Tab delimited file)
Step 8: Assign files
Execute step Assign Files (Figure 15) and the system automatically defaults the filename to the source structure.
Figure 15 Assign file to Source Structure
Step 9: Read data
In this step, LSMW reads the data (Figure 16) from the source file (from your PCs local drive). You have the option to read only selected rows and convert data values to Internal format.
Figure 16 Read Data
Step 10: Display read data
This step (Figure 17) is optional. If required, you can review the field contents for the rows of data read.
Figure 17 Display Read Data
Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.
Step 12: Display Converted data
Again this is an optional step to view how the source data is converted to internal SAP format (Figure 18).
Figure 18 Display Converted Data
Step 13: Create batch input session
Once the source data is converted in an internal format, you can create a batch session to process updates (Figure 19).
Figure 19 Create Batch Input Session
Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).
Note! Browsing thru these 14 steps, you may get a feeling that this is a very lengthy and time-consuming activity. However, for the purposes of demonstration, I have made it detailed. Although it looks lengthy, actually it takes hardly few hours from start-to-finish! After playing around with few simple LSMW scripts, you will find it so easy to change and create more complex ones.
www.****************
Rewards some points if it is helpful.
Rgds,
P.Nag

Lsmw step by step procedure using batch input method

hi,
lsmw step by step procedure using batch input method

Step-by-Step Guide for using BAPI in LSMW
Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
Introduction:
This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
Pre-requisites:
It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
Step-by-Step Procedure:
Details of the BAPI used in this scenario:
Business Object: BUS2012
Method: CreateFromData
Details of Message Type and Basic IDoc Type:
Message Type: PORDCR
Basic IDoc Type: PORDCR02
Lets have a look at the BAPI first, before proceeding to the LSMW:
1. Go to Transaction BAPI
2. Click on Search Button
3. Enter the value BUS2012 and select Obj.type(Technical Object Name
4. Press ENTER
5. Following screen appears:
6. On the left side of the screen, Expand the PurchaseOrder.
7. Select PurchaseOrder and double-click on the same for details.
Building LSMW using BAPI:
1. Go to Transaction LSMW.
2. Enter the Project, Subproject and Object information and click on CREATE.
3. Enter the descriptions for Project, Subproject and Object.
4. Now select Settings à IDoc Inbound Processing
5. IDoc Inbound Processing screen appears. Enter the required details as shown below:
6. Click on Activate IDoc Inbound Processing.
7. Click on Yes when prompted for Activate IDoc Inbound?
8. Hit on Back to return to the main screen.
9. Click on Continue (F8). Following Screen appears:
10. Select the Step 1 Maintain Object Attributes and select Execute.
11. Select the radio button Business Object Method and enter the following details:
Business Object: BUS2012
Method: CreateFromData
Hit ENTER
12. Save and click on BACK button. Following information message is displayed.
13. Now select step 2 Maintain Source Structures and click Execute.
14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on Create again to create the child structure. Following popup appears:
Select Lower Level and click on Continue. Enter the Item data structure name.
Click Save and hit BACK button to go to the main screen.
15. Select step 3 Maintain Source Fields and hit execute.
16. Enter the fields as shown below:
17. Click SAVE and return to main screen.
18. Select step 4 Maintain Structure Relations and click Execute.
Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
Select HEADERDATA and hit ENTER
Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
Click Save and return to main screen.
19. Select the step Maintain Field Mapping and Conversion Rules and click on execute. Maintain the Field Mapping as seen below:
20. Select step 7 Maintain Source Files and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
Save and return to main screen.
21. Select the step Assign Files and click on Execute.
Assign the file provided to the source structure. Here the same file is provided for both the structures.
Save and return to the main screen.
22. Select the step Read Data and click on Execute.
Click on Execute.
Return to the main screen.
23. Select the step Display read data and click on execute.
Click on the structure name to get the field level values.
24. Return to main screen and now select Convert Data.
25. Return to the main screen and select Display Converted data.
26. Return to main screen and select Start IDoc generation.
27. Now select the step Start IDoc Processing on the main screen.
28. Return to main screen and click on Create IDoc overview. Here the data record and status records of the IDoc could be viewed
It is given in screen shot.
http://www.****************
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/LSMW_tutorial.html
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
Reward points if useful.

Procedure for creating Recording in LSMW with header data and line item

Hello Friends,
I have to do the Initial Upload of Model Service specification using LSMW ( Recording).
Transaction : ML10
The problem i am facing is that i have been given 2 files one with HEADER data and the other with LINE ITEM(Service data).
Can we use the RECORDING method to upload 2 files?
If not possible how do we proceed.
Thanks and regards
Ashish Naik.

Step-by-Step Procedure:
Details of the BAPI used in this scenario:
Business Object: BUS2012
Method: CreateFromData
Details of Message Type and Basic IDoc Type:
Message Type: PORDCR
Basic IDoc Type: PORDCR02
Letu2019s have a look at the BAPI first, before proceeding to the LSMW:
1.     Go to Transaction BAPI
2.     Click on Search Button
3.     Enter the value u201CBUS2012u201D and select u201CObj.type(Technical Object Nameu201D
4.     Press ENTER
5.     Following screen appears:
6.     On the left side of the screen, Expand the u201CPurchaseOrderu201D.
7.     Select u201CPurchaseOrderu201D and double-click on the same for details.
Building LSMW using BAPI:
1. Go to Transaction LSMW.
2. Enter the Project, Subproject and Object information and click on CREATE.
3. Enter the descriptions for Project, Subproject and Object as prompted.
4. Now select Settings à IDoc Inbound Processing
5. u201CIDoc Inbound Processingu201D screen appears. Enter the required details as shown below:
6. Click on u201CActivate IDoc Inbound Processingu201D.
7. Click on u201CYesu201D when prompted for u201CActivate IDoc Inbound?u201D
8. Hit on u201CBacku201D to return to the main screen.
9. Click on Continue (F8). Following Screen appears:
10. Select the Step 1 u201CMaintain Object Attributesu201D and select u201CExecuteu201D.
11. Select the radio button u201CBusiness Object Methodu201D and enter the following details:
Business Object: BUS2012
Method: CreateFromData
Hit ENTER
12. Save and click on BACK button. Following information message is displayed.
13. Now select step 2 u201CMaintain Source Structuresu201D and click u201CExecuteu201D.
14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on u201CCreateu201D again to create the child structure. Following popup appears:
Select u201CLower Levelu201D and click on Continue. Enter the Item data structure name.
Click Save and hit BACK button to go to the main screen.
15. Select step 3 u201CMaintain Source Fieldsu201D and hit execute.
16. Enter the fields as shown below:
17. Click SAVE and return to main screen.
18. Select step 4 u201CMaintain Structure Relationsu201D and click Execute.
Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
Select HEADERDATA and hit ENTER
Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
Click Save and return to main screen.
19. Select the step u201CMaintain Field Mapping and Conversion Rulesu201D and click on execute. Maintain the Field Mapping as seen below:
20. Select step 7 u201CMaintain Source Filesu201D and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
Save and return to main screen.
21. Select the step u201CAssign Filesu201D and click on Execute.
Assign the file provided to the source structure. Here the same file is provided for both the structures.
Save and return to the main screen.
22. Select the step u201CRead Datau201D and click on Execute.
Click on Execute.
Return to the main screen.
23. Select the step u201CDisplay read datau201D and click on execute.
Click on the structure name to get the field level values.
24. Return to main screen and now select u201CConvert Datau201D.
25. Return to the main screen and select u201CDisplay Converted datau201D.
26. Return to main screen and select u201CStart IDoc generationu201D.
27. Now select the step u201CStart IDoc Processingu201D on the main screen.
28. Return to main screen and click on u201CCreate IDoc overviewu201D. Here the data record and status records of the IDoc could be viewed:
Check this. This may help

Diff b/w BDC and LSMW

hi
i want know what is the difference between BDC and LSMW and which is best also tell me BDC and LSMW using for which type data (like master or transactional data)
thanka in advance
deepak

Hi deepak,
LSMW and BDC are vastly different.
BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/background processing.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners
http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm
http://www.sap-img.com/sap-data-migration.htm
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://allsaplinks.com/lsmw.html
http://myweb.dal.ca/hchinni/sap/lsmw_home.htm

LSMW procedure

Similar Messages

Maybe you are looking for