one question

[Former Member]

How can I decide whether I should go for LSMW / BAPI / BDC / CATT for Master and Transactional data.....

If I want to schedule it in Background with a period time then which one I should opt for ?

[Former Member]

they all have theire pluses and minuses.

LSMW = more config work

BAPI = faster

BDC = error capturing

[Former Member]

Hi,

The selection of the method depends on the requirement.

LSMW: Large volumes of data and in between SAP and NONSAP systems.

BAPIs are used to communicate between SAP and SAP aswellas NONSAP to SAP and vicecersa.

BDC is used to upload data from datafile only. Moreover we can handle error situation in case of errors

CATT is generally used for testing the functionlity of FM and transactions.

In general we can use background scheduling for LSMW and BDCs.

Based on NO of records, error handling , type of data to upload , etc selection of above methods is done.

Reward points if helpful.

thanks and regards.

[Former Member]

you don't need an external system (SAP to SAP, non-SAP to SAP etc..) to use BAPIs - they are RFC-enabled to allow for this, but you can jsut as easily use them in a standalone SAP system.

[SureshRa]

Hi,

In all situations, LSMW is the best option. LSMW can be based on IDoc, BAPI, Batch input program or Direct recording of TCode.

In all the above scenarios, LSMW provides user the ultimate flexibility in preparing file. Once the file contents are read and converted, the converted file resides in application server.

You can either schedule the posting in back-ground or run in fore-ground. If your method is Batch input or Direct TCode recording, user has an option of creating sessions. These sessions can be processed later either in fore-ground or in background through TCode SM35.

If you need to use a BAPI under LSMW, you need to have the following pre-requisites:

- The Remote-Enabled Function Module should be configured as an API to a business object. (This is the fundamental difference betweeen an Remote Enabled Function Module and BAPI.

- ALE message type for the above BAPI is to be generated.

Due to the above LSMW is the champion choice for data conversion.

Let us look into some of the demerits of other options:

CATT: This is basically a test tool. SAP recommends that this be used only for test purposes. SAP also recommends the maximum volume be limited to a few hundred records. This should not be used for uploading huge amount of data in production environment. You can use this tool to test your transactions and Function Modules.

BAPI: Synchronous call from an external system. This should be a choice only for ongoing interface and not for one time load of huge amount of data.

BDC: Yes this is also a good choice for large volume of data upload. However user has no flexibility on useage. The BDC program you have developed constraints the user with the file layout, selection screen options, etc. Also if the program is executed in back-ground, the input file itself should be in application server.

Hope the above helps,

Regards

Suresh Radhakrishnan

[Former Member]

I would disagree with the statement that "In all cases LSMW is the best option".

also, as i pointed out above, you if you want to use a BAPI to load your data you don't need an external system. that's just a big benefit of BAPIs.

You would have to catch any errors for later processing, but it is fast.

EDIT: Also, you don't have to get ALE involved at all if you're using BAPIs to load data. you just upload your data to an itab. loop at your itab, fill the BAPI and commit it and on to the next record. piece of cake.

Edited by: robert phelan on Jun 3, 2008 7:21 PM