topic Re: Diff between BDC and LSMW in Application Development and Automation Discussions

Diff between BDC and LSMW

Former Member — Mon, 21 Nov 2005 07:14:36 GMT

I have some fundamental doubts ...would u plz clarify ...

Difference between BDC and LSMW.

Difference between macro and subroutine

Difference between change request- customizing request

Re: Diff between BDC and LSMW

jayanthi_jayaraman — Mon, 21 Nov 2005 07:27:28 GMT

Hi,

Check this for macro.

http://help.sap.com/saphelp_47x200/helpdata/EN/9f/db972835c111d1829f0000e829fbfe/frameset.htm

Generally we use sub-routine inside the program.

Diff. between BDC and LSMW.

"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 doesn’t 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.

Kindly reward points by clicking the star on the left of reply,if it helps.

Re: Diff between BDC and LSMW

Former Member — Mon, 21 Nov 2005 07:53:49 GMT

hi, man

list my explain as following:

Difference between BDC and LSMW:

BDC is a technology for run the transaction without manually input. It is used as data inbound into SAP system. SHDB can record the screen process you want.

LSMW is a tools for data migration. It support several way to inbound data into SAP system, include BDC, and IDOC, BAPI and direct input.

Difference between macro and subroutine :

Macro is the same conception as it in C or C++.

just a replacement for the the code you call it.

E.G.


DEFINE OUTPUT.
  data: t  type c.
   WRITE: / 'The result of &1 &2 &3 is', &4.
END-OF-DEFINITION.

output 4 3 3 3.
output 4 3 3 3.

this is a macro, but it will be fail in compile, because Macro is only a replacement for the code.

so using the Macro, the above code is equal to below:

  
  data: t  type c.
   WRITE: / 'The result of 4 3 3 is', 3.
  data: t  type c.
   WRITE: / 'The result of 4 3 3 is', 3.

As a replace, the T has been redelare, so it failed.

But for subroutin, it will transfer the parameter, and run the code in subrountine. So the above restriction on Macro won't happen in Subroutine.

Difference between change request- customizing request :

workbench request is for application, project, FM, Function group, all the ABAP work object in system. You can bind a request to them using workbench request and transport them to other system.

Customizing request is all the setting in system.

E.G. a consulant do some configuratin on table TXXX in IMG, he don't want to reconfigure again in other system. Then he bind this setting in customizing request, and transfer it to target system.

That's all.

Hope it will be helpful

thanks

Re: Diff between BDC and LSMW

Former Member — Mon, 21 Nov 2005 07:56:11 GMT

1. BDC - Batch Data Communication

LSMW - Legacy System Migration Workbench

2. Please go to this link for macros and subroutines.

http://help.sap.com/saphelp_47x200/helpdata/en/9f/db972835c111d1829f0000e829fbfe/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm

3. Change Request is an information source in the Transport Organizer that records and manages all modifications made to Repository objects and Customizing settings during a development project.So that you can differentiate between global changes to the system and client-specific Customizing settings, the CTS records your changes in either a Workbench request or a Customizing request:

Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).

Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.

Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.

Cheers

Afsal

Re: Diff between BDC and LSMW

Former Member — Mon, 21 Nov 2005 08:08:03 GMT

I hope u r clear abt lsmw and change request.

I will provide some basic dif between subroutine & Macro

In macro u have to pass only 9 parameters.

where in sroutine u can pass any number.

In macro u can pass operators also suppose if u want to do 4 basic math operations.

u can pass operator as a parameter.

4 + 3 or 4 -3 or 4 * 3 etc.

where in rotuines u can't pass this operator symbols as parameters.

In macro there is no concept like internal & External, where as u know that in subroutines u have internal routines and external routines.

Hope u r clear abt syntax with previous postings.

Reward points , if this helps.

Regards,

Raja

Re: Diff between BDC and LSMW

Former Member — Mon, 21 Nov 2005 08:52:19 GMT

Hi,

Chek out this link:

Best Regards,

Anjali