Object and Business Object

Hi this solves ur doubt.

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

Let’s 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.saptechnical.com

with regards,

Hema.

pls reward if helpful.

Also, LSMW_BDC:

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

with regards,

Hema.

pls reward if helpful.