Bapi and lsmw.

Hi all,
I have some problems in understanding SAP integration with legacy systems and am into subscribing to canonical documents published by other leagcies.
I just wanted to know which SAP adapter is the best taking in mind their
complexity and fuctionality.
Either to use ALE-IDOC adapter or to go for ALE-BAPI adapter.
whether can I use BAPI client adapter for both read and write into SAP.
The SAP version is 4.6.
Thanks and Regards,
Md.

hi Riyaz
U wanna integrate data? is it a one time thing ur looking for?
if you get a flat file from legacy, use LSMW or BAPI to load into SAP..
I guess u cant explain a bit more.. about ur req.

Similar Messages

In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

hello all
In LSMW, what is diff between LSMW-BAPI and LSMW-IDOC

Hi Swamy,
The differences between IDoc and BAPI are as follows:
IDOC
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system.
Idocs are processed asynchronously and no information whatsoever is returned to the client.
The target system need not be always online. The IDOC would be created and would send the IDOC once the target system is available (tRFC concept). Hence supports guaranteed delivery.
With asynchronous links the sub-process on the client can be finished even if the communication line or the server is not available. In this case the message is stored in the database and the communication can be done later.
The disadvantage of asynchronous links is that the sub-process on the server cannot return information to the calling sub-process on the client. A special way for sending information back to the client is required. In addition, a special error handling mechanism is required to handle errors on the receiving side.
IDOCs may be more changeable from release to release.
IDOCs are poorly documented.
BAPI
BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
BAPIs are called synchronously and (usually) return information.
For BAPIs the client code needs to do the appropriate error handling.
Problems with synchronous links occur if the communication line or the server is temporarily not available. If this happens, the sub-process on the client cannot be finished (otherwise there would be data inconsistencies).
Synchronous links have the advantage that the sub-process on the server can return values to the sub-process on the client that has started the link.
BAPIs are not totally immune to upgrades.
BAPIs are reasonably well documented.
Reward points if useful.
Best Regards,
Sekhar

Material master data BAPI and LSMW log

I have three questions want to ask :
1. I will use all the view to create material master. I want to know if there is one BAPI to create it.?
2. If I use LSMW to create it, in LSMW i use the BAPI method to create it. But I should to know the detail log information When I finished the LSMW. How can I get the log information ,because I should send the log information to other system. I must get the log, then I can send out the log information to other system.
3. I want to know if i can run lsmw in report. if there one FM to do this ? User don't want to step by step to run this , they want to run only once time so they can create the master data.
Thanks in Advance .
susan

Hi Ming,
Use the BAPIs:
BAPI_RETAILMATERIAL_CREATE.
BAPI_MATERIAL_SAVEDATA
refer the sample code
https://forums.sdn.sap.com/click.jspa?searchID=13348102&messageID=3459824
Regards,
Chandra Sekhar

BAPI with LSMW

hi all,
Any one has step by step procedure BAPI with LSMW.
BAPI with BDC.
sri

Hi Sri,
Please Go through this Link ,
BAPI And LSMW
Regards,
Ramganesan K.

Is it possible to add a standard BAPI to LSMW?

Hi,
I want to load BASIC Pay data from legacy system to Info type 0008 through LSMW using BAPI_BASICPAY_CREATE. But the BAPI BAPI_BASICPAY_CREATE is not available as BAPI objects in LSMW.
Is it possible to add standard BAPI to LSMW and use it?
Thanks in advance.
Thanks & Regards,
Govind.

Refer these links:
1. BAPI And LSMW and
2. Getting BAPIs into LSMW?
Regards,
Ravi

BDC , BAPI n LSMW

hi friends,
Tel me a snenorio wher u should go for BDC , BAPI and LSMW....pls dont give technical defintions....pls suggest me the snerios.....
Thanks in advance...
Regards...
Balaji

Hi,
BAPI:
SAP created the Business Framework to allow the technical integration and exchange of business data among SAP components and between SAP and non-SAP components. Important components of the Business Framework are the Business Application Programming Interfaces (BAPIs), which represent visible interfaces at the component boundaries and whose properties serve to integrate these components.
The integration can include both components within a local network and components that are connected with one another through the Internet.
BAPIs allow integration at the business level, not the technical level. This provides for greater stability in the link, and independence from the underlying communication technology.
You can get all the standard SAP BAPI functions with the transactions code 'BAPI'.
BDC:
Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.
The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.
Normally, the tcode SHDB will be used to record the transaction code the user used. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.
LSMW:
No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
So although it was designed for uploading of legacy data it is not restricted to this use.
We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.
The SAP transaction code is 'LSMW' for SAP version 4.6x.
For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded.
You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.
If you are an existing SAP customer with an OSS ID, you can access the SAP Service Marketplace to download the LSWM for your Basis teams to install to your SAP system: http://service.sap.com/lsmw
The LSM Workbench carries out the following tasks:
Reads the transfer data from one or more files (for example, spreadsheets, sequential files etc.)
Converts the data from the source format into the target format
Note that with background processing, the input file must not be located in the presentation server. Access to presentation server files is only possible when you are working online.
Regards,
Bhaskar

LSMW Methods - BAPI and IDOC - why used together?

Hi,
There are four mathods available in LSMW:
- Direct Input
- BAPI
- IDOC
- BDC
Among these BAPI and IDOC always go hand in hand. In case we choose to go in for IDOC, we will have to enter the partner profile settings for an inbound IDOC. But in case we choose to go with th BAPI method, even then we have to mention the inbound IDOC settings.
I would like to know why is this so; if there is a provision for two separate methods, why do we need to use IDOC if a BAPI is selected.
Please advise.
Regards,
Namrata

In LSMW, BAPI method by default uses iDoc as a medium exchange in order to be passed as parameters to it. Actually, a text file is created when you convert the data with iDoc format. From there, you have two options: Either go on with LSMW steps (create idocs from text file, then run idoc transactions) OR go on with SXDA workbench (create a project there and run a job which essentially calls the BAPI).
There are two different methods because SAP developed them at different times. First, they had the ALE layer (as middleware for SAP to SAP/non-SAP communication) that uses the idoc as medium exchange, then at a later time BAPIs were developed as RFC function modules/object methods. Since idoc were already in place, they used that as medium exchange for BAPIs, too.
I hope that is clearer now.

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

How to tranfer IDOC and BAPI through LSMW

Hi friends,
I need documents regarding processing of IDOC and BAPi through LSMW,
Thanks In advance,
Regards,
charan

Hi
LSMW-BAPI
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.****************
LSMW-IDOC
see this and do accordingly
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
Go through the steps
Hi please go through the following steps for IDOC method
Step 1. Run the transaction ( /nlsmw ) you will reach to the screen
Here you have to specify
Project : 060_BUS_TRANS
Subproject : SERVICE_TICKET
Object : SRV_TICKET_ZSVT
click on the execute button .you will reach the screen :
The screen shows the 15 steps to Run the lsmw
Step 2) select the first step ( Maintain object attributes) and click the execute button.After clicking on the execute button you will reach at. the screen
Here you have to specify ( MEssage type and basic type)
click on the BACK button
Step 3) select the 2nd step ( Maintain source structures) and click the execute button
Here you have to specify the source structures.
Step 4) Select the 3rd step ( Maintain source fields) and click on the execute button :
Here you have to specify the fields present in the source structure
Step 5) select the 4th step ( Maintain structure relationship ) and click on the execute button :
Here you have to specify relationship between source and target structures
Step 6) select the 5th step ( Maintain field mapping ) and click on the exécute button :
Here you have to map the fields between source and target structure. Also you have to apply conversion rules here if any
STEP 7) select the 6th step and click on the exécute button
Here you can define any fixed value or user define routines
Step 8) select the 7th step ( Specify files) and click on the exécute button :
At This screen we have to specify the files for This we should be in change mode .So please click on the button shown in the above screen. After clicking on This button you will be in change mode and will be able to specify the files :
Step 9) select the 8th step ( Assign files) and click on the exécute button
For assigning files yoy should be in change mode do the same thing click on the button as shown in the above screen :
Then assign the files to different structures.
Step 10 ) select the 9th step ( Read Data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Again click on the exécute button . After clicking on the exécute button you will reach to the next screen
Here you will see data is read.
Step 11) select the 10th step ( Display read data) and click on the exécute button :
Here you can see your test data present in test files assign to source sturcture
Step 12 ) select the 11th step ( Convert data) and click on the exécute button :
After clicking on the exécute button you will reach to the screen
Click on the exécute button as shown on the : After click on the exécute button you will reach to the next screen
Data is converted
Step 12th ( Display converted data is same as Display read data )
Step 13 ) select the 13th step ( Start idoc generation) and click on the exécute
button :
At this step Idoc is generated using converted data
Step 14) select the 14th step ( Start idoc processing ) and click on the exécute button :
After clicking on the exécute button you will reach to the screen :
And then click on the exécute button : After clicking on the exécute button you will reach to the final processive screen
If data is processed correctly you will see ( 53 Status message with green sign)
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
Reward points for useful Answers
Regards
Anji

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

Creation of material using BAPI in LSMW without using material no.

Hi SAP Gurus,
I have a requirement of creating materials using the BAPI in LSMW.
I tried to create a material using the BAPI (Business Object - BUS1001006 , and method - SAVEDATA) which should be created internally, but it is asking the material number to be given externally and my configuration is setup to create the material number internally.
Even I looked into the material type which is associated with the number range and everything looks good.
Is there any solution to create the material by using BAPI in LSMW without passing the material no. externally ?
Appreciate your help.
Kalikonda.

Hi,
it looks like it's not possible to call this BAPI wihtout material number. Here is a quote from BAPI documentation.
When creating material master data, you must transfer the material
number, the material type, and the industry sector to the method. You
must also enter a material description and its language.
Cheers

Is there is any BAPI/FM/LSMW for BOMBOS Interface?

I have a requirement to write a custom program to transfer BOM to BOS. This we can do through CG37, But I want to execute CG37 functionality through custom program. Could you please let me know if any one knows BAPI/FM/LSMW for this? Thanks in advance.
You can send information to [email protected]
Thanks
Srini

Dear Srinivass
Kannan is right; but why can you not use Cg37? Here you have a user interface to populate the data; and if you drill down you can see how it is designed. But you need to pay attention. The BOMBOS interface will work (according to my knowledgeI) only if you "trigger" the generation of the worklist; and this is done "different" using a different function module; I believe at the "end" 'C1L0_BOM_TRIGGER_GEN_WL is used as well. BOMBOS is not discussed often here.
E.g. check: http://www.se80.co.uk/sapfms/c/c1l0/c1l0_bom_trigger_gen_wl.htm
consolut - C1L0_BOM_TRIGGER_GEN_WL - EHS: BOMBOS - Initialisierung; Erstellung BOM-Eintrag in ESTWL (sorry I found by hazard only german klink; but there is similar link in english)
May be check as well: SAP EHS Management for Beginners; some references to threads regaridng BOMBOS are available there as well.
C.B.

Bdc and lsmw

Hi All,
I am presuming that both bdc's and lsmw are being used for data migration. if this is right then when would someone prefer bdc over lsmw or vice versa. if my assumption is wrong then tell me for what specifications we use lsmw and for what specs we use a bdc.

Hi,
"The Data Transfer Workbench (or DX Workbench, transaction SXDA) is an integrated SAP tool that supports data transfer and analysis. It
does not have the built-in features for mapping for source structures to target structures, but it will allow you to integrate Legacy System Migration Workbench (LSMW) objects as processing tasks within a run definition. The DX workbench has many features for creating
test data and performing data migrations - for example, logging of data migration runs.
However, if you need to map or convert data, you should use the LSMW. Or, you can integrate
your LSMW objects as task within a more user-friendly data migration run, in which the LSMW
project steps "Read data", "Convert data," and "Start IDoc processing" are automated
and use the features of both tools. If you donot need logging and automated data migration
runs, you can perform your data migration without the DX Workbench."
The following was taken at this site :
http://www.info-sun.com/docs/wp_sapinter.pdf
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a
typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program. Typically the input comes in the form
of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The
transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling.
It can also be used for real-time interfaces and custom error handling & logging features. Whereas in Batch Input Sessions, the ABAP
program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using
Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the
BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and
invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate
fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are
not available for all application areas.
Remote Function Call (RFC) in SAP R/3 is based on UNIXs Remote Procedure Call (RPC). RFC enables the real-time link between different R/3 instances and can connect SAP to Non-SAP systems. With Remote Function Call, both inbound (RFCServer) and outbound (RFCClient) interfaces are possible.
SAP also provides a toolkit called RFC API for non-SAP systems to interact with SAPs Function modules remotely.
RFC is a very powerful tool for interfacing with SAP system in real time. Most other interfacing techniques like ALE, EDI, BAPI etc are
inherently based on the RFC technology.
Electronic Data Interchange (EDI) is the industry standard format for exchanging Business data. SAP uses a neutral format called Intermediate Document
(IDoc) for communicating EDI & ALE messages.
The IDoc interface contains data structures and processing logic for each of the business transaction. These are grouped as Message
Types. The external EDI Server is responsible for receiving the EDI messages sent by the trading partners. These EDI messages are then
mapped onto the IDoc structure fields and stored in the IDoc interface layer by SAP.
EDI/IDoc supports both inbound and outbound interfaces. The IDocs received through the EDI Server can be configured to automatically get
processed, or can be stored in the IDoc interface layer for a future manual or scheduled processing. The IDoc interface layer also has a powerful error
handling, reporting, monitoring and reprocessingmechanism built into it (Transaction WEDI). IDoc is also tightly integrated with the WorkFlow system
of SAP for initiating other business tasks upon receiving/sending EDI messages.
The IDoc interface can be employed for non-SAP applications to load or extract data from SAP system. But typically, EDI / IDoc is engaged when
SAP system is to be integrated with any of its business partners (Customers, Suppliers and other partners) for carrying out standard business
transactions (like Create Sales orders, Sending Purchase orders to Suppliers, etc).
Application Link Enabling (ALE) is a middleware tool, which is part of SAPs Business framework Architecture (BFA). ALE can effectively be used
for loosely coupled Asynchronous communication between SAP systems and with non-SAP systems. ALE is based on the distributed processing
architecture and hence integrates applications with the local database rather than centralized one. ALE messages are based on the Intermediate
Document (IDoc) format, similar to the EDI counterpart. Though ALE can be used to interface with non-SAP systems, usually it is used to
distribute Master & Transactional data between SAP R/3 instances.
The ALE distribution can be based on,
Business APIs
IDoc Message Types"
Business API (BAPI) is the most important component of SAP Business Framework. BAPI enables SAP and third party applications to interact and integrate
with each other at the Business Object / Process level.

What is BDC and LSMW? Difference

Dear experts!
Explore the concept of BDC and LSMW and their difference.
Merits/Demerits.
Transactions used for executing and viewing the same.
Rishi.

Rishi,
Hope these links help you:
http://sap-img.com/bdc.htm
http://sap-img.com/sap-data-migration.htm
http://sap-img.com/sap-data-migration.htm
https://websmp206.sap-ag.de/lsmw
LSMW
Data Migration from Non-SAP Systems to SAP systems* Made Easy
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.
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).
Detailed Information
Objectives
High Flexibility to Ensure the Optimal Solution
The Data Transfer Workbench gives you control of the SAP data transfer interfaces: from proven batch input, through very fast direct input, to Business APIs (BAPIs), which are also suitable for permanent interfaces. This solution is sufficient if certified partner products are available for the transfer of open interfaces, or if you explicitly want to do interface programming in ABAP or the language of the legacy system. SAP provides its customers with the Legacy System Migration (LSM) Workbench, which dramatically reduces the considerable expenditure involved in individual programming. This tool makes it possible to transfer data without any programming. You define the rules for the changeover. The LSM Workbench then uses this definition to generate an ABAP program and thus gives you considerable support during the migration.
Description
Data Migration Controlled by your SAP System
In contrast to many conventional approaches, the solution described here is a component of your SAP system. As a result it is no longer necessary to program in a number of different systems. All you need are basic unloading programs in the legacy system, or, alternatively, existing data interfaces can be used. Everything else takes place in the SAP system. With SAP R/3 Release 4.6C the LSM Workbench is also integrated into the Data Transfer Workbench, and can be called up there.
Maximum Quality
Data migration with the Data Transfer Workbench and the LSM Workbench guarantees maximum quality and consistency of your data in the SAP system. When data is imported, the system performs the same checks as it does during online entry. The update in your database is performed through the Standard Batch Input Program, the Standard Direct Input Program, IDOC interfaces, and R/3 System BAPIs.
Proven Concepts
SAP has already gathered over seven years of migration experience with its own products. The LSM Workbench has been developed on the basis of experience gained with the R/2-R/3 Migration Workbench. In the meantime, the LSM Workbench has also been successfully used over 500 times in the migration of legacy systems to R/3.Concepts and techniques that have proven their worth form the backbone of the LSM Workbench:
Transfer of business data objects (such as material master data) instead of individual tables
Definition of flexible conversion rules that are adapted as part of migration customizing
Automatic generation of a conversion program
Synergy Effects through Uniform Procedures
SAP's experience shows that certain algorithms and techniques appear over and over again during data conversion projects. These techniques have been standardized in the LSM Workbench and can be called at the touch of a button. With this concept of central rules you can ensure, for example, that your vendor numbers are converted in the same way in both your vendor master data and in your purchase orders. This uniform procedure guarantees the consistency of your data and captures synergy effects in cases where you need to migrate data from disparate legacy systems.
Importing Data from PCs
More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
Data Verification before Update in the Database
The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
Substantial Reduction of Effort
SAP's experiences show that using the Data Transfer Workbench in conjunction with the LSM Workbench can reduce the effort required for data migration by 30% and more.
Project Library - A Knowledge Database
The LSM Workbench is a learning tool: The experience gained in other implementation projects is continually fed into the LSM Workbench, where it directly benefits your project.

Pur. Info Records by BAPI and Idoc

Hi,
Am uploading Purchasing Info Records by LSMW-Direct method.
Can anyone guide to do the same by BAPI and also by Idoc method...
Please let me know the advantages and disadvantages for the above methods over another.
Thanks

Idoc type :INFREC01
message type : INFREC
FM : IDOC_INPUT_INFREC
I have done output and above details are inbound ,i guess it should work
I do not know about BAPI ..
Thanks
Seshu

Bapi and lsmw.

Similar Messages

Maybe you are looking for