Differences

Former Member — Tue, 13 May 2008 20:46:11 GMT

Hi friends,

Can u plz tell d

1) Difference b/w Smartforms and SAP scripts

2) Difference b/w LSMW and BDC.

3) Difference b/w Classical and Interactive Report

Re: Differences

Former Member — Tue, 13 May 2008 20:54:44 GMT

Hi,

SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. Client dependence is a fundamental one. Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively ...

1. script is client dependent one while smartform is client independent.

2. In scripts we have to write print program while in smart forms it is not necessary.

3. In scripts we can print background logo while in smartforms we cant print background logo

4. In scripts we have 99 main windows while in smartforms we have only 1 main window.

5. In scripts we should write paragraph format otherwise we cant execute program while in smartforms no need to create paragraph formats .

6. In scripts we can print the text in only two character formats.

while in smartforms we can do with more.

7. In scripts we dont have line types while in smartforms we have linetypes.

also refer

the main diffarences between smart form and script form are:

1) smart forms are clinent independent where as scripts are client dependent.

2) smart form require half the time to create and maintain forms compare with

script.

3) smart forms provide multiple page formats where as in script not possible

4) smart forms exisist without main window also where as in script not possible.

5) smart form is entairely graphical user interface comapre with script.

6) labeling is not possible in smart form where as it is possible in script.

7) smart form genarate function module whenver it activate where as script

doesn't genarate.

😎 smart form can easily web publishing using the genarated XML output compare

with script.

9) using smart forms we can design web forms but bot possible with script.

10) we can maintain background graphics in smartform wher as in script not

possible.

11) in smart form we use transaction codes SMARTFORM for designing FORM

and SMARTSTYLES to create differnt styles of text, where as in script we

use SE71 for form painter and SE72 for different styles of text and font.

12) we can migrate script to smart form vice-versa is not possible.

LSMW IS JUST A TOOL TO GET THE DATA FROM A LEGACY SYSTEM.

IN BDC WE HAVE 2 WRITE THE CODE AND CALL THE REQUIRED METHOD

THATS IT. IN FUNCTIONALITY PERSPECTIVE THERE IS NO

DIFFERENCE.

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

The main difference between classical reports and interactive reports are the following:

1. Classical reports can have only one list display where as interactive reports can have upto 21 list displays.

2. events in In classical reports, :

a. INTIALIZATION: This event triggers before selection screen display.

b.AT-SELECTION-SCREEN: This event triggers after proccesing user input still selection screen is in active mode.

c.START OF SELECTION: Start of selection screen triggers after proceesing selection screen.

d.END-OF-SELECTION

Interactive Reports

As the name suggests, the user can Interact with the report. We can have a drill down into the report data. For example, Column one of the report displays the material numbers, and the user feels that he needs some more specific data about the vendor for that material, he can HIDE that data under those material numbers.

And when the user clicks the material number, another report (actually sub report/secondary list) which displays the vendor details will be displayed.

We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21).

Events associated with Interactive Reports are:

AT LINE-SELECTION

AT USER-COMMAND

AT PF<key>

TOP-OF-PAGE DURING LINE-SELECTION.

HIDE statement holds the data to be displayed in the secondary list.

sy-lisel : contains data of the selected line.

sy-lsind : contains the level of report (from 0 to 21)

Interactive Report Events:

AT LINE-SELECTION : This Event triggers when we double click a line on the list, when the event is triggered a new sublist is going to be generated. Under this event what ever the statements that are been return will be displayed on newly generated sublist.

AT PFn: For predefined function keys...

AT USER-COMMAND : It provides user functions keys.

TOP-OF-PAGE DURING LINE-SELECTION :top of page event for secondary list.

Regards,

Re: Differences

Former Member — Tue, 13 May 2008 20:57:48 GMT

Hi,

Refer the threads given below...

Difference between sap scripts and smartforms

Difference Between LSMW and BDC

Difference between Classical Reports and Interactive Reports

Hope it is helpful...

Regards,

Chithra

Edited by: Chithra Saravanan on May 14, 2008 2:28 AM

topic Differences in Application Development and Automation Discussions

Differences

Re: Differences

Re: Differences