Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

when u already have predefined tool LSMW for uploading
data....which is more easy and efficient to use and les
sprogramming is required..then whats the need to write a
program in BDC....
whats the main purpose....?

Answer Posted / nandy

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/backgrou nd
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.

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

i hope it is clear

plz do let me know, if any update.

regards

Govardan.

Is This Answer Correct ?    4 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

What actually happens in real-time recruitment? : sap abap hr

1043


What are the different types of the variable in the sap abap?

1124


Write the bdc table structure? : abap bdc

1035


Which transaction code can I used to analyze the performance of ABAP program.?

1121


What is the tcode to create indexes?

1023


What is the collect statement? How is it different from append?

1052


Difference between sy-tabix and sy-index? Where it is used? Can you check sy-subarc after perform?

1075


Define infotype ? : abap hr

1261


What does an exec sql statement do in abap?

1173


1)can any body tell the transport request number concept and 2)there are 3 screens in one screen u have uploaded the resume and second screen also u have done the same thing but when u are uploading the resume in third screen u got some error in somewhere else but whatever u have uploaded the resume in 1 and 2 should not

2159


What is the difference between a substructure and an append structure?

1222


Have you set up a back ground job ? How to create a background job without a variant ?

1048


correct all performance problem without changing any functionality REPORT z_assignment_01. DATA: gt_user TYPE TABLE OF usr02 WITH HEADER LINE, gt_user_role TYPE TABLE OF agr_users WITH HEADER LINE, ********** DO NOT CHANGE THIS SECTION ********** g_begintime TYPE i, g_endtime TYPE i, g_tottime TYPE i. DATA: BEGIN OF gt_output OCCURS 0, bname LIKE usr02-bname, name_text LIKE adrp-name_text, agr_name LIKE agr_users-agr_name, text LIKE agr_texts-text, role_count TYPE i, END OF gt_output. TYPE-POOLS: slis. START-OF-SELECTION. GET RUN TIME FIELD g_begintime. ********** END NO CHANGE ********** SELECT * INTO TABLE gt_user FROM usr02 WHERE class > 'E'. SELECT * INTO TABLE gt_user_role FROM agr_users FOR ALL ENTRIES IN gt_user WHERE uname = gt_user-bname. PERFORM combine_tables. PERFORM get_addl_data. ********** DO NOT CHANGE THIS SECTION ********** GET RUN TIME FIELD g_endtime. g_tottime = ( g_endtime / 1000000 ) - ( g_begintime / 1000000 ). MESSAGE s398(00) WITH g_tottime. PERFORM output. ********** END NO CHANGE ********** *&---------------------------------------------------------------------* *& Form combine_tables *&---------------------------------------------------------------------* * Combine user and role tables *----------------------------------------------------------------------* FORM combine_tables. DATA: ls_usr21 TYPE usr21, ls_adrp TYPE adrp, ls_texts TYPE agr_texts. LOOP AT gt_user. * Get user name SELECT * INTO ls_usr21 FROM usr21 WHERE bname = gt_user-bname. SELECT * INTO ls_adrp FROM adrp WHERE persnumber = ls_usr21-persnumber. gt_output-name_text = ls_adrp-name_text. ENDSELECT. ENDSELECT. LOOP AT gt_user_role WHERE uname = gt_user-bname. * Only process roles that are currently active CHECK gt_user_role-from_dat <= sy-datum AND gt_user_role-to_dat >= sy-datum. * Get role text SELECT * INTO ls_texts FROM agr_texts WHERE agr_name = gt_output-agr_name AND spras = sy-langu AND line = 0. gt_output-text = ls_texts-text. ENDSELECT. gt_output-bname = gt_user-bname. gt_output-agr_name = gt_user_role-agr_name. APPEND gt_output. ENDLOOP. ENDLOOP. ENDFORM. " combine_tables *&---------------------------------------------------------------------* *& Form get_addl_data *&---------------------------------------------------------------------* * Get extra fields *----------------------------------------------------------------------* FORM get_addl_data. DATA: l_count TYPE i. * Count number of roles per user SORT gt_user_role BY uname. LOOP AT gt_user_role. ADD 1 TO l_count. AT END OF uname. LOOP AT gt_output WHERE bname = gt_user_role-uname. gt_output-role_count = l_count. MODIFY gt_output. CLEAR l_count. ENDLOOP. ENDAT. ENDLOOP. ENDFORM. " get_addl_data *&---------------------------------------------------------------------* *& Form output *&---------------------------------------------------------------------* * Output report *----------------------------------------------------------------------* FORM output. DATA: lt_fieldcat TYPE slis_t_fieldcat_alv, ls_fieldcat TYPE slis_fieldcat_alv, l_repid LIKE sy-repid, ls_layout TYPE slis_layout_alv, ls_variant TYPE disvariant. l_repid = sy-repid. CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE' EXPORTING i_program_name = l_repid i_internal_tabname = 'GT_OUTPUT' i_inclname = l_repid CHANGING ct_fieldcat = lt_fieldcat EXCEPTIONS inconsistent_interface = 1 program_error = 2 OTHERS = 3. IF sy-subrc <> 0. MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. ENDIF. ls_fieldcat-seltext_l = 'Role Count'. ls_fieldcat-seltext_m = 'Role Count'. ls_fieldcat-seltext_s = 'Role Count'. ls_fieldcat-reptext_ddic = 'Role Count'. MODIFY lt_fieldcat FROM ls_fieldcat TRANSPORTING seltext_l seltext_m seltext_s reptext_ddic WHERE fieldname = 'ROLE_COUNT'. ls_layout-zebra = 'X'. ls_layout-colwidth_optimize = 'X'. CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY' EXPORTING is_layout = ls_layout it_fieldcat = lt_fieldcat i_save = 'A' is_variant = ls_variant TABLES t_outtab = gt_output EXCEPTIONS program_error = 1 OTHERS = 2. IF sy-subrc <> 0. MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4. ENDIF. ENDFORM. " output

2490


What is read line in abap?

1118


What are the components of sapscript?

1073