LSMW techniques

Can some one tell me the advantages and disadvantages; and when shall we use
the Direct Input, Batch input recording, BAPI, and IDoc techniques in LSMW workbench...any doumentation will be of great help. eg. why should we choose Direct Input as opposed to Batch Input recording and so on..
Thanks a lot. Will award points
Arianne

LSMW : An SAP system tool that supports one-time and periodic data transfers from external systems to SAP R/3 systems.
The Legacy System Migration Workbench facilitates the conversion of data to the necessary format.
Technologies supported include Batch Input, Call Transaction, Direct Input, BAPIs, and EDI.
Batch Input : A data transfer technology that enables the transfer of large volumes of data to an SAP System using the online transaction.
A batch input session is created for this purpose which you can then process using the Batch Input Monitor.
Call Transaction : A data transfer technology similar to batch input that allows large amounts of data to be transferred to a SAP System using the online transaction.
No batch input folder is generated. Instead, the data is posted directly using the online transaction.
Direct Input :A data transfer technology that uses function modules created for this purpose by SAP to transfer very large volumes of data to an SAP System.
The same consistency checks are performed within the function modules as those performed in the online transaction.
Direct input has definite performance advantages when compared to the batch input and call transaction technologies because no online transaction has been performed here.
Business Application Progarmming Interface(BAPIs) : A standardized programming interface that facilitates external access to business processes and data in the SAP System.
You define Business Application Programming Interfaces (BAPIs) in the Business Object Repository (BOR) as methods of SAP business objects or SAP interface types.
BAPIs offer an object-oriented view of business components in the SAP System. They are implemented and stored as RFC-enabled function modules in the Function Builder of the ABAP Workbench.
Electronic Data Interchange : Cross-company exchange of electronic data (for example business documents) between domestic and international business partners who use a variety of hardware, software, and communication services. The data involved is formatted according to predefined standards. In addition to this, SAP ALE technology is available for data exchange within a company.

Similar Messages

Regarding Line Items posting in LSMW

Hi
Can You let me know the procedure that how we can post the data realted to the line items using LSMW technique.
Regards,
kumar

LSMW cannot be used for data involving table control. U need to go in for a BDC session method for better performance .

Loading Language translations for Catalogs using LSMW

I have hundreds of codes entered for a Catalog in English and I need to be able to load all the French translations for those codes. Doing a translation by hand is simple by just clicking on the Translation selection in the Menu. However, when I try to do that using LSMW recordings, it doesn't record a field that I can attach my source data to for the translation. So, basically, I can't get it to work. Is this even possible? Is there another way to load translations?

Hi,
1. Data has been captured as per the template
2. Instead of capturing catalog codes in English, keep those details in the Required language (in your case, its French).
3. Save the Excel file as Unicode Text instead of Tab delimited or other recommended formats.
4. Login into SAP as normal. Nothing specifically required from SAP side.
5. Do the normal LSMW technique to upload the data.
Material Description in Chineese language
http://www.sap-img.com/general/lsmw-and-ftp-upload-chinese-or-non-english-characters.htm
Regards,
Maheswaran.
Edited by: Maheswaran.K on Apr 12, 2011 8:56 AM

Regarding LMW

Hi Gurus
While I am uploading a file using LSMW technique in Batch Input method.
I was stucked in 2 things.
Please go thru this and suggest me ur views.
While recording ,for some values for eg: KOMGG-KUNNR or KOMGG-KUNWE from database it will come as 270300 based on condition that
KOMGG-KUNNR ,If RV130-SELKZ(01).
KOMGG-KUNWE,IF RV130-SELKZ(02)
from upload file KUNNR.
How to handle this kind of conditions in LSMW?
A batch-input session has to created for every 1000 data records of the upload file.
How this can be handled in LSMW?
After all processing I have to create a file which has to shows :
Number of Records in Upload file
Number of Records in Batch Session
Number of Records successfully processed.
Please suggest me the steps have to follow.
If anyone provide me the useful code/navigation it will be a great help for me.
Thanks & Regards,
Kumar

Hi,
Hope this answers.
While recording ,for some values for eg: KOMGG-KUNNR or KOMGG-KUNWE from database it will come as 270300 based on condition that
KOMGG-KUNNR ,If RV130-SELKZ(01).
KOMGG-KUNWE,IF RV130-SELKZ(02)
from upload file KUNNR.
>>> First of all, you do the recording as you do normally, do not think of LSMW. Now when the data is fetched into R/3 say from Excel sheet, you can have user defined routine in LSMW(There's an opiton it's one of the 16 steps, 5th i think)
to restrict/filter the recrod read.
A batch-input session has to created for every 1000 data records of the upload file.
How this can be handled in LSMW?
>>> The similar way you can keep a counter which tells you when to abort after the required number of records have been processed.
After all processing I have to create a file which has to shows :
Number of Records in Upload file
Number of Records in Batch Session
Number of Records successfully processed.
>>> this is very confusing, I am not clear, where do you want to show this information. If you want a seperate report or what else. in LSMW alone you can handle this situation.
Reward if useful.
Kiran

Multilingual texts

How to add multilingual texts for mass upload of equipments?

Hi,
To my knowledge if the requirment is bulk then try with "LSMW" technique and there use "IE08" the transaction code for Equipment creation
reagrds
DSR
Edited by: D.Srinivasa Rao on Nov 14, 2011 6:34 AM

Data uploading techniques//LSMW

Dear Experts,
As i am very new to SAP HCM. Can any one explain about data uploading techniques in HCM point of view.
ANd what is BDC,PDC
Thanks in Advance
Ram

http://wiki.scn.sap.com/wiki/display/ABAP/Batch+Input+-+BDC
SAP ECC - Plant Data Collection - Time, Attendance and Employee Expenditures (HR-PDC)

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

I want in LSMW SAME CODING. THIS IS USING BDC CALL TRANSACTION

REPORT ZXX_BDC_PRA NO STANDARD PAGE HEADING LINE-COUNT 20
 LINE-SIZE 150 .
Program Name :ZXX_BDC_PRA *
Object Id : *
Develper Name : praveen *
Start Date : 25.06.07 *
Description : uploading flat file to sap system *
*--structure for Data Uploading.
DATA: BEGIN OF IT_STR ,
 VKORG LIKE RF02D-VKORG,
 VTWEG LIKE RF02D-VTWEG,
 SPART LIKE RF02D-SPART,
 KTOKD LIKE RF02D-KTOKD,
 NAME1 LIKE KNA1-NAME1,
 SORTL LIKE KNA1-SORTL,
 ORT01 LIKE KNA1-ORT01,
 PSTLZ LIKE KNA1-PSTLZ,
 LAND1 LIKE KNA1-LAND1,
 SPRAS LIKE KNA1-SPRAS,
 END OF IT_STR.
*--Internal Table for Data Uploading.
DATA: ITAB LIKE IT_STR OCCURS 0.
*--Internal Table to sucessfull Records.
DATA: ITAB1 LIKE IT_STR OCCURS 0.
*--Internal Table to Store Error Records.
DATA: ITAB2 LIKE STANDARD TABLE OF IT_STR WITH HEADER LINE.
*--Internal Table for Storing the BDC data.
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*--Internal Table for storing the messages.
DATA: MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA: COUNT TYPE I VALUE 1,
 S VALUE 0, E VALUE 0.
Selection screen *
SELECTION-SCREEN BEGIN OF BLOCK b1
 WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE TYPE IBIPPARMS-PATH.
SELECTION-SCREEN END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
*functionality to use drill down list
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
 IMPORTING
 FILE_NAME = P_FILE.
Start-of-selection *
START-OF-SELECTION.
DATA FILENAME TYPE STRING.
FILENAME = P_FILE.
*-- Form to upload flatfile data into the internal table.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = FILENAME
 FILETYPE = 'ASC'
 HAS_FIELD_SEPARATOR = 'X'
 TABLES
 DATA_TAB = ITAB
 EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17.
*--Generating the BDC table for the fields of the internal table.
LOOP AT ITAB INTO IT_STR.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0107'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'RF02D-KTOKD'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_FIELD USING 'RF02D-VKORG'
 IT_STR-VKORG.
 PERFORM BDC_FIELD USING 'RF02D-VTWEG'
 IT_STR-VTWEG.
 PERFORM BDC_FIELD USING 'RF02D-SPART'
 IT_STR-SPART.
 PERFORM BDC_FIELD USING 'RF02D-KTOKD'
 IT_STR-KTOKD.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0110'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNA1-SPRAS'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_FIELD USING 'KNA1-NAME1'
 IT_STR-NAME1.
 PERFORM BDC_FIELD USING 'KNA1-SORTL'
 IT_STR-SORTL.
 PERFORM BDC_FIELD USING 'KNA1-ORT01'
 IT_STR-ORT01.
 PERFORM BDC_FIELD USING 'KNA1-PSTLZ'
 IT_STR-PSTLZ.
 PERFORM BDC_FIELD USING 'KNA1-LAND1'
 IT_STR-LAND1.
 PERFORM BDC_FIELD USING 'KNA1-SPRAS'
 IT_STR-SPRAS.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0120'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNA1-TXJCD'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0125'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNA1-NIELS'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0360'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNVK-NAMEV(01)'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ENTR'.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0310'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNVV-BEGRU'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0324'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNVP-PARVW(01)'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ENTR'.
*--Calling the transaction 'Vd01'.
 CALL TRANSACTION 'VD01' USING BDCDATA MODE 'N' UPDATE 'S'
 MESSAGES INTO MESSTAB.
 PERFORM MESSAGES.
 REFRESH : BDCDATA, MESSTAB.
ENDLOOP.
END-OF-SELECTION.
*--Populating the Success records internal table.
IF ITAB1[] IS NOT INITIAL.
format color 5.
 WRITE: /'SUCCESSFUL RECORDS'.
 format color off.
 LOOP AT ITAB1 INTO IT_STR.
 WRITE:/ IT_STR-VKORG,IT_STR-VTWEG,
 IT_STR-SPART,IT_STR-KTOKD,
 IT_STR-NAME1,IT_STR-SORTL,
 IT_STR-ORT01,
 IT_STR-PSTLZ,
 IT_STR-LAND1,
 IT_STR-SPRAS.
 S = S + 1.
 ENDLOOP.
REFRESH : ITAB1.
 WRITE:/ 'TOTAL RECORDS',S.
ENDIF.
*--Populating the error records internal table.
IF ITAB2[] IS NOT INITIAL.
FORMAT COLOR 3.
 WRITE :/ 'ERRORS RECORDS ARE'.
FORMAT COLOR OFF.
 LOOP AT ITAB2.
 WRITE:/ ITAB2-VKORG,
 ITAB2-VTWEG,
 ITAB2-SPART,ITAB2-KTOKD,
 ITAB2-NAME1,ITAB2-SORTL,
 ITAB2-ORT01,
 ITAB2-PSTLZ,
 ITAB2-LAND1,
 ITAB2-SPRAS.
 E = E + 1.
 ENDLOOP.
REFRESH : ITAB2.
 WRITE: / 'TOTAL RECORDS',E.
REFRESH : ITAB2.
ENDIF.
End of Selection *
END-OF-SELECTION.
TOP-OF-PAGE *
TOP-OF-PAGE.
WRITE:/ SY-ULINE.
WRITE:/10 'REPORT ID',21 SY-REPID,35 'USERNAME',46 SY-UNAME,
60 'SYSTEM DATE',70 SY-DATUM,80 'SYSTEM TIME',90 SY-UZEIT,
100 'PAGE NO',108 SY-PAGNO.
WRITE:/ SY-ULINE.
FOrm to Populate the BDC table.
 Start new screen *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM. "BDC_DYNPRO
 Insert field *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> SPACE.
 CLEAR BDCDATA.
 BDCDATA-FNAM = FNAM.
 BDCDATA-FVAL = FVAL.
 APPEND BDCDATA.
ENDIF.
ENDFORM. "BDC_FIELD
*& Form messages
FORM MESSAGES .
LOOP AT MESSTAB.
 IF MESSTAB-MSGTYP = 'I'.
 WRITE : / MESSTAB-MSGV1.
 ELSEIF
MESSTAB-MSGTYP = 'S'.
 INSERT LINES OF ITAB FROM COUNT TO COUNT INTO TABLE ITAB1 .
 COUNT = COUNT + 1.
 WRITE : / MESSTAB-MSGV1.
 ELSEIF
 MESSTAB-MSGTYP = 'E'.
 INSERT LINES OF ITAB FROM COUNT TO COUNT INTO TABLE ITAB2.
 COUNT = COUNT + 1.
 WRITE : / MESSTAB-MSGV1.
 ENDIF.
ENDLOOP.
ENDFORM. " messages

Hi
Go through the doc and do the same using LSMW
BDC is the way to transfer data by writing a batch input program which can use either session or call transaction method.
LSMW used to transfer data without/less code.
What type of data we transfer using LSMW?
LSMW is best suited for transferring master data.
Actually BDC and LSMW are not comparable at all.
for example LSMW itself can use BDC as a way of mass data transfer.
BDC is a mass data transfer technique via screen logic of existing SAP Data entry transactions. It behaves as if you are manually making thousand of entires into sap system as a background job. And that is probably the reason why BAPI's are preffered over BDC's.
On the other hand LSMW is a tool to facilitate DATA migration from other legacy systems ... It contains step by step procedure for data migration.
Like Managing Data Migration Projects , Creating Source Structures , Mapping Source structures wid Target structures , etc etc
LSMW internally might well be using the following techniqes for data transfer..
1. IDOX
2. Direct Input / BDC
4. BAPI's
LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC infact much more but when coming to techinical perspective most the parameters are encapulated. To listout some of the differences :
LSMW is basicaly designed for a fuctional consultant who do not do much coding but need to explore the fuctionality while BDC is designed for a technical consultant.
LSMW offers different techinque for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.
LSMW mapping is done by SAP while in BDC we have to do it explicitly .
LSMW is basically for standard SAP application while bdc basically for customized application.
Coding can be done flexibly in BDC when compared to LSMW
1. Maintain Attributes:
Here you have to choose the second option and you can do the recording how this should work. Then assign the same to the Batch Input Recording name.
2. Maintain Source structure:
Create a structure name
3. Maintain Source field:
In this you have to create a structure same as that of the input file
eg: name
age
4. Maintain structure relations:
This will link the structure to the input file.
5. Maintain field mapping and conversion rules:
Here is the place where you can do coding, depending upon the code you have written or assignment you have done the values will get picked up from the file and get processed.
6. Maintain field mapping and conversion rules:
If you have any fixed values you can define here.
7. Specify files:
Specify the input file path and type.
8. Assign files:
This will assign ur file to the Input file
9. Read Data:
This will read ur data from teh file.
10. Dispaly Read Data:
You can see the uploaded data
11. Convert Data
This will convert the data to the corresponding format for processing
12. Display Converted data:
13. Create batch input session
Here this will create a batch input session for processing
14. Run Batch Input session:
By clicking on the session and process the same you can do teh needfu.
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
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
Reward points for useful Answers
Regards
Anji

Techniques in ABAP program

What are the techniques involved in using SAP supplied programs? do you prefer to write your own programs to load master data? why ?

Chandru,
What are the techniques involved in using SAP supplied programs?
The above question is not clear,what actually you are looking for.
Do you prefer to write your own programs to load master data? why ?
To load transaction data we can use LSMW,SCATT,BDC or BAPI.
BDC is mostly used when uploading data is w.r.t some validations.If it is just a simple upload then we can use LSMW or SCATT.If a BAPI is available then it is the best way to upload data.
K.Kiran.

MR21 Data upload using LSMW

Hi,
Please help me in creating an LSMW for MR21 Transaction. I have a flat file, But i'm not sure about how this can be acheived thru Direct Input. Please also educate me on the other techniques of acheiving this Data Transfer.
Thanks & Regards,
Sai

Hi Thanks.
I have used the same IDoc. But the following fields are not in the IDOC structure .
2. RQPAS-QUALITAT - Qualitative Characteristic
3. PLMK-MKVERSION - Version Number of the Master Inspection Characteristic
4. PLMK-PMTVERSION - Version Number of the Inspection Method
I found that MKVersions are maintaining in the MIC (Master of Inspection Characteristic) , Once the MIC number is given in the inpsection plan , It is populating the version automatically.
SInce IDOC has qunatitive indicator, If value is populated to qunatitative indicator it is checking the quantative othwise if empty it is populating qualitative .
Thanks,
Karunanidhi

Lsmw using bapi's

hi all,
Can any body provide the code to upload purchase order data using bapis in lsmw.urgent pls...
thanks.
assad

BAPIs are normally called synchronously in order to get feedback immediately.A synchronous call will only work if the system we want to access is up and running.For some purposes like data transfer, SAP wanted BAPIs to invoke asynchronously so that the calling application could proceed even if the remote system was currently unavailable.
Hence these BAPIs are linked to ALE (Application Linking and Enabling),an asynchronous message passing mechanism with guaranteed delivery.ALE uses Idocs as the containers for messages. Idocs are instances of Idocs types, which in turn are associated ALE message types
SAP has provided a generator which takes a BAPI and generates an appropriate ALE message type and an associated Idoc type.
Data stored in a file by means of the IDoc technique is generally imported in two steps. You can call these steps in LSM Workbench:
Start IDoc creation.
First, the file of the converted data is read. The "information packages" contained are stored in the R/3 database in IDoc format. It is, however, not stored in the database of the corresponding application. The system assigns a number to every IDoc. Then the file of the converted data is deleted.
Start IDoc processing.
The IDocs created in the first step are submitted to the corresponding application program. This application program checks the data and posts it in the applications database, if applicable.
Thanks,
Manjunath MS
"Reward Points if it is useful"

Sales Order Creation using LSMW IDOC method.. ( Custome Interface)

Hi ABAP'rs,
                 Please provide me LSMW steps for creating Sales Order using IDOC method.
                        Thanks and Regards,
                                              Param.

LSMW-IDOC in General
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
Most of the functions are within R/3, hence platform independence.
Quality and data consistency due to standard import techniques.
Data mapping and conversion rules are reusable across projects.
A variety of technical possibilities of data conversion.
Generation of the conversion program on the basis of defined rules
Interface for data in spreadsheet format.
Creation of data migration objects on the basis of recorded transactions.
Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
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:
Standard Batch / Direct input.
Batch Input Recording
   o If no standard programs available
   o To reduce number of target fields.
   o Only for fixed screen sequence.
BAPI
IDOC
o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
Choose settings -> IDOC inbound processing in LSMW
Set up File port for file transfer, create port using WE21.
Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
Setup partner type (SAP recommended US) using WE44.
Maintain partner number using WE20.
Activate IDOC inbound processing.
Verify workflow customizing.
Steps in creating LSMW Project:
Maintain attributes choose the import method.
Maintain source structure/s with or without hierarchical relations. (Header, Detail)
Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
Fields can be maintained individually or in table form or copy from other sources using upload from a text file
Maintain relationship between source and target structures.
Maintain Field mapping and conversion rules
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.
Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
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)
Assign Files to defined source structures
Read data Can process all the data or part of data by specifying from / to transaction numbers.
Display read data To verify the input data being read
Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
Display converted data To verify the converted data
Import Data Based on the object type selected
Standard Batch input or Recording
o Generate Batch input session
o Run Batch input session
Standard Direct input session
o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
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.
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:
R/3 Transport system
o Extras ->Create change request
o Change request can be exported/imported using CTS
Export Project
o Select / Deselect part / entire project & export to another R/3 system
Import Project
o Exported mapping / rules can be imported through PC file
o Existing Project data gets overwritten
o Prevent overwriting by using
Import under different name
Presetting for Inbound IDOC processing not transportable.
Reward if useful.
regards
santhosh reddy

FAQ's BDC & LSMW

Hi All please answer these Questions,
1. What is BDC ?
2. What is call transaction method ? what is the
syntax/procedure?
3. What is session method and what is the
syntax/procedure?
4. Difference between call transaction & session method?
5. which of these methods can be best used in background
process?
6. What is direct input method?
7. How LSMW is advantageous than normal BDC?
8. what are the steps in lsmw?
9. IN LSMW can you use BAPI, ?
10. Can you call a bdc from a report program?
11. what is the difference between synchronus &
asynchronus methods?
12. call transaction uses synchronus or synchronus method?
13. session method uses synchronus or synchronus method?
14. What is bapi?
15. how bapi is different from call transaction/session?
16. what r the advantages of bapi?
17. for uploading master data(ex:customer data) into sap,
which methods you prefer? call
transaction/session/lsmw/bapi? why?
18. tell any 2 standard bapi function modules used for
uploading sales order data?
Thnaks in advance
 Ranjith

Hi,
1.BDC is Batch Data Communication where data is transferred from legacy system to SAP system.
 Different methods of BDC are
 1. Call Transaction Method.
 2. Session Method
 3. Direct Input method.
2. Call Transaction Method is one of the method in BDC for Data Transfer.
 Syntax :
 CALL TRANSACTION trans [using bdctab MODE mode].
 Where trans = Transaction Code
 Bdctab = Internal table of structure BDCDATA.
 Mode = Display mode.
 Three possible entries are there for MODE.
 A - Display all .
 E - Display errors only.
 N - No Display.
 Procedure :
 1. Prepare a BDCDATA structure for the transaction that u wish 2 run.
 2. With a CALL TRANSACTION USING statement,call the transaction and prepare the BDCDATA structure. For example:
 CALL TRANSACTON ZSRC USING BDCDATA MODE A.
 MESSAGES INTO MESSTAB.
 IF SY-SUBRC <> 0.
 <Error_handling>.
 ENDIF.
3. Procedure :
 1. Generate the batch input session using function module BDC_OPEN_GROUP.
 2. The proceed as follows for each transaction that the session contains:
 a . In the BDCDATA structure, enter the value for all screens and fields that must be processed in the transaction.
 b. Use BDC INSERT to transfer the transaction and the BDCDATA structure to the session.
 c.Close the batch input session with BDC CLOSE GROUP
 d.Start to process the generated session.
4.Session method.
1) asynchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) synchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
5.Call Transaction method.
6.Direct Input is a technique which doesnot create a session but stores data directly.To enhance the batch input procedure, the system offers the direct input technique, especially for transferring large amounts of data.
7.In LSMW ,there are two more import techniques (BAPI,IDoc) & Mapping can be done automatically.It contains 17 to 18 steps for migrating the data.It's an automatic procedure.
8.Goto Transaction 'LSMW' and execute it.We can view the steps.
9.Yes,We can.There is an option in 'Maintaining Object Attributes'.
12.Synchronous processing.
 In Database Update,it may be Synchronous or Asynchronous.
13.Asynchronous processing.
 In Database Update,it is Synchronous.
14.BAPI(Business Application Programming Interface) they are actually methods (business functions) exposed by the sap environment to manipulate business objects defined in the business objects repository. other sap or non sap systems can use these bapis for their business operations.
16: regarding advantages for BAPI, please refer: http://help.sap.com/saphelp_nw04/helpdata/en/7e/5e11dc4a1611d1894c0000e829fbbd/frameset.htm

LSMW: Idoc or BAPI; which one is better and why ?

Hi All,
In LSMW, given the choices between Idoc and BAPI,which processing method is good and why?
Please do reply asap. Its urgent.
Best regards.
Ram

The preferece of Import Techniques are:
1)Batch Input
2)Direct Input
3)BAPI's
4)IDOCS's
5)Recording
6)Custom Program

Refer these Links:
Re: LSMW with Recording or LSMW with BAPI?????
Regards,
AS

Differences between LSMW and BDC

Hi All
Please can you give me the few points about the differences between LSMW and BDC?
Awaiting for your Responce
Praveen

Hai Check with the following document
GOOD
THERE IS THREE TYPE OF METHOD IN BDC
BDC SESSION
CALL TRANSACTION
CALL DIALOG
What is BDC or batch input
The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
BDC functions:
· BDC_OPEN_GROUP : Opens a session group
· BDC_CLOSE_GROUP : Closes a session
· BDC_INSERT : Insert a BDC scenario in the session
· The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
The object itself is maintanable through the transaction SE24.
BDC methods:
Method
Description
Parameters
OPEN_SESSION
Opens a session
SUBRC (Return Code 0 OK)
SESSIONNAME (Session to be created)
CLOSE_SESSION
Closes a session
None
RESET_BDCDATA
Resets the BDC Internal Table...
None. Normally, for internal purpose
BDC_DYNPRO
Handles a new screen
PROGNAME (Name of the program)
DYNPRONR (Screen Number)
BDC_FIELD
Puts a value on the screen
FIELDNAME (Name of the field)
FIELDVALUE (Value to be passed)
CONSTRUCTOR
Constructor - Initializes NO_DATA
NODATA (No data character). The constructor is called automatically when the object is created.
RUN_SESSION
Launches a session with RSBDCBTC
None
CALL_TRANSACTION
Calls a transaction with the current BDC Data
MODE (Display Mode)
UPDATE (Update Mode)
TCODE (Transaction to be called)
BDC_INSERT
Inserts the BDC scenario in the session
TCODE (Transaction to be called)
BDC techniques used in programs:
1) Building a BDC table and calling a transaction,
2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
3) Building a session and lauching the transaction right after closing the session.
BDC using Call Transaction
BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
program. The process involves building an Internal BDC table containing the screen information needed to
execute the required transaction and then passing this to the Call transaction command (See code example).
The full procedure for creating a BDC program is as follows:
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
BATINPUT/DIRECT INPUT
A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
GO THROUGH THIS LINK
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.
The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.
The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.
LSMW vs DX Workbench
The LSM Workbench covers the following steps:
Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
Convert the data from source format to target format.
Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
Experiences made in successful implementation projects have shown that using the LSM Workbench significantly contributes to accelerating data migration.
SAP provides this tool along with documentation to customers and partners free of charge.
Users of the LSM Workbench receive the usual support via SAP Net - R/3 Frontend (component BC-SRV-DX-LSM).
Releases:
Version 1.7.2 of the LSM Workbench ("LSMW 1.7.2") available
Attention : LSMW 1.7.2 requires an SAP R/3 system with SAP R/3 4.0 or SAP R/3 4.5.
Version 1.8.0 of the LSM Workbench (1.21mb) ("LSMW 1.8.0") available
Attention : LSMW 1.8.0 requires an SAP R/3 system with SAP R/3 4.6.
Version 3.0 of the LSM Workbench (1.89mb) ("LSMW 3.0") available for Web Application Server 6.10
Attention : LSMW 3.0 requires a SAP WAS 6.10. Functionality of version 1.7.2 and 3.0 are identical !
Version 4.0 of the LSM Workbench ("LSMW 4.0") integrated in Web Application Server 6.20
Attention : LSMW 4.0 is an integrated part of SAP WAS 6.20.
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

LSMW techniques

Similar Messages

Maybe you are looking for