Disadvantages of Using BDC over BAPI

Hello ,
could you please clear my confusion as why BDC are not supposed to be used for data uploading over bapis.
What are the advantages and disadvantages between BDC and BAPI
thanks in Advance
PAvan

Hi Pavan,
BDC is slower because it additionally processes the screens. This is a big disadvantage (could be more than 10 times slower). An advantage on BDC processing is that you can later view an process the data manually.
With BAPIs (which are not necessarily OO) you have to have some error handling in place if one of the imported data sets fails (sometimes done with restartable jobs, look for example into the documentation of RFBIBL00).
Also, as already mentioned, changes of the screen layout and/or the GUI status will very likely make your BDC sessions fail (no matter these changes were caused by customising settings or a patch).
Regards, Gerd Rother

Similar Messages

ABAP interfaces build using BDC and BAPIs can be used/replaced with the XI?

Hi,
We have develeloped our interfases using BDC and BAPIs. Now our client has decited to implement XI. Now could you please help in finding whether these interfaces can be used/replaced with the XI.
If yes, please let us know how?
Thanks and Regards,
Shweta

Singh,
Check this threads where they have discussed on how to use them with XI:
import BAPI into XI
Re: interface of xi with bapi
Re: BDC
Regards,
---Satish

Disadvantages of Using BDCs in enhancements

Hi All,
Could anybody please tell me what are the possible disadvantages of using BDCs in a complex enhancement.
Thanks,
Anirban.

Hi,
One of the very common disadvantage of the BDC is that it doesnt take into account the configuration settings of the screen. Suppose you make any changes in the screen fields (e.g. you make some of the fields in the screen non editable or you make the fields invisible), in this case BDC will throw an error message beacuse the screen mentioned will now no more contain that field or the field will now no more will be an input field.
If at all there is change in the screen settings or transaction look and feel is changed or screen manouvering is changed in the transaction then the BDC will fail and will give error messages.
This is the major disadvantage of using a BDC
Reward points if found useful
Mayank Agarwal

Reg: Modification of Master Tables using BDC/BAPI

Dear All,
Thanks for Support shown from all of you.
I want the detailed procedure for Modifying the existing data in the Master Tables using BDC's / BAPI's and Dialog programming.
Please send me one example code.
Please Help me Out.
Thanks In Advance.
Regards,
Adinarayana.B

bapi example
REPORT ZMMR_DELETEPO NO STANDARD PAGE HEADING MESSAGE-ID zisb.
tables : zvtls_sap.
*C-- Types Declarations
TYPES : BEGIN OF tp_flatfile_vtls,
 ebeln(10),
 ebelp type ekpo-ebelp,
 END OF tp_flatfile_vtls.
*=====================================================================
 INTERNAL TABLES DECLARATION
*=====================================================================
DATA: t_flatfile_vtls TYPE tp_flatfile_vtls OCCURS 0 WITH HEADER LINE.
data : begin of t_sapdata occurs 0,
 po like zvtls_sap-posap,
 item like zvtls_sap-itemsap,
 end of t_sapdata.
data : begin of t_flatfile_vtls1 occurs 0,
 po(10),
 item like zvtls_sap-itemsap,
 end of t_flatfile_vtls1.
data : begin of t_update occurs 0,
 mandt like zvtls_sap-mandt,
 povtls like zvtls_sap-povtls,
 itemvtls like zvtls_sap-itemvtls,
 posap like zvtls_sap-posap,
 itemsap like zvtls_sap-itemsap,
 aedat like zvtls_sap-aedat,
 paedt like zvtls_sap-paedt,
 loekz like zvtls_sap-loekz,
 end of t_update.
data : begin of t_poheader occurs 0,
 po like zvtls_sap-posap,
 end of t_poheader.
data : begin of t_poitem occurs 0,
 po like zvtls_sap-posap,
 item like zvtls_sap-itemsap,
 end of t_poitem.
DATA : BEGIN OF T_MESSAGE OCCURS 0,
 MSGTY,
 MSGID(2),
 MSGNO(3),
 MSGTX(100),
 PO like zvtls_sap-povtls,
 item like zvtls_sap-itemvtls,
 END OF T_MESSAGE.
DATA : BEGIN OF t_bapi_poheader OCCURS 0.
 INCLUDE STRUCTURE bapimepoheader.
DATA : END OF t_bapi_poheader.
DATA : BEGIN OF t_bapi_poheaderx OCCURS 0.
 INCLUDE STRUCTURE bapimepoheaderx.
DATA : END OF t_bapi_poheaderx.
DATA : BEGIN OF t_bapi_poitem OCCURS 0.
 INCLUDE STRUCTURE bapimepoitem.
DATA : END OF t_bapi_poitem.
DATA : BEGIN OF t_bapi_poitemx OCCURS 0.
 INCLUDE STRUCTURE bapimepoitemx.
DATA : END OF t_bapi_poitemx.
DATA : BEGIN OF t_bapireturn OCCURS 0.
 INCLUDE STRUCTURE bapiret2.
DATA : END OF t_bapireturn.
*=====================================================================
 V A R I A B L E S
*=====================================================================
DATA: w_success(6) TYPE n,
 w_bklas like t023-bklas,
 w_curryear(4),
 w_begda like sy-datum,
 w_endda like sy-datum,
 w_begyr(4),
 w_endyr(4),
 w_currmon(2),
 w_assetclass like ankt-anlkl,
 w_price type p,
 w_recordsap type i,
 w_povtls(10),
 w_count type i.
DATA: w_filepath TYPE rlgrap-filename,
 w_rc TYPE sy-subrc,
 w_sscrfields_ucomm1 TYPE sscrfields-ucomm,
 w_file1 TYPE string,
 w_file2 TYPE FILENAME-FILEINTERN.
*=====================================================================
 C O N S T A N T S
*=====================================================================
CONSTANTS: c_x TYPE c VALUE 'X',
 c_hyp TYPE c VALUE '-',
 c_err TYPE bdc_mart VALUE 'E'.
CONSTANTS: c_slash(1) TYPE c VALUE '/',
 c_hash(1) TYPE c VALUE '#',
 c_pipe TYPE c VALUE '|',
 c_1 TYPE i VALUE 1,
 c_zero TYPE n VALUE '0',
 c_rg1(3) TYPE c VALUE 'rg1',
 c_gr3(3) TYPE c VALUE 'GR3',
 c_gr2(3) TYPE c VALUE 'GR2',
 c_e(1) TYPE c VALUE 'E',
 c_filepath(8) TYPE c VALUE '/interf/',
 c_filetype(10) TYPE c VALUE 'ASC'.
CONSTANTS : c_bapimepoheaderx TYPE x030l-tabname
 VALUE 'bapimepoheaderx',
 c_bapimepoitem TYPE x030l-tabname
 VALUE 'bapimepoitem',
 c_bapimepoaccount TYPE x030l-tabname
 VALUE 'bapimepoaccount',
 c_t_bapi_poheader(15) TYPE c
 VALUE 't_bapi_poheader',
 c_t_bapi_poitem(13) TYPE c
 VALUE 't_bapi_poitem',
 c_t_bapi_poitemx(14) TYPE c
 VALUE 't_bapi_poitemx',
 c_t_bapi_poheaderx(16) TYPE c
 VALUE 't_bapi_poheaderx'.
CLASS cl_abap_char_utilities DEFINITION LOAD.
CONSTANTS:con_tab TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
*======================================================================
 SELECTION SCREEN
*======================================================================
SELECTION-SCREEN BEGIN OF BLOCK inputpath WITH FRAME TITLE text-001.
SELECTION-SCREEN : BEGIN OF BLOCK blk2 WITH FRAME TITLE text-002.
PARAMETERS : p_fore RADIOBUTTON GROUP rg1
 USER-COMMAND pc,
 p_back RADIOBUTTON GROUP rg1 DEFAULT 'X'.
SELECTION-SCREEN : END OF BLOCK blk2.
SELECTION-SCREEN : BEGIN OF BLOCK blk1 WITH FRAME TITLE text-003.
PARAMETERS : p_file1 LIKE rlgrap-filename OBLIGATORY MODIF ID gr2.
PARAMETERS : p_afile1 LIKE rlgrap-filename OBLIGATORY MODIF ID gr3.
SELECTION-SCREEN : END OF BLOCK blk1.
SELECTION-SCREEN END OF BLOCK inputpath.
*C-- Initialization Event
INITIALIZATION.
CLEAR w_filepath.
CONCATENATE c_filepath sy-sysid c_slash sy-mandt c_slash INTO
w_filepath.
CONDENSE w_filepath NO-GAPS.
p_file1 = text-008.
p_afile1 = text-009.
*======================================================================
 SELECTION SCREEN EVENTS
*======================================================================
*C-- Selection Screen Output
AT SELECTION-SCREEN OUTPUT.
IF p_fore = c_x.
 w_sscrfields_ucomm1 = space.
ELSE.
 w_sscrfields_ucomm1 = c_rg1.
ENDIF.
LOOP AT SCREEN.
*C--Modify selection screen if presentation
*C--or application server radio button is chosen
 IF w_sscrfields_ucomm1 = space.
 IF screen-group1 = c_gr3.
 screen-active = c_zero.
 ENDIF.
 ELSE.
 IF screen-group1 = c_gr2.
 screen-active = c_zero.
 ENDIF.
 ENDIF.
 if screen-name = 'P_AFILE1'.
 screen-input = 0.
 ENDIF.
 MODIFY SCREEN.
ENDLOOP.
*C-- Selection Screen VALUE-REQUEST FOR File path
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file1.
IF p_fore EQ c_x.
 CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 program_name = syst-cprog
 dynpro_number = syst-dynnr
 IMPORTING
 file_name = p_file1.
ENDIF.
*C-- At Start of the Selection Process
START-OF-SELECTION.
IF p_fore EQ c_x.
 w_file1 = p_file1.
ELSE.
 w_file2 = p_afile1.
ENDIF.
IF p_fore EQ c_x. " Presentaion Server
*C--Validations for the input files
 PERFORM validate_pre_file USING p_file1.
*C-- Load the contents of the input file into the internal table
 PERFORM upload_file TABLES t_flatfile_vtls
 USING w_file1
 CHANGING w_rc.
 IF w_rc <> 0.
 MESSAGE s006 DISPLAY LIKE c_e.
 ENDIF.
ELSE. " Application Server
*C--Validations for the input files
 PERFORM validate_app_file USING w_file2.
*C-- Load the contents of the input file into the internal table
 PERFORM upload_file_app TABLES t_flatfile_vtls
 USING w_file2
 CHANGING w_rc.
ENDIF.
loop at t_flatfile_vtls.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = t_flatfile_vtls-ebeln
 IMPORTING
 output = t_flatfile_vtls1-po.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = t_flatfile_vtls-ebelp
 IMPORTING
 output = t_flatfile_vtls1-item.
 append t_flatfile_vtls1.
 clear t_flatfile_vtls1.
endloop.
perform get_podata.
loop at t_poheader.
 perform move_to_bapi.
 perform call_bapi.
endloop.
PERFORM STORE_MESSAGES TABLES T_MESSAGE.
*& Form validate_pre_file
 Routine to validate presentation server file path.
 -->fp_name text
FORM validate_pre_file USING fp_name TYPE rlgrap-filename.
DATA : l_result,
 l_filename TYPE string.
l_filename = fp_name.
CLEAR l_result.
CALL METHOD cl_gui_frontend_services=>file_exist
 EXPORTING
 file = l_filename
 RECEIVING
 result = l_result
 EXCEPTIONS
 cntl_error = 1
 error_no_gui = 2
 wrong_parameter = 3
 not_supported_by_gui = 4
 OTHERS = 5.
IF sy-subrc <> 0.
 MESSAGE s007 DISPLAY LIKE c_e.
 LEAVE LIST-PROCESSING.
ELSEIF l_result IS INITIAL.
 MESSAGE s008 DISPLAY LIKE c_e.
 LEAVE LIST-PROCESSING.
ENDIF.
ENDFORM. " validate_pre_file_hdr
*& Form validate_app_file
 text - Checks if the path entered and filename is correct
FORM validate_app_file USING fp_file TYPE FILENAME-FILEINTERN.
data : l_fname(60).
CALL FUNCTION 'FILE_GET_NAME'
 EXPORTING
 LOGICAL_FILENAME = FP_FILE
 OPERATING_SYSTEM = SY-OPSYS
 IMPORTING
 FILE_NAME = L_FNAME
 EXCEPTIONS
 FILE_NOT_FOUND = 1
 OTHERS = 2.
IF SY-SUBRC = '0'.
 OPEN DATASET L_FNAME FOR INPUT IN TEXT MODE ENCODING DEFAULT.
 IF sy-subrc NE 0.
 MESSAGE s007 DISPLAY LIKE c_e.
 ELSE.
 CLOSE DATASET l_fname.
 ENDIF.
ENDIF.
ENDFORM. " validate_app_file
*& Form upload_file
 Routine to upload data from file to tables.
 -->P_fp_flatfile
 -->P_fp_file
 <--P_fp_rc
FORM upload_file TABLES fp_flatfile
 USING fp_file TYPE string
 CHANGING fp_rc TYPE sy-subrc.
IF fp_flatfile[] IS INITIAL.
 CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 filename = fp_file
 filetype = c_filetype
 has_field_separator = c_x
 TABLES
 data_tab = fp_flatfile
 EXCEPTIONS
 file_open_error = 1
 file_read_error = 2
 no_batch = 3
 gui_refuse_filetransfer = 4
 invalid_type = 5
 no_authority = 6
 unknown_error = 7
 bad_data_format = 8
 header_not_allowed = 9
 separator_not_allowed = 10
 header_too_long = 11
 unknown_dp_error = 12
 access_denied = 13
 dp_out_of_memory = 14
 disk_full = 15
 dp_timeout = 16
 OTHERS = 17.
 MOVE sy-subrc TO fp_rc.
ENDIF.
ENDFORM. " upload_file
*& Form upload_file_app
 text
 -->FP_FLATFILEtext
 -->FP_FILE text
 -->FP_RC text
FORM upload_file_app TABLES fp_flatfile
 USING fp_file TYPE FILENAME-FILEINTERN
CHANGING fp_rc TYPE sy-subrc.
DATA: l_string TYPE tedata-data.
DATA: wa_data_file TYPE tp_flatfile_vtls,
 l_wllength TYPE i,
 FNAME(60).
CALL FUNCTION 'FILE_GET_NAME'
 EXPORTING
 LOGICAL_FILENAME = FP_FILE
 OPERATING_SYSTEM = SY-OPSYS
 IMPORTING
 FILE_NAME = FNAME
 EXCEPTIONS
 FILE_NOT_FOUND = 1
 OTHERS = 2.
IF SY-SUBRC = 0.
 OPEN DATASET FNAME FOR INPUT IN TEXT MODE ENCODING DEFAULT.
 IF sy-subrc NE 0.
*C-- commented by Bikash
 MESSAGE s107(yaero_ps) DISPLAY LIKE c_e.
 message e008.
 ELSE.
 DO.
 CLEAR: l_string.
 READ DATASET FNAME INTO l_string LENGTH l_wllength.
 IF sy-subrc NE 0.
 EXIT.
 ELSE.
 SPLIT l_string AT con_tab INTO wa_data_file-ebeln
 wa_data_file-ebelp.
 APPEND wa_data_file TO fp_flatfile.
 ENDIF.
 ENDDO.
 CLOSE DATASET FNAME.
 ENDIF.
ENDIF.
ENDFORM. " upload_file_app
*& Form get_podata
 text
form get_podata.
select *
into table t_update
from zvtls_sap
for all entries in t_flatfile_vtls1
 where itemvtls = t_flatfile_vtls1-item
and povtls = t_flatfile_vtls1-po.
sort t_update by posap itemsap.
loop at t_update.
 at new posap.
 t_poheader-po = t_update-posap.
 append t_poheader.
 clear t_poheader.
 endat.
 t_poitem-po = t_update-posap.
 t_poitem-item = t_update-itemsap.
 append t_poitem.
 clear t_poitem.
 t_update-paedt = sy-datum.
 t_update-loekz = 'X'.
 modify t_update.
endloop.
modify zvtls_sap from table t_update.
endform. "get_podata
*& Form move_to_bapi
 text
form move_to_bapi.
t_bapi_poheader-po_number = t_poheader-po.
CLEAR t_bapi_poheaderx.
PERFORM fill_check_structure USING c_bapimepoheaderx
 c_t_bapi_poheader
 c_t_bapi_poheaderx
 c_x.
refresh : t_bapi_poitem,t_bapi_poitemx.
loop at t_poitem where po = t_poheader-po.
 clear t_bapi_poitem.
 t_bapi_poitem-po_item = t_poitem-item.
 t_bapi_poitem-delete_ind = 'X'.
 CLEAR t_bapi_poitemx.
 PERFORM fill_check_structure USING c_bapimepoitem
 c_t_bapi_poitem
 c_t_bapi_poitemx
 c_x.
 t_bapi_poitemx-po_item = t_poitem-item.
 t_bapi_poitemx-po_itemx = c_x.
 APPEND t_bapi_poitem.
 APPEND t_bapi_poitemx.
 clear t_bapi_poitem.
 clear t_bapi_poitemx.
endloop.
endform. "move_to_bapi
*& Form call_bapi
 This form Routine is used to commit the data records
FORM call_bapi .
DATA : l_msgty TYPE c,
 l_msgid(2) TYPE c,
 l_msgno(3) TYPE c,
 l_msgtx(100) TYPE c,
 l_errflag TYPE c.
CLEAR: t_bapireturn.
REFRESH: t_bapireturn.
CALL FUNCTION 'BAPI_PO_CHANGE'
 EXPORTING
 PURCHASEORDER = T_POHEADER-PO
 POHEADER = T_BAPI_POHEADER
 POHEADERX = T_BAPI_POHEADERX
 TABLES
 RETURN = T_BAPIRETURN
 POITEM = T_BAPI_POITEM
 POITEMX = T_BAPI_POITEMX.
READ TABLE t_bapireturn WITH KEY type = c_err TRANSPORTING NO FIELDS.
IF sy-subrc NE 0.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = c_x.
ENDIF.
*C-- Write messages
WRITE: / 'PO Number', t_poheader-po.
clear : t_update,w_povtls.
read table t_update with key posap = t_poheader-po.
w_povtls = t_update-povtls.
CLEAR l_errflag.
LOOP AT t_bapireturn.
 CLEAR: l_msgty, l_msgid, l_msgno, l_msgtx.
 l_msgty = t_bapireturn-type.
 l_msgid = t_bapireturn-id.
 l_msgno = t_bapireturn-number.
 l_msgtx = t_bapireturn-message.
 WRITE: / l_msgty, l_msgid, l_msgno, l_msgtx.
 if l_msgtx cs t_poheader-po.
 w_count = w_count + 1.
 loop at t_update.
 if sy-tabix = w_count.
 t_message-item = t_update-itemvtls.
 endif.
 endloop.
 endif.
 t_message-msgty = l_msgty.
 t_message-msgid = l_msgid.
 t_message-msgno = l_msgno.
 t_message-msgtx = l_msgtx.
 t_message-po = w_povtls.
 append t_message.
 clear t_message.
 IF l_msgty EQ c_err.
 l_errflag = c_x.
 ENDIF. " l_msgty EQ 'E'
ENDLOOP.
ULINE.
IF l_errflag NE c_x.
 w_success = w_success + 1.
ENDIF. " l_errflag NE C_X
endform. "call_bapi
*& Form fill_check_structure
 This form Routine will check whether the specified structure
 exist/active
FORM fill_check_structure USING fp_tabname TYPE any
 fp_orgtabname TYPE any
 fp_chktabname TYPE any
 fp_check TYPE c.
FIELD-SYMBOLS : <fs_chk>, <fs_org>.
DATA: l_char1(61) TYPE c,
 l_char2(61) TYPE c.
DATA: BEGIN OF tl_nametab OCCURS 60.
 INCLUDE STRUCTURE x031l.
DATA: END OF tl_nametab.
REFRESH tl_nametab.
CALL FUNCTION 'RFC_GET_NAMETAB'
 EXPORTING
 tabname = fp_tabname
 TABLES
 nametab = tl_nametab
 EXCEPTIONS
 table_not_active = 1
 OTHERS = 2.
IF sy-subrc <> 0.
 CLEAR tl_nametab.
ENDIF.
LOOP AT tl_nametab.
 CLEAR: l_char1, l_char2.
 CONCATENATE fp_chktabname c_hyp tl_nametab-fieldname INTO l_char1.
 ASSIGN (l_char1) TO <fs_chk>.
 CONCATENATE fp_orgtabname c_hyp tl_nametab-fieldname INTO l_char2.
 ASSIGN (l_char2) TO <fs_org>.
 IF <fs_org> IS NOT INITIAL.
 <fs_chk> = fp_check.
 ENDIF.
ENDLOOP.
ENDFORM. " fill_check_structure
*& Form STORE_MESSAGES
 text
 -->FP_MESSAGEStext
FORM STORE_MESSAGES TABLES FP_MESSAGES STRUCTURE T_MESSAGE.
DATA: wl_output_data LIKE t_MESSAGE.
DATA: l_catstr TYPE string.
DATA: l_fieldvalue TYPE string.
DATA: l_index TYPE i VALUE 1.
DATA: L_FNAME(60).
FIELD-SYMBOLS <fs>.
CLEAR l_catstr.
CALL FUNCTION 'FILE_GET_NAME'
 EXPORTING
 LOGICAL_FILENAME = '/USR/SAP/VTLS/POCHANGE/LOG'
 OPERATING_SYSTEM = SY-OPSYS
 IMPORTING
 FILE_NAME = L_FNAME
 EXCEPTIONS
 FILE_NOT_FOUND = 1
 OTHERS = 2.
IF SY-SUBRC = '0'.
 IF fp_messages[] IS NOT INITIAL.
 OPEN DATASET L_FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
 IF sy-subrc NE 0.
 LEAVE LIST-PROCESSING.
 ELSE.
 LOOP AT fp_messages INTO wl_output_data.
 DO.
 ASSIGN COMPONENT l_index OF STRUCTURE wl_output_data TO <fs>.
 IF sy-subrc <> 0.
 EXIT.
 ENDIF.
 MOVE <fs> TO l_fieldvalue.
 IF l_catstr IS NOT INITIAL.
 CONCATENATE l_catstr l_fieldvalue INTO l_catstr SEPARATED
 BY con_tab.
 ELSE.
 MOVE l_fieldvalue TO l_catstr.
 ENDIF.
 l_index = l_index + c_1.
 CLEAR l_fieldvalue.
 CLEAR <fs>.
 ENDDO.
 l_index = c_1.
 TRANSFER l_catstr TO L_FNAME .
 CLEAR wl_output_data.
 CLEAR l_catstr.
 ENDLOOP.
 CLOSE DATASET L_FNAME.
 ENDIF.
 ENDIF.
ENDIF.
ENDFORM. "STORE_MESSAGES

What is the disadvantages of using Serialization?

HAi all,
I want to store objects in a file. I am preferred to use serialization. But I want to know what are the disadvantages of using Serialization over other methods (direct file, Keyed File)?
Can we store as many records using serialization? Is there any limit? Is there any security related issues?
Pls help me.
regards,
namanc

I don't think there is disadvantage using serialization compare to direct i/o access to file or any storage, except that you need to design your code such as it is serializable (hence, you may want to use transient keyword, or use externalizable, to be able to store/load the object properly).
Use serialization if possible, it saves you from inventing new+uncompatible mechanism of doing something in java.

How to upload data useing BDC

hI SAP Guru's
here i have to upload non-sap data to sap , in the controling how to MAP the fileds and which T.code have use to please guide me

Dear Purna,
You would first need to identify the transaction for which you want to upload the data. For example KE51 to Create Profit Center. You could use BDC or BAPI methods. You can use LSMW tool as well.
you would need to map SAP fields with the corresponding legacy field. You would prepare a layout for the legacy file and accordingly design BDC.
Steps:
1. Fetch Data (Download/Read Dataset/Select from Tables)
3. Massage data as per SAP format.
3. Validation Check
4. Pass valid data to BDC (Call Transaction/Session) or BAPI
5. In case of session method - session log is generated. In case of Call transaction you can use an internal table with structure BDCMSGCOLL to get messages. In case of BAPI the messages will be returned in return table (strcutre BAPIRET2/BAPIRETTAB).
Hope this will help.
Regards,
Naveen.

IS THERE ANY SUITABLE BAPI'S To Upload data to F-02 ..OR we should use BDC

HI FRIENDS,
IS THERE ANY SUITABLE BAPI'S To Upload data to F-02 ..OR we should use BDC..
WAITING FOR UR REPLY?
THANKS.
KIRAN

Hi,
I need to change the BDC program which is already written for F-02 in 4.7E.The changes are like I need to add 8 new posting keys, Kindly let me know how I can do it ,if already have the coding for the same please share with me.
Thanks in advance,
Jyoti

Can anyone list problems/errors when uploading data using BDC's and BAPI's?

Can anyone list the problems/errors when uploading data using BDC's and BAPI's?

Hi,
If you are actually creating a BDC to load data pls be more specific.
Data format incorrect. Tab delimited/ etc
Dates in wrong formats
Currency incorrect formats
Missing screens
Wrong transaction code
File not found,
Missing Mandatory fields,
Screen resoultion.
You should always use refresh for your Bdcdata table.
Loop at internal table.
refresh Bdcdata.
regards,
sowjanya.

What are the advantages/disadvantages of using PS/CS5 in 64bit over 32bit please?

What are the advantages/disadvantages of using PS/CS5 in 64bit over 32bit please?

From a practical perspective, besides the 64 bit version being a bit faster at just about everything, limitations on document size are lifted in the 64 bit version. Essentially, how much can do is limited only by how much RAM you have installed in your system. You can do things like have larger documents, deeper history, etc. and have it all work quickly.
On the other hand, many 3rd party plug-ins, especially older ones, only provide 32 bit versions, which will only run in 32 bit Photoshop.
Both 32 and 64 bit versions are installed by default. It's important to note that most of the preferences are separate between the two, so you can have two slightly different setups that might help with specialty operations you might need. This gets pretty subtle, but for example I keep the 32 bit version configured with only 1 cache level, so all previews of high bit depth images are always composited in high bit depth. This aids me with some aspects of astroimage processing. It's slower, but more accurate. By contrast I have more cache levels configured for my 64 bit version, so that's faster for general photography work.
-Noel

I want in LSMW SAME CODING. THIS IS USING BDC CALL TRANSACTION

REPORT ZXX_BDC_PRA NO STANDARD PAGE HEADING LINE-COUNT 20
 LINE-SIZE 150 .
Program Name :ZXX_BDC_PRA *
Object Id : *
Develper Name : praveen *
Start Date : 25.06.07 *
Description : uploading flat file to sap system *
*--structure for Data Uploading.
DATA: BEGIN OF IT_STR ,
 VKORG LIKE RF02D-VKORG,
 VTWEG LIKE RF02D-VTWEG,
 SPART LIKE RF02D-SPART,
 KTOKD LIKE RF02D-KTOKD,
 NAME1 LIKE KNA1-NAME1,
 SORTL LIKE KNA1-SORTL,
 ORT01 LIKE KNA1-ORT01,
 PSTLZ LIKE KNA1-PSTLZ,
 LAND1 LIKE KNA1-LAND1,
 SPRAS LIKE KNA1-SPRAS,
 END OF IT_STR.
*--Internal Table for Data Uploading.
DATA: ITAB LIKE IT_STR OCCURS 0.
*--Internal Table to sucessfull Records.
DATA: ITAB1 LIKE IT_STR OCCURS 0.
*--Internal Table to Store Error Records.
DATA: ITAB2 LIKE STANDARD TABLE OF IT_STR WITH HEADER LINE.
*--Internal Table for Storing the BDC data.
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*--Internal Table for storing the messages.
DATA: MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA: COUNT TYPE I VALUE 1,
 S VALUE 0, E VALUE 0.
Selection screen *
SELECTION-SCREEN BEGIN OF BLOCK b1
 WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE TYPE IBIPPARMS-PATH.
SELECTION-SCREEN END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
*functionality to use drill down list
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 PROGRAM_NAME = SYST-CPROG
 DYNPRO_NUMBER = SYST-DYNNR
 IMPORTING
 FILE_NAME = P_FILE.
Start-of-selection *
START-OF-SELECTION.
DATA FILENAME TYPE STRING.
FILENAME = P_FILE.
*-- Form to upload flatfile data into the internal table.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 FILENAME = FILENAME
 FILETYPE = 'ASC'
 HAS_FIELD_SEPARATOR = 'X'
 TABLES
 DATA_TAB = ITAB
 EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17.
*--Generating the BDC table for the fields of the internal table.
LOOP AT ITAB INTO IT_STR.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0107'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'RF02D-KTOKD'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_FIELD USING 'RF02D-VKORG'
 IT_STR-VKORG.
 PERFORM BDC_FIELD USING 'RF02D-VTWEG'
 IT_STR-VTWEG.
 PERFORM BDC_FIELD USING 'RF02D-SPART'
 IT_STR-SPART.
 PERFORM BDC_FIELD USING 'RF02D-KTOKD'
 IT_STR-KTOKD.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0110'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNA1-SPRAS'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_FIELD USING 'KNA1-NAME1'
 IT_STR-NAME1.
 PERFORM BDC_FIELD USING 'KNA1-SORTL'
 IT_STR-SORTL.
 PERFORM BDC_FIELD USING 'KNA1-ORT01'
 IT_STR-ORT01.
 PERFORM BDC_FIELD USING 'KNA1-PSTLZ'
 IT_STR-PSTLZ.
 PERFORM BDC_FIELD USING 'KNA1-LAND1'
 IT_STR-LAND1.
 PERFORM BDC_FIELD USING 'KNA1-SPRAS'
 IT_STR-SPRAS.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0120'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNA1-TXJCD'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0125'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNA1-NIELS'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0360'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNVK-NAMEV(01)'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ENTR'.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0310'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNVV-BEGRU'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '/00'.
 PERFORM BDC_DYNPRO USING 'SAPMF02D' '0324'.
 PERFORM BDC_FIELD USING 'BDC_CURSOR'
 'KNVP-PARVW(01)'.
 PERFORM BDC_FIELD USING 'BDC_OKCODE'
 '=ENTR'.
*--Calling the transaction 'Vd01'.
 CALL TRANSACTION 'VD01' USING BDCDATA MODE 'N' UPDATE 'S'
 MESSAGES INTO MESSTAB.
 PERFORM MESSAGES.
 REFRESH : BDCDATA, MESSTAB.
ENDLOOP.
END-OF-SELECTION.
*--Populating the Success records internal table.
IF ITAB1[] IS NOT INITIAL.
format color 5.
 WRITE: /'SUCCESSFUL RECORDS'.
 format color off.
 LOOP AT ITAB1 INTO IT_STR.
 WRITE:/ IT_STR-VKORG,IT_STR-VTWEG,
 IT_STR-SPART,IT_STR-KTOKD,
 IT_STR-NAME1,IT_STR-SORTL,
 IT_STR-ORT01,
 IT_STR-PSTLZ,
 IT_STR-LAND1,
 IT_STR-SPRAS.
 S = S + 1.
 ENDLOOP.
REFRESH : ITAB1.
 WRITE:/ 'TOTAL RECORDS',S.
ENDIF.
*--Populating the error records internal table.
IF ITAB2[] IS NOT INITIAL.
FORMAT COLOR 3.
 WRITE :/ 'ERRORS RECORDS ARE'.
FORMAT COLOR OFF.
 LOOP AT ITAB2.
 WRITE:/ ITAB2-VKORG,
 ITAB2-VTWEG,
 ITAB2-SPART,ITAB2-KTOKD,
 ITAB2-NAME1,ITAB2-SORTL,
 ITAB2-ORT01,
 ITAB2-PSTLZ,
 ITAB2-LAND1,
 ITAB2-SPRAS.
 E = E + 1.
 ENDLOOP.
REFRESH : ITAB2.
 WRITE: / 'TOTAL RECORDS',E.
REFRESH : ITAB2.
ENDIF.
End of Selection *
END-OF-SELECTION.
TOP-OF-PAGE *
TOP-OF-PAGE.
WRITE:/ SY-ULINE.
WRITE:/10 'REPORT ID',21 SY-REPID,35 'USERNAME',46 SY-UNAME,
60 'SYSTEM DATE',70 SY-DATUM,80 'SYSTEM TIME',90 SY-UZEIT,
100 'PAGE NO',108 SY-PAGNO.
WRITE:/ SY-ULINE.
FOrm to Populate the BDC table.
 Start new screen *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM. "BDC_DYNPRO
 Insert field *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL <> SPACE.
 CLEAR BDCDATA.
 BDCDATA-FNAM = FNAM.
 BDCDATA-FVAL = FVAL.
 APPEND BDCDATA.
ENDIF.
ENDFORM. "BDC_FIELD
*& Form messages
FORM MESSAGES .
LOOP AT MESSTAB.
 IF MESSTAB-MSGTYP = 'I'.
 WRITE : / MESSTAB-MSGV1.
 ELSEIF
MESSTAB-MSGTYP = 'S'.
 INSERT LINES OF ITAB FROM COUNT TO COUNT INTO TABLE ITAB1 .
 COUNT = COUNT + 1.
 WRITE : / MESSTAB-MSGV1.
 ELSEIF
 MESSTAB-MSGTYP = 'E'.
 INSERT LINES OF ITAB FROM COUNT TO COUNT INTO TABLE ITAB2.
 COUNT = COUNT + 1.
 WRITE : / MESSTAB-MSGV1.
 ENDIF.
ENDLOOP.
ENDFORM. " messages

Hi
Go through the doc and do the same using LSMW
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
1. Maintain Attributes:
Here you have to choose the second option and you can do the recording how this should work. Then assign the same to the Batch Input Recording name.
2. Maintain Source structure:
Create a structure name
3. Maintain Source field:
In this you have to create a structure same as that of the input file
eg: name
age
4. Maintain structure relations:
This will link the structure to the input file.
5. Maintain field mapping and conversion rules:
Here is the place where you can do coding, depending upon the code you have written or assignment you have done the values will get picked up from the file and get processed.
6. Maintain field mapping and conversion rules:
If you have any fixed values you can define here.
7. Specify files:
Specify the input file path and type.
8. Assign files:
This will assign ur file to the Input file
9. Read Data:
This will read ur data from teh file.
10. Dispaly Read Data:
You can see the uploaded data
11. Convert Data
This will convert the data to the corresponding format for processing
12. Display Converted data:
13. Create batch input session
Here this will create a batch input session for processing
14. Run Batch Input session:
By clicking on the session and process the same you can do teh needfu.
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
for Long texts Upload
Please take a look at this..
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
Reward points for useful Answers
Regards
Anji

What are the drawbacks or disadvantages of using LSMW

Hi All,
Can anyone tell me what could be the possible disadvantages of using LSMW and also some disadvantages of BAPI.
Regards,
MD.

Hi MD.
I would like to suggest a couple of disadvantages of LSMW.
Here are a few scenarios------>
1. Time consumption -
> IDOC processing plays a vital role. The changes made to the IDOC is therefore very time consuming.
2. In term of BAPI -
> Incomplete in terms of input fields of a particular transaction, rather it is not always complete.
3. In terms of Direct Input -
> No enjoy transactions and incomplete in terms of input fields of a particular transaction.
4. In terms of Batch input -
> Slow in terms of new recordings to be done, but BDCs are much simpler in that terms.
This factor also depends upon the user settings, The kind of processing which is foreground and background.
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

Adv of BDC over LSMW

What are the advantages of BDC over LSMW?

Hi,
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.
Thanks,
Sankar M

Doubt in uploading purchase order data using BDC

Hi friends,
how to upload purchase order data.
1) In both BDC and BAPI which one is preferable?
2) for suppose if it is through BDC, how to use? what are the transactions that we can use(SHDB, ME21N,ME21)?
3) To execute the job in background, is it possible for both call transaction and session method.
Thanks in advance
Sreenivas k

It really depends on the number of records you have. Still for a set of 5,000 records my answer to your questions will be:
1) In both BDC and BAPI which one is preferable? - Go with BDC
2) for suppose if it is through BDC, how to use? what are the transactions that we can use(SHDB, ME21N,ME21)? - Yes, its SHDB for recording, SE38 for abap program and ME21 for PO. Avoid SAP Enjoy transactions for recording as you may end up having problems wiht it.
3) To execute the job in background, is it possible for both call transaction and session method. - If you use call transaction method then you have to schedule the job to run in background or simply run it through F9 instead of F8. In case of session method you can chose to process the session in background. However I would suggest you go with BDC Session method for this.
- Guru
Reward points for helpful answers

Creation of Material using BDC Session method & global class

Hi
Creation of Material using BDC Session method & global class by using oops.
can anyone plz help me out

Hi,
it looks like it's not possible to call this BAPI wihtout material number. Here is a quote from BAPI documentation.
When creating material master data, you must transfer the material
number, the material type, and the industry sector to the method. You
must also enter a material description and its language.
Cheers

Change transaction using BDC-problem for large number of lines on screen

Hi All,
I am developing BAPI (using BDC) which creates quality notification in SAP which is entered via front end web application. Structure p_qmsm contain 3 lines of task in notification. The code is as given below. To avoid problem of large no of lines on screen,code lines starting with * is used. This actually for pagedown after entering every 2 lines and creates new line. so that 2 lines always push up on screen and there will not be problem for creating large no of lines on screen
perform bdc_dynpro using 'SAPLIQS0' '7200'.
perform bdc_field using 'BDC_OKCODE' '=10\TAB11'.
LOOP AT p_qmsm INTO wa_qmsm.
*IF wa_qmsm_cntr > 2.
       wa_qmsm_cntr = 2.
       perform bdc_dynpro using 'SAPLIQS0'                   '7204'.
       perform bdc_field   using 'BDC_OKCODE'                 '=PEND'.
ENDIF.
perform bdc_dynpro using 'SAPLIQS0' '7204'.
perform bdc_field using 'BDC_OKCODE' '/00'.
CONCATENATE 'VIQMSM-QSMNUM(' wa_qmsm_cntr ')' INTO wm_qmsm_qsmnum.
CONCATENATE 'VIQMSM-MNGRP(' wa_qmsm_cntr ')' INTO wm_qmsm_mngrp.
CONCATENATE 'VIQMSM-MNCOD(' wa_qmsm_cntr ')' INTO wm_qmsm_mncod.
CONCATENATE 'VIQMSM-MATXT(' wa_qmsm_cntr ')' INTO wm_qmsm_matxt.
perform bdc_field using wm_qmsm_qsmnum wa_qmsm-qsmnum.
perform bdc_field using wm_qmsm_mngrp wa_qmsm-mngrp.
perform bdc_field using wm_qmsm_mncod wa_qmsm-mncod.
perform bdc_field using wm_qmsm_matxt wa_qmsm-matxt.
wa_qmsm_cntr = wa_qmsm_cntr + 01.
ENDLOOP.
CALL TRANSACTION 'IQS2' USING wt_bdc
MODE 'N' UPDATE 'A' MESSAGES INTO P_MESSTAB.
The same code is used in modify mode also. web application is sending all 3 lines in modify mode even if single line is modified. It is already decided to send all rows back from web application to SAP in same sequence. It is working fine if i comment 5 lines which is starting with *. But in modify mode, how can i ensure that correct row is modified? and how can i achieve problem of large no of lines on screen?Please suggest?

Hi yogesh,
how can i ensure that correct row is modified?
1. For this we need to know two things ;
   a) the database table in which the entries are already stored
   b) the sequence in which they are displayed in the transaction.
2. So before changing any line, we need to compare (the primary key values / important values)
   a) as per the database table and as per the incoming data from web application (using bapi)
b) if the match is ok, it means that particular row was not modified, else modified.
how can i achieve problem of large no of lines on screen?
1. For this I am not sure about the transaction and its screen. Manytimes for appending row on the screen,
there is a PLUS + button on the grid toolbar. So for every entry, (inspite of some empty/filled rows already visible on the screen), we should use the + button, and this new row always appears on the top i.e. row number 1.
hope this helps.
regards,
amit m.

Disadvantages of Using BDC over BAPI

Similar Messages

Maybe you are looking for