WPS1 using BDC table

Hi,
Currently i have a program that call tcode WPS1 via BSP (internet explorer , ITS), i manage to pass data into WPS1 via BSP page using BDC and everything seem fine, but problem occur when i try to create a new revision at the WPS1 program.
Some how the popup window that allow us to key in Planning Plant and Revision Type seem to be not working. When i try to press F4 to retrieve the list of Planning Plant, it doesn't show the list. The problem doesn't occur when we call WPS1 without using BDC data.
the code is looks like :
call transaction 'WPS1' using it_bdctable mode 'E'.
my questions are:
1. is there any other way for me to pass data from bsp to wps1 without using bdc?
2. is there any other way to fix the issue mention above when i using bdc data?
Thank you.

Also, if you look inside the function module, you can go to any section of the sapscript form. Just use the appropriate component in your call, the default is HEADER.
Code from the EDIT_FORM function module
IF COMPONENT <> 'HEADER' AND
 COMPONENT <> 'PARAGRAPH' AND
 COMPONENT <> 'STRING' AND
 COMPONENT <> 'PAGE' AND
 COMPONENT <> 'WINDOW' AND
 COMPONENT <> 'PAGE_WINDOW' AND
 COMPONENT <> 'LAYOUT' AND
 COMPONENT <> 'DOCUMENTATION'.
Regards,
Rich Heilman

Similar Messages

How to upload material text in mm02 using bdc table control

i have problem to upload material Description in mm02 using bdc.
my text file is like
2000251     AF     A12345
2000251     AR     B12345
2000251     BG     C12345
2000252     AF     F12345
2000252     AR     G12345
2000252     AF     H12345
i want to upload material number, language, and material description, how can i upload pls help me.

Hi,
Try with bapi , bapi_material_save_data.. didn't exactly remember it,Please check the same.
Regards,
Nagaraj

A question when using BDC tables

Hi
suppose i have a session named SESSION1, in which there are 100 transactions.
now i want to know each transaction's status ( processed or incorrect ), how to do this using ABAP code?
i searched standard tables such as APQI,APQD,APQL but found nothing i want.
thanks & best rgds.

thanks.
i used sql trace and found the only related tables were BDCUSEOP/APQI/APQD/APQL/TST01. Also couldn't find data i want......
Would you pls help to check these tables?
regards

BDC table control using Excel sheet upload

Hi All,
I am working BDC table control.I want to upload the From excel sheet.I am using the FM ALSM_EXCEL_TO_INTERNAL_TABLE to upload the the data into my internal table.The data is populating in the internal table.
Now i have problem tat how to populate this excel sheet data to the Bdc table control.
Can nybody help me out.\[removed by moderator\]
Thanks,
Swapna.
Edited by: Jan Stallkamp on Jul 25, 2008 10:57 AM

after fetching data from EXCEL sheet, each column data (in excel sheet) will be uploaded to individual record into your internal table along with row number and column number, loop through that internal table and collect all your excel data into record format.pls refer the below code.
data:
 i_excel type alsmex_tabline occurs 0 with header line,
 l_row type i value 1.
data:
 begin of x_data occurs 0,
 kunnr like RF02L-KUNNR,
 klimk(17) type c,
 CTLPC like knkk-CTLPC,
 end of x_data,
 begin of x_data1 occurs 0,
 data(106),
 end of x_data1.
call function 'ALSM_EXCEL_TO_INTERNAL_TABLE'
 exporting
 filename = p_fname
 i_begin_col = 1
 i_begin_row = 1
 i_end_col = no.of columns in your excel file
 i_end_row = no.of rows in your file
 tables
 intern = i_excel.
if sy-subrc = 0.
 loop at i_excel.
 if l_row <> i_excel-row.
 append x_data.
 clear x_data.
 endif.
 case i_excel-col.
 when 1.
 x_data-kunnr = i_excel-value.
 when 2.
 x_data-klimk = i_excel-value.
 when 3.
 x_data-CTLPC = i_excel-value.
 endcase.
 l_row = i_excel-row.
 clear i_excel.
 at last.
 append x_data.
 endat.
 endloop.
endif.
then loop through the internal table X_DATA, pass the data to your table control like.
tbl_control-field1(1) = x_data-field1.
tbl_control-field2(1) = x_data-field2.
tbl_control-fieldn(1) = x_data-fieldn.
Regards,
Sreeram.

What is the use of table control in bdc is it same in module pool table con

Hi,
What is the use of table control in bdc is it same in module pool table control?
regards
eswar

Hi,
Table control means it contains as table and it will scroll in vertical and horizontal.
In module pool by using screen we can create new table control.
But BDC table control means here we can populate the data into the table control.
i.e.if you take VA01 for sales order creation in the belwo of VA01 screen there is table control for the filling of material details so here we will write the code to populate the data into the table control screen.
Thanks and regards,
shyla

I want to update standard table field (EKES-EINDT)? Not using BDC using FM.

Hi all,
I would like to seek for you help, to resolve a problem.
I need to know how can i update the EINDT(date) field in the EKES table.
Is there any Function Module or BAPI available for update EKES-EINDT ?
And my requirement is don't use BDC.
Currently I am doing in following way
LOOP AT I_DATA.
UPDATE EKES SET EINDT = P_NEWDAT
WHERE EBELN = I_DATA-EBELN
AND EBELP = I_DATA-EBELP
AND ETENS = I_DATA-ETENS.
ENDLOOP.
I know we should not update standard table directly. This will only update EKES it will not update other tables related with EKES-EINDT.
Got my point?
Please help me it's on high priority.

EKES can be updated with function module
ME_CONFIRMATION_UPDATE

Is it possible to use u2018CALL TRANSACTIONu2019 without a BDC table ?

HIIIIIIIIIIII
Is it possible to use u2018CALL TRANSACTIONu2019 without a BDC table ?
THANKS

Hi,
Yes you can,
CALL TRANSACTION ta { [AND SKIP FIRST SCREEN] .
This addition suppresses the display of a screen of the initial dynpro of a called dialog transaction. The addition AND SKIP FIRST SCREEN suppresses the first screen under these prerequisites:
For the initial dynpro, in the Screen Painter the own dynpro number must not be specified as the next screen number.
All mandatory input fields of the initial dynpro must be filled completely and with the correct values by the SPA/GPA parameters
If these prerequisites are met, that screen of the dynpro is displayed that is specified in the Screen Painter as the next dynpro of the initial dynpro.
Regards
Jana

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

How to determine fixed line of table control using BDC program ?

Dear All,
I create program using BDC that contains table control.
Unfortunately the table control line of BDC program will depend on the resolution of our PC setting.
Sometime I have 2 lines, sometime 3 lines (in different PC).
How to determine fixed line of table control?
So it will never be confusing me whether I have 2 or 3 lines.
Thnx - Regards,
(Taufik K.)

Hi Taufik,
Check the table CTU_PARAMS and field DEFSIZE for setting fixed line of a table control.
CALL TRANSACTION 'VA01' USING it_bdcdata
OPTIONS FROM OPT
MESSAGES INTO it_mesg.
opt of type ctu_params.
WA_CTU_PARAMS-DISMODE = 'N'. "no screen mode
WA_CTU_PARAMS-UPDMODE = 'S'. "synchronus update
WA_CTU_PARAMS-NOBINPT = 'X'.
WA_CTU_PARAMS-NOBIEND = 'X'.
WA_CTU_PARAMS-DEFSIZE = 'X'. "Default size
Default size will play good role in terms of resoultion. in one system in table control you can see 10rows, but in others system it will show 20 records. it depends on resoultion. but when you set the default size then it will take same (default screen size) in all the systems when you run BDC.
Reward if helps.
Regards,
Senthil
Message was edited by: senthil kumar

Fields in a BDC table

hai gurus....
What are the fields in a BDC table???
Thanks
Pavan

hi,
i hope this answer will helps you..........,
the BDCDATA table contains fields are...
BDCDATA-PROGRAM-----> this field describes the module pool program name which we are used for vaidating and updating the data.
BDCDATA-DYNPRO----
> this field describes the currently active screen.
BDCDATA-DYNBEGIN-------> this field describes the default or initial screen.
BDCDATA-FNAM----
> this field describes the field name which we are used in validations.
BDCDATA-FVAL----
> this field describes the field value which we are used in validations.
by using the above table we perfome the mapping logic in BDC for validating and updating the legacy system data.
regards,
Ashok Reddy
Message was edited by:
Ashok Reddy

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

How to display the output screen when I use bdc.

hey expert,
I want to display the output screen when i use bdc without using mode 'A'.
thank you.

Hi,
You can go for mode 'E'.. it will display the output screen directly and if there is any error in the transaction you would get that particular screen and you can correct and continue after which you will get the final screen if anything goes fine...
check this sample code....
I had a program if you execute below program it automatically creates a new zprogram.
REPORT zprogram_create_recording.
PARAMETER:
p_prog    TYPE sy-repid OBLIGATORY,
p_shtxt TYPE repti OBLIGATORY,
p_pack TYPE devclass DEFAULT '$tmp'.
DATA:
t_bdcdata LIKE
   STANDARD TABLE
         OF bdcdata.
DATA:
wa_bdcdata LIKE LINE OF t_bdcdata.
REFRESH t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-program    = 'SAPLWBABAP'.
wa_bdcdata-dynpro     = '0100'.
wa_bdcdata-dynbegin   = 'X'.
wa_bdcdata-fnam       = 'RS38M-PROGRAMM'.
wa_bdcdata-fval       = p_prog.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam       = 'BDC_OKCODE'.
wa_bdcdata-fval       = 'NEW'.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-program    = 'SAPLSEDTATTR'.
wa_bdcdata-dynpro     = '0200'.
wa_bdcdata-dynbegin   = 'X'.
wa_bdcdata-fnam       = 'RS38M-REPTI'.
wa_bdcdata-fval       = p_shtxt.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam       = 'TRDIR-SUBC'.
wa_bdcdata-fval       = '1'.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam       = 'BDC_OKCODE'.
wa_bdcdata-fval       = 'CONT'.
APPEND wa_bdcdata TO t_bdcdata.
IF p_pack EQ '$TMP'.
*local object
CLEAR wa_bdcdata.
wa_bdcdata-program    = 'SAPLSTRD'.
wa_bdcdata-dynpro     = '0100'.
wa_bdcdata-dynbegin   = 'X'.
wa_bdcdata-fnam       = 'KO007-L_DEVCLASS'.
wa_bdcdata-fval       = ' '.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam       = 'BDC_OKCODE'.
wa_bdcdata-fval       = 'TEMP'.
APPEND wa_bdcdata TO t_bdcdata.
ELSE.
*package assignment with request
CLEAR wa_bdcdata.
wa_bdcdata-program    = 'SAPLSTRD'.
wa_bdcdata-dynpro     = '0100'.
wa_bdcdata-dynbegin   = 'X'.
wa_bdcdata-fnam       = 'KO007-L_DEVCLASS'.
wa_bdcdata-fval       = p_pack.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam       = 'BDC_OKCODE'.
wa_bdcdata-fval       = 'ADD'.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-program    = 'SAPLSTRD'.
wa_bdcdata-dynpro     = '0300'.
wa_bdcdata-dynbegin   = 'X'.
wa_bdcdata-fnam       = 'KO008-TRKORR'.
wa_bdcdata-fval       = ' '.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam       = 'KO008-AS4TEXT'.
wa_bdcdata-fval       = ' '.
APPEND wa_bdcdata TO t_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam       = 'BDC_OKCODE'.
wa_bdcdata-fval       = 'LOCK'.
APPEND wa_bdcdata TO t_bdcdata.
ENDIF.                                 " IF P_PACK EQ '$TMP'
CALL TRANSACTION 'SE38' USING t_bdcdata MODE 'E'.
Hope this would help you..
Regards
Narin Nandivada

Capturing EPC error List into a local file using BDC

Can anyone let me know the Code for downloading the EPC check Results into a local File using BDC...[

You can use the function module
EXTENDED_PROGRAM_CHECK to get the errors and warnigs of a epc for a program.
then you can download that internal table information using GUI_DOWNLOAD fm.
Regards,
Ravi

Error while posting business area to TCODE J1IH using BDC

Hi ,
Using BDC i am trying to post values to J1IH.
Here, the business area is not getting posted.
Can you help me ?
regards
ekadevi S

Thanks for your quick response, Michael!
I have another question on import. I imported a folder and it got imported with a warning (A folder named 'Folder Name' was created or modified during the import but is not in a business area
Import completed, but with warnings. Please check the result.
I can see the folder in the database table. Is there a way to add this folder to the business area? Or my only option is to delete the folder out of EUL?
Thanks once again!
AJ

Call transaction using bdc tab and also skip first screen??

Hi,
Please help.
I want to call transaction PA30 fill it with values which are determined only at runtime and then skip first screen.
The screen doesn't have parameter fields so i cannot use 'set parameter id'.
I also cannot create a transaction with parameters as I only have these at runtime.
Anyone done anything like this???

hi,
you might be populateing the itab bdc_tab with the corresponding values fronm the recording.
while doing the recording go until to the screen wher u want to finsih.
and populate the bdc_tab wit the ok code,screen number and the value.
this will do.
for eg see the code below.
METHOD analyze_log.
DATA : wrk_extid TYPE balhdr-extnumber.
DATA : wrk_date(10) TYPE c.
DATA : it_rspar TYPE TABLE OF rsparams .
DATA : wa_rspar TYPE rsparams.
DATA: it_bdcdata TYPE STANDARD TABLE OF bdcdata,
      wa_bdcdata TYPE bdcdata.
DATA: params TYPE ctu_params.
CONSTANTS : object TYPE balhdr-object VALUE 'ZKIV_LOG'.
IF wa_kopf-vertr_nr IS NOT INITIAL.
    CONCATENATE wa_kopf-vertr_nr '/' wa_kopf-nachtr_nr INTO wrk_extid.
    wrk_date = '01.09.2006'.
    SET PARAMETER ID 'BALOBJ' FIELD object .
    SET PARAMETER ID 'BALEXT' FIELD wrk_extid.
    wa_rspar-selname = 'ALDATE'.
    wa_rspar-sign = 'I'.
    wa_rspar-kind = 'P'.
    wa_rspar-option = 'EQ'.
    wa_rspar-low = wrk_date.
    APPEND wa_rspar TO it_rspar.
ELSE.
    CLEAR wrk_extid.
    SET PARAMETER ID 'BALEXT' FIELD wrk_extid.
ENDIF.
Update BDC tab
--Call SLG1 using BDC--&
params-dismode = 'E'. "Show errors only
CLEAR wa_bdcdata.
wa_bdcdata-program = 'SAPLSLG3'.
wa_bdcdata-dynpro   = '0100'.
wa_bdcdata-dynbegin = 'X'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_CURSOR'.
wa_bdcdata-fval = 'BALHDR-ALDATE'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BALHDR-ALDATE'.
wa_bdcdata-fval = wrk_date.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_OKCODE'.
wa_bdcdata-fval = '=SELE'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-program = 'SAPLSLG3'.
wa_bdcdata-dynpro   = '0100'.
wa_bdcdata-dynbegin = 'X'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_OKCODE'.
wa_bdcdata-fval = '=&F03'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_SUBSCR'.
wa_bdcdata-fval = 'SAPLSBAL_DISPLAY                        0101SUBSCREEN'.
APPEND wa_bdcdata TO it_bdcdata.
CALL TRANSACTION 'SLG1' USING it_bdcdata OPTIONS FROM params.
--End of BDC--&
ENDMETHOD.
here wat i m doing is that i dont want the subscreen 101 to be displayed..
Message was edited by:
        Sandeep S

WPS1 using BDC table

Similar Messages

Maybe you are looking for